Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 38.331  Word version:  17.6.0

Top   Top   Up   Prev   Next
1…   4…   5…   5.2.2.4…   5.3…   5.3.3…   5.3.5…   5.3.5.5…   5.3.5.6…   5.3.5.7…   5.3.5.13…   5.3.6…   5.3.8…   5.3.13…   5.3.14…   5.4…   5.5…   5.5.3…   5.5.4…   5.5.5…   5.5a…   5.7…   5.7.4…   5.7.8…   5.8…   5.8.9…   5.8.10…   5.8.11…   5.9…   6…   6.2.2…   6-2-2-25…   6.3…   6.3.2…   6-3-2-27…   6-3-2-49…   6-3-2-73…   6-3-2-95…   6-3-2-108…   6-3-2-134…   6-3-2-162…   6-3-2-188…   6-3-2-213…   6-3-2-243…   6-3-2-271…   6-3-2-297…   6.3.3…   6-3-3-25…   6-3-3-51…   6.3.4…   6.3.5…   6-3-5-25…   6.3.6…   6.4…   7…   9…   11…   A…   A.4…   B… 
5.3.8 RRC connection release  5.3.8.1 General  5.3.8.2 Initiation  5.3.8.3 Reception of the RRCRelease by the UE  5.3.8.4 T320 expiry  5.3.8.5 UE actions upon the expiry of DataInactivityTimer  5.3.8.6 T346g expiry  5.3.9 RRC connection release requested by upper layers  5.3.9.1 General  5.3.9.2 Initiation  5.3.10 Radio link failure related actions  5.3.10.1 Detection of physical layer problems in RRC_CONNECTED  5.3.10.2 Recovery of physical layer problems  5.3.10.3 Detection of radio link failure  5.3.10.4 RLF cause determination  5.3.10.5 RLF report content determination  5.3.11 UE actions upon going to RRC_IDLE  5.3.12 UE actions upon PUCCH/SRS release request 
...

 

5.3.8  RRC connection release  p. 137

5.3.8.1  General  p. 137

Reproduction of 3GPP TS 38.331, Fig. 5.3.8.1-1: RRC connection release, successful
Figure 5.3.8.1-1: RRC connection release, successful
Up
The purpose of this procedure is:
  • to release the RRC connection, which includes the release of the established radio bearers (except for broadcast MRBs), BH RLC channels, Uu Relay RLC channels, PC5 Relay RLC channels as well as all radio resources; or
  • to suspend the RRC connection only if SRB2 and at least one DRB or multicast MRB or, for IAB, SRB2, are setup, which includes the suspension of the established radio bearers (except for broadcast MRBs).

5.3.8.2  Initiation  p. 137

The network initiates the RRC connection release procedure to transit a UE in RRC_CONNECTED to RRC_IDLE; or to transit a UE in RRC_CONNECTED to RRC_INACTIVE only if SRB2 and at least one DRB or multicast MRB or, for IAB, SRB2, is setup in RRC_CONNECTED; or to transit a UE in RRC_INACTIVE back to RRC_INACTIVE when the UE tries to resume (for resuming a suspended RRC connection or for initiating SDT); or to transit a UE in RRC_INACTIVE to RRC_IDLE when the UE tries to resume (for resuming of a suspended RRC connection or for initiating SDT). The procedure can also be used to release and redirect a UE to another frequency.
Up

5.3.8.3  Reception of the RRCRelease by the UE  p. 137

