IP Library › Granted Patent US 12,407,588
Granted Patent B2
US 12,407,588 · App. 18/619,105 · Granted Sep 2, 2025

Analytics generation and consumption in a mobile network

Inventors: Clarissa Marquezan (Munich, DE); Riccardo Trivisonno (Munich, DE)
Assignee: Huawei Technologies Co., Ltd.
H04L43/06H04L43/04
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,407,588
App. No.
18/619,105
Granted
Sep 2, 2025
Kind
B2
Abstract

A consumer of an analytics output receives control and/or knowledge about a set of parameters that is used for generating the analytics output. A set of baseline parameters is used for generating the analytics output, which (a) is associated with a set of analytics consumers and/or with a set of analytics types, and (b) is related to at least one of a statistical property and/or process and/or an output strategy for providing an analytics output. Network entities and corresponding methods for analytics generation and for consuming analytics may be used for generating an analytics output based on the set of baseline parameters.

Claims (71)

1. A network entity device for analytics generation of a mobile network, the network entity device comprising:

a memory having instructions stored thereon; and

a processor configured to execute the instructions to facilitate performance of the following by the network entity device:

obtaining a set of baseline parameters, wherein the set of baseline parameters is associated with a set of analytics types, wherein the set of baseline parameters comprises an output strategy for providing an analytics output, and wherein the output strategy defines a mechanism that forces the network entity device to provide the analytics output, wherein the defined mechanism overrides a first policy condition for providing the analytics output;

providing the analytics output for the associated set of analytics types, wherein the analytics output is based on the set of baseline parameters;

receiving a first request to provide the set of baseline parameters for generating the analytics output; and

providing the set of baseline parameters in response to the first request.

2. The network entity device according to claim 1 , wherein the set of baseline parameters further comprises at least one of:

volume of data for generating the analytics output;

one or more statistical properties of data for generating the analytics output; or

a synchronization deadline for providing the analytics output.

3. The network entity device according to claim 1 , wherein the first request comprises at least one of:

identification of one or more analytics output types;

identification of one or more analytics outputs;

one or more types of consumers of analytics outputs; or

one or more identifications of a consumer of an analytics output.

4. The network entity device according to claim 1 , wherein the processor is further configured to execute the instructions to facilitate performance of the following by the network entity device:

receiving a second request indicating a requested set of baseline parameters associated with a set of analytics consumers and/or with the set of analytics types; and

wherein the analytics output is based on the requested set of baseline parameters as the set of baseline parameters.

5. The network entity device according to the claim 4 , wherein the processor is further configured to execute the instructions to facilitate performance of the following by the network entity device:

providing an indication of no support or no authorization regarding the requested set of baseline parameters, based on the requested set of baseline parameters not being supported by the network entity device or not authorized.

6. The network entity device according to claim 4 , wherein the second request comprises a request for the analytics output.

7. The network entity device according to claim 1 , wherein the processor is further configured to execute the instructions to facilitate performance of the following by the network entity device:

receiving a second request indicating a requested set of baseline parameters associated with a set of analytics consumers and/or with the set of analytics types;

selecting a subset of baseline parameters from the requested set of baseline parameters; and

including the subset of baseline parameters in the set of baseline parameters for generating the analytics output.

8. The network entity device according to claim 1 , wherein the processor is further configured to execute the instructions to facilitate performance of the following by the network entity device:

receiving a third request indicating one or more proposed sets of baseline parameters associated with a set of analytics consumers and/or with the set of analytics types;

selecting one or more supported sets of baseline parameters from the proposed sets of baseline parameters, wherein the one or more supported sets of baseline parameters are supported by the network entity device; and

providing a response to the third request, the response indicating the one or more supported sets of baseline parameters.

9. The network entity device according to claim 8 , wherein the response to the third request further comprises an identification of the one or more supported sets of baseline parameters, and the identification of the one or more supported sets of baseline parameters relates the third request to the selected one or more supported sets of baseline parameters.

10. The network entity device according to claim 9 , wherein the processor is further configured to execute the instructions to facilitate performance of the following by the network entity device:

receiving a message indicating a selected set of baseline parameters from the one or more supported sets of baseline parameters; and

using the selected set of baseline parameters as the set of baseline parameters for generating the analytics output.

11. The network entity device according to claim 10 , wherein the message indicating a selected set of baseline parameters from the one or more supported sets of baseline parameters further comprises the identification of the one or more supported sets of baseline parameters.

