Section: 5.3.7.2 Initiation
Content: The UE initiates the procedure when one of the following conditions is met: 1> upon detecting radio link failure of the MCG and t316 is not configured, in accordance with 5.3.10; or 1> upon detecting radio link failure of the MCG while SCG transmission is suspended, in accordance with 5.3.10; or 1> upon detecting radio link failure of the MCG while PSCell change or PSCell addition is ongoing, in accordance with 5.3.10; or 1> upon detecting radio link failure of the MCG while the SCG is deactivated, in accordance with 5.3.10; or 1> upon re-configuration with sync failure of the MCG, in accordance with clause 5.3.5.8.3; or 1> upon mobility from NR failure, in accordance with clause 5.4.3.5; or 1> upon integrity check failure indication from lower layers concerning SRB1 or SRB2, except if the integrity check failure is detected on the RRCReestablishment message; or 1> upon an RRC connection reconfiguration failure, in accordance with clause 5.3.5.8.2; or 1> upon detecting radio link failure for the SCG while MCG transmission is suspended, in accordance with clause 5.3.10.3 in NR-DC or in accordance with TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [10] clause 5.3.11.3 in NE-DC; or 1> upon reconfiguration with sync failure of the SCG while MCG transmission is suspended in accordance with clause 5.3.5.8.3; or 1> upon SCG change failure while MCG transmission is suspended in accordance with TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [10] clause 5.3.5.7a; or 1> upon SCG configuration failure while MCG transmission is suspended in accordance with clause 5.3.5.8.2 in NR-DC or in accordance with TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [10] clause 5.3.5.5 in NE-DC; or 1> upon integrity check failure indication from SCG lower layers concerning SRB3 while MCG is suspended; or 1> upon T316 expiry, in accordance with clause 5.7.3b.5; or 1> upon detecting sidelink radio link failure by L2 U2N Remote UE in RRC_CONNECTED which is not configured with MP, in accordance with clause 5.8.9.3; or 1> upon reception of NotificationMessageSidelink including indicationType by L2 U2N Remote UE in RRC_CONNECTED which is not configured with MP, in accordance with clause 5.8.9.10; or 1> upon PC5 unicast link release for the serving L2 U2N Relay UE indicated by upper layer at L2 U2N Remote UE in RRC_CONNECTED which is not configured with MP while T301 is not running; or 1> if MP is configured, upon detecting radio link failure of the MCG (i.e. direct path) in accordance with clause 5.3.10 while the transmission of indirect path is suspended as specified in 5.3.5.17; or 1> if MP is configured, upon detecting sidelink radio link failure of SL indirect path by L2 U2N Remote UE, in accordance with clause 5.8.9.3, while MCG transmission (i.e. direct path) is suspended as specified in clause 5.7.3b; or 1> if MP is configured, upon reception of NotificationMessageSidelink including indicationType in accordance with clause 5.8.9.10, while MCG transmission (i.e. direct path) is suspended as specified in clause 5.7.3b; or 1> if MP is configured, upon PC5 unicast link release indicated by upper layer at L2 U2N Remote UE, while MCG transmission (i.e. direct path) is suspended as specified in clause 5.7.3b; or 1> if MP is configured, upon detecting the failure of N3C indirect path by N3C remote UE in accordance with clause 5.7.3c, while MCG transmission (i.e. direct path) is suspended. NOTE 0: It is up to UE implementation whether to initiate the procedure while T346g is running. Upon initiation of the procedure, the UE shall: 1> stop timer T310, if running; 1> stop timer T312, if running; 1> stop timer T304, if running; 1> start timer T311; 1> stop timer T316, if running; 1> if UE is not configured with attemptCondReconfig; and 1> if UE is not configured with attemptLTM-Switch: 2> reset MAC; 2> release spCellConfig, if configured; 2> suspend all RBs, and BH RLC channels for IAB-MT, and Uu Relay RLC channels for L2 U2N Relay UE, except SRB0 and broadcast MRBs; 2> release the MCG SCell(s), if configured; 2> if MR-DC is configured: 3> perform MR-DC release, as specified in clause 5.3.5.10; 2> perform the LTM configuration release procedure for the MCG and the SCG as specified in clause 5.3.5.18.7; 2> release delayBudgetReportingConfig, if configured and stop timer T342, if running; 2> release overheatingAssistanceConfig, if configured and stop timer T345, if running; 2> release idc-AssistanceConfig, if configured; 2> release btNameList, if configured; 2> release wlanNameList, if configured; 2> release sensorNameList, if configured; 2> release drx-PreferenceConfig for the MCG, if configured and stop timer T346a associated with the MCG, if running; 2> release maxBW-PreferenceConfig for the MCG, if configured and stop timer T346b associated with the MCG, if running; 2> release maxCC-PreferenceConfig for the MCG, if configured and stop timer T346c associated with the MCG, if running; 2> release maxMIMO-LayerPreferenceConfig for the MCG, if configured and stop timer T346d associated with the MCG, if running; 2> release minSchedulingOffsetPreferenceConfig for the MCG, if configured stop timer T346e associated with the MCG, if running; 2> release rlm-RelaxationReportingConfig for the MCG, if configured and stop timer T346j associated with the MCG, if running; 2> release bfd-RelaxationReportingConfig for the MCG, if configured and stop timer T346k associated with the MCG, if running; 2> release releasePreferenceConfig, if configured stop timer T346f, if running; 2> release onDemandSIB-Request if configured, and stop timer T350, if running; 2> release referenceTimePreferenceReporting, if configured; 2> release sl-AssistanceConfigNR, if configured; 2> release obtainCommonLocation, if configured; 2> release musim-GapAssistanceConfig, if configured and stop timer T346h, if running; 2> release musim-GapPriorityAssistanceConfig, if configured; 2> release musim-LeaveAssistanceConfig, if configured; 2> release musim-CapabilityRestrictionConfig, if configured and stop timer T346n, if running; 2> release ul-GapFR2-PreferenceConfig, if configured; 2> release scg-DeactivationPreferenceConfig, if configured, and stop timer T346i, if running; 2> release propDelayDiffReportConfig, if configured; 2> release rrm-MeasRelaxationReportingConfig, if configured; 2> release maxBW-PreferenceConfigFR2-2, if configured; 2> release maxMIMO-LayerPreferenceConfigFR2-2, if configured; 2> release minSchedulingOffsetPreferenceConfigExt, if configured; 2> release multiRx-PreferenceReportingConfigFR2, if configured, and stop timer T440, if running; 2> release uav-FlightPathAvailabilityConfig, if configured; 2> release ul-TrafficInfoReportingConfig, if configured, and stop all instances of timer T346x, if running; 1> release successHO-Config, if configured; 1> release successPSCell-Config configured by the PCell, if configured; 1> release successPSCell-Config configured by the PSCell, if configured; 1> if any DAPS bearer is configured: 2> reset the source MAC and release the source MAC configuration; 2> for each DAPS bearer: 3> release the RLC entity or entities as specified in 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> release sl-L2RelayUE-Config, if configured; 1> release sl-L2RemoteUE-Config, if configured; 1> release the SRAP entity, if configured; 1> release NCR-FwdConfig, if configured; 1> if the UE is NCR-MT: 2> indicate to NCR-Fwd to cease forwarding; 1> if SL indirect path is configured: 2> release cell identity and relay UE ID configured in sl-IndirectPathAddChange; 2> indicate upper layers to trigger PC5 unicast link release of the SL indirect path; 1> if N3C indirect path is configured: 2> release n3c-IndirectPathAddChange; 2> consider the non-3GPP connection is not used; 1> if the UE is acting as a N3C relay UE: 2> release n3c-IndirectPathConfigRelay; 2> consider the non-3GPP connection is not used; 1> if the UE is acting as L2 U2N Remote UE and MP via L2 U2N Relay UE is not configured: 2> if the PC5-RRC connection with the U2N Relay UE is determined to be released: 3> indicate upper layers to trigger PC5 unicast link release; 3> perform either cell selection in accordance with the cell selection process as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ]  [20], or relay selection as specified in clause 5.8.15.3, or both; 2> else (i.e., maintain the PC5 RRC connection): 3> consider the connected L2 U2N Relay UE as suitable and perform actions as specified in clause 5.3.7.3a; NOTE 1: It is up to Remote UE implementation whether to release or keep the current PC5 unicast link. 1> else: 2> if the UE is capable of L2 U2N Remote UE: 3> perform either cell selection as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ]  [20], or relay selection as specified in clause 5.8.15.3, or both; 2> else: 3> perform cell selection in accordance with the cell selection process as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ]  [20]. NOTE 2: For L2 U2N Remote UE, if both a suitable cell and a suitable relay are available, the UE can select either one based on its implementation.