Patent Description:
The following abbreviations are herewith defined, at least some of which are referred to within the following description: Third Generation Partnership Project ("3GPP"), Acknowledge Mode ("AM"), Backhaul ("BH"), Broadcast Multicast ("BM"), Buffer Occupancy ("BO"), Base Station ("BS"), Bandwidth Part ("BWP"), Component Carrier ("CC"), Coordinated Multipoint ("CoMP"), Control Plane ("CP"), CSI-RS Resource Indicator ("CRI"), Channel State Information ("CSI"), Channel Quality Indicator ("CQI"), Central Unit ("CU"), Codeword ("CW"), Downlink ("DL"), Demodulation Reference Signal ("DMRS"), Data Radio Bearer ("DRB"), Distributed Unit ("DU"), Enhanced Mobile Broadband ("eMBB"), Evolved Node B ("eNB"), Enhanced Subscriber Identification Module ("eSIM"), Enhanced ("E"), Frequency Division Duplex ("FDD"), Frequency Division Multiple Access ("FDMA"), Frequency Range ("FR"), Hybrid Automatic Repeat Request ("HARQ"), Integrated Access Backhaul ("IAB"), Identity or Identifier or Identification ("ID"), Information Element ("IE"), Interference Measurement ("IM"), International Mobile Subscriber Identity ("IMSI"), Internet-of Things ("IoT"), Internet Protocol ("IP"), Joint Transmission ("JT"), Level <NUM> ("L1"), Logical Channel ("LCH"), Logical Channel Prioritization ("LCP"), Long Term Evolution ("LTE"), Multiple Input Multiple Output ("MIMO"), Mobile-Termination ("MT"), Machine Type Communication ("MTC"), Multi-User MIMO ("MU-MIMO"), Negative-Acknowledgment ("NACK") or ("NAK"), Next Generation ("NG"), Next Generation Node B ("gNB"), New Radio ("NR"), Non-Zero Power ("NZP"), Orthogonal Frequency Division Multiplexing ("OFDM"), Peak-to-Average Power Ratio ("PAPR"), Physical Broadcast Channel ("PBCH"), Physical Downlink Shared Channel ("PDSCH"), Policy Control Function ("PCF"), Packet Data Convergence Protocol ("PDCP"), Packet Data Network ("PDN"), Protocol Data Unit ("PDU"), Public Land Mobile Network ("PLMN"), Precoding Matrix Indicator ("PMI"), Packet Switched ("PS"), Primary Synchronization Signal ("PSS"), Quasi Co-Located ("QCL"), Quality of Service ("QoS"), Radio Access Network ("RAN"), Radio Access Technology ("RAT"), Resource Element ("RE"), Rank Indicator ("RI"), Radio Link Failure ("RLF"), Radio Resource Control ("RRC"), Reference Signal ("RS"), Reference Signal Received Power ("RSRP"), Reference Signal Received Quality ("RSRQ"), Receive ("RX"), Secondary Cell ("SCell"), Service Data Unit ("SDU"), Subscriber Identity Module ("SIM"), Signal-to-Interference and Noise Ratio ("SINR"), Sequence Number ("SN"), Synchronization Signal ("SS"), SS/PBCH Block ("SSB"), Secondary Synchronization Signal ("SSS"), Time Division Multiplexing ("TDM"), Temporary Mobile Subscriber Identity ("TMSI"), Transmission Reception Point ("TRP"), Transmit ("TX"), User Entity/Equipment (Mobile Terminal) ("UE"), Universal Integrated Circuit Card ("UICC"), Uplink ("UL"), Unacknowledged Mode ("UM"), Universal Mobile Telecommunications System ("UMTS"), User Plane ("UP"), Universal Subscriber Identity Module ("USIM"), Universal Terrestrial Radio Access Network ("UTRAN"), Voice Over IP ("VoIP"), Visited Public Land Mobile Network ("VPLMN"), and Worldwide Interoperability for Microwave Access ("WiMAX"). As used herein, "HARQ-ACK" may represent collectively the Positive Acknowledge ("ACK") and the Negative Acknowledge ("NAK"). ACK means that a TB is correctly received while NAK means a TB is erroneously received.