The UE shall:
1 >
delay the following actions defined in this clause, 60 ms from the moment the RRCRelease message was received or optionally when lower layers indicate that the receipt of the RRCRelease message has been successfully acknowledged, whichever is earlier;
1 >
stop timer T380, if running;
1 >
stop timer T320, if running;
1 >
if timer T316 is running;
2 >
stop timer T316;
2 >
clear the information included in VarRLF-Report, if any;
1 >
stop timer T350, if running;
1 >
stop timer T346g, if running;
1 >
if the AS security is not activated:
2 >
ignore any field included in RRCRelease message except waitTime;
2 >
perform the actions upon going to RRC_IDLE as specified in clause 5.3.11 with the release cause 'other' upon which the procedure ends;
1 >
if the RRCRelease message includes redirectedCarrierInfo indicating redirection to eutra:
2 >
if cnType is included:
3 >
after the cell selection, indicate the available CN Type(s) and the received cnType to upper layers;
2 >
if voiceFallbackIndication is included:
3 >
consider the RRC connection release was for EPS fallback for IMS voice (see TS 23.502);
1 >
if the RRCRelease message includes the cellReselectionPriorities:
2 >
store the cell reselection priority information provided by the cellReselectionPriorities;
2 >
if the t320 is included:
3 >
start timer T320, with the timer value set according to the value of t320;
1 >
else:
2 >
apply the cell reselection priority information broadcast in the system information;
1 >
if deprioritisationReq is included and the UE supports RRC connection release with deprioritisation:
2 >
start or restart timer T325 with the timer value set to the deprioritisationTimer signalled;
2 >
store the deprioritisationReq until T325 expiry;
1 >
if the RRCRelease includes the measIdleConfig:
2 >
if T331 is running:
3 >
stop timer T331;
3 >
perform the actions as specified in clause 5.7.8.3;
2 >
if the measIdleConfig is set to setup:
3 >
store the received measIdleDuration in VarMeasIdleConfig;
3 >
start timer T331 with the value set to measIdleDuration;
3 >
if the measIdleConfig contains measIdleCarrierListNR:
4 >
store the received measIdleCarrierListNR in VarMeasIdleConfig;
3 >
if the measIdleConfig contains measIdleCarrierListEUTRA:
4 >
store the received measIdleCarrierListEUTRA in VarMeasIdleConfig;
3 >
if the measIdleConfig contains validityAreaList:
4 >
store the received validityAreaList in VarMeasIdleConfig;
1 >
if the RRCRelease includes suspendConfig:
2 >
reset MAC and release the default MAC Cell Group configuration, if any;
2 >
apply the received suspendConfig except the received nextHopChainingCount;
2 >
if the sdt-Config is configured:
3 >
for each of the DRB in the sdt-DRB-List:
4 >
consider the DRB to be configured for SDT;
3 >
if sdt-SRB2-Indication is configured:
4 >
consider the SRB2 to be configured for SDT;
3 >
for each RLC bearer (except those associated with broadcast MRBs) that is not suspended:
4 >
re-establish the RLC entity as specified in TS 38.322;
3 >
for SRB2 (if it is resumed) and for SRB1:
4 >
trigger the PDCP entity to perform SDU discard as specified in TS 38.323;
3 >
if sdt-MAC-PHY-CG-Config is configured:
4 >
configure the PCell with the configured grant resources for SDT and instruct the MAC entity to start the cg-SDT-TimeAlignmentTimer;
2 >
if srs-PosRRC-Inactive is configured:
3 >
apply the configuration and instruct MAC to start the inactivePosSRS-TimeAlignmentTimer;
2 >
remove all the entries within the MCG and the SCG VarConditionalReconfig, if any;
2 >
for each measId of the MCG measConfig and for each measId of the SCG measConfig, if configured, if the associated reportConfig has a reportType set to condTriggerConfig:
3 >
for the associated reportConfigId:
4 >
remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;
3 >
if the associated measObjectId is only associated to a reportConfig with reportType set to condTriggerConfig:
4 >
remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;
3 >
remove the entry with the matching measId from the measIdList within the VarMeasConfig;
2 >
if the UE is acting as L2 U2N Remote UE:
3 >
if the PC5-RRC connection with the U2N Relay UE is determined to be released:
4 >
indicate upper layers to trigger PC5 unicast link release;
3 >
else (i.e., maintain the PC5 RRC connection):
4 >
establish or re-establish (e.g. via release and add) SL RLC entity for SRB1;
2 >
else:
3 >
re-establish RLC entities for SRB1;
2 >
if the RRCRelease message with suspendConfig was received in response to an RRCResumeRequest or an RRCResumeRequest1:
3 >
stop the timer T319 if running;
3 >
in the stored UE Inactive AS context:
4 >
replace the KgNB and KRRCint keys with the current KgNB and KRRCint keys;
4 >
replace the nextHopChainingCount with the value of nextHopChainingCount received in the RRCRelease message;
4 >
replace the cellIdentity with the cellIdentity of the cell the UE has received the RRCRelease message;
4 >
if the suspendConfig contains the sl-UEIdentityRemote (i.e. the UE is a L2 U2N Remote UE):
5 >
replace the C-RNTI with the value of the sl-UEIdentityRemote;
5 >
replace the physical cell identity with the value of the sl-PhysCellId in sl-ServingCellInfo contained in the discovery message received from the connected L2 U2N Relay UE;
4 >
else:
5 >
replace the C-RNTI with the C-RNTI used in the cell (see TS 38.321) the UE has received the RRCRelease message;
5 >
replace the physical cell identity with the physical cell identity of the cell the UE has received the RRCRelease message;
3 >
replace the nextHopChainingCount with the value associated with the current KgNB;
3 >
stop the timer T319a if running and consider SDT procedure is not ongoing;
2 >
else:
3 >
store in the UE Inactive AS Context the nextHopChainingCount received in the RRCRelease message, the current KgNB and KRRCint keys, the ROHC state, the EHC context(s), the UDC state, the stored QoS flow to DRB mapping rules, the application layer measurement configuration, the C-RNTI used in the source PCell, the cellIdentity and the physical cell identity of the source PCell, the spCellConfigCommon within ReconfigurationWithSync of the NR PSCell (if configured) and all other parameters configured except for:
  • parameters within ReconfigurationWithSync of the PCell;
  • parameters within ReconfigurationWithSync of the NR PSCell, if configured;
  • parameters within MobilityControlInfoSCG of the E-UTRA PSCell, if configured;
  • servingCellConfigCommonSIB;
  • sl-L2RelayUE-Config, if configured;
  • sl-L2RemoteUE-Config, if configured;
