IP Library › Granted Patent US 12,732,447
Granted Patent B2
US 12,732,447 · App. 18/574,942 · Granted Sep 8, 2026

Performance measurements for network exposure function

Inventors: Joey Chou (Scottsdale, AZ); Yizhi Yao (Chandler, AZ)
Assignee: Intel Corporation
H04L43/091H04L12/1407H04L41/5009
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,732,447
App. No.
18/574,942
Granted
Sep 8, 2026
Kind
B2
Abstract

This disclosure describes systems, methods, and devices related to performance measurements. A device may decode a service request received from a management service consumer for the 5G system (5GS), wherein the service request may be associated with a performance measurement collection service to be delivered by the service producer to the service consumer related to a network exposure function (NEF). The device may detect performance measurements data received from the NEF. The device may decode from the performance measurements data a measurement label associated with the performance measurements data based on the service request. The device may encode a service response based on the performance measurements data received from the NEF.

Claims (28)

1 . An apparatus for a service producer in a 5G system (5GS) comprising:

a processor configured to:

decode a service request received from a service consumer for the 5GS, wherein the service request is associated with a performance measurement collection service to be delivered by the service producer to the service consumer related to a network exposure function (NEF);

detect performance measurements data received from the NEF;

decode, from the performance measurements data, a measurement label associated with the performance measurements data based on the service request, wherein the performance measurement is based on a number of UE radio capability management function (UCMF) dictionary entry creation requests, a number of successful UCMF dictionary entry creations, a number of failed UCMF dictionary entry creations, a number of UCMF dictionary entry deletion requests, a number of successful UCMF dictionary entry deletions, or a number of failed UCMF dictionary entry deletions; and

encode a service response based on the performance measurements data received from the NEF; and

a memory to store the performance measurements data.

2 . The apparatus of claim 1 , wherein decoding the service request triggers the NEF to initiate a generation and delivery of the performance measurements data.

3 . The apparatus of claim 1 , wherein the performance measurement is based on a number of application function (AF) session with quality of service (QoS) creation requests, a number of successful AF session with QoS creation, a number of failed AF session with QoS creation, or a number of AF session with QoS notifications.

4 . The apparatus of claim 1 , wherein the performance measurement is based on a number of background data transfer policy application requests, a number of successful background data transfer policy applications, a number of failed background data transfer policy applications, a number of background data transfer policy update requests, a number of successful background data transfer policy updates, a number of failed background data transfer policy updates, a number of background data transfer policy deletion requests, a number of successful background data transfer policy deletions, or a number of failed background data transfer policy deletions.

5 . The apparatus of claim 1 , wherein the service producer is outside the NEF in a separate management system or inside the NEF.

6 . The apparatus of claim 1 , wherein to generate a first performance measurement comprises the processor being further configured to initiate a cumulative counter for measurements during a collection period.

7 . The apparatus of claim 3 , wherein; the number of AF session with QoS creation requests is cumulated on receipt of an Nnef_AFsessionWithQoS_Create request by the NEF from an AF; the number of successful AF session with QoS creations is cumulated on transmission of an Nnef_AFsession WithQoS_Create response by the NEF to an AF indicating a successful AF session with QoS creation; the number of failed AF session with QoS creations is cumulated on transmission of an Nnef_AFsessionWithQoS_Create response by the NEF to an AF indicating a failed AF session with QoS creation and each message increments a relevant subcounter per failure cause by 1; and the number of AF session with QoS notifications is cumulated on transmission of an Nnef_AFsession WithQoS_Notify message by the NEF to an AF.

