5.3.5 RRC connection reconfiguration

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

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.3.5.1 General

Figure 5.3.5.1-1: RRC connection reconfiguration, successful

Figure 5.3.5.1-2: RRC connection reconfiguration, failure

The purpose of this procedure is to modify an RRC connection, e.g. to establish/ modify/ release RBs, to perform handover, to setup/ modify/ release measurements, to add/ modify/ release SCells, to add/modify/release conditional reconfigurations. As part of the procedure, NAS dedicated information may be transferred from E-UTRAN to the UE.

5.3.5.2 Initiation

E-UTRAN may initiate the RRC connection reconfiguration procedure to a UE in RRC_CONNECTED. E-UTRAN applies the procedure as follows:

– the mobilityControlInfo is included only when AS-security has been activated, and SRB2 with at least one DRB are setup and not suspended;

– the establishment of RBs (other than SRB1, that is established during RRC connection establishment) is included only when AS security has been activated;

– the addition of SCells is performed only when AS security has been activated;

– the addition, release or modification of conditional reconfigurations is performed only when AS security has been activated, and SRB2 with at least one DRB are setup and not suspended;

The UE initiates the RRC connection reconfiguration procedure while in RRC_CONNECTED when a conditional reconfiguration (e.g. CHO, CPA, or inter-SN CPC) is executed i.e. upon the fulfilment of an execution condition, an associated RRCConnectionReconfiguration that is stored is applied.

NOTE: Embedding in an NR Reconfiguration is used for the transfer of IRAT DL DCCH information as used for V2X sidelink communication related information specified by NR RRC e.g. to configure dedicated pool related information, CBR measurements, provision of grant assistance.

5.3.5.3 Reception of an RRCConnectionReconfiguration not including the mobilityControlInfo by the UE

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the UE is in (NG)EN-DC and;

1> if the RRCConnectionReconfiguration does not include the nr-SecondaryCellGroupConfig:

2> if the RRCConnectionReconfiguration includes the scg-State:

3> perform SCG deactivation as specified in TS 38.331 [82], clause 5.3.5.13b;

2> else:

3> perform SCG activation without SN message as specified in TS 38.331 [82], clause 5.3.5.13b1;

1> if the received RRCConnectionReconfiguration includes the daps-SourceRelease:

2> reset source MCG MAC and release the source MCG MAC configuration;

2> for each DAPS bearer:

3> re-establish the RLC entity or entities for the source PCell;

3> release the RLC entity or entities and the associated DTCH logical channel for the source PCell;

3> reconfigure the PDCP entity to release DAPS, as specified in TS 36.323 [8];

2> for each SRB:

3> release the PDCP entity for the source PCell;

3> release the RLC entity and the associated DCCH logical channel for the source PCell;

2> release the physical channel configuration for the source PCell;

1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC connection re-establishment procedure:

2> re-establish PDCP for SRB2 configured with E-UTRA PDCP entity and for all DRBs that are established and configured with E-UTRA PDCP, if any;

2> re-establish RLC for SRB2 and for all DRBs that are established and configured with E-UTRA RLC, if any;

2> if the RRCConnectionReconfiguration message includes the fullConfig:

3> perform the radio configuration procedure as specified in 5.3.5.8;

2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

3> perform the radio resource configuration procedure as specified in 5.3.10.0;

NOTE 1: Void

NOTE 2: Void

1> else:

2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

3> perform the radio resource configuration procedure as specified in 5.3.10.0;

NOTE 3: If the RRCConnectionReconfiguration message includes the establishment of radio bearers other than SRB1, the UE may start using these radio bearers immediately, i.e. there is no need to wait for an outstanding acknowledgment of the SecurityModeComplete message.

1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:

2> perform SCell release as specified in 5.3.10.3a;

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> if the received RRCConnectionReconfiguration includes the sCellGroupToReleaseList:

2> perform SCell group release as specified in 5.3.10.3d;

1> if the received RRCConnectionReconfiguration includes the sCellGroupToAddModList:

2> perform SCell group addition or modification as specified in 5.3.10.3e;

1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or

1> if the current UE configuration includes one or more split DRBs configured with pdcp-Config and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:

2> perform SCG reconfiguration as specified in 5.3.10.10;

1> if the received RRCConnectionReconfiguration includes the nr-Config and it is set to release: or

1> if the received RRCConnectionReconfiguration includes endc-ReleaseAndAdd and it is set to TRUE:

2> perform MR-DC release as specified in TS 38.331 [82], clause 5.3.5.10;

1> if the received RRCConnectionReconfiguration includes the sk-Counter:

2> perform key update procedure as specified in TS 38.331 [82], clause 5.3.5.7;

1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:

2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig2:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC connection re-establishment procedure:

2> resume SRB2 and all DRBs that are suspended, if any, including RBs configured with NR PDCP;

NOTE 4: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

NOTE 5: The UE may discard SRB2 messages and data that it receives prior to completing the reconfiguration used to resume these bearers.

1> if the received RRCConnectionReconfiguration includes the systemInformationBlockType1Dedicated:

2> perfom the actions upon reception of the SystemInformationBlockType1 message as specified in 5.2.2.7;

1> if the received RRCConnectionReconfiguration includes the systemInformationBlockType2Dedicated:

