Enabling measurement for inter-central unit lower layer triggered mobility in dual connectivity

Abstract

This disclosure provides systems, devices, apparatus, and methods, including computer programs encoded on storage media, for configuring measurements for inter-central unit lower layer triggered mobility in dual connectivity. A radio access node, RAN, node (104A) transmits, to a master node, MN, (104B) a secondary node, SN, required message. The RAN node (104A) receives, from the MN, in response to the SN required message, a SN acknowledgement message including a lower-layer triggered mobility, LTM, candidate cell configuration. The RAN node (104A) generates a channel state information, CSI, report configuration based on a reference signal resource configuration. The RAN node (104A) transmits, to a user equipment, UE, (102), the LTM candidate cell configuration, the reference signal resource configuration, and the CSI report configuration associated with an LTM candidate cell.

Description

ENABLING MEASUREMENT FOR INTER-CENTRAL UNIT LOWER LAYER TRIGGERED MOBILITY IN DUAL CONNECTIVITYCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No. US 63 / 563.196, filed 8 March 2024. The disclosure of which is incorporated herein by reference in its entirety.FIELD OF THE DISCLOSURE

[0002] This disclosure relates to wireless communications and, more particularly, to enabling lower-layer measurement (e.g., Layer 1 measurement) for inter-central unit lower layer triggered mobility in dual connectivity7.SUMMARY

[0003] This background description is provided for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherw ise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

[0004] In telecommunication systems, the Packet Data Convergence Protocol (PDCP) sublayer of the radio protocol stack provides services such as transfer of user-plane data, ciphering, integrity' protection, etc. For example, the PDCP layer defined for the Evolved Universal Terrestrial Radio Access (EUTRA) radio interface (see 3GPP specification TS 36.323) and New Radio (NR) (see 3GPP specification TS 38.323) provides sequencing of protocol data units (PDUs) in the uplink direction (from a user device, also known as a user equipment (UE), to a base station) as well as in the downlink direction (from the base station to the UE). Further, the PDCP sublayer provides signaling radio bearers (SRBs) and data radio bearers (DRBs) to the Radio Resource Control (RRC) sublay er. Generally speaking, the UE and a base station can use SRBs to exchange RRC messages as well as non-access stratum (NAS) messages, and can use DRBs to transport data on a user plane.

[0005] UEs can use several types of SRBs and DRBs. When operating in dual connectivity (DC), the cells associated with the base station operating the master node (MN) define a master cell group (MCG), and the cells associated with the base station operating as the secondary7node (SN) define the secondary7cell group (SCG). So-called SRB1 resources carry RRCmessages, which in some cases include NAS messages over the dedicated control channel (DCCH), and SRB2 resources support RRC messages that include logged measurement information or NAS messages, also over the DCCH but with lower priority than SRB1 resources. More generally, SRB1 and SRB2 resources allow the UE and the MN to exchange RRC messages related to the MN and embed RRC messages related to the SN, and also can be referred to as MCG SRBs. SRB3 resources allow the UE and the SN to exchange RRC messages related to the SN, and can be referred to as SCG SRBs. Split SRBs allow the UE to exchange RRC messages directly with the MN via lower layer resources of the MN and the SN. Further. DRBs using the lower-layer resources of only the MN can be referred as MCG DRBs, DRBs using the lower-layer resources of only the SN can be referred as SCG DRBs, and DRBs using the lower-layer resources of both the MCG and the SCG can be referred to as split DRBs.

[0006] The UE in some scenarios can concurrently utilize resources of multiple radio access network (RAN) nodes (e.g., base stations or components of a distributed base station), interconnected by a backhaul. When these network nodes support different radio access technologies (RATs), this type of connectivity is referred to as Multi-Radio Dual Connectivity (MR-DC). When a UE operates in MR-DC, one base station operates as a master node (MN) that covers a primary cell (PCell), and the other base station operates as a secondary node (SN) that covers a primary secondary cell (PSCell). The UE communicates with the MN (via the PCell) and the SN (via the PSCell). In other scenarios, the UE utilizes resources of one base station at a time. One base station and / or the UE determines that the UE should establish a radio connection with another base station. For example, one base station can determine to hand the UE over to the second base station, and initiate a handover procedure.

[0007] When the UE moves from coverage area of one cell to another cell in a RAN, at some point a serving cell change has to be performed for the UE. To perform the serving cell change, the RAN configures the UE to transmit Layer 3 (L3) measurement results. Based on L3 measurement results received from the UE, the RAN transmits a RRC reconfiguration message configuring Reconfiguration with Synchronization (e.g., the RRC reconfiguration message includes a ReconftgurationWithSync IE) for change of the serving cell (e.g., PCell or PSCell). In cases where the UE operates in carrier aggregation (CA) of at least one secondary cell (SCell) with the PCell or PSCell, the RAN has to release the at least one SCell due to the change of the PCell or PSCell. The serving cell change involves complete L2 (and LI) resets, leading to longer latency, larger overhead and longer interruption time. Thus, 3 GPP has introduced.

[0008] While a base station of the RAN communicates with the UE via a serving cell, the base station receives one or more layer 3 (e.g., RRC) measurement results from the UE. The base station consists of a central unit (CU) and one or more distributed units (DUs). One of the DU(s) operating the serving cell is a serving DU. Based on the layer 3 (L3) measurement result(s), the base station determines to configure a LTM candidate cell for LTM cell switch. To configure the LTM candidate cell for the UE, the base station transmits a LTM candidate configuration configuring the LTM candidate cell to the UE via RRC signaling. Later on, the base station receives one or more layer 1 (LI) measurement results from the UE. Based on the one or more LI measurement result(s), the base station determines that the LTM candidate cell qualifies to be a serving cell for the UE. Therefore, the base station transmits a LTM cell switch command to the UE to command the UE to perform the LTM cell switch to the LTM candidate cell. The UE performs a cell change from the serving cell to the LTM candidate cell in response to the LTM cell switch command. If the LTM candidate cell is operated by the serving DU. the LTM cell switch is an intra-CU intra-DU LTM cell switch. If the LTM candidate cell is operated by a candidate DU in the DU(s), the LTM cell switch is an intra-CU inter-DU LTM cell switch. 3 GPP has enabled the intra-CU intra-DU LTM cell switch and intra-CU inter-DU LTN cell switch in Release 18 specifications. However. 3GPP has not specified inter-CU LTM cell switch yet.BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Fig. 1A is a block diagram of an example system in which a radio access network (RAN) and a user device can implement the techniques of this disclosure for managing conditional procedures related to a secondary node (SN) according to some embodiments.

[0010] Fig. IB is another block diagram of an example system in which a radio access network (RAN) and a user device can implement the techniques of this disclosure for managing conditional procedures related to an MN or an SN according to some embodiments.

[0011] Fig. 1C is a block diagram of an example base station including a central unit (CU) and a distributed unit (DU) that can operate in the system of Fig. 1A or Fig. IB according to some embodiments.

[0012] Fig. 2A is a block diagram of an example protocol stack according to which the UE of Fig. 1 A communicates with base stations according to some embodiments.

[0013] Fig. 2B is a block diagram of an example protocol stack according to which the UE of Fig. 1 A communicates with a CU and a DU according to some embodiments.

[0014] Figs. 3-6E are signal flow diagrams for configuring measurements for inter-CU LTM according to some embodiments.

[0015] Fig. 7A illustrates an example method 700A, which can be implemented by an S-SN (e.g., the S-SN 104A in Figs. 6A-6D) according to some embodiments.

[0016] Fig. 7B is a flow diagram of an example method 700B similar to the method 700A, except that the method 700B includes block 709B instead of blocks 709A and 762 according to some embodiments.

[0017] Fig. 8A illustrates an example method 800A similar to the method 700A, which can be implemented by a CU of an S-SN (e.g., the S-SN 104A of Figs. 6A-6D) according to some embodiments.

[0018] Fig. 8B is a flow diagram of an example method 800B similar to the methods 800A and 700B, except that the method 800B includes block 709B instead of blocks 709A and 762. according to some embodiments.

[0019] Fig. 9A illustrates an example method 900 A. which can be implemented by a MN (e.g.. the MN 104B in Figs. 6A-6D) according to some embodiments.

[0020] Fig. 9B is a flow diagram of an example method 900B similar to the method 900A, except that the method 900B includes block 907B instead of blocks 907A and 962 according to some embodiments.

[0021] Fig. 10A illustrates an example method 1000A similar to the method 900A, which can be implemented by a CU of an MN (e.g., the MN 104B of Figs. 6A-6D) according to some embodiments.

[0022] Fig. 10B is a flow diagram of an example method 1000B similar to the method 1000A and 900B, except that the method 1000B includes block 907B instead of blocks 907A and 962 according to some embodiments.

[0023] Fig. 11 illustrates an example method 1100, which can be implemented by a C-SN (e.g., the C-SN 106A of Figs. 6A-6D) according to some embodiments.

[0024] Fig. 12 illustrates an example method 1200. which can be implemented by a CU of a C-SN (e g., the C-SN 106A of Figs. 6A-6D) according to some embodiments.

[0025] Fig. 13A illustrates an example method 1300A similar to the method 700A, which can be implemented by an S-SN (e.g., the S-SN 104A in Figs. 6A-6D), except that the method1300A includes blocks 1372, 1374, 1318, and 1324 instead of blocks 762, 764, 718, and 724 according to some embodiments.

[0026] Fig. 13B illustrates an example method 1300B similar to the method 1300A, which can be implemented by an S-SN (e.g., the S-SN 104A in Figs. 6A-6D), except that the method 1300A includes blocks 1309B instead of blocks 709A and 1372 according to some embodiments.

[0027] Fig. 14 illustrates an example method 1400 similar to the method 1100, which can be implemented by a C-SN (e.g., the C-SN 106A in Figs. 6A-6D), except that the method 1400 includes blocks 1472 and 1474 instead of blocks 1162 according to some embodiments.

[0028] Fig. 15 illustrates an example method 1500 similar to the methods 1100, 1200 and 1400, which can be implemented by a CU of a C-SN (e.g., the C-SN 106A of Figs. 6A-6D) according to some embodiments.DETAILED DESCRIPTION

[0029] Fig. 1A depicts an example wireless communication system 100 in which communication devices can implement these techniques. The wireless communication system 100 includes a UE 102, a base station (BS) 104 A, a base station 106A and a core network (CN) 110. The UE 102 initially connects to the base station 104A. In some scenarios, the base station 104 A can perform an SN addition to configure the UE 102 to operate in dual connectivity (DC) with the base station 104A and the base station 106A. The base stations 104A and 106A operate as an MN and an SN for the UE 102, respectively.

[0030] In various configurations of the wireless communication system 100, the base station 104A can be implemented as a master eNB (MeNB) or a master gNB (MgNB), and the base station 106A can be implemented as a secondary gNB (SgNB). The UE 102 can communicate with the base station 104A and the base station 106 A via the same RAT such as EUTRA or NR, or different RATs. When the base station 104A is an MeNB and the base station 106A is a SgNB, the UE 102 can be in EUTRA-NR DC (EN-DC) with the MeNB and the SgNB.

[0031] In some cases, an MeNB or an SeNB is implemented as an ng-eNB rather than an eNB. When the base station 104A is a Master ng-eNB (Mng-eNB) and the base station 106A is a SgNB. the UE 102 can be in next generation (NG) EUTRA-NR DC (NGEN-DC) with the Mng-eNB and the SgNB. When the base station 104A is an MgNB and the base station 106A is an SgNB, the UE 102 may be in NR-NR DC (NR-DC) with the MgNB and the SgNB. Whenthe base station 104A is an MgNB and the base station 106 A is a Secondary ng-eNB (Sng- eNB), the UE 102 may be in NR-EUTRA DC (NE-DC) with the MgNB and the Sng-eNB.

[0032] In the scenarios where the UE 102 hands over from the base station 104Ato the base station 106A, the base stations 104A and 106A operate as the source base station (S-BS) and a target base station (T-BS), respectively. The UE 102 can operate in DC with the base station 104 A and an additional base station (not shown in Fig. 1 A) for example prior to the handover. The UE 102 can continue to operate in DC with the base station 106A and the additional base station or operate in single connectivity (SC) with the base station 106 A, after completing the handover. The base stations 104A and 106A in this case operate as a source MN (S-MN) and a target MN (T-MN). respectively.

[0033] A core network (CN) 110 can be an evolved packet core (EPC) 111 or a fifthgeneration core (5GC) 160, both of which are depicted in Fig. 1A. The base station 104A can be an eNB supporting an SI interface for communicating with the EPC 111, an ng-eNB supporting an NG interface for communicating with the 5GC 160, or a gNB that supports an NR radio interface as well as an NG interface for communicating with the 5GC 160. To directly exchange messages with each other during the scenarios discussed below, the base stations 104 A and 106A can support an X2 or Xn interface. Among other components, the EPC 111 can include a Serving Gateway (SGW) 112, a Mobility Management Entity7(MME) 114, and a Packet Data Network Gateway (PGW) 116. The SGW 112 is generally configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., and the MME 114 is configured to manage authentication, registration, paging, and other related functions. The PGW 116 provides connectivity7from the UE to one or more external packet data networks, e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network. The 5GC 160 includes a User Plane Function (UPF) 162 and an Access and Mobility Management (AMF) 164, and / or Session Management Function (SMF) 166. The UPF 162 is generally configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., the AMF 164 is configured to manage authentication, registration, paging, and other related functions, and the SMF 166 is configured to manage PDU sessions.

[0034] As illustrated in Fig. 1A, the base station 104A supports cell 124 A, and the base station 106A supports a cell 126A. The cells 124A and 126A can partially overlap, so that the UE 102 can communicate in DC with the base station 104 A and the base station 106 A, where one of the base stations 104A and 106A is an MN and the other is an SN. The base station104 A can support additional cell(s) such as cells 124B and 124C, and the base station 106 A can support additional cell(s) (not shown in Fig. 1A). The cells 124A, 124B and 124C can partially overlap, so that the UE 102 can communicate in carrier aggregation (CA) with the base station 104A. The base station 104A can operate the cells 124A, 124B and 124C via one or more transmit and receive points (TRPs). More particularly, when the UE 102 is in DC with the base station 104A and the base station 106A, one of the base stations 104A and 106A operates as an MeNB, an Mng-eNB or an MgNB, and the other operates as an SgNB or an Sng- eNB.

[0035] In general, the wireless communication network 100 can include any suitable number of base stations supporting NR cells and / or EUTRA cells. More particularly, the EPC 111 or the 5GC 160 can be connected to any suitable number of base stations supporting NR cells and / or EUTRA cells. An example configuration in which the CN 110 is connected to additional base stations is discussed below with reference to Fig. IB. Although the examples below refer specifically to specific CN types (EPC, 5GC) and RAT t pes (5GNR and EUTRA), in general the techniques of this disclosure also can apply to other suitable radio access and / or core network technologies such as sixth generation (6G) radio access and / or 6G core network or 5G NR-6G DC.

[0036] With continued reference to Fig. 1A, the base station 104A is equipped with processing hardware 130 that can include one or more general-purpose processors (e.g., CPUs) and a non-transitory computer-readable memory storing instructions that the one or more general-purpose processors execute. Additionally or alternatively, the processing hardware 130 can include special -purpose processing units. The processing hardware 130 can include a PHY controller 132 configured to transmit data and control signal on physical downlink (DL) channels and DL reference signals with one or more user devices (e.g., UE 102) via one or more cells (e.g., the cell(s) 124A. 124B and / or 124C) and / or one or more TRPs. The PHY controller 132 is also configured to receive data and control signal on physical uplink (UL) channels and / or UL reference signals with the one or more user devices via one or more cells (e.g., the cell(s) 124A, 124B and / or 124C) and / or one or more TRPs. The processing hardware 130 in an example implementation includes a MAC controller 134 configured to perform MAC functions with one or more user devices. The MAC functions include a random access (RA) procedure, managing UL timing advance (TA) for the one or more user devices, and / or communicating UL / DL MAC PDUs with the one or more user devices. The MAC functions include lower triggered mobility (LTM) related functions as described below. The processinghardware 130 can further include an RRC controller 136 to implement procedures and messaging at the RRC sublayer of the protocol communication stack. For example, the RRC controller 132 may be configured to support RRC messaging associated with handover procedures, and / or to support the necessary operations when the base station 104A operates as an MN relative to an SN or as an SN relative to an MN. The base station 106A can include processing hardware 140 that is similar to processing hardware 130. In particular, components 142, 144, and 146 can be similar to the components 132, 134, and 136, respectively.

[0037] The UE 102 is equipped with processing hardware 150 that can include one or more general-purpose processors such as CPUs and non-transitory computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or special-purpose processing units. The PHY controller 152 is also configured to receive data and control signal on physical DL channels and / or DL reference signals with the base station 104A or 106A via one or more cells (e.g., the cell(s) 124A, 124B, 124C and / or 126 A) and / or one or more TRPs. The PHY controller 152 is also configured to transmit data and control signal on physical UL channels and / or UL reference signals with the base station 104A or 106A via one or more cells (e.g., the cell(s) 124A, 124B, 124C and / or 126A) and / or one or more TRPs. The processing hardware 150 in an example implementation includes a MAC controller 154 configured to perform MAC functions with base station 104A or 106A. For example, the MAC functions includes a random access procedure, managing UL timing advance for the one or more user devices, and communicating UL / DL MAC PDUs with the base station 104A or 106 A. In another example, the MAC functions includes LTM related functions as described below. The processing hardware 150 can further include an RRC controller 156 to implement procedures and messaging at the RRC sublayer of the protocol communication stack.

[0038] In operation, the UE 102 in DC can use a radio bearer (e.g., a DRB or an SRB) that at different times terminates at the MN 104A or the SN 106 A. The UE 102 can apply one or more security keys when communicating on the radio bearer, in the uplink (UL) (from the UE 102 to a base station) and / or downlink (from a base station to the UE 102) direction.

[0039] Fig. 1C depicts an example distributed implementation of a base station such as the base station 104A or 106A. The base station in this implementation can include a centralized unit (CU) 172 and one or more distributed units (DUs) 174. The CU 172 is equipped with processing hardware that can include one or more general -purpose processors such as CPUsand non-transitory computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or special-purpose processing units. In one example, the CU 172 is equipped with the processing hardware 130. In another example, the CU 172 is equipped with the processing hardware 140. The processing hardware 140 in an example implementation includes an SN RRC controller 142 configured to manage or control one or more RRC configurations and / or RRC procedures when the base station 106A operates as an SN. The DU 174A is also equipped with processing hardware that can include one or more general-purpose processors such as CPUs and non-transitory computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or special-purpose processing units. In some examples, the processing hardware in an example implementation includes a medium access control (MAC) controller configured to manage or control one or more MAC operations or procedures (e g., a random access procedure) and a radio link control (RLC) controller configured to manage or control one or more RLC operations or procedures when the base station 106 A operates as an MN or an SN. The process hardware may include further a physical layer controller configured to manage or control one or more physical layer operations or procedures.

[0040] Fig. 2A illustrates, in a simplified manner, an example protocol stack 200 according to which the UE 102 can communicate with an eNB / ng-eNB or a gNB (e.g., one or more of the base stations 104A, 106A).

[0041] In the example stack 200, a physical layer (PHY) 202A of EUTRA provides transport channels to the EUTRA MAC sublayer 204A, which in turn provides logical channels to the EUTRA RLC sublayer 206 A. The EUTRA RLC sublayer 206Ain turn provides RLC channels to an EUTRA PDCP sublayer 208 and, in some cases, to an NR PDCP sublayer 210. Similarly, the NR PHY 202B provides transport channels to the NR MAC sublayer 204B, which in turn provides logical channels to the NR RLC sublayer 206B. The NR RLC sublayer 206B in turn provides data transfer services to the NR PDCP sublayer 210. The NR PDCP sublayer 210 in turn can provide data transfer services to Sendee Data Adaptation Protocol (SDAP) 212 or a radio resource control (RRC) sublayer (not shown in Fig. 2A). The UE 102, in some implementations, supports both the EUTRA and the NR stack as shown in Fig. 2A, to support handover between EUTRA and NR base stations and / or to support DC over EUTRA and NR interfaces. Further, as illustrated in Fig. 2A, the UE 102 can support layering of NR PDCP 210 over EUTRA RLC 206A, and SDAP sublayer 212 over the NR PDCP sublayer 210.

[0042] The EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 receive packets (e.g., from an Internet Protocol (IP) layer, layered directly or indirectly over the PDCP layer 208 or 210) that can be referred to as service data units (SDUs), and output packets (e.g., to the RLC layer 206A or 206B) that can be referred to as protocol data units (PDUs). Except where the difference between SDUs and PDUs is relevant, this disclosure for simplicity refers to both SDUs and PDUs as "packets."

[0043] On a control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 can provide signaling radio bearers (SRBs) or RRC sublayer (not shown in Fig. 2A) to exchange RRC messages or non-access-stratum (NAS) messages, for example. On a user plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 can provide Data Radio Bearers (DRBs) to support data exchange. Data exchanged on the NR PDCP sublayer 210 can be SDAP PDUs, Internet Protocol (IP) packets or Ethernet packets.

[0044] Fig. 2B illustrates, in a simplified manner, an example protocol stack 250, which the UE 102 can communicate with a DU (e.g., DU 174) and a CU (e.g., CU 172). The radio protocol stack 200 is functionally split as shown by the radio protocol stack 250 in Fig. 2B. The CU at any of the base stations 104A or 106A can hold all the control and upper layer functionalities (e.g., RRC 214, SDAP 212, NR PDCP 210), while the lower layer operations (e.g., NR RLC 206B, NR MAC 204B, and NR PHY 202B) are delegated to the DU. To support connection to a 5GC, NR PDCP 210 provides SRBs to RRC 214, and NR PDCP 210 provides DRBs to SDAP 212 and SRBs to RRC 214.

[0045] Next, several example scenarios in which the base station operating in the system of Fig. 1A transmits a configuration to the UE 102 and later activates a configuration for communication between the UE 102 and base station. Generally speaking, events in Figs. 3-5 that are similar are labeled with similar reference numbers (e.g., event 302 is similar to event 402 of Fig. 4 and event 502 of Fig. 5, event 390 is similar to event 490 of Fig. 4 and event 590 of Fig. 5), with differences discussed below where appropriate. With the exception of the differences shown in the figures and discussed below, any of the alternative implementations discussed with respect to a particular event (e.g., for messaging and processing) may apply to events labeled with similar reference numbers in other figures.

[0046] Referring first to Fig. 3, in a scenario 300, the base station 104A includes a CU 172 and DU 174 and the DU 174 operates the cell 124A. The UE 102 initially communicates 302 with the DU 174 on a serving cell (e.g., the cell 124A), using a serving DU configuration, andcommunicates with the CU 172 via the DU 174, using a serving CU configuration. The DU 174 is a serving or a source DU (S-DU) for the UE 102. In other words, the DU 174 is a serving DU (S-DU) that is communicating with the UE 102. In some implementations, the UE 102 in earner aggregation (CA) communicates with the DU 174 on the cell 124A and other cell(s) (e.g., cell 124D not shown in Fig. 1A) using the serving DU configuration. The DU 174 operates the other cell(s). The cell 124A and / or the other cell(s) are serving cell(s) for the UE 102. In other implementations, the UE 102 communicates with the DU 174 on the cell 124A only. In some implementations, the UE 102 communicates with the DU 174 on the cell 124A and / or other cell(s) (i.e., serving cell(s)) via one or multiple TRPs. In the following description, events 394, 324, 350, 352, 354, and 326 occur on the serving cell(s). In some implementations, the cell 124A can be a PCell. In such cases, the other cell(s) include SCell(s) and / or additional cell(s) associated with the PCell or a SCell. In other implementations, the cell 124A can be a SCell, and one of the other cell(s) is a PCell. In such cases, the rest includes SCell(s) and / or additional cell(s) associated with the PCell or a SCell. In the following description, the base station 104A can be the DU 174, the CU 172 or the DU 174 and CU 172.

[0047] In the event 302, the UE 102 can transmit UL PDUs and / or UL control signals to the base station 104A on the cell 124A and / or other cell(s) via one or multiple TRPs. In some implementations, the UE 102 communicates UL PDUs and / or DL PDUs with the base station 104A via radio bearers which can include SRBs and / or DRB(s). The base station 104A can configure the radio bearers to the UE 102. In some implementations, UL control signals include UL control information, channel state information, hybrid automatic repeat request (HARQ) acknowledgements (ACKs), HARQ negative ACKs, scheduling request(s) and / or sounding reference signal(s). Similarly, the UE 102 can receive DL PDUs and / or DL control signals from the base station 104A on the cell 124A and / or other cell(s) via one or multiple TRPs. In some implementations, the DL control signals include downlink control information (DCIs) and reference signals (e.g., synchronization signal block, channel state information reference signal(s) (CSI-RS(s)), and / or tracking reference signal(s)). The base station 104A can transmit the DCIs on physical downlink control channel(s) (PDCCH(s)) monitored by the UE 102. on the cell 124A and / or other cell(s) via one or multiple TRPs.

