CN116783873A

CN116783873A - Performance measurement for data management and background data transfer policy control for next generation systems

Info

Publication number: CN116783873A
Application number: CN202280010553.8A
Authority: CN
Inventors: 姚羿志; 乔伊·周
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2021-02-19
Filing date: 2022-02-17
Publication date: 2023-09-19
Also published as: WO2022178127A1

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 measurement for data management and background data transfer policy control for next generation systems

Cross Reference to Related Applications

The present application claims priority from U.S. provisional patent application No. 63/151,513, filed on 19 months 2 of 2021.

Technical Field

Various embodiments may relate generally 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 the next generation wireless system, a unified data warehouse (unified data repository, UDR) provides data management services and application related data to subscribers. The data management services provided by the UDR allow its consumers (e.g., unified data manager (unified data manager, UDM), policy control function (policy control function, PCF), and network exposure function (network exposure function, NEF)) to read, create, update, delete specific datasets, and subscribe/unsubscribe to notifications of related data changes, among other things. In addition, the PCF provides services to the NEF to control the background data transfer policies, including creation and updating of the background data transfer policies.

However, the user's service may not be fulfilled due to a data management service failure, and the user's performance of the background data transfer related service depends on the background data transfer policy. Embodiments of the present disclosure address these and other problems by helping to monitor the performance of background data transfer policy control and data management services.

Drawings

The embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To aid in 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.

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

Fig. 2 illustrates an example of a 5G performance measurement generation method in accordance with various embodiments.

Fig. 3A illustrates an example of a service generator operating in conjunction with a UDR in accordance with various embodiments.

Fig. 3B illustrates an example of a service generator operating in conjunction with a PCF, in accordance with various embodiments.

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

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

Fig. 6 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some example embodiments.

Fig. 7, 8, and 9 depict examples of processes 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 the particular architecture, interfaces, techniques, etc., in order to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to one having ordinary skill in the art having had 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 some 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 this document, the phrases "A or B" and "A/B" mean (A), (B) or (A and B).

As introduced above, the UDR provides data management services and application related data for subscribers, the application related data comprising: subscribing to data; policy data; structured data for exposure; application data, such as packet flow descriptions (packet Flow Description, PFD) for application detection and AF request information about a plurality of UEs; or a Network Function (NF) group ID corresponding to a subscriber identifier (e.g., IMPI, IMPU, SUPI).

The data management services provided by the UDR allow its customers (e.g., UDM, PCF, and NEF) to read, create, update, delete specific datasets, and subscribe/unsubscribe to notifications of related data changes. However, the user's service may not be fulfilled due to failure of the data management service, and thus, it is essential to be able to monitor the performance of the data management service.

For background data transfer, the application function (application function, AF) may need to negotiate policies with the 5GS via NEF and apply the negotiated policies to future PDU sessions. The PCF provides services to the NEF to control the background data transfer policies, including creation and updating of the background data transfer policies. The fulfillment of the background data transfer related services for the user depends on the background data transfer policy. Therefore, it is necessary to monitor the performance of the background data transfer policy control.

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

Fig. 1 illustrates an example of a fifth generation (5G) system architecture, while fig. 2 illustrates an example of a 5G performance measurement generation method, i.e., generation of performance measurements for a network slice selection function (network slice selection function, NSSF), in accordance with various embodiments. In the example shown in fig. 2, the service generator collects raw performance measurements from the NF and then generates performance measurements for the NF for its customers.

In particular, for some embodiments, the NF is a UDR or PCF, and the service generator may be implemented within the NF or in a separate management system. Fig. 3A illustrates one example (on the left) in which the service generator is implemented by a UDR, and another example (on the right) in which the service generator is implemented by a separate management system in communication with the two UDRs that provide the raw performance measurements. Similarly, fig. 3B illustrates one example (on the left) in which the service generator is implemented by a PCF, and another example (on the right) in which the service generator is implemented by a separate management system in communication with the two PCFs that provide raw performance measurements.

The present disclosure next describes examples of performance measurements that may be generated based on raw performance measurements according to various embodiments. For example, these generated measurements may be added to section 5.9 of 3GPP TS 28.552,v.16.8.0,2020-12-16, as indicated by the following numbering.

5.9 definition of Performance measurements

X.1 data management related measurements

5.x.1.1 dataset query

Number of data set query requests of x.1.1.1

a) This measurement provides the number of data set query requests received by the UDR.

b)CC

c) The UDR receives a nudr_dm_query request from an NF service consumer.

d) Integer values

e)DM.QueryReq

f)UDRFunction

