Abstract: An approach is described for a method for a radio access node (RAN) node in a fifth generation (5G) wireless communication or a new radio (NR) system that includes the following steps. The method includes generating a request for location information of a user equipment (UE). The method further includes transmitting the request to an access and mobility function (AMF). The method further includes receiving a response from the AMF, wherein the response comprises the location information of the UE.

Abstract: A computer system that establishes a first registration and a second registration in a common wireless communication system is described. During operation, the computer system performs a first registration of the user equipment over a first access, where, after the first registration, the user equipment is connected via the first access with a first access and mobility management function (AMF). Then, the computer system performs a second registration of the user equipment over a second access, where the second access is different from the first access and, after the second registration, the user equipment is connected via the second access with a second AMF. Moreover, when performing the second registration, the computer system: transfers a context of the user equipment from the first AMF to the second AMF; and/or relocates a network interface in a control plane from the first AMF to the second AMF.

Abstract: Mapping information of a bearer or quality of service can be communicated from a Wireless Local Area Network Termination (WT) to the enhanced Node B (eNB), which then uses radio resource control (RRC) signaling to communicate the mapping to the user equipment (UE). For example, three options can be used to communicate mapping information: (1) Operations and Management (OAM), (2) Semi-static Xw-AP signaling (e.g., WT Configuration Update or Xw Setup procedures) or (3) Dynamic Xw-AP procedures (e.g., WT Addition Request procedure). In some embodiments, the mapping can be signaled by (1) bearer to wireless local area networks (WLAN) access category (AC) mapping or (2) long term evolution (LTE) quality of service class identifier (QCI) to WLAN AC mapping.

Abstract: Embodiments of a Next Generation Node B (gNB) are described herein. The gNB may be configured with logical nodes, including a gNB central unit (gNB-CU) and a gNB distributed unit (gNB-DU). The gNB-CU may comprise a gNB-CU control plane (gNB-CU-CP) for control-plane functionality, and a gNB-CU user plane (gNB-CU-UP) for user-plane functionality. The gNB may initiate an E1 interface setup procedure, a bearer context setup procedure, and a UE context setup procedure to establish a UE context that includes a signaling radio bearer (SRB) and a data radio bearer (DRB) configuration. The UE context setup request message may be configured to include quality-of-service parameters for the DRB configuration.

Abstract: Techniques, systems, and devices to support small data transfers are described. A first node, such as a gNodeB or an eNodeB, can perform operations that include receiving a resume request from a user equipment (UE) that is in an inactive state, the resume request including a small data indication, where context information for the UE resides at a second node; transmitting a retrieve UE context request to the second node, the retrieve UE context request including the small data indication; receiving a UE context response from the second node; transmitting, by the first node, a resume response to the UE to cause the UE to switch to a connected state; processing uplink data from the UE; and transmitting a release message to the UE to cause the UE to switch to the inactive state. The release message can be based on RRC release information received from the second node.

Abstract: Systems and methods of providing uplink in-order packet delivery of a QoS flow offloaded in a 5G network are described. An uplink forwarding tunnel is established between a source and target node after a determination is made to offload a QoS flow of a UE to the target node. The source node receives a SDAP PDU from the UE that contains an end marker and, in response, sends a GTP-U end marker packet to the target node via the uplink forwarding tunnel. The target node buffer packets associated with the QoS flow received from the UE after establishment of the uplink forwarding tunnel until the GTP-U end marker packet is received from the target node via the uplink forwarding tunnel and, in response, sends the buffered packets to the 5GC.

Abstract: An apparatus and system to provide a federated learning scheme between a RAN and connected UEs are described. A gNB-DU, gNB-CU, or LMF acts as a central server that selects an AI/ML model, trains the AI/ML model, and transmits the AI/ML model to UEs. The UEs act as local nodes that each send a model request to the central server, receive the AI/ML model in response to the request, trains the AI/ML model locally with data, and report updated parameters to the central server. The central server aggregates parameters from the local nodes and updates the AI/ML model.

