Binding Scope Parameters for 5G Network Function Routing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing wireless communication systems lack efficient mechanisms for binding indications in network function scenarios, leading to suboptimal network function service instance selection and notification routing, particularly in 5G networks.

Innovation Solution

The implementation of a scope parameter in binding indications to specify scenarios, allowing for network function service instance selection, reselection, and routing of requests or notifications, using identifiers and service names to define binding levels and scenarios such as subscription events, notification events, or further services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If binding indications are implemented without scope parameters, then network function service instance selection and notification routing can be performed, but the selection and routing efficiency is suboptimal and lacks scenario-specific optimization

Engineering Contradiction:

Improvenetwork function service instance selection efficiencyVSAvoidbinding indication structure complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The binding indication is segmented into distinct components: a scope parameter that identifies the scenario (subscription events, notification events, or further services) and specific binding identifiers. This segmentation allows the system to select and process only the relevant binding information for each scenario, improving efficiency without requiring complex processing of unnecessary data.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Different scope parameters are assigned to different scenarios (subscription events, notification events, further services), allowing each scenario to have optimized binding handling. The scope parameter enables local optimization by directing binding indications to appropriate handlers based on the specific scenario, rather than using a uniform complex processing mechanism for all cases.

Inventive Principle:

Principle #3Local quality

2Adaptability or versatility

If multiple binding scenarios are supported without scope parameters, then network functions can handle various events, but the mechanism becomes suboptimal and lacks clear scenario differentiation

Engineering Contradiction:

Improvescenario-specific binding capabilityVSAvoidscenario identification information

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The scope parameter acts as an intermediary that carries scenario identification information between the network function service consumer and producer. It mediates the binding indication by explicitly specifying which scenario (subscription events, notification events, or further services) the binding applies to, preventing loss of scenario differentiation information.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The scope parameter introduces a new parameter dimension to the binding indication structure. By changing the parameter set based on the scenario (different scope values for subscription events, notification events, and further services), the system maintains adaptability across multiple scenarios while preserving clear scenario identification through parameter variation.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If binding indications are sent without scope parameters, then network function service producer can receive bindings, but accurate resource allocation based on defined scenarios cannot be achieved

Engineering Contradiction:

Improvebinding accuracyVSAvoidresource allocation complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The scope parameter is included in advance within the binding indication, performing preliminary scenario identification before resource allocation occurs. This preliminary action enables the network function service producer to immediately route the binding to the appropriate handler for the specific scenario, ensuring accurate resource allocation without requiring complex post-reception analysis.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS12531792B2Scope parameter for binding indication

Publication Date: 2026.01.20 NOKIA TECHNOLOGIES OY

AI summary

Methods, apparatuses, and computer program products for scope parameters for indication are disclosed. The method can include generating an indication comprising a scope parameter and at least one of: a network function service instance identifier, a network function service set identifier, a network function instance identifier, a network function set identifier, and a service name, wherein the scope parameter is configured to indicate at least one scenario to which an associated binding relates; and sending the indication from a network function service consumer to a network function service producer.