Data Channel Bootstrap Caching for Faster Application Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data channel communication systems face inefficiencies due to repetitive execution of the bootstrap procedure for every call establishment, unnecessary resource utilization, and delayed access to relevant applications, especially in emergency situations, caused by repetitive downloading of root applications and irrelevant application lists.
Innovation Solution
A method and system for managing data channel communication that determines the need for a root application request based on application type and validity, transmitting a request with a first application type information element, and receiving a response that includes a list of data channel applications, version, and validity, thereby reducing unnecessary downloads and delivering context-relevant applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the bootstrap procedure is executed for every call establishment, then the user can access applications, but redundant downloads occur and resource utilization increases
Solution Approach 1:
The system performs preliminary actions by downloading and caching the root application and application profiles during the first bootstrap procedure. Subsequent bootstrap procedures leverage this cached information, allowing the UE to skip redundant downloads and directly access applications without re-downloading the root application or retrieving application profile lists from the server.
Solution Approach 2:
The patent implements copying by creating a local copy of the root application and application profiles in the UE's memory during the initial bootstrap. This copied information is then reused across multiple call sessions, eliminating the need for repeated network requests and downloads, thereby reducing resource consumption while maintaining application accessibility.
2Adaptability or versatility
If the root application is downloaded every time a call is established, then the application list is updated, but data usage increases and access time is delayed
Solution Approach 1:
The root application and application profiles are downloaded and cached during the first bootstrap procedure as a preliminary action. Subsequent bootstrap procedures utilize this pre-fetched information, allowing the UE to immediately access applications without waiting for re-downloads, thus reducing access time while still receiving updates when necessary.
Solution Approach 2:
The system implements feedback mechanisms where the UE communicates with the server to check for updates in the root application or application profiles. The server responds with update indicators, allowing the UE to selectively update only when changes are detected, rather than continuously re-downloading, thereby optimizing both update freshness and access speed.
3Reliability
If the bootstrap procedure is repeated for every call, then application profiles are refreshed, but unnecessary data is transmitted
Solution Approach 1:
The patent extracts only the necessary information (application profiles and root application) during the initial bootstrap procedure and caches it locally. Subsequent bootstrap procedures extract only update information from the server when changes are detected, rather than transmitting the complete application profile list, thereby reducing unnecessary data transmission while maintaining profile freshness.
Solution Approach 2:
The system creates a local copy of application profiles and the root application during the first bootstrap. This copied information is reused across multiple sessions, and the UE selectively updates only when changes are detected through feedback from the server, eliminating redundant data transmission while preserving profile freshness.
Data Source
AI summary
A method for managing data channel communication by a user equipment (UE) is provided. The method includes determining transmit a root application request, transmitting the root application request comprising a first application type information element (IE) associated with the root application, based on determining to transmit the root application request, and receiving a root application response based on the first application type IE associated with the root application, in response to the root application request, wherein the root application response comprise at least one of a list of data channel applications, a root application version IE and a root application validity IE.