top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

LTE : In which scenario, UE sends "random number" within the RRC connection request message ?

+1 vote
1,042 views

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.

posted Jan 13, 2016 by Vimal Kumar Mishra

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

1 Answer

+1 vote

As per 24.301...

When the UE is not registered in the tracking area of the current cell during the NAS signalling connection
establishment, the UE NAS does not provide the lower layers with the S-TMSI. If the UE has a valid registered
MME identifier from a previous registration, the UE NAS shall provide the lower layers with the registered
MME identifier.

So in this scenario when ue is making rrc connection with cell having not registed tracking area, UE will send random number in rrc Connection request and registered MME info in rrc Connection complete msg.

answer Jan 21, 2016 by Veer Pal Singh Yadav
Thanks a lot Veer Pal Singh Yadav for your answer.
commented Jan 22, 2016 by Vimal Kumar Mishra
Similar Questions
+2 votes
LTE: What is the use of "S-TMSI" when it receives in the RRC Connection Request message ?

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.

+1 vote
LTE : how to handle when UE sends second connection request with same IMSI ??

If UE shutdown appropriately then context will not be deleted at network. after some time when UE switch on UE will send attach request with the IMSI, but with same IMSI ENB have already an context. Spec says reject the second UE if already old context present but the second UE is valid and first UE is not valid then how to handle.

...