Device information in a context setup request

Apparatuses, methods, and systems are disclosed for transmitting and/or receiving device information in a context setup request. One method (800) includes transmitting (802) a context setup request to a first device. The context setup request includes information corresponding to a second device. The method (800) includes receiving (804) a response to the context setup request.

FIELD

The subject matter disclosed herein relates generally to wireless communications and more particularly relates to device information in a context setup request.

BACKGROUND

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 (“M”), Interference Measurement (“IM”), International Mobile Subscriber Identity (“IMSI”), Internet-of-Things (“IoT”), Internet Protocol (“IP”), Joint Transmission (“JT”), Level 1 (“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 to (“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, context setup requests may be used. In such networks, a context setup request may supply limited information.

BRIEF SUMMARY

Methods for transmitting device information in a context setup request are disclosed. Apparatuses and systems also perform the functions of the apparatus. In one embodiment, the method includes transmitting a context setup request to a first device. In such an embodiment, the context setup request includes information corresponding to a second device. In certain embodiments, the method includes receiving a response to the context setup request.

An apparatus for transmitting device information in a context setup request, in one embodiment, includes a transmitter that transmits a context setup request to a first device. In such an embodiment, the context setup request includes information corresponding to a second device. In various embodiments, the apparatus includes a receiver that receives a response to the context setup request.

One method for receiving device information in a context setup request includes receiving a context setup request at a first device. In such an embodiment, the context setup request includes information corresponding to a second device. In some embodiments, the method includes transmitting a response to the context setup request.

An apparatus for receiving device information in a context setup request, in one embodiment, includes a receiver that receives a context setup request at a first device. In such an embodiment, the context setup request includes information corresponding to a second device. In various embodiments, the apparatus includes a transmitter that transmits a response to the context setup request.

One method for transmitting a message indicating to stop data transmissions includes transmitting a message including an indication to a third device to stop data transmissions corresponding to a second device. In certain embodiments, the method includes receiving a response to the message.

An apparatus for transmitting a message indicating to stop data transmissions, in one embodiment, includes a transmitter that transmits a message including an indication to a third device to stop data transmissions corresponding to a second device. In various embodiments, the apparatus includes a receiver that receives a response to the message.

One method for receiving a message indicating to stop data transmissions includes receiving a message including an indication at a third device to stop data transmissions corresponding to a second device. In some embodiments, the method includes transmitting a response to the message.

An apparatus for receiving a message indicating to stop data transmissions, in one embodiment, includes a receiver that receives a message including an indication at a third device to stop data transmissions corresponding to a second device. In various embodiments, the apparatus includes a transmitter that transmits a response to the message.

DETAILED DESCRIPTION

FIG.1depicts an embodiment of a wireless communication system100for transmitting and/or receiving information. In one embodiment, the wireless communication system100includes remote units102and network units104. Even though a specific number of remote units102and network units104are depicted inFIG.1, one of skill in the art will recognize that any number of remote units102and network units104may be included in the wireless communication system100.

The network units104may be distributed over a geographic region. In certain embodiments, a network unit104may 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. The network units104are generally part of a radio access network that includes one or more controllers communicably coupled to one or more corresponding network units104. The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system100is compliant with the 5G or NG (Next Generation) of the 3GPP protocol, wherein the network unit104transmits using NG RAN technology. More generally, however, the wireless communication system100may implement some other open or proprietary communication protocol, for example, WiMAX, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

In various embodiments, a network unit104may transmit device information in a context setup request. In some embodiments, the network unit104may transmit a context setup request to a first device. In such embodiments, the context setup request includes information corresponding to a second device. In various embodiments, the network unit104may receive a response to the context setup request. Accordingly, a network unit104may be used for transmitting device information in a context setup request.

In certain embodiments, a network unit104may receive device information in a context setup request. In some embodiments, the network unit104may receive a context setup request at a first device. In such embodiments, the context setup request includes information corresponding to a second device. In various embodiments, the network unit104may transmit a response to the context setup request. Accordingly, a network unit104may be used for receiving device information in a context setup request.

In various embodiments, a network unit104may transmit a message indicating to stop data transmissions. In some embodiments, the network unit104may transmit a message including an indication to a third device to stop data transmissions corresponding to a second device. In various embodiments, the network unit104may receive a response to the message. Accordingly, a network unit104may be used for transmitting a message indicating to stop data transmissions.

In certain embodiments, a network unit104may receive a message indicating to stop data transmissions. In some embodiments, the network unit104may receive a message including an indication at a third device to stop data transmissions corresponding to a second device. In various embodiments, the network unit104may transmit a response to the message. Accordingly, a network unit104may be used for receiving a message indicating to stop data transmissions.

The transmitter210is used to provide UL communication signals to the network unit104and the receiver212is used to receive DL communication signals from the network unit104. Although only one transmitter210and one receiver212are illustrated, the remote unit102may have any suitable number of transmitters210and receivers212. The transmitter210and the receiver212may be any suitable type of transmitters and receivers. In one embodiment, the transmitter210and the receiver212may be part of a transceiver.

In one embodiment, the transmitter310transmits a context setup request to a first device. In such an embodiment, the context setup request includes information corresponding to a second device. In various embodiments, the receiver312receives a response to the context setup request.

In another embodiment, the receiver312receives a context setup request at a first device. In such an embodiment, the context setup request includes information corresponding to a second device. In various embodiments, the transmitter310transmits a response to the context setup request.

In one embodiment, the transmitter310transmits a message including an indication to a third device to stop data transmissions corresponding to a second device. In various embodiments, the receiver312receives a response to the message.

In another embodiment, the receiver312receives a message including an indication at a third device to stop data transmissions corresponding to a second device. In various embodiments, the transmitter310transmits a response to the message.

Although only one transmitter310and one receiver312are illustrated, the network unit104may have any suitable number of transmitters310and receivers312. The transmitter310and the receiver312may be any suitable type of transmitters and receivers. In one embodiment, the transmitter310and the receiver312may be part of a transceiver.

FIG.4is a schematic block diagram illustrating one embodiment of an integrated access backhaul (“IAB”) system400. The IAB system400includes a first UE402, a second UE404, a first IAB node406, an IAB donor node408, a second IAB node410, a third IAB node412, and a fourth IAB node414. As illustrated, the first UE402is connected to the IAB donor node408via the first IAB node406. Moreover, the second UE404is connected to the IAB donor node408via the second IAB node410, the third IAB node412, and the fourth IAB node414. The IAB system400, 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 6 GHz 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. InFIG.4, the first UE402may switch from communicating via the first IAB node406to communicating with the second IAB node410if 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 JAB 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, SDAP, 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.

InFIG.4the IAB nodes may be in a standalone mode which includes one IAB-donor and multiple IAB-nodes. The IAB-donor node408may 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 JAB-donor node408may be split according to its functions which can all be either collocated or non-collocated as allowed by 3GPP NG-RAN architecture.

FIG.5is a schematic block diagram illustrating one embodiment of a mobility procedure500. A remote unit (UE502), a source gNB DU504, a target gNB DU506, and a gNB CU508communicate as part of the mobility procedure500. 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.

In one embodiment, in a first communication510transmitted from the UE502to the source gNB DU504, the UE502sends a measurement report message to the source gNB DU504.

In certain embodiments, in a second communication512transmitted from the source gNB DU504to the gNB CU508, the source gNB DU504sends an uplink RRC transfer message to the gNB CU508to convey the received measurement report from the measurement report message.

In some embodiments, in a third communication514transmitted from the gNB CU508to the target gNB DU506, the gNB CU508sends a UE context setup request message to the target gNB DU506to create a UE context and to setup one or more bearers.

In various embodiments, in a fourth communication516transmitted from the target gNB DU506to the gNB CU508, the target gNB DU506responds to the gNB CU508with a UE context setup response message.

In one embodiment, in a fifth communication518transmitted from the gNB CU508to the source gNB DU504, the gNB CU508sends a UE context modification request message to the source gNB DU504, which includes a generated RRCConnectionReconfiguration message and indicates to stop data transmission for the UE502. The source gNB DU504may also send a downlink data delivery status frame to inform the gNB CU508about unsuccessfully transmitted downlink data to the UE502.

In certain embodiments, in a sixth communication520transmitted from the source gNB DU504to the UE502, the source gNB DU504forwards the received RRCConnectionReconfiguration message to the UE502.

In some embodiments, in a seventh communication522transmitted from the source gNB DU504to the gNB CU508, the source gNB DU504responds to the gNB CU508with a UE context modification response message. In some embodiments, the source gNB DU504may send a downlink data delivery status frame to inform the gNB CU508about downlink packets, which may include PDCP PDUs not successfully transmitted in the source gNB DU504, sent from the gNB CU508to the target gNB DU506. In some embodiments, it may be up to the gNB CU508implementation to determine whether to start sending DL user data to target gNB DU506before or after reception of the downlink data delivery status.

In various embodiments, in an eighth communication524transmitted between the UE502and the target gNB DU506, a random access procedure may be performed.

In one embodiment, in a ninth communication526transmitted from the UE502and the target gNB DU506, the UE502responds to the target gNB DU506with an RRCConnectionReconfigurationComplete message.

In certain embodiments, in a tenth communication528transmitted from the target gNB DU506to the gNB CU508, the target gNB DU506sends an uplink RRC transfer message to the gNB CU508to convey the received RRCConnectionReconfigurationComplete message. In one embodiment, downlink packets may be sent to the UE502. In various embodiments, uplink packets may be sent from the UE502, which may also be forwarded to the gNB CU508through the target gNB DU506.

In some embodiments, in an eleventh communication530transmitted from the gNB CU508to the source gNB DU504, the gNB CU508sends a UE context release command message to the source gNB DU504.

In various embodiments, in a twelfth communication532transmitted from the source gNB DU504to the gNB CU508, the source gNB DU504releases the UE context and responds the gNB CU508with a UE context release complete message.

FIG.6is a schematic block diagram illustrating another embodiment of an integrated access backhaul system600. The integrated access backhaul system600includes a first UE602(“UE1”), a second UE604(“UE2”), a third UE606(“UE3”), a gNB central unit608(“gNB CU”), a first gNB distributed unit610(“gNB DU1”), a second gNB distributed unit612(“gNB DU2”), a first IAB node614(“IAB node1”), a second IAB node616(“IAB node2”), a third IAB node618(“TAB node3”), and a fourth IAB node620(“IAB node4”). As illustrated, the third IAB node618accesses the gNB central unit608by connecting to the first IAB node614. However, the gNB central unit608may send information that triggers the third IAB node618to move to the second IAB node616as illustrated by arrow622.

FIG.7is a schematic block diagram illustrating another embodiment of a mobility procedure700. An IAB node702, a source IAB node704, a first gNB DU706, a target IAB node708, a second gNB DU710, and a gNB CU712communicate as part of the mobility procedure700. The mobility procedure700provides one embodiment of communications that may be used to transition communication from the IAB node702(e.g., third IAB node618) communicating with the source IAB node704(e.g., first IAB node614) to the target IAB node708(e.g., second IAB node616).

In one embodiment, in a first communication714transmitted from the IAB node702to the source IAB node704, the IAB node702sends a measurement report message to the source IAB node704.

In certain embodiments, in a second communication716transmitted from the source IAB node704to the gNB CU712, the source IAB node704sends an uplink RRC transfer message to the gNB CU712to convey the received measurement report from the measurement report message that may be relayed by an intermediate IAB node and/or the first gNB DU706.

In some embodiments, in a third communication718transmitted from the gNB CU712to the target IAB node708, the gNB CU712sends a UE context setup request message to the target IAB node708to create a UE context and to setup one or more bearers. In certain embodiments, the UE context setup request message may be relayed by an intermediate IAB node and/or the second gNB DU710. In various embodiments, the UE context setup request message may include additional information to enable the target IAB node708to know whether the IAB node702is an IAB node or a UE. In some embodiments, the additional information may include load assistance information, capacity assistance information, and/or other assistance information. In certain embodiments, the load assistance information includes a number of UEs served by the IAB node702and/or a number of downstream IAB nodes served by the IAB node702. In one embodiment, the capacity assistance information may include an IAB aggregated maximum bit rate for uplink and/or an IAB aggregated maximum bit rate for downlink. An aggregated maximum bit rate may be a summation of all bit rates handled by a particular IAB node. In various embodiments, other assistance information may include an ID corresponding to the IAB node702and/or an ID corresponding to a DU. In some embodiments, the other assistance information may include an indication that the IAB node702is an IAB and not a UE. In various embodiments, the indication may be an implicit indication by including some IAB-related parameter, such as any additional information described herein. In one embodiment, the indication may be a one-bit indicator. The one-bit indicator may be equal to zero to indicate that a device is a UE, and the one-bit indicator may be equal to one to indicate that the device is an IAB node.

In various embodiments, in a fourth communication720transmitted from the target IAB node708to the gNB CU712, the target IAB node708responds to the gNB CU712with a UE context setup response message.

In one embodiment, in a fifth communication722transmitted from the gNB CU712to the source IAB node704, the gNB CU712sends a UE context modification request message to the source IAB node704, which includes a generated RRCConnectionReconfiguration message and indicates to stop data transmission for the IAB node702. The source IAB node704may also send a downlink data delivery status frame to inform the gNB CU712about unsuccessfully transmitted downlink data to the IAB node702. In certain embodiments, as part of the UE context modification request message and/or the fifth communication722, the gNB CU712may indicate with an indicator to an intermediate IAB node on a path between the IAB node702and a donor DU to stop the data transmissions for the IAB node702. The indicator may indicate: uplink data and/or downlink data, an ID for the IAB node702(e.g., to stop downlink and/or uplink data routed and/or served by the IAB node702), a set of UE IDs served by the IAB node702and/or downstream nodes, and/or a set of UE specific bearer IDs served by the IAB node702and/or downstream nodes. In some embodiments, the indicator may be configured by RRC signaling.

In various embodiments, as part of the UE context modification request message and/or the fifth communication722, the IAB node702(e.g., or another node) may indicate with an indicator to upstream nodes to stop the data transmissions for the IAB node702. In certain embodiments, the indicator may be included in an adaptative layer. Moreover, after the IAB node702informs its parent IAB node, the parent IAB node may further propagate the indicator to its parent IAB until all upstream nodes have received the indicator. The indicator may indicate: uplink data and/or downlink data, an ID for the IAB node702(e.g., to stop downlink and/or uplink data routed and/or served by the IAB node702), a set of UE IDs served by the IAB node702and/or downstream nodes, and/or a set of UE specific bearer IDs served by the IAB node702and/or downstream nodes. In some embodiments, the indicator may be configured by RRC signaling. In one embodiment, as part of the UE context modification request message and/or the fifth communication722, a new route table may be included to update routing information.

In certain embodiments, in a sixth communication724transmitted from the source IAB node704to the IAB node702, the source IAB node704forwards the received RRCConnectionReconfiguration message to the IAB node702.

In some embodiments, in a seventh communication726transmitted from the source IAB node704to the gNB CU712, the source IAB node704responds to the gNB CU712with a UE context modification response message. In one embodiment, the seventh communication726may include a response to indicate that an update to a route table is complete. In some embodiments, the source IAB node704may send a downlink data delivery status frame to inform the gNB CU712about downlink packets, which may include PDCP PDUs not successfully transmitted in the source IAB node704, sent from the gNB CU712to the target IAB node708. In some embodiments, it may be up to the gNB CU712implementation to determine whether to start sending DL user data to target IAB node708before or after reception of the downlink data delivery status.

In various embodiments, in an eighth communication728transmitted between the IAB node702and the target IAB node708, a random access procedure may be performed.

In one embodiment, in a ninth communication730transmitted from the IAB node702and the target IAB node708, the IAB node702responds to the target IAB node708with an RRCConnectionReconfigurationComplete message.

In certain embodiments, in a tenth communication732transmitted from the target IAB node708to the gNB CU712, the target IAB node708sends an uplink RRC transfer message to the gNB CU712to convey the received RRCConnectionReconfigurationComplete message. In one embodiment, downlink packets may be sent to the IAB node702. In various embodiments, uplink packets may be sent from the IAB node702, which may also be forwarded to the gNB CU712through an intermediate IAB node and/or the target IAB node708.

In some embodiments, in an eleventh communication734transmitted from the gNB CU712to the source IAB node704, the gNB CU712sends a UE context release command message to the source IAB node704.

In various embodiments, in a twelfth communication736transmitted from the source IAB node704to the gNB CU712, the source IAB node704releases the UE context and responds the gNB CU712with a UE context release complete message.

FIG.8is a schematic flow chart diagram illustrating one embodiment of a method800for transmitting device information in a context setup request. In some embodiments, the method800is performed by an apparatus, such as the network unit104(e.g., IAB node). In certain embodiments, the method800may 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 method800may include transmitting802a context setup request to a first device. In such an embodiment, the context setup request includes information corresponding to a second device. In certain embodiments, the method800includes receiving804a response to the context setup request.

In certain embodiments, the information comprises a number of user devices served by the second device, a number of nodes served by the second device, or a combination thereof. In some embodiments, the information comprises a maximum aggregated bit rate for downlink, a maximum aggregated bit rate for uplink, or a combination thereof. In various embodiments, the information comprises a backhaul node identifier, a distributed unit identifier, or a combination thereof corresponding to the second device.

In one embodiment, the information comprises a one-bit indicator. In certain embodiments, the one-bit indicator is equal to zero if the second device is a user device, and the one-bit indicator is equal to one if the second device is a backhaul node. In some embodiments, the information corresponds to a backhaul node and indicates to the first device that the second device is the backhaul node.

FIG.9is a schematic flow chart diagram illustrating one embodiment of a method900for receiving device information in a context setup request. In some embodiments, the method900is performed by an apparatus, such as the network unit104(e.g., IAB node). In certain embodiments, the method900may 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 method900may include receiving902a context setup request at a first device. In such an embodiment, the context setup request includes information corresponding to a second device. In some embodiments, the method900includes transmitting904a response to the context setup request.

In certain embodiments, the information comprises a number of user devices served by the second device, a number of nodes served by the second device, or a combination thereof. In some embodiments, the information comprises a maximum aggregated bit rate for downlink, a maximum aggregated bit rate for uplink, or a combination thereof. In various embodiments, the information comprises a backhaul node identifier, a distributed unit identifier, or a combination thereof corresponding to the second device.

In one embodiment, the information comprises a one-bit indicator. In certain embodiments, the one-bit indicator is equal to zero if the second device is a user device, and the one-bit indicator is equal to one if the second device is a backhaul node. In some embodiments, the information corresponds to a backhaul node and indicates to the first device that the second device is the backhaul node.

FIG.10is a schematic flow chart diagram illustrating one embodiment of a method1000for transmitting a message indicating to stop data transmissions. In some embodiments, the method1000is performed by an apparatus, such as the network unit104(e.g., IAB node). In certain embodiments, the method1000may 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 method1000may include transmitting1002a message including an indication to a third device to stop data transmissions corresponding to a second device. In certain embodiments, the method1000includes receiving1004a response to the message.

In certain embodiments, the data transmissions comprise uplink data, downlink data, or a combination thereof. In some embodiments, the indication comprises an identifier corresponding to the second device, and the data transmissions served by the second device are stopped based on the indication. In various embodiments, the indication comprises a set of user device identifiers, and the data transmissions corresponding to the set of user device identifiers are stopped based on the indication.

In one embodiment, the indication comprises a set of user device specific bearer identifiers, and the data transmissions corresponding to the set of user device specific bearer identifiers are stopped based on the indication. In certain embodiments, the indication is configured by radio resource control signaling. In some embodiments, the indication is included in an adaptative layer.

In various embodiments, the third device comprises an intermediate node, a parent node, or a combination thereof. In one embodiment, the message is transmitted from a central unit. In certain embodiments, the message is transmitted from an access backhaul node, a child backhaul node, or a combination thereof.

FIG.11is a schematic flow chart diagram illustrating one embodiment of a method1100for receiving a message indicating to stop data transmissions. In some embodiments, the method1100is performed by an apparatus, such as the network unit104(e.g., IAB node). In certain embodiments, the method1100may 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 method1100may include receiving1102a message including an indication at a third device to stop data transmissions corresponding to a second device. In some embodiments, the method1100includes transmitting1104a response to the message.

In certain embodiments, the data transmissions comprise uplink data, downlink data, or a combination thereof. In some embodiments, the indication comprises an identifier corresponding to the second device, and the data transmissions served by the second device are stopped based on the indication. In various embodiments, the indication comprises a set of user device identifiers, and the data transmissions corresponding to the set of user device identifiers are stopped based on the indication.

In one embodiment, the indication comprises a set of user device specific bearer identifiers, and the data transmissions corresponding to the set of user device specific bearer identifiers are stopped based on the indication. In certain embodiments, the indication is configured by radio resource control signaling. In some embodiments, the indication is included in an adaptative layer.

In various embodiments, the third device comprises an intermediate node, a parent node, or a combination thereof. In one embodiment, the message is transmitted from a central unit. In certain embodiments, the message is transmitted from an access backhaul node, a child backhaul node, or a combination thereof.

In one embodiment, a method comprises: transmitting a context setup request to a first device, wherein the context setup request comprises information corresponding to a second device; and receiving a response to the context setup request.

In certain embodiments, the information comprises a number of user devices served by the second device, a number of nodes served by the second device, or a combination thereof.

In some embodiments, the information comprises a maximum aggregated bit rate for downlink, a maximum aggregated bit rate for uplink, or a combination thereof.

In various embodiments, the information comprises a backhaul node identifier, a distributed unit identifier, or a combination thereof corresponding to the second device.

In one embodiment, the information comprises a one-bit indicator.

In certain embodiments, the one-bit indicator is equal to zero if the second device is a user device, and the one-bit indicator is equal to one if the second device is a backhaul node.

In some embodiments, the information corresponds to a backhaul node and indicates to the first device that the second device is the backhaul node.

In one embodiment, an apparatus comprises: a transmitter that transmits a context setup request to a first device, wherein the context setup request comprises information corresponding to a second device; and a receiver that receives a response to the context setup request.

In certain embodiments, the information comprises a number of user devices served by the second device, a number of nodes served by the second device, or a combination thereof.

In some embodiments, the information comprises a maximum aggregated bit rate for downlink, a maximum aggregated bit rate for uplink, or a combination thereof.

In various embodiments, the information comprises a backhaul node identifier, a distributed unit identifier, or a combination thereof corresponding to the second device.

In one embodiment, the information comprises a one-bit indicator.

In certain embodiments, the one-bit indicator is equal to zero if the second device is a user device, and the one-bit indicator is equal to one if the second device is a backhaul node.

In some embodiments, the information corresponds to a backhaul node and indicates to the first device that the second device is the backhaul node.

In one embodiment, a method comprises: receiving a context setup request at a first device, wherein the context setup request comprises information corresponding to a second device; and transmitting a response to the context setup request.

In certain embodiments, the information comprises a number of user devices served by the second device, a number of nodes served by the second device, or a combination thereof.

In some embodiments, the information comprises a maximum aggregated bit rate for downlink, a maximum aggregated bit rate for uplink, or a combination thereof.

In various embodiments, the information comprises a backhaul node identifier, a distributed unit identifier, or a combination thereof corresponding to the second device.

In one embodiment, the information comprises a one-bit indicator.

In certain embodiments, the one-bit indicator is equal to zero if the second device is a user device, and the one-bit indicator is equal to one if the second device is a backhaul node.

In some embodiments, the information corresponds to a backhaul node and indicates to the first device that the second device is the backhaul node.

In one embodiment, an apparatus comprises: a receiver that receives a context setup request at a first device, wherein the context setup request comprises information corresponding to a second device; and a transmitter that transmits a response to the context setup request.

In certain embodiments, the information comprises a number of user devices served by the second device, a number of nodes served by the second device, or a combination thereof.

In some embodiments, the information comprises a maximum aggregated bit rate for downlink, a maximum aggregated bit rate for uplink, or a combination thereof.

In various embodiments, the information comprises a backhaul node identifier, a distributed unit identifier, or a combination thereof corresponding to the second device.

In one embodiment, the information comprises a one-bit indicator.

In certain embodiments, the one-bit indicator is equal to zero if the second device is a user device, and the one-bit indicator is equal to one if the second device is a backhaul node.

In some embodiments, the information corresponds to a backhaul node and indicates to the first device that the second device is the backhaul node.

In one embodiment, a method comprises: transmitting a message comprising an indication to a third device to stop data transmissions corresponding to a second device; and receiving a response to the message.

In certain embodiments, the data transmissions comprise uplink data, downlink data, or a combination thereof.

In some embodiments, the indication comprises an identifier corresponding to the second device, and the data transmissions served by the second device are stopped based on the indication.

In various embodiments, the indication comprises a set of user device identifiers, and the data transmissions corresponding to the set of user device identifiers are stopped based on the indication.

In one embodiment, the indication comprises a set of user device specific bearer identifiers, and the data transmissions corresponding to the set of user device specific bearer identifiers are stopped based on the indication.

In certain embodiments, the indication is configured by radio resource control signaling.

In some embodiments, the indication is included in an adaptative layer.

In various embodiments, the third device comprises an intermediate node, a parent node, or a combination thereof.

In one embodiment, the message is transmitted from a central unit.

In certain embodiments, the message is transmitted from an access backhaul node, a child backhaul node, or a combination thereof.

In one embodiment, an apparatus comprises: a transmitter that transmits a message comprising an indication to a third device to stop data transmissions corresponding to a second device; and a receiver that receives a response to the message.

In certain embodiments, the data transmissions comprise uplink data, downlink data, or a combination thereof.

In some embodiments, the indication comprises an identifier corresponding to the second device, and the data transmissions served by the second device are stopped based on the indication.

In various embodiments, the indication comprises a set of user device identifiers, and the data transmissions corresponding to the set of user device identifiers are stopped based on the indication.

In one embodiment, the indication comprises a set of user device specific bearer identifiers, and the data transmissions corresponding to the set of user device specific bearer identifiers are stopped based on the indication.

In certain embodiments, the indication is configured by radio resource control signaling.

In some embodiments, the indication is included in an adaptative layer.

In various embodiments, the third device comprises an intermediate node, a parent node, or a combination thereof.

In one embodiment, the message is transmitted from a central unit.

In certain embodiments, the message is transmitted from an access backhaul node, a child backhaul node, or a combination thereof.

In one embodiment, a method comprises: receiving a message comprising an indication at a third device to stop data transmissions corresponding to a second device; and transmitting a response to the message.

In certain embodiments, the data transmissions comprise uplink data, downlink data, or a combination thereof.

In some embodiments, the indication comprises an identifier corresponding to the second device, and the data transmissions served by the second device are stopped based on the indication.

In various embodiments, the indication comprises a set of user device identifiers, and the data transmissions corresponding to the set of user device identifiers are stopped based on the indication.

In one embodiment, the indication comprises a set of user device specific bearer identifiers, and the data transmissions corresponding to the set of user device specific bearer identifiers are stopped based on the indication.

In certain embodiments, the indication is configured by radio resource control signaling.

In some embodiments, the indication is included in an adaptative layer.

In various embodiments, the third device comprises an intermediate node, a parent node, or a combination thereof.

In one embodiment, the message is transmitted from a central unit.

In certain embodiments, the message is transmitted from an access backhaul node, a child backhaul node, or a combination thereof.

In one embodiment, an apparatus comprises: a receiver that receives a message comprising an indication at a third device to stop data transmissions corresponding to a second device; and a transmitter that transmits a response to the message.

In certain embodiments, the data transmissions comprise uplink data, downlink data, or a combination thereof.

In some embodiments, the indication comprises an identifier corresponding to the second device, and the data transmissions served by the second device are stopped based on the indication.

In various embodiments, the indication comprises a set of user device identifiers, and the data transmissions corresponding to the set of user device identifiers are stopped based on the indication.

In one embodiment, the indication comprises a set of user device specific bearer identifiers, and the data transmissions corresponding to the set of user device specific bearer identifiers are stopped based on the indication.

In certain embodiments, the indication is configured by radio resource control signaling.

In some embodiments, the indication is included in an adaptative layer.

In various embodiments, the third device comprises an intermediate node, a parent node, or a combination thereof.

In one embodiment, the message is transmitted from a central unit.

In certain embodiments, the message is transmitted from an access backhaul node, a child backhaul node, or a combination thereof.