g) Effective for packet switched traffic

h)5GS

5.x.1.1.2 number of successful dataset queries

a) This measurement provides the number of successful dataset queries at the UDR.

b)CC

c) The UDR sends a nudr_dm_query response to the NF service consumer indicating a successful dataset Query.

d) Integer values

e)DM.QuerySucc

f)UDRFunction

g) Effective for packet switched traffic

h)5GS

Number of data set queries failed by x.1.1.3

a) This measurement provides the number of failed dataset queries at the UDR.

b)CC

c) The UDR sends a nudr_dm_query response to the NF service consumer indicating a failed dataset Query, each message incrementing the associated sub-counter by 1 according to the failure cause.

d) Each sub-counter is an integer value

e)DM.QueryFail.cause

Wherein the cause indicates a cause of failure of the dataset query.

f)UDRFunction

g) Effective for packet switched traffic

h)5GS

Background data transfer policy control related measurements

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) The PCF receives an npcf_bdtpolicicycorol_create request from the NEF.

d) Integer values

e)BDTP.CreateReq

f)PCFFunction

g) Effective for packet switched traffic

h)5GS

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) The PCF sends to the NEF an npcf_bdtpolicicycorol_create response indicating successful background data transfer policy creation.

d) Integer values

e)BDTP.CreateSucc

f)PCFFunction

g) Effective for packet switched traffic

h)5GS

Number of background data transfer policy creations that failed 5.5.X.1.3

a) This measurement provides the number of failed background data transfer policy creations at the PCF.

b)CC

c) The PCF sends to the NEF an npcf_bdtpolicicycorol_create response indicating a failed background data transfer policy creation, each message incrementing the associated sub-counter by 1 for the failure reason.

d) Each sub-counter is an integer value

e)BDTP.CreateFail.cause

Wherein the cause indicates a cause of failure in the creation of the background data transfer policy.

f)PCFFunction

g) Effective for packet switched traffic

h)5GS

System and implementation

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

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

The network 400 may include a UE 402, and the UE 402 may include any mobile or non-mobile computing device designed to communicate with a RAN 404 via an over-the-air connection. UE 402 may be communicatively coupled with RAN 404 through a Uu interface. The UE 402 may be, but is not limited to, a smart phone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment device, in-vehicle entertainment device, dashboard, heads-up display device, in-vehicle diagnostic device, dashboard mobile device, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networking appliance, machine type communication device, M2M or D2D device, ioT device, etc.

In some embodiments, the network 400 may include a plurality of UEs that are directly coupled to each other via a side link interface. The UE may be an M2M/D2D device that communicates using a physical side link channel, such as, but not limited to PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

In some embodiments, the UE 402 may additionally communicate with the AP 406 via an over-the-air connection. The AP 406 may manage WLAN connections that may be used to offload some/all network traffic from the RAN 404. The connection between the UE 402 and the AP 406 may conform to any IEEE 802.11 protocol, where the AP 406 may be wireless fidelity And a router. In some embodiments, UE 402, RAN 404, and AP 406 maycellular-WLAN aggregation (e.g., LWA/LWIP) is utilized. cellular-WLAN aggregation may involve the UE 402 being configured by the RAN 404 to utilize both cellular radio resources and WLAN resources.

RAN 404 may include one or more access nodes, such as AN 408.AN 408 may terminate the air interface protocol for UE 402 by providing AN access plane protocol that includes RRC, PDCP, RLC, MAC and L1 protocols. In this way, the AN 408 may enable data/voice connectivity between the CN 420 and the UE 402. In some embodiments, AN 408 may be implemented in a separate device or as one or more software entities running on a server computer as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. AN 408 is referred to as BS, gNB, RAN node, eNB, ng-eNB, nodeB, RSU, TRxP, TRP, etc. AN 408 may be a macrocell base station or a low power base station for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth than a macrocell.

In embodiments where the RAN 404 includes multiple ANs, they may be coupled to each other 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 interface (which may be separated into control/user plane interfaces in some embodiments) may allow the AN to communicate information related to handover, data/context transfer, 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 AN air interface for network access to the UE 402. The UE 402 may be simultaneously connected with multiple cells provided by the same or different ANs of the RAN 404. For example, the UE 402 and the RAN 404 may use carrier aggregation to allow the UE 402 to connect with multiple component carriers, each component carrier corresponding to one Pcell or Scell. In a dual connectivity scenario, the first AN may be a primary node providing AN MCG and the second AN may be a secondary node providing AN SCG. The first/second AN may be any combination of eNB, gNB, ng-enbs, etc.

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