[0048] In some implementations, the serving DU configuration includes physical layer configuration parameters, MAC configuration parameters, and / or RLC configuration parameters. In some implementations, the serv ing DU configuration includes at least one first non-LTM TCI state configuration for the serving cell(s). In some implementations, the DU 174can transmit these configuration parameters and / or the first non-LTM TCI state configuration(s) to the CU 172. The CU 172 generates one or more messages (e.g., RRC reconfiguration message(s)) including the configuration parameters and / or the first non-LTM TCI state configuration(s) and transmits the one or more messages to the UE 102 via the DU 174. In other implementations, the DU 174 transmits the configuration parameters and / or the first non-LTM TCI state configuration(s) to the UE 102 directly. In some implementations, the serving DU configuration is CellGroupConfig IE defined in 3GPP specification 38.331. In other implementations, the serving DU configuration includes configuration parameters in the CellGroupConfig IE. In some implementations, the serving CU configuration includes PDCP configuration parameters, measurement configuration parameters, and / or radio bearer configuration parameters. In some implementations, the serving CU configuration includes a MeasConfig IE and / or a RadioBearerConfig IE defined in 3GPP specification 38.331 or includes configuration parameters in the MeasConfig IE and / or RadioBearerConfig IE. The radio configuration parameters or the RadioBearerConfig IE configures one or more DRBs. In some implementations, the serving DU configuration includes a CSIMeasConfig IE or configuration parameters for channel state information (CSI) measurement and reporting. In other implementations, the serving CU configuration includes a CSI-MeasConftg IE or configuration parameters for CSI measurement and reporting. In some implementations, the UE 102 receives the serving CU configuration or the configuration parameters in the serving CU configuration from the CU 172 via the DU 174. In other implementations, the UE 102 receives a portion of the serving CU configuration and / or a portion of the serving DU configuration from a base station other than the base station 104A and the remaining portion of these configuration parameters from the base station 104A.

[0049] In some implementations, the DU 174 and the UE 102 communicate with each other using first non-LTM TCI state configuration(s), e.g., in the events 302, 318, 320, 324,350, 354, and / or 326. In some implementations, the DU 174 transmits at least one first non-LTM TCI States Activation / Deactivation command (e g., MAC control element (CE)) to the UE 102 to activate the first non-LTM TCI state configuration(s). The UE 102 activates the first non-LTM TCI state configuration(s) in response to the first non-LTM TCI States Activation / Deactivation command(s). In some implementations, the DU 174 includes a serving cell ID (e.g., a serving cell index) in each of the first non-LTM TCI States Activation / Deactivation command(s) to identify the first non-LTM TCI state configuration(s). Each of the serving cell ID(s) indicates a respective serving cell of the serving cell(s). In some implementations, the serving DUconfiguration includes the serving cell ID(s) and configures association(s) between the serving cell ID(s) and the first non-LTM TCI state configuration(s).

[0050] While communicating with the base station 104A, the UE 102 transmits 304 at least one measurement report to the DU 174. In some implementations, the measurement report(s) includes measurement results for a serving cell (e.g., the cell 124A) of the UE 102 and / or at least one non-serving cell. For each of the measurement report(s), the DU 174 transmits 306 a DU-to-CU message including the measurement report to the CU 172. In some implementations, the DU-to-CU message(s) of the event 306 is / are Fl application protocol (F1AP) message(s) (e.g., UL RRC Message Transfer message(s)). The at least one serving cell includes the cell 124A and / or other cell(s), and the at least one non-serving cell includes the cell 124B and / or additional cell(s). In some implementations, the serving CU configuration includes at least one measurement configuration. In accordance with the measurement configuration(s), the UE 102 performs measurements and transmits 304 the measurement report(s) to the DU 174. In some implementations, the measurement configuration(s) includes Layer 3 (L3) measurement configuration(s) (e.g., MeasConfig IE(s)) and the measurement report(s) include L3 measurement report(s).

[0051] After (e.g., in response to) receiving one or some of the measurement report(s) from the UE 102, the CU 172 determines to prepare a first cell (e.g., cell 1 such as the cell 124B) as a LTM candidate cell for the UE 102. In some implementations, the base station 104A determines to prepare the first cell for the UE 102 because the measurement report(s) indicates that the first cell could be used by the base station 104A to communicate with the UE 102. In some implementations, the base station 104A determines to prepare the first cell for the UE 102 because the measurement report(s) indicates that the first cell qualifies to be a LTM candidate cell that could be used for communication with the UE 102. In some implementations, if the L3 measurement report(s) indicates that signal strength and / or quality of the first cell is above a first predetermined threshold, is better than strength and / or quality of the serving cell (e.g., cell 124A), and / or is better than strength and / or quality of the serving cell by a first predetermined threshold, the CU 172 determines to prepare the first cell for the UE 102. Alternatively, the CU 172 determines to prepare the first cell for the UE 102 regardless of whether a measure report is received from the UE 102 or not.

[0052] In response to determining to prepare the first cell for LTM. the CU 172 transmits 308 a first CU-to-DU message to the DU 174 to prepare the first cell for the UE 102. In someimplementations, the CU 172 includes a cell identity (ID) 1 of the first cell in the first CU-to- DU message to request the DU 174 to prepare the first cell for LTM for the UE 102. For example, the cell ID 1 is cell global identity (CGI). In another example, the cell ID is a portion of the CGI. In yet another example, the cell ID is a physical cell ID (PCI). In some implementations, the CU 172 includes a LTM indicator in the first CU-to-DU message to indicate the DU 174 to prepare the first cell for LTM. In some implementations, the CU 172 includes the LTM indicator in a LTM Information Setup IE and includes the LTM Information Setup IE in the first CU-to-DU message. In yet other implementations, the CU 172 includes the LTM indicator in a LTM Information Modify IE and includes the LTM Information Modify IE in the first CU-to-DU message.

[0053] In response to the first CU-to-DU message, the DU 174 generates a first LTM DU configuration (referred to herein after as LTM DU configuration 1) for the UE 102, which configures the first cell for LTM. In some implementations, the CU 172 includes a first LTM configuration ID (i.e., referred to herein after as LTM ID 1) in the first CU-to-DU message and the DU 174 associates the LTM ID 1 and / or the cell ID 1 with the LTM DU configuration 1. The DU 174 then transmits 310 afirst DU-to-CU message including the LTM DU configuration 1 to the CU 172 in response to the first CU-to-DU message.

[0054] The events 308 and 310 are collectively referred to in Fig. 3 as a LTM preparation procedure 390.

[0055] In some implementations, the DU 174 includes, in the first DU-to-CU message, the cell ID 1 of the first cell associated with the LTM DU configuration 1 to indicate that the LTM DU configuration 1 is configured for or associated with the first cell. In cases where the CU 172 performs multiple LTM preparation procedures (e g., the procedure 390 and the LTM preparation procedure 2, ... , N described below) with the DU 174 to prepare multiple LTM candidate cells, the CU 172 can determine that the LTM DU configuration 1 is configured for or associated with the first cell, based on the cell ID 1 in the first DU-to-CU message.

[0056] In some implementations, the CU 172 does not include a LTM reference DU configuration in the first CU-to-DU message. In such cases, the DU 174 generates a LTM reference DU configuration and includes the LTM reference DU configuration in the first DU- to-CU message. In some implementations, the DU 174 generates the LTM DU configuration 1 as a delta configuration to augment the LTM reference DU configuration. In otherimplementations, the DU 174 generates the LTM DU configuration 1 as a complete configuration, i.e., not on top of the LTM reference DU configuration.

[0057] In some implementations, the CU 172 includes a LTM reference DU configuration request in the first CU-to-DU message, and the DU 174 generates the LTM reference DU configuration and includes the LTM reference DU configuration in the first DU-to-CU message in response to the request. In some implementations, the CU 172 determines whether the UE 102 supports a LTM reference configuration. If the CU 172 determines that the UE 102 supports a LTM reference configuration, the CU 172 includes the LTM reference DU configuration request in the first CU-to-DU message. The DU 174 includes the LTM reference DU configuration in the first DU-to-CU message in response to the LTM reference DU configuration request. Otherwise, if the CU 172 determines that the UE 102 does not support a LTM reference configuration, the CU 172 does not include the LTM reference DU configuration request in the first CU-to-DU message. In this case, the DU 174 may generate the LTM DU configuration 1 as a complete configuration and may not include a / the LTM reference DU configuration in the first DU-to-CU message. In other implementations, the CU 172 transmits an additional CU-to-DU message including the LTM reference DU configuration request to the DU 174 instead of the first CU-to-DU message. In response, the DU 174 includes an additional DU-to-CU message including the LTM reference DU configuration to the CU 172. In yet other implementations, the DU 174 determines whether the UE 102 supports a LTM reference configuration. If the DU 174 determines that the UE 102 supports a LTM reference configuration, the DU 174 includes the LTM reference DU configuration in the first DU-to-CU message. Otherwise, if the DU 174 determines that the UE 102 does not support a LTM reference configuration, the DU 174 does not include a / the LTM reference DU configuration in the first DU-to-CU message.

[0058] In some implementations, the CU 172 includes a LTM reference DU configuration in the first CU-to-DU message. In some implementations, the CU 172 receives the LTM reference DU configuration from an additional DU during a LTM preparation procedure as described above and for Fig. 4. In other implementations, the CU 172 is preconfigured with the LTM reference DU configuration. In some implementations, the DU 174 generates the LTM DU configuration 1 as a delta configuration to augment the LTM reference DU configuration. In other implementations, the DU 174 ignores the LTM reference DU configuration and generates the LTM DU configuration 1 as a complete configuration, i.e., not on top of the LTM reference DU configuration.

[0059] If the DU 174 generates the LTM DU configuration 1 as a complete configuration, the DU 174 may include a complete configuration indication in the first DU-to-CU message to indicate that the LTM DU configuration 1 is a complete configuration. In some implementations, if the first CU-to-DU message does not include a / the LTM reference DU configuration, the CU 172 may determine that the LTM DU configuration 1 as a complete configuration. Otherwise, if the first CU-to-DU message includes a / the LTM reference DU configuration, the CU 172 may determine that the LTM DU configuration 1 is a delta configuration.

[0060] In some implementations, the LTM reference DU configuration is different from the serving DU configuration. In some implementations, a portion of the LTM reference DU configuration is the same as a portion of the serving DU configuration and the rest of the LTM reference DU configuration is different from the rest of the serving DU configuration. In yet other implementations, the LTM reference DU configuration is the same as the serving DU configuration. In some implementations, the LTM reference DU configuration includes physical layer configuration parameters, MAC configuration parameters, and / or RLC configuration parameters. In some implementations, the LTM reference DU configuration is the CellGroupConfig IE defined in 3GPP specification 38.331. In other implementations, the LTM reference DU configuration includes configuration parameters in the CellGroupConfig IE. In some implementations, the LTM reference DU configuration includes a CSI-MeasConfig IE or configuration parameters for channel state information (CSI) measurement and / or reporting.

[0061] In some implementations, the LTM reference DU configuration is different from the serving DU configuration. In some implementations, a portion of the LTM reference DU configuration is the same as a portion of the serving DU configuration and the rest of the LTM reference DU configuration is different from the rest of the serving DU configuration. In other implementations, the LTM reference DU configuration is the same as the serving DU configuration.

[0062] To prepare the first cell as a LTM candidate cell for the UE 102, the CU 172 may transmit 312 a second CU-to-DU message to the DU 174, including a CSI resource configuration (e.g.. CSI resource configuration 1) and / or a LTM SSB configuration (i.e., LTM SSB configuration 1) to request the DU 174 to generate one or more CSI report configurations (e.g., (LTM) CSI report configuration(s) 1 ). The CSI resource configuration (e.g., (LTM) CSIresource configuration(s) 1) include configuration parameters configuring at least one reference signal (RS) transmitted on the first cell. The RS(s) include SSB(s) and / or CSI-RS(s). The LTM SSB configuration include SSB configuration parameters configuring a SSB frequency, a subcarrier spacing, a SSB periodicity. SSB positions and / or SSB power for SSB(s) transmitted on the first cell.

[0063] After (e.g.. in response to) receiving the CSI resource configuration, the DU 174 generates one or more CSI report configurations based on the CSI resource configuration and includes the CSI report configuration(s) in a serving DU configuration (referred to as a second serving DU configuration to distinguish from the serving DU configuration in event 302). In some implementations, the CSI report configuration(s) configures the UE 102 to transmit CSI reports based on measurements of the RS(s). The DU 174 transmits 314 a second DU-to-CU message including the second serving DU configuration to the CU 172. In some implementations, the CSI resource configuration comprises (e.g., is or includes) one or more LTM-CSI-ResourceConflg-r 18 IES. In other implementations, the CSI resource configuration comprises an Itm-CSI-ResourceConflgToAddModList field / IE. In some implementations, the second serving DU configuration is a CellGroupConfig IE.

[0064] In some implementations, the CU 172 includes the cell ID 1 and / or the LTM ID 1 in the second CU-to-DU message. In one implementation, the CU 172 does so to indicate that the CSI resource configuration is / are associated with the first cell. In another implementation, the CU 172 does so for the DU 174 to associate the LTM ID 1 with the first cell, the cell ID 1, the LTM DU configuration 1, and / or the CSI report configuration(s). Based on the above implementation(s), the DU 174 can associate the LTM ID 1 and / or the cell ID 1 with configurations (e.g., LTM DU configuration 1, the CSI resource configuration, and / or the CSI report configuration(s)) related to the first cell. In such implementations, the CU 172 may or may not include the LTM ID 1 in the first CU-to-DU message.

[0065] In some alternative implementations, the CU 172 includes the CSI resource configuration in the first CU-to-DU message and the DU 174 includes the CSI report configuration(s) in the first DU-to-CU message.

[0066] In some implementations, the DU 174 transmits the LTM SSB configuration or the SSB configuration parameters to the CU 172, e.g., in the first DU-to-CU message, the second DU-to-CU message or an additional DU-to-CU message. In some implementations, the DU 174 transmits the additional DU-to-CU message in response to receiving an additional CU-to-DU message from the CU 172. In other implementations, the DU 174 transmits the fourth DU- to-CU message (e.g., a UE Context Modification Required message) in response to receiving the first CU-to-DU message or the second CU-to-DU message.

[0067] The events 312 and 314 are collectively referred to in Fig. 3 as a LTM CSI report configuration and / or LTM ID configuration procedure 392.

[0068] After receiving the first DU-to-CU message, the CU 172 generates a first LTM candidate configuration (i.e.. LTM candidate configuration 1) including the LTM DU configuration 1 and generates a first RRC reconfiguration message including the LTM candidate configuration 1 and the LTM ID 1. In some implementations, the CU 172 includes LTM CU configuration 1 in the LTM candidate configuration 1. In other implementations, the CU 172 does not include a LTM CU configuration in the LTM candidate configuration 1. The CU 172 transmits 316 a third CU-to-DU message including the first RRC reconfiguration message to the DU 174. In turn, the DU 174 transmits 318 the first RRC reconfiguration message to the UE 102. In response, the UE 102 transmits 320 a first RRC reconfiguration complete message to the DU 174. The DU 174 then transmits 322 a third DU-to-CU message including the first RRC reconfiguration complete message to the CU 172.

[0069] If the first DU-to-CU message includes the LTM reference DU configuration, the CU 172 generates a LTM reference configuration including the LTM reference DU configuration. In such cases, the CU 172 may include the LTM reference configuration in the first RRC reconfiguration message. In some implementations, the CU 172 includes a LTM reference CU configuration in the LTM reference configuration. In such cases, the CU 172 may generate the LTM CU configuration 1 as a delta configuration based on the LTM reference CU configuration. In other implementations, the CU 172 does not include a LTM reference CU configuration in the LTM reference configuration. In such cases, the CU 172 may generate the LTM CU configuration 1 as a complete configuration. Alternatively, the CU 172 transmits a second RRC reconfiguration message including the LTM reference configuration to the UE 102 via the DU 174, similar to the events 316 and 318. In response, the UE 102 transmits a second RRC reconfiguration complete message to the CU 172 via the DU 174, similar to the events 320 and 322. In some implementations, if the CU 172 does not receive a LTM reference DU configuration, the CU 172 may generate a LTM reference configuration including only the LTM reference CU configuration. In other implementations, if the CU 172 does not receive a LTM reference DU configuration, the CU 172 may not generate a LTM reference configuration.

[0070] In some implementations, if the first DU-to-CU message includes the complete configuration indication, the CU 172 may determine that the LTM DU configuration 1 as a complete configuration. Otherwise, if the first DU-to-CU message does not include the complete configuration indication, the CU 172 may determine that the LTM DU configuration 1 is a delta configuration. In some implementations, if the LTM DU configuration 1 is a complete configuration, the CU 172 generates the LTM candidate configuration 1 as a complete configuration. Otherwise, if the LTM DU configuration 1 is a delta configuration, the CU 172 generates the LTM candidate configuration 1 as a delta configuration. If the LTM candidate configuration 1 is a complete configuration, the CU 172 includes, in the first RRC reconfiguration message, a complete configuration indication to indicate that the LTM candidate configuration 1 is a complete configuration. If the LTM candidate configuration 1 is a delta configuration, the CU 172 excludes the complete configuration indication from the first RRC reconfiguration message to indicate that the LTM candidate configuration 1 is a delta configuration.

[0071] In the case that the CU 172 performs the procedure 392, the CU 172 may include the second serving DU configuration in the first RRC reconfiguration message. Alternatively, the CU 172 transmits a third RRC reconfiguration message including the second serving DU configuration to the UE 102 via the DU 174, similar to the events 316 and 318. In response, the UE 102 transmits a third RRC reconfiguration complete message to the CU 172 via the DU 174, similar to the events 320 and 322.

[0072] In some implementations, the CU 172 includes the CSI resource configuration in the first RRC reconfiguration message, the second RRC reconfiguration message, or the third RRC reconfiguration message. In other implementations, the CU 172 transmits a fourth RRC reconfiguration message including the CSI resource configuration to the UE 102 via the DU 174, similar to the events 316 and 318. In response, the UE 102 transmits a fourth RRC reconfiguration complete message to the UE 102 via the DU 174, similar to the events 320 and 322.

[0073] In some implementations, the DU 174 transmits a DU-to-CU message to the CU 172, including early synchronization information for the UE 102. The DU-to-CU message may be the first DU-to-CU message, the second DU-to-CU message or a fourth DU-to-CU message. In some implementations, the DU 174 transmits the fourth DU-to-CU message in response to receiving a fourth CU-to-DU message from the CU 172. In other implementations, the DU 174transmits the fourth DU-to-CU message (e.g., a UE Context Modification Required message) in response to receiving the first CU-to-DU message or the second CU-to-DU message. In one implementation, the DU 174 does so, if the DU 174 determines that the UE 102 supports (i.e., is capable of) early UL synchronization with a LTM candidate cell (e.g.. early TA acquisition with a LTM candidate cell, early RA on a LTM candidate cell, or UE measured TA). Otherwise, if the DU 174 determines that the UE 102 does not support the early UL synchronization with a LTM candidate cell, the DU 174 does not transmit the early synchronization information to the CU 172. In other implementations, the CU 172 transmits a CU-to-DU message including an early synchronization information request (e.g.. an IE) to the DU 174, and the DU 174 includes the early synchronization information in the DU-to-CU message in response to the early synchronization information request. The CU-to-DU message may be the first CU-to-DU message, the second CU-to-DU message or the fourth CU-to-DU message. In one implementation, the CU 172 does so if the CU 172 determines that the UE 102 supports the early UL synchronization with a LTM candidate cell. Otherwise, if the CU 172 determines that the UE 102 does not support the early UL synchronization with a LTM candidate cell, the CU 172 does not request the DU 174 to provide the early synchronization information for the UE 102. If the CU 172 receives the early synchronization information, the CU 172 includes the early synchronization information in the first, second, third or fourth RRC reconfiguration message. Alternatively, the CU 172 transmits a fifth RRC reconfiguration message including the early synchronization information to the UE 102 via the DU 174, similar to the events 316 and 318. In response, the UE 102 transmits a fifth RRC reconfiguration complete message to the CU 172 via the DU 174, similar to the events 320 and 322.

[0074] In some implementations, the early synchronization information includes a random access channel (RACH) configuration (i.e., RACH configuration 1) and / or one or more TCI state configurations (i.e., TCI state configuration(s) 1). In some implementations, the early synchronization request may include a request for a RACH configuration. If the early synchronization request includes the request for a RACH configuration, the DU 174 includes the RACH configuration in the early synchronization information or in the DU-to-CU message (e.g., be the first, second or fourth DU-to-CU message). Otherwise, if the early synchronization request does not include the request for a RACH configuration, the DU 174 neither includes the RACH configuration in the early sy nchronization information or in the DU-to-CU message.

[0075] In some implementations, the CU 172 includes, in the first, second, third, fourth and / or fifth RRC reconfiguration messages, one or more other LTM related configurations forthe first cell. For example, the other LTM related configuration(s) include a PCI of the first cell and / or the LTM SSB configuration.

[0076] The events 316, 318, 320, 322 are collectively referred to in Fig. 3 as a LTM configuration delivery' procedure 394. The second, third, fourth and / or fifth RRC reconfiguration message(s)) and the second, third, fourth and / or fifth RRC reconfiguration complete message(s). the related CU-to-DU message(s) and / or the related DU-to-CU message(s) are also considered as part of the LTM configuration delivery procedure 394. In some implementations, the RRC reconfiguration message and the RRC reconfiguration complete message described above are an RRCReconfiguration message and an RRCReconfigurationComplete message, respectively.

[0077] In some implementations, the first CU-to-DU message is a UE Context Modification Request message, and the first DU-to-CU message is a UE Context Modification Response message. In some implementations, the second CU-to-DU message is a UE Context Modification Request message, and the second DU-to-CU message is a UE Context Modification Response message or a UE Context Modification Required message. In the case of the UE Context Modification Required message, the CU 172 can transmit a UE Context Modification Confirm message to the DU 174 in response to UE Context Modification Required message. In some implementations, the third CU-to-DU message is a DL RRC Message Transfer message. In other implementations, the third CU-to-DU message is a UE Context Modification Request message. In some implementations, the third DU-to-CU message is a UL RRC Message Transfer message. In other implementations, the third DU-to-CU message is a UE Context Modification Response message.

[0078] In some implementations, the LTM reference CU configuration is different from the serving CU configuration. In some implementations, a portion of the LTM reference CU configuration is the same as a portion of the serving CU configuration and the rest of the LTM reference CU configuration is different from the rest of the serving CU configuration. In yet other implementations, the LTM reference CU configuration is the same as the serving CU configuration.

[0079] In some implementations, the LTM reference CU configuration includes PDCP configuration parameters, measurement configuration parameters, and / or radio bearer configuration parameters. In some implementations, the LTM CU configuration 1 includes aMeasConfig IE and / or a RadioBearerConfig IE defined in 3GPP specification 38.331 or includes configuration parameters in the MeasConfig IE and / or RadioBearerConfig IE.

[0080] In some implementations, the LTM CU configuration 1 and / or the LTM reference CU configuration include PDCP configuration parameters, measurement configuration parameters, and / or radio bearer configuration parameters. In some implementations, the LTM CU configuration 1 or the LTM reference CU configuration includes a MeasConfig IE and / or a RadioBearerConfig IE defined in 3GPP specification 38.331 or includes configuration parameters in the MeasConfig IE and / or RadioBearerConfig IE.

[0081] In some implementations, the LTM DU configuration 1 includes a plurality of configuration parameters for the UE 102 to communicate with the DU 174 on the first cell. In some implementations, the plurality of configuration parameters include physical layer configuration parameters (e.g.. PhysicalCellGroupConfig IE). MAC layer configuration parameters (e.g., MAC -CellGroupConfig IE) and / or RLC configuration parameters (e.g., RLC- BearerConfig IE(s)). In some further implementations, the plurality' of configuration parameters include a special cell configuration (e.g., SpCellConfig IE) and / or one or more SCell configurations (e.g., SCellConfig IE(s)). In some implementations, the LTM DU configuration 1 is CellGroupConfig IE defined in 3GPP specification 38.331. In other implementations, the LTM DU configuration 1 includes configuration parameters in the CellGroupConfig IE.

[0082] In some implementations, the LTM DU configuration 1 includes a first LI measurement configuration (e.g., a CSI-MeasConfig IE) and / or at least one first transmission configuration indicator (TCI) state configuration. In other implementations, the LTM CU configuration 1 includes the first TCI state configuration(s). In some implementations, the first LI measurement configuration includes at least one first RS resource configuration and / or at least one first report configuration. In some implementations, the first RS resource configuration(s) configures one or more RSs or one or more RS resources associated with the cell 1. The RS(s) includes SSB(s) and / or CSI-RS(s). The RS resource(s) includes SSB resource(s) and / or CSI-RS resource(s). In some implementations, each of the first RS resource configuration(s) includes a RS resource configuration ID. In some implementations, the first RS resource configuration(s) is / are (similar to) CSI-ResourceConfig IE(s). In some implementations, the first report configuration(s) configures one or more UL resources (e.g., PUCCH resources or PUSCH resources) on the first cell for the UE 102 to transmit measurement results (e.g., CSI reports or LTM CSI reports). In some implementations, eachof the first report configuration(s) includes one or more RS resource configuration IDs identifying one or more RS resource configurations included in the first RS resource configuration(s). In some implementations, each of the first TCI state configuration(s) configures a TCI state that associates one or two DL RSs with a corresponding quasi-colocation (QCL) type. The DL RS(s) are associated with the cell 1.