3 >
store any previously or subsequently received application layer measurement report containers for which no segment, or full message, has been submitted to lower layers for transmission;
2 >
suspend all SRB(s) and DRB(s) and multicast MRB(s), except SRB0 and broadcast MRBs;
2 >
indicate PDCP suspend to lower layers of all DRBs and multicast MRBs;
2 >
release Uu Relay RLC channel(s), if configured;
2 >
release PC5 Relay RLC channel(s), if configured;
2 >
release the SRAP entity, if configured;
2 >
if the t380 is included:
3 >
start timer T380, with the timer value set to t380;
2 >
if the RRCRelease message is including the waitTime:
3 >
start timer T302 with the value set to the waitTime;
3 >
inform upper layers that access barring is applicable for all access categories except categories '0' and '2';
2 >
if T390 is running:
3 >
stop timer T390 for all access categories;
3 >
perform the actions as specified in clause 5.3.14.4;
2 >
indicate the suspension of the RRC connection to upper layers;
2 >
if the UE is capable of L2 U2N Remote UE:
3 >
enter RRC_INACTIVE, and perform either cell selection as specified in TS 38.304, or relay selection as specified in clause 5.8.15.3, or both;
2 >
else:
3 >
enter RRC_INACTIVE and perform cell selection as specified in TS 38.304;
1 >
else:
2 >
perform the actions upon going to RRC_IDLE as specified in clause 5.3.11, with the release cause 'other'.
Up

5.3.8.4  T320 expiry  p. 141

The UE shall:
1 >
if T320 expires:
2 >
if stored, discard the cell reselection priority information provided by the cellReselectionPriorities or inherited from another RAT;
2 >
apply the cell reselection priority information broadcast in the system information.

5.3.8.5  UE actions upon the expiry of DataInactivityTimer  p. 141

Upon receiving the expiry of DataInactivityTimer from lower layers while in RRC_CONNECTED, the UE shall:
1 >
perform the actions upon going to RRC_IDLE as specified in clause 5.3.11, with release cause 'RRC connection failure'.