In certain wireless communications networks, handover requests may be used. In such networks, a handover request may supply limited information.

<CIT> describes V2X parameter exchange and handover between base stations.

Claim <NUM> defines a method performed by a source device, claim <NUM> defines a source device, and claim <NUM> defines a processor for wireless communication. In the following, any method and/or apparatus referred to as embodiments but nevertheless do not fall within the scope of the appended claims are to be understood as examples helpful in understanding the invention.

Methods for transmitting handover requests with network information are disclosed. Apparatuses and systems also perform the functions of the apparatus. In one embodiment, the method includes transmitting a handover request to a target device. In such an embodiment, the handover request includes: first information indicating that a source communication network corresponding to a source device is unable to support a predetermined quality of service; and second information corresponding to capacity of the source communication network. In certain embodiments, the method includes receiving a response to the handover request.

An apparatus for transmitting handover requests with network information, in one embodiment, includes a transmitter that transmits a handover request to a target device. In such an embodiment, the handover request includes: first information indicating that a source communication network corresponding to a source device is unable to support a predetermined quality of service; and second information corresponding to capacity of the source communication network. In various embodiments, the apparatus includes a receiver that receives a response to the handover request.

One method for receiving handover requests with network information includes receiving, at a target device, a handover request from a source device. In such embodiments, the handover request includes: first information indicating that a source communication network corresponding to the source device is unable to support a predetermined quality of service; and second information corresponding to capacity of the source communication network. In some embodiments, the method includes transmitting a response to the handover request.

An apparatus for receiving handover requests with network information, in one embodiment, includes a receiver that receives a handover request at the apparatus from a source device. In such an embodiment, the handover request includes: first information indicating that a source communication network corresponding to the source device is unable to support a predetermined quality of service; and second information corresponding to capacity of the source communication network. In various embodiments, the apparatus includes a transmitter that transmits a response to the handover request.

The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments, In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).

<FIG> depicts an embodiment of a wireless communication system <NUM> for transmitting and/or receiving handover requests with network information. In one embodiment, the wireless communication system <NUM> includes remote units <NUM> and network units <NUM>. Even though a specific number of remote units <NUM> and network units <NUM> are depicted in <FIG>, one of skill in the art will recognize that any number of remote units <NUM> and network units <NUM> may be included in the wireless communication system <NUM>.

In one embodiment, the remote units <NUM> may include computing devices, such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), IoT devices, or the like. The remote units <NUM> may communicate directly with one or more of the network units <NUM> via UL communication signals.

In certain embodiments, a network unit <NUM> may also be referred to as an access point, an access terminal, a base, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a RAN, a relay node, a device, a network device, an IAB node, a donor IAB node, or by any other terminology used in the art.

In one implementation, the wireless communication system <NUM> is compliant with the <NUM> or NG (Next Generation) of the 3GPP protocol, wherein the network unit <NUM> transmits using NG RAN technology. More generally, however, the wireless communication system <NUM> may implement some other open or proprietary communication protocol, for example, WiMAX, among other protocols.

In various embodiments, a network unit <NUM> may transmit and/or receive handover requests with network information. In some embodiments, the network unit <NUM> may transmit a handover request to a target device. In these embodiments, the handover request includes: first information indicating that a source communication network corresponding to a source device is unable to support a predetermined quality of service; and second information corresponding to capacity of the source communication network. In these embodiments, the network unit <NUM> may receive a response to the handover request.

