RRC Connection Re-establishment in LTE

Query_1: Why RRCConnectionReestablishment is needed?

This procedure is needed in order to re-establish RRC Connection. Also, it helps
to re-establish the SRB1 operation and re-activate the Security algorithms (the
security algorithms doesn't change)

This procedure is successful only when eNBl has a valid UE context. If eNB
doesn't have the UE context then UE moves to RRC_IDLE state

Query_2: When RRCConnectionReestablishment is triggered?
1. This procedure is triggered when any of the following conditions are met:

Also. an important point is that this procedure is triggered only when AS security has been activated. click here) 2. click here)  upon integrity check failure indication from lower layers  upon an RRC connection reconfiguration failure (To know more about Reconf failure. This procedure will perform the following steps:  stop timer T310. This will be a case of RADIO LINK FAILURE  start timer T311 (This timer is started when UE initiates the RRC connection reestablishment procedure)  suspend all RBs except SRB0 (SRB0 is needed in order to transmit the RRC connection re-establishment message. UE enters any of the state as mentioned in "Query_2". upon detecting radio link failure (To know more about RLF. it will initiate the RRCConnectionReestablishment procedure. What does UE includes in RRCConnectionReestablishmentRequest message?  include the ue-Identity "c-RNTI" as used in the Scell  include the PHY Cell ID of the source cell  include the ue-Identity "c-RNTI" as used in the Scell  include the shortMAC-I for Security algorithms  include the reason of the reestablishmentCause as 'reconfigurationFailure' OR . otherwise. UE doesn't initiate this procedure and moves to RRC_IDLE state Query_3: What happens when RRCConnectionReestablishment procedure is triggered? Once. click here)  upon handover failure  upon mobility from E-UTRA failure (To know more about Mobility from EUTRA failure. and this procedure is needed to re-establish SRB1 operatation)  reset MAC (removed the already applied MAC configurations)  apply the default physical channel configuration  apply the default semi-persistent scheduling configuration  apply the default MAC main configuration  release reportProximityConfig and clear any associated proximity status reporting timer  perform cell selection in accordance with the cell selection process Query_4. if running (This timer is started when the UE detects consecutive out-of-sync indications from lower layers -related to N310 constant-).

The following messages a. UE RRC constructs this message and passes it to lower layers for transmission. Here. c.'handoverFailure' OR 'otherFailure' Important TIP:Now. Which Channels are used for RRCConnectionReestablishment procedure? 1. RRCConnectionReestablishmentReject will use the following: Radio Link Failure in LTE Triggering points of RLF . and  UE should apply ciphering and integrity protection to all subsequent messages received and sent by the UE  UE shall use Security algorithms while transmitting the RRCConnectionReestablishmentComplete msg. Query_6. Query_5. RRCConnectionReestablishment b. RRCConnectionReestablishmentRequest and. What happens when RRCConnectionReestablishment is received by the UE?  stop timer T301 (This timer is started when UE sends the RRCConnectionReestabilshmentRequest)  re-establish PDCP for SRB1  re-establish RLC for SRB1  perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated  resume SRB1  generate security keys as specified by nextHopChainingCount IE  submit the RRCConnectionReestablishmentComplete message to lower layers for transmission Important Points:  eNB should not transmit any message on SRB1 prior to receiving the RRCConnectionReestablishmentComplete message  UE shall configure lower layers to activate ciphering and integrity protection. Random Access procedure will be triggered to send the RRCConnectionReestablishmentRequest message. Note that the contention resolution of the RA procedure will be PDCCH order based on C-RNTI.

e. Upon expiry of this constant. upon receiving N310 consecutive out-of-sync indications from lower layers)  upon random access problem indication from MAC while neither T300. UE will stop T310 2. (click here to know about the RRC CONNECTION RE-ESTABLISHMENT procedure in detail)  if AS security has not been activated then inform upper layers about the release of RRC connection with release cause 'other' In-sync Indications (N311) received: 1. it starts a timer 304. With this duration of the timer if the procedure is not completed then Mobility from E-UTRA procedure is considered to be failed  if the UE does not succeed in establishing the connection to the target RAT as . T301. upon receiving N310 consecutive out-of-sync indications from lower layers T311 Upon initiating the RRC connection re-establishment procedure N310 (constant) Maximum number of consecutive "out-of-sync" indications received from lower layers N311 (constant) Maximum number of consecutive "in-sync" indications received from lower layers Mobility from E-UTRA failure Triggering points of Mobility from EUTRA failure:  When the UE receives MobilityFromEUTRAcommand message. UE will UE maintains the entire radio resource configuration Timers and constants used in RLF: T301 Transmission of RRCConnectionReestabilshmentRequest T310 Upon detecting physical layer problems i. UE won't go for RLF. UE maintains the RRC connection (no configurations are changed) N311 is triggered when in-sync indications are received. upon indication from RLC that the maximum number of re transmissions has been reached  upon expiry of Timer T310 (this timer is started when physical layer problems are detected i. T304 nor T311 is running Actions when RLF is detected  UE shall initiate RRC Connection Re-establishment procedure.e. Once when the condition of N311 is fulfilled.

mentioned in the MobilityFromEUTRAcommand message then Mobility from EUTRA procedure is considered to be failed  if the UE is unable to comply with (part of) the configuration included in the MobilityFromEUTRACommand message then MobilityFromEUTRACommand procedure is considered to be failed  if there is a protocol error in the inter RAT information included in the MobilityFromEUTRACommand message. (To know more about MobilityFromEUTRAcommand click here). if running  if the cs-FallbackIndicator in the MobilityFromEUTRACommand message was set to 'TRUE' then indicate to UE upper layers that the CS Fallback procedure has failed  UE will re-configure itself with that of the prior configuration as used in the source cell. It includes system information. This procedure is needed during:  Handover (the MobilityFromEUTRACommand message includes radio resources that have been allocated for the UE in the target cell)  Cell Change Order (the MobilityFromEUTRACommand message includes information for accessing Connection Establishment in the target cell. causing the UE to fail the procedure according to the specifications applicable for the target RAT then MobilityFromEUTRACommand procedure is considered to be failed All together. Mobility from EUTRA failure is the residual effect of the failure condition of MobilityFromEUTRAcommand message. Actions when Mobility from EUTRA failure occurs:  UE will stop T304. Cell change order is applicable only to GERAN)  CS fallback to CDMA2000 1xRTT (the MobilityFromEUTRACommand message includes radio resources that have been allocated for the UE in the target cell) Query_2: When MobilityFromEUTRACommand is initiated? eNB initiates this procedure when: . mac-MainConfig and sps-Config  UE will initiate the connection re-establishment procedure (click here to know about the RRC CONNECTION RE-ESTABLISHMENT procedure in detail) Query_1: Why MobilityFromEUTRACommand is needed? When a UE is in RRC_Connected state and the UE needs to move to a different RAT (UTRA/GERAN/CDMA2000) then eNB triggers this procedure. excluding the configuration configured by the physicalConfigDedicated.

CS fallback to CDMA system c. Cell Change Order (for GERAN cell) b. Handover (to GERAN or UTRAN) When this message is received by the UE. and in response to the following messages: <!--[if !supportLists]-->§ <!--[endif]-->MeasurementReport message <!--[if !supportLists]-->§ <!--[endif]-->reception of CS fallback indication for the UE from MME provided. if the targetRAT-Type is set to 'cdma2000-1XRTT' or 'cdma2000-HRPD' then:  forward the targetRAT-Type and the targetRAT-MessageContainer to CDMA2000 upper layers for the UE to access the cell as indicated in the inter-RAT message => if the MobilityFromEUTRACommand message includes the purpose set to 'cellChangeOrder':  start timer T304 with the value as received from MobilityFromEUTRACommand message  if the targetRAT-Type is set to 'geran' then acquire networkControlOrder and apply the value (in case this IE is not part of the MobilityFromEUTRACommand message) .= UE's in RRC Connected state. if the targetRAT-Type is set to 'geran' then:  use the contents of systemInformation IE to begin access to the target GERAN cell  UE will not indicate the release of the concerned DRBs to the upper layers if there are DRBs for which no radio bearers are established in the target RAT b. it shall: => stop timer T310 if it is running -T310 is started when UE detects physical layer problems=> if the MobilityFromEUTRACommand message includes the purpose set to 'handover' and the targetRAT-Type is set to 'utra' or 'geran' then:  UE will start accessing the respective RAT as mentioned in the targetRATType IE  forward the nas-SecurityParamFromEUTRA to the upper layers a. = AS Security is activated (if Security is not avtivated then eNB will not trigger this procedure) = SRB2 is established with atleast one DRB is setup and not suspended Query_3: What happens when MobilityFromEUTRACommand message is received by UE? The MobilityFromEUTRACommand message can carry the following information: a.

measurements.. There are couple of scenarios where the UE can behave in a different way and are stated below:  if the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration message then roll back to the previous configurations  if security has not been activated and UE receives RRCConnectionReconfiguration message then proceed to release the RRC Connection with release cause 'other' . use the contents of systemInformation to access and establish the connection to the target cell indicated in the CellChangeOrder => if the MobilityFromEUTRACommand message includes the purpose set to 'e-CSFB' then forward the message to the CDMA2000 upper layers Query_4: What happens when MobilityFromEUTRACommand message fails? When MobilityFromEUTRACommand fails. click here) Important Points to use:   When Mobility form UTRA/GERAN is received at UE and UE is attached to the LTE network and UE supports UTRA/GERAN then:  the message contents of the Mobility from UTRA is validated at UE RRC layer and then is passed to the other respective RAT to process the HO message  LTE PS shall deactivate the UE c-RNTI and will change it's master-ship to SLAVE mode. mobility. thereby giving the control to respective UTRA/GERAN If the CDMA2000 upper layers in the UE receive both the messageContCDMA2000-1XRTT and messageContCDMA2000-HRPD then the UE performs concurrent access to both CDMA2000 1xRTT and CDMA2000 HRPD RAT RRC connection Re-configuration Failure Triggering points of Re-configuration Failure The UE receiving RRC Connection Reconfiguration message -with any related action. If these conditions are not met then UE will trigger Reestablishment Procedure. UE shall initiate the MobilityFromEUTRAFailure procedure. for e.x. (To know about the MobilityFromEUTRA failure procedure.will validate a set of necessary conditions. physical config. radio config etc.

e. upon which the connection reconfiguration procedure ends (click here to know about the RRC CONNECTION RE-ESTABLISHMENT procedure in detail) Important Points:  If the UE is unable to comply with part of the configuration. it does not apply any part of the configuration. i.or else:  initiate the connection Re-establishment procedure. there is no partial success/ failure .