Security configuration and activation for triggering mobile cell handover between central cells in dual connectivity.

By transmitting low-level triggered mobility and security configurations between the primary node and candidate secondary nodes, the security issue of cell handover between central units is resolved, thereby improving the security and efficiency of the communication system.

CN123125928APending Publication Date: 2026-11-17GOOGLE LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580028831.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-07-01
Filing Date
2025-04-04
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In wireless communication, existing technologies have not clearly defined how to handle low-level triggered mobility cell handover (inter-CU LTM) between central units and how to configure security for such handovers.

Method used

Secure communication is achieved between the user equipment (UE) and the candidate cell by sending low-layer triggered mobility (LTM) configuration and security configuration to the candidate secondary node (C-SN) from the primary node (MN).

Benefits of technology

It enables secure configuration and activation during low-level triggered mobile cell handover between central units, improving communication security and efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure FT_1
    Figure FT_1
  • Figure FT_2
    Figure FT_2
  • Figure FT_3
    Figure FT_3
Patent Text Reader

Abstract

A method that can be implemented in a primary node (MN) may include sending to a candidate secondary node (C-SN): (i) a request for low-layer triggered mobility (LTM) configuration for a candidate cell associated with the C-SN, and (ii) a first security configuration. The method may include receiving an LTM candidate configuration from the C-SN in response to the request. The method may include sending the LTM candidate configuration and a second security configuration associated with the first security configuration to a user equipment (UE). Other methods, systems, and devices are described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references to related applications

[0002] This application claims priority and filing date benefit to U.S. Provisional Patent Application No. 63 / 574,873, filed April 4, 2024, entitled "Managing Security Configuration and Activation for Inter-Central Unit Lower Layer Triggered Mobility Cell Switch in Dual Connectivity"; and claims priority and filing date benefit to U.S. Provisional Patent Application No. 63 / 666,312, filed July 1, 2024, entitled "Security Configuration and Activation for Inter-Central Unit Lower Layer Triggered Mobility Cell Switch in Dual Connectivity". The entire contents of these provisional applications are expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates to wireless communications, and more specifically, to the secure configuration and activation of lower layer triggered mobility cell switch between central units (CUs) during dual connectivity. Background Technology

[0004] This background description is provided for the purpose of presenting the general context of this disclosure. The work of the currently attributed inventors, within the scope of this background section, and aspects of this specification that might not otherwise constitute prior art at the time of application, are not expressly or impliedly acknowledged as prior art to this disclosure.

[0005] Generally, base stations operating a cellular radio access network (RAN) use a specific radio access technology (RAT) and multiple layers of the radio protocol stack to communicate with user equipment (UE). For example, the physical layer (PHY) of the RAT provides a transport channel to the media access control (MAC) sublayer, which in turn provides a logical channel to the radio link control (RLC) sublayer, and the RLC sublayer in turn provides data delivery services to the packet data convergence protocol (PDCP) sublayer.

[0006] The PDCP sublayer of the radio protocol stack provides services such as user plane data transmission, encryption, and integrity protection. 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 the ordering of Protocol Data Units (PDUs) in the uplink direction (from the user equipment, also known as the User Equipment (UE), to the base station) and in the downlink direction (from the base station to the UE). Furthermore, the PDCP sublayer provides Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs) to the Radio Resource Control (RRC) sublayer. Generally, the UE and the base station can use SRBs to exchange RRC messages and Non-Access Stratum (NAS) messages, and can use DRBs to transmit data on the user plane.

[0007] A UE can simultaneously utilize the resources of multiple RAN nodes (e.g., base stations or components of distributed base stations) interconnected via backhaul. This type of connection is called Multiple Radio Dual Connectivity (MR-DC) when these multiple RAN nodes support different Radio Access Technologies (RATs). When the UE operates under MR-DC, one base station operates as the primary node (MN) covering the primary cell (PCell), and another base station operates as the secondary node (SN) covering the primary secondary cell (PSCell). The UE communicates with the MN (via the PCell) and with the SN (via the PSCell). In other scenarios, the UE utilizes the resources of one base station at a time. A base station and / or the UE can determine that the UE should establish a radio connection with the second base station. For example, a base station can determine to hand over the UE to the second base station, and the base station can initiate a handover procedure.

[0008] When a UE moves from the coverage area of ​​one cell in the RAN to another, the RAN performs a serving cell change by configuring the UE to send Layer 3 (L3) measurement results. Based on the L3 measurement results received from the UE, the RAN sends an RRC reconfiguration message, which configures a synchronized reconfiguration for changing the serving cell (e.g., PCell or PSCell). (For example, the RRC reconfiguration message includes...) ReconfigurationWithSync (IE). When a UE operates with carrier aggregation (CA) of at least one secondary cell (SCell) and PCell or PSCell, the RAN releases the at least one SCell due to a change in PCell or PSCell. A serving cell change involves a complete L2 (and L1) reset, resulting in longer latency, greater overhead, and longer outage times. To address these issues, 3GPP recently proposed a process called Low Layer Triggered Mobility (LTM).

[0009] During communication between the RAN and the UE via the serving cell associated with the base station, the base station receives one or more L3 (e.g., RRC) measurement results from the UE. Based on the L3 measurement results, the base station determines to configure an LTM candidate cell for LTM cell handover. To configure the LTM candidate cell for the UE, the base station sends an LTM candidate configuration to the UE via RRC signaling. Subsequently, the base station receives one or more L1 measurement results from the UE. Based on the one or more L1 measurement results, the base station determines that the LTM candidate cell meets the conditions to become the UE's serving cell. After making this determination, the base station sends an LTM cell handover command to the UE, instructing the UE to perform an LTM cell handover to the LTM candidate cell. In response to the LTM cell handover command, the UE performs a cell change from the serving cell to the LTM candidate cell. The base station includes a central unit (CU) and one or more distributed units (DUs), and the DU operating the serving cell is called the serving DU. If the serving DU operates the LTM candidate cell, the LTM cell handover is an intra-CU, intra-DU LTM cell handover. If the LTM candidate cell is operated by a candidate DU (C-DU) within a DU, the LTM cell handover is an intra-CU, inter-DU LTM cell handover. 3GPP enabled intra-CU and intra-DU LTM cell handover and intra-CU and inter-DU LTM cell handover in Release 18. However, it is unclear how devices should handle inter-CU LTM cell handover. Furthermore, it is unclear how to configure security for inter-CU LTM cell handover. Summary of the Invention

[0010] One example implementation of these technologies is a method implemented in a primary node (MN) that includes: sending to a candidate secondary node (C-SN) a request for a low-layer triggered mobility (LTM) configuration for a candidate cell associated with the C-SN, and (ii) a first security configuration; receiving an LTM candidate configuration from the C-SN in response to the request; and sending the LTM candidate configuration and a second security configuration associated with the first security configuration to a user equipment (UE).

[0011] Another example implementation of these technologies is a method implemented in a candidate secondary node (C-SN), which includes: receiving (i) a low-level triggered mobility (LTM) configuration of a candidate cell associated with the C-SN and (ii) a security configuration from a primary node (MN); and communicating with the UE using a key based on the security configuration.

[0012] Another example implementation may include a method implemented in a user equipment (UE) comprising: receiving (i) a low-layer triggered mobility (LTM) configuration of a candidate primary and secondary cell (PSCell) from a radio access network (RAN) node, and (ii) a first security configuration associated with the LTM configuration; and communicating with the candidate PSCell using a second security configuration associated with the first security configuration.

[0013] Another example implementation may include a device that includes processing hardware and is configured to implement the methods described herein. Attached Figure Description

[0014] Figure 1A This is a block diagram of an example system in which the radio access network (RAN) and user equipment (UE) can implement the security configurations disclosed herein for managing low-layer triggered mobility (LTM).

[0015] Figure 1B This is another block diagram of an example system in which the RAN and UE can implement the techniques of this disclosure to support secure configuration for LTM;

[0016] Figure 1C This is a block diagram of an example base station including a central unit (CU) and distributed units (DU), which can... Figure 1A or Figure 1B Operating within the system;

[0017] Figure 2A This is a block diagram of an example protocol stack. Figure 1A and Figure 1B The UE communicates with the base station according to this protocol stack;

[0018] Figure 2B This is a block diagram of an example protocol stack. Figure 1A The UE communicates with the CU and DU according to this protocol stack;

[0019] Figure 3 This is a message sequence diagram of an example scenario in which the UE executes the LTM procedure within the CU and DU.

[0020] Figure 4 This is a message sequence diagram of an example scenario in which the UE performs the LTM procedure between DUs within the CU;

[0021] Figure 5 This is a message sequence diagram of an example scenario in which the UE performs the inter-CU LTM procedure and receives security configuration from the source BS;

[0022] Figure 6A This is a message sequence diagram of an example scenario for security configuration of the CU-to-CU LTM process initiated by the SN in a dual-connectivity system.

[0023] Figure 6B This is a message sequence diagram of an example scenario for security configuration during the LTM preparation process initiated by the MN;

[0024] Figure 6C This is a message sequence diagram of an example scenario for security configuration, in which MN, rather than SN, performs the LTM configuration transmission process with the UE;

[0025] Figure 6D This is a message sequence diagram of an example scenario for security configuration, in which MN, rather than SN, executes random access instructions and cell handover commands;

[0026] Figure 7 This is a flowchart of an example method for inter-SN LTM preparation and security configuration implemented in the S-SN, which includes the S-SN receiving security configuration for the UE from the MN;

[0027] Figure 8 This is a flowchart of an example method for MN-SN LTM security configuration implemented in MN, which includes MN sending an LTM security configuration list to C-SN;

[0028] Figure 9 This is a flowchart of an example method for preparing security for LTM candidate cells, implemented in a C-SN, which includes the C-SN receiving a request including a list of LTM security configurations;

[0029] Figure 10 This is a flowchart of an example method implemented in a RAN node for preparing security for LTM candidate cells based on whether LTM is inter-SN or intra-SN;

[0030] Figure 11 This is a flowchart of an example method implemented in the RAN node for configuring UE security and RAN security to communicate with LTM candidate cells;

[0031] Figure 12 This is a flowchart of an example method for receiving the security configuration and LTM configuration of LTM candidate cells;

[0032] Figure 13 This is a flowchart of a second example method for preparing security for LTM candidate cells based on whether LTM is between or within SNs;

[0033] Figure 14A This is a flowchart of an example method for security configuration of LTM candidate cells, wherein the UE determines, before communicating with the cell, whether the security identifier received for that cell is different from the security identifier used for the serving cell;

[0034] Figure 14B It is generally similar to Figure 14A The flowchart shows another example of the method, but in which the UE determines whether the security configuration is associated with the LTM candidate configuration before communicating with the cell associated with the LTM candidate configuration;

[0035] Figure 15 This is a flowchart of an example method implemented in an MN, which, together with an SN, provides dual connectivity (DC) to the UE;

[0036] Figure 16 This is a flowchart of an example method implemented in a candidate SN, which provides DC to the UE together with the MN;

[0037] Figure 17 It is generally similar to Figure 16 The flowchart of another example method, but in which the method is implemented in the source SN rather than the candidate SN; and

[0038] Figure 18 This is a flowchart of an example method implemented in UE. Detailed Implementation

[0039] Base stations and / or UEs can implement the techniques of this disclosure to support secure configurations for communication with LTM candidate cells. Various aspects of this disclosure provide techniques for LTM cell handover between cells associated with different base stations. In a further aspect, these base stations can provide dual connectivity to the UE. Base stations can request and / or provide LTM configurations and / or security configurations for one or more LTM candidate cells. These base stations can provide these LTM and security configurations to the UE. The UE and / or these base stations can select or further configure the security of dual connectivity communication based on the LTM candidate cell security configuration.

[0040] First refer to Figure 1A An example wireless communication system 100 can implement one or more of these technologies. The wireless communication system 100 includes a UE 102, a base station (BS) 104A, a base station 106A, and a core network (CN) 110. Base stations 104A and 106A can operate in a radio access network (RAN) 105. UE 102 is initially connected to base station 104A. In some scenarios, base station 104A can perform SN addition to configure UE 102 to operate with both base stations 104A and 106A in dual connectivity (DC). Base stations 104A and 106A operate as the MN and SN of UE 102, respectively.

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

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

[0043] When UE 102 switches from base station 104A to base station 106A, base stations 104A and 106A operate as the source base station (S-BS) and target base station (T-BS), respectively. For example, before the handover, UE 102 can work with base station 104A and the auxiliary base station (T-BS). Figure 1A (Not shown in the diagram) operates under DC. After the handover is completed, UE 102 can continue to operate under DC with base station 106A and the additional base station, or UE can operate under single connectivity (SC) with base station 106A. In the latter case, base stations 104A and 106A operate as the source MN (S-MN) and the target MN (T-MN), respectively.

[0044] The core network (CN) 110 can be either the Evolved Packet Core (EPC) 111 or the 5th Generation Core (5GC) 160; both are... Figure 1A As described, although the CN can support other cores. Base station 104A can be an eNB supporting the S1 interface for communication with EPC 111, an ng-eNB supporting the NG interface for communication with 5GC 160, or a gNB supporting the NR radio interface and the NG interface for communication with 5GC 160. In order to exchange messages directly with each other during the scenarios discussed below, base stations 104A and 106A can support the X2 or Xn interface.

[0045] like Figure 1A As shown, base station 104A supports cell 124A, and base station 106A supports cell 126A. Cells 124A and 126A can partially overlap, allowing UE 102 to communicate with base stations 104A and 106A under DC, where one of base stations 104A and 106A is MN, and the other is SN. Base station 104A can support additional cells such as cell 124B, and base station 106A can support additional cells (…). Figure 1A (Not shown in the diagram). Cells 124A and 124B may partially overlap, allowing UE 102 to communicate with base station 104A via carrier aggregation (CA). Base station 104A may operate cells 124A and 124B via one or more transmit and receive points (TRPs). More specifically, when UE 102 is in DC with base stations 104A and 106A, one of base stations 104A and 106A operates as a MeNB, Mng-eNB, or MgNB, while the other operates as an SgNB or Sng-eNB.

[0046] Generally, RAN 105 can include any suitable number of base stations supporting NR cells and / or EUTRA cells. More specifically, EPC 111 or 5GC 160 can connect to any suitable number of base stations supporting NR cells and / or EUTRA cells. See references below. Figure 1B An example configuration of CN 110 connected to an additional base station is discussed. Although the examples below specifically refer to particular CN types (EPC, 5GC) and RAT types (5G NR and EUTRA), in general, the techniques disclosed herein can also be applied to other suitable radio access and / or core network technologies, such as sixth-generation (6G) radio access and / or 6G core networks or 5G NR-6G DC.

[0047] Continue to refer to Figure 1A Base station 104A includes processing hardware 130, which may include one or more general-purpose processors (e.g., CPUs) and non-transitory computer-readable storage of instructions executed by the one or more general-purpose processors. Additionally or alternatively, processing hardware 130 may include dedicated processing units. Processing hardware 130 may include a PHY controller 132 configured to transmit data and control signals and DL reference signals on a physical downlink (DL) channel to one or more user equipments (e.g., UE 102) via one or more cells (e.g., cells 124A, 124B) and / or one or more TRPs. PHY controller 132 is also configured to receive data and control signals and / or UL reference signals on a physical uplink (UL) channel from one or more user equipments via one or more cells (e.g., cells 124A, 124B) and / or one or more TRPs. In an example implementation, processing hardware 130 includes a MAC controller 134 configured to perform MAC functions with one or more user equipments. MAC functions include random access (RA) procedures, managing UL timing advance (TA) for one or more user equipments, and / or transmitting UL / DL MAC PDUs with one or more user equipments. MAC functions include Low Layer Triggered Mobility (LTM, also referred to herein as L1 / L2 triggered mobility or low layer triggered mobility) related functions as described below. In the example, LTM controller 137 can implement LTM functions by cooperating with or signaling with MAC controller 134. Processing hardware 130 may further include an RRC controller 136 for implementing procedures and messaging at the RRC sublayer of the protocol communication stack. For example, RRC controller 132 may be configured to support RRC messaging associated with handover procedures, and / or support necessary operations when base station 104A operates as an MN relative to an SN or as an SN relative to an MN. When base station 104A is a distributed base station, CU LTM controller 137A can operate in the CU, and DU LTM controller 137B can operate in the DU (see [link to CU]). Figure 1CBase station 106A may include processing hardware 140 similar to processing hardware 130. In particular, components 142, 144, 146 and 147 may be similar to components 132, 134, 136 and 137, respectively.

[0048] When base station 104A is a distributed base station, CU LTM controller 137A can operate in the CU, and DU LTM controller 137B can operate in the DU (see...). Figure 1C Base station 106A may include processing hardware 140 similar to processing hardware 130 and may support similar functionality. In particular, components 142, 144, 146 and 147 may be similar to components 132, 134, 136 and 137, respectively.

[0049] UE 102 includes processing hardware 150, which may include one or more general-purpose processors (such as a CPU), and non-transitory computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or dedicated processing units. PHY controller 152 is also configured to receive data and control signals and / or DL ​​reference signals on the physical DL channel from base station 104A or 106A via one or more cells (e.g., cells 124A, 124B, and / or 126) and / or one or more TRPs. PHY controller 152 is also configured to transmit data and control signals and / or UL reference signals on the physical UL channel to base station 104A or 106A via one or more cells (e.g., cells 124A, 124B, and / or 126) and / or one or more TRPs. In an example implementation, processing hardware 150 includes a MAC controller 154 configured to perform MAC functions with base station 104A or 106A. For example, MAC functions include random access procedures, managing UL timing advances for one or more user facilities, and transmitting UL / DL MAC PDUs with base station 104A or 106A. In another example, MAC functions include LTM-related functions as described below. Processing hardware 150 may further include RRC controller 156 to implement procedures and message passing at the RRC sublayer of the protocol communication stack.

[0050] In operation, UE 102 can use radio bearers (e.g., DRBs or SRBs) that terminate at different times on MN 104A or SN 106A under DC. When communicating on radio bearers in the uplink (UL) (from UE 102 to the base station) and / or downlink (from the base station to UE 102) directions, UE 102 can apply one or more security keys. The UE can use several types of SRBs and DRBs. When operating under DC, a primary cell group (MCG) is defined with the base station operating as MN, and a secondary cell group (SCG) is defined with the base station operating as SN. For example, a first type of SRB resource (referred to as SRB1 resource) carries RRC messages, which in some cases include NAS messages on the dedicated control channel (DCCH). A second type of SRB resource (referred to as SRB2 resource) supports RRC messages including recorded measurement information or NAS messages, also on the DCCH but with lower priority than SRB1 resource. More generally, SRB1 and SRB2 resources allow the UE and MN to exchange MN-related RRC messages and embed SN-related RRC messages. SRB1 and SRB2 can be referred to as MCG SRBs. SRB3 resources allow the UE and SN to exchange SN-related RRC messages and can be referred to as SCG SRBs. Split SRBs allow the UE to exchange RRC messages directly with the MN via the lower-level resources of the MN and SN. Further, a DRB using only the lower-level resources of the MN can be referred to as an MCG DRB, a DRB using only the lower-level resources of the SN can be referred to as an SCG DRB, and a DRB using both MCG and SCG lower-level resources can be referred to as a split DRB.

[0051] Figure 1B This is another block diagram of example system 100B, in which the RAN and UE can implement the techniques disclosed herein for managing LTM between CUs. Figure 1B Similar to Figure 1A . Figure 1B CN 110 is depicted, which connects to additional base stations 104A, 104B, 106A, and 106B communicating in cells 124A, 124B, 126A, and 126B. Cell 125 may overlap with one of cells 124A, 124B, 126A, and 126B or other cells.

