NWDAF Dynamic Analytics Registration for Custom Functions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing NWDAF architecture lacks flexibility and efficiency due to the requirement for standardized or proprietary analytics functions, limiting operators' ability to define custom functions and necessitating costly software upgrades for new analytic definitions.

Innovation Solution

A system allowing NWDAF service consumers to register dynamic analytics functions, verified against pre-determined criteria, enabling operators to define custom functions on demand without software upgrades, and supporting more versatile service offerings.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If standardized analytics functions are used in NWDAF, then system reliability and interoperability are improved, but flexibility and adaptability to custom operator needs deteriorate

Engineering Contradiction:
Improvesystem reliabilityVSAvoidflexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces dynamic analytics function definitions that can be registered and updated at runtime without requiring system reconfiguration. Service consumers can define custom analytics functions dynamically, and the NWDAF can load and execute these functions on-demand, transforming the static standardized function model into a dynamic system that adapts to varying operator requirements while maintaining reliability through controlled registration processes.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent segments analytics functions into standardized core functions and customizable extension functions. The standardized functions provide reliable base functionality, while extension functions allow operators to add custom analytics capabilities. This segmentation enables the system to maintain reliability through standardized interfaces while achieving flexibility through modular extensions that can be independently registered and managed.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If proprietary analytics functions are implemented in NWDAF, then adaptability to specific operator needs is improved, but ease of operation and function discovery deteriorate

Engineering Contradiction:
ImproveadaptabilityVSAvoidease of operation
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a service consumer as an intermediary between the operator's analytics needs and the NWDAF execution environment. The service consumer defines analytics functions in a standardized, operator-friendly manner, while the NWDAF handles the technical details of function registration, verification, and execution. This intermediary approach simplifies operation for users while enabling advanced analytics capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a feedback mechanism where the NWDAF provides analytics function identifiers and status information back to service consumers after successful registration. This feedback loop enables operators to discover and manage their registered functions easily, improving ease of operation while maintaining adaptability through the dynamic function definition capabilities.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If new analytics functions are added to NWDAF through standardization, then adaptability is improved, but loss of time and implementation cost increase

Engineering Contradiction:
ImproveadaptabilityVSAvoidimplementation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent enables preliminary definition and verification of analytics functions by service consumers before actual deployment. Operators can pre-define analytics function specifications in a standardized format, and the NWDAF can verify their validity in advance. This preliminary action eliminates the need for time-consuming standardization processes when new analytics functions are needed, as operators can simply register their pre-defined functions without waiting for standard body approval.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If dynamic analytics function registration is enabled, then flexibility and adaptability are improved, but device complexity and verification requirements increase

Engineering Contradiction:
ImproveflexibilityVSAvoidcomplexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent enables service consumers to self-define and self-register analytics functions using standardized templates and interfaces. The service consumers are empowered to create their own analytics function definitions without requiring complex configuration or manual intervention from the NWDAF side. This self-service approach manages complexity by pushing the definition work to the consumer side while keeping the NWDAF's verification process simple and automated.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12452139B2Network data analytics function architecture with dynamic analytic functions
Publication Date: 2025.10.21 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US12452139B2 patent drawing
  • US12452139B2 patent drawing
  • US12452139B2 patent drawing

AI summary

A system for network data analytics, the system comprising a network data analytics function, NWDAF, (200) and at least one NWDAF service consumer function, SCF, (220) arranged to connect to the NWDAF (200), wherein the SCF (220) is arranged to obtain (Sa1) a dynamic analytics function definition, wherein the dynamic analytics function definition defines a custom analytics function for processing data at the NWDAF (200), and register (Sa4, 310, 410) the dynamic analytics function definition at the NWDAF (200), wherein the NWDAF (200) is arranged to receive (Sb1) the dynamic analytics function definition from the SCF (220), assign (Sb3) an analytics function identifier to the received dynamic analytics function definition, transmit (Sb4, 320, 420) the analytics function identifier back to the SCF (220), and register (Sb5) the dynamic analytics function definition in an analytics function definition store of the NWDAF (200), wherein the SCF (220) is arranged to receive (Sa5, 320) the analytics identifier associated with the registered dynamic analytics function definition from the NWDAF (200) in response to the registering.