In a V2X scenario, the UE 402 or AN 408 may be or act as AN RSU, which may refer to any traffic infrastructure entity for V2X communications. The RSU may be implemented in or by a suitable AN or a fixed (or relatively fixed) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU"; an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU"; an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU"; etc. In one example, the RSU is a computing device coupled with a roadside-located radio frequency circuit that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic flow statistics, media, and applications/software to sense and control ongoing vehicle and pedestrian traffic flow. The RSU may provide extremely low latency communications required for high speed events such as collision avoidance, traffic alerts, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communication services. The components of the RSU may be enclosed in a weather-proof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., ethernet) to a traffic flow signal controller or a backhaul network.

In some embodiments, the RAN 404 may be an LTE RAN 410 with an eNB, e.g., an eNB 412. The LTE RAN 410 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; a CP-OFDM waveform for DL and an SC-FDMA waveform for UL; turbo coding for data and TBCCs for control; etc. The LTE air interface can rely on the CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH demodulation by means of PDSCH/PDCCH DMRS; and relies on 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 operate in the frequency band below 6 GHz.

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

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

NG-RAN 414 may provide a 5G-NR air interface having the following characteristics: a variable SCS; CP-OFDM for DL, CP-OFDM for UL and DFT-s-OFDM; polar codes for control, repetition codes, simplex codes, and Reed-Muller codes, and LDPC codes 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 CRS but may use PBCH DMRS for PBCH demodulation; PTRS is used for phase tracking of PDSCH; and the tracking reference signal is used for time tracking. The 5G-NR air interface may operate on an FR1 band including a band below 6GHz or an FR2 band including a band from 24.25GHz to 52.6 GHz. The 5G-NR air interface may comprise an SSB, which is a region of the downlink resource grid comprising PSS/SSS/PBCH.

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

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

In some embodiments, CN 420 may be LTE CN 422, which may also be referred to as EPC. LTE CN 422 may include MME 424, SGW 426, SGSN 428, HSS 430, PGW 432, and PCRF 434, which are coupled to each other through interfaces (or "reference points"), as shown. The functions of the elements of the LTE CN 422 may be briefly described as follows.

MME 424 may implement mobility management functions to track the current location of UE 402 to facilitate paging, bearer activation/deactivation, handover, gateway selection, authentication, and so forth.

The SGW 426 may terminate the RAN-oriented S1 interface and route data packets between the RAN and the LTE CN 422. S-GW 426 may be a local mobility anchor point for inter-RAN node handover and may also provide anchoring for inter-3 GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

The SGSN 428 may track the location of the UE 402 and perform security functions and access control. Furthermore, SGSN 428 may perform EPC inter-node signaling for mobility between different RAT networks; select PDN and S-GW as specified by MME 424; selecting an MME for handover; etc. The S3 reference point between MME 424 and SGSN 428 may be an inter-3 GPP access network mobility-enabled user and bearer information exchange in an idle and/or active state.

HSS 430 may include a database for network users including subscription related information to support the handling of communication sessions by network entities. HSS 430 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location compliance, and so on. The S6a reference point between HSS 430 and MME 424 may enable the transfer of subscription and authentication data to authenticate/authorize user access to LTE CN 420.

PGW 432 may terminate an SGi interface towards a Data Network (DN) 436, which may include an application/content server 438.PGW 432 may route data packets between LTE CN 422 and data network 436. PGW 432 may be coupled to SGW 426 via an S5 reference point to facilitate user plane tunneling and tunnel management. PGW 432 may also include nodes (e.g., PCEFs) for policy enforcement and charging data collection. Furthermore, the SGi reference point between PGW 432 and data network 436 may be an external public, private PDN of the operator or an intra-operator packet data network, e.g. for provisioning of IMS services. PGW 432 may be coupled with PCRF 434 via a Gx reference point.

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

In some embodiments, CN 420 may be 5gc 440. The 5gc 440 may include AUSF 442, AMF 444, SMF 446, UPF 448, NSSF 450, NEF 452, NRF 454, PCF 456, UDM 458, and AF 460, coupled to each other through interfaces (or "reference points"), as shown. The function of the elements of the 5gc 440 may be briefly described as follows.

AUSF 442 may store data for authentication of UE 402 and handle authentication related functions. AUSF 442 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5gc 440 through a reference point as shown, the AUSF 442 may also present an interface based on the Nausf service.

