WO2022046756A1 - Computing workload transport over control plane in next generation cellular networks - Google Patents

Abstract

An apparatus and system to provide a flexible measurement information container structure are described. A RIC Subscription is sent from a near-RT RIC to an E2 Node to provide periodic measurements. The RIC Subscription and reporting message includes a structured list of measurements and, for each measurement, a corresponding label that contains values of categories to which the measurement is applicable. An indication in each label is used to override one or more categories of an immediately precedent label. The measurements are used to adjust network resources for traffic steering or QoS-based resource optimization.

Description

COMPUTING WORKLOAD TRANSPORT OVER CONTROL PLANE

IN NEXT GENERATION CELLULAR NETWORKS

PRIORITY CLAIM

[0001] This application claims the benefit of priority to United States Provisional Patent Application Serial No. 63/072,844, filed August 31, 2020, which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Embodiments pertain to fifth generation (5G) and sixth generation (6G) wireless communications. In particular, some embodiments relate to a measurement information container structure in an Open Radio Access Network (O-RAN) system.

BACKGROUND

[0003] The use and complexity of wireless systems, which include 4^th generation (4G) and 5^th generation (5G) 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, especially with the advent of next generation (NG) (or new radio (NR)) systems. 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. 1A illustrates an architecture of a network, in accordance with some aspects.

[0006] FIG. IB 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 Open RAN (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 a RAN Intelligent Controller (RIC) Near-Real Time (RT) RIC REPORT Service in accordance with some aspects.

DETAILED DESCRIPTION

[0012] 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.

[0013] FIG. 1 A illustrates an architecture of a network in accordance with some aspects. The network 140A includes 3GPP 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.

[0014] The network 140A is shown to include user equipment (LIE) 101 and L^TE 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.

[0015] Any of the radio links described herein (e.g., as used in the network 140A 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.

[0016] In some aspects, any of the UEs 101 and 102 can comprise an Internet-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 device-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. [0017] 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.

[0018] 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.

[0019] 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 Discover}' Channel (PSDCH), a Physical Sidelink Broadcast Channel (PSBCH), and a Physical Sidelink Feedback Channel (PSFCH).

[0020] 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). [0021] 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/recepti on 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 pow'er (LP) RAN node 112. [0022] 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.

[0023] 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, aNextGen 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 Sl-mobility management entity (MME) interface 115, winch is a signaling interface between the RAN nodes 1 1 1 and 112 and MMEs 121.

[0024] 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. [0025] The S-GW 122 may terminate the SI interface 113 towards the

RAN 110, and routes data packets between the ILAN 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.

[0026] 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. [0027] 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. [0028] 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 (5G NR) and the unlicensed (5G NR-U) spectrum. One of the current enablers of loT is the narrow'band-loT (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 si delink V2X communications.

[0029] 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 LJPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.

[0030] 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.

[0031] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, FIG. IB illustrates a 5G system architecture 140B 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.

[0032] 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.

[0033] 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 profdes and data (similar to an HSS in a 4G communication system).

[0034] 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. [0035] 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.

[0036] 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.

[0037] 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 1 10 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 SAIF 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.

[0038] 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.

[0039] In some aspects, as illustrated in FIG. I C, sendee-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 sendee-based interface exhibited by the AMF 132), Nsmf 1581 (a sendee-based interface exhibited by the SMF 136), Nnef 158B (a sendee-based interface exhibited by the NEF 154), Npcf 158D (a sendee-based interface exhibited by the PCF 148), a Nudm 158E (a sendeebased interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a sendee-based interface exhibited by the NRF 156), Nnssf 158A (a sendee-based interface exhibited by the NSSF 142), Nausf 158G (a sendee-based interface exhibited by the AUSF 144). Other sendee-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1C can also be used. [0040] 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.

[0041 ] 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. 1A-IC. 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.

[0042] 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.

[0043] 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.

[0044] 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 (UI) 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.).

[0045] 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.

