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. The first node transmits a request to allocate a persistent identifier for a first plurality of user equipments (UEs) of one or more groups of UEs to a second node. The first node receives an indication of a first persistent identifier for the first plurality of UEs from the second node. The first persistent identifier is persistent across multiple radio resource control (RRC) states corresponding to at least one UE within the first plurality of UEs.

Description

USER EQUIPMENT (UE) IDENTIFIER IN OPEN RADIO ACCESS NETWORK (O-RAN)BACKGROUNDCross-reference to related applications

[0001] This application claims benefit of and priority to Greek Patent Application No. 20230100703, filed August 30, 2023 and Greek Patent Application No. 20230101075, filed December 22, 2023, which are hereby incorporated by reference in their entireties.Field of the Disclosure

[0002] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for allocating user equipment (UE) identifiers in open radio access network (O-RAN).Description of Related Art

[0003] Wireless communications systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, or other similar types of services. These wireless communications systems may employ multiple-access technologies capable of supporting communications with multiple users by sharing available wireless communications system resources with those users.

[0004] Although wireless communications systems have made great technological advancements over many years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Accordingly, there is a continuous desire to improve the technical performance of wireless communications systems, including, for example: improving speed and data carrying capacity of communications, improving efficiency of the use of shared communications mediums, reducing power used by transmitters and receivers while performing communications, improving reliability of wireless communications, avoiding redundant transmissions and / or receptions and related processing, improving the coverage area of wireless communications, increasing the number and types of devices that can access wireless communications systems, increasing the ability for different types of devices to intercommunicate, increasing the number and type of wireless communications mediums available for use, and the like. Consequently, there exists aneed for further improvements in wireless communications systems to overcome the aforementioned technical challenges and others.SUMMARY

[0005] One aspect provides a method at a first node, comprising: transmitting, to a second node, a request to allocate a persistent identifier for a user equipment (UE); and receiving an indication of a first persistent identifier for the UE from the second node, 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.

[0006] Another aspect provides a method at a first node, comprising: receiving a request to allocate a persistent identifier for a UE from a second node; and transmitting an indication of a first persistent identifier for the UE to the second node, 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.

[0007] Another aspect provides a method at a near-real time (RT) radio access network (RAN) intelligent controller (RIC), comprising: transmitting, to a network entity, a subscription message to receive UE data comprising one or more tunnel endpoint (TE) identifiers associated with a UE; and receiving at least one first TE identifier associated with a first identifier of the UE, from the network entity, in response to the subscription message.

[0008] Another aspect provides a method at a non-RT RIC, comprising: receiving, from a core network node, one or more permanent identifiers associated with a UE; and transmitting one or more persistent identifiers to a near-RT RIC, wherein the one or more persistent identifiers are based on the one or more permanent identifiers.

[0009] Another aspect provides a method at a first node, comprising: transmitting a request to allocate a persistent identifier for a first plurality of UEs of one or more groups of UEs to a second node; and receiving an indication of a first persistent identifier for the first plurality of UEs from the second node, wherein the first persistent identifier is persistent or applicable across multiple RRC states corresponding to all UEs within the first plurality of UEs.

[0010] Another aspect provides a method at an access and mobility management function (AMF) of a core network node, comprising: receiving a request to store an identifier for at least one of a UE or one or more groups of UEs from a server associated with a next generation (NG) - RAN, wherein the identifier is allocated at the server associated with the NG-RAN; and storing the identifier in a database associated with the AMF of the core network node, in accordance with the request.

[0011] Another aspect provides a method at a first node, comprising: transmitting a request to allocate a persistent identifier for one or more UEs to a second node; and receiving an indication of a first persistent identifier for the one or more UEs from the second node, wherein the first persistent identifier is persistent or applicable across multiple RRC states corresponding to the one or more UEs.

[0012] Other aspects provide: an apparatus operable, configured, or otherwise adapted to perform the aforementioned methods as well as those described elsewhere herein; a non-transitory, computer-readable media comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform the aforementioned methods as well as those described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising code for performing the aforementioned methods as well as those described elsewhere herein; and an apparatus comprising means for performing the aforementioned methods as well as those described elsewhere herein. By way of example, an apparatus may comprise a processing system, a device with a processing system, or processing systems cooperating over one or more networks.

[0013] The following description and the appended figures set forth certain features for purposes of illustration.BRIEF DESCRIPTION OF DRAWINGS

[0014] The appended figures depict certain features of the various aspects described herein and are not to be considered limiting of the scope of this disclosure.

[0015] FIG. 1 depicts an example wireless communications network.

[0016] FIG. 2 depicts an example disaggregated base station (BS) architecture.

[0017] FIG. 3 depicts aspects of an example BS and an example user equipment (UE).

[0018] FIG. 4A, FIG. 4B, FIG. 4C, and FIG. 4D depict various example aspects of data structures for a wireless communications network.

[0019] FIG. 5 depicts another example disaggregated BS architecture.

[0020] FIG. 6A depicts example components of a disaggregated BS architecture.

[0021] FIG. 6B depicts a call flow diagram illustrating example communication among the components of the disaggregated BS architecture.

[0022] FIG. 7A depicts example components of another disaggregated BS architecture.

[0023] FIG. 7B and FIG. 7C depict call flow diagrams illustrating example communication among the components of the disaggregated BS architecture.

[0024] FIG. 8 depicts a call flow diagram illustrating example communication among a UE, a gNodeB (gNB), an access and mobility management function (AMF), and a session management function (SMF) / user plane function (UPF).

[0025] FIG. 9 depicts a call flow diagram illustrating example communication among a UE, a gNB, and a near-real time (RT) radio access network (RAN) intelligent controller (RIC).

[0026] FIG. 10A depicts example components of another disaggregated BS architecture.

[0027] FIG. 10B depicts a call flow diagram illustrating example communication among the components of the disaggregated BS architecture.

[0028] FIG. 11 and FIG. 12 depict methods at a first node.

[0029] FIG. 13 depicts a method at a near-RT RIC.

[0030] FIG. 14 depicts a method at a non-RT RIC.

[0031] FIG. 15 depicts example communications device.DETAILED DESCRIPTION

[0032] An open radio access network (O-RAN) generally refers to a nonproprietary version of a radio access network (RAN) system that allows interoperation between cellular network equipment provided by different vendors. An O-RAN is implemented using a disaggregated base station (BS) architecture.

[0033] The disaggregated BS architecture may include one or more central units (CUs) that can communicate directly with a core network. This communication with the core network may be via a backhaul link, or indirectly with the core network through one or more disaggregated 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). The CU may communicate with one or more distributed units (DUs) via respective midhaul links, such as an Fl interface. The DUs may communicate with one or more radio units (RUs) via respective fronthaul links. The RUs may communicate with user equipments (UEs) via one or more radio frequency (RF) access links. Each of the units, e.g., the CUs, the DUs, the RUs, as well as the near-RT RICs, the non-RT RICs and the SMO framework, may include one or more interfaces or be coupled to the one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium.

[0034] The O-RAN may be used for several use cases, which may require a UE identifier to identify a specific UE. For example, some use cases which target optimizing services for the UE may need to identify the UE using some type of the UE identifier. These use cases may include, for example, training artificial intelligence / machine learning (AI / ML) systems to generate AI / ML based optimizations.

[0035] The O-RAN may include some interfaces (such as E2 and 01 interfaces) with the RAN. Hence, UE identifiers of the UE which are available at the RAN are visible to the O-RAN. Unfortunately, the UE identifiers in the RAN are short lived and are applicable as long as the UE stays in a radio resource control (RRC) connected state. For example, when the UE goes to an RRC idle state from the RRC connected state, the UE identifiers become invalid and the UE is then not recognizable in the RAN. This restriction associated with the UE identifiers in the RAN is applicable for the O-RAN as well, since the O-RAN receives data from the RAN. Accordingly, presently the RAN / 0- RAN does not have any UE identifiers to identify the UE across the different RRC state transitions.

[0036] Since some use cases have a requirement to identify and correlate different UE measurements performed by the UE in the RRC connected state and the RRC idle state, a UE identifier (e.g., a persistent UE identifier) for the UE may be needed. This UE identifier can be used to identify the UE (and its data) across the RRC state transitions.

[0037] Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable mediums for allocating UE identifiers to the UE in the 0-RAN. For example, in the 0-RAN, a RAN node may request an access and mobility management function (AMF) of a core network node to allocate a persistent UE identifier for the UE (or a group of UEs), which can be used to identify the UE / the group of UEs (and their data) across the RRC state transitions. The AMF then allocates and sends the persistent UE identifier for the UE / the group of UEs to the RAN node. In some cases, the persistent UE identifier (e.g., that may stay same across different RRC states) may be a unique long-lasting reference (e.g., which can be used to identify the UE / the group of UEs).

[0038] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, the described techniques can be used to improve AI / ML based training and optimizations of the UE in 0-RAN systems (e.g., by being able to collect and use different UE measurements performed by the UE in the RRC connected state and the RRC idle state for the AI / ML based training, based on the persistent UE identifier for the UE).Introduction to Wireless Communications Networks

