top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration

Facebook Login
Site Registration

Is C_RNTI is mandatory in mobility control info

+1 vote

Why we need c_rnti in mobility control info, because UE will get the CRNTI in target ENB RAR right ???

posted Apr 5, 2017 by Akhilesh

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

2 Answers

0 votes
Best answer

As per 3gop 36.331 c-rnti in mobility control info is mandatory. This could be because rach during HO can be contention based. So ue needs to tell c-rnti to eNb in msg3 to identify the ue context at eNb.

answer Apr 6, 2017 by Veer Pal Singh Yadav
thank you for your answer, now i understood why it is included in mobility control info.  But why it is included in bot the case like contention based and contention free case.
0 votes

In handover case, UE context is already created at target eNodeB, that's why Target cell sends the allocated C-RNTI to source and source cell in turn sends to UE in mobility control info IE.

When UE does RAR with the assigned preamble target eNodeB MAC maps the UE context and since all the contexts have already been created at target eNodeB handover becomes faster.
This is my understanding and interpretation of sending target eNodeB's C-RNTI in mobility control info.

answer Apr 5, 2017 by Harshita
Similar Questions
+4 votes

Since Ue can be configured for measure at the time of RRC Connection Setup. What is the probability to get mobility control info inside RRC Connection Reconfiguration as part of initial attach procedure.

+2 votes

Please can anyone explain me,
In which Scenario, eNB send Idlemodemobilitycontrolinfo IE with release cause "other" inside RRC CONNECTION RELEASE message to UE???

0 votes

5G: Beam level mobility does not require handover,but if the target beam is on another cell will it require handover?

Contact Us
+91 9880187415
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Karnataka INDIA.