[0052] Figure 1C Depicting Figure 1AExamples of distributed or de-aggregated implementations of any one or more base stations shown (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. 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 dedicated processing units. In one example, CU 172 includes processing hardware 130 (… Figure 1A In another example, CU 172 includes processing hardware 140 (). Figure 1A In the example implementation, processing hardware 140 includes an SN RRC controller, which may be similar to RRC controller 146. Figure 1A The RRC controller is configured to manage or control one or more RRC configurations and / or RRC procedures when the base station 106A is operating as an SN.

[0053] Each of the DU 174A includes processing hardware, which may 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 dedicated processing units. In some examples, the processing hardware includes: a MAC controller (e.g., MAC controller 134, 144...). Figure 1A The MAC controller is configured to manage or control one or more MAC operations or procedures (e.g., random access procedures); and the Radio Link Control (RLC) controller is configured to manage or control one or more RLC operations or procedures when the base station 106A operates as an MN or SN. The processing hardware may also include a physical layer controller configured to manage or control one or more physical layer operations or procedures.

[0054] In some implementations, CU 172 may include a logical node CU-CP 172A, which hosts the control plane of CU 172. CU 172 may also include a logical node CU-UP 172B, which hosts the user plane of CU 172. CU-CP 172A may send control information (e.g., RRC messages, F1 application protocol messages), and CU-UP 172B may send data packets (e.g., SDAP PDUs or Internet Protocol packets).

[0055] A CU-CP 172A can connect to multiple CU-UP 172Bs via an E1 interface. The CU-CP 172A selects the appropriate CU-UP 172B for the requested service for UE 102. In some implementations, a single CU-UP 172B can connect to multiple CU-CP 172As via an E1 interface. A CU-CP 172A can connect to one or more DU 174s via an F1-C or W1-C interface. A CU-UP 172B can connect to one or more DU 174s via an F1-U or W1-U interface under the control of the same CU-CP 172A. In some implementations, a DU 174 can connect to multiple CU-UP 172Bs under the control of the same CU-CP 172A. In such implementations, the connection between the CU-UP 172B and the DU 174 is established by the CU-CP 172A using bearer context management functions.

[0056] Figure 2A An example protocol stack 200 is shown in a simplified manner, which UE 102 can use to communicate with eNB / ng-eNB 230 or gNB 232 (e.g., one or more of base stations 104A and 106A).

[0057] In example stack 200, the EUTRA physical layer (PHY) 202A provides a transport channel to the EUTRA MAC sublayer 204A, which in turn provides a logical channel to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A further provides an RLC channel to the EUTRA PDCP sublayer 208 and, in some cases, to the NR PDCP sublayer 210. Similarly, the NRPHY 202B provides a transport channel to the NR MAC sublayer 204B, which in turn provides a logical channel to the NR RLC sublayer 206B. The NR RLC sublayer 206B then provides data transmission services to the NR PDCP sublayer 210. The NR PDCP sublayer 210 can then provide data transmission services to the Serving Data Adaptation Protocol (SDAP) 212 or the Radio Resource Control (RRC) sublayer. Figure 2A (Not shown in the image) provides data transmission services. In some implementations, UE 102 supports both EUTRA and NR stacks (e.g., ...). Figure 2A As shown), to support handover between EUTRA and NR base stations and / or support DC on the EUTRA and NR interfaces. Further, as... Figure 2A As shown, UE102 can support NR PDCP 210 layering on EUTRA RLC 206A, and SDAP sublayer 212 layering on NR PDCP sublayer 210.

[0058] EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 (e.g., from an Internet Protocol (IP) layer layered directly or indirectly on PDCP layers 208 or 210) receive packets that can be referred to as Service Data Units (SDUs), and (e.g., to RLC layers 206A or 206B) output packets that can be referred to as Protocol Data Units (PDUs). For simplicity, this disclosure refers to both SDUs and PDUs as “packets”, except where a distinction between SDUs and PDUs is necessary.

[0059] On the control plane, EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 can provide signaling radio bearer (SRB) or RRC sublayer ( Figure 2A (Not shown) to exchange, for example, RRC messages or Non-Access Stratum (NAS) messages. On the user plane, EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 can provide DRBs to support data exchange. The data exchanged on NR PDCP sublayer 210 can be SDAP PDUs, Internet Protocol (IP) packets, or Ethernet packets.

[0060] Figure 2B An example protocol stack 250 is shown in a simplified manner, on which UE 102 can communicate with DU (e.g., DU 174) and CU (e.g., CU 172). The radio protocol stack 200 is functionally broken down as follows: Figure 2B The radio protocol stack 250 is shown in the diagram. At either base station 104A or 106A, the CU can retain all control and upper-layer functionality (e.g., RRC 214, SDAP 212, NR PDCP 210), while lower-layer operations (e.g., NR RLC 206B, NRMAC 204B, and NR PHY 202B) are delegated to the DU. To support connectivity to the 5GC, NR PDCP 210 provides SRBs to RRC 214, and NR PDCP 210 provides DRBs to SDAP 212 and SRBs to RRC 214.

[0061] Next, refer to Figures 3 to 5 We will discuss several example scenarios in which, Figure 1A The base station operating in the system sends a configuration to UE 102 and later activates the configuration for communication between UE 102 and the base station. Generally speaking, Figures 3 to 5 Similar events are labeled with similar reference numerals that share two least significant figures, with differences discussed below where appropriate. For example, event 302 is similar to... Figure 4 Event 402 and Figure 5Event 502, and event 320 are similar. Figure 4 Event 490 and Figure 5 Event 520. Apart from the differences shown in the figure and discussed below, any of the other implementations discussed for a particular event (e.g., for messaging and processing) can be applied to other events in the figure labeled with similar reference numerals.

[0062] First refer to Figure 3 In scenario 300, base station 104A includes CU 172 and DU 174, and DU 174 operates in cell 124A. UE 102 is initially configured to communicate with DU 174 on the serving cell (e.g., cell 124A) using the serving DU 302, and to communicate with CU 172 via DU 174 using the serving CU 174 302. DU 174 is the serving or source DU (S-DU) of UE 102. In other words, DU 174 is the serving DU (S-DU) that communicates with UE 102. In some implementations, UE 102 uses the serving DU to configure communication with CU 172 on cell 124A and other cells (e.g., cell 124A). Figure 1A UE 102 communicates with DU 174 via carrier aggregation (CA) on a cell (not shown). DU 174 operates on other cells. Cell 124A and / or other cells are the serving cells of UE 102. In other implementations, UE 102 communicates with DU 174 only on cell 124A (e.g., not on other cells). In some implementations, UE 102 communicates with DU 174 on cell 124A and / or other cells (i.e., the serving cells) via one or more TRPs. In the following description, events 394, 324, 350, 352, 354, and 326 occur on the serving cell. In some implementations, cell 124A may be a PCell. In such cases, other cells include SCells and / or additional cells associated with a PCell or Scell. In other implementations, cell 124A may be an Scell, and one of the other cells is a PCell. In such cases, additional cells include SCells and / or additional cells associated with a PCell or Scell. In the following description, base station 104A may include DU 174, CU 172, or both DU 174 and CU 172.

[0063] In event 302, UE 102 may transmit UL PDUs and / or UL control signals to base station 104A via one or more TRPs in cell 124A and / or other cells. In some implementations, UE 102 transmits UL PDUs and / or DL ​​PDUs to base station 104A via radio bearers, which may include SRBs and / or DRBs. Base station 104A may configure the radio bearers for UE 102. To transmit each UL PDU, UE 102 applies one or more security functions (e.g., integrity protection and / or encryption) to the UL data packets using at least one security key (e.g., integrity protection key and / or encryption key) and at least one security algorithm (e.g., integrity protection algorithm and / or encryption algorithm) to generate securely protected UL data packets and includes the securely protected data packets in the UL PDU. When CU 172 receives a UL PDU from UE 102 via DU 174, CU 172 retrieves a secure UL data packet from the UL PDU and applies one or more security functions (e.g., decryption and / or integrity checks) to the secure UL data packet using at least one security key (e.g., an integrity protection key and / or an encryption key) and at least one security algorithm (e.g., an integrity protection algorithm and / or an encryption algorithm) to obtain the UL data packet. In some implementations, the UL control signal includes UL control information, channel state information, Hybrid Automatic Repeat Request (HARQ) acknowledgment (ACK), HARQ negative acknowledgment, scheduling request, and / or probe reference signal. Similarly, UE 102 may receive a DL PDU and / or DL ​​control signal from base station 104A via one or more TRPs in cell 124A and / or other cells. In some implementations, the DL control signal includes downlink control information (DCI) and reference signals (e.g., synchronization signal block, channel state information reference signal (CSI-RS), and / or tracking reference signal). Base station 104A can transmit DCI on the Physical Downlink Control Channel (PDCCH) monitored by UE 102 in cell 124A and / or other cells via one or more TRPs. In order to transmit each DL PDU, CU 172 uses at least one security key (e.g., integrity protection key and / or encryption key) to apply one or more security functions (e.g., integrity protection and / or encryption) to the DL data packets to generate secure DL data packets and includes the secure DL packets in the DLPDU.When UE 102 receives a DL PDU from CU 172 via DU 174, UE 102 retrieves the securely protected DL data packet from the DL PDU and applies one or more security functions (e.g., decryption and / or integrity checks) to the securely protected data packet using at least one security key and at least one security algorithm (e.g., integrity protection algorithm and / or encryption algorithm) to obtain the DL data packet. In some implementations, the security key used by CU 172 is the same as the security key used by UE 102. In other implementations, the security key used by CU 172 is different from the security key used by UE 102.

[0064] Security features may include integrity protection and / or encryption, and the security key may include an integrity key and an encryption key, used for integrity protection / checking and encryption / decryption, respectively. When integrity protection is enabled, the sender (i.e., one of UE 102 and CU 172) can use the integrity key and integrity algorithm to generate an Integrity Message Authentication Code (MAC-I) for protecting the integrity of (UL or DL) data packets. Therefore, in this case, the sender generates a securely protected (UL or DL) packet including the data packet and the MAC-I. When encryption is enabled, the sender can use an encryption key and encryption algorithm to encrypt the UL or DL ​​data packets to obtain an encrypted packet, such that the securely protected packet includes the encrypted data packet. When both integrity protection and encryption are enabled, the sender can use the integrity key and integrity algorithm to generate a MAC-I for protecting data integrity, and then use the encryption key and encryption algorithm to encrypt the data along with the MAC-I to generate an encrypted packet and an encrypted MAC-I. The sender can then transmit the securely protected packet to the receiver (i.e., the other of UE 102 and CU 172). When encryption is enabled, the receiver decrypts the securely protected packet using an encryption key (e.g., the same or different from the encryption key used by the sender) and an encryption algorithm (e.g., the same or different from the encryption algorithm used by the sender) to obtain the data packet. When integrity protection is enabled, the receiver performs an integrity check on the securely protected packet using an integrity key (e.g., the same as the integrity key used by the sender) and an integrity algorithm (e.g., the same as the integrity algorithm used by the sender). When both encryption and integrity protection are enabled, the receiver decrypts the securely protected packet using an encryption key (e.g., the same or different from the encryption key) and an encryption algorithm (e.g., the same or different from the encryption algorithm used by the sender) to obtain the integrity-protected data packet, and then performs an integrity check on the integrity-protected data packet using the integrity key (e.g., the same as the integrity key used by the sender) and an integrity algorithm (e.g., the same or different from the integrity algorithm used by the sender). The aforementioned security protections apply to measurement reports, RRC reconfiguration messages, RRC reconfiguration completion messages, and data communications in events 304, 318, 320, 336, and 340, respectively. In some implementations, the security key includes an integrity key for integrity protection of control plane data packets such as RRC messages (e.g., events 304, 318, 320, and 336). In other implementations, the security key includes an encryption key for encrypting / decrypting control plane data packets such as RRC messages (e.g., events 304, 318, 320, and 336).In some implementations, the security key includes an integrity key for protecting the integrity of user plane data packets (e.g., data packets transmitted via DRB). In still other implementations, the security key includes an encryption key for encrypting / decrypting user plane data packets (e.g., data packets transmitted via DRB).

[0065] 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 Transport Configuration Indicator (TCI) state configuration for the serving cell. In some implementations, DU 174 may send these configuration parameters and / or the first non-LTM TCI state configuration to CU 172. CU 172 generates one or more messages (e.g., RRC reconfiguration messages) including these configuration parameters and / or the first non-LTM TCI state configuration, and CU 172 sends these one or more messages to UE 102 via DU 174. In other implementations, DU 174 sends the configuration parameters and / or the first non-LTM TCI state configuration directly to UE 102. In some implementations, the serving DU configuration is as defined in 3GPP specification 38.331. CellGroupConfig IE. In other implementations, the service DU configuration includes... CellGroupConfig Configuration parameters in 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 those defined in 3GPP specification 38.331. MeasConfig IE and / or RadioBearerConfig IE, or the CU service configuration includes MeasConfig IE and / or RadioBearerConfig Configuration parameters in IE. Radio configuration parameters or RadioBearerConfig IE configures one or more DRBs. In some implementations, the service DU configuration includes... CSI-MeasConfig IE or configuration parameters used for Channel State Information (CSI) measurement and reporting. In other implementations, the service CU configuration includes... CSI-MeasConfig IE or configuration parameters used for CSI measurement and reporting. In some implementations, UE 102 receives the service CU configuration or configuration parameters in the service CU configuration from CU 172 via DU 174. In other implementations, UE 102 receives a portion of the service CU configuration and / or a portion of the service DU configuration from a base station other than base station 104A, and the UE receives the remainder of these configuration parameters from base station 104A.

[0066] In some implementations, DU 174 and UE 102 communicate with each other using a first non-LTM TCI state configuration, for example, in events 302, 318, 320, 324, 350, 354, and / or 326. In some implementations, DU 174 sends at least one first non-LTM TCI state activation / deactivation command (e.g., MAC control element (CE)) to UE 102 to activate the first non-LTM TCI state configuration. UE 102 activates the first non-LTM TCI state configuration in response to the first non-LTM TCI state activation / deactivation command. In some implementations, DU 174 includes a serving cell ID (e.g., a serving cell index) in each of the first non-LTM TCI state activation / deactivation commands to identify the first non-LTM TCI state configuration. Each serving cell ID indicates the corresponding serving cell among serving cells. In some implementations, the serving DU configuration includes the serving cell ID, and the serving DU configures the association between the serving cell ID and the first non-LTM TCI state configuration.

[0067] When communicating with base station 104A, UE 102 sends at least one measurement report (304) to DU 174. In some implementations, the measurement report includes measurement results for the serving cell (e.g., cell 124A) and / or at least one non-serving cell of UE 102. For each of the measurement reports, DU 174 sends a DU-to-CU message (306) including the measurement report to CU 172. In some implementations, the DU-to-CU message of event 306 is an F1 Application Protocol (F1AP) message (e.g., UL RRC News Teleport (Message). The at least one serving cell includes cell 124A and / or other cells, and the at least one non-serving cell includes cell 124B and / or additional cells. In some implementations, the serving CU configuration includes at least one measurement configuration. According to the measurement configuration, UE 102 performs measurements and sends a 304 measurement report to DU 174. In some implementations, the measurement configuration includes a Layer 3 (L3) measurement configuration (e.g., MeasConfig (IE), and the measurement report includes the L3 measurement report.

[0068] Upon receiving one or more measurement reports from UE 102 (e.g., in response to this), CU 172 determines to prepare a first cell (e.g., cell 1, such as cell 124B) as an LTM candidate cell for UE 102. In some implementations, base station 104A determines to prepare the first cell for UE 102 because the measurement report indicates that the first cell can be used by base station 104A to communicate with UE 102. In some implementations, base station 104A determines to prepare the first cell for UE 102 because the measurement report indicates that the first cell meets the conditions to become an LTM candidate cell that can be used to communicate with UE 102. In some implementations, CU 172 determines to prepare the first cell for UE 102 if the L3 measurement report indicates that the signal strength and / or quality of the first cell is higher than a first predetermined threshold, better than the signal strength and / or quality of the serving cell (e.g., cell 124A) (e.g., determined by a comparison operation), and / or better than the signal strength and / or quality of the serving cell by more than a first predetermined threshold. Alternatively, CU 172 determines to prepare the first cell for UE 102, regardless of whether a measurement report is received from UE 102.

[0069] In response to determining that the first cell is ready for LTM, CU 172 sends a 308 First CU to DU message to DU 174 to prepare the first cell for UE 102. In some implementations, CU 172 includes the cell identifier (ID) 1 of the first cell in the First CU to DU message to request DU 174 to prepare the first cell for LTM for UE 102. For example, cell ID 1 includes the Cell Global Identifier (CGI). In another example, the cell ID is part of the CGI. In yet another example, the cell ID is the Physical Cell ID (PCI). In some implementations, CU 172 includes an LTM indicator in the First CU to DU message to instruct DU 174 to prepare the first cell for LTM. In some implementations, CU 172 includes the LTM indicator in... LTM Information Setup In IE, and CU 172 will LTM Information Setup The IE is included in the first CU to DU message. In some implementations, CU 172 includes the LTM indicator. LTM Information Modify In IE, and CU 172 will LTM Information Modify The IE is included in the first CU to DU message.

[0070] In response to the first CU to DU message, DU 174 generates a first LTM DU configuration (hereinafter referred to as LTMDU configuration 1) for UE 102, which uses the first cell configuration for LTM. In some implementations, CU 172 includes the first LTM configuration ID (hereinafter referred to as LTM ID 1) in the first CU to DU message, and DU 174 associates LTM ID 1 and / or cell ID 1 with LTM DU configuration 1. Then, in response to the first CU to DU message, DU 174 sends a first DU to CU message including LTM DU configuration 1 to CU 172.

[0071] Events 308 and 310 Figure 3 This is collectively referred to as the LTM preparation process 390.

[0072] In some implementations, DU 174 includes the cell ID 1 of the first cell associated with LTM DU configuration 1 in the first DU to CU message to indicate that LTM DU configuration 1 is configured for or associated with the first cell. When CU 172 and DU 174 perform multiple LTM preparation procedures (e.g., procedures 390 and LTM preparation procedures 2, ..., N described below) to prepare multiple LTM candidate cells, CU 172 can determine whether 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.

[0073] In some implementations, CU 172 does not include the LTM reference DU configuration in the first CU-DU message. In such cases, DU 174 generates the LTM reference DU configuration and includes it in the first DU-CU message. In some implementations, DU 174 generates LTM DU configuration 1 as an incremental configuration to supplement the LTM reference DU configuration. In other implementations, DU 174 generates LTM DU configuration 1 as a complete configuration, i.e., not merely supplementing the LTM reference DU configuration.

[0074] In some implementations, CU 172 includes an LTM reference DU configuration request in a first CU-DU message, and DU 174 generates an LTM reference DU configuration, and DU 174 includes the LTM reference DU configuration in the first DU-CU message in response to the request. In some implementations, CU 172 determines whether UE 102 supports the LTM reference configuration. In the context of the implementation and as described in 3GPP specification 38.331, the reference configuration is a configuration provided by the network to the UE, which is shared by a set of configured incomplete candidate configurations within the same cell group. The candidate configurations may include complete candidate configurations or incremental configurations relative to the reference configuration. If CU 172 determines that UE 102 supports the LTM reference configuration, CU 172 includes an LTM reference DU configuration request in the first CU-DU message. In response to the LTM reference DU configuration request, DU 174 includes the LTM reference DU configuration in the first DU-CU message. Otherwise, if CU 172 determines that UE 102 does not support the LTM reference configuration, CU 172 does not include the LTM reference DU configuration request in the first CU-DU message. In this case, DU 174 can generate LTM DU configuration 1 as the complete configuration, and DU 174 may not include the LTM reference DU configuration in the first DU-CU message. In other implementations, CU 172 sends an additional CU-DU message to DU 174 including the LTM reference DU configuration request, instead of sending the LTM reference DU configuration request in the first CU-DU message. In response, DU 174 sends an additional DU-CU message to CU 172 including the LTM reference DU configuration. In still other implementations, DU 174 determines whether UE 102 supports the LTM reference configuration. If DU 174 determines that UE 102 supports the LTM reference configuration, DU 174 includes the LTM reference DU configuration in the first DU-CU message. Otherwise, if DU 174 determines that UE 102 does not support the LTM reference configuration, then DU 174 will not include the LTM reference DU configuration in the first DU to CU message.

[0075] In some implementations, CU 172 includes the LTM reference DU configuration in the first CU-DU message. In some implementations, CU 172, as described above and referencing... Figure 4During the LTM preparation process, an LTM reference DU configuration is received from the supplementary DU. In other implementations, CU 172 is pre-configured with an LTM reference DU configuration. In some implementations, DU 174 generates LTM DU configuration 1 as an incremental configuration to supplement the LTM reference DU configuration. In other implementations, DU 174 ignores the LTM reference DU configuration and generates LTM DU configuration 1 as a complete configuration, i.e., not just supplementing the LTM reference DU configuration.

[0076] If DU 174 generates LTM DU configuration 1 as a complete configuration, DU 174 can include a complete configuration indication in the first DU to CU message to indicate that LTM DU configuration 1 is a complete configuration. In some implementations, if the first CU to DU message does not include the LTM reference DU configuration, then CU 172 can determine that LTM DU configuration 1 is a complete configuration. Otherwise, if the first CU to DU message includes the LTM reference DU configuration, then CU 172 can determine that LTM DU configuration 1 is an incremental configuration.

[0077] In some implementations, the LTM reference DU configuration differs from the service DU configuration. In some implementations, a portion of the LTM reference DU configuration is identical to a portion of the service DU configuration, while the remainder of the LTM reference DU configuration differs from the rest of the service DU configuration. In still other implementations, the LTM reference DU configuration is identical to the service DU configuration. In some implementations, the LTM reference DU configuration includes physical layer configuration parameters, MAC configuration parameters, and / or RLC configuration parameters. In some implementations, the LTM reference DU configuration is as defined in 3GPP specification 38.331. CellGroupConfig IE. In other implementations, the LTM reference DU configuration includes... CellGroupConfig Configuration parameters in IE. In some implementations, the LTM reference DU configuration includes... CSI-MeasConfig IE or configuration parameters used for Channel State Information (CSI) measurement and / or reporting.

[0078] In some implementations, the LTM reference DU configuration differs from the service DU configuration. In some implementations, a portion of the LTM reference DU configuration is identical to a portion of the service DU configuration, while the remainder of the LTM reference DU configuration differs from the rest of the service DU configuration. In other implementations, the LTM reference DU configuration is identical to the service DU configuration.

[0079] To prepare the first cell as an LTM candidate cell for UE 102, CU 172 may send a second CU-DU message (312) to DU 174. This message includes CSI resource configuration (e.g., CSI resource configuration 1) and / or LTM synchronization signal block (SSB) configuration (i.e., LTM SSB configuration 1) to request DU 174 to generate one or more CSI report configurations (e.g., (LTM)CSI report configuration 1). The CSI resource configuration (e.g., (LTM)CSI resource configuration 1) includes configuration parameters for at least one reference signal (RS) transmitted on the first cell. The RS includes SSB and / or CSI-RS. The LTM SSB configuration includes SSB configuration parameters that configure the SSB frequency, subcarrier spacing, SSB period, SSB location, and / or SSB power of the SSB transmitted on the first cell.

[0080] Upon receiving the CSI resource configuration (e.g., in response to it), DU 174 generates one or more CSI report configurations based on the CSI resource configuration and includes the CSI report configuration in the service DU configuration (referred to as the second service DU configuration to distinguish it from the service DU configuration in event 302). In some implementations, the CSI report configuration configures UE 102 to send CSI reports based on RS measurements. DU 174 sends a second DU to CU message 314, which includes the second service DU configuration, to CU 172. In some implementations, the CSI resource configuration includes (e.g., is or includes) one or more LTM-CSI- ResourceConfig-r18 IE. In other implementations, CSI resource configuration includes... ltm-CSI- ResourceConfigToAddModList Field / IE. In some implementations, the second service DU configuration is... CellGroupConfig IE.

[0081] In some implementations, CU 172 includes cell ID 1 and / or LTM ID 1 in the second CU-DU message (e.g., at event 312). In one implementation, CU 172 includes cell ID 1 and / or LTM ID 1 in the second CU-DU message to indicate that the CSI resource configuration is associated with the first cell. In another implementation, CU 172 includes cell ID 1 and / or LTM ID 1 in the second CU-DU message to allow DU 174 to associate LTM ID 1 with the first cell, cell ID 1, LTM DU configuration 1, and / or CSI reporting configuration. Based on the above implementations, DU 174 can associate LTM ID 1 and / or cell ID 1 with configurations associated with the first cell (e.g., LTM DU configuration 1, CSI resource configuration, and / or CSI reporting configuration). In some implementations, CU 172 includes LTM ID 1 in the first CU to DU message, while in others, CU 172 does not include LTM ID 1 in the first CU to DU message.

[0082] In some alternative implementations, CU 172 includes CSI resource configuration in the first CU to DU message, and DU 174 includes CSI report configuration in the first DU to CU message.

[0083] In some implementations, DU 174 sends LTM SSB configuration or SSB configuration parameters to CU 172, for example, in a first DU to CU message, a second DU to CU message, or an additional DU to CU message. In some implementations, DU 174 sends an additional DU to CU message in response to receiving an additional CU to DU message from CU 172. In other implementations, DU 174 sends a fourth DU to CU message in response to receiving a first CU to DU message or a second CU to DU message (e.g., ...). UE context modification beg information).

[0084] Events 312 and 314 Figure 3 This is collectively referred to as the LTM CSI report configuration and / or LTM ID configuration process 392.

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

[0086] If the first DU to CU message includes an LTM reference DU configuration, then CU 172 generates an LTM reference configuration that includes the LTM reference DU configuration. In this case, CU 172 may include the LTM reference configuration in the first RRC reconfiguration message. In some implementations, CU 172 includes the LTM reference CU configuration in the LTM reference configuration. In this case, CU 172 may generate LTM CU configuration 1 as an incremental configuration based on the LTM reference CU configuration. In other implementations, CU 172 does not include the LTM reference CU configuration in the LTM reference configuration. In this case, CU 172 may generate LTM CU configuration 1 as a complete configuration. Alternatively, similar to events 316 and 318, CU 172 sends a second RRC reconfiguration message including the LTM reference configuration to UE 102 via DU 174. In response, similar to events 320 and 322, UE 102 sends a second RRC reconfiguration complete message to CU 172 via DU 174. In some implementations, if CU 172 does not receive the LTM reference DU configuration, CU 172 can generate an LTM reference configuration that includes only the LTM reference CU configuration. In other implementations, if CU 172 does not receive the LTM reference DU configuration, CU 172 may not generate an LTM reference configuration.

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

[0088] When CU 172 executes procedure 392, CU 172 may include the second service DU configuration in the first RRC reconfiguration message. Alternatively, in events similar to 316 and 318, CU 172 sends a third RRC reconfiguration message including the second service DU configuration to UE 102 via DU 174. In response, similar to events 320 and 322, UE 102 sends a third RRC reconfiguration completion message to CU 172 via DU 174.

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

[0090] In some implementations, DU 174 sends a DU-to-CU message to CU 172, including early synchronization information for UE 102. The DU-to-CU message can be a first DU-to-CU message, a second DU-to-CU message, or a fourth DU-to-CU message. In some implementations, DU 174 sends a fourth DU-to-CU message in response to receiving a fourth CU-to-DU message from CU 172. In other implementations, DU 174 sends a fourth DU-to-CU message in response to receiving a first CU-to-DU message or a second CU-to-DU message (e.g., UE context modification requirementsIn one implementation, if DU 174 determines that UE 102 supports (i.e., is able to) early UL synchronization with the LTM candidate cell (e.g., early TA acquisition with the LTM candidate cell, early RA on the LTM candidate cell, or TA measured by the UE), then DU 174 sends a fourth DU to CU message. Otherwise, if DU 174 determines that UE 102 does not support early UL synchronization with the LTM candidate cell, then DU 174 does not send early synchronization information to CU 172. In other implementations, CU 172 sends a CU to DU message that includes an early synchronization information request (e.g., IE), and 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 can be a first CU to DU message, a second CU to DU message, or a fourth CU to DU message. In one implementation, if CU 172 determines that UE 102 supports early UL synchronization with the LTM candidate cell, then CU 172 may send an early synchronization information request. Otherwise, if CU 172 determines that UE 102 does not support early UL synchronization with the LTM candidate cell, CU 172 does not request DU 174 to provide early synchronization information for UE 102. If CU 172 receives early synchronization information, CU 172 includes the early synchronization information in the first, second, third, or fourth RRC reconfiguration message. Alternatively, similar to events 316 and 318, CU 172 sends a fifth RRC reconfiguration message including the early synchronization information to UE 102 via DU 174. In response, similar to events 320 and 322, UE 102 sends a fifth RRC reconfiguration complete message to CU 172 via DU 174.

[0091] 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 1). In some implementations, the early synchronization request may include a request for RACH configuration. If the early synchronization request includes a request for RACH configuration, then DU 174 includes the RACH configuration in the early synchronization information or the DU-to-CU message (e.g., the first, second, or fourth DU-to-CU message). Otherwise, if the early synchronization request does not include a request for RACH configuration, then DU 174 does not include the RACH configuration in the early synchronization information or the DU-to-CU message.

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

[0093] Events 316, 318, 320, and 322 are in Figure 3 This is collectively referred to as LTM configuration transfer procedure 394. LTM configuration transfer procedure 394 may further include second, third, fourth, and / or fifth RRC reconfiguration messages and second, third, fourth, and / or fifth RRC reconfiguration completion messages, related CU-to-DU messages, and / or related DU-to-CU messages. In some implementations, the aforementioned RRC reconfiguration messages and RRC reconfiguration completion messages are respectively... RRCReconfiguration Messages and RRCReconfigurationComplete information.

[0094] In some implementations, the first CU to DU message is UE Context Modification Request The message, and the first DU to CU message is UE context modification response Message. In some implementations, the second CU to DU message is UE Context Modification Request The message, and the second DU to CU message is UE context modification response Message or UE context modification requirements Message. In UE top and bottom Document revision requirements In the case of a message, CU 172 can respond to UE context modification requirements Message sent to DU 174 UE The following is a confirmation of the UE context modification. Message. In some implementations, the third CU to DU message is DL RRC message transmission Message. In other implementations, the third CU to DU message is UE Context Modification Request Message. In some implementations, the third DU to CU message is UL RRC message transmission Message. In other implementations, the third DU to CU message is UE context modification response information.

[0095] In some implementations, the LTM reference CU configuration differs from the service CU configuration. In some implementations, a portion of the LTM reference CU configuration is identical to a portion of the service CU configuration, and the remainder of the LTM reference CU configuration differs from the remainder of the service CU configuration. In still other implementations, the LTM reference CU configuration is identical to the service CU configuration.

[0096] In some implementations, the LTM reference CU configuration includes PDCP configuration parameters, measurement configuration parameters, and / or radio bearer configuration parameters. In some implementations, LTM CU configuration 1 includes those defined in 3GPP specification 38.331. MeasConfig IE and / or RadioBearerConfig IE, or LTM CU configuration 1 includes MeasConfig IE and / or RadioBearerConfig Configuration parameters in Internet Explorer.

[0097] In some implementations, LTM CU Configuration 1 and / or LTM Reference CU Configuration include PDCP configuration parameters, measurement configuration parameters, and / or radio bearer configuration parameters. In some implementations, LTM CU Configuration 1 or LTM Reference CU Configuration includes those defined in 3GPP specification 38.331. MeasConfig IE and / or RadioBearerConfig IE, or LTM CU configuration 1 or LTM reference CU configuration including MeasConfig IE and / or RadioBearerConfig Configuration parameters in Internet Explorer.

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

[0099] In some implementations, LTM DU configuration 1 includes a first L1 measurement configuration (e.g., CSI-MeasConfig The first L1 measurement configuration includes at least one first RS resource configuration and / or at least one first reporting configuration. In some implementations, the LTM CU configuration 1 includes a first TCI status configuration. In some implementations, the first L1 measurement configuration includes at least one first RS resource configuration and / or at least one first reporting configuration. In some implementations, the first RS resource configuration configures one or more RSs or one or more RS resources associated with cell 1. The RS includes SSB and / or CSI-RS. The RS resources include SSB resources and / or CSI-RS resources. In some implementations, each of the first RS resource configurations includes an RS resource configuration ID. In some implementations, the first RS resource configuration is (similar to) CSI-ResourceConfigIE. In some implementations, the first report configuration configures one or more UL resources (e.g., PUCCH resources or PUSCH resources) on the first cell for UE102 to transmit measurement results (e.g., CSI reports or LTM CSI reports). In some implementations, each of the first report configurations includes one or more RS resource configuration IDs that identify one or more RS resource configurations included in the first RS resource configuration. In some implementations, each of the first TCI state configurations configures a TCI state that associates one or two DL RSs with the corresponding Quasi-Co-located (QCL) type. The DL RS is associated with cell 1.

[0100] After receiving the LTM-related configuration and the second service DU configuration, or after receiving the aforementioned RRC reconfiguration message, UE 102 performs measurements on at least one first RS, generates at least one first L1 measurement result based on the measurements, and sends at least one first L1 measurement report including the first L1 measurement result to DU 174. The first RS may include an SSB and / or a CSI-RS. In some implementations, the transmission mode of the first RS and / or the first RS is configured in the CSI report configuration, LTM SSB configuration, and / or CSI resource configuration. UE 102 performs measurements on the first RS according to the CSI report configuration, LTM SSB configuration, and / or CSI resource configuration.

[0101] After receiving the LTM-related configuration and the second service DU configuration, or after receiving the aforementioned RRC reconfiguration message, UE 102 performs measurements on at least one second RS, generates at least one second L1 measurement result based on the measurements, and sends at least one second L1 measurement report including the first L1 measurement result to DU 174. The second RS may include an SSB and / or a CSI-RS. In some implementations, the second RS and / or the transmission mode of the second RS are configured in one or more second CSI report configurations, and / or configured in one or more second CSI resource configurations, which are included in the service DU configuration and / or the second service DU configuration in event 302. UE 102 performs measurements on the second RS according to the second CSI report configuration and / or the second CSI resource configuration. The second CSI report configuration may include a non-LTM CSI report configuration and / or an LTM CSI report configuration. The second CSI resource configuration may include a non-LTM CSI resource configuration and / or an LTM CSI resource configuration.

[0102] After sending the RACH configuration to UE 102 via CU 172, DU 174 can send a 350 PDCCH command to UE 102 to instruct UE 102 to send an RA preamble on the first cell. In response to the PDCCH command, UE 102 sends the RA preamble on the first cell. DU 174 includes PDCCH command information in the PDCCH command. The PDCCH command information includes the RA preamble index, UL or supplementary UL indicator, SSB index, and / or physical RACH mask index. In some implementations, DU 174 includes LTMID 1 in the PDCCH command to indicate the first cell. UE 102 identifies the first cell based on LTM ID 1 in the PDCCH command, and UE 102 sends a 352 RA preamble to DU 174 on the first cell using the PDCCH command information. Accordingly, DU 174 receives the 352 RA preamble according to the PDCCH command information. In some implementations, DU 174 may determine the SSB index based on L1 measurement report 324 and / or CSI resource configuration, CSI report configuration, and / or LTM SSB configuration. In some implementations, the L1 measurement report may include the SSB index. In other implementations, the L1 measurement report includes the SS / PBCH block resource indicator (SSBRI) corresponding to the SSB index. Therefore, DU 174 determines the SSB index based on the SSBRI.

[0103] In some implementations, DU 174 determines whether to send a PDCCH command based on the L1 measurement results provided in event 324. In some implementations, DU 174 sends a PDCCH command if the L1 measurement results indicate that the first cell meets the conditions for UE 102 to perform RA for early UL synchronization. Otherwise, DU 174 avoids sending a PDCCH command if the L1 measurement results indicate that the first cell does not meet the conditions for UE 102 to perform RA for early UL synchronization. In other implementations, DU 174 sends a PDCCH command if the L1 measurement results indicate that the first cell meets the conditions for UE 102 to access. Otherwise, DU 174 avoids sending a PDCCH command if the L1 measurement results indicate that the first cell does not meet the conditions for UE 102 to access. In still other implementations, DU 174 sends a PDCCH command after receiving the 320 RRC reconfiguration complete message, regardless of the L1 measurement results provided in event 324.

[0104] After sending a 324 L1 measurement report or a 352 RA preamble, UE 102 may send a 354 additional L1 measurement report to DU 174, similar to event 324. Based on the additional L1 measurement report and / or L1 measurement report 324, DU 174 determines that UE 102 should perform an LTM cell handover to the first cell. In response to this determination, DU 174 generates an LTM cell handover command (e.g., MAC CE) including LTM ID 1 and sends a 326 LTM cell handover command to UE 102. In response to this determination, DU 174 may send a 328 DU-CU cell handover notification message to CU 172. In response to the LTM cell handover command, UE 102 performs an LTM cell handover to the first cell. During the LTM cell handover, UE 102 accesses the first cell (332) and sends a 336 RRC reconfiguration complete message to DU 174 via the first cell. DU 174 sends a DU-CU message (e.g., 338) to CU 172, which includes an RRC reconfiguration completion message. UL RRC message transmission (Message). When UE 102 receives an LTM cell handover command, UE 102 identifies LTM candidate configuration 1 based on LTM ID 1 and uses LTM candidate configuration 1 to access the first cell (332). Depending on the implementation, UE 102 may stop communicating on the serving cell in response to the LTM cell handover command. Then, DU 174 sends a fifth DU-CU message to CU 172, including an RRC reconfiguration completion message. When DU 174 detects that UE 102 has accessed the first cell in event 332, DU 174 may send an access success message (334) to CU 172 to indicate that UE 102 has accessed the first cell.

[0105] In some implementations, DU 174 includes the TA value used for UL synchronization with the first cell in the LTM cell handover command. In one implementation, DU 174 derives the TA value based on the RA preamble (e.g., the reception timing of the RA preamble). In another implementation, DU 174 derives the TA value from the UL transmission of UE 102 on the serving cell (e.g., cell 124A). UE 102 applies the TA value to synchronize with the first cell in the UL transmission. After applying the TA value, UE 102 transmits the first UL transmission on the first cell based on LTM Candidate Configuration 1 without performing the RA procedure on the first cell. In some implementations, UE 102 transmits the first UL transmission on the first cell using UL grant. In this case, the first UL transmission is a PUSCH transmission. In some implementations, the PUSCH transmission includes the RRC reconfiguration complete message provided in event 336. In some implementations, the UL grant is a configuration grant, and LTM Candidate Configuration 1 or LTM DU Configuration 1 includes a configuration grant configuration that configures the configuration grant. In other implementations, the UL grant is a dynamic grant received by UE 102 on the PDCCH of the first cell. After sending the first UL transmission, UE 102 receives the PDCCH transmission addressed to UE 102's C-RNTI and determines that the LTM cell handover has been successfully completed in response to the receipt of the PDCCH transmission.

[0106] PDCCH transmissions may include UL grants or DL ​​allocations. If the PDCCH transmission includes a UL grant, UE 102 sends a PUSCH transmission to DU 174 on the first cell using the UL grant. If the PDCCH transmission includes a DL allocation, DU 174 sends a PDSCH transmission to UE 102 on the first cell according to the DL allocation. DU 174 may send an Access Success 334 message to CU 172 after receiving the first UL transmission, sending a PDCCH transmission, receiving a PUSH transmission, or sending a PDSCH transmission (e.g., in response to this).

[0107] In other implementations, DU 174 does not include the TA value in the LTM cell handover command. If the LTM cell handover command does not include the TA value, UE 102 performs a 332 RA procedure on the first cell according to the RA configuration parameters. In some implementations, the RA configuration parameters are included in LTM Candidate Configuration 1, LTM DU Configuration 1, and / or the LTM cell handover command. In some implementations, the RA configuration parameters configure PRACH resources, the association between SSB and PRACH resources, and / or one or more PRACH timings. If UE 102 successfully completes the RA procedure, UE 102 determines that the LTM cell handover to the first cell has been successfully completed. 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 (CFRA) procedure or a contention-based RA (CBRA) procedure. During a four-step RA procedure, UE 102 transmits an RA preamble (i.e., message 1) on the first cell and receives an RA response (i.e., message 2) from DU 174 on the first cell in response to the RA preamble. Then, the UE transmits message 3 on the first cell using the UL authorization in the RA response, and DU 174 transmits message 4 to UE 102 on the first cell in response. In some implementations, message 4 is a DCI. If the RA procedure is a CBRA procedure, UE 102 determines that contention resolution was successful upon receiving message 4. If the RA procedure is a CBRA procedure, the RA preamble is a dedicated preamble, and UE 102 determines that contention resolution was successful upon receiving the RA response. During a two-step RA procedure, UE 102 transmits message A on the first cell, and DU 174 transmits message B to UE 102 on the first cell in response. If the RA procedure is a CFRA or CBRA procedure, UE 102 determines that contention resolution was successful upon receiving message B. UE 102 may include the RRC reconfiguration complete message 336 in message 3 or message A. Alternatively, UE 102 sends the RRC reconfiguration complete message 336 after completing the RA procedure. After receiving message 3, message A, or the RRC reconfiguration complete message 336, or after sending message 4 or message B, DU 174 may send an access success message 334 to CU 172.

[0108] In some implementations, DU 174 includes a first set of LTM CFRA configuration parameters in the LTM cell handover command to configure UE 102 to perform a CFRA procedure to access the first cell. 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 / Supplementary UL (SUL) indicator. In some implementations, the first UL / NUL indicator configures UE 102 to perform a CFRA procedure on normal UL (NUL) or 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), then UE 102 performs a CFRA procedure on UL. Otherwise, if the first UL / SUL indicator indicates SUL (e.g., if the first UL / SUL indicator is set to a second value), then UE 102 performs a CFRA procedure on SUL. UE 102 uses LTMCFRA configuration parameters and at least one RACH configuration to perform the 332 CFRA procedure to access the first cell. LTM candidate configuration 1 includes the RACH configuration. The RACH configuration is not configured for early UL synchronization. In some implementations, the RACH configuration is configured for LTM cell handover. 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 does not include a dedicated RACH configuration (e.g., RACH-ConfigDedicated IE). In other implementations, the RACH configuration includes a dedicated RACH configuration (e.g., RACH-ConfigDedicated IE). DU 174 performs the CFRA procedure with UE 102 based on the first set of LTMCFRA configuration parameters and the RACH configuration.

[0109] In some implementations, DU 174 determines whether to include the first set of LTM CFRA configuration parameters in the LTM cell handover command based on the measurement report received at event 354. In some implementations, DU 174 obtains (e.g., retrieves, derives, calculates, or determines) one or more measurement results from the measurement report. In some implementations, the measurement results include the measurement results of a first SSB identified by a first SSB index. The first SSB is transmitted by DU 174 on the first cell. In such cases, if the measurement result of the first SSB is higher than (or equal to) a second predetermined threshold, DU 174 includes the first set of LTM CFRA configuration parameters in the LTM cell handover command. Otherwise, if the measurement result of the first SSB is lower than (or equal to) the second predetermined threshold, DU 174 avoids including the first set of LTM CFRA configuration parameters in the LTM cell handover command.

[0110] In some implementations, the DU 174 pre-configures a first set of LTM CFRA configuration parameters. The DU 174 may pre-configure at least one additional set of LTM CFRA configuration parameters, and each additional set 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 additional sets are specifically configured for the first cell. In other implementations, the first set and / or additional sets are configured for any cell operated by the DU 174. In some implementations, the DU 174 pre-configures the first set and / or additional sets for one of UL (i.e., NUL) and SUL. In other implementations, the DU 174 pre-configures the first set for one of UL and SUL, and configures the additional set for the other of UL and SUL.

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

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

[0113] After successfully completing the LTM cell handover to the first cell as described above, UE 102 uses LTM candidate configuration 1 to communicate with DU 174 and CU 172 via the first cell 340. When using the LTM reference configuration, UE 102 first applies the LTM reference configuration, and then applies LTM candidate configuration 1 to supplement the LTM reference configuration.

[0114] In some implementations, each element in the TCI state configuration includes a TCI state ID. In some implementations, DU 174... DU-CU cell handover notificationThe message and / or LTM cell handover command includes a first TCI state ID indicating a first TCI state configuration in the TCI state configuration. UE 102 identifies the first TCI state configuration in the TCI state configuration based on the first TCI state ID and applies the first TCI state configuration to transmit UL and / or DL ​​transmissions with DU 174 in events 332, 336, and / or 340. In events 332, 336, and / or 340, DU 174 applies the first TCI state configuration to transmit UL and / or DL ​​transmissions with UE 102. In other implementations, where separate TCI states are used, the DL TCI state and the ULTCI state use different TCI state IDs. In such cases, DU 174 includes the first TCI state ID for DL ​​and the second TCI state ID for UL in the TCI state configuration. DU-CU cell handover notification In messages and / or LTM cell handover commands, these two IDs identify the first TCI state configuration and the second TCI state configuration, respectively. 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. UE 102 applies the first TCI state configuration and / or the second TCI state configuration to transmit DL and UL transmissions with DU 174 in events 332, 336, and / or 340, respectively. 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. DU 174 applies the first TCI state configuration and the second TCI state configuration to transmit DL and UL transmissions with UE 102 in events 332, 336, and / or 340, respectively.

[0115] In some implementations, before or after sending the LTM cell handover command, or during or after procedures 390 or 392, CU 172 may prepare additional cells (i.e., cells 2, ..., N) as LTM candidate cells for UE 102, as described above, with DU 174. N is an integer and greater than 1. For example, CU 172 and DU 174 perform additional LTM preparation procedures 2, ..., N to prepare cells 2, ..., N respectively. Each of LTM preparation procedures 2, ..., N is similar to procedure 390. In LTM preparation procedures 2, ..., N, CU 172 receives LTM DU configurations 2, ..., N, which configure cells 2, ..., N for LTM respectively. CU 172 generates LTM candidate configurations 2, ..., N, each including LTM DU configurations 2, ..., N. CU 172 assigns LTM IDs 2, ..., N to identify LTM DU configurations 2, ..., N and LTM candidate configurations 2, ..., N, respectively. As described for CSI resource configuration 1 and CSI report configuration 1, CU 172 can obtain CSI resource configurations 2, ..., N and perform CSI report configuration and / or LTM ID configuration procedures 2, ..., N with DU 174 to obtain CSI report configurations 2, ..., N, respectively. As described for RACH configuration 1, CU 172 can obtain RACH configurations 2, ..., N for cells 2, ..., N, respectively. As described for TCI status configuration 1, CU 172 can obtain TCI status configurations 2, ..., N for cells 2, ..., N, respectively. Each of the CSI report configuration and / or LTM ID configuration procedures 2, ..., N is similar to procedure 392. As described for LTM SSB configuration 1, CU 172 can obtain LTM SSB configurations 2, ..., N for cells 2, ..., N, respectively. In some implementations, CU 172 may perform LTM configuration transfer procedures 2, ..., N with UE 102 to send to UE 102 lists including the following items: {LTM ID 2, LTM candidate configuration 2, CSI resource configuration 2 (if obtained), TCI state configuration 2 (if obtained), RACH configuration 2 (if obtained), LTM SSB configuration 2 (if obtained)}, ..., {LTM ID N, LTM candidate configuration N, CSI resource configuration N, TCI state configuration N (if obtained), RACH configuration N (if obtained), LTM SSB configuration N (if obtained)}. Each of LTM configuration transfer procedures 2, ..., N is similar to procedure 394. In other implementations, CU 172 includes this list in the first RRC reconfiguration message.

[0116] To simplify the following description, tuples 1, ..., N are used to represent {LTM ID 1, LTM candidate configuration 1, CSI resource configuration 1 (if obtained), TCI state configuration 1 (if obtained), RACH configuration 1 (if obtained), LTM SSB configuration 1 (if obtained)}, ..., {LTM ID N, LTM candidate configuration N, CSI resource configuration N, TCI state configuration N (if obtained), RACH configuration N (if obtained), LTM SSB configuration N (if obtained)}, respectively. In some implementations, CU172 includes tuples 1, ..., N in RRC reconfiguration messages 1, ..., N during the LTM configuration passing process 1, ..., N. RRC reconfiguration message 1 is the first RRC reconfiguration message 316, 318. In some implementations, CU 172 includes tuples 1, ..., N in the container IE (e.g., ...). LTM-Config IE In other implementations, CU 172 includes tuples 1, ..., N in container IE 1 (e.g., ..., N), and encloses the containers IE 1, ..., N in RRC reconfiguration messages 1, ..., N respectively. LTM-Config In IE), the container IE 1 is included in the first RRC reconfiguration message.

[0117] In some implementations, CU 172 can include CSI resource configurations 1, ..., N in a container IE instead of in a tuple, where N is a positive integer.

[0118] In some implementations, after receiving the 334 Access Success Message or the 338 DU to CU Message, CU 172 may send a 342 CU to DU Message to DU 174. In one implementation, CU 172 sends the 342 CU to DU Message to release the radio resources and / or configuration of the serving cell configured for UE 102. In another implementation, CU 172 sends the 342 CU to DU Message to release some of LTM candidate cells 2, ..., N. In this case, CU 172 sends a message to release the resources and configuration of the candidate cells. In response to the CU to DU Message (e.g., event 342), DU 174 sends a 344 DU to CU 172. In some implementations, the CU to DU Message 342 and the DU to CU Message 344 are respectively... UE context modification Modify request Messages and UE context modification response information.

[0119] In some implementations, the LTM ID is provided in different formats depending on which command or message provides it. For example, the LTM ID can be provided differently in PDCCH instructions, LTM cell handover commands, and RRC reconfiguration messages. For instance, a PDCCH instruction or LTM cell handover command includes a first field for including LTM ID 1, and a first RRC reconfiguration message includes a second field for including LTM ID 1. In some implementations, the first and second fields have different formats or encoding schemes. For example, the first field uses a binary format with values ​​ranging from 0 to 7 (i.e., 3 bits), and the second field uses an integer format with values ​​ranging from 1 to 8. In this example, a first field with a binary value of 000b is equivalent to a second field with an integer value of 1, a first field with a binary value of 001b is equivalent to a second field with an integer value of 2, and so on, and a first field with a binary value of 111b is equivalent to a second field with an integer value of 8.

[0120] Events 304, 306, 390, 392, 394, and 324 are in Figure 3 This is collectively referred to as the CU-DU-LTM configuration process 396. Events 304, 306, 390, 392, 394, 324, 350, 352, 354, 326, 328, 332, 334, 336, 338, and 340 are in... Figure 3 This is collectively referred to as the CU-internal DU-internal LTM process 380.

[0121] Next reference Figure 4 In scenario 400, base station 104A includes CU 172, S-DU 174A, and candidate DU (C-DU) 174B. S-DU 174A operates cell 124A and optionally operates an additional cell, while C-DU 174B operates a different cell (e.g., cell 124B or cell 126). Figure 1A Scene 400 is a scene between DUs within a CU, similar to Scene 300. Therefore, the description of Scene 300 can be largely applied to Scene 400. Figure 3 Some descriptions of DU 174 in the document can be applied to Figure 4 S-DU 174A in, and for Figure 3 Some descriptions of DU 174 in the document can be applied to C-DU 174B. The differences between scenarios 300 and 400 are described below.

[0122] Initially, UE 102 uses a serving DU configuration to communicate with S-DU 174A 402 on one or more serving cells (e.g., cell 124A and / or other cells), and UE 102 uses a serving CU configuration to communicate with CU 172 via S-DU 174A. (See reference...) Figure 3 As described, UE 102 and CU 172 perform security protection on data transmitted between UE 102 and CU 172 via S-DU 174A and C-DU 174B. This data includes, for example, data packets, measurement reports, RRC reconfiguration messages and RRC reconfiguration completion messages, and data packets as described in events 402, 404, 494, 436, and 440, respectively.

[0123] In some implementations, CU 172 and S-DU 174A can perform LTM configuration procedure 496 or LTM procedure 480 with UE 102, as referenced. Figure 3 As described. In the case of procedure 380, UE 102 can perform an LTM cell handover to the first cell (e.g., cell 124B), as referenced. Figure 3 As described. After a successful LTM cell handover, the first cell becomes the serving cell, and cell 124A and / or other cells are no longer serving cells for UE 102. In the case of procedure 496, UE 102 does not perform an LTM cell handover. During communication 402, UE 102 sends at least one measurement report (e.g., an L3 measurement report) via S-DU 174A to CU 172 in steps 404 and 406. Based on this measurement report, CU 172 determines to prepare cell 1 (e.g., cell 126 operated by C-DU 174B) for LTM for UE 102. Cell 1 is identified by a cell ID (i.e., cell ID 1). In response to this determination, CU 172 and C-DU 174B perform LTM preparation procedure 490 to request C-DU 174B to prepare cell 1 as an LTM candidate cell for UE 102. In LTM preparation process 490, CU 172 sends a first CU-DU message to C-DU 174B, including cell ID 1 of cell 1, to request C-DU 174B to prepare cell 1 as an LTM candidate cell for UE 102, similar to event 308. In response, C-DU 174B sends a first DU-CU message to CU 172, including the LTM DU configuration (e.g., LTM DU configuration 1), similar to event 310. In some implementations, CU 172 requests an LTM reference DU configuration in the first CU-DU message, such as a reference... Figure 3As described, in other implementations, CU 172 does not request the LTM reference DU configuration in the first CU to DU message. In some implementations, C-DU 174B includes the LTM reference DU configuration in the first DU to CU message, as reference Figure 3 As described, in other implementations, the C-DU 174B does not include the LTM reference DU configuration in the first DU to CU message.

[0124] In some implementations, if CU 172 receives from S-DU 174A as referenced... Figure 3 If the LTM reference DU configuration is as described, CU 172 can include the LTM reference DU configuration in the first CU-DU message, and C-DU 174B can generate an incremental configuration of the LTM DU configuration based on the LTM reference DU configuration. In this case, C-DU 174B does not send the LTM reference DU configuration for UE 102 to CU 172. In other implementations, CU 172 receives the LTM reference DU configuration from C-DU 174B, for example, in a reference... Figure 3 The LTM reference configuration is received in the first DU-to-CU message or an additional DU-to-CU message. In such cases, CU 172 can generate an LTM reference configuration that includes the LTM reference DU configuration. In some implementations, CU 172 includes the LTM reference CU configuration in the LTM reference configuration, while in other implementations, CU 172 does not include the LTM reference CU configuration in the LTM reference configuration.

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

[0126] To prepare cell 1 as an LTM candidate cell for UE 102, CU 172 can receive early synchronization information for cell 1 in a DU-CU message (e.g., a first DU-CU message or an additional DU-CU message) from C-DU 174B. In some implementations, C-DU 174B sends an additional DU-CU message in response to receiving an additional CU-DU message from CU 172. In other implementations, C-DU 174B sends an additional DU-CU message (e.g., a first DU-CU message or an additional DU-CU message) in response to receiving a first CU-DU message. UE context modification requirements Message). Early synchronization information includes RACH configuration (e.g., RACH configuration 1) and / or at least one TCI state configuration (e.g., TCI state configuration 1), as referenced. Figure 3 As described. In some implementations, the C-DU174B includes the PDCCH instruction information (PDCCH instruction information 1) used for early UL synchronization with cell 1 in the early synchronization information or DU to CU message.

[0127] In some implementations, CU 172 can receive LTM SSB configuration or SSB configuration parameters in the LTM SSB configuration from C-DU 174B, for example, in a first DU-to-CU message or an additional DU-to-CU message. In some implementations, CU 172 can receive the PCI of cell 1 from C-DU 174B in a first DU-to-CU message or an additional DU-to-CU message. In some implementations, C-DU 174B sends an additional DU-to-CU message in response to receiving an additional DU-to-CU message from CU 172. In other implementations, C-DU 174B sends an additional DU-to-CU message in response to receiving a first CU-to-DU message (e.g., ...). UE context modification requirements information).