[0083] After receiving the LTM-related configurations and the second serving DU configuration or after receiving the RRC reconfiguration message(s) described above, the UE 102 performs measurements on at least one first RS, generates at least one first LI measurement result based on the measurements, and transmits 324 at least one first LI measurement report including the first LI measurement result(s) to the DU 174. The first RS(s) may comprise SSB(s) and / or CSI-RS(s). In some implementations, the first RS(s) and / or transmission pattem(s) of the first RS(s) are configured in the CSI report configuration(s), the LTM SSB configuration, and / or the CSI resource configuration. The UE 102 performs the measurements on the first RS(s) in accordance with the CSI report configuration(s). the LTM SSB configuration, and / or the CSI resource configuration.

[0084] After receiving the LTM-related configurations and the second serving DU configuration or after receiving the RRC reconfiguration message(s) described above, the UE 102 performs measurements on at least one second RS, generates at least one second LI measurement result based on the measurements, and transmits at least one second LI measurement report including the first LI measurement result(s) to the DU 174. The second RS(s) may comprise SSB(s) and / or CSI-RS(s). In some implementations, the second RS(s) and / or transmission pattem(s) of the second RS(s) are configured in one or more second CSI report configurations and / or one or more second CSI resource configuration that are included in the serving DU configuration 302 and / or the second serving DU configuration. The UE 102 performs the measurements on the second RS(s) in accordance with the second CSI report configuration(s) and / or the second CSI resource configuration(s). The second CSI report configuration(s) may include non-LTM CSI report configuration(s) and / or LTM CSI report configuration(s). The second CSI resource configuration(s) may include non-LTM CSI resource configuration(s) and / or LTM CSI resource configuration(s).

[0085] After transmitting the RACH configuration to the UE 102 via the CU 172, the DU 174 may transmit 350 a PDCCH order to the UE 102 to command the UE 102 to transmit a RA preamble on the first cell. In response to the PDCCH order, the UE 102 transmits a RApreamble on the first cell. The DU 174 includes PDCCH order information in the PDCCH order. The PDCCH order information includes a RA preamble index, an UL or a supplemental UL indicator, a SSB index and / or a physical RACH mask index. In some implementations, the DU 174 includes the LTM ID 1 in the PDCCH order to indicate the first cell. The UE 102 identifies the first cell based on the LTM ID 1 in the PDCCH order and transmits 352 the RA preamble on the first cell to the DU 174, using the PDCCH order information. Correspondingly, the DU 174 receives 352 the RA preamble in accordance with the PDCCH order information. In some implementations, the DU 174 may determine the S SB index, based on L 1 measurement report(s) 324, and / or the CSI resource configuration, the CS1 report configuration and / or the LTM SSB configuration. In some implementations, the LI measurement report(s) may include the SSB index. In other implementations, the LI measurement report(s) include a SS / PBCH Block Resource Indicator (SSBRI) corresponding to the SSB index. Thus, the DU 174 determines the SSB index based on the SSBRI.

[0086] In some implementations, the DU 174 determines whether to transmit the PDCCH order based on the LI measurement result(s) 324. In some implementations, if the LI measurement result(s) indicate that the first cell qualifies for the UE 102 to perform RA for early UL synchronization, the DU 174 transmits the PDCCH order. Otherwise, if the LI measurement result(s) indicate that the first cell does not qualify for the UE 102 to perform RA for early UL synchronization, the DU 174 refrains from transmitting the PDCCH order. In other implementations, if the LI measurement result(s) indicate that the first cell qualifies for the UE 102 to access, the DU 174 transmits the PDCCH order. Otherwise, if the LI measurement result(s) indicate that the first cell does not qualify for the UE 102 to access, the DU 174 refrains from transmitting the PDCCH order. In yet other implementations, the DU 174 transmits the PDCCH order after receiving 320 the RRC reconfiguration complete message, regardless of the LI measurement result(s) 324.

[0087] After transmitting 324 the LI measurement report(s) or 352 the RA preamble, the UE 102 may transmit 354 additional LI measurement report(s) to the DU 174, similar to the event 324. The DU 174 determines to command the UE 102 to perform a LTM cell switch to the first cell based on the additional LI measurement report(s) and / or the LI measurement report(s) 324. In response to the determination, the DU 174 generates a LTM Cell Switch Command (e.g., a MAC CE) including the LTM ID 1 and transmits 326 the LTM Cell Switch Command to the UE 102. In response to the determination, the DU 174 may transmit 328 a DU-CU Cell Switch Notification message to the CU 172. In response to the LTM Cell Switch Command,the UE 102 performs a LTM cell switch to the first cell. In the LTM cell switch, the UE 102 accesses 332 the first cell and transmits 336 a RRC reconfiguration complete message to the DU 174 via the first cell. The DU 174 transmits 338 a DU-to-CU message (e.g., UL RRC Message Transfer message) including the RRC reconfiguration complete message to the CU 172. When the UE 102 receives the LTM Cell Switch Command, the UE 102 identifies the LTM candidate configuration 1 from the LTM ID 1 and accesses 332 the first cell using the LTM candidate configuration 1. Depending on implementations, the UE 102 may stop communicating on the serving cell(s) in response to the LTM Cell Switch Command. In turn, the DU 174 transmits a fifth DU-to-CU message including the RRC reconfiguration complete message to the CU 172. When the DU 174 detects the UE 102 accesses the first cell in the event 332, the DU 174 may transmit 334 an Access Success message to the CU 172 to indicate that the UE 102 has accessed the first cell.

[0088] In some implementations, the DU 174 includes, in the LTM Cell Switch Command, a TA value for UL synchronization with the first cell. In one implementation, the DU 174 derives the TA value based on the RA preamble (e.g., reception timing of the RA preamble). In another implementation, the DU 174 derives the TA value from an UL transmission on the serving cell (e.g., the cell 124A) from the UE 102. The UE 102 applies the TA value to synchronize with the first cell in UL transmission. After applying the TA value, the UE 102 transmits the first UL transmission on the first cell based on the LTM candidate configuration 1 without performing a RA procedure on the first cell. In some implementations, the UE 102 transmits the first UL transmission on the first cell using a UL grant. In such cases, the first UL transmission is a PUSCH transmission. In some implementations, the PUSCH transmission includes the RRC reconfiguration complete message 336. In some implementations, the UL grant is a configured grant and the LTM candidate configuration 1 or the LTM DU configuration 1 includes the configured grant configuration configuring the configured grant. In other implementations, the UL grant is a dynamic grant that the UE 102 receives on a PDCCH on the first cell. After transmitting the first UL transmission, the UE 102 receives a PDCCH transmission addresses to a C-RNTI of the UE 102 and determines that the LTM cell switch is completed successfully in response to receiving the PDCCH transmission.

[0089] The PDCCH transmission may include a UL grant or a DL assignment. In the case of the UL grant, the UE 102 transmits a PUSCH transmission to the DU 174 on the first cell using the UL grant. In the case of the DL assignment, the DU 174 transmits a PDSCH transmission to the UE 102 on the first cell in accordance with the DL assignment. The DU 174may transmit 334 the Access Success message to the CU 172 after receiving (e.g., in response to) the first UL transmission, transmitting the PDCCH transmission, receiving the PUSH transmission or transmitting the PDSCH transmission.

[0090] In other implementations, the DU 174 does not include a TA value in the LTM Cell Switch Command. If the LTM Cell Switch Command does not include a / the TA value, the UE 102 performs 332 a RA procedure on the first cell in accordance with the RA configuration parameters. In some implementations, the RA configuration parameters are included in the LTM candidate configuration 1 or the LTM DU configuration 1. In some implementations, the RA configuration parameters configure PRACH resources, an association between SSB and PRACH resources, and / or one or more PRACH occasions. If the UE 102 successfully completes the RA procedure, the UE 102 determines the LTM cell switch to the first cell is completed successfully. Depending on implementations and / or the RA configuration parameters, the RA procedure can be a four-step RA procedure or a two-step RA procedure. During the four-step RA procedure, the UE 102 transmits a Message 3 on the first cell and the DU 174 transmits a Message 4 on the first cell to the UE 102 in response. During the two-step RA procedure, the UE 102 transmits a Message A on the first cell and the DU 174 transmits a Message B to the UE 102 on the first cell in response. The UE 102 may include the RRC reconfiguration complete message 336 in the Message 3 or Message A. Alternatively, the UE 102 transmits the RRC reconfiguration complete message 336 after completing the RA procedure. The DU 174 may transmit 334 the Access Success message to the CU 172, after receiving the Message 3, Message A or the RRC reconfiguration complete message 336 or transmitting the Message 4 or Message B.

[0091] After successfully completing the LTM cell switch to the first cell as described above, the UE 102 communicates 340 with the DU 174 and the CU 172 via the first cell, using the LTM candidate configuration 1. In the case of the LTM reference configuration, the UE 102 applies the LTM reference configuration first and then apply the LTM candidate configuration 1 to augment the LTM reference configuration.

[0092] In some implementations, each of the TCI state configuration(s) include a TCI state ID. In some implementations, the DU 174 includes, in the LTM Cell Switch Command, a first TCI state ID indicating a first one of the TCI state configuration(s). The UE 102 identifies the first one of the TC state configuration(s) based on the first TCI state ID and applies the first TCI state configuration to communicate UL transmissions and / or DL transmissions with theDU 174 in the events 332, 336 and / or 340. The DU 174 applies the first TCI state configuration to communicate UL transmissions and / or DL transmissions with the UE 102 in the events 332, 336 and / or 340.

[0093] In some implementations, the CU 172 may prepare additional cell(s) (i.e., cell(s) 2, , N) as LTM candidate cell(s) for the UE 102 with the DU 174, before or after transmitting the LTM Cell Switch Command or during, before or after the procedure 390 or 392. as described above. N is an integer and larger than 1. For example, the CU 172 performs additional LTM preparation procedure(s) 2, ... , N with the DU 174 to prepare the cell(s) 2, ...N respectively. Each of the LTM preparation procedure(s) 2, . . . , N is similar to the procedure 390. In the LTM preparation procedure(s) 2, .... N, the CU 172 receives LTM DU configuration(s) 2, ... , N configuring the cell(s) 2, .... N for LTM, respectively. The CU 172 generates LTM candidate configuration(s) 2, ... , N including the LTM DU configuration(s) 2, ...N, respectively. The CU 172 assigns LTM ID(s) 2, ... , N to identify the LTM DU configured on(s) 2, . .. , N and the LTM candidate configured on(s) 2, . .. , N, respectively. The CU 172 may obtain CSI resource configuration 2, , . . . , N and perform CSI report configuration and / or LTM ID configuration procedure(s) 2, ... , N with the DU 174 to obtain the CSI report configuration(s) 2, ... , N, respectively, as described for the CSI resource configuration 1 and the CSI report configured on(s) 1. The CU 172 may obtain RACH configuration 2, ... , N for the cell(s) 2, ... , N respectively, as described for the RACH configuration 1. The CU 172 may obtain TCI state configuration(s) 2, . . . , N for the cell(s) 2, .. . , N respectively, as described for the TCI state configuration(s) 1. Each of the CSI report configuration and / or LTM ID configuration procedure(s) 2, ... , N is similar to the procedure 392. The CU 172 may obtain LTM SSB configuration 2, . .. , N for the cell(s) 2, .. . , N, respectively, as described for the LTM SSB configuration 1. In some implementations, the CU 172 may perform LTM configuration delivery procedure 2, ... , N with the UE 102 to transmit a list of the {LTM ID 2, the LTM candidate configuration 2, the CSI resource configuration 2 (if obtained), the TCI state configuration 2 (if obtained), the RACH configuration 2 (if obtained), the LTM SSB configuration 2 (if obtained)}, ... , {the LTM ID N, the LTM candidate configuration N. the CSI resource configuration N, the TCI state configuration(s) N (if obtained), the RACH configuration N (if obtained), the LTM SSB configuration N (if obtained)} to the UE 102, respectively. Each of the LTM configuration delivery procedure 2, ... , N is similar to the procedure 394. In other implementations, the CU 172 includes the list in the first RRC reconfiguration message.

[0094] Tn some implementations, after receiving 334 the Access Success message or 338 the DU-to-CU message, the CU 172 may transmit 342 a CU-to-DU message to the DU 174. In one implementation, the CU 172 transmits 342 the CU-to-DU message to release radio resources and / or configurations of the serving cell(s) configured for the UE 102. In another implementation, the CU 172 transmits 342 the CU-to-DU message to release some of the LTM candidate cell(s) 2, . .. , N. In this case, the CU 172. In response to the CU-to-DU message 342, the DU 174 transmits 344 a DU-to-CU message to the CU 172. In some implementations, the CU-to-DU message 342 and the DU-to-CU message 344 are a UE Context Modification Request message and a UE Context Modification Response message, respectively.

[0095] In some implementations, a LTM ID in a PDCCH order, a LTM Cell Switch Command and a RRC reconfiguration message is represented in different formats. For example, the PDCCH order or the LTM Cell Switch Command includes a first field to include the LTM ID 1 and the first RRC reconfiguration message includes a second field to include the LTM ID 1. In some implementations, the first field and the second field have different formats or coding schemes. For example, the first field uses a binary format (i.e., 3 bits) with a value range of 0, . .. , 7 and the second field uses an integer format with a value range of 1, . . . , 8. In this example, the first field with binary' value 000b is equivalent to the second field with integer value 1, the first field with binary' value 001b is equivalent to the second field with integer value 2, .. . , the first field with binary value 11 lb is equivalent to the second field with integer value 8.

[0096] The events 304, 306, 390, 392, 394, and 324 are collectively referred to in Fig. 3 as an intra-CU intra-DU LTM configuration procedure 396. The events 304, 306, 390, 392, 394, 324, 350, 352, 354, 326, 328, 332, 334, 336, 338, and 340 are collectively referred to in Fig. 3 as an intra-CU intra-DU LTM procedure 380.

[0097] Referring next to Fig. 4, in a scenario 400, the base station 104A includes a CU 172, a S-DU 174A and a candidate DU (C-DU) 174B. The S-DU 174A operates the cell 124A and optionally additional cell(s), while the C-DU 174B operates a first cell (e.g., cell 124C). The scenario 400 is an intra-CU inter-DU scenario, similar to the scenario 300. Thus, the descriptions for the scenario 300 can generally apply to the scenario 400. Some descriptions for the DU 174 in Fig. 3 may apply to the S-DU 174A in Fig. 4, and some descriptions for the DU 174 in Fig. 3 may apply to the C-DU 174B. The differences between the scenarios 300 and 400 are described below.

[0098] Initially, the UE 102 communicates 402 with the S-DU 174A on one or more serving cells (e.g., the cell 124A and / or other cell(s)) using a serving DU configuration and communicates with the CU 172 via the S-DU 174A using a serving CU configuration. In some implementations, the CU 172 and S-DU 174A might perform the LTM configuration procedure 396 or the LTM procedure 380 with the UE 102, as described for Fig. 3. In the case of the procedure 380, the UE 102 may perform a LTM cell switch to the first cell (e.g. cell 124B) as described for Fig. 3. Upon successfully completing the LTM cell switch, the first cell becomes a serv ing cell and cell 124A and / or the other cell(s) is / are no longer serving cell(s) for the UE 102. In the case of the procedure 396, the UE 102 does not perform a LTM cell switch. During the communication 402, the UE 102 transmits 404, 406 at least one measurement report (e.g., L3 measurement report(s)) to the CU 172 via the S-DU 174A. Based on the measurement report(s), the CU 172 determines to prepare cell 1 (e.g., cell 124C operated by the C-DU 174B) for LTM for the UE 102. The cell 1 is identified by a cell ID (i.e., cell ID 1). In response to the determination, the CU 172 performs 490 a LTM preparation procedure with the C-DU 174B to (request the C-DU 174B to) prepare the cell 1 as a LTM candidate cell for the UE 102. In the LTM preparation procedure 490, the CU 172 transmits a first CU-to-DU message including a cell ID 1 of the cell 1 to the C-DU 174B to request the C-DU 174B to prepare the cell 1 as a LTM candidate cell for the UE 102, similar to the event 308. In response, the C-DU 174B transmits a first DU-to-CU message including a LTM DU configuration (e.g., LTM DU configuration 1) to the CU 172, similar to the event 310. The CU 172 may or may not request a LTM reference DU configuration in the first CU-to-DU message, as described for Fig. 3. The C-DU 174B may or may not include a LTM reference DU configuration in the first DU-to-CU message, as described for Fig. 3.

[0099] In some implementations, if the CU 172 receives a LTM reference DU configuration from the S-DU 174A as described for Fig. 3, the CU 172 may include the LTM reference DU configuration in the first CU-to-DU message and the C-DU 174B may generate the LTM DU configuration as a delta configuration based on the LTM reference DU configuration. In such cases, the C-DU 174B does not transmit a LTM reference DU configuration for the UE 102 to the CU 172. In other implementations, the CU 172 receives a LTM reference DU configuration from the C-DU 174B, e.g., in the first DU-to-CU message or an additional DU-to-CU message as described for Fig. 3. In such cases, the CU 172 may generate a LTM reference configuration including the LTM reference DU configuration. The CU 172 may or may not include a LTM reference CU configuration in the LTM reference configuration.

[0100] To prepare the cell 1 for LTM, the CU 172 may perform 492 a LTM CSI report configuration and / or LTM ID configuration procedure with the S-DU 174A. In the procedure 492, the CU 172 transmits a second CU-to-DU message including a CSI resource configuration (e.g., CSI resource configuration 1) and / or a LTM SSB configuration (i.e., LTM SSB configuration 1) to the S-DU 174A, similar to the event 312. In response, the S-DU 174A transmits a second DU-to-CU message including one or more CSI report configurations (e.g., CSI report configuration(s) 1) to the CU 172. In some implementations, the CU 172 generates a LTM candidate configuration (e.g., LTM candidate configuration 1) including the LTM DU configuration and assigns a LTM ID (e.g., LTM ID 1) for identifying the LTM DU configuration and / or the LTM candidate configuration as described for Fig. 3. In some implementations, the CU 172 includes {the LTM ID 1, the cell ID 1} as a tuple in the second CU-to-DU message.

[0101] To prepare the cell 1 as a LTM candidate cell for the UE 102, the CU 172 may receive early synchronization information for the cell 1 in a DU-to-CU message (e.g., the first DU-to- CU message or an additional DU-to-CU message) from the C-DU 174B. In some implementations, the C-DU 174B transmits the additional DU-to-CU message in response to receiving an additional CU-to-DU message from the CU 172. In other implementations, the C- DU 174B transmits the additional DU-to-CU message (e.g., a UE Context Modification Required message) in response to receiving the first CU-to-DU message. The early synchronization information includes a RACH configuration (e.g., RACH configuration 1) and / or at least one TCI state configuration (e g., TCI state configuration(s) 1), as described for Fig. 3. In some implementations, the C-DU 174B includes, in the early synchronization information or in the DU-to-CU message, the PDCCH order information (PDCCH order information 1) for early UL synchronization with the first cell.

[0102] In some implementations, the CU 172 may receive the LTM SSB configuration or SSB configuration parameters in the LTM SSB configuration from the C-DU 174B, e.g., in the first DU-to-CU message or an additional DU-to-CU message. In some implementations, the CU 172 may receive a PCI of the cell 1 from the C-DU 174B in the first DU-to-CU message or the additional DU-to-CU message. In some implementations, the C-DU 174B transmits the additional DU-to-CU message in response to receiving an additional CU-to-DU message from the CU 172. In other implementations, the C-DU 174B transmits the additional DU-to-CU message (e.g., a UE Context Modification Required message) in response to receiving the first CU-to-DU message.

[0103] As described for Fig. 3, the CU 172 performs 494 LTM configuration delivery procedure with the UE 102 to transmit the LTM ID 1 and the LTM candidate configuration to the UE 102. In some implementations, the CU 172 transmits {LTM ID, the LTM candidate configuration} as a tuple in a first RRC reconfiguration message in the procedure 494. Depending on the implementations, the CU 172 may include the LTM reference configuration, the CSI report configuration(s), the CSI resource configuration, the RACH configuration, the TCI state configuration(s), the LTM SSB configuration and / or the PCI of the cell 1 to the UE 102 in the first RRC reconfiguration message and / or other RRC reconfiguration message(s) transmitted to the UE 102, as described for Fig. 3. The CU 172 includes the LTM ID in the first RRC reconfiguration or the other RRC reconfiguration message(s) to indicate the CSI resource configuration, the RACH configuration, the TCI state configuration(s), the LTM SSB configuration and / or the PCI of the cell 1 are associated with the cell 1. For example, the CU 172 includes the CSI resource configuration, the RACH configuration, the TCI state configuration(s), the LTM SSB configuration and / or the PCI of the cell 1 in the tuple. In another example, the CU 172 includes {LTM ID, the CSI resource configuration, the RACH configuration, the TCI state configuration(s), the LTM SSB configuration and / or the PCI of the cell 1 } as a tuple in the other RRC reconfiguration message(s). In response to each of the other RRC reconfiguration message(s), the UE 102 transmits a RRC reconfiguration complete message to the CU 172 via the S-DU 174A.

[0104] In some implementations, the PDCCH order information includes a frequency domain resource assignment, a RA preamble index, an UL or a supplemental UL indicator, a SSB index and / or a physical RACH mask index. The CU 172 may transmit a CU-to-DU message (e.g., the second CU-to-DU message or an additional CU-to-DU message) including the PDCCH order information to the S-DU 174A. In some implementations, the CU 172 includes the LTM ID 1 or the cell ID 1 in the CU-to-DU message to indicate that the PDCCH order information is associated with the LTM ID 1 or the cell ID 1. For example, the CU 172 includes {the cell ID 1, the PDCCH order information} as a tuple in the CU-to-DU message. In the case of the additional CU-to-DU message, the S-DU 174A may transmit an additional DU-to-CU message to the CU 172 in response. The S-DU 174A transmits 450 a PDCCH order to the UE 102, based on the PDCCH order information. For example, The S-DU 174A transmits 450 a PDCCH order to the UE 102, including the PDCCH order information. In some implementations, the S-DU 174A may determine a SSB index included in the PDCCH order, based on LI measurement report(s) 424, and / or the CSI resource configuration, the CSI reportconfiguration and / or the LTM SSB configuration. In some implementations, the S-DU 174A includes the LTM ID 1 in the PDCCH order to indicate the cell 1. In the case of the additional CU-to-DU message, the S-DU 174Amay transmit an additional DU-to-CU message to the CU 172 in response. The UE 102 transmits 452 a RA preamble to the C-DU 174B on the cell 1, using the RACH configuration and / or the PDCCH order information. The C-DU 174B derives a TA value based on the RA preamble. The C-DU 174B transmits 456 a DU-CU TA Information Transfer message including the TA value to the CU 172. The CU 172 in turn transmits 458 a CU-DU TA Information Transfer message including the TA value to the S-DU 174A. In some implementations, the C-DU 174B includes the cell ID 1. the RA preamble index, a RA radio network temporary identifier (RA-RNTI) and / or a DU ID of the S-DU 174A in the message 456. In such cases, the CU 172 includes the cell ID 1, the RA preamble index, the RA-RNTI, and / or the DU ID of the S-DU 174A in the message 458. In response to determining to command the UE 102 to perform a LTM cell switch to the cell 1, the S-DU 174A transmits 456 the LTM Cell Switch Command including the LTM ID 1 to the UE 102. If the S-DU 174A receives a TA value as described above, the S-DU 174A may include the TA value in the LTM Cell Switch Command. The S-DU 174A may include a first TCI state ID in the LTM Cell Switch Command. The first TCI state ID indicates a first one of the TCI state configuration(s).

[0105] In some implementations, the C-DU 174B determines the RA-RNTI based on a PRACH occasion in which the C-DU 174B receives the RA preamble 452. In some implementations, the C-DU 174B calculates the RA-RNTI as:RA-RNTI = 1 + s_id + 14 x t_id + 14 x 80 x f_id + 14 x 80 x 8 x ul_carrier_id where s id is the index of the first OFDM symbol of the PRACH occasion (0 < s id < 14), t id is the index of the first slot of the PRACH occasion in a system frame (0 < t_id < 80), where the subcarrier spacing to determine t_id is based on the value of p specified in clause 5.3.2 in 3GPP TS 38.211 for p = {0, 1, 2, 3}, and for p = {5, 6}, t_id is the index of the 120 kHz slot in a system frame that contains the PRACH occasion (0 < t_id < 80). f id is the index of the PRACH occasion in the frequency domain (0 < f id < 8), and ul carrier id is the UL carrier used for the RA Preamble transmission (0 for NUL carrier, and 1 for SUL carrier).

