User equipment (UE) identifier in open radio access network (o-RAN)

Abstract

Certain aspects of the present disclosure provide a method at a first node. A first node sends a request to a second node to assign persistent identifiers for a first plurality of user equipments (UEs) of one or more groups of UEs. The first node receives, from the second node, an indication of a first persistent identifier for the first plurality of UEs. The first persistent identifier is persistent across a plurality of radio resource control (RRC) states corresponding to at least one UE of the first plurality of UEs.

Description

Background Technology

[0001] Cross-references to related applications

[0002] This application claims the benefit and priority of Greek Patent Application No. 20230100703, filed on August 30, 2023, and Greek Patent Application No. 20230101075, filed on December 22, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] Various aspects of this disclosure relate to wireless communications, and more specifically, to techniques for allocating User Equipment (UE) identifiers in an Open Radio Access Network (O-RAN).

[0004] Related technical descriptions

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, broadcasting, or other similar services. These wireless communication systems may employ multiple access technologies that enable communication with several users by sharing available wireless communication system resources.

[0006] Despite significant technological advancements in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and receivers. Therefore, there is a continuous expectation for improving the technical performance of wireless communication systems, including, for example: improving communication speed and data carrying capacity; improving the efficiency of shared communication media; reducing the power used by transmitters and receivers during communication; improving the reliability of wireless communication; avoiding redundant transmission and / or reception and related processing; improving the coverage area of ​​wireless communication; increasing the number and types of devices that can access the wireless communication system; increasing the ability of different types of devices to communicate with each other; and increasing the number and types of available wireless communication media. Therefore, there is a need for further improvements to wireless communication systems to overcome the aforementioned technical challenges and other obstacles. Summary of the Invention

[0007] One aspect provides a method at a first node, the method comprising: sending a request to a second node to assign a persistent identifier for a user equipment (UE); and receiving an indication from the second node of a first persistent identifier for the UE, wherein the first persistent identifier is based on a first identifier of the UE, and wherein the first persistent identifier is persistent across multiple radio resource control (RRC) states corresponding to the UE.

[0008] On the other hand, a method is provided at a first node, the method comprising: receiving a request from a second node to allocate a persistent identifier for a UE; and sending an indication to the second node of a first persistent identifier for the UE, wherein the first persistent identifier is based on a first identifier of the UE, and wherein the first persistent identifier is persistent across multiple RRC states corresponding to the UE.

[0009] On the other hand, a method is provided at a near real-time (RT) radio access network (RAN) intelligent controller (RIC), the method comprising: sending a subscription message to a network entity to receive UE data, the UE data including one or more tunnel endpoint (TE) identifiers associated with the UE; and in response to the subscription message, receiving from the network entity at least one first TE identifier associated with a first identifier of the UE.

[0010] On the other hand, a method is provided at a non-RT RIC, the method comprising: receiving one or more persistent identifiers associated with the UE from a core network node; and sending one or more persistent identifiers to a near RT RIC, wherein the one or more persistent identifiers are based on one or more permanent identifiers.

[0011] On the other hand, a method is provided at a first node, the method comprising: sending a request to a second node to assign a persistent identifier to a first plurality of UEs in one or more groups of UEs; and receiving from the second node an indication of a first persistent identifier for the first plurality of UEs, wherein the first persistent identifier is persistent or applicable across multiple RRC states corresponding to all UEs in the first plurality of UEs.

[0012] On the other hand, a method is provided at the Access and Mobility Management Function (AMF) of a core network node, the method comprising: receiving a request from a server associated with a Next Generation (NG) RAN to store an identifier of one or more UEs or at least one of UEs, wherein the identifier is assigned at the server associated with the NG-RAN; and storing the identifier in a database associated with the AMF of the core network node upon request.

[0013] On the other hand, a method is provided at a first node, the method comprising: sending a request to a second node to assign a persistent identifier to one or more UEs; and receiving from the second node an indication of a first persistent identifier for one or more UEs, wherein the first persistent identifier is persistent or applicable across multiple RRC states corresponding to one or more UEs.

[0014] Other aspects provide: an apparatus capable of operating to, being configured to, or otherwise adapted to perform the foregoing methods and those methods described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the foregoing methods and those methods described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising: code for performing the foregoing methods and those methods described elsewhere herein; and an apparatus comprising components for performing the foregoing methods and those methods described elsewhere herein. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating via one or more networks.

[0015] For illustrative purposes, the following description and figures illustrate certain features. Attached Figure Description

[0016] The accompanying drawings depict certain features of the various aspects described herein and should not be considered as limiting the scope of this disclosure.

[0017] Figure 1 An example wireless communication network is depicted.

[0018] Figure 2 An example decomposed base station (BS) architecture is described.

[0019] Figure 3 Various aspects of the sample BS and sample user equipment (UE) are described.

[0020] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures used in wireless communication networks are described.

[0021] Figure 5 Another example of a decomposed BS architecture is described.

[0022] Figure 6A Example components of a decomposed BS architecture are described.

[0023] Figure 6B A call flow diagram illustrating example communication between components in a decomposed BS architecture is provided.

[0024] Figure 7A An example component of another decomposed BS architecture is described.

[0025] Figure 7B and Figure 7CA call flow diagram illustrating example communication between components in a decomposed BS architecture is provided.

[0026] Figure 8 A call flow diagram illustrating example communication between the UE, gNodeB (gNB), Access and Mobility Management Function (AMF), and Session Management Function (SMF) / User Plane Function (UPF) is depicted.

[0027] Figure 9 A call flow diagram illustrating example communication between a UE, a gNB, and a near real-time (RT) radio access network (RAN) intelligent controller (RIC) is depicted.

[0028] Figure 10A An example component of another decomposed BS architecture is described.

[0029] Figure 10B A call flow diagram illustrating example communication between components in a decomposed BS architecture is provided.

[0030] Figure 11 and Figure 12 The method at the first node is described.

[0031] Figure 13 The method at near RT RIC is described.

[0032] Figure 14 The method at non-RT RIC is described.

[0033] Figure 15 An example communication device is described. Detailed Implementation

[0034] Open Radio Access Network (O-RAN) typically refers to a non-proprietary version of a radio access network (RAN) system that allows interoperability between cellular network equipment from different vendors. O-RAN is implemented using a decomposed base station (BS) architecture.

[0035] A decomposed BS architecture may include one or more central units (CUs) that can communicate directly with the core network. This communication with the core network may occur via a backhaul link or indirectly through one or more decomposed BS units, such as a near-real-time (near-RT) Radio Access Network (RAN) Intelligent Controller (RIC) via an E2 link, or a non-real-time (non-RT) RIC associated with a Service Management and Orchestration (SMO) framework, or both. A CU may communicate with one or more distributed units (DUs) via a corresponding midhaul link (such as an F1 interface). A DU may communicate with one or more radio units (RUs) via a corresponding fronthaul link. An RU may communicate with user equipment (UE) via one or more radio frequency (RF) access links. Each of these units (e.g., CUs, DUs, RUs, and near-RT RICs, non-RT RICs, and SMO frameworks) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media.

[0036] O-RAN can be used in several use cases that require a UE identifier to identify a specific UE. For example, some use cases aimed at optimizing UE services may require using some type of UE identifier to identify the UE. These use cases may include, for example, training an artificial intelligence / machine learning (AI / ML) system to generate AI / ML-based optimizations.

[0037] O-RAN may include some interfaces with the RAN (such as the E2 interface and the O1 interface). Therefore, the UE identifier available at the RAN is visible to the O-RAN. Unfortunately, the UE identifier in the RAN has a short validity period and is only applicable while the UE remains in the Radio Resource Control (RRC) connected state. For example, when the UE transitions from the RRC connected state to the RRC idle state, the UE identifier becomes invalid, and the UE subsequently becomes unrecognizable in the RAN. This limitation associated with the UE identifier in the RAN also applies to the O-RAN, as the O-RAN receives data from the RAN. Therefore, currently, the RAN / O-RAN does not have any UE identifiers for identifying the UE across different RRC state transitions.

[0038] Because some use cases require identifying and associating different UE measurements performed by the UE in RRC connected and RRC idle states, a UE identifier (e.g., a persistent UE identifier) ​​may be needed. This UE identifier can be used to identify the UE (and its data) across RRC state transitions.

[0039] This disclosure provides apparatus, methods, processing systems, and computer-readable media for assigning UE identifiers to UEs in an O-RAN. For example, in an O-RAN, a RAN node may request the Access and Mobility Management Function (AMF) of a core network node to assign a persistent UE identifier to a UE (or a group of UEs), which can be used to identify the UE / group of UEs (and its data) across RRC state transitions. The AMF then assigns the persistent UE identifier to the UE / group of UEs and transmits it to the RAN node. In some cases, the persistent UE identifier (e.g., which remains unchanged across different RRC states) can be a unique long-term reference (e.g., which can be used to identify the UE / group of UEs).

[0040] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to improve AI / ML-based training and optimization of UEs in O-RAN systems, for example, by being able to collect and use different UE measurements performed by the UE in RRC connected and RRC idle states based on the UE's persistent UE identifier.

[0041] An introduction to wireless communication networks

[0042] The techniques and methods described herein can be used in a variety of wireless communication networks. While aspects may be described herein using terms commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of this disclosure are equally applicable to other communication systems and standards not explicitly mentioned herein.

[0043] Figure 1 An example of a wireless communication network 100 in which the aspects described herein can be implemented is depicted.

[0044] Generally, wireless communication network 100 includes various network entities (optionally, network elements or network nodes). Network entities are typically communication devices and / or communication functions performed by communication devices (e.g., user equipment (UE), base station (BS), components of the BS, servers, etc.). For example, various functions of the network and various devices associated with and interacting with the network can be considered network entities. Furthermore, wireless communication network 100 includes terrestrial and non-terrestrial aspects. The terrestrial aspect includes ground-based network entities (e.g., BS 102), and the non-terrestrial aspect includes satellite 140 and aircraft 145, which may include onboard network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and UEs.

[0045] In the depicted example, wireless communication network 100 includes BS 102, UE 104 and one or more core networks (such as Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190) that interoperate to provide communication services over various communication links, including wired and wireless links.

