Application Context Transfer Across Public and Private Mobile Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies fail to seamlessly transfer application contexts between different mobile networks, particularly between public and private networks, due to limited or intermittent connectivity, which disrupts service continuity for critical applications like those used in autonomous vehicles or public safety devices.
Innovation Solution
A client device with a data storage and processor subsystem retrieves and stores an application context from a first mobile network and transfers it to a second mobile network, enabling service continuity by carrying the context locally and uploading it to the new network, independent of direct network connectivity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the application context is transferred between different mobile networks using existing ACT procedures, then service continuity can be maintained within a same mobile network, but the transfer fails when switching between different mobile networks due to limited or intermittent connectivity
Solution Approach 1:
The client device retrieves and stores a local copy of the application context from the first mobile network before disconnecting. This preliminary action ensures that the context data is available locally when switching to a second mobile network, enabling seamless service continuity without relying on real-time network connectivity between networks.
Solution Approach 2:
The client device acts as an intermediary carrier for the application context. Instead of directly transferring context between networks (which requires network-to-network connectivity), the client device receives, stores, and then transmits the context to the second network, mediating the transfer when direct network connectivity is unavailable.
2Reliability
If the application context is stored locally in the client device data storage, then the transfer can occur independently of direct network connectivity, but this increases the device's data storage requirements
Solution Approach 1:
The client device stores a local copy of the application context rather than the full original context. This copying approach allows the essential data needed for service continuity to be retained locally while minimizing storage requirements, as only the necessary context information is duplicated rather than entire application states.
3Ease of manufacture
If the application context is transferred via network connection between mobile networks, then direct transfer is possible, but this increases bandwidth consumption and power usage especially when connectivity is unstable
Solution Approach 1:
The application context is retrieved and stored in the client device's data storage before network disconnection occurs. This preliminary retrieval action eliminates the need for continuous or repeated network transmissions during the switching process, significantly reducing bandwidth consumption and power usage when network connectivity is unstable or intermittent.
Data Source
AI summary
A client device may utilize an application service provided by a mobile network. The client device may be configured to transfer an application context of the application service between different mobile networks by, when the client device is connected to a first mobile network, retrieving the application context from the first mobile network and storing the application context as a local copy in the data storage, and when the client device is connected to a second mobile network, sending the application context to the second mobile network. This way, it may not be needed to rely on connectivity existing between the first mobile network and the second mobile network to transfer the application context, which connectivity may for example lack if one or both of the mobile networks are non-public networks.