[0106] In response to determining to command the UE 102 to perform a LTM cell switch or transmitting 456 the LTM Cell Switch Command, the S-DU 174A transmits 428 aDU-CU Cell Switch Notification message to the CU 172 to indicate that the UE 102 performs a LTM cell switch to the cell 1. In response, the CU 172 transmits 430 a CU-DU Cell Switch Notificationmessage to the C-DU 174B to indicate that the UE 102 performs a LTM cell switch to the cell 1. In some implementations, the S-DU 174A includes the first TCI state ID in the DU-CU Cell Switch Notification message and the CU 172 in turn includes the first TCI state ID in the CU- DU Cell Switch Notification message. The UE 102 and the C-DU 174B identify the first one of the TC state configuration(s) based on the first TCI state ID and apply the first TCI state configuration to communicate UL transmissions and / or DL transmissions in the events 432, 436 and / or 440.

[0107] In some implementations, each of the TCI state configuration(s) includes or is associated with a TCI state ID. In some implementations, the CU 172 may transmit a CU-to- DU message (e.g., the second CU-to-DU message or an additional CU-to-DU message) including the TCI state configuration(s) and / or the associated TCI state ID(s) to the S-DU 174 A. In some implementations, the CU 172 includes the LTM ID 1 or the cell ID 1 in the CU- to-DU message to indicate that the TCI state configuration(s) is associated with the LTM ID 1 or the cell ID 1. For example, the CU 172 includes {the cell ID 1, the TCI state configuration(s)} as a tuple in the CU-to-DU message. In the case of the additional CU-to-DU message, the S-DU 174A may transmit an additional DU-to-CU message to the CU 172 in response. In some implementations, the S-DU 174A includes, in the LTM Cell Switch Command 426, a first TCI state ID indicating a first one of the TCI state configuration(s). In some implementations, the S-DU 174A determines the first TCI state configuration or the fist TCI state ID. The UE 102 identifies the one of the TCI state configuration(s) based on the first TCI state ID and applies the first TCI state configuration in UL transmissions and / or DL receptions in the events 432, 436 and / or 440.

[0108] In some implementations, the CU 172 may prepare additional cell(s) (i.e., cell(s) 2, ... , N) as LTM candidate cell(s) for the UE 102 with the C-DU 174B, before or after transmitting the LTM Cell Switch Command or during, before or after the procedure 490 or 492, as described for Fig. 4

[0109] In some implementations, the first CU-to-DU message and the first DU-to-CU message are a UE Context Setup Request message and a UE Context Setup Response message. In some implementations, the first CU-to-DU message and the first DU-to-CU message are a UE Context Modification Request message and a UE Context Modification Response message. In some implementations, the LTM preparation procedure 490 is a UE Context Setup procedure and the additional LTM preparation procedure is a UE Context Modification procedure. Inother implementations, the LTM procedure 490 and the addition LTM preparation procedures are UE Context Setup procedures. In yet other implementations, the LTM procedure 490 and the addition LTM preparation procedures are UE Context Modification procedures.

[0110] The events 404, 406, 490, 492, 494, 494, and 424 are collectively referred to in Fig. 4 as an intra-CU inter-DU LTM configuration procedure 496. The events 404, 406, 490, 492, 494, 494, 424, 450, 452. 454 456. 458, 426, 428. 430, 432. 434. 436, 438. 440, 442, and 444 are collectively referred to in Fig. 4 as an intra-CU inter-DU LTM procedure 480.

[0111] Referring next to Fig. 5, in a scenario 500, the base station 104A operates as a serving or source base station (S-BS), and the base station 106A operates as a candidate base station (C-BS). The C-BS 106A includes a CU 172 and a DU 174. The scenario 500 is similar to the scenarios 300 and 400, except that the scenario 500 is an inter-CU scenario (i.e., inter-base station scenario) while the scenarios 300 and 400 are intra-CU (i.e., intra-base station) scenarios. The S-BS 104A can include a CU and a DU (not shown in Fig. 5), similar to the base station 104Aof Figs. 3 and 4. Initially, the UE 102 communicates 502 with the S-BS 104A via serving cell(s) using a serving configuration. In some implementations, the S-BS 104Aincludes a S-DU and a CU and the serving configuration may include a serving CU configuration and a serving DU configuration, as described for Figs. 3 and 4. While the communicating 502 with the UE 102, the S-BS 104A might perform 580 intra-CU LTM procedure(s) with the UE 102, similar to the procedures 380 and / or 480. Alternatively, while the communicating 502 with the UE 102, the S-BS 104A might perform 596 intra-CU LTM configuration procedure(s) with the UE 102, similar to the procedures 396 and / or 496.

[0112] While communicating with the S-BS 104A, the UE 102 transmits 504 at least one measurement report to the S-BS 104A. The measurement report(s) include measurement results for a serving cell of the UE 102 and / or at least one non-serving cell (e.g., cell 126A). The S- BS 104A determines to prepare a first cell (e.g., the cell 126 A) as a LTM candidate cell for the UE 102, based on the measurement report(s). For example, the measurement report(s) include a PCI of the first cell and measurement result(s) of the cell 126A. The S-BS 104A identifies that the first cell is operated by the base station 106A based on the PCI, and determines that the first cell qualifies for LTM preparation based on the measurement result(s).

[0113] After (e.g., in response to) determining to prepare the first cell as a LTM candidate cell for the UE 102, the S-BS 104A (e.g., the CU of the S-BS 104A) generates a Handover Request message including a first cell ID (i.e., cell ID 1) of the first cell (i.e., cell 1). The S-BS104A transmits 505 the Handover Request message to the CU 172. Tn some implementations, the Handover Request message includes a LTM indicator indicating the Handover Request message concerns LTM for the first cell ID. After (e.g., in response to) receiving the Handover Request message, the CU 172 performs a LTM preparation procedure 590 with the DU 174 to prepare the first cell as a LTM candidate cell for the UE 102, similar to the procedure 390 or 490. In the procedure 590, the CU 172 transmits a first CU-to-DU message including the first cell ID to the DU 174 to request preparing the first cell, similar to the event 308. In response, the CU 172 may receive a first DU-to-CU message including a LTM DU configuration 1 from the DU 174, similar to the event 310. The CU 172 generates a first LTM candidate configuration (LTM candidate configuration 1). In response to the Handover Request message, the CU 172 transmits 507 a Handover Request Acknowledge message including the first LTM candidate configuration to the S-BS 104A. In some implementations, the CU 172 includes the first cell ID in the Handover Request Acknowledge message to indicate that the first LTM candidate configuration is provided for or associated with the first cell (ID).

[0114] The events 505, 590, 507 are collectively referred to in Fig. 5 as an inter-CU LTM preparation procedure (or called inter-MN LTM preparation procedure) 598.

[0115] In some implementations, the Handover Request message includes a DU ID of the S-DU of the S-BS 104A. In such cases, the CU 172 includes the DU ID in the first CU-to-DU message. In some implementations, the Handover Request message includes a BS ID of the S- BS 104A. When receiving the BS ID. the CU 172 may include the BS ID in the first CU-to- DU message. For example, the BS ID is a gNB ID.

[0116] The CU 172 may or may not request a LTM reference DU configuration in the procedure 590, as described for Figs. 3 and 4. The DU 174 may or may not transmit a LTM reference DU configuration to the CU 172 in the procedure 590, as described for Figs. 3 and 4. In some implementations, the S-BS 104A (e.g., the CU of the S-BS 104A) may obtain a LTM reference configuration, as described for Figs. 3 and 4. In other implementations, the S-BS 104 A may receive a LTM reference configuration from another BS (not shown in Fig. 5) in another inter-CU LTM preparation procedure as described above and below. If the S-BS 104A obtains a LTM reference configuration, the S-BS 104A may include the LTM reference configuration (S-BS generated LTM reference configuration) in the Handover Request message. In some implementations, the S-BS 104A includes the LTM reference configuration in the inter-node RRC message HandoverPreparationlnformation or as an Xn Application Protocol(XnAP) IE or field and includes the inter-node RRC message or the XnAP IE in the Handover Reques message. Alternatively, the S-BS 104 A determines to request or cause the C-BS 106A to provide a complete LTM candidate configuration so that the S-BS 104A does not include the LTM reference configuration in the Handover Request message. If the S-BS 104A does not obtain a LTM reference configuration, the S-BS 104A does not include a LTM reference configuration in the Handover Request, message. If the Handover Request message includes a LTM reference configuration, the CU 172 may include the LTM reference configuration in the first CU-to-DU message. The DU 174 may extract a LTM reference DU configuration from the LTM reference configuration. Alternatively, the CU 172 extracts a LTM reference DU configuration from the LTM reference configuration and includes the LTM reference DU configuration in the first CU-to-DU message. The DU 174 may generate a LTM DU configuration as a delta configuration based on the LTM reference DU configuration, as described for Fig. 3. Alternatively, the DU 174 may ignore the LTM reference (DU) configuration and generate a LTM DU configuration as a complete configuration, as described for Fig. 3.

[0117] Otherwise, if the Handover Request message does not include a LTM reference configuration, the CU 172 may or may not receive a LTM reference DU configuration from the DU 174 as described for Fig. 3. If the CU 172 receives a LTM reference DU configuration (e.g., in the first DU-to-CU message), the CU 172 generates a LTM reference configuration (C-BS generated LTM reference configuration) including the LTM reference DU configuration. The CU 172 may include a LTM reference CU configuration (candidate CU (C-CU) generated LTM reference CU configuration). Otherwise, if the CU 172 does not receive a LTM reference DU configuration from the DU 174 as described for Fig. 3. the CU 172 does not generate a LTM reference configuration. Alternatively, the CU 172 generates a LTM reference configuration (C-BS generated LTM reference configuration) only including a C-CU generated LTM reference CU configuration. In cases where the CU 172 generates a LTM reference configuration (C-BS generated LTM reference configuration), the CU 172 includes the C-BS generated LTM reference configuration in the Handover Request Acknowledge message.

[0118] In some implementations, if the LTM DU configuration 1 is a complete configuration, the CU 172 generates the LTM candidate configuration 1 as a complete configuration. The CU 172 may include a complete configuration indication (e.g., a BS-to-BS interface protocol field / IE) in the Handover Request Acknowledge message to indicate that the LTM candidate configuration 1 is a complete configuration. In some implementations, the BS-to-BS interface protocol is an Xn application protocol defined in 3GPP specification 38.423. In some implementations, the complete configuration indication is a new field / IE (e.g., LTM specific) to avoid an impact to non-LTM configurations. In other implementations, the complete configuration indication is an existing field / IE defined in 3GPP specification 38.423. Otherw ise, if the LTM DU configuration 1 is a delta configuration, the CU 172 generates the LTM candidate configuration 1 as a delta configuration. The CU 172 may exclude the complete configuration indication from the Handover Request Acknowledge message to indicate that the LTM candidate configuration 1 is a delta configuration. Alternatively, the CU 172 may include a delta configuration indication (e.g., a BS-to-BS interface protocol field / IE) in the Handover Request Acknowledge message to indicate that the LTM candidate configuration 1 is a delta configuration. In some implementations, the BS-to-BS interface protocol is an Xn application protocol defined in 3GPP specification 38.423. In some implementations, the delta configuration indication is a new field / IE (e.g., LTM specific) to avoid an impact to non-LTM configurations. In other implementations, the delta configuration indication is an existing field / IE defined in 3GPP specification 38.423. In some implementations, the BS-to-BS interface protocol field / IE have two values (i.e., a first value and a second value). The BS-to- BS interface protocol field / IE set to the first value is the complete configuration indication and the BS-to-BS interface protocol field / IE set to the second value is the delta configuration indication.

[0119] In some implementations, the S-BS 104A is preconfigured with a CSI resource configuration (e.g., (LTM) CSI resource configuration 1) and / or a LTM SSB configuration (LTM SSB configuration 1) for the first cell. In other implementations, the S-BS 104A receives the CSI resource configuration and / or the LTM SSB configuration from an 0AM (Operations, Administration and Maintenance) node. In yet other implementations, the S-BS 104A receives the CSI resource configuration and / or the LTM SSB configuration from the CU 172. For example, the CU 172 includes the CSI resource configuration and / or the LTM SSB configuration in the Handover Request Acknowledge message. In some implementations, the CU 172 includes a PCI (PCI 1) of the first cell in the Handover Request Acknowledge message. To prepare the first cell as a candidate LTM cell for the UE 102, the CU of the S-BS 104A performs a LTM CSI report configuration and / or LTM ID configuration procedure (not shown in Fig. 5) with a S-DU of the S-BS 104A, similar to the procedure 392. In the LTM CSI report configuration and / or LTM ID configuration procedure, the CU of the S-BS 104A transmits the CSI resource configuration and / or the LTM SSB configuration to the S-DU of the S-BS 104A.In response, the CU of the S-BS 104A receives one or more CST report configurations for the UE 102 from the S-DU of the S-BS 104 A. In some implementations, the CU of the S-BS 104A receives the CSI report configuration(s) in a second serving DU configuration from the S-DU.

[0120] To prepare the first cell as a LTM candidate cell for the UE 102, the CU 172 may receive early synchronization information (early synchronization information 1) for the first cell from the DU 174 in a DU-to-CU message (e.g., the first DU-to-CU message or an additional DU-to-CU message). In some implementations, the DU 174 transmits the additional DU-to-CU message in response to receiving an additional CU-to-DU message from the CU 172. In other implementations, the DU 174 transmits the additional DU-to-CU message (e.g., a UE Context Modification Required message) in response to receiving the first CU-to-DU message. The CU 172 includes the early synchronization information in the Handover Request Acknowledge message. The early synchronization information includes a RACH configuration (RACK configuration 1) and / or at least one TCI state configuration (TCI state configuration(s) 1). In some implementations, the DU 174 includes, in the early synchronization information or in the DU-to-CU message, PDCCH order information for early UL synchronization with the first cell. The CU 172 includes the PDCCH order information in the Handover Request Acknowledge message.

[0121] In some implementations, the CU 172 assigns a LTM ID (e.g., LTM ID 1) for identifying the first LTM candidate configuration and includes the LTM ID in the Handover Request Acknowledge message. In other implementations, the S-BS 104A assigns a LTM ID (e.g., LTM ID 1) for identifying the first LTM candidate configuration.

[0122] After (e.g.. in response to) receiving the Handover Request Acknow ledge message, the S-BS 104A (e.g., the CU of the S-BS 104A) transmits 518 a first RRC reconfiguration message to the UE 102, including {the LTM ID 1 , the LTM candidate configuration 1 } as a tuple, similar to the event 318. If the Handover Request Acknowledge message includes the LTM reference configuration, the S-BS 104A may include the LTM reference configuration in the first RRC reconfiguration message. The S-BS 104A may include the CSI resource configuration 1, the TCI state configuration(s) 1, the RACH configuration 1, and / or the LTM SSB configuration 1 in the tuple, if received in the Handover Request Acknowledge message. Alternatively, the S-BS 104 A transmits one or more additional RRC reconfiguration messages to the UE 102, including the CSI resource configuration 1, the TCI state configuration(s) 1. the RACH configuration 1, the LTM SSB configuration 1 , and / or the PCI of the first cell. In eachof the additional RRC reconfiguration message(s), the S-BS 104A includes the LTM ID 1 to indicate that the CSI resource configuration 1, the TCI state configuration(s) 1, the RACH configuration 1, the LTM SSB configuration 1, and / or the PCI of the first cell are associated with the first cell or configured for the first cell. The UE 102 transmits 520 a first RRC reconfiguration complete message to the S-BS 104A in response to the first RRC reconfiguration message. The UE 102 transmits an additional RRC reconfiguration complete message to the S-BS 104Ain response to each of the additional RRC reconfiguration complete message. The RRC reconfiguration message(s) (i.e., the first RRC reconfiguration message and / or the additional RRC reconfiguration message(s)) and the RRC reconfiguration complete message(s) (i.e., the first RRC reconfiguration complete message and / or the additional RRC reconfiguration complete message(s)) form a LTM configuration delivery7procedure. The S- BS 104A may include the second serving DU configuration in the first RRC reconfiguration message or one or the additional RRC reconfiguration message(s).

[0123] In some implementations, if the Handover Request Acknowledge message includes the complete configuration indication to indicate that the LTM candidate configuration 1 is a complete configuration, the S-BS 104A includes, in the first RRC reconfiguration message, a complete configuration indication (e.g., a RRC field / IE) to indicate that the LTM candidate configuration 1 is a complete configuration. Otherwise, if the Handover Request Acknowledge message does not include the complete configuration indication or includes the delta configuration indication to indicate that the LTM candidate configuration 1 is a delta configuration, the S-BS 104A excludes or does not include, in the first RRC reconfiguration message, the complete configuration indication (e g., a RRC field / IE) to indicate that the LTM candidate configuration 1 is a delta configuration.

[0124] If the Handover Request Acknowledge message includes the PDCCH order information (PDCCH order information 1), the S-BS 104A transmits 550 a PDCCH order, based on the PDCCH order information. If the S-BS 104A is a distributed base station, the CU of the S-BS 104A may transmit the PDCCH order information to the S-DU of the S-BS 104 A. For example, the S-BS 104A or the S-DU of the S-BS 104A transmits 550 a PDCCH order to the UE 102, including the PDCCH order information. In some implementations, the S-BS 104A or the S-DU of the S-BS 104A may determine a SSB index included in the PDCCH order, based on LI measurement report(s) 524, and / or the CSI resource configuration, the CSI report configuration and / or the LTM SSB configuration. In some implementations, the S-DU or the S-BS 104A includes the LTM ID 1 in the PDCCH order to indicate the first cell. The UE 102transmits 552 a RA preamble to the DU 174 on the first cell, using the RACH configuration and / or the PDCCH order information. The S-DU or the S-BS 104A derives a TA value based on the RA preamble. The DU 174 transmit 556 a DU-CU TA Information Transfer message including the TA value to the CU 172. The CU 172 transmits 558 a CU-CU TA Information Transfer message including the TA value to the S-SB 104A (e.g., the CU of the S-BS 104A). In some implementations, the DU 174 includes the cell ID 1, the RA preamble index, a RA- RNTI, the DU ID of the S-DU of the S-BS 104A, and / or the BS ID of the S-BS 104A in the message 556. In some implementations, the DU 174 does not include the BS ID in the message 556. In some implementations, the CU 172 includes the cell ID 1, the RA preamble index, the RA-RNTI, the DU ID of the S-DU, and / or the BS ID of the S-BS 104A in the message 558. In some implementations, the CU 172 does not include the BS ID in the message 558. The CU of the S-BS 104A transmits a CU-DU TA Information Transfer message including the TA value, the cell ID 1. the RA preamble index, the RA-RNTI. and / or the DU ID of the S-DU, and / or the BS ID of the S-BS 104Ato the S-DU of the S-BS 104A. In some implementations, the CU of the S-BS 104A does not include the BS ID in the CU-DU TA Information Transfer message.

[0125] In some implementations, the CU 172 determines an address (e.g., an IP address) of the S-BS 104A or the CU of the S-BS 104A, based on the BS ID of the S-BS 104A. In other implementations, the CU 172 determines an address (e.g., an IP address) of the S-BS 104A or the CU of the S-BS 104A, based on the DU ID of the S-DU of the S-BS 104A. With these implementations, the CU 172 sends the CU-CU TA Information Transfer message to the S-BS 104A or the CU of the S-BS 104A in accordance with the address.

[0126] In response to determining to command the UE 102 to perform a LTM cell switch to the first cell, e.g., based on the measurement report(s) 524 and / or 554, the S-DU or the S-BS 104 A transmits 526 the LTM Cell Switch Command including the LTM ID 1 to the UE 102. In response to the LTM Cell Switch Command, the UE 102 may stop communication on the serving cell(s). In response to the LTM Cell Switch Command, the UE 102 accesses 532 the first cell and transmits 536 a RRC reconfiguration complete message to DU 174. The DU 174 in turn transmits 538 a DU-to-CU message including the RRC reconfiguration complete message to the CU 172. After receiving 538 the DU-to-CU message or the RRC reconfiguration complete message, the C-BS 106A communicates 540 with the UE 102 in accordance with the first LTM candidate configuration and / or the LTM reference configuration. In some implementations, the UE 102 includes the LTM ID 1 in the RRC reconfiguration complete message 536 to indicate that the UE 102 applies the first LTM candidate configuration. Inaccordance with the LTM ID 1 , the CU 172 identifies the first LTM candidate configuration and / or the LTM reference configuration. In other implementations, the CU 172 identifies the first LTM candidate configuration and / or the LTM reference configuration based on the first cell ID included in the Access Success message 534. In such implementations, the CU 172 maintains or stores association information between the first cell ID, and the first LTM candidate configuration and / or the LTM reference configuration. When the CU 172 receives the first cell ID in the Access Success message, the CU 172 identifies the first LTM candidate configuration and / or the LTM reference configuration in accordance with the first cell ID and the association information.

[0127] In some implementations, if the S-DU or the S-BS 104A receives a TA value as described above, the S-DU or the S-BS 104 A may include the TA value in the LTM Cell Switch Command. In some implementations, the S-DU or the S-BS 104A includes a first TCI state ID in the LTM Cell Switch Command. The first TCI state ID indicates a first one of the TCI state configuration(s).

[0128] In response to determining to command the UE 102 to perform the LTM cell switch or transmitting 526 the LTM Cell Switch Command, the S-DU of the S-BS 104 A transmits a DU-CU Cell Switch Notification message to the CU of the S-BS 104A to indicate that the UE 102 performs or is performing a LTM cell switch to the first cell. In response to receiving the DU-CU Cell Switch Notification message, the CU of the S-BS 104A transmits 527 a CU-CU Cell Switch Notification message to the CU 172 to indicate that the UE 102 performs a LTM cell switch to the first cell. In response, the CU 172 transmits 530 a CU-DU Cell Switch Notification message to the DU 174 to indicate that the UE 102 performs a LTM cell switch to the first cell. In some implementations, the S-BS 104A includes the first TCI state ID in the CU-CU Cell Switch Notification message and the CU 172 then includes the first TCI state ID in the CU-DU Cell Switch Notification message. The UE 102 and the DU 174 identify the first one of the TC state configuration(s) based on the first TCI state ID and apply the first TCI state configuration to communicate UL transmissions and / or DL transmissions in the events 532, 536 and / or 540.

[0129] In some implementations, after (e.g., in response to) determining to command the UE 102 to perform the LTM cell switch, transmitting 526 the LTM Cell Switch Command, or receiving 527 the DU-CU Cell Switch Notification message, the S-BS 104A (e.g., the CU of the S-BS 104 A) transmits 531 one or more Early Status Transfer messages to the CU 172, eachincluding a DL COUNT value or a DISCARD DL COUNT value for a DRB over which the UE 102 and the S-BS 104A communicate 502 data with each other. In some implementations, after receiving 534 the Access Success message or receiving 538 the DU-to-CU message or the RRC reconfiguration complete message, the CU 172 transmits 539 a LTM Success message to the S-BS 104A (e.g., the CU of the S-BS 104A) to indicate that the LTM cell switch is completed successfully. In some implementations, the LTM Success message is a Handover Success message. In some implementations, the CU 172 includes the first cell ID in the LTM Success message. In other implementations, the CU 172 does not transmit a BS-to-BS message to the S-BS 104A (e.g.. the CU of the S-BS 104A) to indicate that the LTM cell switch is completed successfully.

[0130] In some implementations, after (e.g., in response to) determining to command the UE 102 to perform the LTM cell switch, transmitting 526 the LTM Cell Switch Command, receiving 527 the DU-CU Cell Switch Notification message, or receiving 539 the LTM Success message, the S-BS 104A (e.g.. the CU of the S-BS 104A) transmits 541 a SN Status Transfer message to the CU 172, including a DL COUNT value and / or a UL COUNT value for a / the DRB over which the UE 102 and the S-BS 104A communicate 502 data with each other.

[0131] In some implementations, after (e.g., in response to) receiving 534 the Access Success message, receiving 538 the DU-to-CU message or the RRC reconfiguration complete message or receiving 541 the SN Status Transfer message, the CU 172 transmits 543 a UE Context Release message to the S-BS 104A. In response to the UE Context Release message, the S-BS 104 A releases a UE context of the UE 102.