[0046] Figure 1 Various example UEs 104 are described, which may more generally include: cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players, cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, Internet of Things (IoT) devices, always-on (AON) devices, edge processing devices, or other similar devices. UE 104 may also be more generally referred to as mobile devices, wireless devices, wireless communication devices, stations, mobile stations, subscriber stations, mobile subscriber stations, mobile units, subscriber units, wireless units, remote units, remote devices, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, and others.

[0047] BS 102 communicates wirelessly with UE 104 via communication link 120 (e.g., transmitting or receiving signals to or from UE 104). Communication link 120 between BS 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to BS 102 and / or downlink (DL) (also known as forward link) transmission from BS 102 to UE 104. In various aspects, communication link 120 may utilize multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity.

[0048] BS 102 may typically include: NodeB, enhanced NodeB (eNB), next-generation enhanced NodeB (ng-eNB), next-generation NodeB (gNB or gNodeB), access point, transceiver base station, radio BS, radio transceiver, transceiver functionality, transmit / receive point, and / or others. Each BS in BS 102 may provide communication coverage for a corresponding geographic coverage area 110, which may sometimes be referred to as a cell, and in some cases may overlap (e.g., a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, a BS may provide communication coverage for macro cells (covering a relatively large geographic area), pico cells (covering a relatively small geographic area, such as a stadium), femtocells (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0049] Although BS 102 is described as a single communication device in various aspects, it can be implemented in various configurations. For example, one or more components of BS 102 can be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, to name a few. Also, various aspects of BS 102 can be virtualized. More generally, a BS (e.g., BS 102) can include components located in a single physical location or components located in various physical locations. In examples where BS 102 includes components located in various physical locations, each component can perform its own function, such that the various components collectively achieve functionality similar to BS 102 located in a single physical location. In some aspects, a BS 102 including components located in various physical locations can be referred to as a decomposed radio access network (RAN) architecture, such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture. Figure 2 An example decomposed BS architecture is depicted and described.

[0050] Different BSs 102 within the wireless communication network 100 can also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with 5GC 190 via a second backhaul link 184. BSs 102 can communicate directly or indirectly (e.g., via EPC 160 or 5GC 190) on a third backhaul link 134 (e.g., X2 interface), which can be wired or wireless.

[0051] Wireless communication network 100 can subdivide the electromagnetic spectrum into various categories, bands, channels, or other characteristics. In some aspects, subdivision is provided based on wavelength and frequency, where frequency may also be referred to as carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 600MHz-6GHz, which is often (interchangeably) referred to as “below 6GHz”. Similarly, 3GPP currently defines frequency range 2 (FR2) as including 26GHz-41GHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). A BS configured to communicate using mmWave / near mmWave radio frequency bands (e.g., mmWave BS, such as BS 180) can utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.

[0052] The communication link 120 between BS 102 and, for example, UE 104 can be via one or more carriers, which may have different bandwidths (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz and / or other MHz) and may be aggregated in various ways. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL).

[0053] Compared to lower-frequency communication, communication using higher frequency bands can have higher path loss and shorter range. Therefore, some BSs (e.g., Figure 1The beamforming 182 of the BS 180 and UE 104 can be used to improve path loss and range. For example, the BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 may transmit beamformed signals to the UE 104 in one or more transmit directions 182'. The UE 104 may receive beamformed signals from the BS 180 in one or more receive directions 182''. The UE 104 may also transmit beamformed signals to the BS 180 in one or more transmit directions 182''. The BS 180 may also receive beamformed signals from the UE 104 in one or more receive directions 182''. The BS 180 and UE 104 may then perform beamforming training to determine the optimal receive and transmit directions for each of the BS 180 and UE 104. It is worth noting that the transmit and receive directions of the BS 180 may be the same or different. Similarly, the sending and receiving directions of UE 104 can be the same or different.

[0054] The wireless communication network 100 further includes a Wi-Fi AP 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, unlicensed spectrum in 2.4 GHz and / or 5 GHz.

[0055] Some UEs 104 may use device-to-device (D2D) communication links 158 to communicate with each other. The D2D communication link 158 may use one or more sidelink channels, such as physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), and / or physical sidelink feedback channel (PSFCH).

[0056] EPC 160 may include various functional components, including: Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and / or Packet Data Network (PDN) Gateway 172, as in the illustrated example. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connectivity management.

[0057] Generally, user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP services 176, which may include, for example, the Internet, intranets, IP Multimedia Subsystem (IMS), packet-switched (PS) streaming services, and / or other IP services.

[0058] The BM-SC 170 provides functionality for MBMS user service dispatch and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, can be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and / or can be used to schedule MBMS transmissions. The MBMS gateway 168 can be used to distribute MBMS services to BS 102 belonging to a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and / or can be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0059] 5GC 190 may include various functional components, including: Access and Mobility Management Function (AMF) 192, other AMFs 193, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196.

[0060] AMF 192 is the control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides services such as Quality of Service (QoS) flow and session management.

[0061] Internet Protocol (IP) packets are transmitted via UPF 195, which connects to IP service 197 and provides the UE with IP address allocation and other functions for 5GC 190. IP service 197 may include, for example, the Internet, intranet, IMS, PS streaming service, and / or other IP services.

[0062] The wireless communication network 100 also includes an identifier (ID) component 198. The wireless communication network 100 further includes an ID component 199, which can be configured to perform... Figure 11 Method 1100 Figure 12 Method 1200 Figure 13 Method 1300 and / or Figure 14 Method 1400.

[0063] In various aspects, to give a few examples, network entities or network nodes can be implemented as aggregated BS, decomposed BS, components of BS, integrated access and backhaul (IAB) nodes, trunk nodes, and sidelink nodes.

[0064] Figure 2 An example decomposed BS 200 architecture is depicted. The decomposed BS 200 architecture may include one or more central units (CUs) 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed BS units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both. CUs 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links, such as F1 interfaces. DUs 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. RUs 240 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, UE 104 may be served simultaneously by multiple RUs 240.

[0065] Each of these units (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO frame 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of these units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally or alternatively, units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as radio frequency (RF) transceivers) configured to receive signals on wireless transmission media or transmit signals to one or more other units, or both.

[0066] In some aspects, the CU 210 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 210. The CU 210 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, the CU 210 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 210 can be implemented to communicate with the DU 230 for network control and signaling, as needed.

[0067] DU 230 may correspond to a logic unit that includes one or more BS functions for controlling the operation of one or more RU 240s. In some aspects, DU 230 may at least partially host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) according to functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0068] Lower-layer functionality can be implemented by one or more RU 240s. In some deployments, an RU240 controlled by a DU 230 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration enables the implementation of the DU 230 and CU 210 in cloud-based RAN architectures such as vRAN architectures.

[0069] SMO framework 205 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 205 can be configured to interact with cloud computing platforms such as Open Cloud (O-Cloud) 290 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some implementations, SMO framework 205 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some implementations, SMO framework 205 can communicate directly with one or more RU 240s via the O1 interface. SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of SMO framework 205.

[0070] The non-RT RIC 215 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near-RT RIC 225, such as via an A1 interface. The near-RT RIC 225 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as via an E2 interface, through data collection and actions, connecting one or more CU 210s, one or more DU 230s, or both, and O-eNBs to the near-RT RIC 225.

[0071] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 225 and may be received from non-network data sources or network functions at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 205 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0072] Figure 3 Various aspects of examples BS 102 and UE 104 are described.

[0073] Generally, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively referred to as 334), transceivers 332a-332t (collectively referred to as 332) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., data source 312) and the wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement the various functions described herein related to wireless communication.

[0074] BS 102 includes a controller / processor 340 that can be configured to implement various functions related to wireless communication. In the depicted example, the controller / processor 340 includes an ID component 341 that can represent Figure 1 ID component 199. It is worth noting that, although depicted as one aspect of controller / processor 340, in other specific implementations, ID component 341 may additionally or alternatively be implemented in various other aspects of BS 102.

[0075] Generally, UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively referred to as 352), transceivers 354a-354r (collectively referred to as 354) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., retrieved from data source 362) and the wireless reception of data (e.g., provided to data sink 360). UE 104 includes a controller / processor 380 that can be configured to implement the various functions described herein related to wireless communication.

[0076] UE 104 includes a controller / processor 380 that can be configured to implement various functions related to wireless communication. In the depicted example, the controller / processor 380 includes an ID component 381 that can represent Figure 1 The STC component 198. It is worth noting that, although depicted as one aspect of the controller / processor 380, in other specific implementations, the ID component 381 may additionally or alternatively be implemented in various other aspects of the UE 104.

[0077] Regarding example downlink transmission, BS 102 includes a transmission processor 320 that can receive data from data source 312 and control information from controller / processor 340. The control information may be for a Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical HARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Shared PDCCH (GC PDCCH), and / or others. In some examples, this data may be for a Physical Downlink Shared Channel (PDSCH).

[0078] The transmitter processor 320 can process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmitter processor 320 can also generate reference symbols (such as those for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS)).

[0079] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols where applicable, and can provide the output symbol stream to the modulators (MODs) in transceivers 332a-332t. Each modulator in transceivers 332a-332t can process its corresponding output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from the modulators in transceivers 332a-332t can be transmitted via antennas 334a-334t respectively.

[0080] To receive downlink transmissions, UE 104 includes antennas 352a-352r that receive downlink signals from BS 102 and provide the received signals to demodulators (DEMODs) in transceivers 354a-354r respectively. Each demodulator in transceivers 354a-354r can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator can further process the input sample to obtain the received symbols.

[0081] The MIMO detector 356 acquires received symbols from all demodulators in transceivers 354a-354r, performs MIMO detection on the received symbols where applicable, and provides the detected symbols. The receive processor 358 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide the decoded data for UE 104 to data sink 360, and provide the decoded control information to controller / processor 380.

[0082] Regarding example uplink transmission, UE 104 also includes a transmit processor 364 that receives and processes data from data source 362 (e.g., for PUSCH) and control information from controller / processor 380 (e.g., for Physical Uplink Control Channel (PUCCH)). Transmit processor 364 may also generate reference symbols for reference signals (e.g., for Sounding Reference Signal (SRS)). Symbols from transmit processor 364 may be pre-decoded by TX MIMO processor 366, where applicable, further processed by modulators in transceivers 354a-354r (e.g., for SC-FDM), and transmitted to BS 102.

[0083] At BS 102, uplink signals from UE 104 can be received by antennas 334a-t, processed by demodulators in transceivers 332a-332t, detected by MIMO detector 336 where applicable, and further processed by receiver processor 338 to obtain decoded data and control information transmitted by UE 104. Receiver processor 338 can provide the decoded data to data sink 339 and the decoded control information to controller / processor 340.