8 . The apparatus of claim 4 , wherein: the number of background data transfer policy application requests is cumulated on receipt by the NEF of an Nnef_ApplyPolicy_Create request message from AF; the number of successful background data transfer policy applications is cumulated on transmission by the NEF of an Nnef_ApplyPolicy_Create response message to SMF indicating a successful background data transfer policy application; the number of failed background data transfer policy applications is cumulated on transmission by the NEF of an Nnef_ApplyPolicy_Create response message to AF indicating a failed background data transfer policy application and each message increments a relevant subcounter per failure cause by 1; the number of background data transfer policy update requests is cumulated on receipt by the NEF of an Nnef_ApplyPolicy_Update request message from AF; the number of successful background data transfer policy updates is cumulated on transmission by the NEF of an Nnef_ApplyPolicy_Update response message to AF indicating a successful background data transfer policy update; the number of failed background data transfer policy updates is cumulated on transmission by the NEF of an Nnef_ApplyPolicy_Update response message to AF indicating a failed background data transfer policy update and each message increments a relevant subcounter per failure cause by 1; the number of background data transfer policy deletion requests is cumulated on receipt by the NEF of an Nnef_ApplyPolicy_Delete request message from AF; the number of successful background data transfer policy deletions is cumulated on transmission by the NEF of an Nnef_ApplyPolicy_Delete response message to AF indicating a successful background data transfer policy deletion; and the number of failed background data transfer policy deletions is cumulated on transmission by the NEF of an Nnef_ApplyPolicy_Delete response message to AF indicating a failed background data transfer policy deletion and each message increments a relevant subcounter per failure cause by 1.

9 . The apparatus of claim 1 , wherein: the number of UCMF dictionary entry creation requests is cumulated on receipt of an Nnef_UCMFProvisioning_Create request by the NEF from an AF; the number of successful UCMF dictionary entry creations is cumulated on transmission of an Nnef_UCMFProvisioning_Create response by the NEF to an AF indicating a successful UCMF dictionary entry creation; the number of failed UCMF dictionary entry creations is cumulated on transmission of an Nnef_UCMFProvisioning_Create response by the NEF to an AF indicating a failed UCMF dictionary entry creation and each message increments a relevant subcounter per failure cause by 1; the number of UCMF dictionary entry deletion requests is cumulated on receipt of an Nnef_UCMFProvisioning_Delete request by the NEF from an AF; the number of successful UCMF dictionary entry deletions is cumulated on transmission of an Nnef_UCMFProvisioning_Delete response by the NEF to an AF indicating a successful UCMF dictionary entry deletion; and the number of failed UCMF dictionary entry deletions is cumulated on transmission of an Nnef_UCMFProvisioning_Delete response by the NEF to an AF indicating a failed UCMF dictionary entry deletion and each message increments a relevant subcounter per failure cause by 1.

10 . The apparatus of claim 6 , wherein an initial value of the cumulative counter is set to zero at a beginning of every collection period.

11 . A non-transitory computer-readable medium storing computer-executable instructions which when executed by one or more processors for a service producer in a 5G system (5GS) result in performing operations comprising:

decoding a service request received from a service consumer for the 5GS, wherein the service request is associated with a performance measurement collection service to be delivered by the service producer to the service consumer related to a network exposure function (NEF);

detecting performance measurements data received from the NEF;

decoding, from the performance measurements data, a measurement label associated with the performance measurements data based on the service request, wherein the performance measurement is based on a number of UE radio capability management function (UCMF) dictionary entry creation requests, a number of successful UCMF dictionary entry creations, a number of failed UCMF dictionary entry creations, a number of UCMF dictionary entry deletion requests, a number of successful UCMF dictionary entry deletions, or a number of failed UCMF dictionary entry deletions; and

encoding a service response based on the performance measurements data received from the NEF.

12 . The non-transitory computer-readable medium of claim 11 , wherein decoding the service request triggers the NEF to initiate a generation and delivery of the performance measurements data.

13 . The non-transitory computer-readable medium of claim 11 , wherein the performance measurement is based on a number of application function (AF) session with quality of service (QoS) creation requests, a number of successful AF session with Qos creation, a number of failed AF session with QoS creation, or a number of AF session with QoS notifications.

14 . The non-transitory computer-readable medium of claim 11 , wherein the performance measurement is based on a number of background data transfer policy application requests, a number of successful background data transfer policy applications, a number of failed background data transfer policy applications, a number of background data transfer policy update requests, a number of successful background data transfer policy updates, a number of failed background data transfer policy updates, a number of background data transfer policy deletion requests, a number of successful background data transfer policy deletions, or a number of failed background data transfer policy deletions.

15 . The non-transitory computer-readable medium of claim 11 , wherein the service producer is outside the NEF in a separate management system or inside the NEF.

