Configuring random access for lower layer triggered mobility cell switch

Abstract

A method implemented in a distributed unit (DU) of a distributed base station. The method can include receiving a request, from a central unit (CU) of the distributed base station, to prepare a candidate cell for lower layer triggered mobility (LTM) for a user equipment (UE). The method can further include transmitting, to the CU and in response to the request, LTM contention free random access (CERA) configuration parameters for accessing the candidate cell. Other methods and systems are described.

Description

CONFIGURING RANDOM ACCESS FOR LOWER LAYER TRIGGERED MOBILITY CELL SWITCHCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to and the benefit of the filing date of provisional U.S. Patent Application No. 63 / 571,598 entitled “Configuring Random Access for Lower Layer Triggered Mobility Cell Switch,” filed on March 29, 2024. The entire content of the provisional application is hereby expressly incorporated herein by reference.FIELD OF THE DISCLOSURE

[0002] This disclosure relates to wireless communications and, more particularly, to configuring random access for inter-central unit (inter-CU) lower layer triggered mobility (LTM) cell switch.BACKGROUND

[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 otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

[0004] Generally speaking, a base station operating a cellular radio access network (RAN) communicates with a user equipment (UE) using a certain radio access technology (RAT) and multiple layers of a radio protocol stack. For example, the physical layer (PHY) of a RAT provides transport channels to the Medium Access Control (MAC) sublayer, which in turn provides logical channels to the Radio Link Control (RLC) sublayer, and the RLC sublayer in turn provides data transfer services to the Packet Data Convergence Protocol (PDCP) sublayer.

[0005] The 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) sublayer. 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.

[0006] The UE can concurrently utilize resources of multiple RAN nodes (e.g., base stations or components of a distributed base station), interconnected by a backhaul. When the multiple RAN 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 can determine that the UE should establish a radio connection with a second base station. For example, one base station can determine to hand the UE over to the second base station, and the base station can initiate a handover procedure.

[0007] When the UE moves from the coverage area of one cell to another cell in a RAN, the RAN performs a serving cell change by configuring the UE to transmit Layer 3 (L3) measurement results. Based on L3 measurement results received from the UE, the RAN transmits an RRC reconfiguration message configuring Reconfiguration with Synchronization (e.g., the RRC reconfiguration message includes a ReconfigurationWithSync IE) for change of the serving cell (e.g., PCell or PSCell). When the UE operates in carrier aggregation (CA) of at least one secondary cell (SCell) with the PCell or PSCell, the RAN releases 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. To address these concerns, 3GPP recently proposed procedures referred to as lower layer triggered mobility (LTM).

[0008] During RAN communication with the UE via a serving cell associated with the base station, the base station receives one or more layer 3 (e.g., RRC) measurement results from the UE. Based on the layer 3 (L3) measurement result(s), the base station determines to configure an LTM candidate cell for LTM cell switch. To configure the LTM candidate cell for the UE, the base station transmits an LTM candidate configuration to the UE via RRC signaling. Subsequently, the base station receives one or more layer 1 (LI) measurementresults 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. After making this determination, the base station transmits an 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. The base station includes a central unit (CU) and one or more distributed units (DUs). One of the DU(s) operating the serving cell is referred to as a serving DU. 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 (C- DU) in the DU(s), the LTM cell switch is an intra-CU inter-DU LTM cell switch. 3GPP has enabled the intra-CU intra-DU LTM cell switch and intra-CU inter-DU LTN cell switch in Release 18 specifications. However, it is not clear how devices should handle inter-CU LTM cell switches.

[0009] In addition, when the UE receives an LTM Cell Switch Command from the RAN, the UE performs an LTM cell switch to the LTM candidate cell based on the LTM candidate configuration. However, it is not clear how random access should be performed after LTM cell switch in inter-CU scenarios. In the LTM cell switch command, the RAN can include parameters such as a random access preamble index, a synchronization signal block (SSB) index, a physical random access channel (PRACH) Mask index, and a UL / SUL indicator as described in 3GPP specification 38.321 vl8.0.0. However, it is not clear how the RAN configures these parameters.SUMMARY

[0010] A method can be implemented in a distributed unit (DU) of a distributed baser station. The method can include receiving a request, from a central unit (CU) of the distributed base station, to prepare a candidate cell for lower layer triggered mobility (LTM) for a user equipment (UE). The method can include transmitting, to the CU and in response to the request, LTM contention free random access (CERA) configuration parameters for accessing the candidate cell.

[0011] In another implementation, a method can be implemented in a central unit (CU) of a distributed base station. The method can include transmitting, to a distributed unit (DU), a request to prepare a candidate cell for lower layer triggered mobility (LTM) for a user equipment (UE). The method can include receiving, from the DU and in response to therequest, LTM contention free random access (CFRA) configuration parameters for accessing the candidate cell.

[0012] In yet another implementation, a base station comprising a transceiver and processing hardware can implement any of the methods described herein.BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Fig. 1A is a block diagram of an example system in which a radio access network (RAN) and a user equipment (UE) can implement the techniques of this disclosure for managing inter-CU LTM;

[0014] Fig. IB is another block diagram of an example system in which a RAN and a UE can implement the techniques of this disclosure for managing inter-CU LTM;

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

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

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

[0018] Fig. 3 is a message sequence diagram of an example scenario in which a UE performs an intra-CU intra-DU LTM procedure;

[0019] Fig. 4 is a message sequence diagram of an example scenario in which a UE performs an intra-CU inter-DU LTM procedure;

[0020] Fig. 5 is a message sequence diagram of an example scenario in which a UE performs an inter-CU LTM procedure;

[0021] Fig. 6Ais a message sequence diagram of an example scenario for dual connectivity;

[0022] Fig. 6B is a message sequence diagram of a second example scenario for dual connectivity;

[0023] Fig. 6C is a message sequence diagram of a third example scenario for dual connectivity;

[0024] Fig. 6D is a message sequence diagram of a fourth example scenario for dual connectivity;

[0025] Fig. 7A is a flow diagram of a first example method that can be implemented by a DU;

[0026] Fig. 7B is a flow diagram of a second example method that can be implemented by a DU;

[0027] Fig. 7C is a flow diagram of a third example method that can be implemented by a DU;

[0028] Fig. 7D is a flow diagram of a fourth example method that can be implemented by a DU;

[0029] Fig. 7E is a flow diagram of a fifth example method that can be implemented by a DU;

[0030] Fig. 8A is a flow diagram of a first example method that can be implemented by a C-DU;

[0031] Fig. 8B is a flow diagram of a second example method that can be implemented by a C-DU;

[0032] Fig. 8C is a flow diagram of a third example method that can be implemented by a C-DU;

[0033] Fig. 8D is a flow diagram of a fourth example method that can be implemented by a C-DU;

[0034] Fig. 9A is a flow diagram of a first example method that can be implemented by an S-DU;

[0035] Fig. 9B is a flow diagram of a second example method that can be implemented by an S-DU;

[0036] Fig. 9C is a flow diagram of a third example method that can be implemented by an S-DU;

[0037] Fig. 9D is a flow diagram of a fourth example method that can be implemented by an S-DU;

[0038] Fig. 9E is a flow diagram of a fifth example method that can be implemented by an S-DU;

[0039] Fig. 9F is a flow diagram of a sixth example method that can be implemented by an S-DU;

[0040] Fig. 9G is a flow diagram of a seventh example method that can be implemented by an S-DU;

[0041] Fig. 9H is a flow diagram of an eighth example method that can be implemented by an S-DU;

[0042] Fig. 91 is a flow diagram of a ninth example method that can be implemented by an S-DU;

[0043] Fig. 10A is a flow diagram of a first example method that can be implemented by a CU;

[0044] Fig. 10B is a flow diagram of a second example method that can be implemented by a CU;

[0045] Fig. 10C is a flow diagram of a third example method that can be implemented by a CU;

[0046] Fig. 10D is a flow diagram of a fourth example method that can be implemented by a CU; and

[0047] Fig. 11 is a flow diagram of an example method that a DU of a distributed base station can implement for inter-CU LTM.DETAILED DESCRIPTION OF THE DRAWINGS

[0048] Techniques of the disclosure are directed to lower layer triggered mobility (LTM). LTM enables serving cell change via L1 / L2 signaling, while keeping configuration of the upper layers and minimizing changes of configuration of the lower layers. Procedures are available for performing LTM cell switches between cells served by different base stations (e.g., inter-CU LTM), where the UE may be in DC with the two base stations. Aspects of this disclosure further provide techniques for configuring random access parameters in inter-CU LTM cell switches.

[0049] Referring first to Fig. 1A, an example wireless communication system 100 that can implement one or more of these techniques. The wireless communication system 100 includes a UE 102, a base station (BS) 104A, a base station 106A and a core network (CN) 110. The base stations 104A, 106A can operate in a radio access network (RAN) 105. The UE 102 initially connects to the base station 104A. In some scenarios, the base station 104A 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.

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

[0051] 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 an 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 106 A is an SgNB, the UE 102 may be in NR- NR DC (NR-DC) with the MgNB and the SgNB. When the 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.

[0052] When the UE 102 hands over from the base station 104A to 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 104A and an additional base station (not shown in Fig. 1A) for example prior to the handover. The UE 102 can continue to operate in DC with the base station 106 A and the additional base station, or the UE can operate in single connectivity (SC) with the base station 106A, after completing the handover. In the latter case, the base stations 104A and 106A operate as a source MN (S-MN) and a target MN (T-MN), respectively.

[0053] 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, although the CN cansupport other cores. 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 104A and 106A can support an X2 or an Xn interface.

[0054] As illustrated in Fig. 1A, the base station 104A supports cell 124A, 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 104A 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 station 104A can support additional cell(s) such as cells 124B, and the base station 106A can support additional cell(s) (not shown in Fig. 1A). The cells 124A and 124B can partially overlap, so that the UE 102 can communicate in carrier aggregation (CA) with the base station 104 A. The base station 104A can operate the cells 124A and 124B 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 106 A, one of the base stations 104A and 106 A operates as an MeNB, an Mng-eNB or an MgNB, and the other operates as an SgNB or an Sng-eNB.