2> perfom the actions upon reception of the SystemInformationBlockType2 message as specified in 5.2.2.9;

1> if the RRCConnectionReconfiguration message includes the dedicatedInfoNASList:

2> forward each element of the dedicatedInfoNASList to upper layers in the same order as listed;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;

1> if the RRCConnectionReconfiguration message includes the otherConfig:

2> perform the other configuration procedure as specified in 5.3.10.9;

1> if the RRCConnectionReconfiguration message includes the sl-DiscConfig or sl-CommConfig:

2> perform the sidelink dedicated configuration procedure as specified in 5.3.10.15;

1> if the RRCConnectionReconfiguration message includes the sl-V2X-ConfigDedicated:

2> perform the V2X sidelink communication dedicated configuration procedure as specified in 5.3.10.15a;

NOTE 5a: If the sl-V2X-ConfigDedicated was received embedded within an NR RRCReconfiguration message, the UE does not build an E-UTRA RRCConnectionReconfigurationComplete message for the received sl-V2X-ConfigDedicated.

1> if the RRCConnectionReconfiguration message includes the sl-ConfigDedicatedForNR:

2> perform the related procedures for NR sidelink communication in accordance with TS 38.331 [82], clause 5.3.5.14 and clause 5.5.2;

1> if the RRCConnectionReconfiguration message includes wlan-OffloadInfo:

2> perform the dedicated WLAN offload configuration procedure as specified in 5.6.12.2;

1> if the RRCConnectionReconfiguration message includes rclwi-Configuration:

2> perform the WLAN traffic steering command procedure as specified in 5.6.16.2;

1> if the RRCConnectionReconfiguration message includes lwa-Configuration:

2> perform the LWA configuration procedure as specified in 5.6.14.2;

1> if the RRCConnectionReconfiguration message includes lwip-Configuration:

2> perform the LWIP reconfiguration procedure as specified in 5.6.17.2;

1> upon RRC connection establishment, if UE does not need UL gaps during continuous uplink transmission:

2> configure lower layers to stop using UL gaps during continuous uplink transmission in FDD for RRCConnectionReconfigurationComplete message and subsequent uplink transmission in RRC_CONNECTED except for UL transmissions as specified in TS36.211 [21];

1> if the RRCConnectionReconfiguration message includes the conditionalReconfiguration:

2> perform conditional reconfiguration as specified in 5.3.5.9;

NOTE 6: In case of conditional reconfiguration the text "if the received RRCConnectionReconfiguration. . ." corresponds to applying the stored RRCConnectionReconfiguration message (according to 5.3.5.9.5).

1> set the content of RRCConnectionReconfigurationComplete message as follows:

2> if the RRCConnectionReconfiguration message includes perCC-GapIndicationRequest:

3> include perCC-GapIndicationList and numFreqEffective;

2> if the frequencies are configured for reduced measurement performance:

3> include numFreqEffectiveReduced;

2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:

3> include scg-ConfigResponseNR in accordance with TS 38.331 [82], clause 5.3.5.3;

3> if the RRCConnectionReconfiguration message is applied due to a conditional reconfiguration execution and the RRCConnectionReconfiguration message does not include the mobilityControlInfo:

4> include in selectedCondReconfigurationToApply the condReconfigurationId of the conditional reconfiguration which has been executed;

1> if the UE is configured to operate in EN-DC as result of this procedure, forward upperLayerIndication, as if the UE receives this field from SIB2, to upper layers, otherwise indicate upper layers absence of this field;

1> if the UE is configured with NE-DC:

2> if the received RRCConnectionReconfiguration message was included in an NR RRCResume message:

3> transfer the RRCConnectionReconfigurationComplete message via SRB1 embedded in NR RRC message RRCResumeComplete as specified in TS 38.331 [82], clause 5.3.13.4;

2> else:

3> transfer the RRCConnectionReconfigurationComplete message via SRB1 embedded in NR RRC message RRCReconfigurationComplete as specified in TS 38.331 [82], clause 5.3.5.3;

1> else:

2> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

5.3.5.4 Reception of an RRCConnectionReconfiguration including the mobilityControlInfo by the UE (handover)

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the RRCConnectionReconfiguration is applied due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3:

2> remove all the entries within VarConditionalReconfiguration, if any;

1> if the UE is in (NG)EN-DC and;

1> if the RRCConnectionReconfiguration does not include the nr-SecondaryCellGroupConfig:

2> if the RRCConnectionReconfiguration includes the scg-State:

3> perform SCG deactivation as specified in TS 38.331 [82], clause 5.3.5.13b;

2> else:

3> perform SCG activation without SN message as specified in TS 38.331 [82], clause 5.3.5.13b1;

1> if daps-HO is not configured for any DRB:

2> stop timer T310, if running;

2> if timer T316 is running:

3> stop timer T316;

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

2> resume MCG transmission, if suspended;

1> stop timer T312, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> stop timer T370, if running;

1> if the carrierFreq is included:

2> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target PCell to be one on the frequency of the source PCell with a physical cell identity indicated by the targetPhysCellId;

1> if T309 is running:

2> stop timer T309 for all access categories;

2> perform the actions as specified in 5.3.16.4.

1> start synchronising to the DL of the target PCell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> if BL UE or UE in CE:

2> if sameSFN-Indication is not present in mobilityControlInfo:

3> acquire the MasterInformationBlock in the target PCell;

1> if makeBeforeBreak is configured:

2> perform the remainder of this procedure including and following resetting MAC after the UE has stopped the uplink transmission/downlink reception with the source PCell;

NOTE 1a: It is up to UE implementation when to stop the uplink transmission/ downlink reception with the source PCell to initiate re-tuning for connection to the target cell, as specified in TS 36.133 [16], if makeBeforeBreak is configured.

NOTE 1b: It is up to UE implementation when to stop the uplink transmission/ downlink reception with the source SCell(s) after receiving RRCConnectionReconfiguration message.

1> if daps-HO is configured for any DRB:

2> establish a MAC entity for the target PCell, with the same configuration as the MAC entity for the source PCell;

2> for each DRB configured with daps-HO:

3> establish the RLC entity or entities and the associated DTCH logical channel for the target PCell, with the same configurations as for the source PCell;

3> reconfigure the PDCP entity to configure DAPS as specified in TS36.323 [8].

2> for each DRB not configured with daps-HO:

3> re-establish PDCP;

3> re-establish the RLC entity and associate it, and the associated DTCH logical channel, to the target PCell;

2> for each SRB:

3> establish a PDCP entity for the target PCell, with the same configuration as the PDCP entity for the source PCell;

3> establish an RLC entity and an associated DCCH logical channel for the target PCell, with the same configuration as for the source PCell;

2> suspend the SRBs for the source PCell;

NOTE 1c: In order to understand if a daps-HO is configured, the UE needs to check the presence of the field daps-HO within the received RadioResourceConfigDedicated IE.

NOTE 1d: In DAPS handover, the UE may re-establish PDCP and RLC entity for a DRB not configured with daps-HO when MAC successfully completes the random access procedure. In this case, the UE suspends data transmission and reception for all DRBs not configured with daps-HO in the source PCell for the duration of the DAPS handover.

1> else (if daps-HO is not configured):

2> reset MCG MAC and SCG MAC, if configured;

2> release uplinkDataCompression, if configured;

2> re-establish PDCP for all RBs configured with pdcp-config that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

NOTE 2a: At handover the reestablishPDCP flag will be set for all RBs configured with NR PDCP in nr-RadioBearerConfig1 or nr-RadioBearerConfig2 TS 38.331 [82] which will cause the PDCP entity to be re-established also for these RBs.

2> re-establish MCG RLC and SCG RLC, if configured, for all RBs that are established;

1> for each SCell configured for the UE other than the PSCell:

2> if the received RRCConnectionReconfiguration message includes sCellState for the SCell and indicates activated:

3> configure lower layers to consider the SCell to be in activated state;

2> else if the received RRCConnectionReconfiguration message includes sCellState for the SCell and indicates dormant:

3> configure lower layers to consider the SCell to be in dormant state;

2> else:

3> configure lower layers to consider the SCell to be in deactivated state;

1> apply the value of the newUE-Identity as the C-RNTI in the target MCG;

1> if the RRCConnectionReconfiguration message includes the fullConfig:

2> perform the radio configuration procedure as specified in 5.3.5.8;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> if the received RRCConnectionReconfiguration message includes the rach-Skip:

2> configure lower layers to apply the rach-Skip for the target MCG, as specified in TS 36.213 [23] and 36.321 [6];

1> if UE supports timing advance reporting and the received radioResourceConfigCommon includes the ta-Report:

2> instruct the associated MAC entity to trigger Timing Advance reporting;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:

2> perform SCell release as specified in 5.3.10.3a;

1> if the received RRCConnectionReconfiguration includes the sCellGroupToReleaseList:

2> perform SCell group release as specified in 5.3.10.3d;

1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or

1> if the current UE configuration includes one or more split DRBs and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:

2> perform SCG reconfiguration as specified in 5.3.10.10;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10.0;

1> if the securityConfigHO (without suffix) is included in the RRCConnectionReconfiguration:

2> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

3> update the K_eNB key based on the K_ASME key taken into use with the latest successful NAS SMC procedure, as specified in TS 33.401 [32];

2> else:

3> update the K_eNB key based on the current K_eNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

NOTE 2b: If the UE needs to update the S-K_eNB key as specified in 5.3.10.10, the UE updates the S-K_eNB after updating the K_eNBkey.

2> store the nextHopChainingCount value;

2> if the securityAlgorithmConfig is included in the securityConfigHO:

3> derive the K_RRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

3> if connected as an RN; or

3> if capable of user plane integrity protection:

4> derive the K_UPint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

3> derive the K_RRCenc key and the K_UPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

2> else:

3> derive the K_RRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

3> if connected as an RN; or

3> if capable of user plane integrity protection:

4> derive the K_UPint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

3> derive the K_RRCenc key and the K_UPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

2> configure lower layers to apply the integrity protection algorithm and the K_RRCint key, i.e. the integrity protection configuration 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;

2> configure lower layers to apply the ciphering algorithm, the K_RRCenc key and the K_UPenc key, i.e. the ciphering configuration 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;

NOTE 2c: For a DRB configured for DAPS HO, the new ciphering algorithm and the K_UPenc key is applied for traffic exchange between the UE and the target MCG while the old ciphering algorithm and K_UPenc key is applied for traffic exchange between the UE and the source MCG.