AMF 444 may allow other functions of 5gc 440 to communicate with UE 402 and RAN 404 and subscribe to notifications about mobility events for UE 402. The AMF 444 may be responsible for registration management (e.g., for registering the 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 for transmission of SMS messages between UE 402 and SMSF. The AMF 444 may interact with the AUSF 442 and the UE 402 to perform various security anchoring and context management functions. Further, the AMF 444 may be an end point of the RAN CP interface, which may include or may be an N2 reference point between the RAN 404 and the AMF 444; and the AMF 444 may be a termination point for NAS (N1) signaling and perform NAS encryption and integrity protection. The AMF 444 may also support NAS signaling with the UE 402 over the N3 IWF interface.

The SMF 446 may be responsible for SM (e.g., session establishment, tunnel management between UPF 448 and AN 408); UE IP address assignment and management (including optional authorization); selection and control of the UP function; configuring traffic manipulation at the UPF 448 to route traffic to an appropriate destination; terminating the interface facing the strategy control function; policy enforcement, charging, and QoS control; lawful interception (for SM events and interfaces to LI systems); terminating the SM portion of the NAS message; downlink data notification; initiate AN specific SM information sent to AN 408 over N2 via AMF 444; and determining the SSC mode of the session. SM may refer to the management of PDU sessions, while PDU sessions or "sessions" may refer to PDU connectivity services that provide or enable the exchange of PDUs between UE 402 and data network 436.

The UPF 448 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 436, and a branching point to support multi-homing PDU sessions. The UPF 448 may also perform packet routing and forwarding, perform packet inspection, perform policy rules on the user plane portion, lawful interception packets (UP collection), perform traffic usage reporting, perform QoS treatment for the 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. The UPF 448 may include an uplink classifier to support routing traffic flows to a data network.

NSSF 450 may select a set of network slice instances to serve UE 402. NSSF 450 may also determine allowed NSSAIs and mappings to subscribed S-NSSAIs if desired. NSSF 450 may also determine the set of AMFs, or list of candidate AMFs, to be used to serve UE 402 based on the appropriate configuration and possibly by querying 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 result in a change in AMF. NSSF 450 may interact with AMF 444 via an N22 reference point; and may communicate with another NSSF in the visited network via an N31 reference point (not shown). Furthermore, NSSF 450 may expose an interface based on the Nnssf service.

NEF 452 may securely expose services and capabilities provided by 3GPP network functions for third parties, internal exposure/re-exposure, AF (e.g., AF 460), edge computing or fog computing systems, and so forth. In such embodiments, NEF 452 may authenticate, authorize or throttle AF. NEF 452 may also translate information exchanged with AF 460 and information exchanged with internal network functions. For example, NEF 452 may translate between AF service identifiers and internal 5GC information. The NEF 452 may also receive information from other NFs based on their exposed capabilities. This information may be stored as structured data at NEF 452 or at data store NF using a standardized interface. The stored information may then be re-exposed by NEF 452 to other NFs and AFs, or used for other purposes, such as parsing. Furthermore, NEF 452 may expose an interface based on Nnef services.

NRF 454 may support a service discovery function, receive NF discovery requests from NF instances, and provide information of the discovered NF instances to the NF instances. NRF 454 also maintains information of available NF instances and services supported by them. As used herein, the term "instantiation" and the like may refer to the creation of an instance, and "instance" may refer to a specific occurrence of an object, which may occur, for example, during execution of program code. Further, NRF 454 may present an interface based on Nnrf services.

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

The UDM 458 may handle subscription related information to support handling of communication sessions by network entities and may store subscription data for the 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 comprise two parts, an application front-end and a UDR. The UDR may store subscription data and policy data for UDM 458 and PCF 456, and/or store structured data and application data for NEF 452 for exposure (including PFD for application detection, application request information for multiple UEs 402). The Nudr service-based interface may be exposed by UDR 221 to allow UDM 458, PCF 456, and NEF 452 to access a particular set of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of related data changes in the UDR. The UDM may include a UDM-FE that is responsible for handling credentials, location management, subscription management, and so forth. 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 through reference points as shown, the UDM 458 may also present a Nudm service-based interface.

AF 460 may provide application impact on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

In some embodiments, the 5gc 440 may enable edge computation by selecting an operator/third party service to be geographically close to the point where the UE 402 attaches to the network. This may reduce latency and load on the network. To provide an edge computing implementation, the 5gc 440 may select the UPF 448 close to the UE 402 and perform traffic steering from the UPF 448 to the data network 436 via the N6 interface. This may be based on the UE subscription data, the UE location, and the information provided by AF 460. Thus, AF 460 may affect UPF (re) selection and traffic routing. Based on the operator deployment, the network operator may allow the AF 460 to interact directly with the associated NF when the AF 460 is considered a trusted entity. Furthermore, AF 460 may present an interface based on Naf services.

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

Fig. 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 504. The UE 502 and the AN 504 may be similar to, and substantially interchangeable with, similarly named components described elsewhere herein.

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

The UE 502 may include a host platform 508 coupled with a modem platform 510. The main platform 508 may include application processing circuitry 512, which may be coupled with protocol processing circuitry 514 of the modem platform 510. 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 send and receive application data to and from the data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

Protocol processing circuitry 514 may implement one or more layers of operations to facilitate sending or receiving data over connection 506. Layer operations implemented by the protocol processing circuitry 514 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

Modem platform 510 may also include digital baseband circuitry 516, which may implement one or more layer operations in the network protocol stack that are "lower" than the layer operations performed by protocol processing circuitry 514. These operations may include, for example, PHY operations, including one or more of the following: HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/demapping, 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 space coding), reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