12. The network entity device according to claim 1 , wherein the network entity device is a control plane entity comprising a Network Data Analytics Function (NWDAF).

13. The network entity device according to claim 1 , wherein the set of baseline parameters further comprises:

volume of data for generating the analytics output;

one or more statistical properties of data for generating the analytics output; and

a synchronization deadline for providing the analytics output.

14. The network entity device according to claim 1 , wherein the first policy condition corresponds to providing the analytics output only when a certain level of accuracy or confidence is achieved, and wherein the defined mechanism forces the network entity device to provide the analytics output regardless of level of accuracy or confidence.

15. The network entity device according to claim 14 , wherein the first policy condition is a default policy condition.

16. An entity device for consuming analytics provided by a network entity device for analytics generation of a mobile network, the entity device comprising:

a memory having instructions stored thereon; and

a processor configured to execute the instructions to facilitate performance of the following by the entity device:

providing a request for an analytics output, wherein the analytics output is for a set of analytics types;

receiving the analytics output, wherein the analytics output is generated based on a set of baseline parameters, wherein the set of baseline parameters is associated with the set of analytics types, wherein the set of baseline parameters comprises an output strategy for providing the analytics output, and wherein the output strategy defines a mechanism that forces the network entity device to provide the analytics output, wherein the defined mechanism overrides a first policy condition for providing the analytics output;

providing a first request for the set of baseline parameters for generating the analytics output; and

receiving the set of baseline parameters in response to the first request.

17. The entity device according to claim 16 , wherein the processor is further configured to facilitate performance of the following by the entity device:

providing a second request indicating a requested set of baseline parameters for generating the analytics output;

wherein the analytics output is generated based on the requested set of baseline parameters.

18. The entity device according to claim 16 , wherein the processor is further configured to facilitate performance of the following by the entity device:

providing a third request indicating one or more proposed sets of baseline parameters associated with a set of analytics consumers and/or with the set of analytics types for generating the analytics output;

receiving one or more supported sets of baseline parameters and/or an identification of the one or more supported sets of baseline parameters, the one or more supported sets of baseline parameters being included in the proposed sets of baseline parameters, and the identification of the one or more supported sets of baseline parameters relating the third request to the one or more supported sets of baseline parameters; and

providing a message indicating a selected set of baseline parameters and/or the identification of the one or more supported sets of baseline parameters, the selected set of baseline parameters being selected from the one or more supported sets of baseline parameters;

wherein the analytics output is generated based on the selected set of baseline parameters.

19. A method for analytics generation of a mobile network, which is performed by a network entity device, the method comprising:

obtaining a set of baseline parameters, wherein the set of baseline parameters is associated with a set of analytics types, wherein the set of baseline parameters comprises an output strategy for providing an analytics output, and wherein the output strategy defines a mechanism that forces the network entity device to provide the analytics output, wherein the defined mechanism overrides a first policy condition for providing the analytics output;

providing the analytics output for the associated set of analytics types, wherein the analytics output is based on the set of baseline parameters;

receiving a first request to provide the set of baseline parameters for generating the analytics output; and

providing the set of baseline parameters in response to the first request.

20. The method according to claim 19 , wherein the set of baseline parameters further comprises at least one of:

volume of data for generating the analytics output;

one or more statistical properties of data for generating the analytics output; or

a synchronization deadline for providing the analytics output.

21. A method for an analytics consumer consuming analytics of a mobile network, which is performed by an entity device, the method comprising:

providing a request for an analytics output, wherein the analytics output is for a set of analytics types;

receiving the analytics output, wherein the analytics output is generated based on a set of baseline parameters, wherein the set of baseline parameters is associated with the set of analytics types, wherein the set of baseline parameters comprises an output strategy for providing the analytics output, and wherein the output strategy defines a mechanism that forces a network entity device to provide the analytics output, wherein the defined mechanism overrides a first policy condition for providing the analytics output;

providing a first request for the set of baseline parameters for generating the analytics output; and