1> else if the securityConfigHO-v1530 is included in the RRCConnectionReconfiguration:

2> if the nas-Container is received:

3> forward the nas-Container to upper layers;

2> if the keyChangeIndicator-r15 is received and is set to TRUE:

3> update the K_eNB key based on the K_AMF key, as specified in TS 33.501 [86];

2> else:

3> update the K_eNB key based on the current K_eNB or the NH, using the received nextHopChainingCount-r15, as specified in TS 33.501 [86];

2> store the nextHopChainingCount-r15 value;

2> if the securityAlgorithmConfig-r15 is received:

3> derive the K_RRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

3> derive the K_RRCenc key and the K_UPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

2> else:

3> derive the K_RRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

3> derive the K_RRCenc key and the K_UPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> if the received RRCConnectionReconfiguration includes the nr-Config and it is set to release; or

1> if the received RRCConnectionReconfiguration includes endc-ReleaseAndAdd and it is set to TRUE:

2> perform MR-DC release as specified in TS 38.331 [82], clause 5.3.5.10;

1> if the received RRCConnectionReconfiguration includes the sk-Counter:

2> perform key update procedure as specified in in TS 38.331 [82], clause 5.3.5.7;

1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:

2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3.

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig2:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6.

1> if connected as an RN:

2> configure lower layers to apply the integrity protection algorithm and the K_UPint key, for current or subsequently established DRBs that are configured to apply integrity protection, if any;

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> if the received RRCConnectionReconfiguration includes the sCellGroupToAddModList:

2> perform SCell group addition or modification as specified in 5.3.10.3e;

1> if the received RRCConnectionReconfiguration includes the systemInformationBlockType1Dedicated:

2> perfom the actions upon reception of the SystemInformationBlockType1 message as specified in 5.2.2.7;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;

1> release reportProximityConfig and clear any associated proximity status reporting timer;

1> if the RRCConnectionReconfiguration message includes the otherConfig:

2> perform the other configuration procedure as specified in 5.3.10.9;

1> if the RRCConnectionReconfiguration message includes the sl-DiscConfig or sl-CommConfig:

2> perform the sidelink dedicated configuration procedure as specified in 5.3.10.15;

1> if the RRCConnectionReconfiguration message includes wlan-OffloadInfo:

2> perform the dedicated WLAN offload configuration procedure as specified in 5.6.12.2;

1> if handoverWithoutWT-Change is not configured:

2> release the LWA configuration, if configured, as described in 5.6.14.3;

1> release the LWIP configuration, if configured, as described in 5.6.17.3;

1> if the RRCConnectionReconfiguration message includes rclwi-Configuration:

2> perform the WLAN traffic steering command procedure as specified in 5.6.16.2;

1> if the RRCConnectionReconfiguration message includes lwa-Configuration:

2> perform the LWA configuration procedure as specified in 5.6.14.2;

1> if the RRCConnectionReconfiguration message includes lwip-Configuration:

2> perform the LWIP reconfiguration procedure as specified in 5.6.17.2;

1> if the RRCConnectionReconfiguration message includes the sl-V2X-ConfigDedicated or mobilityControlInfoV2X:

2> perform the V2X sidelink communication dedicated configuration procedure as specified in 5.3.10.15a;

NOTE 2d: In case of conditional reconfiguration the text "if the received RRCConnectionReconfiguration. . ." corresponds to applying the stored RRCConnectionReconfiguration message (according to 5.3.5.9.5).

1> set the content of RRCConnectionReconfigurationComplete message as follows:

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:

3> include rlf-InfoAvailable;

2> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport and if T330 is not running:

3> include logMeasAvailableMBSFN;

2> else if the UE has logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

3> include the logMeasAvailable;

3> if Bluetooth measurement results are included in the logged measurements the UE has available:

4> include logMeasAvailableBT;

3> if WLAN measurement results are included in the logged measurements the UE has available:

4> include logMeasAvailableWLAN;

2> if the UE has connection establishment failure information available in VarConnEstFailReport and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:

3> include connEstFailInfoAvailable;

2> if the RRCConnectionReconfiguration message includes perCC-GapIndicationRequest:

3> include perCC-GapIndicationList and numFreqEffective;

2> if the frequencies are configured for reduced measurement performance:

3> include numFreqEffectiveReduced;

2> if the UE has flight path information available:

3> include flightPathInfoAvailable;

2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:

3> include scg-ConfigResponseNR in accordance with TS 38.331 [82], clause 5.3.5.3;

2> if the UE is connected to NTN:

3> include gnss-validityDuration in accordance with the remaining time of the GNSS validity duration;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure; or

1> if MAC indicates the successful reception of a PDCCH transmission addressed to C-RNTI and if rach-Skip is configured:

2> stop timer T304;

2> if daps-HO is configured for any DRB:

3> stop timer T310 for the source PCell, if running;

3> for each DAPS bearer trigger UL data switching, as specified in TS 36.323 [8];

2> release rach-Skip;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target PCell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target PCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target PCell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> if the UE is configured to provide IDC indications:

3> if the UE has initiated the transmission of an InDeviceCoexIndication message during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo; or