Modem platform 510 may also include transmit circuitry 518, receive circuitry 520, radio frequency circuitry 522, and Radio Frequency Front End (RFFE) 524, which may include or be connected to one or more antenna panels 526. Briefly, the transmit circuit 518 may include digital-to-analog converters, mixers, intermediate Frequency (IF) components, and the like; the receive circuitry 520 may include digital-to-analog converters, mixers, intermediate Frequency (IF) components, and the like; the radio frequency circuit 522 may include low noise amplifiers, power tracking components, and the like; RFFE 524 may include filters (e.g., surface/bulk acoustic wave filters), switches, antenna tuners, beam forming components (e.g., phased array antenna components), and so forth. The selection and arrangement of the components of the transmit circuit 518, receive circuit 520, radio frequency circuit 522, RFFE 524, and antenna panel 526 (commonly referred to as "transmit/receive components") may depend on the specifics of the particular implementation, e.g., whether the communication is TDM or FDM, frequencies below mmWave or 6gHz, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be arranged in the same or different chips/modules, and so on.

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

UE reception may be established by and via antenna panel 526, RFFE 524, RF circuitry 522, receive circuitry 520, digital baseband circuitry 516, and protocol processing circuitry 514. In some embodiments, the antenna panel 526 may receive transmissions from the AN 504 through receive beamformed signals received by multiple antennas/antenna elements of one or more antenna panels 526.

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

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

Fig. 6 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some example embodiments. In particular, FIG. 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 that utilize node virtualization (e.g., NFV), hypervisor (hypervisor) 602 can be executed to provide an execution environment for one or more network slices/sub-slices to utilize hardware resources 600.

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

Memory/storage 620 may include main memory, disk storage, or any suitable combination of these. Memory/storage 620 may include, but is not limited to, any type of volatile, nonvolatile, or semi-volatile memory, such as dynamic random access memory (dynamic random access memory, DRAM), static random access memory (static random access memory, SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (electrically erasable programmable read-only memory), flash memory, solid state storage, and the like.

Communication resources 630 may include an interconnection or network interface controller, component, or other suitable device to communicate with one or more peripheral devices 604 or one or more databases 606 or other network elements via 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, and so forth,(or low energy consumption->) Assembly (S)>Components, and other communication components.

The instructions 650 may include software, programs, applications, applets, apps, or other executable code for causing at least any one of the processors 610 to perform any one or more of the methods discussed herein. The instructions 650 may reside, completely or partially, within at least one of the processors 610 (e.g., within a cache memory of the processor), within the memory/storage device 620, or any suitable combination of these. Further, any portion of instructions 650 may be transferred from any combination of peripherals 604 or databases 606 to hardware resource 600. Thus, the memory of the processor 610, the memory/storage 620, the peripherals 604 and the database 606 are examples of computer readable and machine readable media.

Example procedure

In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s) or portions or implementations of fig. 4-6 or some other figures 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 fig. 7. For example, process 700 may include, at 705, retrieving raw performance measurements from a memory regarding a data management service associated with a unified data warehouse (UDR). The process also includes, at 710, generating a performance measurement based on the raw performance measurement, wherein the generated performance measurement includes dataset query information associated with the UDR. The process also includes, at 715, providing the generated performance measure to the service consumer.

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

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

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

Example

Example 1 may include a measured service generator supported by one or more processors configured to:

Raw performance measurements related to the data management service are obtained from the UDR.

Performance measurements are generated and provided based on the raw performance measurements obtained.

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

Example 3 may include the method of example 1 or some other example herein, wherein the performance measure relates to a dataset query.

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

