Subscription Switch Management Agent for Seamless MNO Transition
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing methods for switching a subscription from one Mobile Network Operator (MNO) to another are prone to service disruptions and network disconnections due to errors during the subscription switch process, highlighting the need for a reliable method to ensure a seamless transition.
Innovation Solution
A method involving a Subscription Switch Management agent and a token entity that requests necessary data from a remote server, temporarily stores updates, and seeks user authorization before switching the subscription from the first MNO to the second MNO, with flags to manage data updates and ensure a 'Point of No Return' during the process, and reverts if the switch is not effective, along with informing the networks of the subscription change.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a direct subscription switch method is used from first MNO to second MNO, then the switching process is simple and quick, but service disruptions and network disconnections occur due to errors during the switch process
Solution Approach 1:
The patent applies preliminary action by creating a new account with all necessary subscription data and authentication data in advance on the second MNO before the actual subscription switch occurs. This preparatory step ensures that when the switch happens, all data is ready and validated, preventing errors during the switch process while maintaining service continuity.
Solution Approach 2:
The patent introduces a remote server as an intermediary between the first MNO and the second MNO. This server coordinates the subscription switch process, manages data transfer, and ensures proper sequencing of operations. The intermediary role of the remote server prevents direct connection errors between MNOs and maintains service continuity throughout the transition.
2Productivity
If subscription data is updated directly during the switch process, then the switching process is fast, but data corruption or loss may occur leading to system collapse
Solution Approach 1:
The patent creates the complete new account with all subscription data and authentication data in advance on the second MNO before the actual switch. This preliminary data preparation ensures data integrity is maintained while allowing fast switching, as no complex data transfers occur during the critical switch moment.
Solution Approach 2:
The patent involves creating a copy of the subscription data in the form of a new account on the second MNO. The remote server retrieves and processes data to create this duplicate account structure, ensuring data integrity through proper copying and validation before the actual subscription switch occurs.
3Reliability
If the system performs extensive data validation and user authorization checks, then data integrity and user consent are ensured, but the switching process becomes complex and time-consuming
Solution Approach 1:
The patent performs user authorization requests and data validation checks in advance during the account creation phase on the second MNO. By completing these complex verification steps before the actual subscription switch, the patent ensures data accuracy and user consent while keeping the final switch process simple and quick.
4Reliability
If the system implements rollback mechanisms for failed switches, then service continuity is maintained, but the system complexity increases
Solution Approach 1:
The patent prepares the complete new account with all necessary data in advance on the second MNO before the subscription switch. This preliminary preparation reduces the need for complex rollback mechanisms because the switch process becomes more predictable and less prone to failure, thereby maintaining service continuity with reduced system complexity.
Data Source
Figure 1
Figure 2
AI summary
The invention relates to a method for switching a subscription of a user from a first MNO (1) to a second MNO (2), characterized in that it comprises requesting to a remoter server switching from the first MNO to the second MNO and temporary storing data updates related to the second MNO in a dedicated file.