[0132] In some implementations, the S-BS 104A (e.g.. the CU of the S-BS 104A) may prepare additional cell(s) (i.e., cell(s) 2, ... , N) as LTM candidate cell(s) for the UE 102 with the CU 172, before or after transmitting the LTM Cell Switch Command or during, before or after the procedure 598, as described above. The cell(s) 2, .. . , N are identified by cell ID(s) 2, ... , N, respectively and operated by the DU 174 and / or other DU(s) of the C-BS 106A. N is an integer and larger than 1. For example, the S-BS 104A performs additional inter-CU LTM preparation procedure(s) 2, ... , N with the CU 172 to prepare the cell(s) 2, ...N respectively. Each of the inter-CU LTM preparation procedure(s) 2, . .. , N is similar to the procedure 598. In the inter-CU LTM preparation procedure(s) 2, .... N, the S-BS 104A receives LTM candidate configuration(s) 2. .... N configuring the cell(s) 2, ... , N for LTM. respectively. As described above, the S-BS 104 A or the C-BS 106A assigns LTM ID(s) 2, ... , N to identify the LTMcandidate configuration(s) 2, ... , N, respectively. The S-BS 104 A may obtain CSI resource configuration 2, , N for the cell(s) 2, ... , N respectively, as described for the CSI resource configuration 1. The S-BS 104A may obtain CSI report configuration(s) 2, . . . , N or the cell(s) 2, ... , N, respectively, as described for the CSI report configuration(s) 1. The S-BS 104A may obtain RACH configuration 2, . . . , N for the cell(s) 2, . . . , N respectively, as described for the RACH configuration 1. The S-BS 104A may obtain TCI state configuration(s) 2, ... , N for the cell(s) 2, ... , N respectively, as described for the TCI state configuration(s) 1. The S-BS 104A may obtain LTM SSB configuration 2. .... N for the cell(s) 2, . .. , N, respectively, as described for LTM SSB configuration 1. The S-BS 104A may obtain PCI(s) 2, .... N for the cell(s) 2. .... N respectively, as described for the PCI 1. In some implementations, the S-BS 104A may perform LTM configuration delivery procedure 2, ... , N with the UE 102 to transmit a list of the {LTM ID 2, the LTM candidate configuration 2, the CSI resource configuration 2 (if obtained), the TCI state configuration 2 (if obtained), the RACH configuration 2 (if obtained), the LTM SSB configuration 2 (if obtained), the PCI 2 (if obtained)}, ... , {the LTM ID N, the LTM candidate configuration N, the CSI resource configuration N, the TCI state configuration(s) N (if obtained), the RACH configuration N (if obtained), the LTM SSB configuration N (if obtained), the PCI N (if obtained)} to the UE 102, respectively. Each of the LTM configuration delivery procedure 2, ... , N is similar to the procedures 394, 494 and / or 594. In other implementations, the S-BS 104A includes the list in the first RRC reconfiguration message.

[0133] In other implementations, the S-BS 104A performs the procedure 598 with the CU 172 to prepare one or more of the cell(s) 1, .. . , N as LTM candidate cell(s) for the UE 102. In such implementations, the S-BS 104A includes the cell ID(s) 1, . . . , N in the Handover Request message 505 for LTM, as described for the cell ID 1 . In some implementations, upon receiving the Handover Request message, the CU 172 determines or selects the cell(s) 1, . . . , M from the cell(s) 1, ... , N as LTM candidate cell(s). M is a positive integer and M < N. In other implementations, CU 172 prepares the cell(s) 1, ... , N for LTM as requested in the Handover Request message. The CU 172 performs LTM preparation procedure(s) 2, ... , M with the DU 172 to prepare the cell(s) 2, . . . , M as LTM candidate cell(s) for the UE 102, respectively. The LTM preparation procedure(s) 2, ... , M are similar to the procedure 590 that the CU 172 performs with the DU 174 to prepare the cell 1. The CU 172 obtains the LTM candidate configuration(s) 2, . . . , M for the cell(s) 2, .. . , M as a result of the LTM preparation procedure(s) 2, . . . , M respectively, similar to obtaining the LTM candidate configuration 1 . The C-BS 106Amay generate the LTM candidate configuration(s) 2, ... , M as complete configuration(s) or generate delta configuration(s) based on the LTM reference configuration, as described for the LTM candidate configuration 1. The CU 172 includes the LTM candidate configuration(s) 2, . .. , M in the Handover Request Acknowledge message. In some implementations, the CU 172 or the S-BS 104A assigns LTM ID(s) 2, . . . , M to identify the LTM preparation procedure(s) 2, ... , M respectively, as described for the LTM ID 1. In the case the CU 172 assigns the LTM ID(s) 1, ... , M, the CU 172 includes the LTM ID(s) 1, ... , M with the LTM candidate configuration(s) 1. .. . , M. respectively in the Handover Request Acknowledge message, as described for the LTM ID 1 and the LTM candidate configuration 1.

[0134] In some implementations, the CU 172 obtains early synchronization information 2, ... , M for the cell(s) 2, ... , M, respectively, as described for the early synchronization information 1. The CU 172 includes the early synchronization information 2, ... , M in the Handover Request Acknowledge message. In some implementations, the CU 172 or the S-BS 104 A obtains CSI resource configuration(s) 2, .. . , M for the cell(s) 2, . . . , M, respectively, as described for the CSI resource configuration 1. In the case that the CU 172 obtains the CSI resource configuration(s) 2, ... , M, the CU 172 includes the CSI resource configuration(s) 2, . .. , M in the Handover Request Acknowledge message.

[0135] In some implementations, the CU 172 or the S-BS 104A obtains LTM SSB configuration(s) 2, ... , M for the cell(s) 2, ... , M, respectively, as described for the LTM SSB configuration 1. In the case that the CU 172 obtains the LTM SSB configuration(s) 2. ... , M, the CU 172 includes the LTM SSB configuration(s) 2, ... , M in the Handover Request Acknowledge message. In some implementations, the CU 172 or the S-BS 104A obtains PCI(s) 2, .. . , M for the cell(s) 2, . . . , M, respectively, as described for the PCI 1. In the case that the CU 172 obtains the PCI(s) 2, .. . , M, the CU 172 includes the PCI(s) 2, . . . , M in the Handover Request Acknowledge message.

[0136] In some implementations, the CU 172 includes a list of {the cell ID 1, the LTM ID 1 (if obtained or optional), the LTM candidate configuration 1, the CSI resource configuration 1 (if obtained or optional), the TCI state configuration 1 (if obtained or optional), the early synchronization information 1 (if obtained or optional), the LTM SSB configuration 1 (if obtained or optional), PCI 1 (if obtained or optional)}, , {the cell ID M, the LTM ID M (if obtained or optional), the LTM candidate configuration M. the CSI resource configuration M (if obtained or optional), the TCI state configuration M (if obtained or optional), the earlysynchronization information M (if obtained or optional), the LTM SSB configuration M (if obtained or optional), the PCI M (if obtained or optional)} in the Handover Request Acknowledge message.

[0137] In some implementations, the CU 172 obtains PDCCH order information 2, ... , M for the cell(s) 2, . . . , M, respectively, as described for the PDCCH order information 1. In one implementation, the CU 172 includes the PDCCH order information 2, . . . , M in the Handover Request Acknowledge message. In another implementation, the CU 172 includes the PDCCH order information 2, . . . , M in the early synchronization information 2, . .. , M, respectively. The S-BS 104A may obtain RACH configuration 2, TCI state configuration(s) 2 and / or the PDCCH order information 2. ... ., RACH configuration M. TCI state configuration(s) M and / or the PDCCH order information M from the early synchronization information 2, . . . , M, respectively or from the Handover Request Acknowledge message.

[0138] In some implementations, the S-BS 104A may perform LTM configuration delivery procedure 2, ... , M with the UE 102 to transmit a list of the {LTM ID 2, the LTM candidate configuration 2, the CSI resource configuration 2 (if obtained), the TCI state configuration 2 (if obtained), the RACH configuration 2 (if obtained), the LTM SSB configuration 2 (if obtained), the PCI 2 (if obtained)}, ... , {the LTM ID M, the LTM candidate configuration M, the CSI resource configuration M, the TCI state configuration(s) M (if obtained), the RACH configuration M (if obtained), the LTM SSB configuration M (if obtained), the PCI M (if obtained)} to the UE 102, respectively. Each of the LTM configuration delivery procedure 2, ... , M is similar to the procedures 394, 494 and / or 594. In other implementations, the S-BS 104A includes the list in the first RRC reconfiguration message.

[0139] In some implementations, the S-BS 104A may include measurement result(s) 1, . .. , N for the cell(s) 1, ... , N respectively in the Handover Request message. The S-BS 104A receives the measurement result(s) from the UE 102. The C-BS 106A may select or determine the cell(s) 1, . . . M, based on the measurement result(s) 1, . . . , N. In other implementations, the C-BS 106A may select or determine the cell(s) 1, ... M, based on one or more other factors (e.g., capacity or load of the cell(s) 1, ... , N and / or a maximum number of LTM candidate cell(s)). In one implementation, the maximum number is included in the Handover Request message. In another implementation, the maximum number is a predetermined number.

[0140] Referring next to Fig. 6A, in a scenario 600 A, the base station 104B operates as an MN, the base station 106A operates as a candidate SN (C-SN) and the base station 104Aoperates as a serving or source SN (S-SN). The C-SN 106A includes a CU 172 and a DU 174. The MN 104B may include a CU and a DU (not show n in Fig. 6 A), similar to the BS 104A in Fig. 3. The S-SN 104A may include a CU and a DU (not shown in Fig. 6A), similar to the C- SN 106 A. The scenario 600A is similar to the scenario 500. except that the scenario 600A is a SN scenario and the scenario 500 is a MN scenario.

[0141] Initially, the UE 102 in DC communicates 602 with the MN 104B and with S-SN 104 A. In some implementations, the UE 102 communicates with the DU of the S-SN 104 A on cell 124A using a serving DU configuration and communicates with the CU of the S-SN 104A via the DU of the S-SN 104A using a serving CU configuration, similar to the event 302. In some implementations, the UE 102 in DC can communicate 602 UL PDUs and / or DL PDUs with the MN 104B and / or S-SN 104A via radio bearers which can include SRBs and / or DRB(s). The MN 104B and / or the S-SN 104A can configure the radio bearers to the UE 102. The UE 102 in DC communicates 602 UL PDUs and / or DL PDUs with the S-SN 104A on an SCG (i.e., SCG radio resources) that the S-SN 104A configures for communication with the UE 102. The UE 102 in DC communicates UL PDUs and / or DL PDUs with the MN 104B on an MCG (i.e., MCG radio resources) in accordance with a MN configuration (i.e., MCG configuration). In some implementations, the serving DU configuration is a SN configuration (i.e., SCG configuration). In the MN configuration, the MN 104B configures the MCG which includes at least one serving cell (e.g., the cell 124B and / or other cell(s)) operated by the MN 104B. In the serving DU configuration, the S-SN 104 A configures the SCG which includes at least one serving cell (e.g., the cell 124A and / or other cell(s)) operated by the S-SN 104A. In some implementations, the MN configuration includes multiple configuration parameters and the UE 102 receives the configuration parameters in one or more RRC messages from the MN 104B. As described for Fig. 3, the serving DU configuration includes multiple configuration parameters. In some implementations, the UE 102 receives these configuration parameters in one or more RRC messages from the S-SN 104A, e.g., via the MN 104B and / or on an SRB (e.g., SRB3) that the MN 104B or S-SN 104 A configures to exchange RRC messages between the UE 102 and the S-SN 104A.

[0142] While communicating with the UE 102 in DC with the MN 104B and S-SN 104 A, the S-SN 104A can perform 696 an intra-CU LTM configuration procedure with the UE 102, similar to the procedures 396 and / or 496. While communicating w ith the UE 102 in DC with the MN 104B and S-SN 104A, the S-SN 104A can perform 680 an intra-CU LTM procedure with the UE 102, similar to the procedures 380 and / or 480. In the procedure 696 or 680, theCU of the S-SN 104 A may transmit one or more RRC reconfiguration messages, each including one or more LTM candidate configurations, to the UE 102 via the SRB3, similar to the procedure 394 or 494. Alternatively, the CU of the S-SN 104A may transmit one or more RRC reconfiguration messages, each including one or more LTM candidate configurations, to the UE 102 via the MN 104B. In response to each of the RRC reconfiguration message(s), the UE 102 transmits a RRC reconfiguration complete message to the S-SN 104A via the MN 104B.

[0143] While communicating in DC with the MN 104B and S-SN 104 A, the UE 102 can transmit 604A at least one measurement report to the S-SN 104A directly, e.g., via the SRB3, similar to the events 304 / 306, the events 404 / 406 and the event 504. Alternatively, the UE 102 can transmit the measurement report(s) to the MN 104B. The MN 104B generates at least one SN message including the measurement report(s) and transmits the SN message(s) to the CU 172. In one implementation, the SN message(s) include RRC Transfer message(s) and / or SN Modification Request message(s). The S-SN 104A (e.g., the CU of the S-SN 104A) generates a measurement configuration to configure the UE 102 to transmit the measurement report(s) and transmits the measurement report to the UE 102 directly (e.g., via the S-DU of the S-SN 104 A) or via the MN 104B.

[0144] After (e.g., in response to) receiving one or some of the measurement report(s) from the UE 102, the S-SN 104A (e.g., the CU of the S-SN 104A) determines to prepare a first cell (e.g., the cell 126A) as a LTM candidate cell for the UE 102. In response to the determination, the S-SN 104A generates a SN Required message (a first SN Required message) including a first cell ID (e.g., cell ID 1) of the first cell (e.g., cell 1) and / or a target SN ID indicating the C- SN 106 A. In some implementations, the SN Required message includes a LTM indicator indicating the SN Required message concerns LTM for the first cell ID. The S-SN 104A transmits 603 the SN Required message to the MN 104B. After (e.g., in response to) receiving the SN Required message, the MN 104B transmits 605 a SN Request message (a first SN Request message) including the first cell ID to the CU 172 to request preparing the first cell as a LTM candidate cell for the UE 102. In response to the SN Request message, the CU 172 performs a LTM preparation procedure 690 with the DU 174 to prepare the first cell as a LTM candidate cell for the UE 102, similar to the procedure 390. 490 or 590. In the procedure 690, the CU 172 transmits a first CU-to-DU message including the first cell ID to the DU 174 to request preparing the first cell, similar to the event 308. In response, the CU 172 may receive a first DU-to-CU message including a LTM DU configuration 1 from the DU 174, similar to the event 310. The CU 172 generates a first LTM candidate configuration (LTM candidateconfiguration 1). In response to the SN Request message, the CU 172 transmits 607 a SN Request Acknowledge message (a first SN Request Acknowledge message) including the first LTM candidate configuration to the MN 104B. In some implementations, the CU 172 includes the first cell ID in the SN Request Acknowledge message to indicate that the first LTM candidate configuration is provided for or associated with the first cell (ID). The MN 104B transmits 609A a SN Confirm message (e.g., a first SN Confirm message) including the first LTM candidate configuration to the S-SN 104A. In some implementations, the MN 104B includes the first cell ID in the SN Confirm message to indicate that the first LTM candidate configuration is provided for or associated with the first cell (ID).

[0145] The events 603, 605, 690, 607 and 609A are collectively referred to in Fig. 6A as an SN-initiated inter-SN LTM preparation procedure 698 A.

[0146] In some implementations, the SN Required message and the SN Confirm message are a SN Change Required message and a SN Change Confirm message, respectively. In other implementations, the SN Required message and the SN Confirm message are a SN Modification Required message and a SN Modification Confirm message, respectively. In some implementations, the SN Request message and the SN Request Acknowledge message are a SN Addition Request message and a SN Addition Request Acknowledge message, respectively. In other implementations, the SN Request message and the SN Request Acknowledge message are a SN Modification Request message and a SN Modification Request Acknowledge message, respectively.

[0147] In some implementations, the SN Required message includes a DU ID of the S-DU of the S-SN 104A. In such cases, the MN 104B may include the DU ID in the SN Request message and the CU 172 may include the DU ID in the first CU-to-DU message. In other implementations, the SN Required message includes a first BS ID of the S-SN 104A. In some implementations, the MN 104B may include the first BS ID in the SN Request message. When receiving the first BS ID. the CU 172 may include the first BS ID in the first CU-to-DU message. In some implementations, the MN 104B may include a second BS ID of the MN 104B in the SN Request message. When receiving the second BS ID, the CU 172 may include the second BS ID in the first CU-to-DU message. In some implementations, the first BS ID and the second BS ID are gNB IDs.

[0148] The CU 172 may or may not request a LTM reference DU configuration in the procedure 690. as described for Figs. 3, 4 and 5. The DU 174 may or may not transmit a LTMreference DU configuration to the CU 172 in the procedure 690, as described for Figs. 3, 4 and 5. In some implementations, the S-SN 104A (e.g., the CU of the S-SN 104A) may obtain a LTM reference configuration, as described for Figs. 3 and 4. In other implementations, the S- SN 104A may receive a LTM reference configuration from the MN 106B (not shown in Fig. 6A) in another inter-SN LTM preparation procedure as described above and below. If the S-SN 104A obtains a LTM reference configuration, the S-SN 104A may include the LTM reference configuration (S-SN generated LTM reference configuration) in the SN Required message. In turn, the MN 104B includes the LTM reference configuration in the SN Request message. Alternatively, the S-SN 104 A determines to request or cause the C-SN 106A to provide a complete LTM candidate configuration so that the S-SN 104A does not transmit the LTM reference configuration to the C-SN 106A. If the S-SN 104A does not obtain a LTM reference configuration, the S-SN 104A does not include a LTM reference configuration in the SN Required message. If the SN Required message includes a LTM reference configuration, the MN 104B includes the LTM reference configuration in the SN Request message. Otherwise, if the SN Required message does not include a LTM reference configuration, the MN 104B may not include the LTM reference configuration in the SN Request message.

[0149] If the SN Request message includes a LTM reference configuration as described above, the CU 172 may include the LTM reference configuration in the first CU-to-DU message. Alternatively, the CU 172 may extract a LTM reference DU configuration from the LTM reference configuration and includes the LTM reference DU configuration in the first CU- to-DU message. Otherwise, if the SN Request message does not include a LTM reference configuration, the CU 172 may or may not receive a LTM reference DU configuration from the DU 174 as described for Fig. 3. If the CU 172 receives a LTM reference DU configuration (e.g., in the first DU-to-CU message), the CU 172 generates a LTM reference configuration (C-SN generated LTM reference configuration) including the LTM reference DU configuration. The CU 172 may include a LTM reference CU configuration (candidate CU (C-CU) generated LTM reference CU configuration). Otherwise, if the CU 172 does not receive a LTM reference DU configuration from the DU 174 as described for Fig. 3. the CU 172 does not generate a LTM reference configuration. Alternatively, the CU 172 generates a LTM reference configuration (C-SN generated LTM reference configuration) only including a C-CU generated LTM reference CU configuration. In cases where the CU 172 generates a LTM reference configuration (C-SN generated LTM reference configuration), the CU 172 includes the C-SN generated LTM reference configuration in the SN Request Acknowledge message.

[0150] Tn some implementations, if the LTM DU configuration 1 is a complete configuration, the CU 172 generates the LTM candidate configuration 1 as a complete configuration. The CU 172 may include a complete configuration indication (e g., a BS-to-BS interface protocol field / IE) in the SN Request Acknowledge message to indicate that the LTM candidate configuration 1 is a complete configuration. In some implementations, the BS-to-BS interface protocol is an Xn application protocol defined in 3GPP specification 38.423. In some implementations, the complete configuration indication is a new field / IE (e.g., LTM specific) to avoid an impact to non-LTM configurations. In other implementations, the complete configuration indication is an existing field / IE defined in 3GPP specification 38.423. Otherw ise, if the LTM DU configuration 1 is a delta configuration, the CU 172 generates the LTM candidate configuration 1 as a delta configuration. The CU 172 may exclude the complete configuration indication from the SN Request Acknowledge message to indicate that the LTM candidate configuration 1 is a delta configuration. Alternatively, the CU 172 may include a delta configuration indication (e g., a BS-to-BS interface protocol field / IE) in the SN Request Acknowledge message to indicate that the LTM candidate configuration 1 is a delta configuration. In some implementations, the BS-to-BS interface protocol is an Xn application protocol defined in 3GPP specification 38.423. In some implementations, the delta configuration indication is a new field / IE (e.g., LTM specific) to avoid an impact to non-LTM configurations. In other implementations, the delta configuration indication is an existing field / IE defined in 3GPP specification 38.423. In some implementations, the BS-to-BS interface protocol field / IE have two values (i.e., a first value and a second value). The BS-to- BS interface protocol field / IE set to the first value is the complete configuration indication and the BS-to-BS interface protocol field / IE set to the second value is the delta configuration indication.

[0151] In some implementations, the S-SN 104A is preconfigured with a CSI resource configuration (e.g., (LTM) CSI resource configuration 1) and / or a LTM SSB configuration (LTM SSB configuration 1) for the first cell. In yet other implementations, the CU 172 receives the CSI resource configuration and / or the LTM SSB configuration from an 0AM (Operations. Administration and Maintenance) node. In yet other implementations, the S-SN 104A receives the CSI resource configuration and / or the LTM SSB configuration from the CU 172. For example, the CU 172 includes the CSI resource configuration and / or the LTM SSB configuration in the SN Request Acknowledge message. In this case, the MN 104B may include the CSI resource configuration and / or the LTM SSB configuration in the SN Confirm message.In some implementations, the CU 172 includes a PCI of the first cell in the SN Request Acknowledge message. In this case, the MN 104B may include the PCI of the first cell in the SN Confirm message. To prepare the first cell as a candidate LTM cell for the UE 102, the CU of the S-SN 104A performs a LTM CSI report configuration and / or LTM ID configuration procedure (not shown in Fig. 6A) with an S-DU of the S-SN 104 A, similar to the procedure 392 or 492. In the LTM CSI report configuration and / or LTM ID configuration procedure, the CU of the S-SN 104A transmits the CSI resource configuration and / or the LTM SSB configuration to the S-DU of the S-SN 104A. In response, the CU of the S-SN 104A receives one or more CSI report configurations for the UE 102 from the S-DU of the S-SN 104A. In some implementations, the S-SN 104A receives a second serving DU configuration including the CSI report configuration(s).

[0152] In some implementations, the CU 172 receives early synchronization information for the first cell and / or PDCCH order information from the DU 174, as described for Fig. 5. In some implementations, the early synchronization information includes a RACH configuration (e.g., RACH configuration 1) and / or at least one TCI state configurations (e.g., TCI state configuration(s) 1). The CU 172 includes the early synchronization information and / or the PDCCH order information in the SN Request Acknowledge message. The MN 104B includes the early synchronization information and / or the PDCCH order information in the SN Confirm message.

[0153] In some implementations, the CU 172 assigns a LTM ID (e.g., LTM ID 1) for identifying the first LTM candidate configuration and includes the LTM ID and / or an associated (or mapped) cell ID for the LTM ID in the SN Request Acknowledge message. The MN 104 includes the LTM ID and / or an associated (or mapped) cell ID for the LTM ID in the SN Confirm message. In other implementations, the S-SN 104A assigns a LTM ID (e.g.. LTM ID 1) for identifying the first LTM candidate configuration. In yet other implementations, the MN 104B assigns a LTM ID (e.g., LTM ID 1 ) for identifying the first LTM candidate configuration. In such cases, the MN 104B may include the LTM ID in the SN Confirm message. After receiving or assigning the LTM ID, the CU of the S-SN 104A transmits the LTM ID and the first cell ID to the S-DU in a LTM ID configuration procedure, similar to the procedure 390, 392 or 492.

[0154] After (e.g.. in response to) receiving the SN Confirm message, the S-SN 104A (e.g., the CU of the S-SN 104A) performs 694 LTM configuration delivery procedure with the UE102 to transmit the LTM ID and the LTM candidate configuration to the UE 102. In some implementations, the S-SN 104 A transmits {LTM ID, the LTM candidate configuration} as a tuple in a first RRC reconfiguration message in the procedure 694. Depending on the implementations, the S-SN 104A may include the LTM reference configuration, the CSI report configuration(s), the CSI resource configuration, the RACH configuration, the TCI state configuration(s), the LTM SSB configuration and / or the PCI of the first cell to the UE 102 in the first RRC reconfiguration message and / or other RRC reconfiguration message(s) transmitted to the UE 102, as described for Figs. 3 and 4. The S-SN 104A includes the LTM ID in the first RRC reconfiguration or the other RRC reconfiguration message(s) to indicate the CSI resource configuration, the RACH configuration, the TCI state configuration(s), the LTM SSB configuration and / or the PCI of the first cell are associated with the first cell. For example, the S-SN 104A includes the CSI resource configuration, the RACH configuration, the TCI state configuration(s). the LTM SSB configuration and / or the PCI of the cell 1 in the tuple. In another example, the S-SN 104A includes {LTM ID 1, the CSI resource configuration, the RACH configuration, the TCI state configuration(s), the LTM SSB configuration and / or the PCI of the cell 1 } as a tuple in the other RRC reconfiguration message(s). In response to each of the other RRC reconfiguration message(s). the UE 102 transmits a RRC reconfiguration complete message to the CU 172 via the S-DU 174A.

[0155] In some implementations, if the SN Required message includes the complete configuration indication to indicate that the LTM candidate configuration 1 is a complete configuration, the S-SN 104A includes, in the first RRC reconfiguration message, a complete configuration indication (e g., a RRC field / IE) to indicate that the LTM candidate configuration 1 is a complete configuration. Otherwise, if the SN Required message does not include the complete configuration indication or includes the delta configuration indication to indicate that the LTM candidate configuration 1 is a delta configuration, the S-SN 104 A excludes or does not include, in the first RRC reconfiguration message, the complete configuration indication (e.g., a RRC field / IE) to indicate that the LTM candidate configuration 1 is a delta configuration.

