CS-PS Mobility Data Synchronization via Release Indicators
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobility Management (MM) data desynchronization between the Circuit Switched (CS) and Packet-Switched (PS) domains in mobile networks leads to incorrect mobility management procedures, such as paging issues, when a mobile device switches between different PS data networks.
Innovation Solution
A visitor location database in the CS domain synchronizes MM data by updating associations with MM nodes in the PS domain, using release indicators in specific messages (e.g., Gs-RELEASE-REQUEST, SGs-RELEASE-REQUEST) to ensure that associations are correctly deactivated and re-established, maintaining accurate MM data across both domains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a mobile device simultaneously attaches to both CS domain and PS domain (Class A operation mode), then the mobile device can access both voice services and data services, but MM data becomes desynchronized across the CS and PS domains
Solution Approach 1:
The VLR implements a feedback mechanism by sending release indicators to the old MM node when a mobile device attaches to a new PS domain. This feedback loop ensures that the old MM node is notified and can update its MM data accordingly, maintaining synchronization between CS and PS domains while allowing simultaneous attachment for versatile service access
Solution Approach 2:
The VLR acts as an intermediary between the CS domain and PS domain MM nodes. It receives location update requests from new MM nodes, updates MM data in the CS domain, and coordinates with old MM nodes through release indicators. This intermediary role enables seamless mobility management and data synchronization across domain boundaries
2Reliability
If the VLR updates MM data to remove association with an old MM node when the mobile device moves to a new PS data network, then MM data synchronization is maintained, but the old MM node continues to store incorrect association information
Solution Approach 1:
The system implements feedback by sending release indicators from the VLR to the old MM node. This feedback mechanism ensures that the old MM node receives notification of the association change and can update its stored MM data, preventing information loss and maintaining accuracy across the network
3Productivity
If paging procedures are performed without synchronized MM data between CS and PS domains, then mobility management can proceed, but paging procedures are not performed correctly
Solution Approach 1:
The system performs preliminary synchronization actions by updating MM data in the VLR and sending release indicators to old MM nodes before mobility management procedures are executed. This preliminary action ensures that all nodes have current and accurate MM data, preventing paging errors and ensuring correct procedure execution
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Systems and methods for synchronizing mobility management (MM) data between a CS domain and a PS domain. In one embodiment, a visitor location database of the CS domain stores MM data for a mobile device. If the visitor location database updates MM data for the mobile device to add an association for an MM node for mobility management, then the visitor location database determines if a prior association existed with another MM node. If so, the visitor location database removes the prior association with the other MM node, and transmits a release indicator to the other MM node indicating that the association has been removed. In response to the release indicator, the other MM node removes an association with the visitor location database, and the MM data for the mobile device is synchronized between the CS domain and the PS domain.