5.3.11 Radio link failure related actions

36.3313GPPEvolved Universal Terrestrial Radio Access (E-UTRA)Protocol specificationRadio Resource Control (RRC)Release 15TS

5.3.11.1 Detection of physical layer problems in RRC_CONNECTED

The UE shall:

1> upon receiving N310 consecutive "out-of-sync" indications for the PCell from lower layers while neither T300, T301, T304 nor T311 is running:

2> start timer T310;

1> upon receiving N313 consecutive "out-of-sync" indications for the PSCell from lower layers while T307 is not running:

2> start T313;

NOTE: Physical layer monitoring and related autonomous actions do not apply to SCells except for the PSCell.

5.3.11.1a Early detection of physical layer problems in RRC_CONNECTED

The UE shall:

1> upon receiving N310 consecutive "early-out-of-sync" indications for the PCell from lower layers:

2> start timer T314 with the timer value set to the value of T310;

5.3.11.1b Detection of physical layer improvements in RRC_CONNECTED

The UE shall:

1> upon receiving N311 consecutive "early-in-sync" indications for the PCell from lower layers:

2> start timer T315 with the timer value set to the value of T310;

5.3.11.2 Recovery of physical layer problems

Upon receiving N311 consecutive "in-sync" indications for the PCell from lower layers while T310 is running, the UE shall:

1> stop timer T310;

1> stop timer T312, if running;

NOTE 1: In this case, the UE maintains the RRC connection without explicit signalling, i.e. the UE maintains the entire radio resource configuration.

NOTE 2: Periods in time where neither "in-sync" nor "out-of-sync" is reported by layer 1 do not affect the evaluation of the number of consecutive "in-sync" or "out-of-sync" indications.

Upon receiving N314 consecutive "in-sync" indications for the PSCell from lower layers while T313 is running, the UE shall:

1> stop timer T313;

5.3.11.2a Recovery of early detection of physical layer problems

Upon receiving N311 consecutive "in-sync" indications for the PCell from lower layers while T314 is running, the UE shall:

1> stop timer T314;

5.3.11.2b Cancellation of physical layer improvements in RRC_CONNECTED

Upon receiving N311 consecutive "in-sync" indications for the PCell from lower layers while T315 is running, the UE shall:

1> stop timer T315;

5.3.11.3 Detection of radio link failure

The UE shall:

1> upon T310 expiry; or

1> upon T312 expiry; or

1> upon random access problem indication from MCG MAC while neither T300, T301, T304 nor T311 is running; or

1> upon indication from MCG RLC, which is allowed to be send on PCell, that the maximum number of retransmissions has been reached for an SRB or DRB:

2> consider radio link failure to be detected for the MCG i.e. RLF;

2> except for NB-IoT, store the following radio link failure information in the VarRLF-Report by setting its fields as follows:

3> clear the information included in VarRLF-Report, if any;

3> set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN);

3> set the measResultLastServCell to include the RSRP and RSRQ, if available, of the PCell based on measurements collected up to the moment the UE detected radio link failure;

3> set the measResultNeighCells to include the best measured cells, other than the PCell, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected radio link failure, and set its fields as follows;

4> if the UE was configured to perform measurements for one or more EUTRA frequencies, include the measResultListEUTRA;

4> if the UE was configured to perform measurement reporting for one or more neighbouring UTRA frequencies, include the measResultListUTRA;

4> if the UE was configured to perform measurement reporting for one or more neighbouring GERAN frequencies, include the measResultListGERAN;

4> if the UE was configured to perform measurement reporting for one or more neighbouring CDMA2000 frequencies, include the measResultsCDMA2000;

4> for each neighbour cell included, include the optional fields that are available;

NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Blacklisted cells are not required to be reported.

3> if available, set the logMeasResultListWLAN to include the WLAN measurement results, in order of decreasing RSSI for WLAN APs;

3> if available, set the logMeasResultListBT to include the Bluetooth measurement results, in order of decreasing RSSI for Bluetooth beacons;

3> if detailed location information is available, set the content of the locationInfo as follows:

4> include the locationCoordinates;

4> include the horizontalVelocity, if available;

3> set the failedPCellId to the global cell identity, if available, and otherwise to the physical cell identity and carrier frequency of the PCell where radio link failure is detected;

3> set the tac-FailedPCell to the tracking area code, if available, of the PCell where radio link failure is detected;

3> if an RRCConnectionReconfiguration message including the mobilityControlInfo was received before the connection failure:

4> if the last RRCConnectionReconfiguration message including the mobilityControlInfo concerned an intra E-UTRA handover:

5> include the previousPCellId and set it to the global cell identity of the PCell where the last RRCConnectionReconfiguration message including mobilityControlInfo was received;

5> set the timeConnFailure to the elapsed time since reception of the last RRCConnectionReconfiguration message including the mobilityControlInfo;

4> if the last RRCConnectionReconfiguration message including the mobilityControlInfo concerned a handover to E-UTRA from UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO:

5> include the previousUTRA-CellId and set it to the physical cell identity, the carrier frequency and the global cell identity, if available, of the UTRA Cell in which the last RRCConnectionReconfiguration message including mobilityControlInfo was received;

5> set the timeConnFailure to the elapsed time since reception of the last RRCConnectionReconfiguration message including the mobilityControlInfo;

3> if the UE supports QCI1 indication in Radio Link Failure Report and has a DRB for which QCI is 1:

4> include the drb-EstablishedWithQCI-1;

3> set the connectionFailureType to rlf;

3> set the c-RNTI to the C-RNTI used in the PCell;

3> set the rlf-Cause to the trigger for detecting radio link failure;

2> if AS security has not been activated:

3> if the UE is a NB-IoT UE:

4> if the UE supports RRC connection re-establishment for the Control Plane CIoT EPS optimisation:

5> initiate the RRC connection re-establishment procedure as specified in 5.3.7;

4> else:

5> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘RRC connection failure’;

3> else:

4> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’;

2> else:

3> initiate the connection re-establishment procedure as specified in 5.3.7;

In case of DC or NE-DC, the UE shall:

1> upon T313 expiry; or

1> upon random access problem indication from SCG MAC; or

1> upon indication from SCG RLC, which is allowed to be sent on PSCell, that the maximum number of retransmissions has been reached for an SCG, for a split DRB or for a split SRB:

2> consider radio link failure to be detected for the SCG i.e. SCG-RLF;

2> initiate the SCG failure information procedure as specified in 5.6.13 to report SCG radio link failure;

In case of CA PDCP duplication, the UE shall:

1> upon indication from an RLC entity, which is restricted to be sent on SCell only, that the maximum number of retransmissions has been reached:

2> initiate the failure information procedure as specified in 5.6.21 to report RLC failure of type duplication;

The UE may discard the radio link failure information, i.e. release the UE variable VarRLF-Report, 48 hours after the radio link failure is detected, upon power off or upon detach.

5.3.11.3a Detection of early-out-of-sync event

The UE shall:

1> upon T314 expiry;

2> consider "early-out-of-sync" event to be detected and initiate transmission of the UEAssistanceInformation message in accordance with 5.6.10;

5.3.11.3b Detection of early-in-sync event

The UE shall:

1> upon T315 expiry;

2> consider "early-in-sync" event to be detected and initiate transmission of the UEAssistanceInformation message in accordance with 5.6.10;