UE Capability Update via Segmented Signaling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems, particularly LTE, face inefficiencies in updating user equipment (UE) capabilities, which requires significant network resources and overhead, especially when UE capabilities change, as existing methods involve tearing down and re-establishing RRC connections, leading to high overhead and inefficiency in dynamic capability updates.
Innovation Solution
The implementation of a method where user equipment (UE) provides capability-type indications and change indications using RRC signaling or lower layer signaling, allowing for autonomous or triggered updates, reducing the need for core network involvement and minimizing overhead by only transmitting changed capability information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional RRC connection teardown and re-establishment is used for capability updates, then capability changes can be communicated to the network, but network overhead and resource usage increase significantly
Solution Approach 1:
The capability update process is segmented into two distinct types: persistent capabilities (sent via RRC signaling) and non-persistent capabilities (sent via lower layer signaling). This segmentation allows the system to use the most efficient signaling method for each capability type, reducing overall network overhead while maintaining reliability.
Solution Approach 2:
The patent extracts non-persistent capabilities from the traditional RRC connection management process and handles them separately through lower layer signaling (MAC CE or physical layer). This extraction eliminates the need to teardown and re-establish RRC connections for non-persistent capability updates, significantly reducing network overhead.
2Loss of information
If RRC signaling is used for capability updates, then complete capability information can be transmitted, but signaling overhead and update time increase
Solution Approach 1:
Capability information is segmented into persistent and non-persistent categories, each transmitted through appropriate signaling channels. Persistent capabilities use RRC signaling for completeness, while non-persistent capabilities use faster lower layer signaling, reducing overall update time without losing critical information.
Solution Approach 2:
The UE preliminarily categorizes capabilities as persistent or non-persistent before transmission. This preliminary action allows the network to prepare appropriate reception and processing methods, reducing latency and ensuring no capability information is lost during transmission.
3Loss of information
If entire capability information is sent for every update, then all capability changes are communicated, but network overhead increases significantly
Solution Approach 1:
The patent extracts only the changed capability information from the complete capability set and transmits only what is necessary. For non-persistent capabilities, only the specific changed capability is sent via lower layer signaling, not the entire capability information, significantly reducing signaling overhead.
Solution Approach 2:
Different parts of the capability information are treated with different quality requirements. Critical persistent capabilities are transmitted with full detail via RRC signaling, while less critical non-persistent capabilities are transmitted with minimal information via lower layer signaling, optimizing the balance between information completeness and overhead.
4Productivity
If autonomous capability updates are allowed, then update speed increases, but network control and coordination decrease
Solution Approach 1:
The patent implements a dynamic capability update mechanism where the UE can autonomously initiate updates for non-persistent capabilities through lower layer signaling, while still allowing the network to request capability information when needed. This dynamic approach balances update speed with network control, adapting to different operational scenarios.
Solution Approach 2:
The network maintains the ability to send capability inquiry requests to the UE, creating a feedback loop that ensures network awareness of UE capabilities. This feedback mechanism coordinates autonomous UE updates with network needs, maintaining control while enabling fast updates.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A user equipment (UE) provides a capability-type indication for each of one or more UE capabilities. Each indication corresponds to a capability type, the type being one of a persistent capability or a second-type capability. Information corresponding to the capability-type indication may be provided to an eNB associated with the UE by RRC signaling. The UE provides a capability-change indication for each of one or more UE capabilities that has changed capability type. Information corresponding to the capability-change indication may be provided to an eNB by lower layer signaling, RRC signaling, or a combination thereof. Capability change information may be sent to the eNB autonomously by the UE, or in response to an inquiry from the eNB. The inquiry from the eNB may be triggered by the UE.