Example 5 may include the method of example 4 or some other example herein, wherein the number of dataset Query requests is obtained when the UDR receives a nudr_dm_query request from an NF service consumer;

the number of successful dataset queries is obtained when the UDR sends a nudr_dm_query response to NF service consumers indicating a successful dataset Query; and is also provided with

The number of failed dataset queries is obtained when the UDR sends a nudr_dm_query response to NF service consumers indicating a failed dataset Query, each message incrementing the associated sub-counter by 1 for the reason of the failure.

Example 6 may include a measured service generator supported by one or more processors configured to:

raw performance measurements related to background data transfer policy control are obtained from the PCF.

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

Example 8 may include the method of example 6 or some other example herein, wherein the performance measure relates to a background data transfer policy creation.

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

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 when the PCF receives an npcf_bdpolicy control_create request from the NEF;

the number of successful background data transfer policy creations is obtained when the PCF sends to the NEF a npcf_bdtpoliccontrol_create response indicating successful background data transfer policy creations;

The number of failed background data transfer policy creations is obtained when the PCF sends to the NEF an npcf_bdtpolicccontrol_create response indicating a failed background data transfer policy creation, each message incrementing the associated sub-counter by 1 for the failure reason.

Example 11 includes a method comprising:

raw performance measurements related to the data management service are received by the service generator from a Unified Data Repository (UDR).

Generating, by the service generator, 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 is also provided with

The generated performance measurements are provided by the service generator to a consumer associated with the service generator.

Example 12 includes the method of example 11 or some other example herein, wherein the service generator 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 generator generates a plurality of performance measurements, and the plurality of performance measurements further includes an indication of: the number of failed dataset queries, the number of background data transfer policy creation requests, the number of successful background data transfer policy creation, or the number of failed background data transfer policy creation.

Example X1 includes an apparatus comprising:

a memory for storing raw performance measurements for a data management service associated with a unified data warehouse (UDR); and

processing circuitry coupled to the memory for:

retrieving the raw performance measurements from the memory; and is also provided with

Generating a performance measurement based on the raw performance measurement, wherein the generated performance measurement includes dataset query information associated with the UDR; and is also provided with

The generated performance measure is provided to the service consumer.

Example X2 includes the apparatus of example X1 or some other example herein, wherein the dataset query information includes an indication of: the number of data set query requests, the number of successful data set queries, or the 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 received 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 dataset queries is based on a number of nudr_dm_query responses by the UDR to NF service consumers indicating successful dataset queries.

Example X5 includes the apparatus of example X2 or some other example herein, wherein the number of failed dataset queries is based on a number of nudr_dm_query responses by the UDR to NF service consumers indicating failed dataset queries.

Example X6 includes the apparatus of any of examples X1-X5 or some other example herein, wherein the processing circuitry is further to implement a service generator adapted to generate the performance measurement and to 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 generator 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 generator to:

receiving raw performance measurements related to a data management service from a unified data warehouse (UDR);

The generated performance measure is provided to the service consumer.

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

Example X10 includes one or more computer-readable media as described in example X9 or some other example herein, wherein the number of dataset Query requests is based on a number of nudr_dm_query requests received by the UDR from a Network Function (NF) service consumer.

Example X11 includes one or more computer-readable media as described in example X9 or some other example herein, wherein the number of successful dataset queries is based on a number of nudr_dm_query responses by the UDR to NF service consumers indicating successful dataset queries.

Example X12 includes one or more computer-readable media as described in example X9 or some other example herein, wherein the number of failed dataset queries is based on a number of nudr_dm_query responses by the UDR to NF service consumers indicating failed dataset queries.

Example X13 includes one or more computer-readable media of any of examples X8-X12, wherein the service generator is implemented by a network function that includes the UDR, or by a management function.

Example X14 includes an apparatus comprising:

a memory to store raw performance measurements for background data transfer policy control associated with a Policy Control Function (PCF); and

processing circuitry coupled to the memory for:

Generating a performance measurement based on the raw performance measurement, wherein the generated performance measurement includes an indication of background data transfer policy creation information; and is also provided with

The generated performance measure is provided to the service consumer.

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

Example X16 includes an apparatus as described in example X15 or some other example herein, wherein:

The number of background data transfer policy creation requests is based on the number of npcf_bdtpolicicycontrol_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_bdtpolicicycorol_create responses to the one or more NEFs indicating successful background data transfer policy creations; and is also provided with

The number of failed background data transfer policy creations is based on a number of npcf_bdtpolicicycontrol_create responses to the one or more NEFs indicating failed background data transfer policy creations.

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