[0156] If the SN Confirm message includes the PDCCH order information (PDCCH order information 1), the S-SN 104A may transmit 650A a PDCCH order to the UE 102, based on the PDCCH order information. If the S-SN 104A is a distributed base station, the CU of the S- SN 104A may transmit the PDCCH order information to the S-DU of the S-SN 104A and the S-DU may transmit 650A the PDCCH order to the UE 102. For example, the S-SN 104A orthe S-DU of the S-SN 104A transmits 650A a PDCCH order to the UE 102, including the PDCCH order information. In some implementations, the S-SN 104A or the S-DU may determine to transmit the PDCCH order, based on (e.g., in response to) the measurement report(s) 624A. In some implementations, the S-SN 104A or the S-DU may determine a SSB index included in the PDCCH order, based on LI measurement report(s) 624A, and / or the CSI resource configuration, the CSI report configuration and / or the LTM SSB configuration. In some implementations, the S-DU or the S-SN 104A includes the LTM ID 1 in the PDCCH order to indicate the first cell. The UE 102 transmits 652 a RA preamble to the DU 174 on the first cell, using the RACH configuration and / or the PDCCH order information. The S-DU or the S-SN 104A derives a TA value based on the RA preamble. The DU 174 transmit 656 aDU- CU TA Information Transfer message including the TA value to the CU 172. The CU 172 transmits 657 a CU-CU TA Information Transfer message including the TA value to the MN 104B (e.g.. the CU of the MN 104B). The MN 104B transmits 658 a CU-CU TA Information Transfer message including the TA value to the S-SN 104A. In some implementations, the DU 174 includes the cell ID 1, the RA preamble index, a RA-RNTI, and / or the DU ID of the S-DU of the S-SN 104A in the message 656. The DU 174 may additionally include the first BS ID and / or the second BS ID in the message 656. In some implementations, the CU 172 includes the cell ID 1, the RA preamble index, the RA-RNTI, and / or the DU ID of the S-DU in the message 657. In some implementations, the CU 172 may additionally include the first BS ID and / or the second BS ID in the message 657. The MN 104B then includes the cell ID 1, the RA preamble index, the RA-RNTI, and / or the DU ID of the S-DU in the message 658. In some implementations, the MN 104B may additionally include the first BS ID and / or the second BS ID in the message 658.

[0157] In some implementations, the CU 172 determines an address (e.g., an IP address) of the MN 104B or the CU of the MN 104B, based on the second BS ID. Thus, the CU 172 transmits the message 657 to the MN 104B in accordance with the address. In some implementations, the MN 104B determines an address (e g., an IP address) of the S-SN 104A or the CU of S-SN 104A, based on the first BS ID. In other implementations, the MN 104B determines an address (e.g., an IP address) of the S-SN 104A or the CU of the S-SN 104A, based on the DU ID of the S-DU of the S-SN 104A. With these implementations, the MN 104B sends 658 the CU-CU TA Information Transfer message to the S-SN 104A or the CU of the S- SN 104 A in accordance with the address.

[0158] Tn response to determining to command the UE 102 to perform a LTM cell switch to the first cell, e.g., based on the LI measurement report(s) 624A and / or 654A, the S-DU or the S-SN 104A transmits 626Athe LTM Cell Switch Command including the LTM ID 1 to the UE 102. In response to the LTM Cell Switch Command, the UE 102 may stop communication on the serving cell(s). In response to the LTM Cell Switch Command, the UE 102 accesses 632 the first cell and transmits 636A a RRC reconfiguration complete message to DU 174. The DU 174 in turn transmits 638 a DU-to-CU message including the RRC reconfiguration complete message to the CU 172. In some alternatively implementations, the UE 102 transmits the RRC reconfiguration complete message to the C-SN 106A via the MN 104B instead of via the DU 174. After receiving 638 the DU-to-CU message or the RRC reconfiguration complete message, the C-SN 106A communicates 640 with the UE 102 in DC with the MN 104B and the C-SN 106A in accordance with the first LTM candidate configuration and / or the LTM reference configuration. In some implementations, the UE 102 includes the LTM ID 1 in the RRC reconfiguration complete message 636Ato indicate that the UE 102 applies the first LTM candidate configuration. In accordance with the LTM ID 1, the CU 172 identifies the first LTM candidate configuration and / or the LTM reference configuration. In other implementations, the CU 172 identifies the first LTM candidate configuration and / or the LTM reference configuration based on the first cell ID included in the Access Success message 634. In such implementations, the CU 172 maintains or stores association information between the first cell ID, and the first LTM candidate configuration and / or the LTM reference configuration. When the CU 172 receives the first cell ID in the Access Success message, the CU 172 identifies the first LTM candidate configuration and / or the LTM reference configuration in accordance with the first cell ID and the association information.

[0159] In some implementations, if the S-DU or the S-SN 104A receives a TA value as described above, the S-DU or the S-SN 104A may include the TA value in the LTM Cell Switch Command. In some implementations, the S-DU or the S-SN 104A includes a first TCI state ID in the LTM Cell Switch Command. The first TCI state ID indicates a first one of the TCI state configuration(s).

[0160] In response to determining to command the UE 102 to perform the LTM cell switch or transmitting 626 A the LTM Cell Switch Command, the S-DU of the S-SN 104A transmits a DU-CU Cell Switch Noti fication message to the CU of the S-SN 104A to indicate that the UE 102 performs a LTM cell switch to the first cell. In response to receiving the DU-CU Cell Switch Notification message, the CU of the S-SN 104A transmits 627A a CU-CU Cell SwitchNotification message to the MN 104B to indicate that the UE 102 performs or is performing a LTM cell switch to the first cell. In response, the MN 104B transmits 628 a CU-CU Cell Switch Notification message to the CU 172 to indicate that the UE 102 performs or is performing a LTM cell switch to the first cell. In response, the CU 172 transmits 630 a CU-DU Cell Switch Notification message to the DU 174 to indicate that the UE 102 performs or is performing a LTM cell switch to the first cell. In some implementations, the S-SN 104A includes the first TCI state ID in the CU-CU Cell Switch Notification message 627A. In such cases, the MN 104B includes the first TCI state ID in the CU-CU Cell Switch Notification message 628. The CU 172 then includes the first TCI state ID in the CU-DU Cell Switch Notification message. The UE 102 and the DU 174 identify the first one of the TC state configuration(s) based on the first TCI state ID and apply the first TCI state configuration to communicate UL transmissions and / or DL transmissions in the events 632, 636A and / or 640.

[0161] In some implementations, after (e.g., in response to) determining to command the UE 102 to perform the LTM cell switch or transmitting 626A the LTM Cell Switch Command, the S-SN 104 A transmits 631 one or more Early Status Transfer messages to the MN 104B, each including a DL COUNT value or a DISCARD DL COUNT value for a DRB over which the UE 102 and the S-SN 104 A communicate 602 data with each other. The MN 104B transmits one or more Early Status Transfer messages to CU 172. each including the DL COUNT value or the DISCARD DL COUNT value for the DRB over which the UE 102 and the S-SN 104A communicate 602 data with each other.

[0162] In some implementations, after receiving 634 the Access Success message or receiving 638 the DU-to-CU message or the RRC reconfiguration complete message, the CU 172 transmits 639 a LTM Success message to the MN 104B (e.g., the CU of the MN 104B) to indicate that the LTM cell switch is completed successfully. In some implementations, the LTM Success message is a SN Modification Required message or a BS-to-BS Access Success message. In some implementations, the CU 172 includes the first cell ID in the LTM Success message. In other implementations, the CU 172 does not transmit a BS-to-BS message to the MN 104B (e g., the CU of the MN 104B) to indicate that the LTM cell switch is completed successfully. In some implementations, after (e.g., in response to) receiving the LTM Success message or receiving the RRC reconfiguration complete message from the UE 102, the MN 104B may transmit a SN message (as shown event 645 in Fig. 6C) to the S-SN 104 A. The SN message may indicate that the LTM cell switch is completed successfully, indicate the S-SN 104A to suspend communication with the UE 102, or indicate the S-SN 104Ato release a UEcontext of the UE 102 and resources configured for the UE 102. The MN 104B may include the first cell ID in the SN message. In some implementations, the SN message is a SN Modification Request message, a SN Release Request message, a SN Access Success message or the like.

[0163] In some implementations, after (e.g.. in response to) determining to command the UE 102 to perform the LTM cell switch, transmitting 626A the LTM Cell Switch Command, receiving the DU-CU Cell Switch Notification message from the S-DU, or receiving the SN message, the S-SN 104A (e.g., the CU of the S-SN 104A) transmits 641 a SN Status Transfer message to the MN 104B, including a DL COUNT value and / or a UL COUNT value for a / the DRB over which the UE 102 and the S-SN 104A communicate 602 data with each other. After (e.g., in response to) receiving the SN Status Transfer message 641, the MN 104B transmits 642 a SN Status Transfer message to the CU 172, including the DL COUNT value and / or the UL COUNT value.

[0164] In some implementations, the S-SN 104A (e.g., the CU of the S-SN 104A) may prepare additional cell(s) (i.e., cell(s) 2, ... , N) as LTM candidate cell(s) for the UE 102 with the MN 104B and one or more C-SNs (including the C-SN 106A), before or after transmitting the LTM Cell Switch Command or during, before or after the procedure 698A, as described above. N is an integer and larger than 1. The cell(s) 2, .. . , N may be operated by the C-SN(s). For example, the S-SN 104A performs additional inter-SN LTM preparation procedure(s) 2, . .. , N with the MN 104B to prepare the cell(s) 2, . . . N respectively. Each of the inter-SN LTM preparation procedure(s) 2, ... , N is similar to the procedure 698A. In the inter-SN LTM preparation procedure(s) 2, ... , N, the S-SN 104A receives LTM candidate configuration(s) 2, . .. , N configuring the cell(s) 2, . .. , N for LTM, respectively. As described above, the MN 104B, S-SN 104A or C-SN(s) assign LTM ID(s) 2, ... , N to identify the LTM candidate configuration(s) 2, ... , N, respectively. The S-SN 104Amay obtain CSI resource configuration 2, ,... , N for the cell(s) 2, ... , N respectively, as described for the CSI resource configuration1. The S-SN 104A may obtain CSI report configuration(s) 2, ... , N or the cell(s) 2, ... , N, respectively, as described for the CSI report configuration(s) 1. The S-SN 104A may obtain RACH configuration 2, .. . , N for the cell(s) 2, .. . , N respectively, as described for the RACH configuration 1. The S-SN 104A may obtain TCI state configuration(s) 2, .. . , N for the cell(s)2, ... , N respectively, as described for the TCI state configuration(s) 1. The S-SN 104 A may obtain LTM SSB configuration 2, ... , N for the cell(s) 2, ... , N, respectively, as described for LTM SSB configuration 1. In some implementations, the S-SN 104A may perform LTMconfiguration delivery procedure 2, ... , N with the UE 102 to transmit the {LTM ID 2, the LTM candidate configuration 2, the CSI resource configuration 2 (if obtained), the TCI state configuration 2 (if obtained), the RACH configuration 2 (if obtained), the LTM SSB configuration 2 (if obtained)}, ... , {the LTM ID N, the LTM candidate configuration N, the CSI resource configuration N, the TCI state configuration(s) N (if obtained), the RACH configuration N (if obtained), the LTM SSB configuration N (if obtained)} to the UE 102, respectively. Each of the LTM configuration delivery procedure 2, ... , N is similar to the procedures 394, 494 and / or 594. In other implementations, the S-SN 104A includes the tuples in the first RRC reconfiguration message.

[0165] In some implementations, a SN Required message and a SN Confirm message in each of the inter-SN LTM preparation procedure(s) 2, ... , N are a SN Modification Required message and a SN Modification Confirm message, respectively. In other implementations, a SN Required message and a SN Confirm message in each of the inter-SN LTM preparation procedure(s) 2. . .. , N are a SN Change Required message and a SN Change Confirm message, respectively. In some implementations, a SN Request message and a SN Request Acknowledge message in each of the inter-SN LTM preparation procedure(s) 2, . . . , N are a SN Addition Request message and a SN Addition Request Acknowledge message, respectively. In other implementations, the SN Request message and the SN Request Acknowledge message in each of the inter-SN LTM preparation procedure(s) 2. .... N are a SN Modification Request message and a SN Modification Request Acknowledge message, respectively. In some implementations, the information provided in the SN Confirm message (e.g., LTM candidate configuration, LTM reference configuration, first cell ID, or LTM ID) are alternatively provided in an SN Modification Request message from the MN 104B to the S-SN 104A (i.e., similar to the event 609B which will be described in the scenario 600B).

[0166] In other implementations, the S-SN 104A performs the procedure 698A with the CU 172 to prepare (one or more of) the cell 1 and cell(s) 2, . . . , N as LTM candidate cell(s) for the UE 102. The cell(s) 2, . . . , N are identified by cell ID(s) 2, .. . , N respectively and operated by the DU 174 and / or other DU(s) of the C-SN 106A. In such implementations, the S-SN 104A includes the cell ID(s) 2, ... , N in the SN Required message 603 for LTM and the MN 104B includes the cell ID(s) 2, . .. , N in the SN Request message, as descried for the cell ID 1 above. In some implementations, upon receiving the SN Request message, the CU 172 determines or selects the cell(s) 1 , . . . , M from the cell(s) 1 , . .. , N as LTM candidate cell(s). M is a positive integer and M < N. In other implementations, CU 172 prepares the cell(s) 1, . . . , N for LTM asrequested in the SN Request message. The CU 172 performs LTM preparation procedure(s) 2, ... , M with the DU 172 to prepare the cell(s) 2, ... , M as LTM candidate cell(s) for the UE 102, respectively. The LTM preparation procedure(s) 2, .. . , M are similar to the procedure 690 that the CU 172 performs with the DU 174 to prepare the cell 1. The CU 172 obtains the LTM candidate configuration(s) 2, ... , M for the cell(s) 2, ... , M as a result of the LTM preparation procedure(s) 2, ... , M respectively, similar to obtaining the LTM candidate configuration 1. The C-SN 106A may generate the LTM candidate configuration(s) 2, ... , M as complete configuration(s) or generate delta configuration(s) based on the LTM reference configuration, as descnbed for the LTM candidate configuration 1. The CU 172 includes the LTM candidate configuration(s) 2, . . . , M in the SN Request Acknowledge message. In some implementations, the CU 172, the MN 104B or the S-SN 104A assigns LTM ID(s) 2, . .. , M to identify the LTM preparation procedure(s) 2, . . . , M respectively, as described for the LTM ID 1 and the LTM candidate configuration 1. In the case the CU 172 assigns the LTM ID(s) 1. ... , M, the CU 172 includes the LTM ID(s) 1, ... , M with the LTM candidate configuration(s) 1, ... , M, respectively in the SN Request Acknowledge message, as described for the LTM ID 1 and the LTM candidate configuration 1.

[0167] In some implementations, the CU 172 obtains early synchronization information 2, ... , M for the cell(s) 2, ... , M, respectively, as described for the early synchronization information 1. The CU 172 includes the early synchronization information 2. .... M in the SN Request Acknowledge message. In some implementations, the CU 172 or the S-SN 104A obtains CSI resource configuration(s) 2, ... , M for the cell(s) 2, ... , M, respectively, as described for the CSI resource configuration 1. In the case that the CU 172 obtains the CSI resource configuration(s) 2, ... , M, the CU 172 includes the CSI resource configuration(s) 2, . .. , M in the SN Request Acknowledge message.

[0168] In some implementations, the CU 172 or the S-SN 104A obtains LTM SSB configuration(s) 2, ... , M for the cell(s) 2, ... , M, respectively, as described for the LTM SSB configuration 1. In the case that the CU 172 obtains the LTM SSB configuration(s) 2, ... , M, the CU 172 includes the LTM SSB configuration(s) 2, .. . , M in the SN Request Acknowledge message. In some implementations, the CU 172 or the S-SN 104A obtains PCI(s) 2, . . . , M for the cell(s) 2, . . . , M, respectively, as described for the PCI 1. In the case that the CU 172 obtains the PCI(s) 2, . . . , M, the CU 172 includes the PCI(s) 2, .. . , M in the SN Request Acknowledge message.

[0169] Tn some implementations, the CU 172 includes a list of {the cell ID 1 , the LTM ID 1 (if obtained or optional), the LTM candidate configuration 1, the CSI resource configuration 1 (if obtained or optional), the TCI state configuration 1 (if obtained or optional), the early synchronization information 1 (if obtained or optional), the LTM SSB configuration 1 (if obtained or optional), PCI 1 (if obtained or optional)}, , {the cell ID M, the LTM ID M (if obtained or optional), the LTM candidate configuration M, the CSI resource configuration M (if obtained or optional), the TCI state configuration M (if obtained or optional), the early synchronization information M (if obtained or optional), the LTM SSB configuration M (if obtained or optional), the PCI M (if obtained or optional)} in the SN Request Acknowledge message. The MN 104B include the list or a portion of the list in the SN Confirm message.

[0170] In some implementations, the CU 172 obtains PDCCH order information 2, ... , M for the cell(s) 2, . . . , M, respectively, as described for the PDCCH order information 1. In one implementation, the CU 172 includes the PDCCH order information 2, . . . , M in the SN Request Acknowledge message. In another implementation, the CU 172 includes the PDCCH order information 2, . . . , M in the early synchronization information 2, . . . , M, respectively. The MN 104B may include the PDCCH order information 2, ... , M in the SN Confirm message as described for the PDCCH order information 1. The S-SN 104A may obtain RACH configuration 2, TCI state configuration(s) 2 and / or the PDCCH order information 2, ...., RACH configuration M, TCI state configuration(s) M and / or the PDCCH order information M from the early synchronization information 2, . . . , M, respectively or from the SN Confirm message.

[0171] In some implementations, the S-SN 104A may perform LTM configuration delivery procedure 2, ... , M with the UE 102 to transmit the tuples {LTM ID 2, the LTM candidate configuration 2, the CSI resource configuration 2 (if obtained), the TCI state configuration 2 (if obtained), the RACH configuration 2 (if obtained), the LTM SSB configuration 2 (if obtained), the PCI 2 (if obtained)}, ... , {the LTM TD M, the LTM candidate configuration M, the CSI resource configuration M, the TCI state configuration(s) M (if obtained), the RACH configuration M (if obtained), the LTM SSB configuration M (if obtained), the PCI M (if obtained)} to the UE 102, respectively. Each of the LTM configuration delivery procedure 2, ... , M is similar to the procedures 394, 494 and / or 594. In other implementations, the S-SN 104A includes the tuples in the first RRC reconfiguration message.

[0172] Tn some implementations, the MN 104B may include measurement result(s) 1 , . . . , N for the cell(s) 1, . . . , N respectively in the SN Request message. In some implementations, the MN 104B may receive the measurement result(s) from the UE 102 and / or in the SN Required message from the S-SN 104A. The C-SN 106A may select or determine the cell(s) 1, ... M, based on the measurement result(s) 1, ... , N. In other implementations, the C-SN 106A may select or determine the cell(s) 1, .. . M, based on other factors (e.g., capacity or load of the cell(s) 1, ... , N and / or a maximum number of LTM candidate cell(s)). In one implementation, the maximum number is included in the SN Request message. In another implementation, the maximum number is a predetermined number.

[0173] The events 626 A, 627A. 628, 630. 631, 632, 633 and 634 are collectively referred to in Fig. 6A as an LTM execution procedure 699.

[0174] Referring next to Fig. 6B, a scenario 600B is generally similar to the scenario 600 A. except that the scenario 600B includes events 604B, 609B and 611 instead of events 603 and 609 A. In the scenario 600B, the MN 104B initiates 698B inter-SN LTM preparation procedure, while in the scenario 600A, the S-SN 104A initiates 698A inter-SN LTM preparation procedure. While communicating in DC with the MN 104B and S-SN 104A, the UE 102 can transmit 604B at least one measurement report to the MN 104B, e.g., via the SRBL similar to the events 304 / 306, the events 404 / 406 and the event 504. If the MN 104B is a distributed base station, the MN 104B includes a CU and a DU. The CU of the MN 104B receives the measurement report(s) from the UE 102 via the DU of the MN 104B. The MN 104B (e.g., the CU of the MN 104B) generates a measurement configuration to configure the UE 102 to transmit the measurement report(s) and transmits the measurement configuration to the UE 102 (e.g., via the DU of the MN 104B).

[0175] After (e.g., in response to) receiving one or some of the measurement report(s) from the UE 102, the MN 104B (e.g., the CU of the MN 104B) determines to prepare a first cell (e.g., the cell 124B) as a LTM candidate for the UE 102. In response to the determination, the MN 104B generates a SN Request message (a first SN Request message) including a first cell ID (e.g., cell ID 1) of the first cell (e.g., cell 1) and transmits 605 the SN Request message to the C-SN 106 A. In response to the SN Request message, the CU 172 (decides and) performs the LTM preparation procedure 690 with the DU 174 and transmits 607 the SN Request Acknowledge message to the MN 104B, as described for Fig. 6A. After (e.g., in response to) receiving the message 607, the MN 104B transmits 609B a SN Modification Request messageto the S-SN 104 A, including a first LTM candidate configuration (LTM candidate configuration 1), a LTM reference configuration, and / or the first cell ID, similar to the event 609A. If the SN Request Acknowledge message includes LTM related configurations such as the RACH configuration, the TCI state configuration(s). the CSI resource configuration, the LTM SSB configuration and / or the PCI of the first cell for configuring the first cell as a LTM candidate cell, the MN 104B includes the LTM related configurations in the SN Modification Request message. In response to the SN Modification Request message, the S-SN 104A transmits 611 a SN Modification Request Acknowledge message to the MN 104B and performs 694 the LTM configuration delivery procedure with the UE 102 to transmit the first LTM candidate configuration and / or the LTM reference configuration to the UE 102. The events 605, 690, 607, 609B and 611 are collectively referred to in Fig. 6B as an MN-initiated inter-SN LTM preparation procedure 698B.

[0176] As described for Fig. 6A, the SN Request Acknowledge message 607 may include the PDCCH order information. If the SN Request Acknowledge message 607 includes the PDCCH order information, the MN 104B includes the PDCCH order information in the SN Modification Request message. If the SN Modification Request message includes the PDCCH order information, the S-SN 104A may transmit 650A a PDCCH order to the UE 102, based on the PDCCH order information, as described for Fig. 6A. If the SN Modification Request message includes the TCI state configured on(s), the S-SN 104A may include a first TCI state ID in the LTM Cell Switch Command as described for Fig. 6A.

[0177] In some implementations, the MN 104B (e.g., the CU of the MN 104B) may perform one or more LTM preparation procedures to prepare additional cell(s) (i.e., cell(s) 2, ... , N) as LTM candidate cell(s) for the UE 102 with the CU 172 or other C-SN(s), and each of the LTM preparation procedure is similar to the procedure 698B. The MN 104B may perform the LTM preparation procedure(s) before or after transmitting the LTM Cell Switch Command or during, before or after the procedure 698B.

[0178] In other implementations, the MN 104B performs the procedure 698B with the CU 172 to prepare (one or more of) the cell 1 and cell(s) 2, . . . , N as LTM candidate cell(s) for the UE 102. N is an integer larger than 1. The cell(s) 2, . . . , N are identified by cell ID(s) 2, .. . , N, respectively and operated by the DU 174 and / or other DU(s) of the C-SN 106A. In such implementations, the MN 104B includes the cell ID(s) 2, ... , N in the SN Request message 605, as descried for the cell ID 1 above.

[0179] Referring next to Fig. 6C, a scenario 600C is generally similar to the scenarios 600A and 600B, except that the scenario 600C includes events 694C, 636C and 645 instead of events 694A, 636A and 638. In the scenario 600C, the MN 104B transmits, to the UE 102, the second serving DU configuration (including the CSI report configuration), the LTM ID, the first LTM candidate configuration, the LTM reference configuration, the CSI resource configuration, the LTM SSB configuration, the RACH configuration, the TCI state configuration(s), and / or the PCI of the first cell for configuring the first cell as a LTM candidate cell in one or more RRC reconfiguration messages in the LTM configuration deliver}’ procedure 694C similar to the procedure 394, 494 o 594. In some implementations, the MN 104B generates the RRC reconfiguration message(s) in the procedure 694C, while the S-SN 104A generates the RRC reconfiguration message(s) in the procedure 694 A. In some implementations, the MN 104B assigns the LTM ID in the scenario 600C, while the S-SN 104A assigns the LTM ID in the scenarios 600A and 600B.

[0180] When the UE 102 performs 699 the LTM execution procedure, the UE 102 transmit 636C a RRC reconfiguration message to the MN 104B, similar to the event 636A. In some implementations, the UE 102 includes the LTM ID in the RRC reconfiguration complete message to indicate that the UE 102 applies the first LTM candidate configuration. After (e.g., in response to) receiving the RRC reconfiguration message, the MN 104B may transmit 645 the SN message to the S-SN 104A as described for Fig. 6A. In some implementations, the MN 104B may include a first cell ID of the first cell in the SN message. The MN 104B may determines the first cell ID based on the LTM ID received in the RRC reconfiguration complete message.

