5G Network Function Re-Registration After Isolation Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G networks, isolated network functions (NFs) fail to de-register, leading to unnecessary network traffic and 503 errors, which degrade network efficiency and customer experience.
Innovation Solution
A method and system to identify isolated NFs, trigger a notification from the Network Repository Function (NRF) to the Service Communication Proxy (SCP) to de-register the NF, and facilitate re-registration upon restoration, using heartbeat monitoring and configurable timers to manage NF isolation and maintenance mode.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If the NRF continues to direct traffic to registered NFs without verifying their availability, then the NRF maintains simple registration management, but unnecessary network traffic is generated and 503 errors occur
Solution Approach 1:
The system performs preliminary actions by implementing heartbeat monitoring and isolation detection mechanisms that proactively identify NFs before they become completely unavailable. The NRF sends periodic heartbeats to registered NFs and detects isolation conditions before traffic is directed to failed NFs, preventing 503 errors before they occur.
Solution Approach 2:
The system implements feedback mechanisms where the NRF receives status information from NFs through heartbeat responses and sends de-registration notifications to the SCP when NFs are detected as isolated. This continuous feedback loop ensures the SCP has up-to-date information about NF availability without requiring complex management procedures.
2Ease of operation
If the SCP maintains a cache of all registered NFs without de-registration capability, then the SCP simplifies service routing, but traffic continues to be directed to isolated NFs causing network inefficiency
Solution Approach 1:
The NRF acts as an intermediary between the SCP and NFs, receiving heartbeat information from NFs and sending de-registration notifications to the SCP when NFs are isolated. This intermediary mechanism allows the SCP to maintain its simple cache-based routing while the NRF handles the complexity of availability monitoring and de-registration coordination.
Solution Approach 2:
The system performs preliminary de-registration actions by detecting isolation conditions and notifying the SCP to remove isolated NFs from its cache before traffic is directed to them. This prevents network efficiency degradation while keeping the SCP's routing operation simple.
3Reliability
If the NFs are monitored continuously for isolation status, then isolated NFs can be de-registered promptly, but the system complexity and resource consumption increase
Solution Approach 1:
The system uses periodic heartbeat monitoring instead of continuous monitoring, where the NRF sends heartbeats at defined intervals to check NF availability. This periodic approach maintains reliable isolation detection while significantly reducing system resource consumption compared to continuous monitoring.
Solution Approach 2:
The NFs participate in the monitoring process by responding to heartbeats from the NRF, effectively performing self-service availability reporting. This reduces the burden on the NRF and SCP, as the NFs themselves provide information about their operational status through heartbeat responses.
Data Source
AI summary
Methods and systems provided herein provide for de-registration and re-registration of network functions. Methods provided herein identify isolated network functions and trigger a notification from the network repository function (NRF) to the service communication proxy (SCP) of the isolation. The SCP deletes the isolated NF from storage and sends no further traffic to the NF. Upon detection of restoration of the network function, the network function may be prompted by the NRF to re-register with the NRF.