Abstract: A user equipment (UE) or network device such as a Vehicle-to-Everything (V2X) node, or V2X device operates to configure sidelink signals with another vehicle or node with resources that can be used for ranging and sidelink communications within a Long Term Evolution (LTE) network or a New Radio (NR) network. The UE/device generate or process a broadcast communication of the sidelink signal via an adaptive antenna array or a directional antenna array and forming a directional radiation pattern from a beam sweeping operation based on geo-location information determined based on a sidelink signal. Depending on the geo-location information coordinates or the position of other vehicles or nodes can be derived to select or configure resources for a sidelink communication, including a Sidelink Ranging Reference Signal (SR-RS) and associated sidelink communication data.

Abstract: Apparatuses, systems, and methods for a network node to inter-connect with a first secondary node (SN) within a core network. The network node may be a master node and may serve a UE. The first SN may be a source SN. The network node may initiate a change from the first SN to a second SN, which may be a target SN. The network mode may determine data forwarding from the first SN to the second SN and may request, from the first SN, data forwarding intentions prior to initiating the change from the first SN to a second first SN to the second SN. The network node may send, to the first SN, data forwarding instructions (e.g., based, at least in part, on the data forwarding intentions of the first SN) and the data forwarding instructions may include a requirement for the first SN to follow the data forwarding instructions.

Abstract: An apparatus of a next generation NodeB (gNB) comprises one or more baseband processors to process a radio resource control (RRC) resume request (RRCResumeRequest) from a user equipment (UE) in an inactive state (RRC_INACTIVE), and to send a UE context request (Retrieve UE Context Request) to a last serving gNB, wherein the UE context request includes a physical cell identifier (PCI) and cell radio network temporary identifier (C-RNTI) of the gNB. The apparatus can include a memory to store the RRC resume request at the gNB and the UE context request at the last serving gNB.

Abstract: Techniques discussed herein can facilitate acknowledgment and/or re-ordering of LWIPEP (LWIP (LTE (Long Term Evolution)/WLAN (Wireless Local Area Network) Radio Level Integration Using IPSec (Internet Protocol Security) Tunnel) Encapsulation Protocol) packets. In various aspects employing a LWIP acknowledgment mode, LWIPEP packets can comprise an enhanced GRE (Generic Routing Encapsulation) header comprising a SN (Sequence Number) of the payload of that LWIPEP packet, which can facilitate acknowledgment of LWIPEP packets and re-ordering of LWIPEP packets (e.g., communicated over a WLAN link, an LTE link, or both) based on the SN(s) indicated in the enhanced GRE header(s).

Abstract: An apparatus of a next generation Node B (gNB) Distributed Unit (DU) comprises one or more baseband processors to transmit one or more retransmitted Packet Data Convergence Protocol (PDCP) Protocol Data Units (PDUs) received from a gNB Central Unit (CU) to a user equipment (UE), and to feed back not only a latest, in-sequence New Radio User-plane (NR-U) Sequence Number (SN) to the CU for Release 15, but also a highest, in-sequence successfully delivered/transmitted PDCP SN, optionally, with a NR-U SN up to which the reported PDCP SN should be applied, which can provide an exact range of successfully delivered/transmitted status for retransmitted packets even in case of DU's re-ordering based on PDCP SN before transmitting to the UE. The apparatus can include a memory to store the reported PDCP SN and NR-U SN.

Abstract: Embodiments of a Next Generation Node B (gNB) are described herein. The gNB may be configured with logical nodes, including a gNB central unit (gNB-CU) and a gNB distributed unit (gNB-DU). The gNB-CU may include a gNB-CU control plane (gNB-CU-CP) for control-plane functionality, and a gNB-CU user plane (gNB-CU-UP) for user-plane functionality. The gNB may initiate an E1 interface setup procedure, a bearer context setup procedure, and a UE context setup procedure to establish a UE context that includes a signaling radio bearer (SRB) and a data radio bearer (DRB) configuration. The UE context setup request message may be configured to include quality-of-service parameters for the DRB configuration.

Abstract: Systems, method, and devices provide for recovery from backhaul failures for Integrated Access and Backhaul (IAB) communication systems with multi-hop routing.

