WO2022150154A1 - Qos flow remapping support at handover - Google Patents

Abstract

An apparatus and system for lossless handover from a source gNB are described. A gNB-CU-CP determines whether QoS flow remapping for a DRB is to occur during the handover and sends, to a gNB-CU-UP, a BEARER CONTEXT SETUP REQUEST message for the DRB. The QoS flow remapping occurs after completion of transmission of PDCP SDUs of the DRB forwarded from the source gNB. The message includes a PDU Session Resource To Setup List IE having a QoS mapping IE for the gNB-CU-UP to use to transmit the SDUs and a QoS Remapping IE that indicates the remapping. The QoS Remapping IE has a first value to indicate that QoS flows are to be updated and second value to indicate that no QoS flows are to be mapped to the DRB.

Description

QOS FLOW REMAPPING SUPPORT AT HANDOVER

PRIORITY CLAIM

[0001] This application claims the benefit of priority to United States Provisional Patent Application Serial No. 63/134,743, filed January 7, 2021, which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Embodiments pertain to next generation wireless communications. In particular, some embodiments relate to handover at a disaggregated next generation radio access network (NG-RAN), and even more specifically, quality of service (QoS) flow remapping at handover for at a disaggregated NG-RAN.

BACKGROUND

[0003] The use and complexity of wireless systems, which include 5^th generation (5G) networks and are starting to include sixth generation (6G) networks among others, has increased due to both an increase in the types of devices user equipment (UEs) using network resources as well as the amount of data and bandwidth being used by various applications, such as video streaming, operating on these UEs. With the vast increase in number and diversity of communication devices, the corresponding network environment, including routers, switches, bridges, gateways, firewalls, and load balancers, has become increasingly complicated. As expected, a number of issues abound with the advent of any new technology.

BRIEF DESCRIPTION OF THE FIGURES

[0004] In the figures, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The figures illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document. [0005] FIG. 1 A illustrates an architecture of a network, in accordance with some aspects.

[0006] FIG. 1 B illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0007] FIG. 1C illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0008] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.

[0009] FIG. 3 illustrates an O-RAN system architecture in accordance with some aspects.

[0010] FIG. 4 illustrates a logical architecture of the O-RAN system of FIG. 3 in accordance with some aspects.

[0011] FIG. 5 illustrates an example O-RAN Architecture in accordance with some aspects.

[0012] FIG. 6 illustrates a flow diagram of a handover (HO) process in accordance with some aspects.

[0013] FIG. 7 illustrates a Bearer Context Setup procedure in accordance with some embodiments.

[0014] FIG. 8 illustrates a gNB-CU-CP initiated Bearer Context Modification procedure in accordance with some embodiments.

[0015] FIG. 9 illustrates a gNB-CU-UP initiated Bearer Context Modification procedure in accordance with some embodiments.

DETAILED DESCRIPTION

[0016] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0017] FIG. 1 A illustrates an architecture of a network in accordance with some aspects. The network 140 A includes 3 GPP LTE/4G and NG network functions that may be extended to 6G functions. Accordingly, although 5G will be referred to, it is to be understood that this is to extend as able to 6G structures, systems, and functions. A network function can be implemented as a discrete network element on a dedicated hardware, as a software instance running on dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., dedicated hardware or a cloud infrastructure.

[0018] The network 140A is shown to include user equipment (UE) 101 and UE 102. The UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface. The UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.

[0019] Any of the radio links described herein (e.g., as used in the network: 140 A or any other illustrated network) may operate according to any exemplary radio communication technology and/or standard. Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3 6-3.8 GHz, and other frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and other frequencies). Different Single Carrier or Orthogonal Frequency Domain Multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc ), and in particular 3GPP NR, may be used by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0020] In some aspects, any of the UEs 101 and 102 can comprise an Intemet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing shortlived UE connections. In some aspects, any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or de vice -to- device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The loT UEs may execute background applications (e.g., keepalive messages, status updates, etc.) to facilitate the connections of the loT network. In some aspects, any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0021] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.

[0022] The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a 5G protocol, a 6G protocol, and the like.

[0023] In an aspect, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), a Physical Sidelink Broadcast Channel (PSBCH), and a Physical Sidelink Feedback Channel (PSFCH).

[0024] The UE 102 is shown to be configured to access an access point (AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0025] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some aspects, the communication nodes 111 and 112 can be transmi ssion/reception points (TRPs). In instances when the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The

RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112. [0026] Any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102. In some aspects, any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In an example, any of the nodes 111 and/or 112 can be a gNB, an eNB, or another type of RAN node.

[0027] The RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113. In aspects, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C). In this aspect, the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the SI -mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121. [0028] In this aspect, the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0029] The S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.

[0030] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the CN 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 can also communicate data to other external networks

131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125. The application server 184 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120. [0031] The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0032] In some aspects, the communication network 140 A can be an loT network or a 5G or 6G network, including 5G new radio network using communications in the licensed (5GNR) and the unlicensed (5GNR-U) spectrum. One of the current enablers of loT is the narrowband-IoT (NB-IoT). Operation in the unlicensed spectrum may include dual connectivity (DC) operation and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without the use of an “anchor” in the licensed spectrum, called MulteFire. Further enhanced operation of LTE systems in the licensed as well as unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operations can include techniques for sidelink resource allocation and UE processing behaviors for NR sidelink V2X communications.

[0033] An NG system architecture (or 6G system architecture) can include the RAN 110 and a 5G core network (5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The CN 120 (e.g., a 5G core network/5GC) can include an access and mobility function (AMF) and/or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces. [0034] In some aspects, the NG system architecture can use reference points between various nodes. In some aspects, each of the gNBs and the NG- eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth. In some aspects, a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.

[0035] FIG. 1 B illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, FIG. IB illustrates a 5G system architecture 1408 in a reference point representation, which may be extended to a 6G system architecture. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5GC network entities. The 5G system architecture 140B includes a plurality of network functions (NFs), such as an AMF 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, UPF 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (HSS) 146.

[0036] The UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third- party services. The AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technologies. The SMF 136 can be configured to set up and manage various sessions according to network policy. The SMF 136 may thus be responsible for session management and allocation of IP addresses to UEs. The SMF 136 may also select and control the UPF 134 for data transfer. The SMF 136 may be associated with a single session of a UE 101 or multiple sessions of the UE 101. This is to say that the UE 101 may have multiple 5G sessions. Different SMFs may be allocated to each session. The use of different SMFs may permit each session to be individually managed. As a consequence, the functionalities of each session may be independent of each other.

[0037] The UPF 134 can be deployed in one or more configurations according to the desired service type and may be connected with a data network. The PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system). [0038] The AF 150 may provide information on the packet flow to the PCF 148 responsible for policy control to support a desired QoS. The PCF 148 may set mobility and session management policies for the UE 101. To this end, the PCF 148 may use the packet flow information to determine the appropriate policies for proper operation of the AMF 132 and SMF 136. The AUSF 144 may store data for UE authentication.

[0039] In some aspects, the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some aspects, the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator.

[0040] In some aspects, the UDM/HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS). The AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

[0041] A reference point representation shows that interaction can exist between corresponding NF services. For example, FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), N11 (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the AMF 132 in case of a non-roaming scenario, or between the PCF 148 and a visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. IB can also be used.

[0042] FIG. 1C illustrates a 5G system architecture 140C and a servicebased representation. In addition to the network entities illustrated in FIG. IB, system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some aspects, 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

[0043] In some aspects, as illustrated in FIG. 1C, service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture 140C can include the following service-based interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), aNudm 158E (a service-based interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the AUSF 144). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1C can also be used.