3> if the RRCConnectionReconfiguration message is applied due to a conditional reconfiguration execution and the UE has initiated transmission of an InDeviceCoexIndication message since it was configured to do so in accordance with 5.6.9.2:

4> initiate transmission of the InDeviceCoexIndication message in accordance with 5.6.9.3;

2> if the UE is configured to provide power preference indications, overheating assistance information, SPS assistance information, delay budget report or maximum bandwidth preference indications:

3> if the UE has initiated the transmission of a UEAssistanceInformation message during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo; or

3> if the RRCConnectionReconfiguration message is applied due to a conditional reconfiguration execution, and the UE has initiated transmission of a UEAssistanceInformation message for the corresponding cell group since it was configured to do so in accordance with 5.6.10.2:

4> initiate transmission of the UEAssistanceInformation message in accordance with 5.6.10.3;

2> if SystemInformationBlockType15 is broadcast by the PCell:

3> if the UE has initiated the transmission of a MBMSInterestIndication message during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo; or

3> if the RRCConnectionReconfiguration message is applied due to a conditional reconfiguration execution and the UE supports MBMS reception and the UE has initiated transmission of an MBMSInterestIndication message since it was configured to do so in accordance with 5.8.5.2:

4> ensure having a valid version of SystemInformationBlockType15 for the PCell;

4> determine the set of MBMS frequencies of interest in accordance with 5.8.5.3;

4> determine the set of MBMS services of interest in accordance with 5.8.5.3a;

4> initiate transmission of the MBMSInterestIndication message in accordance with 5.8.5.4;

2> if SystemInformationBlockType18 is broadcast by the target PCell; and the UE initiated the transmission of a SidelinkUEInformation message indicating a change of sidelink communication related parameters relevant in target PCell (i.e. change of commRxInterestedFreq or commTxResourceReq, commTxResourceReqUC if SystemInformationBlockType18 includes commTxResourceUC-ReqAllowed or commTxResourceInfoReqRelay if PCell broadcasts SystemInformationBlockType19 including discConfigRelay) during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo; or

2> if SystemInformationBlockType19 is broadcast by the target PCell; and the UE initiated the transmission of a SidelinkUEInformation message indicating a change of sidelink discovery related parameters relevant in target PCell (i.e. change of discRxInterest or discTxResourceReq, discTxResourceReqPS if SystemInformationBlockType19 includes discConfigPS or discRxGapReq or discTxGapReq if the UE is configured with gapRequestsAllowedDedicated set to true or if the UE is not configured with gapRequestsAllowedDedicated and SystemInformationBlockType19 includes gapRequestsAllowedCommon) during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo; or

2> if SystemInformationBlockType21 is broadcast by the target PCell; and the UE initiated the transmission of a SidelinkUEInformation message indicating a change of V2X sidelink communication related parameters relevant in target PCell (i.e. change of v2x-CommRxInterestedFreqList or v2x-CommTxResourceReq) during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo; or

2> if the RRCConnectionReconfiguration message is applied due to a conditional reconfiguration execution, and at least one of SystemInformationBlockType18, SystemInformationBlockType19, and SystemInformationBlockType21 is broadcast by the target PCell, and the UE has initiated transmission of a SidelinkUEInformation message since it was configured to do so in accordance with 5.10.2.2:

3> initiate transmission of the SidelinkUEInformation message in accordance with 5.10.2.3;

2> remove all the entries within VarConditionalReconfiguration, if any;

2> for each measId, if the associated reportConfig is condReconfigurationTriggerEUTRA:

3> remove the entry with the matching measId from the measIdList within the VarMeasConfig;

3> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;

3> if the measObjectId is only included in a MeasIdToAddMod:

4> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;

2> the procedure ends;

NOTE 4: The UE is not required to determine the SFN of the target PCell by acquiring system information from that cell before performing RACH access in the target PCell, except for BL UEs or UEs in CE when sameSFN-Indication is not present in mobilityControlInfo.

5.3.5.5 Reconfiguration failure

The UE shall:

1> if the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration message or if the upper layers indicate that the nas-Container is invalid:

2> continue using the configuration used prior to the reception of RRCConnectionReconfiguration message;

2> if the UE is in NE-DC:

3> perform the actions as specified in TS 38.331 [82], clause 5.3.7;

2> else if security has not been activated:

3> 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, upon which the connection reconfiguration procedure ends;

NOTE 1: The UE may apply above failure handling also in case the RRCConnectionReconfiguration message causes a protocol error for which the generic error handling as defined in 5.7 specifies that the UE shall ignore the message.

NOTE 2: If the UE is unable to comply with part of the configuration, it does not apply any part of the configuration, i.e. there is no partial success/ failure.

NOTE 3: The compliance also covers the NR configuration carried within octet strings e.g. field nr-SecondaryCellGroupConfig. I.e. the failure behaviour defined also applies in case the UE cannot comply with the NR configuration or with the combination of (parts of) the LTE and NR configurations.

NOTE 4: The compliance also covers the NR sidelink configuration carried within an octet string, e.g. field sl-ConfigDedicatedNR, i.e. the failure behaviour defined also applies in case the UE cannot comply with the embedded NR sidelink configuration.

5.3.5.6 T304 expiry (handover failure)

If T304 expires (handover failure), the UE shall:

NOTE 1: Following T304 expiry any dedicated preamble, if provided within the rach-ConfigDedicated, is not available for use by the UE anymore.

1> if no DAPS bearer is configured; or

1> if any DAPS bearer is configured and radio link failure has been detected for the source MCG in accordance with 5.3.11.3:

2> if attemptCondReconf is not configured:

3> revert back to the configuration used in the source PCell, excluding the configuration configured by the physicalConfigDedicated, the mac-MainConfig and the sps-Config;

2> else:

3> revert back to the configuration used in the source PCell;

NOTE 1a: In the context above, "the configuration" includes state variables and parameters of each radio bearer. PDCP entities associtated with RLC UM and SRB bearers are reset after the successful RRC connection re-establishment procedure according to clause 5.2 in TS 36.323 [8]. In the above, "the configuration" includes the RB configuration using NR PDCP, if configured (i.e. by nr-RadioBearerConfig1 and nr-RadioBearerConfig2).

2> store the following handover failure information in 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 source PCell based on measurements collected up to the moment the UE detected handover failure and in accordance with the following;

4> if the UE includes rsrqResult, include the lastServCellRSRQ-Type;

3> set the measResultNeighCells to include the best measured cells, other than the source PCell, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected handover 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 includes rsrqResult, include the rsrq-Type;

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> if the UE was configured to perform measurement reporting, not related to NR sidelink communication, for one or more neighbouring NR frequencies, include the measResultListNR;

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

NOTE 2: 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. Exclude-listed 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> if last RRCConnectionReconfiguration message including mobilityControlInfo concerned a failed intra-RAT handover (E-UTRA to E-UTRA):

4> set the failedPCellId to the global cell identity, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

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

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

3> else if last MobilityFromEUTRACommand concerned a failed inter-RAT handover from E-UTRA to NR:

4> set the failedNR-PCellId 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;

4> include previousPCellId and set it to the global cell identity of the PCell where the last MobilityFromEUTRACommand message was received;

4> set the timeConnFailure to the elapsed time since reception of the last MobilityFromEUTRACommand message;

3> set the connectionFailureType to ‘hof‘;

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

2> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the RRC connection reconfiguration procedure ends;

1> else (any DAPS bearer is configured and radio link failure has not been detected for the source MCG):

2> release the MAC entity for the target PCell;

2> for each DAPS bearer:

3> re-establish the RLC entity for the target PCell;

3> release the RLC entity or entities and the associated DTCH logical channel for the target PCell;

3> reconfigure the PDCP entity to release DAPS as specified in TS 36.323 [8];

2> for each non-DAPS bearer:

3> revert back to the configuration used for the DRB in the source PCell, including PDCP and RLC states and the security configuration;

2> for each SRB:

3> discard any PDCP SDUs along with the PDCP data PDUs for the source PCell;

3> re-establish the RLC entity for the source PCell;

3> release the PDCP entity for the target PCell;

3> release the RLC entity and the associated DCCH logical channel for the target PCell;

2> release the physical channel configuration for the target PCell;

2> resume the SRBs for the source PCell;

2> initiate the failure information procedure as specified in 5.6.21 to report a DAPS HO failure.

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

NOTE 3: E-UTRAN may retrieve the handover failure information using the UE information procedure with rlf-ReportReq set to true, as specified in 5.6.5.3.

5.3.5.7 Void

5.3.5.7a T307 expiry (SCG change failure)

The UE shall:

1> if T307 expires:

NOTE 1: Following T307 expiry any dedicated preamble, if provided within the rach-ConfigDedicatedSCG, is not available for use by the UE anymore.

2> if the UE is configured with DC; or

2> if the UE is configured with NE-DC and MCG transmission is not suspended:

3> initiate the SCG failure information procedure as specified in 5.6.13 to report SCG change failure;

2> else:

3> initiate the connection re-establishment procedure as specified in TS 38.331 [82] 5.3.7;

5.3.5.8 Radio Configuration involving full configuration option

The UE shall:

1> if the UE is connected to EPC:

2> release/ clear all current dedicated radio configurations except for the following:

– the MCG C-RNTI,

– the MCG security configuration,

– the PDCP, RLC, logical channel configurations for the RBs,

– the logged measurement configuration;

– the serviceType;

1> else if the UE is connected to 5GC:

2> release/ clear all current dedicated radio configurations except for the following:

– the MCG C-RNTI,

– the MCG security configuration,

– the configurations (SDAP if configured, PDCP, RLC and logical channel) for the RBs;

– the logged measurement configuration;

NOTE 1: Radio configuration is not just the resource configuration but includes other configurations like MeasConfig and OtherConfig. In case (NG)EN-DC is configured, this also includes the entire NR SCG configuration. Such NR SCG configuration does not include the DRB configuration as configured by nr-RadioBearerConfig1 and nr-RadioBearerConfig2).

1> if the RRCConnectionReconfiguration message includes the measConfigAppLayer set to setup and the measConfigAppLayer includes the serviceType stored in the current UE configuration:

2> discard the measConfigAppLayer;

2> consider the measConfigAppLayer as not received;

1> else if a serviceType is stored in the current UE configuration:

2> release the stored serviceType;

2> inform upper layers to clear the stored application layer measurement configuration;

2> discard received application layer measurement report information from upper layers;

2> consider itself not to be configured to send application layer measurement report;