Abstract: A Next Generation Node-B (gNB) and methods of communication are generally described herein. The gNB is configurable to operate as a source gNB. The gNB is configured with logical nodes including a gNB central unit (gNB-CU) and a gNB distributed unit (gNB-DU). The gNB-CU comprises a gNB-CU control plane (gNB-CU-CP) for control-plane functionality, and a gNB-CU user plane (gNB-CU-UP) for user-plane functionality. When a handover of a User Equipment (UE) from the source gNB to a target gNB is performed, the gNB transfers, from the gNB-DU to the gNB-CU-UP, a downlink data delivery status (DDDS) message to indicate that the gNB-CU-UP is to stop transfer, to the gNB-DU, of downlink data intended for the UE.

Abstract: A device of a User Equipment (UE), a method to operate the device, and a machine readable medium. The device includes processing circuitry and a radio frequency (RF) interface coupled to the processing circuitry, the processing circuitry to: decode a signal sent in a cellular network from a base station (BS), the signal including a network allocation vector (NAV) information update regarding a NAV corresponding to a Wi-Fi network, the NAV to be set by a Wi-Fi station (STA) that is in the Wi-Fi network, and that is to be coupled to the UE via a connection; and send the NAV information update to the STA by way of the connection to allow the STA to set its NAV in the Wi-Fi network based on the NAV information update.

Abstract: Embodiments of an integrated access and backhaul (IAB) donor, IAB node, and methods of communication are generally described herein. An IAB network may comprise a plurality of IAB nodes to operate as relays between the IAB donor and one or more User Equipment (UE). The IAB donor may, for each of the IAB nodes, allocate a plurality of subframes to the IAB node. Each allocated subframe may have a subframe type that is one of: a downlink subframe, an uplink subframe, a flexible subframe or a not available subframe. The IAB donor may transmit, from a central unit (CU) of the IAB donor to a distributed unit (DU) an IAB node over an F1 interface, a resource coordination request message that indicates the subframe types of the plurality of subframes.

Abstract: Embodiments of an Evolved Node-B (eNB), radio access network (RAN) central unit (RCU) and methods for radio resource control (RRC) are generally described herein. A RAN distributed unit (RDU) at an eNB may communicate with an RCU of a cloud RAN to cooperatively perform RRC functionality for the eNB 104. The RDU 105 may receive a request for an RRC connection from a User Equipment (UE), and may request global load information from the RCU. The RDU may determine whether to establish the requested RRC connection based on the global load information when a response from the RCU is received before a predetermined time. The RDU may determine whether to establish the requested RRC connection based on local load information when the response from the RCU is not received before the predetermined time.

Abstract: Embodiments described herein relate to managing bearers in a radio access network (e.g., next generation RAN (NG-RAN), etc.). In one example, a central-unit control-plane (CU-CP) communicates with a distributed unit (DU) and a CU-UP to exchange transport network layer addresses (TNLAs) and tunnel endpoint identifiers (TEIDs) between the DU and the CU-UP. In this way, the DU becomes resistant to the CU-UP's rejection of a bearer setup request from the CU-CP during a bearer setup procedure. Furthermore, during virtual machine (VM) migration or local problems of the CU-UP, an E1 procedure known as “bearer relocate” can be defined to notify the DU of a new TNLA for one or more affected general packet radio service tunneling protocol (GTP) tunnels that are affected by the VM migration or local problems.

Abstract: Embodiments described herein relate to managing bearers in a radio access network (e.g., next generation RAN (NG-RAN), etc.). In one example, a central-unit control-plane (CU-CP) communicates with a distributed unit (DU) and a CU-UP to exchange transport network layer addresses (TNLAs) and tunnel endpoint identifiers (TEIDs) between the DU and the CU-UP. In this way, the DU becomes resistant to the CU-UP's rejection of a bearer setup request from the CU-CP during a bearer setup procedure. Furthermore, during virtual machine (VM) migration or local problems of the CU-UP, an E1 procedure known as “bearer relocate” can be defined to notify the DU of a new TNLA for one or more affected general packet radio service tunneling protocol (GTP) tunnels that are affected by the VM migration or local problems.