[0039] The techniques and methods described herein may be used for various wireless communications networks. While aspects may be described herein using terminology commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of the present disclosure may likewise be applicable to other communications systems and standards not explicitly mentioned herein.

[0040] FIG. 1 depicts an example of a wireless communications network 100, in which aspects described herein may be implemented.

[0041] Generally, wireless communications network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is generally a communications device and / or a communications function performed by a communications device (e.g., a user equipment (UE), a base station (BS), a component of a BS, a server, etc.). For example, various functions of a network as well as various devices associated with and interacting with a network may be considered network entities. Further, wireless communications network 100 includes terrestrial aspects, such as ground-based network entities (e.g., BSs 102), and non-terrestrial aspects, such assatellite 140 and aircraft 145, which may include network entities on-board (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and UEs.

[0042] In the depicted example, wireless communications network 100 includes BSs 102, UEs 104, and one or more core networks, such as an Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190, which interoperate to provide communications services over various communications links, including wired and wireless links.

[0043] FIG. 1 depicts various example UEs 104, which may more generally include: a cellular phone, smart phone, session initiation protocol (SIP) phone, laptop, personal digital assistant (PDA), satellite radio, global positioning system, multimedia device, video device, digital audio player, camera, game console, tablet, smart device, wearable device, vehicle, electric meter, gas pump, large or small kitchen appliance, healthcare device, implant, sensor / actuator, display, internet of things (loT) devices, always on (AON) devices, edge processing devices, or other similar devices. UEs 104 may also be referred to more generally as a mobile device, a wireless device, a wireless communications device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and others.

[0044] BSs 102 wirelessly communicate with (e.g., transmit signals to or receive signals from) UEs 104 via communications links 120. The communications links 120 between BSs 102 and UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a BS 102 and / or downlink (DL) (also referred to as forward link) transmissions from a BS 102 to a UE 104. The communications links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity in various aspects.

[0045] BSs 102 may generally include: a NodeB, enhanced NodeB (eNB), next generation enhanced NodeB (ng-eNB), next generation NodeB (gNB or gNodeB), access point, base transceiver station, radio BS, radio transceiver, transceiver function, transmission reception point, and / or others. Each of BSs 102 may provide communications coverage for a respective geographic coverage area 110, which may sometimes be referred to as a cell, and which may overlap in some cases (e.g., small cell102’ may have a coverage area 110’ that overlaps the coverage area 110 of a macro cell). A BS may, for example, provide communications coverage for a macro cell (covering relatively large geographic area), a pico cell (covering relatively smaller geographic area, such as a sports stadium), a femto cell (relatively smaller geographic area (e.g., a home)), and / or other types of cells.

[0046] While BSs 102 are depicted in various aspects as unitary communications devices, BSs 102 may be implemented in various configurations. For example, one or more components of a BS 102 may be disaggregated, including a central unit (CU), one or more distributed units (DUs), one or more radio units (RUs), a Near-Real Time (Near- RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, to name a few examples. In another example, various aspects of a BS 102 may be virtualized. More generally, a BS (e.g., BS 102) may include components that are located at a single physical location or components located at various physical locations. In examples in which a BS 102 includes components that are located at various physical locations, the various components may each perform functions such that, collectively, the various components achieve functionality that is similar to a BS 102 that is located at a single physical location. In some aspects, a BS 102 including components that are located at various physical locations may be referred to as a disaggregated radio access network (RAN) architecture, such as an Open RAN (O-RAN) or Virtualized RAN (VRAN) architecture. FIG. 2 depicts and describes an example disaggregated BS architecture.

[0047] Different BSs 102 within wireless communications network 100 may also be configured to support different radio access technologies, such as 3G, 4G, and / or 5G. For example, BSs 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E- UTRAN)) may interface with the EPC 160 through first backhaul links 132 (e.g., an SI interface). BSs 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) may interface with 5GC 190 through second backhaul links 184. BSs 102 may communicate directly or indirectly (e.g., through the EPC 160 or 5GC 190) with each other over third backhaul links 134 (e.g., X2 interface), which may be wired or wireless.

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

[0049] The communications links 120 between BSs 102 and, for example, UEs 104, may be through one or more carriers, which may have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and / or other MHz), and which may be aggregated in various aspects. Carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL).

[0050] Communications using higher frequency bands may have higher path loss and a shorter range compared to lower frequency communications. Accordingly, certain BSs (e.g., 180 in FIG. 1) may utilize beamforming 182 with a UE 104 to improve path loss and range. For example, BS 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and / or antenna arrays to facilitate the beamforming. In some cases, BS 180 may transmit a beamformed signal to UE 104 in one or more transmit directions 182’. UE 104 may receive the beamformed signal from the BS 180 in one or more receive directions 182”. UE 104 may also transmit a beamformed signal to the BS 180 in one or more transmit directions 182”. BS 180 may also receive the beamformed signal from UE 104 in one or more receive directions 182’. BS 180 and UE 104 may then perform beam training to determine the best receive and transmit directions for each of BS 180 and UE 104. Notably, the transmit and receive directions for BS 180 may or may not be the same. Similarly, the transmit and receive directions for UE 104 may or may not be the same.

[0051] Wireless communications network 100 further includes a Wi-Fi AP 150 in communication with Wi-Fi stations (STAs) 152 via communications links 154 in, for example, a 2.4 GHz and / or 5 GHz unlicensed frequency spectrum.

[0052] Certain UEs 104 may communicate with each other using device-to-device (D2D) communications link 158. D2D communications link 158 may use one or moresidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

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

[0054] Generally, user Internet protocol (IP) packets are transferred through Serving Gateway 166, which itself is connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation as well as other functions. PDN Gateway 172 and the BM-SC 170 are connected to IP Services 176, which may include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) streaming service, and / or other IP services.

[0055] BM-SC 170 may provide functions for MBMS user service provisioning and delivery. BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and / or may be used to schedule MBMS transmissions. MBMS Gateway 168 may be used to distribute MBMS traffic to the BSs 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and / or may be responsible for session management (start / stop) and for collecting eMBMS related charging information.

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

[0057] AMF 192 is a control node that processes signaling between UEs 104 and 5GC190. AMF 192 provides, for example, quality of service (QoS) flow and session management.

[0058] Internet protocol (IP) packets are transferred through UPF 195, which is connected to the IP Services 197, and which provides UE IP address allocation as well as other functions for 5GC 190. IP Services 197 may include, for example, the Internet, an intranet, an IMS, a PS streaming service, and / or other IP services.

[0059] Wireless communication network 100 further includes identifier (ID) component 198. Wireless communication network 100 further includes ID component 199, which may be configured to perform method 1100 of FIG. 11, method 1200 of FIG. 12, method 1300 of FIG. 13, and / or method 1400 of FIG. 14.

[0060] In various aspects, a network entity or network node can be implemented as an aggregated BS, as a disaggregated BS, a component of a BS, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.

[0061] FIG. 2 depicts an example disaggregated BS 200 architecture. The disaggregated BS 200 architecture may include one or more central units (CUs) 210 that can communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated 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). A CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an Fl interface. The DUs 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RUs 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 240.

[0062] Each of the units, e.g., the CUs 210, the DUs 230, the RUs 240, as well as the Near-RT RICs 225, the Non-RT RICs 215 and the SMO Framework 205, may include one or more interfaces 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 the units, or an associated processor or controller providing instructions to the communications interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally oralternatively, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a radio frequency (RF) transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0063] In some aspects, the CU 210 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 210. The CU 210 may be configured to handle user plane functionality (e.g., Central Unit - User Plane (CU-UP)), control plane functionality (e.g., Central Unit - Control Plane (CU-CP)), or a combination 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. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the El interface when implemented in an 0-RAN configuration. The CU 210 can be implemented to communicate with the DU 230, as necessary, for network control and signaling.

[0064] The DU 230 may correspond to a logical unit that includes one or more BS functions to control the operation of one or more RUs 240. In some aspects, the DU 230 may host one or more of a radio link control (RLC) layer, a 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, or the like) depending, at least in part, on a functional split, such as those defined by the 3rdGeneration Partnership Project (3GPP). In some aspects, the DU 230 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 230, or with the control functions hosted by the CU 210.

[0065] Lower-layer functionality can be implemented by one or more RUs 240. In some deployments, an RU 240, 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 the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 240 can be implemented to handle over the air (OTA) communications withone or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU(s) 240 can be controlled by the corresponding DU 230. In some scenarios, this configuration can enable the DU(s) 230 and the CU 210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0066] The SMO Framework 205 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an 01 interface). For virtualized network elements, the SMO Framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 210, DUs 230, RUs 240 and Near-RT RICs 225. In some implementations, the SMO Framework 205 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 211, via an 01 interface. Additionally, in some implementations, the SMO Framework 205 can communicate directly with one or more RUs 240 via an 01 interface. The SMO Framework 205 also may include a Non-RT RIC 215 configured to support functionality of the SMO Framework 205.