[0084] Memory 342 and memory 382 can store data and program code for BS 102 and UE 104, respectively.

[0085] Scheduler 344 can schedule UE to transmit data on the downlink and / or uplink.

[0086] In various respects, BS 102 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" can refer to various mechanisms that output data, such as from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceiver 332a-332t, antenna 334a-334t, and / or other aspects described herein. Similarly, "receiving" can refer to various mechanisms that acquire data, such as from antenna 334a-334t, transceiver 332a-332t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.

[0087] In various respects, UE 104 can also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from data source 362, memory 382, ​​transmit processor 364, controller / processor 380, TX MIMO processor 366, transceiver 354a-354t, antenna 352a-352t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antenna 352a-352t, transceiver 354a-354t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, ​​and / or other aspects described herein.

[0088] In some respects, the processor can be configured to perform various operations (such as those associated with the methods described herein) and to send (output) data to or receive data from another interface configured to send or receive data, respectively.

[0089] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes the use of wireless communication networks (such as Figure 1 All aspects of the data structure of the wireless communication network 100.

[0090] Specifically, Figure 4A Figure 400 is an example of the first subframe within a 5G (e.g., 5G NR) frame structure. Figure 4B Figure 430 illustrates an example of a DL channel within a 5G subframe. Figure 4C Figure 450 illustrates an example of the second subframe within a 5G frame structure, and Figure 4D Figure 480 illustrates an example of a UL channel within a 5G subframe.

[0091] Wireless communication systems can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single-Carrier Frequency Division Multiplexing (SC-FDM) will (e.g., as...) Figure 4B and Figure 4D The system bandwidth is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0092] Wireless communication frame structures can be frequency division duplex (FDD), where for a specific set of subcarriers, subframes within that set are dedicated to either deep (DL) or ultra-low (UL). Wireless communication frame structures can also be time division duplex (TDD), where for a specific set of subcarriers, subframes within that set are dedicated to both DL and UL.

[0093] exist Figure 4A and Figure 4C In this example, the wireless communication frame structure is TDD, where D stands for DL, U for UL, and X can be flexibly used between DL and UL. The UE can configure the time slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). In the depicted example, a 10ms frame is divided into 10 equal-sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. Subframes may also include micro-slots, which typically have fewer symbols than the entire time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0094] In some respects, the number of time slots within a subframe is based on the time slot configuration and parameter set. For example, for time slot configuration 0, different parameter sets (μ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 time slots per subframe, respectively. For time slot configuration 1, different parameter sets 0 to 2 allow for 2, 4, and 8 time slots per subframe, respectively. Therefore, for time slot configuration 0 and parameter set μ, there are 14 symbols per time slot and 2µ time slots per subframe. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to... kHz, where μ is the parameter set from 0 to 5. Therefore, the parameter set... It has a subcarrier spacing of 15 kHz and a parameter set It has a subcarrier spacing of 480 kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D It provides slot configuration 0 with 14 symbols per slot and parameter set with 4 slots per subframe. Example: The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0095] like Figure 4A , Figure 4B , Figure 4C and Figure 4DThe resource grid depicted can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)) extending for, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0096] like Figure 4A As illustrated, some REs in the RE carry information for the UE (e.g., Figure 1 and Figure 3 The reference (pilot) signal (RS) for the UE (104) may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0097] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0098] The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is generated by the UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identifier.

[0099] The secondary synchronization signal (SSS) can be located in symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identifier group number and radio frame timing.

[0100] Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block. The MIB provides the number of RBs and the System Frame Number (SFN) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Block (SIB)) not transmitted via the PBCH, and / or paging messages.

[0101] like Figure 4CAs illustrated, some REs in the REs carry DMRS for channel estimation at the BS (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE can transmit DMRS for PUCCH and DMRS for PUSCH. PUSCH DMRS can be transmitted, for example, in the first or second symbol preceding the PUSCH. PUCCH DMRS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and depending on the specific PUCCH format used. UE104 can transmit a Sounding Reference Signal (SRS). SRS can be transmitted, for example, in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of the comb teeth. SRS can be used by the BS for channel quality estimation to enable frequency-dependent scheduling at the UL.

[0102] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0103] An introduction to mmWave wireless communication

[0104] In wireless communication, the electromagnetic spectrum is typically subdivided into various categories, bands, channels, or other characteristics. Subdivisions are usually provided based on wavelength and frequency, where frequency can also be referred to as carrier, subcarrier, channel, tone, or subband.

[0105] Fifth-generation (5G) networks can utilize several frequency ranges, which in some cases are defined by standards such as the 3rd Generation Partnership Project (3GPP) standards. For example, although the 3GPP technical standard TS 38.101 currently defines Frequency Range 1 (FR1) as including 600MHz-6GHz, specific uplink and downlink allocations can fall outside this general range. Therefore, FR1 is often referred to (interchangeably) as the "sub-6GHz" band.

[0106] Similarly, although TS 38.101 currently defines Frequency Range 2 (FR2) as including 26 GHz–41 GHz, specific uplink and downlink allocations may fall outside this general range. FR2 is sometimes referred to (interchangeably) as the “millimeter wave” (“mmW” or “mmWave”) band, although it differs from the Extremely High Frequency (EHF) band (30 GHz–300 GHz) designated as “millimeter wave” by the International Telecommunication Union (ITU) because wavelengths at these frequencies are between 1 mm and 10 mm.

[0107] Compared to lower frequency communications, communications using mmWave / near-mmWave radio frequency bands (e.g., 3 GHz to 300 GHz) can have higher path loss and shorter range. (See above regarding...) Figure 1 As described, a base station (BS) (e.g., 180) configured to communicate using mmWave / near mmWave radio frequency bands can utilize beamforming (e.g., 182) with user equipment (UE) (e.g., 104) to improve path loss and range.

[0108] Overview of Open Radio Access Networks (O-RAN)

[0109] Figure 5 An example Open Radio Access Network (O-RAN) including a split base station (BS) 500 architecture is described. For example... Figure 5 As depicted and as noted above, the decomposed BS 500 architecture may include one or more central units (CUs) that may communicate directly with the core network via a backhaul link or indirectly with the core network via one or more decomposed BS units, such as a near real-time (near-RT) radio access network (RAN) intelligent controller (RIC) via an E2 link, or a non-real-time (non-RT) RIC associated with a service management and orchestration (SMO) framework, or both.

[0110] The core network may store a permanent UE identifier for the user equipment (UE) (e.g., a subscription permanent identifier (SUPI) or international mobile subscriber identity (IMSI)), which can be used to identify the UE across different radio resource control (RRC) state / mode transitions.

[0111] The CU can communicate with one or more distributed units (DUs) via a corresponding midhaul link (such as the F1 interface). The DU can communicate with one or more radio units (RUs) via a corresponding fronthaul link. The RU can communicate with the UE via one or more radio frequency (RF) access links.

[0112] Each of these units (e.g., CU, DU, RU, and near-RT RIC, non-RT RIC, and SMO frameworks) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively referred to as signals) via wired or wireless transmission media.

[0113] Non-RT RICs can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, or policy-based guidance for applications / features in near-RT RICs.

[0114] O-RAN can be used in several use cases that require a UE identifier to identify a specific UE. For example, some use cases aimed at optimizing UE services may require using some type of UE identifier to identify the UE. These use cases may include, for example, training an artificial intelligence / machine learning (AI / ML) system to generate AI / ML-based optimizations.

[0115] O-RAN may include some interfaces with the RAN (such as the E2 interface and the O1 interface). Therefore, the UE identifier available to the RAN is visible to the O-RAN. Unfortunately, the UE identifier in the RAN has a short validity period and is only applicable while the UE remains in RRC connected state. For example, when the UE transitions from RRC connected state to RRC idle state, the UE identifier becomes invalid, and the UE subsequently becomes unrecognizable in the RAN. This same limitation associated with the UE identifier also applies to the O-RAN, as the O-RAN receives data from the RAN.

[0116] Since O-RAN does not have any interface / communication with the core network, O-RAN is also unable to utilize or access permanent UE identifiers for UE-specific AI / ML optimizations.

[0117] In some cases, O-RAN can use all available UE identifiers for the UE in the RAN to correlate reports from different nodes associated with the UE and provide UE-specific AI / ML-based optimizations based on those reports. However, as noted above, the UE identifier in the RAN is valid only as long as the UE remains in RRC connected state, and becomes invalid once the UE enters RRC idle state. When the UE identifier becomes invalid, the UE is not identifiable in the RAN (and O-RAN). Therefore, currently the RAN / O-RAN does not have any UE identifiers for identifying the UE across RRC state transitions.

[0118] Because some use cases require identifying and associating different UE measurements performed by the UE in RRC connected and RRC idle states, a temporary UE identifier may be needed. This temporary UE identifier can be used to identify the UE (and its data) across RRC state transitions.

[0119] Various aspects related to User Equipment (UE) identifiers in Open Radio Access Networks (O-RAN)

[0120] This disclosure provides apparatus, methods, processing systems, and computer-readable media for assigning UE identifiers to user equipment (UEs) in an open radio access network (O-RAN). For example, in an O-RAN, a server associated with the radio access network (RAN) may request the Access and Mobility Management Function (AMF) of a core network node to assign a temporary or persistent UE identifier to a UE (or a group of UEs) to identify the UE (or the group of UEs) across different Radio Resource Control (RRC) state transitions. The AMF then assigns the temporary or persistent UE identifier to the UE (or the group of UEs) and transmits it to the server. In some cases, the persistent UE identifier may be a unique long-term reference (e.g., using a string of letters and numbers) that can be used to identify the UE / group of UEs, compared to the temporary UE identifier of the UE / group of UEs.

[0121] The technique proposed in this paper for allocating UE identifiers in O-RAN can be found at [reference needed]. Figures 6A to 15 To understand.

[0122] Figure 6A Example components of a decomposed base station (BS) 600 architecture are depicted. The decomposed BS 600 architecture may include one or more central units (CUs) (not shown) that can communicate directly with the core network 610. This communication with the core network may occur, for example, via a backhaul link, or indirectly with the core network 610 through one or more decomposed BS units, such as a next-generation (NG) radio access network (RAN) 615, a near real-time (near-RT) RAN intelligent controller (RIC) 620, and / or a non-RT RIC 625 associated with a service management and orchestration (SMO) framework.