receiving the set of baseline parameters in response to the first request.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 5, 2025
From: MARQUEZAN, CLARISSA; TRIVISONNO, RICCARDO
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 071933/0194 →
Continuity (3)
Continuation 17898198 · Aug 29, 2022
Continuation PCTEP2020055161 · Feb 27, 2020
Related Publication 20240243983A1 · Jul 18, 2024
References Cited (38)
US 8185619B1 · Maiocco et al. · 2012 [cited by applicant]
US 20100088234A1 · Moore et al. · 2010 [cited by applicant]
US 20140337268A1 · Bhattacharya · 2014 [cited by examiner]
US 20150065121A1 · Gupta et al. · 2015 [cited by applicant]
US 20160171134A1 · Mirabella et al. · 2016 [cited by applicant]
US 20160241579A1 · Roosenraad · 2016 [cited by examiner]
US 20190356558A1 · Han et al. · 2019 [cited by applicant]
US 20200044943A1 · Bor-Yaliniz et al. · 2020 [cited by applicant]
US 20210014141A1 · Patil · 2021 [cited by examiner]
US 20220116814A1 · Di Girolamo · 2022 [cited by examiner]
US 20220321423A1 · Norrman et al. · 2022 [cited by applicant]
US 20220345865A1 · Munoz De La Torre Alonso et al. · 2022 [cited by applicant]
US 20220345925A1 · Garcia Martin · 2022 [cited by examiner]
CN 110769455A · 2020 [cited by applicant]
JP 2021520745A · 2021 [cited by applicant]
KR 20190132898A · 2019 [cited by applicant]
WO 2019214830A1 · 2019 [cited by applicant]
WO 2019219173A1 · 2019 [cited by applicant]
WO 2020027638A1 · 2020 [cited by applicant]
WO 2020074092A1 · 2020 [cited by applicant]
WO 2020098951A1 · 2020 [cited by applicant]
WO 2020169174A1 · 2020 [cited by applicant]
WO 2021083612A1 · 2021 [cited by applicant]
“Shorten attribute names for QoS Sustainability,” TSG-CT WG3 Meeting #108-e, E-Meeting, C3-201306, Total 15 pages, 3rd Generation Partnership Project, Valbonne, France (Feb. 19-28, 2020). [cited by applicant]
“New Key Issue on Multiple NWDAF instances,” 3GPP SA WG2 Meeting #135, Split, Croatia, S2-1910575, Total 2 pages, 3rd Generation Partnership Project, Valbonne, France (Oct. 14-18, 2019). [cited by applicant]
“Clarifications on Potential QoS Change,” 3GPP TSG-SA WG2 Meeting #134, Sapporo, Japan, S2-1908221, Total 5 pages, 3rd Generation Partnership Project, Valbonne, France (Jun. 24-28, 2019). [cited by applicant]
“Corrections to general and framework parts of analytics,” SA WG2 Meeting #136, Reno, Nevada, USA, S2-1912272, Total 9 pages, 3rd Generation Partnership Project, Valbonne, France (Nov. 18-22, 2019). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 16),” 3GPP TS 23.501 V16.3.0, pp. 1-417, 3rd Generation Partn… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for 5G System (5GS) to support network data analytics services (Release 16),” 3GPP TS 23.288 V16.… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 16),” 3GPP TS 23.502 V16.3.0, pp. 1-558, 3rd Generation Partnership Pr… [cited by applicant]
“Corrections for analytics exposure framework related parameters,” SA WG2 Meeting #134, Sapporo, Japan, S2-1908038, Total 12 pages, 3rd Generation Partnership Project, Valbonne, France (Jun. 24-28, 2019). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study of Enablers for Network Automation for 5G (Release 16),” 3GPP TR 23.791 V16.2.0, pp. 1-124, 3rd Generation Partnershi… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enablers for network automation for the 5G System (5GS); Phase 2 (Release 17),” 3GPP TR 23.700-91 V0.3.0, pp. 1-35… [cited by applicant]
“Proposed New SID on Enablers for Network Automation for 5G—Phase 2,” 3GPP TSG-SA WG2 Meeting #133, Reno, USA, S2-1906722, Total 4 pages, 3rd Generation Partnership Project, Valbonne, France (May 13-17, 2019). [cited by applicant]
“Solution to support Multiple NWDAF Instances,” 3GPP SA WG2 Meeting #136, Reno, US, S2-1911341, Total 3 pages, 3rd Generation Partnership Project, Valbonne, France (Nov. 18-22, 2019). [cited by applicant]
SA WG2, “Presentation of TS 23.288: Architecture enhancements for 5G System (5GS) to support network data analytics services (Release 16),” 3GPP TSG SA Meeting #84, Newport Beach, USA, SP-190456, total 55 pages, 3rd Gen… [cited by applicant]
JP/2024-039898, Office Action, Feb. 18, 2025. [cited by applicant]
U.S. Appl. No. 17/898,198, filed Aug. 29, 2022. [cited by applicant]