Content for  TS 38.300  Word version:  18.0.0

A Conditional Handover (CHO) is defined as a handover that is executed by the UE when one or more handover execution conditions are met. The UE starts evaluating the execution condition(s) upon receiving the CHO configuration, and stops evaluating the execution condition(s) once a handover is executed. The following principles apply to CHO:

• The CHO configuration contains the configuration of CHO candidate cell(s) generated by the candidate gNB(s) and execution condition(s) generated by the source gNB.
• An execution condition may consist of one or two trigger condition(s) (CHO events A3/A5, as defined in TS 38.331). Only single RS type is supported and at most two different trigger quantities (e.g. RSRP and RSRQ, RSRP and SINR, etc.) can be configured simultaneously for the evalution of CHO execution condition of a single candidate cell.
• Before any CHO execution condition is satisfied, upon reception of HO command (without CHO configuration), the UE executes the HO procedure as described in clause 9.2.3.2, regardless of any previously received CHO configuration.
• While executing CHO, i.e. from the time when the UE starts synchronization with target cell, UE does not monitor source cell.

CHO is also supported for the IAB-MT in context of intra- and inter-donor IAB-node migration and BH RLF recovery. CHO is not supported for NG-C based handover in this release of the specification.

As in intra-NR RAN handover, in intra-NR RAN CHO, the preparation and execution phase of the conditional handover procedure is performed without involvement of the 5GC; i.e. preparation messages are directly exchanged between gNBs. The release of the resources at the source gNB during the conditional handover completion phase is triggered by the target gNB. The Figure below depicts the basic conditional handover scenario where neither the AMF nor the UPF changes:

The U-plane handling for Conditional Handover follows the same principles for DAPS handover in clause 9.2.3.2.2, if early data forwarding is applied, except that, in case of Full Configuration, HFN and PDCP SN are reset in the target gNB after the SN assignment is handed over to the target gNB. If late data forwarding is applied, the U-plane handling follows the RLC-AM or RLC-UM bearer principles defined in clause 9.2.3.2.2.

If late data forwarding is applied, the source NG-RAN node initiates data forwarding once it knows which target NG-RAN node the UE has successfully accessed. In that case the behavior of the Conditional Handover data forwarding follows the same behavior as defined in clause 9.2.3.2.3 for the intra-system handover data forwarding, except the behavior for DRBs configured with DAPS handover. If early data forwarding is applied instead, the source NG-RAN node initiates data forwarding before the UE executes the handover, to a candidate target node of interest. The behavior of early data forwarding for the Conditional Handover follows the same principles for DRBs configured with DAPS handover in the intra-system handover as defined in clause 9.2.3.2.3.

LTM is a procedure in which a gNB receives L1 measurement report(s) from a UE, and on their basis the gNB changes UE serving cell by a cell switch command signalled via a MAC CE. The cell switch command indicates an LTM candidate configuration that the gNB previously prepared and provided to the UE through RRC signalling. Then the UE switches to the target configuration according to the cell switch command. The LTM procedure can be used to reduce the mobility latency as described in Annex G. When configured by the network, it is possible to activate TCI states of one or multiple cells that are different from the current serving cell. For instance, the TCI states of the LTM candidate cells can be activated in advance before any of those cells become the serving cell. This allows the UE to be DL synchronized with those cells, thereby facilitating a faster cell switch to one of those cells when cell switch is triggered. When configured by the network, it is possible to initiate UL TA acquisition (called early TA) procedure of one or multiple cells that are different from the current serving cells. If the cell has the same NTA as the current serving cells or NTA=0, early TA acquisition procedure is not required. The network may request the UE to perform early TA acquisition of a candidate cell before a cell switch. The early TA acquisition procedure is triggered by PDCCH order as specified in clause 9.2.6 or realized through UE-based TA measurement as configured by RRC. In the former case, the gNB to which the candidate cell belongs calculates the TA value and sends it to the gNB to which the serving cell belongs. The serving cell sends the TA value in the LTM cell switch command MAC CE when triggering LTM cell switch. In the latter case, the UE performs TA measurement for the candidate cells after being configured by RRC but the exact time the UE performs TA measurement is up to UE implementation. The UE applies the TA value measured by itself and performs RACH-less LTM upon receiving the cell switch command. The network may also send a TA value in the LTM cell switch command MAC CE without early TA acquisition. Depending on the availability of a valid TA value, the UE performs either a RACH-less LTM or RACH-based LTM cell switch. If the TA value is provided in the cell switch command, the UE applies the TA value as instructed by the network. In the case where UE-based TA measurement is configured, but no TA value is provided in the cell switch command, the UE applies the TA value by itself if available. Meanwhile, the UE performs RACH-less LTM cell switch upon receiving the cell switch command. If no valid TA value is available, the UE performs RACH-based LTM cell switch. Regardless of whether the UE is configured for UE-based TA measurement for a certain candidate cell, it will still follow the PDCCH order, which includes requesting a random access procedure towards the candidate cells. This also applies to the candidate cells for which the UE is capable of deriving TA values by itself. Additionally, regardless of whether the UE has already performed a random access procedure towards the candidate cells, it will still follow the UE-based measurement configuration if configured by the network. For RACH-less LTM, the UE accesses the target cell using either a configured grant or a dynamic grant. The configured grant is provided in the LTM candidate configuration, and the UE selects the configured grant occasion associated with the beam indicated in the cell switch command. Upon initiation of LTM cell switch to the target cell, the UE starts to monitor PDCCH on the target cell for dynamic scheduling. Before RACH-less LTM procedure completion, the UE shall not trigger random access procedure if it does not have a valid PUCCH resource for triggered SRs. The following principles apply to LTM:

• Security key is maintained upon an LTM cell switch;
• Subsequent LTM is supported.

LTM supports both intra-gNB-DU and intra-gNB-CU inter-gNB-DU mobility. LTM supports both intra-frequency and inter-frequency mobility, including mobility to inter-frequency cell that is not a current serving cell. LTM is supported only for licensed spectrum. The following scenarios are supported:

• PCell change in non-CA scenario and non-DC scenario;
• PCell and SCell(s) change in CA scenario;
• Dual connectivity scenario, PCell and MCG SCell(s) change and intra-SN PSCell and SCG SCell(s) change without MN involvement. LTM for simultaneous PCell and PSCell change is not supported.

While the UE has stored LTM candidate configurations the UE can also execute any L3 handover command sent by the network.

Cell switch command is conveyed in a MAC CE, which contains the necessary information to perform the LTM cell switch. The overall procedure for LTM is shown in Figure 9.2.3.5.2-1 below. Subsequent LTM is done by repeating the early synchronization, LTM cell switch execution, and LTM cell switch completion steps without releasing other LTM candidate configurations after each LTM cell switch completion. The general procedure over the air interface is applicable to SCG LTM. Further details of SCG LTM can be found in TS 37.340.

The procedure for LTM is as follows: The steps 4-8 can be performed multiple times for subsequent LTM using the LTM candidate configuration(s) provided in step 2. The procedure over the air interface described in Figure x is applicable to both intra-gNB-DU LTM and inter-gNB-DU LTM. The overall LTM procedures over F1-C interface are captured in TS 38.401.

After receiving an LTM cell switch command MAC CE, the UE performs MAC reset. Whether the UE performs RLC re-establishment and PDCP data recovery during cell switch is explicitly controlled by the network through RRC signalling.