Configure Channel State Information Reporting for Mobility in Dual Connectivity
By configuring low-level trigger mobility channel state information resources and reports between central units for user equipment, the problems of prolonged cell handover and high overhead in dual connectivity mode are solved, and more efficient mobility processing is achieved.
Patent Information
- Application Number
- CN202580026360.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-07-19
- Filing Date
- 2025-04-02
- Publication Date
- 2026-11-10
AI Technical Summary
Existing technologies suffer from issues such as long latency, high overhead, and long downtime during serving cell changes when user equipment (UE) moves from one cell to another. In particular, in dual connectivity mode, existing systems fail to effectively support low-level triggered mobility (LTM) cell handover between central units.
By configuring low-level triggered mobility (LTM) channel state information (CSI) resources and reports between central units for user equipment (UE), network entities coordinate the preparation and handover process of LTM candidate cells, including sending and receiving relevant resource configurations and reports, to optimize the cell handover process.
It reduces the latency of LTM cell handover, lowers system overhead, and improves the efficiency and reliability of mobility processing.
Smart Images

Figure CN123077170A_ABST
Abstract
Description
[0001] Related applications
[0002] This application claims priority to U.S. Provisional Patent Application Serial No. 63 / 574,890, filed April 4, 2024, entitled "Configuring Channel State Information Reporting for Mobility in Dual Connectivity," and U.S. Provisional Patent Application Serial No. 63 / 673,251, filed July 19, 2024, both entitled "Configuring Channel State Information Reporting for Mobility in Dual Connectivity," the entire contents of which are hereby incorporated by reference. Technical Field
[0003] This disclosure generally relates to wireless communications, and in some aspects to configuring channel state reporting for mobility under 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 (to the extent described in this background section) and aspects of the specification that would not have been considered prior art at the time of filing are neither expressly nor impliedly acknowledged as prior art to this disclosure.
[0005] User equipment (UE) can operate in dual connectivity (DC) mode. In DC mode, the UE can simultaneously utilize the resources of multiple radio access network (RAN) nodes. RAN nodes can be network entities, such as monolithic base stations or distributed base stations (also known as decomposed base stations). In distributed base stations, the functionality of the base station can be distributed across a central unit (CU) and one or more distributed units (DU) interconnected via backhaul. When RAN nodes support different radio access technologies (RATs), this type of connectivity is called multiple radio dual connectivity (MR-DC). In DC, one RAN node operates as the primary node (MN) covering the primary cell (PCell), and the other RAN node operates as the secondary node (SN) covering the primary and secondary cells (PSCells). The UE communicates with the MN (via the PCell) and the SN (via the PSCell). The cells of the MN are called the primary cell group (MCG), and the cells of the SN are called the secondary cell group (SCG).
[0006] When a UE moves from the coverage area of one cell to another, a serving cell change must be performed for the UE at some point. To perform the serving cell change, the RAN can configure the UE to send Layer 3 (L3) measurement results. Based on the L3 measurement results received from the UE, the RAN sends a Radio Resource Control (RRC) reconfiguration message with synchronization (e.g., the RRC reconfiguration message includes...). ReconfigurationWithSync IE) for changes to the serving cell (e.g., PCell or PSCell). Where the UE operates under carrier aggregation (CA) with at least one secondary cell (SCell) and PCell or PSCell, the RAN releases that at least one SCell due to the change of PCell or PSCell. Serving cell changes involve a complete Layer 2 (L2) and Layer 1 (L1) reset, resulting in longer latency, greater overhead, and longer downtime.
[0007] When the RAN's base station communicates with the UE via the serving cell, the base station receives one or more L3 (e.g., RRC) measurement results from the UE. One of the DUs operating the serving cell is the serving DU. Based on the L3 measurement results, the base station can configure a low-layer triggered mobility (LTM, also known as "L1 / L2 triggered mobility") candidate cell for LTM cell handover. To configure the UE's LTM candidate cell, the base station sends an LTM candidate configuration to the UE via RRC signaling. Later, the base station receives one or more L1 measurement results from the UE. Based on these one or more L1 measurement results, the base station determines that the LTM candidate cell is eligible to become the UE's serving cell. Therefore, the base station sends an LTM cell handover command to the UE to instruct the UE to perform an LTM cell handover to the LTM candidate cell. Summary of the Invention
[0008] The systems, methods, and apparatuses disclosed herein each have several innovative aspects, but no single innovative aspect is solely responsible for the desired properties disclosed herein.
[0009] One innovative aspect of the subject matter described in this disclosure can be implemented as a method for wireless communication performed by a first network entity. The method further includes transmitting a first low-layer triggered Mobility Channel State Information (LTM) resource configuration for a first cell to a user equipment (UE) operating with both the first and second network entities under dual connectivity. This first LTM CSI resource configuration configures one or more first LTM CSI resources associated with the first cell. The method also includes transmitting a second LTM CSI resource configuration for the first cell to a third network entity. This second LTM CSI resource configuration configures one or more second LTM CSI resources associated with the first cell.
[0010] Another innovative aspect of the subject matter described in this disclosure can be implemented as a method for wireless communication performed by a first network entity. The method further includes receiving from a second network entity a request to prepare a second cell as an LTM candidate cell for a UE in dual-connectivity mode within the first cell. The method also includes receiving from the second network entity an LTM CSI resource configuration that configures one or more LTM CSI resources associated with the first cell.
[0011] Another innovative aspect of the subject matter described in this disclosure can be implemented as a method for wireless communication performed by a first network entity. The method further includes receiving from a second network entity a request for preparing a handover of a UE from a first cell to a second cell, the request including an LTM CSI resource configuration that configures one or more LTM CSI resources associated with the first cell. The method also includes sending an acknowledgment to the second network entity of the request for preparing the handover.
[0012] Another innovative aspect of the subject matter described in this disclosure can be implemented as an apparatus comprising a communication unit and a processing system configured to control the communication unit to implement any of the methods mentioned above.
[0013] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages will become apparent from the specification, drawings, and claims. Attached Figure Description
[0014] Figure 1A This is a block diagram of an example wireless communication system in which network entities configure low-layer triggered Mobility (LTM) Channel State Information (CSI) resources and LTM CSI reports for inter-Cell handover between Central Units (CUs).
[0015] Figure 1B This is another block diagram of an example wireless communication system in which network entities configure LTM CSI resources and LTM CSI reports for inter-Center Unit (CU) cell handover.
[0016] Figure 1C It is possible Figure 1A or Figure 1B A block diagram of an example base station operating in the system, including a central unit (CU) and a distributed unit (DU).
[0017] Figure 2A This is a block diagram of an example protocol stack. Figure 1A The UE communicates with the base station according to this example 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 example protocol stack.
[0019] Figure 3 This is a sequence diagram illustrating an example operation for cell handover within a CU and a DU.
[0020] Figure 4 This is a sequence diagram illustrating an example operation for the communication process of cell handover between DUs within a CU.
[0021] Figure 5 This is a sequence diagram illustrating an example operation for a communication process of inter-CU cell handover, wherein the first base station operates as a serving base station or source base station (S-BS), and the second base station operates as a candidate base station (C-BS).
[0022] Figure 6A This is a sequence diagram illustrating example operations for a communication process of inter-cell handover between first example CUs, wherein the first base station operates as the master node (MN), the second base station operates as the candidate SN (C-SN), and the third base station operates as the serving SN or source SN (S-SN).
[0023] Figure 6B This is a sequence diagram illustrating example operations for a communication process of inter-cell handover between second example CUs, wherein the first base station acts as the MN operation, the second base station acts as the C-SN operation, and the third base station acts as the S-SN operation.
[0024] Figure 6C This is a sequence diagram illustrating example operations for communication procedures in a third example CU inter-cell handover, where the first base station acts as the MN operation, the second base station acts as the C-SN operation, and the third base station acts as the S-SN operation.
[0025] Figure 6D This is a sequence diagram illustrating example operations for communication procedures used in a fourth example CU inter-cell handover, where the first base station acts as the MN operation, the second base station acts as the C-SN operation, and the third base station acts as the S-SN operation.
[0026] Figure 7A This is a flowchart illustrating a first example operation of a method that can be implemented by an MN for configuring LTM CSI resources and LTM CSI reports for inter-CU cell handover.
[0027] Figure 7B This is a flowchart illustrating a second example operation of a method that can be implemented by an MN for configuring LTM CSI resources and LTM CSI reports for inter-CU cell handover.
[0028] Figure 8 This is a flowchart illustrating a third example operation of a method that can be implemented by an MN for configuring LTM CSI resources and LTM CSI reports for inter-CU cell handover.
[0029] Figure 9A This is a flowchart illustrating a first example operation of a method for configuring LTM CSI resources and LTM CSI reports for inter-CU cell handover, which can be implemented by a candidate secondary node (C-SN).
[0030] Figure 9B This is a flowchart illustrating a second example operation of a method that can be implemented by a C-SN for configuring LTM CSI resources and LTM CSI reports for inter-CU cell handover.
[0031] Figure 10A This is a flowchart illustrating a first example operation of a method for configuring LTMCSI resources and LTM CSI reports for inter-CU cell handover, which can be implemented by the central unit (CU) of a C-SN.
[0032] Figure 10B This is a flowchart illustrating a second example operation of a method for configuring LTMCSI resources and LTM CSI reports for inter-CU cell handover, which can be implemented by the central unit (CU) of a C-SN.
[0033] Figure 11 This is a flowchart illustrating an example operation of a method for configuring LTM CSI resources and LTM CSI reports for inter-CU cell handover, which can be implemented by the target SN (T-SN).
[0034] Figure 12 This is a flowchart illustrating an example operation of a method that can be implemented by a CU of a T-SN for configuring LTM CSI resources and LTMCSI reports for inter-CU cell handover.
[0035] Figure 13 This is a flowchart illustrating a first example operation of a method for wireless communication performed by a first network entity.
[0036] Figure 14 This is a flowchart illustrating a second example operation of a method for wireless communication performed by a first network entity.
[0037] Figure 15 This is a flowchart illustrating a third example operation of a method for wireless communication performed by a first network entity.
[0038] Figure 16 This is a block diagram illustrating an example configuration of network entities and user equipment. Detailed Implementation
[0039] For the purpose of describing the innovative aspects of this disclosure, the following description relates to certain implementations. However, those skilled in the art will readily recognize that the teachings herein can be applied in many different ways. Some examples in this disclosure are based on wireless communications according to 3GPP wireless standards such as Ambient Internet of Things (A-IoT), 4G Long Term Evolution (LTE) standards, and 5G New Radio (NR) standards. However, the described techniques can be implemented in any apparatus, system, or network capable of transmitting and receiving radio frequency signals according to any wireless communication standard (including any of the IEEE 802.11 or 802.16 wireless standards) or other known signals used for communication within wireless, cellular, or IoT networks, such as systems utilizing 4G, 5G, 6G, ZigBee, Bluetooth, WiFi, or future radio technologies.
[0040] As described above, the RAN's base station communicates with the UE via a serving cell. The base station can be a distributed base station, where its functionality is distributed across a central unit (CU) and one or more distributed units (DUs). The base station can configure low-layer triggered mobility (LTM, also known as "L1 / L2 triggered mobility") candidate cells for LTM cell handover. During operation, the base station receives one or more L1 measurement results from the UE. Based on these L1 measurement results, the base station determines that the LTM candidate cell is eligible to become the UE's serving cell. Therefore, the base station sends an LTM cell handover command to the UE to instruct the UE to perform an LTM cell handover to the LTM candidate cell. If the LTM candidate cell is operated by a serving DU, the LTM cell handover is called an intra-CU, intra-DU LTM cell handover. If the LTM candidate cell is operated by a candidate DU within a DU, the LTM cell handover is called an intra-CU, inter-DU LTM cell handover. Both of these handovers occur within the same base station or the same CU of a distributed base station, and are therefore referred to as "intra-CU" cell handover. While existing systems can support intra-CU LTM cell handover (e.g., intra-CU intra-DU cell handover and intra-CU inter-DU cell handover), existing systems may not support inter-CU LTM cell handover between a first cell associated with a first network entity (such as a first base station or a CU of the first network entity) and a second cell associated with a second network entity (such as a second base station or a CU of the second base station).
[0041] This disclosure relates to techniques for configuring LTM Channel State Information (CSI) resources and LTM CSI reporting for network entities operating with User Equipment (UE) in a dual-connectivity environment for inter-Center Unit (CU) low-level triggered mobility (LTM) (also referred to as "L1 / L2 triggered mobility") cell handover. The network entity and the UE communicate via a serving cell. The network entity can configure the UE with a first LTM candidate configuration for a first cell. The first network entity can send a request to a second network entity, requesting the second network entity to prepare a second cell as an LTM candidate cell for the UE. The first network entity can configure LTM CSI resources for a second LTM candidate configuration that designates the first cell as a candidate cell. For example, the first network entity can send a second LTM CSI resource configuration for the first cell to the second network entity, specifying LTM CSI resources for the first cell. The second network entity can use the LTM CSI resource configuration to configure the UE for measuring the CSI of the first cell. The second network entity can send an LTM CSI report configuration to the first network entity, which configures one or more reports associated with the LTM CSI resources. After an LTM handover to a candidate cell (e.g., the second cell), the LTM CSI resources have been configured and are available for use with respect to the first cell, which now becomes the LTM candidate cell for the second cell after the handover.
[0042] A potential technical advantage of this disclosure is that a first network entity, such as a base station (or distributed base stations), can configure a second network entity with LTM CSI resources, and the second network entity can configure CSI reporting associated with the LTM CSI resources prior to an LTM cell handover from the first cell to the second cell. After the LTM cell handover, the LTM CSI resources are immediately available to the UE to measure and report CSI, which the second network entity can use to determine whether to perform an LTM cell handover back to the first cell. This can lead to a reduction in latency associated with such LTM cell handovers.
[0043] Figure 1AThis is a block diagram of an example wireless communication system 100A, in which network entities configure LTM CSI resources and LTM CSI reports for inter-CU cell handover. Wireless communication system 100A includes a UE 102, a first network entity (e.g., base station (BS) 104), a second network entity (e.g., base station 106), and a core network (CN) 110. UE 102 can initially connect to base station 104. In some scenarios, base station 104 can configure another base station (e.g., base station 106) as a secondary node (SN), and UE 102 can be configured to operate with both base stations 104 and 106 under dual connectivity (DC). Base stations 104 and 106 can operate as the MN and SN of UE 102, respectively.
[0044] In addition to base stations 104 and 106, network entities can also be Evolved Universal Terrestrial Radio Access Network Node B (E-UTRAN Node B), Evolved Node B (eNodeB or eNB), Next Generation Node B (gNodeB or gNB), Next Generation E-UTRAN Node B (ng-eNB), access points, radio heads, etc. Network entities can be implemented in macro cells, micro cells, small cells, pico cells, etc., or any combination thereof. In some aspects, base stations such as base station 104 and / or base station 106 can be monolithic base stations, where the functionality of the base station is implemented as a single unit. In other aspects, base stations can be distributed base stations, where the functionality of the base station can be distributed among two or more units (such as a central unit (CU) and one or more distributed units (DU)).
[0045] In various configurations of the wireless communication system 100A, base station 104 can be implemented as a primary eNB (MeNB) or primary gNB (MgNB), and base station 106 can be implemented as a secondary gNB (SgNB). In some aspects, UE 102 can communicate with base station 104 and base station 106 via the same radio access technology (RAT) (such as Evolved Universal Terrestrial Radio Access (EUTRA) or New Radio (NR)). In other aspects, UE 102 can communicate with base station 104 and base station 106 via different RATs. When base station 104 is a MeNB and base station 106 is an SgNB, UE 102 can be in EUTRA-NR DC (EN-DC) with both the MeNB and the SgNB.
[0046] In some aspects, a MeNB or SeNB can be implemented as an ng-eNB. When base station 104 is the primary ng-eNB (Mng-eNB) and base station 106 is the SgNB, UE 102 can be in a next-generation (NG) EUTRA-NR DC (NGEN-DC) with both the Mng-eNB and SgNB. When base station 104 is a MgNB and base station 106 is an SgNB, UE 102 can be in an NR-NRDC (NR-DC) with both the MgNB and SgNB. When base station 104 is a MgNB and base station 106 is a secondary ng-eNB (Sng-eNB), UE 102 can be in an NR-EUTRA DC (NE-DC) with both the MgNB and Sng-eNB.
[0047] In the scenario where UE 102 switches from base station 104 to base station 106, base stations 104 and 106 operate as the source base station (S-BS) and the target base station (T-BS), respectively. For example, before the handover, UE 102 can operate under DC with base station 104 and the auxiliary base station (T-BS). Figure 1A (Not shown in the diagram) After the handover is complete, UE 102 can continue to operate with base station 106 and the additional base station under DC, or with base station 106 under single connectivity (SC). In this case, base stations 104 and 106 operate as the source MN (S-MN) and the target MN (T-MN), respectively.
[0048] The core network (CN) 110 can be either the Evolved Packet Core (EPC) 111 or the 5th Generation Core (5GC) 160; both are... Figure 1AThe example is depicted. Base station 104 may be an eNB supporting an S1 interface for communication with EPC 111, an ng-eNB supporting an NG interface for communication with 5GC 160, or a gNB supporting an NR radio interface and an NG interface for communication with 5GC 160. Base stations 104 and 106 may support X2 or Xn interfaces to directly exchange messages with each other during the scenarios discussed below. Among other components, EPC 111 may also include a Serving Gateway (SGW) 112, a Mobility Management Entity (MME) 114, and a Packet Data Network Gateway (PGW) 116. SGW 112 is typically configured to deliver user plane packets associated with audio calls, video calls, Internet traffic, etc. MME 114 is configured to manage authentication, registration, paging, and other related functions. PGW 116 provides connectivity from the UE to one or more external packet data networks (e.g., Internet networks and / or Internet Protocol (IP) Multimedia Subsystem (IMS) networks). 5GC 160 includes User Plane Functions (UPF) 162, Access and Mobility Management Functions (AMF) 163, and / or Session Management Functions (SMF) 166. UPF 162 is typically configured to deliver user plane packets related to audio calls, video calls, internet traffic, etc. AMF 163 is configured to manage authentication, registration, paging, and other related functions. SMF 166 is configured to manage PDU sessions.
[0049] exist Figure 1A In the example shown, base station 104 supports cell 124A, and base station 106 supports cell 126A. Cells 124A and 126A can partially overlap, allowing UE 102 to communicate with both base stations 104 and 106 under DC, where one of base stations 104 and 106 is MN and the other is SN. Base station 104 can support additional cells, such as cells 124B and 124C, and base station 106 can support additional cells (…). Figure 1A (Not shown in the image). Cells 124A, 124B, and 124C may partially overlap, allowing UE 102 to communicate with base station 104 via carrier aggregation (CA). Base station 104 may communicate via one or more transmit and receive points (TRPs). Figure 1A (Not shown in the diagram) Operating cells 124A, 124B, and 124C. More specifically, when UE 102 is under DC with base stations 104 and 106, one of base stations 104 and 106 operates as a MeNB, Mng-eNB, or MgNB, and the other operates as an SgNB or Sng-eNB.
[0050] Generally, the wireless communication system 100A can include any suitable number of base stations supporting NR cells and / or EUTRA cells. More specifically, the EPC 111 or 5GC 160 can connect to any suitable number of base stations supporting NR cells and / or EUTRA cells. See below for reference. 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 network or 5G NR-6G DC.
[0051] Base station 104 is equipped with 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. 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 transmit DL reference signals with one or more user equipments (e.g., UE 102) on a physical downlink (DL) channel via one or more cells (e.g., cells 124A, 124B, and / or 124C) and / or one or more TRPs. PHY controller 132 is also configured to receive data and control signals and / or receive UL reference signals with one or more user equipments on a physical uplink (UL) channel via one or more cells (e.g., cells 124A, 124B, and / or 124C) and / or one or more TRPs. In an example implementation, processing hardware 130 includes a media access control (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 equipment (UEs), and / or transmitting UL / DL MAC PDUs with one or more UEs. In some aspects, MAC functions may include low-layer triggered mobility (LTM) related functions as described herein. In some other aspects, LTM controller 137 may perform the LTM functions described herein. Processing hardware 130 may further include radio resource control (RRC) controller 136 to implement procedures and messaging at the RRC sublayer of the protocol communication stack. For example, RRC controller 136 may be configured to support RRC messaging associated with handover procedures and / or support necessary operations when base station 104 operates as MN relative to SN or as SN relative to MN. Base station 106 may include processing hardware 140 similar to processing hardware 130. Specifically, components 142, 144, 146, and 147 of base station 106 may be similar to components 132, 134, 136, and 137 of base station 104, respectively.
[0052] UE 102 is equipped with 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 configured to receive data and control signals and / or receive DL reference signals on a physical DL channel with base station 104 or 106 via one or more cells (e.g., cells 124A, 124B, 124C, and / or 126A) and / or one or more TRPs. PHY controller 152 is also configured to transmit data and control signals and / or transmit UL reference signals on a physical UL channel with base station 104 or 106 via one or more cells (e.g., cells 124A, 124B, 124C, and / or 126A) and / or one or more TRPs. In an example implementation, processing hardware 150 includes MAC controller 154, which is configured to perform MAC functions with base station 104 or 106. For example, MAC functions may include random access procedures, managing UL timing advances for one or more user facilities, and transmitting UL / DL MAC PDUs with base station 104 or 106. In some aspects, MAC functions may 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. Although described as being included within processing hardware 150, some of the above-described functionalities may be implemented as firmware or in software modules (e.g., software modules stored in computer-readable storage).
[0053] In operation, UE 102 under DC can use radio bearers to communicate with base stations such as base station 104 or base station 106. Generally, the UE and base station can use signaling radio bearers (SRBs) to exchange RRC messages and non-access stratum (NAS) messages. UE 102 and base station 104 or 106 can use data radio bearers (DRBs) to transmit data on the user plane.
[0054] The UE can use several types of SRBs and DRBs. When operating under dual connectivity (DC), the cell associated with the base station operating as the MN defines the primary cell group (MCG), and the cell associated with the base station operating as the secondary node (SN) defines the secondary cell group (SCG). SRB1 resources can carry RRC messages, which in some cases may include NAS messages exchanged (e.g., transmitted and / or received) on the dedicated control channel (DCCH). SRB2 resources support RRC messages, which may include recorded measurement information or NAS messages. SRB2 resources can also be exchanged via the DCCH, but with lower priority than SRB1 resources. SRB1 and SRB2 resources allow the UE and MN to exchange MN-related RRC messages as well as SN-related embedded RRC messages. These SRB1 and SRB2 messages can be referred to as MCG SRBs. SRB3 resources can be used by the UE and SN to exchange SN-related RRC messages. These SRB3 resources can be referred to as SCG SRBs. An SRB that is used by the UE to directly exchange RRC messages with the MN via the low-level resources of both the MN and SN can be called a split SRB. Similarly, a DRB that uses only the low-level resources of the MN can be called an MCG DRB. A DRB that uses only the low-level resources of the SN can be called an SCG DRB. A DRB that uses both the low-level resources of MCG and SCG can be called a split DRB.
[0055] exist Figure 1A In the example shown, UE 102 operating under DC can use radio bearers (e.g., DRB or SRB) that terminate at different times at base station 104 operating as MN or base station 106 operating as SN. When communicating on radio bearers in the uplink (UL) direction (e.g., from UE 102 to the base station) and / or in the downlink direction (e.g., from the base station to UE 102), UE 102 can apply one or more security keys.
[0056] Figure 1B This is another block diagram of example wireless communication system 100B, in which network entities configure LTM CSI resources and LTM CSI reports for inter-cell handover between central units (CUs). Figure 1B In the example shown, base station 104A can be an implementation of base station 104 in Figure 1, and base station 106A can be... Figure 1A The implementation method of base station 106. Figure 1B The example also depicts additional base stations 104B and 106B that can be included in the wireless communication system 100B. UE 102 is initially connected to base station 104A. Base stations 104B and 106B can have similar processing hardware to base station 106A.
[0057] In some scenarios, base station 104A can perform an SN addition procedure (e.g., "instant SN addition") to configure UE 102 to operate in dual connectivity (DC) with both base station 104A (via PCell) and base station 106A (via PSCell other than cell 126A). In such scenarios, base stations 104A and 106A act as the MN and SN for UE 102, respectively. In some cases, UE 102 can operate using MR-DC connectivity modes, for example, communicating with base station 104A using 5G NR and with base station 106A using EUTRA, or communicating with base station 104A using EUTRA and with base station 106A using 5G NR. Multi-connection coordination can help two base stations coordinate shared UE capabilities, including operating frequencies (e.g., band combinations, frequency ranges), UE measurements and reporting (e.g., intra-frequency measurements, inter-frequency measurements, inter-RAT measurements, measurement gaps), receive timing (e.g., DRX configuration, offset timing), and uplink power control (e.g., power margin, maximum transmit power).
[0058] When UE 102 is communicating with base station 104A and S-SN 106A under DC, base station 104A, acting as MN, can perform an SN change procedure (e.g., "instant SN change") to change UE 102's SN from base station 106A (referred to as the source SN or serving SN, "S-SN") to base station 104B (referred to as the target SN or "T-SN"). In another scenario, S-SN 106A can perform a PSCell change procedure (e.g., "instant PSCell change") to change UE 102's PSCell to cell 126A. In one implementation, S-SN 106A can send a configuration to UE 102 via a signaling radio bearer (SRB) (e.g., SRB3) to change the PSCell to cell 126A for PSCell change. In another implementation, S-SN 106A can send a configuration to UE 102 via base station 104A to change the PSCell to cell 126A for PSCell change. Base station 104A can also send the same configuration to UE 102 via SRB1. Extended multi-connectivity coordination can help newly added base stations coordinate shared UE capabilities.
[0059] Figure 1C An example distributed implementation of base station 164 is described. In some respects, base station 164 can be... Figure 1A Base station 104 or 106, or Figure 1BThe implementation of base station 104A, 104B, 106A, or 106B. In this implementation, base station 164 may include a central unit (CU) 172 and one or more distributed units (DUs) 174. CU 172 is equipped with processing hardware, which may include one or more general-purpose processors (such as CPUs) and non-transitory computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or dedicated processing units. In one example, CU 172 is equipped with processing hardware 130. In another example, CU 172 is equipped with... Figure 1A Processing hardware 140. In the example implementation, processing hardware 140 includes an SN RRC controller (e.g., Figure 1A The SN RRC controller 146 is configured to manage or control one or more RRC configurations and / or RRC procedures when the base station 164 operates as an SN. The DU174 is also equipped with processing hardware that 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. In some examples, in example implementations, the processing hardware includes: a MAC controller configured to manage or control one or more MAC operations or procedures (e.g., random access procedures); and a Radio Link Control (RLC) controller configured to manage or control one or more RLC operations or procedures when the base station 164 operates as an MN or SN. The processing hardware may further include a physical layer controller configured to manage or control one or more physical layer operations or procedures.
[0060] Figure 2A This is a block diagram illustrating an example protocol stack 200, which the UE uses to communicate with a base station. For example, the UE 102 can communicate with an eNB, ng-eNB 230, or gNB 232 (e.g., one or more of base stations 104A and 106A) via the example protocol stack 200.
[0061] In example protocol stack 200, EUTRA's physical layer (PHY) 202A provides a transport channel to EUTRA MAC sublayer 204A, which in turn provides a logical channel to EUTRA RLC sublayer 206A. EUTRA RLC sublayer 206A then provides an RLC channel to EUTRA Packet Data Convergence Protocol (PDCP) sublayer 208 and, in some cases, to NR PDCP sublayer 210.
[0062] Similarly, NR PHY 202B provides a transport channel to NR MAC sublayer 204B, which in turn provides a logical channel to NR RLC sublayer 206B. NR RLC sublayer 206B then provides data delivery services to NR PDCP sublayer 210. NR PDCP sublayer 210 can then provide data delivery services to Serving Data Adaptation Protocol (SDAP) sublayer 212 or RRC sublayer (…). Figure 2A (Not shown in the image) provides data transfer services. In some implementations, UE 102 supports both EUTRA and NR stacks, such as... Figure 2A As shown, this is to support handover between EUTRA and NR base stations and / or support DCs via EUTRA and NR interfaces. Furthermore, as... Figure 2A As shown, UE102 can support the layering of NR PDCP sublayer 210 on EUTRA RLC sublayer 206A, and the layering of SDAP sublayer 212 on NRPDCP sublayer 210.
[0063] The PDCP sublayer of example protocol stack 200 provides services such as user plane data delivery, encryption, and integrity protection. For example, the EUTRA PDCP sublayer 208 (e.g., as defined in 3GPP Technical Specification (TS) 36.323) defined for the EUTRA radio interface and the NR PDCP sublayer 210 (e.g., as defined in 3GPP TS 38.323) defined for the NR interface provide ordering of user data and control signaling in both uplink and downlink directions. For example, EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 receive packets that can be referred to as Service Data Units (SDUs) and output packets that can be referred to as Protocol Data Units (PDUs). PDCP sublayers 208 and 210 can receive packets, for example, from the Internet Protocol (IP) layer, which are layered directly or indirectly above EUTRA PDCP sublayer 208 or NR PDCP sublayer 210. PDCP sublayers 208 and 210 can, for example, output packets to RLC sublayers 206A or 206B. Except in cases involving differences between SDU and PDU, for simplicity, this disclosure refers to both SDU and PDU as “packets”.
[0064] In some aspects, on the control plane, EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 can provide SRB. In some other aspects, the RRC sublayer of UE 102 ( Figure 2A(Not shown in the diagram) and the base station can exchange 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, IP packets, or Ethernet packets.
[0065] Figure 2B This is a block diagram of the example protocol stack 250. Figure 1A UE 102 communicates with the CU and DU according to this example protocol stack. For example, UE 102 can communicate with the DU (e.g., DU 174) and CU (e.g., CU 172) via example protocol stack 250. Example protocol stack 250 is functionally decomposed, such as... Figure 2B Example protocol stack 250 is shown in the diagram. The CU at any of base stations 104, 104A, 104B, 106, 106A, or 106B can retain all control and upper-layer functionality (e.g., RRC 214, SDAP 212, NR PDCP sublayer 210), while lower-layer operations (e.g., NR RLC sublayer 206B, NR MAC sublayer 204B, and NRPHY 202B) are delegated to the DU. To support connectivity to the 5GC, NR PDCP sublayer 210 provides SRBs to RRC 214, and NR PDCP sublayer 210 provides DRBs to SDAP 212 and SRBs to RRC 214.
[0066] Figures 3 to 5 and Figures 6A to 6D This is a sequence diagram illustrating several example communication processes in which the base station sends configuration to the UE and subsequently activates the configuration for communication between the UE and the base station. Generally, Figures 3 to 5 and Figures 6A to 6D Similar events and processes are labeled using similar reference numerals as shown in the attached diagram. For example Event 302 and Figure 4 Event 402 and Figure 5 Similar to event 502, process 390 is similar. Figure 4 Process 490 and Figure 5 The process is similar to 590, where differences are discussed below where appropriate. Apart from the differences shown in the figures and discussed below, any alternative implementations discussed for specific events (e.g., for messaging and processing) can be applied to other events labeled with similar reference numerals in the figures.
[0067] Figures 3 to 5 and Figures 6A to 6DThe discussion involves tuples. In the discussion, a tuple can be represented as a comma-separated list of elements enclosed in curly braces (e.g., {element1, element2, ..., elementN}).
[0068] Figure 3 This is a sequence diagram illustrating an example operation of the communication process 300 for cell handover within a CU and a DU. Figure 3 Base station 301 can be Figure 1A Base station 104 Figure 1B Base station 104A or 104B, Figure 1C Base station 164, or Figure 2A The implementation methods of eNB, ng-eNB 230 or gNB 232.
[0069] exist Figure 3 In the example shown, base station 301 includes CU 172 and DU 174, and DU 174 operates in cell 124A. At event 302, UE 102 initially uses the serving DU to communicate with DU 174 on the serving cell (e.g., cell 124A) and uses the serving CU to communicate with CU 172 via DU 174. DU 174 is the serving DU 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 may be configured for carrier aggregation (CA) and uses the serving DU to communicate in cell 124A and one or more other cells (e.g., Figure 1AUE 102 communicates with DU 174 on either cell 124B or 124C. DU 174 operates one or more other cells. Cell 124A and / or one or more other cells are the serving cells of UE 102. In other implementations, UE 102 communicates with DU 174 only on cell 124A. In some implementations, UE 102 communicates with DU 174 on cell 124A and / or one or more other cells (i.e., serving cells) via one or more TRPs. In the following description, procedures 394 and events 324, 350, 352, 354, and 326 occur or are performed on the serving cell. In some implementations, cell 124A may be a PCell. In such cases, other cells include SCells and / or one or more 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, the remaining cells may be other SCells and / or additional cells associated with a PCell or SCell. In the following description, base station 301 may be DU 174 only, CU 172 only, or both DU 174 and CU 172.
[0070] In event 302, UE 102 may transmit UL PDUs and / or UL control signals to base station 301 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 301 via a radio bearer, which may include SRBs and / or DRBs. Base station 301 may configure the radio bearer for UE 102. In some aspects, UE 102 may use 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 apply one or more security functions (e.g., integrity protection and / or encryption) to UL data packets to generate securely protected UL data packets and include the securely protected data packets in the UL PDU. In this respect, 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 can apply 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 may include one or more of the following: UL Control Information (UCI), CSI, Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ACK), HARQ Negation ACK, Scheduling Request, and / or Sounding Reference Signal (SRS).
[0071] Similarly, UE 102 may receive DL PDUs and / or DL control signals from base station 301 via one or more TRPs in cell 124A and / or one or more other cells. In some implementations, the DL control signals include downlink control information (DCI) and reference signals (e.g., synchronization signal block (SSB), CSI reference signal (CSI-RS), and / or tracking reference signal). Base station 301 may transmit the DCI via one or more TRPs on the physical downlink control channel (PDCCH) monitored by UE 102 in cell 124A and / or other cells. In some aspects, in order to transmit DL PDUs, CU 172 may use 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 DL data packets to generate securely protected DL data packets and include the securely protected DL packets in the DL PDU. In this respect, when UE 102 receives a DL PDU from CU 172 via DU 174, UE 102 can obtain the DL data packet by retrieving the securely protected DL data packet from the DL PDU and applying one or more security functions (e.g., decryption and / or integrity checks) to the securely protected DL data packet using at least one security key and at least one security algorithm (e.g., integrity protection algorithm and / or encryption algorithm). 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.
[0072] Security features may include integrity protection and / or encryption, and security keys may include integrity keys and encryption keys used for integrity protection / integrity checking and encryption / decryption, respectively. When integrity protection is enabled, the transmitter (e.g., one of UE 102 and CU 172) may generate an Integrity Message Authentication Code (MAC-I) to protect the integrity of UL or DL data packets. The transmitter may use the integrity key and integrity algorithm to encrypt the UL or DL data packets to obtain encrypted packets using the encryption algorithm. Therefore, in this case, the transmitter generates securely protected UL or DL packets including data packets and MAC-I.
[0073] When encryption is enabled, the transmitter can use an encryption key and an encryption algorithm to encrypt data packets and can include the encrypted data packets in a secure packet. When both integrity protection and encryption are enabled, the transmitter can use an integrity key and an integrity algorithm to generate a MAC-I for protecting data integrity, and use an encryption key and an encryption algorithm to encrypt the data along with the MAC-I to generate an encrypted packet and an encrypted MAC-I. The transmitter can then send the secure packet to the receiver (i.e., the other of UE 102 and CU 172).
[0074] When encryption is enabled, the receiver uses an encryption key and an encryption algorithm to decrypt the securely protected packet to obtain the data packet. The encryption key may be the same as or different from the encryption key used by the sender. Similarly, the encryption algorithm may be the same as or different from the encryption algorithm used by the sender.
[0075] When integrity protection is enabled, the receiver can use an integrity key and an integrity algorithm to perform integrity checks on securely protected packets. In some respects, the integrity key can be the same as the integrity key used by the sender. In some respects, the integrity algorithm can be the same as the integrity algorithm used by the sender.
[0076] When both encryption and integrity protection are enabled, the receiver uses an encryption key and an encryption algorithm to decrypt the securely protected packet to obtain the integrity-protected data packet. As mentioned above, the encryption key can be the same as or different from the encryption key used by the sender. Similarly, the encryption algorithm can be the same as or different from the encryption algorithm used by the sender. The receiver can then use the integrity key and integrity algorithm to perform an integrity check on the integrity-protected data packet. The integrity key can be the same as the integrity key used by the sender. The integrity algorithm can be the same as the integrity algorithm used by the sender.
[0077] The aforementioned security protections can be applied to measurement reports (e.g., at event 304), RRC reconfiguration messages (e.g., at event 318), RRC reconfiguration completion messages (e.g., at events 320 and 336), and data communications (e.g., at event 340). In some implementations, the security key may include an integrity key for integrity protection of control plane data packets such as RRC messages (e.g., at events 304, 318, 320, and 336). In other implementations, the security key may include an encryption key for encryption / decryption of control plane data packets such as RRC messages (e.g., at events 304, 318, 320, and 336). In still other implementations, the security key may include an integrity key for integrity protection of user plane data packets (e.g., transmitted via one or more DRBs). In still other implementations, the security key may include an encryption key for encryption / decryption of user plane data packets (e.g., transmitted via one or more DRBs).
[0078] 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 can send these configuration parameters and / or one or more first non-LTM TCI state configurations to CU 172. CU 172 can generate one or more messages (e.g., RRC reconfiguration messages) including the configuration parameters and / or one or more first non-LTM TCI state configurations, and can send these messages to UE 102 via DU 174. In other implementations, DU 174 can directly send the configuration parameters and / or one or more first non-LTM TCI state configurations to UE 102. In some implementations, the serving DU configuration is... CellGroupConfig Information elements (IEs) (e.g., as defined in 3GPP TS 38.331). In other implementations, the service DU configuration includes... CellGroupConfig Configuration parameters in IE. In some implementations, the service CU configuration includes PDCP configuration parameters, measurement configuration parameters, and / or radio bearer configuration parameters. In some implementations, the service CU configuration includes... MeasConfig IE and / or RadioBearerConfig IE (e.g., as defined in 3GPP TS 38.331), or including MeasConfig IE and / or RadioBearerConfig Configuration parameters in IE. Radio configuration parameters or RadioBearerConfig IE can configure one or more DRBs. In some implementations, the service DU configuration includes... CSI-MeasConfig IE or configuration parameters used for 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 may receive the service CU configuration or configuration parameters in the service CU configuration from CU 172 via DU 174. In other implementations, UE 102 may receive a portion of the service CU configuration and / or a portion of the service DU configuration from a base station other than base station 301, and receive the remainder of these configuration parameters from base station 301.
[0079] In some implementations, DU 174 and UE 102 may communicate with each other using one or more first non-LTM TCI state configurations, for example, in events 302, 318, 320, 324, 350, 354, and / or 326. In some implementations, DU 174 may send at least one first non-LTM TCI state activation / deactivation command to UE 102 (e.g., via a MAC control element (CE)) to activate one or more first non-LTM TCI state configurations. UE 102 activates one or more first non-LTM TCI state configurations in response to the one or more first non-LTM TCI state activation / deactivation commands. In some implementations, DU 174 includes a serving cell identifier (ID) (e.g., a serving cell index) in each of the one or more first non-LTM TCI state activation / deactivation commands to identify the first non-LTM TCI state configuration. Each serving cell ID may indicate the corresponding serving cell among the serving cells. In some implementations, the serving DU configuration includes a serving cell ID and can be configured to associate the serving cell ID with one or more first non-LTM TCI state configurations.
[0080] When communicating with base station 301, at event 304, UE 102 may send at least one measurement report to DU 174. In some implementations, the measurement report includes the serving cell of UE 102 (e.g., Figure 1AThe measurement results are from cell 124A (or cell 124A in Figure 2) and / or at least one non-serving cell. In some aspects, for each measurement report in the measurement report, at event 306, DU 174 may send a DU-to-CU message including the measurement report to CU 172. In some implementations, the DU-to-CU message at event 306 is an F1 Application Protocol (F1AP) message (e.g., a UL RRC messaging message). The serving cell includes cell 124A and / or other cells, and at least one non-serving cell includes cell 124B and / or an additional cell. In some implementations, the serving CU configuration includes at least one measurement configuration. Based on the at least one measurement configuration, at event 304, UE 102 may perform measurements and may send a measurement report to DU 174. In some implementations, the at least one measurement configuration may include one or more Layer 3 (L3) measurement configurations (e.g., MeasConfig IE), and the measurement report may include one or more L3 measurement reports.
[0081] Upon receiving one or more measurement reports from UE 102 (e.g., in response to this), CU 172 determines to prepare a first cell (also referred to as "Cell 1") as an LTM candidate cell for UE 102. For example, Cell 1 could be... Figure 1A Cell 124B. In some implementations, base station 301 determines to prepare a first cell for UE 102 in response to one or more measurement reports, the one or more measurement reports indicating that the first cell may be used by base station 301 to communicate with UE 102. In some implementations, base station 301 determines to prepare a first cell for UE 102 in response to one or more measurement reports, the one or more measurement reports indicating that the first cell is eligible to be an LTM candidate cell that may be used to communicate with UE 102. In some aspects, CU 172 determines to prepare the first cell as an LTM candidate cell for UE 102 if one or more measurement reports indicate that the signal strength and / or quality of the first cell is higher than a first predetermined threshold, the signal strength of the first cell is better than the strength and / or quality of the serving cell (e.g., cell 124A), and / or the signal strength of the first cell is better than the strength and / or quality of the serving cell by a first predetermined threshold. In some other aspects, CU 172 determines to prepare the first cell as an LTM candidate cell for UE 102 regardless of whether a measurement report is received from UE 102.
[0082] In response to determining that the first cell should be prepared as a candidate cell for LTM, at event 308, CU 172 may send a first CU-DU message to DU 174 to prepare the first cell as a candidate cell for LTM of UE 102. In some implementations, CU 172 includes the cell identifier (ID) 1 of the first cell in the first CU-DU message to request DU 174 to prepare the first cell as a candidate cell for LTM of UE 102. As an example, cell ID 1 may be a Cell Global Identifier (CGI). As another example, cell ID 1 may be part of a CGI. As a further example, cell ID 1 may be a Physical Cell ID (PCI). In some implementations, CU 172 includes an LTM indicator in the first CU-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 Establishment In IE, and the LTM information establishes IE Included in the first CU to DU message. In other implementations, CU 172 includes the LTM indicator. LTM Information Modification In IE, and the LTM Information Modification The IE is included in the first CU to DU message.
[0083] In response to the first CU to DU message, DU 174 can generate a first LTM DU configuration (referred to as LTMDU configuration 1) for UE 102, which configures a first cell for LTM. In some implementations, CU 172 includes the first LTM configuration ID (referred to as LTM ID 1) in the first CU to DU message, and DU 174 can associate LTM ID 1 and / or cell ID 1 with LTM DU configuration 1. At event 310, DU 174 sends a first DU to CU message including LTM DU configuration 1 to CU 172 in response to the first CU to DU message.
[0084] Events 308 and 310 Figure 3 This process is collectively referred to as the LTM preparation process 390.
[0085] 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. Where CU 172 and DU 174 perform multiple LTM preparation procedures (e.g., procedures 390 and LTM preparation procedures 2 to 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.
[0086] In some implementations, CU 172 does not include the LTM reference DU configuration in the first CU-DU message. In such cases, DU 174 can generate the LTM reference DU configuration and include it in the first DU-CU message. In some implementations, DU 174 can generate LTM DU configuration 1 as an incremental configuration to enhance the LTM reference DU configuration. For example, LTM DU configuration 1 may include changes, deletions, and / or additions to the LTM reference DU configuration. In other implementations, DU 174 can generate LTM DU configuration 1 as a complete configuration, for example, a standalone configuration, rather than generating the LTM DU configuration based on the LTM reference DU configuration.
[0087] In some implementations, CU 172 includes the LTM reference DU configuration request in the first CU-DU message. In such implementations, DU 174 can generate an LTM reference DU configuration and, in response to the request, include the LTM reference DU configuration in the first DU-CU message. In some implementations, CU 172 determines whether UE 102 supports LTM reference configuration. If CU 172 determines that UE 102 supports LTM reference configuration, then CU 172 includes the 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. If CU 172 determines that UE 102 does not support LTM reference configuration, then CU 172 may 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 a complete configuration and 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 an LTM reference DU configuration request, instead of 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 yet another implementation, DU 174 determines whether UE 102 supports the LTM reference configuration. If DU 174 determines that UE 102 supports the LTM reference configuration, then DU 174 includes the LTM reference DU configuration in the first DU-CU message. If DU 174 determines that UE 102 does not support the LTM reference configuration, then DU 174 may not include the LTM reference DU configuration in the first DU-CU message.
[0088] In some implementations, CU 172 includes the LTM reference DU configuration in the first CU-DU message. In some implementations, CU 172 may receive the LTM reference DU configuration from the additional DU during the LTM preparation process, as described above and also as follows. Figure 4 In other implementations, CU 172 is pre-configured with an LTM reference DU configuration. In some implementations, DU 174 can generate LTM DU configuration 1 as an incremental configuration with changes, deletions, and / or deletions to enhance 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 (e.g., standalone) configuration, i.e., not based on the LTM reference DU configuration.
[0089] 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 an LTM reference DU configuration, then CU 172 can determine that LTM DU configuration 1 is a complete configuration. If the first CU to DU message includes an LTM reference DU configuration, then CU 172 can determine that LTM DU configuration 1 is an incremental configuration.
[0090] 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 remainder 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... CellGroupConfig IE (e.g., as defined in 3GPP TS 38.331). 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.
[0091] To prepare the first cell as an LTM candidate cell for UE 102, at event 312, CU 172 may send a second CU-DU message to DU 174. The second CU-DU message may include a CSI resource configuration (referred to as CSI resource configuration 1) and / or an LTM SSB configuration (referred to as LTM SSB configuration 1) to request DU 174 to generate one or more CSI report configurations (e.g., LTM CSI report configuration 1, and possibly other CSI report configurations). The CSI resource configuration (e.g., LTM CSI resource configuration 1) may include configuration parameters that configure at least one reference signal (RS) transmitted on the first cell. At least one RS may include one or more SSBs and / or one or more CSI-RSs. The LTM SSB configuration may include SSB configuration parameters that configure the SSB frequency, subcarrier spacing, SSB periodicity, SSB location, and / or SSB power of the SSB transmitted on the first cell.
[0092] Upon receiving the CSI resource configuration (e.g., in response to this), DU 174 may generate one or more CSI report configurations based on the CSI resource configuration and include one or more CSI report configurations 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 one or more CSI report configurations configure UE 102 to send CSI reports based on RS measurements.
[0093] At event 314, DU 174 sends a second DU-to-CU message to CU 172, including the configuration of the second service DU. In some implementations, the CSI resource configuration includes one or more... LTM-CSI-ResourceConfig-r18 IE. In other implementations, CSI resource configuration includes... ltm-CSI-ResourceConfigToAddModList Fields or IE. In some implementations, the second service DU configuration is... CellGroupConfig IE.
[0094] In some implementations, CU 172 includes Cell ID 1 and / or LTM ID 1 in the second CU-DU message. In one implementation, CU 172 does this to indicate that the CSI resource configuration is associated with the first cell. In another implementation, CU 172 does this so that DU 174 associates LTM ID 1 with the first cell, Cell ID 1, LTM DU configuration 1, and / or one or more CSI reporting configurations. 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 one or more CSI reporting configurations). In such implementations, CU 172 may or may not include LTM ID 1 in the first CU-DU message.
[0095] In some other implementations, CU 172 includes CSI resource configuration in the first CU to DU message, and DU 174 includes one or more CSI report configurations in the first DU to CU message.
[0096] In some implementations, DU 174 may send 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 may send an additional DU to CU message in response to receiving an additional CU to DU message from CU 172. In other implementations, DU 174 may send 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 requirements information).
[0097] Events 312 and 314 Figure 3 This is collectively referred to as the LTM CSI report configuration and / or LTM ID configuration process 392.
[0098] Upon receiving the first DU to CU message, CU 172 can generate a first LTM candidate configuration (referred to as LTM candidate configuration 1) that includes LTM DU configuration 1, and can generate a first RRC reconfiguration message that includes 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.
[0099] At event 316, CU 172 can send a third CU-DU message to DU 174, which includes the first RRC reconfiguration message.
[0100] At event 318, DU 174 can send the first RRC reconfiguration message to UE 102.
[0101] At event 320, in response to receiving the first RRC reconfiguration message, UE 102 can send the first RRC reconfiguration complete message to DU 174.
[0102] At event 322, DU 174 can then send a third DU to CU message to CU 172, which includes the first RRC reconfiguration complete message.
[0103] If the first DU to CU message includes an LTM reference DU configuration, then CU 172 can generate an LTM reference configuration that includes the LTM reference DU configuration. In this case, CU 172 can 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 can generate LTM CU configuration 1 as an incremental configuration based on the LTM reference CU configuration. For example, the incremental configuration can include changes, additions, or deletions regarding 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 can generate LTM CU configuration 1 as a complete (e.g., standalone) configuration. Alternatively or additionally, CU 172 can send a second RRC reconfiguration message including the LTM reference configuration to UE 102 via DU 174, similar to events 316 and 318 described above. In response, UE 102 can send a second RRC reconfiguration complete message to CU 172 via DU 174, similar to events 320 and 322 described above. 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.
[0104] 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. 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 can generate LTM candidate configuration 1 as a complete configuration. If LTM DU configuration 1 is an incremental configuration, then CU 172 can generate 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.
[0105] When CU 172 executes procedure 392, CU 172 may include the second service DU configuration in the first RRC reconfiguration message. When CU 172 does not execute procedure 392, CU 172 may send a third RRC reconfiguration message including the second service DU configuration to UE 102 via DU 174, similar to events 316 and 318 above. In response, UE 102 may send a third RRC reconfiguration completion message to CU 172 via DU 174, similar to events 320 and 322 above.
[0106] In some implementations, CU 172 includes the CSI resource configuration in the first, second, or third RRC reconfiguration message. In other implementations, CU 172 may send a fourth RRC reconfiguration message including the CSI resource configuration to UE 102 via DU 174, similar to events 316 and 318 above. In response, UE 102 may send a fourth RRC reconfiguration complete message to UE 102 via DU 174, similar to events 320 and 322 above.
[0107] In some implementations, DU 174 may send a DU-to-CU message to CU 172, which includes early synchronization information for UE 102. The DU-to-CU message may 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 may send a fourth DU-to-CU message in response to receiving a fourth CU-to-DU message from CU 172. In other implementations, DU 174 may send 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 this implementation, if DU 174 determines that UE 102 supports (i.e., is capable of) early UL synchronization with the LTM candidate cell (e.g., UE 102 supports early TA acquisition with the LTM candidate cell, early RA on the LTM candidate cell, or TA measured by the UE), then DU 174 may send a fourth DU to CU message. 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 may send a CU to DU message that includes an early synchronization information request (e.g., IE), and DU 174, in response to the early synchronization information request, includes the early synchronization information in the DU to CU message. The CU to DU message may be a first CU to DU message, a second CU to DU message, or a fourth CU to DU message. In this implementation, if CU 172 determines that UE 102 supports early UL synchronization with the LTM candidate cell, then CU 172 does so. If CU 172 determines that UE 102 does not support early UL synchronization with the LTM candidate cell, then CU 172 does not request DU 174 to provide early synchronization information for UE 102. If CU 172 receives early synchronization information, then CU 172 includes the early synchronization information in a first RRC reconfiguration message, a second RRC reconfiguration message, a third RRC reconfiguration message, or a fourth RRC reconfiguration message. If CU 172 receives early synchronization information, then CU 172 can send a fifth RRC reconfiguration message including the early synchronization information to UE 102 via DU 174, similar to events 316 and 318 above. In response, UE 102 can send a fifth RRC reconfiguration complete message to CU 172 via DU 174, similar to events 320 and 322 above.
[0108] In some implementations, the early synchronization information may include a random access channel (RACH) configuration (referred to as RACH configuration 1) and / or one or more TCI state configurations (referred to as TCI state configuration 1). In some implementations, the early synchronization information request may include a request for the RACH configuration. If the early synchronization information request includes a request for the RACH configuration, then DU 174 includes the RACH configuration in the early synchronization information or in a DU-to-CU message (e.g., a first DU-to-CU message, a second DU-to-CU message, or a fourth DU-to-CU message). In some aspects, if the early synchronization information request does not include a request for the RACH configuration, then DU 174 neither includes the RACH configuration in the early synchronization information nor in the DU-to-CU message.
[0109] In some implementations, CU 172 may include one or more other LTM-related configurations for the first cell in the first RRC reconfiguration message, the second RRC reconfiguration message, the third RRC reconfiguration message, the fourth RRC reconfiguration message, and / or the fifth RRC reconfiguration message. For example, other LTM-related configurations may include the PCI and / or LTM SSB configurations for the first cell.
[0110] Events 316, 318, 320, and 322 are in Figure 3 This is collectively referred to as LTM configuration delivery process 394. In the following description, LTM configuration delivery process 1 can be used to represent process 394. The second RRC reconfiguration message, the third RRC reconfiguration message, the fourth RRC reconfiguration message and / or the fifth RRC reconfiguration message, as well as the second RRC reconfiguration completion message, the third RRC reconfiguration completion message, the fourth RRC reconfiguration completion message and / or the fifth RRC reconfiguration completion message, the associated CU to DU message and / or the associated DU to CU message can also be considered as part of LTM configuration delivery process 394. In some implementations, the aforementioned RRC reconfiguration message and RRC reconfiguration completion message can be respectively... RRCReconfiguration Messages and RRCReconfigurationComplete information.
[0111] In some implementations, the first CU to DU message can be UE Context Modification Request Message, and the first DU to CU message can be UE context modification response Message. In some implementations, the second CU to DU message can be... UE Request for amendments Message, and the second DU to CU message can be UE context modification response Message or UE context modification requires beg Message. In UE context modification requirements In the case of a message, CU 172 can respond to UE context modification requirements Message sent to DU 174 UE context modification confirmation Message. In some implementations, the third CU to DU message can be... DL RRC Message passing Message. In other implementations, the third CU to DU message can be... UE Context Modification Request Messages. In some implementations, the third DU to CU message can be... UL RRC Messaging Message. In other implementations, the third DU to CU message can be... UE context modification response information.
[0112] In some implementations, the LTM reference CU configuration may differ from the service CU configuration. In some implementations, a portion of the LTM reference CU configuration may be identical to a portion of the service CU configuration, and the remainder of the LTM reference CU configuration may differ from the remainder of the service CU configuration. In still other implementations, the LTM reference CU configuration may be identical to the service CU configuration.
[0113] In some implementations, the LTM reference CU configuration includes PDCP configuration parameters, measurement configuration parameters, and / or radio bearer configuration parameters. In some implementations, the LTM CU configuration 1 includes (e.g., as defined in 3GPP TS 38.331) MeasConfig IE and / or RadioBearerConfig IE, or including MeasConfig IE and / or RadioBearerConfig Configuration parameters in Internet Explorer.
[0114] In some implementations, LTM Reference CU Configuration 1 and / or the LTM Reference CU Configuration may include PDCP configuration parameters, measurement configuration parameters, and / or radio bearer configuration parameters. In some implementations, LTM CU Configuration 1 or the LTM Reference CU Configuration may include (e.g., as defined in 3GPP TS 38.331) MeasConfig IE and / or RadioBearerConfig IE, or including MeasConfig IE and / or RadioBearerConfig Configuration parameters in Internet Explorer.
[0115] In some implementations, LTM DU configuration 1 may include multiple configuration parameters for UE 102 to communicate with DU 174 on the first cell. In some implementations, the multiple configuration parameters may 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, multiple configuration parameters may include specific cell configurations (e.g., SpCellConfig IE) and / or one or more SCell configurations (e.g., SCellConfig (IE). In some implementations, LTM DU configuration 1 can be... CellGroupConfig IE (e.g., as defined in 3GPP TS 38.331). In other implementations, LTM DU configuration 1 may include CellGroupConfig Configuration parameters in Internet Explorer.
[0116] In some implementations, LTM DU configuration 1 may include 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 other implementations, the LTM CU configuration 1 includes a first TCI state 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 may configure one or more RSs or one or more RS resources associated with cell 1. RSs may include SSBs and / or CSI-RSs. RS resources may include SSB resources and / or CSI-RS resources. In some implementations, each first RS resource configuration in the first RS resource configuration may include an RS resource configuration ID. In some implementations, the first RS resource configuration is (similar to) CSI-ResourceConfig IE. In some implementations, the first report configuration configures one or more UL resources (e.g., Physical Uplink Control Channel (PUCCH) resources or Physical Uplink Shared Channel (PUSCH) resources) on the first cell for UE 102 to transmit measurement results (e.g., CSI reports or LTM CSI reports). In some implementations, each first report configuration in the first report configuration may include one or more RS resource configuration IDs identifying one or more RS resource configurations included in the first RS resource configuration. In some implementations, each first TCI state configuration in the first TCI state configuration configures one or two DLRSs associated with the TCI state of the corresponding Quasi-Co-location (QCL) type. DL RSs may be associated with cell 1.
[0117] After receiving the LTM-related configuration and the second service DU configuration, or after receiving the aforementioned RRC reconfiguration message, UE 102 can perform measurements on at least one first RS, generate at least one first L1 measurement result based on the measurements, and at event 324, send 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 first RS and / or the transmission mode of the first RS are configured in the CSI report configuration, LTM SSB configuration, and / or CSI resource configuration. UE 102 can perform measurements on the first RS according to the CSI report configuration, LTM SSB configuration, and / or CSI resource configuration.
[0118] After receiving the LTM-related configuration and the second service DU configuration, or after receiving the aforementioned RRC reconfiguration message, UE 102 may perform measurements on at least one second RS, generate at least one second L1 measurement result based on the measurements, and send 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 one or more second CSI resource configurations, which are included in the service DU configuration and / or the second service DU configuration (used for communication between UE 102 and the S-DU at event 302). UE 102 may perform 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.
[0119] At event 350, after sending the RACH configuration to UE 102 via CU 172, DU 174 can send a PDCCH command to UE 102 to instruct UE 102 to send the RA preamble on the first cell. In response to the PDCCH command, UE 102 can send the RA preamble on the first cell. DU 174 can include PDCCH command information in the PDCCH command. The PDCCH command information may include the RA preamble index, UL or supplementary UL indicator, SSB index, and / or physical RACH mask index. In some implementations, DU 174 includes LTM ID 1 in the PDCCH command to indicate the first cell.
[0120] At event 352, UE 102 identifies the first cell based on LTM ID 1 in the PDCCH command and can use the PDCCH command information to send an RA preamble to DU 174 on the first cell. Accordingly, DU 174 can receive the RA preamble based on the PDCCH command information. In some implementations, DU 174 can determine the SSB index based on the L1 measurement report, CSI resource configuration, CSI report configuration, and / or LTM SSB configuration received at event 324. In some implementations, the L1 measurement report may include the SSB index. In other implementations, the L1 measurement report may include a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) Block Resource Indicator (SSBRI) corresponding to the SSB index. In such implementations, DU 174 determines the SSB index based on the SSBRI.
[0121] At event 324, in some implementations, DU 174 determines whether to send a PDCCH command based on the L1 measurement results. In some implementations, if the L1 measurement results indicate that the first cell is eligible for UE 102 to perform RA for early UL synchronization, DU 174 may send a PDCCH command. If the L1 measurement results indicate that the first cell is not eligible for UE 102 to perform RA for early UL synchronization, DU 174 avoids sending a PDCCH command. In other implementations, if the L1 measurement results indicate that the first cell is eligible for UE 102 access, DU 174 may send a PDCCH command. If the L1 measurement results indicate that the first cell is not eligible for UE 102 access, DU 174 avoids sending a PDCCH command. In yet another implementation, DU 174 may send a PDCCH command after receiving an RRC reconfiguration complete message (event 320), regardless of the L1 measurement results.
[0122] At event 354, after sending the L1 measurement report (event 324) or the RA preamble (event 352), UE 102 may send an additional L1 measurement report to DU 174, similar to event 324. DU 174 determines the command to instruct UE 102 to perform an LTM cell handover to the first cell based on the additional L1 measurement report and / or the L1 measurement report obtained at event 324.
[0123] At event 326, in response to this determination, DU 174 can generate an LTM cell handover command (e.g., MAC CE) including LTM ID 1, and can send the LTM cell handover command to UE 102.
[0124] At event 328, in response to this confirmation, DU 174 can send a DU-CU cell handover notification message to CU 172.
[0125] At event 332, in response to an LTM cell handover command, UE 102 can perform an LTM cell handover to the first cell. For example, when UE 102 receives an LTM cell handover command, UE 102 can identify LTM candidate configuration 1 from LTM ID 1 and can use LTM candidate configuration 1 to access the first cell. Depending on the implementation, UE 102 can also cease communication on the serving cell in response to the LTM cell handover command.
[0126] At event 334, DU 174 detects that UE 102 has accessed the first cell in event 332. In response to this detection, DU 174 can send an access success message to CU 172 to indicate that UE 102 has accessed the first cell.
[0127] At event 336, as part of the LTM cell handover, UE 102 can access the first cell and send an RRC reconfiguration complete message to DU 174 via the first cell.
[0128] At event 338, DU 174 can send a DU-CU message to CU 172 including an RRC reconfiguration completion message (e.g., UL RRC Message Transmission (Message). Subsequently, DU 174 can send a fifth DU-CU message to CU 172, including an RRC reconfiguration complete message.
[0129] 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 can derive the TA value based on the RA preamble (e.g., the reception timing of the RA preamble). In another implementation, DU 174 can derive the TA value from the serving cell (e.g., Figure 1A and / or Figure 1B The TA value is derived from the UL transmission from UE 102 on cell 124A. UE 102 can apply the TA value to synchronize with the first cell in the UL transmission. After applying the TA value, UE 102 can send 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 can use UL grant to send the first UL transmission on the first cell. In this case, the first UL transmission is a PUSCH transmission. In some implementations, the PUSCH transmission includes an RRC reconfiguration completion message for event 336. In some implementations, the UL grant is a configured grant, and LTM Candidate Configuration 1 or LTM DU Configuration 1 includes a configured grant configuration that configures the configured grant. In other implementations, the UL grant is a dynamic grant that UE 102 can receive on the PDCCH on the first cell. After sending the first UL transmission, UE102 can receive the PDCCH transmission addressing the Cell Radio Network Temporary Identifier (C-RNTI) of UE102, and determine that the LTM cell handover has been successfully completed in response to receiving the PDCCH transmission.
[0130] PDCCH transmissions may include UL grants or DL assignments. In the case of UL grants, UE 102 can use the UL grant to send PUSCH transmissions to DU 174 on the first cell. In the case of DL assignments, DU 174 can send Physical Downlink Shared Channel (PDSCH) transmissions to UE 102 on the first cell according to the DL assignment. At event 334, DU 174 may send an access success message to CU 172 after receiving the first UL transmission, sending a PDCCH transmission, receiving a PUSCH transmission, or sending a PDSCH transmission (e.g., in response to this).
[0131] In other implementations, DU 174 does not include the TA value in the LTM cell handover command at event 326. If the LTM cell handover command does not include the TA value, then at event 332, UE 102 can perform an RA procedure on the first cell based on 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 Physical Random Access Channel (PRACH) resources, the association between SSB and PRACH resources, and / or one or more PRACH timings. If UE 102 successfully completes the RA procedure at event 332, UE 102 determines that it has successfully completed the LTM cell handover to the first cell. 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 may send an RA preamble (i.e., message 1) on the first cell and may receive an RA response (i.e., message 2) from DU 174 on the first cell in response to the RA preamble. The UE may then use the UL grant in the RA response to send message 3 on the first cell, and in response, DU 174 may send message 4 to UE 102 on the first cell. In some implementations, message 4 is a DCI. In the case where the RA procedure is a CBRA, UE 102 determines that the contention resolution was successful in response to receiving message 4. In the case where the RA procedure is a CBRA, the RA preamble is a dedicated preamble, and UE 102 determines that the contention resolution was successful in response to receiving the RA response. During a two-step RA procedure, UE 102 may send message A on the first cell, and in response, DU 174 may send message B to UE 102 on the first cell. In cases where the RA procedure is a CFRA or CBRA procedure, UE 102 determines that the contention resolution was successful upon receiving message B. UE 102 may include the RRC reconfiguration completion message of event 336 in message 3 or message A. Alternatively or additionally, UE 102 may send the RRC reconfiguration completion message of event 336 after completing the RA procedure. DU 174 may send an access success message of event 334 to CU 172 after receiving message 3 or message A, the RRC reconfiguration completion message of event 336, or sending message 4 or message B.
[0132] In some implementations, DU 174 may include 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 a first cell. In some implementations, the first set of LTM CFRA configuration parameters may include one or more of 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 a normal UL (NUL) or SUL. For example, if the first UL or SUL indicator indicates UL (e.g., the first UL or SUL indicator is set to a first value), then UE 102 may perform a CFRA procedure on UL. If the first UL or SUL indicator indicates SUL (e.g., the first UL or SUL indicator is set to a second value), then UE 102 may perform a CFRA procedure on SUL. At event 332, UE 102 can use LTM CFRA configuration parameters and at least one RACH configuration to perform a CFRA procedure to access the first cell. LTM candidate configuration 1 may include a RACH configuration. In some aspects, the RACH configuration may not be configured for early UL synchronization. In some implementations, the RACH configuration may be configured for LTM cell handover. In some implementations, at least one RACH configuration may include a common RACH configuration (e.g., RACH- ConfigCommon IE) and / or general 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, RACH configuration includes dedicated RACH configuration (e.g., RACH-ConfigDedicated IE). DU 174 can perform the CFRA procedure with UE 102 based on the first set of LTM CFRA configuration parameters and RACH configuration.
[0133] In some implementations, DU 174 may determine 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 may obtain (e.g., retrieve, derive, calculate, and / or determine) one or more measurement results from the measurement report. In some implementations, one or more measurement results may include the measurement results of a first SSB identified by a first SSB index. DU 174 may transmit the first SSB 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. 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.
[0134] In some implementations, DU 174 can configure a first set of LTM CFRA configuration parameters. DU 174 can configure one or more additional sets of LTM CFRA configuration parameters, and each of these additional sets may include one or more of the following: RA preamble index, SSB index, PRACH mask index, and / or UL or SUL indicator of the first cell. In some implementations, the first set and / or one or more additional sets can be specifically configured for the first cell. In other implementations, DU 174 can configure the first set and / or one or more additional sets for any cell operated by DU 174. In some implementations, DU 174 can configure the first set and / or one or more additional sets for one of UL (i.e., NUL) and SUL. In other implementations, DU 174 can configure the first set for one of UL and SUL and configure an additional set for the other of UL and SUL.
[0135] In some implementations, DU 174 identifies the first SSB index based on the measurement report as described above, and DU 174 identifies the first set of LTM CFRA configuration parameters based on the first SSB index. In some implementations, DU 174 may determine the value of the first UL or 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 or SUL indicator to a first value indicating UL (i.e., NUL). If the measurement result of the first SSB is above (or equal to) the third predetermined threshold, DU 174 sets the first UL or SUL indicator to a second value indicating SUL. In another example, if the measurement result is above (or equal to) the third predetermined threshold, DU 174 sets the first UL or SUL indicator to a first value indicating UL (i.e., NUL). If the measurement result of the first SSB is below (or equal to) the third predetermined threshold, DU 174 sets the first UL or SUL indicator to a second value indicating SUL. In other implementations, DU 174 may determine the value of the first UL or 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, then DU 174 sets the first UL or SUL indicator to a first value. In some aspects, if LTM DU configuration 1 includes a RACH configuration for SUL and may or may not include a RACH configuration for UL, then DU 174 may set the first UL or SUL indicator to a second value. In some other aspects, DU 174 may determine the value of the first UL or SUL indicator based on the measurement result of the first SSB as described above. In yet another implementation, DU 174 sets the first UL or 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 or SUL indicator to a pre-configured value (e.g., a second value), for example, because DU 174 is pre-configured to do so.
[0136] In some implementations, the first predetermined threshold, the second predetermined threshold, and the third predetermined threshold may be the same threshold (e.g., have the same threshold value). In other implementations, at least two of the first predetermined threshold, the second predetermined threshold, and the third predetermined threshold are different or are set to different values.
[0137] At event 340, after completing the LTM cell handover to the first cell as described above, UE 102 communicates with DU 174 and CU 172 via the first cell using LTM candidate configuration 1. In some aspects, in the case of the LTM reference configuration, UE 102 may first apply the LTM reference configuration and then apply LTM candidate configuration 1 to enhance the LTM reference configuration.
[0138] In some implementations, each TCI state configuration in the TCI state configuration may include a TCI state ID. In some implementations, DU 174 will include the first TCI state ID of the first TCI state configuration in the TCI state configuration. DU-CU cell handover notification In messages and / or LTM cell handover commands. UE 102 can identify the first TCI state configuration in the TCI state configuration based on the first TCI state ID, and can apply the first TCI state configuration in events 332, 336, and / or 340 to transmit UL and / or DL transmissions with DU 174. DU 174 can apply the first TCI state configuration in events 332, 336, and / or 340 to transmit UL and / or DL transmissions with UE 102. In other implementations, where DU 174 uses separate TCI states, the DL TCI state and the UL TCI state can have different TCI state IDs. In such cases, DU 174 can include the first TCI state ID of the DL and / or the second TCI state ID of the UL in the TCI state configuration. DU-CU cell handover communication Know In messages and / or LTM cell handover commands, these TCI state IDs identify the first TCI state configuration and the second TCI state configuration. UE 102 can identify 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 can apply the first TCI state configuration and the second TCI state configuration in events 332, 336, and / or 340 to transmit DL and UL transmissions with DU 174, respectively. DU 174 can identify 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 can apply the first TCI state configuration and the second TCI state configuration in events 332, 336, and / or 340 to transmit DL and UL transmissions with UE 102, respectively.
[0139] In some implementations, before or after sending the LTM cell handover command, or during, before or after, procedures 390 or 392, CU 172 may, together with DU 174, prepare additional cells (i.e., cells 2 to N) as LTM candidate cells for UE 102, as described above. N is an integer greater than 1. For example, CU 172 may, together with DU 174, perform additional LTM preparation procedures 2 to N to prepare cells 2 to N respectively. Each LTM preparation procedure in LTM preparation procedures 2 to N is similar to procedure 390. In LTM preparation procedures 2 to N, CU 172 may receive LTM DU configurations 2 to N respectively configuring cells 2 to N for LTM. CU 172 may generate LTM candidate configurations 2 to N respectively including LTM DU configurations 2 to N. CU 172 assigns LTM IDs 2 to N to identify LTM DU configurations 2 to N and LTM candidate configurations 2 to N respectively. CU 172 can obtain CSI resource configurations 2 to N, and together with DU 174, perform CSI report configuration and / or LTM ID configuration procedures 2 to N to obtain CSI report configurations 2 to N, as described for CSI resource configuration 1 and CSI report configuration 1. CU 172 can obtain RACH configurations 2 to N for cells 2 to N, as described for RACH configuration 1. CU 172 can obtain TCI state configurations 2 to N for cells 2 to N, as described for TCI state configuration 1. Each of the CSI report configuration and / or LTM ID configuration procedures 2 to N is similar to procedure 392. CU 172 can obtain LTM SSB configurations 2 to N for cells 2 to N, as described for LTM SSB configuration 1. In some implementations, CU 172 may perform LTM configuration delivery procedures 2 to N with UE 102 to send the following tuple lists to UE 102 respectively: {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 LTM configuration delivery procedure in LTM configuration delivery procedures 2 to N is similar to procedure 394. In other implementations, CU 172 includes the tuple list in the first RRC reconfiguration message.
[0140] To simplify the following description, tuples 1 through N are used to 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), LTMSSB configuration 1 (if obtained)}, …, {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)}. In some implementations, CU 172 includes tuples 1 through N in RRC reconfiguration messages 1, …N within LTM configuration delivery processes 1 through N. RRC reconfiguration message 1 is the first RRC reconfiguration message for events 316 and / or 318. In some implementations, CU 172 includes tuples 1 through N in the container IE (e.g., LTM -Config IE Tuples 1 through N are included in RRC reconfiguration messages 1 through N, respectively. In other implementations, CU 172 includes tuples 1 through N in container IE 1 (e.g., LTM). -Config In IE), and include container IE 1 in the first RRC reconfiguration message.
[0141] In some implementations, CU 172 can include CSI resource configurations from 1 to N instead of tuples in the container IE, where N is an integer greater than zero.
[0142] At event 342, after receiving an access success message at event 334, or after receiving a DU to CU message at event 338, in some implementations, CU 172 may send a CU to DU message to DU 174. In one implementation, CU 172 may send a CU to DU message to release the radio resources and / or configurations configured for UE 102 in the serving cell. In another implementation, CU 172 may send a CU to DU message to release some LTM candidate cells from LTM candidate cells 2 to N.
[0143] At event 344, in response to the CU to DU message, DU 174 can send a DU to CU message to CU 172. In some implementations, the CU to DU message at event 342 and the DU to CU message at event 344 are respectively... UE Context Modification Request Messages and UE context modification response information.
[0144] In some implementations, the LTM ID, LTM cell handover command, and RRC reconfiguration message in the PDCCH command can be represented in different formats. For example, the PDCCH command or LTM cell handover command may include a first field to include LTMID 1, and the first RRC reconfiguration message may include a second field to include LTM ID 1. In some implementations, the first field and the second field have different formats or code processing schemes. For example, the first field can use a binary format with bits representing a value range of 0, ..., 7 (i.e., a 3-bit wide field), and the second field can use an integer format with a value range of 1, ..., 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 a first field with a binary value of 111b is equivalent to a second field with an integer value of 8. In this example, the first field is a bitmap of binary values, and there is a mapping from the binary values of the first field to the integer values of the second field.
[0145] Events 304, 306, and 324, along with processes 390, 392, and 394, are in Figure 3 In this disclosure, and elsewhere, the process is collectively referred to as CU-DU-LTM configuration procedure 396. Events 304, 306, 350, 352, 354, 326, 328, 332, 334, 336, 338, and 340, together with procedures 390, 392, and 394, are... Figure 3 The rest of this disclosure is collectively referred to as CU-DU-LTM process 380.
[0146] Figure 4 This is a sequence diagram illustrating an example operation of the communication process 400 for inter-DU cell handover within a CU. Figure 4 Base station 401 can be Figure 1A Base station 104 Figure 1B Base station 104A or 104B, Figure 1C Base station 164, or Figure 2A The implementation methods of eNB, ng-eNB 230 or gNB 232.
[0147] exist Figure 4In the example shown, base station 401 includes CU 172, S-DU 174A, and candidate DU (e.g., C-DU) 174B. As an example, S-DU 174A can operate cell 124A and optionally operate one or more additional cells, while C-DU 174B can operate a different first cell (e.g., cell 124C). Communication procedure 400 is an intra-CU inter-DU communication procedure similar to communication procedure 300. Therefore, the description for communication procedure 300 can generally be applied to communication procedure 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 documentation can be applied to C-DU 174B. The differences between communication procedures 300 and 400 are described below.
[0148] At event 402, UE 102 uses the serving DU configuration to communicate with S-DU 174A on one or more serving cells (e.g., cell 124A and / or other cells), and uses the serving CU configuration to communicate with CU 172 via S-DU 174A. UE 102 and CU 172 can perform security protection on the data transmitted between UE 102 and CU 172 via S-DU 174A and C-DU 174B, as described above. Figure 3 For example, data for which security protection can be applied may include data packets (e.g., data packets starting at event 402), measurement reports (event 404), RRC reconfiguration messages and RRC reconfiguration completion messages (process 494), RRC reconfiguration completion messages (event 436), and data packets (data packets at event 440).
[0149] In some implementations, CU 172 and S-DU 174A can perform LTM configuration procedure 396 or LTM procedure 380 with UE 102, as described above. Figure 3 As described above, in the case of procedure 380, UE 102 can perform an LTM cell handover to the first cell (e.g., cell 124B), as described above regarding... Figure 3 As described above. After a successful LTM cell handover, the first cell becomes the serving cell, and cell 124A and / or other cells are no longer the serving cells of UE 102. In the case of procedure 396, UE 102 does not perform an LTM cell handover.
[0150] During the communication that begins at event 402, at events 404 and / or 406, UE 102 may send at least one measurement report (e.g., an L3 measurement report) to CU 172 via S-DU174A. Based on the measurement report, CU 172 determines that cell 1 (e.g., cell 124C operated by C-DU 174B) is ready for UE 102 for LTM. Cell 1 is identified by a cell ID (i.e., cell ID 1). In response to this determination, CU 172 may perform an LTM preparation procedure 490 with C-DU 174B to (request C-DU 174B) prepare cell 1 as an LTM candidate cell for UE 102. In the LTM preparation procedure 490, CU 172 may send 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 may send a first DU-to-CU message to CU 172, including the LTM DU configuration (e.g., LTM DU configuration 1), similar to event 310. CU 172 may or may not request the LTM reference DU configuration in the first CU-to-DU message, as described above regarding... Figure 3 As stated above, the C-DU 174B may or may not include the LTM reference DU configuration in the first DU to CU message, as mentioned above. Figure 3 As stated above.
[0151] In some implementations, if CU 172 receives the LTM reference DU configuration from S-DU 174A, as described above... Figure 3 As described above, CU 172 can include the LTM reference DU configuration in the first CU-DU message, and C-DU 174B can generate an LTM DU configuration as an incremental configuration based on this 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 can receive the LTM reference DU configuration from C-DU 174B, for example, in the first DU-CU message or an additional DU-CU message, as described above. Figure 3 In such cases, CU 172 can generate an LTM reference configuration that includes the LTM reference DU configuration. CU 172 may or may not include the LTM reference CU configuration in the LTM reference configuration.
[0152] 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 can send a second CU-DU message to S-DU 174A, which includes CSI resource configuration (e.g., CSI resource configuration 1) and / or LTM SSB configuration (e.g., LTM SSB configuration 1), similar to event 312. In response, S-DU 174A can send a second DU-CU message to CU 172, which includes one or more CSI report configurations (e.g., CSI report configuration 1). In some implementations, CU 172 can generate an LTM candidate configuration (e.g., LTM candidate configuration 1) that includes LTM DU configurations and assign an LTM ID (e.g., LTM ID 1) to identify the LTM DU configuration and / or LTM candidate configuration, as described above regarding... Figure 3 As described above. In some implementations, CU 172 includes the tuple {LTM ID 1, Cell ID 1} in the second CU to DU message.
[0153] To prepare cell 1 as an LTM candidate cell for UE 102, CU 172 can receive early synchronization information for cell 1 from C-DU 174B in a DU-CU message (e.g., a first DU-CU message or an additional DU-CU message). In some implementations, C-DU 174B can send an additional DU-CU message in response to receiving an additional DU-CU message from CU 172. In other implementations, C-DU 174B can send an additional DU-CU message in response to receiving a first CU-DU message (e.g., ...). UE context modification requirements (Message). Early synchronization information may include RACH configuration (e.g., RACH configuration 1) and / or at least one TCI state configuration (e.g., TCI state configuration 1), as described above regarding... Figure 3 As described above. In some implementations, the C-DU 174B includes the PDCCH command information (identified herein as PDCCH command information 1) used for early UL synchronization with cell 1 in the early synchronization information or in the DU to CU message.
[0154] In some implementations, CU 172 may receive LTM SSB configuration or SSB configuration parameters in the LTM SSB configuration from C-DU 174B, for example, in a first DU-CU message or an additional DU-CU message. In some implementations, CU 172 may receive the PCI of cell 1 from C-DU 174B in a first DU-CU message or an additional DU-CU message. In some implementations, C-DU 174B may send an additional DU-CU message in response to receiving an additional CU-CU message from CU 172. In other implementations, C-DU 174B may send an additional DU-CU message in response to receiving a first CU-CU message (e.g., UE context modification requirements information).
[0155] In some implementations, C-DU 174B includes a first set of LTM CFRA configuration parameters in the first DU-to-CU message of LTM preparation 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 or SUL indicator. In such cases, CU 172 may include the first set of LTM CFRA configuration parameters in a second CU-to-DU message of LTM ID configuration 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 LTM preparation process 490. Each additional set of LTM CFRA configuration parameters may include an RA preamble index, an SSB index, a PRACH mask index, and / or a UL or SUL indicator. In such cases, CU 172 includes the additional set of LTM CFRA configuration parameters in the second CU-to-DU message of LTM ID configuration process 492. In some implementations, the C-DU174B configures a first set and / or an additional set for UE 102. In some implementations, the first set and / or the additional set are specifically configured for cell 1. In other implementations, the C-DU 174B can configure the first set and / or the additional set for any LTM candidate cell of UE 102.
[0156] In some implementations, the first set and supplementary sets do not include individual UL or SUL indicators. In some implementations, the C-DU 174B can configure the first set and / or supplementary sets for one UL (e.g., NUL) or SUL, and can include a single UL or SUL indicator in the first DU to CU message indicating that the first set and / or supplementary sets are configured for one of the indicated UL and SUL. In such cases, the CU172 can include a single UL or SUL indicator in a second CU to DU message indicating that the first set and / or supplementary sets are configured for one of the UL or SUL. In other implementations, if the C-DU 174B configures the first set and / or supplementary sets for a UL, the C-DU 174B can include the first set and / or supplementary sets in a first field or IE of the first DU to CU message. If C-DU 174B configures a first set and / or an additional set for SUL, C-DU 174B may include the first set and / or the additional set in a second field or IE of the first DU to CU message. In this case, the first field or IE and the second field or IE are defined for UL and SUL, respectively. In some implementations, if the first DU to CU message includes the first set and / or the additional set in a first field or IE, CU 172 may include the first set and / or the additional set in a first field or IE of the second CU to DU message. If the first DU to CU message includes the first set and / or the additional set in a second field or IE, CU 172 may include the first set and / or the additional set in a second field or IE of the second CU to DU message. In this case, the first field or IE and the second field or IE are defined for UL and SUL, respectively.
[0157] In some implementations, C-DU 174B configures the first set for one of UL and SUL, and the additional set for the other. In some implementations, C-DU 174B sets the first UL or SUL indicator to a value indicating one of UL and SUL, and sets the UL or SUL indicator in the additional set to a value indicating the other. In other implementations, if C-DU 174B configures the first set for one of UL and SUL and the additional set for the other, then C-DU 174B may include the first set and the additional set in one and the other of the first field or IE and the second field IE in the first DU to CU message, respectively. In such cases, CU 172 may include the first set and the additional set in one and the other of the first field or IE and the second field IE in the second CU to DU message, respectively.
[0158] As mentioned above Figure 3 As described above, CU 172 can perform an LTM configuration delivery procedure 494 with UE 102 to send the LTM ID and LTM candidate configuration to UE 102. In some implementations, CU 172 can send {LTM ID, LTM candidate configuration} as a tuple in the first RRC reconfiguration message during the LTM configuration delivery procedure 494. Depending on the implementation, CU 172 can include the LTM reference configuration, CSI report configuration, CSI resource configuration, RACH configuration, TCI state configuration, LTMSSB configuration, and / or the PCI of cell 1 to UE 102 in the first RRC reconfiguration message and / or other RRC reconfiguration messages sent to UE 102, as described above. Figure 3 The CU 172 may include the LTM ID in the first RRC reconfiguration message 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 is associated with cell 1. For example, the CU 172 may include 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, the CU 172 may include {LTM ID, CSI resource configuration, RACH configuration, TCI state configuration, LTM SSB configuration, and / or the PCI of cell 1} as a tuple (e.g., tuple 1) in other RRC reconfiguration messages. In response to each RRC reconfiguration message in the other RRC reconfiguration messages, the UE 102 may send an RRC reconfiguration complete message to the CU 172 via S-DU 174A.
[0159] In some implementations, the PDCCH command information includes frequency domain resource assignment, 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) including the PDCCH command information to S-DU 174A. In some implementations, CU 172 can include 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, CU 172 can include {cell ID 1, PDCCH command information} as a tuple in the CU-DU message. In the case of an additional CU-DU message, S-DU 174A can send an additional DU-CU message to CU 172 in response.
[0160] At event 424, UE 102 may send at least one first measurement report, including a first measurement result, to S-DU 174A. The at least one first measurement report and the first measurement result may be at least one first L1 measurement report and a first L1 measurement result, respectively.
[0161] At event 450, S-DU 174A can send a PDCCH command to UE 102 based on PDCCH command information. For example, S-DU 174A can send a PDCCH command to UE 102 that includes PDCCH command information. In some implementations, S-DU 174A can determine the SSB index to be included in the PDCCH command based on the L1 measurement report of event 424, and / or CSI resource configuration, CSI report configuration, and / or LTM SSB configuration. In some implementations, S-DU 174A can include LTM ID 1 in the PDCCH command to indicate cell 1. In the case of an appended CU to DU message, S-DU 174A can send an appended DU to CU message to CU 172 in response.
[0162] At event 452, UE 102 can send an RA preamble to C-DU174B on cell 1 using RACH configuration and / or PDCCH command information. C-DU 174B can then derive the TA value based on the RA preamble.
[0163] At event 456, C-DU 174B can send a DU-CU TA information transmission message to CU 172, including the TA value.
[0164] At event 458, CU 172 can then send a CU-DU TA information transmission message including the TA value to S-DU 174A. In some implementations, C-DU 174B may include cell ID 1, RA preamble index, RA radio network temporary identifier (RA-RNTI), and / or the DU ID of S-DU 174A in the CU-DU TA information transmission message. In such cases, CU 172 may include cell ID 1, RA preamble index, RA-RNTI, and / or the DU ID of S-DU 174A in the message.
[0165] At event 454, UE 102 may send an additional measurement report to DU 174, similar to event 424. In some respects, the additional measurement report may be an L1 measurement report. DU 174 determines, based on the additional measurement report and / or the measurement report obtained at event 424, to instruct UE 102 to perform an LTM cell handover to the first cell.
[0166] At event 426, in response to the confirmation command UE 102 to perform an LTM cell handover to cell 1, S-DU 174A may send an LTM cell handover command including LTM ID 1 to UE 102. If S-DU 174A receives a TA value as described above, S-DU 174A may include that TA value in the LTM cell handover command. S-DU 174A may include a first TCI state ID in the LTM cell handover command. The first TCI state ID may indicate the first TCI state configuration in the TCI state configuration.
[0167] In some implementations, the C-DU 174B determines the RA-RNTI based on the PRACH timing, at which the C-DU 174B receives the RA preamble at event 452 discussed above. In some implementations, the C-DU 174B calculates the RA-RNTI as follows:
[0168] Where s_id is the index of the first orthogonal frequency division multiplexing (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 the subcarrier spacing used to determine t_id is based on the value of μ (e.g., as described in Clause 5.3.2 of 3GPP TS38.211) for μ = {0,1, 2, 3} and for μ = {5, 6}, t_id is the index of the 120 kHz slot in the system frame containing 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 represents NUL carrier and 1 represents SUL carrier).
[0169] At event 428, in response to the determination command UE 102 to perform LTM cell handover or send an LTM cell handover command, S-DU 174A can send to CU 172 DU-CU cell handover notification The message indicates that UE 102 can perform an LTM cell handover to cell 1.
[0170] At event 430, in response, CU 172 can send to C-DU 174B. CU-DU Cell Handover Notification The message instructs UE 102 to perform an LTM cell handover to cell 1.
[0171] At event 432, UE 102 can access cell 1 in response to an 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 to configure UE 102 to perform the CFRA procedure to access cell 1, as described above. Figure 3 As described above, UE 102 can use LTMCFRA configuration parameters and at least one RACH configuration to perform the CFRA procedure to access cell 1, as mentioned above. Figure 3 As described above, the C-DU 174B can perform the CFRA procedure with UE 102 according to the LTM CFRA configuration parameters and RACH configuration, as mentioned above. Figure 3 As stated above.
[0172] In some implementations, the S-DU 174A may determine, 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 may obtain (e.g., retrieve, derive, calculate, or determine) 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 C-DU 174B may transmit the first SSB 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 may include the first set of LTM CFRA configuration parameters in the LTM cell handover command. 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.
[0173] In some implementations, where the first set includes a first UL or SUL indicator, the S-DU174A can include the first UL or SUL indicator in the LTM cell handover command, as mentioned above. Figure 3 As described above. In other implementations, where the first set does not include UL or SUL indicators, the S-DU 174A can determine the value of the UL or SUL indicator and can include the UL or SUL indicator in the LTM cell handover command, as described below and / or above regarding... Figure 3In some implementations, if the second CU-to-DU message includes a first set of LTM CFRA configuration parameters in the first field for UL or the IE, then the S-DU 174A sets the UL or SUL indicator to a first value representing UL. If the second CU-to-DU message includes a first set of LTM CFRA configuration parameters in the second field for UL or the IE, then the S-DU 174A sets the UL or SUL indicator to a second value representing SUL. In other implementations, the S-DU 174A determines the value of the UL or 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 or SUL indicator to a first value, and the first set may be included in the LTM cell handover command. If the measurement result is below (or equal to) a predetermined threshold, the S-DU 174A sets the UL or SUL indicator to a second value and may include an additional set instead of the first set in the LTM cell handover command. In other implementations, the S-DU 174A sets the UL or SUL indicator to a pre-configured value (e.g., the first value), for example, because the C-DU 174B does not support SUL. In yet another implementation, the S-DU 174A sets the UL or SUL indicator to a pre-configured value (e.g., the second value), for example, because the S-DU 174A is pre-configured to do so.
[0174] In some implementations, the S-DU 174A can include the first TCI status ID. DU-CU cell handover notification The message, and CU 172 can then include the first TCI status ID. CU-DU Cell Handover Notification In the message, UE 102 and C-DU 174B 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 in events 432, 436 and / or 440 to transmit UL transmissions and / or DL transmissions.
[0175] In other implementations where the S-DU 174A uses separate TCI states, the DL TCI state and the UL TCI state can have different TCI state IDs. In such cases, the S-DU 174A can include the first TCI state ID of the DL and the second TCI state ID of the UL. DU-CU cell handover notification In messages and / or LTM cell handover commands, these TCI state IDs identify the first and second TCI state configurations in the TCI state configuration. In response to... DU-CU Community Switch notificationThe message, CU 172 can then include the first TCI status ID and the second TCI status ID in the message sent to C-DU174B. 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. UE 102 can apply the first TCI state configuration and the second TCI state configuration in events 432, 436, and / or 440 to transmit DL and UL transmissions with C-DU 174B, 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 can apply the first TCI state configuration and the second TCI state configuration in events 432, 436, and / or 440 to transmit DL and UL transmissions with UE 102, respectively.
[0176] In some implementations, each TCI state configuration in the TCI state configuration may include or be 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 may include 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, CU 172 may include {Cell ID 1, TCI state configuration} as a tuple in the CU-DU message. In the case of an additional CU-DU message, S-DU 174A may send an additional DU-CU message to CU 172 in response. In some implementations, S-DU 174A may include a first TCI state ID indicating a first TCI state configuration in the TCI state configuration in the LTM cell handover command of event 426. In some implementations, S-DU 174A determines the first TCI state configuration or the first TCI state ID. UE 102 identifies a TCI state configuration based on the first TCI state ID, and can apply the first TCI state configuration to UL transmission and / or DL reception in events 432, 436, and / or 440.
[0177] In some implementations, before or after sending the LTM cell handover command, or during or after the LTM preparation process 490 or the LTM ID configuration process 492, the CU 172 may prepare additional cells (i.e., cells 2 to N) as LTM candidate cells for the UE 102 in conjunction with the C-DU 174B.
[0178] In some implementations, the first CU to DU message and the first DU to CU message can be respectively UE Context Establishment ask Messages and UE Context Establishment Response Messages. In some implementations, the first CU to DU message and the first DU to CU message can be respectively UE Context Modification Request Messages and UE context modification response In some implementations, LTM preparation procedure 490 can be a UE context establishment procedure, and the additional LTM preparation procedure can be a UE context modification procedure. In other implementations, LTM preparation procedure 490 and the additional LTM preparation procedure can be UE context establishment procedures. In yet another implementation, LTM preparation procedure 490 and the additional LTM preparation procedure are UE context modification procedures.
[0179] At event 442, after receiving an access success message at event 434, or after receiving a DU to CU message at event 438, in some implementations, CU 172 may send a CU to DU message to DU 174A. In one implementation, CU 172 may send a CU to DU message to release the radio resources and / or configurations configured for UE 102 in the serving cell. In another implementation, CU 172 may send a CU to DU message to release some LTM candidate cells from LTM candidate cells 2 to N, or some LTM candidate cells prepared for UE 102 by DU 174A.
[0180] At event 444, in response to the CU to DU message, DU 174A can send a DU to CU message to CU 172. In some implementations, the CU to DU message at event 442 and the DU to CU message at event 444 are respectively... UE Context Modification Request Messages and UE context modification response information.
[0181] Events 404, 406, and 424, along with processes 490, 492, and 494, are in Figure 4 This is collectively referred to as the CU-DU inter-LTM configuration process 496. Events 404, 406, 424, 450, 452, 454, 456, 458, 426, 428, 430, 432, 434, 436, 438, 440, 442, and 444, along with processes 490, 492, and 494, are in... Figure 4 This is collectively referred to as the CU-internal DU-internal LTM process 480.
[0182] Figure 5This is a sequence diagram illustrating example operations for a communication process 500 for example inter-CU cell handover, where a first base station operates as a serving base station or source base station (S-BS), and a second base station operates as a candidate base station (C-BS). Figure 5 In the example shown, S-BS 501 can be Figure 1A Base station 104 Figure 1B Base station 104A or 104B, Figure 1C Base station 164, or Figure 2A The implementation methods of eNB, ng-eNB 230 or gNB 232. Figure 5 C-BS 506 can be Figure 1A Base station 106 Figure 1B Base station 106A or 106B, Figure 1C Base station 164, or Figure 2A The implementation methods of eNB, ng-eNB 230 or gNB 232.
[0183] In some implementations, C-BS 506 may include CU 172 and DU 174. Communication process 500 is similar to communication processes 300 and 400, except that communication process 500 is an inter-CU communication process (i.e., inter-base station communication process), while communication processes 300 and 400 are intra-CU communication processes (i.e., intra-base station communication processes). S-BS 501 may include CU and DU (…). Figure 5 (not shown in the image), similar to Figure 3 Base station 301 and Figure 4 Base station 401.
[0184] At event 502, UE 102 communicates with S-BS 501 via the serving cell using the service configuration. In some implementations, S-BS 501 may include S-DU and CU, and the service configuration may include serving CU configuration and serving DU configuration, as described above. Figure 3 and Figure 4 As described above, UE 102 can use at least one first security key and at least one first security algorithm to perform security protection on data transmitted with S-BS 501, as described above. Figure 3 and Figure 4 As described above. Similarly, S-BS 501 can use at least one first security key and at least one first security algorithm to perform security protection on data transmitted with UE 102, as described above. Figure 3 and Figure 4 Depending on the implementation, the first security key and the first security algorithm used by UE 102 and S-BS 501 may be the same or different.
[0185] In some respects, when communicating with UE 102 at event 502, S-BS 501 can execute the CU-internal LTM procedure 580 with UE 102, respectively similar to Figure 3 and Figure 4 The processes 380 and / or 480. In some other methods, when communicating with UE102 at event 502, S-BS 501 can perform the CU-in-CU LTM configuration process 596 with UE102, respectively similar to... Figure 3 and Figure 4 The process is 396 and / or 496.
[0186] At event 504, while communicating with S-BS 501, UE 102 may send at least one measurement report to S-BS 501. The measurement report may include UE 102's serving cell and / or at least one non-serving cell (e.g., cell 126 in Figure 1 and...). Figure 1B The measurement results of cell 126A are used by S-BS 501 to determine whether to prepare the first cell (e.g., cell 126A) as an LTM candidate cell for UE 102. For example, the measurement report may include the PCI of the first cell and the measurement results of cell 126A. S-BS 501 identifies the first cell as operated by C-BS 506 based on the PCI and can determine whether the first cell is eligible for LTM preparation based on the measurement results.
[0187] After determining that the first cell is to be prepared as the LTM candidate cell for UE 102 (e.g., in response to this), S-BS 501 (e.g., the CU of S-BS 501) can generate Switching requests The handover request message includes the first cell ID (i.e., cell ID 1) of the first cell (i.e., cell 1).
[0188] At event 505, S-BS 501 can send to CU 172. Switching requests Message. In some implementations, cut Change request The message may include an LTM indicator, which indicates Switching requests The message relates to LTM for the first cell ID. Upon receiving... Switching requests Following the message (e.g., in response to this), CU 172 can perform LTM preparation procedure 590 with DU 174 to prepare the first cell as an LTM candidate cell for UE 102, similar to the procedures discussed above. Figure 3 and Figure 4The LTM preparation process is either 390 or 490. In process 590, CU 172 can send a first CU-DU message including the first cell ID to DU 174 to request DU to prepare the first cell, similar to the discussion above. Figure 3 Event 308. In response, CU 172 can receive a first DU-to-CU message from DU 174, including LTM DU configuration 1, similar to... Figure 3 Event 310. CU 172 can generate the first LTM candidate configuration (LTM candidate configuration 1).
[0189] At event 507, the response was... Switching requests The message indicates that CU 172 can send a message to S-BS 501 including the first LTM candidate configuration. Switch request confirmation Message. In some implementations, the CU 172 can include the first cell ID. Please switch Please confirm. The message indicates that the first LTM candidate configuration is provided for or associated with the first cell (ID).
[0190] Events 505 and 507, along with LTM preparation process 590, are in Figure 5 This is collectively referred to as the CU-interval LTM preparation process 598 (also known as the MN-interval LTM preparation process).
[0191] In some implementations, Switching requests The message may include the DU ID of the S-DU of S-BS 501. In such cases, CU 172 may include the DU ID in the first CU to DU message. In some implementations, Switching requests The message may include the BS ID of S-BS 501. When the BS ID is received, CU 172 may include the BS ID in the first CU to DU message. For example, the BS ID may be the gNB ID.
[0192] CU 172 may or may not request the LTM reference DU configuration during LTM preparation process 590, as described above regarding... Figure 3 and Figure 4 The procedures described in 390 and 490 are as follows. DU 174 may or may not send the LTM reference DU configuration to CU 172 during LTM preparation procedure 590, as described above regarding... Figure 3 and Figure 4 The processes described in 390 and 490 are as follows. In some implementations, the S-BS501 (e.g., the CU of the S-BS501) can obtain an LTM reference configuration, as described above regarding... Figure 3 and Figure 4As described above. In other implementations, S-BS 501 can be used from another BS (...) during the LTM preparation process between another CU. Figure 5 (Not shown in the original text) Receives the LTM reference configuration, as described above and below. If S-BS 501 obtains the LTM reference configuration, S-BS 501 may include that LTM reference configuration (e.g., the LTM reference configuration generated by S-BS) in... Switching requests In some implementations, S-BS 501 can include the LTM reference configuration in the inter-node RRC message. HandoverPreparationInformation It can be included in the Xn Application Protocol (XnAP) IE or field, and can include inter-node RRC messages or XnAP IEs. Switching requests In the message. Alternatively or additionally, S-BS 501 determines that the request or C-BS 506 provides a complete LTM candidate configuration, such that S-BS 501 does not include the LTM reference configuration. Switching requests The message states that if the S-BS 501 does not obtain the LTM reference configuration, then the S-BS 501 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, CU172 can include that LTM reference configuration in the first CU-DU message. DU 174 can extract an LTM reference DU configuration from the LTM reference configuration. Alternatively or additionally, CU 172 can extract the LTM reference DU configuration from the LTM reference configuration and include it 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, as described above. Figure 3 Alternatively or additionally, DU 174 may ignore the LTM reference (DU) configuration and generate an LTM DU configuration as the complete configuration, as described above. Figure 3 As stated above.
[0193] if Switching requests If the message does not include the LTM reference configuration, then CU 172 may or may not receive the LTM reference DU configuration from DU 174, as mentioned above. Figure 3 As described above. If CU 172 (e.g., in the first DU to CU message) receives an LTM reference DU configuration, CU 172 can generate an LTM reference configuration that includes the 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)). If CU 172 does not receive an LTM reference DU configuration from DU 174, as described above... Figure 3In this case, CU 172 does not generate an LTM reference configuration. Alternatively or additionally, CU 172 may generate an LTM reference configuration that only includes the LTM reference CU configuration generated by the C-CU (e.g., the LTM reference configuration generated by the C-BS). In the case where CU 172 generates an LTM reference configuration (e.g., the LTM reference configuration generated by the C-BS), CU 172 may include the LTM reference configuration generated by the C-BS. Switch request confirmation In the message.
[0194] In some implementations, if LTM DU configuration 1 is a complete configuration, then CU 172 can generate LTM candidate configuration 1 as the complete configuration. CU 172 can include the complete configuration indication (e.g., BS-to-BS interface protocol field or IE) in... cut Change request confirmation 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 (e.g., as defined in 3GPP TS 38.423). In some implementations, the complete configuration indication is a new field or IE (e.g., LTM-specific) to avoid impacting non-LTM configurations. In other implementations, the complete configuration indication is an existing field or IE (e.g., as defined in 3GPP TS 38.423). If LTM DU configuration 1 is an incremental configuration, CU 172 can generate 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 or additionally, CU 172 may include the incremental configuration indication (e.g., BS-to-BS interface protocol field or 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 an Xn application protocol (e.g., as defined in 3GPP TS 38.423). In some implementations, the incremental configuration indication is a new field or IE (e.g., LTM-specific) to avoid impacting non-LTM configurations. In other implementations, the incremental configuration indication is an existing field or IE defined in 3GPP specification 38.423. In some implementations, the BS-to-BS interface protocol field or IE can have two values (i.e., a first value and a second value). The BS-to-BS interface protocol field or IE set to the first value can be a full configuration indication, and the BS-to-BS interface protocol field or IE set to the second value can be an incremental configuration indication.
[0195] In some implementations, the S-BS 501 may be 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 other implementations, the S-BS 501 may receive the CSI resource configuration and / or LTM SSB configuration from an Operations, Administration and Maintenance (OAM) node. In yet another implementation, the S-BS 501 may receive the CSI resource configuration and / or LTM SSB configuration from the CU 172. For example, the CU 172 may include the CSI resource configuration and / or LTM SSB configuration in... Switch request confirmation In the message, in some implementations, CU 172 can include the PCI of the first cell (identified as PCI 1 in this document) in... Switch request confirmation In the message, to prepare the first cell as a candidate LTM cell for UE 102, the CU of S-BS 501 can perform the LTMCSI report configuration and / or LTM ID configuration procedures with the S-DU of S-BS 501. Figure 5 (not shown in the image), similar to Figure 3 Procedure 392. During the LTM CSI report configuration and / or LTM ID configuration process, the CU of S-BS 501 may send CSI resource configuration and / or LTM SSB configuration to the S-DU of S-BS 501. In response, the CU of S-BS 501 may receive one or more CSI report configurations for UE 102 from the S-DU of S-BS 501. In some implementations, the CU of S-BS 501 may receive the CSI report configuration from the second service DU configuration from the S-DU.
[0196] To prepare the first cell as an LTM candidate cell for UE 102, CU 172 can receive early synchronization information (referred to herein as early synchronization information 1) for 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 can send an additional DU-CU message in response to receiving an additional CU-DU message from CU 172. In other implementations, DU 174 can send an additional DU-CU message in response to receiving a first CU-DU message (e.g., ...). UE context modification requirements (Message). CU 172 can include early synchronization information. Switch request confirmationThe early synchronization information may include RACH configuration (identified herein as RACH configuration 1) and / or at least one TCI state configuration (identified herein as TCI state configuration 1). In some implementations, DU 174 may include PDCCH command information in the early synchronization information or in the DU-to-CU message for early UL synchronization with the first cell. CU 172 may include PDCCH command information in... Switch request confirmation In the message.
[0197] In some implementations, CU 172 may assign an LTM ID (e.g., LTM ID 1) to identify the first LTM candidate configuration, and the LTM ID may be included in... Switch request confirmation In other implementations, S-BS501 assigns an LTM ID (e.g., LTM ID 1) to identify the first LTM candidate configuration.
[0198] At event 518, upon receiving... Switch request confirmation Following the message (e.g., in response to this), S-BS 501 (e.g., the CU of S-BS 501) may send a first RRC reconfiguration message to UE 102, which includes {LTMID 1, LTM candidate configuration 1} as a tuple (e.g., tuple 1), similar to Figure 3 Event 318. If Switch request confirmation If the message includes the LTM reference configuration, then S-BS 501 can include the LTM reference configuration in the first RRC reconfiguration message. For example, if in Switch request confirmation If the message receives CSI Resource Configuration 1, TCI State Configuration 1, RACH Configuration 1, LTM SSB Configuration 1, and / or the PCI of the first cell, the S-BS 501 may include them in a tuple. Alternatively or additionally, the S-BS 501 may send one or more additional RRC reconfiguration messages to the UE 102, which include CSI Resource Configuration 1, TCI State Configuration 1, RACH Configuration 1, LTM SSB Configuration 1, and / or the PCI of the first cell. The S-BS 501 may include LTM ID 1 in each additional RRC reconfiguration message 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.
[0199] At event 520, UE 102 may send a first RRC reconfiguration complete message to S-BS 501 in response to the first RRC reconfiguration message. UE 102 may send additional RRC reconfiguration complete messages to S-BS 501 in response to each additional RRC reconfiguration complete message in the additional RRC reconfiguration complete messages. 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 procedure. S-BS 501 may include the second service DU configuration in one of the additional RRC reconfiguration messages in either the first RRC reconfiguration message or the additional RRC reconfiguration message.
[0200] In some implementations, the S-BS 501 (e.g., the CU of the S-BS 501) may include the first security information. Switching requests In the message. In some implementations, the first security information may include a RAN-level security key (e.g., key-NG-RAN-Star) and / or a next-hop link count. In some implementations, S-BS 501 may include the security capabilities of UE 102 in... Switching requests In the message.
[0201] In some implementations, CU 172 can generate a first security configuration for UE 102 based on first security information. In one implementation, CU 172 can include the first security configuration in... Switch request confirmation In another implementation, CU 172 may include the first security configuration in the first LTM candidate configuration or LTM reference configuration.
[0202] In other implementations, S-BS 501 (e.g., the CU of S-BS 501) instead of CU 172 may generate 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) for UE 102. Switch request confirmation In the message, the first LTM candidate configuration and / or the LTM reference configuration.
[0203] In some implementations, S-BS 501 may include the first security configuration in a container IE that may include tuple 1 (e.g., LTM-Config In the first RRC reconfiguration message, the container IE can be included in the first security configuration (IE). In other implementations, S-BS 501 can include the first security configuration in tuple 1.
[0204] In some implementations, the first security configuration may include at least a portion of the first security information. For example, the first security configuration includes a next-hop link 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-BS 501 (e.g., the CU of S-BS 501) or CU 172 may determine the second security algorithm based on security capabilities. In some implementations, the second security algorithm may include encryption algorithms and / or integrity algorithms that may be the same as or different from the first security algorithm.
[0205] In some implementations, the first security configuration may include a key set change indicator (e.g., keySetChangeIndicator The key set change indicator indicates whether a new CN key (e.g., a new K key) is required. AMF The new BS key (e.g., the new K) is derived from the next hop (NH) parameter or the next hop (NH) parameter. gNB In some implementations, the S-BS 501 (e.g., the CU of the S-BS 501) or CU 172 sets the key set change indicator to a first value indicating that the first new key is derived from the NH parameters. In other implementations, the S-BS 501 or CU 172 may be pre-configured to set the key set change indicator to a first value indicating that the first new key is derived from the NH parameters. This is because inter-CU LTM may not support deriving a new BS key based on a new CN key.
[0206] In some implementations, if Switch request confirmation If the message includes a complete configuration indication to indicate that LTM candidate configuration 1 is a complete configuration, then S-BS 501 may include the complete configuration indication (e.g., an RRC field or IE) in the first RRC reconfiguration message to indicate that LTM candidate configuration 1 is a complete configuration. If Switch request confirmation If the message does not include a complete configuration indication or includes an incremental configuration indication to indicate that LTM candidate configuration 1 is an incremental configuration, then S-BS 501 excludes or does not include a complete configuration indication (e.g., an RRC field or IE) in the first RRC reconfiguration message to indicate that LTM candidate configuration 1 is an incremental configuration.
[0207] At event 524, UE 102 may send at least one first measurement report, including a first measurement result, to S-BS 501. The at least one first measurement report and the first measurement result may be at least one first L1 measurement report and a first L1 measurement result, respectively.
[0208] At event 550, if Switch request confirmationIf the message includes PDCCH command information (e.g., PDCCH command information 1), then S-BS 501 can send a PDCCH command based on the PDCCH command information. If S-BS 501 is a distributed base station, then the CU of S-BS 501 can send the PDCCH command information to the S-DU of S-BS 501. For example, S-BS 501 or its S-DU can send a PDCCH command including the PDCCH command information to UE 102. In some implementations, S-BS 501 or its S-DU can determine the SSB index to be included in the PDCCH command based on the L1 measurement report of event 524, CSI resource configuration, CSI report configuration, and / or LTM SSB configuration. In some implementations, S-DU or S-BS 501 can include LTMID 1 in the PDCCH command to indicate the first cell.
[0209] At event 552, UE 102 can send an RA preamble to DU174 on the first cell using RACH configuration and / or PDCCH command information. DU 174 can then derive the TA value based on the RA preamble.
[0210] At event 556, DU 174 can send a message including the TA value to CU 172. DU-CU TA Information Transmission information.
[0211] At event 558, CU 172 may send a CU-CU TA information transmission message including the TA value to S-BS 501 (e.g., the CU of S-BS 501). In some implementations, DU 174 may include the cell ID 1, RA preamble index, RA-RNTI, DU ID of S-DU of S-BS 501, and / or BS ID of S-BS 501 in the message. In some implementations, DU 174 does not include the BS ID in event 556. DU-CU TA Information Transmission In some implementations, CU 172 may include Cell ID 1, RA preamble index, RA-RNTI, S-DU ID, and / or S-BS 501 BS ID in the message of Event 558. In some implementations, CU 172 may not include the BS ID in the message of Event 558. The CU of S-BS 501 may send to the S-DU of S-BS 501. CU-DU TA Information Transmission The message includes the TA value, cell ID 1, RA preamble index, RA-RNTI and / or the DU ID of the S-DU and / or the BS ID of the S-BS 501. In some implementations, the CU of the S-BS 501 does not include the BSID. CU-DU TA Information Transmission In the message.
[0212] In some implementations, CU 172 determines the address (e.g., IP address) of S-BS 501 or its CU based on the BS ID of S-BS 501. In other implementations, CU 172 determines the address (e.g., IP address) of S-BS 501 or its CU based on the DU ID of S-DU of S-BS 501. In such implementations, CU 172 sends data to S-BS 501 or its CU based on this address. CU-CU TA Information Transmission information.
[0213] At event 554, UE 102 may send an additional measurement report to S-BS 501 (or the CU of S-BS 501), similar to event 524. In some respects, the additional measurement report may be an L1 measurement report. S-BS 501 determines the command for UE 102 to perform an LTM cell handover to the first cell based on the additional measurement report and / or the measurement report of event 524.
[0214] At event 526, in response to, for example, a measurement report determination command based on events 524 and / or 554, in which UE 102 performs an LTM cell handover to a first cell, the S-DU of S-BS 501 can send an LTM cell handover command including LTM ID 1 to UE 102. In response to the LTM cell handover command, UE 102 can cease communication on the serving cell.
[0215] At event 527, in response to a confirmation command UE 102 performing an LTM cell handover or in response to sending an LTM cell handover command, S-BS 501 can send to CU 172 CU-CU cell handover notification The message instructs UE 102 to perform an LTM cell handover to cell 1.
[0216] At event 530, in response, CU 172 can send to C-DU 174B. CU-DU Cell Handover Notification The message instructs UE 102 to perform an LTM cell handover to cell 1.
[0217] At event 532, in response to the LTM cell handover command, UE 102 can access the first cell.
[0218] At event 536, UE 102 may send an RRC reconfiguration complete message to DU 174 when or after accessing the first cell.
[0219] At event 538, DU 174 can then send a DU-CU message to CU 172 including an RRC reconfiguration completion message. In some implementations, UE 102 can derive at least one second security key based on the first security configuration. In some implementations, UE 102 can derive a new BS key (e.g., a new K key) based on the first security configuration. gNB Furthermore, the second security key can be derived from the new BS key. In some implementations, if UE 102 receives the second security algorithm for the first cell (i.e., the LTM candidate cell) as described above, UE 102 can derive the second security key based on the new BS key and the second security algorithm. If UE 102 does not receive the second security algorithm for the first cell, UE 102 can derive the second security key based on the new BS key and the first security algorithm.
[0220] In some implementations, UE 102 may derive a second security key in response to receiving an LTM cell handover command at event 526. In other implementations, UE 102 may derive the second security key after receiving the first security configuration and before receiving the LTM cell handover command. UE 102 may apply the second security key to communicate with CU 172 at events 536 and 540. If UE 102 receives the second security algorithm as described above, UE 102 may apply both the second security key and the second security algorithm to communicate with CU 172 at events 536 and 540. If UE 102 does not receive the second security algorithm, UE 102 may apply both the second security key and the first security algorithm to communicate with CU 172 at 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., data packets at event 536 and / or RRC messages at event 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 yet another implementation, the security key includes an integrity key for integrity protection of user plane data packets (e.g., data packets transmitted via the DRB) in event 540. In still another implementation, the security key includes an encryption key for encrypting / decrypting user plane data packets (e.g., data packets transmitted via the DRB) in event 540. In some aspects, when UE 102 begins communicating with CU 172 using the second security key, UE 102 ceases communicating with CU 172 using the first security key.
[0221] In some implementations, CU 172 can derive at least one second security key based on the first security information. In some implementations, CU 172 can derive a new BS key (e.g., a new K key) based on the first security information. gNB The CU 172 can derive at least one second security key from the new BS key. In some implementations, if the CU 172 sends the second security algorithm to the UE 102 as described above, the CU 172 can derive the second security key based on the new BS key and the second security algorithm. If the CU 172 does not send the second security algorithm to the UE 102, the CU 172 can derive the second security key based on the new BS key and the first security algorithm. The CU 172 can apply the second security key to communicate with the UE 102 in events 536 and 540. If the CU 172 sends the second security algorithm to the UE 102 as described above, the CU 172 can apply the second security key and the second security algorithm to communicate with the UE 102 in events 536 and 540. If the CU 172 does not send the second security algorithm to the UE 102, the CU 172 can apply the second security key and the first security algorithm to communicate with the UE 102 in events 536 and 540.
[0222] In some implementations, CU 172 may derive a second security key in response to receiving a CU-CU cell handover notification message at event 527, an access success message at event 534, or a DU-CU message at event 538. In other implementations, CU 172 may derive the second security key after generating or sending the first security configuration and before receiving the CU-CU cell handover notification message at event 527, the access success message at event 534, or the DU-CU message at event 538. CU 172 may apply the second security key in events 536 and 540 to communicate with UE 102. 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 or decrypting control plane data packets (e.g., data packets in event 536 and / or RRC messages in event 540). In yet another implementation, the second security key includes an integrity key for integrity protection of user plane data packets (e.g., transmitted via DRB) in event 540. In yet another implementation, the second security key includes an encryption key for encrypting or decrypting user plane data packets (e.g., data packets transmitted via DRB) in event 540. In some implementations, the second security key applied by CU 172 is the same as the second security key applied by UE 102.
[0223] At event 540, after receiving the DU to CU message or the RRC reconfiguration complete message at event 538, C-BS506 can communicate with UE 102 based on the first LTM candidate configuration and / or LTM reference configuration. In some implementations, UE 102 may include LTM ID 1 in the RRC reconfiguration complete message at event 536 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 LTM reference configuration. In other implementations, CU 172 is based on event 534. Connection successful The message includes a first cell ID 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 LTM reference configuration. When CU 172... Connection successful When 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, UE 102 may perform an RA procedure to access the first cell in event 532. 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 501 may include 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 may use the first set of LTM CFRA configuration parameters to perform the CFRA procedure. In some implementations, DU 174 may include the first set of LTM CFRA configuration parameters in the first DU to CU message of LTM preparation procedure 590.
[0225] As described in LTM preparation procedure 590, CU 172 can then include the first set of LTM CFRA configuration parameters in Switch request confirmation In some implementations, DU 174 may include at least one additional set of LTM CFRA configuration parameters in the first DU to CU message, as described above for LTM preparation procedure 590. CU 172 may then include the additional set of LTM CFRA configuration parameters in... Switch request confirmation In the message.
[0226] In some implementations, DU 174 configures a first set and / or additional sets for UL (e.g., NUL) or SUL, and such configurations can be indicated in the first DU to CU message, such as Figure 4As described in C-DU 174B, where DU174 is configured with a first set and / or an additional set for either UL or SUL, CU 172 can include a single UL or SUL indicator. Switch request confirmation In the message, the single UL or SUL indicator indicates that the first set and / or additional set are configured for either UL or SUL. Where DU 174 is configured for UL, CU 172 may include the first set and / or additional set in the configuration. Switch request confirmation The first field in the message or in the IE. Where DU 174 configures the first set and / or additional sets for SUL, CU 172 can include the first set and / or additional sets. Switch request confirmation The second field or IE in the message. In such cases, the first field or IE and the second field or IE are defined for UL and SUL, respectively.
[0227] In some implementations, DU 174 configures a first set for one of UL and SUL, and an additional set for the other of UL and SUL, and this configuration can be indicated in the first DU to CU message, such as... Figure 4 As described in C-DU 174B. In such cases, CU 172 sets the UL or SUL indicator in the first set to a value indicating either UL or SUL, and sets the UL or SUL indicator in the supplementary set to a value indicating the other of UL or SUL. Alternatively or additionally, CU 172 may include the first set and the supplementary set separately. Switch request confirmation The message contains either the first field or the second field, one of which is the other.
[0228] In some implementations, if the S-DU of S-BS 501 receives the TA value as described above, the S-DU of S-BS 501 may include the TA value in the LTM cell handover command. In some implementations, the S-DU of S-BS 501 may include the first TCI state ID in the LTM cell handover command. The first TCI state ID may indicate the first TCI state configuration in the TCI state configuration. If the LTM cell handover command includes the TA value, UE 102 may skip performing the RA procedure in event 532 to access the first cell. Otherwise, UE 102 may perform the RA procedure in event 532 to access the first cell, as described above.
[0229] In response to the confirm command UE 102 performing LTM cell handover or in response to sending (Event 526) LTM cell handover command, the S-DU of S-BS 501 can send to the CU of S-BS 501. DU-CU cell handover notification information( Figure 5 (not shown in the image) to indicate that UE 102 is performing or is performing an LTM cell handover to the first cell.
[0230] At event 527, the response was received. DU-CU cell handover notification The message indicates that the CU of S-BS 501 can send a message to CU172. CU-CU cell handover notification The message instructs UE 102 to perform an LTM cell handover to the first cell.
[0231] At event 530, in response, CU 172 can send 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 501 may include the first TCI state ID. CU-CU cell handover notification In the message, and then CU 172 can include the first TCI status ID. CU-DU Cell Handover Notification In the message, UE 102 and DU 174 can 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 in events 532, 536, and / or 540 to transmit UL and / or DL transmissions. 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-BS 501 can include the first TCI state ID of DL and the second TCI state ID of UL separately. DU-CU cell handover notification In messages and / or LTM cell handover commands, these TCI state IDs identify the first and second TCI state configurations of the TCI state configuration. In response to... DU-CU community switching Change notification The message states that the CU of S-BS 501 can then include the first TCI status ID and the second TCI status ID in CU 172. CU-CU cell handover notification In the message. Then, CU 172 can include the first TCI status ID and the second TCI status ID in the message to DU 174. CU-DU Cell Handover NotificationIn the message, UE 102 can identify 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 can apply the first TCI state configuration and the second TCI state configuration in events 532, 536, and / or 540 to transmit DL and UL transmissions with DU 174, respectively. DU 174 can identify 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 can apply the first TCI state configuration and / or the second TCI state configuration in events 532, 536, and / or 540 to transmit DL and / or UL transmissions with UE 102, respectively.
[0232] At event 531, in some implementations, the LTM cell handover is determined by the command UE 102 to perform the LTM cell handover, the LTM cell handover command is sent at event 526, or the command is received at event 527. DU-CU cell handover notification Following the message (e.g., in response to this), S-BS 501 (e.g., the CU of S-BS 501) may send one or more messages to CU 172. Early state transfer Each early state delivery message includes a DL COUNT value for the DRB or a DISCARD DL COUNT value, and UE 102 and S-BS 501 (e.g., in a communication that begins at event 502) transmit data to each other on that DRB.
[0233] At event 539, in some implementations, it is received at event 534. Connection successful After receiving a DU to CU message or an RRC reconfiguration complete message at event 538, CU 172 can send an LTM success message to S-BS 501 (e.g., the CU of S-BS 501) to indicate successful LTM cell handover. In some implementations, the LTM success message can be... Switching successful In some implementations, CU 172 may include 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 501 (e.g., the CU of S-BS 501) to indicate successful LTM cell handover.
[0234] At event 541, in some implementations, the LTM cell handover is determined by UE 102, the LTM cell handover command is sent at event 527, and the command is received at event 527. DU-CU cell handover notification After receiving an LTM success message at event 539 (e.g., in response to this), S-BS 501 (e.g., the CU of S-BS 501) may send a message to CU 172. SN status transmission The SN status transmission message includes the DL COUNT value and / or UL COUNT value for the DRB, and UE102 and S-BS 501 transmit data to each other on the DRB (e.g., communication that begins at event 502).
[0235] At event 543, in some implementations, it is received at event 534. Connection successful The message is received at event 538 as a DU to CU message or an RRC reconfiguration complete message, or at event 541. SN status transmission Following the message (e.g., in response to this), CU 172 can send to S-BS 501. UE context release Message. Response to UE context release The message indicates that S-BS 501 can release the UE context of UE 102.
[0236] In some implementations, before or after sending the LTM cell handover command, or during, before or after the inter-CU LTM preparation process 598, S-BS 501 (e.g., the CU of S-BS 501) may prepare additional cells (i.e., cells 2 to N) as LTM candidate cells for UE 102 with CU 172, as described above. Cells 2 to N are identified by cell IDs 2 to N respectively, and are operated by DU 174 and / or other DUs of C-BS 506. N is an integer greater than 1. For example, S-BS 501 may perform additional inter-CU LTM preparation processes 2 to N with CU 172 to prepare cells 2 to N respectively. Each inter-CU LTM preparation process 2 to N is similar to inter-CU LTM preparation process 598. In inter-CU LTM preparation processes 2 to N, S-BS 501 may receive LTM candidate configurations 2 to N respectively configured for LTM. As described above, S-BS 501 or C-BS 506 can assign LTM IDs 2 to N to identify LTM candidate configurations 2 to N respectively. S-BS 501 can obtain CSI resource configurations 2 to N for cells 2 to N respectively, as described for CSI resource configuration 1. S-BS 501 can obtain CSI reporting configurations 2 to N or CSI resource configurations 2 to N for cells 2 to N respectively, as described for CSI reporting configuration 1. S-BS 501 can obtain RACH configurations 2 to N for cells 2 to N respectively, as described for RACH configuration 1. S-BS 501 can obtain TCI status configurations 2 to N for cells 2 to N respectively, as described for TCI status configuration 1. S-BS 501 can obtain LTM SSB configurations 2 to N for cells 2 to N respectively, as described for LTM SSB configuration 1. S-BS 501 can obtain PCI 2 to N for cells 2 to N respectively, as described for PCI 1. In some implementations, S-BS 501 may perform LTM configuration delivery procedures 2 to N with UE 102 to send the following lists to UE 102 respectively: {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 LTM configuration delivery procedure in LTM configuration delivery procedures 2 to N is similar to procedures 394, 494 and / or LTM configuration delivery procedure 1 (i.e., events 518 and 520). In other implementations, S-BS 501 may include this list in the first RRC reconfiguration message.
[0237] To simplify the following description, tuples 1 through N are used to 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), LTMSSB configuration 1 (if obtained)}, …, {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)}. In some implementations, S-BS 501 may include tuples 1 through N in RRC reconfiguration messages 1 through N within LTM configuration delivery processes 1 through N. RRC reconfiguration message 1 is the first RRC reconfiguration message of event 518. In some implementations, S-BS 501 may include tuples 1 through N in containers IE 1 through N, and may include containers IE 1 through N in RRC reconfiguration messages 1 through N. In other implementations, CU 172 can include tuples 1 through N in container IE 1, and container IE1 can be included in the first RRC reconfiguration message. In some aspects, container IE can be LTM. -Config IE .
[0238] In other implementations, S-BS 501 can perform an inter-CU LTM preparation procedure 598 with CU 172 to prepare one or more cells from cell 1 to N as LTM candidate cells for UE 102. In this implementation, S-BS 501 can include cell IDs 1 to N in event 505. Switching requests The message, as described for cell ID 1, states that in some implementations, upon receiving... Switching requests Following the message, CU 172 determines or selects cells 1 through M from cells 1 through N as LTM candidate cells. M is a positive integer and M ≤ N. In other implementations, CU 172... Switching requestsCells 1 to N are prepared for LTM as requested in the message. CU 172 and DU 174 can perform LTM preparation procedures 2 to M to prepare cells 2 to M as LTM candidate cells for UE 102, respectively. LTM preparation procedures 2 to M are similar to LTM preparation procedure 590 performed by CU 172 and DU 174 to prepare cell 1. As a result of LTM preparation procedures 2 to M, CU 172 can obtain LTM candidate configurations 2 to M for cells 2 to M, similar to obtaining LTM candidate configuration 1. C-BS 506 can generate LTM candidate configurations 2 to M as a complete configuration, or generate incremental configurations based on the LTM reference configuration, as described for LTM candidate configuration 1. CU 172 can include LTM candidate configurations 2 to M in... Switch request confirmation In some implementations, CU 172 or S-BS 501 assigns LTM IDs 2 to M to identify LTM preparation processes 2 to M respectively, as described for LTM ID 1. When CU 172 assigns LTM IDs 1 to M, CU 172 can include LTM IDs 1 to M and LTM candidate configurations 1 to M respectively. Switching request confirmed recognize The message is as described for LTM ID 1 and LTM candidate configuration 1.
[0239] In some implementations, CU 172 can obtain early synchronization information 2 to M for cells 2 to M respectively, as described for early synchronization information 1. CU 172 can include the early synchronization information 2 to M in... Switch request confirmation In some implementations, CU 172 or S-BS 501 can obtain CSI resource configurations 2 to M for cells 2 to M respectively, as described for CSI resource configuration 1. When CU 172 can obtain CSI resource configurations 2 to M, CU 172 can include CSI resource configurations 2 to M in... Switch request confirmation In the message.
[0240] In some implementations, CU 172 or S-BS 501 can obtain LTM SSB configurations 2 to M for cells 2 to M respectively, as described for LTM SSB configuration 1. When CU 172 obtains LTM SSB configurations 2 to M, CU 172 can include LTM SSB configurations 2 to M in... Switch request confirmation The message states that in some implementations, CU 172 or S-BS 501 can obtain PCI 2 to M for cells 2 to M respectively, as described for PCI 1. When CU 172 obtains PCI 2 to M, CU 172 can include PCI 2 to M in... Switch request confirmation In the message.
[0241] In some implementations, CU 172 can include the following list of tuples. 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), LTMSSB configuration 1 (if obtained or optional), PCI 1 (if obtained or optional)}, ..., {Cell ID M, LTMID 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)}.
[0242] In some implementations, CU 172 can obtain PDCCH command information 2 to M for cells 2 to M respectively, as described for PDCCH command information 1. In one implementation, CU 172 can include PDCCH command information 2 to M in... cut Change request confirmation In another implementation, CU 172 can include PDCCH command messages 2 to M in the early synchronization messages 2 to M respectively. S-BS 501 can extract the information from the early synchronization messages 2 to M or from... Switch request confirmation The message contains RACH configuration 2, TCI status configuration 2 and / or PDCCH command information 2, ..., RACH configuration M, TCI status configuration M and / or PDCCH command information M.
[0243] In some implementations, S-BS 501 and UE 102 may each perform LTM configuration delivery procedures 2 to M to send tuples 2 to M to UE 102. In some implementations, S-BS 501 may include tuples 1 to M in containers IE 1 to M, and may include containers IE 1 to M in RRC reconfiguration messages 1 to M respectively. In other implementations, S-BS 501 may include tuples 1 to M in the first RRC reconfiguration message. In some implementations, S-BS 501 may include tuples 1 to M in container IE 1 (e.g., LTM-Config In the IE (Container IE), container IE 1 can be included in the first RRC reconfiguration message. In some respects, container IE can be LTM (Limited Time Management). -Config IE .
[0244] In some implementations, S-BS 501 can include the measurement results of cells 1 to N separately. Please switch beg In the message, S-BS 501 can receive measurement results from UE 102. C-BS 506 can select or determine cells 1 to M based on measurement results 1 to N. In other implementations, C-BS 506 can select or determine cells 1 to M based on one or more other factors (e.g., the capacity or load of cells 1 to 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.
[0245] In some implementations, S-BS 501 (e.g., the CU of S-BS 501) or CU 172 can generate a first security configuration (i.e., a single security configuration) for LTM candidate cells 1 to M of UE 102, or generate LTM candidate configurations 1 to M for UE 102. In some implementations, S-BS 501 can indicate LTM candidate configurations 1 to M and / or RRC reconfiguration messages 1 to M in LTM configuration delivery procedures 2 to M associated with the first security configuration in the first RRC reconfiguration message of event 518. To indicate the association, S-BS 501 can include the first security configuration and the first security configuration ID identifying the first security configuration in container IE 1, and include the first security configuration ID in a tuple (e.g., LTM-Candidate In IE 1 to M, based on the first security configuration ID, UE 102 identifies that LTM candidate cells 1 to M or LTM candidate configurations 1 to M of UE 102 share the same security configuration (i.e., the first security configuration). In some implementations, S-BS 501 may include the service security configuration ID associated with the serving cell in the first RRC reconfiguration message or container IE 1. In some implementations, the service security configuration ID may indicate (e.g., identify) 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 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 can determine the security configuration change for LTM cell handover from the serving cell to cell 1 and can apply the first security configuration to communicate with C-BS 506 via cell 1, as described above.
[0246] In the communication that begins at event 540, UE 102 may receive an LTM cell handover command from C-BS 506, thereby instructing UE 102 to perform an LTM cell handover to cell 2. In this case, UE 102 may perform an LTM cell handover to cell 2 in response to the LTM cell handover command, as described for an LTM cell handover to cell 1. Since UE 102 identifies the same security configuration (i.e., the first security configuration) as applicable 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 506 on cell 2. If UE 102 uses the second security algorithm to communicate with C-BS 506 on cell 1, then UE 102 uses or continues to use the second security algorithm to communicate with C-BS 506 on cell 2. If UE 102 uses the first security algorithm to communicate with C-BS 506 on cell 1, then UE 102 uses or continues to use the first security algorithm to communicate with C-BS 506 on cell 2. Similarly, C-BS 506 can perform similar actions to communicate with UE 102, as described above. The “M” in the above description can be changed to “N”.
[0247] In some implementations, S-BS 501 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 an LTM candidate cell (e.g., a cell operated by the second C-BS), similar to inter-CU LTM preparation procedure 598. S-BS 501 may send the LTM candidate configuration and the second security configuration to UE 102, similar to events 518 and 520. S-BS 501 may send second security information to the second C-BS, as described for the first security information. The examples and implementations described for 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.
[0248] In some implementations, S-BS 501 can include CSI resource configurations from 1 to N instead of tuples in the container IE, where N is an integer and greater than zero.
[0249] Figures 6A to 6D These are sequence diagrams illustrating example operations of communication processes 600A to 600D. Communication processes 600A to 600D are described with respect to MN 601B, C-SN 606, and S-SN 601A. MN 601B and S-SN 601A can be base station 104 of Figure 1. Figure 1B Base station 104A or 104B, Figure 1C Base station 164, or Figure 2A The implementation methods include eNB, ng-eNB 230, or gNB 232. C-SN 606 can be... Figure 1A Base station 106 Figure 1B Base station 106A or 106B, Figure 1C Base station 164, or Figure 2A The implementation methods of eNB, ng-eNB 230 or gNB 232.
[0250] Figure 6A This is a sequence diagram illustrating example operations for a communication process of inter-cell handover between first example CUs, wherein the first base station operates as MN 601B, the second base station operates as candidate SN (C-SN) 606, and the third base station operates as serving SN or source SN (S-SN) 601A.
[0251] In some respects, C-SN 606 includes CU 172 and DU 174. MN 601B may include CU and DU ( Figure 6A (not shown in the image), similar to Figure 3 Base station 301 in the S-SN 601A may include CU and DU ( Figure 6A (Not shown in the image), similar to C-SN606. Communication process 600A is similar to communication process 500, except that communication process 600A is an SN communication process, while communication process 500 is an MN communication process.
[0252] At event 602, UE 102 under DC can communicate with MN 601B and S-SN 601A. In some implementations, UE 102 is configured using the serving DU in cell 124A ( Figure 1A and Figure 1BThe UE 102 communicates with the DU of S-SN 601A on the DC and uses the serving CU to configure communication with the CU of S-SN 601A via the DU, similar to event 302. In some implementations, the UE 102 under the DC can transmit UL PDUs and / or DL PDUs with MN 601B and / or S-SN 601A via a radio bearer, which may include SRBs and / or DRBs. MN 601B and / or S-SN 601A can configure the radio bearer for the UE 102. The UE 102 under the DC can transmit UL PDUs and / or DL PDUs with S-SN 601A on the SCG (i.e., SCG radio resources) configured on S-SN 601A for communication with the UE 102. Under DC, UE 102 can transmit UL PDUs and / or DL PDUs with MN 601B on MCG (i.e., MCG radio resources) according to MN configuration (i.e., MCG configuration). In some implementations, the serving DU configuration can be SN configuration (e.g., SCG configuration).
[0253] In the MN configuration, MN 601B configures an MCG that includes at least one serving cell (e.g., cell 124B and / or other cells) operated by MN 601B. In the serving DU configuration, S-SN 601A configures an SCG that includes at least one serving cell (e.g., cell 124A and / or other cells) operated by S-SN 601A. In some implementations, the MN configuration may include multiple configuration parameters, and UE 102 may receive these configuration parameters from MN 601B in one or more RRC messages. (See also: Regarding...) Figure 3 The service DU configuration may include multiple configuration parameters. In some implementations, UE 102 may include these parameters in one or more RRC messages. For example Via MN 601B and / or in SRB ( For example The SRB receives these configuration parameters from the S-SN 601A on the MN 601B or S-SN 601A to exchange RRC messages between the UE 102 and the S-SN 601A.
[0254] UE 102 can use at least one first master security key and at least one first master security algorithm to perform security protection on data transmitted with MN601B, as described above. Figures 3 to 5 As described above, MN 601B can use 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, as described above. Figures 3 to 5As described above, depending on the implementation, the first master security key and the first master security algorithm used by UE 102 and MN 601B may be the same or different.
[0255] UE 102 can use 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 601A, as described above. Figure 3 and Figure 4 As described above, S-SN 601A can use at least one first secondary security key and at least one first secondary security algorithm to perform security protection on data transmitted with UE 102, as described above. Figure 3 and Figure 4 As described above, depending on the implementation, the first secondary security key and the first secondary security algorithm used by UE 102 and S-SN 601A may be the same or different.
[0256] In some respects, when communicating with UE 102 under DC via MN 601B and S-SN 601A, S-SN 601A can perform the CU-in-CU LTM configuration procedure 696 with UE 102, similar to the above-mentioned... Figure 3 and Figure 4 The procedures 396 and / or 496 are described above. In some other methods, when communicating with UE 102 under DC with MN 601B and S-SN 601A, S-SN 601A can perform an in-CU LTM procedure 680 with UE 102, similar to the above description. Figure 3 and Figure 4 Procedures 380 and / or 480 are described above. In procedure 696 or 680, the CU of S-SN 601A can send one or more RRC reconfiguration messages to UE 102 via SRB3. Each RRC reconfiguration message includes one or more LTM candidate configurations, similar to the above description. Figure 3 and Figure 4 The process described is 394 or 494. Alternatively or additionally, the CU of S-SN 601A may send one or more RRC reconfiguration messages to UE 102 via MN 601B, each RRC reconfiguration message including one or more LTM candidate configurations. In response to each RRC reconfiguration message, UE 102 may send an RRC reconfiguration complete message to S-SN 601A via MN 601B.
[0257] At event 604A, when communicating with MN 601B and S-SN 601A under DC, UE 102 can, for example, directly send at least one measurement report to S-SN 601A via SRB3, similar to the above regarding... Figures 3 to 5The discussed events are 304 or 306, 404 or 406, and 504. Alternatively or additionally, UE 102 may send a measurement report to MN 601B. MN601B may generate at least one SN message including the measurement report and may send the SN message to CU 172. In one implementation, the SN message includes... RRC transmission Messages and / or SN Modification Request The S-SN 601A (e.g., the CU of the S-SN 601A) can generate a measurement configuration to configure the UE 102 to send measurement reports, and can send measurement reports to the UE 102 directly (e.g., via the S-DU of the S-SN 601A) or via the MN 601B.
[0258] After receiving one or more measurement reports from the measurement reports from UE 102 (e.g., in response to this), S-SN 601A (e.g., the CU of S-SN 601A) can determine that the first cell (e.g., Figure 1B Cell 126A is prepared as an LTM candidate cell for UE 102. In response to the determination, S-SN 601A may generate a first cell ID (e.g., cell ID 1) including the first cell (e.g., cell 1) and / or an indication of the target SN ID of C-SN 606 (first SN requirement message). In some implementations, the SN requirement message may include an LTM indicator indicating that the SN requirement message relates to LTM for the first cell ID.
[0259] At event 603, S-SN 601A can send an SN request message to MN 601B.
[0260] At event 605, upon receiving the SN request message (e.g., in response to this), MN 601B may send an SN request message (first SN request message) including the first cell ID to CU 172 to request that the first cell be prepared as an LTM candidate cell for UE 102.
[0261] In response to the SN request message, CU 172 can perform LTM preparation procedure 690 with DU 174 to prepare the first cell as an LTM candidate cell for UE 102, similar to LTM preparation procedures 390, 490, or 590. In procedure 690, CU 172 can send 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 can then generate a first LTM candidate configuration (LTM candidate configuration 1).
[0262] At event 607, in response to the SN request message, CU 172 may send an SN request confirmation message (first SN request confirmation message) to MN 601B, including the first LTM candidate configuration. In some implementations, CU 172 may include 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).
[0263] At event 609A, MN 601B may send an SN confirmation message (e.g., a first SN confirmation message) to S-SN 601A that includes the first LTM candidate configuration. In some implementations, MN 601B may include 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).
[0264] Events 603, 605, 607, and 609A, along with LTM preparation process 690, are in Figure 6A This is collectively referred to as the SN-initiated SN-inter-SN LTM preparation process 698A.
[0265] In some implementations, the SN request message and the SN confirmation message can be respectively SN Change Requirement Messages and SN change Further confirmation Messages. In other implementations, the SN request message and the SN confirmation message can be respectively SN modification requirements Messages and SN Modification Confirmation Messages. In some implementations, the SN request message and the SN request acknowledgment message can be SN... Please add beg Messages and SN Add request confirmation Messages. In other implementations, the SN request message and the SN request confirmation message can be SN... Modification Request Messages and SN Confirmation of modification request information.
[0266] In some implementations, the SN request message may include the DU ID of the S-DU of S-SN 601A. In such cases, MN 601B 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 may include the first BS ID of S-SN 601A. In some implementations, MN 601B 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 601B 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 may be gNB IDs.
[0267] CU 172 may or may not request the LTM reference DU configuration in procedure 690, as mentioned above. Figure 3 , Figure 4 and Figure 5 As described above, DU 174 may or may not send the LTM reference DU configuration to CU 172 in process 690, as mentioned above. Figure 3 , Figure 4 and Figure 5 As described above. In some implementations, the S-SN 601A (e.g., the CU of the S-SN 601A) can obtain an LTM reference configuration, as mentioned above. Figure 3 and Figure 4 In other implementations, S-SN 601A may receive an LTM reference configuration from MN 601B during the LTM preparation process between another SN, as described above and below. If S-SN 601A obtains the LTM reference configuration, it may include the LTM reference configuration (e.g., an LTM reference configuration generated by S-SN) in the SN request message. Subsequently, MN 601B may include the LTM reference configuration in the SN request message. Alternatively or additionally, S-SN 601A determines to request or cause C-SN 606 to provide a complete LTM candidate configuration such that S-SN 601A does not send the LTM reference configuration to C-SN 606. If S-SN 601A does not obtain the LTM reference configuration, it does not include the LTM reference configuration in the SN request message. If the SN request message includes the LTM reference configuration, MN 601B may include the LTM reference configuration in the SN request message. If the SN requirement information does not include the LTM reference configuration, then the MN 601B may omit the LTM reference configuration from the SN request message.
[0268] If the SN request message includes an LTM reference configuration as described above, then CU 172 may include the LTM reference configuration in the first CU-DU message. Alternatively or additionally, CU 172 may extract the LTM reference DU configuration from the LTM reference configuration and may include the LTM reference DU configuration in the first CU-DU message. If the SN request message does not include an LTM reference configuration, then CU 172 may or may not receive the LTM reference DU configuration from DU 174, as described above. Figure 3 As described above. If CU 172 (e.g., in the first DU to CU message) receives an LTM reference DU configuration, CU 172 can generate an LTM reference configuration that includes the LTM reference DU configuration (e.g., an LTM reference configuration generated by the C-SN). CU 172 can include an LTM reference CU configuration (e.g., an LTM reference CU configuration generated by the C-CU) in the LTM reference configuration. If CU 172 does not receive an LTM reference DU configuration from DU 174, as described above... Figure 3 In this case, CU 172 does not generate an LTM reference configuration. Alternatively or additionally, CU 172 may generate an LTM reference configuration that includes the LTM reference CU configuration generated by C-CU (e.g., the LTM reference configuration generated by C-SN). In some aspects, the LTM reference configuration only includes the LTM reference CU configuration generated by C-CU. In the case where CU 172 generates an LTM reference configuration (e.g., the LTM reference configuration generated by C-SN), CU 172 may include the LTM reference configuration generated by C-SN in the SN request confirmation message.
[0269] In some implementations, if LTM DU configuration 1 is a complete configuration, CU 172 can generate LTM candidate configuration 1 as a complete configuration. CU 172 can include a complete configuration indication (e.g., a BS-to-BS interface protocol field or 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 an Xn application protocol (e.g., as defined in 3GPP TS 38.423). In some implementations, the complete configuration indication can be a new field or IE (e.g., LTM-specific) to avoid impacting non-LTM configurations. In other implementations, the complete configuration indication can be an existing field or IE (e.g., as defined in 3GPP TS 38.423).
[0270] If LTM DU configuration 1 is an incremental configuration, CU 172 can generate LTM candidate configuration 1 as an incremental configuration. CU 172 can exclude the full configuration indication from the SN request confirmation message to indicate that LTM candidate configuration 1 is an incremental configuration. Alternatively or additionally, CU 172 can include an incremental configuration indication (e.g., a BS-to-BS interface protocol field or 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 an Xn application protocol (e.g., as defined in 3GPP TS 38.423). In some implementations, the incremental configuration indication is a new field or IE (e.g., LTM-specific) to avoid impacting non-LTM configurations. In other implementations, the incremental configuration indication is an existing field or IE (e.g., as defined in 3GPP TS 38.423). In some implementations, the BS-to-BS interface protocol field or IE can have two values (i.e., a first value and a second value). The BS-to-BS interface protocol field or IE set to the first value is a full configuration indication, and the BS-to-BS interface protocol field or IE set to the second value is an incremental configuration indication.
[0271] In some implementations, the S-SN 601A 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 other implementations, the CU 172 can receive the CSI resource configuration and / or LTM SSB configuration from the OAM node. In yet another implementation, the S-SN 601A can receive the CSI resource configuration and / or LTM SSB configuration from the CU 172. For example, the CU 172 can include the CSI resource configuration and / or LTM SSB configuration in the SN request confirmation message. In this case, the MN 601B can include the CSI resource configuration and / or LTM SSB configuration in the SN confirmation message. In some implementations, the CU 172 can include the PCI of the first cell in the SN request confirmation message. In this case, the MN 601B can include the PCI of the first cell in the SN confirmation message. In order to prepare the first cell as a candidate LTM cell for UE 102, the CU of S-SN 601A can perform the LTMCSI report configuration and / or LTM ID configuration procedures with the S-DU of S-SN 601A. Figure 6A (not shown in the image), respectively similar to Figure 3 and Figure 4Procedure 392 or 492. During the LTM CSI report configuration and / or LTM ID configuration process, the CU of S-SN 601A may send CSI resource configuration and / or LTM SSB configuration to the S-DU of S-SN 601A. In response, the CU of S-SN 601A may receive one or more CSI report configurations for UE 102 from the S-DU of S-SN 601A. In some implementations, S-SN 601A may receive a second service DU configuration that includes the CSI report configuration.
[0272] In some implementations, CU 172 can receive early synchronization information and / or PDCCH command information for the first cell from DU 174, as described above. Figure 5 As described above. In some implementations, early synchronization information may include RACH configuration (e.g., RACH configuration 1) and / or at least one TCI state configuration (e.g., TCI state configuration 1). CU 172 may include early synchronization information and / or PDCCH command information in the SN request confirmation message. MN 601B may include early synchronization information and / or PDCCH command information in the SN confirmation message.
[0273] In some implementations, CU 172 may assign an LTM ID (e.g., LTM ID 1) to identify a first LTM candidate configuration, and may include the LTM ID and / or the associated (or mapped) cell ID for the LTM ID in the SN request confirmation message. MN 601B may include the LTM ID and / or the associated (or mapped) cell ID for the LTM ID in the SN confirmation message. In other implementations, S-SN 601A may assign an LTM ID (e.g., LTM ID 1) to identify a first LTM candidate configuration. In yet another implementation, MN 601B assigns an LTM ID (e.g., LTM ID 1) to identify a first LTM candidate configuration. In such cases, MN 601B may include the LTM ID in the SN confirmation message. After receiving or assigning the LTM ID, the CU of S-SN 601A may send the LTM ID and the first cell ID to the S-DU during the LTM ID configuration process, similar to... Figure 3 Process 390 or 392 or Figure 4 The process 492.
[0274] Upon receiving the SN confirmation message (e.g., in response to it), S-SN 601A (e.g., the CU of S-SN 601A) may perform LTM configuration delivery procedure 694A with UE 102 to send the LTM ID and LTM candidate configuration to UE 102. In some implementations, S-SN 601A may send {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, S-SN 601A 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 the first cell in the tuple sent to the first RRC reconfiguration message and / or other RRC reconfiguration messages to UE 102, as described above regarding... Figure 3 and Figure 4 The S-SN 601A may include the LTM ID in the first RRC reconfiguration message 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 the first cell are associated with the first cell. For example, the S-SN 601A may include 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, the S-SN 601A may include the tuple in an RRC reconfiguration message other than the first RRC reconfiguration message. In response to each RRC reconfiguration message in the other RRC reconfiguration messages, the UE 102 may send an RRC reconfiguration complete message to the CU 172 via the S-DU 174A.
[0275] In some implementations, the MN 601B (e.g., the CU of the MN 601B) may include the first MN-to-SN LTM security configuration in the SN request message. In some aspects, the first MN-to-SN LTM security configuration may be an LTM security configuration or a list of configuration parameters. In some implementations, the first MN-to-SN LTM security configuration may include a list of tuples 1 to L, where L is a positive-zero integer. Tuples 1 to L may include {RAN-level security key (e.g., S-NG-RAN node security key) 1 and / or security key (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 601B may include the security capabilities of UE 102 in the SN request message.
[0276] In some implementations, the MN 601B (e.g., the CU of the MN 601B) can generate a first UE LTM security configuration based on the first MN-SN LTM security configuration, and can include the first UE LTM security configuration in the SN confirmation message. In some aspects, the first UE LTM security configuration can be an LTM security configuration or a list of configuration parameters. In some implementations, the S-SN 601A can include the first UE LTM security configuration in a container IE that includes tuple 1 (e.g., LTM-Config In the IE, the container IE can be included in the first RRC reconfiguration message. In other implementations, S-SN 601A can include the first UE LTM security configuration in tuple 1.
[0277] In some implementations, the first UE LTM security configuration may include at least a portion of the first MN to SN LTM security configurations. For example, the first UE LTM security configuration may include a list of SK counters (e.g., SK counters 1 to L) included in the first MN to SN LTM security configurations, and may not include any RAN-level security keys in the first MN to SN LTM security configurations. 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 the security capabilities of the MN and / or SN. In some implementations, the second security algorithm may include encryption algorithms and / or integrity algorithms that may be the same as or different from the first security algorithm.
[0278] In some implementations, if the SN request message includes a full configuration indication to indicate that LTM candidate configuration 1 is a full configuration, then the S-SN 601A may include the full configuration indication (e.g., an RRC field or IE) in the first RRC reconfiguration message to indicate that LTM candidate configuration 1 is a full configuration. If the SN request message does not include a full configuration indication or includes an incremental configuration indication to indicate that LTM candidate configuration 1 is an incremental configuration, then the S-SN 601A excludes or does not include the full configuration indication (e.g., an RRC field or IE) in the first RRC reconfiguration message to indicate that LTM candidate configuration 1 is an incremental configuration.
[0279] At event 624A, UE 102 may optionally send at least one measurement report including measurement results to S-SN 601A. In some aspects, the measurement report may be an L1 measurement report including L1 measurement results.
[0280] At event 650A, if the SN confirmation message of event 609A includes PDCCH command information (PDCCH command information 1), then S-SN 601A may optionally send a PDCCH command to UE 102 based on the PDCCH command information. If S-SN 601A is a distributed base station, then the CU of S-SN 601A may send the PDCCH command information to the S-DU of S-SN 601A, and the S-DU may send a PDCCH command to UE 102. For example, S-SN 601A or its S-DU may send a PDCCH command including the PDCCH command information to UE 102. In some implementations, S-SN 601A or its S-DU may determine to send the PDCCH command based on (e.g., in response to) the measurement report of event 624A. In some implementations, the S-SN 601A or S-DU may determine the SSB index to be included in the PDCCH command based on the L1 measurement report of event 624A, and / or CSI resource configuration, CSI report configuration, and / or LTM SSB configuration. In some implementations, the S-DU or S-SN 601A may include LTM ID 1 in the PDCCH command to indicate the first cell.
[0281] At event 652, UE 102 can send an RA preamble to DU174 on the first cell using RACH configuration and / or PDCCH command information. S-DU or S-SN 601A can derive the TA value based on the RA preamble.
[0282] At event 656, DU 174 can send a message including the TA value to CU 172. DU-CU TA Information Transmission Message. In some implementations, DU 174 may include the cell ID 1, RA preamble index, RA-RNTI, and / or the DU ID of the S-DU of S-SN 601A in the message. DU-CU TA Information Transmission The message states that DU 174 may include the first BS ID and / or the second BS ID. DU-CU TA Information Transmission In the message.
[0283] At event 657, CU 172 can send a message including the TA value to MN 601B (e.g., the CU of MN 601B). CU-CU TA Information Transmission Message. In some implementations, CU 172 can include the cell ID 1, RA preamble index, RA-RNTI, and / or S-DU DU ID in the message. CU-CU TA Information Transmission In the message. In some implementations, CU 172 may additionally include the first BS ID and / or the second BS ID. CU-CU TA Information Transmission In the message.
[0284] In some implementations, CU 172 determines the address (e.g., IP address) of MN 601B or its CU based on a second BS ID. In such implementations, CU 172 can send event 657 to MN 601B based on this address. CU-CU TA Information Transmission information.
[0285] At event 658, MN 601B can send a message including the TA value to S-SN 601A. CU-CU TA Information Transmission Message. In some implementations and depending on the element sent at events 656 and / or 657, MN 601B can... CU-CU TA Information transmission The message includes cell ID 1, RA preamble index, RA-RNTI, and / or the DU ID of the S-DU. In some implementations, if the first BS ID and / or the second BS ID are included in event 656... DU-CU TA Information Transmission Messages and / or events 657 CU-CU TA Information Transmission In the message, MN 601B may additionally include the first BS ID and / or the second BS ID. CU-CU TA Information Transmission In the message.
[0286] In some implementations, MN 601B can determine the address (e.g., IP address) of S-SN 601A or its CU based on the first BS ID. In other implementations, MN 601B can determine the address (e.g., IP address) of S-SN 601A or its CU based on the DU ID of S-DU of S-SN 601A. In such implementations, MN 601B sends event 658 to S-SN 601A or its CU based on the address. CU-CU TA Information Transmission information.
[0287] At event 654A, UE 102 may send at least one measurement report, including measurement results, to S-SN 601A. In some respects, the measurement report may be an L1 measurement report that includes L1 measurement results.
[0288] At event 626A, in response to an L1 measurement report determination command based on events 624A and / or 654A, UE102 performs an LTM cell handover to the first cell, S-DU or S-SN 601A may send an LTM cell handover command including LTM ID 1 to UE102.
[0289] At event 632, in response to the LTM cell handover command, UE 102 can cease communication on the serving cell and access the first cell. When UE 102's access to the first cell is detected, at event 634, DU 174 can send an access success message to CU 172. At event 636A, UE 102 can send an RRC reconfiguration complete message to DU 174 during or after the access event at event 632. At event 638, DU 174 can then send a DU-CU message including the RRC reconfiguration complete message to CU 172. In some other implementations, UE 102 can send the RRC reconfiguration complete message to C-SN 606 via MN 601B instead of via DU 174.
[0290] In some implementations, UE 102 can derive at least one second security key based on a first UE LTM security configuration (e.g., SK timer 1). In some implementations, UE 102 can derive a new SN key (e.g., a new SK timer 1) based on the first UE LTM security configuration. gNB The UE 102 can derive the second security key from the new SN key. In some implementations, if the UE 102 receives a second security algorithm for the first cell (i.e., the LTM candidate cell), the UE 102 can derive the second security key based on the new SN key and the second security algorithm. If the UE 102 does not receive the second security algorithm, the UE 102 can derive the second security key based on the new SN key and the first security algorithm. In some implementations, the UE 102 can derive the second security key in response to receiving an LTM cell handover command at event 626A. In other implementations, the UE 102 can derive the second security key after receiving the first UE LTM security configuration and before receiving the LTM cell handover command at event 626A.
[0291] UE 102 may apply a second security key to communicate with CU 172 in events 636A and 640. If UE 102 receives the second security algorithm as described above, UE 102 may apply both the second security key and the second security algorithm to communicate with CU 172 in events 636A and 640. If UE 102 does not receive the second security algorithm, UE 102 may apply both the second security key and the first security algorithm to communicate with CU 172 in events 636A 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 636A and / or 640). In other implementations, the second security key includes an encryption key for encryption / decryption of control plane data packets (e.g., RRC reconfiguration completion messages in event 636A and / or RRC messages in event 640). In another implementation, the security key includes an integrity key for integrity protection of user plane data packets in event 640 (e.g., transmitted via DRB). In yet another implementation, the security key includes an encryption key for encryption / decryption of user plane data packets in event 640 (e.g., transmitted via DRB). UE 102 may stop communicating with CU 172 using the first security key.
[0292] In some implementations, CU 172 can derive at least one second security key based on the first MN-to-SN LTM security configuration (e.g., RAN-level security key 1 and SK counter 1). In some implementations, CU 172 can derive a new SN key (e.g., a new SK counter) based on the first MN-to-SN LTM security configuration. gNB Furthermore, the second security key can be derived from the new SN key. In some implementations, if CU 172 sends a second security algorithm for the first cell (i.e., the LTM candidate cell) to UE 102, CU 172 can derive the second security key based on the new SN key and the second security algorithm. If CU 172 does not send the second security algorithm to UE 102, CU 172 can derive the second security key based on the new SN key and the first security algorithm.
[0293] In some implementations, CU 172 may derive a second security key in response to receiving a CU-CU cell handover notification message for event 628, an access success message for event 634, or a DU-CU message for event 638. In other implementations, CU 172 may derive the second security key after receiving the first MN-SN LTM security configuration and before receiving the CU-CU cell handover notification message for event 628, the access success message for event 634, or the DU-CU message for event 638. CU 172 may apply the second security key in events 636A and 640 to communicate with UE 102. 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 636A and / or 640). In other implementations, the second security key includes an encryption key for encryption / decryption of control plane data packets (e.g., RRC messages in events 636A and / or 640). In yet another implementation, the second security key includes an integrity key for integrity protection of user plane data packets in event 640 (e.g., transmitted via DRB). In yet another implementation, the second security key includes an encryption key for encryption / decryption of user plane data packets in event 640 (e.g., transmitted via DRB). In some implementations, the second security key applied by CU 172 is the same as the second security key applied by UE 102.
[0294] In some implementations, UE 102 may perform an RA procedure to access the first cell in event 632. 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 601A may include a first set of LTM CFRA configuration parameters in the LTM cell handover command of event 626A to configure UE 102 to perform a CFRA procedure to access the first cell. UE 102 may use the first set of LTM CFRA configuration parameters to perform the CFRA procedure. In some implementations, DU 174 may include the first set of LTM CFRA configuration parameters in the first DU to CU message of LTM preparation procedure 690, as described for LTM preparation procedure 490. CU 172 may then include the first set of LTM CFRA configuration parameters in the SN request confirmation message. In some implementations, DU 174 may include at least one additional set of LTM CFRA configuration parameters in the first DU to CU message, as described for LTM preparation procedure 490. CU 172 can then include an additional set of LTM CFRA configuration parameters in the SN request confirmation message of event 607.
[0295] In some implementations, DU 174 configures a first set and / or an additional set for UL (i.e., NUL) or SUL, and such configuration can be indicated in the first DU to CU message, such as Figure 4 As described in C-DU 174B. When configuring a first set and / or an additional set for either UL or SUL, CU 172 may include a single UL or SUL indicator in the SN request confirmation message, indicating that the first set and / or the additional set is configured for either UL or SUL. When configuring the first set and / or the additional set for UL in DU 174, CU 172 may include the first set and / or the additional set in a first field or IE in the SN request confirmation message. When configuring the first set and / or the additional set for SUL in DU 174, CU 172 may include the first set and / or the additional set in a second field or IE in the SN request confirmation message. In such cases, the first field or IE and the second field or IE are defined for UL and SUL, respectively.
[0296] In some implementations, DU 174 configures a first set for one of UL and SUL, and an additional set for the other of UL and SUL, and this configuration can be indicated in the first DU to CU message, such as... Figure 4 As described in C-DU 174B. In such cases, CU 172 sets the UL or SUL indicator in the first set to indicate the value of either UL or SUL, and sets the UL or SUL indicator in the supplementary set to indicate the value of the other UL or SUL. Alternatively or additionally, CU 172 may include the first set and the supplementary set in one and the other of the first field or IE and the second field or IE in the SN request confirmation message, respectively.
[0297] After receiving the access success message at event 634 or the DU-to-CU message including the RRC reconfiguration completion message at event 638, at event 640, C-SN 606 communicates with UE 102 under DC and MN 601B and C-SN 606 according to the first LTM candidate configuration and / or LTM reference configuration. In some implementations, UE 102 may include LTM ID 1 in the RRC reconfiguration completion message at event 636A 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 LTM reference configuration. In other implementations, CU 172 identifies the first LTM candidate configuration and / or LTM reference configuration based on the first cell ID included in the access success message at event 634. In such implementations, CU 172 may maintain or store association information between the first cell ID and the first LTM candidate configuration and / or LTM reference configuration. When CU 172 receives the first cell ID in the access success message, CU 172 identifies the first LTM candidate configuration and / or LTM reference configuration based on the first cell ID and associated information.
[0298] In some implementations, if the S-DU or S-SN 601A receives the TA value as described above, the S-DU or S-SN 601A may include the TA value in the LTM cell handover command for event 626A. In some implementations, the S-DU or S-SN 601A may include the first TCI state ID in the LTM cell handover command. The first TCI state ID may indicate the first TCI state configuration in the TCI state configuration.
[0299] In response to the confirmation command UE 102 performing an LTM cell handover or sending an LTM cell handover command at event 626A, the S-DU of S-SN 601A can send to the CU of S-SN 601A. DU-CU cell handover notification The message instructs UE 102 to perform an LTM cell handover to the first cell.
[0300] At event 627A, in response to receiving DU-CU cell handover notification The message indicates that the CU of S-SN 601A can send data to MN601B. CU-CU cell handover notification Information to instruct UE 102 to perform or be performing an LTM cell handover to the first cell.
[0301] At event 628, the response was received. CU-CU cell handover notification The MN 601B can send messages to the 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.
[0302] At event 630, the response was received. DU-CU cell handover notification Message, CU 172 can send to DU 174 CU-DU Cell Handover Notification This message indicates that UE 102 is about to perform or is performing an LTM cell handover to the first cell. In some implementations, S-SN 601A may include the first TCI state ID in event 627A. CU-CU cell handover notification In the message. In such cases, the MN 601B can include the first TCI state ID in event 628. CU-CU cell handover Know In the message. Then, CU 172 can include 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 apply the first TCI state configuration in events 632, 636A, and / or 640 to transmit UL and / or DL transmissions. In other implementations, where separate TCI states are used, the DL TCI state and the UL TCI state can use different TCI state IDs. In such cases, the S-DU of S-SN 601A can include the first TCI state ID of DL and the second TCI state ID of UL. DU-CU Cell handover notification In messages and / or LTM cell handover commands, these TCI state IDs identify the first and second TCI state configurations in the TCI state configuration. In response to... DU-CU cell handover notification The message states that the CU of S-SN 601A can then include the first TCI status ID and the second TCI status ID in MN 601B. CU-CU cell handover notification The message states that MN601B can include the first TCI status ID and the second TCI status ID in the CU 172. CU-CU cell handover notification In the message. Then, CU 172 can include the first TCI status ID and the second TCI status ID in the message to DU 174. CU-DU cell handover notifyIn 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 can apply the first TCI state configuration and the second TCI state configuration in events 632, 636A, and / or 640 to transmit DL and UL transmissions with DU 174, 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 can apply the first TCI state configuration and / or the second TCI state configuration in events 632, 636A, and / or 640 to transmit DL and / or UL transmissions with UE 102, respectively.
[0303] At event 631, in some implementations, after determining that UE 102 performs an LTM cell handover or after sending an LTM cell handover command at event 626A (e.g., in response to this), S-SN 601A may send one or more commands to MN 601B. Early state transfer Each early state delivery message includes a DL COUNT value or DISCARD DLCOUNT value for the DRB, and UE 102 and S-SN 601A can (e.g., at event 602) transmit data to each other on that DRB.
[0304] At event 633, MN 601B can send one or more messages to CU 172. Early state transfer Each early state delivery message includes a DL COUNT value for the DRB or a DISCARD DL COUNT value, and UE 102 and S-SN 601A can (e.g., at event 602) transmit data to each other on that DRB.
[0305] At event 639, in some implementations, upon receiving event 634... Connection successful After receiving either the DU to CU message or the RRC reconfiguration complete message (Event 638), CU 172 can send an LTM success message to MN 601B (e.g., the CU of MN 601B) to indicate successful LTM cell handover. In some implementations, the LTM success message is... SN Modification requirementsThe message is either a BS-to-BS access success message. In some implementations, CU 172 may include the first cell ID in the LTM success message. In other implementations, CU 172 does not send a BS-to-BS message to MN 601B (e.g., the CU of MN 601B) to indicate successful LTM cell handover. In some implementations, after receiving an LTM success message from UE 102 or receiving an RRC reconfiguration completion message (e.g., in response to this), MN 601B may send an SN message to S-SN 601A (e.g., ...). Figure 6C (As shown at event 645 in the diagram). The SN message can indicate that the LTM cell handover has been successfully completed, that S-SN 601A will suspend communication with UE 102, or that S-SN 601A will release the UE context of UE 102 and the resources configured for UE 102. MN 601B can include the first cell ID and / or the RRC reconfiguration completion message of event 636C in the SN message. In some implementations, the SN message is... SN Modification Request Message , SN release request Messages, SN access success messages, etc.
[0306] At event 641, in some implementations, the LTM cell handover is performed by determining the command UE 102 to perform the handover, the LTM cell handover command is sent at event 626A, and the command is received from the S-DU. DU-CU cell handover notification Upon receiving a message or an SN message (e.g., in response to this), S-SN 601A (e.g., the CU of S-SN 601A) may send an SN to MN 601B including the DL COUNT value and / or UL COUNT value for the DRB. State transfer The message indicates that UE 102 and S-SN 601A transmit data to each other on this DRB.
[0307] Received at event 642, received at event 641 SN status transmission Following the message (e.g., in response to this), the MN601B can send an SN to the CU 172 including the DL COUNT value and / or the UL COUNT value. State transfer information.
[0308] In some implementations, before or after sending the LTM cell handover command, or during, before or after process 698A, S-SN 601A (e.g., the CU of S-SN 601A) may, together with MN 601B and one or more C-SNs (including C-SN 606), prepare additional cells (i.e., cells 2 to N) as LTM candidate cells for UE 102, as described above. N is an integer greater than 1. C-SNs may operate cells 2 to N. For example, S-SN 601A may, together with MN 601B, perform additional inter-SN LTM preparation processes 2 to N to prepare cells 2 to N respectively. Each inter-SN LTM preparation process 2 to N is similar to process 698A. In inter-SN LTM preparation processes 2 to N, S-SN 601A may receive LTM candidate configurations 2 to N respectively configured for LTM. As described above, MN 601B, S-SN 601A, or C-SN assigns LTM IDs 2 to N to identify LTM candidate configurations 2 to N, respectively. S-SN 601A can obtain CSI resource configurations 2 to N for cells 2 to N, as described for CSI resource configuration 1. S-SN 601A can obtain CSI reporting configurations 2 to N for cells 2 to N, as described for CSI reporting configuration 1. S-SN 601A can obtain RACH configurations 2 to N for cells 2 to N, as described for RACH configuration 1. S-SN 601A can obtain TCI status configurations 2 to N for cells 2 to N, as described for TCI status configuration 1. S-SN 601A can obtain LTM SSB configurations 2 to N for cells 2 to N, as described for LTM SSB configuration 1. In some implementations, the S-SN 601A can perform LTM configuration delivery procedures 2 to N with the UE 102 to send to the UE 102, respectively, a list of tuples such as: {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 PCI N of cell N}. Each LTM configuration delivery procedure 2 to N is associated with... Figure 3 Process 394 Figure 4 Process 494 and / or Figure 5Events 518 and 520 are similar. In other implementations, S-SN 601A can include the list in the first RRC reconfiguration message.
[0309] To simplify the following description, tuples 1 through N are used to 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}. In some implementations, S-SN 601A may include tuples 1 through N in RRC reconfiguration messages 1 through N within LTM configuration delivery procedures 1 through N. RRC reconfiguration message 1 is the first RRC reconfiguration message of procedure 694A. In some implementations, S-SN 601A may include tuples 1 through N in a container IE (e.g., ...). LTM-Config IE) 1 to N, and containers IE 1 to N can be included in RRC reconfiguration messages 1 to N respectively. In other implementations, S-SN 601A can include tuples 1 to N in container IE 1 (e.g., LTM-Config In IE), container IE 1 can be included in the first RRC reconfiguration message.
[0310] In some implementations, the S-SN 601A can include CSI resource configurations from 1 to N instead of tuples in the container IE, where N is an integer greater than zero.
[0311] In some implementations, the SN request message and SN confirmation message in each of the SN-to-N inter-SN LTM preparation processes 2 to N can be respectively an SN modification request message and an SN modification confirmation message. In other implementations, the SN request message and SN confirmation message in each of the SN-to-N inter-SN LTM preparation processes 2 to N can be respectively an SN change request message and an SN change confirmation message. In some implementations, the SN request message and SN request confirmation message in each of the SN-to-N inter-SN LTM preparation processes 2 to N can be respectively an SN... Add request Messages and SN Please add Please confirm. Messages. In other implementations, the SN request message and SN request confirmation message in each of the SN LTM preparation processes 2 to N can be respectively SN Modification Request Messages and SN Confirmation of modification request 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) can alternatively be provided in the SN modification request message from MN 601B to S-SN 601A (i.e., similar to that provided in the SN confirmation message). Figure 6B (Event 609B described in communication process 600B).
[0312] In other implementations, S-SN 601A may perform procedure 698A with CU 172 to prepare one or more cells from cell 1 and cells 2 to N as LTM candidate cells for UE 102. Cells 2 to N are identified by cell IDs 2 to N, respectively, and are operated by DU 174 and / or other DUs of C-SN 606. In such implementations, S-SN 601A may include cell IDs 2 to N in the SN request message for LTM event 603, and MN 601B may include cell IDs 2 to N in the SN request message, as described above for cell ID 1. In some implementations, upon receiving the SN request message, CU 172 determines or selects cells 1 to M from cells 1 to N as LTM candidate cells. M is a positive integer and M ≤ N. In other implementations, CU 172 prepares cells 1 to N for LTM as requested in the SN request message. CU 172 can perform LTM preparation procedures 2 to M with DU 172 to prepare cells 2 to M as LTM candidate cells for UE 102, respectively. LTM preparation procedures 2 to M are similar to the procedure 690 performed by CU 172 with DU 174 to prepare cell 1. As a result of LTM preparation procedures 2 to M, CU 172 can obtain LTM candidate configurations 2 to M for cells 2 to M, similar to obtaining LTM candidate configuration 1. C-SN 606 can generate LTM candidate configurations 2 to M as a complete configuration, or generate incremental configurations based on the LTM reference configuration, as described for LTM candidate configuration 1. CU 172 can include LTM candidate configurations 2 to M in the SN request confirmation message. In some implementations, CU 172, MN 601B, or S-SN 601A assigns LTM IDs 2 to M to identify LTM preparation procedures 2 to M, respectively, as described for LTM ID 1 and LTM candidate configuration 1. When CU 172 assigns LTM IDs 1 to M, CU 172 may include LTM IDs 1 to M and LTM candidate configurations 1 to M in the SN request confirmation message, as described for LTM ID 1 and LTM candidate configuration 1 respectively.
[0313] In some implementations, CU 172 can obtain early synchronization information 2 to M for cells 2 to M respectively, as described for early synchronization information 1. CU 172 can include the early synchronization information 2 to M in the SN request confirmation message. In some implementations, CU 172 or S-SN 601A can obtain CSI resource configurations 2 to M for cells 2 to M respectively, as described for CSI resource configuration 1. When CU 172 obtains CSI resource configurations 2 to M, CU 172 can include the CSI resource configurations 2 to M in the SN request confirmation message.
[0314] In some implementations, CU 172 or S-SN 601A can obtain LTM SSB configurations 2 to M for cells 2 to M respectively, as described for LTM SSB configuration 1. When CU 172 obtains LTM SSB configurations 2 to M, CU 172 can include LTM SSB configurations 2 to M in the SN request confirmation message. In some implementations, CU 172 or S-SN 601A can obtain PCI 2 to M for cells 2 to M respectively, as described for PCI 1. When CU 172 obtains PCI 2 to M, CU 172 can include PCI 2 to M in the SN request confirmation message.
[0315] In some implementations, CU 172 may include a list of tuples in the SN request confirmation message including: {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 IDM, 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 601B may include the list or a portion of the list in the SN confirmation message.
[0316] In some implementations, CU 172 can obtain PDCCH command information 2 to M for cells 2 to M respectively, as described for PDCCH command information 1. In one implementation, CU 172 can include PDCCH command information 2 to M in the SN request confirmation message. In another implementation, CU 172 can include PDCCH command information 2 to M in the early synchronization information 2 to M respectively. MN 601B can include PDCCH command information 2 to M in the SN confirmation message, as described for PDCCH command information 1. S-SN 601A can obtain RACH configuration 2, TCI status configuration 2 and / or PDCCH command information 2, ..., RACH configuration M, TCI status configuration M and / or PDCCH command information M respectively from the early synchronization information 2 to M or from the SN confirmation message.
[0317] In some implementations, S-SN 601A can perform LTM configuration delivery procedures 2 to M with UE 102 to send tuples 2 to M to UE 102 respectively. Each LTM configuration delivery procedure in LTM configuration delivery procedures 2 to M is related to... Figure 3 Process 394 Figure 4 Process 494 and / or Figure 5 Events 518 and 520 are similar. In some implementations, S-SN 601A can include tuples 1 to M in the container IE (e.g., LTM-Config IE) 1 to M, and containers IE 1 to M can be included in RRC reconfiguration messages 1 to M respectively. In other implementations, S-SN 601A can include tuples in the first RRC reconfiguration message. In some implementations, S-SN 601A can include tuples 1 to M in container IE 1 (e.g., LTM-Config In IE), container IE 1 can be included in the first RRC reconfiguration message.
[0318] In some implementations, MN 601B may include the measurement results 1 to N of cells 1 to N separately in the SN request message. In some implementations, MN 601B may receive the measurement results from UE 102 and / or from the SN request message from S-SN 601A. C-SN 606 may select or determine cells 1 to M based on the measurement results 1 to N. In other implementations, C-SN 606 may select or determine cells 1 to M based on other factors (e.g., the capacity or load of cells 1 to N and / or the maximum number of LTM candidate cells). In one implementation, the maximum number of LTM candidate cells may be included in the SN request message. In another implementation, the maximum number may be a predetermined number.
[0319] Events 626A, 627A, 628, 630, 631, 632, 633, and 634 are in Figure 6A This is collectively referred to as LTM execution process 699.
[0320] In some implementations, MN 601B (e.g., the CU of MN 601B) or S-SN 601A (e.g., the CU of S-SN 601A) may associate the first UE LTM security configuration (i.e., a single security configuration) for LTM candidate cells 1 to M of UE 102 or the LTM candidate configurations 1 to M for UE 102. In some implementations, S-SN 601A may indicate the LTM candidate configurations 1 to M associated with the first LTM security configuration (list) in the first RRC reconfiguration message and / or the RRC reconfiguration messages 1 to M in the LTM configuration delivery procedures 2 to M. To indicate the association, S-SN 601A may include the first UE LTM security configuration and the first security configuration ID identifying the first UE LTM security configuration in container IE 1, and include the first security configuration ID in a tuple (e.g., LTM-Candidate In IE 1 to M, based on the first security configuration ID, UE 102 identifies that LTM candidate cells 1 to M or LTM candidate configurations 1 to M of UE 102 share the same security configuration (i.e., the first UE LTM security configuration). In some implementations, S-SN 601A may include the service security configuration ID of the serving cell of S-SN 601A or associated with the serving cell in the first RRC reconfiguration message or container IE 1. In some implementations, the service security configuration ID may indicate (e.g., identify) 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 service security configuration ID (i.e., the value) may be different from the first security configuration ID (i.e., have a different value). Since the first security configuration ID is different from the service security configuration ID, UE 102 determines the security configuration change for LTM cell handover from the serving cell to cell 1 and may apply the first UE LTM security configuration to communicate with C-SN 606 via cell 1, as described above.
[0321] In the communication at event 640, UE 102 may receive a second LTM cell handover command from C-SN 606, thereby instructing UE 102 to perform an LTM cell handover to cell 2. In this case, UE 102 may perform an LTM cell handover to cell 2 in response to the second LTM cell handover command, as described above for an LTM cell handover to cell 1. Since UE 102 identifies the same security configuration (i.e., the first security configuration) as applicable to both cell 1 and cell 2 (or LTM candidate configuration 1 and LTM candidate configuration 2), UE 102 may use or continue to use the second security key to communicate with C-SN 606 on cell 2. If UE 102 uses the second security algorithm to communicate with C-SN 606 on cell 1, then UE 102 may use or continue to use the second security algorithm to communicate with C-SN 606 on cell 2. If UE 102 uses the first security algorithm to communicate with C-SN 606 on cell 1, then UE 102 can use or continue to use the first security algorithm to communicate with C-SN 606 on cell 2. Similarly, C-SN 606 can perform similar actions to communicate with UE 102, as described above. The “M” in the above description can be changed to “N”.
[0322] In some implementations, S-SN 601A may perform another inter-CU LTM preparation procedure for UE 102 with another second C-SN to obtain an LTM candidate configuration and a second UE LTM security configuration for the LTM candidate cell (e.g., a cell operated by the second C-SN) and send the LTM candidate configuration and the second UE LTM security configuration to UE 102, similar to procedures 698A and 694A. MN 601B may send a second MN-to-SN LTM security configuration to the second C-SN 606, as described for the first MN-to-SN LTM security configuration. The examples and implementations described for the first UE LTM security configuration and the first MN-to-SN LTM security configuration can be applied to the second UE LTM security configuration and the second MN-to-SN LTM security configuration, respectively. In some implementations, the second UE LTM security configuration and / or the second MN-to-SN LTM security configuration may differ from the first UE LTM security configuration and the first MN-to-SN LTM security configuration.
[0323] In some implementations, the S-SN 601A can include CSI resource configurations from 1 to N instead of tuples in the container IE, where N is an integer greater than zero.
[0324] Figure 6BThis is a sequence diagram illustrating example operations of communication procedure 600B for a second example inter-CU cell handover, where the first base station acts as the MN, the second base station as the C-SN, and the third base station as the S-SN. Communication procedure 600B is broadly similar to communication procedure 600A, except that it includes events 604B, 609B, and 611 instead of events 603 and 609A. In communication procedure 600B, MN 601B initiates inter-SN LTM preparation procedure 698B, while in communication procedure 600A, S-SN 601A initiates inter-SN LTM preparation procedure 698A.
[0325] At event 602, UE 102 under DC can communicate with MN 601B and S-SN 601A, as described above. Figure 6A As described above. In some aspects, when communicating with UE 102 under DC via MN 601B and S-SN 601A, S-SN 601A can perform CU-in-CU LTM configuration procedure 696 or CU-in-CU LTM procedure 680 with UE 102, as described above. Figure 6A As stated above.
[0326] At event 604B, when communicating with MN 601B and S-SN 601A under DC, UE 102 can, for example, send at least one measurement report to MN 601B via SRB1, similar to... Figure 3 Events 304 and / or 306 Figure 4 Events 404 and / or 406 and Figure 5 Event 504. If MN 601B is a distributed base station, then MN 601B may include a CU and a DU. The CU of MN 601B may receive measurement reports from UE 102 via the DU of MN 601B. MN 601B (e.g., the CU of MN 601B) may generate measurement configurations to configure UE 102 to send measurement reports, and may send the measurement configurations to UE 102 (e.g., via the DU of MN 601B).
[0327] After receiving one or more measurement reports from the measurement reports from UE 102 (e.g., in response to this), MN601B (e.g., the CU of MN 601B) can determine that the first cell (e.g., Figure 1A and Figure 1B Cell 124B is being prepared as an LTM candidate for UE102.
[0328] At event 605, in response to determination, MN 601B may generate 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 may send the SN request message to C-SN 606.
[0329] In response to the SN request message, CU 172 can perform LTM preparation procedure 690 with DU 174, and at event 607, it can send an SN request confirmation message to MN 601B, as described above. Figure 6A As stated above.
[0330] At event 609B, after receiving the SN request confirmation message (e.g., in response to this), MN 601B may send an SN to S-SN 601A including the first LTM candidate configuration (LTM candidate configuration 1), the LTM reference configuration, and / or the first cell ID. Modification Request The message is 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 PCI of the first cell, then MN 601B may include the LTM-related configurations in the message. SN Modification Request In the message.
[0331] At event 611, in response to the SN modification request message, S-SN 601A may send an SN modification request confirmation message to MN 601B, and may perform LTM configuration delivery procedure 694A with UE 102 to send a first LTM candidate configuration and / or LTM reference configuration to UE 102.
[0332] Events 605, 607, 609B, and 611, along with LTM preparation procedure 690, are in Figure 6B This is collectively referred to as the MN-initiated SN-interval LTM preparation process 698B.
[0333] As mentioned above Figure 6A The SN request acknowledgment message for event 607 may include PDCCH command information. If the SN request acknowledgment message includes PDCCH command information, then MN 601B may include the PDCCH command information in... SN Modification Request In the message. If SN Modification Request If the message includes PDCCH command information, then S-SN 601A can send 650A PDCCH commands to UE 102 based on the PDCCH command information, as mentioned above. Figure 6A As stated. If SN Modification RequestIf the message includes TCI status configuration, then the S-SN 601A can include the first TCI status ID in the LTM cell handover command, as mentioned above. Figure 6A As stated above.
[0334] In some implementations, MN 601B (e.g., the CU of MN 601B) may perform one or more LTM preparation procedures with CU 172 or other C-SNs to prepare additional cells (i.e., cells 2 to N) as LTM candidate cells for UE 102, and each LTM preparation procedure is similar to procedure 698B. MN 601B may perform the LTM preparation procedure before or after sending the LTM cell handover command, or during, before or after procedure 698B.
[0335] In other implementations, MN 601B may execute procedure 698B with CU 172 to accurately identify one or more cells from cell 1 and cells 2 to N as LTM candidate cells for UE 102, where N is an integer greater than 1. Cells 2 to N are identified by cell IDs 2 to N, respectively, and are operated by DU 174 and / or other DU operations of C-SN 606. In such implementations, MN 601B may include cell IDs 2 to N in SN request message 605, as described above for cell ID 1.
[0336] Figure 6B The events 624A, 650A, 652, 656, 657, 658, 654A, 636A, 638, 639, 641, 642, and 640 shown, along with processes 694A and 699, are as described above regarding... Figure 6A As stated above.
[0337] Figure 6C This is a sequence diagram illustrating example operations of communication procedure 600C for inter-cell handover of a third example CU, where the first base station acts as the MN, the second base station as the C-SN, and the third base station as the S-SN. Communication procedure 600C is generally similar to communication procedures 600A and 600B, except that communication procedure 600C may include events and procedures 694C, 636C, and 645 instead of events and procedures 694A, 636A, and 638.
[0338] In the LTM configuration delivery procedure 694C of communication procedure 600C, MN 601B may send a second service 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, for configuring the first cell as an LTM candidate cell, similar to Figure 3 Process 394 Figure 4 Process 494 or Figure 5 Procedure 594. In some implementations, MN 601B can generate the RRC reconfiguration message in procedure 694C, while S-SN 601A generates the RRC reconfiguration message in procedure 694A. In some implementations, MN 601B can assign the LTM ID in communication procedure 600C, while S-SN 601A can assign the LTM ID in communication procedures 600A and 600B.
[0339] In event 636C, when UE 102 executes LTM execution procedure 699, UE 102 can send an RRC reconfiguration message to MN 601B, similar to the above-mentioned... Figure 6A Event 636A is described. In some implementations, UE 102 may include the LTMID in the RRC reconfiguration complete message to instruct UE 102 to apply the first LTM candidate configuration.
[0340] At event 645, after receiving the RRC reconfiguration message (e.g., in response to this), MN 601B can send an SN message to S-SN 601A, as described above regarding... Figure 6A As described above. In some implementations, the MN 601B may include the first cell ID of the first cell in the SN message. The MN 601B may determine the first cell ID based on the LTM ID received in the RRC reconfiguration complete message.
[0341] In some implementations, the MN 601B (e.g., the CU of the MN 601B) can generate a first UE LTM security configuration based on a first MN-to-SN LTM security configuration, and can include the first UE LTM security configuration in the first RRC reconfiguration message of procedure 694C. In some implementations, the MN 601B can include the first UE LTM security configuration in a container IE that may include tuple 1 (e.g., LTM-Config In the IE (Internet Element), the container IE can be included in the first RRC reconfiguration message. In other implementations, the MN 601B can include the first UE LTM security configuration in tuple 1. For Figure 6A The above description of S-SN 601A can be applied to MN 601B.
[0342] Figure 6D This is a sequence diagram illustrating example operations of communication procedure 600D for inter-cell handover of a fourth example CU, where the first base station acts as the MN operation, the second base station acts as the C-SN operation, and the third base station acts as the S-SN operation. Communication procedure 600D is generally similar to communication procedures 600A, 600B, and 600C, except that communication procedure 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 MN 601B involves events 624D, 650D, 654D, and 626D, while S-SN 601A involves events 624A, 650A, 654A, and 626A. The difference between Event 627D and 627A is that in Event 627D, MN 601B can send to S-SN 601A. CU-CU cell handover notification The CU-CU cell handover notification message may include a first TCI status ID and / or a second TCI status ID.
[0343] In some implementations, MN 601B can generate a CSI report configuration based on CSI resource configuration, as described for S-SN 601A. The CSI resource configuration can be configured in the RS transmitted on the first cell. MN 601B can send the CSI report configuration to UE 102 in procedure 694C. In some implementations, MN 601B is pre-configured with CSI resource configuration. In other implementations, MN 601B can receive CSI resource configuration from the OAM node. In yet another implementation, MN 601B can receive CSI resource configuration from CU 172 or S-SN 601A.
[0344] Next, refer to Figure 7A , Figure 7B , Figure 8 , Figure 9A , Figure 9B , Figure 10A , Figure 10B , Figure 11 and Figure 12 Discussions can take place in RAN (e.g., Figures 6A to 6D Several example methods implemented in S-SN 601A, MN 601B, C-SN 606, or CU 172. For Figures 3 to 5 and Figures 6A to 6D The provided description may be applicable Figure 7A , Figure 7B , Figure 8 , Figure 9A , Figure 9B , Figure 10A , Figure 10B , Figure 11 and Figure 12 The operations of boxes marked similarly to those marked with events (e.g., 302, 402, 502, 602, etc.) are similar to each other, and therefore individual descriptions are omitted for boxes that have already been described.
[0345] Figure 7A This is a flowchart illustrating a first example operation of method 700A for configuring LTM CSI resources and LTM CSI reports for inter-CU cell handover, which can be implemented by an MN. As an example, the MN could be... Figure 1A Base station 104 Figure 1B Base station 104A or 104B, Figure 1C Base station 164 Figure 2A eNB, ng-eNB 230 or gNB 232, or Figures 6A to 6D The implementation method of MN601B.
[0346] At box 702 and as mentioned above... Figures 6A to 6D As described in Event 602, the MN communicates with the UE via the serving cell.
[0347] At box 780 and as mentioned above... Figures 6A to 6D As described in process 680, the MN may send to the UE a first LTM candidate configuration, a first LTM configuration ID identifying the first LTM candidate configuration, a first (LTM) CSI resource configuration, and / or an LTM CSI report configuration. In some aspects, the first LTM candidate configuration may configure a first cell as an LTM candidate cell. In some aspects, the first LTM CSI resource configuration may configure a first LTM CSI resource. In some aspects, the first LTM report configuration may configure a CSI report for the first LTM CSI resource.
[0348] At box 705A and as mentioned above. Figures 6A to 6D As described in event 605, the MN can send a first interface message to the first C-SN, which requests the second cell to be prepared as an LTM candidate cell for the UE and includes a first LTM configuration ID and / or a second LTM CSI resource configuration. The second LTM CSI resource configuration can configure second LTM CSI resources. The first C-SN can be... Figure 1A Base station 106 Figure 1B Base station 106A or 106B, Figure 1C Base station 164 Figure 2AeNB, ng-eNB 230 or gNB 232, or Figures 6A to 6D The implementation method of C-SN 606. In order to prepare for the LTM cell handover between subsequent SNs to the first cell, the MN can include the first configuration ID and / or the second LTM CSI resource configuration in the first interface message.
[0349] At box 707A and as mentioned above... Figures 6A to 6D As described in event 607, the MN can receive a second interface message from the first C-SN, the second interface message including a second LTM candidate configuration for the UE. The second LTM candidate configuration can configure a second cell as an LTM candidate cell and can include a second LTM CSI report configuration that configures a CSI report for the second LTM CSI resources.
[0350] At box 718A, the MN can send a first RRC message to the UE. The first RRC message may include a second LTM candidate configuration. In some implementations, the MN may include a second LTM configuration ID that identifies the second LTM candidate configuration in the first RRC message.
[0351] In some implementations, the MN can perform an inter-SN LTM configuration procedure with an attached C-SN to obtain a first LTM candidate configuration and / or a first LTM CSI report configuration (e.g., similar to procedures 698A and 698B described above). In some implementations, the first LTM CSI report configuration can be included in the first LTM candidate configuration. In other implementations, the MN can receive the first LTM candidate configuration and / or the first LTM CSI report configuration from the S-SN. The S-SN can configure the first LTM candidate configuration and / or the first LTM CSI report configuration (i.e., intra-SN LTM configuration). In some aspects, the S-SN can be... Figure 1A Base station 104 Figure 1B Base station 104A or 104B, Figure 1C Base station 164 Figure 2A eNB, ng-eNB 230 or gNB 232, or Figures 6A to 6D The implementation method of S-SN 601A.
[0352] In some implementations, the first interface message and the second interface message can be SN respectively. Request message or SN please Please confirm. Messages. In other implementations, the first interface message and the second interface message are related to the SN. Request message or SN ask confirmThe messages differ from the New Next Generation Application Protocol (NGAP) messages. For example, the first interface message and the second interface message are LTM-specific NGAP messages. In some implementations, the first interface message may include the first cell ID of the first cell and may indicate that a first configuration ID and / or a second CSI resource configuration are associated with the first cell ID. In other implementations, the first interface message may include the ID of the second C-SN. In some implementations, the first interface message may include the second cell ID of the second cell to indicate a request to prepare the second cell as an LTM candidate cell.
[0353] In some implementations, the second LTM CSI resource configuration may be the same as the first LTM CSI resource configuration. In such cases, "second LTM CSI resource configuration" can be replaced with "first LTM CSI resource configuration". In other implementations, the second LTM CSI resource configuration may be different from the first LTM CSI resource configuration. In yet another implementation, the first LTM CSI resource configuration may include the second LTM CSI resource configuration. In still another implementation, the second LTM CSI resource configuration may include the first LTM CSI resource configuration. In some implementations, MN may include at least a portion of the second LTM CSI resource configuration in the first RRC message. In some other implementations, this portion is not included in the first LTM CSI resource configuration.
[0354] In some implementations, the S-SN can send an LTM cell handover command to the UE via the serving cell, thereby instructing the UE to perform an LTM cell handover to a second cell (e.g., as described above with respect to event 626A). In some implementations, the S-SN can indicate (e.g., include) a second LTM configuration ID in the LTM cell handover command, and the UE identifies a second LTM candidate configuration based on the second LTM configuration ID. In response, the UE can access the second cell and can communicate with the first C-SN according to the second LTM candidate configuration (e.g., as described above with respect to events 632, 636A, and / or 640). After the UE successfully completes the LTM cell handover to the second cell, the S-SN is no longer the UE's S-SN, and the first C-SN can become the UE's S-SN. The UE can perform measurements on the second LTM CSI resources, obtain an L1 measurement report (e.g., a CSI report) based on the measurements, and send the L1 measurement report to the first C-SN via the second cell according to the second LTM CSI report configuration. Based on the L1 measurement report, the first C-SN can determine that an LTM cell handover to the first cell is triggered. If the first C-SN determines that an LTM cell handover to the first cell is triggered, the first C-SN can (e.g., via a second cell) send an LTM cell handover command to the UE, thereby instructing the UE to execute the LTM cell handover command to the first cell. In some implementations, the first C-SN can indicate (e.g., include) a first LTM configuration ID in the LTM cell handover command, and the UE can identify a first LTM candidate configuration based on the first LTM configuration ID. In response to the LTM cell handover command, the UE can access the first cell and communicate on the first cell according to the first LTM candidate configuration. After the UE successfully completes the LTM cell handover to the first cell, the additional C-SN becomes the UE's S-SN, and the first C-SN is no longer the UE's S-SN.
[0355] In some implementations, the MN may send a first additional interface message to the second C-SN, requesting the second C-SN to prepare a third cell as an LTM candidate cell for the UE and including a third LTM CSI resource configuration, similar to box 705A above. In response, the MN may receive a second additional interface message from the second C-SN, which includes a third LTM candidate configuration that configures the third cell as an LTM candidate cell for the UE, similar to box 707A. The third LTM candidate configuration may include a third LTM CSI report configuration that configures the CSI report for the third LTM CSI resources. In some implementations, the MN may include the third LTM candidate configuration in a first RRC message. In other implementations, the MN may send an additional RRC message to the UE that includes the third LTM candidate configuration. The MN may include a third LTM configuration ID identifying the third LTM candidate configuration in either the first RRC message or the additional RRC message.
[0356] In some implementations, the third LTM CSI resource configuration may be the same as the second LTM CSI resource configuration. In such cases, "third LTM CSI resource configuration" can be replaced with "second LTM CSI resource configuration". In other implementations, the third LTM CSI resource configuration may be different from the second LTM CSI resource configuration. In yet another implementation, the third LTM CSI resource configuration may include the second LTM CSI resource configuration. In still another implementation, the second LTM CSI resource configuration may include the third LTM CSI resource configuration. In some implementations, MN may include at least a portion of the third LTM CSI resource configuration in the first RRC message and / or the supplementary RRC message. In some implementations, this portion is not included in the first LTM CSI resource configuration and / or the second LTM CSI resource configuration. In some implementations, the first RRC message and the supplementary RRC message may be RRC reconfiguration messages.
[0357] In some implementations, the first LTM CSI resource configuration, the second LTM CSI resource configuration, and / or the third LTM CSI resource configuration can configure LTM CSI resources (e.g., SSB and / or CSI-RS) for the first cell. In some implementations, LTM CSI resources are specifically configured for LTM. In other implementations, LTM CSI resources can be configured for LTM and other 3GPP functions / features. In some implementations, the MN can receive the first LTM CSI resource configuration, the second LTM CSI resource configuration, and / or the third LTM CSI resource configuration from the S-SN.
[0358] In some implementations, the MN can obtain the fourth LTM CSI resource configuration of the second C-SN. The MN can receive the fourth LTM CSI resource configuration from the second C-SN, for example, in a second additional interface message. In some implementations, the fourth LTM CSI resource configuration can configure fourth LTM CSI resources (e.g., SSB) for the third cell. In some implementations, the fourth LTM CSI resource can be specifically configured for LTM. In other implementations, the fourth LTM CSI resource can be configured for LTM and other 3GPP functions / features. In some implementations, the MN can include the third LTM configuration ID and / or the fourth LTM CSI resource configuration in the first interface message. In such cases, the first C-SN can generate a fourth LTM CSI report configuration that configures the fourth LTM CSI resource and include the fourth LTM CSI report configuration in the second LTM candidate configuration. After the UE successfully accesses the second cell, the first C-SN becomes the UE's S-SN, and the S-SN is no longer the UE's S-SN. The UE can then perform measurements on the fourth LTM CSI resource, obtain an L1 measurement report (e.g., a CSI report) based on these measurements, and send the L1 measurement report to the first C-SN according to the fourth LTM CSI report configuration. Based on the L1 measurement report, the first C-SN can determine which triggers the UE's LTM cell handover to the third cell. In cases where the first C-SN determines that an LTM cell handover to the third cell is triggered, the first C-SN can (e.g., via the second cell) send an LTM cell handover command to the UE, thereby instructing the UE to execute the LTM cell handover command to the third cell. In some implementations, the first C-SN can indicate (e.g., include) a third LTM configuration ID in the LTM cell handover command, and the UE identifies the third LTM candidate configuration based on the third LTM configuration ID. In response to the LTM cell handover command, the UE can access the third cell and communicate with the second C-SN according to the third LTM candidate configuration. After the UE successfully completes the LTM cell handover to the third cell, the second C-SN becomes the UE's S-SN, and the first C-SN is no longer the UE's S-SN.
[0359] In other implementations, MN determines not to include the third LTM configuration ID and / or the fourth LTM CSI resource configuration in the first interface message.
[0360] Figure 7BThis is a flowchart illustrating a second example operation of method 700B, which can be implemented by an MN, for configuring LTM CSI resources and LTM CSI reports for inter-CU cell handover. Example method 700B is similar to method 700A, except that method 700B includes blocks 705B-1, 707B-1, 705B-2, 707B-2, and 718B instead of blocks 705A and 707A. As an example, the MN could be... Figure 1A Base station 104 Figure 1B Base station 104A or 104B, Figure 1C Base station 164 Figure 2A eNB, ng-eNB 230 or gNB 232, or Figures 6A to 6D The implementation method of MN 601B.
[0361] At box 705B-1 and as mentioned above... Figures 6A to 6D As described in event 605, the MN may send a first interface message to the first C-SN, which requests that the second cell be prepared as the LTM candidate cell for the UE.
[0362] At box 707B-1 and as mentioned above... Figures 6A to 6D As described in event 607, the MN receives a second interface message from the C-SN, the second interface message including a second LTM candidate configuration for the UE, wherein the second LTM candidate configuration configures the second cell as an LTM candidate cell.
[0363] At box 705B-2, the MN can send a third interface message for LTM and UE to the first C-SN. This third interface message includes a first LTM configuration ID and / or a second LTM CSI resource configuration. The second LTM CSI resource configuration can configure second LTM CSI resources.
[0364] At box 707B-2 and as mentioned above... Figures 6A to 6D As described in event 607, the MN can receive a fourth interface message from the first C-SN, the fourth interface message including an additional LTM candidate configuration for the UE. The additional LTM candidate configuration may include a second LTM CSI report configuration that configures the CSI report of the second LTM CSI resource, and the second LTM candidate configuration may be updated.
[0365] At box 718B, the MN can send a second RRC message to the UE, which includes an additional LTM candidate configuration.
[0366] In some implementations, the MN may include the second LTM configuration ID in the second RRC message to instruct the additional LTM candidate configuration to update (e.g., modify or replace) the second LTM candidate configuration. When the UE receives the second LTM configuration ID and the additional LTM candidate configuration (e.g., as a tuple), the UE identifies the second LTM candidate configuration based on the second LTM configuration ID and updates the second LTM candidate configuration using the additional LTM candidate configuration.
[0367] exist Figure 7A In this context, MN utilizes frames 705A and 707A to prepare a second cell for LTM, and to prepare subsequent inter-CU LTM from the first C-SN to the first cell of MN. Figure 7B In this implementation, MN uses frames 705B-1 and 707B-1 to prepare a second cell for LTM with the first C-SN, and uses frames 705B-2 and 707B-2 to prepare subsequent inter-CU LTM from the first C-SN to the first cell of MN. In some implementations, MN may perform actions similar to those in frames 705B-1, 707B-1, 705B-2, and 707B-2 to prepare a third cell for LTM, and may also prepare subsequent inter-CU LTM from the second C-SN to the first cell of MN.
[0368] The above text is about Figure 7A The examples and implementations described can be applied to Figure 7B .
[0369] In some implementations, the third and fourth interface messages can be either SN request messages or SN request acknowledgment messages, respectively. In other implementations, the third and fourth interface messages are new NGAP messages that differ from the SN request message or SN request acknowledgment message. For example, the third and fourth interface messages can be LTM-specific NGAP messages. In some implementations, the third interface message may include the first cell ID of the first cell and may indicate that a first configuration ID and / or a second CSI resource configuration are associated with the first cell ID. In some implementations, the third interface message does not include the second cell ID of the second cell to indicate a request to prepare the second cell as an LTM candidate cell.
[0370] In some implementations, the first and second RRC messages can be combined into a single RRC message (e.g., an RRC reconfiguration message). In other implementations, the first and second RRC messages can be separate RRC messages (e.g., an RRC reconfiguration message).
[0371] Figure 8This is a flowchart illustrating a third example operation of a method, implemented by an MN, for configuring LTM CSI resources and LTM CSI reports for inter-CU cell handover. As an example, the MN could be... Figure 1A Base station 104 Figure 1B Base station 104A or 104B, Figure 1C Base station 164 Figure 2A eNB, ng-eNB 230 or gNB 232, or Figures 6A to 6D The implementation of MN 601B. In some respects, example method 800 and... Figure 7A The method is similar to that of the 700A.
[0372] Method 800 begins at boxes 702 and 780, as mentioned above. Figure 7A These boxes are described.
[0373] At box 805 and as mentioned above... Figures 6A to 6D As described in Event 605, the MN can send an SN request message to the target SN (T-SN), which requests preparation for an SN change for the UE to the second cell and includes a first LTM configuration ID and / or a second LTM CSI resource configuration for the first cell. The second LTM CSI resource configuration can configure second LTM CSI resources for the first cell. The T-SN can be... Figure 1A Base station 106 Figure 1B Base stations 106A and 106B, Figure 1C Base station 164, or Figure 2A The implementation methods of eNB, ng-eNB 230 or gNB 232.
[0374] At box 807 and as mentioned above... Figures 6A to 6D As described in Event 607, the MN can receive an SN Request Confirmation message from the T-SN. The SN Request Confirmation message may include an RRC reconfiguration message for SN changes. The RRC reconfiguration message may configure a second cell for SN changes and may include a second LTM CSI report configuration that configures a CSI report for second LTM CSI resources.
[0375] At box 818, the MN can send an RRC reconfiguration message to the UE.
[0376] In some implementations, the SN request message may include the first cell ID of the first cell. In some implementations, the SN request message may include the second cell ID of the second cell. In some implementations, the T-SN may be the C-SN (e.g., as mentioned above regarding...). Figure 6A (Described as either the first C-SN or the second C-SN). In other implementations, the T-SN is not a C-SN.
[0377] The UE can perform an SN change to the second cell after receiving an RRC reconfiguration message. After the UE successfully performs the SN change to the second cell, the T-SN becomes the UE's S-SN, and the S-SN is no longer the UE's S-SN. After successfully performing the SN change to the second cell, the UE can perform measurements on the second LTM CSI resources, obtain an L1 measurement report (e.g., a CSI report) based on the measurements, and send the L1 measurement report to the T-SN via the second cell according to the second LTM CSI report configuration. Based on the L1 measurement report, the T-SN can determine whether to trigger an LTM cell handover to the first cell. In the case where the T-SN determines that an LTM cell handover to the first cell is triggered, the T-SN can (e.g., via the second cell) send an LTM cell handover command to the UE, thereby instructing the UE to perform an LTM cell handover to the first cell. In some implementations, the T-SN can indicate (e.g., include) a first LTM configuration ID in the LTM cell handover command, and the UE identifies a first LTM candidate configuration based on the first LTM configuration ID. In response to an LTM cell handover command, the UE can access a first cell and communicate with a first S-SN or an additional C-SN on the first cell according to a first LTM candidate configuration. After the UE successfully completes the LTM cell handover to the first cell, the S-SN or additional C-SN becomes the UE's S-SN, and the T-SN is no longer the UE's S-SN.
[0378] Among them, MN is as mentioned above. Figure 7A In the case where the fourth LTM CSI resource configuration is obtained from the third BS, the MN may include the fourth LTM CSI resource configuration in the SN request message. Alternatively or additionally, the MN may not include the fourth LTM CSI resource configuration in the SN request message.
[0379] The above text is about Figure 7A The examples and implementations described can be applied to Figure 8 .
[0380] Figure 9A This is a flowchart illustrating a first example operation of method 900A for configuring LTM CSI resources and LTM CSI reports for inter-CU cell handover, which can be implemented by a candidate secondary node (C-SN). The C-SN can be... Figure 1A Base station 106 Figure 1B Base station 106A or 106B, Figure 1C Base station 164 Figure 2A eNB, ng-eNB 230 or gNB 232, or Figures 6A to 6D The implementation of C-SN 606.
[0381] At box 905A and as mentioned above... Figures 6A to 6D As described in event 605, the first C-SN can receive a first interface message from the MN requesting that a second cell be prepared as an LTM candidate cell for the UE. The first interface message may include a first LTM configuration ID and / or a second LTM CSI resource configuration for the first cell, wherein the second LTM CSI resource configuration configures second LTM CSI resources.
[0382] At box 907A and as mentioned above... Figures 6A to 6D As described in Event 607, the first C-SN may send a second interface message to the MN, the second interface message including a second LTM candidate configuration for the UE. The second interface message may include the second LTM candidate configuration to configure a second cell as an LTM candidate cell, and may include a second LTM CSI report configuration that configures a CSI report for the second LTM CSI resources. In some implementations, the second LTM candidate configuration does not include a second LTM CSI report configuration.
[0383] The above text is about Figure 7A The examples and implementations described can be applied to Figure 9A .
[0384] Figure 9B This is a flowchart illustrating a second example operation of a method for configuring LTM CSI resources and LTM CSI reports for inter-CU cell handover, which can be implemented by a C-SN. The C-SN can be... Figure 1A Base station 106 Figure 1B Base station 106A or 106B, Figure 1C Base station 164 Figure 2A eNB, ng-eNB 230 or gNB 232, or Figures 6A to 6D The implementation of C-SN 606.
[0385] At box 905B-1 and as mentioned above... Figures 6A to 6D As described in event 605, the first C-SN can receive a first interface message from the MN. The MN can be... Figure 1A Base station 104 Figure 1B Base station 104A or 104B, Figure 1C Base station 164 Figure 2A eNB, ng-eNB 230 or gNB 232, or Figures 6A to 6D The implementation of MN 601B. The first interface message can be a request to prepare a second cell as an LTM candidate cell for the UE.
[0386] At box 907B-1 and as mentioned above... Figures 6A to 6D As described in event 607, the first C-SN may send a second interface message to the MN, the second interface message including a second LTM candidate configuration for the UE. The second LTM candidate configuration may configure a second cell as an LTM candidate cell.
[0387] At box 905B-2 and as mentioned above... Figures 6A to 6D As described in event 605, the first C-SN can receive a third interface message from the MN for configuring LTM for the UE. The third interface message may include a first LTM configuration ID and / or one or more second LTM CSI resource configurations for the first cell. The one or more second LTM CSI resource configurations can configure one or more second LTM CSI resources.
[0388] At box 907B-2 and as mentioned above... Figures 6A to 6D As described in event 607, the first C-SN may send a fourth interface message to the MN, the fourth interface message including an additional LTM candidate configuration for the UE. The additional LTM candidate configuration may include a second LTM CSI report configuration that configures the CSI report of the second LTM CSI resource and updates the second LTM candidate configuration.
[0389] The above text is about Figure 7A and Figure 7B The examples and implementations described can be applied to Figure 9B .
[0390] Figure 10A This is a flowchart illustrating a first example operation of a method 1000A for configuring LTMCSI resources and LTM CSI reports for inter-CU cell handover, which can be implemented by the central unit (CU) of a C-SN. The C-SN can be... Figure 1A Base station 106 Figure 1B Base station 106A or 106B, Figure 1C Base station 164 Figure 2A eNB, ng-eNB 230 or gNB 232, or Figures 6A to 6D The implementation of C-SN 606 is shown below. Example method 1000A is similar to method 900A described above.
[0391] Method 1000A begins with (as mentioned above) Figure 9A (Description) Box 905A. The process proceeds from box 905A to box 1008A.
[0392] At box 1008A, the CU can send a CU-DU message to the DU, which requests the DU to prepare a second cell as a candidate LTM cell for the UE. The CU-DU message may include one or more second LTM CSI resource configurations.
[0393] At box 1010A, the CU can receive a DU-to-CU message from the DU, which includes a first LTM DU configuration for the UE, wherein the first LTM DU configuration may include a second LTM CSI report configuration that configures the CSI report of the second LTM CSI resource.
[0394] At box 1007A and as mentioned above... Figures 6A to 6D As described in event 607, the CU can send a second interface message to the MN, which includes a second LTM candidate configuration for the UE. The second LTM candidate configuration can configure a second cell as an LTM candidate cell and may include a first LTM DU configuration. Box 1007A is related to the above regarding... Figure 9A The description box is similar to 907A.
[0395] The above text is about Figure 7A The examples and implementations described can be applied to Figure 10A .
[0396] In some implementations, the CU-to-DU message and the DU-to-CU message can be respectively UE Context Establishment Request Messages and UE Context Establishment Response information.
[0397] Figure 10B This is a flowchart illustrating a second example operation of a method 1000B for configuring LTMCSI resources and LTM CSI reports for inter-CU cell handover, which can be implemented by the central unit (CU) of a C-SN. The C-SN can be... Figure 1A Base station 106 Figure 1B Base station 106A or 106B, Figure 1C Base station 164 Figure 2A eNB, ng-eNB 230 or gNB 232, or Figures 6A to 6D The implementation of C-SN 606. Example method 1000B is similar to methods 1000A and 900B above, except that method 1000B includes boxes 1008B-1, 1010B-1, 1008B-2, 1010B-2 and 1007B, instead of boxes 1008A and 1010A.
[0398] Method 1000B begins with (as mentioned above) Figure 9B (Described in box 905B-1). The process proceeds from box 905B-1 to box 1008B-1.
[0399] At box 1008B-1, the CU can send a first CU to DU message to the DU, which requests the DU to prepare the second cell as the LTM candidate cell for the UE.
[0400] At box 1010B-1, the CU can receive a first DU-to-CU message from the DU, which includes a first LTM DU configuration for the UE. In some implementations, the first LTM DU configuration does not include an LTM CSI report configuration that configures the CSI report for the second LTM CSI resource.
[0401] At box 1008B-2, the CU can send a second CU-DU message for LTM to the DU, which includes a second LTM CSI resource configuration.
[0402] At box 1010B-2, the CU can receive a second DU to CU message from the DU, the second DU to CU message including a second LTM DU configuration, wherein the second LTM DU configuration includes a second LTM CSI report configuration that configures the CSI report of the second LTM CSI resource and updates the first LTM DU configuration.
[0403] At box 1007B and as mentioned above... Figures 6A to 6D As described in event 607, the CU may send a fourth interface message to the MN, which includes an additional LTM candidate configuration for the UE. The additional LTM candidate configuration may update the second LTM candidate configuration.
[0404] Boxes 1007A and 1007B are respectively related to the above. Figure 9A and Figure 9B The descriptions of boxes 907A and 907B-2 are similar. In some implementations, the first CU to DU message and the first DU to CU message can be respectively... UE Context Establishment Request Messages and UE Context Establishment Response Messages. In some implementations, the second CU to DU message and the second DU to CU message can be respectively UE Context Modification Request Messages and UE context modification response information.
[0405] The above text is about Figure 7A and Figure 7B The examples and implementations described can be applied to Figure 10B .
[0406] Figure 11 This is a flowchart illustrating an example operation of method 1100 for configuring LTM CSI resources and LTM CSI reports for inter-CU cell handover, which can be implemented by a T-SN. The T-SN can be... Figure 1A Base station 106 Figure 1B Base station 106A or 106B, Figure 1C Base station 164, or Figure 2A The implementation methods of eNB, ng-eNB 230 or gNB 232.
[0407] At box 1105, and similar to the above regarding... Figures 6A to 6D Event 605 describes a process in which the T-SN can receive an SN request message from the MN, which requests the T-SN to prepare a second cell SN for the UE. The MN can be... Figure 1A Base station 104 Figure 1B Base station 104A or 104B, Figure 1C Base station 164 Figure 2A eNB, ng-eNB 230 or gNB 232, or Figures 6A to 6D The implementation of MN 601B. The SN request may include a first LTM configuration ID and / or a second LTM CSI resource configuration for the first cell, wherein the second LTM CSI resource configuration can configure the second LTM CSI resource.
[0408] At box 1107, and similar to the above regarding... Figures 6A to 6D As described in event 607, the T-SN may send an SN request confirmation message to the MN, which includes an RRC reconfiguration message for the UE. The RRC reconfiguration message may configure the SN change to the second cell and may include a second LTMCSI report configuration that configures the CSI report for the second LTM CSI resource.
[0409] At box 1172, the T-SN can perform a random access procedure with the UE via a second cell for SN change.
[0410] At box 1174, the T-SN can receive an RRC reconfiguration complete message from the UE via the second cell or MN in response to the RRC reconfiguration message.
[0411] The above text is about Figure 7A and Figure 8 The examples and implementations described can be applied to Figure 11 .
[0412] Figure 12 This is a flowchart illustrating an example operation of method 1200 for configuring LTM CSI resources and LTMCSI reports for inter-CU cell handover, which can be implemented by a CU of a T-SN. The T-SN can be... Figure 1A Base station 106 Figure 1B Base station 106A or 106B, Figure 1CBase station 164, or Figure 2A The implementation methods of eNB, ng-eNB 230 or gNB 232.
[0413] Method 1200 begins at box 1105, as mentioned above. Figure 11 The box is described.
[0414] At box 1208, the CU can send a CU-DU message to the DU that includes the second LTM CSI resource configuration.
[0415] At box 1210, the CU can receive a DU-to-CU message including the DU configuration from the DU. The DU configuration may include a second LTM CSI report configuration that configures the CSI report for the second LTM CSI resource.
[0416] At box 1207, and similar to the above regarding... Figures 6A to 6D As described in event 607, the CU can send an SN request confirmation message to the MN. The MN can be... Figure 1A Base station 104 Figure 1B Base station 104A or 104B, Figure 1C Base station 164 Figure 2A eNB, ng-eNB 230 or gNB 232, or Figures 6A to 6D The implementation of MN 601B. The SN request confirmation message may include an RRC reconfiguration message for the UE, wherein the RRC reconfiguration message may configure the SN change of the second cell and may include DU configuration.
[0417] At box 1274, the CU can receive an RRC reconfiguration complete message from the UE via the DU or MN in response to the RRC reconfiguration message.
[0418] The above text is about Figure 7A , Figure 8 and Figure 10A The examples and implementations described can be applied to Figure 12 The above text is about Figure 3 The examples and implementations of the described service DU configurations can be applied to DU configurations.
[0419] Figure 13 This is a flowchart illustrating a first example operation of a method 1300 for wireless communication performed by a first network entity. As an example, the first network entity could be... Figure 1A Base station 104 Figure 1B Base station 104A or 104B, Figure 1C Base station 164 Figure 2A eNB, ng-eNB 230 or gNB 232, or Figures 6A to 6DThe implementation method of MN 601B.
[0420] At box 1380 and as mentioned above... Figure 7A As described in block 780, the first network entity sends a first low-layer triggered Mobility (LTM) Channel State Information (CSI) resource configuration for a first cell to a UE operating with the first network entity and the second network entity under dual connectivity. The first LTM CSI resource configuration configures one or more first LTM CSI resources associated with the first cell.
[0421] At box 1305 and as mentioned above... Figure 7A As described in block 705A, the first network entity sends a second LTM CSI resource configuration for the first cell to a third network entity. This second LTM CSI resource configuration configures one or more second LTM CSI resources associated with the first cell. As an example, the third network entity could be... Figure 1A Base station 106 Figure 1B Base station 106A or 106B, Figure 1C Base station 164, or Figure 2A The implementation methods of eNB, ng-eNB 230 or gNB 232.
[0422] Figure 14 This is a flowchart illustrating a second example operation of a method 1400 for wireless communication performed by a first network entity. As an example, the first network entity could be... Figure 1A Base station 106 Figure 1B Base station 106A or 106B, Figure 1C Base station 164 Figure 2A eNB, ng-eNB 230 or gNB 232, or Figures 6A to 6D The implementation method of MN 601B.
[0423] At box 1405-1 and as mentioned above... Figures 6A to 6D Event 605 and Figure 9A As described in block 905A, the first network entity receives a request from the second network entity to prepare the second cell as an LTM candidate cell for the UE in dual-connectivity mode in the first cell. As an example, the second network entity could be... Figure 1A Base station 104 Figure 1B Base station 104A or 104B, Figure 1C Base station 164 Figure 2A eNB, ng-eNB 230 or gNB 232, or Figures 6A to 6D The implementation method of MN601B.
[0424] At box 1405-2 and as mentioned above... Figures 6A to 6D Event 605 and Figure 9B As described in box 905B-2, the first network entity receives an LTM CSI resource configuration from the second network entity, the LTM CSI resource configuration configuring one or more LTM CSI resources associated with the first cell.
[0425] Figure 15 This is a flowchart illustrating a third example operation of a method 1500 for wireless communication performed by a first network entity. As an example, the first network entity could be... Figure 1A Base station 106 Figure 1B Base station 106A or 106B, Figure 1C Base station 164 Figure 2A eNB, ng-eNB 230 or gNB 232, or Figures 6A to 6D The implementation method of MN 601B.
[0426] At box 1505 and similar to the above. Figures 6A to 6D Event 605 and Figure 9A In box 905A, a first network entity receives a request from a second network entity to prepare for a handover of a UE from a first cell to a second cell. This request includes an LTM CSI resource configuration that configures one or more LTM CSI resources associated with the first cell. As an example, the second network entity could be... Figure 1A Base station 104 Figure 1B Base station 104A or 104B, Figure 1C Base station 164 Figure 2A eNB, ng-eNB 230 or gNB 232, or Figures 6A to 6D The implementation method of MN 601B.
[0427] At box 1507 and as mentioned above... Figures 6A to 6D As described in event 607, the first network entity sends an acknowledgment to the second network entity of the request to prepare for handover.
[0428] Figure 16 A block diagram of example UE 1602 and example network entity 1604 is shown. It should be noted that the depicted hardware configuration represents the processing and communication components of network entity 1604. Base station 1604 may be... Figure 1A Base station 104 or 106 Figure 1B Base stations 104A, 104B, 106A, 106B, Figure 1C Base station 164, or Figure 2AThe implementations of eNB, ng-eNB 230, and gNB 232 are described herein. UE 1602 may be an implementation of UE 102 as described herein. The hardware configuration depicted may omit certain components that are well understood to be frequently implemented in such electronic devices, such as displays, peripherals, power supplies, etc.
[0429] UE 1602 includes an antenna 1603A, a radio frequency front-end (RF front-end) 1603B, and radio frequency transceivers (e.g., LTE transceiver 1603D and 5G NR transceiver 1603C) for communicating with network entity 1604. The RF front-end 1603B includes one or more modems, one or more analog-to-digital converters (ADCs), one or more digital-to-analog converters (DACs), signal processors, etc., configured for the corresponding RAT (e.g., 3GPP 5G NR). Figure 16 In the example shown, the RF front-end 1603B of UE 1602 can couple or connect a 5G NR transceiver 1603C to the antenna 1603A to facilitate various types of wireless communication. The RF front-end 1603B actually operates as a physical (PHY) transceiver interface to conduct and process signaling between one or more processors 1603E and the antenna 1603A to facilitate various types of wireless communication.
[0430] The antenna 1603A of UE 1602 includes an array of multiple antennas that can be tuned to one or more frequency bands associated with a corresponding RAT. Antenna 1603A and RF front-end 1603B are tuned to and / or tunable to one or more frequency bands defined by the 3GPP 5G NR communication standard and implemented by the 5G NR transceiver 1603C. Additionally, antenna 1603A, RF front-end 1603B, and / or 5G NR transceiver 1603C can be configured to support beamforming for transmission and reception of communications with netwo...
Claims
1. A method for wireless communication performed by a first network entity (104, 104A, 601B), the method comprising: Sending (680, 696, 780, 1380) a first low-layer triggered Mobility LTM Channel State Information (CSI) resource configuration for a first cell (124A) to a User Equipment (UE) (102) operating with the first network entity and the second network entity (106, 106A, 601A) under dual connectivity, wherein the first LTM CSI resource configuration is used to configure one or more first LTM CSI resources associated with the first cell; as well as Send (605, 705A, 705B-2, 805, 1305) a second LTM CSI resource configuration for the first cell to a third network entity (106, 106A, 106B, 606). The second LTM CSI resource configuration is used to configure one or more second LTM CSI resources associated with the first cell.
2. The method of claim 1, wherein sending the second LTM CSI resource configuration includes at least one of the following: The second LTM CSI resource configuration is sent in at least one of the following: a secondary node SN add request message, an SN modify request message, or a Next Generation Application Protocol (NGAP) message; or The second LTM CSI resource configuration is sent in the request to prepare the second cell as an LTM candidate cell.
3. The method of claim 1 or 2, wherein sending the second LTM CSI resource configuration includes sending the first cell identifier ID of the first cell, and wherein the second LTM CSI resource configuration is associated with the first cell ID.
4. The method according to any one of claims 1 to 3, further comprising: Send (680, 696, 780) a first LTM CSI report configuration to the UE, the first LTM CSI report configuration being used to configure at least one first CSI report associated with the one or more first LTM CSI resources; as well as Receive (607, 707A, 707B-2, 807) a second LTM CSI report configuration from the third network entity, the second LTM CSI report configuration being used to configure at least one second CSI report associated with the one or more second LTM CSI resources.
5. The method of claim 4, wherein the configuration for receiving the second LTM CSI report includes at least one of the following: Receive the second LTM report configuration in the updated LTM candidate configuration; or The second LTM CSI report is received in at least one of the SN Add Request Confirmation or SN Modification Request Confirmation messages.
6. The method according to any one of claims 1 to 5, wherein: The first network entity includes the master node MN (601B). The second network entity includes the source-secondary node S-SN (601A), and The third network entity includes one of the following: Candidate auxiliary node C-SN (606); Base station (BS); or Target auxiliary node T-SN.
7. A method for wireless communication performed by a first network entity (106, 106A, 106B, 606), the method comprising: Receive (605, 905A, 905B-1, 1405-1) requests from the second network entities (104, 104A, 601B) to prepare the second cell as a low-layer triggered mobility LTM candidate cell for a user equipment (UE) operating in dual connectivity mode in the first cell. as well as Receive (605, 905A, 905B-2, 1405-2) LTM Channel State Information (CSI) resource configuration from the second network entity. The LTM CSI resource configuration is used to configure one or more LTM CSI resources associated with the first cell.
8. The method of claim 7, wherein receiving the LTM CSI resource configuration comprises at least one of the following: The LTM CSI resource configuration is received in at least one of the following: a secondary node SN add request message, an SN modify request message, or a next-generation application protocol NGAP message; Receive the LTM CSI resource configuration as part of the request to prepare the second cell as the LTM candidate cell; or Receive the first cell identifier ID of the first cell.
9. The method of claim 7 or 8, wherein: The first network entity includes candidate secondary nodes C-SN (606), and The second network entity includes the master node MN (601B).
10. The method of any one of claims 7 to 9, further comprising: Send the updated LTM candidate configuration (907B-2) to the second network entity.
11. The method of any one of claims 7 to 10, wherein receiving the LTM CSI resource configuration includes receiving the LTM CSI resource configuration by the central unit (CU) of the first network entity, the method further comprising: The CU sends a first CU-to-DU message to the distributed unit DU, the first CU-to-DU message including one or more of the following: The DU's request to prepare the second cell as the LTM candidate cell for the UE; or The LTM CSI resource configuration.
12. The method of claim 11, wherein the first CU to DU message includes a UE context establishment request message.
13. The method of claim 11, further comprising: The CU sends a second CU-DU message, including the LTM CSI resource configuration, to the DU.
14. The method of any one of claims 11 to 13, further comprising: The CU receives a UE context modification response message, including the LTM DU configuration, from the DU.
15. The method of any one of claims 11 to 14, further comprising: The CU receives (1010A, 1010B-2) LTMCSI report configurations associated with the one or more LTM CSI resources from the DU.
16. A method for wireless communication performed by a first network entity (106, 106A, 106B, 606), the method comprising: Receive (1105, 1505) a request from a second network entity (104, 104A, 601B) to prepare for a handover of a user equipment (UE) operating in dual connectivity mode in a first cell from the first cell to the second cell. The request includes a low-layer triggered mobility LTM channel state information (CSI) resource configuration for configuring one or more LTM CSI resources associated with the first cell. as well as Send (1107, 1507) confirmation to the second network entity for the request to prepare for the handover, the confirmation including LTM CSI report configuration associated with the one or more LTM CSI resources.
17. The method of claim 16, wherein: The first network entity includes auxiliary nodes SN (104, 104A, 104B, 601A), and The second network entity includes master nodes MN (104, 104A, 104B, 601B).
18. The method of claim 16 or 17, wherein receiving the request for preparing the handover comprises receiving the request for preparing the handover by a central unit (CU) of the first network entity, the method further comprising at least one of the following: Send a CU-DU message including the LTM CSI resource configuration to the Distributed Unit (DU); or Receive LTM CSI report configurations associated with the one or more LTM CSI resources from the DU.
19. An apparatus comprising: Communication unit; as well as A processing system configured to control the communication unit to implement any of the methods described in any one of claims 1 to 18.
