Content for TS 38.331 Word version: 18.2.0

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.5.17… 5.3.6… 5.3.8… 5.3.13… 5.3.14… 5.4… 5.5… 5.5.3… 5.5.4… 5.5.4.15… 5.5.4.23… 5.5.5… 5.5a… 5.7… 5.7.4… 5.7.8… 5.7.12… 5.8… 5.8.9… 5.8.9.2… 5.8.9.8… 5.8.10… 5.8.11… 5.9… 5.10… 6… 6.2.2… 6-2-2-23… 6-2-2-27… 6-2-2-43… 6-2-2-47… 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-2-341… 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.6 Counter check 5.3.6.1 General 5.3.6.2 Initiation 5.3.6.3 Reception of the CounterCheck message by the UE 5.3.7 RRC connection re-establishment 5.3.7.1 General 5.3.7.2 Initiation 5.3.7.3 Actions following cell selection while T311 is running 5.3.7.3a Actions following relay selection while T311 is running 5.3.7.4 Actions related to transmission of RRCReestablishmentRequest message 5.3.7.5 Reception of the RRCReestablishment by the UE 5.3.7.6 T311 expiry 5.3.7.7 T301 expiry or selected cell/L2 U2N Relay UE no longer suitable 5.3.7.8 Reception of the RRCSetup by the UE
...

5.3.6 Counter check p. 167

5.3.6.1 General p. 167

Reproduction of 3GPP TS 38.331, Fig. 5.3.6.1-1: Counter check procedure

Figure 5.3.6.1-1: Counter check procedure

The counter check procedure is used by the network to request the UE to verify the amount of data sent/ received on each DRB. More specifically, the UE is requested to check if, for each DRB, the most significant bits of the COUNT match with the values indicated by the network.

5.3.6.2 Initiation p. 167

The network initiates the procedure by sending a CounterCheck message.

5.3.6.3 Reception of the CounterCheck message by the UE p. 167

Upon receiving the CounterCheck message, the UE shall:

1 >

for each DRB that is established:

2 >

if no COUNT exists for a given direction (uplink or downlink) because it is a uni-directional bearer configured only for the other direction:

3 >

assume the COUNT value to be 0 for the unused direction;

2 >

if the drb-Identity is not included in the drb-CountMSB-InfoList:

3 >

include the DRB in the drb-CountInfoList in the CounterCheckResponse message by including the drb-Identity, the count-Uplink and the count-Downlink set to the value of TX_NEXT - 1 and RX_NEXT - 1 (specified in TS 38.323), respectively;

2 >

else if, for at least one direction, the most significant bits of the COUNT are different from the value indicated in the drb-CountMSB-InfoList:

3 >

1 >

for each DRB that is included in the drb-CountMSB-InfoList in the CounterCheck message that is not established:

2 >

include the DRB in the drb-CountInfoList in the CounterCheckResponse message by including the drb-Identity, the count-Uplink and the count-Downlink with the most significant bits set identical to the corresponding values in the drb-CountMSB-InfoList and the least significant bits set to zero;

1 >

submit the CounterCheckResponse message to lower layers for transmission upon which the procedure ends.

5.3.7 RRC connection re-establishment p. 168

5.3.7.1 General p. 168

Reproduction of 3GPP TS 38.331, Fig. 5.3.7.1-1: RRC connection re-establishment, successful

Figure 5.3.7.1-1: RRC connection re-establishment, successful

Reproduction of 3GPP TS 38.331, Fig. 5.3.7.1-2: RRC re-establishment, fallback to RRC establishment, successful

Figure 5.3.7.1-2: RRC re-establishment, fallback to RRC establishment, successful

The purpose of this procedure is to re-establish the RRC connection. A UE in RRC_CONNECTED, for which AS security has been activated with SRB2 and at least one DRB/multicast MRB setup or, for IAB and NCR, SRB2, may initiate the procedure in order to continue the RRC connection. The connection re-establishment succeeds if the network is able to find and verify a valid UE context or, if the UE context cannot be retrieved, and the network responds with an RRCSetup according to clause 5.3.3.4.

The network applies the procedure e.g as follows:

When AS security has been activated and the network retrieves or verifies the UE context:
- to re-activate AS security without changing algorithms;
- to re-establish and resume the SRB1;
When UE is re-establishing an RRC connection, and the network is not able to retrieve or verify the UE context:
- to discard the stored AS Context and release all RBs and BH RLC channels and Uu Relay RLC channels;
- to fallback to establish a new RRC connection.

