Section: 5.3.5.3 Reception of an RRCReconfiguration by the UE
Content: The UE shall perform the following actions upon reception of the RRCReconfiguration, upon execution of the conditional reconfiguration (CHO, CPA or CPC), or upon execution of an LTM cell switch: 1> if the RRCReconfiguration 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 the MCG and the SCG VarConditionalReconfig, if any; 1> if the RRCReconfiguration includes the daps-SourceRelease: 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 TS 38.322[ NR; Radio Link Control (RLC) protocol specification ]  [4], clause 5.1.3, and the associated logical channel for the source SpCell; 3> reconfigure the PDCP entity to release DAPS as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ]  [5]; 2> for each SRB: 3> release the PDCP entity for the source SpCell; 3> release the RLC entity as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ]  [4], clause 5.1.3, 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> if the RRCReconfiguration is received via other RAT (i.e., inter-RAT handover to NR): 2> if the RRCReconfiguration does not include the fullConfig and the UE is connected to 5GC (i.e., delta signalling during intra 5GC handover): 3> re-use the source RAT SDAP and PDCP configurations if available (i.e., current SDAP/PDCP configurations for all RBs from source E-UTRA RAT prior to the reception of the inter-RAT HO RRCReconfiguration message); 1> else: 2> if the RRCReconfiguration includes the fullConfig: 3> perform the full configuration procedure as specified in 5.3.5.11; 1> if the RRCReconfiguration includes the masterCellGroup: 2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5; 1> if the RRCReconfiguration includes the masterKeyUpdate: 2> perform AS security key update procedure as specified in 5.3.5.7; 1> if the RRCReconfiguration includes the sk-Counter: 2> perform security key update procedure as specified in 5.3.5.7; 1> if the RRCReconfiguration includes the secondaryCellGroup: 2> perform the cell group configuration for the SCG according to 5.3.5.5; 1> if the RRCReconfiguration includes the mrdc-SecondaryCellGroupConfig: 2> if the mrdc-SecondaryCellGroupConfig is set to setup: 3> if the mrdc-SecondaryCellGroupConfig includes mrdc-ReleaseAndAdd: 4> perform MR-DC release as specified in clause 5.3.5.10; 3> if the received mrdc-SecondaryCellGroup is set to nr-SCG: 4> perform the RRC reconfiguration according to 5.3.5.3 for the RRCReconfiguration message included in nr-SCG; 3> if the received mrdc-SecondaryCellGroup is set to eutra-SCG: 4> perform the RRC connection reconfiguration as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [10], clause 5.3.5.3 for the RRCConnectionReconfiguration message included in eutra-SCG; 2> else (mrdc-SecondaryCellGroupConfig is set to release): 3> perform MR-DC release as specified in clause 5.3.5.10; 1> if the RRCReconfiguration message includes the radioBearerConfig: 2> perform the radio bearer configuration according to 5.3.5.6; 1> if the RRCReconfiguration message includes the radioBearerConfig2: 2> perform the radio bearer configuration according to 5.3.5.6; 1> if the RRCReconfiguration message includes the measConfig: 2> perform the measurement configuration procedure as specified in 5.5.2; 1> if the RRCReconfiguration message includes the dedicatedNAS-MessageList: 2> forward each element of the dedicatedNAS-MessageList to upper layers in the same order as listed; 1> if the RRCReconfiguration message includes the dedicatedSIB1-Delivery: 2> perform the action upon reception of SIB1 as specified in 5.2.2.4.2; NOTE 0: If this RRCReconfiguration is associated to the MCG and includes reconfigurationWithSync in spCellConfig and dedicatedSIB1-Delivery, the UE initiates (if needed) the request to acquire required SIBs, according to clause 5.2.2.3.5, only after the random access procedure or the LTM cell switch execution towards the target SpCell is completed. 1> if the RRCReconfiguration message includes the dedicatedSystemInformationDelivery: 2> perform the action upon reception of System Information as specified in 5.2.2.4; 2> if all the SIB(s) and/or posSIB(s) requested in DedicatedSIBRequest message have been acquired: 3> stop timer T350, if running; 1> if the RRCReconfiguration message includes the dedicatedPosSysInfoDelivery: 2> perform the action upon reception of the contained posSIB(s), as specified in clause 5.2.2.4.16; 2> if all the SIB(s) and/or posSIB(s) requested in DedicatedSIBRequest message have been acquired: 3> stop timer T350, if running; 1> if the RRCReconfiguration message includes the otherConfig: 2> perform the other configuration procedure as specified in 5.3.5.9; 1> if the RRCReconfiguration message includes the bap-Config: 2> perform the BAP configuration procedure as specified in 5.3.5.12; 1> if the RRCReconfiguration message includes the iab-IP-AddressConfigurationList: 2> if iab-IP-AddressToReleaseList is included: 3> perform release of IP address as specified in 5.3.5.12a.1.1; 2> if iab-IP-AddressToAddModList is included: 3> perform IAB IP address addition/update as specified in 5.3.5.12a.1.2; 1> if the RRCReconfiguration message includes the conditionalReconfiguration: 2> perform conditional reconfiguration as specified in 5.3.5.13; 1> if the RRCReconfiguration message includes the needForGapsConfigNR: 2> if needForGapsConfigNR is set to setup: 3> consider itself to be configured to provide the measurement gap requirement information of NR target bands; 2> else: 3> consider itself not to be configured to provide the measurement gap requirement information of NR target bands; 1> if the RRCReconfiguration message includes the needForGapNCSG-ConfigNR: 2> if needForGapNCSG-ConfigNR is set to setup: 3> consider itself to be configured to provide the measurement gap and NCSG requirement information of NR target bands; 2> else: 3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of NR target bands; 1> if the RRCReconfiguration message includes the needForGapNCSG-ConfigEUTRA: 2> if needForGapNCSG-ConfigEUTRA is set to setup: 3> consider itself to be configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands; 2> else: 3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands; 1> if the RRCReconfiguration message includes the onDemandSIB-Request: 2> if onDemandSIB-Request is set to setup: 3> consider itself to be configured to request SIB(s) or posSIB(s) in RRC_CONNECTED in accordance with clause 5.2.2.3.5; 2> else: 3> consider itself not to be configured to request SIB(s) or posSIB(s) in RRC_CONNECTED in accordance with clause 5.2.2.3.5; 3> stop timer T350, if running; 1> if the RRCReconfiguration message includes the sl-ConfigDedicatedNR: 2> perform the sidelink dedicated configuration procedure as specified in 5.3.5.14; NOTE 0a: If the sl-ConfigDedicatedNR was received embedded within an E-UTRA RRCConnectionReconfiguration message, the UE does not build an NR RRCReconfigurationComplete message for the received sl-ConfigDedicatedNR. 1> if the RRCReconfiguration message includes the sl-L2RelayUE-Config: 2> perform the L2 U2N or U2U Relay UE configuration procedure as specified in 5.3.5.15; 1> if the RRCReconfiguration message includes the sl-L2RemoteUE-Config: 2> perform the L2 U2N or U2U Remote UE configuration procedure as specified in 5.3.5.16; 1> if the RRCReconfiguration message includes the dedicatedPagingDelivery: 2> perform the Paging message reception procedure as specified in 5.3.2.3; 1> if the RRCReconfiguration message includes the sl-ConfigDedicatedEUTRA-Info: 2> perform related procedures for V2X sidelink communication in accordance with TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [10], clause 5.3.10 and clause 5.5.2; 1> if the RRCReconfiguration message includes the ul-GapFR2-Config: 2> perform the FR2 UL gap configuration procedure as specified in 5.3.5.13c; 1> if the RRCReconfiguration message includes the musim-GapConfig: 2> perform the MUSIM gap configuration procedure as specified in 5.3.5.9a; 1> if idleInactiveReportAllowed is not included in the RRCReconfiguration message: 2> for each application layer measurement configuration with configforRRC-IdleInactive set to true: 3> forward the measConfigAppLayerId and inform upper layers about the release of the application layer measurement configuration; 3> discard any application layer measurement reports which were not yet submitted to lower layers for transmission; 3> if stored, release the application layer measurement configuration in UE variables VarAppLayerIdleConfig and VarAppLayerPLMN-ListConfig; 3> consider itself not to be configured to send application layer measurement report for the measConfigAppLayerId; 1> if the RRCReconfiguration message includes the appLayerMeasConfig: 2> perform the application layer measurement configuration procedure as specified in 5.3.5.13d; 1> if the RRCReconfiguration message includes the ue-TxTEG-RequestUL-TDOA-Config: 2> if ue-TxTEG-RequestUL-TDOA-Config is set to setup: 3> perform the UE positioning assistance information procedure as specified in 5.7.14; 2> else: 3> release the configuration of UE positioning assistance information; 1> if the RRCReconfiguration message includes the uav-Config: 2> (re)configure the UAV parameters in accordance with the included uav-Config; 1> if the RRCReconfiguration message includes the sl-IndirectPathAddChange: 2> perform the SL indirect path specific configuration procedure as specified in 5.3.5.17.2.2; 1> if the RRCReconfiguration message includes the n3c-IndirectPathAddChange: 2> perform configuration procedure for the remote UE part of N3C indirect path as specified in 5.3.5.17.3.2; 1> if the RRCReconfiguration message includes the n3c-IndirectPathConfigRelay: 2> perform the configuration procedure for the relay UE part of N3C indirect path as specified in 5.3.5.17.3.3; 1> if the RRCReconfiguration message includes the ltm-Config: 2> if the ltm-Config is set to setup: 3> perform the LTM configuration procedure as specified in 5.3.5.18.1; 2> else: 3> perform the LTM configuration release procedure as specified in clause 5.3.5.18.7; 1> set the content of the RRCReconfigurationComplete message as follows: 2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrent: 3> include the uplinkTxDirectCurrentList for each MCG serving cell with UL; 3> include uplinkDirectCurrentBWP-SUL for each MCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentList; 2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrentTwoCarrier: 3> include in the uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the MCG; 2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrentMoreCarrier: 3> include in the uplinkTxDirectCurrentMoreCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the MCG; 2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrent: 3> include the uplinkTxDirectCurrentList for each SCG serving cell with UL; 3> include uplinkDirectCurrentBWP-SUL for each SCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentList; 2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrentTwoCarrier: 3> include in the uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the SCG; 2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrentMoreCarrier: 3> include in the uplinkTxDirectCurrentMoreCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the SCG; NOTE 0b: The UE does not expect that the reportUplinkTxDirectCurrentTwoCarrier or reportUplinkTxDirectCurrentMoreCarrier is received in both masterCellGroup and in secondaryCellGroup. Network only configures at most one of reportUplinkTxDirectCurrent, reportUplinkTxDirectCurrentTwoCarrier or reportUplinkTxDirectCurrentMoreCarrier in one RRC message. 2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to eutra-SCG: 3> include in the eutra-SCG-Response the E-UTRA RRCConnectionReconfigurationComplete message in accordance with TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [10] clause 5.3.5.3; 2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to nr-SCG: 3> include in the nr-SCG-Response the SCG RRCReconfigurationComplete message; 3> if the RRCReconfiguration message is applied due to conditional reconfiguration execution and the RRCReconfiguration message does not include the reconfigurationWithSync in the masterCellGroup: 4> include in the selectedCondRRCReconfig the condReconfigId for the selected cell of conditional reconfiguration execution; 4> if a new sk-Counter value has been selected due to the conditional reconfiguration execution for subsequent CPAC: 5> include selectedSK-Counter and set its value to the selected sk-Counter value; 3> if the RRCReconfiguration message is applied due to conditional reconfiguration execution and condExecutionCondPSCell is configured for the selected PSCell: 4> include in the selectedPSCellForCHO-WithSCG and set it to the information of the selected PSCell; 2> if the RRCReconfiguration includes the reconfigurationWithSync in spCellConfig of an MCG: 3> if the UE has logged measurements available for NR and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport; or 3> if the UE has logged measurements available for NR and if the current registered SNPN is included in snpn-ConfigIDList stored in the VarLogMeasReport: 4> include the logMeasAvailable in the RRCReconfigurationComplete message; 4> if Bluetooth measurement results are included in the logged measurements the UE has available for NR: 5> include the logMeasAvailableBT in the RRCReconfigurationComplete message; 4> if WLAN measurement results are included in the logged measurements the UE has available for NR: 5> include the logMeasAvailableWLAN in the RRCReconfigurationComplete message; 3> if the sigLoggedMeasType in VarLogMeasReport is included; or 3> 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[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [10] is included: 4> if T330 timer is running (associated to the logged measurement configuration for NR or for LTE): 5> set sigLogMeasConfigAvailable to true in the RRCReconfigurationComplete message; 4> else: 5> if the UE has logged measurements: 6> set sigLogMeasConfigAvailable to false in the RRCReconfigurationComplete message; 3> 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 3> 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: 4> include connEstFailInfoAvailable in the RRCReconfigurationComplete message; 3> 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 3> if the UE has radio link failure or handover failure information available in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [10] 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[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [10]; or 3> 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: 4> include rlf-InfoAvailable in the RRCReconfigurationComplete message; 3> if the UE was configured with successHO-Config when connected to the source PCell; and 3> if the applied RRCReconfiguration is not due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3: 4> perform the actions for the successful handover report determination as specified in clause 5.7.10.6, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the MCG; 3> 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 3> 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: 4> include successHO-InfoAvailable in the RRCReconfigurationComplete message; 3> if the UE supports logging the successful PSCell change or addition information, release successPSCell-Config configured by the source PCell, if available; 3> 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 3> 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: 4> include successPSCell-InfoAvailable in the RRCReconfigurationComplete message; 2> if the RRCReconfiguration message was received via SRB1, but not within mrdc-SecondaryCellGroup or E-UTRA RRCConnectionReconfiguration or E-UTRA RRCConnectionResume: 3> if the UE is configured to provide the measurement gap requirement information of NR target bands: 4> if the RRCReconfiguration message includes the needForGapsConfigNR; or 4> if the NeedForGapsInfoNR information is changed compared to last time the UE reported this information; or 4> if the RRCReconfiguration message includes the needForInterruptionConfigNR and set it to enabled; or 4> if the needForInterruptionConfigNR is enabled and the NeedForInterruptionInfoNR information is changed compared to last time the UE reported this information: 5> include the NeedForGapsInfoNR and set the contents as follows: 6> include intraFreq-needForGap and set the gap requirement information of intra-frequency measurement for each NR serving cell; 6> if requestedTargetBandFilterNR is configured: 7> for each supported NR band that is also included in requestedTargetBandFilterNR, include an entry in interFreq-needForGap and set the gap requirement information for that band; 6> else: 7> include an entry in interFreq-needForGap and set the corresponding gap requirement information for each supported NR band; 5> if the needForInterruptionConfigNR is enabled: 6> include the needForInterruptionInfoNR and set the contents as follows: 7> include intraFreq-needForInterruption with the same number of entries, and listed in the same order, as in intraFreq-needForGap; 7> for each entry in intraFreq-needForInterruption, include interruptionIndication and set the interruption requirement information if the corresponding entry in intraFreq-needForGap is set to no-gap; 7> include interFreq-needForInterruption with the same number of entries, and listed in the same order, as in interFreq-needForGap; 7> for each entry in interFreq-needForInterruption, include interruptionIndication and set the interruption requirement information if the corresponding entry in interFreq-needForGap is set to no-gap; 3> if the UE is configured to provide the measurement gap and NCSG requirement information of NR target bands: 4> if the RRCReconfiguration message includes the needForGapNCSG-ConfigNR; or 4> if the needForGapNCSG-InfoNR information is changed compared to last time the UE reported this information: 5> include the NeedForGapNCSG-InfoNR and set the contents as follows: 6> include intraFreq-needForNCSG and set the gap and NCSG requirement information of intra-frequency measurement for each NR serving cell; 6> if requestedTargetBandFilterNCSG-NR is configured: 7> for each supported NR band included in requestedTargetBandFilterNCSG-NR, include an entry in interFreq-needForNCSG and set the NCSG requirement information for that band; 6> else: 7> include an entry for each supported NR band in interFreq-needForNCSG and set the corresponding NCSG requirement information; 3> if the UE is configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands: 4> if the RRCReconfiguration message includes the needForGapNCSG-ConfigEUTRA; or 4> if the needForGapNCSG-InfoEUTRA information is changed compared to last time the UE reported this information: 5> include the NeedForGapNCSG-InfoEUTRA and set the contents as follows: 6> if requestedTargetBandFilterNCSG-EUTRA is configured, for each supported E-UTRA band included in requestedTargetBandFilterNCSG-EUTRA, include an entry in needForNCSG-EUTRA and set the NCSG requirement information for that band; otherwise, include an entry for each supported E-UTRA band in needForNCSG-EUTRA and set the corresponding NCSG requirement information; 2> if the UE has flight path information available: 3> if the UE had not previously provided a flight path information since last entering RRC_CONNECTED state; or 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; NOTE 0c: If neither flightPathUpdateDistanceThr nor flightPathUpdateTimeThr is configured, it is up to UE implementation whether to include flightPathInfoAvailable when updated flight path information is available. 1> if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (UE in (NG)EN-DC): 2> if the RRCReconfiguration message was received via E-UTRA SRB1 as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [10]; or 2> if the RRCReconfiguration message was received via E-UTRA RRC message RRCConnectionReconfiguration within MobilityFromNRCommand (handover from NR standalone to (NG)EN-DC); 3> if the RRCReconfiguration is applied due to a conditional reconfiguration execution for CPC which is configured via conditionalReconfiguration contained in nr-SecondaryCellGroupConfig specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [10]: 4> submit the RRCReconfigurationComplete message via the E-UTRA MCG embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [10], clause 5.6.2a. 3> else if the RRCReconfiguration message was included in E-UTRA RRCConnectionResume message: 4> submit the RRCReconfigurationComplete message via E-UTRA embedded in E-UTRA RRC message RRCConnectionResumeComplete as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [10], clause 5.3.3.4a; 3> else: 4> submit the RRCReconfigurationComplete via E-UTRA embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [10], clause 5.3.5.3/5.3.5.4/5.4.2.3; 3> if the scg-State is not included in the E-UTRA message (RRCConnectionReconfiguration or RRCConnectionResume) containing the RRCReconfiguration message: 4> perform SCG activation as specified in 5.3.5.13a; 4> if reconfigurationWithSync was included in spCellConfig of an SCG: 5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ]  [3]; 4> else if the SCG was deactivated before the reception of the E-UTRA RRC message containing the RRCReconfiguration message: 5> if bfd-and-RLM was not configured to true before the reception of the E-UTRA RRCConnectionReconfiguration or RRCConnectionResume message containing the RRCReconfiguration message or if lower layers indicate that a Random Access procedure is needed for SCG activation: 6> initiate the Random Access procedure on the SpCell, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ]  [3]; 5> else the procedure ends; 4> else the procedure ends; 3> else: 4> perform SCG deactivation as specified in 5.3.5.13b; 4> the procedure ends; 2> if the RRCReconfiguration message was received within nr-SecondaryCellGroupConfig in RRCConnectionReconfiguration message received via SRB3 within DLInformationTransferMRDC: 3> submit the RRCReconfigurationComplete via E-UTRA embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [10], clause 5.3.5.3/5.3.5.4; 3> if the scg-State is not included in the RRCConnectionReconfiguration: 4> if reconfigurationWithSync was included in spCellConfig of an SCG: 5> initiate the Random Access procedure on the SpCell, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ]  [3]; 4> else the procedure ends; 3> else: 4> perform SCG deactivation as specified in 5.3.5.13b; 4> the procedure ends; NOTE 1: The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation. 2> else (RRCReconfiguration was received via SRB3) but not within DLInformationTransferMRDC: 3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration; NOTE 2: In (NG)EN-DC and NR-DC, in the case RRCReconfiguration is received via SRB1 or within DLInformationTransferMRDC via SRB3, the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case RRCReconfiguration is received via SRB3 but not within DLInformationTransferMRDC, the random access is triggered by the MAC layer due to arrival of RRCReconfigurationComplete. 1> else if the RRCReconfiguration message was received via SRB1 within the nr-SCG within mrdc-SecondaryCellGroup (UE in NR-DC, mrdc-SecondaryCellGroup was received in RRCReconfiguration or RRCResume via SRB1): 2> if the RRCReconfiguration is applied due to a conditional reconfiguration execution for CPC which is configured via conditionalReconfiguration contained in nr-SCG within mrdc-SecondaryCellGroup; or 2> if the RRCReconfiguration is applied due to an LTM cell switch execution: 3> submit the RRCReconfigurationComplete message via the NR MCG embedded in NR RRC message ULInformationTransferMRDC as specified in clause 5.7.2a.3. 2> if the scg-State is not included in the RRCReconfiguration or RRCResume message containing the RRCReconfiguration message: 3> perform SCG activation as specified in 5.3.5.13a; 3> if reconfigurationWithSync was included in spCellConfig in nr-SCG: 4> if the RRCReconfiguration message is not applied due to an LTM cell switch execution for which lower layer indicate to skip the Random Access procedure: 5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ]  [3]; 4> if the UE was configured with successPSCell-Config when connected to the source PSCell (for PSCell change) or to the PCell (for PSCell addition or change): 5> perform the actions for the successful PSCell change or addition report determination as specified in clause 5.7.10.7, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the SCG; 3> else if the SCG was deactivated before the reception of the NR RRC message containing the RRCReconfiguration message: 4> if bfd-and-RLM was not configured to true before the reception of the RRCReconfiguration or RRCResume message containing the RRCReconfiguration message; or 4> if lower layers indicate that a Random Access procedure is needed for SCG activation: 5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ]  [3]; 4> else the procedure ends; 3> else the procedure ends; 2> else 3> perform SCG deactivation as specified in 5.3.5.13b; 3> the procedure ends; NOTE 2a: The order in which the UE sends the RRCReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation. 1> else if the RRCReconfiguration message was received via SRB3 (UE in NR-DC): 2> if the RRCReconfiguration message was received within DLInformationTransferMRDC: 3> if the RRCReconfiguration message was received within the nr-SCG within mrdc-SecondaryCellGroup (NR SCG RRC Reconfiguration): 4> if the scg-State is not included in the RRCReconfiguration message containing the RRCReconfiguration message: 5> if reconfigurationWithSync was included in spCellConfig in nr-SCG: 6> initiate the Random Access procedure on the PSCell, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ]  [3]; 6> if the UE was configured with successPSCell-Config by the PCell or by the source PSCell: 7> perform the actions for the successful PSCell change report determination as specified in clause 5.7.10.7, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the SCG; 5> else: 6> the procedure ends; 4> else: 5> perform SCG deactivation as specified in 5.3.5.13b; 5> the procedure ends; 3> else: 4> if the RRCReconfiguration does not include the mrdc-SecondaryCellGroupConfig: 5> if the RRCReconfiguration includes the scg-State: 6> perform SCG deactivation as specified in 5.3.5.13b; 4> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration; 2> else: 3> if the RRCReconfiguration includes the reconfigurationWithSync in spCellConfig for the SCG; and 3> if the UE was configured with successPSCell-Config: 4> perform the actions for the successful PSCell change report determination as specified in clause 5.7.10.7, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the SCG; 3> 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 3> 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: 4> include successPSCell-InfoAvailable in the RRCReconfigurationComplete message; 3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration; 1> else (RRCReconfiguration was received via SRB1): 2> if the UE is in NR-DC and; 2> if the RRCReconfiguration does not include the mrdc-SecondaryCellGroupConfig: 3> if the RRCReconfiguration includes the scg-State: 4> perform SCG deactivation as specified in 5.3.5.13b; 3> else: 4> perform SCG activation without SN message as specified in 5.3.5.13b1; 2> if the reconfigurationWithSync was included in spCellConfig of an MCG: 3> if ta-Report or ta-ReportATG is configured with value enabled and the UE supports TA reporting: 4> indicate TA report initiation to lower layers; 2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration; 2> if this is the first RRCReconfiguration message after successful completion of the RRC re-establishment procedure: 3> resume SRB2, SRB4, DRBs, multicast MRB, and BH RLC channels for IAB-MT, and Uu Relay RLC channels for L2 U2N Relay UE, that are suspended; 1> if sl-IndirectPathAddChange was included in RRCReconfiguration message and if SRB1 is configured as split SRB and pdcp-Duplication is configured: 2> when successfully sending RRCReconfigurationComplete message via SL indirect path (i.e., PC5 RLC acknowledgement is received from target L2 U2N Relay UE): 3> stop timer T421; 1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG and when MAC of an NR cell group successfully completes a Random Access procedure triggered above; or, 1> if sl-PathSwitchConfig was included in reconfigurationWithSync included in spCellConfig of an MCG, and when successfully sending RRCReconfigurationComplete message (i.e., PC5 RLC acknowledgement is received from target L2 U2N Relay UE); or, 1> if rach-LessHO was included in reconfigurationWithSync included in spCellConfig of an MCG, and upon indication from lower layers that the RACH-less handover has been successfully completed; or, 1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG and the RRCReconfiguration message is applied due to an LTM cell switch execution and upon an indication from lower layer that the LTM cell switch execution has been successfully completed: 2> stop timer T304 for that cell group if running; 2> if sl-PathSwitchConfig was included in reconfigurationWithSync: 3> stop timer T420; 3> release all radio resources, including release of the RLC entities and the MAC configuration at the source side; 3> reset MAC used in the source cell; 2> if rach-LessHO was included in reconfigurationWithSync and cg-NTN-RACH-Less-Configuration was configured: 3> release the uplink grant configured for RACH-less handover in cg-NTN-RACH-Less-Configuration; NOTE 2b: PDCP and SDAP configured by the source prior to the path switch that are reconfigured and re-used by target when delta signalling is used, are not released as part of this procedure. 2> stop timer T310 for source SpCell if running; 2> apply the parts of the CSI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any; 2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell; 2> for each DRB configured as DAPS bearer, request uplink data switching to the PDCP entity, as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ]  [5]; 2> if the reconfigurationWithSync was included in spCellConfig of an MCG: 3> if T390 is running: 4> stop timer T390 for all access categories; 4> perform the actions as specified in 5.3.14.4. 3> if T350 is running: 4> stop timer T350; 3> if RRCReconfiguration does not include dedicatedSIB1-Delivery and 3> if the active downlink BWP, which is indicated by the firstActiveDownlinkBWP-Id for the target SpCell of the MCG, has a common search space configured by searchSpaceSIB1: 4> acquire the SIB1, which is scheduled as specified in TS 38.213[ NR; Physical layer procedures for control ]  [13], of the target SpCell of the MCG; 4> upon acquiring SIB1, perform the actions specified in clause 5.2.2.4.2; 2> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution and the subsequentCondReconfig is included in the entry in VarConditionalReconfig containing the RRCReconfiguration message: 3> for each condReconfigId included in condExecutionCondToAddModList within subsequentCondReconfig: 4> replace within VarConditionalReconfig the entry in condExecutionCond or condExecutionCondSCG with the matching condReconfigId value; 2> if the reconfigurationWithSync was included in spCellConfig of an MCG; or 2> if the reconfigurationWithSync was included in spCellConfig of an SCG and the CPA, CPC, or subsequent CPAC was configured: 3> remove all the entries in the condReconfigList within the MCG and the SCG VarConditionalReconfig except for the entries in which subsequentCondReconfig is present, if any; 3> remove all the entries within VarConditionalReconfiguration as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [10], clause 5.3.5.9.6, if any; 3> for each measId of the MCG measConfig, if configured, and for each measId of the SCG measConfig, if configured, if the associated reportConfig has a reportType set to condTriggerConfig: 4> if the reportConfigId is not associated with any measId indicated by the condExecutionCond or the condExecutionCondSCG in an entry of condReconfigList in VarConditionalReconfig in which subsequentCondReconfig is included: 5> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig; 4> if the associated measObjectId is only associated to a reportConfig with reportType set to condTriggerConfig; and 4> if the measObjectId is not associated with any measId indicated by the condExecutionCond or the condExecutionCondSCG in an entry of condReconfigList in VarConditionalReconfig in which subsequentCondReconfig is included: 5> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig; 4> remove the entry with the matching measId from the measIdList within the VarMeasConfig; 2> if reconfigurationWithSync was included in masterCellGroup or secondaryCellGroup: 3> if the UE initiated transmission of a UEAssistanceInformation message for the corresponding cell group during the last 1 second, and the UE is still configured to provide the concerned UE assistance information for the corresponding cell group; or 3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution or an LTM cell switch procedure, and the UE is configured to provide UE assistance information for the corresponding cell group, 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.7.4.2: 4> initiate transmission of a UEAssistanceInformation message for the corresponding cell group in accordance with clause 5.7.4.3 to provide the concerned UE assistance information; 4> start or restart the prohibit timer (if exists) or the leave without response timer for the MUSIM associated with the concerned UE assistance information with the timer value set to the value in corresponding configuration; 3> if SIB12 is provided by the target PCell, and the UE initiated transmission of a SidelinkUEInformationNR message indicating a change of NR sidelink communication/discovery related parameters relevant in target PCell (i.e. change of sl-RxInterestedFreqList or sl-TxResourceReqList) during the last 1 second preceding reception of the RRCReconfiguration message including reconfigurationWithSync in spCellConfig of an MCG; or 3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution and the UE is capable of NR sidelink communication/discovery and SIB12 is provided by the target PCell, and the UE has initiated transmission of a SidelinkUEInformationNR message since it was configured to do so in accordance with 5.8.3.2: 4> initiate transmission of the SidelinkUEInformationNR message in accordance with 5.8.3.3; 2> if reconfigurationWithSync was included in masterCellGroup: 3> if configured with application layer measurements and if application layer measurement report container has been received from upper layers for which the successful transmission of the message or at least one segment of the message has not been confirmed by lower layers: 4> re-submit the MeasurementReportAppLayer message or all segments of the MeasurementReportAppLayer message to lower layers for transmission via SRB4; 2> if reconfigurationWithSync was included in masterCellGroup and the target cell provides SIB21: 3> if the UE initiated transmission of an MBSInterestIndication message during the last 1 second preceding reception of this RRCReconfiguration message; or 3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution, and the UE has initiated transmission of an MBSInterestIndication message after having received this RRCReconfiguration message: 4> initiate transmission of an MBSInterestIndication message in accordance with clause 5.9.4; 2> the procedure ends. NOTE 3: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast or MBS multicast data reception, i.e. the broadcast and unicast/MBS multicast beams are quasi co-located. NOTE 4: The UE sets the content of UEAssistanceInformation according to latest configuration (i.e. the configuration after applying the RRCReconfiguration message) and latest UE preference. The UE may include more than the concerned UE assistance information within the UEAssistanceInformation according to 5.7.4.2. Therefore, the content of UEAssistanceInformation message might not be the same as the content of the previous UEAssistanceInformation message.