In various embodiments, a network unit <NUM> may transmit and/or receive handover requests with network information. In some embodiments, the network unit <NUM> may receive, at the network unit <NUM>, a handover request from a source device. In such embodiments, the handover request includes: first information indicating that a source communication network corresponding to the source device is unable to support a predetermined quality of service; and second information corresponding to capacity of the source communication network. In these embodiments, the network unit <NUM> may transmit a response to the handover request. Accordingly, a network unit <NUM> may be used for transmitting and/or receiving handover requests with network information.

<FIG> depicts one embodiment of an apparatus <NUM> that may be used for communication with a network. The apparatus <NUM> includes one embodiment of the remote unit <NUM>. Furthermore, the remote unit <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, a display <NUM>, a transmitter <NUM>, and a receiver <NUM>. In some embodiments, the input device <NUM> and the display <NUM> are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit <NUM> may not include any input device <NUM> and/or display <NUM>. In various embodiments, the remote unit <NUM> may include one or more of the processor <NUM>, the memory <NUM>, the transmitter <NUM>, and the receiver <NUM>, and may not include the input device <NUM> and/or the display <NUM>.

The transmitter <NUM> is used to provide UL communication signals to the network unit <NUM> and the receiver <NUM> is used to receive DL communication signals from the network unit <NUM>.

<FIG> depicts one embodiment of an apparatus <NUM> that may be used for transmitting and/or receiving handover requests with network information. The apparatus <NUM> includes one embodiment of the network unit <NUM>. Furthermore, the network unit <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, a display <NUM>, a transmitter <NUM>, and a receiver <NUM>. As may be appreciated, the processor <NUM>, the memory <NUM>, the input device <NUM>, the display <NUM>, the transmitter <NUM>, and the receiver <NUM> may be substantially similar to the processor <NUM>, the memory <NUM>, the input device <NUM>, the display <NUM>, the transmitter <NUM>, and the receiver <NUM> of the remote unit <NUM>, respectively.

In one embodiment, the transmitter <NUM> transmits a handover request to a target device. In such an embodiment, the handover request includes: first information indicating that a source communication network corresponding to a source device is unable to support a predetermined quality of service; and second information corresponding to capacity of the source communication network. In various embodiments, the receiver <NUM> receives a response to the handover request.

In some embodiments, the receiver <NUM> receives a handover request at the apparatus from a source device. In such embodiments, the handover request includes: first information indicating that a source communication network corresponding to the source device is unable to support a predetermined quality of service; and second information corresponding to capacity of the source communication network. In various embodiments, the transmitter <NUM> transmits a response to the handover request.

Although only one transmitter <NUM> and one receiver <NUM> are illustrated, the network unit <NUM> may have any suitable number of transmitters <NUM> and receivers <NUM>.

<FIG> is a schematic block diagram illustrating one embodiment of an integrated access backhaul ("IAB") system <NUM>. The IAB system <NUM> includes a first UE <NUM>, a second UE <NUM>, a first IAB node <NUM>, an IAB donor node <NUM>, a second IAB node <NUM>, a third IAB node <NUM>, and a fourth IAB node <NUM>. As illustrated, the first UE <NUM> is connected to the IAB donor node <NUM> via the first IAB node <NUM>. Moreover, the second UE <NUM> is connected to the IAB donor node <NUM> via the second IAB node <NUM>, the third IAB node <NUM>, and the fourth IAB node <NUM>. The IAB system <NUM>, as illustrated, may be used for multi-hop backhauling via multiple IAB nodes.

As may be appreciated, multi-hop backhauling systems may provide a larger range extension than single hop systems. This may especially be beneficial for frequencies above <NUM> due to a limited range of such frequencies. In some configurations, multi-hop backhauling enables backhauling around obstacles (e.g., buildings).

A maximum number of hops in a deployment may depend on many factors such as frequency, cell density, propagation environment, and traffic load. Thus, flexibility in hop count may be desirable. With an increased number of hops, scalability issues may arise, performance may be limited, and/or signaling load may increase signaling load to undesirable levels.