[0044] NR-V2X architectures may support high-reliability low latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival time and size. Techniques disclosed herein can be used for supporting high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[0045] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments. The communication device 200 may be a UE such as a specialized computer, a personal or laptop computer (PC), a tablet PC, or a smart phone, dedicated network equipment such as an eNB, a server running software to configure the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. For example, the communication device 200 may be implemented as one or more of the devices shown in FIGS. 1 A-1C. Note that communications described herein may be encoded before transmission by the transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by the receiving entity.

[0046] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[0047] Accordingly, the term “module” (and “component”) is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general -purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

[0048] The communication device 200 may include a hardware processor (or equivalently processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208. The main memory 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory. The communication device 200 may further include a display unit 210 such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (Ul) navigation device 214 (e.g., a mouse). In an example, the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display. The communication device 200 may additionally include a storage device (e.g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The communication device 200 may further include an output controller, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[0049] The storage device 216 may include a non-transitory machine readable medium 222 (hereinafter simply referred to as machine readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, and/or within the hardware processor 202 during execution thereof by the communication device 200. While the machine readable medium 222 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 224.

[0050] The term “machine readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or canying data structures used by or associated with such instructions. Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.

[0051] The instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via the network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks. Communications over the networks may include one or more different protocols, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, IEEE 802.16 family of standards known as WiMax, IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, a next generation (NG)/5^th generation (5G) standards among others. In an example, the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phonejacks) or one or more antennas to connect to the transmission medium 226. [0052] Note that the term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to cany out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0053] The term “processor circuitry” or “processor” as used herein thus refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. The term “processor circuitry” or “processor” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single- or multi-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes.

[0054] Any of the radio links described herein may operate according to any one or more of the following radio communication technologies and/or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3GPP) radio communication technology, for example Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3 GPP Long Term Evolution (LTE), 3 GPP Long Term Evolution Advanced (LTE Advanced), Code division multiple access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed Circuit-Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+), Universal Mobile Telecommunications System-Time-Division Duplex (UMTS-TDD), Time Division-Code Division Multiple Access (TD-CDMA), Time Division- Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3 GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10) , 3GPP Rel. 11 (3rd Generation Partnership Project Release 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPP Rel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel. 15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17) and subsequent Releases (such as Rel. 18, Rel. 19, etc.), 3GPP 5G, 5G, 5G New Radio (5GNR), 3GPP 5GNew Radio, 3GPP LTE Extra, LTE-Advanced Pro, LTE Licensed-Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G), Code division multiple access 2000 (Third generation) (CDMA2000 (3G)), Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS (1G)), Total Access Communication System/Extended Total Access Communication System (TACS/ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System (AMTS), OLT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation for Mobiltelefonisystem D, or Mobile telephony system D), Public Automated Land Mobile (Autotel/PALM), ARP (Finnish for Autoradiopuhelin, "car radio phone"), NMT (Nordic Mobile Telephony), High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handyphone System (PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), also referred to as also referred to as 3 GPP Generic Access Network, or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general (wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802.1 lad, IEEE 802.1 lay, etc.), technologies operating above 300 GHz and THz bands, (3GPP/LTE based or IEEE 802.1 Ip or IEEE 802.1 Ibd and other) Vehicle-to-Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to- Infrastructure (V2I) and Infrastructure-to-Vehicle (I2V) communication technologies, 3GPP cellular V2X, DSRC (Dedicated Short Range Communications) communication systems such as Intelligent-Transport-Systems and others (typically operating in 5850 MHz to 5925 MHz or above (typically up to 5935 MHz following change proposals in CEPT Report 71)), the European ITS-G5 system (i.e. the European flavor of IEEE 802.1 lp based DSRC, including ITS-G5A (i.e., Operation of ITS-G5 in European ITS frequency bands dedicated to ITS for safety re-lated applications in the frequency range 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., Operation in European ITS frequency bands dedicated to ITS non- safety applications in the frequency range 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., Operation of ITS applications in the frequency range 5,470 GHz to 5,725 GHz)), DSRC in Japan in the 700MHz band (including 715 MHz to 725 MHz), IEEE 802.1 Ibd based systems, etc.

[0055] Aspects described herein can be used in the context of any spectrum management scheme including dedicated licensed spectrum, unlicensed spectrum, license exempt spectrum, (licensed) shared spectrum (such as LSA = Licensed Shared Access in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies and SAS = Spectrum Access System / CBRS = Citizen Broadband Radio System in 3.55-3.7 GHz and further frequencies). Applicable spectrum bands include IMT (International Mobile Telecommunications) spectrum as well as other types of spectrum/bands, such as bands with national allocation (including 450 - 470 MHz, 902-928 MHz (note: allocated for example in US (FCC Part 15)), 863-868.6 MHz (note: allocated for example in European Union (ETSI EN 300 220)), 915.9-929.7 MHz (note: allocated for example in Japan), 917-923.5 MHz (note: allocated for example in South Korea), 755-779 MHz and 779-787 MHz (note: allocated for example in China), 790 - 960 MHz, 1710 - 2025 MHz, 2110 - 2200 MHz, 2300 - 2400 MHz, 2.4-2.4835 GHz (note: it is an ISM band with global availability and it is used by Wi-Fi technology family (1 Ib/g/n/ax) and also by Bluetooth), 2500 - 2690 MHz, 698-790 MHz, 610 - 790 MHz, 3400 - 3600 MHz, 3400 - 3800 MHz, 3800 - 4200 MHz, 3.55- 3.7 GHz (note: allocated for example in the US for Citizen Broadband Radio Service), 5.15-5.25 GHz and 5.25-5.35 GHz and 5.47-5.725 GHz and 5.725-5.85 GHz bands (note: allocated for example in the US (FCC part 15), consists four U-NII bands in total 500 MHz spectrum), 5.725-5.875 GHz (note: allocated for example in EU (ETSI EN 301 893)), 5.47-5.65 GHz (note: allocated for example in South Korea, 5925-7125 MHz and 5925-6425MHz band (note: under consideration in US and EU, respectively. Next generation Wi-Fi system is expected to include the 6 GHz spectrum as operating band but it is noted that, as of December 2017, Wi-Fi system is not yet allowed in this band. Regulation is expected to be finished in 2019-2020 time frame), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3800 - 4200 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, etc.), spectrum made available under FCC's "Spectrum Frontier" 5G initiative (including 27.5 - 28.35 GHz, 29.1 - 29.25 GHz, 31 - 31.3 GHz, 37 - 38.6 GHz, 38.6 - 40 GHz, 42 - 42.5 GHz, 57 - 64 GHz, 71 - 76 GHz, 81 - 86 GHz and 92 - 94 GHz, etc), the ITS (Intelligent Transport Systems) band of 5.9 GHz (typically 5.85-5.925 GHz) and 63-64 GHz, bands currently allocated to WiGig such as WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz) and WiGig Band 3 (61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz), 57- 64/66 GHz (note: this band has near-global designation for Multi -Gigabit Wireless Systems (MGWS)/WiGig . In US (FCC part 15) allocates total 14 GHz spectrum, while EU (ETSI EN 302 567 and ETSI EN 301 217-2 for fixed P2P) allocates total 9 GHz spectrum), the 70.2 GHz - 71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated to automotive radar applications such as 76-81 GHz, and future bands including 94-300 GHz and above. Furthermore, the scheme can be used on a secondary basis on bands such as the TV White Space bands (typically below 790 MHz) where in particular the 400 MHz and 700 MHz bands are promising candidates. Besides cellular applications, specific applications for vertical markets may be addressed such as PMSE (Program Making and Special Events), medical, health, surgery, automotive, low-latency, drones, etc. applications.

[0056] Aspects described herein can also implement a hierarchical application of the scheme is possible, e.g., by introducing a hierarchical prioritization of usage for different types of users (e.g., low/medium/high priority, etc.), based on a prioritized access to the spectrum e.g., with highest priority to tier-1 users, followed by tier-2, then tier-3, etc. users, etc.

[0057] Aspects described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0058] Some of the features in this document are defined for the network side, such as APs, eNBs, NR or gNBs - note that this term is typically used in the context of 3GPP 5G and 6G communication systems, etc. Still, a UE may take this role as well and act as an AP, eNB, or gNB; that is some or all features defined for network equipment may be implemented by a UE.