[0128] In some implementations, C-DU 174B includes a first set of LTM CFRA configuration parameters in the first DU to CU message of process 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, CU 172 includes the first set of LTM CFRA configuration parameters in the second CU to DU message of process 492. C-DU 174B may include at least one additional set of LTM CFRA configuration parameters in the first DU to CU message of process 490. Each additional set of LTM CFRA configuration parameters includes an RA preamble index, an SSB index, a PRACH mask index, and / or a UL / SUL indicator. In such cases, CU 172 includes the additional set of LTM CFRA configuration parameters in the second CU to DU message of process 492. In some implementations, the C-DU 174B configures the first group and / or supplementary group LTM CFRA configuration parameters for UE 102. In some implementations, the first group and / or supplementary group LTM CFRA configuration parameters are specifically configured for cell 1. In other implementations, the first group and / or supplementary group LTM CFRA configuration parameters are configured for any LTM candidate cells configured by the C-DU 174B for UE 102.

[0129] In some implementations, the first and supplementary group LTM CFRA configuration parameters do not include a separate UL / SUL indicator. In some implementations, the C-DU 174B configures the first and / or supplementary group LTM CFRA configuration parameters for either UL (i.e., NUL) or SUL (e.g., UL / NUL or SUL), and the C-DU 174B includes a single UL / SUL indicator in the first DU to CU message, indicating that the first and / or supplementary group LTM CFRA configuration parameters are configured for UL / NUL or SUL. In such cases, the CU 172 includes a single UL / SUL indicator in the second CU to DU message, indicating that the first and / or supplementary group LTM CFRA configuration parameters are configured for UL / NUL or SUL. In other implementations, if C-DU 174B configures the first group and / or additional group LTM CFRA configuration parameters for UL, then C-DU 174B includes the first group and / or additional group in the first field / IE of the first DU to CU message. Otherwise, if C-DU 174B configures the first group and / or additional group LTM CFRA configuration parameters for SUL, then C-DU 174B includes the first group and / or additional group in the second field / IE of 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 group and / or additional group LTM CFRA configuration parameters in the first field / IE, then CU172 includes the first group and / or additional group in the first field / IE of the second CU to DU message. Otherwise, if the first DU to CU includes the first group and / or additional group LTM CFRA configuration parameters in the second field / IE, then CU 172 includes the first group and / or additional group in the second field / IE of 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.

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

[0131] For reference Figure 3 As described, CU 172 performs LTM configuration transfer procedure 494 with UE 102 to send LTM ID 1 and LTM candidate configuration to UE 102. In some implementations, CU 172 sends {LTM ID, LTM candidate configuration} as a tuple in the first RRC reconfiguration message during procedure 494. Depending on the implementation, CU 172 may include the LTM reference configuration, CSI report configuration, CSI resource configuration, RACH configuration, TCI state configuration, LTM SSB configuration, and / or the PCI of cell 1 in the first RRC reconfiguration message sent to UE 102 and / or in other RRC reconfiguration messages sent to UE 102, such as the reference configuration. Figure 3 As described, CU 172 includes the LTM ID in the first RRC reconfiguration or other RRC reconfiguration messages to indicate that the CSI resource configuration, RACH configuration, TCI state configuration, LTM SSB configuration, and / or the PCI of cell 1 are associated with cell 1. For example, CU 172 includes the CSI resource configuration, RACH configuration, TCI state configuration, LTM SSB configuration, and / or the PCI of cell 1 in a tuple. In another example, CU 172 includes {LTM ID, CSI resource configuration, RACH configuration, TCI state configuration, LTM SSB configuration, and / or the PCI of cell 1} as a tuple in other RRC reconfiguration messages. In response to each of the other RRC reconfiguration messages, UE 102 sends an RRC reconfiguration complete message to CU 172 via S-DU 174A.

[0132] In some implementations, the PDCCH command information includes frequency domain resource allocation, RA preamble index, UL or supplementary UL indicator, SSB index, and / or physical RACH mask index. CU 172 can send a CU-DU message (e.g., a second CU-DU message or an additional CU-DU message) containing the PDCCH command information to S-DU 174A. In some implementations, CU 172 includes LTM ID 1 or cell ID 1 in the CU-DU message to indicate that the PDCCH command information is associated with LTM ID 1 or cell ID 1. For example, when CU 172 sends the PDCCH command information in a second CU-DU message, CU 172 includes {cell ID 1, PDCCH command information} as a tuple in the CU-DU message. When CU 172 sends an additional CU-DU message, S-DU 174A can send an additional DU-CU message in response. The S-DU 174A sends a 450 PDCCH command to UE 102 based on the PDCCH command information. For example, the S-DU 174A sends a 450 PDCCH command including the PDCCH command information to UE 102. In some implementations, the S-DU 174A may determine the SSB index to be included in the PDCCH command based on L1 Measurement Report 424 and / or CSI resource configuration, CSI report configuration, and / or LTM SSB configuration. In some implementations, the S-DU 174A includes LTM ID 1 in the PDCCH command to indicate cell 1. When CU 172 sends the PDCCH command information in an appended CU to DU message, the S-DU 174A may send an appended DU to CU message to CU 172 in response. UE 102 sends a 452 RA preamble to C-DU 174B on cell 1 using RACH configuration and / or the PDCCH command information. C-DU 174B derives the TA value based on the RA preamble. C-DU 174B sends DU-CU TA information transmission message 456, including the TA value, to CU 172. CU 172 then sends CU-DU TA information transmission message 458, including the TA value, to S-DU 174A. In some implementations, C-DU 174B includes cell ID 1, RA preamble index, RA radio network temporary identifier (RA-RNTI), and / or the DU ID of S-DU 174A in message 456. In such cases, CU 172 includes cell ID 1, RA preamble index, RA-RNTI, and / or the DU ID of S-DU 174A in message 458. In response to the determination command UE 102 to perform an LTM cell handover to cell 1, S-DU 174A sends an LTM cell handover command 456, including LTM ID 1, to UE 102.If the S-DU 174A receives the TA value as described above, the S-DU 174A can include the TA value in the LTM cell handover command. The S-DU 174A can also include the first TCI state ID in the LTM cell handover command. The first TCI state ID indicates the first TCI state configuration in the TCI state configuration.

[0133] In some implementations, the C-DU 174B determines the RA-RNTI based on the PRACH timing of the RA preamble 452 received by the C-DU 174B. In some implementations, the C-DU 174B calculates the RA-RNTI as follows:

[0134]

[0135] Wherein, s_id is the index of the first OFDM symbol of the PRACH timing (0 ≤ s_id < 14), t_id is the index of the first slot of the PRACH timing in the system frame (0 ≤ t_id < 80), where, for μ = {0, 1, 2, 3}, the subcarrier spacing used to determine t_id is based on the μ value specified in Clause 5.3.2 of 3GPP TS 38.211, and for μ = {5, 6}, t_id is the index of the 120 kHz slot in the system frame that includes the PRACH timing (0 ≤ t_id < 80), f_id is the index of the PRACH timing in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for RA preamble transmission (0 indicates NUL carrier, 1 indicates SUL carrier).

[0136] In response to the confirmation command UE 102 to perform LTM cell handover or send LTM cell handover command 426, S-DU174A sends command 428 to CU 172. DU-CU cell handover notification The message instructs UE 102 to perform an LTM cell handover to cell 1. In response, CU 172 sends a 430 message to C-DU 174B. CU-DU Cell Handover Notification The message instructs UE 102 to perform an LTM cell handover to cell 1. UE 102 accesses cell 1 (432) in response to the LTM cell handover command. In some implementations, S-DU 174A determines whether to include a first set of LTM CFRA configuration parameters in the LTM cell handover command, and / or include the first set of LTM CFRA configuration parameters in the command to configure UE 102 to perform the CFRA procedure to access cell 1, as referenced. Figure 3 As described. UE 102 uses LTM CFRA configuration parameters and at least one RACH configuration to perform the CFRA procedure to access cell 1, as referenced. Figure 3As described. The C-DU 174B performs the CFRA procedure with UE 102 according to the LTM CFRA configuration parameters and RACH configuration, as referenced. Figure 3 As described.

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