1> if the RRCConnectionReconfiguration message includes the mobilityControlInfo:

2> release/ clear all current common radio configurations;

2> use the default values specified in 9.2.5 for timer T310, T311 and constant N310, N311;

1> else:

2> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SystemInformationBlockType2 (or SystemInformationBlockType2-NB in NB-IoT);

1> apply the default physical channel configuration as specified in 9.2.4;

1> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

1> apply the default MAC main configuration as specified in 9.2.2;

1> if the UE is a NB-IoT UE; or

1> for each srb-Identity value included in the srb-ToAddModList (SRB reconfiguration):

2> apply the specified configuration defined in 9.1.2 for the corresponding SRB;

2> apply the corresponding default RLC configuration for the SRB specified in 9.2.1.1 for SRB1 or in 9.2.1.2 for SRB2;

2> apply the corresponding default logical channel configuration for the SRB as specified in 9.2.1.1 for SRB1 or in 9.2.1.2 for SRB2;

2> if the corresponding SRB was configured with NR PDCP and the UE is connected to EPC:

3> release the NR PDCP entity and establish it with an E-UTRA PDCP entity and with the current (MCG) security configuration;

NOTE 1a: The UE applies the LTE ciphering and integrity protection algorithms that are equivalent to the previously configured NR security algorithms.

3> associate the RLC bearer of this SRB with the established PDCP entity;

NOTE 2: This is to get the SRBs (SRB1 and SRB2 for handover and SRB2 for reconfiguration after reestablishment) to a known state from which the reconfiguration message can do further configuration.

2> else if the UE is connected to 5GC:

3> apply the corresponding default PDCP configuration for the SRB as specified in TS 38.331 [82], clause 9.2.1;

1> for each srb-Identity value which was configured in the srb-ToAddModListExt but is not added in the RRC message configuring the full configuration:

2> release the RLC entity or entities;

2> release the DCCH logical channel;

2> release the PDCP entity;

1> if the UE is connected to EPC:

2> for each eps-BearerIdentity value included in the drb-ToAddModList or nr-RadioBearerConfig1 or nr-RadioBearerConfig2 that is part of the current E-UTRA and NR UE configuration:

3> release the E-UTRA or NR PDCP entity;

3> release the RLC entity or entities;

3> release the DTCH logical channel;

3> release the drb-identity;

NOTE 3: This will retain the eps-bearerIdentity but remove the DRBs including drb-identity of these bearers from the current UE configuration and trigger the setup of the DRBs within the AS in clause 5.3.10.3 using the new configuration. The eps-bearerIdentity acts as the anchor for associating the released and re-setup DRB. In the AS the DRB re-setup is equivalent with a new DRB setup (including new PDCP and logical channel configurations).

2> for each eps-BearerIdentity value that is part of the current E-UTRA and NR UE configuration but not added with same eps-BearerIdentity in drb-ToAddModList nor in nr-RadioBearerConfig1 nor in nr-RadioBearerConfig2:

3> perform DRB release as specified in 5.3.10.2;

1> if the UE is connected to 5GC:

2> except for NB-IoT:

3> for each pdu-Session that is part of the current NR UE configuration:

4> release the SDAP entity (clause 5.1.2 in TS 37.324 [97]);

4> release the NR PDCP entity for each DRB associated to the pdu-Session;

4> release the RLC entity or entities for each DRB associated to the pdu-Session;

4> release the DTCH logical channel for each DRB associated to the pdu-Session;

4> release the drb-identity for each DRB associated to the pdu-Session;

NOTE 4: This will retain the pdu-Session but remove the DRBs including drb-identity of these bearers from the current NR UE configuration and trigger the setup of the DRBs within the AS in clause 5.3.10.3 using the new configuration. The pdu-Session acts as the anchor for associating the released and re-setup DRB. In the AS the DRB re-setup is equivalent with a new DRB setup (including new PDCP and logical channel configurations).

3> for each pdu-Session that is part of the current NR UE configuration but not added with same pdu-Session in nr-RadioBearerConfig1 nor in nr-RadioBearerConfig2:

4> if the procedure was triggered due to handover:

5> indicate the release of the user plane resources for the pdu-Session to upper layers after successful handover;

4> else:

5> indicate the release of the user plane resources for the pdu-Session to upper layers immediately;

2> for NB-IoT UE:

3> for each pdu-Session that is part of the current UE configuration:

4> release the PDCP entity for the DRB associated to the pdu-Session;

4> release the RLC entity for the DRB associated to the pdu-Session;

4> release the DTCH logical channel for the DRB associated to the pdu-Session;

4> release the drb-identity for the DRB associated to the pdu-Session;

3> for each pdu-Session that is part of the current UE configuration but not added with same pdu-Session in drb-ToAddModList:

4> indicate the release of the user plane resources for the pdu-Session to upper layers;

5.3.5.9 Conditional reconfiguration

5.3.5.9.1 General

The network configures the UE with conditional reconfiguration (i.e. conditional handover, conditional PSCell addition, or inter-SN conditional PSCell change) including per candidate target cell an RRCConnectionReconfiguration to be stored and to be applied upon the fulfilment of an associated execution condition.

The UE shall:

1> if the received conditionalReconfiguration includes the condReconfigurationToRemoveList:

