WO2022178127A1 - Performance measurements for data management and background data transfer policy control for next-generation systems - Google Patents

Abstract

Various embodiments herein may relate to generating performance measurements for data management and background data transfer policy control in next-generation wireless systems. Other embodiments may be disclosed or claimed.

Description

PERFORMANCE MEASUREMENTS FOR DATA MANAGEMENT AND BACKGROUND DATA TRANSFER POLICY CONTROL FOR NEXT-GENERATION

SYSTEMS

CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority to U.S. Provisional Patent Application No. 63/151,513, which was filed February 19, 2021.

FIELD

Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to generating performance measurements for data management and background data transfer policy control in next-generation wireless systems.

BACKGROUND

In next-generation wireless systems, a unified data repository (UDR) provides data management services and application related data to subscribers. Among other things, the data management services provided by the UDR allow to its consumers (e.g., unified data manager (UDM), policy control function (PCF) and network exposure function (NEF)) to read, create, update, delete particular sets of data and subscribe/unsubscribe to notifications of relevant data changes. Additionally, the PCF provides the services for NEF to control the background data transfer polices, including the creation and update of the background data transfer policies.

However, users’ services may not be fulfilled due to a failed data management service, and the fulfilment of background data-transfer-related services for users relies on a background data transfer policy. Embodiments of the present disclosure address these and other issues by helping to monitor the performance of background data transfer policy control and data management services.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings.

Figure 1 illustrates an example of a fifth-generation (5G) system architecture in accordance with various embodiments.

Figure 2 illustrates an example of a 5G performance measurements generation method according to various embodiments.

Figure 3 A illustrates examples of a service producer operating in conjunction with a UDR according to various embodiments. Figure 3B illustrates examples of a service producer operating in conjunction with a PCF according to various embodiments.

Figure 4 schematically illustrates a wireless network in accordance with various embodiments.

Figure 5 schematically illustrates components of a wireless network in accordance with various embodiments.

Figure 6 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

Figures 7, 8, and 9 depict examples of procedures for practicing the various embodiments discussed herein.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A/B” mean (A), (B), or (A and B).

As introduced above, a UDR provides data management services for the subscriber and application related data, including: subscription data; policy data; structured data for exposure; application data such as packet Flow Descriptions (PFDs) for application detection and AF request information for multiple UEs; or a network function (NF) group ID corresponding to subscriber identifier (e g. IMPI, IMPU, SUPI).

The data management services provided by UDR allow to its consumer (e.g., UDM, PCF and NEF) to read, create, update, delete a particular set of data and subscribe/unsubscribe to notification of relevant data changes. However, users’ service may not be fulfilled due to a failed data management service, therefore it is indispensable that the performance of data management services can be monitored. For background data transfer, an application function (AF) may need to negotiate the policies for with 5GS via NEF, and apply the negotiated policies for a future PDU Session. A PCF provides the services for NEF to control the background data transfer polices, including creation and update of the background data transfer policies. The fulfilment of background data transfer related services for the users rely on background data transfer policy. Therefore it is necessary to monitor the performance of background data transfer policy control.

Among other things, some embodiments of the present disclosure are directed to generating measurements related to data management service for UDR, and measurements related to background data transfer policy control for PCF.

Figure 1 illustrates an example of a fifth-generation (5G) system architecture, while Figure 2 illustrates an example of a 5G performance measurements generation method according to various embodiments, namely for the generation of performance measurements for a network slice selection function (NSSF). In the example shown in Figure 2, a service producer collects raw performance measurements from NFs, and then generates the performance measurements for NFs for its consumers.

Specifically for some embodiments, the NF is a UDR or PCF, and the Service producer may be implemented within the NF or in a separate management system. Figure 3A illustrates one example (on the left), where a service producer is implemented by a UDR, and another example (on the right) where the service producer is implemented by a separate management system in communication with two UDRs supplying raw performance measurements. Similarly, Figure 3B illustrates one example (on the left), where a service producer is implemented by a PCF, and another example (on the right) where the service producer is implemented by a separate management system in communication with two PCFs supplying raw performance measurements.

The present disclosure proceeds by describing examples of performance measurements that can be generated based on raw performance measurements in accordance with various embodiments. For example, these generated measurements may be added to section 5.9 of 3 GPP TS 28.552, v. 16.8.0, 2020-12-16 as indicated by the numbering below.

5.9 Performance measurements definitions

5.x.1 Data management related measurements 5.x.1.1 Data set query

5.x.1.1.1 Number of data set query requests a) This measurement provides the number of data set query requests received by the UDR. b) CC c) Receipt of an Nudr DM Query request by the UDR from an NF service consumer. d) An integer value e) DM. Query Req f) UDRFunction g) Valid for packet switched traffic h) 5GS

5.x.1.1.2 Number of successful data set queries a) This measurement provides the number of succesful data set queries at the UDR. b) CC c) Transmission of an Nudr DM Query response by the UDR to an NF service consumer indicating a successful data set query. d) An integer value e) DM. Query Succ f) UDRFunction g) Valid for packet switched traffic h) 5GS

5.x.1.1.3 Number of failed data set queries a) This measurement provides the number of failed data set queries at the UDR. b) CC c) Transmission of an Nudr DM Query response by the UDR to an NF service consumer indicating a failed data set query, each message increments the relevant subcounter per failure cause by 1. d) Each subcounter is an integer value e) D M . Query F ai 1. cause

Where cause indicates the failure cause of the data set query. f) UDRFunction g) Valid for packet switched traffic h) 5GS

5.5.x Background data transfer policy control related measurements

5.5.x.1 Background data transfer policy creation

5.5.x.1.1 Number of background data transfer policy creation requests a) This measurement provides the number of background data transfer policy creation requests received by the PCF. b) CC c) Receipt of an Npcf BDTPolicyControl Create request by the PCF from an NEF. d) An integer value e) BDTP.CreateReq f) PCFFunction g) Valid for packet switched traffic h) 5GS

5.5.x.1.2 Number of successful background data transfer policy creations a) This measurement provides the number of successful background data transfer policy creations at the PCF. b) CC c) Transmission of an Npcf BDTPolicyControl Create response by the PCF to an NEF indicating a successful background data transfer policy creation. d) An integer value e) BDTP.CreateSucc f) PCFFunction g) Valid for packet switched traffic h) 5GS

5.5.x.1.3 Number of failed background data transfer policy creations a) This measurement provides the number of failed background data transfer policy creations at the PCF. b) CC c) Transmission of an Npcf BDTPolicyControl Create response by the PCF to an NEF indicating a failed background data transfer policy creation, each message increments the relevant subcounter per failure cause by 1. d) Each subcounter is an integer value e) B DT P . C reate Fai 1. cause

Where cause indicates the failure cause of background data transfer policy creation. f) PCFFunction g) Valid for packet switched traffic h) 5GS SYSTEMS AND IMPLEMENTATIONS

Figures 4-5 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

Figure 4 illustrates a network 400 in accordance with various embodiments. The network 400 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3 GPP systems, or the like.