[0067] The Non-RT RIC 215 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy -based guidance of applications / features in the Near-RT RIC 225. The Non-RT RIC 215 may be coupled to or communicate with (such as via an Al interface) the Near-RT RIC 225. The Near-RT RIC 225 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 210, one or more DUs 230, or both, as well as an O-eNB, with the Near-RT RIC 225.

[0068] 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 enrichmentinformation from external servers. Such information may be utilized by the Near-RT RIC 225 and may be received at the SMO Framework 205 or the Non-RT RIC 215 from nonnetwork data sources or from network functions. 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 for performance and employ AI / ML models to perform corrective actions through the SMO Framework 205 (such as reconfiguration via 01) or via creation of RAN management policies (such as Al policies).

[0069] FIG. 3 depicts aspects of an example BS 102 and a UE 104.

[0070] Generally, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-t (collectively 334), transceivers 332a-t (collectively 332), which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS 102 may send and receive data between BS 102 and UE 104. BS 102 includes controller / processor 340, which may be configured to implement various functions described herein related to wireless communications.

[0071] BS 102 includes controller / processor 340, which may be configured to implement various functions related to wireless communications. In the depicted example, controller / processor 340 includes ID component 341, which may be representative of ID component 199 of FIG. 1. Notably, while depicted as an aspect of controller / processor 340, ID component 341 may be implemented additionally or alternatively in various other aspects of BS 102 in other implementations.

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

[0073] UE 104 includes controller / processor 380, which may be configured to implement various functions related to wireless communications. In the depicted example, controller / processor 380 includes ID component 381, which may be representative of ID component 198 of FIG. 1. Notably, while depicted as an aspect ofcontroller / processor 380, ID component 381 may be implemented additionally or alternatively in various other aspects of UE 104 in other implementations.

[0074] In regards to an example downlink transmission, BS 102 includes a transmit processor 320 that may receive data from a data source 312 and control information from a controller / processor 340. The control information may be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical HARQ indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC PDCCH), and / or others. The data may be for the physical downlink shared channel (PDSCH), in some examples.

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

[0076] Transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and / or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) in transceivers 332a-332t. Each modulator in transceivers 332a- 332t may process a respective output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from the modulators in transceivers 332a-332t may be transmitted via the antennas 334a-334t, respectively.

[0077] In order to receive the downlink transmission, UE 104 includes antennas 352a- 352r that may receive the downlink signals from the BS 102 and may provide received signals to the demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples to obtain received symbols.

[0078] MIMO detector 356 may obtain received symbols from all the demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols ifapplicable, and provide detected symbols. Receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.

[0079] In regards to an example uplink transmission, UE 104 further includes a transmit processor 364 that may receive and process data (e.g., for the PUSCH) from a data source 362 and control information (e.g., for the physical uplink control channel (PUCCH)) from the controller / processor 380. Transmit processor 364 may also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS)). The symbols from the transmit processor 364 may be precoded by a TX MIMO processor 366 if applicable, further processed by the modulators in transceivers 354a-354r (e.g., for SC-FDM), and transmitted to BS 102.

[0080] At BS 102, the uplink signals from UE 104 may be received by antennas 334a- t, processed by the demodulators in transceivers 332a-332t, detected by a MIMO detector 336 if applicable, and further processed by a receive processor 338 to obtain decoded data and control information sent by UE 104. Receive processor 338 may provide the decoded data to a data sink 339 and the decoded control information to the controller / processor 340.

[0081] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.

[0082] Scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

[0083] In various aspects, BS 102 may be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms of outputting data, such as outputting data from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceivers 332a-t, antenna 334a-t, and / or other aspects described herein. Similarly, “receiving” may refer to various mechanisms of obtaining data, such as obtaining data from antennas 334a-t, transceivers 332a-t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.

[0084] In various aspects, UE 104 may likewise be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms of outputting data, such as outputting data from data source 362, memory 382, transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a-t, antenna 352a-t, and / or other aspects described herein. Similarly, “receiving” may refer to various mechanisms of obtaining data, such as obtaining data from antennas 352a-t, transceivers 354a-t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, and / or other aspects described herein.

[0085] In some aspects, a processor may be configured to perform various operations, such as those associated with the methods described herein, and transmit (output) to or receive (obtain) data from another interface that is configured to transmit or receive, respectively, the data.

[0086] FIG. 4A, FIG. 4B, FIG. 4C, and FIG. 4D depict aspects of data structures for a wireless communications network, such as wireless communications network 100 of FIG. 1.

[0087] In particular, FIG. 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5GNR) frame structure, FIG. 4B is a diagram 430 illustrating an example of DL channels within a 5G subframe, FIG. 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and FIG. 4D is a diagram 480 illustrating an example of UL channels within a 5G subframe.

[0088] Wireless communications systems may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. Such systems may also support half-duplex operation using time division duplexing (TDD). OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth (e.g., as depicted in FIG. 4B and FIG. 4D) into multiple orthogonal subcarriers. Each subcarrier may be modulated with data. Modulation symbols may be sent in the frequency domain with OFDM and / or in the time domain with SC-FDM.

[0089] A wireless communications frame structure may be frequency division duplex (FDD), in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for either DL or UL. Wireless communications frame structures may alsobe time division duplex (TDD), in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for both DL and UL.

[0090] In FIG. 4A and 4C, the wireless communications frame structure is TDD where D is DL, U is UL, and X is flexible for use between DL / UL. UEs may be configured with a slot format through a received slot format indicator (SFI) (dynamically through DL control information (DCI), or semi-statically / statically through radio resource control (RRC) signaling). In the depicted examples, a 10 ms frame is divided into 10 equally sized 1 ms subframes. Each subframe may include one or more time slots. In some examples, each slot may include 7 or 14 symbols, depending on the slot format. Subframes may also include mini-slots, which generally have fewer symbols than an entire slot. Other wireless communications technologies may have a different frame structure and / or different channels.

[0091] In certain aspects, the number of slots within a subframe is based on a slot configuration and a numerology. For example, for slot configuration 0, different numerol ogies (p) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 slots, respectively, per subframe. For slot configuration 1, different numerol ogies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology p, there are 14 symbols / slot and 2p slots / subframe. The subcarrier spacing and symbol length / duration are a function of the numerology. The subcarrier spacing may be equal to 2^ X 15 kHz, where p is the numerology 0 to 5. As such, the numerology p = 0 has a subcarrier spacing of 15 kHz and the numerology p = 5 has a subcarrier spacing of 480 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 4A, FIG. 4B, FIG. 4C, and FIG. 4D provide an example of slot configuration 0 with 14 symbols per slot and numerology p = 2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 ps.

[0092] As depicted in FIG. 4A, FIG. 4B, FIG. 4C, and FIG. 4D, a resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends, 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.

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

[0094] FIG. 4B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including, for example, nine RE groups (REGs), each REG including, for example, four consecutive REs in an OFDM symbol.

[0095] A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE (e.g., 104 of FIG. 1 and FIG. 3) to determine subframe / symbol timing and a physical layer identity.

[0096] A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing.

[0097] Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the aforementioned DMRS. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs), and / or paging messages.

[0098] As illustrated in FIG. 4C, some of the REs carry DMRS (indicated as R for one particular configuration, but other DMRS configurations are possible) for channel estimation at the BS. The UE may transmit DMRS for the PUCCH and DMRS for the PUSCH. The PUSCH DMRS may be transmitted, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. UE 104 may transmit sounding reference signals (SRS). The SRS may be transmitted, for example, in the last symbol ofa subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a BS for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0099] FIG. 4D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.Introduction to mmWave Wireless Communications

[0100] In wireless communications, an electromagnetic spectrum is often subdivided into various classes, bands, channels, or other features. The subdivision is often provided based on wavelength and frequency, where frequency may also be referred to as a carrier, a subcarrier, a frequency channel, a tone, or a subband.

[0101] 5thgeneration (5G) networks may utilize several frequency ranges, which in some cases are defined by a standard, such as 3rd generation partnership project (3GPP) standards. For example, 3GPP technical standard TS 38.101 currently defines Frequency Range 1 (FR1) as including 600 MHz - 6 GHz, though specific uplink and downlink allocations may fall outside of this general range. Thus, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band.

[0102] Similarly, TS 38.101 currently defines Frequency Range 2 (FR2) as including 26 - 41 GHz, though again specific uplink and downlink allocations may fall outside of this general range. FR2, is sometimes referred to (interchangeably) as a “millimeter wave” (“mmW” or “mmWave”) band, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) that is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band because wavelengths at these frequencies are between 1 millimeter and 10 millimeters.

[0103] Communications using mmWave / near mmWave radio frequency band (e.g., 3 GHz - 300 GHz) may have higher path loss and a shorter range compared to lower frequency communications. As described above with respect to FIG. 1, a base station (BS) (e.g., 180) configured to communicate using mmWave / near mmWave radiofrequency bands may utilize beamforming (e.g., 182) with a user equipment (UE) (e.g., 104) to improve path loss and range.Overview Of Open Radio Access Network (O-RAN)