If AS security has not been activated, the UE shall not initiate the procedure but instead moves to RRC_IDLE directly, with release cause 'other'. If AS security has been activated, but SRB2 and at least one DRB or multicast MRB or, for IAB and NCR, SRB2, are not setup, the UE does not initiate the procedure but instead moves to RRC_IDLE directly, with release cause 'RRC connection failure'.

5.3.7.2 Initiation p. 168

The UE initiates the procedure when one of the following conditions is met:

1 >

upon detecting radio link failure of the MCG and t316 is not configured, in accordance with clause 5.3.10; or

1 >

upon detecting radio link failure of the MCG while SCG transmission is suspended, in accordance with clause 5.3.10; or

1 >

upon detecting radio link failure of the MCG while PSCell change or PSCell addition is ongoing, in accordance with clause 5.3.10; or

1 >

upon detecting radio link failure of the MCG while the SCG is deactivated, in accordance with clause 5.3.10; or

1 >

upon re-configuration with sync failure of the MCG, in accordance with clause 5.3.5.8.3; or

1 >

upon mobility from NR failure, in accordance with clause 5.4.3.5; or

1 >

upon integrity check failure indication from lower layers concerning SRB1 or SRB2, except if the integrity check failure is detected on the RRCReestablishment message; or

1 >

upon an RRC connection reconfiguration failure, in accordance with clause 5.3.5.8.2; or

1 >

upon detecting radio link failure for the SCG while MCG transmission is suspended, in accordance with clause 5.3.10.3 in NR-DC or in accordance with clause 5.3.11.3 of TS 36.331 in NE-DC; or

1 >

upon reconfiguration with sync failure of the SCG while MCG transmission is suspended in accordance with clause 5.3.5.8.3; or

1 >

upon SCG change failure while MCG transmission is suspended in accordance with clause 5.3.5.7a of TS 36.331; or

1 >

upon SCG configuration failure while MCG transmission is suspended in accordance with clause 5.3.5.8.2 in NR-DC or in accordance with clause 5.3.5.5 of TS 36.331 in NE-DC; or

1 >

upon integrity check failure indication from SCG lower layers concerning SRB3 while MCG is suspended; or

1 >

upon T316 expiry, in accordance with clause 5.7.3b.5; or

1 >

upon detecting sidelink radio link failure by L2 U2N Remote UE in RRC_CONNECTED which is not configured with MP, in accordance with clause 5.8.9.3; or

1 >

upon reception of NotificationMessageSidelink including indicationType by L2 U2N Remote UE in RRC_CONNECTED which is not configured with MP, in accordance with clause 5.8.9.10; or

1 >

upon PC5 unicast link release for the serving L2 U2N Relay UE indicated by upper layer at L2 U2N Remote UE in RRC_CONNECTED which is not configured with MP while T301 is not running; or

1 >

if MP is configured, upon detecting radio link failure of the MCG (i.e. direct path) in accordance with clause 5.3.10 while the transmission of indirect path is suspended as specified in 5.3.5.17; or

1 >

if MP is configured, upon detecting sidelink radio link failure of SL indirect path by L2 U2N Remote UE, in accordance with clause 5.8.9.3, while MCG transmission (i.e. direct path) is suspended as specified in clause 5.7.3b; or

1 >

if MP is configured, upon reception of NotificationMessageSidelink including indicationType in accordance with clause 5.8.9.10, while MCG transmission (i.e. direct path) is suspended as specified in clause 5.7.3b; or

1 >

if MP is configured, upon PC5 unicast link release indicated by upper layer at L2 U2N Remote UE, while MCG transmission (i.e. direct path) is suspended as specified in clause 5.7.3b; or

1 >

if MP is configured, upon detecting the failure of N3C indirect path by N3C remote UE in accordance with clause 5.7.3c, while MCG transmission (i.e. direct path) is suspended.

Upon initiation of the procedure, the UE shall:

1 >

stop timer T310, if running;

1 >

stop timer T312, if running;

1 >

stop timer T304, if running;

1 >

start timer T311;

1 >

stop timer T316, if running;

1 >

if UE is not configured with attemptCondReconfig; and

1 >

if UE is not configured with attemptLTM-Switch:

2 >

reset MAC;

2 >

release spCellConfig, if configured;

2 >

