Section: 5.3.5.5.2 Reconfiguration with sync
Content: The UE shall perform the following actions to execute a reconfiguration with sync. 1> if the AS security is not activated, perform the actions upon going to RRC_IDLE as specified in 5.3.11 with the release cause 'other' upon which the procedure ends; 1> stop timer T430 if running; 1> if no DAPS bearer is configured: 2> stop timer T310 for the corresponding SpCell, if running; 1> if this procedure is executed for the MCG: 2> if timer T316 is running; 3> stop timer T316; 3> if the UE supports RLF-Report for fast MCG recovery procedure: 4> set the elapsedTimeT316 in the VarRLF-Report to the value of the elapsed time of the timer T316; 4> set the pSCellId to the global cell identity of the PSCell, if available, otherwise to the physical cell identity and carrier frequency of the PSCell; 3> else: 4> clear the information included in VarRLF-Report, if any; 2> resume MCG transmission, if suspended. 1> stop timer T312 for the corresponding SpCell, if running; 1> if sl-PathSwitchConfig is included: 2> consider the target L2 U2N Relay UE to be the one indicated by the targetRelayUE-Identity in the sl-PathSwitchConfig; 2> start timer T420 for the corresponding target L2 U2N Relay UE with the timer value set to t420, as included in the sl-PathSwitchConfig; 2> apply the value of the newUE-Identity as the C-RNTI; 2> indicate to upper layer (to trigger the PC5 unicast link establishment) with the target L2 U2N Relay UE indicated by the targetRelayUE-Identity; 2> apply the default configuration of SL-RLC1 as defined in 9.2.4 for SRB1; 1> else (sl-PathSwitchConfig is not included): 2> if this procedure is executed for the MCG or if this procedure is executed for an SCG not indicated as deactivated in the E-UTRA or NR RRC message in which the RRCReconfiguration message is embedded: 3> start timer T304 for the corresponding SpCell with the timer value set to t304, as included in the reconfigurationWithSync; 2> if the frequencyInfoDL is included: 3> consider the target SpCell to be one on the SSB frequency indicated by the frequencyInfoDL with a physical cell identity indicated by the physCellId; 2> else: 3> consider the target SpCell to be one on the SSB frequency of the source SpCell with a physical cell identity indicated by the physCellId; 2> start synchronising to the DL of the target SpCell; 2> apply the specified BCCH configuration defined in 9.1.1.1 for the target SpCell; 2> acquire the MIB of the target SpCell, which is scheduled as specified in TS 38.213[ NR; Physical layer procedures for control ]  [13]; 2> if NTN-Config is configured for the target cell: 3> start timer T430 with the timer value set to ntn-UlSyncValidityDuration from the subframe indicated by epochTime, according to the target cell NTN-Config; NOTE 1: The UE should perform the reconfiguration with sync as soon as possible following the reception of the RRC message triggering the reconfiguration with sync, which could be before confirming successful reception (HARQ and ARQ) of this message. NOTE 2: The UE may omit reading the MIB if the UE already has the required timing information, or the timing information is not needed for random access. NOTE 2a: A UE with DAPS bearer does not monitor for system information updates in the source PCell. 2> If any DAPS bearer is configured: 3> create a MAC entity for the target cell group with the same configuration as the MAC entity for the source cell group; 3> for each DAPS bearer: 4> establish an RLC entity or entities for the target cell group, with the same configurations as for the source cell group; 4> establish the logical channel for the target cell group, with the same configurations as for the source cell group; NOTE 2b: In order to understand if a DAPS bearer is configured, the UE needs to check the presence of the field daps-Config within the RadioBearerConfig IE received in radioBearerConfig or radioBearerConfig2. 3> for each SRB: 4> establish an RLC entity for the target cell group, with the same configurations as for the source cell group; 4> establish the logical channel for the target cell group, with the same configurations as for the source cell group; 3> suspend SRBs for the source cell group; NOTE 3: Void 3> apply the value of the newUE-Identity as the C-RNTI in the target cell group; 3> configure lower layers for the target SpCell in accordance with the received spCellConfigCommon; 3> configure lower layers for the target SpCell in accordance with any additional fields, not covered in the previous, if included in the received reconfigurationWithSync. 2> else: 3> reset the MAC entity of this cell group; 3> consider the SCell(s) of this cell group, if configured, that are not included in the SCellToAddModList in the RRCReconfiguration message, to be in deactivated state; 3> apply the value of the newUE-Identity as the C-RNTI for this cell group; 3> configure lower layers in accordance with the received spCellConfigCommon; 3> if rach-LessHO is included: 4> configure lower layers in accordance with rach-LessHO for the target SpCell; 3> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received reconfigurationWithSync. 2> if the UE is acting as L2 U2N Remote UE at the source side: 3> indicate upper layer to trigger PC5 unicast link release. Upon L2 U2N Relay UE receiving reconfigurationWithSync, it either indicates to upper layers (to trigger PC5 unicast link release) or sends NotificationMessageSidelink message to the connected L2 U2N Remote UE(s) in accordance with 5.8.9.10.