[0059] As above, FIG. 3 illustrates an O-RAN system architecture in accordance with some aspects. FIG. 3 provides a high-level view of an O-RAN architecture 300. The O-RAN architecture 300 includes four O-RAN defined interfaces - namely, the Al interface, the 01 interface, the 02 interface, and the Open Fronthaul Management (M)-plane interface - which connect the Service Management and Orchestration (SMO) framework 302 to O-RAN network functions (NFs) 304 and the O-Cloud 306.

[0060] The 01 interface is an interface between orchestration & management entities (Orchestration/NMS) and O-RAN managed elements, for operation and management, by which FCAPS management, Software management, File management and other similar functions is achieved. The 02 interface is an interface between the SMO Framework and the O-Cloud. The Al interface is an interface between Non-RT RIC and Near-RT RIC to enable policy-driven guidance of Near-RT RIC applications/functions, and support AI/ML workflow.

[0061] The SMO 302 also connects with an external system 310, which provides additional configuration data to the SMO 302. FIG. 3 also illustrates that the Al interface connects the O-RAN Non-Real Time (RT) RAN Intelligent Controller (RIC) 312 in or at the SMO 302 and the O-RAN Near-RT RIC 314 in or at the O-RAN NFs 304. The O-RAN NFs 304 can be virtualized network functions (VNFs) such as virtual machines (VMs) or containers, sitting above the O-Cloud 306 and/or Physical Network Functions (PNFs) utilizing customized hardware. All O-RAN NFs 304 are expected to support the 01 interface when interfacing with the SMO framework 302. The O-RAN NFs 304 connect to the NG-Core 308 via the NG interface (which is a 3GPP defined interface). The Open Fronthaul M-plane interface between the SMO 302 and the O-RAN Radio Unit (O-RU) 316 supports the O-RU 316 management in the O- RAN hybrid model. The Open Fronthaul M-plane interface is an optional interface to the SMO 302 that is included for backward compatibility purposes and is intended for management of the O-RU 316 in hybrid mode only. The O- RU 316 termination of the 01 interface towards the SMO 302.

[0062] FIG. 4 illustrates a logical architecture of the O-RAN system of FIG. 3 in accordance with some aspects. FIG. 4 shows an O-RAN logical architecture 400 corresponding to the O-RAN architecture 300 of FIG. 3. In FIG. 4, the SMO 402 corresponds to the SMO 302, O-Cloud 406 corresponds to the O-Cloud 306, the Non-RT RIC 412 corresponds to the Non-RT RIC 312, the Near-RT RIC 414 corresponds to the Near-RT RIC 314, and the O-RU 416 corresponds to the O-RU 316 of FIG. 3, respectively. The O-RAN logical architecture 400 includes a radio portion and a management portion.

[0063] The management portion/side of the architectures 400 includes the SMO Framework 402 containing the Non-RT RIC 412 and may include the O-Cloud 406. The O-Cloud 406 is a cloud computing platform including a collection of physical infrastructure nodes to host the relevant O-RAN functions (e.g., the Near-RT RIC 414, O-RAN Central Unit - Control Plane (O-CU-CP) 421, O-RAN Central Unit - User Plane (O-CU-UP) 422, and the O-RAN Distributed Unit (O-DU) 415), supporting software components (e.g., OSs, VMMs, container runtime engines, ML engines, etc.), and appropriate management and orchestration functions.

[0064] The radio portion/side of the logical architecture 400 includes the Near-RT RIC 414, the O-RAN Distributed Unit (0-DU) 415, the 0-RU 416, the O-RAN Central Unit - Control Plane (O-CU-CP) 421, and the O-RAN Central Unit - User Plane (O-CU-UP) 422 functions. The radio portion/side of the logical architecture 400 may also include the O-e/gNB 410.

[0065] The 0-DU 415 is a logical node hosting radio link control (RLC), medium access control (MAC), and higher physical (PHY) layer entities/ elements (High-PHY layers) based on a lower layer functional split. The 0-RU 416 is a logical node hosting lower PHY layer entities/elements (Low-PHY layer) (e.g., Fast Fourier Transform/Inverse Fast Fourier Transform (FFT/iFFT), Physical Random Access Channel (PRACH) extraction, etc.) and RF processing elements based on a lower layer functional split. The O-CU-CP 421 is a logical node hosting the Radio Resource Control (RRC) and the control plane (CP) part of the Packet Data Convergence Protocol (PDCP) protocol. The O-CU-UP 422 is a logical node hosting the user-plane part of the PDCP protocol and the Service Data Adaptation Protocol (SDAP) protocol.

[0066] An E2 interface terminates at a plurality of E2 nodes. The E2 nodes are logical nodes/entities that terminate the E2 interface. For NR/5G access, the E2 nodes include the O-CU-CP 421, O-CU-UP 422, O-DU 415, or any combination of elements. For E-UTRA access the E2 nodes include the O- e/gNB 410. As shown in FIG. 4, the E2 interface also connects the O-e/gNB 410 to the Near-RT RIC 414. The protocols over the E2 interface are based exclusively on CP protocols. The E2 functions are grouped into the following categories: (a) Near-RT RIC 414 services (REPORT, INSERT, CONTROL, and POLICY; and (b) Near-RT RIC 414 support functions, which include E2 Interface Management (E2 Setup, E2 Reset, Reporting of General Error Situations, etc.) and Near-RT RIC Service Update (e.g., capability exchange related to the list of E2 Node functions exposed over E2).

[0067] FIG. 4 shows the Uu interface between a UE 401 and O-e/gNB 410 as well as between the UE 401 and O-RAN components. The Uu interface is a 3GPP defined interface, which includes a complete protocol stack from LI to L3 and terminates in the NG-RAN or E-UTRAN. The O-e/gNB 410 is an LTE eNB, a 5G gNB, or ng-eNB that supports the E2 interface. The O-e/gNB 410 may be the same or similar as other RAN nodes discussed previously. The UE 401 may correspond to UEs discussed previously and/or the like. There may be multiple UEs 401 and/or multiple O-e/gNB 410, each of which may be connected to one another via respective Uu interfaces. Although not shown in FIG. 4, the O-e/gNB 410 supports O-DU 415 and 0-RU 416 functions with an Open Fronthaul (OF) interface between them.

[0068] The OF interface(s) is/are between O-DU 415 and 0-RU 416 functions. The OF interface^) includes the Control User Synchronization (CUS) Plane and Management (M) Plane. FIG. 3 and FIG. 4 also show that the 0-RU 416 terminates the OF M-Plane interface towards the O-DU 415 and optionally towards the SMO 402. The O-RU 416 terminates the OF CUS-Plane interface towards the O-DU 415 and the SMO 402.

[0069] The Fl-c interface connects the O-CU-CP 421 with the O-DU

415. As defined by 3GPP, the Fl-c interface is between the gNB-CU-CP and gNB-DU nodes. However, for purposes of O-RAN, the Fl-c interface is adopted between the O-CU-CP 421 with the O-DU 415 functions while reusing the principles and protocol stack defined by 3GPP and the definition of interoperability profile specifications.