[0123] Each of these units may include (or be coupled to) one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of these units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via a transmission medium. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via a wired transmission medium. Additionally or alternatively, units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as radio frequency (RF) transceivers) configured to receive signals on a wireless transmission medium or transmit signals to one or more other units, or both.

[0124] For example, such as Figure 6A As depicted, the core network 610 and NG-RAN 615 can communicate or be associated with each other via the NG interface. The NG-RAN 615 and the near-RT RIC 620 can communicate or be associated with each other via the E2 interface. The near-RT RIC 620 and the non-RT RIC 625 can communicate or be associated with each other via the A1 interface.

[0125] Figure 6B A call flow diagram illustrating example communication between core network 610, NG-RAN 615, near-RT RIC 620, and UE 628 is depicted. Figure 6B The core network 610 shown can be about Figure 2 An example of the core network 220 depicted and described. Figure 6B The NG-RAN 615 shown may be about Figure 1 and Figure 3 Examples of BS 102 as depicted and described. Figure 6B The near-RT RIC 620 shown may be related to Figure 2 Examples of near-RT RIC 225 depicted and described. Figure 6B The UE 628 shown may be about Figure 1 and Figure 3 Examples of UE 104 depicted and described.

[0126] As indicated at location 630, near RT RIC 620 subscribes to NG-RAN 615 to receive the UE identifier (e.g., temporary UE identifier) ​​of UE 628.

[0127] In some cases, the near-RT RIC 620 may also subscribe to the NG-RAN 615 to receive another UE identifier, such as a persistent identifier for a single UE (e.g., UE 628) or a group of UEs (e.g., which may include UE 628 and other UEs). Some or all of the UEs in this group may have at least one common characteristic. In one example, the NG-RAN 615 may select the group of UEs from the multiple UEs based at least on one or more characteristics corresponding to the multiple UEs. In another example, the core network 610 may select the group of UEs from the multiple UEs based at least on one or more characteristics corresponding to the multiple UEs.

[0128] As indicated at 635, UE 628 establishes a radio resource control (RRC) connection with NG-RAN 615 (i.e., RRC connection status).

[0129] As indicated at 640, NG-RAN 615 triggers (or executes some instructions) to run an artificial intelligence / machine learning (AI / ML) workflow, which includes model training and updates for UE 628 (or the group of UEs).

[0130] As indicated at 645, during the AI / ML training of UE 628, NG-RAN 615 transmits a request for a temporary UE identifier to core network 610 (e.g., to the AMF of core network 610) (e.g., to identify UE 628 across different RRC state transitions).

[0131] In some cases, NG-RAN 615 may also transmit a request for a persistent identifier to core network 610 (e.g., to the AMF of core network 610) to identify the individual UE or the group of UEs across different RRC state transitions. In some cases, this request may be included in an initial context establishment request, which may be used during the initial connection between at least one UE in the group and NG-RAN 615. For example, whenever at least one UE in the group becomes available to connect to NG-RAN 615, NG-RAN 615 may request core network 610 to provide a persistent identifier for the group of UEs via an initial context establishment request.

[0132] As indicated at location 650, the core network 610 generates a temporary UE identifier and assigns / transmits it to the NG-RAN 615.

[0133] In some respects, the core network 610 can randomly generate temporary UE identifiers based on the permanent UE identifier of UE 628.

[0134] In some respects, the core network 610 may use a function to derive a temporary UE identifier. The function may be based on a Subscription Permanent Identifier (SUPI), an International Mobile Subscriber Identity (IMSI), at least one key, and / or at least one parameter. The function may be a one-way function, such as a secure hash function. At least one key may be known only to the core network 610. At least one parameter may be an optional parameter (e.g., it may be used to avoid temporary UE identifier conflicts).

[0135] In some respects, when using the derivation process, core network 610 may store at least one key and at least one parameter (if used) as part of the UE context of UE 628 (e.g., not for each UE, but for all UEs). Since core network 610 knows at least one key and at least one parameter, core network 610 may use the at least one key and at least one parameter to derive a temporary UE identifier (e.g., because core network 610 already knows the SUPI and IMSI of UE 628) upon NG-RAN 615 request.

[0136] In some respects, when multiple keys are used to generate a temporary UE identifier, core network 610 may store a key identifier associated with each key used to derive the temporary UE identifier as part of the UE context. Core network 610 may then determine which keys are used to derive the temporary UE identifier. This example scenario may be valid only within core network 610. In some cases, when core network 610 changes, the new core network may generate a new temporary UE identifier for UE 628 (e.g., unless at least one key used for the temporary UE identifier is shared between different core networks by core network 610).

[0137] In some respects, the core network 610 may determine the validity period (or lifetime) of the temporary UE identifier (e.g., to avoid prolonged tracking of UE 628 at NG-RAN 615 and to limit the linking of UE data at NG-RAN 615). The core network 610 may determine the validity period based on information associated with NG-RAN 615 or policies associated with the core network 610.

[0138] In some respects, once the validity period of the temporary UE identifier expires, the core network 610 assigns a new temporary UE identifier to the UE 628. In such cases, the core network 610 may also change at least one key and / or at least one parameter used to generate the new temporary UE identifier. If a new key is used to generate the new temporary UE identifier, the key identifier associated with the new key is stored as part of the UE context (e.g., to determine which key was used to derive the temporary UE identifier).

[0139] In some cases, the core network 610 may generate a persistent identifier for the individual UE or the group of UEs and then assign / transmit it to the NG-RAN 615. In some cases, when it is the same UE and / or the same group of UEs, the core network 610 may provide the same persistent identifier for the individual UE or the group of UEs to the NG-RAN 615 across different RRC connections.

[0140] As indicated at 655, NG-RAN 615 (e.g., in the UE context) stores a temporary UE identifier.

[0141] In some cases, NG-RAN 615 may (e.g., within the UE context) store a persistent identifier for an individual UE or a group of UEs. In some cases, NG-RAN 615 may use the persistent identifier to associate UE measurements performed by the individual UE or a group of UEs in connected RRC and idle RRC states. In some cases, NG-RAN 615 may request the AMF to store the persistent identifier when at least one UE to which the persistent identifier is applicable enters an RRC idle state.

[0142] As indicated at location 660, NG-RAN 615 transmits a temporary UE identifier to the nearby RT RIC 620.

[0143] In some cases, NG-RAN can transmit persistent identifiers to the near-RT RIC 620.

[0144] As indicated at 665, NG-RAN 615 moves to the RRC idle state with UE 628. That is, the RRC connection between NG-RAN 615 and UE 628 ends.

[0145] As indicated at 670, UE 628 re-establishes an RRC connection with NG-RAN 615.

[0146] As indicated at 675, NG-RAN 615 again transmits a request for a temporary UE identifier to core network 610. For example, whenever UE 628 connects to NG-RAN 615, NG-RAN 615 may request core network 610 (e.g., via an initial context establishment request) to provide a temporary UE identifier.

[0147] As indicated at 680, the core network 610 identifies (e.g., provides a temporary UE identifier) ​​the request for the same UE 628 and assigns the same (i.e., the previously assigned) temporary UE identifier to UE 628.

[0148] As indicated at 685, the core network 610 transmits the same temporary UE identifier to the NG-RAN 615. For example, if the request is associated with the same UE 628, the AMF of the core network 610 can provide the same temporary UE identifier to the NG-RAN 615 across different RRC connections. In some respects, the NG-RAN 615 can use the temporary UE identifier to associate different UE measurements performed by UE 628 in both RRC connected and RRC idle states.

[0149] In some respects, NG-RAN 615 can assign persistent identifiers (e.g., to identify the individual UE and / or the group of UEs across different RRC state transitions). For example, NG-RAN 615 can assign a first identifier to the individual UE and / or the group of UEs, and then make the first identifier persistent across different RRC states corresponding to the individual UE and / or the group of UEs. In some cases, to make the first identifier persistent across different RRC states corresponding to the individual UE and / or the group of UEs, NG-RAN 615 can send a request to the AMF of core network 610 to store the first identifier in a database associated with the AMF of core network 610. This request can be sent when the individual UE is available to move to an RRC idle state and / or when a UE in the group of UEs is available to move to an RRC idle state. In some cases, when a single UE is available to return to RRC connection state and / or when a UE in a group of UEs is available to return to RRC connection state (or a handover process is underway), the AMF of the core network 610 may provide the NG-RAN 615 with (e.g., in response to some request from the NG-RAN 615) the same first identifier for the single UE and / or the group of UEs. Thus, the NG-RAN 615 may be able to identify the single UE and / or the group of UEs using the same first identifier.

[0150] The identifier, and the requirement that the AMF store the RAN-assigned identifier when the UE enters idle state, and provide the same identifier when the UE regains connection or undergoes handover, etc., make it persistent across RRC states. In this way, the RAN can identify it as the same UE. The second aspect is not clear from this claim.

[0151] Figure 7A Components of another example decomposed BS 700 architecture are depicted. The decomposed BS 700 architecture includes a core network 710, an NG-RAN 715, a near-RT RIC 720, and (e.g., associated with an SMO framework) a non-RT RIC 725.

[0152] like Figure 7AAs depicted, the core network 710 and NG-RAN 715 can communicate or associate with each other via the NG interface. The NG-RAN 715 and near-RT RIC 720 can communicate or associate with each other via the E2 interface. The near-RT RIC 720 and non-RT RIC 725 can communicate or associate with each other via the A1 interface. The core network 710 and non-RT RIC 725 can communicate or associate with each other via a service-based architecture (SBA) interface (e.g., which could be a UE identifier interface).

[0153] Figure 7B A call flow diagram illustrating example communication between core network 710, near RT RIC 720, and non-RT RIC 725 is depicted. Figure 7B The core network 710 shown can be about Figure 2 An example of the core network 220 depicted and described. Figure 7B The near-RT RIC 720 shown may be related to Figure 2 Examples of near-RT RIC 225 depicted and described. Figure 7B The non-RT RIC 725 shown may be related to Figure 2 Examples of non-RT RIC 215 depicted and described.

[0154] As indicated at 730, the non-RT RIC 725 triggers (or executes some instructions) to run an AI / ML workflow that includes model training and updates for the UE.

[0155] As indicated at 735, the non-RT RIC 725 (e.g., via the O1 and A1 interfaces) receives UE-specific data including the UE's RAN UE identifier.

