Core Network Function Exposure for Fast Service Instantiation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Network operators face challenges in efficiently instantiating, scaling, and reconfiguring network functions (NFs) due to delayed network reconfiguration and geographic placement of services, which affects charging record collection and service availability.

Innovation Solution

A core network system with processors and memory for dynamic registration, discovery, instantiation, and reconfiguration of network functions, enabling nodes like UE and AS to request and manage NFs, including geographic placement and charging information configuration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If network reconfiguration is performed to scale or reconfigure network functions, then network flexibility and operational efficiency are improved, but notification time to nodes increases significantly

Engineering Contradiction:
Improvenetwork reconfiguration efficiencyVSAvoidnotification time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system establishes a subscription mechanism where nodes beforehand indicate their interest in receiving notifications about network function changes. The network operator maintains a registry of subscribed nodes and proactively pushes notifications when reconfiguration occurs, eliminating the need for nodes to continuously query the network status.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback loop where nodes subscribe to notification services, the network operator processes reconfiguration requests and updates the registry, and then automatically pushes notifications to subscribed nodes. This closed-loop feedback mechanism ensures timely information delivery without requiring continuous node-initiated queries.

Inventive Principle:
Principle #23Feedback

2Speed

If network functions are instantiated at the edge of the network close to devices, then service proximity and latency are improved, but charging record collection becomes difficult

Engineering Contradiction:
Improveservice latencyVSAvoidcharging record management
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system introduces a charging record collection point as an intermediary component between the edge network functions and the central charging system. This intermediary is specifically designed to aggregate charging records from distributed edge instances and forward them to the central charging system, simplifying the charging architecture while enabling edge instantiation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If a catalog of network functions is maintained for instantiation requests, then service discovery and configuration options are improved, but system complexity increases

Engineering Contradiction:
Improveservice discovery capabilityVSAvoidrepository management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements a universal notification service that handles multiple types of communications (subscription confirmations, reconfiguration notifications, charging records) through a single standardized mechanism. This multi-functional approach reduces overall system complexity compared to maintaining separate specialized systems for each function.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12627575B2Capability exposure for service instantiation
Publication Date: 2026.05.12 INTERDIGITAL PATENT HOLDINGS INC
  • US12627575B2 patent drawing
  • US12627575B2 patent drawing
  • US12627575B2 patent drawing

AI summary

The application is at least directed to a core network including a non-transitory memory having instructions stored thereon for registering a network function or network function template in the core network. The network includes a processor, operably coupled to the non-transitory memory. The processor is configured to perform the instruction of determining that registration of the network function or network function template is acceptable. The processor is also configured to perform the instruction of transmitting a message including the network function or network function template to a repository in the core network. The processor is also configured to perform the instruction of verifying the network function or network function template against existing policies in the core network. The processor is also configured to perform the instruction of registering the network function or network function template in the repository after verification. The application is also directed to a core network that discovers a network function or network function template therein. The application is also directed to a core network that instantiates a network function.