Example X18 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a service generator to:

receiving raw performance measurements associated with background data transfer policy control from a Policy Control Function (PCF);

The generated performance measure is provided to the service consumer.

Example X19 includes one or more computer-readable media as described in example X18 or some other example herein, wherein the background data transfer policy creation information includes an indication of: the number of background data transfer policy creation requests, the number of successful background data transfer policy creation, or the number of failed background data transfer policy creation.

Example X20 includes one or more computer-readable media as described in example X19 or some other example herein, wherein:

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

Example Z01 may include an apparatus comprising means for performing one or more elements of the method described in or associated with 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, when executed by one or more processors of the electronic device, to perform one or more elements of the methods 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 the methods described in or associated with 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 any of examples 1-X21 or in connection with any of examples 1-X21, or portions 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 a method, technique, or process as described in any one of examples 1-X21 or in connection with any one of examples 1-X21, or some portion thereof.

Example Z06 may include a signal as described in any of examples 1-X21 or related to any of examples 1-X21, or portions thereof.

Example Z07 may include a datagram, packet, frame, fragment, protocol Data Unit (PDU), or message, or some portion thereof, as described in any one of examples 1-X21 or in relation to any one of examples 1-X21, or other described datagram, packet, frame, fragment, protocol Data Unit (PDU), or message in this disclosure.

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

Example Z09 may include a signal encoded with a datagram, packet, frame, fragment, protocol Data Unit (PDU) or message, or some portion thereof, as described in any one of examples 1-X21 or in relation to any one of examples 1-X21, or other described datagram, packet, frame, fragment, protocol Data Unit (PDU) or message in this disclosure.

Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors causes the one or more processors to perform the method, technique, or process as described in any one of examples 1-X21 or in relation to any one of examples 1-X21, or some portion thereof.

Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process as described in or in connection with any of examples 1-X21, or some portion thereof.

Example Z12 may include signals 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 communications as shown and described herein.

Example Z15 may include an apparatus for providing wireless communication as shown and described herein.

Any of the above 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 the 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 (abbreviations)

Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 v16.0.0 (2019-06). For purposes of this document, the following abbreviations may apply to the examples and embodiments discussed herein.

/>

Terminology

For purposes of this document, the following terms and definitions apply to the examples and embodiments discussed herein.

The term "circuitry" as used herein refers to, is part of, or includes, hardware components such as the following configured to provide the described functionality: electronic circuitry, logic circuitry, processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field-programmable device (field-programmable device, FPD) (e.g., field-programmable gate array (field-programmable gate array, FPGA), programmable logic device (programmable logic device, PLD), complex PLD (CPLD), high-capacity PLD (hcpll), structured ASIC, or programmable SoC), digital signal processor (digital signal processor, DSP), and so forth. In some embodiments, circuitry may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuitry" may also refer to a combination of one or more hardware elements (or circuitry for use in an electrical or electronic system) and program code for performing the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

The term "processor circuit" as used herein refers to, is part of, or includes the following circuitry: the circuitry is capable of sequentially and automatically performing a sequence of operations or logic operations, or recording, storing, and/or transmitting digital data. The 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 circuit" 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 tri-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. The processing circuitry may include further 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 with "processor circuitry" and may be referred to as "processor circuitry".

The term "interface circuit" as used herein refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I/O interface, a peripheral component interface, a network interface card, and so forth.

The term "user equipment" or "UE" as used herein refers to a device that has radio communication capabilities and may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with, and may be referred to as, the following terms: a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless/wired device or any computing device that includes a wireless communication interface.

The term "network element" as used herein refers to a physical or virtualized device and/or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with and/or referred to by the following terms: networked computers, networking hardware, network devices, network nodes, routers, switches, hubs, bridges, radio network controllers, RAN devices, RAN nodes, gateways, servers, virtualized VNFs, NFVI, and so forth.

The term "computer system" as used herein refers to any type of interconnected electronic device, computer device, or component thereof. Furthermore, the terms "computer system" and/or "system" may refer to components of a computer that are communicatively coupled to each other. Furthermore, the terms "computer system" and/or "system" may refer to a plurality of computer devices and/or a plurality of computing systems communicatively coupled to each other and configured to share computing and/or networking resources.