The network 400 may include a UE 402, which may include any mobile or non-mobile computing device designed to communicate with a RAN 404 via an over-the-air connection. The UE 402 may be communicatively coupled with the RAN 404 by a Uu interface. The UE 402 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, IoT device, etc.

In some embodiments, the network 400 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

In some embodiments, the UE 402 may additionally communicate with an AP 406 via an over-the-air connection. The AP 406 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 404. The connection between the UE 402 and the AP 406 may be consistent with any IEEE 802.11 protocol, wherein the AP 406 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 402, RAN 404, and AP 406 may utilize cellular-WLAN aggregation (for example, LWA/LWIP). Cellular-WLAN aggregation may involve the UE 402 being configured by the RAN 404 to utilize both cellular radio resources and WLAN resources.

The RAN 404 may include one or more access nodes, for example, AN 408. AN 408 may terminate air-interface protocols for the UE 402 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 408 may enable data/voice connectivity between CN 420 and the UE 402. In some embodiments, the AN 408 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 408 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 408 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

In embodiments in which the RAN 404 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 404 is an LTE RAN) or an Xn interface (if the RAN 404 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.

The ANs of the RAN 404 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 402 with an air interface for network access. The UE 402 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 404. For example, the UE 402 and RAN 404 may use carrier aggregation to allow the UE 402 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.

The RAN 404 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.

In V2X scenarios the UE 402 or AN 408 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

In some embodiments, the RAN 404 may be an LTE RAN 410 with eNBs, for example, eNB 412. The LTE RAN 410 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub-6 GHz bands.

In some embodiments, the RAN 404 may be an NG-RAN 414 with gNBs, for example, gNB 416, or ng-eNBs, for example, ng-eNB 418. The gNB 416 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 416 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 418 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 416 and the ng-eNB 418 may connect with each other over an Xn interface.

In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 414 and a UPF 448 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN414 and an AMF 444 (e.g., N2 interface).

The NG-RAN 414 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.

In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 402 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 402, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 402 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 402 and in some cases at the gNB 416. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

The RAN 404 is communicatively coupled to CN 420 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 402). The components of the CN 420 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 420 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 420 may be referred to as a network slice, and a logical instantiation of a portion of the CN 420 may be referred to as a network sub-slice.

In some embodiments, the CN 420 may be an LTE CN 422, which may also be referred to as an EPC. The LTE CN 422 may include MME 424, SGW 426, SGSN 428, HSS 430, PGW 432, and PCRF 434 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 422 may be briefly introduced as follows.

The MME 424 may implement mobility management functions to track a current location of the UE 402 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.

The SGW 426 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 422. The SGW 426 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

The SGSN 428 may track a location of the UE 402 and perform security functions and access control. In addition, the SGSN 428 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 424; MME selection for handovers; etc. The S3 reference point between the MME 424 and the SGSN 428 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active states.

The HSS 430 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 430 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 430 and the MME 424 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 420.

The PGW 432 may terminate an SGi interface toward a data network (DN) 436 that may include an application/content server 438. The PGW 432 may route data packets between the LTE CN 422 and the data network 436. The PGW 432 may be coupled with the SGW 426 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 432 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 432 and the data network 436 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 432 may be coupled with a PCRF 434 via a Gx reference point.

The PCRF 434 is the policy and charging control element of the LTE CN 422. The PCRF 434 may be communicatively coupled to the app/content server 438 to determine appropriate QoS and charging parameters for service flows. The PCRF 432 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

In some embodiments, the CN 420 may be a 5GC 440. The 5GC 440 may include an AUSF 442, AMF 444, SMF 446, UPF 448, NSSF 450, NEF 452, NRF 454, PCF 456, UDM 458, and AF 460 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 440 may be briefly introduced as follows.

The AUSF 442 may store data for authentication of UE 402 and handle authentication- related functionality. The AUSF 442 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 440 over reference points as shown, the AUSF 442 may exhibit an Nausf service-based interface.

The AMF 444 may allow other functions of the 5GC 440 to communicate with the UE 402 and the RAN 404 and to subscribe to notifications about mobility events with respect to the UE 402. The AMF 444 may be responsible for registration management (for example, for registering UE 402), connection management, reachability management, mobility management, lawful interception of AMF -related events, and access authentication and authorization. The AMF 444 may provide transport for SM messages between the UE 402 and the SMF 446, and act as a transparent proxy for routing SM messages. AMF 444 may also provide transport for SMS messages between UE 402 and an SMSF. AMF 444 may interact with the AUSF 442 and the UE 402 to perform various security anchor and context management functions. Furthermore, AMF 444 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 404 and the AMF 444; and the AMF 444 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection. AMF 444 may also support NAS signaling with the UE 402 over an N3 IWF interface.

The SMF 446 may be responsible for SM (for example, session establishment, tunnel management between UPF 448 and AN 408); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 448 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 444 over N2 to AN 408; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 402 and the data network 436.

The UPF 448 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 436, and a branching point to support multi-homed PDU session. The UPF 448 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF- to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 448 may include an uplink classifier to support routing traffic flows to a data network.

The NSSF 450 may select a set of network slice instances serving the UE 402. The NSSF 450 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 450 may also determine the AMF set to be used to serve the UE 402, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 454. The selection of a set of network slice instances for the UE 402 may be triggered by the AMF 444 with which the UE 402 is registered by interacting with the NSSF 450, which may lead to a change of AMF. The NSSF 450 may interact with the AMF 444 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 450 may exhibit an Nnssf service-based interface.

The NEF 452 may securely expose services and capabilities provided by 3 GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 460), edge computing or fog computing systems, etc. In such embodiments, the NEF 452 may authenticate, authorize, or throttle the AFs. NEF 452 may also translate information exchanged with the AF 460 and information exchanged with internal network functions. For example, the NEF 452 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 452 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 452 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 452 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 452 may exhibit an Nnef service-based interface.

The NRF 454 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 454 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 454 may exhibit the Nnrf service-based interface.

The PCF 456 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 456 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 458. In addition to communicating with functions over reference points as shown, the PCF 456 exhibit an Npcf service-based interface.

The UDM 458 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 402. For example, subscription data may be communicated via an N8 reference point between the UDM 458 and the AMF 444. The UDM 458 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 458 and the PCF 456, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 402) for the NEF 452. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 458, PCF 456, and NEF 452 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM- FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 458 may exhibit the Nudm service-based interface.

The AF 460 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control. In some embodiments, the 5GC 440 may enable edge computing by selecting operator/3^rd party services to be geographically close to a point that the UE 402 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 440 may select a UPF 448 close to the UE 402 and execute traffic steering from the UPF 448 to data network 436 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 460. In this way, the AF 460 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 460 is considered to be a trusted entity, the network operator may permit AF 460 to interact directly with relevant NFs. Additionally, the AF 460 may exhibit an Naf service-based interface.

The data network 436 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 438.

Figure 5 schematically illustrates a wireless network 500 in accordance with various embodiments. The wireless network 500 may include a UE 502 in wireless communication with an AN 504. The UE 502 and AN 504 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.