[0156] As indicated at 740, the non-RT RIC 725 transmits a request to the core network 710 (e.g., to the AMF of the core network 710) for a temporary UE identifier associated with identifier X for the UE (e.g., to identify the UE across different RRC state transitions).

[0157] As indicated at 745, the core network 710 transmits the temporary UE identifier Y associated with the identifier X to the non-RT RIC 725.

[0158] As indicated at 750, the non-RT RIC 725 transmits another request to the core network 710 for a temporary UE identifier associated with identifier Z for the UE.

[0159] As indicated at location 755, core network 710 identifies that identifier X and identifier Z belong to the same UE, and assigns the same temporary UE identifier Y to that UE.

[0160] As indicated at location 760, the core network 710 transmits the temporary UE identifier Y associated with identifier Z to the non-RT RIC 725.

[0161] Figure 7C Another call flow diagram illustrates example communication between core network 710, near RT RIC 720, and non-RT RIC 725.

[0162] As indicated at location 765, the near-RT RIC 720 triggers (or executes some instructions) to run an AI / ML workflow that includes model training and updates for the UE.

[0163] As indicated at 770, the UE-specific data, including the RAN UE identifier of the UE, is received near the RT RIC 720 (e.g., via the E2 interface).

[0164] As indicated at 775, the near-RT RIC 720 transmits a request for a temporary UE identifier associated with identifier X to the non-RT RIC 725.

[0165] As indicated at 780, the non-RT RIC 725 transmits the received request to the core network 710 for the temporary UE identifier associated with the identifier X of the UE.

[0166] As indicated at location 785, the core network 710 transmits the temporary UE identifier Y associated with identifier X to the non-RT RIC 725.

[0167] As indicated at 790, the non-RT RIC 725 transmits the received temporary UE identifier Y associated with identifier X to the near RT RIC 720.

[0168] In some cases, the non-RT RIC 725 may also transmit a request to the core network 710 (e.g., to the AMF of the core network 710) for a persistent identifier for an individual UE or a group of UEs with certain characteristics (e.g., to identify these UEs across different RRC state transitions). In response to this request, the core network 710 may assign a persistent identifier to the individual UE or the group of UEs and transmit it to the non-RT RIC 725. In some cases, the non-RT RIC 725 may store the persistent identifier at the core network 710 and may retrieve the persistent identifier from the core network 710 as needed and when required.

[0169] Figure 8A call flow diagram illustrating example communication between a UE, a gNodeB (gNB), the AMF of the core network, and the Session Management Function (SMF) / User Plane Function (UPF) is depicted. Figure 8 The UE shown can be about Figure 1 and Figure 3 Examples of UE 104 depicted and described. Figure 8 The gNB shown can be about Figure 1 and Figure 3 Examples of BS 102 as depicted and described. Figure 8 The core network shown can be about Figure 2 An example of the core network 220 depicted and described.

[0170] As indicated at 805, the UE sends a connection establishment request (e.g., RRC connection) to the gNB.

[0171] As indicated at location 810, the gNB transmits a UE context establishment request to the AMF.

[0172] As indicated at 815, the AMF transmits a request to the SMF / UPF for a tunnel endpoint (TE) identifier associated with the UE (e.g., for use in a packet data unit (PDU) session).

[0173] As indicated at 820, the SMF / UPF generates a TE identifier associated with the UE and transmits it to the AMF.