[0104] FIG. 5 depicts an example open radio access network (O-RAN) including disaggregated base station (BS) 500 architecture. As depicted in FIG. 5 and noted above, the disaggregated BS 500 architecture may include one or more central units (CUs) that can communicate directly with a core network via a backhaul link, or indirectly with the core network through one or more disaggregated 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).

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

[0106] The CU may communicate with one or more distributed units (DUs) via respective midhaul links, such as an Fl interface. The DUs may communicate with one or more radio units (RUs) via respective fronthaul links. The RUs may communicate with UEs via one or more radio frequency (RF) access links.

[0107] Each of the units, e.g., the CUs, the DUs, the RUs, as well as the near-RT RICs, the non-RT RICs and the SMO framework, may include one or more interfaces or be coupled to the one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium.

[0108] The non-RT RIC may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the near-RT RIC.

[0109] The O-RAN may be used for several use cases, which may require a UE identifier to identify a specific UE. For example, some use cases which target optimizing services for the UE may need to identify the UE using some type of the UE identifier.These use cases may include, for example, training artificial intelligence / machine learning (AI / ML) systems to generate AI / ML based optimizations.

[0110] The 0-RAN may include some interfaces (such as E2 and 01 interfaces) with the RAN. Hence, UE identifiers of the UE which are available at the RAN are visible to the 0-RAN. Unfortunately, the UE identifiers in the RAN are short lived and are applicable as long as the UE stays in an RRC connected state. For example, when the UE goes to an RRC idle state from the RRC connected state, the UE identifiers become invalid and the UE is then not recognizable in the RAN. This same restriction associated with the UE identifiers is applicable for the 0-RAN as well, since the 0-RAN receives data from the RAN.[OHl] Since the 0-RAN does not have any interface / communication with the core network, the 0-RAN is also unable to leverage or access the permanent UE identifier for UE-specific AI / ML optimization.

[0112] In some cases, the 0-RAN may use all available UE identifiers of the UE in the RAN to correlate a report from different nodes associated with the UE and provide UE-specific AI / ML based optimizations based on the report. However, as noted above, the UE identifiers in the RAN are valid as long as the UE remains in the RRC connected state and the UE identifiers in the RAN become invalid once the UE goes to the RRC idle state. When the UE identifiers become invalid, the UE is not identifiable in the RAN (as well as the 0-RAN). Accordingly, presently the RAN / O-RAN does not have any UE identifiers to identify the UE across the RRC state transitions.

[0113] Since some use cases have a requirement to identify and correlate different UE measurements performed by the UE in the RRC connected state and the RRC idle state, a temporary UE identifier for the UE may be needed. This temporary UE identifier can be used to identify the UE (and its data) across the RRC state transitions.Aspects Related To User Equipment (UE) Identifiers In Open Radio Access Network (0-RAN)

[0114] Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable mediums for allocating user equipment (UE) identifiers to a UE in open radio access network (0-RAN). For example, in the 0-RAN, a server associated with a radio access network (RAN) may request an access and mobility management function (AMF) of a core network node to allocate a temporary UE identifieror a persistent UE identifier for 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 allocates and sends the temporary UE identifier or the persistent UE identifier for the UE (or the group of UEs) to the server. In some cases, the persistent UE identifier may be a unique long-lasting reference (e.g., using a string of letters and numbers) which can be used to identify the UE / the group of UEs, in comparison to the temporary UE identifier for the UE / the group of UEs.

[0115] The techniques proposed herein for allocating the UE identifiers in the 0-RAN may be understood with reference to FIG. 6 A - FIG. 15.

[0116] FIG. 6A depicts example components of a disaggregated base station (BS) 600 architecture. The disaggregated BS 600 architecture may include one or more central units (CUs) (not shown) that can communicate directly with a core network 610. This communication with the core network may be, for example, via a backhaul link or indirectly with the core network 610 through one or more disaggregated 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.

[0117] Each of the 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 the units, or an associated processor or controller providing instructions to the communications interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally or alternatively, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a radio frequency (RF) transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0118] For example, as depicted in FIG. 6 A, the core network 610 and the NG-RAN 615 may communicate or are associated to each other via NG interface. The NG-RAN 615 and the near-RT RIC 620 may communicate or are associated to each other via E2interface. The near-RT RIC 620 and the non-RT RIC 625 may communicate or are associated to each other via Al interface.

[0119] FIG. 6B depicts a call flow diagram illustrating example communication among the core network 610, the NG-RAN 615, the near-RT RIC 620 and a UE 628. The core network 610 shown in FIG. 6B may be an example of the core network 220 depicted and described with respect to FIG. 2. The NG-RAN 615 shown in FIG. 6B may be an example of the BS 102 depicted and described with respect to FIG. 1 and FIG. 3. The near-RT RIC 620 shown in FIG. 6B may be an example of the near-RT RIC 225 depicted and described with respect to FIG. 2. The UE 628 shown in FIG. 6B may be an example of the UE 104 depicted and described with respect to FIG. 1 and FIG. 3.

[0120] As indicated at 630, the near-RT RIC 620 subscribes with the NG-RAN 615 for receiving a UE identifier (e.g., a temporary UE identifier) of the UE 628.

[0121] In some cases, the near-RT RIC 620 may also subscribe with (to) the NG- RAN 615 for receiving another UE identifier such as a persistent identifier for a single UE (e.g., the UE 628) or a group of UEs (e.g., which may include the UE 628 and other UEs). Some or all UEs of the group of UEs may have at least one common characteristic. In one example, the NG-RAN 615 may select the group of UEs from 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 the one or more characteristics corresponding to the multiple UEs.

[0122] As indicated at 635, the UE 628 establishes a radio resource control (RRC) connection (i.e., an RRC connected state) with the NG-RAN 615.

[0123] As indicated at 640, the NG-RAN 615 triggers (or execute some instructions) to run artificial intelligence / machine learning (AI / ML) workflows including model training and updates for the UE 628 (or the group of UEs).

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

[0125] In some cases, the NG-RAN 615 may also send a request to the core network 610 (e.g., to the AMF of the core network 610) for the persistent identifier (e.g., to identify the single UE or the group of UEs across the different RRC state transitions). In somecases, this request may be included within an initial context setup request, which may be used during an initial connection between at least one UE within the group of UEs and the NG-RAN 615. For example, every time at least one UE within the group of UEs may connect to the NG-RAN 615, the NG-RAN 615 may request the core network 610 to provide the persistent identifier for the group of UES via the initial context setup request.

[0126] As indicated at 650, the core network 610 generates and allocates / sends the temporary UE identifier to the NG-RAN 615.

[0127] In certain aspects, the core network 610 may randomly generate the temporary UE identifier based on a permanent UE identifier of the UE 628.

[0128] In certain aspects, the core network 610 may derive the temporary UE identifier using a function. The function may be based on at least one key, a subscription permanent identifier (SUPI), an international mobile subscriber identity (IMSI), and / or at least one parameter. The function may be a one-way function, such as, a secure hash function. The at least one key may only be known to the core network 610. The at least one parameter may be an optional parameter (e.g., which may be used to avoid the temporary UE identifier collision).

[0129] In certain aspects, when derivation process is used, the core network 610 may store the at least one key (e.g., not per UE but for all UEs) and the at least one parameter (if used) as part of UE context for the UE 628. Since the core network 610 knows the at least one key and the at least one parameter, the core network 610 can derive the temporary UE identifier using the at least one key and the at least one parameter (e.g., as the core network 610 already knows the SUPI, the IMSI of the UE 628) when requested by the NG-RAN 615.

[0130] In certain aspects, when multiple keys are used for the generation of the temporary UE identifier, the core network 610 may store a key identifier associated with each key used for the temporary UE identifier derivation as part of the UE context. The core network 610 may later determine which all keys to use to derive the temporary UE identifier. This example case may only be valid within the core network 610. In some cases, when the core network 610 is changed, a new core network may generate a new temporary UE identifier for the UE 628 (e.g., unless the at least one key used for the temporary UE identifier was shared among different core networks by the core network 610).

[0131] In certain aspects, the core network 610 may decide a validity time (or a life time) for the temporary UE identifier (e.g., to avoid long-time tracking of the UE 628 at the NG-RAN 615 and to limit a linkage of UE data at the NG-RAN 615). The core network 610 may determine the validity time, based on information associated with the NG-RAN 615 or a policy associated with the core network 610.

[0132] In certain aspects, once the validity time for the temporary UE identifier expires, the core network 610 allocates a new temporary UE identifier for the UE 628. In such cases, the core network 610 may also change the at least one key and / or the at least one parameter for generating the new temporary UE identifier. If a new key is used for generating the new temporary UE identifier, a key identifier associated with the new key is stored as part of the UE context (e.g., so as to determine which key is used for the temporary UE identifier derivation).

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

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