The UE 502 may be communicatively coupled with the AN 504 via connection 506. The connection 506 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.

The UE 502 may include a host platform 508 coupled with a modem platform 510. The host platform 508 may include application processing circuitry 512, which may be coupled with protocol processing circuitry 514 of the modem platform 510. The application processing circuitry 512 may run various applications for the UE 502 that source/sink application data. The application processing circuitry 512 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations

The protocol processing circuitry 514 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 506. The layer operations implemented by the protocol processing circuitry 514 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

The modem platform 510 may further include digital baseband circuitry 516 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 514 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

The modem platform 510 may further include transmit circuitry 518, receive circuitry 520, RF circuitry 522, and RF front end (RFFE) 524, which may include or connect to one or more antenna panels 526. Briefly, the transmit circuitry 518 may include a digital -to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 520 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 522 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 524 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 518, receive circuitry 520, RF circuitry 522, RFFE 524, and antenna panels 526 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.

In some embodiments, the protocol processing circuitry 514 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.

A UE reception may be established by and via the antenna panels 526, RFFE 524, RF circuitry 522, receive circuitry 520, digital baseband circuitry 516, and protocol processing circuitry 514. In some embodiments, the antenna panels 526 may receive a transmission from the AN 504 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 526.

A UE transmission may be established by and via the protocol processing circuitry 514, digital baseband circuitry 516, transmit circuitry 518, RF circuitry 522, RFFE 524, and antenna panels 526. In some embodiments, the transmit components of the UE 504 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 526.

Similar to the UE 502, the AN 504 may include a host platform 528 coupled with a modem platform 530. The host platform 528 may include application processing circuitry 532 coupled with protocol processing circuitry 534 of the modem platform 530. The modem platform may further include digital baseband circuitry 536, transmit circuitry 538, receive circuitry 540, RF circuitry 542, RFFE circuitry 544, and antenna panels 546. The components of the AN 504 may be similar to and substantially interchangeable with like-named components of the UE 502. In addition to performing data transmission/reception as described above, the components of the AN 508 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

Figure 6 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 6 shows a diagrammatic representation of hardware resources 600 including one or more processors (or processor cores) 610, one or more memory/storage devices 620, and one or more communication resources 630, each of which may be communicatively coupled via a bus 640 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 602 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 600.

The processors 610 may include, for example, a processor 612 and a processor 614. The processors 610 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

The memory/storage devices 620 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 620 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

The communication resources 630 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 604 or one or more databases 606 or other network elements via a network 608. For example, the communication resources 630 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

Instructions 650 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 610 to perform any one or more of the methodologies discussed herein. The instructions 650 may reside, completely or partially, within at least one of the processors 610 (e.g., within the processor’s cache memory), the memory/storage devices 620, or any suitable combination thereof. Furthermore, any portion of the instructions 650 may be transferred to the hardware resources 600 from any combination of the peripheral devices 604 or the databases 606. Accordingly, the memory of processors 610, the memory/storage devices 620, the peripheral devices 604, and the databases 606 are examples of computer-readable and machine-readable media.

EXAMPLE PROCEDURES

In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 4-6, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in Figure 7. For example, process 700 may include, at 705, retrieving raw performance measurements related to a data management service associated with a unified data repository (UDR) from a memory. The process further includes, at 710, generating a performance measurement based on the raw performance measurements, wherein the generated performance measurement includes data set query information associated with the UDR. The process further includes, at 715, providing the generated performance measurement to a service consumer.

Another such process is illustrated in Figure 8. In this example, the process 800 includes, at 805, receiving, from a unified data repository (UDR), raw performance measurements related to a data management service. The process further includes, at 810, generating a performance measurement based on the raw performance measurements, wherein the generated performance measurement includes data set query information associated with the UDR. The process further includes, at 815, providing the generated performance measurement to a service consumer.

Another such process is illustrated in Figure 9. In this example, the process 900 includes, at 905, receiving, from a policy control function (PCF), raw performance measurements associated with background data transfer policy control. The process further includes, at 910, generating a performance measurement based on the raw performance measurements, wherein the generated performance measurement includes an indication of background data transfer policy creation information. The process further includes, at 915, providing the generated performance measurement to a service consumer.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

EXAMPLES

Example 1 may include the service producer for measurements supported by one or more processors, is configured to: obtain the raw performance measurements from UDR related to data management service. generate and provide the performance measurements based on the obtained raw performance measurements.

Example 2 may include the apparatus of example 2 or some other example herein, wherein the apparatus is located in UDR or in a management function.

Example 3 may include the method of example 1 or some other example herein, wherein the performance measurement is related to data set query.

Example 4 may include the method of example 3 or some other example herein, wherein the performance measurement is number of data set query requests, number of successful data set queries or number of failed data set queries

Example 5 may include the method of example 4 or some other example herein, wherein the number of data set query requests is obtained on receipt of an Nudr DM Query request by the UDR from an NF service consumer; the number of successful data set queries is obtained on transmission of an Nudr DM Query response by the UDR to an NF service consumer indicating a successful data set query; and the number of failed data set queries is obtained on transmission of an Nudr DM Query response by the UDR to an NF service consumer indicating a failed data set query, each message increments the relevant subcounter per failure cause by 1. Example 6 may include a service producer for measurements supported by one or more processors, is configured to: obtain the raw performance measurements from PCF related to background data transfer policy control. generate and provide the performance measurements based on the obtained raw performance measurements.

Example 7 may include the apparatus of example 6 or some other example herein, wherein the apparatus is located in PCF or in a management function.

Example 8 may include the method of example 6 or some other example herein, wherein the performance measurement is related to background data transfer policy creation.

Example 9 may include the method of example 8 or some other example herein, wherein the performance measurement is number of background data transfer policy creation requests, number of successful background data transfer policy creations or number of failed background data transfer policy creations.

Example 10 may include the method of example 9 or some other example herein, wherein the number of background data transfer policy creation requests is obtained on receipt of an Npcf BDTPolicyControl Create request by the PCF from an NEF; the number of successful background data transfer policy creations is obtained on transmission of an Npcf BDTPolicyControl Create response by the PCF to an NEF indicating a successful background data transfer policy creation; the number of failed background data transfer policy creations is obtained on transmission of an Npcf BDTPolicyControl Create response by the PCF to an NEF indicating a failed background data transfer policy creation, each message increments the relevant subcounter per failure cause by 1.

Example 11 includes a method comprising: receiving, by a service producer, raw performance measurements related to a data management service from a unified data repository (UDR). generating, by the service producer, one or more performance measurements based on the received raw performance measurements, wherein the one or more performance measurements include an indication of a number of data set query requests or a number of successful data set queries; and providing, by the service producer, the generated performance measurement to a consumer associated with the service producer. Example 12 includes the method of example 11 or some other example herein, wherein the service producer is implemented by a policy control function (PCF) or a management function.

Example 13 includes the method of example 11 or some other example herein, wherein the service producer generates a plurality of performance measurements, and the plurality of performance measurements further include an indication of: a number of failed data set queries, a number of background data transfer policy creation requests, a number of successful background data policy creations, or a number of failed background data transfer policy creations.