The terms "appliance," "computer appliance," and the like, as used herein, refer to a computer device or computer system having program code (e.g., software or firmware) specifically designed to provide a particular 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 is otherwise dedicated to providing specific computing resources.

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 a computer device, a mechanical device, a memory space, a processor/CPU time, a processor/CPU usage, a processor and accelerator load, a hardware time or usage, a power supply, an input/output operation, a port or network socket, a channel/link allocation, a throughput, a memory usage, a storage, a network, a database and application, a workload unit, and the like. "hardware resources" may refer to computing, storage, and/or network resources provided by physical hardware element(s). "virtualized resources" may refer to computing, storage, and/or network resources provided by a virtualization infrastructure to applications, devices, systems, and the like. The term "network resource" or "communication resource" may refer to a resource that is accessible by a computer device/system via a communication network. The term "system resource" may refer to any kind of shared entity that provides a service and may include computing and/or network resources. A system resource may be considered a collection of coherent functions, network data objects, or services accessible through a server, where such system resource resides on a single host or multiple hosts and is clearly identifiable.

The term "channel" as used herein refers to any transmission medium, whether tangible or intangible, used to convey data or data streams. The term "channel" may be synonymous and/or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier wave," "radio frequency carrier wave," and/or any other similar term that refers to a channel or medium through which data is communicated. Furthermore, the term "link" as used herein refers to a connection that occurs between two devices via a RAT in order to send and receive information.

The term "instantiation" and the like as used herein refers to creating an instance. "instance" also refers to a specific occurrence of an object, which may occur, for example, during execution of program code.

The terms "coupled," "communicatively coupled," and their derivatives are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still co-operate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements purportedly coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements are in contact with each other through communication means, including by wire or other interconnection connection, by wireless communication channels or links, and so forth.

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

The term "SMTC" refers to an SSB-based measurement timing configuration configured by SSB-measurementtiming configuration.

The term "SSB" refers to an SS/PBCH block.

The term "primary cell" refers to an MCG cell operating on a primary frequency, wherein the UE either performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

The term "primary SCG cell" refers to an SCG cell in which a UE performs random access when performing a reconfiguration procedure with synchronization for DC operation.

The term "secondary cell" refers to a cell that provides additional radio resources for a CA-configured UE over a special cell.

The term "secondary cell group" refers to a subset of serving cells for a DC configured UE that includes PSCell and zero or more secondary cells.

The term "serving cell" refers to a primary cell for a UE in rrc_connected that is not configured with CA/DC, and only one serving cell is composed of the primary cell.

The term "serving cell" refers to a set of cells including special cell(s) and all secondary cells for a UE in rrc_connected configured with CA.

The term "special cell" refers to a PCell of an MCG or a PSCell of an SCG for DC operation; otherwise, the term "special cell" refers to a Pcell.

Claims

1. An apparatus, comprising:

a memory for storing raw performance measurements related to a data management service, the data management service being associated with a Unified Data Repository (UDR); and

processing circuitry coupled to the memory for:

The generated performance measure is provided to the service consumer.

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

3. The apparatus of claim 2, wherein the number of dataset Query requests is based on a number of nudr_dm_query requests received by the UDR from a Network Function (NF) service consumer.

4. The apparatus of claim 2, wherein the number of successful dataset queries is based on a number of nudr_dm_query responses by the UDR to NF service consumers indicating successful dataset queries.

5. The apparatus of claim 2, wherein the number of failed dataset queries is based on a number of nudr_dm_query responses by the UDR to NF service consumers indicating failed dataset queries.

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

7. The apparatus of claim 6, wherein the service generator 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 generator to:

The generated performance measure is provided to the service consumer.

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

10. The one or more computer-readable media of claim 9, wherein the number of dataset Query requests is based on a number of nudr_dm_query requests received 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 dataset queries is based on a number of nudr_dm_query responses by the UDR to NF service consumers indicating successful dataset queries.

12. The one or more computer-readable media of claim 9, wherein the number of failed dataset queries is based on a number of nudr_dm_query responses by the UDR to NF service consumers indicating failed dataset queries.

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

14. An apparatus, comprising:

a memory for storing raw performance measurements related to a background data transfer policy control associated with a Policy Control Function (PCF); and

Processing circuitry coupled to the memory for:

The generated performance measure is provided to the service consumer.

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

16. The apparatus of claim 15, wherein:

the number of successful background data transfer policy creations is based on a number of npcf_bdtpoliccontrol_create responses to the one or more NEFs, the responses indicating successful background data transfer policy creations; and is also provided with

The number of failed background data transfer policy creations is based on a number of npcf_bdtpoliccontrol_create responses to the one or more NEFs, the responses indicating failed background data transfer policy creations.

17. The apparatus of any of claims 14-16, wherein the service generator 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 generator to:

The generated performance measure is provided to the service consumer.

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

20. The one or more computer-readable media of claim 19, wherein:

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