[0135] In some cases, the NG-RAN 615 may store the persistent identifier for the single UE or the group of UEs (e.g., in the UE context). In some cases, the NG-RAN 615 may use the persistent identifier to correlate UE measurements of the single UE or the group of UEs in both connected and idle RRC states. In some cases, the NG-RAN 615 may request the AMF to store the persistent identifier when at least one UE for which the persistent identifier is applicable goes to an RRC idle state.

[0136] As indicated at 660, the NG-RAN 615 sends the temporary UE identifier to the near-RT RIC 620.

[0137] In some cases, the NG-RAN may send the persistent identifier to the near-RT RIC 620.

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

[0139] As indicated at 670, the UE 628 again establishes the RRC connection with the NG-RAN 615.

[0140] As indicated at 675, the NG-RAN 615 again sends the request to the core network 610 for the temporary UE identifier. For example, every time the UE 628 connects to the NG-RAN 615, the NG-RAN 615 can request the core network 610 to provide the temporary UE identifier (e.g., via an initial context setup request).

[0141] As indicated at 680, the core network 610 identifies that the request (e.g., to provide the temporary UE identifier) is for the same UE 628 and allocates the same (i.e., previously allocated) temporary UE identifier for the UE 628.

[0142] As indicated at 685, the core network 610 sends the same temporary UE identifier to the NG-RAN 615. For example, the AMF of the core network 610 may provide the same temporary UE identifier to the NG-RAN 615 across the different RRC connections, if the request is associated with the same UE 628. In certain aspects, the NG- RAN 615 may use the temporary UE identifier to correlate different UE measurements in RRC connected and idle states of the UE 628.

[0143] In certain aspects, the NG-RAN 615 may allocate the persistent identifier (e.g., to identify the single UE and / or the group of UEs across the different RRC state transitions). For example, the NG-RAN 615 may allocate a first identifier for the single UE and / or the group of UEs, and then may make the first identifier persistent across different RRC states corresponding to the single UE and / or the group of UEs. In some cases, to make the first identifier persistent across the different RRC states corresponding to the single UE and / or the group of UEs, the NG-RAN 615 may send a request to the AMF of the core network 610 to store the first identifier in a database associated with the AMF of the core network 610. The request may be sent when the single UE may move in an RRC idle state and / or when UEs within the group of UEs may move into the RRC idle state. In some cases, when the single UE may move back into an RRC connected state and / or when UEs within the group of UEs may move back into the RRC connected state (or there is a handover procedure), the AMF of the core network 610 may provide (e.g., may be in response to some request from the NG-RAN 615) the same first identifier for the single UE and / or the group of UEs to the NG-RAN 615. In this way, the NG-RAN 615 may be able to identify the single UE and / or the group of UEs using the same first identifier.

[0144] an identifier and makes it persistent across RRC states by asking AMF to store this RAN allocated identifier when the UE goes idle and provide the same identifier when UE comes back connected or undergoes handover etc. This way the RAN can identify it is the same UE. The second aspect is not clear from this claim.

[0145] FIG. 7A depicts components of another example disaggregated BS 700 architecture. The disaggregated BS 700 architecture includes a core network 710, a NG- RAN 715, a near-RT RIC 720, and a non-RT RIC 725 (e.g., associated with a SMO framework).

[0146] As depicted in FIG. 7A, the core network 710 and the NG-RAN 715 may communicate or are associated to each other via NG interface. The NG-RAN 715 and the near-RT RIC 720 may communicate or are associated to each other via E2 interface. The near-RT RIC 720 and the non-RT RIC 725 may communicate or are associated to each other via Al interface. The core network 710 and the non-RT RIC 725 may communicate or are associated to each other via service-based architecture (SB A) interface (e.g., which may be UE identifier interface).

[0147] FIG. 7B depicts a call flow diagram illustrating example communication among the core network 710, the near-RT RIC 720 and the non-RT RIC 725. The core network 710 shown in FIG. 7B may be an example of the core network 220 depicted and described with respect to FIG. 2. The near-RT RIC 720 shown in FIG. 7B may be an example of the near-RT RIC 225 depicted and described with respect to FIG. 2. The non- RT RIC 725 shown in FIG. 7B may be an example of the non-RT RIC 215 depicted and described with respect to FIG. 2.

[0148] As indicated at 730, the non-RT RIC 725 triggers (or execute some instructions) to run AI / ML workflows including model training and updates for a UE.

[0149] As indicated at 735, the non-RT RIC 725 receives UE-specific data including RAN UE identifiers (e.g., via 01 and Al interfaces) for the UE.

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

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

[0152] As indicated at 750, the non-RT RIC 725 sends another request to the core network 710 for the temporary UE identifier of the UE associated with an identifier Z.

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

[0154] As indicated at 760, the core network 710 sends the temporary UE identifierY for the UE associated with the identifier Z to the non-RT RIC 725.

[0155] FIG. 7C depicts another call flow diagram illustrating example communication among the core network 710, the near-RT RIC 720 and the non-RT RIC 725.

[0156] As indicated at 765, the near-RT RIC 720 triggers (or execute some instructions) to run the AI / ML workflows including model training and updates for the UE.

[0157] As indicated at 770, the near-RT RIC 720 receives the UE-specific data including the RAN UE identifiers (e.g., via E2 interfaces) for the UE.

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

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

[0160] As indicated at 785, the core network 710 sends the temporary UE identifierY for the UE associated with the identifier X to the non-RT RIC 725.

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

[0162] In some cases, the non-RT RIC 725 may also send a request to the core network 710 (e.g., to an AMF of the core network 710) for a persistent identifier for a single UE or a group of UEs of certain characteristics (e.g., to identify these UEs across different RRC state transitions). In response to the request, the core network 710 may allocate and send the persistent identifier for the single UE or the group of UEs to the non-RT RIC 725. In some cases, the non-RT RIC 725 may store the persistent identifierat the core network 710, and may retrieve the persistent identifier from the core network710 as and when needed.

[0163] FIG. 8 depicts a call flow diagram illustrating example communication among a UE, a gNodeB (gNB), an AMF of a core network, and a session management function (SMF) / user plane function (UPF). The UE shown in FIG. 8 may be an example of the UE 104 depicted and described with respect to FIG. 1 and FIG. 3. The gNB shown in FIG. 8 may be an example of the BS 102 depicted and described with respect to FIG. 1 and FIG. 3. The core network shown in FIG. 8 may be an example of the core network 220 depicted and described with respect to FIG. 2.

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

[0165] As indicated at 810, the gNB sends a UE context setup request to the AMF.

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

[0167] As indicated at 820, the SMF / UPF generates and sends the TE identifier associated with the UE to the AMF.

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

[0169] As indicated at 830, the AMF sends a UE context setup response (e.g., for the UE context setup request) including the TE identifier associated with the UE to the gNB.

[0170] As indicated at 835, the gNB sends a connection setup response (e.g., for the connection setup request) to the UE.

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

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

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

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

[0175] As indicated at 860, the UE again sends the connection setup request to the gNB. The gNB may then send the UE context setup request to the AMF

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

[0177] As indicated at 870, the SMF / UPF identifies that the request for the TE identifier is for the same UE, and allocates the same (i.e., previously allocated or assigned) TE identifier for the UE.

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

[0179] As indicated at 880, the AMF sends the UE context setup response (e.g., for the UE context setup request) including the TE identifier associated with the UE to the gNB.

[0180] As indicated at 885, the gNB sends the connection setup response (e.g., for the connection setup request) to the UE.

[0181] As noted above, during the PDU session for the UE, the TE identifier is allocated to the UE for the PDU session by the SMF / UPF and (indirectly) provided to the gNB via the NG interface. The TE identifier may be stored in SMF / UPF context even when the UE goes to the RRC idle state, and the same TE identifier is again allocated to the same UE when the UE goes back to the RRC connected state and again establishes the PDU session. However, in RAN systems, entire UE context including the TE identifier allocated to the UE may be lost, when the UE goes to the RRC idle state from the RRC connected state.

[0182] FIG. 9 depicts a call flow diagram illustrating example communication among a UE, a gNB, and a near-RT RIC. The UE shown in FIG. 9 may be an example of the UE 104 depicted and described with respect to FIG. 1 and FIG. 3. The gNB shown in FIG. 9 may be an example of the BS 102 depicted and described with respect to FIG. 1 and FIG. 3. The near-RT RIC shown in FIG. 9 may be an example of the near-RT RIC 225 depicted and described with respect to FIG. 2.

[0183] As indicated at 905, the near-RT RIC subscribes with the gNB to receive UE related data including a TE identifier for the UE. For example, the near-RT RIC maysubscribe to the gNB via E2 interface to receive available core network allocated uplink TE identifiers of the UE (e.g., in the UE related data over the E2 interface).

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

[0185] As indicated at 915, the gNB sends the UE related data including the TE identifier for the UE to the near-RT RIC.

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

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

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