Example XI includes an apparatus comprising: memory to store raw performance measurements related to a data management service associated with a unified data repository (UDR); and processing circuitry, coupled with the memory, to: retrieve the raw performance measurements from the memory; and generate a performance measurement based on the raw performance measurements, wherein the generated performance measurement includes data set query information associated with the UDR; and provide the generated performance measurement to a service consumer.

Example X2 includes the apparatus of example XI or some other example herein, wherein the data set query information includes an indication of: a number of data set query requests, a number of successful data set queries, or a number of failed data set queries.

Example X3 includes the apparatus of example X2 or some other example herein, wherein the number of data set query requests is based on a number of Nudr DM Query requests by the UDR from a network function (NF) service consumer.

Example X4 includes the apparatus of example X2 or some other example herein, wherein the number of successful data set queries is based on a number of Nudr DM Query responses by the UDR to an NF service consumer that indicate a successful data set query.

Example X5 includes the apparatus of example X2 or some other example herein, wherein the number of failed data set queries is based on a number of Nudr DM Query responses by the UDR to an NF service consumer that indicate a failed data set query.

Example X6 includes the apparatus of any of examples XI -X5 or some other example herein, wherein the processing circuitry is further to implement a service producer adapted to generate the performance measurement and provide the generated performance measurement to the service consumer. Example X7 includes the apparatus of example X6 or some other example herein, wherein the service producer is implemented by a network function comprising the UDR, or by a management function.

Example X8 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause one or more functions of a service producer to: receive, from a unified data repository (UDR), raw performance measurements related to a data management service; generate a performance measurement based on the raw performance measurements, wherein the generated performance measurement includes data set query information associated with the UDR; and provide the generated performance measurement to a service consumer.

Example X9 includes the one or more computer readable media of example X8 or some other example herein, wherein the data set query information includes an indication of: a number of data set query requests, a number of successful data set queries, or a number of failed data set queries.

Example XI 0 includes the one or more computer readable media of example X9 or some other example herein, wherein the number of data set query requests is based on a number of Nudr DM Query requests by the UDR from a network function (NF) service consumer.

Example XI 1 includes the one or more computer readable media of example X9 or some other example herein, wherein the number of successful data set queries is based on a number of Nudr DM Query responses by the UDR to an NF service consumer that indicate a successful data set query.

Example X12 includes the one or more computer readable media of example X9 or some other example herein, wherein the number of failed data set queries is based on a number of Nudr DM Query responses by the UDR to an NF service consumer that indicate a failed data set query.

Example XI 3 includes the one or more computer readable media of any of examples X8- X12, wherein the service producer is implemented by a network function comprising the UDR, or by a management function.

Example X14 includes an apparatus comprising: memory to store raw performance measurements related to background data transfer policy control associated with a policy control function (PCF); and processing circuitry, coupled with the memory, to: retrieve the raw performance measurements from the memory; and generate a performance measurement based on the raw performance measurements, wherein the generated performance measurement includes an indication of background data transfer policy creation information; and provide the generated performance measurement to a service consumer.

Example XI 5 includes the apparatus of example X14 or some other example herein, wherein the background data transfer policy creation information includes an indication of: a number of background data transfer policy creation requests, a number of successful background data transfer policy creations, or a number of failed background data transfer policy creations.

Example XI 6 includes the apparatus of example XI 5 or some other example herein, wherein: the number of background data transfer policy creation requests is based on a number of Npcf BDTPolicyControl Create requests received by the PCF from one or more network exposure functions (NEFs); the number of successful background data transfer policy creations is based on a number of Npcf BDTPolicyControl Create responses to the one or more NEFs indicating a successful background data transfer policy creation; and the number of failed background data transfer policy creations is based on a number of Npcf BDTPolicyControl Create responses to the one or more NEFs indicating a failed background data transfer policy creation.

Example X17 includes the apparatus of any of examples X14-X16, wherein the service producer is implemented by the PCF or by a management function.

Example XI 8 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a service producer to: receive, from a policy control function (PCF), raw performance measurements associated with background data transfer policy control; generate a performance measurement based on the raw performance measurements, wherein the generated performance measurement includes an indication of background data transfer policy creation information; and provide the generated performance measurement to a service consumer.

Example XI 9 includes the one or more computer-readable media of example XI 8 or some other example herein, wherein the background data transfer policy creation information includes an indication of: a number of background data transfer policy creation requests, a number of successful background data transfer policy creations, or a number of failed background data transfer policy creations. Example X20 includes the one or more computer-readable media of example XI 9 or some other example herein, wherein: the number of background data transfer policy creation requests is based on a number of Npcf BDTPolicyControl Create requests received by the PCF from one or more network exposure functions (NEFs); the number of successful background data transfer policy creations is based on a number of Npcf BDTPolicyControl Create responses to the one or more NEFs indicating a successful background data transfer policy creation; and the number of failed background data transfer policy creations is based on a number of Npcf BDTPolicyControl Create responses to the one or more NEFs indicating a failed background data transfer policy creation.

Example X21 includes the one or more computer-readable media of any of examples X18-X20 or some other example herein, wherein the service producer is implemented by the PCF or by a management function.

Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-X21, or any other method or process described herein.

Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1- X21, or any other method or process described herein.

Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1- X21, or any other method or process described herein.

Example Z04 may include a method, technique, or process as described in or related to any of examples 1- X21, or portions or parts thereof.

Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1- X21, or portions thereof.

Example Z06 may include a signal as described in or related to any of examples 1- X21, or portions or parts thereof. Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1- X21, or portions or parts thereof, or otherwise described in the present disclosure.

Example Z08 may include a signal encoded with data as described in or related to any of examples 1- X21, or portions or parts thereof, or otherwise described in the present disclosure.

Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1- X21, or portions or parts thereof, or otherwise described in the present disclosure.

Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1- X21, or portions thereof.

Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1- X21, or portions thereof.

Example Z12 may include a signal in a wireless network as shown and described herein.

Example Z13 may include a method of communicating in a wireless network as shown and described herein.

Example Z14 may include a system for providing wireless communication as shown and described herein.

Example Z15 may include a device for providing wireless communication as shown and described herein.

Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Abbreviations

Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 vl6.0.0 (2019-06). For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein. 3 GPP Third AP Application 70 BCH Broadcast Generation Protocol, Channel

Partnership Antenna Port, BER Bit Error

Project Access Point Ratio 4G Fourth 40 API Application BFD Beam Generation Programming 75 Failure Detection 5G Fifth Interface BLER Block Error Generation APN Access Point Rate 5GC 5G Core Name BPSK Binary Phase network 45 ARP Allocation Shift Keying AC and Retention 80 BRAS Broadband

Application Priority Remote Access

Client ARQ Automatic Server

ACK Repeat Request BSS Business

Acknowledge 50 AS Access Support System ment Stratum 85 BS Base Station

ACID ASP BSR Buffer Status

Application Application Service Report Client Identification Provider BW Bandwidth AF Application 55 BWP Bandwidth Function ASN.l Abstract 90 Part AM Syntax Notation C-RNTI Cell