[0070] The Fl-u interface connects the O-CU-UP 422 with the O-DU 415. As defined by 3GPP, the Fl-u interface is between the gNB-CU-UP and gNB-DU nodes. However, for purposes of O-RAN, the Fl-u interface is adopted between the O-CU-UP 422 with the O-DU 415 functions while reusing the principles and protocol stack defined by 3GPP and the definition of interoperability profile specifications.

[0071] The NG-c interface is defined by 3GPP as an interface between the gNB-CU-CP and the AMF in the 5GC. The NG-c is also referred to as the N2 interface. The NG-u interface is defined by 3GPP, as an interface between the gNB-CU-UP and the UPF in the 5GC. The NG-u interface is referred to as the N3 interface. In O-RAN, NG-c and NG-u protocol stacks defined by 3GPP are reused and may be adapted for O-RAN purposes.

[0072] The X2-c interface is defined in 3 GPP for transmitting control plane information between eNBs or between eNB and en-gNB in EN-DC. The X2-u interface is defined in 3 GPP for transmitting user plane information between eNBs or between eNB and en-gNB in EN-DC. In O-RAN, X2-c and X2-u protocol stacks defined by 3GPP are reused and may be adapted for O- RAN purposes.

[0073] The Xn-c interface is defined in 3GPP for transmitting control plane information between gNBs, ng-eNBs, or between an ng-eNB and gNB. The Xn-u interface is defined in 3GPP for transmitting user plane information between gNBs, ng-eNBs, or between ng-eNB and gNB. In O-RAN, Xn-c and Xn-u protocol stacks defined by 3GPP are reused and may be adapted for O- RAN purposes.

[0074] The El interface is defined by 3GPP as being an interface between the gNB-CU-CP and gNB-CU-UP. In O-RAN, El protocol stacks defined by 3GPP are reused and adapted as being an interface between the O- CU-CP 421 and the O-CU-UP 422 functions.

[0075] The O-RAN Non-RT RIC 412 is a logical function within the SMO framework 302, 402 that enables non-real-time control and optimization of RAN elements and resources; Al/machine learning (ML) workflow(s) including model training, inferences, and updates; and policy-based guidance of applications/features in the Near-RT RIC 414.

[0076] The O-RAN Near-RT RIC 414 is a logical function that enables near-real-time control and optimization of RAN elements and resources via fine- grained data collection and actions over the E2 interface. The Near-RT RIC 414 may include one or more AI/ML workflows including model training, inferences, and updates.

[0077] The Non-RT RIC 412 can be an ML training host to host the training of one or more ML models. ML training can be performed offline using data collected from the RIC, O-DU 415, and O-RU 416. For supervised learning, Non-RT RIC 412 is part of the SMO 402, and the ML training host and/or ML model host/actor can be part of the Non-RT RIC 412 and/or the Near- RT RIC 414. For unsupervised learning, the ML training host and ML model host/actor can be part of the Non-RT RIC 412 and/or the Near-RT RIC 414. For reinforcement learning, the ML training host and ML model host/actor may be co-located as part of the Non-RT RIC 412 and/or the Near-RT RIC 414. In some implementations, the Non-RT RIC 412 may request or trigger ML model training in the training hosts regardless of where the model is deployed and executed. ML models may be trained and not currently deployed.

[0078] In some embodiments, the Non-RT RIC 412 provides a query- able catalog for an ML designer/developer to publish/install trained ML models (e.g., executable software components). In these implementations, the Non-RT RIC 412 may provide a discovery mechanism if a particular ML model can be executed in a target ML inference host (MF), and what number and type of ML models can be executed in the MF. For example, there may be three types of ML catalogs made discoverable by the Non-RT RIC 412: a design-time catalog (e.g., residing outside the Non-RT RIC 412 and hosted by some other ML platform(s)), a training/deployment-time catalog (e.g., residing inside the Non- RT RIC 412), and a run-time catalog (e.g., residing inside the Non-RT RIC 412). The Non-RT RIC 412 supports necessary capabilities for ML model inference in support of ML assisted solutions running in the Non-RT RIC 412 or some other ML inference host. These capabilities enable executable software to be installed such as VMs, containers, etc. The Non-RT RIC 412 may also include and/or operate one or more ML engines, which are packaged software executable libraries that provide methods, routines, data types, etc., used to run ML models. The Non-RT RIC 412 may also implement policies to switch and activate ML model instances under different operating conditions.

[0079] The Non-RT RIC 412 can access feedback data (e.g., FM and PM statistics) over the 01 interface on ML model performance and perform necessary evaluations. If the ML model fails during runtime, an alarm can be generated as feedback to the Non-RT RIC 412. How well the ML model is performing in terms of prediction accuracy or other operating statistics it produces can also be sent to the Non-RT RIC 412 over 01. The Non-RT RIC 412 can also scale ML model instances running in a target MF over the 01 interface by observing resource utilization in MF. The environment where the ML model instance is running (e.g., the MF) monitors resource utilization of the running ML model. This can be done, for example, using an ORAN-SC component called ResourceMonitor in the Near-RT RIC 414 and/or in the Non- RT RIC 412, which continuously monitors resource utilization. If resources are low or fall below a certain threshold, the runtime environment in the Near-RT RIC 414 and/or the Non-RT RIC 412 provides a scaling mechanism to add more ML instances. The scaling mechanism may include a scaling factor such as a number, percentage, and/or other like data used to scale up/down the number of ML instances. ML model instances running in the target ML inference hosts may be automatically scaled by observing resource utilization in the MF. For example, the Kubemetes® (K8s) runtime environment typically provides an auto-scaling feature.

[0080] The Al interface is between the Non-RT RIC 412 (within or outside the SMO 402) and the Near-RT RIC 414. The Al interface supports three types of services, including a Policy Management Service, an Enrichment Information Service, and ML Model Management Service. Al policies have the following characteristics compared to persistent configuration: Al policies are not critical to traffic; Al policies have temporary validity; Al policies may handle individual UE or dynamically defined groups of UEs; Al policies act within and take precedence over the configuration; and Al policies are non- persistent, i.e., do not survive a restart of the Near-RT RIC.

[0081] FIG. 5 illustrates an example O-RAN Architecture in accordance with some aspects. As shown, the Near-RT RIC is a logical network node placed between the SMO layer, which hosts the Non-RT RIC, and the E2 Nodes. The Near-RT-RIC logical architecture and related interfaces are shown in FIG.

5. The Near-RT RIC is connected to the Non-RT RIC through the Al interface. A Near-RT RIC is connected to only one Non-RT RIC. As above, E2 is a logical interface connecting the Near-RT RIC with an E2 Node. The Near-RT RIC is connected to the O-CU-CP. The Near-RT RIC is connected to the O-CU-

UP. The Near-RT RIC is connected to the 0-DU. The Near-RT RIC is connected to the O-eNB. An E2 Node is connected to only one Near-RT RIC. A Near-RT RIC can be connected to multiple E2 Nodes, i.e., multiple O-CU- CPs, O-CU-UPs, O-DUs and O-eNBs. Fl (Fl-C, Fl-U) and El are logical 3GPP interfaces, whose protocols, termination points and cardinalities are specified in 3GPP TS 38.401.

[0082] The Near-RT RIC hosts one or more xApps that use the E2 interface to collect near real-time information (e.g., UE basis, Cell basis) and provide value added services. The Near-RT RIC may receive declarative Policies and obtain Data Enrichment information over the Al interface. The protocols over E2 interface are based on control plane protocols. On E2 or Near- RT RIC failure, the E2 Node may provide services but there may be an outage for certain value-added services that may only be provided using the Near-RT RIC.