[0174] As indicated at 825, the SMF / UPF (e.g., in the UE's UE context) stores the TE identifier associated with the UE.

[0175] As indicated at 830, the AMF transmits a UE context establishment response to the gNB, which includes the TE identifier associated with the UE (e.g., for a UE context establishment request).

[0176] As indicated at 835, the gNB transmits a connection establishment response (e.g., in response to a connection establishment request) to the UE.

[0177] As indicated at 840, the UE establishes an RRC connection with the gNB.

[0178] As indicated at 845, the gNB initiates the release of information associated with the UE context.

[0179] As indicated at 850, an RRC idle state is established between the gNB and the UE.

[0180] As indicated at 855, the UE initiates an RRC connection with the gNB again.

[0181] As indicated at 860, the UE again transmits a connection establishment request to the gNB. The gNB can then transmit a UE context establishment request to the AMF.

[0182] As indicated at 865, the AMF again sends a request to the SMF / UPF for the TE identifier associated with the UE.

[0183] As indicated at 870, the SMF / UPF identifier requests for TE identifiers for the same UE and assigns the same (i.e., the previously assigned or assigned) TE identifier to that UE.

[0184] As indicated at 875, the SMF / UPF again transmits the TE identifier associated with the UE to the AMF.

[0185] As indicated at 880, the AMF transmits a UE context establishment response to the gNB, which includes the TE identifier associated with the UE (e.g., for a UE context establishment request).

[0186] As indicated at 885, the gNB transmits a connection establishment response (e.g., in response to a connection establishment request) to the UE.

[0187] As noted above, during a UE's PDU session, the TE identifier is assigned to the UE by the SMF / UPF for use in the PDU session and is (indirectly) provided to the gNB via the NG interface. Even when the UE enters the RRC idle state, the TE identifier can be stored in the SMF / UPF context, and when the UE returns to the RRC connected state and re-establishes the PDU session, the same TE identifier is reassigned to the same UE. However, in the RAN system, when a UE enters the RRC idle state from the RRC connected state, the entire UE context, including the TE identifier assigned to the UE, can be lost.

[0188] Figure 9 A call flow diagram illustrating example communication between the UE, gNB, and near-RT RIC is depicted. Figure 9 The UE shown can be about Figure 1 and Figure 3 Examples of UE 104 depicted and described. Figure 9 The gNB shown can be about Figure 1 and Figure 3 Examples of BS 102 as depicted and described. Figure 9 The near-RT RIC shown can be about Figure 2 Examples of near-RTRIC 225 depicted and described.

[0189] As indicated at 905, the near-RT RIC subscribes to the gNB to receive UE-related data, including the UE's TE identifier. For example, the near-RT RIC may subscribe to the gNB via the E2 interface to (e.g., from the UE-related data via the E2 interface) receive the UE's available, core network-assigned uplink TE identifier.

[0190] As indicated at 910, the UE establishes an RRC connection with the gNB.

[0191] As indicated at 915, the gNB transmits UE-related data, including the UE's TE identifier, to the nearby RT RIC.

[0192] As indicated at 920, the near-RT RIC stores the UE's TE identifier in a database, which may include UE-specific TE identifiers.

[0193] As indicated at 925, an RRC idle state is established between the UE and the gNB.

[0194] As indicated at 930, during the RRC idle state, the gNB loses all UE context / information associated with the UE.

[0195] As indicated at 935, the UE re-establishes an RRC connection with the gNB.

[0196] As indicated at 940, the gNB again transmits UE-related data, including the UE's TE identifier, to the nearby RT RIC.

[0197] As indicated at 945, the near-RT RIC matches the received TE identifier with available TE identifiers in the database.

[0198] As indicated at 950, the near-RT RIC identifies the UE whose received TE identifier and available TE identifier are the same based on the matching of the received TE identifier and available TE identifiers. For example, when a TE identifier matching a different UE identifier is received from the gNB, the near-RT RIC can identify the UE associated with the TE identifier based on the matching of the TE identifiers.

[0199] Figure 10A Another example of a decomposed BS 1000 architecture is described. The decomposed BS 700 architecture includes a core network 1005, an NG-RAN 1010, a near-RT RIC 1015, and a management data analytics function (MDAF) 1020. The MDAF 1020 may include or be associated with a non-RT RIC (e.g., the non-RT RIC is further associated with an SMO framework).

[0200] like Figure 10AAs depicted, core network 1005 and NG-RAN 1010 can communicate or be associated with each other via the NG interface. NG-RAN 1010 and near-RT RIC 1015 can communicate or be associated with each other via the E2 interface. Near-RT RIC 1015 and MDAF 1020 can communicate or be associated with each other via the A1 interface. Core network 1005 and MDAF 1020 can communicate or be associated with each other via the SBA interface.

[0201] Figure 10B A call flow diagram illustrating example communication between core network 1005, non-RT RIC 1020, and near-RT RIC 1015 is depicted. Figure 10B The core network 1005 shown can be about Figure 2 An example of the core network 220 depicted and described. Figure 10B The near-RT RIC 1015 shown may be related to Figure 2 Examples of near-RT RIC 225 depicted and described. Figure 10B The non-RT RIC 1020 shown can be about Figure 2 Examples of non-RT RIC 215 depicted and described. In some cases, non-RT RIC 1020 acts as (e.g., in the Operation, Administration and Maintenance (OAM) layer) MDAF and connects to core network 1005 to receive services from core network 1005.

[0202] As indicated at 1025, the core network 1005 transmits one or more permanent identifiers associated with the UE to the non-RT RIC 1020. These one or more permanent identifiers may include a Subscription Permanent Identifier (SUPI) and / or an International Mobile Subscriber Identity (IMSI).

[0203] As indicated at 1030, the non-RT RIC 1020 determines one or more temporary identifiers associated with the UE based on one or more permanent identifiers. For example, since the non-RT RIC 1020 acts as an MDAF, it can access one or more permanent identifiers from the core network 1005 and convert those permanent identifiers into one or more temporary identifiers (e.g., and perform UE-specific AI / ML training and optimization for the UE based on the one or more temporary identifiers).

[0204] As indicated at 1035, the non-RT RIC 1020 transmits one or more temporary identifiers to the near-RT RIC 1015. For example, based on the operator's trusted network configuration, the non-RT RIC 1020 may provide one or more temporary identifiers to the near-RT RIC 1015 (e.g., to perform UE-specific AI / ML training and optimization in the near-RT RIC 1015).

[0205] Example methods for wireless communication at next-generation (NG) radio access networks (RAN).

[0206] Figure 11 It shows the use of the first node (e.g., such as Figure 1 and Figure 3 An example of a method 1100 for wireless communication at BS 102. In one example, the first node may include a server associated with a next-generation (NG) radio access network (RAN).

[0207] Method 1100 begins with step 1105: sending a request to a second node to allocate a temporary identifier for the User Equipment (UE). The second node may include the Access and Mobility Management Function (AMF) of the core network node. In some cases, this step refers to the operation as described in reference... Figure 15 The circuitry and / or code described for transmitting, or the code for transmitting, may be executed by the circuitry and / or code for transmitting.

[0208] Then, method 1100 proceeds to step 1110: receiving an indication of a first temporary identifier for the UE from the second node. The first temporary identifier is based on the UE's first identifier. The first temporary identifier is persistent across multiple Radio Resource Control (RRC) states corresponding to the UE. In some cases, the operation of this step refers to, as referenced... Figure 15 The circuitry and / or code described for receiving, or the code for receiving, may be executed by the circuitry and / or code for receiving.

[0209] In some respects, NG-RAN and AMF are interconnected via the NG interface.

[0210] In some respects, the UE's first identifier includes the UE's permanent identifier.

[0211] In some respects, method 1100 then proceeds to identify the UE across multiple RRC states based on a first temporary identifier.

[0212] In some respects, method 1100 then proceeds to using a first temporary identifier to associate different measurements performed by the UE across multiple RRC states.

[0213] In some respects, multiple RRC states include at least the RRC connected state, the RRC inactive state, and the RRC idle state.

[0214] In some respects, method 1100 then proceeds to receiving a subscription message for a UE temporary identifier from the near real-time (RT) RAN intelligent controller (RIC) via the E2 interface; and in response to the subscription message, sending a first temporary identifier to the near RT RIC.

[0215] In some respects, method 1100 then proceeds to determining that the first temporary identifier has been used for a period of time; and based on the determination, receiving an indication of a second temporary identifier for the UE from the second node.

[0216] In some respects, method 1100 then proceeds to sending an indication of a first temporary identifier to a third node via the XN interface. The first and third nodes may include different servers associated with different NG-RANs.

[0217] In some respects, method 1100 then proceeds to sending different measurements performed by the UE and a first temporary identifier to the third node via the XN interface.

[0218] In some respects, method 1100 then proceeds to receiving, via the XN interface, different measurements performed by the UE and a first temporary identifier from the third node.

[0219] In some respects, the first node may include Service Management and Orchestration (SMO) or a non-RT RIC; the second node may include network element devices of the core network node; and the SMO or non-RT RIC and the network element devices are interconnected via a Service-Based Architecture (SBA) interface.

[0220] In some respects, requests from SMO or non-RT RIC to network element devices include the UE's RAN-based identifier.

[0221] In some respects, method 1100 then proceeds to sending an indication of the first temporary identifier to the near-RT RIC via the A1 interface.

[0222] In some aspects, method 1100 then proceeds to receiving a message requesting a temporary identifier for the UE from the near RT RIC, wherein the message also includes the UE's RAN-based identifier; and in response to the message, sending a first temporary identifier to the near RT RIC. The first temporary identifier is based on the RAN-based identifier.

[0223] In one aspect, method 1100 or any aspect thereof may be made by means of a device (such as...) Figure 15The communication device 1500 is used to perform the method 1100. The device includes various components that are operable to, configured to, or adapted to perform the method 1100. The communication device 1500 is described in more detail below.

[0224] It should be noted that Figure 11 This is just one example of a method, and other methods that include fewer, additional, or alternative steps may be consistent with this disclosure.

[0225] Example methods for wireless communication at the Access and Mobility Management Function (AMF)

[0226] Figure 12 It shows the use of the first node (e.g., such as Figure 1 and Figure 3 An example of a method 1200 for wireless communication at BS 102. In one example, the first node may include the access and mobility management function (AMF) of the core network node.

[0227] Method 1200 begins with step 1205: receiving a request from a second node to assign a temporary identifier to the user equipment (UE). The second node may include a server associated with a next-generation (NG) radio access network (RAN). In some cases, this step refers to the operation as described in reference... Figure 15 The circuitry and / or code described for receiving, or the code for receiving, may be executed by the circuitry and / or code for receiving.

[0228] Method 1200 begins with step 1210: sending an indication of a first temporary identifier for the UE to the second node. The first temporary identifier is based on the UE's first identifier. The first temporary identifier is persistent across multiple Radio Resource Control (RRC) states corresponding to the UE. In some cases, the operation of this step refers to... Figure 15 The circuitry and / or code described for transmitting, or the code for transmitting, may be executed by the circuitry and / or code for transmitting.

[0229] In some respects, NG-RAN and AMF are interconnected via the NG interface.

[0230] In some respects, the UE's first identifier includes the UE's permanent identifier.

[0231] In some respects, method 1200 then proceeds to randomly generating a first temporary identifier based on the first identifier; and storing the first temporary identifier as part of the UE context.

[0232] In some respects, method 1200 then proceeds to using a function to derive a first temporary identifier based on a first identifier. The function is based on at least one of the following: a Subscription Permanent Identifier (SUPI), an International Mobile Subscriber Identity (IMSI), at least one key, or at least one parameter.

[0233] In some respects, method 1200 then proceeds to storing at least one of at least one key or at least one parameter as part of the UE context.

[0234] In some respects, method 1200 then proceeds to storing the identifier (ID) associated with the key used to derive the first temporary identifier as part of the UE context when the function is based on two or more keys.

[0235] In some respects, the first node may include network element equipment of the core network node. The second node may include a Service Management and Orchestration (SMO) or Non-Real-Time (RT) RAN Intelligent Controller (RIC). The SMO or non-RT RIC interconnects with the network element equipment via a Service-Based Architecture (SBA) interface. In some cases, a request from the SMO or non-RT RIC to the network element equipment may include the UE's Radio Access Network (RAN) based identifier.

[0236] In one aspect, method 1200 or any aspect thereof may be made by means of a device (such as...) Figure 15 The communication device 1500 performs the execution, and the device includes various components capable of operating, being configured, or adapted to perform the method 1200. The communication device 1500 is described in more detail below.

[0237] It should be noted that Figure 12 This is just one example of a method, and other methods that include fewer, additional, or alternative steps may be consistent with this disclosure.

[0238] Demonstration for wireless communication at the intelligent controller (RIC) of a near real-time (RT) radio access network (RAN). Example method

[0239] Figure 13 An example of a near real-time (RT) radio access network (RAN) intelligent controller (RIC) is shown (e.g., such as...). Figure 1 and Figure 3 An example of a method 1300 for wireless communication at BS 102.

[0240] Method 1300 begins with step 1305: sending a subscription message to a network entity to receive User Equipment (UE) data, which includes one or more Tunnel Endpoint (TE) identifiers associated with the UE. In some cases, this step refers to the operation as described in reference... Figure 15The circuitry and / or code described for transmitting, or the code for transmitting, may be executed by the circuitry and / or code for transmitting.

[0241] Method 1300 begins with step 1310: in response to a subscription message, receiving at least one first TE identifier associated with the first identifier of the UE from a network entity. In some cases, this step refers to the operation as described in reference... Figure 15 The circuitry and / or code described for receiving, or the code for receiving, may be executed by the circuitry and / or code for receiving.

[0242] In some respects, method 1300 then proceeds to receiving from the network entity at least one second TE identifier associated with the second identifier of the UE.

[0243] In some respects, method 1300 then proceeds to determining that at least one first TE identifier and at least one second TE identifier are associated with the same UE when at least one first TE identifier matches at least one second TE identifier.

[0244] In one aspect, method 1300 or any aspect thereof may be made by means of a device (such as...) Figure 15 The communication device 1500 is used to perform the method 1300, which includes various components capable of operating, being configured, or adapted to perform the method. The communication device 1500 is described in more detail below.

[0245] It should be noted that Figure 13 This is just one example of a method, and other methods that include fewer, additional, or alternative steps may be consistent with this disclosure.

[0246] Demonstration for wireless communication at the intelligent controller (RIC) of a non-real-time (RT) radio access network (RAN). Example method

[0247] Figure 14 An example of a smart controller (RIC) for non-real-time (RT) radio access network (RAN) is shown (e.g., such as...). Figure 1 and Figure 3 An example of a method 1400 for wireless communication at BS 102.

[0248] Method 1400 begins with step 1405: receiving one or more permanent identifiers associated with the User Equipment (UE) from the core network node. In some cases, this step refers to the operation as described in reference... Figure 15 The circuitry and / or code described for receiving, or the code for receiving, may be executed by the circuitry and / or code for receiving.

[0249] Method 1400 begins with step 1410: sending one or more temporary identifiers to the near RT RIC. The one or more temporary identifiers are based on one or more permanent identifiers. In some cases, this step refers to the operation as described in the reference... Figure 15 The circuitry and / or code described for transmitting, or the code for transmitting, may be executed by the circuitry and / or code for transmitting.

[0250] In some respects, the non-RT RIC is configured as a management data analytics service within the Operations, Administration and Maintenance (OAM) layer.

[0251] In some respects, one or more permanent identifiers include at least one of the following: Subscription Permanent Identifier (SUPI) or International Mobile Subscriber Identity (IMSI).

[0252] In some respects, method 1400 then proceeds to convert one or more permanent identifiers into one or more temporary identifiers; receive a request for one or more temporary identifiers from the near RT RIC; and in response to the request, send an instruction for one or more temporary identifiers to the near RT RIC.

[0253] In one aspect, method 1400 or any aspect thereof may be made by means of a device (such as...) Figure 15 The communication device 1500 is used to perform the method 1400, which includes various components capable of operating, being configured, or adapted to perform the method. The communication device 1500 is described in more detail below.

[0254] It should be noted that Figure 14 This is just one example of a method, and other methods that include fewer, additional, or alternative steps may be consistent with this disclosure.

[0255] Example communication device

[0256] Figure 15 Various aspects of the example communication device 1500 are described. In some aspects, the communication device 1500 is a network entity, such as... Figure 1 and Figure 3 BS 102 or as about Figure 2 The decomposed base station under discussion.

[0257] Communication device 1500 includes a processing system 1505 coupled to a transceiver 1555 (e.g., a transmitter and / or receiver) and / or a network interface 1565. Transceiver 1555 is configured to transmit and receive signals for communication device 1500 via antenna 1560, such as various signals as described herein. Network interface 1565 is configured to transmit and receive signals for communication device 1500 via a communication link (such as, as described herein, etc.). Figure 2The described backhaul link, midhaul link, and / or fronthaul link acquire and transmit signals for communication device 1500. Processing system 1505 can be configured to perform processing functions of communication device 1500, including processing signals received by and / or to be transmitted by communication device 1500.

[0258] Processing system 1505 includes one or more processors 1510. In various aspects, the one or more processors 1510 may represent one or more of a receive processor 338, a transmit processor 320, a TX MIMO processor 330, and / or a controller / processor 340, as per [reference to...]. Figure 3 As described. One or more processors 1510 are coupled to a computer-readable medium / memory 1530 via a bus 1550. In some aspects, the computer-readable medium / memory 1530 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 1510, cause one or more processors 1510 to perform actions related to... Figure 11 The described method 1100, about Figure 12 The described method 1200, about Figure 13 The described method 1300, about Figure 14 The method 1400 described herein or any aspect thereof. It should be noted that references to the processor performing the function of the communication device 1500 may include one or more processors 1510 of the communication device 1500 performing that function.

[0259] In the depicted example, computer-readable medium / memory 1530 stores code (e.g., executable instructions), such as code 1535 for transmitting and code 1540 for receiving. Processing the code 1535 for transmitting and the code 1540 for receiving enables the communication device 1500 to perform operations related to... Figure 11 The described method 1100, about Figure 12 The described method 1200, about Figure 13 The described method 1300, about Figure 14 The method described 1400 or any aspect thereof.

[0260] One or more processors 1510 include circuitry configured to implement (e.g., execute) code stored in computer-readable medium / memory 1530, including circuitry such as circuitry 1515 for transmitting and circuitry 1520 for receiving. Processing of the circuitry 1515 for transmitting and the circuitry 1520 for receiving enables the communication device 1500 to perform operations related to... Figure 11 The described method 1100, about Figure 12 The described method 1200, about Figure 13The described method 1300, about Figure 14 The method described 1400 or any aspect thereof.

[0261] The various components of the communication device 1500 can provide for performing tasks related to... Figure 11 The described method 1100, about Figure 12 The described method 1200, about Figure 13 The described method 1300, about Figure 14 The described method 1400 or any component related to it.

[0262] Components used for sending, transmitting, or outputting for transmission may include Figure 3 The transceiver 332 and / or antenna 334 of BS 102 illustrated herein, and / or Figure 15 The communication device 1500 includes a transmission circuit 1515, a transmission code 1535, a transceiver 1855, and an antenna 1560.

[0263] The component used for receiving or obtaining may include Figure 3 The transceiver 332 and / or antenna 334 of BS 102 illustrated herein, and / or Figure 15 The communication device 1500 includes a receiving circuit 1520, a receiving code 1540, a transceiver 1855, and an antenna 1560.

[0264] In some cases, a device may not actually transmit, for example, signals and / or data, but may have an interface (a component for output) for outputting signals and / or data for transmission. For example, a processor may output signals and / or data to an RF front-end for transmission via a bus interface. In various aspects, an RF front-end may include a variety of components, including, for example, in... Figure 3 The examples depict transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, etc.

[0265] In some cases, a device may not actually receive signals and / or data, but may have an interface (a component for receiving) for acquiring signals and / or data received from another device. For example, a processor may acquire (or receive) signals and / or data from an RF front-end via a bus interface for reception. In various aspects, an RF front-end may include a variety of components, including, for example, in Figure 3 The examples depict transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, etc. It is worth noting that... Figure 15 This is just one example, and many other examples and configurations of the communication device 1500 are possible.

[0266] Example Terms

[0267] Specific implementation examples are described in the following numbered clauses: Clause 1: A method at a first node, the method comprising: sending a request to a second node to assign a persistent identifier to a first plurality of UEs in one or more groups of user equipment (UEs); and receiving from the second node an indication of a first persistent identifier for the first plurality of UEs, wherein the first persistent identifier is applicable across a plurality of radio resource control (RRC) states corresponding to all UEs in the first plurality of UEs.

[0268] Clause 2: The method according to Clause 1, wherein the first node includes a server associated with a next-generation (NG) radio access network (RAN); the second node includes an access and mobility management function (AMF) of a core network node; the NG-RAN and the AMF are interconnected via an NG interface; and the first persistent identifier is a long-term reference for the first plurality of UEs.

[0269] Clause 3: The method according to any one of Clauses 1 to 2, wherein each of the first plurality of UEs is associated with at least one common characteristic.

[0270] Clause 4: The method according to any one of Clauses 1 to 3, wherein at least two or more of the first plurality of UEs are associated with at least one common characteristic.

[0271] Clause 5: The method according to any one of Clauses 1 to 4 further includes selecting a first plurality of UEs from the plurality of UEs based at least on one or more characteristics corresponding to the plurality of UEs, wherein each of the first plurality of UEs is associated with at least one common characteristic.

[0272] Clause 6: The method according to any one of Clauses 1 to 5 further includes receiving signaling from the second node instructing the first plurality of UEs, wherein each of the first plurality of UEs is associated with at least one common characteristic.

[0273] Clause 7: The method according to any one of Clauses 1 to 6 further includes storing the first persistent identifier of the first plurality of UEs in a database.

[0274] Clause 8: The method according to any one of Clauses 1 to 7 further includes using the first persistent identifier of the first plurality of UEs to associate different measurements performed by one or more of the first plurality of UEs across different RRC states associated with the one or more of the first plurality of UEs.

[0275] Clause 9: The method according to any one of Clauses 1 to 8, wherein: the request is included in an initial context establishment request; and the initial context establishment request is used during the initial connection between the first node and at least one of the first plurality of UEs.

[0276] Clause 10: The method according to any one of Clauses 1 to 9, wherein: the first persistent identifier is assigned to the first plurality of UEs across different RRC states corresponding to each of the first plurality of UEs; and the different RRC states include at least an RRC connected state, an RRC inactive state, and an RRC idle state.

[0277] Clause 11: The method according to any one of Clauses 1 to 10, the method further comprising: determining that at least one of the first plurality of UEs has moved to an RRC idle state; and sending a request to the second node based on the determination to store the first persistent identifier of the first plurality of UEs.

[0278] Clause 12: A method at the Access and Mobility Management Function (AMF) of a core network node, the method comprising: receiving a request from a server associated with a Next Generation (NG) Radio Access Network (RAN) to store an identifier of one or more sets of User Equipment (UEs) or at least one of UEs, wherein the identifier is assigned at the server associated with the NG-RAN; and storing the identifier in a database associated with the AMF of the core network node according to the request.

[0279] Clause 13: The method described in Clause 12, wherein the NG-RAN and the AMF are interconnected via the NG interface.

[0280] Clause 14: The method according to any one of Clauses 12 to 13, wherein each of the one or more groups of UEs is associated with at least one common characteristic.

[0281] Clause 15: The method according to any one of Clauses 12 to 14 further includes selecting at least one group of UEs from the plurality of UEs based on one or more characteristics corresponding to the plurality of UEs, wherein each of the at least one group of UEs is associated with at least one common characteristic.

[0282] Clause 16: The method according to any one of Clauses 12 to 15, wherein: the storage includes storing the identifier of the UE in the database when the UE moves to an RRC idle state; determining that the UE has moved from the RRC idle state to an RRC connected state; and obtaining the identifier of the UE from the database when the UE moves to the RRC connected state.

[0283] Clause 17: The method according to any one of Clauses 12 to 16, wherein: the storage includes storing the identifier of the group or groups of UEs in the database when a UE in the group or groups of UEs moves to an RRC idle state; determining that the UE in the group or groups of UEs has moved from the RRC idle state to an RRC connected state; and obtaining the first identifier of the group or groups of UEs from the database when a UE in the group or groups of UEs has moved to the RRC connected state.

[0284] Clause 18: A method at a first node, the method comprising: sending a request to a second node to assign a persistent identifier to one or more user equipment (UEs); and receiving from the second node an indication of a first persistent identifier for the one or more UEs, wherein the first persistent identifier is applicable across multiple radio resource control (RRC) states corresponding to the one or more UEs.

[0285] Clause 19: The method according to Clause 18, wherein the first node includes a Service Management and Orchestration (SMO) or Non-Real-Time (RT) Radio Access Network (RAN) Intelligent Controller (RIC); the second node includes network element devices of a core network node; and the SMO or the non-RT RIC is interconnected with the network element devices via a Service-Based Architecture (SBA) interface.

[0286] Clause 20: The method according to Clause 19 further includes storing the first persistent identifier of the one or more UEs in a database associated with the second node.

[0287] Clause 21: An apparatus comprising: at least one memory including executable instructions; and one or more processors configured individually or collectively to execute the executable instructions and to cause the apparatus to perform a method according to any one of Clauses 1 to 20.

[0288] Clause 22: An apparatus comprising components for performing the method according to any one of Clauses 1 to 20.

[0289] Clause 23: A non-transitory computer-readable medium comprising executable instructions that, when executed by one or more processors of a device, cause the device to perform the method according to any one of Clauses 1 to 20.

[0290] Clause 24: A computer program product embodied on a computer-readable storage medium, said computer-readable storage medium including code for performing the method according to any one of Clauses 1 to 20.

[0291] Additional Notes

[0292] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, the function and arrangement of the elements discussed may be changed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in various examples. For example, the described methods may be performed in a different order than described, and various actions may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Moreover, the scope of this disclosure is intended to cover such apparatuses or methods practiced using other structures, functionalities, or structures and functionalities that complement or replace the various aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0293] The various exemplary logic blocks, modules, and circuits described in this disclosure can be implemented or executed using a general-purpose processor, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic device, discrete hardware component, or any combination thereof designed to perform the functions described herein. While the general-purpose processor may be a microprocessor, in alternative embodiments, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration.

[0294] As used herein, "processor," "at least one processor," or "one or more processors" generally refers to a single processor configured to perform one or more operations, or multiple processors configured to collectively perform one or more operations. In the case of multiple processors, the execution of one or more operations may be divided among different processors, but one processor may perform multiple operations, and multiple processors may collectively perform a single operation. Similarly, "memory," "at least one memory," or "one or more memory" generally refers to a single memory configured to store data and / or instructions, or multiple memories configured to collectively store data and / or instructions.

[0295] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. For example, A, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0296] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, lookup (e.g., searching in a table, database, or other data structure), assertion, etc. Furthermore, "determine" can include receiving (e.g., receiving information) and accessing (e.g., accessing data in memory). Additionally, "determine" can include parsing, selecting, picking, building, etc.

[0297] The methods disclosed herein include one or more actions for implementing the methods. These actions may be interchanged without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of a particular action may be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above may be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors.

[0298] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless specifically stated otherwise, reference to the singular form of an element is not intended to mean “one and only one,” but rather “one or more.” Unless otherwise specifically stated, the term “some” refers to one or more. No element of any claim shall be interpreted in accordance with 35 USC §112(f) unless that element is explicitly stated using the phrase “for a component of.” All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known to a person skilled in the art or will later be known are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly recited in the claims.

Claims

1. A first node, the first node comprising: At least one memory, said at least one memory comprising instructions; and One or more processors, individually or collectively configured to execute the instructions, and to cause the first node to: Send a request to the second node to assign a persistent identifier to the first plurality of UEs in one or more groups of user equipment (UEs); as well as The second node receives an indication of a first persistent identifier for the first plurality of UEs, wherein the first persistent identifier is applicable across a plurality of radio resource control (RRC) states corresponding to all UEs in the first plurality of UEs.

2. The first node according to claim 1, wherein: The first node includes a server associated with a next-generation (NG) radio access network (RAN); The second node includes the access and mobility management functions (AMF) of the core network node; The NG-RAN and the AMF are interconnected via the NG interface; and The first persistent identifier is a long-term reference for the first plurality of UEs.

3. The first node according to claim 1, wherein each of the first plurality of UEs is associated with at least one common characteristic.

4. The first node according to claim 1, wherein at least two or more of the first plurality of UEs are associated with at least one common characteristic.

5. The first node of claim 1, wherein the one or more processors are individually or jointly configured to execute the instructions and to cause the first node to select the first plurality of UEs from the plurality of UEs based at least on one or more characteristics corresponding to the plurality of UEs, wherein each of the first plurality of UEs is associated with at least one common characteristic.

6. The first node of claim 1, wherein the one or more processors are individually or jointly configured to execute the instructions and cause the first node to receive signaling from the second node instructing the first plurality of UEs, wherein each of the first plurality of UEs is associated with at least one common characteristic.

7. The first node of claim 1, wherein the one or more processors are individually or jointly configured to execute the instructions and cause the first node to store the first persistent identifier of the first plurality of UEs in a database.

8. The first node of claim 1, wherein the one or more processors are individually or jointly configured to execute the instructions and cause the first node to use the first persistent identifier of the first plurality of UEs to associate different measurements performed by one or more of the first plurality of UEs across different RRC states associated with the one or more of the first plurality of UEs.

9. The first node according to claim 1, wherein: The request is included in the initial context establishment request; and The initial context establishment request is used during the initial connection between the first node and at least one of the first plurality of UEs.

10. The first node according to claim 1, wherein: The first persistent identifier is assigned to the first plurality of UEs across different RRC states corresponding to each of the first plurality of UEs; and The different RRC states include at least the RRC connected state, the RRC inactive state, and the RRC idle state.

11. The first node of claim 1, wherein the one or more processors are individually or jointly configured to execute the instructions, and cause the first node to: It is determined that at least one of the first plurality of UEs has moved to the RRC idle state; and Based on the determination, a request is sent to the second node to store the first persistent identifier of the first plurality of UEs.

12. An Access and Mobility Management Function (AMF) for a core network node, the AMF comprising: At least one memory, said at least one memory comprising instructions; and One or more processors, individually or collectively configured to execute the instructions and enable the AMF of the core network node: A request is received from a server associated with a next-generation (NG) radio access network (RAN) to store an identifier of one or more user equipment (UE) sets or at least one of the UEs, wherein the identifier is assigned at the server associated with the NG-RAN; as well as The identifier is stored in the database associated with the AMF of the core network node, according to the request.

13. The AMF of the core network node according to claim 12, wherein the NG-RAN and the AMF of the core network node are interconnected via an NG interface.

14. The AMF of the core network node according to claim 12, wherein each of the one or more groups of UEs is associated with at least one common characteristic.

15. The AMF of the core network node according to claim 12, wherein the one or more processors are individually or jointly configured to execute the instructions and cause the AMF of the core network node to select at least one group of UEs from the plurality of UEs based on one or more characteristics corresponding to the plurality of UEs, wherein each UE in the at least one group of UEs is associated with at least one common characteristic.

16. The AMF of the core network node according to claim 12, wherein: The storage includes storing the UE's identifier in the database when the UE moves to an RRC idle state; The one or more processors are individually or jointly configured to execute the instructions and cause the AMF of the core network node to determine that the UE has moved from the RRC idle state to the RRC connected state; and The one or more processors are individually or collectively configured to execute the instructions and cause the AMF of the core network node to obtain the UE's identifier from the database when the UE moves to the RRC connection state.

17. The AMF of the core network node according to claim 12, wherein: The storage includes storing the identifiers of the group or groups of UEs in the database when a UE in one or more groups of UEs moves to an RRC idle state; The one or more processors are individually or collectively configured to execute the instructions and cause the AMF of the core network node to determine that the UE in the one or more groups of UEs has moved from the RRC idle state to the RRC connected state; and The one or more processors are individually or collectively configured to execute the instructions and cause the AMF of the core network node to obtain the first identifier of the group or more UEs from the database when the UE in the group or more UEs has moved to the RRC connection state.

18. A first node, the first node comprising: At least one memory, said at least one memory comprising instructions; and One or more processors, individually or collectively configured to execute the instructions, and to cause the first node to: Send a request to the second node to assign a persistent identifier for one or more user equipment (UEs); as well as The second node receives an indication of a first persistent identifier for the one or more UEs, wherein the first persistent identifier is applicable across multiple Radio Resource Control (RRC) states corresponding to the one or more UEs.

19. The first node according to claim 18, wherein: The first node includes a Service Management and Orchestration (SMO) or Non-Real-Time (RT) Radio Access Network (RAN) Intelligent Controller (RIC). The second node includes network component devices of the core network node; and The SMO or the non-RT RIC is interconnected with the network element device via a service-based architecture (SBA) interface.

20. The first node of claim 19, wherein the one or more processors are individually or jointly configured to execute the instructions and cause the first node to store the first persistent identifier of the one or more UEs in a database associated with the second node.

21. A non-real-time (RT) radio access network (RAN) intelligent controller (RIC), the non-real-time (RT) radio access network (RAN) intelligent controller (RIC) comprising: At least one memory, said at least one memory comprising instructions; and One or more processors, individually or in any combination, are configured to execute the instructions, and enable the non-RT RIC to: Send a request to the network element device of the core network node to allocate a temporary identifier for the user equipment (UE); as well as The network element device receives an indication of a first temporary identifier for the UE, wherein the first temporary identifier is based on the UE's first identifier and wherein the first temporary identifier is persistent across multiple Radio Resource Control (RRC) states corresponding to the UE.

22. The non-RT RIC of claim 21, wherein the non-RT RIC and the network element device are interconnected via a service-based architecture (SBA) interface.

23. The non-RT RIC of claim 21, wherein the request includes a RAN-based identifier of the UE.

24. The non-RT RIC of claim 21, wherein the one or more processors are further configured individually or in any combination to execute the instructions, and the non-RT RIC sends an indication of the first temporary identifier to the near-RT RIC via an A1 interface.

25. The non-RT RIC of claim 21, wherein the one or more processors are further configured individually or in any combination to execute the instructions, and the non-RT RIC: Receive a message requesting a temporary identifier for the UE from the near-RT RIC, wherein the message also includes the UE's RAN-based identifier; and In response to the message, the first temporary identifier is sent to the near RT RIC, wherein the first temporary identifier is based on the RAN-based identifier.

26. A network element device for a core network node, the network element device comprising: At least one memory, said at least one memory comprising instructions; and One or more processors, individually or in any combination, are configured to execute the instructions and cause the network element device to: Receive a request from the non-real-time (RT) radio access network (RAN) intelligent controller (RIC) to assign a temporary identifier to the user equipment (UE); as well as Send an indication of a first temporary identifier for the UE to the non-RT RIC, wherein the first temporary identifier is based on the UE's first identifier and wherein the first temporary identifier is persistent across multiple Radio Resource Control (RRC) states corresponding to the UE.

27. The network element device of claim 26, wherein the non-RT RIC and the network element device are interconnected via a service-based architecture (SBA) interface.

28. The network element device of claim 26, wherein the request includes an identifier of the UE based on a radio access network (RAN).

29. A near real-time (RT) radio access network (RAN) intelligent controller (RIC), the near real-time (RT) radio access network (RAN) intelligent controller (RIC) comprising: At least one memory, said at least one memory comprising instructions; and One or more processors, individually or in any combination, are configured to execute the instructions, and enable the near-RT RIC: Send a subscription message to a network entity to receive user equipment (UE) data, the user equipment (UE) data including one or more tunnel endpoint (TE) identifiers associated with the UE; as well as In response to the subscription message, at least one first TE identifier associated with the first identifier of the UE is received from the network entity.

30. The near-RT RIC of claim 29, wherein the one or more processors are further configured individually or in any combination to execute the instructions and cause the near-RT RIC to receive from the network entity at least one second TE identifier associated with the second identifier of the UE.

31. The near-RT RIC of claim 30, wherein the one or more processors are further configured individually or in any combination to execute the instructions and to cause the near-RT RIC to: determine that the at least one first TE identifier and the at least one second TE identifier are associated with the same UE when the at least one first TE identifier matches the at least one second TE identifier.

32. A non-real-time (RT) radio access network (RAN) intelligent controller (RIC), the non-real-time (RT) radio access network (RAN) intelligent controller (RIC) comprising: At least one memory, said at least one memory comprising instructions; and One or more processors, individually or in any combination, are configured to execute the instructions, and enable the non-RT RIC to: Receive one or more permanent identifiers associated with the user equipment (UE) from the core network node; as well as Send one or more temporary identifiers to the near RT RIC, wherein the one or more temporary identifiers are based on the one or more permanent identifiers.

33. The non-RT RIC of claim 32, wherein the non-RT RIC is configured as a management data analysis function in the Operation, Administration and Maintenance (OAM) layer.

34. The non-RT RIC of claim 32, wherein the one or more permanent identifiers include at least one of the following: Subscription Permanent Identifier (SUPI) or International Mobile Subscriber Identity (IMSI).

35. The non-RT RIC of claim 32, wherein the one or more processors are further configured individually or in any combination to execute the instructions, and the non-RT RIC: Convert the one or more permanent identifiers into the one or more temporary identifiers; Receive requests for the one or more temporary identifiers from the nearby RT RIC; as well as In response to the request, an indication for the one or more temporary identifiers is sent to the near-RT RIC.

Images