Network Function Subscription Scope for Seamless Event Transfer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing communication systems lack efficient mechanisms for managing network function subscriptions and event notifications in wireless communication networks, particularly in scenarios involving changes in device location, public land mobile networks, and standalone non-public networks, leading to potential disruptions and inefficiencies.

Innovation Solution

An apparatus and method for managing network function subscriptions by determining event provision based on subscription scope, handling changes in device location, network type, and network function producer transitions, and transferring subscriptions to target producers when necessary.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If network function subscriptions are managed without scope definition, then subscription setup is simple, but event notification reliability deteriorates during network changes

Engineering Contradiction:
Improveevent notification reliabilityVSAvoidsubscription management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by defining subscription scope (including PLMN ID, S-NSSAI, area of validity) in advance during subscription setup. This pre-definition enables the network function producer to proactively evaluate whether to continue event notifications when network changes occur, preventing unreliable notifications before they happen. The scope parameters are established beforehand to guide subsequent decision-making during mobility events.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements dynamics by making subscription management adaptive to network conditions. The network function producer dynamically evaluates current network state (PLMN, slice, area) against the pre-defined subscription scope and adjusts event notification behavior accordingly. This dynamic evaluation ensures reliable notifications are sent only when within scope, while automatically stopping or transferring subscriptions when out of scope, maintaining reliability without rigid complexity.

Inventive Principle:
Principle #15Dynamics

2Productivity

If event notifications are continuously provided without scope checking, then service continuity is maintained, but network resource efficiency deteriorates

Engineering Contradiction:
Improvenetwork resource efficiencyVSAvoidservice continuity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies feedback by continuously monitoring network parameters (PLMN ID, S-NSSAI, area of validity) and comparing them against the subscribed scope. This feedback mechanism enables the network function producer to make informed decisions about continuing, stopping, or transferring event notifications. The feedback loop ensures resource efficiency by stopping unnecessary notifications while maintaining service continuity through automatic subscription transfer when moving to valid scopes.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent extracts the scope evaluation logic from the subscription management process. By separating the scope checking function (comparing current network state with subscribed scope) from the event notification function, the system can efficiently determine when to stop notifications without affecting the core notification mechanism. This extraction enables resource-efficient filtering of unnecessary notifications while preserving service continuity for valid subscriptions.

Inventive Principle:
Principle #2Taking out (Extraction)

3Measurement precision

If subscription scope validation is performed at every network change, then event notification accuracy is improved, but processing time increases

Engineering Contradiction:
Improvesubscription scope matching accuracyVSAvoidsubscription evaluation time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-defining all scope parameters (PLMN ID list, S-NSSAI list, area of validity) during subscription setup. This pre-preparation eliminates the need for complex real-time calculations during network changes. When mobility events occur, the system only needs to compare current network state against the pre-stored scope parameters, significantly reducing processing time while maintaining high matching accuracy.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If subscriptions are automatically transferred to target network function producers, then service continuity is improved, but system complexity increases

Engineering Contradiction:
Improveservice continuityVSAvoidsubscription transfer mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies self-service by enabling the network function consumer to autonomously evaluate and execute subscription transfers. When a mobility event occurs and the current network function producer is determined to be out of scope, the consumer automatically initiates the transfer process to a target producer within the new scope. This self-service mechanism ensures service continuity without requiring complex centralized coordination, as each consumer independently manages its own subscription transfers based on scope evaluation.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20260046592A1Apparatus, methods, and computer programs
Publication Date: 2026.02.12 NOKIA TECHNOLOGIES OY
  • US20260046592A1 patent drawing
  • US20260046592A1 patent drawing
  • US20260046592A1 patent drawing

AI summary

An apparatus comprises at least one processor and at least one memory storing instructions for a network function. The instructions when executed by the at least one processor cause the apparatus to perform: receiving subscription information defining a scope for a subscription, the subscription being for a network function service consumer to receive events from a network function service producer, the events being associated with a communications device; and determining, based on the subscription information, that the subscription to the network function service producer is to be set up.