5.3.8.6  T346g expiry  p. 141

The UE shall:
1 >
if T346g expires:
2 >
perform the actions upon going to RRC_IDLE as specified in clause 5.3.11, with release cause 'other'.

5.3.9  RRC connection release requested by upper layers  p. 141

5.3.9.1  General  p. 141

The purpose of this procedure is to release the RRC connection. Access to the current PCell may be barred as a result of this procedure.

5.3.9.2  Initiation  p. 141

The UE initiates the procedure when upper layers request the release of the RRC connection as specified in TS 24.501. The UE shall not initiate the procedure for power saving purposes.
The UE shall:
1 >
if the upper layers indicate barring of the PCell:
2 >
treat the PCell used prior to entering RRC_IDLE as barred according to TS 38.304;
1 >
perform the actions upon going to RRC_IDLE as specified in clause 5.3.11, with release cause 'other'.
Up

5.3.10  Radio link failure related actions  p. 142

5.3.10.1  Detection of physical layer problems in RRC_CONNECTED  p. 142

The UE shall:
1 >
if any DAPS bearer is configured, upon receiving N310 consecutive "out-of-sync" indications for the source SpCell from lower layers and T304 is running:
2 >
start timer T310 for the source SpCell.
1 >
upon receiving N310 consecutive "out-of-sync" indications for the SpCell from lower layers while neither T300, T301, T304, T311, T316 nor T319 are running:
2 >
start timer T310 for the corresponding SpCell.

5.3.10.2  Recovery of physical layer problems  p. 142

Upon receiving N311 consecutive "in-sync" indications for the SpCell from lower layers while T310 is running, the UE shall:
1 >
stop timer T310 for the corresponding SpCell.
1 >
stop timer T312 for the corresponding SpCell, if running.
Up

5.3.10.3  Detection of radio link failure  p. 142