Acknowledge One Radio Network d Mode AUSF Temporary

AMBRAggregate 60 Authenticatio Identity Maximum Bit Rate n Server 95 CA Carrier AMF Access and Function Aggregation, Mobility AWGN Certification

Management Additive Authority Function 65 White Gaussian CAPEX AN Access Noise 100 CAPital Network BAP Backhaul Expenditure

ANR Automatic Adaptation CBRA Contention Neighbour Protocol Based Random

Relation Access CC Component CK Cipher Key Central Carrier, CM Connection Processing

Country Management, Unit

Code, Cryptographic Conditional C/R Checksum 40 Mandatory 75 Command/Re

CCA Clear Channel CMAS Commercial sponse field bit Assessment Mobile Alert CRAN Cloud Radio CCE Control Service Access Channel Element CMD Command Network, CCCH Common 45 CMS Cloud 80 Cloud RAN Control Channel Management System CRB Common CE Coverage CO Conditional Resource Block Enhancement Optional CRC Cyclic CDM Content CoMP Coordinated Redundancy Check Delivery Network 50 Multi-Point 85 CRI Channel-State CDMA Code- CORESET Information Division Multiple Control Resource Access Resource Set Indicator, CSI-RS

CFRA Contention COTS Commercial Resource Free Random 55 Off-The-Shelf 90 Indicator Access CP Control Plane, C-RNTI Cell

CG Cell Group Cyclic Prefix, RNTI CGF Connection CS Circuit

Charging Gateway Point Switched

Function 60 CPD Connection 95 CSAR Cloud Service

CHF Point Descriptor Archive

Charging Function CPE Customer CSI Channel-State Cl Cell Identity Premise Information CID Cell-ID (e g., Equipment CSI-IM CSI positioning 65 CPICHCommon 100 Interference method) Pilot Channel Measurement

CIM Common CQI Channel CSI-RS CSI Information Model Quality Indicator Reference Signal CIR Carrier to CPU CSI CSI-RSRP CSI Interference Ratio 70 processing unit, 105 reference signal received DCI Downlink DwPTS power 35 Control Downlink

CSI-RSRQ CSI Information Pilot Time Slot reference signal DF Deployment 70 E-LAN received Flavour Ethernet quality DL Downlink Local Area

CSI-SINR CSI 40 DMTF Distributed Network signal-to-noise and Management Task E2E End-to-End interference Force 75 ECCA extended clear ratio DPDK Data Plane channel

CSMA Carrier Sense Development Kit assessment, Multiple 45 DM-RS, DMRS extended CCA

Access Demodulation ECCE Enhanced

CSMA/CA Reference Signal 80 Control Channel

CSMA with DN Data network Element, collision DNN Data Enhanced CCE avoidance 50 Network Name ED Energy CSS Common DNAI Data Detection Search Space, Cell- Network Access 85 EDGE Enhanced specific Identifier Datarates for GSM Search Space Evolution CTF 55 DRB Data Radio (GSM Evolution)

Charging Trigger Bearer EAS Edge Function DRS Discovery 90 Application Server

CTS Clear-to-Send Reference Signal EASID Edge CW Codeword DRX Discontinuous Application Server CWS Contention 60 Reception Identification Window Size DSL Domain ECS Edge D2D Device-to- Specific Language. 95 Configuration Server Device Digital ECSP Edge DC Dual Subscriber Line Computing Service Connectivity, Direct 65 DSLAM DSL Provider Current Access Multiplexer EDN Edge

100 Data Network EEC Edge 35 eNB evolved 70 Integrated Circuit

Enabler Client NodeB, E-UTRAN Card EECID Edge Node B E-UTRA

Enabler Client EN-DC E- Evolved

Identification UTRA-NR Dual UTRA EES Edge 40 Connectivity 75 E-UTRAN

Enabler Server EPC Evolved Evolved EESID Edge Packet Core UTRAN

Enabler Server EPDCCH EV2X Enhanced

Identification enhanced V2X EHE Edge 45 PDCCH, enhanced 80 FIAP FI

Hosting Environment Physical Application Protocol EGMF Exposure Downlink Control Fl-C FI Control Governance Cannel plane interface

Management EPRE Energy per Fl-U FI User plane

Function 50 resource 85 interface

EGPRS element FACCH Fast

Enhanced EPS Evolved Associated Control

GPRS Packet System CHannel

EIR Equipment EREG enhanced FACCH/F Fast Identity 55 REG, enhanced 90 Associated Control

Register resource Channel/Full eLAA enhanced element groups rate Licensed Assisted ETSI European FACCH/H Fast Access, Telecommuni Associated Control enhanced LAA 60 cations 95 Channel/Half EM Element Standards rate Manager Institute FACH Forward eMBB Enhanced ETWS Earthquake Access Channel Mobile and Tsunami FAUSCH Fast

Broadband 65 Warning 100 Uplink Signalling EMS Element System Channel Management eUICC embedded FB Functional System UICC, embedded Block Universal FBI Feedback FPGA Field- centralized Information 35 Programmable Gate 70 unit FCC Federal Array gNB-DU gNB- Communications FR Frequency distributed unit, Next

Commission Range Generation FCCH Frequency FQDN Fully NodeB Correction 40 Qualified Domain 75 distributed

CHannel Name unit

FDD Frequency G-RNTI GNSS Global Division Duplex GERAN Navigation Satellite FDM Frequency Radio Network System Division 45 Temporary 80 GPRS General

Multiplex Identity Packet Radio Service FDM A Frequency GERAN GPSI Generi Division GSM EDGE c Public Subscription

Multiple RAN, GSM EDGE Identifier

Access 50 Radio Access 85 GSM Global

FE Front End Network System for Mobile

FEC Forward Error GGSN Gateway Communicati

Correction GPRS Support ons, Groupe

FFS For Further Node Special

Study 55 GLONASS 90 Mobile

FFT Fast Fourier GLObal'naya GTP GPRS Transformatio NAvigatsionn Tunneling Protocol n aya Sputnikovaya GTP-UGPRS feLAA further Si sterna (Engl.: Tunnelling Protocol enhanced Licensed 60 Global Navigation 95 for User Plane Assisted Satellite GTS Go To Sleep Access, further System) Signal (related enhanced gNB Next to WUS)

LAA Generation NodeB GUMMEI

FN Frame 65 gNB-CU gNB- 100 Globally Number centralized unit, Next Unique MME Generation Identifier

NodeB GUTI Globally HTTP Hyper Text IEI Information Unique Temporary 35 Transfer Element UE Identity Protocol 70 Identifier HARQ Hybrid ARQ, HTTPS Hyper IEIDL Information Hybrid Text Transfer Element

Automatic Protocol Identifier Repeat Request 40 Secure (https is Data Length HANDO Handover http/ 1.1 over 75 IETF Internet HFN HyperFrame SSL, i.e. port 443) Engineering Task Number I-Block Force HHO Hard Information IF Infrastructure Handover 45 Block IM Interference HER Home ICCID Integrated 80 Measurement, Location Register Circuit Card Intermodulati HN Home Identification on, IP Multimedia Network IAB Integrated IMC IMS HO 50 Access and Credentials

