top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

what is the use of Random value in RRCconnectionRequest message in LTE?

+4 votes
what is the use of Random value in RRCconnectionRequest message in LTE?
posted Oct 7, 2013 by Giri Prasad

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

2 Answers

+1 vote
Best answer

Actually when an UE attaches to a network it can send either S-TMSI (in case of second time attach). Since S-TMSI is 5 bytes long (MMEC+ T-MSI). If UE doesn't have any stored S-TMSI then UE sends a 5 bytes long random value. If UE is sending S-TMSI then it helps to eNodeB to forward "Initial Ue Message" to appropriate MME.
If UE sends random value. It means eNodeB perform load balancing to send "Initial Ue Message" to the MME which is decided by load balancing algorithm.

I would like to share a Use case.
Suppose an UE went to RRC idle state. In that case, MME maintains Ue Context for some period of time to avoid creating a new context for every attach and lot of signalling message exchange in core network. For that purpose MME run implicit detach timer. Once the timer gets expired MME releases the context in the core network nodes.

It's my personal thoughts that something is also done at UE similar to MME. which decides either UE should sends S-TMSI or random value.

answer Oct 7, 2013 by Neeraj Mishra
+1 vote

I hope I understood the problem correctly, I assume you are talking about a random number which is filled as UEIdentity as part of connection setup request.

Case 1: The UE identity is signalled using the SAE Temporary Mobile Subscriber Identity (S-TMSI) if the UE is registered with the Tracking Area to which the current cell belongs.
Case 2: Otherwise, the UE selects a random number in the range from 0 to 2^40 - 1 to represent the UE
identity. (I hope this should clarify why random number is used)

answer Oct 7, 2013 by Deepankar Dubey
Similar Questions
+1 vote

Usually, I always saw when UE sends "S-TMSI" in RRC connection Request message then it definitely sends "Registered MME Information " in RRC Connection Setup Complete message.

I am looking for a scenario on which UE sends "Random number" in RRC Connection Request message and "Registered MME Information" in RRC Connection Setup Complete message.

+2 votes

It may be an easy question but still I have some doubt.
How RRC Connection setup procedure gets impacted with the presence of "S-TMSI" as an UE-Identity within the RRC Connection Request message ?
Note: RRC Connection request message can carry either 5 bytes long (S-TMSI) or 5 bytes long random value.