RRC Connection ReEstablishment
RRC Connection ReEstablishment
RRC Connection ReEstablishment
1.1 Objective
The main objective of this document is to understand the RRC connection
Establishment procedure and RRC connection Re-Establishment procedure at both
eNB and UE perspective.
1) After the cell search is done and when UE initiates the call procedure, RACH
procedure is initiated by the UE(if it is contention based RACH)
3) eNB sends RAR PDU with Uplink Grant on reception of preamble ID. RAR
PDU contains the parameters C_RNTI (Cell Radio Network Temporary
Identifier), UL grant, Random access channel preamble ID and timing
advance.
5) eNB will send back the same msg3 to UE stating that RRC connection
request is received on Msg4.
8) After SRB1 is created, UE and eNB should communicate through the SRB1
only.
15)eNB sends request to UE for its capability information and sends to MME.
When a UE looses sync with the eNB, it tries to regain its connection with
the eNB. In simple words, the above process can be interpreted as Re-
Establishment. In this procedure, UE initiates RACH procedure and on successful
RACH operation, UE requests eNB for RRC connection Re-Establishment setup,
which in turn UE sends RRC connection Re-Establishment completed to eNB, to
regain back to RRC_Connected state.
UE eNB
UE eNB
Below are some of the reasons for triggering RRC connection Re-Establishment.
1) On T310 failure,
2) On RACH msg / indication to UE when T311 is not started,
3) On indication to UE that max number of RLC retransmission has been
reached.
4) On UL TB CRC failure scenario either in control plane or data plane.
When any of the above causes occurred, the UE will consider that radio link
failure happened and should be detected. If the security is activated the UE will
initiate the RRC connection re-establishment procedure, else the UE will leave the
state RRC_CONNECTED.
Hand over failure can happen when any one of the following scenarios were
met, leading to triggering of RRC connection ReEstablishment.
1) When TeNB does not have enough resources to admit a new UE.
2) When TeNB does not have that particular UEs valid context.
For remaining scenarios, same C-RNTI is used from the cell in which
the trigger for Re-establishment happened.
1) Stop timer T310(UE to get back in sync with eNB) if already running
a. The reason why we are suspending the PDCP and RLC entities is,
after suspending the PDCP and RLC entities, no meta data will be
sent to MAC for scheduling.
a. All the HARQ process IDs were released and the state is reset to
HARQ_IDLE in this MAC reset process.
b. Despite of receiving ACK / NACK from the UE, when
ReEstablishment has been triggered, releasing of HARQ
retransmission buffers will happen.
5) To reset and apply default physical channel configurations and MAC main
configurations
At UE after the cell selection is completed the timer T311 is stopped and
timer T301 is started to initiate the contention based RACH. If the selected
cell is inter RAT cell, the UE will leave the state RRC connected.
The RRC Connection Re-Establishment reject could happen when the eNB
rejects the Re-Establishment request message sent by the UE. The following are
few of the reasons for the Re-Establishment reject scenario.