As may be appreciated, wireless backhaul links may be vulnerable to blockage (e.g., due to moving objects such as vehicles, due to seasonal changes (foliage), due to infrastructure changes (new buildings), and so forth). Such vulnerability may also apply to physically stationary IAB-nodes. In <FIG>, the first UE <NUM> may switch from communicating via the first IAB node <NUM> to communicating with the second IAB node <NUM> if a backhaul link is blocked by objects (e.g., moving objects). Moreover, traffic variations may create uneven load distribution on wireless backhaul links leading to local link congestion and/or node congestion.

In some embodiments, an IAB node may include MT and DU functions. The MT function may be a component of a mobile equipment, or, as used herein, MT may be a function residing on an IAB node that terminates radio interface layers of a backhaul Uu interface toward the IAB-donor or other IAB nodes.

In various embodiments, a gNB may include a gNB-CU and one or more gNB-DUs. Moreover, a gNB-CU and a gNB-DU may be connected via an F1 interface. A gNB-CU may be a gNB central unit that is a logical node hosting RRC, SOAP, and PDCP protocols of the gNB. Furthermore, a gNB-DU may be a gNB distributed unit that is a logical node hosting RLC, MAC, and PHY layers of the gNB. In some embodiments, one cell is supported by only one gNB-DU.

In <FIG> the IAB nodes may be in a standalone mode which includes one IAB-donor and multiple lAB-nodes. The IAB-donor node <NUM> may be treated as a single logical node that includes a set of functions such as gNB-DU, gNB-CU-CP, gNB-CU-UP and potentially other functions. In certain embodiments, the lAB-donor node <NUM> may be split according to its functions which can all be either collocated or non-collocated as allowed by 3GPP NG-RAN architecture.

<FIG> is a schematic block diagram illustrating one embodiment of a handover procedure <NUM>. A remote unit (UE <NUM>), a source gNB <NUM>, and a target gNB <NUM> communicate as part of the handover procedure <NUM>. As may be appreciated, any of the communications described in this and other embodiments may include one or more messages as part of a communication.

The handover procedure <NUM> includes a first communication <NUM> transmitted from the source gNB <NUM> to the target gNB <NUM>. The first communication <NUM> may include the source gNB <NUM> initiating handover and issuing a handover request, such as over an Xn interface (e.g., an inter-base station interface).

The target gNB <NUM> may perform admission control at step <NUM> and may provide an RRC configuration as part of a handover acknowledgement.

The handover procedure <NUM> includes a second communication <NUM> transmitted from the target gNB <NUM> to the source gNB <NUM>. The second communication <NUM> may include the target gNB <NUM> transmitting the handover acknowledgement to the source gNB <NUM>.

In a third communication <NUM> transmitted from the source gNB <NUM> to the UE <NUM>, the source gNB <NUM> may provide the RRC configuration to the UE <NUM> in a handover command. A message having the handover command may also include at least a cell ID and all information (e.g., access information) required to access the target cell so that the UE <NUM> can access the target cell without reading system information. For some configurations, the information required for contention-based and contention-free random access may be included in the message having the handover command. Moreover, access information for the target cell may include beam specific information.

The UE <NUM> may move (e.g., reconfigure), at step <NUM>, its RRC connection to the target gNB <NUM>. Furthermore, in a fourth communication <NUM> transmitted from the UE <NUM> to the target gNB <NUM>, the UE <NUM> may transmit a handover complete reply to the target gNB <NUM>.

<FIG> is a schematic block diagram illustrating one embodiment of an unsuccessful handover procedure <NUM>. A source gNB <NUM> and a target gNB <NUM> communicate as part of the unsuccessful handover procedure <NUM>.

The unsuccessful handover procedure <NUM> includes a first communication <NUM> transmitted from the source gNB <NUM> to the target gNB <NUM>. The first communication <NUM> may include a handover request.