suspend all RBs, and BH RLC channels for IAB-MT, and Uu Relay RLC channels for L2 U2N Relay UE, except SRB0 and broadcast MRBs;

2 >

release the MCG SCell(s), if configured;

2 >

if MR-DC is configured:

3 >

perform MR-DC release, as specified in clause 5.3.5.10;

2 >

perform the LTM configuration release procedure for the MCG and the SCG as specified in clause 5.3.5.18.7;

2 >

release delayBudgetReportingConfig, if configured and stop timer T342, if running;

2 >

release overheatingAssistanceConfig, if configured and stop timer T345, if running;

2 >

release idc-AssistanceConfig, if configured;

2 >

release btNameList, if configured;

2 >

release wlanNameList, if configured;

2 >

release sensorNameList, if configured;

2 >

release drx-PreferenceConfig for the MCG, if configured and stop timer T346a associated with the MCG, if running;

2 >

release maxBW-PreferenceConfig for the MCG, if configured and stop timer T346b associated with the MCG, if running;

2 >

release maxCC-PreferenceConfig for the MCG, if configured and stop timer T346c associated with the MCG, if running;

2 >

release maxMIMO-LayerPreferenceConfig for the MCG, if configured and stop timer T346d associated with the MCG, if running;

2 >

release minSchedulingOffsetPreferenceConfig for the MCG, if configured stop timer T346e associated with the MCG, if running;

2 >

release rlm-RelaxationReportingConfig for the MCG, if configured and stop timer T346j associated with the MCG, if running;

2 >

release bfd-RelaxationReportingConfig for the MCG, if configured and stop timer T346k associated with the MCG, if running;

2 >

release releasePreferenceConfig, if configured stop timer T346f, if running;

2 >

release onDemandSIB-Request if configured, and stop timer T350, if running;

2 >

release referenceTimePreferenceReporting, if configured;

2 >

release sl-AssistanceConfigNR, if configured;

2 >

release obtainCommonLocation, if configured;

2 >

release musim-GapAssistanceConfig, if configured and stop timer T346h, if running;

2 >

release musim-GapPriorityAssistanceConfig, if configured;

2 >

release musim-LeaveAssistanceConfig, if configured;

2 >

release musim-CapabilityRestrictionConfig, if configured and stop timer T346n, if running;

2 >

release ul-GapFR2-PreferenceConfig, if configured;

2 >

release scg-DeactivationPreferenceConfig, if configured, and stop timer T346i, if running;

2 >

release propDelayDiffReportConfig, if configured;

2 >

release rrm-MeasRelaxationReportingConfig, if configured;

2 >

release maxBW-PreferenceConfigFR2-2, if configured;

2 >

release maxMIMO-LayerPreferenceConfigFR2-2, if configured;

2 >

release minSchedulingOffsetPreferenceConfigExt, if configured;

2 >

release multiRx-PreferenceReportingConfigFR2, if configured, and stop timer T440, if running;

2 >

release uav-FlightPathAvailabilityConfig, if configured;

2 >

release ul-TrafficInfoReportingConfig, if configured, and stop all instances of timer T346x, if running;

1 >

release successHO-Config, if configured;

1 >

release successPSCell-Config configured by the PCell, if configured;

1 >

release successPSCell-Config configured by the PSCell, if configured;

1 >

if any DAPS bearer is configured:

2 >

reset the source MAC and release the source MAC configuration;

2 >

for each DAPS bearer:

3 >

release the RLC entity or entities as specified in clause 5.1.3 of TS 38.322, and the associated logical channel for the source SpCell;

3 >

reconfigure the PDCP entity to release DAPS as specified in TS 38.323;

2 >

for each SRB:

3 >

release the PDCP entity for the source SpCell;

3 >

release the RLC entity as specified in clause 5.1.3 of TS 38.322, and the associated logical channel for the source SpCell;

2 >

release the physical channel configuration for the source SpCell;

2 >

discard the keys used in the source SpCell (the KgNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key), if any;

1 >

release sl-L2RelayUE-Config, if configured;

1 >

release sl-L2RemoteUE-Config, if configured;

1 >

release the SRAP entity, if configured;

1 >

release NCR-FwdConfig, if configured;

1 >

if the UE is NCR-MT:

2 >

indicate to NCR-Fwd to cease forwarding;

1 >

if SL indirect path is configured:

2 >