16 . The non-transitory computer-readable medium of claim 11 , wherein to generate a first performance measurement comprises the processor being further configured to initiate a cumulative counter for measurements during a collection period.

17 . The non-transitory computer-readable medium of claim 13 , wherein: the number of AF session with QoS creation requests is cumulated on receipt of an Nnef_AFsession WithQoS_Create request by the NEF from an AF; the number of successful AF session with QoS creations is cumulated on transmission of an Nnef_AFsession WithQoS_Create response by the NEF to an AF indicating a successful AF session with QoS creation; the number of failed AF session with QoS creations is cumulated on transmission of an Nnef_AFsession WithQoS_Create response by the NEF to an AF indicating a failed AF session with QoS creation and each message increments a relevant subcounter per failure cause by 1; and the number of AF session with QoS notifications is cumulated on transmission of an Nnef_AFsession WithQoS_Notify message by the NEF to an AF.

18 . The non-transitory computer-readable medium of claim 14 , wherein; the number of background data transfer policy application requests is cumulated on receipt by the NEF of an Nnef_ApplyPolicy_Create request message from AF; the number of successful background data transfer policy applications is cumulated on transmission by the NEF of an Nnef_ApplyPolicy_Create response message to SMF indicating a successful background data transfer policy application; the number of failed background data transfer policy applications is cumulated on transmission by the NEF of an Nnef_ApplyPolicy_Create response message to AF indicating a failed background data transfer policy application and each message increments a relevant subcounter per failure cause by 1; the number of background data transfer policy update requests is cumulated on receipt by the NEF of an Nnef_ApplyPolicy_Update request message from AF; the number of successful background data transfer policy updates is cumulated on transmission by the NEF of an Nnef_ApplyPolicy_Update response message to AF indicating a successful background data transfer policy update; the number of failed background data transfer policy updates is cumulated on transmission by the NEF of an Nnef_ApplyPolicy_Update response message to AF indicating a failed background data transfer policy update and each message increments a relevant subcounter per failure cause by 1; the number of background data transfer policy deletion requests is cumulated on receipt by the NEF of an Nnef_ApplyPolicy_Delete request message from AF; the number of successful background data transfer policy deletions is cumulated on transmission by the NEF of an Nnef_ApplyPolicy_Delete response message to AF indicating a successful background data transfer policy deletion; and the number of failed background data transfer policy deletions is cumulated on transmission by the NEF of an Nnef_ApplyPolicy_Delete response message to AF indicating a failed background data transfer policy deletion and each message increments a relevant subcounter per failure cause by 1.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 11, 2026
From: INTEL CORPORATION
To: INTEL PRODUCTS IP LLC
Reel/Frame 075991/0408 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 27, 2024
From: YAO, YIZHI; CHOU, JOEY
To: INTEL CORPORATION
Reel/Frame 069686/0231 →
Continuity (2)
Provisional Application 63230572 · Aug 6, 2021
Related Publication 20240333623A1 · Oct 3, 2024
References Cited (13)
US 20190253912A1 · Yao · 2019 [cited by examiner]
US 20190354607A1 · Snow · 2019 [cited by examiner]
US 20200404073A1 · Huang et al. · 2020 [cited by applicant]
US 20210014141A1 · Patil · 2021 [cited by examiner]
US 20210120473A1 · Yao et al. · 2021 [cited by applicant]
US 20210168643A1 · Yao et al. · 2021 [cited by applicant]
US 20240064557A1 · Wei · 2024 [cited by examiner]
US 20240129739A1 · Kunz · 2024 [cited by examiner]
WO 2020181496A1 · 2020 [cited by applicant]
3GPP TS 28.552 V17.3.1 “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; 5G performance measurements (Release 17)” (Year: 2021). [cited by examiner]
U.S. Appl. No. 63/151,473, filed Feb. 19, 2021 (Year: 2021). [cited by examiner]
International Search Report and Written Opinion mailed Nov. 17, 2022 in Application No. PCT/US2022/039213, 11 pages. [cited by applicant]
3GPP TSG SA “Management and orchestration; 5G performance measurements,” 3GPP TS 28.552 V17.3.1, Jun. 24, 2021, 26 pages. [cited by applicant]