[0055] In general, the RAN 105 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 types (5G NR 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.

[0056] With continued reference to Fig. 1A, the base station 104A includes 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 signals on physical downlink (DL)channels and DL reference signals to one or more user devices (e.g., UE 102) via one or more cells (e.g., the cell(s) 124A, 124B) and / or one or more TRPs. The PHY controller 132 is also configured to receive data and control signals on physical uplink (UL) channels and / or UL reference signals from the one or more user devices via one or more cells (e.g., the cell(s) 124A, 124B) 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 layer triggered mobility (LTM, also referred to herein as Ll / L2-triggered mobility or low layer triggered mobility) related functions as described below. In examples, the LTM Controller 137 can implement LTM functions in coordination or through signaling with MAC controller 134. The processing hardware 130 can further include an RRC controller 136 to implement procedures and messaging at the RRC sublayer of the protocol communication stack. Lor 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. When the base station 104A is a distributed base station, a CU LTM Controller 137 A can operate in a CU, and a DU LTM Controller 137B can operate in a DU (see Eig. 1C). The base station 106 can include processing hardware 140 that is similar to processing hardware 130. In particular, components 142, 144, 146, and 147 can be similar to the components 132, 134, 136, and 137 respectively.

[0057] The UE 102 includes 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 from the base station 104A or 106A via one or more cells (e.g., the cell(s) 124A, 124B, and / or 126) 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 to the base station 104A or 106A via one or more cells (e.g., the cell(s) 124A, 124B, and / or 126) 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 104Aor 106A. For example, the MAC functions include 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 106A. In another example, the MAC functions include 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.

[0058] 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 106A. 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. UEs can use several types of SRBs and DRBs. When operating in DC, the cells associated with the base station operating the MN define a master cell group (MCG), and the cells associated with the base station operating as SN define the secondary cell group (SCG). For example, a first type of SRB resource, referred to as SRB1 resources, carry RRC messages, which in some cases include NAS messages over the dedicated control channel (DCCH). A second type of SRB resource, referred to as 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 to embed RRC messages related to the SN. The SRB1 and SRB2can 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.

[0059] Fig. IB is another block diagram of an example system 100B in which the RAN and a UE can implement the techniques of this disclosure for managing inter-CU LTM. Fig. IB is similar to Fig. 1A. Fig. IB depicts CN 110 having connected thereto additional base stations 104A, 104B, 106 A, and 106B communicating in cells 124A, 124B, 126 A, and 126B. Cell 125 can overlap one ore others of cells 124A, 124B, 126 A, and 126B.

[0060] Fig. 1C depicts an example distributed or disaggregated implementation of any one or more of the base station(s) shown in Fig. 1A (e.g., base station 104A or 106A). In this implementation, the base station includes a central unit (CU) 172 and one or more DUs 174. The CU 172 includes processing hardware such as one or more general-purpose processors (e.g., CPUs) and non-transitory computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or specialpurpose processing units. In one example, the CU 172 includes the processing hardware 130 (FIG. 1A). In another example, the CU 172 includes the processing hardware 140 (FIG. 1A). The processing hardware 140 in an example implementation includes an SN RRC controller that can be similar to RRC Controller 146 (FIG. 1A) configured to manage or control one or more RRC configurations and / or RRC procedures when the base station 106 A operates as an SN.

[0061] Each of the DUs 174A includes processing hardware that can include one or more general-purpose processors (e.g., 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 includes a MAC controller (e.g., MAC controller 134, 144 (Fig. 1A)) 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 106A operates as an MN or an SN. The processing hardware may also include a physical layer controller configured to manage or control one or more physical layer operations or procedures.

[0062] In some implementations, the CU 172 can include a logical node CU-CP 172A that hosts the control plane of the CU 172. The CU 172 can also include logical node(s) CU-UP 172B that hosts the user plane of the CU 172. The CU-CP 172A can transmit control information (e.g., RRC messages, Fl application protocol messages), and the CU-UP 172B can transmit the data packets (e.g., SDAP PDUs or Internet Protocol packets).

[0063] The CU-CP 172A can be connected to multiple CU-UP 172B through the El interface. The CU-CP 172A selects the appropriate CU-UP 172B for the requested services for the UE 102. In some implementations, a single CU-UP 172B can be connected to multiple CU-CP 172A through the El interface. The CU-CP 172A can be connected to one or more DU(s) 174 through an Fl-C or Wl-C interface. The CU-UP 172B can be connected to one ormore DU 174 through an Fl-U or Wl-U interface under the control of the same CU-CP 172A. In some implementations, one DU 174 can be connected to multiple CU-UP 172B under the control of the same CU-CP 172A. In such implementations, the connectivity between a CU-UP 172B and a DU 174 is established by the CU-CP 172A using Bearer Context Management functions.

[0064] 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 230 or a gNB 232 (e.g., one or more of the base stations 104A, 104B, 106A, 106B (Figs. 1A-1B).

[0065] 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 206A. The EUTRA RLC sublayer 206A in 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 Service 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 206 A, and SDAP sublayer 212 over the NR PDCP sublayer 210.

[0066] 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.”

[0067] On a control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 can provide signaling radio bearers (SRBs) or an 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 DataRadio 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.

[0068] Fig. 2B illustrates, in a simplified manner, an example protocol stack 250, on 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.

[0069] Next, with reference to Figs. 3-5, several example scenarios in which a base station operating in the system of Fig. 1 A transmits a configuration to the UE 102 and later activates a configuration for communication between the UE 102 and the base station. Generally speaking, similar events in Figs. 3-5 are labeled with similar reference numbers that share two least significant digits, with differences discussed below where appropriate. For example, event 302 is similar to event 402 of Fig. 4 and event 502 of Fig. 5, and event 390 is similar to event 490 of Fig. 4 and event 590 of Fig. 5. With the exception of the differences shown in the figures and discussed below, any of the other 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.

[0070] Referring first to Fig. 3, in a scenario 300, the base station 104A includes a CU 172 and a 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, and communicates 302 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 communicates with the UE 102. In some implementations, the UE 102 in carrier aggregation (CA) communicates with the DU 174 on the cell 124A and other cell(s) (e.g., cell(s) 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 in communicates with the DU 174 on the cell 124A only (e.g., not on other cell(s)). In some implementations, the UE 102 communicates with the DU 174 on the cell 124A and / or other cell(s) (i.e., servingcell(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 an Scell. In other implementations, the cell 124A can be an Scell, and one of the other cell(s) is a PCell. In such cases, the additional cell(s) include(s) SCell(s) and / or additional cell(s) associated with the PCell or an Scell. In the following description, the base station 104A can include the DU 174, the CU 172 or both the DU 174 and CU 172.

[0071] 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) (CSLRS(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 on other cell(s) via one or multiple TRPs.

[0072] In some implementations, the serving DU configuration includes physical layer configuration parameters, MAC configuration parameters, and / or RLC configuration parameters. In some implementations, the serving DU configuration includes at least one first non-LTM transmission configuration indicator (TCI) state configuration for the serving cell(s). In some implementations, the DU 174 can 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 the CU 172 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, theserving 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 the serving CU configuration 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 CSl-MeasConfig IE or configuration parameters for channel state information (CSI) measurement and reporting. In other implementations, the serving CU configuration includes a CSl-MeasConfig 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 UE receives the remaining portion of these configuration parameters from the base station 104A.

[0073] 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., a 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 DU configuration includes the serving cell ID(s), and the serving DU configures association(s) between the serving cell ID(s) and the first non-LTM TCI state configuration(s).

[0074] 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 atleast 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).

[0075] 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 an 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 an LTM candidate cell that could be used for communication with the UE 102. In some implementations, if the L3 measurement report(s) indicates that the signal strength and / or the quality of the first cell is above a first predetermined threshold, is better than the signal strength and / or the quality of the serving cell (e.g., cell 124A as determined, e.g., through a comparison operation), and / or is better than the signal strength and / or the 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.

[0076] 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 some implementations, 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 includes 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 an LTM indicator in the first CU-to-DU message toindicate the DU 174 to prepare the first cell for LTM. In some implementations, the CU 172 includes the LTM indicator in an LTM Information Setup IE, and the CU 172 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 an LTM Information Modify IE, and the CU 172 includes the LTM Information Modify IE in the first CU-to-DU message.

[0077] 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 (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 a first DU-to-CU message including the LTM DU configuration 1 to the CU 172 in response to the first CU-to-DU message.

[0078] The events 308 and 310 are collectively referred to in Eig. 3 as an LTM preparation procedure 390.

[0079] 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. When 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.

[0080] In some implementations, the CU 172 does not include an LTM reference DU configuration in the first CU-to-DU message. In such cases, the DU 174 generates an 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 other implementations, the DU 174 generates the LTM DU configuration 1 as a complete configuration, i.e., not merely to augment the LTM reference DU configuration.

[0081] In some implementations, the CU 172 includes an LTM reference DU configuration request in the first CU-to-DU message, and the DU 174 generates the LTM reference DU configuration, and the DU 174 includes the LTM reference DU configuration in the first DU- to-CU message in response to the request. In some implementations, the CU 172 determineswhether the UE 102 supports an LTM reference configuration. In the context of implementations and as described in the 3GPP specification 38.331, a reference configuration is a configuration provided by the network to the UE that is common, within the same cell group, to a group of configured non-complete candidate configurations. A candidate configuration can include a complete candidate configuration or a delta configuration relative to the reference configuration. If the CU 172 determines that the UE 102 supports an 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 an 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 the DU 174 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, rather than transmitting the LTM reference DU configuration request in the first CU-to-DU message. In response, the DU 174 transmits, to the CU 172, an additional DU-to-CU message including the LTM reference DU configuration. In yet other implementations, the DU 174 determines whether the UE 102 supports an LTM reference configuration. If the DU 174 determines that the UE 102 supports an 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 an LTM reference configuration, the DU 174 does not include a / the LTM reference DU configuration in the first DU-to-CU message.

[0082] In some implementations, the CU 172 includes an 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 an LTM preparation procedure as described above and with reference to Eig. 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 merely to augment the LTM reference DU configuration.

[0083] 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.

[0084] 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 remainder of the LTM reference DU configuration is different from the other portions of the serving DU configuration. In yet other implementations, the LTM reference DU configuration is the same as the serving DU configuration.

[0085] 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 remainder of the LTM reference DU configuration is different from the other portions of the serving DU configuration. In other implementations, the LTM reference DU configuration is the same as the serving DU configuration.

[0086] To prepare the first cell as an 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 an LTM synchronization signal block (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) CSI resource 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 CSLRS(s). The LTM SSB configuration include SSB configuration parameters configuring an SSB frequency, a subcarrier spacing, an SSB periodicity, SSB positions and / or SSB power for SSB(s) transmitted on the first cell.

[0087] 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 andincludes 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-CSl-ResourceConfig-rl8 IES. In other implementations, the CSI resource configuration comprises an Itm-CSl-ResourceConfigToAddModList field / IE. In some implementations, the second serving DU configuration is a CellGroupConfig IE.

[0088] In some implementations, the CU 172 includes the cell ID 1 and / or the LTM ID 1 in the second CU-to-DU message, (e.g., at event 312) In one implementation, the CU 172 includes the cell ID 1 and / or the LTM ID 1 in the second CU-to-DU message to indicate that the CSI resource configuration is / are associated with the first cell. In another implementation, the CU 172 includes the cell ID 1 and / or the LTM ID 1 in the second CU-to-DU message to allow 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, in some implementations, the CU 172 includes the LTM ID 1 in the first CU-to-DU message while in other implementations the CU 172 does not include the LTM ID 1 in the first CU-to-DU message.

[0089] 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.

[0090] 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.

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

[0092] 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 an 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.

[0093] If the first DU-to-CU message includes the LTM reference DU configuration, the CU 172 generates an 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 an 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 an 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, similarly 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, similarly to the events 320 and 322. In some implementations, if the CU 172 does not receive an LTM reference DU configuration, the CU 172 may generate an LTM reference configuration including only the LTM reference CU configuration. In other implementations, if the CU 172 does not receive an LTM reference DU configuration, the CU 172 may not generate an LTM reference configuration.

[0094] 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 is 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.

[0095] When 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, in an event 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, in an event similar to the events 320 and 322.

[0096] 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, in an event 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, in an event similar to the events 320 and 322.

[0097] 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 otherimplementations, 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. In one implementation, the DU 174 transmits the fourth DU-to- CU message if the DU 174 determines that the UE 102 supports (i.e., is capable of) early UL synchronization with an LTM candidate cell (e.g., early TA acquisition with an LTM candidate cell, early RA on an 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 an 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 may transmit an early synchronization information request if the CU 172 determines that the UE 102 supports the early UL synchronization with an LTM candidate cell. Otherwise, if the CU 172 determines that the UE 102 does not support the early UL synchronization with an 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, in an event 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, in an event similar to the events 320 and 322.

[0098] 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 174does not include the RACH configuration in either the early synchronization information or in the DU-to-CU message.

[0099] 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 for the first cell. For example, the other LTM related configuration(s) include a PCI of the first cell and / or the LTM SSB configuration.

[0100] The events 316, 318, 320, 322 are collectively referred to in Fig. 3 as an LTM configuration delivery procedure 394. The LTM configuration delivery procedure 394 can further include 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). In some implementations, the RRC reconfiguration message and the RRC reconfiguration complete message described above are an RRCReconfiguration message and an RRCReconfigurationComplete message, respectively.

[0101] 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 DE 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 UE RRC Message Transfer message. In other implementations, the third DU-to-CU message is a UE Context Modification Response message.

[0102] 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 remaining portions of the LTM reference CU configuration is different from the remaining portions of the serving CU configuration. In yet other implementations, the LTM reference CU configuration is the same as the serving CU configuration.

[0103] 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 a MeasConfig IE and / or a RadioBearerConfig IE defined in 3GPP specification 38.331 or the LTM CU configuration 1 includes configuration parameters in the MeasConfig IE and / or RadioBearerConfig IE.

[0104] 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 the LTM CU configuration 1 or the LTM reference CU configuration includes configuration parameters in the MeasConfig IE and / or RadioBearerConfig IE.

[0105] 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 includes 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 includes 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.

[0106] In some implementations, the LTM DU configuration 1 includes a first LI measurement configuration (e.g., a CSl-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 RS(s) or one or more RS resources associated with the cell 1. The RS(s) includes SSB(s) and / or CSLRS(s). The RS resource(s) includes SSBresource(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) CSl-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, each of 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 quasicolocation (QCL) type. The DL RS(s) is / are associated with the cell 1.

[0107] 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 the UE 102 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 pattern(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.

[0108] 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 the UE 102 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 CSLRS(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 in one or more second CSI resource configuration(s) that is / are included in the serving DU configuration in event 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 reportconfiguration(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).

[0109] 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 an RA preamble on the first cell. In response to the PDCCH order, the UE 102 transmits an RA preamble on the first cell. The DU 174 includes PDCCH order information in the PDCCH order. The PDCCH order information includes an RA preamble index, a UL, or a supplemental (or supplementary) UL indicator, an 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 the UE 102 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 SSB index, based on LI measurement report(s) 324, and / or the CSI resource configuration, the CSI 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.

[0110] 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 UE 102 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. 1

[0111] 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 an 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 an 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 an LTM cell switch to the first cell. In the LTM cell switch, the UE 102 accesses 332 the first cell and transmits 336 an 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 the implementation, 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.

[0112] 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 a 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 an 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 theconfigured 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 addressed to a C-RNTI of the UE 102 and determines that the LTM cell switch has completed successfully in response to receiving the PDCCH transmission.

[0113] The PDCCH transmission may include a UL grant or a DL assignment. If the PDCCH transmission includes a UL grant, the UE 102 transmits a PUSCH transmission to the DU 174 on the first cell using the UL grant. If the PDCCH transmission includes a 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 174 may 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.

[0114] 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 an 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, the LTM DU configuration 1, and / or the LTM Cell Switch Command. 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 has completed successfully. Depending on the implementation and / or the RA configuration parameters, the RA procedure can be a four-step RA procedure or a two-step RA procedure. Depending on the implementation and / or the RA configuration parameters, the RA procedure can be a contention-free RA (CERA) procedure or a contention-based RA (CBRA) procedure. During a four-step RA procedure, the UE 102 transmits an RA preamble (i.e., Message 1) on the first cell and receives an RA response (i.e., Message 2) on the first cell from the DU 174 in response to the RA preamble. The UE then transmits Message 3 on the first cell using a UL grant in the RA response, and the DU 174 transmits a Message 4 on the first cell to the UE 102 in response. In some implementations, the Message 4 is a DCI. In the case where the RA procedure is a CBRA procedure, the UE 102 determines contention resolution is successful in response to receiving the Message 4. In the case where the RA procedure is a CBRA procedure, the RApreamble is dedicated preamble, and the UE 102 determines contention resolution is successful in response to receiving the RA response. During a 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. When the RA procedure is a CFRA or CBRA procedure, the UE 102 determines contention resolution is successful in response to receiving the Message B. 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 after transmitting the Message 4 or Message B.

[0115] In some implementations, the DU 174 includes a first set of LTM CFRA configuration parameters in the LTM Cell Switch Command to configure the UE 102 to perform a CFRA procedure to access the first cell. In some implementations, the first set of LTM CFRA configuration parameters include a first RA preamble index, a first SSB index, a first PRACH Mask index, and / or a first UL / supplemental (or supplementary) UL (SUL) indicator. In some implementations, the first UL / NUL indicator configures the UE 102 to perform the CFRA procedure on a normal UL (NUL) or a SUL. For example, if the first UL / SUL indicator indicates UL (e.g., if the first UL / SUL indicator is set to a first value), the UE 102 performs the CFRA procedure on the UL. Otherwise, if the first UL / SUL indicator indicates SUL (e.g., the first UL / SUL indicator is set to a second value), the UE 102 performs the CFRA procedure on the SUL. The UE 102 performs 332 the CFRA procedure to access the first cell using the LTM CFRA configuration parameters and at least one RACH configuration. The LTM candidate configuration 1 includes the RACH configuration(s). The RACH configuration(s) is / are not configured for early UL synchronization. In some implementations, the RACH configuration(s) is / are configured for an LTM cell switch. In some implementations, the at least one RACH configuration includes a common RACH configuration (e.g., RACH-ConfigCommon IE) and / or a generic RACH configuration (e.g., RACH-ConfigGeneric IE). In some implementations, the RACH configuration(s) does not include a dedicated RACH configuration (e.g., RACH-ConfigDedicated IE). In other implementations, the RACH configuration(s) includes a dedicated RACH configuration (e.g., RACH-ConfigDedicated IE). The DU 174 performs the CFRA procedure with the UE 102 inaccordance with the first set of LTM CFRA configuration parameters and the RACH configuration(s).

[0116] In some implementations, the DU 174 determines whether to include the first set of LTM CFRA configuration parameters in the LTM Cell Switch Command, based on the measurement report(s) received at event 354. In some implementations, the DU 174 obtains (e.g., retrieves, derives, calculates, or determines) one or more measurement results from the measurement report(s). In some implementations, the measurement result(s) include a measurement result for a first SSB identified by the first SSB index. The first SSB is transmitted by the DU 174 on the first cell. In such cases, if the measurement result for the first SSB is above (or equal to) a second predetermined threshold, the DU 174 includes the first set of LTM CFRA configuration parameters in the LTM Cell Switch Command. Otherwise, if the measurement result for the first SSB is below (or equal to) the second predetermined threshold, the DU 174 refrains from including the first set of LTM CFRA configuration parameters in the LTM Cell Switch Command.

[0117] In some implementations, the DU 174 (pre)configures the first set of LTM CFRA configuration parameters. The DU 174 may preconfigure at least one additional set of LTM CFRA configuration parameters and each of the additional set(s) includes an RA preamble index, an SSB index, a PRACH Mask index and / or a UL / SUL indicator for the first cell. In some implementations, the first set and / or the additional set(s) are configured specifically for the first cell. In other implementations, the first set and / or the additional set(s) are configured for any cell operated by the DU 174. In some implementations, the DU 174 preconfigures the first set and / or the additional set(s) for one of UL (i.e., NUL) and SUL. In other implementations, the DU 174 preconfigures the first set for one of UL and SUL and configures the additional set for the other of UL and SUL.

[0118] In some implementations, when the DU 174 identifies the first SSB index based on the measurement report(s) as described above, the DU 174 identifies the first set of LTM CFRA configuration parameters based on the first SSB index. In some implementations, the DU 174 determines a value of the first UL / SUL indicator based on the measurement result for the first SSB. For example, if the measurement result is below (or equal to) a third predetermined threshold, the DU 174 sets the first UL / SUL indicator to a first value indicating UL (i.e., NUL). Otherwise, if the measurement result for the first SSB is above (or equal to) the third predetermined threshold, the DU 174 sets the first UL / SUL indicator to asecond value indicating SUL. In other implementations, the DU 174 determines a value of the first UL / SUL indicator based the LTM DU configuration 1. For example, if the LTM DU configuration 1 includes a RACH configuration for UL and does not include a RACH configuration for SUL, the DU 174 sets the first UL / SUL indicator to the first value.Otherwise, if the LTM DU configuration 1 includes a RACH configuration for SUL (wherein in some implementations the LTM DU configuration 1 includes a RACH configuration for UL while in other implementations the LTM DU configuration 1 does not include a RACH configuration for UL), the DU 174 may set the first UL / SUL indicator to the second value or determine a value of the first UL / SUL indicator based on the measurement result for the first SSB as described above. In yet other implementations, the DU 174 sets the first UL / SUL indicator to a preconfigured value (e.g., the first value), e.g., because the DU 174 does not support SUL. In yet other implementations, the DU 174 sets the first UL / SUL indicator to a preconfigured value (e.g., the second value), e.g., because the DU 174 is preconfigured to set the first UL / SUL indicator to this preconfigured value.

[0119] In some implementations, the first, second and third predetermined thresholds are the same threshold. In other implementations, at least two of the first, second and third predetermined thresholds are different or are set to different values.

[0120] 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 applies the LTM candidate configuration 1 to augment the LTM reference configuration.

[0121] In some implementations, each of the TCI state configuration(s) include a TCI state ID. In some implementations, the DU 174 includes, in the DU-CU Cell Switch Notification message and / or 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 TCI 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 the DU 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. In other implementations, in case that separate TCI states are used, the DL TCI State and the UL TCI state use different TCI State IDs. In such cases, the DU 174 includes, in the DU-CU CellSwitch Notification message and / or the LTM Cell Switch Command, a first TCI State ID for DL and / or a second TCI State ID for UL that identify a first one and a second one of the TCI state configuration(s) respectively. The UE 102 identifies the first TCI state configuration and the second TCI state configuration based on the first TCI state ID and the second TCI state ID, respectively. The UE 102 applies the first TCI state configuration and the second TCI state configuration to communicate DL transmissions and UL transmissions, respectively, with the DU 174 in the events 332, 336, and / or 340. The DU 174 identifies the first TCI state configuration and the second of the TCI state configuration based on the first TCI state ID and the second TCI state ID, respectively. The DU 174 applies the first TCI state configuration and the second TCI state configuration to communicate DL transmissions and UL transmissions, respectively, with the UE 102 in the events 332, 336, and / or 340.

[0122] 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. Lor 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 configuration(s) 2, ..., N and the LTM candidate configuration(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 configuration(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 listincluding: {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(s) 2, ..., N is similar to the procedure 394. In other implementations, the CU 172 includes the list in the first RRC reconfiguration message.

[0123] In 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 transmits messages to release resources and configurations of candidate cells. 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.

[0124] In some implementations, an LTM ID is provided in a different format depending on which command or message provides the LTM ID. For example, the LTM ID may be provided differently in a PDCCH order, an LTM Cell Switch Command, and an RRC reconfiguration message. 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, ... , and the first field with binary value 11 lb is equivalent to the second field with integer value 8.

[0125] The events 304, 306, 390, 392, 394, and 324 are collectively referred to 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 as an intra- CU intra-DU LTM procedure 380.

[0126] Referring next to Fig. 4, in a scenario 400, the base station 104A includes a CU 172, an 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 different cell (e.g., cell 124B or cell 126A (Fig. 1A)). 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.

[0127] 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 the UE 102 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 may perform the LTM configuration procedure 496 or the LTM procedure 480 with the UE 102, similar to the procedures 396 and 380, respectively, as described with reference to Fig. 3. In the case of the procedure 380, the UE 102 may perform an LTM cell switch to the first cell (e.g., cell 124B) as described with reference to Fig. 3. Upon successfully completing the LTM cell switch, the first cell becomes a serving 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 496, the UE 102 does not perform an 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 126A 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 an LTM preparation procedure with the C-DU 174B to prepare or to request the C-DU 174B to prepare the cell 1 as an 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 an 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 an LTM DU configuration (e.g., LTM DU configuration 1) to the CU 172, similar to the event 310. In some implementations, the CU 172 requests an LTM reference DU configuration in the first CU-to-DU message, as described with reference toFig. 3, while in other implementations the CU 172 does not request an LTM reference DU configuration in the first CU-to-DU message. In some implementations, the C-DU 174B includes an LTM reference DU configuration in the first DU-to-CU message, as described with reference to Fig. 3, while in other implementations, the C-DU 174B does not include an LTM reference DU configuration in the first DU-to-CU message.

[0128] In some implementations, if the CU 172 receives an LTM reference DU configuration from the S-DU 174A as described with reference to 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 an LTM reference DU configuration for the UE 102 to the CU 172. In other implementations, the CU 172 receives an 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 with reference to Fig. 3. In such cases, the CU 172 may generate an LTM reference configuration including the LTM reference DU configuration. In some implementations, the CU 172 includes an LTM reference CU configuration in the LTM reference configuration, while in other implementations the CU 172 does not include an LTM reference CU configuration in the LTM reference configuration.

[0129] To prepare the cell 1 for LTM, the CU 172 may perform 492 an 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 an 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 an LTM candidate configuration (e.g., LTM candidate configuration 1) including the LTM DU configuration and the CU 172 assigns an LTM ID (e.g., LTM ID 1) for identifying the LTM DU configuration and / or the LTM candidate configuration as described with reference to 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.

[0130] To prepare the cell 1 as an 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 firstDU-to-CU message or an additional DU-to-CU message) from the C-DU 174B similarly to DU-to-CU messages describes with reference to Fig. 3.

[0131] 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 in 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 in 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.

[0132] In some implementations, the C-DU 174B includes a first set of LTM CFRA configuration parameters in the first DU-to-CU message of the procedure 490. In some implementations, the first set of LTM CFRA configuration parameters includes a first RA preamble index, a first SSB index, a first PRACH Mask index, and / or a first UL / SUL indicator. In such cases, the CU 172 includes the first set of LTM CFRA configuration parameters in the second CU-to-DU message of the procedure 492. The C-DU 174B may include at least one additional set of LTM CFRA configuration parameters in the first DU-to- CU message of the procedure 490. Each of the additional set(s) of LTM CFRA configuration parameters include an RA preamble index, an SSB index, a PRACH Mask index, and / or a UL / SUL indicator. In such cases, the CU 172 includes the additional set(s) of LTM CFRA configuration parameters in the second CU-to-DU message of the procedure 492. In some implementations, the C-DU 174B configures the first set and / or the additional set(s) of LTM CFRA configuration parameters for the UE 102. In some implementations, the first set and / or the additional set(s) of LTM CFRA configuration parameters are configured specifically for the cell 1. In other implementations, the first set and / or the additional set(s) of LTM CFRA configuration parameters are configured for any LTM candidate cell configured by the C-DU 174B for the UE 102.

[0133] In some implementations, the first set and the additional set(s) of LTM CFRA configuration parameters do not include separate UL / SUL indicators. In some implementations, the C-DU 174B configures the first set and / or the additional set(s) of LTM CFRA configuration parameters for one of UL (i.e., NUL) and SUL (e.g., either UL / NUL orSUL), and the C-DU 174B includes, in the first DU-to-CU message, a single UL / SUL indicator indicating that the first set and / or the additional set(s) of LTM CFRA configuration parameters are configured for UL / NUL or SUL. In such cases, the CU 172 includes, in the second CU-to-DU message, a single UL / SUL indicator indicating the first set and / or the additional set(s) of LTM CFRA configuration parameters are configured for UL / NUL or SUL. In other implementations, if the C-DU 174B configures the first set and / or the additional set(s) of LTM CFRA configuration parameters for UL, the C-DU 174B includes, in the first DU-to-CU message, the first set and / or the additional set(s) in a first field / IE in the first DU-to-CU message. Otherwise, if the C-DU 174B configures the first set and / or the additional set(s) of LTM CFRA configuration parameters for SUL, the C-DU 174B includes, in the first DU-to-CU message, the first set and / or the additional set(s) in a second field / IE in the first DU-to-CU message. In such cases, the first field / IE and the second field / IE are defined for UL and SUL, respectively. In some implementations, if the first DU-to-CU includes the first set and / or the additional set(s) of LTM CFRA configuration parameters in the first field / IE, the CU 172 includes the first set and / or the additional set(s) in a first field / IE in the second CU-to-DU message. Otherwise, if the first DU-to-CU includes the first set and / or the additional set of LTM CFRA configuration parameters in the second field / IE, the CU 172 includes the first set and / or the additional set(s) in a second field / IE in the second CU-to-DU message. In such cases, the first field / IE and the second field / IE are defined for UL and SUL, respectively.

[0134] In some implementations, the C-DU 174B configures the first set of LTM CFRA configuration parameters for one of UL and SUL (e.g., either UL or SUL), and the C-DU 174B configures the additional set for the other of UL and SUL. In some implementations, the C-DU 174B sets the first UL / SUL indicator to a value indicating the one of UL and SUL and sets the UL / SUL indicator in the additional set to a value indicating the other of the UL and SUL. In other implementations, if the C-DU 174B configures the first set for one of UL and SUL and configures the additional set for the other of UL and SUL, the C-DU 174B includes the first set and the additional set in one and the other of the first field / IE and the second field IE respectively in the first DU-to-CU message. In such cases, the CU 172 includes the first set and the additional set in one and the other of the first field / IE and the second field IE respectively in the second CU-to-DU message.

[0135] As described with reference to Fig. 3, the CU 172 performs 494 an LTM configuration delivery procedure with the UE 102 to transmit the LTM ID 1 and the LTMcandidate 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 in the first RRC reconfiguration message to the UE 102 and / or other RRC reconfiguration message(s) transmitted to the UE 102, as described with reference to Fig. 3. The CU 172 includes the LTM ID in the first RRC reconfiguration or the other RRC reconfiguration message(s) to indicate that 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 an RRC reconfiguration complete message to the CU 172 via the S-DU 174A.

[0136] In some implementations, the PDCCH order information includes a frequency domain resource assignment, an RA preamble index, a UL or a supplemental (or supplementary) UL indicator, an 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, when the CU 172 transmits the PDCCH order information in the second CU-to-DU message, the CU 172 includes {the cell ID 1, the PDCCH order information} as a tuple in the CU-to-DU message. When the CU 172 transmits an 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 an SSB index included in the PDCCH order, based on LI measurementreport(s) 424, and / or the CSI resource configuration, the CSI report configuration, 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. When the CU 172 transmits the PDCCH order information in 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 UE 102 transmits 452 an 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, an 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 an 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).

[0137] 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 OLDM 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).

[0138] In response to determining to command the UE 102 to perform an LTM cell switch or transmitting 426 the LTM Cell Switch Command, the S-DU 174A transmits 428 a DU-CUCell Switch Notification message to the CU 172 to indicate that the UE 102 performs an LTM cell switch to the cell 1. In response, the CU 172 transmits 430 a CU-DU Cell Switch Notification message to the C-DU 174B to indicate that the UE 102 performs an LTM cell switch to the cell 1. The UE 102 accesses 432 the cell 1 in response to the LTM Cell Switch Command. In some implementations, the S-DU 174A determines to include and / or includes the first set of LTM CFRA configuration parameters in the LTM Cell Switch Command to configure the UE 102 to perform a CFRA procedure to access the cell 1 as described with reference to Fig. 3. The UE 102 performs the CFRA procedure to access the cell 1, using the LTM CFRA configuration parameters and at least one RACH configuration as described with reference to Fig. 3. The C-DU 174B performs the CFRA procedure with the UE 102 in accordance with the LTM CFRA configuration parameters and the RACH configuration(s) as described with reference to Fig. 3.

[0139] In some implementations, the S-DU 174A determines whether to include the first set of LTM CFRA configuration parameters in the LTM Cell Switch Command, based on the measurement report(s) received at event 454. In some implementations, the S-DU 174A obtains (e.g., retrieves, derives, calculates, or determines) one or more measurement results from the measurement report(s). In some implementations, the measurement result(s) include a measurement result for a first SSB identified by the first SSB index. The first SSB is transmitted by the C-DU 174B on the cell 1. In such cases, if the measurement result for the first SSB is above (or equal to) a second predetermined threshold, the S-DU 174A includes the first set of LTM CFRA configuration parameters in the LTM Cell Switch Command. Otherwise, if the measurement result for the first SSB is below (or equal to) the second predetermined threshold, the S-DU 174A refrains from including the first set of LTM CFRA configuration parameters in the LTM Cell Switch Command.

[0140] In some implementations, in the case in which the first set of LTM CFRA configuration parameters includes the first UL / SUL indicator, the S-DU 174A includes the first UL / SUL indicator in the LTM Cell Switch Command as described with reference to Fig. 3. In other implementations, in the case in which the first set of LTM CFRA configuration parameters does not include a UL / SUL indicator, the S-DU 174A may determine a value of a UL / SUL indicator and include the UL / SUL indicator in the LTM Cell Switch Command as described below and / or with reference to Fig. 3. In some implementations, if the second CU- to-DU message includes the first set of LTM CFRA configuration parameters in the first field / IE for UL, the S-DU 174A sets the UL / SUL indicator to the first value for UL.Otherwise, if the second CU-to-DU message includes the first set of LTM CFRA configuration parameters in the second field / IE for UL, the S-DU 174A sets the UL / SUL indicator to the second value for SUL. In other implementations, the S-DU 174A determines a value of the UL / SUL indicator in the LTM Cell Switch Command based on a measurement result for the first SSB that the S-DU 174A obtains from the measurement report(s) at event 454. In one implementation, if the measurement result is above (or equal to) a predetermined threshold, the S-DU 174A sets the UL / SUL indicator to the first value and includes the first set in the LTM cell switch command. Otherwise, if the measurement result is below (or equal to) the predetermined threshold, the S-DU 174A sets the UL / SUL indicator to the second value and includes the additional set in the LTM cell switch command instead of the first set. In other implementations, the S-DU 174A sets the UL / SUL indicator to a preconfigured value (e.g., the first value), because the C-DU 174B does not support SUL. In yet other implementations, the S-DU 174A sets the UL / SUL indicator to a preconfigured value (e.g., the second value), because the S-DU 174A is preconfigured to set the UL / SUL indicator to the preconfigured value.

[0141] 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 TCI 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.

[0142] In other implementations, if separate TCI states are used, the DL TCI State and the UL TCI state use different TCI State IDs. In such cases, the S-DU 174A includes, in the DU- CU Cell Switch Notification message and / or the LTM Cell Switch Command, a first TCI State ID for DL and a second TCI State ID for UL that identify a first and a second TCI state configuration(s) respectively. The CU 172, in response to the DU-CU Cell Switch Notification message, in turn includes the first TCI State ID and the second TCI state ID in the CU-DU Cell Switch Notification message to the C-DU 174B. The UE 102 identifies the first TCI state configuration and the second TCI state configuration based on the first TCI state ID and the second TCI state ID, respectively. The UE 102 applies the first TCI state configuration and the second TCI state configuration to receive DL transmissions and transmit UL transmissions, respectively, with the C-DU 174B in the events 432, 436 and / or440. The C-DU 174B identifies the first TCI state configuration and the second the TCI stateconfiguration based on the first TCI state ID and second TCI state ID, respectively. The C- DU 174B applies the first TCI state configuration and the second TCI state configuration to communicate DL transmissions and UL transmissions, respectively, with the UE 102 in the events 432, 436, and / or 440.

[0143] 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 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 TCI state configuration(s) is associated with the LTM ID 1 or the cell ID 1. For example, when the CU 172 transmits the TCI state configuration(s) and / or the associated TCI state ID(s) in the second CU-to-DU message, the CU 172 includes {the cell ID 1, the TCI state configuration(s)} as a tuple in the CU-to-DU message. When the CU 172 transmits an 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 first 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.

[0144] 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 with reference to Fig. 3.

[0145] 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. In other implementations, the LTM procedure 490 and the additionalLTM preparation procedures are UE Context Setup procedures. In yet other implementations, the LTM procedure 490 and the additional LTM preparation procedures are UE Context Modification procedures.

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

[0147] Referring next to Eig. 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 Eig. 5), similar to the base station 104A of Eigs. 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 104A includes an S-DU and a CU and the serving configuration may include a serving CU configuration and a serving DU configuration, as described with reference to Figs. 3 and 4. While communicating 502 with the UE 102, the S-BS 104A may perform 580 intra-CU LTM procedure(s) with the UE 102, similar to the procedures 380 and / or 480. Alternatively, while communicating 502 with the UE 102, the S-BS 104A may perform 596 intra-CU LTM configuration procedure(s) with the UE 102, similar to the procedures 396 and / or 496.

[0148] 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 126A) as an 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 106 A based on the PCI and determines that the first cell qualifies for LTM preparation based on the measurement result(s).

[0149] After (e.g., in response to) determining to prepare the first cell as an LTM candidate cell for the UE 102, the S-BS 104A (e.g., the CU of the S-BS 104A) generates a HandoverRequest message including a first cell ID (i.e., cell ID 1) of the first cell (i.e., cell 1). The S- BS 104A transmits 505 the Handover Request message to the CU 172. In some implementations, the Handover Request message includes an 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 an LTM preparation procedure 590 with the DU 174 to prepare the first cell as an 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 an 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).

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

[0151] 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 may be a gNB ID.

[0152] In some implementations, the CU 172 requests an ETM reference DU configuration in the procedure 590, as described with reference to Figs. 3 and 4, while in other implementations, the CU 172 does not request an ETM reference DU configuration. In some implementation s, the DU 174 transmits an ETM reference DU configuration to the CU 172 in the procedure 590, as described with reference to Figs. 3 and 4, while in other implementations, the DU 174 does not transmit an ETM reference DU configuration to the CU 172. In some implementations, the S-BS 104A (e.g., the CU of the S-BS 104A) may obtain an ETM reference configuration, as described with reference to Figs. 3 and 4. In other implementations, the S-BS 104A may receive an LTM reference configuration from anotherBS (not shown in Fig. 5) in another inter-CU LTM preparation procedure as described above and later herein. If the S-BS 104A obtains an 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 messageHandoverP reparationinformation or as an Xn Application Protocol (XnAP) IE or field and includes the inter-node RRC message or the XnAP IE in the Handover Request message. Alternatively, the S-BS 104A determines to request or cause the C-BS 106A to provide a complete LTM candidate configuration in which case the S-BS 104A does not include the LTM reference configuration in the Handover Request message. If the S-BS 104A does not obtain an LTM reference configuration, the S-BS 104A does not include an LTM reference configuration in the Handover Request message. If the Handover Request message includes an LTM reference configuration, the CU 172 may include the LTM reference configuration in the first CU-to-DU message. The DU 174 may extract an LTM reference DU configuration from the LTM reference configuration. Alternatively, the CU 172 extracts an 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 an LTM DU configuration as a delta configuration based on the LTM reference DU configuration, as described with reference to Fig. 3. Alternatively, the DU 174 may ignore the LTM reference (DU) configuration and generate an LTM DU configuration as a complete configuration, as described with reference to Fig. 3.

[0153] Otherwise, if the Handover Request message does not include an LTM reference configuration, in some implementations the CU 172 receives an LTM reference DU configuration from the DU 174 as described with reference to Fig. 3 while in other implementations the CU 172 does not receive an LTM reference DU configuration from the DU 174. If the CU 172 receives an LTM reference DU configuration (e.g., in the first DU-to- CU message), the CU 172 generates an LTM reference configuration (C-BS generated LTM reference configuration) including the LTM reference DU configuration. The CU 172 may include an LTM reference CU configuration (candidate CU (C-CU) generated LTM reference CU configuration). Otherwise, if the CU 172 does not receive an LTM reference DU configuration from the DU 174 as described with reference to Fig. 3, the CU 172 does not generate an LTM reference configuration. Alternatively, the CU 172 generates an LTM reference configuration (C-BS generated LTM reference configuration) only including a C-CU generated LTM reference CU configuration. When the CU 172 generates an 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.

[0154] 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 dedicated field / IE (e.g., LTM specific) to reduce or eliminate an impact to non-LTM configurations. In other implementations, the complete configuration indication is an existing field / IE defined in 3GPP specification 38.423. Otherwise, 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 dedicated field / IE (e.g., LTM specific) to reduce or eliminate 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 can have one of at least two possible values (i.e., a first value and a second value). A first value for the BS-to-BS interface protocol field / IE can indicate a complete configuration and the second value for BS-to-BS interface protocol field / IE can indicate a delta configuration.

[0155] In some implementations, the S-BS 104A is preconfigured with a CSI resource configuration (e.g., CSI resource configuration 1 or LTM CSI resource configuration 1) and / or an 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 LTMSSB configuration from an OAM (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 an LTM CSI report configuration and / or LTM ID configuration procedure (not shown in Fig. 5) with an 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 CSI report configurations for the UE 102 from the S-DU of the S-BS 104A. 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.

[0156] To prepare the first cell as an LTM candidate cell for the UE 102, the CU 172 may receive early synchronization information (e.g., 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 (e.g., RACH configuration 1) and / or at least one TCI state configuration (e.g., 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.

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

[0158] After (e.g., in response to) receiving the Handover Request Acknowledge 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 the S-BS 104A received this information in the Handover Request Acknowledge message. Alternatively, the S-BS 104A 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 each of 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 104A in 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 an LTM configuration delivery procedure. The S-BS 104A may include the second serving DU configuration in the first RRC reconfiguration message or in one of the additional RRC reconfiguration message(s).

[0159] 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., an 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 if the Handover Request Acknowledge message includes the delta configuration indication to indicate that the LTM candidate configuration 1 is a delta configuration, the S-BS 104Aexcludes or does not include, in the first RRC reconfiguration message, the complete configuration indication (e.g., an RRC field / IE) to indicate that the LTM candidate configuration 1 is a delta configuration.

[0160] If the Handover Request Acknowledge message includes the PDCCH order information (e.g., 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 104A. 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 an 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 102 transmits 552 an 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 transmits 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-BS 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, an 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 104A to 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.

[0161] 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 theseimplementations, 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.

[0162] In response to determining to command the UE 102 to perform an 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 104A transmits 526 the LTM Cell Switch Command including the LTM ID 1 (e.g., configuration identifier) 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 an 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 transmits 536 the RRC reconfiguration complete message including the LTM ID 1 to 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 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 between the first cell ID and the LTM reference configuration. When the CU 172 receives 534 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.

[0163] In some implementations, the UE 102 may perform an RA procedure to access the first cell in the event 532. The RA procedure can be a four-step RA procedure or a two-step RA procedure. The RA procedure can be a CBRA procedure or a CERA procedure. In some implementations, the S-BS 104A includes a first set of LTM CERA configuration parameters in the LTM Cell Switch Command to configure the UE 102 to perform a CERA procedure to access the first cell. The UE 102 performs the CERA procedure using the first set of LTM CERA configuration parameters. In some implementations, the DU 174 includes the first set of the LTM CERA configuration parameters in the first DU-to-CU message of the procedure 590 as described for the procedure 490. The CU 172 in turn includes the first set of the LTMCFRA configuration parameters in the Handover Request Acknowledge message. In some implementations, the DU 174 includes at least one additional set of LTM CFRA configuration parameters in the first DU-to-CU message as described for the procedure 490. The CU 172 in turn includes the additional set(s) of the LTM CFRA configuration parameters in the Handover Request Acknowledge message.

[0164] In some implementations, the DU 174 configures the first set and / or the additional set(s) for UL (i.e., NUL) or SUL and indicates such configurations in the first DU-to-CU message, as described for the C-DU 174B in Fig. 4. In cases where the first set and / or the additional set(s) are configured for one of UL and SUL, the CU 172 includes, in the Handover Request Acknowledge message, a single UL / SUL indicator indicating the first set and / or the additional set(s) are configured for the one of UL and SUL. In cases in which the first set and / or the additional set(s) are configured for UL, the CU 172 includes the first set and / or the additional set(s) in a first field / IE in the Handover Request Acknowledge message. In cases in which the first set and / or the additional set(s) are configured for SUL, the CU 172 includes the first set and / or the additional set(s) in a second field / IE in the Handover Request Acknowledge message. In such cases, the first field / IE and the second field / IE are defined for UL and SUL, respectively.

[0165] In some implementations, the DU 174 configures the first set for one of UL and SUL and configures the additional set for the other of UL and SUL, and the DU 174 indicates such configurations in the first DU-to-CU message, as described with reference to the C-DU 174B in Fig. 4. In such cases, the CU 172 sets a UL / SUL indicator in the first set to a value indicating the one of UL and SUL, and the CU 172 sets a UL / SUL indicator in the additional set to a value indicating the other of the UL and SUL. Alternatively, the CU 172 includes the first set and the additional set in one and the other of the first field / IE and the second field IE respectively in the Handover Request Acknowledge message.

[0166] 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 104A 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 configurations(s). If the LTM Cell Switch Command includes the TA value, the UE 102 may skip performing an / the RA procedure to access the first cell in the event 532.Otherwise, the UE 102 may perform an / the RA procedure to access the first cell in the event 532 as described above.

[0167] 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 104A 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 an 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 an 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 an 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 TCI state configuration(s) based on the first TCI state ID and the UE 102 and the DU 174 apply the first TCI state configuration to communicate UL transmissions and / or DL transmissions in the events 532, 536 and / or 540. In other implementations, when separate TCI states are used, the DL TCI State and the UL TCI state use different TCI State IDs. In such cases, the S-DU of the S-BS 104A includes, in the DU-CU Cell Switch Notification message and / or the LTM Cell Switch Command, a first TCI State ID for DL and / or a second TCI State ID for UL that identify a first and a second TCI state configuration(s) respectively. In response to the DU-CU Cell Switch Notification message, the CU of the S-BS 104A includes the first TCI State ID and the second TCI state ID in the CU-CU Cell Switch Notification message to the CU 172. The CU 172 then includes the first TCI state ID and the second TCI state ID in the CU-DU Cell Switch Notification message to the DU 174. The UE 102 identifies the first TCI state configuration and the second TCI state configuration based on the first TCI state ID and the second TCI state ID respectively. The UE 102 applies the first TCI state configuration and the second TCI state configuration to receive DL transmissions and transmit UL transmissions, respectively, with the DU 174 in the events 532, 536 and / or 540. The DU 174 identifies the first TCI state configuration and the second TCI state configuration based on the first TCI state ID and second TCI state ID, respectively. The DU 174 applies the first and / or the second TCI state configuration to communicate DL transmissions and / or UL transmissions, respectively, with the UE 102 in the events 532, 536, and / or 540.

[0168] 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 104A) transmits 531 one or more Early Status Transfer messages to the CU 172, each including 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 after receiving 538 the DU-to-CU message or the RRC reconfiguration complete message, the CU 172 transmits 539 an LTM Success message to the S-BS 104A (e.g., the CU of the S-BS 104A) to indicate that the LTM cell switch has 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 has completed successfully.

[0169] 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 an 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.

[0170] 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 104A releases a UE context of the UE 102.

[0171] 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 582, 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. Lor example, the S-BS 104A performs additional inter-CU LTMpreparation 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 582. 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 104A or the C-BS 106A assigns LTM ID(s) 2, ..., N to identify the LTM candidate configuration(s) 2, ..., N, respectively. The S-BS 104A 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, and / or 494. In other implementations, the S-BS 104A includes the list in the first RRC reconfiguration message.

[0172] In other implementations, the S-BS 104A performs the procedure 582 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, ..., Mwith the DU 174 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 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 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.When 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.

[0173] 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 104A obtains CSI resource configuration(s) 2, ..., M for the cell(s) 2, ..., M, respectively, as described for the CSI resource configuration 1. When 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.

[0174] 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. When 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. When the CU 172 obtains the PCI(s) 2, ..., M, the CU 172 includes the PCI(s) 2, ..., M in the Handover Request Acknowledge message.

[0175] In some implementations, the CU 172 includes a list: {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 Handover Request Acknowledge message.

[0176] In some implementations, the CU 172 obtains PDCCH order information 2, ..., M for the cell(s) 2, ..., M, respectively, as described with reference to 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.

[0177] In some implementations, the S-BS 104A may perform LTM configuration delivery procedure 2, ..., M with the UE 102 to transmit a list comprising: {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, and / or 494. In other implementations, the S-BS 104A includes the list in the first RRC reconfiguration message.

[0178] 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.

[0179] Figs. 6A-6D are message sequence diagrams of inter-CU LTM scenarios in which a UE is in DC. Referring first to Fig. 6A, in a scenario 600A, the base station 104B operates as an MN, the base station 106A operates as a candidate SN (C-SN) and the base station 104A operates 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 shown in Fig. 6A), 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 106A. The scenario 600A is similar to the scenario 500, except that the scenario 600A is a DC scenario and the scenario 500 is not a DC scenario.

[0180] Initially, the UE 102 in DC communicates 602 with the MN 104B and with S-SN 104A. In some implementations, the UE 102 communicates with the DU of the S-SN 104A 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 an 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 104A configures the SCG which includes at least one serving cell (e.g., the cell 124A and / orother 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 with reference to 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 104A configures to exchange RRC messages between the UE 102 and the S-SN 104A.

[0181] While communicating with the UE 102 in DC with the MN 104B and S-SN 104A, 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 with 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, 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 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 an RRC reconfiguration complete message to the S-SN 104A via the MN 104B.

[0182] While communicating in DC with the MN 104B and S-SN 104A, 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 104A) or via the MN 104B.

[0183] 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 an LTM candidate cell for the UE 102. In response to the determination, the S-SN 104A generates an 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 106A. In some implementations, the SN Required message includes an 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 an SN Request message (a first SN Request message) including the first cell ID to the CU 172 to request preparing the first cell as an LTM candidate cell for the UE 102. In response to the SN Request message, the CU 172 performs an LTM preparation procedure 690 with the DU 174 to prepare the first cell as an 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 an 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 SN Request message, the CU 172 transmits 607 an 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 an 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).

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

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

[0186] 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.

[0187] In some implementations, the CU 172 requests an LTM reference DU configuration in the procedure 690, as described for Figs. 3, 4 and 5 while in other implementations the CU 172 does not request an LTM reference DU configuration. In some implementations, the DU 174 transmits an LTM reference DU configuration to the CU 172 in the procedure 690, as described for Figs. 3, 4 and 5 while in other implementations the DU 174 does not transmit an LTM reference DU configuration to the CU 172. In some implementations, the S-SN 104A (e.g., the CU of the S-SN 104A) may obtain an LTM reference configuration, as described for Figs. 3 and 4. In other implementations, the S-SN 104A may receive an 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 an 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 104A 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 an LTM reference configuration, the S-SN 104A does not include an LTM reference configuration in the SN Required message. If the SN Required message includes an 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 an LTM reference configuration, the MN 104B may not include the LTM reference configuration in the SN Request message.

[0188] If the SN Request message includes an 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 an 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 an LTM reference configuration, in some implementations, the CU 172 receives an LTM reference DU configuration from the DU 174 as described with reference to Fig. 3 while in other implementations, the CU 172 does not receive an LTM reference DU configuration from the DU 174. If the CU 172 receives an LTM reference DU configuration (e.g., in the first DU-to- CU message), the CU 172 generates an LTM reference configuration (C-SN generated LTM reference configuration) including the LTM reference DU configuration. The CU 172 may include an LTM reference CU configuration (candidate CU (C-CU) generated LTM reference CU configuration). Otherwise, if the CU 172 does not receive an LTM reference DU configuration from the DU 174 as described with reference to Fig. 3, the CU 172 does not generate an LTM reference configuration. Alternatively, the CU 172 generates an LTM reference configuration (C-SN generated LTM reference configuration) only including a C- CU generated LTM reference CU configuration. When the CU 172 generates an 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.

[0189] 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 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 dedicated field / IE (e.g., LTM specific) to reduce or eliminate an impact to non-LTM configurations. In other implementations, the complete configuration indication is an existing field / IE defined in 3GPP specification 38.423. Otherwise, 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 SNRequest 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 dedicated field / IE (e.g., LTM specific) to reduce or eliminate 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 can have one of at least two possible values (i.e., a first value and a second value). A first value for the BS-to-BS interface protocol field / IE can indicate a complete configuration and a second value for the BS-to-BS interface protocol field / IE can indicate a delta configuration.

[0190] In some implementations, the S-SN 104A is preconfigured with a CSI resource configuration (e.g., a CSI resource configuration 1 or an LTM CSI resource configuration 1) and / or an 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 an LTM CSI report configuration and / or an LTM ID configuration procedure (not shown in Fig. 6A) with an S-DU of the S-SN 104A, 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).

[0191] 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 with reference to 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.

[0192] In some implementations, the CU 172 assigns an 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 104B 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 an LTM ID (e.g., LTM ID 1) for identifying the first LTM candidate configuration. In yet other implementations, the MN 104B assigns an 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 an LTM ID configuration procedure, similar to the procedure 390, 392 or 492.

[0193] 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 LTM configuration delivery procedure 694 with the UE 102 to transmit the LTM ID and the LTM candidate configuration to the UE 102. In some implementations, the S-SN 104A 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 with reference to 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 that 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 resourceconfiguration, 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 an RRC reconfiguration complete message to the CU 172 via the S-DU 174A.

[0194] 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., an 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 104A excludes or does not include, in the first RRC reconfiguration message, the complete configuration indication (e.g., an RRC field / IE) to indicate that the LTM candidate configuration 1 is a delta configuration.

[0195] 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 or the 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 an 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 an 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 transmits 656 a DU-CU TA Information Transfer message including the TA value tothe 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, an 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.

[0196] 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 104A in accordance with the address.

[0197] In response to determining to command the UE 102 to perform an 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 626A 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 632 the first cell. When detecting the UE 102 in the event 632, the DU 174 transmits 634 an Access Success message to the CU 172. The UE 102 transmits 636A an RRC reconfiguration complete message to DU 174 during or after the access 632. 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.

[0198] In some implementations, the UE 102 may perform an RA procedure to access the first cell in the event 632. The RA procedure can be a four-step RA procedure or a two-step RA procedure. The RA procedure can be a CBRA procedure or a CFRA procedure. In some implementations, the S-SN 104A includes a first set of LTM CFRA configuration parameters in the ETM Cell Switch Command to configure the UE 102 to perform a CFRA procedure to access the first cell. The UE 102 performs the CFRA procedure using the first set of ETM CFRA configuration parameters. In some implementations, the DU 174 includes the first set of the ETM CFRA configuration parameters in the first DU-to-CU message of the procedure 690 as described for the procedure 490. The CU 172 in turn includes the first set of the ETM CFRA configuration parameters in the SN Request Acknowledge message. In some implementations, the DU 174 includes at least one additional set of ETM CFRA configuration parameters in the first DU-to-CU message as described for the procedure 490. The CU 172 in turn includes the additional set(s) of the ETM CFRA configuration parameters in the SN Request Acknowledge message.

[0199] In some implementations, the DU 174 configures the first set and / or the additional set(s) for UE (i.e., NUE) or SUL and indicates such configurations in the first DU-to-CU message, as described for the C-DU 174B in Fig. 4. In cases where the first set and / or the additional set(s) are configured for one of UL and SUL, the CU 172 includes, in the SN Request Acknowledge message, a single UL / SUL indicator indicating the first set and / or the additional set(s) are configured for the one of UL and SUL. In cases where the first set and / or the additional set(s) are configured for UL, the CU 172 includes the first set and / or the additional set(s) in a first field / IE in the SN Request Acknowledge message. In cases where the first set and / or the additional set(s) are configured for SUL, the CU 172 includes the first set and / or the additional set(s) in a second field / IE in the SN Request Acknowledge message. In such cases, the first field / IE and the second field / IE are defined for UL and SUL, respectively.

[0200] In some implementations, the DU 174 configures the first set for one of UL and SUL and configures the additional set for the other of UL and SUL and indicates such configurations in the first DU-to-CU message, as described regarding the C-DU 174B with reference to Fig. 4. In such cases, the CU 172 sets a UL / SUL indicator in the first set to a value indicating the one of UL and SUL and sets a UL / SUL indicator in the additional set to a value indicating the other of the UL and SUL. Alternatively, the CU 172 includes the first setand the additional set in one and the other of the first field / IE and the second field IE respectively in the SN Request Acknowledge message.

[0201] After receiving 634 the Access Success message or receiving 638 the DU-to-CU message or receiving 636A 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 106 A 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 636A to 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.

[0202] 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).

[0203] 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-DU of the S-SN 104A transmits a DU-CU Cell Switch Notification message to the CU of the S-SN 104A to indicate that the UE 102 performs an 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 Switch Notification message to the MN 104B to indicate that the UE 102 performs or is performing an LTM cell switch to the first cell. In response, the MN 104B transmits 629 a CU-CU Cell Switch Notification message to the CU 172 to indicate that the UE 102 performs or is performing an LTM cell switch to the first cell. In response, the CU 172 transmits 630 aCU-DU Cell Switch Notification message to the DU 174 to indicate that the UE 102 performs or is performing an 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 629. 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 TCI 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. In other implementations, in case that separate TCI states are used, the DL TCI State and the UL TCI state use different TCI State IDs. In such cases, the S-DU of the S- SN 104A includes, in the DU-CU Cell Switch Notification message and / or the LTM Cell Switch Command, a first TCI State ID for DL and a second TCI State ID for UL that identify a first one and a second one of the TCI state configuration(s). The CU of the S-SN 104A, in response to the DU-CU Cell Switch Notification message, in turn includes the first TCI State ID and the second TCI state ID in the CU-CU Cell Switch Notification message to the MN 104B. The MN 104B includes the first TCI state ID and the second TCI state ID in the CU- CU Cell Switch Notification message to the CU 172. The CU 172 then includes the first TCI state ID and the second TCI state ID in the CU-DU Cell Switch Notification message to the DU 174. The UE 102 identifies the first TCI state configuration and / or the second TCI state configuration based on the first TCI state ID and the second TCI state ID, respectively. The UE 102 applies the first TCI state configuration and the second TCI state configuration to communicate DL transmissions and UL transmissions, respectively, with the DU 174 in the events 632, 636A, and / or 640. The DU 174 identifies the first TCI state configuration and the second TCI state configuration based on the first TCI state ID and the second TCI state ID, respectively. The DU 174 applies the first and / or the second TCI state configuration to communicate DL transmissions and / or UL transmissions, respectively, with the UE 102 in the events 632, 636A, and / or 640.

[0204] 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 104A 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 104A communicate 602 data with each other. The MN 104B transmits one or more Early Status Transfer messages to CU 172, each including theDL 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.

[0205] 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 an 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 an 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 an SN message (as shown with event 645 in Eig. 6C) to the S-SN 104A. 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 104A to release a UE context 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 an SN Modification Request message, an SN Release Request message, an SN Access Success message, or the like.

[0206] 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 an 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 625 an SN Status Transfer message to the CU 172, including the DL COUNT value and / or the UL COUNT value.

[0207] 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 104A may obtain CSI resource configuration 2, ..., N for the cell(s) 2, ..., N, respectively, as described for the CSI resource configuration 1. 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 104A 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 LTM configuration 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(s) 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.

[0208] In some implementations, an SN Required message and an SN Confirm message in each of the inter-SN LTM preparation procedure(s) 2, ..., N are an SN Modification Required message and an SN Modification Confirm message, respectively. In other implementations, an SN Required message and an SN Confirm message in each of the inter-SN LTM preparation procedure(s) 2, ..., N are an SN Change Required message and an SN Change Confirm message, respectively. In some implementations, an SN Request message and an SN Request Acknowledge message in each of the inter-SN LTM preparation procedure(s) 2, ...,N are an SN Addition Request message and an 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 an SN Modification Request message and an 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 with reference to the scenario 600B).

[0209] 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 earlier herein. 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 as requested in the SN Request message. The CU 172 performs LTM preparation procedure(s) 2, ..., M with the DU 174 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 106 A 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 described 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 RequestAcknowledge message, as described for the LTM ID 1 and the LTM candidate configuration 1.

[0210] 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. When 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.

[0211] 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. When 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. When the CU 172 obtains the PCI(s) 2, ..., M, the CU 172 includes the PCI(s) 2, ..., M in the SN Request Acknowledge message.

[0212] 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 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.

[0213] 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 SNRequest 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.

[0214] In some implementations, the S-SN 104A may perform LTM configuration delivery procedure(s) 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 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-SN 104A includes the tuples in the first RRC reconfiguration message.

[0215] In 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.

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

[0217] Referring next to Eig. 6B, a scenario 600B is generally similar to the scenario 600A, except that the scenario 600B includes events 604B, 609B and 611 instead of events603 and 609A. In the scenario 600B, the MN 104B initiates inter-SN LTM preparation procedure 698B, while in the scenario 600A, the S-SN 104A initiates inter-SN LTM preparation procedure 698A. 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 SRB1, 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).

[0218] 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 an LTM candidate for the UE 102. In response to the determination, the MN 104B generates an 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 106A. In response to the SN Request message, the CU 172 determines to perform the LTM preparation procedure 690 with the DU 174 and transmits 607 the SN Request Acknowledge message to the MN 104B, as described with reference to Fig. 6A. After (e.g., in response to) receiving the message 607, the MN 104B transmits 609B an SN Modification Request message to the S-SN 104A, including a first LTM candidate configuration (e.g., LTM candidate configuration 1), an 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 an 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 an 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.

[0219] As described with reference to 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 with reference to Fig. 6A. If the SN Modification Request message includes the TCI state configuration(s), the S-SN 104A may include a first TCI state ID in the LTM Cell Switch Command as described with reference to Fig. 6A.

[0220] 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.

[0221] 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 described with reference to the cell ID 1 above.

[0222] Referring next to Eig. 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 an LTM candidate cell in one or more RRC reconfiguration messages in the LTM configuration delivery procedure 694C similar to the procedure 394, 494, or 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 694A. Insome 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.

[0223] When the UE 102 performs 699 the LTM execution procedure, the UE 102 transmit 636C an 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 with reference to 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.

[0224] 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, 627D instead of events 624A, 650A, 654A, 626A, and 627A. The events 624D, 650D, 654D, and 626D are similar to the events 624A, 650A, 654A, and 626A, 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, 654A, and 626A. The event 627D is different from the 627A that in the event 627D, the MN 104B may transmit the CU-CU Cell Switch Notification message which may include the first TCI State ID and / or the second TCI State ID to the S-SN 104A.

[0225] 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 MN 104B is preconfigured with CSI resource configuration. In other implementations, the MN 104B receives the CSI resource configuration from an 0AM node. In yet other implementations, the MN 104B receives the CSI resource configuration from the CU 172 or the S-SN 104A.

[0226] Next, with reference to Figs. 7A-10D, several example methods, which can be implemented in a RAN node (e.g., the CU 172 (Figs. 3-6D), DU 174 (Figs. 3 and 5-6D) and configurations thereof (e.g., C-DU 174B, S-DU 174A (Fig. 4 for intra-CU / inter-DU LTM))(are discussed. Generally speaking, similar events in Figs. 3-6D are labeled withsimilar reference numbers in Figs. 7A-10D, with numbers sharing two least significant digits corresponding to similar operations, with differences discussed below where appropriate. For example, operation 708 can be similar to operation 308, and operation 734 can be similar to operations 334, 434, and 534, and individual descriptions are therefore omitted.

[0227] Fig. 7A illustrates an example method 700A, which can be implemented by a DU. The method 700A begins at block 708, with the DU receiving a CU-to-DU message from a CU, requesting to prepare a first cell as an LTM candidate cell for the UE. At block 710A, the DU transmits a DU-to-CU message to the CU, including a first set of LTM CFRA configuration parameters, where the first set of LTM CERA configuration parameters are configured for the UE to access an LTM candidate cell for the UE. At block 760A, the DU attempts to detect access on the first cell in accordance with the first set of LTM CFRA configuration parameters. At block 732A, the DU may detect that the UE accessed the first cell in accordance with the first set of LTM CFRA configuration parameters. At block 734, the DU may transmit an Access Success message to the CU, notifying that the UE successfully accessed the first cell in an LTM cell switch. At block 740, the DU may communicate with the UE via the first cell.

[0228] In some implementations, the DU is an S-DU or a C-DU. The description for the S- DU or the C-DU above or below can apply to the DU in the method 700A. When the description for the S-DU applies to the DU in the method 700A, the description for the C-DU may apply to the DU in some implementations, while the description for the C-Du may not apply to the DU in other implementations. When the description for the C-DU applies to the DU in the method 700A, the description for the S-DU may apply to the DU in some implementations while the description for the S-DU may not apply to the DU in other implementations .

[0229] In such implementations, the S-DU receives one or more measurement reports (e.g., CSI reports) from the UE (e.g., events, 354, 454, 554, 654A, or 654D). The S-DU determines to transmit the LTM cell switch command, based on the measurement report(s). In some implementations, the measurement report(s) include one or more measurement results for one or more SSBs. The UE performs measurements on the SSB(s) and obtain the measurement result(s) from the measurements. In some implementations, the S-DU determines to configure CFRA in the LTM cell switch, based on the measurement report(s). The S-DU includes thefirst set of LTM CFRA configuration parameters in an LTM cell switch command and transmits the LTM cell switch command to the UE (e.g., event 326).

[0230] In some implementations, the DU (e.g., the S-DU or the C-DU) attempts to detect access on the first cell after (e.g., in response to) transmitting the first set of LTM CFRA configuration parameters. In the case of the C-DU, the C-DU receives a CU-DU Cell Switch Notification message from the CU, notifying that an LTM cell switch to the first cell is triggered (e.g., event 430, 530, 630). In some implementations, the C-DU attempts to detect access on the first cell before receiving the CU-DU Cell Switch Notification message. In other implementations, the C-DU attempts to detect access on the first cell after (e.g., in response to) receiving the CU-DU Cell Switch Notification message.

[0231] In some implementations, the first set of LTM CFRA configuration parameters include a first RA preamble index, a first SSB index, a first PRACH Mask index, and / or a first UL / SUL indicator. In some implementations, the DU receives the first set of LTM CFRA configuration parameters from an 0AM node.

[0232] In some implementations, the DU includes at least one additional set of LTM CFRA configuration parameters for the UE in the DU-to-CU message. In some implementations, the DU receives the addition set(s) of LTM CFRA configuration parameters from the 0AM node. For example, each of the additional set(s) includes an RA preamble index, an SSB index, a PRACH mask, and / or a UL / SUL indicator. In some implementations, the first set and / or the addition set(s) are configured by the DU only for the first cell (i.e., LTM candidate cell) and the UE. In other implementations, the first set and / or the addition set(s) are configured by the C-SN only for the UE and any LTM candidate cell (i.e., the first cell and the other LTM candidate cell(s)). In yet other implementations, the first set and the addition set(s) are configured by the C-SN only for the UE and the first cell and the other LTM candidate cell(s) respectively.

[0233] The first set and the additional set(s) of LTM CFRA configuration parameters include different values. In some implementations, the first SSB index (value) in the first set of LTM CFRA configuration parameters is different from the SSB index(es) (value(s)) in the additional set(s) of LTM CFRA configuration parameters. In some implementations, an SSB index (value) in one of the additional set(s) of LTM CFRA configuration parameters is different from an SSB index (value) in another one of the additional set(s) of LTM CFRA configuration parameters. In some implementations, the first RA preamble index (value) inthe first set of LTM CFRA configuration parameters is different from the RA preamble index(es) (value(s)) in the additional set(s) of LTM CFRA configuration parameters. In some implementations, an RA preamble index (value) in one of the additional set(s) of LTM CFRA configuration parameters is different from an RA preamble index (value) in another one of the additional set(s) of LTM CFRA configuration parameters. In some implementations, the first PRACH Mask index (value) in the first set of LTM CFRA configuration parameters is different from the PRACH Mask index(es) (value(s)) in the additional set(s) of LTM CFRA configuration parameters. In some implementations, a PRACH Mask index (value) in one of the additional set(s) of LTM CFRA configuration parameters is different from a PRACH Mask index (value) in another one of the additional set(s) of LTM CFRA configuration parameters. In some implementations, the first UL / SUL indicator (value) in the first set of LTM CFRA configuration parameters is different from the UL / SUL indicator(s) (value(s)) in the additional set(s) of LTM CFRA configuration parameters. In other implementations, the first UL / SUL indicator (value) in the first set of LTM CFRA configuration parameters is the same as the UL / SUL indicator(s) (value(s)) in the additional set(s) of LTM CFRA configuration parameters. In some implementations, a UL / SUL indicator (value) in one of the additional set(s) of LTM CFRA configuration parameters is different from a UL / SUL indicator (value) in another one of the additional set(s) of LTM CFRA configuration parameters. In other implementations, a UL / SUL indicator (value) in one of the additional set(s) of LTM CFRA configuration parameters is the same as a UL / SUL indicator (value) in another one of the additional set(s) of LTM CFRA configuration parameters.

[0234] In some implementations, the S-DU determines (whether) to include the first set of LTM CFRA configuration parameters in the LTM cell switch command, based on the measurement report(s). In some implementations, the S-DU obtains (e.g., retrieves, derives, calculates, or determines) one or more measurement results from the measurement report(s). In some implementations, the measurement result(s) include a measurement result for a first SSB identified by the first SSB index. The first SSB is transmitted by the C-DU on the first cell. In some implementations, if the measurement result for the first SSB is above (or equal to) a predetermined threshold, the S-DU includes the first set of LTM CFRA configuration parameters in the LTM cell switch command. Otherwise, if the measurement result for the first SSB is less than or equal to a predetermined threshold, the S-DU refrains from including the first set of LTM CFRA configuration parameters in the LTM cell switch command. In other implementations, the measurement result(s) include a measurement result for a secondSSB identified by a second SSB index and does not include a measurement result for the first SSB. The second SSB is transmitted by the C-DU on the first cell. In one implementation, the S-DU does not receive LTM CFRA configuration parameters including the second SSB index for the UE and the first cell. In another implementation, the measurement result for the second SSB is below (or equal to) the predetermined threshold. In such cases, the S-DU refrains from including (the first set of) LTM CFRA configuration parameters in the LTM cell switch command.

[0235] In some implementations, the DU includes the first set in of LTM CFRA configuration parameters a specific field / IE in the DU-to-CU message. If the specific field / IE (i.e., a first specific field / IE) is defined for or indicates UL, the S-DU sets the UL / SUL indicator in the LTM cell switch command to a first value indicating indicate UL (i.e., normal UL (NUL)). Otherwise, if the specific field / IE (i.e., a second specific field / IE) is defined for or indicates SUL, the S-DU sets the UL / SUL indicator in the LTM cell switch command to a second value indicating SUL.

[0236] In some implementations, the DU indicates the first set of LTM CFRA configuration parameters for one of UL and SUL and indicates the additional set of LTM CFRA configuration parameters for the other of UL and SUL in the DU-to-CU message. In some implementations, the C-DU sets the UL / SUL indicator in the first set of LTM CFRA configuration parameters to a value indicating the one of UL and SUL and sets the UL / SUL indicator in the additional set of LTM CFRA configuration parameters to a value indicating the other of UL and SUL.

[0237] In other implementations, the DU includes the first set of LTM CFRA configuration parameters in a first specific field / IE for the one of UL and SUL and includes the additional set of LTM CFRA configuration parameters in a second specific field / IE for the other of UL and SUL in the DU-to-CU message. In such cases, the first set of LTM CFRA configuration parameters and the additional set of LTM CFRA configuration parameters may not include a / the UL / SUL indicator. In some implementations, the S-DU determines a value of a UL / SUL indicator in the LTM cell switch command based on a measurement result for the first SSB (index) that the S-DU obtains (e.g., identifies or determines) from the measurement report(s). In one implementation, if the measurement result is above (or equal to) a predetermined threshold, the S-DU sets the UL / SUL indicator to the first value and includes the first set of LTM CFRA configuration parameters in theLTM cell switch command. Otherwise, if the measurement result is below (or equal to) the predetermined threshold, the S-DU sets the UL / SUL indicator to the second value and includes the additional set of LTM CFRA configuration parameters in the LTM cell switch command instead of the first set of LTM CFRA configuration parameters.

[0238] In other implementations, the DU indicates the first set of LTM CFRA configuration parameters and / or the additional set of LTM CFRA configuration parameters for either UL or SUL in the DU-to-CU message. In some implementations, the DU includes the first set of LTM CFRA configuration parameters and / or the additional set of LTM CFRA configuration parameters in a specific IE defined either for UL or SUL in the DU-to-CU message. In other implementations, the DU includes, in the DU-to-CU message, a single UL / SUL indicator indicating the first set of LTM CFRA configuration parameters and the additional set of LTM CFRA configuration parameters for either UL or SUL.

[0239] In some implementations, the first set of LTM CFRA configuration parameters includes the first RA preamble index and may not include an SSB index, a PRACH Mask index and a UL / SUL indicator. In some implementations, the S-DU determines an SSB index, a PRACH Mask index and / or a UL / SUL indicator and includes the first RA preamble, the SSB index, the PRACH Mask index and the UL / SUL indicator in the LTM cell switch command. In one implementation, the S-DU determines the SSB index based on the measurement report(s) as described above. The SSB index indicates an SSB transmitted on the first cell. In some implementations, the measurement result(s) are associated with an SSB identified by an SSB index. In some implementations, the measurement result(s) for the SSB is above or equal to a predetermined threshold. In some implementations, the S-DU determines the PRACH Mask index based on a first RACH configuration. In some implementations, the CU-to-DU message may include the first RACH configuration (e.g., a generic RACH configuration such as a RACH-ConfigGeneric IE), e.g., in a specific field / IE. In some implementations, the specific field / IE is a first specific field / IE indicating the first RACH configuration for UL. In other implementations, the specific field / IE is a second specific field / IE indicating the first RACH configuration for SUL. In such cases, the CU may include a UL / SUL indicator in the CU-to-DU message, indicating the first RACH configuration for either UL or SUL. In other implementations, the S-DU receives the first RACH configuration from the 0AM node. In some implementations, the first RACH configuration is configured for CFRA only, CBRA or both CFRA and CBRA. In some implementations, S-DU sets or is preconfigured to set the UL / SUL indicator to a first valueindicating indicate UL (i.e., NUL). In other implementations, the S-DU sets or is preconfigured to set the UL / SUL indicator to a second value indicating SUL. In yet other implementations, the S-DU sets the UL / SUL indicator to the first value or the second value, based on the first RACH configuration. For example, if the first RACH configuration is associated with UL (i.e., NUL), the S-DU sets the UL / SUL indicator to the first value. If the first RACH configuration is associated with SUL, the S-DU sets the UL / SUL indicator to the second value. The CU may indicate the first RACH configuration for UL or SUL in the CU- to-DU message. In yet other implementations, the S-DU determines the UL / SUL indicator based on measurement result(s) in the measurement report(s). In one implementation, if the measurement result(s) is above (or equal to) a predetermined threshold, the S-DU sets the UL / SUL indicator to the first value. Otherwise, if the measurement result(s) is below (or equal to) the predetermined threshold, the S-DU sets the UL / SUL indicator to the second value.

[0240] In some implementations, the DU may receive a second CU-to-DU message from the CU, requesting to prepare a second cell of the C-SN as an LTM candidate cell for the UE. In response, the DU transmits a second DU-to-CU message to the CU, including a second LTM candidate configuration and / or a second set of LTM CFRA configuration parameters for the second cell, as described above. In some implementations, the second set of LTM CFRA configuration parameters include second RA preamble index, second SSB index, second PRACH Mask index, and / or second UL / SUL indicator. Description for the first set can apply to the second set by replacing “first” with “second.” In some implementations, the first set and the second set are the same. In other implementations, the first set and the second set are different. In some alternative implementations, when preparing the second cell as an LTM candidate cell for the UE, the DU does not include the second set of LTM CFRA configuration parameters for the UE in the second DU-to-CU message. In such cases, if the S-DU determines to command the UE to perform an LTM cell switch to the second cell, the S-DU transmits an LTM cell switch command to the UE, indicating the UE to perform an LTM cell switch to the second cell. In some implementations, the S-DU includes the first set of LTM CFRA configuration parameters in the LTM cell switch command. In such cases, the first set of LTM CFRA configuration parameters may be configured for the UE to access any LTM candidate cell operated by the C-DU. Descriptions above for the first cell can be applied to the second cell by replacing the phrase “first cell” with the phrase “second cell”. In other implementations, the S-DU refrains from including the first set of LTM CFRAconfiguration parameters in the LTM cell switch command. In such cases, the first set of LTM CFRA configuration parameters may be configured for the UE to access only the first cell.

[0241] Fig. 7B is a flow diagram of an example method 700B similar to the method 700A, except that the method 700B includes blocks 710B, 760B and 732B instead of blocks 710A, 760A and 732A. At block 710B, the DU transmits a DU-to-CU message to the CU, including a first dedicated RACH configuration, where the first dedicated RACH configuration is configured for the UE to access an LTM candidate cell for the UE. At block 760B, the DU attempts to detect access on the first cell in accordance with the first dedicated RACH configuration. At block 732B, the DU may detect that the UE accesses the first cell in accordance with the first dedicated RACH configuration.

[0242] Example and implementations described with reference to Fig. 7A can apply to Fig. 7B.

[0243] In some implementations, the first dedicated RACH configuration includes one or more sets of LTM CFRA configuration parameters {RA preamble index, SSB index, PRACH mask, and / or UL / SUL indicator] s (e.g., the first set, the additional set(s) and / or the second set described with reference to Fig. 7A). In some implementations, the first dedicated RACH configuration is a RACH-ConfigDedicated IE defined in 3GPP specification 38.331.

[0244] In some implementations, the DU indicates the first dedicated RACH configuration is for either UL or SUL in the DU-to-CU message. The DU implicitly or explicitly indicates the first dedicated RACH configuration for UL or SUL in the DU-to-CU message. In some implementations, if the DU generates the first dedicated RACH configuration configured for UL (i.e., NUL), the DU includes the first dedicated RACH configuration in a first field / UE in the DU-to-CU message. Otherwise, if the DU generates the first dedicated RACH configuration configured for SUL, the DU includes the first dedicated RACH configuration in a second field / UE in the DU-to-CU message. In such cases, the first field / IE and the second field / IE are defined for UL and SUL, respectively.

[0245] In other implementations, the DU includes the first dedicated RACH configuration in the DU-to-CU message. In one implementation, if the DU generates the first dedicated RACH configuration for UL, the DU sets a UL / SUL indicator to a first value and includes the UL / SUL indicator in the DU-to-CU message. Otherwise, if the DU generates the first dedicated RACH configuration configured for SUL, the DU sets the UL / SUL indicator to asecond value and includes the UL / SUL indicator in the DU-to-CU message. The UL / SUL indicator set to the first value indicates that the first dedicated RACH configuration for UL. The UL / SUL indicator set to the second value indicates that the first dedicated RACH configuration for SUL. In another implementation, if the DU generates the first dedicated RACH configuration for UL, the DU includes a UL indicator in the DU-to-CU message. Alternatively, the DU indicates the first dedicated RACH configuration for UL by excluding the SUL indicator in the DU-to-CU message. Otherwise, if the DU generates the first dedicated RACH configuration configured for SUL, the DU includes a SUL indicator in the DU-to-CU message. Alternatively, the DU indicates the first dedicated RACH configuration for SUL by excluding the SUL indicator in the DU-to-CU message. The UL indicator indicates that the first dedicated RACH configuration for UL. The SUL indicator indicates that the first dedicated RACH configuration for SUL.

[0246] In some implementations, if the first dedicated RACH configuration is indicated or configured for UL, the S-DU may set the UL / SUL indicator in the LTM cell switch command to the first value. Otherwise, if the first dedicated RACH configuration is indicated or configured for SUL, the S-DU may set the UL / SUL indicator in the LTM cell switch command to the second value.

[0247] The UE described above is a first UE. In some implementations, the DU may configure a second dedicated RACH configuration for a second UE when preparing the first cell as an LTM candidate cell for the second UE, similar to the above description of preparing the first cell as an LTM candidate cell for the first UE. The second dedicated RACH configuration is different from the first dedicated RACH configuration.

[0248] Fig. 7C is a flow diagram of an example method 700C similar to the method 700A, except that the method 700C includes blocks 774C, 760C-1 and 760C-2 instead of block 760A. At block 774C, the DU determines whether the first set of LTM CFRA configuration parameters are configured for UL or SUL. If the first set of LTM CFRA configuration parameters are configured for UL (i.e., “UL” branch of block 774C), the flow proceeds to block 760C-1. At block 760C-1, the DU attempts to detect access on UL of the first cell in accordance with the first set of LTM CFRA configuration parameters. Otherwise, if the first set of LTM CFRA configuration parameters are configured for SUL (i.e., “SUL” branch of block 774C), the flow proceeds to block 760C-2. At block 760C-2, the DU attempts to detectaccess on SUL of the first cell in accordance with the first set of LTM CFRA configuration parameters. The flow proceeds to block 732A from block 760C-1 as well as block 760C-2.

[0249] Fig. 7D is a flow diagram of an example method 700D similar to the method 700B, except that the method 700D includes blocks 774D, 760D-1 and 760D-2 instead of block 760B. At block 774D, the DU determines whether the first dedicated RACH configuration is configured for UL or SUL. If the first dedicated RACH configuration is configured for UL (i.e., “UL” branch of block 774D), the flow proceeds to block 760D-1. At block 760D-1, the DU attempts to detect access on UL of the first cell in accordance with the first dedicated RACH configuration. Otherwise, if the first dedicated RACH configuration is configured for SUL (i.e., “SUL” branch of block 774D), the flow proceeds to block 760D-2. At block 760C- 2, the DU attempts to detect access on SUL of the first cell in accordance with the first dedicated RACH configuration. The flow proceeds to block 732B from block 760D-1 as well as block 760D-2.

[0250] Fig. 7E is a flow diagram of an example method 700E similar to the method 700A, except that the method 700E includes blocks 710E and 760E instead of blocks 710A and 760A. At block 710E, the DU transmits a DU-to-CU message to the CU, including a first set of LTM CFRA configuration parameters and an additional set of LTM CFRA configuration parameters, where the first set and the additional set are configured for the UE to access LTM candidate cell(s) for the UE. At block 760E, the DU attempts to detect access on the first cell in accordance with the first set of LTM CFRA configuration parameters and the additional set of LTM CFRA configuration parameters.

[0251] Example and implementations described with reference to Fig. 7A can apply to Figs. 7C-7E.

[0252] In some implementations, the DU includes the first set and the additional set in a dedicated RACH configuration and includes the dedicated RACH configuration in the DU- to-CU message. In other implementations, the DU includes the first set and the additional set in a first dedicated RACH configuration for one of UL and SUL and a second dedicated RACH configuration for the other of UL and SUL, respectively, and includes the first dedicated RACH configuration and the second dedicated RACH configuration in the DU-to- CU message.

[0253] Fig. 8A illustrates an example method 800A, which can be implemented by a C- DU. The method 800A begins at block 808, where the C-DU receives a CU-to-DU message,requesting to prepare a first cell as an LTM candidate cell for a UE. At block 868A, the C- DU determines to configure or configures at least one set of LTM CFRA configuration parameters for the UE. At bock 874A, the DU determines whether the set(s) of LTM CFRA configuration parameters are configured for UL or SUL. If the set(s) of the LTM CFRA configuration parameters are configured for UL (i.e., “UL” branch of block 874A), the flow proceeds to block 878 A. At block 878 A, the DU includes the set(s) of LTM CFRA configuration parameters in a first field / IE in a DU-to-CU message. Otherwise, if the set(s) of the LTM CFRA configuration parameters are configured for SUL (i.e., “SUL” branch of block 874A), the flow proceeds to block 879A. At block 879A, the DU includes the set(s) of LTM CFRA configuration parameters in a second field / IE in the DU-to-CU message. The flow proceeds to block 810 from block 878A as well as block 879A. At block 810, the DU transmits the DU-to-CU message to the CU.

[0254] Descriptions with reference to Fig. 7A can apply to Fig. 8A.

[0255] Fig. 8B is a flow diagram of an example method 800B similar to the method 800A, except that the method 800B includes blocks 868B, 874B, 878B, and 879B instead of blocks 868A, 874A, 878A, and 879A. At block 868B, the C-DU determines to configure or configures a dedicated RACH configuration for LTM and the UE. At block 874B, the DU determines whether the dedicated RACH configuration is configured for UL or SUL. If the dedicated RACH configuration is configured for UL (i.e., “UL” branch of block 874B), the flow proceeds to block 878B. At block 878B, the DU includes the dedicated RACH configuration in a first field / IE in a DU-to-CU message. Otherwise, if the dedicated RACH configuration is configured for SUL (i.e., “SUL” branch of block 874B), the flow proceeds to block 879B. At block 879B, the DU includes the dedicated RACH configuration in a second field / IE in the DU-to-CU message. The flow proceeds to block 810 from block 878B as well as block 879B.

[0256] Fig. 8C is a flow diagram of an example method 800C similar to the method 800A, except that the method 800C includes blocks 878C, 813, and 883 instead of blocks 878A and 879A. At block 878C, the DU includes the set(s) of LTM CFRA configuration parameters in a DU-to-CU message. The flow proceeds to block 874A. If a cell or node has configured the set(s) of the LTM CFRA configuration parameters for UL (i.e., “UL” branch of block 874A), the flow proceeds to block 813. At block 813, the DU sets a UL / SUL indicator to a first value and includes the UL / SUL indicator in the DU-to-CU message. Otherwise, if the set(s) of theLTM CFRA configuration parameters are configured for SUL (i.e., “SUL” branch of block 874A), the flow proceeds to block 883. At block 883, the DU sets a UL / SUL indicator to a second value and includes the UL / SUL indicator in the DU-to-CU message. The flow proceeds to block 810 from block 813 as well as block 883.

[0257] In some alternative implementations for block 813, the DU includes a UL indicator in the DU-to-CU message instead of the UL / SUL indicator. In some alternative implementations for block 883, the DU includes a SUL indicator in the DU-to-CU message instead of the UL / SUL indicator. In other alternative implementations, the DU excludes the SUL indicator in the DU-to-CU message to indicate that the set(s) of LTM CFRA configuration parameters are configured for UL. In other alternative implementations, the DU excludes the UL indicator in the DU-to-CU message to indicate that the set(s) of LTM CFRA configuration parameters are configured for SUL.

[0258] Fig. 8D is a flow diagram of an example method 800D similar to the methods 800B and 800C, except that the method 800D includes block 878D instead of block 878C. At block 878D, the DU includes the dedicated RACH configuration in a DU-to-CU message. The flow proceeds to block 874B. If a cell or node has configured the dedicated RACH configuration for UL (i.e., “UL” branch of block 874B), the flow proceeds to block 813. Otherwise, if the dedicated RACH configuration is configured for SUL (i.e., “SUL” branch of block 874B), the flow proceeds to block 883.

[0259] Descriptions with reference to Figs. 7A and 7B can apply to Figs. 8B-8D.

[0260] Fig. 9A illustrates an example method 900A, which can be implemented by an S-DU. The method 900A begins at block 912A, where the DU receives a CU-to-DU message from a CU, including a first set of LTM CFRA configuration parameters and an additional set of LTM CFRA configuration parameters, where the first set and the additional set are configured for a UE to access LTM candidate cell(s). At block 954, the S-DU receives one or more measurement reports from the UE. At block 915, the S-DU determines to command the UE to perform an LTM cell switch to a first cell (i.e., an LTM candidate cell), e.g., based on the measurement report(s). At block 963A, the S-DU selects the first set of LTM CFRA configuration parameters based on the measurement report(s), in response to the determination. At block 964, the S-DU includes the first set of LTM CFRA configuration parameters in an LTM Cell Switch Command for the LTM cell switch. At block 926, the S- DU transmits the LTM Cell Switch Command to the UE.

[0261] Fig. 9B is a flow diagram of an example method 900B similar to the method 900A, except that the method 900B includes blocks 962, 965 instead of block 963 A. At block 962, the S-DU determines whether to configure the UE to use the first set of LTM CFRA configuration parameters or the additional set of LTM CFRA configuration parameters to perform a CFRA procedure on the first cell. If the S-DU determines to configure the UE to use the first set of LTM CFRA configuration parameters to perform a CFRA procedure on the first cell (i.e., “First set” branch of block 962), the flow proceeds to block 964. At block964, the S-DU includes the first set of LTM CFRA configuration parameters in an LTM cell switch command. Otherwise, if the S-DU determines to configure the UE to use the additional set of LTM CFRA configuration parameters to perform a CFRA procedure on the first cell (i.e., “Additional set” branch of block 962), the flow proceeds to block 965. At block965, the S-DU includes the additional set of LTM CFRA configuration parameters in the LTM cell switch command. The flow proceeds to block 926 from block 964 as well as block 965. At block 926, the S-DU transmits the LTM Cell Switch Command to the UE.

[0262] Fig. 9C is a flow diagram of an example method 900C similar to the methods 900A and 900B, except that the method 900C includes blocks 912C, 970C and 966 instead of blocks 912A, 962 and 966. At block 912C, the S-DU receives a CU-to-DU message from a CU, including a first set of LTM CFRA configuration parameters, where the first set of LTM CFRA configuration parameters are configured for a UE to access LTM candidate cell(s). At block 970C, the S-DU determines whether UE qualifies for using the first set of LTM CFRA configuration parameters for the LTM cell switch. If the UE qualifies for using the first set of LTM CFRA configuration parameters for the LTM cell switch (i.e., “Yes” branch of block 970C), the flow proceeds to block 964. Otherwise, if the UE does not qualify for using the first set of LTM CFRA configuration parameters (i.e., “No” branch of block 970C), the flow proceeds to block 966. At block 966, the S-DU refrains from including the first set of LTM CFRA configuration parameters in the LTM Cell Switch Command. The flow proceeds to block 926 from block 964 as well as block 966.

[0263] Fig. 9D is a flow diagram of an example method 900D similar to the methods 900A, 900B and 900C, except that the method 900D includes blocks 974D, 976 and 977 instead of blocks 970C, 964, 965 and 966. At block 974D, the S-DU determines whether the first set of LTM CFRA configuration parameters are configured for UL or SUL. If the first set of LTM CFRA configuration parameters are configured for UL (i.e., “UL” branch of block 974D, or normal uplink (NUL)), the flow proceeds to block 976. At block 976, the S-DU sets a UL / SUL indicator in the LTM cell switch command to a first value. Otherwise, if the first set of LTM CFRA configuration parameters are configured for SUL (i.e., “SUL” branch of block 974C), the flow proceeds to block 977. At block 977, the S-DU sets a UL / SUL indicator in the LTM Cell Switch Command to a second value. The flow proceeds to block 926 from block 976 as well as block 977.

[0264] Fig. 9E is a flow diagram of an example method 900E similar to the methods 900A- 900D, except that the method 900E includes blocks 974E instead of blocks 974C. At block 974E, the S-DU determines whether the first set of LTM CFRA configuration parameters are included in a first field / IE or a second field / IE in the CU-to-DU message. If the first set of LTM CFRA configuration parameters are included in the first field / IE (i.e., “First field / IE” branch of block 974E), the flow proceeds to block 976. Otherwise, if the first set of LTM CFRA configuration parameters are included in the second field / IE (i.e., “Second field / IE” branch of block 974E), the flow proceeds to block 977.

[0265] Fig. 9F is a flow diagram of an example method 900F similar to the method 900A, except that the method 900F includes blocks 912F and 963F instead of blocks 912A and 963A. At block 912F, the S-DU receives a CU-to-DU message from a CU, including a first dedicated RACH configuration, where the first Dedicated RACH configuration is configured for a UE to access LTM candidate cell(s). At block 963F, the S-DU selects a first set of LTM CFRA configuration parameters from the first dedicated RACH configuration, based on the measurement report(s).

[0266] Fig. 9G is a flow diagram of an example method 900G similar to the methods 900F and 900C, except that the method 900G includes blocks 970G instead of block 970C. At block 970G, the S-DU determines whether UE qualifies for using a first set of LTM CFRA configuration parameters in the first dedicated RACH configuration for the LTM cell switch. If the UE qualifies for using the first set of LTM CFRA configuration parameters for the LTM cell switch (i.e., “Yes” branch of block 970G), the flow proceeds to block 964. Otherwise, if the UE does not qualify for using the first set of LTM CFRA configuration parameters (i.e., “No” branch of block 970G), the flow proceeds to block 966.

[0267] Fig. 9H is a flow diagram of an example method 900H similar to the methods 900F and 900D, except that the method 900H includes block 974H instead of block 974H. At block 974H, the S-DU determines whether the first dedicated RACH configuration is configured for UL or SUL. If the first dedicated RACH configuration is configured for UL (i.e., “UL”branch of block 974H), the flow proceeds to block 966. Otherwise, if the first dedicated RACH configuration is configured for SUL (i.e., “SUL” branch of block 974D), the flow proceeds to block 967.

[0268] Fig. 91 is a flow diagram of an example method 9001 similar to the methods 900F, 900D and 900H, except that the method 9001 includes block 9741 instead of block 974D. At block 9741, the S-DU determines whether the first dedicated RACH configuration is included in a first field / IE or a second field / IE in the CU-to-DU message. If the first dedicated RACH configuration is included in the first field / IE (i.e., “first field / IE” branch of block 9741), the flow proceeds to block 966. Otherwise, if the first dedicated RACH configuration is included in the second field / IE (i.e., “second field / IE” branch of block 9741), the flow proceeds to block 967.

[0269] Descriptions with reference to Figs. 7A and 7B can apply to Figs. 9A-9I.

[0270] Fig. 10A illustrates an example method 1000A, which can be implemented by a CU. The method 1000A begins at block 1010A, where the CU receives a DU-to-CU message from a first DU, including a first set of LTM CFRA configuration parameters, where the first set of LTM CFRA configuration parameters are configured for a UE to access an LTM candidate cell. At block 1074A, the CU determines whether the first set of LTM CFRA configuration parameters are configured for UL or SUL. If the first set of LTM CFRA configuration parameters are configured for UL (i.e., “UL” branch of block 1074A), the flow proceeds to block 1095A. At block 1095A, the CU includes the first set of LTM CFRA configuration parameters in a first field / IE in a CU-to-DU message. Otherwise, if the first set of LTM CFRA configuration parameters are configured for SUL (i.e., “SUL” branch of block 1074C), the flow proceeds to block 1097A. At block 1097A, the CU includes the first set of LTM CFRA configuration parameters in a second field / IE in a CU-to-DU message. The flow proceeds to block 1012 from block 1095A as well as block 1097A.

[0271] In some implementations, if the DU-to-CU message includes the first set of LTM CFRA configuration parameters in a first field / IE, the CU determines the first set of LTM CFRA configuration parameters are configured for UL. Otherwise, if the DU-to-CU message includes the first set of LTM CFRA configuration parameters in a second field / IE, the CU determines the first set of LTM CFRA configuration parameters are configured for SUL.

[0272] Fig. 10B is a flow diagram of an example method 1000B similar to the method 1000A, except that the method 1000B includes blocks 1073B, 1086, 1083 and 1088 insteadof blocks 1095A and 1097A. At block 1073B, the CU includes the first set of LTM CFRA configuration parameters in a CU-to-DU message. If the first set of LTM CFRA configuration parameters are configured for UL (i.e., “UL” branch of block 1074C), the flow proceeds to block 1086. At block 1086, the CU sets a UL / SUL indicator to a first value. Otherwise, if the first set of LTM CFRA configuration parameters are configured for SUL (i.e., “SUL” branch of block 1074C), the flow proceeds to block 1087. At block 1087, the CU includes sets the UL / SUL indicator to a second value. The flow proceeds to block 1088 from block 1086 as well as block 1087. The flow proceeds to block 1012 from block 1088.

[0273] In some alternative implementations, if the first set of LTM CFRA configuration parameters are configured for UL (i.e., “UL” branch of block 1074C), the CU includes a UL indicator in the CU-to-DU message instead of the UL / SUL indicator. The UL indicator indicates that the first set of LTM CFRA configuration parameters are configured for UL. Alternatively, the CU excludes an indicator (e.g., the UL / SUL indicator or the UL indicator) in the CU-to-DU message to indicate that the first set of LTM CFRA configuration parameters are configured for UL. In some alternative implementations, if the first set of LTM CFRA configuration parameters are configured for SUL (i.e., “SUL” branch of block 1074C), the CU includes a SUL indicator in the CU-to-DU message instead of the UL / SUL indicator. The SUL indicator indicates that the first set of LTM CFRA configuration parameters are configured for SUL. Alternatively, the CU excludes an indicator (e.g., the UL / SUL indicator or the SUL indicator) in the CU-to-DU message to indicate that the first set of LTM CFRA configuration parameters are configured for SUL.

[0274] Fig. 10C is a flow diagram of an example method 1000C similar to the method 1000A, except that the method 1000C includes blocks 1010C, 1074D, 1095C and 1097C instead of blocks 1010A, 1074C, 1095A and 1097A. At block 1010C, the CU receives a DU- to-CU message from a first DU, including a first dedicated RACH configuration, where the first dedicated RACH configuration is configured for a UE to access an LTM candidate cell. At block 1074D, the CU determines whether the first dedicated RACH configuration is configured for UL or SUL. If the first dedicated RACH configuration is configured for UL (i.e., “UL” branch of block 1074D), the flow proceeds to block 1095C. At block 1095C, the CU includes the first dedicated RACH configuration in a first field / IE in a CU-to-DU message. Otherwise, if the first dedicated RACH configuration is configured for SUL (i.e., “SUL” branch of block 1074D), the flow proceeds to block 1097C. At block 1097C, the CUincludes the first dedicated RACH configuration in a second field / IE in the Cu-to-DU message. The flow proceeds to block 1012 from block 1095C as well as block 1097C.

[0275] In some implementations, if the DU-to-CU message includes the first dedicated RACH configuration in a first field / IE, the CU determines the first dedicated RACH configuration is configured for UL. Otherwise, if the DU-to-CU message includes the first dedicated RACH configuration in a second field / IE, the CU determines the first dedicated RACH configuration is configured for SUL.

[0276] Fig. 10D is a flow diagram of an example method WOOD similar to the methods 1000C and 1000B, except that the method WOOD includes blocks 1073D instead of block 1073B. At block 1073D, the CU includes the first RACH dedicated configuration in a CU-to- DU message.

[0277] Descriptions with reference to Figs. 7A and 7B can apply to Figs. 10A-10D.

[0278] Fig. 11 is a flow diagram of an example method 1100 that a distributed unit (DU) (e.g., DU 174, S-DU 174A, C-DU 174B, etc.) of a distributed base station can implement for inter-CU LTM.

[0279] The method 1100 begins at block 1108 with the DU receiving a request, from a centralized unit (CU) of the distributed base station, related to lower layer triggered mobility (LTM) for a user equipment (UE) (e.g., event 708 or 808).

[0280] The method 1100 can continue with block 1110 with the DU transmitting, to the CU and in response to the request, random access (RA) configuration parameters for accessing an LTM candidate cell (e.g., event 710A, 710B, 710E, or 810).

[0281] The DU can be a source DU (S-DU). The method 1100 can include receiving, by the S-DU, measurement reports for the LTM candidate cell.

[0282] The measurement reports can be received from the UE. The method 1100 can further include transmitting a Cell Switch Command if the measurement reports indicate the UE should implement a cell switch. The S-DU can determine which set of a plurality of sets of RA configuration parameters to provide in the Cell Switch Command based on the measurement reports. The S-DU can determine which set of a plurality of sets of RA configuration parameters to provide in the Cell Switch Command based on capability information of the UE with respect to each of the plurality of sets of RA configurationparameters or based on the measurement reports (e.g., event 912A, 912C, 912F, 963A, or 963F).

[0283] The measurement reports can be received from an LTM C-DU separate from the S- DU. The measurement reports can include a measurement result for a synchronization signal block (SSB). The S-DU can refrain from providing the RA configuration parameters in the Cell Switch Command if the measurement result for the SSB is below a threshold.

[0284] RA configurations can be received from the CU or another CN node. The CN node can comprise an 0AM node. For example, the method 1100 can comprise receiving a generic RA channel (RACH) configuration from the CU or other CN node. The generic RACH configuration can be included in a message having a field indicating whether the generic RACH configuration is for uplink (UL or normal uplink (NUL)) or supplemental uplink (SUL) communications. The generic RACH configuration can be configured for either or both of CFRA or CBRA.

[0285] The RA configuration parameters can include at least one set of CFRA configuration parameters (e.g., event 868A). The at least one set of CFRA configuration parameters may include either separate or combined NUL and SUL indicators. The method 1100 can include transmitting the at least one set of CFRA configuration parameters in a first field of a DU-to-CU message if the at least one set is configured for NUL and transmitting the at least one set in a second field of the DU-to-CU message otherwise (e.g., event 774C, 774D, 874A, 878A, or 879A). The method 1100 can include setting an indicator having a first value or a second value based on whether the at least one set of CFRA configuration parameters is configured for NUL or SUL (e.g., event 874A, 813 or 883).

[0286] The method 1100 can include transmitting an NUL indicator and an SUL indicator in an LTM Cell Switch Command. The DU can determine a value for the NUL indicator and SUL indicator based on measurement reports. The measurement reports can include a measurement result for SSB transmitted by a C-DU. The DU can refrain from transmitting RA configuration parameters if the measurement results for the SSB are below a threshold. An S-DU can set a value for the NUL indicator and the SUL indicator based on whether the LTM C-DU supports SUL.

[0287] The method 1100 can include detecting access by the UE on the LTM candidate cell, the access being according to the RA configuration parameters (e.g., event 760A, 732A, or 732B). The access can be according to a dedicated RACH configuration (e.g., event 760B,760D-1, 760D-2, or 868B) or a CFRA configuration. If the access is according to a dedicated RACH configuration, the method 1100 can include transmitting the dedicated RACH configuration in a first field of a DU-to-CU message if the dedicated RACH configuration is configured for NUL and transmitting the dedicated RACH configuration in a second field of the DU-to-CU message otherwise (e.g., event 874B, 878B, or 879B). Alternatively, the method 1100 can include setting an indicator having a first value or a second value based on whether the dedicated RACH configuration is configured for NUL or SUL. The method 1100 can include detecting access of the UE on the NUL or SUL depending on configuration of the dedicated RACH (e.g., event 774D).

[0288] When the DU is a C-DU, the method 1100 can include the C-DU transmitting measurement reports for an LTM candidate cell to the CU and / or to the S-DU. The method 1100 can include transmitting at least one set of CFRA parameters include an RA preamble index, an SSB index, a PRACH Mask index, and / or a UL / SUL indicator. The measurement reports can include a measurement result for an SSB. Fig. 12 is a flow diagram of an example method 1100 that a CU of a distributed base station can implement for inter-CU ETM.

[0289] The method 1200 begins at block 1210 with the CU receiving, from a first DU, RA configuration parameters for configuring a UE to access an ETM candidate cell (e.g., event 1010A or 1010C).

[0290] The method 1200 can include transmitting, in block 1212, the RA configuration parameters to a second DU (e.g., event 1012).

[0291] The method 1200 can include receiving CFRA parameters or dedicated RACH parameters. At operation 1274, the CU can determine whether the RA configuration parameters configure normal uplink (e.g., NUL or UL) or supplemental uplink (e.g., SUL) (e.g., event 1074A or 1074C). If the RA configuration parameters configure UL, the method 1200 can include block 1295 with the CU configuring the RA configuration parameters in a first field of a CU-to-DU message. Otherwise, in operation 1297, the CU can configure the RA configuration parameters in a second field of the CU-to-DU message.

[0292]

[0293] The following list of examples reflects a variety of the implementations explicitly contemplated by the present disclosure.

[0294] Example 1. A method implemented in a distributed unit (DU) of a distributed base station, the method comprising: receiving a request, from a centralized unit (CU) of the distributed base station, related to lower layer triggered mobility (LTM) for a user equipment (UE); and transmitting, to the CU and in response to the request, random access (RA) configuration parameters for accessing an LTM candidate cell.

[0295] Example 2. The method of example 1, wherein: the DU is a source DU (S-DU), and wherein the LTM candidate cell is associated with a DU of a different distributed base station than the S-DU.

[0296] Example 3. The method of example 2, further comprising: receiving, by the S-DU, measurement reports for the LTM candidate cell.

[0297] Example 4. The method of any of examples 2-3, wherein: receiving the measurement reports comprises receiving the measurement reports from the UE.

[0298] Example 5. The method of any of examples 2-4, further comprising: transmitting a Cell Switch Command if the measurement reports indicate the UE should implement a cell switch.

[0299] Example 6. The method of example 5, wherein: the S-DU determines which set of a plurality of sets of RA configuration parameters to provide in the Cell Switch Command based on the measurement reports.

[0300] Example 7. The method of example 5, wherein the S-DU determines which set of a plurality of sets of RA configuration parameters to provide in the Cell Switch Command based on capability information of the UE with respect to each of the plurality of sets of RA configuration parameters.

[0301] Example 8. The method of any of examples 3-7, further comprising: receiving a first set of RA configuration parameters and an additional set of RA configuration parameters from the CU; and transmitting the first set or the additional set to the UE based on the measurement reports.

[0302] Example 9. The method of example 8, wherein: transmitting the first set or the additional set comprises transmitting an LTM Cell Switch Command.

[0303] Example 10. The method of example 3, wherein: the measurement reports include a measurement result for a synchronization signal block (SSB) transmitted by an LTM candidate DU (C-DU) separate from the S-DU.

[0304] Example 1 l.The method of example 10, wherein: the S-DU refrains from providing the RA configuration parameters in the Cell Switch Command if the measurement result for the SSB is below a threshold.

[0305] Example 12. The method of any of examples 2-11, further comprising: receiving a generic RA channel (RACH) configuration.

[0306] Example 13. The method of example 12, wherein: the generic RACH configuration is included in a message having a field indicating whether the generic RACH configuration is for uplink or supplemental uplink communications.

[0307] Example 14. The method of any of examples 12-13, further comprising: receiving the generic RACH configuration from a core network (CN) node or the CU.

[0308] Example 15. The method of example 14, wherein: the CN node comprises an Operations Administration and Maintenance (0AM) node.

[0309] Example 16. The method of example 12, wherein: the generic RACH configuration is configured for Contention Free RA (CFRA), Contention Based RA, or both CFRA and CBRA.

[0310] Example 17. The method of any of examples 1-16, wherein: the RA configuration parameters include at least one set of contention free random access (CFRA) configuration parameters.

[0311] Example 18. The method of example 17, wherein: the at least one set of CFRA configuration parameters includes separate normal uplink (NUL) and supplementary uplink (SUL) indicators.

[0312] Example 19. The method of example 17, wherein: the at least one set of CFRA configuration parameters does not include separate normal uplink (NUL) and supplementary uplink (SUL) indicators.

[0313] Example 20. The method of any of examples 17-19, further comprising: transmitting the at least one set of CFRA configuration parameters in a first field of a DU-to-CU message if the at least one set is configured for NUL and transmitting the at least one set in a second field of the DU-to-CU message otherwise.

[0314] Example 21. The method of any of examples 17-19, further comprising: setting an indicator having a first value or a second value based on whether the at least one set of CFRAconfiguration parameters is configured for NUL or SUL; and transmitting the indicator to the CU.

[0315] Example 22. The method of any of examples 17-21, wherein when the DU is a source DU (S-DU), the method comprises: transmitting an NUL indicator and an SUL indicator in an LTM Cell Switch Command.

[0316] Example 23. The method of example 22, wherein: the S-DU determines a value for the NUL indicator and the SUL indicator based on measurement reports.

[0317] Example 24. The method of example 23, wherein: the measurement reports include a measurement result for a synchronization signal block (SSB) transmitted by an LTM candidate DU (C-DU) separate from the S-DU.

[0318] Example 25. The method of example 24, wherein: the S-DU refrains from transmitting RA configuration parameters if the measurement result for the SSB is below a threshold.

[0319] Example 26. The method of example 24, wherein: the S-DU sets a value for theNUL indicator and the SUL indicator based on whether the LTM C-DU supports SUL.

[0320] Example 27. The method of any of examples 1-26, further comprising: detecting access by the UE on the LTM candidate cell, the access being according to the RA configuration parameters.

[0321] Example 28. The method of example 27, wherein: the access is according to a dedicated RA channel (RACH) configuration.

[0322] Example 29. The method of example 28, further comprising: transmitting the dedicated RACH configuration in a first field of a DU-to-CU message if the dedicated RACH configuration is configured for normal uplink (NUL) and transmitting the dedicated RACH configuration in a second field of the DU-to-CU message otherwise.

[0323] Example 30. The method of example 28, further comprising: setting an indicator having a first value or a second value based on whether the dedicated RACH configuration is configured for NUL or SUL; transmitting the indicator to the CU.

[0324] Example 31. The method of example 30, further comprising: detecting access of the UE on the NUL if the dedicated RACH is configured for NUL and detecting access of the UE on the SUL otherwise.

[0325] Example 32. The method of example 28, wherein: the access is according to a contention free random access (CFRA) configuration.

[0326] Example 33. The method of example 1, wherein: the DU is a candidate DU (C-DU); and the method further comprises transmitting measurement reports, to a source DU or the CU, for the LTM candidate cell.

[0327] Example 34. The method of example 33, further comprising: transmitting at least one set of LTM contention free RA (CFRA) configuration parameters, the at least one set including an RA preamble index, a synchronization signal block (SSB) index, a physical RA channel (PRACH) Mask index, or an uplink / supplemental uplink (UL / SUL) indicator.

[0328] Example 35. The method of example 33, wherein: the measurement reports include at least a measurement result for a synchronization signal block (SSB).

[0329] Example 36. The method of example 1, wherein: the RA configuration parameters indicate whether a subsequent RA procedure shall comprise a two-step RA procedure or a four-step RA procedure.

[0330] Example 37. The method of example 36, wherein the RA configuration parameters indicate whether a subsequent RA procedure shall be contention-free or contention-based.

[0331] Example 38. The method of examples 1, wherein: the RA configuration parameters are included an LTM candidate configuration.

[0332] Example 39. The method of example 1, wherein the RA configuration parameters are included in an LTM DU configuration.

[0333] Example 40. A method implemented in a centralized unit (CU) of a distributed base station, the method comprising: receiving, from a first distributed unit (DU), random access (RA) configuration parameters for configuring a user equipment (UE) to access a lower layer triggered mobility (LTM) candidate cell; and transmitting the RA configuration parameters to a second DU.

[0334] Example 41. The method of example 40, wherein: the RA configuration parameters include at least one set of contention free random access (CFRA) configuration parameters.

[0335] Example 42. The method of example 41, wherein: the at least one set of CFRA configuration parameters includes separate normal uplink (NUL) and supplementary uplink (SUL) indicators.

[0336] Example 43. The method of example 41, wherein: the at least one set of CFRA configuration parameters does not include separate normal uplink (NUL) and supplementary uplink (SUL) indicators.

[0337] Example 44. The method of any of examples 41-43, further comprising: transmitting the at least one set of CFRA configuration parameters in a first field of a CU-to-DU message if the at least one set is configured for NUL and transmitting the at least one set in a second field of the CU-to-DU message otherwise.

[0338] Example 45. The method of any of examples 41-43, further comprising: setting an indicator having a first value or a second value based on whether the at least one set of CFRA configuration parameters is configured for NUL or SUL; and transmitting the indicator to the second DU.

[0339] Example 46. The method of example 40, wherein: the RA configuration parameters include at least one set of dedicated RA channel (RACH) parameters.

[0340] Example 47. The method of example 46, further comprising: transmitting the dedicated RACH configuration in a first field of a CU-to-DU message if the dedicated RACH configuration is configured for normal uplink (NUL) and transmitting the dedicated RACH configuration in a second field of the CU-to-DU message otherwise.

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

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

[0343] 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. Thedescription 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.

[0344] 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. Lor 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.

[0345] 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.

[0346] Certain implementations 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 specialpurpose processor, such as a field programmable gate array (FPGA) or an applicationspecific 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.

[0347] 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.

[0348] 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 implementations and applications have been illustrated and described, it is to be understood that the disclosed implementations are not 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.

Claims

What is claimed is:

1. A method implemented in a distributed unit (DU) of a distributed base station, the method comprising: receiving a request, from a central unit (CU) of the distributed base station, to prepare a candidate cell for lower layer triggered mobility (LTM) for a user equipment (UE); and transmitting, to the CU and in response to the request, LTM contention free random access (CFRA) configuration parameters for accessing the candidate cell.

2. The method of claim 1, wherein: the transmitting comprises transmitting a UE CONTEXT SETUP RESPONSE including the CFRA configuration parameters.

3. The method of claim 1, wherein: the transmitting comprises transmitting a UE CONTEXT MODIFICATION RESPONSE including the CFRA configuration parameters.

4. The method of any of claims 1-3, wherein: the LTM CFRA configuration parameters include a resource configuration for supplementary uplink (SUL).

5. The method of any of claims 1-4, wherein: the LTM CFRA configuration parameters are included in a random access channel (RACH) configuration dedicated information element (IE).

6. The method of any of claims 1-5, further comprising: transmitting, to the CU, an access success message notifying that the UE has accessed the candidate cell.

7. The method of claim 1, wherein: the DU is a source DU (S-DU), and the candidate cell is associated with a DU of a different distributed base station than the S- DU.

8. The method of claim 7, further comprising: determining to transmit an LTM Cell Switch Command to the UE based on a measurement report received from the UE.

9. The method of claim 8, wherein: the DU determines which set of a plurality of sets of random access (RA) configuration parameters to provide in the LTM Cell Switch Command based on the measurement report.

10. The method of claim 8, wherein: the DU determines which set of a plurality of sets of random access (RA) configuration parameters to provide in the LTM Cell Switch Command based on capability information of the UE with respect to each of the plurality of sets of RA configuration.

11. The method of any of claims 1-10, further comprising: detecting that the UE accessed the candidate cell according to the LTM CFRA configuration parameters.

12. The method of any of claims 1-10, wherein: the candidate cell is associated with a second DU of a different distributed base station.

13. A method implemented in a central unit (CU) of a distributed base station, the method comprising: transmitting, to a distributed unit (DU), a request to prepare a candidate cell for lower layer triggered mobility (LTM) for a user equipment (UE); and receiving, from the DU and in response to the request, LTM contention free random access (CFRA) configuration parameters for accessing the candidate cell.

14. The method of claim 13, further comprising: transmitting the LTM CFRA configuration parameters to a second DU.

15. A base station comprising a transceiver and processing hardware, the base station configured to implement a method of any of claims 1-14.

Images