[0083] The Near-RT RIC provides a database function that stores the configurations relating to E2 nodes, Cells, Bearers, Flows, UEs and the mappings between them. The Near-RT RIC provides ML tools that support data pipelining. The Near-RT RIC provides a messaging infrastructure. The Near- RT RIC provides logging, tracing and metrics collection from Near-RT RIC framework and xApps to SMO. The Near-RT RIC provides security functions. The Near-RT RIC supports conflict resolution to resolve the potential conflicts or overlaps which may be caused by the requests from xApps.

[0084] The Near-RT RIC also provides an open API enabling the hosting of 3rd party xApps and xApps from the Near-RT RIC platform vendor. The Near-RT RIC also provides an open API decoupled from specific implementation solutions, including a Shared Data Layer (SDL) that works as an overlay for underlying databases and enables simplified data access.

[0085] An xApp is an application designed to run on the Near-RT RIC. Such an application is likely to include or provide one or more microservices and at the point of on-boarding will identify which data it consumes and which data it provides. An xApp is independent of the Near-RT RIC and may be provided by any third party. The E2 enables a direct association between the xApp and the RAN functionality. A RAN Function is a specific Function in an E2 Node; examples include X2AP, F1AP, E1AP, SI AP, NGAP interfaces and RAN internal functions handling UEs, Cells, etc.

[0086] The architecture of an xApp has the code implementing the xApp's logic and the RIC libraries that allow the xApp to: send and receive messages; read from, write to, and get notifications from the SDL layer; and write log messages. Additional libraries will be available in future versions including libraries for setting and resetting alarms and sending statistics. Furthermore, xApps can use access libraries to access specific name-spaces in the SDL layer. For example, the R-NIB that provides information about which E2 nodes (e.g., CU/DU) the RIC is connected to and which SMs are supported by each E2 node, can be read by using the R-NIB access library. [0087] The O-RAN standard interfaces (e.g., 01, Al, and E2) are exposed to the xApps as follows: xApp receive its configuration via K8s ConfigMap - the configuration can be updated while the xApp is running and the xApp can be notified of this modification by using inotifyO; xApp can send statistics (PM) either by (a) sending it directly to VES collector in VES format, (b) by exposing statistics via a REST interface for Prometheus to collect; xApp will receive Al policy guidance via an RMR message of a specific kind (policy instance creation and deletion operations); and xApp can subscribe to E2 events by constructing the E2 subscription ASN.l payload and sending it as a message (RMR), xApp will receive E2 messages (e.g., E2 INDICATION) as RMR messages with the ASN.l payload. Similarly xApp can issue E2 control messages.

[0088] In addition to Al and E2 related messages, xApps can send messages that are processes by other xApps and can receive messages produced by other xApps. Communication inside the RIC is policy driven, that is, an xApp cannot specify the target of a message - the xApp simply sends a message of a specific type and the routing policies specified for the RIC instance determine to which destinations this message is to be delivered (logical pub/sub). [0089] Logically, an xApp is an entity that implements a well-defined function. Mechanically, an xApp is a K8s pod that includes one or multiple containers. For an xApp to be deployable, the xApp has an xApp descriptor (e.g., JSON) that describes the xApp's configuration parameters and information the RIC platform uses to configure the RIC platform for the xApp. The xApp developer also provides a JSON schema for the descriptor.

[0090] In addition to these basic requirements, an xApp may do any of the following: read initial configuration parameters (passed in the xApp descriptor); receive updated configuration parameters; send and receive messages; read and write into a persistent shared data storage (key-value store); receive Al-P policy guidance messages - specifically operations to create or delete a policy instance (JSON payload on an RMR message) related to a given policy type; define a new Al policy type; make subscriptions via E2 interface to the RAN, receive E2 INDICATION messages from the RAN, and issue E2 POLICY and CONTROL messages to the RAN; and report metrics related to its own execution or observed RAN events. [0091] The lifecycle of xApp development and deployment includes the following states: Development: Design, implementation, local testing; Released: The xApp code and xapp descriptor are committed to LF Gerrit repo and included in an O-RAN release. The xApp is packaged as Docker container and its image released to LF Release registry; On-boarded/Distributed: The xApp descriptor (and potentially helm chart) is customized for a given RIC environment and the resulting customized helm chart is stored in a local helm chart repo used by the RIC environment's xApp Manager; Run-time Parameters Configuration: Before the xApp can be deployed, run-time helm chart parameters will be provided by the operator to customized the xApp Kubemetes deployment instance. This procedure is mainly used to configure run-time unique helm chart parameters such as instance UUID, liveness check, east-bound and north-bound service endpoints (e.g., DBAAS entry, VES collector endpoint) and so on; Deployed: The xApp has been deployed via the xApp Manager and the xApp pod is running on a RIC instance. For xApps where it makes sense, the deployed status may be further divided into additional states controlled via xApp configuration updates. For example, Running, Stopped.

[0092] The general principles guiding the definition of Near-RT RIC architecture as well as the interfaces between Near-RT RIC, E2 Nodes and SMO include the following: Near-RT RIC and E2 Node functions are fully separated from transport functions. Addressing scheme used in Near-RT RIC and the E2 Nodes are not be tied to the addressing schemes of transport functions; the E2 Nodes support all protocol layers and interfaces defined within 3GPP radio access networks that include eNB for E-UTRAN and gNB/ ng-eNB for NG- RAN; Near-RT RIC and hosted “xApp” applications use a set of services exposed by an E2 Node that is described by a series of RAN function and Radio Access Technology (RAT) dependent “E2 Service Models”; The Near-RT RIC interfaces are defined along the following principles: the functional division across the interfaces have as few options as possible, interfaces are based on a logical model of the entity controlled through this interface, one physical network element can implement multiple logical nodes.

[0093] xApps may enhance the RRM capabilities of the Near-RT RIC. xApps provide logging, tracing and metrics collection to the Near-RT RIC. [0094] According to various embodiments, xApps include an xApp descriptor and xApp image. The xApp image is the software package. The xApp image contains all the files used to deploy an xApp. An xApp can have multiple versions of xApp image, which are tagged by the xApp image version number.

[0095] The xApp descriptor describes the packaging format of xApp image. The xApp descriptor also provides the data to enable their management and orchestration. The xApp descriptor provides xApp management services with necessary information for the LCM of xApps, such as deployment, deletion, upgrade etc. The xApp descriptor also provides extra parameters related to the health management of the xApps, such as auto scaling when the load of xApp is too heavy and auto healing when xApp becomes unhealthy. The xApp descriptor provides FCAPS and control parameters to xApps when xApp is launched.

[0096] The definition of xApp descriptor includes: The basic information of xApp, including name, version, provider, URL of xApp image, virtual resource requirements (e.g. CPU), etc. This information is used to support LCM of xApps. Additionally or alternatively, the basic information include or indicate configuration, metrics, and control data about an xApp; the FCAPS management specifications that specify the options of configuration, performance metrics collection, etc. for the xApp; the control specifications that specify the data types consumed and provided by the xApp for control capabilities (e.g., Performance Management (PM) data that the xApp subscribes, the message type of control messages).

