AMF Local Data Storage for 5G Registration Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing 5G cellular network registration process experiences latency due to the need to retrieve configuration and subscription data from a cloud-based unified data management (UDM) entity, leading to redundant data storage and increased bandwidth consumption.
Innovation Solution
Storing configuration and subscription data locally within the Access and Mobility Function (AMF) and using a UE ID to initiate registration, allowing the AMF to retrieve the necessary data locally instead of from a remote UDM, thereby reducing latency and bandwidth usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If configuration and subscription data is stored in centralized UDM and downloaded to AMF during registration, then data management is unified and consistent, but registration latency increases and bandwidth consumption increases
Solution Approach 1:
The patent segments the centralized UDM data storage into distributed AMF local storage. Each AMF maintains a local copy of configuration and subscription data, eliminating the need to retrieve data from centralized UDM during registration. This segmentation resolves the contradiction by allowing local access (reducing latency) while maintaining data consistency through periodic updates from UDM.
Solution Approach 2:
The patent applies preliminary action by pre-loading configuration and subscription data into AMF before registration occurs. The AMF retrieves and stores this data in advance, so it is immediately available when a UE registration request arrives. This eliminates the real-time data retrieval delay from UDM, reducing registration latency while maintaining data consistency.
2Reliability
If configuration and subscription data is stored in centralized UDM and downloaded to AMF during registration, then centralized control is maintained, but bandwidth consumption increases
Solution Approach 1:
The patent segments the centralized data storage model into distributed local storage at each AMF. This eliminates the need for continuous bandwidth-intensive data transfers from UDM to AMF during registration, as each AMF maintains its own local copy. Centralized control is preserved through periodic update mechanisms from UDM.
Solution Approach 2:
The patent uses copying by creating local replicas of configuration and subscription data at each AMF. Instead of repeatedly transmitting the same data from UDM to AMF during each registration, the data is copied to local storage once and reused locally. This dramatically reduces bandwidth consumption while maintaining data availability and centralized control through update mechanisms.
3Loss of information
If configuration and subscription data is stored for each individual UE in UDM, then complete user-specific data is maintained, but redundant data storage increases
Solution Approach 1:
The patent applies homogeneity by identifying and grouping UEs with identical configuration and subscription data. Instead of storing separate copies for each UE, the system recognizes that multiple UEs share the same data characteristics and stores a single shared copy that serves all identical users. This eliminates redundant storage while maintaining complete user-specific data for heterogeneous cases.
Solution Approach 2:
The patent makes the stored configuration and subscription data universal by creating a single copy that serves multiple UEs with identical requirements. This shared data structure performs the function of individual UE-specific storage for all matching users simultaneously, eliminating redundancy while maintaining data completeness through the universal shared representation.
Data Source
AI summary
A system and method may improve latency for user equipment (UE) registration in cellular networks. UE registration may retrieve the UE's configuration and subscription data locally rather than from a network or cloud-based unified data management (UDM) entity that manages a unified data repository (UDR). For example, the UE may send a unique identification (e.g., a UE ID) for the UE to a registering entity of a cellular network system. The UE ID may then be used to identify a UE Group Identification for the UE at the UDM. The UE Group Identification may be a pointer to the locally-stored configuration and subscription data for the UE. The entity requesting registration may then use the pointer to retrieve the configuration and subscription data locally rather than a remote entity such as the UDM.