Handover Backhaul 85 IMEI International

HPLMN Home ICIC Inter-Cell Mobile Public Land Mobile Interference Equipment Network Coordination Identity

HSDPA High 55 ID Identity, IMGI International

Speed Downlink identifier 90 mobile group

Packet Access IDFT Inverse identity HSN Hopping Discrete Fourier IMPI IP Multimedia Sequence Number Transform Private HSPA High Speed 60 IE Information Identity Packet Access element 95 IMPU IP Multimedia HSS Home IBE In-Band PUblic Subscriber Server Emission identity HSUPA High IEEE Institute of IMS IP Multimedia

Speed Uplink Packet 65 Electrical and Subsystem Access Electronics 100 IMSI International

Engineers Mobile Subscriber 35 I-WLAN 70 L2 Layer 2 (data

Identity Interworking link layer)

IoT Internet of WLAN L3 Layer 3

Things Constraint (network layer)

IP Internet length of the LAA Licensed

Protocol 40 convolutional 75 Assisted Access

Ipsec IP Security, code, USIM LAN Local Area Internet Individual key Network

Protocol LADN Local

Security kB Kilobyte Area Data Network

IP-CAN IP- 45 (1000 bytes) 80 LBT Listen Before Connectivity Access kbps kilo-bits per Talk Network second LCM LifeCycle

IP-M IP Multicast Kc Ciphering key Management IPv4 Internet Ki Individual LCR Low Chip Protocol Version 4 50 subscriber 85 Rate IPv6 Internet authentication LCS Location Protocol Version 6 key Services IR Infrared KPI Key LCID Logical IS In Sync Performance Channel ID

IRP Integration 55 Indicator 90 LI Layer Reference Point KQI Key Quality Indicator ISDN Integrated Indicator LLC Logical Link Services Digital KSI Key Set Control, Low Layer Network Identifier Compatibility

ISIM IM Services 60 ksps kilo-symbols 95 LPLMN Local Identity Module per second PLMN ISO International KVM Kernel Virtual LPP LTE Organisation for Machine Positioning Protocol Standardisation LI Layer 1 LSB Least ISP Internet 65 (physical layer) 100 Significant Bit Service Provider Ll-RSRP Layer LTE Long Term IWF Interworking- 1 reference signal Evolution Function received LWA LTE-WLAN power aggregation LWIP LTE/WLAN Multicast MGRP Measurement Radio Level Service Gap Repetition

Integration MBSFN Period with IP sec Multimedia MIB Master

Tunnel 40 Broadcast 75 Information Block,

LTE Long Term multicast Management Evolution service Single Information Base

M2M Machine-to- Frequency MIMO Multiple Input Machine Network Multiple Output MAC Medium 45 MCC Mobile 80 MLC Mobile Access Control Country Code Location Centre (protocol MCG Master Cell MM Mobility layering context) Group Management MAC Message MCOT Maximum MME Mobility authentication code 50 Channel 85 Management Entity (security/ encry pti on Occupancy MN Master Node context) Time MNO Mobile

MAC-A MAC MCS Modulation Network Operator used for and coding MO Measurement authentication 55 scheme 90 Object, and key MDAF Management Mobile agreement Data Analytics Originated (TSG T WG3 Function MPBCH MTC context) MD AS Management Physical Broadcast

MAC-IMAC used for 60 Data Analytics 95 CHannel data integrity of Service MPDCCH MTC signalling messages MDT Minimization Physical Downlink (TSG T WG3 of Drive Tests Control context) ME Mobile CHannel

MANO 65 Equipment 100 MPDSCH MTC

Management MeNB master eNB Physical Downlink and Orchestration MER Message Shared MBMS Error Ratio CHannel

Multimedia MGL Measurement MPRACH MTC Broadcast and 70 Gap Length 105 Physical Random Access 35 Communicati NEF Network CHannel ons Exposure

MPUSCH MTC mMTCmassive 70 Function Physical Uplink MTC, massive NF Network Shared Machine- Function

Channel 40 Type NFP Network

MPLS Multiprotocol Communicati Forwarding Path Label Switching ons 75 NFPD Network MS Mobile MU-MIMO Multi Forwarding Path Station User MIMO Descriptor MSB Most 45 MWUS MTC NFV Network Significant Bit wake-up signal, MTC Functions MSC Mobile wus 80 Virtualization Switching Centre NACK Negative NFVI NFV MSI Minimum Acknowledgement Infrastructure System 50 NAI Network NFVO NFV

Information, Access Identifier Orchestrator MCH Scheduling NAS Non-Access 85 NG Next Information Stratum, Non- Generation, Next Gen MSID Mobile Access NGEN-DC NG- Station Identifier 55 Stratum layer RAN E-UTRA-NR MSIN Mobile NCT Network Dual Connectivity Station Connectivity 90 NM Network

Identification Topology Manager

Number NC-JT Non- NMS Network

MSISDN 60 Coherent Joint Management

Mobile Transmission System

Subscriber ISDN NEC Network 95 N-PoP Network Number Capability Point of Presence MT Mobile Exposure NMIB, N-MIB Terminated, Mobile 65 NE-DC NR-E- Narrowband MIB Termination UTRA Dual NPBCH MTC Machine- Connectivity 100 Narrowband Type Physical Broadcast 35 NRS Narrowband 70 OFDMA CHannel Reference Signal Orthogonal NPDCCH NS Network Frequency

Narrowband Service Division

Physical NS A Non- Multiple Access

Downlink 40 Standalone operation 75 OOB Out-of-band Control CHannel mode OO S Out of NPDSCH NSD Network Sync

Narrowband Service Descriptor OPEX OPerating

Physical NSR Network EXpense

Downlink 45 Service Record 80 OSI Other System Shared CHannel NSSAINetwork Slice Information NPRACH Selection OSS Operations

Narrowband Assistance Support System

Physical Information OTA over-the-air

Random 50 S-NNSAI 85 PAPR Peak-to- Access CHannel Single-NSSAI Average Power NPUSCH NSSF Network Slice Ratio

Narrowband Selection PAR Peak to Physical Uplink Function Average Ratio Shared CHannel 55 NW Network 90 PBCH Physical NPSS Narrowband NWU S N arrowb and Broadcast Channel Primary wake-up signal, PC Power

Synchronizati N arrowb and WU S Control, Personal on Signal NZP Non-Zero Computer

NSSS Narrowband 60 Power 95 PCC Primary Secondary O&M Operation and Component

Synchronizati Maintenance Carrier, on Signal ODU2 Optical Primary CC

NR New Radio, channel Data Unit - PCell Primary Cell Neighbour 65 type 2 100 PCI Physical Cell

Relation OFDM Orthogonal ID, Physical Cell NRF NF Frequency Identity Repository Function Division PCEF Policy and

Multiplexing Charging Enforcement P-GW PDN Gateway 70 PRB Physical