[0046] The term “machine readable medium” may include any medium that is capable of storing, encoding, or carryring 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 carrying 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. [0047] 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.

[0048] 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 (PED), a complex PIED (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 carry 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.

[0049] 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.

[0050] 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), 3GPP Long Term Evolution (LTE), 3GPP 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), 3 GPP Rel. 17 (3rd Generation Partnership Project Release 17) and subsequent Releases (such as Rel. 18, Rel.

19, etc.), 3GPP 5G, 5G, 5G New Radio (5G NR), 3GPP 5G New 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 (1 st Generation) (AMPS (IG)), 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

Mobil telefoni system 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 (PUS), Wideband Integrated Digital Enhanced Network (WIDEN), iBurst, Unlicensed Mobile Access (UM A), 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. Had, 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 Ip 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.

[0051] 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 io 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.

[0052] 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.

[0053] 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.

[0054] 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 fifth generation (5G) 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.

[0055] 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 A l interface, the Ol 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. 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 Ol 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 Ol interface towards the SMO 302.

[0056] 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.

[0057] 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. [0058] The radio portion/side of the logical architecture 400 includes the near-RT RIC 414, the O-RAN Distributed Unit (O-DU) 415, the O-RU 416, the O-CU-CP 421 , and the O-CU-UP 422 functions. The radio portion/side of the logical architecture 400 may also include the O-e/gNB 410.

[0059] The O-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 O-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 PDCP protocol. The O O-CU-UP 422 is a logical node hosting the userplane part, of the PDCP protocol and the Service Data Adaptation Protocol (SDAP) protocol. [0060] 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).

[0061] FIG. 4 shows the Uu interface between a UE 401 and O-e/gNB 410 as well as between the UE 401 and 0-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 di scussed 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 O-RU 416 functions with an Open Fronthaul (OF) interface between them.

[0062] The OF interface(s) is/are between O-DU 415 and O-RU 416 functions. The OF interface(s) includes the Control User Synchronization (CUS) Plane and Management (M) Plane. FIG. 3 and FIG. 4 also show⁷ that the O-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. [0063] 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 F l-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 3 GPP and the definition of interoperability profile specifications.

[0064] The Fl-u interface connects the O-CU-UP 422 with the O-DU 415. As defined by 3GPP, the FI-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.

[0065] 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.

[0066] The X2-c interface is defined in 3GPP for transmitting control plane information between eNBs or between eNB and en-gNB in EN-DC. The X2-u interface is defined in 3GPP 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 3 GPP are reused and may be adapted for O- RAN purposes. [0067] 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 transmiting user plane information between gNBs, ng-eNBs, or between ng-eNB and gNB. In 0-RAN, Xn-c and Xn-u protocol stacks defined by 3GPP are reused and may be adapted for O- RAN purposes.

[0068] The El interface is defined by 3GPP as being an interface between the gNB-CU-CP (e.g., gNB-CU-CP) and gNB-CU-UP. In 0-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. [0069] The O-RAN Non-Real Time (RT) RAN Intelligent Controller