[0181] Referring next to Fig. 6D, a scenario 600D is generally similar to the scenarios 600A, 600B, and 600C, except that the scenario 600D includes events 624D. 650D, 654D, 626D instead of events 624A, 650A. 654A, and 626A. The events 624D, 650D. 654D, and 626D are similar to the events 624A, 650A, 654A, and 626 A respectively, except that the MN 104B is involved in the events 624D, 650D, 654D, and 626D, while the S-SN 104A is involved in the events 624A, 650A, 654 A, and 626A.

[0182] In some implementations, the MN 104B may generate the CSI report configuration(s) based on a CSI resource configuration, as described for S-SN 104A. The CSI resource configuration configures RS(s) transmitted on the first cell. The MN 104B transmits the CSI report configuration(s) to the UE 102 in the procedure 694C. In some implementations, the MN104B is preconfigured with CSI resource configuration. In other implementations, the MN 104B receives the CSI resource configuration from an OAM node. In yet other implementations, the MN 104B receives the CSI resource configuration from the CU 172 or the S-SN 104 A.

[0183] Next, several example methods, which can be implemented in a RAN node (e.g., a base station, a DU or a CU) or a UE, for LTM, are discussed next with reference to Figs. 7A- 15. Descriptions described for Figs. 3-6D can apply to Figs. 7A-15. Similar steps are similarly labeled (e.g., 302, 402, 502, 602, 802, etc.) and individual descriptions are therefore omitted.

[0184] Fig. 7A illustrates an example method 700A, which can be implemented by an S-SN (e.g., the S-SN 104A in Figs. 6A-6D). The method 700A begins at block 702, where the S-SN communicates with a UE in DC with a MN and the S-SN. At block 780, the S-SN might perform at least one intra-SN ETM configuration and / or execution procedure with the UE (e.g.. event 696 or 680). At block 760, the S-SN determines to prepare a first cell of a C-SN as a LTM candidate cell for the UE. At block 703, the S-SN transmits a SN Required message to the MN, requesting preparing the first cell as a LTM candidate cell for the UE. In some implementations, the SN Required message includes a first cell ID of the first cell. At block 709A, the S-SN receives a SN Confirm message from the MN, including a first LTM candidate configuration configuring the first cell as a LTM candidate cell for the UE. At block 762, the S-SN obtains a first LTM CSI resource configuration, configuring CSI resources for the first cell. At block 764, the S-SN generates a first LTM CSI report configuration based on the first LTM CSI resource configuration. At block 718, the S-SN transmits a first LTM candidate configuration, the first LTM CSI resource configuration and the first LTM CSI report configuration to the UE. At block 724, the S-SN receives one or more LI measurement reports from the UE in accordance with the first LTM CSI report configuration. In some implementations, the intra-SN LTM configuration and / or execution procedure(s) includes an intra-SN intra-DU LTM configuration and / or execution procedure similar to the procedure 396 or 380. In other implementations, the intra-SN LTM configuration and / or execution procedure(s) includes an intra-SN inter-DU LTM configuration and / or execution procedure similar to the procedure 496 or 480.

[0185] In some implementations, the S-SN receives the first LTM CSI resource configuration from a network node (e.g., OAM). In other implementations, the S-SN is preconfigured with the first LTM CSI resource configuration in a storage and obtains the first LTM CSI resource configuration from the storage. In some implementations, the first LTM CSIreport configuration configures CST report(ing) for CSI resources configured in the first LTM CSI resource configuration. In some implementations, the CSI resources include one or more reference signals, and / or time and frequency resources for the reference signal(s). The reference signal(s) might include SSB(s) and / or CSI-RS(s).

[0186] In some implementations, the LI measurement report(s) include LI measurement results for the first cell. The LI measurement report(s) may include LI measurement result(s) for a serving cell where the S-SN receives the LI measurement report(s). The S-SN determines whether to command the UE to perform a LTM cell switch to the first cell, based on the LI measurement report(s). If the S-SN determines to command the UE to perform a LTM cell switch to the first cell, the S-SN transmits a LTM cell switch command to the UE, commanding the UE to perform a LTM cell switch to the first cell. In response to commanding the UE to perform the LTM cell switch, the S-SN might transmit a CU-to-CU Cell Switch Notification message to the MN, notifying that the S-SN initiates transmission of a LTM cell switch command to the UE for a LTM cell switch to the first cell. In response to commanding the UE to perform the LTM cell switch, the S-SN might transmit an Early Status Transfer message to the MN, including a DL COUNT value or a DISCARD DL COUNT value for a DRB over which the UE and the S-SN communicate data with each other. After transmitting the LTM cell switch command, the S-SN might receive an LTM Success message from the MN, notifying the LTM cell switch is completed successfully. In response to commanding the UE to perform the LTM cell switch or after transmitting the LTM cell switch command or receiving the LTM Success message, the S-SN might transmit a SN Status Transfer message to the MN, including a UL COUNT value and / or a DL COUNT value for the DRB.

[0187] In some implementations, the S-SN generates at least one first RRC message including the first LTM candidate configuration, a first configuration ID identifying the first LTM candidate configuration, the first LTM CSI resource configuration and the first LTM CSI report configuration. In some implementations, the S-SN generates a first LTM configuration, including the first LTM candidate configuration, the first configuration ID, and the first LTM CSI resource configuration. In some implementations, the first configuration ID is a LTM candidate ID. In some implementations, the S-SN generates a first serving configuration including the first LTM CSI report configuration. For example, the first serving configuration is a cell group configuration (e.g., CellGroupConfig IE). The S-SN at block 718 transmits the first RRC message(s) including the first LTM configuration and the first serving configuration to the UE via the MN or a SRB (e.g.. SRB3). In some implementations, the SN Confirmmessage (a first SN Confirm message) includes the first cell ID to indicate that the first LTM candidate configuration is associated with the first cell. In other implementations, the SN Confirm message includes the first cell ID to respond to the SN Required message (a first SN Required message) including the first cell ID.

[0188] In some implementations, while or after preparing the first cell for LTM, the S-SN may prepare a second cell of the C-SN (i.e.. a first C-SN) as a LTM candidate cell for the UE by transmitting a second SN Required message to the MN, similar to block 703. In some implementations, the second SN Required message includes a second cell ID of the second cell. In response, the S-SN receives a second SN Confirm message from the MN, including a second LTM candidate configuration configuring the second cell for LTM. similar to block 709 A. The S-SN obtains a second LTM CSI resource configuration configuring CSI resources for the second cell and generates a second LTM CSI report configuration based on the second LTM CSI resource configuration, similar to blocks 762 and 764 respectively. In some implementations, the S-SN includes the second LTM candidate configuration, a second configuration ID identifying the second LTM candidate configuration, the second LTM CSI resource configuration and the second LTM CSI report configuration in the first RRC message(s). The S-SN might include the second LTM CSI report configuration in the first serving configuration or the first RRC message. In some implementations, the second configuration ID is a LTM candidate ID.

[0189] In other implementations, the S-SN transmits at least one second RRC message to the UE, including the second configuration ID, the second LTM candidate configuration, the second LTM CSI resource configuration and the second LTM CSI report configuration, similar to block 718. In some implementations, the S-SN generates a second LTM configuration, including the second LTM candidate configuration, the second configuration ID, and the second LTM CSI resource configuration. In some implementations, the S-SN might include the second LTM CSI report configuration in a second serving configuration and includes the second serving configuration in the second RRC message(s). For example, the second serving configuration is a cell group configuration (e.g., CellGroupConfig IE). The S-SN includes the second LTM configuration and the second serving configuration in the second RRC message(s).

[0190] In some implementations, the second SN Required message includes the second cell ID to indicate that the second LTM candidate configuration is associated with the second cell.In other implementations, the second SN Confirm message includes the second cell ID to respond to the second SN Required including the second cell ID.

[0191] In some implementations, while or after preparing the first cell for LTM, the S-SN may prepare a third cell of another C-SN (i.e., second C-SN) as a LTM candidate cell for the UE by transmitting a third SN Required message to the MN, similar to block 703. In some implementations, the third SN Required message includes a third cell ID of the third cell. In response, the S-SN receives a third SN Confirm message from the MN, including a third LTM candidate configuration configuring the third cell for LTM, similar to block 709A. The S-SN obtains a third LTM CSI resource configuration configuring CSI resources for the third cell and generates a third CSI report configuration based on the third LTM CSI resource configuration, similar to blocks 762 and 764 respectively. In some implementations, the S-SN includes the third LTM candidate configuration, a third configuration ID identifying the third LTM candidate configuration, the third LTM CSI resource configuration in the first LTM configuration, the second LTM configuration, the first RRC message(s) and / or the second RRC message(s). The S-SN might include the third LTM CSI report configuration in the first serving configuration, the first RRC message, the second serving configuration or the second RRC message. In some implementations, the third configuration ID is a LTM candidate ID.

[0192] In other implementations, the S-SN transmits at least one third RRC message to the UE, including the third LTM candidate configuration, the third configuration ID, the third LTM CSI resource configuration and the third LTM CSI report configuration similar to block 718. In some implementations, the S-SN generates a third LTM configuration, including the third LTM candidate configuration, the third configuration ID, and the third LTM CSI resource configuration. In some implementations, the S-SN includes the third LTM CSI report configuration in a third serving configuration and includes the third serving configuration in the third RRC message(s). For example, the third serving configuration is a cell group configuration (e g., CellGroupConfig IE). The S-SN includes the third LTM configuration and the third serving configuration in the third RRC message(s).

[0193] In some implementations, the third SN Required message includes the third cell ID to indicate that the third LTM candidate configuration is associated with the third cell. In other implementations, the third SN Confirm message includes the third cell ID to respond to the third SN Required including the third cell ID.

[0194] While the S-SN simultaneously prepare the first cell and the second and / or third cell(s) as described above, the S-SN can determine which SN Confirm message responds to which SN Required message, based on a cell ID in a SN Required message and a SN Confirm message. In some implementations, the first, second and third RRC message(s) are RRC reconfiguration messages.

[0195] Fig. 7B is a flow diagram of an example method 700B similar to the method 700A. except that the method 700B includes block 709B instead of blocks 709 A and 762. At block 709B, the S-SN receives a SN Confirm message from the MN, including a first LTM candidate configuration and a first LTM CSI resource configuration for the UE, where the first LTM candidate configuration configures the first cell for LTM and the first LTM CSI resource configuration configures CSI resources for LTM. Unlike the method 700A, the S-SN receives the LTM CSI resource configuration from the MN.

[0196] Fig. 8 A illustrates an example method 800A similar to the method 700 A, which can be implemented by a CU of an S-SN (e.g., the S-SN 104A of Figs. 6A-6D). The method 800A begins at block 802, where the CU communicates with a UE in DC with a MN and the S-SN, where the CU communicates with the UE via an S-DU (e.g.. the event 302). At block 880-1, the CU might perform an intra-CU intra-DU LTM configuration and / or execution procedure with the S-DU and the UE (e.g., the event 396 or 380). At block 880-2, the CU might perform an intra-CU inter-DU LTM configuration and / or execution procedure with a C-DU and the UE (e.g., the event 496 or 480). The flow proceeds to blocks 760, 703, 709A. and 762. At block 812, the CU transmits a first CU-to-DU message to the S-DU, including the first LTM CSI resource configuration. At block 718, the CU transmits the first LTM candidate configuration, the first LTM CSI resource configuration and the first LTM CSI report configuration to the UE.

[0197] Examples and implementations described for Fig. 7A can apply to the Fig. 8A. In some implementations, the CU includes the second configuration ID and the second cell ID in the first CU-to-DU message. In other implementations, the CU transmits a second CU-to-DU message to the S-DU, including second configuration ID and the second cell ID, similar to the event 312, 392, or 492. In some implementations, the CU includes the third configuration ID and the third cell ID in the first CU-to-DU message or the second CU-to-DU message. In other implementations, the CU transmits a third CU-to-DU message to the S-DU, including third configuration ID and the third cell ID. similar to the event 312, 392, or 492.

[0198] Fig. 8B is a flow diagram of an example method 800B similar to the methods 800A and 700B, except that the method 800B includes block 709B instead of blocks 709Aand 762.

[0199] Fig. 9A illustrates an example method 900A, which can be implemented by a MN (e.g., the MN 104B in Figs. 6A-6D). The method 900A begins at block 902, where the MN communicates with a UE in DC with the MN and an S-SN. At block 980. the MN might perform at least one intra-MN LTM configuration and / or execution procedure with the UE (e.g.. the events 396, 380, 496, and / or 480). At block 905, the MN transmits a SN Request message to a C-SN, requesting to prepare a first cell as a LTM candidate cell for the UE. In some implementations, the SN Request message includes a first cell ID of the first cell. At block 907 A, the MN receives a SN Request Acknowledge message from the C-SN, including a first LTM candidate configuration configuring the first cell as a LTM candidate cell for the UE. At block 962, the MN obtains a first LTM CSI resource configuration, configuring CSI resources for the first cell. The flow might proceed from block 962 to block 964, where the MN generates a first LTM CSI report configuration based on the first LTM CSI resource configuration. The flow continues to proceed to block 918, where the MN transmits the first LTM configuration, the first LTM CSI resource configuration and the first LTM CSI report configuration to the UE. The flow continues to proceed to block 924, where the MN receives one or more LI measurement reports from the UE in accordance with the first LTM CSI report configuration.

[0200] Alternatively, the flow might proceed from block 962 to block 909 A, where the MN transmits a SN message to the S-SN, including the first LTM candidate configuration and the first LTM CSI resource configuration.

[0201] In some implementations, the intra-MN LTM configuration and / or execution procedure(s) includes an intra-MN intra-DU LTM configuration and / or execution procedure similar to the procedure 396 or 380. In other implementations, the intra-MN LTM configuration and / or execution procedure(s) includes an intra-MN inter-DU LTM configuration and / or execution procedure similar to the procedure 496 or 480.

[0202] In some implementations, the MN receives the first LTM CSI resource configuration from a network node (e.g., 0AM). In other implementations, the MN is preconfigured with the first LTM CSI resource configuration in a storage and obtains the first LTM CSI resource configuration from the storage. In some implementations, the first LTM CSI report configuration configures CSI report(ing) for CSI resources configured in the first LTM CSI resource configuration. In some implementations, the CSI resources include one or morereference signals, and / or time and frequency resources for the reference signal(s). The reference signal(s) might include SSB(s) and / or CSI-RS(s).

[0203] In some implementations, the LI measurement report(s) include LI measurement results for the first cell. The LI measurement report(s) may include LI measurement result(s) for a serving cell where the MN receives the LI measurement report(s). The MN determines whether to command the LIE to perform a LTM cell switch to the first cell, based on the LI measurement report(s). If the MN determines to command the UE to perform a LTM cell switch to the first cell, the MN transmits a LTM cell switch command to the UE, commanding the UE to perform a LTM cell switch to the first cell. In response to commanding the UE to perform the LTM cell switch, the MN might transmit a CU-to-CU Cell Switch Notification message to the S-SN, notifying that the MN initiates transmission of a LTM cell switch command to the UE for a LTM cell switch to the first cell. After transmitting the CU-to-CU Cell Switch Notification message to the S-SN, the MN might receive an Early Status Transfer message from the S-SN and transmit the Early Status Transfer message to the C-SN. The Early Status Transfer message might include a DL COUNT value or a DISCARD DL COUNT value for a DRB over which the UE and the S-SN communicate data with each other. After transmitting the LTM cell switch command, the MN might receive an LTM Success message from the C- SN, notifying the LTM cell switch is completed successfully. In response to commanding the UE to perform the LTM cell switch or after transmitting the LTM cell switch command or receiving the LTM Success message, the MN might receive a SN Status Transfer message from the S-SN and transmits the SN Status Transfer message to the C-SN. The SN Status Transfer message might include a UL COUNT value and / or a DL COUNT value for the DRB.

[0204] In some implementations, the MN generates at least one first RRC message including the first LTM candidate configuration, a first configuration ID identifying the first LTM candidate configuration, the first LTM CSI resource configuration and the first LTM CSI report configuration. In some implementations of block 964, the MN generates a first LTM configuration, including the first LTM candidate configuration and the first configuration ID and the first LTM CSI resource configuration, and includes the first LTM configuration in the first RRC message. In some implementations, the first configuration ID is a LTM candidate ID. In some implementations, the MN generates a first serving configuration including the first LTM CSI report configuration. For example, the first serving configuration is a cell group configuration (e.g., CellGroupConfig IE). The MN at block 918 transmits the first RRC message(s) including the first LTM configuration and the first serving configuration to the UEvia a SRB (e.g., SRB1). In some implementations, the SN Request Acknowledge message (a first SN Request message) includes the first cell ID to indicate that the first LTM candidate configuration is associated with the first cell. In other implementations, the SN Request Acknowledge message includes the first cell ID to respond to the SN Request message includes the first cell ID.

[0205] In some implementations, while or after preparing the first cell for LTM. the MN may prepare a second cell of the C-SN (i.e., a first C-SN) as a LTM candidate cell for the UE by transmitting a second SN Request message to the C-SN, similar to block 905. In some implementations, the second SN Request message includes a second cell ID of the second cell. In response, the MN receives a second SN Request Acknowledge message from the C-SN, including a second LTM candidate configuration configuring the second cell for LTM, similar to block 907 A. The MN obtains a second LTM CSI resource configuration, configuring CSI resources for the second cell and generates a second LTM CSI report configuration based on the second LTM CSI resource configuration, similar to blocks 962 and 964 respectively. In some implementations, the MN includes the second LTM candidate configuration, a second configuration ID identifying the second LTM candidate configuration, the second CSI resource configuration and the second CSI report configuration in the first RRC message(s). The MN might include the second LTM CSI report configuration in the first serving configuration or the first RRC message. In some implementations, the second configuration ID is a LTM candidate ID.

[0206] In other implementations, the MN transmits at least one second RRC message to the UE, including the second LTM candidate configuration, the second CSI resource configuration and the second CSI report configuration, similar to block 918. In some implementations, the MN might include the second LTM CSI report configuration in a second serving configuration and includes the second serving configuration in the second RRC message(s). For example, the second serving configuration is a cell group configuration (e.g., CellGroupConfig IE). The MN includes the second LTM configuration and the second serving configuration in the second RRC message(s).

[0207] In some implementations, the second SN Request message includes the second cell ID to indicate that the second LTM candidate configuration is associated with the second cell. In other implementations, the second SN Request Acknowledge message includes the second cell ID to respond to the second SN Request including the second cell ID.

[0208] Tn some implementations, while or after preparing the first cell for LTM, the MN may prepare a third cell of another C-SN (i.e., a second C-SN) as a LTM candidate cell for the UE by transmitting a third SN Request message to the second C-SN, similar to block 905. In some implementations, the third SN Request message includes a third cell ID of the third cell. In response, the MN receives a third SN Request Acknowledge message from the second C-SN, including a third LTM candidate configuration configuring the third cell for LTM, similar to block 907 A. The MN obtains a third LTM CSI resource configuration, configuring CSI resources for the third cell and generates a third LTM CSI report configuration based on the third LTM CSI resource configuration, similar to blocks 962 and 964 respectively. In some implementations, the MN includes the third LTM candidate configuration, a third configuration ID identifying the third LTM candidate configuration, and the third CSI resource configuration in the first LTM configuration, the second LTM configuration, the first RRC message(s) and / or the second RRC message(s). The MN might include the third LTM CSI report configuration in the first serving configuration, the first RRC message, the second serving configuration or the second RRC message. In some implementations, the third configuration ID is a LTM candidate ID.

[0209] In other implementations, the MN transmits at least one third RRC message to the UE, including the third LTM candidate configuration, the third configuration ID, the third CSI resource configuration and the third CSI report configuration, similar to block 918. In some implementations, the MN generates a third LTM configuration, including the third LTM candidate configuration, the third configuration ID, and the third LTM CSI resource configuration. In some implementations, the MN includes the third LTM CSI report configuration in a third serving configuration and includes the third serving configuration in the third RRC message(s). For example, the third serving configuration is a cell group configuration (e.g., CellGroupConfig IE). The MN includes the third LTM configuration and the third serving configuration in the third RRC message(s).

[0210] In some implementations, the third SN Request message includes the third cell ID to indicate that the third LTM candidate configuration is associated with the third cell. In other implementations, the third SN Request Acknowledge message includes the third cell ID to respond to the third SN Request including the third cell ID.

[0211] While the MN simultaneously prepare the first cell and the second and / or third cell(s) as described above, the MN can determine which SN Request Acknowledge message respondsto which SN Request message, based on a cell ID in a SN Request message and a SN Request Acknowledge message. In some implementations, the first, second and third RRC message(s) are RRC reconfiguration messages.

[0212] Fig. 9B is a flow diagram of an example method 900B similar to the method 900A, except that the method 900B includes block 907B instead of blocks 907A and 962. At block 907B, the MN receives a SN Request Acknowledge message from the C-SN, including a first LTM CSI resource configuration and a first LTM candidate configuration configuring the first cell as a LTM candidate cell for the UE. Unlike the method 900 A, the MN receives from the C-SN the first LTM CSI resource configuration configuring CSI resources for the first cell in the method 900B.

[0213] Fig. 10A illustrates an example method 1000A similar to the method 900A, which can be implemented by a CU of an MN (e.g.. the MN 104B of Figs. 6A-6D). The method 1000A begins at block 1002, where the CU communicates with a UE in DC with the MN and an S-SN, where the CU communicates with the UE via an S-DU. At block 1080-1, the CU might perform an intra-CU intra-DU LTM configuration and / or execution procedure with the S-DU and the UE (e.g.. the events 396, 380, 696. or 680). At block 1080-2. the CU might perform an intra-CU inter-DU LTM configuration and / or execution procedure with a C-DU and the UE (e.g., the events 496, 480, 696, or 680). The flow proceeds to blocks 905, 907 A, and 962. At block 1012, the CU transmits a CU-to-DU message to the S-DU, including the first LTM CSI resource configuration. At block 1014, the CU receives a DU-to-CU message from the S-DU, including a first LTM CSI report configuration. At block 1018, the CU transmits the first LTM configuration, the first LTM CSI resource configuration and the first LTM CSI report configuration to the UE via the S-DU

[0214] Examples and implementations described for Fig. 9A can apply to Fig. 10A.

[0215] Fig. 10B is a flow diagram of an example method 1000B similar to the method 1000A and 900B, except that the method 1000B includes block 907B instead of blocks 907Aand 962.

[0216] Fig. 11 illustrates an example method 1100, which can be implemented by a C-SN (e.g., the C-SN 106A of Figs. 6A-6D). The method 1100 begins at block 1105, where the C- SN receives a SN Request message from a MN, requesting to prepare a first cell as a LTM candidate cell for a UE. At block 1162. the C-SN obtains a first LTM CSI resource configuration configuring CSI resources for the first cell. At block 1107, the C-SN transmits a SN Request Acknowledge message to the MN, including a first LTM candidate configurationand the first LTM CSI resource configuration, where the first LTM candidate configuration configures the first cell as a LTM candidate cell for the UE.

[0217] In some implementations, the C-SN receives the first LTM CSI resource configuration from a network node (e.g., 0AM). In other implementations, the C-SN is preconfigured with the first LTM CSI resource configuration in a storage and obtains the first LTM CSI resource configuration from the storage.

[0218] In some implementations, the C-SN may prepare a second cell as a LTM candidate cell for the UE as described above.

[0219] Fig. 12 illustrates an example method 1200. which can be implemented by a CU of a C-SN (e g., the C-SN 106A of Figs. 6A-6D). The method 1200 begins at block 1105 performed by the CU. At block 1262, the CU receives a DU-to-CU message including a first LTM CSI resource configuration from a DU, where the first LTM CSI resource configuration configures CSI resources for the first cell. The method 1200 ends at block 1107 performed by the CU.

[0220] The DU operates the first cell. In some implementations, the CU transmits a CU-to- DU message to the DU and receives the DU-to-CU message from the DU in response. For example, the CU-to-DU message and the DU-to-CU message are a UE Context Setup Request message and a UE Context Setup Response message, respectively. In other implementations, the CU-to-DU message and the DU-to-CU message are a UE Context Modification Request message and a UE Context Modification Response message, respectively. In other implementations, the DU-to-CU message is a Fl Setup Request message and the CU transmits a F 1 Setup Response message to the DU in response. In yet other implementations, the DU- to-CU message is a GNB-DU Configuration Update message and the CU transmits a GNB-DU Configuration Update Acknowledge message to the DU in response. In yet other implementations, the DU-to-CU message is a GNB-CU Configuration Update Acknowledge message.

[0221] Examples and implementations described for Fig. 7A-10B can apply to Figs. 11 and 12.

[0222] Fig. 13A illustrates an example method 1300A similar to the method 700A, which can be implemented by an S-SN (e.g., the S-SN 104A in Figs. 6A-6D), except that the method 1300A includes blocks 1372, 1374, 1318, and 1324 instead of blocks 762, 764, 718, and 724. At block 1372. the S-SN obtains first SSB information for the first cell, where the first SSB information includes time and frequency configuration of one or more SSBs transmitted on thefirst cell. At block 1374, the S-SN generates a first LTM SSB configuration based on the first SSB information. At block 1318, the S-SN transmits the first LTM candidate configuration and the first LTM SSB configuration to the UE. At block 1324, the S-SN receives, from the UE, one or more LI measurement reports each including a measurement result for a SSB configured in the first SSB configuration.

