Routing Data Layer for Roaming Subscriber Data Caching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The current process for establishing a roaming communication link for user equipment (UE) in a visited communication network is complex and time-consuming, especially in 5G networks, as it requires fetching subscriber-specific data from the home communication network, which can lead to congestion and overload.
Innovation Solution
Implementing a routing data layer (RDL) entity in the visited communication network that synchronizes subscriber-specific data with the home communication network, allowing the UE to obtain all necessary data for roaming without querying multiple network elements, thereby simplifying the roaming procedure and reducing message traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If subscriber-specific data is fetched from the home communication network during roaming connection establishment, then the UE can be authenticated and registered in the visited network, but the connection procedure becomes complex and time-consuming, leading to network congestion and overload
Solution Approach 1:
The RDL entity pre-fetches and stores subscriber-specific data (such as authentication credentials, service profiles, and routing information) from the home communication network before the UE actually needs to connect. This preliminary data preparation eliminates the need for time-consuming data retrieval during the critical connection establishment phase, thereby reducing connection procedure time while maintaining reliable authentication and registration
Solution Approach 2:
The RDL entity acts as an intermediary layer between the UE and the home communication network. Instead of the visited network directly querying multiple network elements in the home network during connection establishment, the RDL entity mediates by providing a localized cache of subscriber data, thus simplifying the interaction and reducing the time required for authentication and registration procedures
2Reliability
If multiple network elements are queried for subscriber-specific data during roaming, then complete authentication information can be obtained, but the system architecture becomes complex and message traffic increases causing congestion
Solution Approach 1:
The RDL entity consolidates multiple sources of subscriber-specific data (authentication credentials, service profiles, routing information, and policy data) into a single localized repository within the visited network. This merging of data sources eliminates the need for the visited network to query multiple separate network elements in the home network, thereby reducing system architecture complexity and minimizing message traffic while maintaining complete authentication capability
Solution Approach 2:
The RDL entity creates and maintains a local copy (cache) of subscriber-specific data that is normally stored in the home communication network. This copying mechanism allows the visited network to access all necessary authentication and service information locally without establishing complex communication paths to multiple home network elements, thus simplifying the system architecture while ensuring authentication completeness
3Reliability
If subscriber-specific data is retrieved from the home communication network during roaming, then the UE can be properly registered, but network congestion and overload occur due to increased message traffic
Solution Approach 1:
The RDL entity performs preliminary data retrieval and caching of subscriber-specific information during off-peak periods or during the initial setup phase, before the actual roaming connection demand arises. This advance preparation ensures that when UEs need to connect and register in the visited network, all necessary data is already available locally, eliminating the need for high-volume message traffic during peak connection periods and thus maintaining high network throughput while ensuring reliable UE registration
Solution Approach 2:
The RDL entity serves as an intermediary data repository that localizes subscriber-specific information within the visited network. By mediating between the UE registration process and the home communication network, the RDL entity prevents direct high-volume querying of home network elements during roaming connection bursts, thereby reducing network congestion and maintaining high productivity while still enabling proper UE registration through local data access
Data Source
AI summary
A method for initiating a roaming communication link with a user equipment in a visited communication network comprises: transmitting a registration request by the UE to a network entity of the visited communication network; detecting by the network entity of the visited communication network that the registration request is related to a roaming communication with the UE; determining by the network entity of the visited communication network a home communication network of the UE; retrieving, by the network entity of the visited communication network, subscriber-specific data of the UE from a routing data layer entity of the visited communication network for roaming the UE in the visited communication network, wherein the RDL entity is coupled to the home communication network of the UE via a data base interface; and initiating the roaming communication link with the UE based on the subscriber-specific data of the UE received via the RDL entity.