[0189] As indicated at 935, the UE again establishes the RRC connection with the gNB.

[0190] As indicated at 940, the gNB again sends the UE related data including the TE identifier for the UE to the near-RT RIC.

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

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

[0193] FIG. 10A depicts another example disaggregated BS 1000 architecture. The disaggregated BS 700 architecture includes a core network 1005, a NG-RAN 1010, a near-RT RIC 1015, and a management data analytics function (MDAF) 1020. The MDAF 1020 may include or is associated with a non-RT RIC (e.g., which is further associated with a SMO framework).

[0194] As depicted in FIG. 10A, the core network 1005 and the NG-RAN 1010 may communicate or are associated to each other via NG interface. The NG-RAN 1010 and the near-RT RIC 1015 may communicate or are associated to each other via E2 interface.The near-RT RIC 1015 and the MDAF 1020 may communicate or are associated to each other via Al interface. The core network 1005 and the MDAF 1020 may communicate or are associated to each other via SB A interface.

[0195] FIG. 10B depicts a call flow diagram illustrating example communication among the core network 1005, the non-RT RIC 1020 and the near-RT RIC 1015. The core network 1005 shown in FIG. 10B may be an example of the core network 220 depicted and described with respect to FIG. 2. The near-RT RIC 1015 shown in FIG. 10B may be an example of the near-RT RIC 225 depicted and described with respect to FIG. 2. The non-RT RIC 1020 shown in FIG. 10B may be an example of the non-RT RIC 215 depicted and described with respect to FIG. 2. In some cases, the non-RT RIC 1020 acts as the MDAF (e.g., in an operations, administration, and maintenance (0AM) layer) and connects to the core network 1005 to receive services from the core network 1005.

[0196] As indicated at 1025, the core network 1005 sends one or more permanent identifiers associated with a UE to the non-RT RIC 1020. The one or more permanent identifiers may include subscription permanent identifier (SUPI) and / or international mobile subscriber identity (IMSI).

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

[0198] As indicated at 1035, the non-RT RIC 1020 sends the one or more temporary identifiers to the near-RT RIC 1015. For example, based on operator’s trusted network configuration, the non-RT RIC 1020 may provide the one or more temporary identifiers to the near-RT RIC 1015 (e.g., for UE specific AI / ML training and optimization in the near-RT RIC 1015).Example Method For Wireless Communications At A Next Generation (NG) - Radio Access Network (RAN)

[0199] FIG. 11 shows an example of a method 1100 for wireless communications at a first node (e.g., such as the BS 102 of FIG. 1 and FIG. 3). In one example, the first nodemay include a server associated with a next generation (NG) - radio access network (RAN).

[0200] Method 1100 begins at step 1105 with transmitting, to a second node, a request to allocate a temporary identifier for a user equipment (UE). The second node may include an access and mobility management function (AMF) of a core network node. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and / or code for transmitting as described with reference to FIG. 15.

[0201] Method 1100 then proceeds to step 1110 with receiving an indication of a first temporary identifier for the UE from the second node. The first temporary identifier is based on a first identifier of the UE. The first temporary identifier is persistent across multiple radio resource control (RRC) states corresponding to the UE. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 15.

[0202] In certain aspects, the NG-RAN and the AMF are interconnected via NG interface.

[0203] In certain aspects, the first identifier of the UE includes a permanent identifier of the UE.

[0204] In certain aspects, the method 1100 then proceeds to identifying the UE across the multiple RRC states based on the first temporary identifier.

[0205] In certain aspects, the method 1100 then proceeds to correlating different measurements performed by the UE, across the multiple RRC states, using the first temporary identifier.

[0206] In certain aspects, the multiple RRC states include at least an RRC connected state, an RRC inactive state, and an RRC idle state.

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

[0208] In certain aspects, the method 1100 then proceeds to determining that the first temporary identifier has been used for a period of time; and receiving an indication of asecond temporary identifier for the UE from the second node, in accordance with the determination.

[0209] In certain aspects, the method 1100 then proceeds to transmitting the indication of the first temporary identifier to a third node via XN interface. The first node and the third node may include different servers associated with different NG-RANs.

[0210] In certain aspects, the method 1100 then proceeds to transmitting, to a third node, different measurements performed by the UE along with the first temporary identifier via XN interface.

[0211] In certain aspects, the method 1100 then proceeds to receiving, from a third node, different measurements performed by the UE along with the first temporary identifier via XN interface.

[0212] In certain aspects, the first node may include a service management and orchestration (SMO) or a non-RT RIC; the second node may include a network element device of a core network node; and the SMO or the non-RT RIC and the network element device are interconnected via a service-based architecture (SB A) interface.

[0213] In certain aspects, the request from the SMO or the non-RT RIC to the network element device includes a RAN-based identifier of the UE.

[0214] In certain aspects, the method 1100 then proceeds to transmitting an indication of the first temporary identifier to a near- RT RIC over Al interface.

[0215] In certain aspects, the method 1100 then proceeds to receiving a message requesting for a UE temporary identifier from a near- RT RIC where the message also includes a RAN-based identifier of the UE; and transmitting the first temporary identifier to the near-RT RIC, in response to the message. The first temporary identifier is based on the RAN-based identifier.

[0216] In one aspect, the method 1100, or any aspect related to it, may be performed by an apparatus, such as a communications device 1500 of FIG. 15, which includes various components operable, configured, or adapted to perform the method 1100. The communications device 1500 is described below in further detail.

[0217] Note that FIG. 11 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.Example Method For Wireless Communications At An Access And Mobility Management Function (A MF)

[0218] FIG. 12 shows an example of a method 1200 for wireless communications at a first node (e.g., such as the BS 102 of FIG. 1 and FIG. 3). In one example, the first node may include an access and mobility management function (AMF) of a core network node.

[0219] Method 1200 begins at step 1205 with receiving a request to allocate a temporary identifier for a user equipment (UE) from a second node. The second node may include a server associated with a next generation (NG) - radio access network (RAN). In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 15.

[0220] Method 1200 begins at step 1210 with transmitting an indication of a first temporary identifier for the UE to the second node. The first temporary identifier is based on a first identifier of the UE. The first temporary identifier is persistent across multiple radio resource control (RRC) states corresponding to the UE. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and / or code for transmitting as described with reference to FIG. 15.

[0221] In certain aspects, the NG-RAN and the AMF are interconnected via NG interface.

[0222] In certain aspects, the first identifier of the UE includes a permanent identifier of the UE.

[0223] In certain aspects, the method 1200 then proceeds to randomly generating the first temporary identifier based on the first identifier; and storing the first temporary identifier as part of UE context.

[0224] In certain aspects, the method 1200 then proceeds to deriving the first temporary identifier based on the first identifier using a function. The function is based on at least one of: at least one key, a subscription permanent identifier (SUPI), an international mobile subscriber identity (IMSI), or at least one parameter.

[0225] In certain aspects, the method 1200 then proceeds to storing at least one of: the at least one key or the at least one parameter as part of UE context.

[0226] In certain aspects, the method 1200 then proceeds to storing an identification (ID) associated with a key used for deriving the first temporary identifier as part of UE context, when the function is based on two or more keys.

[0227] In certain aspects, the first node may include a network element device of a core network node. The second node may include a service management and orchestration (SMO) or a non-real time (RT) RAN intelligent controller (RIC). The SMO or the non- RT RIC and the network element device are interconnected via a service-based architecture (SBA) interface. In some cases, the request from the SMO or the non-RT RIC to the network element device may include a radio access network (RAN)-based identifier of the UE.

[0228] In one aspect, the method 1200, or any aspect related to it, may be performed by an apparatus, such as a communications device 1500 of FIG. 15, which includes various components operable, configured, or adapted to perform the method 1200. The communications device 1500 is described below in further detail.

[0229] Note that FIG. 12 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.Example Method For Wireless Communications At A Near-Real Time (RT) Radio Access Network (RAN) Intelligent Controller (RIC)

[0230] FIG. 13 shows an example of a method 1300 for wireless communications at a near-real time (RT) radio access network (RAN) intelligent controller (RIC) (e.g., such as the BS 102 of FIG. 1 and FIG. 3).

[0231] Method 1300 begins at step 1305 with transmitting, to a network entity, a subscription message to receive user equipment (UE) data including one or more tunnel endpoint (TE) identifiers associated with a UE. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and / or code for transmitting as described with reference to FIG. 15.

[0232] Method 1300 begins at step 1310 with receiving at least one first TE identifier associated with a first identifier of the UE, from the network entity, in response to the subscription message. In some cases, the operations of this step refer to, or may beperformed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 15.

[0233] In certain aspects, the method 1300 then proceeds to receiving at least one second TE identifier associated with a second identifier of the UE from the network entity.

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

[0235] In one aspect, the method 1300, or any aspect related to it, may be performed by an apparatus, such as a communications device 1500 of FIG. 15, which includes various components operable, configured, or adapted to perform the method 1300. The communications device 1500 is described below in further detail.