release cell identity and relay UE ID configured in sl-IndirectPathAddChange;

2 >

indicate upper layers to trigger PC5 unicast link release of the SL indirect path;

1 >

if N3C indirect path is configured:

2 >

release n3c-IndirectPathAddChange;

2 >

consider the non-3GPP connection is not used;

1 >

if the UE is acting as a N3C relay UE:

2 >

release n3c-IndirectPathConfigRelay;

2 >

consider the non-3GPP connection is not used;

1 >

if the UE is acting as L2 U2N Remote UE and MP via L2 U2N Relay UE is not configured:

2 >

if the PC5-RRC connection with the U2N Relay UE is determined to be released:

3 >

indicate upper layers to trigger PC5 unicast link release;

3 >

perform either cell selection in accordance with the cell selection process as specified in TS 38.304, or relay selection as specified in clause 5.8.15.3, or both;

2 >

else (i.e., maintain the PC5 RRC connection):

3 >

consider the connected L2 U2N Relay UE as suitable and perform actions as specified in clause 5.3.7.3a;

1 >

else:

2 >

if the UE is capable of L2 U2N Remote UE:

3 >

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 >

perform cell selection in accordance with the cell selection process as specified in TS 38.304.

5.3.7.3 Actions following cell selection while T311 is running p. 172

Upon selecting a suitable NR cell, the UE shall:

1 >

ensure having valid and up to date essential system information as specified in clause 5.2.2.2;

1 >

stop timer T311;

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 >

stop the relay (re)selection procedure, if ongoing;

1 >

if the cell selection is triggered by detecting radio link failure of the MCG or re-configuration with sync failure of the MCG or mobility from NR failure, and

1 >

if attemptCondReconfig is configured; and

1 >

if the selected cell is not configured with CondEventT1, or the selected cell is configured with CondEventT1 and leaving condition has not been fulfilled; and

1 >

if the selected cell is one of the candidate cells for which the reconfigurationWithSync is included in the masterCellGroup in the MCG VarConditionalReconfig and the condExecutionCondPSCell is not configured for the corresponding condReconfigId in the MCG VarConditionalReconfig:

2 >

if the UE supports RLF-Report for conditional handover, set the choCellId in the VarRLF-Report to the global cell identity, if available, otherwise to the physical cell identity and carrier frequency of the selected cell;

2 >

apply the stored condRRCReconfig associated to the selected cell and perform actions as specified in clause 5.3.5.3;

1 >

if the cell selection is triggered by detecting radio link failure of the MCG or re-configuration with sync failure of the MCG or mobility from NR failure; and

1 >

if attemptLTM-Switch is configured; and

1 >

if the selected cell is one of the LTM candidate cells in the LTM-Candidate IE within VarLTM-Config associated with the MCG:

2 >

perform the LTM cell switch procedure for the selected LTM candidate cell according to the actions specified in clause 5.3.5.18.6;

1 >

else:

2 >

if UE is configured with attemptCondReconfig; or

2 >

if UE is configured with attemptLTM-Switch:

3 >

reset MAC;

3 >

release spCellConfig, if configured;

3 >

release the MCG SCell(s), if configured;

3 >

release delayBudgetReportingConfig, if configured and stop timer T342, if running;

3 >

release overheatingAssistanceConfig , if configured and stop timer T345, if running;

3 >

if MR-DC is configured:

4 >

perform MR-DC release, as specified in clause 5.3.5.10;

3 >

release idc-AssistanceConfig, if configured;

3 >

release btNameList, if configured;

3 >

release wlanNameList, if configured;

3 >

release sensorNameList, if configured;

3 >

release drx-PreferenceConfig for the MCG, if configured and stop timer T346a associated with the MCG, if running;

3 >

release maxBW-PreferenceConfig for the MCG, if configured and stop timer T346b associated with the MCG, if running;

3 >

release maxCC-PreferenceConfig for the MCG, if configured and stop timer T346c associated with the MCG, if running;

3 >

release maxMIMO-LayerPreferenceConfig for the MCG, if configured and stop timer T346d associated with the MCG, if running;

3 >

release minSchedulingOffsetPreferenceConfig for the MCG, if configured and stop timer T346e associated with the MCG, if running;

3 >

release rlm-RelaxationReportingConfig for the MCG, if configured and stop timer T346j associated with the MCG, if running;

3 >

release bfd-RelaxationReportingConfig for the MCG, if configured and stop timer T346k associated with the MCG, if running;