[0138] In some implementations, when the first set of LTM CFRA configuration parameters includes a first UL / SUL indicator, the S-DU174A includes the first UL / SUL indicator in the LTM cell handover command, as shown in the reference. Figure 3 As described. In other implementations, when the first set of LTM CFRA configuration parameters does not include a UL / SUL indicator, the S-DU 174A can determine the value of the UL / SUL indicator and include it in the LTM cell handover command, as described below and / or referenced. Figure 3As described. In some implementations, if the second CU-to-DU message includes a first set of LTM CFRA configuration parameters in the first field / IE for UL, the S-DU 174A sets the UL / SUL indicator to a first value for UL. Otherwise, if the second CU-to-DU message includes a first set of LTM CFRA configuration parameters in the second field / IE for UL, the S-DU 174A sets the UL / SUL indicator to a second value for SUL. In other implementations, the S-DU 174A determines the value of the UL / SUL indicator in the LTM cell handover command based on the measurement result of the first SSB obtained by the S-DU 174A from the measurement report at event 454. In one implementation, if the measurement result is higher than (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 handover 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 group instead of the first group in the LTM cell handover command. In other implementations, the S-DU 174A sets the UL / SUL indicator to a pre-configured value (e.g., the first value), for example, because the C-DU 174B does not support SUL. In still other implementations, the S-DU 174A sets the UL / SUL indicator to a pre-configured value (e.g., the second value), for example, because the S-DU 174A is pre-configured to set the UL / SUL indicator to that pre-configured value.

[0139] In some implementations, the S-DU 174A includes the first TCI status ID. DU-CU cell handover notification The message further includes the first TCI status ID in CU 172. CU-DU Cell Handover Notification In the message, UE 102 and C-DU174B identify the first TCI state configuration in the TCI state configuration based on the first TCI state ID, and apply the first TCI state configuration to transmit UL transmissions and / or DL ​​transmissions in events 432, 436 and / or 440.

[0140] 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 the first TCI state ID for DL ​​and the second TCI state ID for UL within... DU-CU cell handover notification In messages and / or LTM cell handover commands, these two IDs identify the first TCI state configuration and the second TCI state configuration, respectively. In response to... DU-CU cell handover notification The message, CU 172, then includes the first TCI status ID and the second TCI status ID in the message sent to C-DU 174B. CU-DU Cell Handover Notification In the message, 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. UE 102 applies the first TCI state configuration and the second TCI state configuration to receive DL transmissions and transmit UL transmissions with C-DU 174B in events 432, 436, and / or 440, respectively. C-DU 174B 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. C-DU 174B applies the first TCI state configuration and the second TCI state configuration to transmit DL transmissions and UL transmissions with UE 102 in events 432, 436, and / or 440, respectively.

[0141] In some implementations, each of the TCI state configurations includes or is associated with a TCI state ID. In some implementations, CU 172 may send a CU-DU message (e.g., a second CU-DU message or an additional CU-DU message) to S-DU 174A that includes the TCI state configuration and / or the associated TCI state ID. In some implementations, CU 172 includes LTM ID 1 or Cell ID 1 in the CU-DU message to indicate that the TCI state configuration is associated with LTM ID 1 or Cell ID 1. For example, when CU 172 sends the TCI state configuration and / or the associated TCI state ID in a second CU-DU message, CU 172 includes {Cell ID 1, TCI state configuration} as a tuple in the CU-DU message. When CU 172 sends an additional CU-DU message, S-DU 174A may send an additional DU-CU message in response. In some implementations, the S-DU 174A includes the first TCI state ID, indicating the first in the TCI state configuration, in the LTM cell handover command 426. In some implementations, the S-DU 174A determines either the first TCI state configuration or the first TCI state ID. The UE 102 identifies one of the TCI state configurations based on the first TCI state ID and applies the first TCI state configuration in UL transmission and / or DL ​​reception in events 432, 436, and / or 440.

[0142] In some implementations, before or after sending the LTM cell handover command, or during or after procedures 490 or 492, CU 172 may prepare additional cells (i.e., cells 2, ..., N) with C-DU 174B as LTM candidate cells for UE102, as referenced. Figure 3 As described.

[0143] In some implementations, the first CU to DU message and the first DU to CU message are UE Context Establishment Request Messages and UE Context Establishment Response Messages. In some implementations, the first CU to DU message and the first DU to CU message are... UE Request for amendments Messages and UE context modification response In some implementations, LTM preparation procedure 490 is a UE context establishment procedure, and the additional LTM preparation procedure is a UE context modification procedure. In other implementations, LTM procedure 490 and the additional LTM preparation procedure are both UE context establishment procedures. In still other implementations, LTM procedure 490 and the additional LTM preparation procedure are both UE context modification procedures.

[0144] Events 404, 406, 490, 492, 494, and 424 are collectively referred to as CU-DU inter-LTM configuration procedure 497. Events 404, 406, 490, 492, 494, 424, 450, 452, 454, 456, 458, 426, 428, 430, 432, 434, 436, 438, 440, 442, and 444 are collectively referred to as CU-DU inter-LTM procedure 480.

[0145] Next reference Figure 5 In scenario 500, base station 104A operates as a serving base station or source base station (S-BS), and base station 106A operates as a candidate base station (C-BS). C-BS 106A includes CU 172 and DU 174. Scenario 500 is similar to scenarios 300 and 400, except that scenario 500 is an inter-CU scenario (i.e., an inter-base station scenario), while scenarios 300 and 400 are intra-CU scenarios (i.e., intra-base station scenarios). S-BS 104A may include CU and DU (… Figure 5 (not shown in the image), similar to Figure 3 and Figure 4 Base station 104A. Initially, UE 102 communicates with S-BS 104A via the serving cell using the service configuration 502. In some implementations, S-BS 104A includes S-DU and CU, and the service configuration may include a service CU configuration and a service DU configuration, as referenced. Figure 3 and Figure 4 As described. UE 102 uses at least one first security key and at least one first security algorithm to perform security protection on data transmitted with S-BS104A, as referenced. Figure 3 and Figure 4 As described, S-BS 104A uses at least one first security key and at least one first security algorithm to perform security protection on data transmitted with UE 102, as referenced. Figure 3 and Figure 4 As described. Depending on the implementation, the first security key and the first security algorithm used by UE 102 and S-BS 104A may be the same or different. When communicating with UE 102 502, S-BS 104A may perform an in-CU LTM procedure 580 with UE 102, similar to procedures 380 and / or 480. Alternatively, when communicating with UE 102 502, S-BS 104A may perform an in-CU LTM configuration procedure 596 with UE 102, similar to procedures 396 and / or 496.

[0146] When communicating with S-BS 104A, UE 102 sends at least one measurement report (504) to S-BS 104A. The measurement report includes measurement results for UE 102's serving cell and / or at least one non-serving cell (e.g., cell 126). Based on the measurement report, S-BS 104A determines a first cell (e.g., cell 126) to be prepared as an LTM candidate cell for UE 102. For example, the measurement report includes the PCI of the first cell and the measurement results for cell 126. Based on the PCI, S-BS 104A identifies that the first cell is operated by base station 106A and determines that the first cell meets the conditions for LTM preparation based on the measurement results.

[0147] After determining that the first cell is ready as an LTM candidate cell for UE 102 (e.g., in response to this), the S-BS104A (e.g., the CU of S-BS 104A) generates a first cell ID (i.e., cell ID 1) that includes the first cell (i.e., cell 1). Switching requests Message. S-BS 104A sends 505 to CU 172. Switching requests Message. In some implementations, Switching requests The message includes an LTM indicator, which indicates that... Switching requests The message pertains to LTM for the first cell ID. Upon receiving... Switching requests Following the message (e.g., in response to this), CU 172 and DU 174 perform LTM preparation procedure 590 to prepare a first cell as an LTM candidate cell for UE 102, similar to procedure 390 or 490. In procedure 590, CU 172 sends a first CU-DU message including the first cell ID to DU 174 to request preparation of the first cell, similar to event 308. In response, CU 172 can receive a first DU-CU message including LTM DU configuration 1 from DU 174, similar to event 310. CU 172 generates a first LTM candidate configuration (LTM candidate configuration 1). In response to Switching requests Message: CU 172 sends 507 to S-BS 104A, including the first LTM candidate configuration. Switch request confirmation Message. In some implementations, CU 172 includes the first cell ID. Switch request confirmation The message indicates that the first LTM candidate configuration is provided for or associated with the first cell (ID).

[0148] Events 505, 590, and 507 are in Figure 5 This is collectively referred to as the CU-inter-LTM preparation process (or, the MN-inter-LTM preparation process) 582.

[0149] In some implementations, Switching requests The message includes the 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-DU message. In some implementations, Switching requests The message includes the BS ID of S-BS 104A. When the BS ID is received, CU 172 can include the BS ID in the first CU to DU message. For example, the BS ID is the gNB ID.

[0150] In some implementations, CU 172 requests the LTM reference DU configuration in procedure 590, such as the reference... Figure 3 and Figure 4 As described, in other implementations, CU 172 does not request the LTM reference DU configuration. In some implementations, DU 174 sends the LTM reference DU configuration to CU 172 in procedure 590, such as the reference... Figure 3 and Figure 4 As described, in other implementations, DU 174 does not send the LTM reference DU configuration to CU 172. In some implementations, S-BS 104A (e.g., the CU of S-BS 104A) can obtain the LTM reference configuration, such as reference... Figure 3 and Figure 4 As described. In other implementations, the S-BS 104A can, during another CU's LTM preparation process as described above and later herein, transfer data from another BS ( Figure 5 (Not shown in the image) Receives the LTM reference configuration. If the S-BS 104A obtains the LTM reference configuration, the S-BS 104A can include the LTM reference configuration (the LTM reference configuration generated by the S-BS) in... Switching requests In some implementations, S-BS 104A includes the LTM reference configuration in the inter-node RRC message. HandoverPreparationInformation In, or as an Xn Application Protocol (XnAP) IE or field, and include inter-node RRC messages or XnAP IEs. Switching requestsThe message states that, alternatively, S-BS 104A determines the request or causes C-BS 106A to provide a complete LTM candidate configuration, in which case S-BS 104A does not include the LTM reference configuration. Switching requests The message states that if the S-BS 104A does not obtain the LTM reference configuration, then the S-BS 104A will not include the LTM reference configuration in the message. Switching requests In the message. If Switching requests If the message includes an LTM reference configuration, CU 172 can include the LTM reference configuration in the first CU-DU message. DU 174 can extract the LTM reference DU configuration from the LTM reference configuration. Alternatively, CU 172 extracts the LTM reference DU configuration from the LTM reference configuration and includes the LTM reference DU configuration in the first CU-DU message. DU 174 can generate an LTM DU configuration as an incremental configuration based on the LTM reference DU configuration, such as the reference... Figure 3 As described. Alternatively, DU 174 can ignore the LTM reference (DU) configuration and generate an LTM DU configuration as a complete configuration, as described in the reference. Figure 3 As described.

[0151] Otherwise, if Switching requests In some implementations, the CU 172 receives the LTM reference DU configuration from the DU 174, such as the reference DU configuration. Figure 3 As described, in other implementations, CU 172 does not receive an LTM reference DU configuration from DU 174. If CU 172 receives an LTM reference DU configuration (e.g., in the first DU to CU message), then CU 172 generates an LTM reference configuration that includes that LTM reference DU configuration (the LTM reference configuration generated by the C-BS). CU 172 may include an LTM reference CU configuration (the LTM reference CU configuration generated by the candidate CU (C-CU)). Otherwise, if CU 172 does not receive an LTM reference DU configuration as described... Figure 3 If an LTM reference DU configuration is received from DU 174 as described, then CU 172 does not generate an LTM reference configuration. Instead, CU 172 generates an LTM reference configuration (C-BS generated LTM reference configuration) that includes only the LTM reference CU configuration generated by C-CU. When CU 172 generates an LTM reference configuration (C-BS generated LTM reference configuration), CU 172 includes the C-BS generated LTM reference configuration... Switch request confirmation In the message.

[0152] In some implementations, if LTM DU configuration 1 is a complete configuration, then CU 172 generates LTM candidate configuration 1 as the complete configuration. CU 172 may include the complete configuration indication (e.g., the BS-to-BS interface protocol field / IE) in... Switching requests confirm The message indicates that LTM candidate configuration 1 is a complete configuration. In some implementations, the BS-to-BS interface protocol is the 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 the impact on non-LTM configurations. In other implementations, the complete configuration indication is an existing field / IE defined in 3GPP specification 38.423. Otherwise, if LTM DU configuration 1 is an incremental configuration, CU 172 generates LTM candidate configuration 1 as an incremental configuration. CU 172 can obtain... Switch request confirmation The message excludes the full configuration indication to indicate that LTM candidate configuration 1 is an incremental configuration. Alternatively, CU 172 may include the incremental configuration indication (e.g., the BS-to-BS interface protocol field / IE) in the message. Switch request confirmation The message indicates that LTM candidate configuration 1 is an incremental configuration. In some implementations, the BS-to-BS interface protocol is the Xn application protocol defined in 3GPP specification 38.423. In some implementations, the incremental configuration indication is a dedicated field / IE (e.g., LTM-specific) to reduce or eliminate the impact on non-LTM configurations. In other implementations, the incremental 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 at least two possible values ​​(i.e., a first value and a second value). The first value of the BS-to-BS interface protocol field / IE can indicate a full configuration, and the second value of the BS-to-BS interface protocol field / IE can indicate an incremental configuration.

[0153] In some implementations, the S-BS 104A is pre-configured with CSI resource configuration (e.g., CSI resource configuration 1 or LTM CSI resource configuration 1) and / or 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 LTM SSB configuration from the OAM (Operation, Administration, and Maintenance) node. In still other implementations, the S-BS 104A receives the CSI resource configuration and / or LTM SSB configuration from the CU 172. For example, the CU 172 includes the CSI resource configuration and / or LTM SSB configuration in... Switch request confirmation The message states that in some implementations, CU 172 includes the PCI (PCI 1) of the first cell. Switch request confirmationIn the message, to prepare the first cell as a candidate LTM cell for UE 102, the CU and S-DU of S-BS 104A perform the LTM CSI report configuration and / or LTM ID configuration procedures. Figure 5 (Not shown in the diagram), similar to procedure 392. During the LTM CSI report configuration and / or LTM ID configuration process, the CU of S-BS 104A sends the CSI resource configuration and / or LTM SSB configuration to the S-DU of S-BS 104A. In response, the CU of S-BS 104A receives one or more CSI report configurations for UE 102 from the S-DU of S-BS 104A. In some implementations, the CU of S-BS 104A receives the CSI report configuration from the second service DU configuration of the S-DU.

[0154] To prepare the first cell as an LTM candidate cell for UE 102, CU 172 can receive early synchronization information (e.g., early synchronization information 1) of the first cell from DU 174 in a DU-CU message (e.g., a first DU-CU message or an additional DU-CU message). In some implementations, DU 174 sends an additional DU-CU message in response to receiving an additional CU-DU message from CU 172. In other implementations, DU 174 sends an additional DU-CU message in response to receiving a first CU-DU message (e.g., ...). UE context modification request message ). CU 172 includes early synchronization information. Switch request confirmation The message includes early synchronization information such as RACH configuration (e.g., RACH configuration 1) and / or at least one TCI state configuration (e.g., TCI state configuration 1). In some implementations, DU 174 includes PDCCH instruction information for early UL synchronization with the first cell in the early synchronization information or DU to CU message. CU 172 includes PDCCH instruction information in... Switch request confirmation In the message.

[0155] In some implementations, CU 172 assigns an LTM ID (e.g., LTMID 1) to identify the first LTM candidate configuration, and CU 172 includes this LTM ID in... Switch request confirmation In other implementations, S-BS 104A assigns an LTM ID (e.g., LTM ID 1) to identify the first LTM candidate configuration.

[0156] Received Switch request confirmationFollowing the message (e.g., in response to this), S-BS 104A (e.g., the CU of S-BS 104A) sends a 518 first RRC reconfiguration message to UE 102, which includes {LTM ID 1, LTM candidate configuration 1} as a tuple, similar to event 318. If Switch request confirmation If the message includes the LTM reference configuration, the S-BS 104A can include the LTM reference configuration in the first RRC reconfiguration message. If the S-BS 104A receives... Switch request confirmation If the message contains CSI resource configuration 1, TCI state configuration 1, RACH configuration 1, and / or LTM SSB configuration 1, then the S-BS 104A may include this information in the tuple. Alternatively, the S-BS 104A sends one or more additional RRC reconfiguration messages to the UE 102, including CSI resource configuration 1, TCI state configuration 1, RACH configuration 1, LTM SSB configuration 1, and / or the PCI of the first cell. In each of the additional RRC reconfiguration messages, the S-BS 104A includes LTM ID 1 to indicate that CSI resource configuration 1, TCI state configuration 1, RACH configuration 1, LTM SSB configuration 1, and / or the PCI of the first cell are associated with or configured for the first cell. In response to the first RRC reconfiguration message, the UE 102 sends a 520 First RRC Reconfiguration Complete Message to the S-BS 104A. UE 102 sends an additional RRC reconfiguration complete message to S-BS 104A in response to each additional RRC reconfiguration complete message. The RRC reconfiguration messages (i.e., the first RRC reconfiguration message and / or the additional RRC reconfiguration messages) and the RRC reconfiguration complete messages (i.e., the first RRC reconfiguration complete message and / or the additional RRC reconfiguration complete messages) form the LTM configuration delivery process. S-BS 104A may include the second service DU configuration in the first RRC reconfiguration message or one of the additional RRC reconfiguration messages.

[0157] In some implementations, the S-BS 104A (e.g., the CU of the S-BS 104A) includes the first security information. cut Change request In the message. In some implementations, the first security information includes the RAN-level security key (e.g., Key NG-RANStar) and / or the next-hop chain count. In some implementations, S-BS 104A includes the security capabilities of UE 102 in... Switch ask In the message.

[0158] In some implementations, CU 172 generates a first security configuration for UE 102 based on the first security information. In one implementation, CU 172 includes the first security configuration in... Switch request confirmation In another implementation, CU 172 includes the first security configuration in the first LTM candidate configuration or LTM reference configuration.

[0159] In other implementations, instead of CU 172 generating the first security configuration, S-BS 104A (e.g., the CU of S-BS104A) generates the first security configuration based on the first security information. In such cases, CU 172 does not include the security configuration (e.g., the first security configuration) used for UE 102. Switch request confirmation In the message, the first LTM candidate configuration and / or the LTM reference configuration.

[0160] In some implementations, S-BS 104A includes the first security configuration in the container IE that includes tuple 1 (e.g., LTM-Config In the first RRC reconfiguration message, the S-BS 104A includes the container IE in the first RRC reconfiguration message. In other implementations, the S-BS 104A includes the first security configuration in tuple 1.

[0161] In some implementations, the first security configuration includes at least a portion of the first security information. For example, the first security configuration includes a next-hop chain count and does not include a RAN-level security key. In some implementations, the first LTM candidate configuration, LTM reference configuration, or first security configuration configures at least one second security algorithm. In some implementations, the S-BS104A (e.g., the CU of S-BS 104A) or CU 172 determines the second security algorithm based on security capabilities. In some implementations, the second security algorithm includes encryption algorithms and / or integrity algorithms, which may be the same as or different from the first security algorithm.

[0162] In some implementations, the first security configuration includes a key set change indicator (e.g., keySetChangeIndicator This indicator indicates the new BS key (e.g., the new K key). gNB It needs to be obtained from the new CN key (e.g., the new K key). AMFThe key set change indicator is either derived from the next hop (NH) parameter or not. In some implementations, the S-BS 104A (e.g., the CU of the S-BS 104A) or CU 172 sets the key set change indicator to a first value that indicates the first new key is derived from the NH parameter. In other implementations, the S-BS 104A or CU 172 is pre-configured to set the key set change indicator to a first value that indicates the first new key is derived from the NH parameter. This is because inter-CU LTM may not support deriving a new BS key based on a new CN key.

[0163] In some implementations, if Switch request confirmation If the message includes a full configuration indication to indicate that LTM candidate configuration 1 is a full configuration, then S-BS 104A will include the full configuration indication (e.g., the RRC field / IE) in the first RRC reconfiguration message to indicate that LTM candidate configuration 1 is a full configuration. Otherwise, if Switch request confirmation The message does not include a complete configuration instruction (or if...) Switch request confirmation If the message includes an incremental configuration indication to indicate that LTM candidate configuration 1 is an incremental configuration, then S-BS104A will exclude or not include the complete configuration indication (e.g., RRC field / IE) in the first RRC reconfiguration message to indicate that LTM candidate configuration 1 is an incremental configuration.

[0164] if Switch request confirmation If the message includes PDCCH instruction information (e.g., PDCCH instruction information 1), then the S-BS104A sends a 550 PDCCH instruction based on the PDCCH instruction information. If the S-BS104A is a distributed base station, the CU of the S-BS104A can send the PDCCH instruction information to the S-DU of the S-BS104A. For example, the S-BS104A or its S-DU sends a 550 PDCCH instruction, including the PDCCH instruction information, to UE 102. In some implementations, the S-BS104A or its S-DU can determine the SSB index included in the PDCCH instruction based on L1 Measurement Report 524 and / or CSI resource configuration, CSI report configuration, and / or LTM SSB configuration. In some implementations, the S-DU or S-BS104A includes LTM ID 1 in the PDCCH instruction to indicate the first cell. UE 102 uses RACH configuration and / or PDCCH command information to send a 552 RA preamble to DU 174 on the first cell. S-DU or S-BS 104A derives the TA value based on the RA preamble. DU 174 then sends a 556 DU-CU TA containing the TA value to CU 172. Information transmissionMessage. CU 172 sends a CU-CU TA information transmission message 558, including the TA value, to S-BS 104A (e.g., the CU of S-BS 104A). In some implementations, DU 174 includes cell ID 1, RA preamble index, RA-RNTI, DU ID of S-DU of S-BS 104A, and / or BS ID of S-BS 104A in message 556. In some implementations, DU 174 does not include the BS ID in message 556. In some implementations, CU 172 includes cell ID 1, RA preamble index, RA-RNTI, DU ID of S-DU, and / or BS ID of S-BS 104A in message 558. In some implementations, CU 172 does not include the BS ID in message 558. The CU of S-BS 104A sends to the S-DU of S-BS 104A a message including the TA value, cell ID 1, RA preamble index, RA-RNTI, and / or the DU ID of the S-DU and / or the BSID of the S-BS 104A. CU-DU TA Information Transmission Message. In some implementations, the CU of S-BS 104A does not include the BS ID. CU-DU TA information transmission In the message.

[0165] In some implementations, CU 172 determines the address (e.g., IP address) of S-BS 104A or its CU based on the BS ID of S-BS 104A. In other implementations, CU 172 determines the address (e.g., IP address) of S-BS 104A or its CU based on the DU ID of S-DU of S-BS 104A. Through these implementations, CU 172 sends data to S-BS 104A or its CU based on this address. CU-CU TA Information Transmission information.

[0166] In response to a determination, for example, based on measurement reports 524 and / or 554, that UE 102 is to perform an LTM cell handover to a first cell, S-DU or S-BS 104A sends an LTM cell handover command 526, including LTM ID 1 (e.g., a configuration identifier), to UE 102. In response to the LTM cell handover command, UE 102 may cease communication on the serving cell. In response to the LTM cell handover command, UE 102 accesses the first cell 532 and sends an RRC reconfiguration complete message 536 to DU 174. DU 174 then sends a DU-CU message 538, including the RRC reconfiguration complete message, to CU 172. In some implementations, UE 102 derives at least one second security key based on the first security configuration. In some implementations, UE 102 derives a new BS key (e.g., a new K key) based on the first security configuration. gNB The UE 102 then derives the second security key from the new BS key. In some implementations, if the UE 102 receives the second security algorithm for the first cell (i.e., the LTM candidate cell) as described above, the UE 102 derives the second security key based on the new BS key and the second security algorithm. Otherwise, if the UE 102 does not receive the second security algorithm for the first cell, the UE 102 derives the second security key based on the new BS key and the first security algorithm.

[0167] In some implementations, UE 102 derives a second security key in response to receiving the 526 LTM cell handover command. In other implementations, UE 102 derives the second security key after receiving the first security configuration and before receiving the 526 LTM cell handover command. UE 102 applies the second security key to communicate with CU 172 in events 536 and 540. If UE 102 receives the second security algorithm as described above, UE 102 applies the second security key and the second security algorithm to communicate with CU 172 in events 536 and 540. Otherwise, if UE 102 does not receive the second security algorithm, UE 102 applies both the second security key and the first security algorithm to communicate with CU 172 in events 536 and 540. In some implementations, the second security key includes an integrity key for integrity protection of control plane data packets (e.g., RRC messages in events 536 and / or 540). In other implementations, the second security key includes an encryption key for encrypting / decrypting control plane data packets (e.g., RRC messages in event 536 and / or event 540). In still other implementations, the security key includes an integrity key for integrity protection of user plane data packets (e.g., data packets transmitted via DRB) in event 540. In yet other implementations, the security key includes an encryption key for encrypting / decrypting user plane data packets (e.g., data packets transmitted via DRB) in event 540. UE102 stops using the first security key to communicate with CU 172.

[0168] In some implementations, CU 172 derives at least one second security key based on the first security information. In some implementations, CU 172 derives a new BS key (e.g., a new K key) based on the first security information. gNBCU 172 derives the at least one second security key from the new BS key. In some implementations, if CU 172 sends the second security algorithm to UE 102 as described above, CU 172 derives the second security key based on the new BS key and the second security algorithm. Otherwise, if CU 172 does not send the second security algorithm to UE 102, CU 172 derives the second security key based on the new BS key and the first security algorithm. CU 172 applies the second security key to communicate with UE 102 in events 536 and 540. If CU 172 sends the second security algorithm to UE 102 as described above, CU 172 applies the second security key and the second security algorithm to communicate with UE 102 in events 536 and 540. Otherwise, if CU 172 does not send the second security algorithm to UE 102, CU 172 applies the second security key and the first security algorithm to communicate with UE 102 in events 536 and 540.

[0169] In some implementations, CU 172 derives a second security key in response to receiving a 527 CU-to-CU cell handover notification message, a 534 access success message, or a 538 DU-to-CU message. In other implementations, CU 172 derives the second security key after receiving the first security configuration and before receiving the 527 CU-to-CU cell handover notification message, before receiving the 534 access success message, or before receiving the 538 DU-to-CU message. CU 172 applies the second security key to communicate with UE 102 in events 536 and 540. In some implementations, the second security key includes an integrity key for integrity protection of control plane data packets (e.g., RRC messages in events 536 and / or 540). In other implementations, the second security key includes an encryption key for encrypting / decrypting control plane data packets (e.g., RRC messages in events 536 and / or 540). In some implementations, the second security key includes an integrity key for protecting the integrity of user plane data packets (e.g., data packets transmitted via DRB) in event 540. In still other implementations, the second security key includes an encryption key for encrypting / decrypting user plane data packets (e.g., data packets transmitted via DRB) in event 540. In some implementations, the second security key used by CU172 is the same as the second security key used by UE 102.

[0170] Upon receiving a DU-to-CU message (538) or an RRC reconfiguration complete message, C-BS 106A communicates with UE 102 (540) based on a first LTM candidate configuration and / or an LTM reference configuration. In some implementations, UE 102 sends an RRC reconfiguration complete message (536) including LTMID 1 to instruct UE 102 to apply the first LTM candidate configuration. Based on LTM ID 1, CU 172 identifies the first LTM candidate configuration and / or the LTM reference configuration. In other implementations, CU 172 uses a configuration provided in event (534). Connection successful The first cell ID in the message identifies the first LTM candidate configuration and / or LTM reference configuration. In this implementation, CU 172 maintains or stores the association information between the first cell ID and the first LTM candidate configuration and / or the LTM reference configuration. When CU 172... Connection successful When the message receives the first cell ID 534, CU 172 identifies the first LTM candidate configuration and / or LTM reference configuration based on the first cell ID and associated information.

[0171] In some implementations, UE 102 may perform an RA procedure in event 532 to access the first cell. The RA procedure may be a four-step RA procedure or a two-step RA procedure. The RA procedure may be a CBRA procedure or a CFRA procedure. In some implementations, S-BS 104A includes a first set of LTM CFRA configuration parameters in the LTM cell handover command to configure UE 102 to perform a CFRA procedure to access the first cell. UE 102 performs the CFRA procedure using the first set of LTM CFRA configuration parameters. In some implementations, as described for procedure 490, DU 174 includes the first set of LTM CFRA configuration parameters in the first DU to CU message of procedure 590. CU 172 then includes the first set of LTM CFRA configuration parameters in... Switch request confirmation In some implementations, such as those described for procedure 490, DU 174 includes at least one additional group LTM CFRA configuration parameter in the first DU to CU message. CU 172 then includes the additional group LTM CFRA configuration parameter in... Switch request confirmation In the message.

[0172] In some implementations, such as for Figure 4 As described in C-DU 174B, DU 174 configures a first group and / or an additional group for UL (i.e., NUL) or SUL, and indicates these configurations in the first DU to CU message. When the first group and / or the additional group are configured for either UL or SUL, CU 172... Switch request confirmationThe message includes a single UL / SUL indicator that indicates the first group and / or the supplementary group is configured for either UL or SUL. When the first group and / or the supplementary group is configured for UL, CU 172 includes the first group and / or the supplementary group. Switch request confirmation The first field in the message / IE. When the first group and / or supplementary groups are configured for SUL, CU 172 includes the first group and / or supplementary groups. Switching requests confirm In the second field / IE of the message. In this case, the first field / IE and the second field / IE are defined for UL and SUL, respectively.

[0173] In some implementations, such as for Figure 4 As described in C-DU 174B, DU 174 configures a first group for either UL or SUL and an additional group for the other, indicating these configurations in the first DU-to-CU message. In this case, CU 172 sets the UL / SUL indicator in the first group to a value indicating either UL or SUL, and sets the UL / SUL indicator in the additional group to a value indicating the other. Alternatively, CU 172... Switch request confirmation The message includes the first group and the additional group in one of the first field / IE and the other in the second field IE, respectively.

[0174] In some implementations, if the S-DU or S-BS 104A receives the TA value as described above, the S-DU or S-BS 104A may include the TA value in the LTM cell handover command. In some implementations, the S-DU or S-BS 104A includes a first TCI state ID in the LTM cell handover command. The first TCI state ID indicates the first TCI state configuration in the TCI state configuration. If the LTM cell handover command includes the TA value, the UE 102 may skip the RA procedure for accessing the first cell in event 532. Otherwise, the UE 102 may perform the RA procedure for accessing the first cell in event 532 as described above.

[0175] In response to the confirmation command UE 102 performing LTM cell handover or sending LTM cell handover command 526, the S-DU of S-BS104A sends a message to the CU of S-BS104A. DU-CU cell handover notification The message instructs UE 102 to perform or be performing an LTM cell handover to the first cell. In response to receiving... DU-CU cell handover notification Message: CU of S-BS 104A sends 527 to CU172 CU-CU cell handover notificationThe message instructs UE 102 to perform an LTM cell handover to the first cell. In response, CU 172 sends a 530 message to DU 174. CU-DU Cell Handover Notification The message instructs UE 102 to perform an LTM cell handover to the first cell. In some implementations, S-BS 104A includes the first TCI state ID. CU-CU cell handover notification In the message, CU 172 then includes the first TCI status ID. CU-DU Cell Handover Notification In the message, UE 102 and DU 174 identify the first TCI state configuration in the TCI state configuration based on the first TCI state ID, and UE 102 and DU 174 apply this first TCI state configuration to transmit UL transmissions and / or DL ​​transmissions in events 532, 536, and / or 540. In other implementations, when using separate TCI states, the DL TCI state and the UL TCI state use different TCI state IDs. In such cases, the S-DU of S-BS 104A in DU-CU cell handover notification The message and / or LTM cell handover command includes a first TCI state ID for DL ​​and a second TCI state ID for UL, which respectively identify the first and second TCI state configurations in the TCI state configuration. The S-BS 104A CU responds to... DU-CU Community Switch notification The message was then sent to CU 172. CU-CU cell handover notification The message includes a first TCI status ID and a second TCI status ID. Then, CU 172 includes the first and second TCI status IDs in the message sent to DU 174. CU-DU small Zone switch notification In the message, 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. UE 102 applies the first TCI state configuration and the second TCI state configuration to transmit DL transmissions and UL transmissions with DU 174 in events 532, 536, and / or 540, respectively. 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. DU 174 applies the first and / or second TCI state configurations to transmit DL transmissions and / or UL transmissions with UE 102 in events 532, 536, and / or 540, respectively.

[0176] In some implementations, the UE 102 determines whether to execute an LTM cell handover, send the 526 LTM cell handover command, or receive the 527 command. DU-CU cell handover notificationFollowing the message (e.g., in response to this), S-BS 104A (e.g., the CU of S-BS 104A) sends one or more 531s to CU 172. Early state transition Each early state transition message includes the DL COUNT value of the DRB or the DISCARD DL COUNT value. UE 102 and S-BS 104A transmit 502 data to each other via this DRB. In some implementations, upon receiving 534... Connection successful Following the message, either after receiving the 538 DU to CU message or after receiving the RRC reconfiguration complete message, CU 172 sends a 539 LTM success message to S-BS 104A (e.g., the CU of S-BS 104A) to indicate that the LTM cell handover was successfully completed. In some implementations, the LTM success message is... Switching successful In some implementations, CU 172 includes the first cell ID in the LTM success message. In other implementations, CU 172 does not send a BS-to-BS message to S-BS 104A (e.g., the CU of S-BS 104A) to indicate that the LTM cell handover has been successfully completed.

[0177] In some implementations, the process involves determining whether UE 102 is performing an LTM cell handover, sending the 526 LTM cell handover command, and receiving the 527 command. DU-CU cell handover notification Upon receiving a 539 LTM success message (e.g., in response to this), S-BS 104A (e.g., the CU of S-BS 104A) sends 541 to CU 172. SN state transition The message includes the DL COUNT value and / or UL COUNT value of the DRB, through which UE 102 and S-BS 104A transmit 502 data to each other.

[0178] In some implementations, upon receiving 534 Connection successful Message received, 538 DU to CU message received or RRC reconfiguration complete message received or 541 SN state transition Following the message (e.g., in response to this), CU 172 sends 543 to S-BS 104A. UE context release Message. Response to UE context release The message indicates that S-BS 104A releases the UE context of UE 102.

[0179] In some implementations, as described above, the S-BS 104A (e.g., the CU of the S-BS 104A) may prepare additional cells (i.e., cells 2, ..., N) with CU 172 as LTM candidate cells for UE 102 before or after sending the LTM cell handover command, or during, before or after procedure 582. Cells 2, ..., N are identified by cell IDs 2, ..., N, respectively, and are operated by DU 174 and / or other DUs of the C-BS 106A. N is an integer greater than 1. For example, the S-BS 104A and CU 172 perform additional inter-CU LTM preparation procedures 2, ..., N to prepare cells 2, ..., N, respectively. Each of the inter-CU LTM preparation procedures 2, ..., N is similar to procedure 582. In the inter-CU LTM preparation procedures 2, ..., N, the S-BS 104A receives LTM candidate configurations 2, ..., N, respectively, configuring cells 2, ..., N for LTM. As described above, S-BS 104A or C-BS106A assigns LTM IDs 2, ..., N to identify LTM candidate configurations 2, ..., N respectively. As described for CSI resource configuration 1, S-BS 104A can obtain CSI resource configurations 2, ..., N for cells 2, ..., N respectively. As described for CSI reporting configuration 1, S-BS 104A can obtain CSI reporting configurations 2, ..., N for cells 2, ..., N respectively. As described for RACH configuration 1, S-BS 104A can obtain RACH configurations 2, ..., N for cells 2, ..., N respectively. As described for TCI status configuration 1, S-BS 104A can obtain TCI status configurations 2, ..., N for cells 2, ..., N respectively. As described for LTM SSB configuration 1, S-BS 104A can obtain LTM SSB configurations 2, ..., N for cells 2, ..., N respectively. As described for PCI 1, S-BS 104A can obtain PCI 2, ..., N for cells 2, ..., N respectively. In some implementations, S-BS 104A can perform LTM configuration transfer procedures 2, ..., N with UE 102 to send to UE 102 a list consisting of {LTM ID 2, LTM candidate configuration 2, CSI resource configuration 2 (if obtained), TCI state configuration 2 (if obtained), RACH configuration 2 (if obtained), LTM SSB configuration 2 (if obtained), PCI 2 (if obtained)}, ..., {LTM ID N, LTM candidate configuration N, CSI resource configuration N, TCI state configuration N (if obtained), RACH configuration N (if obtained), LTM SSB configuration N (if obtained), PCI N (if obtained)}.Each of the LTM configuration passing procedures 2, ..., N is similar to procedures 394, 494 and / or LTM configuration passing procedure 1 (i.e., events 518 and 520). In other implementations, S-BS 104A includes this list in the first RRC reconfiguration message.

[0180] To simplify the following description, tuples 1, ..., N represent {LTM ID 1, LTM candidate configuration 1, CSI resource configuration 1 (if obtained), TCI state configuration 1 (if obtained), RACH configuration 1 (if obtained), LTM SSB configuration 1 (if obtained)}, ..., {LTM ID N, LTM candidate configuration N, CSI resource configuration N, TCI state configuration N (if obtained), RACH configuration N (if obtained), LTM SSB configuration N (if obtained)}, respectively. In some implementations, the S-BS104A includes tuples 1, ..., N in RRC reconfiguration messages 1, ..., N during the LTM configuration passing process 1, ..., N. RRC reconfiguration message 1 is the first RRC reconfiguration message 518. In some implementations, the S-BS 104A includes tuples 1, ..., N in the container IE (e.g., ...). LTM-Config IE In other implementations, CU 172 includes tuples 1, ..., N in the container IE 1, ..., N, and encloses the container IE 1, ..., N in the RRC reconfiguration messages 1, ..., N respectively. LTM-Config In IE) 1, and CU 172 includes container IE 1 in the first RRC reconfiguration message.

[0181] In other implementations, S-BS 104A and CU 172 perform procedure 582 to prepare one or more cells from cell 1, ..., N as LTM candidate cells for UE 102. In such implementations, as described for cell ID 1, S-BS 104A includes cell IDs 1, ..., N in the LTM candidate cells. Switching requests In message 505. In some implementations, upon receiving... Switching requests When a message is received, CU 172 determines or selects cells 1, ..., N as LTM candidate cells. M is a positive integer, and M ≤ N. In other implementations, CU 172 follows... Switching requestsThe message requests the preparation of cells 1, ..., N for LTM. CU 172 and DU 174 perform LTM preparation procedures 2, ..., M to prepare cells 2, ..., M as LTM candidate cells for UE 102, respectively. LTM preparation procedures 2, ..., M are similar to the procedure 590 performed by CU 172 and DU 174 to prepare cell 1. As a result of LTM preparation procedures 2, ..., M, CU 172 obtains LTM candidate configurations 2, ..., M for cells 2, ..., M, similar to obtaining LTM candidate configuration 1. As described for LTM candidate configuration 1, C-BS 106A can generate LTM candidate configurations 2, ..., M as a complete configuration, or generate incremental configurations based on the LTM reference configuration. CU 172 includes LTM candidate configurations 2, ..., M in... Switch request confirmation In some implementations, such as those described for LTM ID 1, CU 172 or S-BS 104A assigns LTM IDs 2, ..., M to identify LTM preparation processes 2, ..., M respectively. As described for LTM ID 1 and LTM candidate configuration 1, when CU 172 assigns LTM IDs 1, ..., M, CU 172 includes LTM IDs 1, ..., M with LTM candidate configurations 1, ..., M respectively. Switch request confirmation In the message.

[0182] In some implementations, such as those described for early synchronization information 1, CU 172 obtains early synchronization information 2, ..., M for cells 2, ..., M respectively. CU 172 includes the early synchronization information 2, ..., M... Switch request confirmation In some implementations, such as those described for CSI resource configuration 1, CU 172 or S-BS 104A obtains CSI resource configurations 2, ..., M for cells 2, ..., M respectively. When CU 172 obtains CSI resource configurations 2, ..., M, CU 172 includes CSI resource configurations 2, ..., M in... Switch request confirmation In the message.

[0183] In some implementations, such as those described for LTM SSB configuration 1, CU 172 or S-BS 104A obtains LTM SSB configurations 2, ..., M for cells 2, ..., M respectively. When CU 172 obtains LTM SSB configurations 2, ..., M, CU 172 includes LTM SSB configurations 2, ..., M in... Switch request confirmationIn the message, in some implementations, such as those described for PCI 1, CU 172 or S-BS 104A obtains PCI 2, ..., M for cells 2, ..., M respectively. When CU 172 obtains PCI 2, ..., M, CU 172 includes PCI 2, ..., M in... Switch request confirmation In the message.

[0184] In some implementations, CU 172 will include a list of the following items. Switch request confirmation The message contains: {Cell ID 1, LTM ID 1 (if obtained or optional), LTM candidate configuration 1, CSI resource configuration 1 (if obtained or optional), TCI status configuration 1 (if obtained or optional), early synchronization information 1 (if obtained or optional), LTM SSB configuration 1 (if obtained or optional), PCI 1 (if obtained or optional)}, ..., {Cell ID M, LTM ID M (if obtained or optional), LTM candidate configuration M, CSI resource configuration M (if obtained or optional), TCI status configuration M (if obtained or optional), early synchronization information M (if obtained or optional), LTM SSB configuration M (if obtained or optional), PCI M (if obtained or optional)}.

[0185] In some implementations, such as those described for PDCCH instruction information 1, CU 172 obtains PDCCH instruction information 2, ..., M for cells 2, ..., M respectively. In one implementation, CU 172 includes PDCCH instruction information 2, ..., M in... Switch request confirmation In another implementation, CU 172 includes PDCCH instruction information 2, ..., M in the early synchronization information 2, ..., M, respectively. S-BS 104A can retrieve this information from the early synchronization information 2, ..., M, or from... Switch request confirmation The message contains information such as RACH configuration 2, TCI status configuration 2 and / or PDCCH instruction information 2, ..., RACH configuration M, TCI status configuration M and / or PDCCH instruction information M.

[0186] In some implementations, the S-BS 104A can perform LTM configuration transfer procedures 2, ..., M with the UE 102 to send tuples 2, ..., M to the UE 102 respectively. In some implementations, the S-BS 104A includes tuples 1, ..., M in containers IE (e.g., ...). LTM-Config IEIn some implementations, S-BS 104A includes tuples 1, ..., M in the first RRC reconfiguration message, and includes containers IE 1, ..., M in the RRC reconfiguration messages 1, ..., M respectively. LTM- Config In IE), the container IE 1 is included in the first RRC reconfiguration message.

[0187] In some implementations, the S-BS 104A can include the measurement results 1, ..., N for cells 1, ..., N respectively. Switching requests In the message, S-BS 104A receives measurement results from UE 102. C-BS 106A can select or determine cell 1, ..., M based on measurement results 1, ..., N. In other implementations, C-BS 106A can select or determine cell 1, ..., M based on one or more other factors (e.g., the capacity or load of cell 1, ..., N and / or the maximum number of LTM candidate cells). In one implementation, the maximum number is included... Switching requests The message states that in another implementation, the maximum quantity is the predetermined quantity.

[0188] In some implementations, S-BS 104A (e.g., the CU of S-BS 104A) or CU 172 generates a first security configuration (i.e., a single security configuration) for LTM candidate cells 1, ..., M of UE 102 or for LTM candidate configurations 1, ..., M of UE 102. In some implementations, S-BS 104A indicates the LTM candidate configurations 1, ..., M associated with the first security configuration in the first RRC reconfiguration message 518 and / or the RRC reconfiguration message 1, ..., M in the LTM configuration transfer process 2, ..., M. To indicate this association, S-BS 104A may include the first security configuration and a first security configuration ID identifying the first security configuration in container IE 1, and in a tuple (e.g., LTM-Candidate IEThe LTM candidate cells 1, ..., M include a first security configuration ID. Based on the first security configuration ID, UE 102 identifies that UE 102's LTM candidate cells 1, ..., M or LTM candidate configurations 1, ..., M share the same security configuration (i.e., the first security configuration). In some implementations, S-BS 104A includes a service security configuration ID for the serving cell or associated with the serving cell in the first RRC reconfiguration message or container IE 1. In some implementations, the service security configuration ID indicates (e.g., identifies) the first security key, the first security algorithm, and / or security parameters used to derive the first security key associated with the serving cell. The service security configuration ID (i.e., the value) is different from the first security configuration ID (i.e., the value). Because the first security configuration ID is different from the service security configuration ID, UE 102 determines the security configuration change for the LTM cell handover from the serving cell to cell 1 and applies the first security configuration as described above to communicate with C-BS 106A via cell 1.

[0189] Subsequently, UE 102 can receive a 540 LTM cell handover command from C-BS 106A, instructing UE 102 to perform an LTM cell handover to cell 2. In this case, as described for an LTM cell handover to cell 1, UE 102 responds to the LTM cell handover command and performs an LTM cell handover to cell 2. Because UE 102 recognizes that the same security configuration (i.e., the first security configuration) applies to both cell 1 and cell 2 (or LTM candidate configuration 1 and LTM candidate configuration 2), UE 102 uses or continues to use the second security key to communicate with C-BS 106A on cell 2. If UE 102 uses the second security algorithm to communicate with C-BS 106A on cell 1, then UE 102 uses or continues to use the second security algorithm to communicate with C-BS 106A on cell 2. Otherwise, if UE 102 uses the first security algorithm to communicate with C-BS 106A on cell 1, then UE 102 uses or continues to use the first security algorithm to communicate with C-BS 106A on cell 2. Similarly, C-BS 106A performs similar actions to communicate with UE 102 as described above. In the above description, "M" can be changed to "N".

[0190] In some implementations, S-BS 104A may perform an inter-CU LTM preparation procedure for UE 102 with another, second C-BS, to obtain an LTM candidate configuration and a second security configuration for the LTM candidate cell (e.g., a cell operated by the second C-BS), similar to procedure 582. S-BS 104A sends the LTM candidate configuration and the second security configuration to UE 102, similar to events 518 and 520. As described with respect to the first security information, S-BS 104A may send second security information to the second C-BS. The examples and implementations described with respect to the first security configuration and the first security information can be applied to the second security configuration and the second security information, respectively. In some implementations, the second security information and / or the second security configuration differs from the first security information and / or the first security configuration.

[0191] In some implementations, S-BS 104A can include CSI resource configurations 1, ..., N in a container IE instead of in a tuple, where N is a positive integer.

[0192] Next reference Figure 6A In scenario 600A, base station 104B operates as the MN, base station 106A operates as a candidate SN (C-SN), and base station 104A operates as a serving or source SN (S-SN). C-SN 106A includes CU 172 and DU 174. MN104B may include CU and DU (…). Figure 6A (not shown in the image), similar to Figure 3 BS 104A in S-SN 104A. S-SN 104A may include CU and DU ( Figure 6A (Not shown in the image), similar to C-SN 106A. Scene 600A is similar to Scene 500, except that Scene 600A is an SN scene, while Scene 500 is an MN scene.

[0193] Initially, UE 102 in the DC communicates with MN 104B and S-SN 104A 602. In some implementations, UE 102 is configured to communicate with the DU of S-SN 104A on cell 124A using a serving DU, and UE 102 is configured to communicate with the CU of S-SN 104A via the DU of S-SN 104A using a serving CU, similar to event 302. In some implementations, UE 102 in the DC may transmit 602 UL PDUs and / or DL ​​PDUs to MN 104B and / or S-SN 104A via radio bearers, which may include SRBs and / or DRBs. MN 104B and / or S-SN 104A can configure these radio bearers for UE 102. UE 102, located in the DC, transmits 602 UL PDUs and / or DL ​​PDUs with S-SN 104A on a secondary cell group (SCG) (i.e., SCG radio resources), which is configured by S-SN 104A as the SN for communication with UE 102. UE 102, also located in the DC, transmits UL PDUs and / or DL ​​PDUs with MN 104B on a primary cell group (MCG) (i.e., MCG radio resources) according to an 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, MN 104B configures an MCG that includes at least one serving cell (e.g., cell 124B and / or other cells) operated by MN 104B. In the serving DU configuration, S-SN 104A configures an SCG that includes at least one serving cell (e.g., cell 124A and / or other cells) operated by S-SN 104A. In some implementations, the MN configuration includes multiple configuration parameters, and UE 102 receives these configuration parameters from MN 104B in one or more RRC messages. (See reference...) Figure 3 As described, the service DU configuration includes multiple configuration parameters. In some implementations, UE 102 receives these configuration parameters in one or more RRC messages from S-SN 104A, for example, via MN 104B and / or on an SRB (e.g., SRB3) configured by MN 104B or S-SN 104A to exchange RRC messages between UE 102 and S-SN 104A.

[0194] For reference Figures 3 to 5 As described, UE 102 uses at least one first master security key and at least one first master security algorithm to perform security protection on data transmitted with MN 104B. (See reference...) Figures 3 to 5As described, MN 104B uses at least one first master security key and at least one first master security algorithm to perform security protection on data transmitted with UE 102. Depending on the implementation, the first master security key and the first master security algorithm used by UE 102 and MN 104B may be the same or different.

[0195] For reference Figure 3 and Figure 4 As described, UE 102 uses at least one first secondary security key and at least one first secondary security algorithm to perform security protection on data transmitted with S-SN 104A. For example, regarding... Figure 3 and Figure 4 As described, the S-SN104A uses at least one first secondary security key and at least one first secondary security algorithm to perform security protection on data transmitted with the UE 102. Depending on the implementation, the first secondary security key and the first secondary security algorithm used by the UE 102 and the S-SN 104A may be the same or different.

[0196] When communicating with UE 102 located in the same DC as MN 104B and S-SN 104A, S-SN 104A may perform an in-CU LTM configuration procedure 696 with UE 102, similar to procedures 396 and / or 496. When communicating with UE 102 located in the same DC as MN 104B and S-SN 104A, S-SN 104A may perform an in-CU LTM procedure 680 with UE 102, similar to procedures 380 and / or 480. In procedure 696 or 680, the CU of S-SN 104A may send one or more RRC reconfiguration messages to UE 102 via SRB3, each RRC reconfiguration message including one or more LTM candidate configurations, similar to procedures 394 or 494. Alternatively, the CU of S-SN 104A may send one or more RRC reconfiguration messages to UE 102 via MN 104B, each RRC reconfiguration message including one or more LTM candidate configurations. In response to each of the RRC reconfiguration messages, UE 102 sends an RRC reconfiguration complete message to S-SN 104A via MN 104B.

[0197] When communicating with MN 104B and S-SN 104A under DC, UE 102 can, for example, send at least one measurement report (604A) to S-SN 104A directly via SRB3, similar to events 304 / 306, 404 / 406, and 504. Alternatively, UE 102 can send the measurement report to MN 104B. MN 104B generates at least one SN message including the measurement report and sends the SN message to CU 172. In one implementation, the SN message includes... RRC transmissionMessages and / or SN Modification Request The S-SN 104A (e.g., the CU of the S-SN 104A) generates a measurement configuration that enables the UE 102 to send measurement reports, and sends the measurement reports to the UE 102 directly (e.g., via the S-DU of the S-SN 104A) or via the MN 104B.

[0198] After receiving one or more measurement reports from UE 102 (e.g., in response to this), S-SN 104A (e.g., the CU of S-SN 104A) determines a first cell (e.g., cell 126A) to be prepared as an LTM candidate cell for UE 102. In response to this determination, S-SN 104A generates an SN request message (first SN request message) including a first cell ID (e.g., cell ID 1) of the first cell (e.g., cell 1) and / or an indication of a target SN ID for C-SN 106A. In some implementations, the SN request message includes an LTM indicator indicating that the SN request message relates to an LTM for the first cell ID. S-SN 104A sends a 603 SN request message to MN 104B. Upon receiving the SN request message (e.g., in response to this), MN 104B sends SN request message 605, including the first cell ID (first SN request message), to CU 172 to request CU 172 to prepare the first cell as an LTM candidate cell for UE 102. In response to the SN request message, CU 172 and DU 174 perform LTM preparation procedure 690 to prepare the first cell as an LTM candidate cell for UE 102, similar to procedures 390, 490, or 590. In procedure 690, CU 172 sends a first CU-DU message including the first cell ID to DU 174 to request preparation of the first cell, similar to event 308. In response, CU 172 can receive a first DU-CU message including LTM DU configuration 1 from DU 174, similar to event 310. CU 172 generates a first LTM candidate configuration (LTM candidate configuration 1). In response to the SN request message, CU 172 sends a 607 SN request confirmation message (first SN request confirmation message) to MN 104B, which includes the first LTM candidate configuration. In some implementations, CU 172 includes the first cell ID in the SN request confirmation message to indicate that the first LTM candidate configuration is provided for or associated with the first cell (ID). MN 104B sends a 609A SN confirmation message (e.g., first SN confirmation message) to S-SN 104A, which includes the first LTM candidate configuration. In some implementations, MN 104B includes the first cell ID in the SN confirmation message to indicate that the first LTM candidate configuration is provided for or associated with the first cell (ID).

[0199] Events 603, 605, 690, 607, and 609A are in Figure 6A This is collectively referred to as the SN-initiated SN-inter-SN LTM preparation process 698A.

[0200] In some implementations, the SN requirement message and the SN confirmation message are respectively SN Change Requirements Messages and SN Change Certificate Reality Message. In other implementations, the SN requires the message and the SN confirms the message, respectively. SN Modification Requirements Messages and SN Modification Certificate Reality Messages. In some implementations, the SN request message and the SN request acknowledgment message are respectively... SN Add Request Messages and SN Add Add confirmation request Messages. In other implementations, the SN request message and the SN request confirmation message are respectively SN Modification Request Messages and SN modification request confirmation information.

[0201] In some implementations, the SN request message includes the DU ID of the S-DU of S-SN 104A. In this case, MN104B may include the DU ID in the SN request message, and CU 172 may include the DU ID in the first CU to DU message. In other implementations, the SN request message includes the first BS ID of S-SN 104A. In some implementations, MN104B may include the first BS ID in the SN request message. When the first BS ID is received, CU 172 may include the first BS ID in the first CU to DU message. In some implementations, MN 104B may include its second BS ID in the SN request message. When the second BS ID is received, 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.

[0202] In some implementations, such as the reference Figure 3 , Figure 4 and Figure 5 As described, CU 172 requests the LTM reference DU configuration in process 690, while in other implementations, CU 172 requests the LTM reference DU configuration. In some implementations, such as reference Figure 3 , Figure 4 and Figure 5As described, DU 174 sends the LTM reference DU configuration to CU 172 in process 690. In other implementations, DU 174 does not send the LTM reference DU configuration to CU 172. In some implementations, S-SN 104A (e.g., the CU of S-SN 104A) can obtain the LTM reference configuration, such as a reference... Figure 3 and Figure 4 As described. In other implementations, S-SN104A can be from MN 106B during another SN-to-LTM preparation process as described above and below. Figure 6A (Not shown in the image) Receives the LTM reference configuration. If S-SN 104A obtains the LTM reference configuration, S-SN 104A may include the LTM reference configuration (the LTM reference configuration generated by S-SN) in the SN request message. Then, MN 104B includes the LTM reference configuration in the SN request message. Alternatively, S-SN 104A determines to request or cause C-SN 106A to provide a complete LTM candidate configuration, such that S-SN 104A does not send the LTM reference configuration to C-SN 106A. If S-SN 104A does not obtain the LTM reference configuration, S-SN 104A does not include the LTM reference configuration in the SN request message. If the SN request message includes the LTM reference configuration, MN 104B includes the LTM reference configuration in the SN request message. Otherwise, if the SN request message does not include the LTM reference configuration, MN 104B may not include the LTM reference configuration in the SN request message.

[0203] If the SN request message includes the LTM reference configuration as described above, then CU 172 may include the LTM reference configuration in the first CU-DU message. Alternatively, CU 172 may extract the LTM reference DU configuration from the LTM reference configuration and include that LTM reference DU configuration in the first CU-DU message. Otherwise, if the SN request message does not include the LTM reference configuration, then in some implementations, CU 172 may refer to... Figure 3 The description refers to receiving an LTM reference DU configuration from DU 174. In other implementations, CU 172 does not receive an LTM reference DU configuration from DU 174. If CU 172 receives an LTM reference DU configuration (e.g., in a first DU-to-CU message), then CU 172 generates an LTM reference configuration (an LTM reference configuration generated by the C-SN) that includes that LTM reference DU configuration. CU 172 may include an LTM reference CU configuration (an LTM reference CU configuration generated by the candidate CU (C-CU)). Otherwise, if CU 172 does not receive an LTM reference DU configuration as described above... Figure 3If an LTM reference DU configuration is received from DU 174 as described, then CU 172 does not generate an LTM reference configuration. Alternatively, CU 172 generates an LTM reference configuration (C-SN generated LTM reference configuration) that includes only the LTM reference CU configuration generated by C-CU. In the case where CU 172 generates an LTM reference configuration (C-SN generated LTM reference configuration), CU 172 includes the C-SN generated LTM reference configuration in the SN request confirmation message.

[0204] In some implementations, if LTM DU configuration 1 is a complete configuration, CU 172 generates LTM candidate configuration 1 as a complete configuration. CU 172 may include a complete configuration indication (e.g., a BS-to-BS interface protocol field / IE) in the SN request confirmation message to indicate that LTM candidate configuration 1 is a complete configuration. In some implementations, the BS-to-BS interface protocol is the 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 the impact on non-LTM configurations. In other implementations, the complete configuration indication is an existing field / IE defined in 3GPP specification 38.423. Otherwise, if LTM DU configuration 1 is an incremental configuration, CU 172 generates LTM candidate configuration 1 as an incremental configuration. CU 172 may exclude the complete configuration indication from the SN request confirmation message to indicate that LTM candidate configuration 1 is an incremental configuration. Alternatively, CU 172 may include an incremental configuration indication (e.g., a BS-to-BS interface protocol field / IE) in the SN request confirmation message to indicate that LTM candidate configuration 1 is an incremental configuration. In some implementations, the BS-to-BS interface protocol is the Xn application protocol defined in 3GPP specification 38.423. In some implementations, the incremental configuration indication is a dedicated field / IE (e.g., LTM-specific) to reduce or eliminate the impact on non-LTM configurations. In other implementations, the incremental configuration indication is an existing field / IE defined in 3GPP specification 38.423. In some implementations, the BS-to-BS interface protocol field / IE has two values ​​(i.e., a first value and a second value). The BS-to-BS interface protocol field / IE may have a first value to indicate a complete configuration, and the BS-to-BS interface protocol field / IE may have a second value to indicate an incremental configuration.

[0205] In some implementations, the S-SN 104A is pre-configured with a CSI resource configuration (e.g., (LTM) CSI resource configuration 1) and / or an LTM SSB configuration (LTM SSB configuration 1) for the first cell. In still other implementations, the CU 172 receives the CSI resource configuration and / or LTM SSB configuration from the OAM (Operation, Administration, and Maintenance) node. In yet another implementation, the S-SN 104A receives the CSI resource configuration and / or LTM SSB configuration from the CU 172. For example, the CU 172 includes the CSI resource configuration and / or LTM SSB configuration in the SN request confirmation message. In this case, the MN 104B may include the CSI resource configuration and / or LTM SSB configuration in the SN confirmation message. In some implementations, the CU 172 includes the PCI of the first cell in the SN request confirmation message. In this case, the MN 104B may include the PCI of the first cell in the SN confirmation message. To prepare the first cell as a candidate LTM cell for UE 102, the CU and S-DU of S-SN 104A perform the LTMCSI report configuration and / or LTM ID configuration procedures. Figure 6A (Not shown in the diagram), similar to procedures 392 or 492. During the LTM CSI report configuration and / or LTM ID configuration process, the CU of S-SN 104A sends the CSI resource configuration and / or LTM SSB configuration to the S-DU of S-SN 104A. In response, the CU of S-SN 104A receives one or more CSI report configurations of UE 102 from the S-DU of S-SN 104A. In some implementations, S-SN 104A receives a second service DU configuration including the CSI report configuration.

[0206] In some implementations, CU 172 receives early synchronization information and / or PDCCH instruction information of the first cell from DU 174, as shown in the reference. Figure 5 As described. In some implementations, early synchronization information includes RACH configuration (e.g., RACH configuration 1) and / or at least one TCI state configuration (e.g., TCI state configuration 1). CU 172 includes early synchronization information and / or PDCCH instruction information in the SN request confirmation message. MN 104B includes early synchronization information and / or PDCCH instruction information in the SN confirmation message.

[0207] In some implementations, CU 172 assigns an LTM ID (e.g., LTMID 1) to identify the first LTM candidate configuration and includes the LTM ID and / or its associated (or mapped) cell ID in the SN request confirmation message. MN 104B includes the LTM ID and / or its associated (or mapped) cell ID in the SN confirmation message. In other implementations, S-SN 104A assigns an LTM ID (e.g., LTM ID 1) to identify the first LTM candidate configuration. In still other implementations, MN 104B assigns an LTM ID (e.g., LTM ID 1) to identify the first LTM candidate configuration. In such cases, MN 104B may include the LTM ID in the SN confirmation message. After receiving or assigning the LTM ID, the CU of S-SN 104A sends the LTM ID and the first cell ID to the S-DU during an LTM ID configuration process similar to procedures 390, 392, or 492.

[0208] Upon receiving the SN confirmation message (e.g., in response to this), S-SN 104A (e.g., the CU of S-SN 104A) performs the 694A LTM ​​configuration transfer procedure with UE 102 to send the LTM ID and LTM candidate configuration to UE 102. In some implementations, S-SN 104A sends {LTM ID, LTM candidate configuration} as a tuple (e.g., tuple 1) in the first RRC reconfiguration message during procedure 694A. Depending on the implementation, such as for Figure 3 and Figure 4 As described, S-SN 104A may include the LTM reference configuration, CSI report configuration, CSI resource configuration, RACH configuration, TCI status configuration, LTM SSB configuration, and / or the PCI of the first cell in a tuple sent to the first RRC reconfiguration message and / or other RRC reconfiguration messages to UE 102. S-SN 104A includes the LTM ID in the first RRC reconfiguration message or other RRC reconfiguration messages to indicate that the CSI resource configuration, RACH configuration, TCI status configuration, LTM SSB configuration, and / or the PCI of the first cell are associated with the first cell. For example, S-SN 104A includes the CSI resource configuration, RACH configuration, TCI status configuration, LTM SSB configuration, and / or the PCI of cell 1 in a tuple. In another example, S-SN 104A includes this tuple in other RRC reconfiguration messages. In response to each of the other RRC reconfiguration messages, UE 102 sends an RRC reconfiguration complete message to CU 172 via S-DU 174A.

[0209] In some implementations, the MN 104B (e.g., the CU of the MN 104B) includes a first (MN to SN) LTM security configuration list in the SN request message. In some implementations, the first (MN to SN) LTM security configuration list includes a list of tuples 1, ..., L, where L is a positive-zero integer. Tuples 1, ..., L include specific {RAN-level security key (e.g., S-NG-RAN node security key) 1 and / or SK counter L}, ..., {RAN-level security key (e.g., S-NG-RAN node security key) L and / or SK counter L}. In some implementations, the MN 104B includes the security capabilities of the UE 102 in the SN request message.

[0210] In some implementations, the MN 104B (e.g., the CU of the MN 104B) generates a first UE LTM security configuration list based on the first MN-SN LTM security configuration list and includes the first UE LTM security configuration list in the SN confirmation message. In some implementations, the S-SN 104A includes the first UE LTM security configuration list in a container IE that includes tuple 1 (e.g., LTM-Config In the first RRC reconfiguration message, the container IE is included in the first UE LTM security configuration list. In other implementations, S-BS 104A includes the first UE LTM security configuration list in tuple 1.

[0211] In some implementations, the first UE LTM security configuration list includes at least a portion of the first MN to SN LTM security configuration lists. For example, the first UE LTM security configuration list includes a list of SK counters (e.g., SK counter 1, ..., L) included in the first MN to SN LTM security configuration lists, but does not include any RAN-level security keys in the first MN to SN LTM security configuration lists. In some implementations, the first LTM candidate configuration, LTM reference configuration, or first UE LTM security configuration configures at least one second security algorithm. In some implementations, CU 172 determines the second security algorithm based on security capabilities. In some implementations, the second security algorithm includes encryption algorithms and / or integrity algorithms, which may be the same as or different from the first security algorithm.

[0212] In some implementations, if the SN requires the message to include a full configuration indication to indicate that LTM candidate configuration 1 is a full configuration, then the S-SN 104A includes the full configuration indication (e.g., the RRC field / IE) in the first RRC reconfiguration message to indicate that LTM candidate configuration 1 is a full configuration. Otherwise, if the SN requires the message to exclude the full configuration indication, or includes an incremental configuration indication to indicate that LTM candidate configuration 1 is an incremental configuration, then the S-SN 104A excludes or does not include the full configuration indication (e.g., the RRC field / IE) in the first RRC reconfiguration message to indicate that LTM candidate configuration 1 is an incremental configuration.

[0213] If the SN confirmation message includes PDCCH instruction information (PDCCH instruction information 1), then S-SN 104A can send a 650A PDCCH instruction to UE 102 based on the PDCCH instruction information. If S-SN 104A is a distributed base station, then the CU of S-SN 104A can send the PDCCH instruction information to the S-DU of S-SN 104A, and the S-DU can send a 650A PDCCH instruction to UE 102. For example, S-SN 104A or its S-DU sends a 650A PDCCH instruction to UE 102, including the PDCCH instruction information. In some implementations, S-SN 104A or its S-DU can determine whether to send the PDCCH instruction based on (e.g., in response to) measurement report 624A. In some implementations, the S-SN 104A or S-DU can determine the SSB index included in the PDCCH command based on the L1 Measurement Report 624A and / or CSI resource configuration, CSI report configuration, and / or LTM SSB configuration. In some implementations, the S-DU or S-SN 104A includes LTM ID 1 in the PDCCH command to indicate the first cell. UE 102 uses the RACH configuration and / or PDCCH command information to send a 652 RA preamble to DU 174 on the first cell. The S-DU or S-SN 104A derives the TA value based on the RA preamble. DU 174 sends a 656 command including the TA value to CU 172. DU-CU TA Information Transmission Message. CU 172 sends 657 including the TA value to MN 104B (e.g., the CU of MN 104B). CU-CU TA Information Transmission Message. MN104B sends 658 including the TA value to S-SN 104A. CU-CU TA Information TransmissionIn some implementations, DU 174 includes cell ID 1, RA preamble index, RA-RNTI, and / or the DU ID of the S-DU of S-SN 104A in message 656. DU 174 may additionally include the first BS ID and / or the second BS ID in message 656. In some implementations, CU 172 includes cell ID 1, RA preamble index, RA-RNTI, and / or the DU ID of the S-DU in message 657. In some implementations, CU 172 may additionally include the first BS ID and / or the second BS ID in message 657. Then, MN 104B includes cell ID 1, RA preamble index, RA-RNTI, and / or the DU ID of the S-DU in message 658. In some implementations, MN 104B may additionally include the first BS ID and / or the second BS ID in message 658.

[0214] In some implementations, CU 172 determines the address (e.g., IP address) of MN 104B or its CU based on a second BS ID. Therefore, CU 172 sends message 657 to MN 104B based on the address. In some implementations, MN 104B determines the address (e.g., IP address) of S-SN 104A or its CU based on a first BS ID. In other implementations, MN 104B determines the address (e.g., IP address) of S-SN 104A or its CU based on the DU ID of S-DU of S-SN 104A. Through these implementations, MN 104B transmits message 658 to S-SN 104A or its CU based on the address. CU-CU TA Information Transmission information.

[0215] In response to, for example, a command to UE 102 to perform an LTM cell handover to a first cell based on L1 measurement reports 624A and / or 654A, S-DU or S-SN 104A sends an LTM cell handover command 626A, including LTM ID 1, to UE 102. In response to the LTM cell handover command, UE 102 may cease communication on the serving cell. In response to the LTM cell handover command, UE 102 accesses the first cell 632. When UE 102 is detected in event 632, DU 174 sends an access success message 634 to CU 172. UE 102 sends an RRC reconfiguration complete message 636A to DU 174 during or after access 632. DU 174 then sends a DU-CU message 638, including the RRC reconfiguration complete message, to CU 172. In some alternative implementations, UE 102 sends the RRC reconfiguration complete message to C-SN 106A via MN 104B instead of via DU 174.

[0216] In some implementations, UE 102 derives at least one second security key based on a first UE LTM security configuration list (e.g., SK counter 1). In some implementations, UE 102 derives a new SN key (e.g., a new SK counter 1) based on the first UE LTM security configuration list. gNB The UE 102 derives the second security key from the new SN key. In some implementations, if the UE 102 receives the second security algorithm for the first cell (i.e., the LTM candidate cell), the UE 102 derives the second security key based on the new SN key and the second security algorithm. Otherwise, if the UE 102 does not receive the second security algorithm, the UE 102 derives the second security key based on the new SN key and the first security algorithm. In some implementations, the UE 102 derives the second security key in response to receiving the 626A LTM ​​cell handover command. In other implementations, the UE 102 derives the second security key after receiving the first LTM security configuration list and before receiving the 626A LTM ​​cell handover command.

[0217] UE 102 applies a second security key to communicate with CU 172 in events 636 and 640. If UE 102 receives the second security algorithm as described above, UE 102 applies the second security key and the second security algorithm to communicate with CU 172 in events 636 and 640. Otherwise, if UE 102 does not receive the second security algorithm, UE 102 applies the second security key and the first security algorithm to communicate with CU 172 in events 636 and 640. In some implementations, the second security key includes an integrity key for integrity protection of control plane data packets (e.g., RRC messages in events 636 and / or 640). In other implementations, the second security key includes an encryption key for encrypting / decrypting control plane data packets (e.g., RRC messages in events 636 and / or 640). In some implementations, the security key includes an integrity key for protecting the integrity of user plane data packets (e.g., data packets transmitted via the DRB) in event 640. In other implementations, the security key includes an encryption key for encrypting / decrypting user plane data packets (e.g., data packets transmitted via the DRB) in event 640. UE 102 stops using the first security key to communicate with CU 172.

[0218] In some implementations, CU 172 derives at least one second security key based on the first MN-to-SN LTM security configuration list (e.g., RAN-level security key 1 and SK counter 1). In some implementations, CU 172 derives a new SN key (e.g., a new SK counter 1) based on the first MN-to-SN LTM security configuration list. gNB The CU 172 then derives the second security key from the new SN key. In some implementations, if the CU 172 sends the second security algorithm for the first cell (i.e., the LTM candidate cell) to the UE 102, the CU 172 derives the second security key based on the new SN key and the second security algorithm. Otherwise, if the CU 172 does not send the second security algorithm to the UE 102, the CU 172 derives the second security key based on the new SN key and the first security algorithm.

[0219] In some implementations, CU 172 derives a second security key in response to receiving a 627A CU-to-CU cell handover notification message, a 634 access success message, or a 638 DU-to-CU message. In other implementations, CU 172 derives the second security key after receiving the first MN-to-SN LTM security configuration list, and before receiving the 628 CU-to-CU cell handover notification message, before receiving the 634 access success message, or before receiving the 638 DU-to-CU message. CU 172 applies the second security key to communicate with UE 102 in events 636 and 640. In some implementations, the second security key includes an integrity key for integrity protection of control plane data packets (e.g., RRC messages in events 636 and / or 640). In other implementations, the second security key includes an encryption key for encrypting / decrypting control plane data packets (e.g., RRC messages in events 636 and / or 640). In some implementations, the second security key includes an integrity key for protecting the integrity of user plane data packets (e.g., data packets transmitted via the DRB) in event 640. In still other implementations, the second security key includes an encryption key for encrypting / decrypting user plane data packets (e.g., data packets transmitted via the DRB) in event 640. In some implementations, the second security key used by CU 172 is the same as the second security key used by UE 102.

[0220] In some implementations, UE 102 may perform an RA procedure in event 632 to access the first cell. The RA procedure may be a four-step RA procedure or a two-step RA procedure. The RA procedure may be a CBRA procedure or a CFRA procedure. In some implementations, S-SN 104A includes a first set of LTM CFRA configuration parameters in the LTM cell handover command to configure UE 102 to perform a CFRA procedure to access the first cell. UE 102 performs the CFRA procedure using the first set of LTM CFRA configuration parameters. In some implementations, as described for procedure 490, DU 174 includes the first set of LTM CFRA configuration parameters in the first DU to CU message of procedure 690. CU 172 then includes the first set of LTM CFRA configuration parameters in the SN request confirmation message. In some implementations, as described for procedure 490, DU 174 includes at least one additional set of LTM CFRA configuration parameters in the first DU to CU message. CU 172 then includes the additional group LTM CFRA configuration parameters in the SN request confirmation message.

[0221] In some implementations, such as for Figure 4As described in C-DU 174B, DU 174 configures a first group and / or an additional group for UL (i.e., NUL) or SUL and indicates these configurations in a first DU to CU message. When the first group and / or the additional group is configured for either UL or SUL, CU 172 includes a single UL / SUL indicator in the SN request confirmation message, indicating that the first group and / or the additional group is configured for either UL or SUL. When the first group and / or the additional group is configured for UL, CU 172 includes the first group and / or the additional group in a first field / IE in the SN request confirmation message. When the first group and / or the additional group is configured for SUL, CU 172 includes the first group and / or the additional group in a second field / IE in the SN request confirmation message. In this case, the first field / IE and the second field / IE are defined for UL and SUL, respectively.

[0222] In some implementations, such as for Figure 4 As described in C-DU 174B, DU 174 configures a first group for one of UL and SUL, and an additional group for the other of UL or SUL, indicating these configurations in the first DU to CU message. In this case, CU 172 sets the UL / SUL indicator in the first group to a value indicating one of UL or SUL, and sets the UL / SUL indicator in the additional group to a value indicating the other of UL or SUL. Alternatively, CU 172 includes the first group and the additional group in one of the first field / IE and the other in the second field IE, respectively, in the SN request confirmation message.

[0223] Upon receiving a 634 Access Success Message, a 638 DU to CU Message, or an RRC Reconfiguration Complete Message, C-SN 106A communicates 640 with UE 102, which is in the same DC as MN 104B and C-SN 106A, according to a first LTM candidate configuration and / or an LTM reference configuration. In some implementations, UE 102 includes LTM ID 1 in the RRC Reconfiguration Complete Message 636A to indicate that UE 102 applies the first LTM candidate configuration. Based on LTM ID 1, CU 172 identifies the first LTM candidate configuration and / or the LTM reference configuration. In other implementations, CU 172 is based on the LTM ID 1 included in the first LTM candidate configuration and / or the LTM reference configuration. Connection successful The first cell ID in message 634 is used to identify the first LTM candidate configuration and / or LTM reference configuration. In this implementation, CU 172 maintains or stores the association information between the first cell ID and the first LTM candidate configuration and / or the LTM reference configuration. When CU 172... Connection successfulWhen the first cell ID is received in the message, CU 172 identifies the first LTM candidate configuration and / or LTM reference configuration based on the first cell ID and associated information.

[0224] In some implementations, if the S-DU or S-SN 104A receives the TA value as described above, the S-DU or S-SN 104A may include the TA value in the LTM cell handover command. In some implementations, the S-DU or S-SN 104A includes a first TCI state ID in the LTM cell handover command. The first TCI state ID indicates the first TCI state configuration in the TCI state configuration.

[0225] In response to the confirmation command UE 102 to perform LTM cell handover or send the 626A LTM ​​cell handover command, the S-DU of S-SN 104A sends a message to the CU of S-SN 104A. DU-CU cell handover notification The message instructs UE 102 to perform an LTM cell handover to the first cell. In response to receiving... DU-CU cell handover notification Message: The CU of S-SN 104A sends a 627A signal to MN 104B. CU-CU cell handover notification The message instructs UE 102 to perform or be performing an LTM cell handover to the first cell. In response, MN 104B sends a 628 message to CU 172. CU-CU cell handover notification The message instructs UE 102 to perform or be performing an LTM cell handover to the first cell. In response, CU 172 sends 630 to DU 174. CU-DU Cell Handover Notification The message instructs UE 102 to perform or be performing an LTM cell handover to the first cell. In some implementations, S-SN 104A in CU-CU cell handover notification Message 627A includes the first TCI state ID. In this case, MN 104B is... CU-CU cell handover notification Message 628 includes the first TCI status ID. Then, CU 172 in... CU-DU Cell Handover Notification The message includes a first TCI state ID. UE 102 and DU 174 identify the first TCI state configuration in the TCI state configuration based on the first TCI state ID and apply the first TCI state configuration to transmit UL and / or DL ​​transmissions in events 632, 636A, and / or 640. In other implementations, where 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 S-SN 104A in... DU-CU cell handover notificationThe message and / or LTM cell handover command includes a first TCI state ID for DL ​​and a second TCI state ID for UL, which identify the first and second TCI state configurations in the TCI state configuration. The S-SN104A's CU responds to... DU-CU cell handover notification The message was subsequently sent to MN 104B. CU-CU cell handover notification The message includes a first TCI status ID and a second TCI status ID. MN 104B includes the first and second TCI status IDs in the message to CU 172. CU-CU cell handover notification In the message. Then, CU 172 includes the first TCI status ID and the second TCI status ID in the message sent to DU 174. CU-DU Cell Handover Notification In the message, 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. UE 102 applies the first TCI state configuration and the second TCI state configuration to transmit DL and UL transmissions with DU 174 in events 632, 636A, and / or 640, respectively. 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. DU 174 applies the first and / or second TCI state configurations to transmit DL and / or UL transmissions with UE 102 in events 632, 636A, and / or 640, respectively.

[0226] In some implementations, after determining that UE 102 performs an LTM cell handover or sends a 626A LTM ​​cell handover command (e.g., in response to this), S-SN 104A sends one or more 631 commands to MN 104B. Early state transition Each early state transition message includes a DL COUNT value for the DRB or a DISCARD DL COUNT value. UE 102 and S-SN 104A transmit 602 data to each other through this DRB. MN 104B sends one or more messages to CU 172. Early state transition Each early state transition message includes a DL COUNT value for the DRB or a DISCARD DL COUNT value, through which UE 102 and S-SN 104A transmit 602 data to each other.

[0227] In some implementations, upon receiving 634 Connection successfulUpon receiving either a 638 DU to CU message or an RRC reconfiguration complete message, CU 172 sends a 639 LTM success message to MN 104B (e.g., the CU of MN 104B) to indicate that the LTM cell handover has been successfully completed. In some implementations, the LTM success message is... SN Modification Requirements The message is either a BS-to-BS access success message. In some implementations, CU 172 includes the first cell ID in the LTM success message. In other implementations, CU 172 does not send a BS-to-BS message to MN 104B (e.g., the CU of MN 104B) to indicate successful LTM cell handover. In some implementations, after receiving the LTM success message or receiving the RRC reconfiguration completion message from UE 102 (e.g., in response to this), MN 104B may send an SN message to S-SN 104A (e.g., ...). Figure 6C (As shown in event 645). The SN message can indicate that the LTM cell handover has been successfully completed, instruct S-SN 104A to suspend communication with UE 102, or instruct S-SN 104A to release the UE context and resources configured for UE 102. MN 104B can include the first cell ID in the SN message. In some implementations, the SN message is... SN Modification Request information, SN release request Messages, SN access success messages, etc.

[0228] In some implementations, the UE 102 determines whether to execute LTM cell handover, sends the 626A LTM ​​cell handover command, and receives the command from the S-DU. DU-CU cell handover notification Upon receiving a message or an SN message (e.g., in response to this), S-SN104A (e.g., the CU of S-SN 104A) sends 641 to MN 104B. SN state transition The message includes the DL COUNT value and / or UL COUNT value for the DRB, through which UE 102 and S-SN 104A transmit 602 data to each other. Upon receiving SN state transition Following message 641 (e.g., in response to this), MN 104B sends 642 to CU 172. SN state transition The message includes the DL COUNT value and / or the UL COUNT value.

[0229] In some implementations, as described above, S-SN 104A (e.g., the CU of S-SN 104A) may, before or after sending the LTM cell handover command, or during, before or after process 698A, work with MN 104B and one or more C-SNs (including C-SN 106A) to prepare additional cells (i.e., cells 2, ..., N) as LTM candidate cells for UE 102. N is an integer greater than 1. Cells 2, ..., N can be operated by the C-SNs. For example, S-SN 104A and MN 104B perform additional inter-SN LTM preparation processes 2, ..., N to prepare cells 2, ..., N respectively. Each process in inter-SN LTM preparation processes 2, ..., N is similar to process 698A. In inter-SN LTM preparation processes 2, ..., N, S-SN 104A receives LTM candidate configurations 2, ..., N respectively, configuring cells 2, ..., N for LTM. As described above, MN 104B, S-SN 104A, or C-SN assigns LTM IDs 2, ..., N to identify LTM candidate configurations 2, ..., N, respectively. As described for CSI resource configuration 1, S-SN 104A can obtain CSI resource configurations 2, ..., N for cells 2, ..., N, respectively. As described for CSI reporting configuration 1, S-SN 104A can obtain CSI reporting configurations 2, ..., N for cells 2, ..., N, respectively. As described for RACH configuration 1, S-SN 104A can obtain RACH configurations 2, ..., N for cells 2, ..., N, respectively. As described for TCI status configuration 1, S-SN 104A can obtain TCI status configurations 2, ..., N for cells 2, ..., N, respectively. As described for LTM SSB configuration 1, S-SN 104A can obtain LTM SSB configurations 2, ..., N for cells 2, ..., N, respectively. In some implementations, S-SN 104A may perform LTM configuration transfer procedures 2, ..., N with UE 102 to send to UE 102 a list including the following items: {LTM ID 2, LTM candidate configuration 2, CSI resource configuration 2 (if obtained), TCI state configuration 2 (if obtained), RACH configuration 2 (if obtained), LTM SSB configuration 2 (if obtained) and / or PCI 1 of cell 1}, ..., {LTM ID N, LTM candidate configuration N, CSI resource configuration N, TCI state configuration N (if obtained), RACH configuration N (if obtained), LTM SSB configuration N (if obtained) and / or PCIN of cell N}. Each procedure in LTM configuration transfer procedures 2, ..., N is similar to procedures 394, 494 and / or events 518 and 520.In other implementations, the S-SN 104A includes this list in the first RRC reconfiguration message.

[0230] To simplify the following description, tuples 1, ..., N represent {LTM ID 1, LTM candidate configuration 1, CSI resource configuration 1 (if obtained), TCI status configuration 1 (if obtained), RACH configuration 1 (if obtained), LTM SSB configuration 1 (if obtained) and / or PCI 1}, ..., {LTM ID N, LTM candidate configuration N, CSI resource configuration N, TCI status configuration N (if obtained), RACH configuration N (if obtained), LTM SSB configuration N (if obtained) and / or PCI N}, respectively. In some implementations, S-SN 104A includes tuples 1, ..., N in RRC reconfiguration messages 1, ..., N, respectively, during LTM configuration passing procedures 1, ..., N. RRC reconfiguration message 1 is the first RRC reconfiguration message of procedure 694A. In some implementations, S-SN 104A includes tuples 1, ..., N in the container IE (e.g., ...). LTM-Config IE In other implementations, S-SN 104A includes tuples 1, ..., N in container IE 1 (e.g., ..., N), and encloses the containers IE 1, ..., N in RRC reconfiguration messages 1, ..., N respectively. LTM-Config In IE), the container IE1 is included in the first RRC reconfiguration message.

[0231] In some implementations, the S-SN 104A can include the CSI resource configurations 1, ..., N in the container IE instead of in the tuple, where N is a positive integer.

[0232] In some implementations, the SN request message and SN confirmation message in each of the SN-to-SN LTM preparation processes 2, ..., N are respectively the SN modification request message and the SN modification confirmation message. In other implementations, the SN request message and SN confirmation message in each of the SN-to-SN LTM preparation processes 2, ..., N are respectively the SN change request message and the SN change confirmation message. In some implementations, the SN request message and SN request confirmation message in each of the SN-to-SN LTM preparation processes 2, ..., N are respectively... SN Add Request Messages and SN Add Request Confirmation Messages. In other implementations, the SN request message and SN request confirmation message in each of the SN-to-SN LTM preparation processes 2, ..., N are respectively SN Modification Request Messages and SN modification request confirmationMessage. In some implementations, the information provided in the SN confirmation message (e.g., LTM candidate configuration, LTM reference configuration, first cell ID, or LTM ID) is alternatively provided in the SN modification request message from MN 104B to S-SN 104A (i.e., similar to event 609B, which will be described in scenario 600B).

[0233] In other implementations, S-SN 104A and CU 172 perform procedure 698A to prepare cell 1 and cell 2, ..., N (one or more of them) as LTM candidate cells for UE 102. Cell 2, ..., N are identified by cell IDs 2, ..., N, respectively, and are operated by DU 174 and / or other DU operations of C-SN 106A. In such an implementation, as described above for cell ID 1, S-SN 104A includes cell IDs 2, ..., N in an SN request message 603 for LTM, and MN 104B includes cell IDs 2, ..., N in an SN request message. In some implementations, upon receiving an SN request message, CU 172 determines or selects cell 1, ..., M from cells 1, ..., N as LTM candidate cells. M is a positive integer and M≤N. In other implementations, CU 172 prepares cells 1, ..., N for LTM as requested in the SN request message. CU 172 and DU 174 perform LTM preparation procedures 2, ..., M to prepare cells 2, ..., M as LTM candidate cells for UE 102, respectively. LTM preparation procedures 2, ..., M are similar to the procedure 690 performed by CU 172 and DU 174 to prepare cell 1. As a result of LTM preparation procedures 2, ..., M, CU 172 obtains LTM candidate configurations 2, ..., M for cells 2, ..., M, similar to obtaining LTM candidate configuration 1. As described for LTM candidate configuration 1, C-SN 106A can generate LTM candidate configurations 2, ..., M as a complete configuration, or generate an incremental configuration based on the LTM reference configuration. CU 172 includes LTM candidate configurations 2, ..., M in the SN request confirmation message. In some implementations, as described for LTM ID 1 and LTM candidate configuration 1, CU 172, MN 104B, or S-SN 104A assigns LTM IDs 2, ..., M to identify LTM preparation process 2, ..., M, respectively. When CU 172 assigns LTM IDs 1, ..., M, as described for LTM ID 1 and LTM candidate configuration 1, CU 172 includes LTM IDs 1, ..., M together with LTM candidate configuration 1, ..., M in the SN request confirmation message.

[0234] In some implementations, such as those described for early synchronization information 1, CU 172 obtains early synchronization information 2, ..., M for cells 2, ..., M respectively. CU 172 includes the early synchronization information 2, ..., M in the SN request confirmation message. In some implementations, such as those described for CSI resource configuration 1, CU 172 or S-SN 104A obtains CSI resource configuration 2, ..., M for cells 2, ..., M respectively. When CU 172 obtains CSI resource configuration 2, ..., M, CU 172 includes the CSI resource configuration 2, ..., M in the SN request confirmation message.

[0235] In some implementations, such as those described for LTM SSB configuration 1, CU 172 or S-SN 104A obtains LTM SSB configurations 2, ..., M for cells 2, ..., M respectively. When CU 172 obtains LTM SSB configurations 2, ..., M, CU 172 includes LTM SSB configurations 2, ..., M in the SN request confirmation message. In some implementations, such as those described for PCI 1, CU 172 or S-SN 104A obtains PCI 2, ..., M for cells 2, ..., M respectively. When CU 172 obtains PCI 2, ..., M, CU 172 includes PCI 2, ..., M in the SN request confirmation message.

[0236] In some implementations, CU 172 includes a list of the following items in the SN request confirmation message: {Cell ID 1, LTM ID 1 (if obtained or optional), LTM candidate configuration 1, CSI resource configuration 1 (if obtained or optional), TCI status configuration 1 (if obtained or optional), early synchronization information 1 (if obtained or optional), LTM SSB configuration 1 (if obtained or optional), PCI 1 (if obtained or optional)}, ..., {Cell ID M, LTM ID M (if obtained or optional), LTM candidate configuration M, CSI resource configuration M (if obtained or optional), TCI status configuration M (if obtained or optional), early synchronization information M (if obtained or optional), LTM SSB configuration M (if obtained or optional), PCI M (if obtained or optional)}. MN 104B includes the list or a portion thereof in the SN confirmation message.

[0237] In some implementations, as described for PDCCH instruction information 1, CU 172 obtains PDCCH instruction information 2, ..., M for cells 2, ..., M respectively. In one implementation, CU 172 includes PDCCH instruction information 2, ..., M in the SN request confirmation message. In another implementation, CU 172 includes PDCCH instruction information 2, ..., M in the early synchronization information 2, ..., M respectively. As described for PDCCH instruction information 1, MN 104B may include PDCCH instruction information 2, ..., M in the SN confirmation message. S-SN 104A may obtain RACH configuration 2, TCI status configuration 2 and / or PDCCH instruction information 2, ..., RACH configuration M, TCI status configuration M and / or PDCCH instruction information M respectively from the early synchronization information 2, ..., M or from the SN confirmation message.

[0238] In some implementations, S-SN 104A can perform LTM configuration transfer procedures 2, ..., M with UE 102 to send tuples 2, ..., M to UE 102 respectively. Each procedure in LTM configuration transfer procedures 2, ..., M is similar to procedures 394, 494 and / or events 518 and 520. In some implementations, S-SN 104A includes tuples 1, ..., M in containers IE (e.g., ...). LTM-Config IE In some implementations, S-SN 104A includes tuples 1, ..., M in the first RRC reconfiguration message, and also includes containers IE 1, ..., M in the RRC reconfiguration messages 1, ..., M respectively. In other implementations, S-SN 104A includes these tuples in the first RRC reconfiguration message. In some implementations, S-SN 104A includes tuples 1, ..., M in container IE 1 (e.g., ..., M). LTM-Config In IE), the container IE 1 is included in the first RRC reconfiguration message.

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

[0240] Events 626A, 627A, 628, 630, 631, 632, 633, and 634 are in Figure 6A This is collectively referred to as LTM execution process 699.

[0241] In some implementations, MN 104B (e.g., the CU of MN 104B) or S-SN 104A (e.g., the CU of S-BS104A) associates a first LTM security configuration list (i.e., a single security configuration list) for LTM candidate cells 1, ..., M or LTM candidate configurations 1, ..., M for UE 102 with UE 102. In some implementations, S-SN 104A indicates the LTM candidate configurations 1, ..., M associated with the first LTM security configuration list in the first RRC reconfiguration message and / or the RRC reconfiguration message 1, ..., M in the LTM configuration delivery process 2, ..., M. To indicate this association, S-SN 104A may include the first LTM security configuration list and a first security configuration ID identifying the first LTM security configuration list in a container IE 1, and include the first security configuration ID in a tuple (e.g., LTM-Candidate In IE 1, ..., M, based on the first security configuration ID, UE 102 identifies that LTM candidate cells 1, ..., M or LTM candidate configurations 1, ..., M of UE 102 share the same security configuration (i.e., the first LTM security configuration list). In some implementations, S-SN 104A includes the serving cell or the serving security configuration ID associated with the serving cell in the first RRC reconfiguration message or container IE 1. In some implementations, the serving security configuration ID indicates (e.g., identifies) the first security key, the first security algorithm, and / or the security parameters used to derive the first security key associated with the serving cell. The serving security configuration ID (i.e., the value) is different from the first security configuration ID (i.e., the value). Because the first security configuration ID is different from the serving security configuration ID, UE 102 determines the security configuration change for LTM cell handover from the serving cell to cell 1 and applies the first LTM security configuration list as described above to communicate with C-SN 106A via cell 1.

[0242] Subsequently, in communication 640, UE 102 may receive an LTM cell handover command from C-SN 106A, instructing UE 102 to perform an LTM cell handover to cell 2. In this case, as described for an LTM cell handover to cell 1, UE 102 responds to the LTM cell handover command and performs an LTM cell handover to cell 2. Because UE 102 recognizes that the same security configuration (i.e., the first security configuration) applies to both cell 1 and cell 2 (or LTM candidate configuration 1 and LTM candidate configuration 2), UE 102 uses or continues to use the second security key to communicate with C-SN 106A on cell 2. If UE 102 uses the second security algorithm to communicate with C-SN 106A on cell 1, then UE 102 uses or continues to use the second security algorithm to communicate with C-SN 106A on cell 2. Otherwise, if UE 102 uses the first security algorithm to communicate with C-SN 106A on cell 1, then UE 102 uses or continues to use the first security algorithm to communicate with C-SN 106A on cell 2. Similarly, C-SN 106A performs similar actions to communicate with UE 102 as described above. In the above description, "M" can be changed to "N".

[0243] In some implementations, S-SN 104A may perform an inter-CU LTM preparation procedure for UE 102 with another, second C-BS, to obtain an LTM candidate configuration and a second LTM security configuration list for LTM candidate cells (e.g., cells operated by the second C-BS), and send the LTM candidate configuration and the second UE LTM security configuration list to UE 102, similar to procedure 680. As described with respect to the first MN to SN LTM security configuration list, MN 104B may send the second MN to SN LTM security configuration list to the second C-BS. The examples and implementations described with respect to the first UE LTM security configuration list and the first MN to SN LTM security configuration list can be applied to the second UE LTM security configuration list and the second MN to SN LTM security configuration list, respectively. In some implementations, the second UE LTM security configuration list and / or the second MN to SN LTM security configuration list are different from the first UE LTM security configuration list and the first MN to SN LTM security configuration list.

[0244] In some implementations, the S-SN 104A can include the CSI resource configurations 1, ..., N in the container IE instead of in the tuple, where N is a positive integer.

[0245] Next reference Figure 6BScenario 600B is generally similar to Scenario 600A, except that Scenario 600B includes events 604B, 609B, and 611, instead of events 603 and 609A. In Scenario 600B, MN 104B initiates the 698B inter-SN LTM preparation procedure, while in Scenario 600A, S-SN 104A initiates the 698A inter-SN LTM preparation procedure. While communicating with MN 104B and S-SN 104A via DC, UE 102 can send at least one measurement report of 604B to MN 104B, for example via SRB1, similar to events 304 / 306, 404 / 406, and 504. If MN 104B is a distributed base station, then MN 104B includes CU and DU. The CU of MN 104B receives measurement reports from UE 102 via the DU of MN 104B. MN 104B (e.g., CU of MN 104B) generates a measurement configuration that configures UE 102 to send measurement reports, and sends the measurement configuration to UE 102 (e.g. via DU of MN 104B).

[0246] After receiving one or more measurement reports from UE 102 (e.g., in response to this), MN 104B (e.g., the CU of MN 104B) determines to prepare a first cell (e.g., cell 124B) as an LTM candidate for UE 102. In response to this determination, MN 104B generates an SN request message (first SN request message) including the first cell ID (e.g., cell ID 1) of the first cell (e.g., cell 1) and sends a 605 SN request message to C-SN 106A. In response to the SN request message, CU 172 determines whether to perform LTM preparation procedure 690 with DU 174, and performs LTM preparation procedure 690 with DU 174. Then, as referenced... Figure 6A As described, CU 172 sends a 607 SN request acknowledgment message to MN 104B. Upon receiving message 607 (e.g., in response to this), MN 104B sends a 609B message to S-SN 104A. SN Modification Request The message includes a first LTM candidate configuration (LTM candidate configuration 1), an LTM reference configuration, and / or a first cell ID, similar to event 609A. If the SN request confirmation message includes LTM-related configurations for configuring the first cell as an LTM candidate cell, such as RACH configuration, TCI state configuration, CSI resource configuration, LTM SSB configuration, and / or the first cell's PCI, then MN 104B will include the LTM-related configurations in the message. SN Modification ask In the message. Response to SN Modification Request Message: S-SN 104A sends 611 to MN 104B SN modification request confirmationThe message is sent, and the 694A LTM ​​configuration transfer procedure is performed with UE 102 to send the first LTM candidate configuration and / or LTM reference configuration to UE 102. Events 605, 690, 607, 609B, and 611 are in Figure 6B The process is collectively referred to as the MN-initiated SN-interval LTM preparation process 698B.

[0247] For reference Figure 6A As described, the SN request confirmation message 607 may include PDCCH instruction information. If the SN request confirmation message 607 includes PDCCH instruction information, then MN 104B will include the PDCCH instruction information in... SN Modification Request In the message. See reference. Figure 6A As described, if SN Modification Request If the message includes PDCCH command information, then S-SN 104A can send a 650A PDCCH command to UE 102 based on the PDCCH command information. (See reference...) Figure 6A As described, if SN Modification Request If the message includes TCI status configuration, then S-SN 104A can include the first TCI status ID in the LTM cell handover command.

[0248] In some implementations, MN 104B (e.g., the CU of MN 104B) may perform one or more LTM preparation procedures with CU 172 or other C-SNs to prepare additional cells (i.e., cell 2, ..., N) as LTM candidate cells for UE 102, and each LTM preparation procedure is similar to procedure 698B. MN 104B may perform the LTM preparation procedure before or after sending the LTM cell handover command, or during, before or after procedure 698B.

[0249] In other implementations, MN 104B and CU 172 perform procedure 698B to prepare cell 1 and cell 2, ..., N (one or more of them) as LTM candidate cells for UE 102. N is an integer greater than 1. Cell 2, ..., N are identified by cell ID 2, ..., N respectively, and are operated by DU 174 and / or other DU operations of C-SN 106A. In these implementations, as described above for cell ID 1, MN 104B includes cell ID 2, ..., N in SN request message 605.

[0250] Next reference Figure 6CScenario 600C is generally similar to scenarios 600A and 600B, except that it includes events 694C, 636C, and 645, instead of events 694A, 636A, and 638. In scenario 600C, during the LTM configuration delivery process 694C (similar to procedures 394 or 494), MN 104B sends a second serving DU configuration (including CSI report configuration), LTM ID, first LTM candidate configuration, LTM reference configuration, CSI resource configuration, LTM SSB configuration, RACH configuration, TCI state configuration, and / or the PCI of the first cell to UE 102 in one or more RRC reconfiguration messages to configure the first cell as an LTM candidate cell. In some implementations, MN 104B generates the RRC reconfiguration message in procedure 694C, while S-SN 104A generates the RRC reconfiguration message in procedure 694A. In some implementations, MN 104B assigns LTM IDs in scenario 600C, while S-SN 104A assigns LTM IDs in scenarios 600A and 600B.

[0251] When UE 102 performs the 699 LTM execution procedure, UE 102 sends a 636C RRC reconfiguration message to MN 104B, similar to event 636A. In some implementations, UE 102 includes the LTM ID in the RRC reconfiguration completion message to indicate that UE 102 applies the first LTM candidate configuration. Upon receiving the RRC reconfiguration message (e.g., in response to this), MN 104B may send a 645 SN message to S-SN 104A, as referenced. Figure 6A As described. In some implementations, the MN 104B may include the first cell ID of the first cell in the SN message. The MN 104B may determine the first cell ID based on the LTM ID received in the RRC reconfiguration complete message.

[0252] In some implementations, the MN 104B (e.g., the CU of the MN 104B) generates a first UE LTM security configuration list based on the first MN-to-SN LTM security configuration list and includes the first UE LTM security configuration list in the first RRC reconfiguration message of procedure 694C. In some implementations, the MN 104B includes the first UE LTM security configuration list in a container IE that includes tuple 1 (e.g., LTM-Config In the IE), the container IE is included in the first RRC reconfiguration message. In other implementations, MN 104B includes the first UE LTM security configuration list in tuple 1. For Figure 6A The description of S-SN104A can be applied to MN 104B.

[0253] Next reference Figure 6D Scenario 600D is generally similar to scenarios 600A, 600B, and 600C, except that scenario 600D includes events 624D, 650D, 654D, 626D, and 627D, instead of events 624A, 650A, 654A, 626A, and 627A. Events 624D, 650D, 654D, and 626D are similar to events 624A, 650A, 654A, and 626A, respectively, except that MN104B participates in events 624D, 650D, 654D, and 626D, while S-SN 104A participates in events 624A, 650A, 654A, and 626A. Event 627D differs from event 627A in that in event 627D, MN 104B can send to S-SN 104A. CU-CU Community Switch notification The message may include a first TCI status ID and / or a second TCI status ID.

[0254] In some implementations, such as those for S-SN 104A, MN 104B can generate a CSI report configuration based on the CSI resource configuration. The CSI resource configuration configures the RS transmitted on the first cell. MN 104B sends the CSI report configuration to UE 102 in procedure 694C. In some implementations, MN 104B has a pre-configured CSI resource configuration. In other implementations, MN 104B receives the CSI resource configuration from the OAM node. In still other implementations, MN 104B receives the CSI resource configuration from CU 172 or S-SN 104A.

[0255] Next, refer to Figure 7 A to Figure 14B Discuss RAN (e.g., Figures 6A to 6D The S-SN 104A, MN 104B, C-SN 106A, or CU 172) or UE (e.g., UE 102) can be implemented using several example methods for inter-CU LTM. See reference. Figures 3 to 6D The provided description may be applicable Figure 7 A to Figure 14B Generally speaking, Figure 7 A to Figure 14B Similar events in the figure are marked with similar figure references, which are consistent with the references. Figures 3 to 6DThe reference numerals for the described events have at least two identical significant digits, with differences discussed below where appropriate. For example, operation 702 is similar to events 302, 402, 502, and 602, etc., and therefore a separate description is omitted. Apart from the differences shown in the figures and discussed below, any other implementations discussed for a particular event (e.g., for message passing and processing) can be applied to other events in the figures labeled with similar reference numerals.

[0256] Figure 7 This is a flowchart of an example method 700 for inter-SN LTM preparation and security configuration. An S-SN (e.g., the CU of the S-SN) may implement example method 700. Method 700 begins at block 702, where the S-SN communicates with a UE located in the same DC as the MN and the S-SN, wherein the S-SN communicates with the UE via the serving cell using at least one first security key and at least one first security algorithm (e.g., event 602). At block 780, the S-SN may perform intra-SN LTM configuration and / or execution procedures with the UE (e.g., events 696 or 680). At block 798, the S-SN performs an inter-SN LTM preparation procedure with the MN for the UE to prepare a first cell as an LTM candidate cell for the UE (e.g., event 698A or event 698B). At block 709, the S-SN receives a first LTM candidate configuration and a first security configuration for the UE from the MN during the inter-SN LTM preparation procedure, wherein the first LTM candidate configuration configures the first cell for LTM (e.g., events 609A or 609B). In some implementations, during the inter-SN LTM preparation process, the S-SN sends a first interface message to the MN, requesting that the first cell be prepared as an LTM candidate cell for the UE. In response, the S-SN receives a second interface message from the MN at block 709, which includes the first LTM candidate configuration and the first security configuration.

[0257] At box 718, the S-SN sends a first RRC message to the UE, which includes a first LTM candidate configuration for configuring the first cell for LTM (e.g., event 518). At box 726, the S-SN may send an LTM cell handover command to the UE, instructing the UE to perform an LTM cell handover to the first cell, wherein the LTM cell handover command includes a first set of CFRA configuration parameters (e.g., event 626A). At box 727, the S-SN may send a CU-to-CU cell handover notification message for the UE to the MN, notifying that an LTM cell handover to the first cell has been triggered for the UE (e.g., event 627A). At box 731, the S-SN may send a CU-to-CU cell handover notification message for the UE to the MN. Early state transition Messages (e.g., event 631). In some implementations, Early state transitionThe message includes a DL COUNT value or a DISCARD DL COUNT value for each of at least one first DRB, through which the S-SN transmits data to the UE. At block 741, the S-SN may send data to the MN for the UE. SN state transition Messages (e.g., event 641). In some implementations, SN state transition The message includes a DL COUNT value and / or UL COUNT value for at least one second DRB, through which the UE and S-SN transmit data to each other. In some implementations, the first DRB and the second DRB include the same DRB and / or different DRBs.

[0258] In some implementations, the first interface message and the second interface message are either SN request messages or SN confirmation messages, respectively. In other implementations, the first interface message and the second interface message are dedicated NGAP messages, distinct from SN request messages or SN confirmation messages. For example, the first interface message and the second interface message are LTM-specific NGAP messages. In some implementations, the first security configuration is referenced... Figure 6A The first UE LTM security configuration list or the first MN to SN LTM security configuration list is described.

[0259] In some implementations, the first security configuration is associated with the first LTM candidate configuration. In some implementations, the first security configuration is an LTM-specific security configuration. In some implementations, the first LTM candidate configuration includes the first security configuration. In other implementations, the first LTM candidate configuration does not include the first security configuration. In some implementations, the MN includes the first LTM candidate configuration and the first security configuration in the first field / IE and the second field / IE, respectively, in the second interface message. In such cases, the S-SN extracts the first LTM candidate configuration and the first security configuration from the first field / IE and the second field / IE, respectively.

[0260] Figure 8This is a flowchart of an example method 800 for MN-SN LTM security configuration. The MN (e.g., the CU of the MN) may implement method 800. Method 800 begins at block 802, where the MN communicates with a UE located in the same DC as the MN and the S-SN (e.g., event 602). In some implementations, the S-SN communicates with the UE via the serving cell using at least one first security key and at least one first security algorithm. At block 805, the MN sends an SN request message to the C-SN, requesting the C-SN to prepare a first cell as an LTM candidate cell for the UE, and includes a list of MN-SN LTM security configurations (e.g., event 605). At block 807, the MN receives an SN request confirmation message from the C-SN, which includes a first LTM candidate configuration, wherein the first LTM candidate configuration configures the first cell for LTM (e.g., event 607). At block 809, the MN may send an SN message to the S-SN, which includes the first LTM candidate configuration (e.g., events 609A or 609B). At box 818, the MN may send a first RRC message to the UE, which includes a first LTM candidate configuration and a first UE LTM security configuration list (e.g., event 518).

[0261] At block 826, the MN can send an LTM cell handover command to the UE, instructing the UE to perform an LTM cell handover to the first cell, wherein the LTM cell handover command includes a first set of CFRA configuration parameters (e.g., event 626D). In some other implementations, the S-SN (instead of the MN) can send the LTM cell handover command to the UE (e.g., event 626A). At block 827, the MN can send a first CU-to-CU cell handover notification message for the UE to the S-SN, notifying that an LTM cell handover to the first cell has been triggered for the UE (e.g., event 627D). In some other implementations, the MN can receive the first CU-to-CU cell handover notification message for the UE from the S-SN (e.g., event 627A). At block 828, the MN can send a second CU-to-CU cell handover notification message for the UE to the C-SN, notifying that an LTM cell handover to the first cell has been triggered for the UE (e.g., event 628). At block 831, the MN receives the first CU-to-CU cell handover notification message for the UE from the S-SN. Early state transition Message (e.g., event 631). In some implementations, the first Early state transition The message includes a DL COUNT value or a DISCARD DL COUNT value for each of at least one first DRB, through which the S-SN transmits data to the UE. At block 833, the MN sends a second [data] for the UE to the first C-SN. Early state transition Message (e.g., event 633). In some implementations, the second Early symptoms state transition The message includes the DL COUNT value or the DISCARD DL COUNT value. At box 839, the MN receives an LTM success message from the C-SN, notifying the UE of successful access to the C-SN or the first cell (e.g., event 639). At box 842, the MN sends the first LTM message to the C-SN for the UE. SN state transition Message (e.g., event 642). In some implementations, the first SN state transition The message includes a DL COUNT value and / or UL COUNT value for at least one second DRB, through which the UE and S-SN transmit data to each other. In some implementations, the first DRB and the second DRB include the same DRB and / or different DRBs. In some implementations, the MN receives the second DRB for the UE from the S-SN. SN state transition The message includes the DL COUNT value and / or the UL COUNT value.

[0262] Figure 9 This is a flowchart of an example method 900 for preparing security for an LTM candidate cell. The C-SN can implement method 900. Method 900 begins at block 905, where the C-SN receives an SN request message from the MN (e.g., event 605). The SN request may include a request to prepare a first cell as an LTM candidate cell for the UE, and the request may include a list of first MN-SN LTM security configurations. At block 907, the C-SN sends an SN request confirmation message to the MN, which includes the first LTM candidate configuration, wherein the first LTM candidate configuration configures the first cell for LTM (e.g., event 607). At block 928, the C-SN receives a CU-CU cell handover notification message from the MN, notifying that an LTM cell handover to the first cell has been triggered for the UE (e.g., event 628). At block 933, the C-SN can receive from the MN a list of LTM security configurations for the UE. Early state transition Message (e.g., event 633). At box 932, the C-SN detects that the UE has accessed the first cell according to the first LTM CFRA configuration parameters (e.g., event 632). At box 939, the C-SN can send an LTM success message to the MN, notifying the UE of successful access to the C-SN or the first cell (e.g., event 639). At box 942, the C-SN can receive from the MN information for the UE... SN state transition Message (e.g., event 642). At block 960, the C-SN derives at least one (second) security key based on the first MN-to-SN LTM security configuration. At block 940, the C-SN can use the (second) security key to communicate with the UE via the first cell (e.g., event 640).

[0263] Figure 10 This is a flowchart of an example method 1000 for preparing security for LTM candidate cells based on whether LTM is inter-SN or intra-SN. RAN (e.g., RAN 105) Figure 1A Method 1000 can be implemented. Method 1000 begins at box 1098, where the RAN obtains a candidate LTM configuration for the UE. At box 1062, the RAN includes the candidate LTM configuration in an RRC message. At box 1063, the RAN determines whether the candidate LTM configuration obtained is for inter-SN LTM or intra-SN LTM. If the RAN obtains a candidate LTM configuration for inter-SN LTM (i.e., the “Inter-SN LTM” branch of box 1063), the process continues to boxes 1064 and 1066. At box 1064, the RAN includes the security configuration in an RRC message. Otherwise, if the RAN obtains a candidate LTM configuration for intra-SN LTM (i.e., the “Intra-SN LTM” branch of box 1063), the process skips box 1064 and continues to box 1066. At box 1066, the RAN sends an RRC message to the UE.

[0264] In some implementations, the RAN performs an inter-SN LTM preparation procedure to obtain an LTM candidate configuration (e.g., event 698A or 698B). In other implementations, the RAN performs an intra-SN LTM preparation procedure to obtain an LTM candidate configuration (e.g., event 696 or 680).

[0265] Figure 11This is a flowchart of an example method 1100 for configuring UE security and RAN security for communication with LTM candidate cells. The RAN (e.g., including an MN, S-SN, and / or C-SN) may implement method 1100. Method 1100 begins at block 1102, where the RAN communicates with a UE in a DC with the MN and S-SN of the same RAN, wherein the S-SN communicates with the UE via the serving cell using at least one first security key. At block 1118, the RAN sends LTM candidate configurations 1, ..., N and UE security configurations associated with LTM candidate configurations 1, ..., N to the UE, wherein LTM candidate configurations 1, ..., N configure LTM candidate PSCell 1, ..., N respectively, and N is an integer greater than 0. At block 1126-1, the RAN (e.g., an MN or S-SN) may send an LTM cell handover command to the UE, instructing the UE to perform an LTM cell handover to LTM candidate PSCell 1. At block 1132-1, the RAN (e.g., C-SN) can detect UE access to cell 1. At block 1160, the RAN (e.g., C-SN) can derive at least one second security key based on the RAN security configuration. In some implementations, the RAN (e.g., C-SN) obtains the UE security configuration based on the RAN security configuration. At block 1140-1, the RAN (e.g., C-SN) can communicate with the UE via cell 1 using the second security key. At block 1126-2, the RAN (e.g., C-SN) can send an LTM cell handover command to the UE, instructing the UE to perform an LTM cell handover to LTM candidate PSCell 2. At block 1132-2, the RAN (e.g., C-SN) can detect UE access to LTM candidate PSCell 2. At block 1140-2, the RAN (e.g., C-BS) can communicate with the UE via LTM candidate PSCell 2 using the second security key.

[0266] In some implementations, UE security configuration is similar to that for... Figures 6A to 6D The first UE LTM security configuration list. In some implementations, the RAN security configuration is similar to that for... Figures 6A to 6D The first MN to SNLTM security configuration list.

[0267] Figure 12This is a flowchart of an example method 1200 for receiving security configurations and LTM configurations for LTM candidate cells. A UE can implement method 1200. Method 1200 begins at block 1202, where the UE communicates with the RAN using at least one first security key (e.g., event 602). At block 1218, the UE receives from the RAN LTM candidate configurations 1, ..., N and the security configurations associated with them, where LTM candidate configurations 1, ..., N configure LTM candidate PSCells 1, ..., N respectively, and N is an integer greater than 0 (e.g., event 518). At block 1226-1, the UE can receive an LTM cell handover command from the RAN, instructing the UE to perform an LTM cell handover to LTM candidate PSCell 1 (e.g., event 626A or event 626D). At block 1232-1, the UE can access LTM candidate PSCell 1 in response to the LTM cell handover command (e.g., event 632). At block 1260, the UE can derive at least one second security key based on a security configuration. At block 1240-1, the UE can use the second security key to communicate with the RAN via cell 1 (e.g., event 640). At block 1226-2, the UE can receive an LTM cell handover command from the RAN, instructing the UE to perform an LTM cell handover to cell 2 (e.g., event 626A or event 626D). At block 1232-2, the UE can access LTM candidate PSCell 2 in response to an LTM cell handover command (e.g., event 632). At block 1240-2, the UE can use the second security key to communicate with the UE via LTM candidate PSCell 2 (e.g., event 640).

[0268] In some implementations, security configurations are similar to those for... Figures 6A to 6D The first UE LTM security configuration list.

[0269] Figure 13This is a flowchart of a second example method 1300 for preparing security for LTM candidate cells based on whether LTM is inter-SN or intra-SN. A RAN (e.g., including an MN, S-SN, and / or C-SN) can implement method 1300. Method 1300 may be similar to method 1100, with the differences described below. Method 1300 begins at block 1302, where the RAN communicates with the UE via the serving PSCell using at least one first security key. At block 1318, the RAN sends LTM candidate configurations 1, ..., N to the UE, where LTM candidate configurations 1, ..., N configure LTM candidate PSCells 1, ..., N respectively, and N is an integer greater than 0. The process continues to blocks 1326-1 and 1332-1. At block 1376, the RAN determines whether the serving PSCell and LTM candidate PSCell 1 operate within the same SN. If the serving PSCell and LTM candidate PSCell 1 are operated by different SNs (i.e., the "No" branch of box 1376), the procedure continues to boxes 1360 and 1340-1. At box 1360, the RAN derives at least one second security key based on the MN-to-SN security configuration. At box 1340-1, the RAN uses the second security key to communicate with the UE via LTM candidate PSCell 1. For example, the serving PSCell and LTM candidate cell 1 are operated by the S-SN and C-SN, respectively. Otherwise, if the serving PSCell and LTM candidate PSCell 1 are operated by the same SN (e.g., the S-SN) (i.e., the "Yes" branch of box 1376), the procedure continues to box 1340. At box 1340, the RAN uses the first security key to communicate with the UE via LTM candidate PSCell 1.

[0270] Figure 14AAn example method 1400A for security configuration of LTM candidate cells is shown. A UE can implement method 1400A. Method 1400A begins at block 1402. At block 1402, the UE communicates with the RAN via the serving PSCell using at least one first security key. At block 1418, the UE receives LTM candidate configurations 1, ..., N from the RAN, where LTM candidate configurations 1, ..., N configure LTM candidate PSCells 1, ..., N respectively, and N is an integer greater than 0. The process continues to blocks 1426-1 and 1432-1. At block 1476A, the UE determines whether the first security ID (i.e., value) for cell 1 is different from the serving security ID (i.e., value) for the serving cell. If the first security ID is the same as the serving security ID (i.e., the "yes" branch of block 1476A), the process continues to blocks 1460 and 1440-1. At block 1460, the UE derives at least one second security key based on the first security configuration identified by the first security ID. At box 1440-1, the UE communicates with the RAN via LTM candidate PSCell 1 using the second security key. Otherwise, if the first security ID differs from the service security ID (the "No" branch of box 1476A), the process continues to box 1440. At box 1440, the UE communicates with the RAN via LTM candidate PCell 1 using the first security key.

[0271] In some implementations, the UE receives the First Security ID and the Service Security ID from the RAN. In some implementations, the "Security ID" can be replaced with the "Security Configuration ID". In other implementations, the "Security ID" can be replaced with the "Security Cell Set ID". (For...) Figure 5 and Figures 6A to 6D The examples and implementations described in "Security Configuration ID" can be applied to "Security ID".

[0272] Figure 14B This is a flowchart of an example method 1400B, similar to method 1400A, except that method 1400B includes block 1476B. At block 1476B, the UE determines whether it has received a first security configuration associated with LTM candidate configuration 1. If the UE has received the first security configuration associated with LTM candidate configuration 1 (i.e., the "Yes" branch of block 1476B), the process continues to blocks 1460 and 1440-1. In some implementations, the first security configuration is the aforementioned first UE LTM security configuration list. Otherwise, if the UE has not received a security configuration associated with LTM candidate configuration 1 (e.g., the first security configuration) (i.e., the "No" branch of block 1476B), the process continues to block 1440.

[0273] Figure 15This is a flowchart of example method 1500 implemented in an MN, which provides the DC to the UE together with the SN. The MN (e.g., the CU of the MN) can implement method 1500.

[0274] Method 1500 begins at block 1505, at which point the MN sends to the candidate C-SN: (i) a request for low-layer triggered mobility (LTM) configuration for the candidate cell associated with the C-SN, and (ii) a first security configuration (e.g., event 605 or event 805). This request may be included in the SN request message. Before and throughout method 1500, the MN may communicate with the UE by performing security protection on the data transmitted to the UE using the master security key and master security algorithm (see event 602 or event 802).

[0275] The first security configuration may include a RAN-level security key, which may contain or include an S-NG-RAN node security key. Alternatively or additionally, the first security configuration may include a security key counter and / or information about the UE's security capabilities.

[0276] At box 1507, the MN receives the LTM configuration from the C-SN (e.g., event 607 or event 807). The LTM configuration may be received in an acknowledgment message from the C-SN, and the LTM configuration may include LTM candidate configurations and / or cell identifiers of candidate cells. The MN may send an acknowledgment message to the S-SN including the LTM configurations of the candidate cells (e.g., events 609A, 609B, 809). See above for reference. Figure 6A , Figure 6B and Figure 8 The verification may include Channel State Information (CSI) resource configuration information, LTM Synchronization Signal Block (SSB) configuration information, Physical Cell ID (PCI) of the candidate cell, early synchronization information, and / or an identifier for identifying the LTM candidate configuration.

[0277] At box 1518, the MN may send a first RRC message to the UE, including a first LTM candidate configuration and a first UE LTM security configuration list (e.g., event 518).

[0278] Method 1500 may further include: sending a reference LTM configuration to the C-SN. Method 1500 may include: generating a second security configuration from at least a portion of a first security configuration. The second security configuration may include a security key counter. In some embodiments, the second security configuration does not include a RAN-level security key.

[0279] Method 1500 may include receiving a message identifying one or more candidate cells or candidate SNs from a source SN (e.g., event 603). The message may include an SN request message, and the message may include an LTM indicator indicating that the message pertains to LTM for a candidate cell. The SN request message may include an identifier of a source distributed element (S-DU) or a base station identifier and / or an LTM reference configuration.

[0280] Method 1500 may include sending an LTM cell handover command to the UE (e.g., event 626D or event 826). Additionally, the MN may send a notification to the C-SN and / or S-SN regarding the UE's handover to a candidate cell (e.g., events 627D, 628, 827, 828). This notification may include a Transport Configuration Indicator (TCI) status identifier.

[0281] Method 1500 may include: receiving an indication from the C-SN that an LTM cell handover has been successfully performed (e.g., event 639 or event 839). The MN may then notify the S-SN of the successful LTM cell handover (e.g., event 642 or event 842). The MN may receive an early state transition notification from the S-SN including parameters for downlink communication (e.g., event 631 or event 831), and the MN may then provide these parameters for downlink communication to the C-SN (e.g., event 633 or event 833).

[0282] Figure 16 This is a flowchart of an example method implemented by providing a candidate SN (cell-cell) to the UE along with the MN (Medium-Nutrition Node). Method 1600 begins at block 1605, where the C-SN receives from the MN: (i) a low-layer triggered mobility (LTM) configuration for the candidate cell associated with the SN, and (ii) a security configuration (e.g., event 605 or event 905). The LTM configuration and security configuration may be received in a request message (e.g., an SN request message). In response to this request message, the C-SN may perform an LTM preparation procedure with the distributed element (DU) associated with the SN to prepare the candidate cell (e.g., event 690). The C-SN may also request an LTM reference DU configuration.

[0283] The security configuration may include a RAN-level security key, which may in turn include an S-NG-RAN node security key. The security configuration may further include a security key counter and / or information about the UE's security capabilities. The C-SN may derive the security key based on the security information (e.g., event 960). The security key may include: (i) an integrity key for integrity protection of control plane data packets, (ii) an integrity key for integrity protection of user plane data packets, (iii) an encryption key for encryption or decryption of control plane data packets, and / or (iv) an encryption key for encryption or decryption of user plane data packets.

[0284] Method 1600 continues at block 1640, where the C-SN communicates with the UE using a key based on a security configuration (e.g., event 640 or event 940).

[0285] Method 1600 may include sending a response to the LTM configuration to the MN (e.g., event 607 or event 907). The response may include confirmation of the LTM configuration, such as a confirmation request from the SN. The confirmation may include the LTM configuration of the candidate cell, the cell identifier of the candidate cell, an indication of whether the LTM configuration is a full configuration or an incremental configuration, or similar information.

[0286] Method 1600 may further include receiving a notification that the UE is performing an LTM cell handover to a candidate cell (e.g., event 628 or event 928). Additionally, method 1600 may include receiving an early state transition message from the MN, the early state transition message including downlink communication parameters for communicating with the UE (e.g., event 633 or event 933).

[0287] Figure 17 It is generally similar to Figure 16 The flowchart for another example method, method 1700, is provided, but in which the method is implemented in the source SN (S-SN) rather than the candidate SN. The S-SN (e.g., the CU of the S-SN) may implement example method 1700. Method 1700 begins at block 1709, where the S-SN receives from the MN: (i) configuration information identifying a lower-layer triggered mobility (LTM) candidate secondary cell, and (ii) a first security configuration (e.g., event 609A, event 609B, or event 709). Method 1700 continues at block 1718, where the S-SN sends a second security configuration associated with the first security configuration to the UE (e.g., event 518 or event 718).

[0288] Configuration information can be received in a confirmation message from the MN. This confirmation message may include a SN change confirmation message (e.g., an SN modification confirmation message). In some implementations, the confirmation includes Channel State Information (CSI) resource configuration information, LTM Synchronization Signal Block (SSB) configuration information, Physical Cell ID (PCI) of the candidate cell, early synchronization information, an identifier for identifying the LTM candidate configuration, and / or similar information.

[0289] The configuration information may include a UE LTM security configuration list. Box 1718 may further include encoding a container information element (IE) that, among other information or the IE, further includes the UE LTM security configuration list. The UE LTM security configuration list may include a security key counter.

[0290] In some implementations, method 1700 includes: in response to receiving a measurement report from the UE, sending a message identifying an LTM candidate cell or candidate S-SN to the MN (e.g., event 603). This message may include an SN request message, which may include: (i) an LTM indicator indicating that the message pertains to LTM for a candidate cell, (ii) an identifier of the source distributed element (S-DU) or a base station identifier, and / or (iii) an LTM reference configuration. The source S-SN may provide the LTM reference configuration during transmission to the candidate S-SN.

[0291] At box 1731, the S-SN may send an early state transition notification (e.g., event 631 or 731) including parameters for downlink communication. Method 1700 may further include sending a notification message to the MN to indicate that the UE has completed LTM cell handover (e.g., event 627A or event 727). Method 1700 may further include avoiding this transmission if the LTM candidate configuration is used for in-SN LTM (e.g., event 680 or event 605).

[0292] In some implementations, the first security configuration is associated with the first LTM candidate configuration. In some implementations, the first security configuration is an LTM-specific security configuration. In some implementations, the first LTM candidate configuration includes the first security configuration. In other implementations, the first LTM candidate configuration does not include the first security configuration. In some implementations, the MN includes the first LTM candidate configuration and the first security configuration in the first field / IE and the second field / IE, respectively, in the second interface message. In such cases, the S-SN extracts the first LTM candidate configuration and the first security configuration from the first field / IE and the second field / IE, respectively.

[0293] Figure 18This is a flowchart of an example method implemented in the UE. The UE communicates with the RAN on the serving PSCell using at least one initial security key (e.g., event 602 or event 1202). At block 1818, the UE receives from the radio access network (RAN): (i) a low-layer triggered mobility (LTM) configuration for the candidate primary / secondary cell (PSCell), and (ii) a first security configuration associated with the LTM configuration (e.g., event 518 or event 1218).

[0294] The UE can receive a cell handover command from the RAN instructing the UE to switch to a candidate PSCell (e.g., event 626A, event 626D, or event 1226-1). The UE can access the candidate PSCell based on the cell handover command (e.g., event 632 or event 1232-1). The UE can derive at least one second security key based on a security configuration (e.g., event 1260). The first security configuration may include a list of security configurations associated with multiple candidate PSCells. The first security configuration may configure at least one security algorithm for deriving the security key. Method 1800 may further include: deriving at least one security key for communicating with the candidate PSCell based on the first security configuration.

[0295] At block 1840, the UE can communicate with the candidate PSCell using a second security configuration associated with the first security configuration (e.g., event 640 or event 1240-1). The UE can receive additional cell handover commands to hand over to the additional candidate PSCell. Based on these commands, the UE can derive at least one second security key for communicating with the additional candidate PSCell (e.g., event 626A, event 626D, or event 1226-2).

[0296] Method 1800 may include: avoiding the export of the security key if the identifier of the service PSCell is no different from the identifier of the candidate PSCell (e.g., event 1476A or event 1476B).

[0297] The following list of examples reflects various embodiments explicitly contemplated in this disclosure.

[0298] Example 1. A method implemented in a primary node (MN) that provides dual connectivity (DC) to a user equipment (UE) together with a secondary node (SN), the method comprising: sending to a candidate SN (C-SN): (i) a request for a low-layer triggered mobility (LTM) configuration for a candidate cell associated with the C-SN, and (ii) a first security configuration; receiving an LTM candidate configuration from the C-SN in response to the request; and sending the LTM candidate configuration and a second security configuration associated with the first security configuration to the UE.

[0299] Example 2. The method described in Example 1 further includes: sending a reference LTM configuration to the C-SN.

[0300] Example 3. The method described in Example 1 or 2, wherein: the request for LTM configuration is included in the SN request message.

[0301] Example 4. The method according to any one of Examples 1 to 3, wherein the first security configuration includes a radio access network (RAN) level security key.

[0302] Example 5. The method described in Example 4, wherein the RAN-level security key includes the secondary next-generation RAN (S-NG-RAN) node security key.

[0303] Example 6. The method according to any one of the foregoing examples, wherein the first security configuration includes a security key counter.

[0304] Example 7. The method according to any one of the foregoing examples, wherein the first security configuration includes an indication of the security capabilities of the UE.

[0305] Example 8. The method according to any one of the foregoing examples further includes: generating a second security configuration from at least a portion of a first security configuration.

[0306] Example 9. The method described in Example 8, wherein the second security configuration includes a security key counter.

[0307] Example 10. The method described in Example 8, wherein the second security configuration does not include a RAN-level security key.

[0308] Example 11. The method according to any one of the foregoing examples, wherein the LTM candidate configuration is received in an acknowledgment from the C-SN.

[0309] Example 12. The method according to Example 11, wherein the confirmation includes the cell identifier of the candidate cell.

[0310] Example 13. The method according to any one of the foregoing examples further includes: receiving a message identifying one or more candidate cells or C-SNs from a source SN.

[0311] Example 14. The method according to Example 13, wherein the message identifying one or more candidate cells or C-SNs includes an SN request message.

[0312] Example 15. The method according to Example 14, wherein the message identifying one or more candidate cells or C-SNs includes an LTM indicator that indicates the message relates to LTM for the candidate cell.

[0313] Example 16. The method according to Example 14, wherein the SN request message includes the identifier of the source distributed unit (S-DU) or the base station identifier.

[0314] Example 17. The method according to Example 14, wherein the SN request message includes an LTM reference configuration, and wherein the method further includes: sending the LTM reference configuration to the C-SN.

[0315] Example 18. The method according to Example 17, wherein sending the LTM reference configuration to the C-SN is in response to receiving a message identifying the candidate cell or the C-SN from the source SN.

[0316] Example 19. The method according to Example 13 further includes: sending an LTM cell handover command to the UE.

[0317] Example 20. The method according to Example 19 further includes: sending a notification to the C-SN and the source SN that the UE is switching to a candidate cell.

[0318] Example 21. The method according to Example 20, wherein the notification includes a Transport Configuration Indication (TCI) status identifier.

[0319] Example 22. The method according to Example 13 further includes: receiving an indication from the C-SN that an LTM cell handover has been successfully performed; and providing the indication to the source SN.

[0320] Example 23. The method according to Example 13 further includes: receiving an early state transition notification from a source SN including parameters for downlink communication; and sending an early state transition message to a C-SN, the message including the parameters for downlink communication received from the source SN.

[0321] Example 24. The method according to Example 23 further includes: sending confirmation including the LTM candidate configuration to the source SN.

[0322] Example 25. The method according to Example 24, wherein the confirmation includes Channel State Information (CSI) resource configuration information.

[0323] Example 26. The method described in Example 24, wherein the confirmation includes LTM synchronization signal block (SSB) configuration information.

[0324] Example 27. The method according to Example 24, wherein the confirmation includes the physical cell ID (PCI) of the candidate cell.

[0325] Example 28. The method described in Example 24, wherein the confirmation includes early synchronization information.

[0326] Example 29. The method according to Example 24, wherein the verification includes an identifier for identifying the LTM candidate configuration.

[0327] Example 30. The method described in Example 1 further includes: performing security protection on the data transmitted between the MN and the UE using a master security key and a master security algorithm before sending the request.

[0328] Example 31. A device including processing hardware and configured to implement the method according to any one of Examples 1 to 30.

[0329] Example 32. A method implemented in a secondary node (SN) that provides dual connectivity to a user equipment (UE) together with a primary node (MN), the method comprising: receiving from the MN (i) a low-layer triggered mobility (LTM) configuration of a candidate cell associated with the SN, and (ii) a security configuration; and communicating with the UE using a key based on the security configuration.

[0330] Example 33. The method described in Example 32, wherein the LTM configuration and security configuration are received in the request message.

[0331] Example 34. The method described in Example 33, wherein the request message is an SN request message.

[0332] Example 35. The method according to Example 34 further includes: in response to an SN request message, performing an LTM preparation process with a distributed unit (DU) associated with the SN to prepare a candidate cell.

[0333] Example 36. The method according to any one of Examples 32 to 35 further includes: requesting an LTM reference distributed unit (DU) configuration.

[0334] Example 37. The method according to any one of Examples 32 to 36, wherein the security configuration includes a radio access network (RAN) level security key.

[0335] Example 38. The method according to Example 37, wherein the RAN-level security key includes the secondary next-generation RAN (S-NG-RAN) node security key.

[0336] Example 39. The method according to any one of Examples 32 to 38, wherein the security configuration includes a security key counter.

[0337] Example 40. The method according to any one of Examples 32 to 39, wherein the security configuration includes information about the security capabilities of the UE.

[0338] Example 41. The method according to Example 40 further includes: deriving a security key based on information about the security capabilities of the UE.

[0339] Example 42. The method according to Example 41, wherein the security key includes an integrity key for integrity protection of control plane data packets.

[0340] Example 43. The method according to Example 41, wherein the security key includes an integrity key for integrity protection of user plane data packets.

[0341] Example 44. The method according to Example 41, wherein the security key includes an encryption key for encrypting or decrypting control plane data packets.

[0342] Example 45. The method according to Example 41, wherein the security key includes an encryption key for encrypting or decrypting user plane data packets.

[0343] Example 46. The method according to any one of Examples 32 to 45 further includes: sending a response to the LTM configuration to the MN.

[0344] Example 47. The method described in Example 46, wherein the response includes confirmation of the LTM configuration.

[0345] Example 48. The method according to Example 47, wherein the confirmation includes an SN request confirmation.

[0346] Example 49. The method according to any one of Examples 47 to 48, wherein the confirmation includes the LTM configuration of the candidate cell.

[0347] Example 50. The method according to any one of Examples 47 to 49, wherein the confirmation includes the cell identifier of the candidate cell.

[0348] Example 51. The method according to any one of Examples 47 to 50, wherein the confirmation includes an indication as to whether the LTM configuration is a full configuration or an incremental configuration.

[0349] Example 52. The method according to any one of Examples 32 to 51 further includes: receiving a notification that the UE is performing an LTM cell handover to a candidate cell.

[0350] Example 53. The method according to any one of Examples 32 to 52 further includes: receiving an early state transition message from the MN, the early state transition message including downlink communication parameters for communicating with the UE.

[0351] Example 54. A device including processing hardware and configured to implement the method according to any one of Examples 32 to 53.

[0352] Example 55. A method implemented in a secondary node (SN) that provides dual connectivity to a user equipment (UE) together with a primary node (MN), the method comprising: receiving from the MN: (i) a low-layer triggered mobility (LTM) configuration identifying an LTM candidate secondary cell, and (ii) a first security configuration; and sending to the UE a second security configuration associated with the first security configuration.

[0353] Example 56. The method according to Example 55, wherein the LTM configuration is received in a confirmation message from the MN.

[0354] Example 57. The method according to Example 56, wherein the confirmation message includes an SN change confirmation message.

[0355] Example 58. The method according to Example 57, wherein the SN change confirmation message includes an SN modification confirmation message.

[0356] Example 59. The method according to any one of Examples 56 to 58, wherein the confirmation message includes Channel State Information (CSI) resource configuration information.

[0357] Example 60. The method according to any one of Examples 56 to 59, wherein the confirmation message includes LTM synchronization signal block (SSB) configuration information.

[0358] Example 61. The method according to any one of Examples 56 to 60, wherein the confirmation message includes the Physical Cell ID (PCI) of the LTM candidate secondary cell.

[0359] Example 62. The method according to any one of Examples 56 to 61, wherein the confirmation message includes early synchronization information.

[0360] Example 63. The method according to any one of Examples 56 to 62, wherein the confirmation message includes an identifier for identifying a candidate LTM configuration among a plurality of LTM configurations.

[0361] Example 64. The method according to any one of Examples 55 to 63 further includes: in response to receiving a measurement report from the UE, sending a message to the MN identifying an LTM candidate secondary cell or a candidate SN associated with an LTM candidate secondary cell.

[0362] Example 65. The method according to Example 64, wherein the message identifying the LTM candidate secondary cell or the candidate SN associated with the LTM candidate secondary cell includes an SN request message.

[0363] Example 66. The method of Example 65, wherein the message identifying one or more of the LTM candidate secondary cells or candidate SNs includes an LTM indicator indicating that the message relates to LTM for the LTM candidate secondary cells.

[0364] Example 67. The method according to Example 66, wherein the SN request message includes the identifier of the source distributed unit (S-DU) or the base station identifier.

[0365] Example 68. The method according to Example 66, wherein the SN request message includes an LTM reference configuration, and wherein the method further includes: sending the LTM reference configuration to the candidate SN.

[0366] Example 69. The method according to any one of Examples 55 to 68, wherein the LTM configuration includes a list of UE LTM security configurations.

[0367] Example 70. The method according to Example 69, wherein sending the second security configuration includes encoding a container information element that includes a list of UE LTM security configurations.

[0368] Example 71. The method according to Example 70, wherein the UE LTM security configuration list includes a security key counter.

[0369] Example 72. The method according to any one of Examples 55 to 71 further includes: sending an early state transition notification to the MN, including parameters for downlink communication.

[0370] Example 73. The method according to any one of Examples 55 to 72 further includes: sending a notification message to the MN to indicate that the UE has completed LTM cell handover.

[0371] Example 74. The method according to any one of Examples 55 to 73 further includes: if the LTM configuration is used for in-SN LTM, then avoid sending a second security configuration to the UE.

[0372] Example 75. An apparatus including processing hardware and configured to implement the method according to any one of Examples 55 to 74.

[0373] Example 76. A method implemented in a user equipment (UE) comprising: receiving (i) a low-layer triggered mobility (LTM) configuration of a candidate primary / secondary cell (PSCell) from a radio access network (RAN), and (ii) a first security configuration associated with the LTM configuration; and communicating with the candidate PSCell using a second security configuration associated with the first security configuration.

[0374] Example 77. The method according to Example 76 further includes: receiving from the RAN a cell handover command instructing the UE to hand over to a candidate PSCell; and accessing the candidate PSCell based on the cell handover command.

[0375] Example 78. The method according to any one of Examples 76 to 77, wherein the first security configuration includes a security configuration list, the security configuration list including multiple security configurations associated with multiple candidate PSCells.

[0376] Example 79. The method according to any one of Examples 76 to 78, wherein the first security configuration configures at least one security algorithm for deriving the security key.

[0377] Example 80. The method according to any one of Examples 76 to 79 further includes: deriving at least one security key for communicating with the candidate PSCell based on a first security configuration.

[0378] Example 81. The method according to Example 80 further includes: receiving an additional cell handover command to hand over to an additional candidate PSCell; and deriving at least one second security key for communicating with the additional candidate PSCell.

[0379] Example 82. The method according to Example 79, wherein the at least one security algorithm includes at least one of an encryption algorithm or an integrity algorithm.

[0380] Example 83. The method according to Example 80 further includes: communicating with the RAN on the service PSCell using at least one initial security key.

[0381] Example 84. The method according to Example 83 further includes: avoiding exporting the security key if the identifier of the service PSCell is the same as the identifier of the candidate PSCell.

[0382] Example 85. The method according to Example 83, wherein the first security configuration does not include a radio access network (RAN) level security key.

[0383] Example 86. The method according to Example 78, wherein the first security configuration includes a security key counter.

[0384] Example 87. A device including processing hardware and configured to implement the method according to any one of Examples 76 to 86.

[0385] The following descriptions can be applied to the descriptions above.

[0386] In some implementations, the SN requirement message and the SN confirmation message are respectively SN Change Requirements Messages and SN Change Certificate Reality Message. In other implementations, the SN requires the message and the SN confirms the message, respectively. SN Modification Requirements Messages and SN Modification Certificate Reality Messages. In some implementations, the SN request message and the SN request acknowledgment message are respectively... SN Add Request Messages and SN Add Add confirmation request Messages. In other implementations, the SN request message and the SN request confirmation message are respectively SN Modification Request Messages and SN modification request confirmation information.

[0387] In general, a description of one of the above figures can be applied to another of the above figures. Examples, implementations, and methods can be combined if there is no conflict. The events or boxes described above can be optional or omitted. For example, events or boxes marked with dashed lines in the figures can be optional. Descriptions from the perspective of the receiving node also apply to the sending node. For example, a description of a receiving node (e.g., DU) receiving a message from a sending node (e.g., CU) can be replaced with a description of the sending node sending a message to the receiving node. Similarly, a description of a receiving node (e.g., CU) receiving a message from a sending node (e.g., DU) can be replaced with a description of the sending node sending a message to the receiving node.

[0388] In some implementations, "message" is used and can be replaced with "information element (IE)" and vice versa. In some implementations, "IE" is used and can be replaced with "field" and vice versa. In some implementations, "configurations" or "configuration parameters" can be used to replace "configuration" and vice versa. In some implementations, "LTM command" can be replaced with "serving cell change command," "Layer 1 / Layer 2 LTM cell handover command," "lower layer handover 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, "cell group configuration" can be used to replace "DU configuration." In some implementations, "serving cell index," "LTM cell index," "Special cell (SpCell) index," "PCell index," or "PSCell index" can be used to replace "cell index." In some implementations, "service" can be replaced with "source." In some implementations, "measurement report" or "CSI report" can be used instead of "measurement result". In some implementations, "early TA acquisition" can be replaced with "early UL timing synchronization" or "early UL synchronization". In some implementations, "early TA acquisition on candidate cells" can be replaced with "early UL timing synchronization with candidate cells" or "early UL synchronization with candidate cells". In some implementations, "include" can be replaced with "comprise". In some implementations, "exclude" can be replaced with "avoid inclusion". In some implementations, the above " Switching requests "and" Switch request confirmation "This is used to describe the invention and can be replaced with a message having a common name. For example, " Switching requests "and" Switch request confirmation "This can be replaced with the first CU-to-CU message and the second CU-to-CU message, respectively. In another example, " Switching requests "and" Switch Request confirmation "This can be replaced with the first interface message and the second interface message, respectively. In yet another example," Switching requests "and" Switch request confirmationThe terms "SN request," "SN confirm," "SN request," and "SN request acknowledge" are used to describe the invention and can be replaced with messages with generic names. For example, "SN request message" can be replaced with an SN to MN message. In another example, "SN confirm message" can be replaced with an MN to SN message. In some implementations, "security configuration ID" can be replaced with "security cell set ID." In some implementations, the "RACH configuration" used for early UL synchronization can be replaced with "early UL synchronization configuration."

[0389] User devices implementing the technologies of this disclosure (e.g., UE 102) can be any suitable device capable of wireless communication, such as smartphones, tablets, laptops, mobile game consoles, point-of-sale (POS) terminals, health monitoring devices, drones, cameras, media streaming dongles or other personal media devices, wearable devices such as smartwatches, Wi-Fi hotspots, femtocells, or broadband routers. Furthermore, in some cases, the user device may be embedded in electronic systems, such as the main unit of a vehicle or an advanced driver assistance system (ADAS). Further still, the user device can operate as an Internet of Things (IoT) device or a mobile internet device (MID). Depending on the type, the user device may include one or more general-purpose processors, computer-readable storage, a user interface, one or more network interfaces, one or more sensors, etc.

[0390] Some embodiments described in this disclosure include logic or multiple components or modules. A module can be a software module (e.g., code or machine-readable instructions stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit capable of performing certain operations and can be configured or arranged in a certain way. A hardware module may include a dedicated circuit system or logic (e.g., as a dedicated processor, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), digital signal processor (DSP), etc.) that is persistently configured to perform certain operations. A hardware module may also include programmable logic or a circuit system (e.g., included 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 a dedicated and persistently configured circuit system or in a temporarily configured circuit system (e.g., configured by software) may be driven by cost and time considerations.

[0391] As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having,” or any other variation thereof are intended to cover non-exclusive inclusion. For example, a process, method, article of manufacture, or apparatus that includes a list of elements is not necessarily limited to those elements, but may include other elements not expressly listed or inherent to such process, method, article of manufacture, or apparatus. Furthermore, unless expressly stated to the contrary, “or” means inclusive or, not exclusive or. For example, any of the following conditions A or B are satisfied: A is true (or exists), and B is false (or does not exist); A is false (or does not exist), and B is true (or exists); and both A and B are true (or exist).

[0392] When implemented in software, these technologies can be provided as part of an operating system, libraries used by multiple applications, or specific software applications. This software can be executed by one or more general-purpose processors or one or more dedicated processors.

[0393] Upon reading this disclosure, those skilled in the art will understand additional and alternative structural and functional designs for handling mobility between base stations using the principles disclosed herein. Therefore, while specific embodiments and applications have been shown and described, it should be understood that the disclosed embodiments are not limited to the precise constructions and components disclosed herein. Various modifications, alterations, and variations that can be understood by those skilled in the art regarding the arrangement, operation, and details of the methods and apparatus disclosed herein without departing from the spirit and scope defined by the appended claims.

Claims

1. A method implemented in a master node MN, the method comprising: Send to the candidate secondary node C-SN: (i) a request for low-layer trigger mobility LTM configuration for the candidate cell associated with the C-SN, and (ii) a first security configuration; In response to the request, receive LTM candidate configurations from the C-SN; as well as Send the LTM candidate configuration and the second security configuration associated with the first security configuration to the user equipment (UE).

2. The method according to claim 1, further comprising: Send the second security configuration to the source auxiliary node S-SN.

3. The method according to any one of claims 1 to 2, wherein: The first security configuration includes a radio access network (RAN) level security key.

4. The method according to claim 3, wherein: The RAN-level security key includes the secondary next-generation RAN S-NG-RAN node security key.

5. The method according to any one of the preceding claims, wherein: The first security configuration includes a security key counter.

6. The method according to any one of the preceding claims, wherein: The first security configuration includes an indication of the UE's security capabilities.

7. The method according to any one of the preceding claims further comprises: The second security configuration is generated using at least a portion of the first security configuration.

8. The method according to claim 7, wherein: The second security configuration includes a security key counter.

9. The method according to claim 7, wherein: The second security configuration does not include a RAN-level security key.

10. The method according to any one of the preceding claims, wherein: The first security configuration and the second security configuration each include a first security algorithm and a second security algorithm.

11. The method according to claim 10, wherein, The first security algorithm is different from the second security algorithm.

12. A method implemented in a candidate secondary node C-SN, the method comprising: Receive (i) low-layer triggered mobility LTM configuration for the candidate cell associated with the C-SN from the master node MN, and (ii) security configuration; as well as Communicate with the UE using a key based on the security configuration.

13. The method according to claim 12, wherein: The security configuration includes information about the security capabilities of the UE, and The method further includes deriving a security key based on the information regarding the security capabilities of the UE.

14. A method implemented in a user equipment (UE), the method comprising: Receive (i) a low-layer triggered mobility LTM configuration for candidate primary and secondary cells PSCell from the radio access network RAN ​​node, and (ii) a first security configuration associated with the LTM configuration; as well as Communicate with the candidate PSCell using a second security configuration associated with the first security configuration.

15. The method of claim 14, wherein: The first security configuration includes a security configuration list, which includes multiple security configurations associated with multiple candidate PSCells.

16. An apparatus comprising processing hardware and configured to implement the method according to any one of claims 1 to 15.