Function PHICH resource block PCF Policy Physical PRG Physical Control Function hybrid-ARQ resource block PCRF Policy 40 indicator group

Control and Charging channel 75 ProSe Proximity Rules PHY Physical layer Services, Function PLMN Public Land Proximity-

PDCP Packet Data Mobile Based Service Convergence 45 Network PRS Positioning

Protocol, PIN Personal 80 Reference Signal Packet Data Identification PRR Packet

Convergence Number Reception Radio Protocol layer PM Performance PS Packet PDCCH 50 Measurement Services

Physical PMI Precoding 85 PSBCH

Downlink Control Matrix Indicator Physical Channel PNF Physical Sidelink Broadcast

PDCP Packet Data Network Function Channel Convergence 55 PNFD Physical PSDCH

Protocol Network Function 90 Physical

PDN Packet Data Descriptor Sidelink Downlink Network, Public PNFR Physical Channel Data Network Network Function PSCCH PDSCH 60 Record Physical

Physical POC PTT over 95 Sidelink Control

Downlink Shared Cellular Channel Channel PP, PTP Point- PSSCH

PDU Protocol Data to-Point Physical Unit 65 PPP Point-to-Point Sidelink Shared

PEI Permanent Protocol 100 Channel Equipment PRACH PSCell Primary SCell

Identifiers Physical PSS Primary PFD Packet Flow RACH Synchronization Description Signal PSTN Public RA-RNTI RF Radio Switched Telephone 35 Random Frequency Network Access RNTI 70 RI Rank PT-RS Phase- RAB Radio Access Indicator tracking reference Bearer, RIV Resource signal Random indicator value

PTT Push-to-Talk 40 Access Burst RL Radio Link PUCCH RACH Random 75 RLC Radio Link

Physical Access Channel Control, Radio Uplink Control RADIUS Link Control Channel Remote layer PUSCH 45 Authentication Dial RLC AM RLC

Physical In User 80 Acknowledged Mode Uplink Shared Service RLC UM RLC Channel RAN Radio Access Unacknowledged

QAM Quadrature Network Mode Amplitude 50 RAND RANDo RLF Radio Link

Modulation number (used for 85 Failure QCI QoS class of authentication RLM Radio Link identifier ) Monitoring

QCL Quasi co- RAR Random RLM-RS location 55 Access Response Reference

QFI QoS Flow ID, RAT Radio Access 90 Signal for RLM QoS Flow Technology RM Registration Identifier RAU Routing Area Management

QoS Quality of Update RMC Reference Service 60 RB Resource Measurement

QPSK Quadrature block, Radio Bearer 95 Channel (Quaternary) Phase RBG Resource RMSI Remaining Shift Keying block group MSI, Remaining

QZSS Quasi-Zenith REG Resource Minimum Satellite 65 Element Group System

System Rel Release 100 Information REQ REQuest RN Relay Node RNC Radio 35 RTP Real Time 70 SAPI Service Network Controller Protocol Access Point RNL Radio RTS Ready-To- Identifier Network Layer Send SCC Secondary RNTI Radio RTT Round Trip Component Network Temporary 40 Time 75 Carrier, Identifier Rx Reception, Secondary CC ROHC RObust Receiving, SCell Secondary Header Receiver Cell

Compression S1AP SI SCEF RRC Radio 45 Application Protocol 80 Service Resource Control, Sl-MME SI for Capability Exposure Radio the control plane Function

Resource Control Sl-U SI for the SC-FDMA Single layer user plane Carrier Frequency RRM Radio 50 S-GW Serving 85 Division Resource Gateway Multiple Access

Management S-RNTI SRNC SCG Secondary RS Reference Radio Network Cell Group Signal Temporary SCM Security

RSRP Reference 55 Identity 90 Context Signal Received S-TMSI SAE Management Power Temporary Mobile SCS Sub carrier

RSRQ Reference Station Spacing Signal Received Identifier SCTP Stream Quality 60 SA Standalone 95 Control

RSSI Received operation mode Transmission Signal Strength SAE System Protocol Indicator Architecture SDAP Service Data RSU Road Side Evolution Adaptation Unit 65 SAP Service 100 Protocol,

RSTD Reference Access Point Service Data Signal Time SAPD Service Adaptation difference Access Point Protocol layer

Descriptor SDL S-GW Serving SON Self-

Supplementar Gateway Organizing Network y Downlink SI System SpCell Special Cell SDNF Structured Information SP-CSI-RNTISemi- Data Storage 40 SI-RNTI 75 Persistent CSI RNTI

Network System SPS Semi- Function Information RNTI Persistent Scheduling SDP Session SIB System SQN Sequence Description Information Block number

Protocol 45 SIM Subscriber 80 SR Scheduling

SDSF Structured Identity Module Request Data Storage SIP Session SRB Signalling

Function Initiated Protocol Radio Bearer

SDU Service Data SiP System in SRS Sounding Unit 50 Package 85 Reference Signal

SEAF Security SL Sidelink SS Anchor Function SLA Service Level Synchronizati SeNB secondary Agreement on Signal eNB SM Session SSB

SEPP Security Edge 55 Management 90 Synchronizati Protection Proxy SMF Session on Signal Block SFI Slot format Management SSID Sendee Set indication Function Identifier SFTD Space- SMS Short SS/PBCH Block Frequency Time 60 Message Service 95 SSBRI SS/PBCH Diversity, SMSF SMS Function Block Resource

SFN and frame SMTC S SB-based Indicator, timing Measurement Synchronization difference Timing Signal Block

SFN System Frame 65 Configuration 100 Resource Number SN Secondary Indicator

SgNB Secondary Node, Sequence SSC Session and gNB Number Service

SGSN Serving SoC System on Continuity GPRS Support Node 70 Chip SS-RSRP TAC Tracking Area 70 TMSI Temporary

Synchronizati Code Mobile on Signal based TAG Timing Subscriber Reference Advance Group Identity Signal Received 40 TAI TNL Transport Power Tracking Area 75 Network Layer SS-RSRQ Identity TPC Transmit

Synchronizati TAU Tracking Area Power Control on Signal based Update TPMI Transmitted

Reference 45 TB Transport Precoding Matrix Signal Received Block 80 Indicator Quality TBS Transport TR Technical SS-SINR Block Size Report

Synchronizati TBD To Be TRP, TRxP on Signal based 50 Defined Transmission

Signal to TCI Transmission 85 Reception Point Noise and Configuration TRS Tracking

Interference Ratio Indicator Reference Signal SSS Secondary TCP Transmission TRx Transceiver Synchronization 55 Communicati TS Technical Signal on Protocol 90 Specifications,

SSSG Search Space TDD Time Division Technical Set Group Duplex Standard

SSSIF Search Space TDM Time Division TTI Transmission Set Indicator 60 Multiplexing Time Interval SST Slice/Service TDMATime Division 95 Tx Transmission, Types Multiple Transmitting,

SU-MIMO Single Access Transmitter User MIMO TE Terminal U-RNTI SUL 65 Equipment UTRAN