2> perform the conditional reconfiguration removal procedure as specified in 5.3.5.9.2;

1> if the received conditionalReconfiguration includes the condReconfigurationToAddModList:

2> perform the conditional reconfiguration addition/modification procedure as specified in 5.3.5.9.3;

5.3.5.9.2 Conditional reconfiguration removal

The UE shall:

1> for each CondReconfigurationId included in the condReconfigurationToRemoveList that is part of the current UE configuration in VarConditionalReconfiguration:

2> remove the entry with the matching condReconfigurationId from the condReconfigurationList within the VarConditionalReconfiguration.

NOTE: The UE does not consider the message as erroneous if the condReconfigurationToRemoveList includes any CondReconfigurationId value that is not part of the current UE configuration.

5.3.5.9.3 Conditional reconfiguration addition/modification

The UE shall:

1> for each condReconfigurationId included in the condReconfigurationToAddModList:

2> if an entry with the matching condReconfigurationId exists in the condReconfigurationList within the VarConditionalReconfiguration:

3> if the entry in condReconfigurationToAddModList includes a triggerCondition or triggerConditionSN;

4> replace triggerCondition or triggerConditionSN within the VarConditionalReconfiguration with the value received for this condReconfigurationId

3> if the entry in condReconfigurationToAddModList includes an condReconfigurationToApply;

4> replace condReconfigurationToApply within the VarConditionalReconfiguration with the value received for this condReconfigurationId;

2> else:

3> add a new entry for this condReconfigurationId within the VarConditionalReconfiguration;

3> store the associated RRCConnectionReconfiguration in VarConditionalReconfiguration.

5.3.5.9.4 Conditional reconfiguration evaluation

If AS security has been activated successfully, the UE shall:

1> if VarConditionalReconfiguration includes at least one condReconfigurationId:

2> perform conditional reconfiguration evaluation;

1> for each condReconfigurationId within the VarConditionalReconfiguration:

2> if the RRCConnectionReconfiguration within condReconfigurationToApply includes the MobilityControlInfo:

3> consider the cell which has a physical cell identity matching the value indicated in the MobilityControlInfo within condReconfigurationToApply to be an applicable cell;

2> else if the RRCConnectionReconfiguration within condReconfigurationToApply includes the nr-SecondaryCellGroupConfig:

3> consider the cell which has a physical cell identity matching the value indicated in the nr-SecondaryCellGroupConfig within the received condReconfigurationToApply to be an applicable cell;

2> if triggerConditionSN is configured (in case of SN initiated inter-SN CPC for EN-DC):

3> perform the conditional reconfiguration evaluation as specified in TS 38.331 [82], clause 5.3.5.13.4a;

3> the procedure ends;

2> for each measId included in the measIdList within VarMeasConfig indicated in the triggerCondition associated to condReconfigurationId:

3> if the entry condition(s) applicable for this event associated with the condReconfigurationId, i.e. the event corresponding with the condEventId of the corresponding condReconfigurationTriggerEUTRA within VarConditionalReconfiguration, or the event corresponding with the condEventId of the corresponding condReconfigurationTriggerNR within VarConditionalReconfiguration, is fulfilled for the applicable cell for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event within the VarConditionalReconfiguration:

4> consider the entry condition for the associated measId within triggerCondition as fulfilled;

3> if the measId for this event associated with the condReconfigurationId has been modified; or

3> if the leaving condition(s) applicable for this event associated with the condReconfigurationId, i.e. the event corresponding with the condEventId(s) of the corresponding condReconfigurationTriggerEUTRA within VarConditionalReconfiguration, or the event corresponding with the condEventId of the corresponding condReconfigurationTriggerNR within VarConditionalReconfiguration, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event within the VarConditionalReconfiguration:

4> consider the event associated to that measId to be not fulfilled;

2> if trigger conditions for all associated measId(s) within triggerCondition are fulfilled:

3> consider the target cell candidate within the stored condReconfigurationToApply, associated to that condReconfigurationId, as a triggered cell;

3> initiate the conditional reconfiguration execution, as specified in 5.3.5.9.5;

5.3.5.9.5 Conditional reconfiguration execution

The UE shall:

1> if more than one triggered cell exists:

2> select one of the triggered cells as the selected cell for conditional reconfiguration;

1> else:

2> consider the triggered cell as the selected cell for conditional reconfiguration;

1> for the selected cell of conditional reconfiguration:

2> apply the stored condReconfigurationToApply associated to that condReconfigurationId and perform the actions as specified in 5.3.5.4, or perform the actions as specified in 5.3.5.3;

5.3.5.9.6 VarConditionalReconfiguration remove

The UE shall:

1> remove all the entries within VarConditionalReconfiguration;

1> for each measId, that is part of the current UE configuration in VarMeasConfig, if the associated reportConfig has condReconfigurationTriggerEUTRA/condReconfigurationTriggerNR configured:

2> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;

2> if the associated measObjectId is only associated with condReconfigurationTriggerEUTRA/ condReconfigurationTriggerNR:

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;

5.3.5.9.7 VarConditionalReconfiguration CPC remove

The UE shall:

1> remove all the entries within VarConditionalReconfiguration for which the RRCConnectionReconfiguration within condReconfigurationToApply does not include the MobilityControlInfo.