The UE shall:
1 >
if any DAPS bearer is configured and T304 is running:
2 >
upon T310 expiry in source SpCell; or
2 >
upon random access problem indication from source MCG MAC; or
2 >
upon indication from source MCG RLC that the maximum number of retransmissions has been reached; or
2 >
upon consistent uplink LBT failure indication from source MCG MAC:
3 >
consider radio link failure to be detected for the source MCG i.e. source RLF;
3 >
suspend the transmission and reception of all DRBs and multicast MRBs in the source MCG;
3 >
reset MAC for the source MCG;
3 >
release the source connection.
1 >
else:
2 >
during a DAPS handover: the following only applies for the target PCell;
2 >
upon T310 expiry in PCell; or
2 >
upon T312 expiry in PCell; or
2 >
upon random access problem indication from MCG MAC while neither T300, T301, T304, T311 nor T319 are running and SDT procedure is not ongoing; or
2 >
upon indication from MCG RLC that the maximum number of retransmissions has been reached while SDT procedure is not ongoing; or
2 >
if connected as an IAB-node, upon BH RLF indication received on BAP entity from the MCG; or
2 >
upon consistent uplink LBT failure indication from MCG MAC while T304 is not running:
3 >
if the indication is from MCG RLC and CA duplication is configured and activated for MCG, and for the corresponding logical channel allowedServingCells only includes SCell(s):
4 >
initiate the failure information procedure as specified in clause 5.7.5 to report RLC failure.
3 >
else:
4 >
consider radio link failure to be detected for the MCG, i.e. MCG RLF;
4 >
discard any segments of segmented RRC messages stored according to clause 5.7.6.3;
4 >
if AS security has not been activated:
5 >
perform the actions upon going to RRC_IDLE as specified in clause 5.3.11, with release cause 'other';-
4 >
else if AS security has been activated but SRB2 and at least one DRB or multicast MRB or, for IAB, SRB2, have not been setup:
5 >
store the radio link failure information in the VarRLF-Report as described in clause 5.3.10.5;
5 >
perform the actions upon going to RRC_IDLE as specified in clause 5.3.11, with release cause 'RRC connection failure';
4 >
else:
5 >
store the radio link failure information in the VarRLF-Report as described in clause 5.3.10.5;
5 >
if T316 is configured; and
5 >
if SCG transmission is not suspended; and
5 >
if the SCG is not deactivated; and
5 >
if neither PSCell change nor PSCell addition is ongoing (i.e. timer T304 for the NR PSCell is not running in case of NR-DC or timer T307 of the E-UTRA PSCell is not running as specified in clause 5.3.10.10 of TS 36.331, in NE-DC):
6 >
initiate the MCG failure information procedure as specified in clause 5.7.3b to report MCG radio link failure.
5 >
else:
6 >
initiate the connection re-establishment procedure as specified in clause 5.3.7.
A L2/L3 U2N Relay UE shall:
1 >
upon detecting radio link failure:
2 >
either indicate to upper layers (to trigger PC5 unicast link release) or send NotificationMessageSidelink to the connected L2/L3 U2N Remote UE(s) in accordance with clause 5.8.9.10.
The UE shall:
1 >
upon T310 expiry in PSCell; or
1 >
upon T312 expiry in PSCell; or
1 >
upon random access problem indication from SCG MAC; or
1 >
upon indication from SCG RLC that the maximum number of retransmissions has been reached; or
1 >
if connected as an IAB-node, upon BH RLF indication received on BAP entity from the SCG; or
1 >
upon consistent uplink LBT failure indication from SCG MAC:
2 >
if the indication is from SCG RLC and CA duplication is configured and activated for SCG, and for the corresponding logical channel allowedServingCells only includes SCell(s):
3 >
initiate the failure information procedure as specified in clause 5.7.5 to report RLC failure.
2 >
else:
3 >
consider radio link failure to be detected for the SCG, i.e. SCG RLF;
3 >
if the SCG is deactivated:
4 >
stop radio link monitoring on the SCG;
4 >
indicate to lower layers to stop beam failure detection on the PSCell;
3 >
if MCG transmission is not suspended:
4 >
initiate the SCG failure information procedure as specified in clause 5.7.3 to report SCG radio link failure.
3 >
else:
4 >
if the UE is in NR-DC:
5 >
initiate the connection re-establishment procedure as specified in clause 5.3.7;
4 >
else (the UE is in (NG)EN-DC):
5 >
initiate the connection re-establishment procedure as specified in clause 5.3.7 of TS 36.331;
Up

5.3.10.4  RLF cause determination  p. 144

The UE shall set the rlf-Cause in the VarRLF-Report as follows:
1 >
if the UE declares radio link failure due to T310 expiry:
2 >
set the rlf-Cause as t310-Expiry;
1 >
else if the UE declares radio link failure due to the random access problem indication from MCG MAC:
2 >
if the random access procedure was initiated for beam failure recovery:
3 >
set the rlf-Cause as beamFailureRecoveryFailure;
2 >
else:
3 >
set the rlf-Cause as randomAccessProblem;
1 >
else if the UE declares radio link failure due to the reaching of maximum number of retransmissions from the MCG RLC:
2 >
set the rlf-Cause as rlc-MaxNumRetx;
1 >
else if the UE declares radio link failure due to consistent uplink LBT failures:
2 >
set the rlf-Cause as lbtFailure;
1 >
else if the IAB-MT declares radio link failure due to the reception of a BH RLF indication on BAP entity:
2 >
set the rlf-Cause as bh-rlfRecoveryFailure.
1 >
else if the UE declares radio link failure due to T312 expiry:
2 >
set the rlf-Cause as t312-Expiry;
Up

5.3.10.5  RLF report content determination  p. 145