[0097] Additionally or alternatively, the xApp descriptor components include the following: Configuration: The xApp configuration specification included a data dictionary for the configuration data, i.e., metadata such as a yang definition or a list of configuration parameters and their semantics. Additionally it may include an initial configuration of xApps; Control: xApp controls specification shall include the types of data it consumes and provides that enable control capabilities (e.g. xApp URL, parameters, input/output type). Metrics: The xApp metrics specification included a list of metrics (e.g., metric name, type, unit and semantics) provided by the xApp. [0098] In these examples, the Near-RT RIC hosts the following functions: Database functionality, which allows reading and writing of RAN/UE information; xApp subscription management, which merges subscriptions from different xApps and provides unified data distribution to xApps; Conflict mitigation, which resolves potentially overlapping or conflicting requests from multiple xApps; Messaging infrastructure, which enables message interaction amongst Near-RT RIC internal functions; Security, which provides the security scheme for the xApps; and Management services including: fault management, configuration management, and performance management as a service producer to SMO; life-cycle management of xApps; and logging, tracing and metrics collection, which capture, monitor and collect the status of Near-RT RIC internals and can be transferred to external system for further evaluation; and Interface Termination including: E2 termination, which terminates the E2 interface from an E2 Node; Al termination, which terminates the Al interface from the Non-RT RIC; and 01 termination, which terminates the 01 interface from SMO; and Functions hosted by xApps, which allow services to be executed at the Near-RT RIC and the outcomes sent to the E2 Nodes via E2 interface.

[0099] xApps may provide UE related information to be stored in the UE-NIB (UE-Network Information Base) database. UE-NIB maintains a list of UEs and associated data. The UE-NIB maintains tracking and correlation of the UE identities associated with the connected E2 nodes. xApps may provide radio access network related information to be stored in the R-NIB (Radio-Network Information Base) database. The R-NIB stores the configurations and near realtime information relating to connected E2 Nodes and the mappings between them.

[00100] xApp subscription management manages subscriptions from the xApps to the E2 Nodes. xApp subscription management enforces authorization of policies controlling xApp access to messages. xApp subscription management enables merging of identical subscriptions from different xApps into a single subscription to the E2 Node.

[00101] FIG. 6 illustrates a flow diagram of a handover (HO) process in accordance with some aspects. As above, high mobility or dense environments with large numbers of (micro and other) cells may increase the frequency of a UE engaging in the handover process. As shown: [00102] 11.. The source gNB-CU-CP sends HANDOVER REQUEST message to the target gNB-CU-CP. In case of Conditional Handover, the target gNB is regarded as a candidate gNB which is only accessed by the UE when the CHO condition(s) are fulfilled.

[00103] 2-4. Bearer Context Setup procedure is performed as described in Section 8.9.2 of 3GPP TS 38.401.

[00104] 55.. The target gNB-CU-CP responds the source gNB-CU-CP with a HANDOVER REQUEST ACKNOWLEDGE message.

[00105] 6. The F 1 UE Context Modification procedure is performed to send the handover command to the UE, and to indicate to stop the data transmission for the UE.

[00106] 7-8. Bearer Context Modification procedure (gNB-CU-CP initiated) is performed to enable the gNB-CU-CP to retrieve the PDCP UL/DL status and to exchange data forwarding information for the bearer.

[00107] 9. The source gNB-CU-CP sends an SN STATUS

TRANSFER message to the target gNB-CU-CP.

[00108] 10-11. Bearer Context Modification procedure is performed as described in Section 8.9.2. The target gNB-CU-CP does not transfer the PDCP UL/DL status carried from the SN STATUS TRANSFER message to the target gNB-CU-UP if the PDCP status does not need to be preserved (e.g. full configuration).

[00109] 1122.. Data Forwarding may be performed from the source gNB-

CU-UP to the target gNB-CU-UP.

[00110] 12a. In case of DAPS Handover or Conditional Handover, the target gNB-CU-CP sends the HANDOVER SUCCESS message to the source gNB-CU-CP to inform that the UE has successfully accessed the target cell.

[00111] 12b. In case of DAPS Handover or Conditional Handover, the

Fl UE Context Modification procedure is performed to indicate to stop the data transmission for the UE.

[00112] 12c-12d. In case of DAPS Handover or Conditional

Handover, the Bearer context modification procedure (gNB-CU-CP initiated) is performed to indicate the source gNB-CU-UP to stop packet delivery and also to retrieve the PDCP UL/DL status. [00113] 12e. In case of DAPS Handover or Conditional Handover, the source gNB-CU-CP sends the SN STATUS TRANSFER message to the target gNB-CU-CP.

[00114] 12f-12g. In case of DAPS Handover or Conditional

Handover, the Bearer context modification procedure is performed to provide the PDCP UL/DL status to the target gNB-CU-UP only if the PDCP status needs to be preserved as described in TS 38.300.

[00115] 13-15. Path Switch procedure is performed to update the DL

TNL address information for the NG-U towards the core network.

[00116] 1166.. The target gNB-CU-CP sends an UE CONTEXT

RELEASE message to the source gNB-CU-CP.

[00117] 17. and 19. Bearer Context Release procedure is performed.

[00118] 18. Fl UE Context Release procedure is performed to release the UE context in the source gNB-DU.

[00119] 3GPP has been supporting data forwarding and lossless delivery when a UE hands over from one cell to another. For NR (i.e., from 3GPP Rel- 15), support for lossless was extended even when a QoS flow is remapped to a different data radio bearer (DRB) at handover. During lossless delivery when a QoS flow is mapped to a different DRB at handover, the old DRB (i.e., configured by the source node) is configured in the target cell. For in-order delivery in the downlink (DL), the target gNB first transmits the forwarded PDCP service data units (SDUs) on the old DRB before transmitting new data from the 5GC on the new DRB. In the uplink (UL), the target gNB may not deliver data of the QoS flow from the new DRB to the 5GC before receiving the end marker on the old DRB from the UE.

[00120] Achieving lossless during handover is based on the source forwarding PDCP SDUs with sequence number (SN) assigned but not acknowledged by the UE in an old DRB. In fact, DL QoS flows can be forwarded over the PDU session tunnel in a lossless fashion, but in this case the old DRB is configured with the presence of a DL SDAP header to determine that Service Data Adaptation Protocol (SDAP) SDUs extracted from those PDCP SDUs (already processed through SDAP entity) belongs to which QoS flow (based on the QoS Flow Identifier (QFI)). Moreover, QoS flow level forwarding by establishing a PDU session forwarding tunnel does not guarantee duplicate delivery protection. To guarantee lossless and avoid duplicate delivery, and also to be able to guarantee in-sequence delivery by the existing PDCP SN preservation mechanism, the old DRB is configured and continued temporarily at the target side, and the source performs DRB-level forwarding and forwards QoS flows of old DRBs by PDCP SDUs until the source receives an end-marker from the CN.

[00121] This mechanism is sufficient when a target node is aggregated. However, in case of a separated CP-UP, currently the target CU-CP first sets up old DRBs in the target CU-UP side and then updates mapping (or establishes a new DRB) separately via the El AP BEARER CONTEXT SETUP and BEARER CONTEXT MODIFICATION procedure. Of course, such an update on DRB configuration via the El AP BEARER CONTEXT MODIFICATION procedure should not happen before the target CU-UP finishes transmitting the forwarded old DRBs* PDCP SDUs. This may break lossless delivery for old DRBs. Moreover, as QoS flow remapping is to occur at handover, the mapping update for old DRBs is better to happen in a timely fashion, i.e., as soon as the target CU-UP finishes transmitting the forwarded PDCP SDUs. However, it is the target CU-UP that is responsible for user plane processing - the target CU-CP has no idea when the target CU-UP would be finished for a subjected DRB. A bearer context, as known, is a block of information in a gNB-CU-UP node associated to one UE that is used for communication over the El interface. The bearer context may include information about data radio bearers, PDU sessions and QoS-flows associated to the UE and contains information to maintain userplane services toward the UE.

