LTE Default Bearer Management for Mobile Connection Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In LTE capable communication devices on new operating systems, the 'Connect' button does not recover after the 'Disconnect' button is clicked, leading to a 'NO SERVICE' state and requiring a device reset, due to the lack of a CS domain for deactivating the last default bearer.
Innovation Solution
The communication device manages default bearers by checking the Context ID of the current connection, deactivating the second default bearer if present, and maintaining the first default bearer to keep the device registered, allowing the 'Connect' button to always appear on the host panel.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the last default bearer is deactivated in LTE mode, then the connection is released, but the device deregisters from the network causing the Connect button to never appear again
Solution Approach 1:
The patent segments the bearer management into two distinct parts: default bearers and dedicated bearers. By separating the deactivation scope to only dedicated bearers while preserving default bearers, the system avoids complete deregistration. This segmentation allows connection release for specific data flows without affecting the overall network registration state, resolving the contradiction between connection management flexibility and network registration reliability.
Solution Approach 2:
The patent applies local quality by making different bearer types subject to different deactivation rules. Default bearers are protected from deactivation to maintain network registration, while dedicated bearers can be deactivated for individual connection management. This localized differentiation in bearer treatment allows the system to achieve both connection control and registration stability simultaneously.
2Device complexity
If the PS attach is combined with PDP activation in LTE feature, then network registration is simplified, but the device cannot recover from NO SERVICE state after disconnection
Solution Approach 1:
The patent prepares the system in advance by maintaining at least one default bearer in an activated state before disconnection occurs. This preliminary action ensures that the network registration is pre-preserved, so when a disconnection event happens, the device remains in a recoverable state with the Connect button available, eliminating the need for device reset and enabling quick connection recovery.
Solution Approach 2:
The patent provides a cushioning mechanism by keeping default bearers active as a protective layer against complete deregistration. This beforehand cushioning ensures that even if dedicated bearers are deactivated during disconnection, the default bearers maintain the network registration, preventing the NO SERVICE state and enabling easy reconnection without system reset.
3Adaptability or versatility
If additional radio management software is installed, then radio control functionality is enhanced, but user confusion increases due to conflicting interfaces
Solution Approach 1:
The patent merges the radio management functionality directly into the operating system's network settings, eliminating the need for separate third-party radio management applications. By combining connection management, radio control, and network configuration into a unified native interface, the system provides enhanced adaptability while maintaining interface consistency, resolving the contradiction between functionality and user experience.
Data Source
AI summary
A communication device, user equipment, and a communication system are provided. The communication device comprises a Context ID check module to check a Context ID (CID) of a current default bearer in response to a disconnect command from a host; wherein, if the Context ID check module determines that there is only a first default bearer activated, the Context ID check module releases the connection between the communication device and the host without deactivating the first default bearer; and if the Context ID check module determines that there are two default bearers activated, the Context ID check module releases the second default bearer.