Supplementar TEID Tunnel End 100 Radio Network y Uplink Point Identifier Temporary TA Timing TFT Traffic Flow Identity Advance, Tracking Template UART Universal Area Asynchronous Receiver and 35 URLLC Ultra- 70 VM Virtual

Transmitter Reliable and Low Machine UCI Uplink Latency VNF Virtualized Control Information USB Universal Network UE User Serial Bus Function Equipment 40 USIM Universal 75 VNFFG VNF UDM Unified Data Subscriber Identity Forwarding Graph Management Module VNFFGD VNF UDP User USS UE-specific Forwarding Graph Datagram Protocol search space Descriptor UDSF Unstructured 45 UTRA UMTS 80 VNFMVNF Manager Data Storage Terrestrial Radio VoIP Voice-over-

Network Access IP, Voice-over- Function UTRAN Internet UICC Universal Universal Protocol Integrated Circuit 50 Terrestrial Radio 85 VPLMN

Card Access Visited Public

UL Uplink Network Land Mobile UM UwPTS Uplink Network

Unacknowled Pilot Time Slot VPN Virtual ged Mode 55 V2I Vehicle-to- 90 Private Network UML Unified Infrastruction VRB Virtual Modelling Language V2P Vehicle-to- Resource Block UMTS Universal Pedestrian WiMAX Mobile V2V Vehicle-to- Worldwide

Telecommuni 60 Vehicle 95 Interoperability cations System V2X Vehicle-to- for UP User Plane everything Microwave Access

UPF User Plane VIM Virtualized WLANWireless Function Infrastructure Local Area URI Uniform 65 Manager 100 Network Resource Identifier VL Virtual Link, WMAN URL Uniform VLAN Virtual LAN, Wireless Resource Locator Virtual Local Area Metropolitan Area Network Network WPANWireless Personal Area Network

X2-C X2-Control plane

X2-U X2-User plane

XML extensible Markup Language

XRES EXpected user RESponse XOR exclusive OR ZC Zadoff-Chu ZP Zero Power

Terminology

For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer- executable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like. The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.

The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/sy stems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.

The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.

The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content.

The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration .

The term “SSB” refers to an SS/PBCH block. The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.

The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.

The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC. The term “Serving Cell” refers to the primary cell for a UE in RRC CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.

The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC CONNECTED configured with CA /.

The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

Claims

CLAIMS What is claimed is:

1. An apparatus comprising: memory to store raw performance measurements related to a data management service associated with a unified data repository (UDR); and processing circuitry, coupled with the memory, to: retrieve the raw performance measurements from the memory; and generate a performance measurement based on the raw performance measurements, wherein the generated performance measurement includes data set query information associated with the UDR; and provide the generated performance measurement to a service consumer.

2. The apparatus of claim 1, wherein the data set query information includes an indication of: a number of data set query requests, a number of successful data set queries, or a number of failed data set queries.

3. The apparatus of claim 2, wherein the number of data set query requests is based on a number of Nudr DM Query requests by the UDR from a network function (NF) service consumer.

4. The apparatus of claim 2, wherein the number of successful data set queries is based on a number of Nudr DM Query responses by the UDR to an NF service consumer that indicate a successful data set query.

5. The apparatus of claim 2, wherein the number of failed data set queries is based on a number of Nudr DM Query responses by the UDR to an NF service consumer that indicate a failed data set query.

6. The apparatus of any of claims 1-5, wherein the processing circuitry is further to implement a service producer adapted to generate the performance measurement and provide the generated performance measurement to the service consumer.

7. The apparatus of claim 6, wherein the service producer is implemented by a network function comprising the UDR, or by a management function.

8. One or more computer-readable media storing instructions that, when executed by one or more processors, cause one or more functions of a service producer to: receive, from a unified data repository (UDR), raw performance measurements related to a data management service; generate a performance measurement based on the raw performance measurements, wherein the generated performance measurement includes data set query information associated with the UDR; and provide the generated performance measurement to a service consumer.

9. The one or more computer readable media of claim 8, wherein the data set query information includes an indication of: a number of data set query requests, a number of successful data set queries, or a number of failed data set queries.

10. The one or more computer readable media of claim 9, wherein the number of data set query requests is based on a number of Nudr DM Query requests by the UDR from a network function (NF) service consumer.

11. The one or more computer readable media of claim 9, wherein the number of successful data set queries is based on a number of Nudr DM Query responses by the UDR to an NF service consumer that indicate a successful data set query.

12. The one or more computer readable media of claim 9, wherein the number of failed data set queries is based on a number of Nudr DM Query responses by the UDR to an NF service consumer that indicate a failed data set query.

13. The one or more computer readable media of any of claims 8-12, wherein the service producer is implemented by a network function comprising the UDR, or by a management function.

14. An apparatus comprising: memory to store raw performance measurements related to background data transfer policy control associated with a policy control function (PCF); and processing circuitry, coupled with the memory, to: retrieve the raw performance measurements from the memory; and generate a performance measurement based on the raw performance measurements, wherein the generated performance measurement includes an indication of background data transfer policy creation information; and provide the generated performance measurement to a service consumer.

15. The apparatus of claim 14, wherein the background data transfer policy creation information includes an indication of: a number of background data transfer policy creation requests, a number of successful background data transfer policy creations, or a number of failed background data transfer policy creations.

16. The apparatus of claim 15, wherein: the number of background data transfer policy creation requests is based on a number of Npcf BDTPolicyControl Create requests received by the PCF from one or more network exposure functions (NEFs); the number of successful background data transfer policy creations is based on a number of Npcf BDTPolicyControl Create responses to the one or more NEFs indicating a successful background data transfer policy creation; and the number of failed background data transfer policy creations is based on a number of Npcf BDTPolicyControl Create responses to the one or more NEFs indicating a failed background data transfer policy creation.

17. The apparatus of any of claims 14-16, wherein the service producer is implemented by the PCF or by a management function.

18. One or more computer-readable media storing instructions that, when executed by one or more processors, cause a service producer to: receive, from a policy control function (PCF), raw performance measurements associated with background data transfer policy control; generate a performance measurement based on the raw performance measurements, wherein the generated performance measurement includes an indication of background data transfer policy creation information; and provide the generated performance measurement to a service consumer.

19. The one or more computer-readable media of claim 18, wherein the background data transfer policy creation information includes an indication of: a number of background data transfer policy creation requests, a number of successful background data transfer policy creations, or a number of failed background data transfer policy creations.

20. The one or more computer-readable media of claim 19, wherein: the number of background data transfer policy creation requests is based on a number of

Npcf BDTPolicyControl Create requests received by the PCF from one or more network exposure functions (NEFs); the number of successful background data transfer policy creations is based on a number of Npcf BDTPolicyControl Create responses to the one or more NEFs indicating a successful background data transfer policy creation; and the number of failed background data transfer policy creations is based on a number of Npcf BDTPolicyControl Create responses to the one or more NEFs indicating a failed background data transfer policy creation.

21. The one or more computer-readable media of any of claims 18-20, wherein the service producer is implemented by the PCF or by a management function.