[00122] In some embodiments, the target CU-CP can estimate the timing as the CN sends an end-marker to the source upon receiving a path switch request from the target CU-CP. However, there may be a processing delay in the CN side that cannot be estimated. Moreover, the number of buffered packets in the source side (and thus the time to finish forwarding at the source side and the time to finish transmitting at the target side) differs dependent on the DRB. A blind estimation of the timing to update DRB configuration via the E1AP BEARER CONTEXT MODIFICATION procedure could result in breaking lossless delivery if early (as mentioned above), or if late, then the benefit of QoS flow remapping at handover is lost. Even assuming that the target CU-CP is able to determine the exact timing, the target CU-CP may end up triggering multiple BEARER CONTEXT MODIFICATION procedures as the timing could differ by DRBs, which is inefficient. Therefore, it is desirable to provide a mechanism to overcome the above limitations in NR when a target NG-RAN node has a CP-UP separation.

[00123] FIGS. 7-9 show the Bearer Context Setup and Modification procedures. Specifically, FIG. 7 illustrates a Bearer Context Setup procedure in accordance with some embodiments. The Bearer Context Setup procedure allows the gNB-CU-CP to establish a bearer context in the gNB-CU-UP. The gNB-CU-CP initiates the procedure by sending the BEARER CONTEXT SETUP REQUEST message to the gNB-CU-UP. If the gNB-CU-UP succeeds to establish the requested resources, it replies to the gNB-CU-CP with the BEARER CONTEXT SETUP RESPONSE message. The gNB-CU-UP reports to the gNB-CU-CP, in the BEARER CONTEXT SETUP RESPONSE message, the result for all the requested resources including, for NG-RAN: a list of successfully established PDU Session Resources in a PDU Session Resource Setup List IE; a list of PDU Session Resources that failed to be established in a PDU Session Resource Failed List IE; for each established PDU Session Resource, a list of successfully established DRBs in a DRB Setup List IE; for each established PDU Session Resource, a list of DRBs that failed to be established in the DRB Failed Ust IE; for each established DRB, a list of successfully established QoS Flows in a Flow Setup List IE; and for each established DRB, a list of QoS Flows that failed to be established in a Flow Failed List IE.

[00124] FIG. 8 illustrates a gNB-CU-CP initiated Bearer Context Modification procedure in accordance with some embodiments. The gNB-CU- CP initiated Bearer Context Modification procedure allows the gNB-CU-CP to modify a bearer context in the gNB-CU-UP. The gNB-CU-CP initiates the procedure by sending the BEARER CONTEXT MODIFICATION REQUEST message to the gNB-CU-UP. If the gNB-CU-UP succeeds to modify the bearer context, it replies to the gNB-CU-CP with the BEARER CONTEXT MODIFICATION RESPONSE message.

[00125] FIG. 9 illustrates a gNB-CU-UP initiated Bearer Context Modification procedure in accordance with some embodiments. The gNB-CU- UP initiated Bearer Context Modification procedure allows the gNB-CU-UP to modify a bearer context (e.g., due to local problems) and inform the gNB-CU- CP. The gNB-CU-UP initiates the procedure by sending the BEARER CONTEXT MODIFICATION REQUIRED message to the gNB-CU-CP. The gNB-CU-CP replies with the BEARER CONTEXT MODIFICATION CONFIRM message.

[00126] Embodiment 1 : The target CU-CP establishes old DRBs in the target CU-UP. Then, the target CU-UP informs the target CU-CP when the target CU-UP finishes transmitting forwarded PDCP SDUs, so that the target CU-CP can timely update the DRB configuration via the subsequent BEARER CONTEXT MODIFICATION procedure. In this case, knowledge of the exact timing may be irrelevant as the target CU-UP is responsible for user plane processing. However, roundtrip delay and an indication from the target CU-UP and subsequent update from the target CU-CP could occur multiple times as the exact timing could differ between DRBs. An example implementation for El AP (TS 38.463) is as follows:

[00127] For TS 38.463 [00128] 9.3.3.2 PDU Session Resource To Setup List [00129] This IE contains PDU session resource-related information used at Bearer Context Setup Request.

[00130] As shown, the Forwarding Complete Notification Request IE may indicate a request for a Forwarding Complete Notification message from the gNB-CU-UP when forwarding has been completed.

[00131] 9.2.2.X FORWARDING COMPLETE NOTIFICATION

[00132] This message is sent by the gNB-CU-UP to indicate to the gNB-

CU-CP that transmitting the forwarded PDCP SDUs has been completed for the listed DRBs.

[00133] Direction: gNB-CU-UP → gNB-CU-CP

[00134] The Message Type IE uniquely identifies the message being sent. The gNB-CU-CP UE El AP ID uniquely identifies the UE association over the El interface within the gNB-CU-CP. The gNB-CU-UP UE E1AP ID uniquely identifies the UE association over the El interface within the gNB-CU-UP. The DRB ID uniquely identifies a DRB for a UE.

[00135] Embodiment 2: The target CU-CP establishes a superset of old and new DRBs in the target CU-UP and at the same time indicates the updated mapping to the old DRBs to be reflected when the target CU-UP finishes transmitting the forwarded PDCP SDUs. In this embodiment, the QoS flows may not be subject to forwarding as each DRB is a superset of QoS flows to be setup for that DRB. In this case, the source DRB configuration is retained and then updated to new mapping, which occurs as soon as the target CU-UP finishes transmitting the forwarded PDCP SDUs for each old DRB (whose timing could be different dependent on the DRB). No additional communication is used between the target CU-CP and CU-UP as in Embodiment 1, or potential delay that could be involved; the one-time BEARER CONTEXT SETUP procedure may be sufficient.

[00136] For TS 38.463 [00137] 9.3.3.2 PDU Session Resource To Setup List [00138] This IE contains PDU session resource related information used at Bearer Context Setup Request

[00139] If the Updated QoS Flows Information To Be Setup IE is present,

QoS flow mapping in the DRB is updated as soon as transmitting the forwarded

PDCP SDUs from the source during handover has been completed. The QoS

Flow QoS Parameters List contained is provided below:

[00140] 9.3.1.25 QoS Flow QoS Parameters List

[00141] This IE contains a list of QoS Flows including the QoS Flow parameters.

[00142] In some embodiments, rather than the above Updated QoS Flows Information To Be Setup parameter, a QoS flows remapping parameter may be used. The QoS flows remapping parameter is similar to the Updated QoS Flows Information To Be Setup parameter, indicating a change in the DRB configuration of the DRB used during forwarding of the DRBs from the source gNB after completion of the forwarding. In particular, the enumerated values of the QoS flows remapping parameter may indicate that the DRB is to still exist but the QoS flows of the DRB are to be changed (enumeration value "update") or may indicate that the DRB may be deleted (enumeration "source configuration").

[00143] Thus, some embodiments, if the QoS Flows Remapping IE is contained within the DRB To Setup List IE in the BEARER CONTEXT SETUP REQUEST message for a DRB and set to "update", the gNB-CU-UP may consider that QoS flows mapped for the DRB is updated to the QoS flow(s) included in the QoS Flows Information To Be Setup IE after finishing handling forwarded PDCP SDUs during an intra-system handover procedure. If the QoS Flows Remapping IE is contained within the DRB To Setup List IE in the BEARER CONTEXT SETUP REQUEST message for a DRB and set to "source configuration", the gNB-CU-UP may consider that no QoS flow is mapped to the DRB after finishing handling forwarded PDCP SDUs over that DRB during an intra-system handover procedure and ignore the information included in the QoS Flows Information To Be Setup IE for the concerned DRB.

[00144] In some embodiments, the QoS Flows Remapping IE may be contained within the DRB To Setup List IE of the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message.

[00145] Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[00146] The subject matter may be referred to herein, individually and/or collectively, by the term “embodiment” merely for convenience and without intending to voluntarily limit the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description. [00147] In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects. [00148] The Abstract of the Disclosure is provided to comply with 37