[0223] In some implementations, the S-SN obtains or receives the SSB information from a network node (e.g., 0AM). In other implementations, the S-SN is preconfigured with the first SSB information in a storage and obtains the first SSB information from the storage. In some implementations, the first SSB information is LTM SSB information.

[0224] In some implementations, the S-SN generates at least one first RRC message including the first LTM candidate configuration, a first configuration ID, and the first LTM SSB configuration to the UE. The first configuration ID identifies the first LTM candidate configuration and / or the first LTM SSB configuration. In some implementations, the S-SN generates a first LTM configuration, including the first LTM candidate configuration, the first configuration ID, and the first LTM SSB configuration. In some implementations, the first configuration ID is a LTM candidate ID. The S-SN transmits the first RRC message including the first LTM configuration to the UE at block 1318.

[0225] In some implementations, while or after preparing the first cell as a LTM candidate cell for the UE, the S-SN may prepare a second cell of the C-SN (i.e., a first C-SN) as a LTM candidate cell for the UE by transmitting a second SN Required message to the MN, similar to block 703. In response, the S-SN receives a second SN Confirm message from the MN, including a second LTM candidate configuration configuring the second cell for LTM. similar to block 709 A. The S-SN obtains second SSB information for the UE, which includes time and frequency configuration of one or more SSBs transmitted on the second cell, similar to block 1372. The second SSB information might be LTM SSB information. The S-SN generates a second LTM SSB configuration based on the second SSB information, similar to block 1374. Alternatively, the S-SN obtains the second LTM SSB configuration, e.g., from the network node or the storage, instead of the second SSB information. In some implementations, the S- SN includes the second LTM candidate configuration, a second configuration ID, the second LTM SSB configuration in the first RRC message or the first LTM configuration. The second configuration ID identifies the second LTM candidate configuration and / or the second LTMSSB configuration. In some implementations, the second configuration ID is a LTM candidateID.

[0226] In other implementations, the S-SN transmits at least one second RRC message to the UE, including the second LTM candidate configuration, the second configuration ID, and the second LTM SSB configuration, similar to block 1318. In some implementations, the S-SN generates a second LTM configuration, including the second LTM candidate configuration, the second configuration ID, and the second LTM SSB configuration. The S-SN includes the second LTM configuration in the second RRC message(s).

[0227] In some implementations, the second SN Required message and the second SN Confirm message can be combined with the first SN Required message and the SN Confirm message as a single SN Required message and a single SN Confirm message, respectively.

[0228] In some implementations, while or after preparing the first cell for LTM, the S-SN may prepare a third cell of another C-SN (i.e., second C-SN) as a LTM candidate cell for the UE by transmitting a third SN Required message to the MN, similar to block 703. In response, the S-SN receives a third SN Confirm message from the MN, including a third LTM candidate configuration configuring the third cell for LTM, similar to block 709A. The S-SN obtains third SSB information for the UE. which includes time and frequency configuration of one or more SSBs transmitted on the third cell, similar to block 1372. The third SSB information might be LTM SSB information. The S-SN generates a third LTM SSB configuration based on the third SSB information, similar to block 1374. Alternatively, the S-SN obtains the third LTM SSB configuration, e.g., from the network node or the storage, instead of the third SSB information. In some implementations, the S-SN includes the third LTM candidate configuration, a third configuration ID, the third LTM SSB configuration in the first LTM configuration, the second LTM configuration, the first RRC message(s) and / or the second RRC message(s). The third configuration ID identifies the third LTM candidate configuration and / or the third LTM SSB configuration. In some implementations, the third configuration ID is a LTM candidate ID.

[0229] In other implementations, the S-SN transmits at least one third RRC message to the UE, including the third LTM candidate configuration, the third configuration ID. and the third LTM SSB configuration, similar to block 1318. In some implementations, the S-SN generates a third LTM configuration, including the third LTM candidate configuration, the third configuration ID, and the third LTM SSB configuration. The S-SN includes the third LTM configuration in the third RRC message(s).

[0230] Fig. 13B illustrates an example method 1300B similar to the method 1300A, which can be implemented by an S-SN (e.g., the S-SN 104A in Figs. 6A-6D), except that the method 1300A includes blocks 1309B instead of blocks 709A and 1372.

[0231] At block 1309B, the S-SN receives a SN Confirm message from the MN, including a first LTM candidate configuration and first SSB information for the UE, where the first LTM candidate configuration configures the first cell for LTM. and the first SSB information includes time and frequency configuration of one or more SSBs transmitted on the first cell.

[0232] Examples and implementations described for Fig. 7A can apply to Figs. 13A and 13B. Fig. 13A or 13B can be combined with Fig. 7A or 7B.

[0233] Fig. 14 illustrates an example method 1400 similar to the method 1100, which can be implemented by a C-SN (e.g., the C-SN 106A in Figs. 6A-6D), except that the method 1400 includes blocks 1472 and 1474 instead of block 1162. The method begins at block 1105 and proceeds to blocks 1472 and 1474 similar to blocks 1372 and 1374 respectively. At block 1407, the C-SN transmits a SN Request Acknowledge message to the MN, including a first LTM candidate configuration and the first LTM SSB configuration, where the first LTM candidate configuration configures the first cell as a LTM candidate cell for the UE.

[0234] In some implementations, the C-SN receives the first SSB information from a network node (e.g., 0AM). In other implementations, the C-SN is preconfigured with the first SSB information in a storage and obtains the first SSB information from the storage. In some alternative implementations, the C-SN obtains the first LTM SSB configuration instead of the first SSB information. In such cases, block 1474 is skipped.

[0235] Examples and implementations described for Figs. 7A, 7B, and 11 can apply to Fig. 14. Fig. 14 can be combined with Fig. 11. Examples and implementations described for the S- SN in Figs. 13A and 13B can apply to the C-SN of Fig. 14. For example, while preparing the second cell with the S-SN as described for Fig. 13A, the C-SN obtains the second SSB information and generates the second LTM SSB configuration based on the second SSB information instead of the S-SN. Alternatively, the C-SN obtains the second LTM SSB configuration, e.g., from the network node or the storage, instead of the second SSB information. The C-SN includes the second LTM SSB configuration in the second SN Request Acknowledge message.

[0236] Fig. 15 illustrates an example method 1500 similar to the methods 1100, 1200, and 1400, which can be implemented by a CU of a C-SN (e.g., the C-SN 106A of Figs. 6A-6D).

[0237] The method 1500 begins at block 1105 and proceeds to block 1572. At block 1572, the CU receives a DU-to-CU message including first SSB information from a DU, where the first SSB information includes time and frequency configuration of one or more SSBs transmitted on the first cell. The flow proceeds to blocks 1474 and 1407 from block 1572.

[0238] In some implementations, the DU first obtains or receives the first SSB information from a network node (e.g.. 0AM). In other implementations, the DU is preconfigured with the first SSB information in a storage and obtains the first SSB information from the storage.

[0239] Examples and implementations described for Figs. 7A, 7B, 11, 12, and 14 can apply to Fig. 15. Fig. 15 can be combined with Fig. 12. Examples and implementations described for the S-SN of Figs. 13A and 13B can apply to the CU of Fig. 15. For example, while preparing the second cell with the S-SN as described for Fig. 13 A, the CU of the C-SN receives the second SSB information in a DU-to-CU message from the DU and generates the second LTM SSB configuration based on the second SSB information. Alternatively, the CU of the C-SN obtains the second LTM SSB configuration in a DU-to-CU message from the DU instead of the second SSB information. The C-SN includes the second LTM SSB configuration in the first or second SN Request Acknowledge message.

[0240] The following description may be applied to the description above.

[0241] In some implementations, the SN Required message and the SN Confirm message are a SN Change Required message and a SN Change Confirm message, respectively. In other implementations, the SN Required message and the SN Confirm message are a SN Modification Required message and a SN Modification Confirm message, respectively. In some implementations, the SN Request message and the SN Request Acknowledge message are a SN Addition Request message and a SN Addition Request Acknowledge message, respectively. In other implementations, the SN Request message and the SN Request Acknowledge message are a SN Modification Request message and a SN Modification Request Acknowledge message, respectively.

[0242] Generally speaking, description for one of the above figures can apply to another of the above figures. Examples, implementations and methods described above can be combined, if there is no conflict. An event or block described above can be optional or omitted. For example, an event or block with dashed lines in the figures can be optional. The description described from the perspective of the receiving node also applies to the sending node. For example, a description that a receiving node (e.g., DU) receives a message from a sending node(e.g., CU) may be replaced by the sending node sending a message to the receiving node. Similarly, a description that a receiving node (e.g., CU) receives a message from a sending node (e.g., DU) may be replaced by the sending node sending a message to the receiving node.

[0243] In some implementations, “message” is used and can be replaced by “information element (IE)”, and vice versa. In some implementations, “IE” is used and can be replaced by “field”, and vice versa. In some implementations, “configuration” can be replaced by “configurations” or “configuration parameters”, and vice versa. In some implementations, the “LTM command” can be replaced by “serving cell change command”, “Layer 1 / Layer 2 LTM cell switch command”, “lower layer switching command” or “lower layer serving cell change command”. In some implementations, “some” means “one or more”. In some implementations, “at least one” means “one or more”. In some implementations, the “DU configuration” can be replaced by “cell group configuration”. In some implementations, the “cell index” can be replaced with “serving cell index”, “LTM cell index”, “special cell (SpCell) index”. “PCell index” or “PSCell index”. In some implementations, the “serving” can be replaced by “source”. In some implementations, the “measurement report” can be replaced by “measurement result(s)” or “CSI report”. In some implementations, the “early TA acquisition” can be replaced by “early UL timing synchronization” or “early UL synchronization”. In some implementations, the “early TA acquisition on a / the candidate cell” can be replaced by “early UL timing synchronization with a / the candidate cell” or “early UL synchronization with a / the candidate cell”. In some implementations, “include” can be replaced by “comprise”. In some implementations, “exclude” can be replaced by “refrain from including”. In some implementations, “Handover Request"' and “Handover Request Acknowledge'" described above are for illustration of the invention and can be replaced by messages with general names. For example, “Handover Request"" and “Handover Request Acknowledge"" can be replaced by a first CU-to-CU message and a second CU-to-CU message, respectively. In another example, “Handover Request"" and “Handover Request Acknowledge"" can be replaced by a first interface message and a second interface message, respectively. In yet another example, “Handover Request"" and “Handover Request Acknowledge"' can be replaced by a first BS-to-BS message and a second BS-to-BS message, respectively. In some implementations, “SN Request”, “SN Confirm”, “SN Request” and “SN Request Acknowledge” described above are for illustration of the invention and can be replaced by messages with general names. For example, the “SN Required message” can be replaced by a SN-to-MN message. In another example, the “SN Confirm message” can be replaced by a MN-to-SN message.

[0244] A user device in which the techniques of this disclosure can be implemented (e.g., the UE 102) can be any suitable device capable of wireless communications such as a smartphone, a tablet computer, a laptop computer, a mobile gaming console, a point-of-sale (POS) terminal, a health monitoring device, a drone, a camera, a media-streaming dongle or another personal media device, a wearable device such as a smartwatch, a wireless hotspot, a femtocell, or a broadband router. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Still further, the user device can operate as an intemet-of-things (loT) device or a mobile-internet device (MID). Depending on the type, the user device can include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0245] Certain embodiments are described in this disclosure as including logic or a number of components or modules. Modules may can be software modules (e.g., code, or machine- readable instructions stored on non-transitory machine-readable medium) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module can comprise dedicated circuitry or logic that is permanently configured (e.g, as a special -purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), a digital signal processor (DSP), etc.) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g, as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g. configured by software) may be driven by cost and time considerations.

[0246] When implemented in software, the techniques can be provided as part of the operating system, a library used by multiple applications, a particular software application, etc. The software can be executed by one or more general-purpose processors or one or more special-purpose processors.

[0247] Upon reading this disclosure, those of skill in the art will appreciate still additional and alternative structural and functional designs for handling mobility between base stations through the principles disclosed herein. Thus, while particular embodiments and applications have been illustrated and described, it is to be understood that the disclosed embodiments arenot limited to the precise construction and components disclosed herein. Various modifications, changes and variations, which will be apparent to those of ordinary’ skill in the art, may be made in the arrangement, operation and details of the method and apparatus disclosed herein without departing from the spirit and scope defined in the appended claims.

[0248] The following examples are illustrative only and may be combined with other examples or teachings described herein, without limitation.

[0249] Example 1 is a method of wireless communication performed by a radio access network, RAN, node, the method including transmitting, to a master node, MN, a secondary node, SN, required message; receiving, from the MN, in response to the SN required message, a SN acknowledgement message including a lower-layer triggered mobility, LTM, candidate cell configuration; generating a channel state information, CSI. report configuration based on a reference signal resource configuration; and transmitting, to a user equipment, UE. the LTM candidate cell configuration, the reference signal resource configuration, and the CSI report configuration associated with an LTM candidate cell.

[0250] Example 2 may be combined with example 1 and further includes obtaining the reference signal resource configuration associated with the LTM candidate cell.

[0251] Example 3 may be combined with example 1 and further includes that the CSI report configuration associated with the LTM candidate cell is configured based on the reference signal resource configuration.

[0252] Example 4 may be combined with example 1 and further includes that the SN acknowledgement message further includes the reference signal resource configuration configuring CSI resources associated with the LTM candidate cell.

[0253] Example 5 may be combined with example 1 and further includes that the SN required message includes an identification, ID, of a first cell.

[0254] Example 6 may be combined with any examples 1 to 2 and further includes that the reference signal resource configuration indicates resources for at least one of a CSI reference signal, CSI-RS, or a synchronization signal block, SSB.

[0255] Example 7 may be combined with example 6 and further includes that the SSB indicates time and frequency configuration of one or more SSBs transmitted on LTM candidate cell.

[0256] Example 8 may be combined with example 7 and further includes that the SSB is received from at least one of: an operations, administration and maintenance, 0AM, node, or a memory of the RAN node.

[0257] Example 9 may be combined with any examples 1 to 8 and further includes receiving, from the UE, a measurement report based on the CSI report configuration and the reference signal resource configuration.

[0258] Example 10 may be combined with any examples 1 to 9 and further includes that the measurement report includes measurement information associated with the one or more SSBs transmitted on LTM candidate cell.

[0259] Example 11 may be combined with any examples 1 to 10 and further includes transmitting, to the UE, an LTM cell switch command to switch to the LTM candidate cell; transmitting, to the MN, at least one of: a cell switch notification message; or an early status transfer message; and receiving, from the MN, an LTM success message.

[0260] Example 12 may be combined with any examples 1 to 11 and further includes that the transmitting the CSI report configuration associated with an LTM candidate cell, the reference signal resource configuration, and the LTM candidate cell configuration including: transmitting the CSI report configuration, the reference signal resource configuration, and the LTM configuration in a radio resource control, RRC, reconfiguration message.

[0261] Example 13 may be combined with any examples 1 to 12 and further includes that the RAN node including a source secondary node, S-SN.

[0262] Example 14 may be combined with any examples 1 to 13 and further includes that the RAN node communicates with the UE in a dual connectivity, DC, with the MN.

[0263] Example 15 is a method of wireless communication performed by a radio access network, RAN, node, the method including transmitting, to a master node, MN, a secondary node, SN, required message; receiving, from the MN, in response to the SN required message, a SN acknowledgement message including a lower-layer triggered mobility, LTM, candidate cell configuration; obtaining a reference signal resource configuration associated with a LTM candidate cell; transmitting, by a central unit, CU. of the RAN node, to a distributed unit, DU, of the RAN node, a CU-to-DU message including the reference signal resource configuration; receiving, by the CU from the DU, a DU-to-CU message including a channel state information,CSI, report configuration; and transmitting, to a user equipment, UE, the LTM candidate cell configuration, the reference signal resource configuration, and the CSI report configuration.

[0264] Example 16 may be combined with example 15 and further includes that the SN acknowledgement message further includes a reference signal resource configuration associated with the LTM candidate cell configuring CSI resources associated with the LTM candidate cell.

[0265] Example 18 the method of any claims 15-17 and further includes that the CU-to-DU message further indicates a configuration identification, ID, and a cell ID.

[0266] Example 19 may be combined with any examples 15 to 18 and further includes that the RAN node including a source secondary RAN node, S-SN.

[0267] Example 17 may be combined with example 15 and further includes receiving a reference signal resource configuration associated with the LTM candidate cell.

[0268] Example 20 is a method of wireless communication performed by a radio access network, RAN, node, the method including transmitting, to a candidate secondary' node, C-SN, a SN request message; and obtaining, from the C-SN in response to the SN request message, a SN request acknowledgement message including a lower-layer triggered mobility, LTM, candidate cell configuration.

[0269] Example 21 may be combined with example 20 and further includes that the SN acknowledgement message further includes a reference signal resource configuration configuring channel state information, CSI, resources associated with a LTM candidate cell.

[0270] Example 22 may be combined with example 20 and further includes receiving a reference signal resource configuration associated with a LTM candidate cell.

[0271] Example 23 may be combined with example 22 and further includes transmitting, to a user equipment, UE, the LTM candidate cell configuration, the reference signal resource configuration, and a channel state information, CSI, report configuration associated with the LTM candidate cell.

[0272] Example 24 the method of any claims 20-23 and further includes receiving, from the UE, a measurement report based on the CSI report configuration associated with a LTM candidate cell.

[0273] Example 25 the method of any claims 20-24 and further includes transmitting, to a source secondary node, S-SN, a SN message including the LTM candidate cell configuration and the reference signal resource configuration associated with a LTM candidate cell.

[0274] Example 26 may be combined with any examples 20-25 and further includes that the RAN node including a master node, MN.

[0275] Example 27 is a method of wireless communication performed by a radio access network, RAN. node, the method including transmitting, to a candidate secondary node, C-SN, a SN request message; and obtaining, from the C-SN in response to the SN request message, a SN request acknowledgement message including a lower-layer triggered mobility, LTM, candidate cell configuration; transmitting, by a central unit, CU, of the RAN node, to a distributed unit, DU, of the RAN node, a CU-to-DU message indicating a reference signal resource configuration; and receiving, by the CU from the DU, a channel state information. CSI, report configuration.

[0276] Example 28 may be combined with example 27 and further includes receiving the reference signal resource configuration associated with a LTM candidate cell.

[0277] Example 29 may be combined with example 27 and further includes that the SN acknowledgement message further includes the reference signal resource configuration configuring channel state information, CSI, resources associated with a LTM candidate cell.

[0278] Example 30 may be combined with any examples 27-29 and further includes that the RAN node including a master node. MN.

[0279] Example 31 is a method of wireless communication performed by a radio access network, RAN, node, the method including receiving, from a master node, MN, a handover request message; and transmitting, to the MN, a handover request acknowledgement message indicating a lower-layer triggered mobility, LTM, candidate cell configuration and a reference signal resource configuration associated with a LTM candidate cell.

[0280] Example 32 may be combined with example 31 and further includes that the reference signal resource configuration indicates resources for at least one of: a CSI reference signal, CSI-RS; or a synchronization signal block. SSB.

[0281] Example 33 may be combined with example 32 and further includes that the SSB indicates time and frequency configuration of one or more SSBs transmitted on LTM candidate cell.

[0282] Example 34 is a method of wireless communication performed by a radio access network, RAN, node, the method including receiving, from a master node, MN, a handover request message; obtaining, by a central unit, CU, of the RAN node, from a distributed unit, DU, of the RAN node, a DU-to-CU message including a reference signal resource configuration associated with a LTM candidate cell; and transmitting, to the MN, a handover request acknowledgement message including a lower-layer triggered mobility, LTM, candidate cell configuration and the reference signal resource configuration associated with the LTM candidate cell.

[0283] Example 35 may be combined with example 34 and further includes that the reference signal resource configuration indicates resources for at least one of: a CSI reference signal, CSLRS; or a synchronization signal block, SSB.

[0284] Example 36 may be combined with any examples 34-35 and further includes transmitting, by the CU to the DU, a user equipment, UE, context setup request message; and receiving, from the DU, a UE context setup response message.

[0285] Example 37 may be combined with any examples 34-36 and further includes transmitting, by the CU to the DU, a user equipment, UE, context modification request message; and receiving, from the DU, a UE context modification response message.

[0286] Example 38 may be combined with any examples 34-37 and further includes receiving, from the DU, a next generation node B, GNB,-DU configuration update message; and transmitting, by the CU to the DU, a GNB-DU configuration update acknowledgement message.

[0287] Example 39 may be combined with any examples 34-38 and further includes that the RAN node including a candidate secondary node, C-SN.

[0288] Example 40 is an apparatus for wireless communication for implementing a method as in any of Examples 1-39.

[0289] Example 41 is an apparatus for wireless communication including means for implementing a method as in any of Examples 1-39.

[0290] Example 42 is a non-transitory computer-readable medium storing computer executable code, the code when executed by a processor causes the processor to implement a method as in any of Examples 1-39.

[0291] Example 43 is a computer program product for implementing a method as in any of Examples 1-39.

Claims

CLAIMSWhat is claimed is:

1. A method of wireless communication performed by a radio access network, RAN, node (104A), the method comprising: transmitting (603,703), to a master node, MN, (104B), a secondary node, SN, required message; receiving (609A,709A), from the MN, in response to the SN required message, a SN acknowledgement message including a lower-layer triggered mobility. LTM. candidate cell configuration; generating, based on a reference signal resource configuration, a channel state information, CSI, report configuration associated with an LTM candidate cell; and transmitting (718), to a user equipment, UE, (102), the LTM candidate cell configuration, the reference signal resource configuration, and the CSI report configuration associated with the LTM candidate cell.

2. The method of claim 1, further comprising: obtaining (762) the reference signal resource configuration associated with the LTM candidate cell, wherein the CSI report configuration associated with the LTM candidate cell is configured based on the reference signal resource configuration.

3. The method of claim 1 , wherein the SN required message includes an identification, ID, of a first cell.

4. The method of any of claims 1 to 3, further comprising: receiving (724), from the UE (102), a measurement report based on the CSI report configuration and the reference signal resource configuration, wherein the measurement report includes measurement information associated with one or more synchronization signal blocks, SSBs, transmitted on the LTM candidate cell.

5. The method of any of claims 1-4, further comprising: transmitting, to the UE (102). an LTM cell switch command to switch to the LTM candidate cell;transmitting, to the MN, at least one of: a cell switch notification message; or an early status transfer message; and receiving, from the MN, an LTM success message.

6. The method of claim 1, further comprising: transmitting (812), by a central unit. CU, of the RAN node, to a distributed unit, DU, of the RAN node, a CU-to-DU message including the reference signal resource configuration; and receiving (814), by the CU from the DU, a DU-to-CU message including a channel state information, CSI, report configuration.

7. A method of wireless communication performed by a radio access network, RAN, node (104), the method comprising: transmitting (905), to a candidate secondary node. C-SN, a SN request message; and obtaining (907A), from the C-SN in response to the SN request message, a SN request acknowledgement message including a lower-layer triggered mobility, LTM, candidate cell configuration.

8. The method of claim 7, further comprising: receiving (962) a reference signal resource configuration associated with a LTM candidate cell.

9. The method of claim 8, further comprising: transmitting (918), to a user equipment, UE ( 102), the LTM candidate cell configuration, the reference signal resource configuration, and a channel state information, CSI, report configuration associated with the LTM candidate cell; and receiving (924), from the UE (102), a measurement report based on the CSI report configuration associated with the LTM candidate cell.

10. The method of any claims 7-9, further comprising: transmitting (909 A), to a source secondary node. S-SN, a SN message including the LTM candidate cell configuration and the reference signal resource configuration associated with a LTM candidate cell.11 . The method of claim 8, further comprising: transmitting (1012), by a central unit, CU, of the RAN node, to a distributed unit, DU, of the RAN node, a CU-to-DU message indicating the reference signal resource configuration; and receiving (1014), by the CU from the DU, a channel state information, CSI, report configuration.

12. The method of claim 7, further comprising: obtaining, by a central unit, CU, of the RAN node (106A). from a distributed unit, DU. of the RAN node (106), a DU-to-CU message including a reference signal resource configuration associated with a LTM candidate cell.

13. The method of claim 12, further comprising: receiving, from the DU, a DU configuration update message; and transmitting, to the DU, a DU configuration update acknowledgement message.

14. A method of wireless communication performed by a radio access network, RAN. node (106), the method comprising: receiving, from a master node, MN, (104 A), a handover request message; and transmitting, to the MN (104 A), a handover request acknowledgement message indicating a lower-layer triggered mobility, LTM, candidate cell configuration and a reference signal resource configuration associated with a LTM candidate cell.

15. The method of claim 14, wherein the reference signal resource configuration indicates resources for at least one of: a CSI reference signal, CSI-RS; or a synchronization signal block, SSB, wherein the SSB indicates time and frequency configuration of one or more SSBs transmitted on the LTM candidate cell.

16. An apparatus for wireless communication comprising a memory’ and at least one processor coupled to the memory' and configured to implement a method as in any of claims 1- 15.

Images