[0236] Note that FIG. 13 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.Example Method For Wireless Communications At A Non-Real Time (RT) Radio Access Network (RAN) Intelligent Controller (RIC)

[0237] FIG. 14 shows an example of a method 1400 for wireless communications at a non-real time (RT) radio access network (RAN) intelligent controller (RIC) (e.g., such as the BS 102 of FIG. 1 and FIG. 3).

[0238] Method 1400 begins at step 1405 with receiving, from a core network node, one or more permanent identifiers associated with a user equipment (UE). In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 15.

[0239] Method 1400 begins at step 1410 with transmitting one or more temporary identifiers to a near-RT RIC. The one or more temporary identifiers are based on the one or more permanent identifiers. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and / or code for transmitting as described with reference to FIG. 15.

[0240] In certain aspects, the non-RT RIC is configured as a management data analytics service in an operations, administration, and maintenance (0AM) layer.

[0241] In certain aspects, the one or more permanent identifiers include at least one of: subscription permanent identifier (SUPI) or international mobile subscriber identity (IMSI).

[0242] In certain aspects, the method 1400 then proceeds to translating the one or more permanent identifiers into the one or more temporary identifiers; receiving, from a near-RT RIC, a request for the one or more temporary identifiers; and transmitting, to the near-RT RIC, an indication of the one or more temporary identifiers, in response to the request.

[0243] In one aspect, the method 1400, or any aspect related to it, may be performed by an apparatus, such as a communications device 1500 of FIG. 15, which includes various components operable, configured, or adapted to perform the method 1400. The communications device 1500 is described below in further detail.

[0244] Note that FIG. 14 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.Example Communications Device

[0245] FIG. 15 depicts aspects of an example communications device 1500. In some aspects, communications device 1500 is a network entity, such as BS 102 of FIG. 1 and FIG. 3, or a disaggregated base station as discussed with respect to FIG. 2.

[0246] The communications device 1500 includes a processing system 1505 coupled to a transceiver 1555 (e.g., a transmitter and / or a receiver) and / or a network interface 1565. The transceiver 1555 is configured to transmit and receive signals for the communications device 1500 via an antenna 1560, such as the various signals as described herein. The network interface 1565 is configured to obtain and send signals for the communications device 1500 via communication link(s), such as a backhaul link, midhaul link, and / or fronthaul link as described herein, such as with respect to FIG. 2. The processing system 1505 may be configured to perform processing functions for the communications device 1500, including processing signals received and / or to be transmitted by the communications device 1500.

[0247] The processing system 1505 includes one or more processors 1510. In various aspects, one or more processors 1510 may be representative of one or more of receiveprocessor 338, transmit processor 320, TX MIMO processor 330, and / or controller / processor 340, as described with respect to FIG. 3. The one or more processors 1510 are coupled to a computer-readable medium / memory 1530 via abus 1550. In certain aspects, the computer-readable medium / memory 1530 is configured to store instructions (e.g., computer-executable code) that when executed by the one or more processors 1510, cause the one or more processors 1510 to perform the method 1100 described with respect to FIG. 11, the method 1200 described with respect to FIG. 12, the method 1300 described with respect to FIG. 13, the method 1400 described with respect to FIG. 14, or any aspect related to it. Note that reference to a processor of communications device 1500 performing a function may include one or more processors 1510 of communications device 1500 performing that function.

[0248] In the depicted example, the computer-readable medium / memory 1530 stores code (e.g., executable instructions), such as code for transmitting 1535 and code for receiving 1540. Processing of the code for transmitting 1535 and code for receiving 1540 may cause the communications device 1500 to perform the method 1100 described with respect to FIG. 11, the method 1200 described with respect to FIG. 12, the method 1300 described with respect to FIG. 13, the method 1400 described with respect to FIG. 14, or any aspect related to it.

[0249] The one or more processors 1510 include circuitry configured to implement (e.g., execute) the code stored in the computer-readable medium / memory 1530, including circuitry such as circuitry for transmitting 1515 and circuitry for receiving 1520. Processing with circuitry for transmitting 1515 and circuitry for receiving 1520 may cause the communications device 1500 to perform the method 1100 described with respect to FIG. 11, the method 1200 described with respect to FIG. 12, the method 1300 described with respect to FIG. 13, the method 1400 described with respect to FIG. 14, or any aspect related to it.

[0250] Various components of the communications device 1500 may provide means for performing the method 1100 described with respect to FIG. 11, the method 1200 described with respect to FIG. 12, the method 1300 described with respect to FIG. 13, the method 1400 described with respect to FIG. 14, or any aspect related to it.

[0251] Means for transmitting, sending or outputting for transmission may include transceivers 332 and / or antenna(s) 334 of the BS 102 illustrated in FIG. 3 and / or thecircuitry for transmitting 1515, the code for transmitting 1535, the transceiver 1855 and the antenna 1560 of the communications device 1500 in FIG. 15.

[0252] Means for receiving or obtaining may include transceivers 332 and / or antenna(s) 334 of the BS 102 illustrated in FIG. 3 and / or the circuitry for receiving 1520, the code for receiving 1540, the transceiver 1855 and the antenna 1560 of the communications device 1500 in FIG. 15.

[0253] In some cases, rather than actually transmitting, for example, signals and / or data, a device may have an interface to output signals and / or data for transmission (a means for outputting). For example, a processor may output signals and / or data, via a bus interface, to an RF front end for transmission. In various aspects, the RF front end may include various components, including transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, and the like, such as depicted in the examples in FIG. 3.

[0254] In some cases, rather than actually receiving signals and / or data, a device may have an interface to obtain the signals and / or data received from another device (a means for obtaining). For example, a processor may obtain (or receive) the signals and / or data, via a bus interface, from an RF front end for reception. In various aspects, an RF front end may include various components, including transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, and the like, such as depicted in the examples in FIG. 3. Notably, FIG. 15 is an example, and many other examples and configurations of communication device 1500 are possible.Example Clauses

[0255] Implementation examples are described in the following numbered clauses:

[0256] Clause 1 : A method at a first node, comprising: transmitting a request to allocate a persistent identifier for a first plurality of user equipments (UEs) of one or more groups of UEs to a second node; and receiving an indication of a first persistent identifier for the first plurality of UEs from the second node, wherein the first persistent identifier is applicable across multiple radio resource control (RRC) states corresponding to all UEs within the first plurality of UEs.

[0257] Clause 2: The method of Clause 1, wherein the first node comprises a server associated with a next generation (NG) - radio access network (RAN); the second node comprises 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-lasting reference for the first plurality of UEs.

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

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

[0260] Clause 5: The method of any one of Clauses 1-4, further comprising selecting the first plurality of UEs from multiple UEs based at least on one or more characteristics corresponding to the multiple UEs, wherein each UE within the first plurality of UEs is associated with at least one common characteristic.

[0261] Clause 6: The method of any one of Clauses 1-5, further comprising receiving signaling indicating the first plurality of UEs from the second node, wherein each UE within the first plurality of UEs is associated with at least one common characteristic.

[0262] Clause 7: The method of any one of Clauses 1-6, further comprising storing the first persistent identifier for the first plurality of UEs in a database.

[0263] Clause 8: The method of any one of Clauses 1-7, further comprising correlating different measurements performed by one or more UEs of the first plurality of UEs, across different RRC states associated with the one or more UEs of the first plurality of UEs, using the first persistent identifier for the first plurality of UEs.

[0264] Clause 9: The method of any one of Clauses 1-8, wherein: the request is included within an initial context setup request; and the initial context setup request is used during an initial connection between the first node and the at least one UE within the first plurality of UEs.

[0265] Clause 10: The method of any one of Clauses 1-9, wherein: the first persistent identifier is allocated for the first plurality of UEs across different RRC states corresponding to each UE within the first plurality of UEs; and the different RRC states comprise at least an RRC connected state, an RRC inactive state, and an RRC idle state.

[0266] Clause 11 : The method of any one of Clauses 1-10, further comprising: determining that at least one UE within the first plurality of UEs has moved into an RRCidle state; and transmitting a request to the second node to store the first persistent identifier for the first plurality of UEs, in accordance with the determination.

[0267] Clause 12: A method at an access and mobility management function (AMF) of a core network node, comprising: receiving a request to store an identifier for at least one of a user equipment (UE) or one or more groups of UEs from a server associated with a next generation (NG) - radio access network (RAN), wherein the identifier is allocated at the server associated with the NG-RAN; and storing the identifier in a database associated with the AMF of the core network node, in accordance with the request.

[0268] Clause 13: The method of Clause 12, wherein the NG-RAN and the AMF are interconnected via an NG interface.

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

[0270] Clause 15: The method of any one of Clauses 12-14, further comprising selecting at least one group of UEs from multiple UEs based on one or more characteristics corresponding to the multiple UEs, wherein each UE within the at least one group of UEs is associated with at least one common characteristic.