C.F.R. § 1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims

CLAIMS What is claimed is:

1. An apparatus for a 5^th generation NodeB Central Unit-Control Plane (gNB-CU-CP), the apparatus comprising: processing circuitry configured to: determine that handover of a user equipment (UE) from a source gNB is to occur; determine whether quality of service (QoS) flow remapping for a data radio bearer (DRB) is to occur during the handover; and in response to a determination that the QoS flow remapping is to occur, provide, to a Central Unit-User Plane (gNB-CU-UP) via an El interface, a message for the DRB that indicates QoS flow remapping is to occur for the gNB-CU-UP after completion of transmission of Packet Data Convergence Protocol (PDCP) service data units (SDUs) of the DRB that are forwarded from the source gNB; and a memory configured to store the message.

2. The apparatus of claim 1, wherein the handover is lossless handover.

3. The apparatus of claim 1, wherein the message comprises a PDU Session Resource To Setup List information element (IE) indicates the QoS flow remapping in a QoS remapping IE.

4. The apparatus of claim 3, wherein the PDU Session Resource To Setup List IE further comprises a QoS mapping IE for the DRB from the source gNB for the gNB-CU-UP to use to transmit the PDCP SDUs forwarded from the source gNB.

5. The apparatus of claim 1, wherein the message indicates that the gNB- CU-UP is to apply the QoS remapping automatically after the completion of the transmission of the PDCP SDUs forwarded from the source gNB.

6. The apparatus of claim 1, wherein: the processing circuitry is further configured to decode a request to establish the DRB in the gNB-CU-UP; and the message indicates an updated DRB configuration for the DRB in response to the request, the updated DRB configuration comprising the QoS flow remapping.

The apparatus of claim 1, wherein: the processing circuitry is further configured to decode a request to establish the DRB in the gNB-CU-UP; and the message indicates an updated DRB configuration for the DRB, the updated DRB configuration comprising the QoS flow remapping, the updated DRB configuration indicated after establishment of the DRB.

8. The apparatus of claim 1, wherein the processing circuitry is further configured to provide an updated DRB configuration to update a DRB configuration of the DRB via a BEARER CONTEXT SETUP REQUEST procedure, the updated DRB configuration comprising the QoS flow remapping.

9. The apparatus of claim 8, wherein the BEARER CONTEXT SETUP REQUEST procedure comprises transmission of a BEARER CONTEXT SETUP REQUEST message to the gNB-CU-UP, and, in response to successful establishment of a bearer context by the gNB-CU-UP, reception of a BEARER CONTEXT SETUP RESPONSE message from the gNB-CU-UP.

10. The apparatus of claim 1, wherein: the message is a BEARER CONTEXT SETUP REQUEST message, the BEARER CONTEXT SETUP REQUEST message comprises a DRB To Setup List IE, the DRB To Setup List IE comprises a QoS Flows Information To Be Setup IE and a QoS Flows Remapping IE, and the QoS Flows Remapping IE indicates to the gNB-CU-UP that QoS flows mapped for the DRB are to be updated to at least one QoS flow included in the QoS Flows Information To Be Setup IE after the completion of the transmission of the PDCP SDUs of the DRB.

11. The apparatus of claim 1, wherein: the message is a BEARER CONTEXT SETUP REQUEST message, the BEARER CONTEXT SETUP REQUEST message comprises a DRB To Setup List IE, the DRB To Setup List IE comprises a QoS Flows Information To Be Setup IE and a QoS Flows Remapping IE, and the QoS Flows Remapping IE indicates to the gNB-CU-UP that, after the completion of the transmission of the PDCP SDUs of the DRB, no QoS flows mapped for the DRB are to be mapped to the DRB and that information included in the QoS Flows Information To Be Setup IE is to be ignored for the DRB.

12. An apparatus for a 5^th generation NodeB Central Unit-User Plane (gNB- CU-UP), the apparatus comprising: processing circuitry configured to: receive, from a Central Unit-Control Plane (gNB-CU-CP) via an El interface during lossless handover of a user equipment (UE) from a source gNB, a BEARER CONTEXT SETUP REQUEST message that indicates whether quality of service (QoS) flow remapping is to occur after completion of transmission of Packet Data Convergence Protocol (PDCP) service data units (SDUs) of the DRB that are forwarded from the source gNB; determine whether the transmission the PDCP SDUs has been completed; and in response to a determination that the transmission the PDCP SDUs has been completed and the QoS flow remapping is to occur, provide, to a Central Unit-Control Plane (gNB-CU-CP) via an El interface, adjust a DRB configuration of the DRB based on the BEARER CONTEXT SETUP REQUEST message; and a memory configured to store the BEARER CONTEXT SETUP REQUEST message.

13. The apparatus of claim 12, wherein the BEARER CONTEXT SETUP REQUEST message comprises a PDU Session Resource To Setup List information element (IE) indicates the QoS flow remapping in a QoS remapping IE.

14. The apparatus of claim 13, wherein the PDU Session Resource To Setup List IE further comprises a QoS mapping IE for the DRB for the gNB-CU-UP to use to transmit the PDCP SDUs forwarded from the source gNB.

15. The apparatus of claim 12, wherein the BEARER CONTEXT SETUP REQUEST message indicates that the gNB-CU-UP is to apply the QoS remapping automatically after the completion of the transmission of the PDCP SDUs forwarded from the source gNB.

16. The apparatus of claim 12, wherein: the BEARER CONTEXT SETUP REQUEST message comprises a DRB To Setup List IE, the DRB To Setup List IE comprises a QoS Flows Information To Be Setup IE and a QoS Flows Remapping IE, and the QoS Flows Remapping IE indicates to the gNB-CU-UP that QoS flows mapped for the DRB are to be updated to at least one QoS flow included in the QoS Flows Information To Be Setup IE after the completion of the transmission of the PDCP SDUs of the DRB.

17. The apparatus of claim 12, wherein: the BEARER CONTEXT SETUP REQUEST message comprises a DRB To Setup List IE, the DRB To Setup List IE comprises a QoS Flows Information To Be Setup IE and a QoS Flows Remapping IE, and the QoS Flows Remapping IE indicates to the gNB-CU-UP that, after the completion of the transmission of the PDCP SDUs of the DRB, no QoS flows mapped for the DRB are to be mapped to the DRB and that information included in the QoS Flows Information To Be Setup IE is to be ignored for the DRB.

18. A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of a 5^th generation NodeB Central Unit-Control Plane (gNB-CU-CP), the one or more processors to configure the gNB-CU-CP to, when the instructions are executed: determine that intra-gNB lossless handover of a user equipment (UE) from a source gNB is to occur; determine whether quality of service (QoS) flow remapping for a data radio bearer (DRB) is to occur during the handover; and in response to a determination that the QoS flow remapping is to occur, provide, to a Central Unit-User Plane (gNB-CU-UP) via an El interface, a BEARER CONTEXT SETUP REQUEST message for the DRB that indicates QoS flow remapping is to occur for the gNB-CU-UP after completion of transmission of Packet Data Convergence Protocol (PDCP) service data units (SDUs) of the DRB that are forwarded from the source gNB.

19. The non-transitory computer-readable storage medium of claim 18, wherein the BEARER CONTEXT SETUP REQUEST message comprises a PDU Session Resource To Setup List information element (IE) that indicates the QoS flow remapping in a QoS remapping IE.

20. The non-transitory computer-readable storage medium of claim 19, wherein the PDU Session Resource To Setup List IE further comprises a QoS mapping IE for the gNB-CU-UP to use to transmit the PDCP SDUs forwarded from the source gNB.