Temporary UE Identifier Segmentation Across RRC Messages
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless networks face challenges in transmitting a temporary UE ID due to size limitations in the RRC connection request, which affects contention resolution and connection performance, especially in LTE networks with truncated identifiers.
Innovation Solution
The temporary UE ID is divided into two parts, with the first part transmitted via the RRC Connection Request message and the second part via the RRC Connection Setup Complete message, allowing for a larger identifier size that fits within the message constraints.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the temporary UE ID is transmitted in the RRC Connection Request message, then the device identification is provided for contention resolution, but the identifier size is limited by the message structure
Solution Approach 1:
The temporary UE ID is divided into two parts: the first part (e.g., 32 bits) is transmitted in the RRC Connection Request message for initial contention resolution, while the second part (e.g., 16 bits) is transmitted later in the RRC Connection Setup Complete message. This segmentation allows the initial message to remain within size constraints while preserving the ability to transmit the complete identifier subsequently.
2Ease of operation
If the temporary UE ID is truncated to fit the message size, then the message can be transmitted successfully, but the device identification becomes ambiguous
Solution Approach 1:
By segmenting the temporary UE ID into two parts transmitted at different stages, the system avoids truncation entirely. The first part enables initial message transmission and contention resolution, while the second part is transmitted later to provide complete, unambiguous device identification, thus maintaining both transmission feasibility and identification precision.
3Reliability
If a larger temporary UE ID is used for better identification, then device security is improved, but the message size exceeds transmission constraints
Solution Approach 1:
The complete temporary UE ID (e.g., 48 bits providing unique device identification) is segmented into two parts. The first part fits within the initial RRC Connection Request message size constraints, while the second part is transmitted in the subsequent RRC Connection Setup Complete message. This approach maintains full identification reliability without exceeding any single message size limitations.
Solution Approach 2:
The system performs preliminary contention resolution using the first part of the temporary UE ID before transmitting the complete identifier. This preliminary action enables the network to resolve contention among multiple devices using only the first part, and then obtains the complete identifier afterward for reliable device recognition and security establishment.
Data Source
Figure 1
Figure 2~3B
Figure 4
AI summary
Various implementations of a method for transmitting a temporary identifier involve a wireless communication device: transmitting a first portion of a temporary identifier of the wireless communication device to a radio access network in a first message; and transmitting a second portion of the temporary identifier to the radio access network in a second message.