3 >

release releasePreferenceConfig, if configured and stop timer T346f, if running;

3 >

release onDemandSIB-Request if configured, and stop timer T350, if running;

3 >

release referenceTimePreferenceReporting, if configured;

3 >

release sl-AssistanceConfigNR, if configured;

3 >

release obtainCommonLocation, if configured;

3 >

release scg-DeactivationPreferenceConfig, if configured, and stop timer T346i, if running;

3 >

release musim-GapAssistanceConfig, if configured and stop timer T346h, if running;

3 >

release musim-GapPriorityAssistanceConfig, if configured;

3 >

release musim-LeaveAssistanceConfig, if configured;

3 >

release musim-CapabilityRestrictionConfig, if configured and stop timer T346n, if running;

3 >

release propDelayDiffReportConfig, if configured;

3 >

release ul-GapFR2-PreferenceConfig, if configured;

3 >

release rrm-MeasRelaxationReportingConfig, if configured;

3 >

release maxBW-PreferenceConfigFR2-2, if configured;

3 >

release maxMIMO-LayerPreferenceConfigFR2-2, if configured;

3 >

release minSchedulingOffsetPreferenceConfigExt, if configured;

3 >

release uav-FlightPathAvailabilityConfig, if configured;

3 >

release ul-TrafficInfoReportingConfig, if configured, and stop all instances of timer T346x, if running;

3 >

suspend all RBs, and BH RLC channels for the IAB-MT, except SRB0 and broadcast MRBs;

2 >

remove all the entries within the MCG VarConditionalReconfig, if any;

2 >

perform the LTM configuration release procedure for the MCG and the SCG as specified in clause 5.3.5.18.7;

2 >

for each measId, 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 >

remove the servingSecurityCellSetId within the VarServingSecurityCellSetID, if any;

2 >

release the PC5 RLC entity for SL-RLC0, if any;

2 >

start timer T301;

2 >

apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1;

2 >

apply the default MAC Cell Group configuration as specified in clause 9.2.2;

2 >

apply the CCCH configuration as specified in clause 9.1.1.2;

2 >

apply the timeAlignmentTimerCommon included in SIB1;

2 >

initiate transmission of the RRCReestablishmentRequest message in accordance with clause 5.3.7.4;

Upon selecting an inter-RAT cell, 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.7.3a Actions following relay selection while T311 is running p. 175

Upon selecting a suitable L2 U2N Relay UE, the L2 U2N Remote UE shall:

1 >

indicate to upper layer to trigger the PC5 unicast link establishment with the selected L2 U2N Relay UE, if a new L2 U2N Relay UE is selected;

1 >

ensure having valid and up to date essential system information as specified in clause 5.2.2.2;

1 >

stop timer T311;

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 >

stop the cell selection procedure, if ongoing;

1 >

start timer T301;

1 >

release the RLC entity for SRB0, if any;

1 >

establish a SRAP entity as specified in TS 38.351, if no SRAP entity has been established;

1 >

apply the specified configuration of SL-RLC0 as specified in clause 9.1.1.4;

1 >

apply the SDAP configuration and PDCP configuration as specified in clause 9.1.1.2 for SRB0;

1 >

initiate transmission of the RRCReestablishmentRequest message in accordance with clause 5.3.7.4.

5.3.7.4 Actions related to transmission of RRCReestablishmentRequest message p. 176

The UE shall set the contents of RRCReestablishmentRequest message as follows:

1 >

if the procedure was initiated due to radio link failure as specified in clause 5.3.10.3 or reconfiguration with sync failure as specified in clause 5.3.5.8.3; or

1 >

if the procedure was initiated due to mobility from NR failure as specified in clause 5.4.3.5 and if voiceFallbackIndication is included in the MobilityFromNRCommand message:

2 >

set the reestablishmentCellId in the VarRLF-Report to the global cell identity of the selected cell;

1 >

set the ue-Identity as follows:

2 >

set the c-RNTI to the C-RNTI used in the source PCell (reconfiguration with sync or mobility from NR failure) or used in the PCell in which the trigger for the re-establishment occurred (other cases);

2 >

set the physCellId to the physical cell identity of the source PCell (reconfiguration with sync or mobility from NR failure) or of the PCell in which the trigger for the re-establishment occurred (other cases);

2 >

set the shortMAC-I to the 16 least significant bits of the MAC-I calculated:

3 >

over the ASN.1 encoded as per clause 8 (i.e., a multiple of 8 bits) VarShortMAC-Input;

3 >

with the KRRCint key and integrity protection algorithm that was used in the source PCell (reconfiguration with sync or mobility from NR failure) or of the PCell in which the trigger for the re-establishment occurred (other cases); and

3 >

with all input bits for COUNT, BEARER and DIRECTION set to binary ones;

1 >

set the reestablishmentCause as follows:

2 >

if the re-establishment procedure was initiated due to reconfiguration failure as specified in clause 5.3.5.8.2:

3 >

set the reestablishmentCause to the value reconfigurationFailure;

2 >

else if the re-establishment procedure was initiated due to reconfiguration with sync failure as specified in clause 5.3.5.8.3 (intra-NR handover failure) or 5.4.3.5 (inter-RAT mobility from NR failure):

3 >

set the reestablishmentCause to the value handoverFailure;

2 >

else:

3 >

set the reestablishmentCause to the value otherFailure;

1 >

re-establish PDCP for SRB1;

1 >

if the UE is acting as L2 U2N Remote UE:

2 >

establish or re-establish (e.g. via release and add) SL RLC entity for SRB1;

2 >

apply the default configuration of SL-RLC1 as defined in clause 9.2.4 for SRB1;

2 >

apply the default configuration of PDCP as defined in clause 9.2.1 for SRB1;

2 >

apply the default configuration of SRAP as defined in clause 9.2.5 for SRB1;

1 >

else:

2 >

re-establish RLC for SRB1;

2 >

apply the default configuration defined in clause 9.2.1 for SRB1;

1 >

configure lower layers to suspend integrity protection and ciphering for SRB1;

1 >

resume SRB1;

1 >

if ta-Report or ta-ReportATG is configured with value enabled and the UE supports TA reporting:

2 >

indicate TA report initiation to lower layers;

1 >

submit the RRCReestablishmentRequest message to lower layers for transmission.

5.3.7.5 Reception of the RRCReestablishment by the UE p. 177

The UE shall:

1 >

stop timer T301;

1 >

consider the current cell to be the PCell;

1 >

update the KgNB key based on the current KgNB key or the NH, using the received nextHopChainingCount value, as specified in TS 33.501;

1 >

store the nextHopChainingCount value indicated in the RRCReestablishment message;

1 >

derive the KRRCenc and KUPenc keys associated with the previously configured cipheringAlgorithm, as specified in TS 33.501;

1 >

derive the KRRCint and KUPint keys associated with the previously configured integrityProtAlgorithm, as specified in TS 33.501.

1 >

request lower layers to verify the integrity protection of the RRCReestablishment message, using the previously configured algorithm and the KRRCint key;

1 >

if the integrity protection check of the RRCReestablishment message fails:

2 >

perform the actions upon going to RRC_IDLE as specified in clause 5.3.11, with release cause 'RRC connection failure', upon which the procedure ends;

1 >

configure lower layers to resume integrity protection for SRB1 using the previously configured algorithm and the KRRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1 >

configure lower layers to resume ciphering for SRB1 using the previously configured algorithm and, the KRRCenc key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1 >

release the measurement gap configuration indicated by the measGapConfig, if configured;

1 >

release the MUSIM gap configuration indicated by the musim-GapConfig, if configured;

1 >

release the FR2 UL gap configuration indicated by the ul-GapFR2-Config, if configured;

1 >

perform the L2 U2N Remote UE configuration procedure in accordance with the received sl-L2RemoteUE-Config as specified in clause 5.3.5.16;

1 >

set the content of RRCReestablishmentComplete message as follows:

2 >

if the UE has logged measurements available for NR and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport; or

2 >

if the UE has logged measurements available for NR and if the current registered SNPN are included in snpn-ConfigIDList stored in VarLogMeasReport:

3 >

include the logMeasAvailable in the RRCReestablishmentComplete message;

3 >

if Bluetooth measurement results are included in the logged measurements the UE has available for NR:

4 >

include the logMeasAvailableBT in the RRCReestablishmentComplete message;

3 >

if WLAN measurement results are included in the logged measurements the UE has available for NR:

4 >

include the logMeasAvailableWLAN in the RRCReestablishmentComplete message;

2 >

if the sigLoggedMeasType in VarLogMeasReport is included; or

2 >