If the target gNB <NUM> does not admit at least one PDU session resource, or a failure occurs during handover preparation, the target gNB <NUM>, in a second communication <NUM>, transmits a message including a handover preparation failure indication to the source gNB <NUM>. The message may include a cause IE with an appropriate value. The handover preparation failure may inform the source gNB <NUM> that handover preparation has failed.

<FIG> is a schematic block diagram illustrating another embodiment of an integrated access backhaul system <NUM>. The integrated access backhaul system <NUM> includes a first UE <NUM> ("UE1"), a second UE <NUM> ("UE2), a first donor central unit <NUM> ("Donor CU1"), a second donor central unit <NUM> ("Donor CU2"), a first donor distributed unit <NUM> ("Donor DU1"), a second donor distributed unit <NUM> ("Donor DU2"), a first IAB node <NUM> ("IAB node1"), a second IAB node <NUM> ("IAB node2"), a third IAB node <NUM> ("IAB node3"), a fourth IAB node <NUM> ("IAB node4"), and a fifth IAB node <NUM> ("IAB node5"). As illustrated, the fifth IAB node <NUM> accesses the first donor central unit <NUM> by connecting to the third IAB node <NUM>. However, the first donor central unit <NUM> may send information that triggers the fifth IAB node <NUM> to move to the second donor central unit <NUM> based on information such as Uu channel quality and/or loading, as illustrated by arrow <NUM>. Thus, the third IAB node <NUM> may be a source IAB node, and the fourth IAB node <NUM> may be a target IAB node for upstream communication from the fifth IAB node <NUM>.

<FIG> is a schematic block diagram illustrating another embodiment of a handover procedure <NUM>. An IAB node <NUM>, a source IAB node <NUM>, a source donor CU <NUM>, a target donor CU <NUM>, and a target IAB node <NUM> communicate as part of the handover procedure <NUM>. The handover procedure <NUM> provides one embodiment of communications that may be used to transition communication from the IAB node <NUM> (e.g., fifth IAB node <NUM>) communicating with the source IAB node <NUM> (e.g., third IAB node <NUM>) to the target IAB node <NUM> (e.g., fourth IAB node <NUM>).

In one embodiment, in a first communication <NUM> transmitted from the source donor CU <NUM> to the target donor CU <NUM>, the source donor CU <NUM> may initiate handover and may transmit a handover request over an Xn interface (e.g., an inter-base station interface) to the target donor CU <NUM>. In some embodiments, a new cause IE may be added to the handover request to indicate that a current backhaul link (e.g., source backhaul link corresponding to the source IAB node <NUM>) cannot meet QoS requirements. In certain embodiments, the QoS requirement corresponds to a type of communication service (e.g., URLLC, MTC, eMBB, etc.). In various embodiments, the new cause IE may indicate "QoS not supported for backhaul link reason," "latency not supported for backhaul link reason," "bit rate not supported for backhaul link reason," "deterioration of backhaul link quality," and/or other reasons. In one embodiment, the handover request may include IAB related information (e.g., corresponding to the source IAB node <NUM>). In some embodiments, the IAB related information may include an uplink IAB aggregated maximum bit rate and/or a downlink IAB aggregated maximum bit rate. An aggregated maximum bit rate may include a combination of bit rates for all uplink and/or downlink devices that communicate with a particular IAB node (e.g., the source IAB node <NUM>). In various embodiments, the IAB related information may include a number of UEs served by a particular IAB node (e.g., the source IAB node <NUM>) and/or a number of downstream IAB nodes corresponding to the particular IAB node.

In certain embodiments, in a second communication <NUM> transmitted from the target donor CU <NUM> to the target IAB node <NUM>, the target donor CU <NUM> may send a UE context setup request message to the target IAB node <NUM> to create a UE context and setup one or more bearers.

In some embodiments, in a third communication <NUM> transmitted from the target IAB node <NUM> to the target donor CU <NUM>, the target IAB node <NUM> may respond to the target donor CU <NUM> with a UE context setup response message.

In various embodiments, in a fourth communication <NUM> transmitted from the target donor CU <NUM> to the source donor CU <NUM>, the target donor CU <NUM> may perform admission control and may provide an RRC configuration as part of a handover acknowledgement to the source donor CU <NUM>.

In one embodiment, in a fifth communication <NUM> transmitted from the source donor CU <NUM> to the source IAB node <NUM>, the source donor CU <NUM> may send a UE context modification request message to the source IAB node <NUM> which includes a generated RRCConnectionReconfiguration message for the IAB node <NUM>.

In certain embodiments, in a sixth communication <NUM> transmitted from the source IAB node <NUM> to the IAB node <NUM>, the source IAB node <NUM> may provide the RRC configuration to the IAB node <NUM> in a handover command message. The handover command message may include at least a cell ID (e.g., target IAB node <NUM> ID) and all information required to access the target IAB node <NUM>.

In some embodiments, in a seventh communication <NUM> transmitted from the IAB node <NUM> to the target IAB node <NUM>, the IAB node <NUM> may move its RRC connection to the target IAB node <NUM> and send a reply to the IAB node <NUM> having a handover complete message indicating that handover is complete.

<FIG> is a schematic block diagram illustrating another embodiment of an unsuccessful handover procedure <NUM>. A source donor CU <NUM> and a target donor CU <NUM> communicate as part of the unsuccessful handover procedure <NUM>.

In one embodiment, in a first communication <NUM> transmitted from the source donor CU <NUM> to the target donor CU <NUM>, the source donor CU <NUM> may initiate handover and may transmit a handover request message over an Xn interface (e.g., an inter-base station interface) to the target donor CU <NUM>.

The target donor CU <NUM> may perform <NUM> admission control and may determine that the handover request is to be denied.

In certain embodiments, in a second communication <NUM> from the target donor CU <NUM> to the source donor CU <NUM>, the target donor CU <NUM> may transmit a handover preparation failure indication that includes a cause (e.g., a cause IE) to the source donor CU <NUM>. In various embodiments, the cause may indicate that the handover request is denied because a handover may cause a backhaul link overload at a communication network of the target donor CU <NUM>, the backhaul link of the communication network of the target donor CU <NUM> has limited capacity, and/or other reasons.

<FIG> is a schematic flow chart diagram illustrating one embodiment of a method <NUM> for transmitting handover requests with network information. In some embodiments, the method <NUM> is performed by an apparatus, such as the network unit <NUM> (e.g., IAB node). In certain embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM> may include transmitting <NUM> a handover request to a target device. In such an embodiment, the handover request includes: first information indicating that a source communication network corresponding to a source device is unable to support a predetermined quality of service; and second information corresponding to capacity of the source communication network. In certain embodiments, the method <NUM> includes receiving <NUM> a response to the handover request.

In certain embodiments, the target device comprises a target central unit, a target integrated access backhaul node, or a combination thereof. In some embodiments, the source communication network comprises a source backhaul link. In various embodiments, the source device comprises a source central unit, a source integrated access backhaul node, or a combination thereof.

In one embodiment, the predetermined quality of service corresponds to a type of communication service. In certain embodiments, the predetermined quality of service comprises a latency, a bit rate, a deterioration level, or some combination thereof. In some embodiments, the first information is included in a cause IE (information element) comprising a latency problem of a backhaul link, a bit rate problem of the backhaul link, a deterioration of the backhaul link, or some combination thereof.

In various embodiments, the second information comprises a maximum aggregated bit rate, a number of user devices served by the source device, or some combination thereof. In one embodiment, the response to the handover request comprises a handover failure message. In certain embodiments, the handover failure message indicates that a target communication network is unable to support the predetermined quality of service.

In some embodiments, the handover failure message indicates an overload of the target communication network. In various embodiments, the indication of the overload of the target communication network is included in a cause information element. In one embodiment, the handover failure message indicates a limited capacity of the target communication network.

In certain embodiments, the indication of the limited capacity of the target communication network is included in a cause information element. In some embodiments, the target communication network comprises a target backhaul link.

<FIG> is a schematic flow chart diagram illustrating one embodiment of a method <NUM> for receiving handover requests with network information. In some embodiments, the method <NUM> is performed by an apparatus, such as the network unit <NUM> (e.g., IAB node). In certain embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM> may include receiving <NUM>, at a target device, a handover request from a source device. In such embodiments, the handover request includes: first information indicating that a source communication network corresponding to the source device is unable to support a predetermined quality of service; and second information corresponding to capacity of the source communication network. In some embodiments, the method <NUM> includes transmitting <NUM> a response to the handover request.

In one embodiment, the predetermined quality of service corresponds to a type of communication service. In certain embodiments, the predetermined quality of service comprises a latency, a bit rate, a deterioration level, or some combination thereof. In some embodiments, the first information is included in a cause information element comprising a latency problem of a backhaul link, a bit rate problem of the backhaul link, a deterioration of the backhaul link, or some combination thereof.

In one embodiment, a method comprises: transmitting a handover request to a target device, wherein the handover request comprises: first information indicating that a source communication network corresponding to a source device is unable to support a predetermined quality of service; and second information corresponding to capacity of the source communication network; and receiving a response to the handover request.

In certain embodiments, the target device comprises a target central unit, a target integrated access backhaul node, or a combination thereof.

In some embodiments, the source communication network comprises a source backhaul link.

In various embodiments, the source device comprises a source central unit, a source integrated access backhaul node, or a combination thereof.

In one embodiment, the predetermined quality of service corresponds to a type of communication service.

In certain embodiments, the predetermined quality of service comprises a latency, a bit rate, a deterioration level, or some combination thereof.

In some embodiments, the first information is included in a cause information element comprising a latency problem of a backhaul link, a bit rate problem of the backhaul link, a deterioration of the backhaul link, or some combination thereof.

In various embodiments, the second information comprises a maximum aggregated bit rate, a number of user devices served by the source device, or some combination thereof.

In one embodiment, the response to the handover request comprises a handover failure message.

In certain embodiments, the handover failure message indicates that a target communication network is unable to support the predetermined quality of service.

In some embodiments, the handover failure message indicates an overload of the target communication network.

In various embodiments, the indication of the overload of the target communication network is included in a cause information element.

In one embodiment, the handover failure message indicates a limited capacity of the target communication network.

In certain embodiments, the indication of the limited capacity of the target communication network is included in a cause information element.

In some embodiments, the target communication network comprises a target backhaul link.

In one embodiment, an apparatus comprises: a transmitter that transmits a handover request to a target device, wherein the handover request comprises: first information indicating that a source communication network corresponding to a source device is unable to support a predetermined quality of service; and second information corresponding to capacity of the source communication network; and a receiver that receives a response to the handover request.

In one embodiment, a method comprises: receiving, at a target device, a handover request from a source device, wherein the handover request comprises: first information indicating that a source communication network corresponding to the source device is unable to support a predetermined quality of service; and second information corresponding to capacity of the source communication network; and transmitting a response to the handover request.

In one embodiment, an apparatus comprises: a receiver that receives, at the apparatus, a handover request from a source device, wherein the handover request comprises: first information indicating that a source communication network corresponding to the source device is unable to support a predetermined quality of service; and second information corresponding to capacity of the source communication network; and a transmitter that transmits a response to the handover request.

In certain embodiments, the apparatus comprises a target device, a target central unit, a target integrated access backhaul node, or some combination thereof.

Claim 1:
A method (<NUM>) performed by a source device, the method (<NUM>) comprising:
transmitting (<NUM>) a handover request to a target device, wherein the handover request comprises:
first information indicating that a source communication network corresponding to the source device is unable to support a predetermined quality of service; and
second information corresponding to capacity of the source communication network; and
receiving (<NUM>) a response to the handover request.