[0271] Clause 16: The method of any one of Clauses 12-15, wherein: the storing comprises storing the identifier for the UE in the database when the UE moves into an RRC idle state; determining that the UE has moved into an RRC connected state from the RRC idle state; and obtaining the identifier for the UE from the database when the UE moves into the RRC connected state.

[0272] Clause 17: The method of any one of Clauses 12-16, wherein: the storing comprises storing the identifier for the one or more groups of UEs in the database when UEs within the one or more groups of UEs move into an RRC idle state; determining that the UEs within the one or more groups of UEs have moved into an RRC connected state from the RRC idle state; and obtaining the first identifier for the one or more groups of UEs from the database when the UEs within the one or more groups of UEs have moved into the RRC connected state.

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

[0274] Clause 19: The method of Clause 18, wherein the first node comprises a service management and orchestration (SMO) or a non-real time (RT) radio access network (RAN) intelligent controller (RIC); the second node comprises a network element device of a core network node; and the SMO or the non-RT RIC and the network element device are interconnected via a service-based architecture (SBA) interface.

[0275] Clause 20: The method of Clause 19, further comprising storing the first persistent identifier for the one or more UEs at a database associated with the second node.

[0276] Clause 21 : An apparatus, comprising: at least one memory comprising executable instructions; and one or more processors, individually or collectively, configured to execute the executable instructions and cause the apparatus to perform a method in accordance with any one of Clauses 1-20.

[0277] Clause 22: An apparatus, comprising means for performing a method in accordance with any one of Clauses 1-20.

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

[0279] Clause 24: A computer program product embodied on a computer-readable storage medium comprising code for performing a method in accordance with any one of Clauses 1-20.Additional Considerations

[0280] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein are not limiting of the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may beperformed in an order different from that described, and various actions may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0281] The various illustrative logical blocks, modules and circuits described in connection with the present disclosure may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.

[0282] As used herein, “a processor,” “at least one processor” or “one or more processors” generally refers to a single processor configured to perform one or multiple operations or multiple processors configured to collectively perform one or more operations. In the case of multiple processors, performance the one or more operations could be divided amongst different processors, though one processor may perform multiple operations, and multiple processors could collectively perform a single operation. Similarly, “a memory,” “at least one memory” or “one or more memories” generally refers to a single memory configured to store data and / or instructions, multiple memories configured to collectively store data and / or instructions.

[0283] As used herein, a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as anycombination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

[0284] As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.

[0285] The methods disclosed herein comprise one or more actions for achieving the methods. The method actions may be interchanged with one another 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 specific actions may be modified without departing from the scope of the claims. Further, the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and / or software component(s) and / or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor.

[0286] The following claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims. Within a claim, reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. No claim element is to be construed under the provisions of 35 U.S.C. §112(f) unless the element is expressly recited using the phrase “means for”. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Claims

CLAIMS1. A first node, comprising: at least one memory comprising instructions; and one or more processors, individually or collectively, configured to execute the instructions and cause the first node to: transmit a request to allocate a persistent identifier for a first plurality of user equipments (UEs) of one or more groups of UEs to a second node; and receive an indication of a first persistent identifier for the first plurality of UEs from the second node, wherein the first persistent identifier is applicable across multiple radio resource control (RRC) states corresponding to all UEs within the first plurality of UEs.

2. The first node of claim 1, wherein: the first node comprises a server associated with a next generation (NG) - radio access network (RAN); the second node comprises 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-lasting reference for the first plurality of UEs.

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

4. The first node of claim 1, wherein at least two or more UEs within 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, individually or collectively, are configured to execute the instructions and cause the first node to select the first plurality of UEs from multiple UEs based at least on one or more characteristics corresponding to the multiple UEs, wherein each UE within 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, individually or collectively, are configured to execute the instructions and cause the first node to receive signaling indicating the first plurality of UEs from the second node, wherein each UE within 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, individually or collectively, are configured to execute the instructions and cause the first node to store the first persistent identifier for the first plurality of UEs in a database.

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

9. The first node of claim 1, wherein: the request is included within an initial context setup request; and the initial context setup request is used during an initial connection between the first node and at least one UE within the first plurality of UEs.

10. The first node of claim 1, wherein: the first persistent identifier is allocated for the first plurality of UEs across different RRC states corresponding to each UE within the first plurality of UEs; and the different RRC states comprise at least an RRC connected state, an RRC inactive state, and an RRC idle state.

11. The first node of claim 1, wherein the one or more processors, individually or collectively, are configured to execute the instructions and cause the first node to: determine that at least one UE within the first plurality of UEs has moved into an RRC idle state; and transmit a request to the second node to store the first persistent identifier for the first plurality of UEs, in accordance with the determination.

12. An access and mobility management function (AMF) of a core network node, comprising: at least one memory comprising instructions; and one or more processors, individually or collectively, configured to execute the instructions and cause the AMF of the core network node to: receive a request to store an identifier for at least one of a user equipment (UE) or one or more groups of UEs from a server associated with a next generation (NG) - radio access network (RAN), wherein the identifier is allocated at the server associated with the NG-RAN; and store the identifier in a database associated with the AMF of the core network node, in accordance with the request.

13. The AMF of the core network node of 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 of claim 12, wherein each UE within the one or more groups of UEs is associated with at least one common characteristic.

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

16. The AMF of the core network node of claim 12, wherein: the store comprises store the identifier for the UE in the database when the UE moves into an RRC idle state; the one or more processors, individually or collectively, are configured to execute the instructions and cause the AMF of the core network node to determine that the UE has moved into an RRC connected state from the RRC idle state; and the one or more processors, individually or collectively, are configured to execute the instructions and cause the AMF of the core network node to obtain the identifier for the UE from the database when the UE moves into the RRC connected state.

17. The AMF of the core network node of claim 12, wherein: the store comprises store the identifier for the one or more groups of UEs in the database when UEs within the one or more groups of UEs move into an RRC idle state; the one or more processors, individually or collectively, are configured to execute the instructions and cause the AMF of the core network node to determine that the UEs within the one or more groups of UEs have moved into an RRC connected state from the RRC idle state; and the one or more processors, individually or collectively, are configured to execute the instructions and cause the AMF of the core network node to obtain the first identifier for the one or more groups of UEs from the database when the UEs within the one or more groups of UEs have moved into the RRC connected state.

18. A first node, comprising: at least one memory comprising instructions; and one or more processors, individually or collectively, configured to execute the instructions and cause the first node to: transmit a request to allocate a persistent identifier for one or more user equipments (UEs) to a second node; and receive an indication of a first persistent identifier for the one or more UEs from the second node, 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 of claim 18, wherein: the first node comprises a service management and orchestration (SMO) or a non- real time (RT) radio access network (RAN) intelligent controller (RIC); the second node comprises a network element device of a core network node; and the SMO or the non-RT RIC and the network element device are interconnected via a service-based architecture (SBA) interface.

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

21. A non-real time (RT) radio access network (RAN) intelligent controller (RIC), comprising: at least one memory comprising instructions; and one or more processors configured, individually or in any combination, to execute the instructions and cause the non-RT RIC to: transmit, to a network element device of a core network node, a request to allocate a temporary identifier for a user equipment (UE); and receive an indication of a first temporary identifier for the UE from the network element device, wherein the first temporary identifier is based on a first identifier of the UE, 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 (SB A) interface.

23. The non-RT RIC of claim 21, wherein the request comprises 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 cause the non-RT RIC to transmit an indication of the first temporary identifier to a near-RT RIC over an Al 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 cause the non-RT RIC to: receive a message requesting for a UE temporary identifier from a near-RT RIC, wherein the message also comprises a RAN-based identifier of the UE; and transmit the first temporary identifier to the near-RT RIC, in response to the message, wherein the first temporary identifier is based on the RAN-based identifier.

26. A network element device of a core network node, comprising: at least one memory comprising instructions; and one or more processors configured, individually or in any combination, to execute the instructions and cause the network element device to: receive a request to allocate a temporary identifier for a user equipment (UE) from a non-real time (RT) radio access network (RAN) intelligent controller (RIC); and transmit an indication of a first temporary identifier for the UE to the non- RT RIC, wherein the first temporary identifier is based on a first identifier of the UE, 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 comprises a radio access network (RAN)-based identifier of the UE.

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

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 thenear-RT RIC to receive at least one second TE identifier associated with a second identifier of the UE from the network entity.

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 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 a 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), comprising: at least one memory comprising instructions; and one or more processors configured, individually or in any combination, to execute the instructions and cause the non-RT RIC to: receive, from a core network node, one or more permanent identifiers associated with a user equipment (UE); and transmit one or more temporary identifiers to a 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 analytics function in an operations, administration, and maintenance (0AM) layer.

34. The non-RT RIC of claim 32, wherein the one or more permanent identifiers comprise at least one of: 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 cause the non-RT RIC to: translate the one or more permanent identifiers into the one or more temporary identifiers;receive, from a near-RT RIC, a request for the one or more temporary identifiers; and transmit, to the near-RT RIC, an indication of the one or more temporary identifiers, in response to the request.

Images