The UE shall determine the content in the VarRLF-Report as follows:
1 >
clear the information included in VarRLF-Report, if any;
1 >
set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN);
1 >
set the measResultLastServCell to include the cell level RSRP, RSRQ and the available SINR, of the source PCell (in case HO failure) or PCell (in case RLF) based on the available SSB and CSI-RS measurements collected up to the moment the UE detected failure;
1 >
if the SS/PBCH block-based measurement quantities are available:
2 >
set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest SS/PBCH block RSRP is listed first if SS/PBCH block RSRP measurement results are available, otherwise the highest SS/PBCH block RSRQ is listed first if SS/PBCH block RSRQ measurement results are available, otherwise the highest SS/PBCH block SINR is listed first, based on the available SS/PBCH block based measurements collected up to the moment the UE detected failure;
1 >
if the CSI-RS based measurement quantities are available:
2 >
set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected failure;
1 >
set the ssbRLMConfigBitmap and/or csi-rsRLMConfigBitmap in measResultLastServCell to include the radio link monitoring configuration of the source PCell (in case HO failure) or PCell (in case RLF), if available;
1 >
for each of the configured measObjectNR in which measurements are available:
2 >
if the SS/PBCH block-based measurement quantities are available:
3 >
set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest SS/PBCH block RSRP is listed first if SS/PBCH block RSRP measurement results are available, otherwise the cell with highest SS/PBCH block RSRQ is listed first if SS/PBCH block RSRQ measurement results are available, otherwise the cell with highest SS/PBCH block SINR is listed first, based on the available SS/PBCH block based measurements collected up to the moment the UE detected failure;
4 >
for each neighbour cell included, include the optional fields that are available;
2 >
if the CSI-RS based measurement quantities are available:
3 >
set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected radio link failure;
4 >
for each neighbour cell included, include the optional fields that are available;
2 >
for each neighbour cell, if any, included in measResultListNR in measResultNeighCells:
3 >
if the UE supports RLF-Report for conditional handover and if the neighbour cell is one of the candidate cells for which the reconfigurationWithSync is included in the masterCellGroup in the MCG VarConditionalReconfig at the moment of the detected failure:
4 >
set choConfig in MeasResult2NR to the execution condition for each measId within condTriggerConfig associated to the neighbour cell within the MCG VarConditionalReconfig;
4 >
if the first entry of choConfig corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure; or
4 >
if the second entry of choConfig, if available, corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure:
5 >
set firstTriggeredEvent to the execution condition condFirstEvent corresponding to the first entry of choConfig or to the execution condition condSecondEvent corresponding to the second entry of choConfig, whichever execution condition was fulfilled first in time;
5 >
set timeBetweenEvents to the elapsed time between the point in time of fullfilling the condition in choConfig that was fulfilled first in time, and the point in time of fullfilling the condition in choConfig that was fulfilled second in time, if both the first execution condition corresponding to the first entry and the second execution condition corresponding to the second entry in the choConfig were fullfilled;
1 >
for each of the configured EUTRA frequencies in which measurements are available;
2 >
set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, and based on measurements collected up to the moment the UE detected failure;
3 >
for each neighbour cell included, include the optional fields that are available;
1 >
set the c-RNTI to the C-RNTI used in the source PCell (in case HO failure) or PCell (in case RLF);
1 >
if the failure is detected due to reconfiguration with sync failure as described in clause 5.3.5.8.3, set the fields in VarRLF-report as follows:
2 >
set the connectionFailureType to hof;
2 >
if the UE supports RLF-Report for DAPS handover and if any DAPS bearer was configured while T304 was running:
3 >
set lastHO-Type to daps;
3 >
if radio link failure was detected in the source PCell, according to clause 5.3.10.3:
4 >
set timeConnSourceDAPS-Failure to the time between the initiation of the DAPS handover execution and the radio link failure detected in the source PCell while T304 was running;
4 >
set the rlf-Cause to the trigger for detecting the source radio link failure in accordance with clause 5.3.10.4;
2 >
if the UE supports RLF-Report for conditional handover and if configuration of the conditional handover is available in the MCG VarConditionalReconfig at the moment of the handover failure:
3 >
if the UE executed a conditional handover toward target PCell according to the condRRCReconfig of the target PCell:
4 >
set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed conditional handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig of the target PCell of the failed conditional handover;
3 >
else:
4 >
set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig;
3 >
set choCandidateCellList to include the global cell identity, if available, and otherwise to the physical cell identity and carrier frequency of each of the candidate target cells for conditional handover included in condRRCReconfig within the MCG VarConditionalReconfig at the time of the failed handover, excluding the candidate target cells included in measResultNeighCells;
2 >
if the UE supports RLF-Report for conditional handover and if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover:
3 >
set lastHO-Type to cho;
2 >
set the nrFailedPCellId in failedPCellId to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;
2 >
include nrPreviousCell in previousPCellId and set it to the global cell identity and tracking area code of the PCell where the last RRCReconfiguration message including reconfigurationWithSync was received;
2 >
set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync;
1 >
else if the failure is detected due to Mobility from NR failure as described in clause 5.4.3.5, set the fields in VarRLF-report as follows:
2 >
set the connectionFailureType to hof;
2 >
if last MobilityFromNRCommand concerned a failed inter-RAT handover from NR to E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA (NR to EUTRA):
3 >
set the eutraFailedPCellId in failedPCellId to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;
2 >
include nrPreviousCell in previousPCellId and set it to the global cell identity and tracking area code of the PCell where the last MobilityFromNRCommand message was received;
2 >
set the timeConnFailure to the elapsed time since the initialization of the handover associated to the last MobilityFromNRCommand message;
1 >
else if the failure is detected due to radio link failure as described in clause 5.3.10.3, set the fields in VarRLF-report as follows:
2 >
set the connectionFailureType to rlf;
2 >
set the rlf-Cause to the trigger for detecting radio link failure in accordance with clause 5.3.10.4;
2 >
set the nrFailedPCellId in failedPCellId to the global cell identity and the tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the PCell where radio link failure is detected;
2 >
if an RRCReconfiguration message including the reconfigurationWithSync was received before the connection failure:
3 >
if the last successfully executed RRCReconfiguration message including the reconfigurationWithSync concerned an intra NR handover and it was received while connected to the previous PCell to which the UE was connected before connecting to the PCell where radio link failure is detected; and
3 >
if T311 was not running before entering the PCell in which the radio link failure was detected:
4 >
include the nrPreviousCell in previousPCellId and set it to the global cell identity and the tracking area code of the PCell where the last executed RRCReconfiguration message including reconfigurationWithSync was received;
4 >
if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a DAPS handover:
5 >
set lastHO-Type to daps;
4 >
else if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover:
5 >
set lastHO-Type to cho;
4 >
set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync;
3 >
else if the last RRCReconfiguration message including the reconfigurationWithSync concerned a handover to NR from E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA:
4 >
include the eutraPreviousCell in previousPCellId and set it to the global cell identity and the tracking area code of the E-UTRA PCell where the last RRCReconfiguration message including reconfigurationWithSync was received embedded in E-UTRA RRC message MobilityFromEUTRACommand message as specified in clause 5.4.3.3 of TS 36.331;
4 >
set the timeConnFailure to the elapsed time since reception of the last RRCReconfiguration message including the reconfigurationWithSync embedded in E-UTRA RRC message MobilityFromEUTRACommand message as specified in clause 5.4.3.3 of TS 36.331;
2 >
if configuration of the conditional handover is available in the MCG VarConditionalReconfig at the moment of declaring the radio link failure:
3 >
set timeSinceCHO-Reconfig to the time elapsed between the detection of the radio link failure, and the reception, in the source PCell, of the last conditionalReconfiguration including the condRRCReconfig message;
3 >
set choCandidateCellList to include the global cell identity if available, and otherwise to the physical cell identity and carrier frequency of each of all the candidate target cells for conditional handover included in condRRCReconfig within the MCG VarConditionalReconfig at the time of radio link failure, excluding the candidate target cells included in measResultNeighCells;
1 >
if connectionFailureType is rlf and the rlf-Cause is set to randomAccessProblem or beamFailureRecoveryFailure; or
1 >
if connectionFailureType is hof and if the failed handover is an intra-RAT handover:
2 >
set the ra-InformationCommon to include the random-access related information as described in clause 5.7.10.5;
1 >
if available, set the locationInfo as in clause 5.3.3.7.
The UE may discard the radio link failure information or handover failure information, i.e. release the UE variable VarRLF-Report, 48 hours after the radio link failure/handover failure is detected.
Up