if the UE is capable of reporting availability of signalling based logged MDT for inter-RAT (i.e. LTE to NR), and if the sigLoggedMeasType in VarLogMeasReport of TS 36.331 is included:

3 >

if T330 timer is running (associated to the logged measurement configuration for NR or for LTE):

4 >

set sigLogMeasConfigAvailable to true in the RRCReestablishmentComplete message;

3 >

else:

4 >

if the UE has logged measurements:

5 >

set sigLogMeasConfigAvailable to false in the RRCReestablishmentComplete message;

2 >

if the UE has connection establishment failure or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport or in at least one of the entries of VarConnEstFailReportList; or

2 >

if the UE supports multiple CEF report and if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the registered SNPN identity is equal to snpn-identity stored in VarConnEstFailReport or any entry of VarConnEstFailReportList:

3 >

include connEstFailInfoAvailable in the RRCReestablishmentComplete message;

2 >

if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report; or

2 >

if the UE has radio link failure or handover failure information available in VarRLF-Report of TS 36.331 and if the UE is capable of cross-RAT RLF reporting and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331; or

2 >

if the UE has radio link failure or handover failure information available in VarRLF-Report and if the current registered SNPN is included in snpn-IdentityList stored in VarRLF-Report:

3 >

include rlf-InfoAvailable in the RRCReestablishmentComplete message;

2 >

if the UE has successful handover information available in VarSuccessHO-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessHO-Report; or

2 >

if the UE has successful handover information available in VarSuccessHO-Report and if the current registered SNPN is included in snpn-IdentityList stored in the VarSuccessHO-Report:

3 >

include successHO-InfoAvailable in the RRCReestablishmentComplete message;

2 >

if the UE has successful PSCell change or addition information available in VarSuccessPSCell-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessPSCell-Report; or

2 >

if the UE has successful PSCell change or addition information available in VarSuccessPSCell-Report and if the current registered SNPN is included in snpn-IdentityList stored in the VarSuccessPSCell-Report:

3 >

include successPSCell-InfoAvailable in the RRCReestablishmentComplete message;

2 >

if the UE has flight path information available:

3 >

if at least one waypoint was not previously provided; or

3 >

if at least one upcoming waypoint that was previously provided is being removed; or

3 >

if flightPathUpdateDistanceThr is configured and for at least one waypoint, the 3D distance between the previously provided location and the new location is more than or equal to the distance threshold configured by flightPathUpdateDistanceThr; or

3 >

if flightPathUpdateTimeThr is configured and for at least one waypoint, the timestamp was not previously provided but is now available, or the time between the previously provided timestamp and the new timestamp, if available, is more than or equal to the time threshold configured by flightPathUpdateTimeThr:

4 >

include flightPathInfoAvailable;

3 >

if the UE had not previously provided a flight path information since last entering RRC_CONNECTED state; or

1 >

submit the RRCReestablishmentComplete message to lower layers for transmission;

1 >

if SIB21 is provided by the PCell:

2 >

if the UE initiated transmission of an MBSInterestIndication message during the last 1 second preceding detection of radio link failure:

3 >

initiate transmission of an MBSInterestIndication message in accordance with clause 5.9.4;

1 >

the procedure ends.

5.3.7.6 T311 expiry p. 179

Upon T311 expiry, the UE shall:

1 >

if the procedure was initiated due to radio link failure or handover failure:

2 >

set the noSuitableCellFound in the VarRLF-Report to true;

1 >

perform the actions upon going to RRC_IDLE as specified in clause 5.3.11, with release cause 'RRC connection failure'.

5.3.7.7 T301 expiry or selected cell/L2 U2N Relay UE no longer suitable p. 179

The UE shall:

1 >

if timer T301 expires; or

1 >

if the selected cell becomes no longer suitable according to the cell selection criteria as specified in TS 38.304; or

1 >

if the (re)selected L2 U2N Relay UE becomes unsuitable; or

1 >

upon reception of NotificationMessageSidelink indicating relayUE-HO or relayUE-CellReselection; or

1 >

upon PC5 unicast link release indicated by upper layer at L2 U2N Remote UE:

2 >

perform the actions upon going to RRC_IDLE as specified in clause 5.3.11, with release cause 'RRC connection failure'.

5.3.7.8 Reception of the RRCSetup by the UE p. 180

The UE shall:

1 >

perform the RRC connection establishment procedure as specified in clause 5.3.3.4.