NF Repository Function for Network Component Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the EPC network, when an exception occurs in an NF component, such as overload or fault, it affects procedure message exchange between NF components, leading to a deterioration in network quality of service, and existing solutions are inefficient in enabling timely deployment of new network services due to high costs and long development periods.
Innovation Solution
The introduction of an NF repository management function component that pre-stores sets of NF components of the same type, allowing for the selection of a new NF component to take over partial or all functions of a faulty component, ensuring continuous procedure message exchange and improving network service reliability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If an NF component is split into independent functional components to enable flexible service deployment, then the adaptability and deployment speed of new network services are improved, but the reliability of network service deteriorates when exceptions occur in individual components
Solution Approach 1:
The patent implements preliminary action by pre-establishing backup NF components and pre-configuring their replacement relationships. When an exception occurs in a primary NF component, the backup component is already prepared and can immediately take over, eliminating the need for real-time discovery and configuration. This resolves the contradiction by ensuring both rapid deployment capability and continuous service availability through advance preparation of backup resources.
Solution Approach 2:
The patent applies beforehand cushioning by introducing backup NF components that stand ready to compensate for potential failures. The backup components are pre-positioned with identical or complementary functions to the primary components, creating a cushion against exceptions. This ensures that when a primary component fails, service continuity is maintained without interruption, thus resolving the reliability issue while preserving the flexibility of component-based architecture.
2Ease of manufacture
If NF components are decoupled into independent units to reduce development costs and improve deployment flexibility, then the ease of manufacture and deployment are improved, but the system complexity increases due to multiple components and their coordination
Solution Approach 1:
The patent applies merging by consolidating the backup NF components into a unified backup pool managed by the NF Repository Function. Instead of managing individual backup relationships between each primary component and its backup, the system merges all backup components under a central management function that handles discovery, selection, and coordination. This reduces the coordination complexity while maintaining the benefits of independent, easily deployable NF components.
Solution Approach 2:
The patent introduces the NF Repository Function as an intermediary between primary NF components and backup NF components. This intermediary manages the complexity of component coordination by providing a centralized interface for discovering, selecting, and coordinating backup resources. The NF Repository Function abstracts the complexity of component relationships, allowing primary components to simply declare their backup needs while the intermediary handles the intricate coordination details.
3Reliability
If backup NF components are introduced to ensure service continuity during exceptions, then the reliability of network service is improved, but the device complexity and resource consumption increase
Solution Approach 1:
The patent applies universality by designing the NF Repository Function to serve multiple purposes: it manages the backup pool, handles exception detection, coordinates failover, and provides resource allocation. This multi-functional approach consolidates what would otherwise require separate systems into a single unified function, reducing overall system complexity while maintaining high reliability through comprehensive backup management.
Solution Approach 2:
The patent uses copying by creating backup NF components that are functional copies of primary components. These copies are pre-configured with the same service capabilities and are stored in a managed pool. When needed, a backup copy is activated to replace the failed primary component. This copying approach ensures service continuity while keeping the backup infrastructure organized and manageable through the NF Repository Function's centralized control.
Data Source
Figure 1
Figure 1a-1
Figure 1a-2
AI summary
This application provides a method and a system for processing an NF component exception, and a device, and relates to the field of communications technologies, to resolve the following existing problem: When an exception occurs in an NF component, procedure message exchange between NF components is affected, and consequently network quality of service of an EPC network deteriorates. The method is applied to a network including user equipment, a first NF component, a second NF component, and an NF repository management function component, and includes: receiving, by the NF repository management function component, an NF discovery request message that includes an identifier of a set to which the second NF component belongs; determining, by the NF repository management function component based on the identifier of the set to which the second NF component belongs, that a third NF component having a same function as the second NF component exists in the network; and sending, by the NF repository management function component to the first NF component, a first message that includes an identifier of the third NF component, so that the first NF component sends, to the third NF component, received signaling sent by the user equipment.