5.3.11  UE actions upon going to RRC_IDLE  p. 148

The UE shall:
1 >
reset MAC;
1 >
set the variable pendingRNA-Update to false, if that is set to true;
1 >
if going to RRC_IDLE was triggered by reception of the RRCRelease message including a waitTime:
2 >
if T302 is running:
3 >
stop timer T302;
2 >
start timer T302 with the value set to the waitTime;
2 >
inform upper layers that access barring is applicable for all access categories except categories '0' and '2'.
1 >
else:
2 >
if T302 is running:
3 >
stop timer T302;
3 >
perform the actions as specified in clause 5.3.14.4;
1 >
if T390 is running:
2 >
stop timer T390 for all access categories;
2 >
perform the actions as specified in clause 5.3.14.4;
1 >
if the UE is leaving RRC_INACTIVE:
2 >
if going to RRC_IDLE was not triggered by reception of the RRCRelease message:
3 >
if stored, discard the cell reselection priority information provided by the cellReselectionPriorities;
3 >
stop the timer T320, if running;
2 >
if T319a is running:
3 >
stop timer T319a;
3 >
consider SDT procedure is not ongoing;
1 >
stop all timers that are running except T302, T320, T325, T330, T331, T400 and T430;
1 >
discard the UE Inactive AS context, if any;
1 >
release the suspendConfig, if configured;
1 >
remove all the entries within the MCG and the SCG VarConditionalReconfig, if any;
1 >
for each measId, if the associated reportConfig has a reportType set to condTriggerConfig:
2 >
for the associated reportConfigId:
3 >
remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;
2 >
if the associated measObjectId is only associated to a reportConfig with reportType set to condTriggerConfig:
3 >
remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;
2 >
remove the entry with the matching measId from the measIdList within the VarMeasConfig;
1 >
discard the KgNB key, the S-KgNB key, the S-KeNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key, if any;
1 >
release all radio resources, including release of the RLC entity, the BAP entity, the MAC configuration and the associated PDCP entity and SDAP for all established RBs (except for broadcast MRBs), BH RLC channels, Uu Relay RLC channels, PC5 Relay RLC channels and SRAP entity;
1 >
indicate the release of the RRC connection to upper layers together with the release cause;
1 >
inform upper layers about the release of all application layer measurement configurations;
1 >
discard any application layer measurement reports which were not yet submitted to lower layers for transmission;
1 >
discard any segments of segmented RRC messages stored according to clause 5.7.6.3;
1 >
except if going to RRC_IDLE was triggered by inter-RAT cell reselection while the UE is in RRC_INACTIVE or RRC_IDLE or when selecting an inter-RAT cell while T311 was running or when selecting an E-UTRA cell for EPS fallback for IMS voice as specified in clause 5.4.3.5:
2 >
if the UE is capable of L2 U2N Remote UE:
3 >
enter RRC_IDLE, and perform either cell selection as specified in TS 38.304, or relay selection as specified in clause 5.8.15.3, or both;
2 >
else:
3 >
enter RRC_IDLE and perform cell selection as specified in TS 38.304;
Up

5.3.12  UE actions upon PUCCH/SRS release request  p. 150

Upon receiving a PUCCH release request from lower layers, for all bandwidth parts of an indicated serving cell the UE shall:
1 >
release PUCCH-CSI-Resources configured in CSI-ReportConfig;
1 >
release SchedulingRequestResourceConfig instances configured in PUCCH-Config.
Upon receiving an SRS release request from lower layers, for all bandwidth parts of an indicated serving cell the UE shall:
1 >
release SRS-Resource instances configured in SRS-Config.
Upon receiving a positioning SRS configuration for RRC_INACTIVE release request from lower layers, the UE shall:
1 >
release the configured srs-PosRRC-Inactive.
Up

Up   Top   ToC