AMF Context Synchronization for 5G Network Reliability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G telecommunications networks, the failure of an Access and Mobility Management Function (AMF) can lead to an overload on other network elements, potentially causing a 'domino effect' due to the need for large numbers of client devices to re-register, which is operationally restrictive and inefficient.
Innovation Solution
A method is introduced where each management device in a set of (N + 1) management equipment shares or synchronizes context data with another management device within the set. If the first management device becomes out of service, the second management device takes over the client devices, minimizing the need for re-registration and distributing the load across multiple replacement management devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If context data is shared in real time between all AMFs in the same AMF Set, then client devices can avoid re-registration during AMF failure, but the number of AMFs per AMF Set must be large which implies large volume of data to be stored and exchanged
Solution Approach 1:
The patent segments the AMF Set into multiple groups, where each AMF shares context data only with a specific subset of other AMFs rather than all AMFs. This segmentation reduces the data volume and synchronization complexity while maintaining the ability to handle AMF failures effectively.
Solution Approach 2:
The patent implements local quality by having each AMF configure its own specific sharing relationship with particular other AMFs based on local requirements and failure scenarios. Not all AMFs need to share data with all other AMFs, only those in their designated sharing group, optimizing the balance between reliability and complexity.
2Device complexity
If the number of AMFs per AMF Set is small, then data storage and synchronization is simplified, but following AMF failure the other AMFs must bear significant additional load
Solution Approach 1:
The patent divides the AMF Set into multiple sharing groups where each AMF has a limited set of partners to share data with. This segmentation ensures that when one AMF fails, only the AMFs in its sharing group need to pick up its load, rather than all AMFs bearing the full additional load, thus balancing complexity and load distribution.
Solution Approach 2:
The patent implements preliminary action by pre-configuring sharing relationships between AMFs before failures occur. Each AMF is pre-assigned a specific sharing group, so when failure happens, the responsible AMFs are already identified and ready to take over, avoiding the need for all AMFs to react to every failure scenario.
3Quantity of substance
If AMF data is externalized into a shared database, then data storage requirement per AMF is reduced, but real time synchronization between different sites implies significant volumes of data exchanges
Solution Approach 1:
The patent segments the synchronization process by having each AMF synchronize only with specific other AMFs in its sharing group rather than synchronizing with all AMFs or using a centralized database for everything. This reduces the total volume of synchronization data exchanges while maintaining real-time data availability.
Solution Approach 2:
The patent introduces an intermediary mechanism where AMFs maintain shared data structures with specific peer AMFs rather than using a centralized database for all communications. This intermediary approach reduces synchronization overhead by limiting the scope of data exchanges to only those necessary for the sharing relationship.
Data Source
Figure 1
Figure 2a
Figure 2b
AI summary
The present invention relates to a method for toggling of a management entity in a telecommunications network, in which the network operator has defined at least one given set of (N + 1) management entities, where N≥ 2. Said method comprises, for at least one management entity of said set, termed "first management entity", the following steps: - as long as said first management entity is in service: • during the registration of at least one client device on the network, the first management entity takes charge of this client device, · this client device records the identity of the first management entity, as well as the identity of another management entity of said set, termed "second management entity", which is provided to it by the first management entity, and • the first management entity shares or synchronizes with said second management entity the context data relating to this client device, and - if the first management entity goes off-service, each second management entity is informed thereof and takes charge of the client devices for which it has shared or synchronized the context data with the first management entity. Application to 5G networks.