5G Network Function Recovery Timestamp Binding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G communication networks with Service-Based Architecture, ambiguity in recovery information during NF entity restarts can lead to service disruptions, particularly when the binding level is set to NF Service Set or NF Instance, causing hanging contexts and service reestablishment issues.
Innovation Solution
Enhanced communication of recovery information is introduced, where a recovery timestamp is associated with the binding level of session contexts served by the NF entity, included in restart notifications via NRF and direct signaling, using custom HTTP headers or message bodies, to accurately indicate affected entities and facilitate proper resource handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a NF Set or NF Service Set is deployed with multiple instances for redundancy, then service continuity and reliability are improved, but ambiguity in recovery information during restart causes hanging contexts and service disruptions
Solution Approach 1:
The patent segments the recovery information by introducing distinct binding level indicators (NF Instance level, NF Service Instance level, NF Set level, NF Service Set level) that clearly differentiate the scope of session context binding. This segmentation eliminates ambiguity about which NF instance should handle recovered sessions, ensuring proper service continuity without hanging contexts.
Solution Approach 2:
The patent changes the parameter representation of recovery information by introducing enhanced binding level parameters in restart notifications. Instead of generic restart indicators, the system now includes specific binding level parameters that define the scope of session context recovery, transforming ambiguous recovery signals into precise operational instructions.
2Measurement precision
If recovery timestamp is associated with a specific NF instance, then precise tracking of affected sessions is improved, but service disruptions occur when the binding level is incorrectly set to NF Service Set or NF Instance
Solution Approach 1:
The patent introduces the binding level indicator as an intermediary parameter between the recovery timestamp and the NF instance identification. This intermediary clarifies the relationship between the timestamp and the affected NF entities, ensuring that session contexts are correctly associated with the appropriate binding level (NF Instance, NF Service Instance, NF Set, or NF Service Set) without causing service disruptions.
3Manufacturing precision
If restart notification includes detailed recovery information, then service restoration accuracy is improved, but message complexity and signaling overhead increase
Solution Approach 1:
The patent creates a universal binding level indicator that serves multiple functions: it identifies the scope of session context binding, determines the appropriate NF instance for service restoration, and guides the recovery process. This multi-functional parameter provides detailed restoration accuracy without proportionally increasing message complexity, as it leverages existing notification frameworks.
Data Source
AI summary
An enhanced communication of recovery information related to restart of a NF Service provider of NF consumer (e.g., NF Service Instance, NF Service Set, NF Instance, NF Set) is introduced. In exemplary embodiments, a recovery timestamp in a restart notification related to the restart of a NF Service provider or NF consumer is associated with the NF Service provider or NF consumer corresponding to the binding level of session contexts served by the service provider or NF consumer. The NF Service provider/consumer may be a NF Service Instance, NF Service Set, NF Instance and NF Set. In the case of a failure, the recovery timestamp populated in a recovery notification is matching the binding level of session contexts which will be affected by the failed NF Service provider/consumer. The recovery timestamp may be included in indirect signaling via a NRF and in direct signal between NFs. Further the recovery timestamp can be included in the header of a restart notification or in a message body of the restart notification. The restart notification may be a service request/response, notification request/response, or a Subscription request/response.