(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.

[0070] In some embodiments, the Non-RT RIC 412 is a function that sits within the SMO platform (or SMO framework) 402 in the O-RAN architecture.

The primary goal of non-RT RIC is to support intelligent radio resource management for a non-real-time interval (i.e. , greater than 300 ms), policy optimization in RAN, and insertion of AIZML models to near-RT RIC and other RAN functions. The non-RT RIC terminates the Al interface to the near-RT RIC. It will also collect 0AM data over the 01 interface from the 0-RAN nodes. [0071] The 0-RAN near-RT RIC 414 is a logical function that enables near-real-time control and optimization of RAN elements and resources via finegrained 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. [0072] The non-RT RIC 412 can be an ML training host to host the training of one or more AIL models. ML training can be performed offline using data collected from the RIC, 0-DU 415, and O-R.U 416. For supervised learning, non-RT RIC 412 is part of the SMO 402, and the AIL 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 AIL 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.

AIL models may be trained and not currently deployed.

[0073] In some implementations, the non-RT RIC 412 provides a queryable 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 AIL model can be executed in a target AIL inference host (MF), and what number and type of AIL 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 AIL model inference in support of AIL assisted solutions running in the non-RT RIC 412 or some other AIL 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.

[0074] The non-RT RIC 412 can access feedback data (e.g., 1 X1 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 MI, 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 Kubernetes® (K8s) runtime environment typically provides an auto-scaling feature.

[0075] 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 Sendee, 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. [0076] O-RAN has been striving to embrace Al and ML based intelligence into wireless communication networks. Introducing AI/ML not only increases performance of existing networks, but also optimizes/ steers various network components to a certain key performance indicator (KPI) of interest. Currently, feeding accurate and timely measurement information in a RAN to the intelligence controller is a first step to succeed in those optimizations. E2 Service Model KPM (E2SM-KPM) supports open centralized unit control plane (O-CU-CP), open centralized unit user plane (O-CU-UP), and open centralized unit distributed unit (O-DU) as part of NG-RAN connected to 5GC or as part of E-UTRAN connected to EPC .

[0077] With respect to Near-RT RIC, it is expected that amount of those measurement information requested from RAN nodes will be immense (e.g,, UE-level, cell-level, etc.). Most of the measurements are incorporated into E2SM-KPM which has been specified to exposure O-DU’s cell-related, O-CU- CP’s UE-related, and O-CU-UP’ s bearer-related performance measurements of

UEs and RAN nodes to Near-RT RIC over E2 interface. FIG. 5 illustrates a RIC Near-RT RIC REPORI' Sendee in accordance with some aspects. Periodic reporting of measurements is to be provided to those network elements that are subscribed from the Near-RT RIC. [0078] For the REPORT sendee, at operation 1 the Near-RT RIC configures a RIC Subscription in the E2 Node with information for an Indication (Report) that is to be sent by the E2 Node with each occurrence of the RIC trigger event condition. During normal functioning of an associated procedure in the E2 Node, an RIC Event Trigger is detected at operation 2. At operation 3, the E2 Node sends an RIC INDICATION message to the Near-RT RIC containing the requested REPORT information along with the originating Request ID. At operation 4, the associated procedure instance continues in the E2 Node. The Near-RT RIC is then able to control the E2 Node (or other nodes) based on the measurements through a RIC CONTROL REQUEST message. [0079] Considering massive new measurement information into E2SM-

KPM, a unified but flexible and extendable measurement information container structure is desirable. The embodiments include: [0080] Hierarchical structure: a nested list of lists is the current baseline structure for measurement information container in E2 Service Model (E2SM)-KPM vOl.OO.

[0081] Labeling approach: structured by list of measurements each accompanied by a corresponding label that contains values of categories that this measurement is applicable to.

[0082] Hybrid of hierarchical + labeling approach: structured by a few nested lists of categories whose item each is realized by the above labeling structure, seeking middle ground between Embodiments 1 and 2. [0083] An improved labeling approach: on top of labeling approach, a simple indication may be added to indicate that a precedent label definition can be overwritten.

[0084] Embodiment 1 : Hierarchical structure

[0085] For example, 8.3,21a O-DU Performance Measurement Container for 5GC is structured as follows:

List of cells

> per cell measurement 1 .. > List of PLMNs

> per PLMN measurement 2..

> List of Slices

> per slice measurement 3 > ..

> List of 5 Qis

> per 5QI measurement 4 [0086] The O-DU Performance Measurement Container may have a relatively efficiently sized data structure, which may become increasingly complex with an increasing number of parameters and may not be forward compatible if a different hierarchy is used in the future. [0087] Embodiment 2: Labeling approach

[0088] The measurement information container from RAN nodes can be structured by list of measurements each accompanied by a corresponding label that contains values of categories to which this measurement is applicable. The example structure can be as follows: List of measurements + corresponding labels

> a measurement value

» E.e. by choice of measurement 1 or measurement 2 or measurement 3, etc..

> a corresponding label (contains values of categories)

» which cell, which PLMN, which slice, which 5QI, which QCI, which interface, etc., (as Optional)

[0089] The labeling approach may be forward compatible as a label definition can be easily extendable and universally used, has a simple container structure, and optionality allows only an absolutely necessary category/value to be included. This is at a cost of being relatively inefficient in size as the same label is repeatedly included if measurements share the same categories or values as well as being a complete makeshift of existing E2SM-KPM vOl .00 structures.

[0090] Embodiment 3: Hybrid of hierarchical + labeling

[0091] The measurement information container from RAN nodes can be structured by a few nested lists of categories whose item each is realized by labeling structure. An example structure can be as follows:

List of cells (if per cell is the baseline for all the measurements)

> per cell measurement 1..

> List of measurements + corresponding labels

> a measurement value

> a corresponding label (which PLMN, which slice, which 5QI, which QCI, etc. as Optional)

List of PLMNs (if per PLMN is the baseline for all the measurements)

> per PLMN measurement 1..

> List of measurement + corresponding labels

> a measurement value

> a corresponding label (which cell, which slice, which 5QI, which QCI, etc. as Optional)

[0092] This approach is a between Embodiment 1 and Embodiment 2.

[0093] Embodiment 4: An improved labeling approach

[0094] In order to mitigate one concern of the labeling approach (i.e., the same label may be repeatedly included if measurements share the same categories or values), a simple indication of overriding precedent label is optionally added to the labeling definition. An example structure can be as follows:

List of measurements + corresponding labels

> a measurement value

» E.g. by choice of measurement 1 or measurement 2 or measurement 3, etc..

> a corresponding label

» which cell, which PLMN, etc., (as optional) + (optional) indication of overriding precedent label

[0095] For example, in such a list of measurements + corresponding labels,

- Item 1

> a measurement value

> Cell - 1, PLMN == 1 , Slice == 1, 5QI - 1

- Item 2

> a measurement value

> 5QI ^:::: 3, override ^:::: on Cell ^:::: 1, PLMN ^::: 1, Slice ^::: 1,

5QI = 3

- Item 3

> a measurement value

> PLMN = 2, override = on Cell = 1, PLMN = 2, Slice = I,

5QI === 3

[0096] The RIC SUBSCRIPTION REQUEST is sent by the Near-R T

RIC to an E2 Node to create a new Subscription in the E2 Node.

The RIC Action Definition is an information element that provides parameters to be used when executed the REPORT sendee.

[0098] The E2AP procedures, E2 SETUP and RIC SERVICE UPDATE, are used to transport the RAN Function Definition IE. In this E2SM -K PVL the RAN Function Definition IE provides: the RAN Function name along with associated information on E2SM definition, event trigger styles list along with the corresponding encoding type for each associated E2AP IE, and RIC

REPORT Service styles list along with the corresponding encoding type for each associated E2AP IE.

[0099] The supported RIC Event Trigger Styles includes a periodic report and has an Event Trigger Style to set the KPM report period and use the RIC Event Trigger Definition IE Format 1. [00100] The supported RIC REPORT Service Styles include a REPORT Service Style 1 : E2 Node Measurement that provides the performance measurement information collection from an E2 Node, The REPORT Service RIC Action Definition IE contents aims to subscribe to the E2 Node measurements and uses the RIC Action Definition IE Format described below.

The REPORT Sendee RIC Action Definition IE contains measurement types that, the Near-RT RIC is requesting to subscribe to followed by a list of categories or subcounters to be measured for each measurement type, and a granularity period indicating collection interval of those measurements. The IE may also contain a cell identifier to point to a specific cell for collecting measurements within the E2 Node. The container contents include a set of measurement data reported from an E2 Node. The reported data contains a set of measurement records, each collected at even⁷ granularity period during the reporting period (or if unable to provide reliable data for a granularity period during the reporting period, an Incomplete Flag IE).

[00101] The messages for RIC Functional procedures include an RIC EVENT TRIGGER DEFINITION IE that is part of the RIC SUBSCRIPTION REQUEST message sent by the Near-RT RIC to an E2 Node and is used for event triggers used to initiate REPORT actions.

[00102] The E2SM-KPM Event Trigger Definition Format I is:

[00103] The RIC ACTION DEFINITION IE is part of the RIC SUBSCRIPTION REQUEST message sent by the Near-RT RIC to the E2 Node.

[00104] The E2SM-KPM Action Definition Format 1 is:

[00105] The measurement Type ID defines the identifier of a given measurement type.

[00106] The measurement label defines values of subcounters applicable to an associated measurement type in accordance with Embodiment 2 and

Embodiment 4.

[00107] The use cases of the measurement include traffic steering and QoS based resource optimizations.

[00108] In traffic steering, the Near-RT RIC Traffic Steering is to interpret the policies received over Al and to determine the optimum changes to make towards achieving those goals. More specifically, the Near-RT RIC triggers an E2 procedure and related control/policies so as to obtain network performance that would fulfill the criteria identified in the Al policies. The process starts when the Non-RT RIC and/or Near-RT RIC perform data evaluation, determine that TS-aware optimization is to be initiated or updated and establishes target/ s). The Non-RT RIC evaluates the collected data and Al policy feedback and generates or updates the appropriate TS-aware resource optimization policy, such as TS targets, and sends the policy to Near-RT RIC via the Al interface. The Non-RT RIC sends optional traffic steering related Al Enrichment Information. Based on received Al policy and/or Al -El from the Non-RT RIC or internal trigger and/or internal evaluation and trigger, the Near- RT RIC sets up or updates the TS-aware resource optimization procedure. The Near-RT RIC subscribes to a UE context information and measurement metrics via E2 interface. The E2 Nodes report the UE context information and E2 measurements via RIC REPORT periodically or event-triggered. The Near-RT RIC evaluates the performance data from E2 Nodes (including performance data from different E2 Nodes for the same UE) and finds the performance is out of TS targets which are indicated in the Al policy and/or internal near-RT RIC TS targets. Based on the UE context information, E2 measurement metrics (RIC REPORT), and A l policy, Near-RT RIC may generate new or modify the existing E2 policies and sends them to E2 Nodes. Near-RT RIC may also generate control command(s) and send them to E2 Node(s) to trigger re- allocation of radio resources so that TS indicators can move back to the limits outlined in the Al policies. E2 node functions target of E2 policy and control commands may be: E-UTRAN-NR Dual Connectivity, Carrier Aggregation, Connected mode mobility. Idle Mode Mobility. This may be repeated. The Near-RT RIC sends information to the SMO domain using Al policy feedback and/or Ol-PM. The Non-RT RIC may use this information and information collected from E2 Nodes using Ol-PM as policy feedback to assess the performance of TS optimization function in the Near-RT RIC, or to assess the outcome of the applied Al policies. Subsequently, an Al policy can be updated. In parallel, the Near-RT RIC may use available information to assess the performance of TS optimization function in the Near-RT RIC, and/or to assess the outcome of the applied A l policies. Subsequently the Near-RT RIC TS optimization targets can be updated. These may be repeated. The Non-RT RIC then decides to delete TS-aware resource optimization policy and sends the related message or following internal trigger, the Near-RT RIC terminates the TS-aware resource optimization procedure.

[00109] The followings are examples of UE context information identified: UE ID; Slice level: S-NSSAI; DRB level: e.g., established DRB ID, mapping with QoS flows, etc.; QoS related: e.g., E-RAB Level QoS Parameters (4G, NSA) or QoS Flow Level QoS Parameters (NG-RAN ); and UE capabilities: CA and DC capabilities. For example, UE ID, S-NSSAI, DRB ID, or QCI/5QI can be used to derive the QoS requirements and the resource occupation; the UE capabilities may be used to select the appropriate RRM action (e.g. CA/DC configuration).

[00110] The E2 measurements are used for inference and prediction in the Near-RT RIC as the driver for decisions in addition to KPMs. For the Traffic Steering use case, the Near-RT RIC can translate an Al policy (relatively static targets) into a flexible selection of controls over E2 (e.g. handover control, DC, CA, idle mode mobility) by taking into account the RAN resource utilization, cell level and the UE level performance, the radio conditions, etc.

[001 I I] Cell level configuration parameters, such as PCI, neighbor relations and related offsets etc. are used at Near-RT RIC in order to e.g. configure UE measurements monitor cell level performance and manage mobility control (handover and cell reselection) according to the network topology’ and the related E2 parameters.

[00112] QoS Based Resource Optimization permits the network to prioritize resources while presenting the required QoS properties, e.g. reliability, latency, bandwidth requirements, as specified in 3GPP TS 23.203. The QoS aware resource optimization should provide a refined granularity of radio resource allocation based on varying radio conditions and traffics to meet the diverse requirements of reliability, latency, and bandwtidth simultaneously. In addition, it should coordinate allocation of radio resources for co-existing multiple services, which may have different priorities, to achieve the optimal utilization of radio resources.

[00113] The QoS Based Resource Optimization has an outer loop and inner loop. The outer loop starts when the Non-RT RIC evaluates the collected data and Al policy feedback and generates or updates the appropriate QoS- aware resource optimization policy, such as QoS targets, and sends it to Near-RT RIC via Al interface. When the Near-RT RIC receives an Al policy from Non- RT RIC, the Near-RT RIC initiates the corresponding optimization procedure. The inner loop starts when the Near-RT RIC subscribes to a UE context information and measurement metrics via the E2 interface. The E2 Nodes report the UE context information and E2 measurements via RIC REPORT periodically or event-triggered. The Near-RT RIC evaluates the performance data from E2 Nodes (including performance data from different E2 Nodes for the same UE) and finds the performance is out of QoS targets which are indicated in the Al policy. If performance is within the targets, the Near-RT RIC keeps monitoring. Based on the UE context information, E2 measurement metrics (RIC REPORT), and Al policy, the Near-RT RIC may generate new or modify the existing E2 policies and sends them to the E2 Nodes. The Near-RT RIC may also generate control command(s) and send them to E2 Node(s) to trigger re-allocation of radio resources so that QoS indicators can move back to the limits outlined in the Al policies. The inner loop ends and may be repeated. If required, the Near-RT RIC sends a policy feedback to the Non-RT RIC to assess the performance of QoS optimization function in the Near-RT RIC, or to assess the outcome of the applied Al policies. Subsequently, an Al policy can be updated. The outer loop ends and may be repeated.

[00114] DRB Control: RB control can be applied for modification of the following QoS properties: DRB QoS modification: The DRB level QoS may be tuned to accommodate Al policy requirement; QoS flow remapping: The mapping relationship between QoS flows and DRBs may be adjusted; Logical channel reconfiguration: The relevant parameters can be considered, e.g., priority, prioritized bit rate, bucket size duration, etc.; Radio Admission Control: DRB admission control such as reject or release may be applied; Modification of dual -connectivity DRB (TS 37.340): change of bearer termination point (MN or SN) and/or bearer types (MCG/SCG/ split), and control of split ratio for a split bearer; and Activation and deactivation of packet duplication and configuration of the number of legs in DC, CA, or DC+CA scenarios (TS 36.300, TS 38.300). RIC CONTROL (e.g. request for QoS flow remapping) or RIC POLICY (e.g. DRB admission policy) can be applicable. [00115] Radio Resource Allocation, such as configuration of DRX, semi -persistent scheduling (SPS), or guidance for the scheduling and rate selection in MAC, For example, based on prediction, an E2 policy or control to reconfigure SPS configuration or ConfiguredGraniCctnfig for UL may be generated. DRX: Long DRX cycle length, Short DRX cycle length as well as short DRX cycle timer can be considered; SR periodicity reconfiguration (TS 38.331, TS 36.331): Both sr~Prohibit Timer and sr-TransMax. can be treated; SPS configuration (TS 38.331, TS 36.331): Both SPS-Config (DL.) and

ConfiguredGrantConfig (UL) can be treated; Reconfiguration of slice level PRB quota (TS 28.541); Configuration of CQI table with certain target block error rate (TS 38.214). Both RIC POLICY and RIC CONTROL can be used. For example, SPS can be configured via RIC CONTROL; RIC POLICY can be used, e.g. to set the guidance for the scheduler.

[00116] Radio Access Control: Depending on operator's policies, deployment scenarios, subscriber profiles, and available services, different criterion will be used in determining which access attempt should be allowed or blocked when congestion occurs in the system, as specified in 3GPP TS 22.261. For example, access control may be applied to restrict access of other UEs for a specific cell to achieve better QoS for some UEs. A cell-level, UE-level, or slicelevel access control can be applied. Four categories of radio access control are indicated as below: RACH Backoff; RRC Connection Reject; RRC Connection Release; and Access Barring. Both RIC POLICY and RIC CONTROL can be used.

[00117] Connection Mobility Control: For example, a neighbouring cell may be selected for the optimization of QoS of a specific UE. A neighbour blacklist (e.g. handover restriction list) may be configured to prevent the UEs from HO to some neighbouring cells in order to guarantee QoS of the UEs served by those neighbouring cells. Or, a capacity boosting mechanism may be used to achieve better QoS, e.g. enable CA/DC. Handover from the source cell to the target cell; Configuration/reconfiguration of handover restriction list, Enable, disable, or modify CA (TS 38.473, TS 38.331, TS 36.331); Enable, disable, or modify dual connectivity (TS 38.473, TS 38.331, TS 36.331). Both RIC POLICY and RIC CONTROL can be used.

[00118] The followings are examples of UE context information: UE ID; Slice level: S-NSSAI; DRB level: e.g., established DRB ID, mapping with QoS flows, etc.; QoS related: e.g., E-RAB Level QoS Parameters (4G, NSA) or QoS Flow Level QoS Parameters (NG-RAN); UE capabilities: CA and DC capabilities; RLC/MAC/PHY level: e.g., logical channel, DRX, scheduling request, SPS configurations. For example, UE ID, S-NSSAI, DRB ID, or QCI/5QI can be used for different granularity of controls over E2; an established DRB level information may be needed to change the mapping of QoS flows to a specific DRB or modify DRB attributes; the UE capabilities may be required to make sure if CA/DC can be enabled.

[00119] The E2 measurements are used for inference and prediction in the Near-RT RIC as the driver for decisions in addition to KPMs. For the QoS based resource optimization use case, the Near-RT RIC can translate an Al policy (relatively static targets) into a flexible selection of controls over E2 (e.g. RB control, handover, access control) by taking into account the runtime status in the Near-RT RIC. Therefore, it is desired to specify those measurement parameters as possible as needed over E2 interface.

[00120] 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.

[00121] 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.

[00122] 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.

[00123] 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 near real-time (RT) radio access network intelligence controller (RIC) in an open radio access network (O-RAN), the apparatus comprising: processing circuitry configured to: encode, for transmission to an E2 Node, a RIC Subscription, the RIC Subscription comprising a request that, the E2 Node send a report message to the Near-RT RIC, the RIC Subscription comprising a structured list of measurements and, for each measurement, a corresponding label that contains values of categories to which the measurement is applicable; decode, at the RIC, the report message from the E2 Node in response to the RIC Subscription, the report message comprising the measurements; and adjust, based on the measurements, network components to improve at least one key performance indicator (KPI); and a memory configured to store the measurements.

2. The apparatus of claim 1, wherein the report message comprises another list of measurements that comprise the measurement accompanied by another corresponding label.

3. The apparatus of claim 1 or 2, wherein the RIC Subscription comprises an information element indicating an action of the RIC Subscription, the action comprising reporting of the measurements,

4. The apparatus of any one or more of claims 1-3, wherein the RIC Subscription comprises an information element that contains a period for periodic reporting of the measurements by the E2 Node.

5. The apparatus of any one or more of claims 1-4, wherein the categories comprise: a public land mobile network (PLMN) identifier (ID), a network slice ID, 5G quality of service (QoS) ID, QoS Flow ID (QFI), and QoS Class Identifier (QCI).

6. The apparatus of claim 5, wherein the categories further comprise at least one of: a sum of the measurement from a start of the measurement during a period, a minimum, maximum and average of the measurement during the period, or a distribution of the measurement.

7. The apparatus of any one or more of claims 1-6, wherein the categories comprise an indication to override a category of a precedent label.

8. The apparatus of claim 7, wherein the precedent label is an immediately precedent label.

9. The apparatus of claim 8, wherein for a current label that contains the indication to override the category' of the immediately precedent label, categories of the current label are limited to categories of the immediately precedent label being overridden.

10. The apparatus of any one or more of claims 1-9, wherein adjustment of the network components comprises providing the measurements to a Non-RT RIC for at least one of traffic steering and a quality of service (QoS)-based resource optimization.

11 , An apparatus for an E2 node in an open radio access network (O-RAN), the apparatus comprising: processing circuitry configured to: decode, from a near real-time (RT) RAN intelligence controller (RIC), a RIC message; determine that the RIC message is an RIC Subscription to request that the E2 Node send a report message to the Near-RT RIC, the RIC Subscription comprising a structured list of measurements and, for each measurement, a corresponding label that contains values of categories to which the measurement is applicable; measure, for each label, the categories indicated by the label to obtain the measurements; and encode, for transmission to the RIC, the measurements in the report message; and a memory configured to store the measurements.

12, The apparatus of claim 1 1, wherein the RIC Subscription compri ses an information element indicating an action of the RIC Subscription, the action comprising reporting of the measurements.

13. The apparatus of claim 11 or 12, wherein the RIC Subscription comprises an information element that contains a period for periodic reporting of the measurements by the E2 Node.

14. The apparatus of any one or more of claims 11-13, wherein the categories comprise an indication to override a category of a precedent label.

15. The apparatus of claim 14, wherein the precedent label is an immediately precedent label.

16. The apparatus of claim 15, wherein for a current label that contains the indication to override the category of the immediately precedent label, categories of the current label are limited to categories of the immediately precedent label being overridden.

17. A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of a near real-time (RT) radio access network intelligence controller (RIC) in an open radio access network (0-RAN), the one or more processors to configure the near-RT RIC to, when the instructions are executed: encode, for transmission to an E2 Node, a RIC Subscription, the RIC Subscription to request that the E2 Node send a report message to the Near-RT RIC, the RIC Subscription comprising a structured list of measurements and, for each measurement, a corresponding label that contains values of categories to which the measurement is applicable; decode, at the RIC, the report message from the E2 Node in response to the RIC Subscription; and adjust, based on the measurements, network components to improve at least one key performance indicator (KPI).

18. The medium of claim 17, wherein the RIC Subscription comprises: an information element indicating an action of the RIC Subscription, the action comprises reporting of the measurements, and an information element that contains a period for periodic reporting of the measurements by the E2 Node.

19. The medium of claim 17 or 18, wherein the categories comprise an indication to override a category' of an immediately precedent label.

20. The medium of claim 19, wherein for a current label that contains the indication to override the category of the immediately precedent label, categories of the current label are limited to categories of the immediately precedent label being overridden.