Simultaneous layer 1 / layer 2 triggered mobility in master and secondary nodes

Abstract

Disclosed herein is a system configured to receive one of a mobility configuration indication and a mobility configuration request from a secondary node (SN) control unit (CU) to determine one or more candidate primary cell (Pcell) configuration modifications. The one or more candidate Pcell configuration modifications indicate one or more modifications to at least one candidate primary secondary cell (PScell) corresponding to a Pcell change for a user equipment (UE). The system is configured to determine the one or more candidate Pcell configuration modifications based on an overlap of one or more candidate Pcells of a master node (MN) CU with at least one candidate PScell of the SN CU. The system is configured to transmit the one or more candidate Pcell configuration modifications to the SN CU for generating a PScell configuration of the at least one candidate PScell based on the one or more candidate Pcell configuration modifications for facilitating a mobility of the UE from a serving PScell to the at least one candidate PScell.

Description

Cross-references to related applications

[0001] This application claims priority to Indian Provisional Application No. 202441027458, filed on 2 April 2024, and Indian Non-Provisional Application No. 202441027458, filed on 24 August 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to Layer 1 / Layer 2 triggered mobility (LTM) occurring simultaneously in a primary node and a secondary node. Background Technology

[0003] The information disclosed in this Background section is only intended to enhance the understanding of the overall background of this disclosure and should not be construed as confirmation or in any way implying that such information constitutes prior art known to those skilled in the art.

[0004] The fifth-generation (5G) advanced technology is configured with a split architecture of gNodeB (gNB), including gNB Distributed Unit (DU), gNB Control Unit (CU) and gNB Radio Unit (RU), alternatively referred to as a cell that communicates with one or more User Equipment (UE) and provides efficient communication services to the one or more UEs.

[0005] Figure 1The illustration depicts a discrete architecture for the exemplary gNB 102 defined in the 3GPP 5G specification. gNB 102 may include one or more gNB DUs 106 and 108 associated with multiple cells 109, 110, 111, and 112. gNB-DU 106 carries the Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) layers and performs one or more operations, such as, but not limited to, scheduling. Each cell (such as, but not limited to, cell 109) may communicate with one or more UEs (e.g., but not limited to, UE 104), indicating that cell 109 acts as the serving cell for UE 104. Each gNB-DU 106, 108 may carry multiple such cells. For example, in the current 3GPP specification, a maximum of 512 cells can be carried. In addition, gNB 102 may also include gNB-CU 115, which includes a gNB-CU control plane (CP) 116 carrying the Packet Data Convergence Protocol Control (PDCP-c) and Radio Resource Control (RRC) layers, and one or more gNB user planes (UP) 118 carrying the PDCP user plane and Service Data Adaptation Protocol (SDAP) layers. gNB-CU-CP 116 can be connected to one or more gNB-DUs 106 and 108 via an F1-C interface. One or more gNB-CU-UP 118 can be connected to one or more gNB-DUs 106 and 108 via an F1-U interface, and connected to gNB-CU-CP 116 via an E1 interface.

[0006] Various mobility technologies have been defined in 5G advanced technologies, such as, but not limited to, LTM, sometimes also referred to as low-layer triggered mobility. LTM has been introduced in 3GPP specification version 18 (Rel) to provide signaling handover to UEs moving from one serving cell to another using layer 1 / layer 2 signaling.

[0007] During LTM, the UE transmits a MeasurementReport message to the serving gNB (also known as gNB). The gNB decides to use LTM and initiates LTM candidate preparation. The gNB transmits an RRCReconfiguration message to the UE, including the configuration of one or more LTM candidate target cells. The UE stores the configuration of the LTM candidate target cells(s) and transmits an RRCReconfigurationComplete message to the gNB. The UE may perform downlink (DL) synchronization and timing advance (TA) acquisition with the candidate target cells(s)(s) before receiving the LTM cell handover command. The UE performs Layer 1 (L1) measurements on the configured LTM candidate target cells(s) and transmits a low-layer measurement report to the gNB. The gNB decides to perform an LTM cell handover to the target cell and transmits a MAC control element (CE) that triggers the LTM cell handover. The UE hands over to the LTM candidate target cell configuration. If TA is unavailable, the UE performs a random access procedure toward the target cell. The UE indicates to the target cell that the LTM cell handover was successfully completed.

[0008] Because LTM is executed by gNB-DU using L1 / L2 protocols, its execution differs from Layer 3 mobility. Therefore, LTM avoids or minimizes significant modifications to higher-level configurations and / or minimizes modifications to lower-level configurations.

[0009] According to the 3GPP standard, Dual Connectivity (DC) allows a User Equipment (UE) to simultaneously connect to a first gNB-CU acting as a Primary Node (MN) and a second gNB-CU acting as a Secondary Node (SN). A gNB-DU that can be associated with the MN and provide communication services to the UE can be defined as a Primary Cell Group (MCG). An MCG may include multiple cells, including primary cells (Pcells) and multiple secondary cells (Scells). The cell the UE can connect to (of the MCG) can be called a Pcell, and the other cells can be defined as Scells. A gNB-DU that can be associated with the SN and provide communication services to the UE can be defined as a Secondary Cell Group (SCG). An SCG may include multiple cells, including primary and secondary cells (PScells) and multiple Scells. The cell the UE can connect to (of the SCG) for the DC can be defined as a PScell, and the other cells of the SCG can be defined as Scells. In a few scenarios, a UE can connect to two different gNB-DUs for the same gNB-CU for the DC. In these scenarios, the gNB-CU can act as both the MN and the SN. Improvements to technologies such as DC and LTM may be essential. Summary of the Invention

[0010] The embodiments of this disclosure address the problem of enabling a smooth and seamless transfer for a UE when a UE configured with LTM and DC moves from the serving Pcell of the MN CU to a candidate Pcell and simultaneously moves from the serving PScell ​​of the SN CU to a candidate PScell.

[0011] This document discloses a system configured to receive one of a mobility configuration indication and a mobility configuration request from a secondary node (SN) control unit (CU) to determine one or more candidate primary cell (Pcell) configuration modifications. The one or more candidate Pcell configuration modification indications one or more modifications to at least one candidate primary / secondary cell (PScell) corresponding to a Pcell change of a user equipment (UE). The system is configured to determine the one or more candidate Pcell configuration modifications based on the overlap between the one or more candidate Pcells of the primary node (MN) CU and at least one candidate PScell ​​of the SN CU. The system is also configured to transmit the one or more candidate Pcell configuration modifications to the SN CU for generating a PScell ​​configuration for the at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications, to facilitate UE mobility from the serving PScell ​​to the at least one candidate PScell.

[0012] This document also discloses a method comprising: receiving one of a mobility configuration indication and a mobility configuration request from a secondary node (SN) control unit (CU) to determine one or more candidate primary cell (Pcell) configuration modifications. The one or more candidate Pcell configuration modification indications one or more modifications to at least one candidate primary / secondary cell (PScell) corresponding to a Pcell change of a user equipment (UE). The method comprises: determining the one or more candidate Pcell configuration modifications based on the overlap between the one or more candidate Pcells of the primary node (MN) CU and at least one candidate PScell ​​of the SN CU. The method comprises: transmitting the one or more candidate Pcell configuration modifications to the SN CU for generating a PScell ​​configuration for the at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications, to facilitate UE mobility from the serving PScell ​​to the at least one candidate PScell.

[0013] This document also discloses a non-transitory computer-readable medium storing program instructions. The program instructions include: receiving one of a mobility configuration indication and a mobility configuration request from a secondary node (SN) control unit (CU) to determine one or more candidate primary cell (Pcell) configuration modifications. The one or more candidate Pcell configuration modification indications one or more modifications to at least one candidate primary / secondary cell (PScell) corresponding to a Pcell change of a user equipment (UE). The program instructions include: determining the one or more candidate Pcell configuration modifications based on the overlap between the one or more candidate Pcells of the primary node (MN) CU and at least one candidate PScell ​​of the SN CU. The program instructions include: transmitting the one or more candidate Pcell configuration modifications to the SN CU for generating a PScell ​​configuration for the at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications, to facilitate UE mobility from the serving PScell ​​to the at least one candidate PScell. Attached Figure Description

[0014] The features, aspects, and advantages of embodiments of this disclosure will be described below with reference to the accompanying drawings, wherein like reference numerals denote like elements, and wherein:

[0015] Figure 1 The diagram illustrates an exemplary architecture of gNodeB (gNB) as specified in the 3GPP standard;

[0016] Figure 2A and Figure 2B The illustration depicts the mobility of a user equipment (UE) configured with dual connectivity (DC);

[0017] Figure 3A and Figure 3B The illustration shows a schematic diagram of enabling inter-node coordination for UE mobility according to an embodiment of the present disclosure;

[0018] Figure 4 An exemplary block diagram of a master node (MN) control unit (CU) for enabling inter-node coordination for UE mobility is illustrated according to an embodiment of the present disclosure.

[0019] Figure 5 An exemplary block diagram of a secondary node (SN) CU for enabling inter-node coordination for UE mobility is illustrated according to an embodiment of the present disclosure.

[0020] Figure 6 An exemplary block diagram of an SNDU for enabling inter-node coordination for UE mobility, according to an embodiment of the present disclosure, is illustrated.

[0021] Figure 7The illustration shows an exemplary data flow diagram for enabling inter-node coordination for UE mobility according to an embodiment of the present disclosure;

[0022] Figure 8 The illustration shows an exemplary data flow diagram for enabling inter-node coordination for UE mobility according to another embodiment of the present disclosure;

[0023] Figure 9 An exemplary data flow diagram for enabling inter-node coordination for UE mobility is illustrated according to yet another embodiment of the present disclosure.

[0024] Figure 10 An exemplary flowchart of a method for enabling inter-node coordination for UE mobility, according to an embodiment of the present disclosure, is illustrated.

[0025] Figure 11 An exemplary flowchart of a method for enabling inter-node coordination for UE mobility, according to another embodiment of the present disclosure, is illustrated.

[0026] Figure 12 An exemplary flowchart of a method for enabling inter-node coordination for UE mobility, according to yet another embodiment of the present disclosure, is illustrated.

[0027] Figure 13 An exemplary flowchart illustrating a method for enabling inter-node coordination for UE mobility, according to yet another embodiment of this disclosure, is shown; and

[0028] Figure 14 An exemplary component for enabling inter-node coordination for UE mobility is illustrated according to yet another embodiment of this disclosure. Detailed Implementation

[0029] The following detailed description of exemplary embodiments is taken with reference to the accompanying drawings. This disclosure provides illustration and description, but is not intended to be exhaustive or to limit implementation to the exact forms disclosed. Modifications and variations may be derived from this disclosure or from practice of implementation. Furthermore, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, the flowcharts and operational descriptions provided below relate to at least one embodiment of this disclosure. It should be noted that other embodiments may be made that do not perfectly match the flowcharts and their descriptions. It will be understood that in other embodiments, one or more operations may be omitted, one or more operations may be added, and one or more operations may be performed (at least partially) simultaneously.

[0030] Clearly, the systems and / or methods described herein can be implemented in various forms of hardware, software, or a combination of both. The actual dedicated control hardware or software code used to implement these systems and / or methods should not limit their implementation. Therefore, this document describes the operation and behavior of the systems and / or methods without reference to any specific software code. It is understood that software and hardware can be designed based on the descriptions herein to implement these systems and / or methods.

[0031] Although specific combinations of features are stated in the claims and / or disclosed in the specification, these specific combinations are not intended to limit the disclosure of implementation. In fact, many of these features can be combined in ways not specifically stated in the claims and / or not disclosed in the specification. Even if a dependent claim is directly dependent on only one claim, this disclosure may indicate that the dependent claim is dependent on other claims in the claim set.

[0032] Unless explicitly stated otherwise, no element, action, or instruction used herein should be construed as essential or necessary. Furthermore, as used herein, the articles “a” and “one” (in other words, a noun not mentioned in a plural form) are intended to include one or more items and may be used interchangeably with “one or more”. Additionally, as used herein, the terms “having,” “having,” “containing,” “including,” “comprise,” etc., are intended to be open-ended terms. Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless explicitly stated otherwise. Moreover, expressions such as “at least one of [A] and [B],” “[A] and / or [B],” or “at least one of [A] or [B]” should be understood to include only A, only B, or both A and B.

[0033] The embodiments of this disclosure address one or more problems contemplated when a UE configured with LTM and DC moves from the serving Pcell of an MN CU to a candidate Pcell and simultaneously moves from the serving PScell ​​of an SN CU to a candidate PScell. In the embodiments, systems and methods for enabling coordination between the MN CU and the SN CU are disclosed. The system and methods enable the MN CU and the SN CU to share one or more candidate Pcell configuration modifications corresponding to the candidate PScell ​​of the UE. The SN CU may also share the one or more candidate Pcell configuration modifications with the SN-DU associated with the candidate PScell. The SN DU may generate a PScell ​​configuration based on the one or more candidate Pcell configuration modifications to perform LTM for the UE from the serving PScell ​​to the candidate PScell. In another embodiment, the SN CU may automatically detect one or more candidate Pcell changes and / or configuration modifications and request the MN CU to provide the one or more candidate Pcell configuration modifications. In another embodiment, when both the serving Pcell and the serving PScell ​​communicate with the same CU, the system and methods enable coordination between the CU acting as both the MN and the SN and the SCG DU. The CU can identify one or more candidate Pcell configuration modifications and transmit these one or more candidate Pcell configuration modifications to the SCG-DU to generate a PScell ​​configuration to perform LTM for the UE from the serving PScell ​​to the candidate PScell.

[0034] Therefore, embodiments of this disclosure enable coordination between the MN CU and the SN CU when the UE undergoes an intra-SN LTM (such as, but not limited to, an LTM PScell ​​change). Embodiments of this disclosure also enable the SCG DU to perform autonomous LTM by providing the SCG DU with one or more candidate Pcell configuration modifications corresponding to candidate PScells during the LTM preparation phase.

[0035] Figure 2A and Figure 2B The illustration depicts a user equipment (UE) configured with dual connectivity (DC).

[0036] Figure 2AThe illustration depicts a UE 104 connected to gNB-CU 202, which can act as a master node (MN), and gNB-CU 204, which can act as a slave node (SN), to implement a DC. In one embodiment, the DC can be an NR DC. In another embodiment, the DC can be any other type of DC. gNB-CU 202 may alternatively be referred to herein as MN CU 202, and gNB-CU 204 may alternatively be referred to herein as SN CU 204. Each of gNB-CU 202 and gNB-CU 204 can be similar to Figure 1 The gNB-CU 115. Furthermore, MN CU 202 can be connected to one or more gNB DUs (also referred to as one or more MN DUs 206), and SN CU 204 can be connected to one or more gNB DUs (also referred to as one or more SN DUs 208). Additionally, UE 104 can be connected to MN CU 202 via at least one MN DU of one or more MN DUs 206 (e.g., MN DU 206-1), and connected to SN CU 204 via at least one SN DU of one or more SN DUs 208 (e.g., SN DU 208-1). MN-DU 206-1 and SN DU 208-1 can be similar in design and operation. Figure 1 gNB-DU 106 or gNB-DU 108.

[0037] MN DU 206-1 may include an MCG, and SN DU 208-1 may include an SCG. For example... Figure 2A As shown, UE 104 can be connected to both Pcell 210 and PScell ​​212 simultaneously for DC use. Pcell 210 and PScell ​​212 can be similar to Figure 1 One or more of the multiple neighborhoods 109-112.

[0038] Figure 2B The illustration depicts a UE 104 connected to two different gNB-DUs for DC use within the same gNB-CU 202, as shown in another embodiment. For example, UE 104 could be connected to an MN DU 206-1 including an MCG and an SN DU 208-1 including an SCG. In this case, gNB-CU 202 can function as both MN and SN. In some embodiments, the MCG and SCG can reside within the same gNB-DU, such as gNB-DU 206-1 or gNB-DU 208-1.

[0039] The following explains one or more issues envisioned during UE 104 movement.

[0040] Rel-19 Technical Specification (TS) of the 3GPP standard specifies support for Layer 1 / Layer 2 triggered mobility (LTM) between CUs for UE 104. For example, when a DC is configured and the CU acts as the SN and the MCG remains unchanged, Rel-19 TS indicates support for inter-CU LTM. Similarly, when a DC is configured, the CU acts as the MN, and the SCG remains unchanged or is released, Rel-19 TS indicates support for inter-CU LTM for UE 104. Rel-19 also specifies that cases where LTM is configured in both the MCG and SCG can be excluded. Furthermore, during discussions at RAN#125 regarding the coexistence of LTM with other functions (such as, but not limited to, DC), an agreement was reached that there are no restrictions on configuring MCG LTM and SCG LTM, and no further enhancements to network interaction in RAN2 to better enable LTM. This agreement can indicate that LTM can be configured independently in both the MN and SN simultaneously without any further discussion within the Rel-18 working scope regarding MN-SN coordination. The following section discusses one or more problems envisioned in the implementation of the LTM described above.

[0041] Figure 3A and Figure 3B The illustration shows a schematic diagram of enabling inter-node coordination for UE mobility according to an embodiment of the present disclosure.

[0042] like Figure 3A As shown, UE 104 can use the mobile communication network to communicate for DC within the service coverage area (also referred to as coverage) of MN CU 202 and SN CU 204. The coverage of a CU can be defined as the geographical area through which UE 104 can receive communication services via one or more cells associated with that CU. The coverage arrangement of MN CU 202 and SN CU 204 is provided for illustrative purposes only and should not be construed as limiting. MN CU 202 may include one or more MN DU 206, such as, but not limited to, MN DU 206-1 and MN DU 206-2. In other embodiments, MN CU 202 may include any number of MNDUs, and is not limited to... Figure 3A The illustration.

[0043] Furthermore, SN CU 204 may include one or more SN DU 208, such as, but not limited to, SN DU 208-1 and SNDU 208-2. SN CU 204 may include any number of SN DU, and is not limited to, Figure 3AThe SN DU 208-1 and SNDU 208-2 are shown. Furthermore, in one embodiment, the size (macrocell) of one or more MN DU 206 can be larger than the size of one or more SN DU 208, for example, as shown... Figure 3A As shown. In other embodiments, the size of one or more MN DU 206 may be smaller than the size of one or more SN DU 208. Each of the one or more MN DU 206 and the one or more SNDU 208 may include multiple cells serving multiple UEs, for example... Figure 1 Multiple cells 109-111. Furthermore, the coverage of at least one SN DU 208 may overlap with the coverage of at least two MN DUs 206. As a non-limiting example, the coverage of SN DU 208-2 may overlap with the coverage of MN DU 206-1 and MNDU 206-2.

[0044] Furthermore, UE 104 may initially connect to the Pcell associated with a first MN DU in one or more MN DUs 206, and the PScell ​​associated with a first SN DU in one or more SN DUs 208 for DC use. As a non-limiting example, UE 104 may initially connect to both MN DU 206-1 and SN DU 208-1 simultaneously for DC use. In this scenario, shared resources may exist between MN CU 202 and SN CU 204, such as, but not limited to, frequency, carrier, frequency band combination, etc. The first MN DU may be configured to control the selection of one or more resources between the first MN DU and the first SN DU. The first MN DU may allocate a first set of these one or more resources to itself and allocate a second set of these one or more resources to the first SN DU. The first MN DU may configure UE 104 to communicate simultaneously with the Pcell of the first MN DU and the PScell ​​of the first SN DU based on this allocation.

[0045] The one or more resources may include one or more shared resources, such as, but not limited to, one or more frequencies, one or more frequency bands, one or more combinations of frequency bands, and one or more carriers. As a non-limiting example, consider UE 104 capable of communicating using frequency bands B1, B2, B3, B4, B5, and B6, and SN DU 208-1 may include four PS cells—C1, C2, C3, and C4. In this example, MN DU 206-1 may allocate frequency bands B4, B5, and B6 to MN DU 206-1 to configure UE 104, and allocate frequency bands B1, B2, and B3 to SN DU 208-1, including cells C1 and C2. However, MN DU 206-1 may change the allocation, allocating frequency bands B1, B2, and B3 to MN DU 206-1, and allocating frequency bands B4, B5, and B6 to SN DU 208-1. In addition, SN DU 208-1 configures frequency bands B1, B2 and B3 to UE 104 for communication with PScells C1 and C2; and configures B4, B5 and B6 for communication with PScells C3 and C4 of SN DU 208-1.

[0046] Furthermore, at step 312, UE 104 can undergo a move from the serving PScell ​​of the first SN DU to a candidate PScell ​​of the second SN DU without any change in the Pcells within the coverage area of ​​the first MN DU. A candidate PScell ​​can be defined as a PScell ​​of the second SN DU, which can act as a candidate cell for performing LTM. For example, the second SN DU could be SN DU 208-2. In this scenario, the candidate PScell ​​of the second SN DU can act as the serving PScell ​​for UE 104 after the move. In this case, the first MN DU can allocate one or more shared resources to multiple PScells (including the candidate PScell) of SN DU 208-2 to communicate with UE 104 to perform a successful LTM. In this scenario, although the PScell ​​of UE 104 changes, the Pcells remain unchanged because UE 104 remains within the coverage area of ​​the first MN DU. Therefore, in this scenario, the second SN DU can perform autonomous LTM for UE 104 based on the allocation of one or more shared resources by the first MN DU.

[0047] Subsequently, UE 104 can move further within the coverage of the second SN DU, but between the coverage of the first MN DU and the second MN DU. As a non-limiting example, UE 104 can move at step 314 from the coverage of MN DU 206-1 to the coverage of MN DU 206-2, and within the coverage of the second SN DU. In this case, while performing LTM, UE 104's Pcell can be modified from the serving Pcell of the first MN DU to a candidate Pcell of the second MN DU. Furthermore, UE 104's PScell ​​can also be modified from the serving PScell ​​to a candidate PScell ​​of the second SN DU. Therefore, the second MN DU can select one or more shared resources for the candidate Pcell to communicate with UE 104, and these resources can be different from those allocated to the serving Pcell by the first MN DU.

[0048] Therefore, one or more shared resources used for the Pcell can be modified. Consequently, since one or more shared resources used for the PScell ​​can depend on one or more shared resources allocated to the Pcell, one or more shared resources allocated to the candidate PScell ​​can also differ from those serving the PScell. As a non-limiting example, UE 104 can use B4, B5, and B6 associated with SN DU 208-2 based on the allocation of MN DU 206-1; however, MNDU 206-2 can allocate B1, B4, and B5 to SN DU 208-2 for performing LTM. However, due to the lack of coordination between the MN CU and the SN CU, the second SN DU may not be able to perform autonomous LTM for UE 104.

[0049] In some scenarios, such as Figure 3B As shown, the coverage of the first SN DU can overlap with the coverage of the second SN DU along the boundary. Furthermore, UE 104 can move from the first SN DU to the second SN DU, and correspondingly from the first MN DU to the second MN DU. For example, UE 104 can move from the coverage of SN DU 208-1 to the coverage of SN DU 208-2 at step 316. Therefore, UE 104 can also move between the coverage of MN DU 206-1 and the coverage of MN DU 206-2. In this scenario, the Pcell of UE 104 can be modified from the serving Pcell of the first MN DU to the candidate Pcell of the second MN DU, and the PScell ​​of UE 104 can also be modified from the serving PScell ​​of the first SN DU to the candidate PScell ​​of the second SN DU.

[0050] Accordingly, the second MN DU can allocate one or more shared resources to UE 104 that are different from those allocated by the first MN DU. Therefore, the allocation of one or more shared resources for Pcell and PScell ​​to UE 104 can be modified. As a non-limiting example, UE 104 can communicate with SN DU 208-2 using B4, B5, and B6 based on the allocation of MN DU 206-1; however, MN DU 206-2 can allocate B1, B4, and B5 to SN DU 208-2. However, due to the lack of coordination between the first MN CU and the first SNCU, the second SN DU may not be able to perform autonomous LTM for UE 104.

[0051] The embodiments of this disclosure address some of the problems described above. Therefore, in an embodiment, when one of the SN DUs 208 of SN CU 204 enables LTM, SN CU 204 can instruct MN CU 202. MN CU 202 can provide one or more candidate Pcell configuration modifications, indicating one or more modifications to a candidate PScell ​​corresponding to a change in the Pcell of UE 104. SN CU 204 can receive the one or more candidate Pcell configuration modifications and can transmit them to a second SN DU. The second SN DU can receive the one or more candidate Pcell configuration modifications and can prepare a candidate PScell ​​configuration based on the one or more candidate Pcell configuration modifications for performing LTM mobility of UE 104 from the serving PScell ​​to a candidate PScell. Thereafter, regardless of how the Pcell of UE 104 changes, the second SN DU can autonomously perform LTM. In another embodiment, one or more candidate Pcell configuration modifications corresponding to each Pcell of the plurality of MN DUs of MN CU 202 can be shared with adjacent gNB CUs (such as, but not limited to, SN CU 204) during the Xn setup process. This avoids any negotiation-based communication during UE mobility. A second SN DU can generate the correct candidate PScell ​​configuration based on one or more Pcell configuration modifications indicated by MN CU 202. Various embodiments of this disclosure will be described in detail below.

[0052] In one embodiment, during the Xn setup process, MN CU 202 may transmit the identifier of each Pcell among multiple Pcells in one or more MN DU 206s of MN CU 202 to SN CU 204 via an Xn parameter. The Xn setup process may include the exchange of application layer configuration data required for interoperability between any two CUs via the Xn control plane (Xn-C) interface. The Xn parameter may be, but is not limited to, "served cell information". Similarly, SN CU 204 may also transmit the identifiers of multiple PScells of one or more SN DU 208s of SN CU 204 to MN CU 204 via an Xn parameter during the Xn setup process. This identifier may also be used to generate a mapping of multiple PScells of one or more SN DU 208 PScells corresponding to each Pcell among multiple Pcells of one or more MN DU 206s.

[0053] Furthermore, UE 104 can be initially configured for a single connection and LTM with MN CU 202. Subsequently, UE 104 can measure and transmit at least Layer 3 (L3) measurement reports, which include one or more L3 measurements for one or more cells of MN CU 204. These one or more L3 measurements may include, but are not limited to, Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ). Additionally, MN CU 202 can determine the enabled DC for UE 104 based on the L3 measurement reports and can configure intra-gNB DC and / or inter-gNB DC. This DC can be an NR DC or an EN DC. An intra-gNB DC can be defined as providing DC service to UE 104 via the Pcell and PScell ​​of the same gNB CU. An inter-gNB DC can be defined as providing DC service to UE 104 via the Pcell of the first gNB CU and the PScell ​​of the second gNB CU. Intra-gNB and / or inter-gNB NR DCs may depend on the PScell ​​already selected for the DC. In the case of NR DC within gNB, the same gNB-CU can act as both MN and SN.

[0054] Furthermore, SN CU 204 may indicate LTM enable to MN CU 202 at the same time as DC is established at UE 104 or at any subsequent time while providing DC service to UE 104. SN CU 204 may transmit the LTM enable indication via the Xn parameter, also referred to herein as a mobility configuration indication. The Xn parameter may be any parameter transmitted from SN CU 204 to MN CU 202 via the Xn interface.

[0055] Furthermore, MN CU 202 can determine one or more candidate Pcell configuration modifications that may affect the configuration of at least one candidate PScell ​​of UE 104. In some embodiments, the at least one candidate PScell ​​may be a target PScell ​​for LTM. In other embodiments, the at least one candidate PScell ​​may be one or more candidate PScells for LTM that may or may not be selected as a target PScell. The one or more candidate Pcell configuration modifications may indicate one or more modifications required at a candidate PScell ​​due to a change in the Pcell of UE 104. When UE 104 moves simultaneously between one or more MN DU 206 and / or one or more SN DU 208, the Pcell and PScell ​​of UE 104 may change. MN CU 202 can determine one or more candidate Pcell configuration modifications required at the at least one candidate PScell ​​due to a change in the Pcell. For example, UE 104 may move from the Pcell of a first MN DU 206-1 to the Pcell of a second MN DU 206-2, and simultaneously move between multiple PScells of a second SN DU 208-2. In another example, UE 104 can move from the Pcell of the first MN DU 206-1 (also known as the serving Pcell) to the Pcell of the second MN DU 206-2 (also known as the candidate / target Pcell), and simultaneously move from the PScell ​​of the first SN DU 208-1 to the PScell ​​of the second SN DU 208-2. Here, the PScell ​​of the first SN DU 208-1 can be defined as the serving PScell, and the PScell ​​of the second SN DU 208-2 to which UE 104 moves can be defined as the candidate / target PScell.

[0056] The one or more candidate Pcell configuration modifications may include an indication that a first MN DU has been assigned to the first MN DU for configuring one or more shared resources for UE 104, and an indication that a first SN DU is available for configuring one or more shared resources for UE 104. One or more shared resources associated with one or more SN DU 208 of SN CU 204, corresponding to at least one candidate PScell ​​for LTM, are configured for UE 104. For example, the one or more candidate Pcell configuration modifications may indicate one or more modifications requested at at least one candidate PScell ​​of a second SN DU to determine an LTM candidate cell configuration for UE 104 to move from the coverage of the first SN DU to the coverage of the second SN DU. The one or more shared or dependent resources may include at least one of the following: one or more frequencies, one or more frequency bands, one or more frequency band combinations, or one or more carriers shared between MN CU 202 and SN CU 204. In some embodiments, the one or more candidate Pcell configuration modifications may include one or more dependent resources, which include at least one security key of the first MN DU and the second MN DU of MN CU 202.

[0057] The one or more resources may indicate one or more resources at the first MN DU and the second MN DU that can be used for the configuration of one or more Pcells. The one or more Pcells may include at least the serving Pcell of the first MN DU and the candidate / target Pcell of the second MN DU.

[0058] Furthermore, MN CU 202 can determine the one or more candidate Pcell configuration modifications and transmit them to SN CU 204. SN CU 204 can also transmit the one or more candidate Pcell configuration modifications to a second SN DU, enabling the second SN DU to perform autonomous LTM by publishing a PScell ​​configuration determined based on the correct Pcell configuration. Additionally, SN CU 204 can deduce one or more dependent resources for the at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications. For example, when a Pcell can be served by different CU-UPs, SN CU 204 can deduce a security key for the at least one candidate PScell.

[0059] In some other embodiments, when the coverage of the at least one candidate PScell ​​overlaps with the coverage of multiple candidate Pcells, the second SNDU can prepare multiple PScell ​​configurations corresponding to each of the multiple Pcells. The second SNDU can transmit the multiple PScell ​​configurations to the UE 104. Upon receiving the multiple PScell ​​configurations, the UE 104 can select an appropriate PScell ​​configuration from the multiple PScell ​​configurations based on the serving Pcell for the current time period.

[0060] In some embodiments, MN CU 202 may transmit one or more candidate Pcell configuration modifications corresponding to each of the multiple Pcells of MN CU 202 to multiple gNB-CUs of SN CU 204 that are eligible to be configured for UE 104 in the DC. MN CU 202 may transmit these one or more candidate Pcell configuration modifications during or after Xn setup using a non-UE associated message. For example, the non-UE associated message may be a Next Generation Radio Access Network (NG-RAN) node configuration update message. This non-UE associated message may imply that negotiation of the one or more shared resources is not required when configuring the DC or LTM configuration for the UE later.

[0061] The second SN DU can receive the one or more candidate Pcell configuration modifications and can generate a candidate PScell ​​configuration based on the one or more candidate Pcell configuration modifications to perform LTM for UE 104 towards the candidate PScell ​​associated with the second SN DU. In some embodiments, SN CU 204 can transmit the one or more candidate Pcell configuration modifications to two or more SN DUs that may include an SCG for UE 104. In some other embodiments, SN CU 204 or MN CU 202 can transmit the one or more candidate Pcell configuration modifications to other SN CUs that can act as potential SN CUs for UE 104.

[0062] Therefore, the solution of this disclosure provides coordination between MN CU 202 and SN CU 204, enabling smooth and seamless LTM for UE 104 simultaneously moving between the coverage of one or more MN DU 206 and one or more SN DU 208, without requiring any dynamic negotiation. Furthermore, the method and system of this disclosure enable the provision of the one or more candidate Pcell configuration modifications to the second SN DU, allowing the second SN DU to prepare candidate PScell ​​configurations based on the corresponding one or more candidate Pcell configuration modifications even when UE 104 moves (while performing LTM). This provides the second SN DU with advance information about the configurations of various candidate Pcells, enabling the second SN DU to perform autonomous LTM during the LTM execution phase without communicating with MN CU 202. Whenever SN CU 204 identifies a Pcell change based on topology information, embodiments of this disclosure also enable SN CU 204 or the candidate PScell ​​to adopt the corresponding PScell ​​configuration based on the one or more candidate Pcell configuration modifications.

[0063] In some embodiments, when MN CU 202 may be unable to provide the one or more candidate Pcell configuration modifications based on the mobility configuration indication from SN CU 204, SN CU 204 may transmit a mobility configuration request for the one or more candidate Pcell configuration modifications. MN CU 202 may be unable to provide the one or more candidate Pcell configuration modifications due to the dynamic nature of the parameters, or because MN CU 202 cannot determine the appropriate mapping between multiple Pcells and their corresponding multiple PScells, or for any other reason.

[0064] In one embodiment, SN CU 204 may employ a machine learning (ML) model to detect the mobility of UE 104 between a first MNDU and a second MNDU, and may request MN CU 202 to provide configuration modifications for the one or more candidate Pcells. SN CU 204 may identify one of the one or more candidate Pcells corresponding to the at least one candidate PScell ​​based on the served cell information of one or more MNDUs 206. Furthermore, SN CU 204 may determine the mapping between the identified one or more Pcells and the at least one candidate PScell. The ML model may predict modifications to the one or more candidate Pcells based on this mapping. Therefore, SN CU 204 may detect the mobility of UE 104 between the first Pcell or the serving Pcell of the first MNDU and the second Pcell of the second MNDU, and thus detect changes in the Pcells of UE 104. SN CU 204 may also transmit a mobility configuration request to MN CU 202. MN CU 202 may receive the mobility configuration request and further determine the configuration modifications for the one or more candidate Pcells based on the mobility configuration request. MN CU202 can transmit the one or more candidate Pcell configuration modifications to SN CU 204, and SN CU 204 can also transmit the one or more candidate Pcell configuration modifications to the second SNDU to perform LTM for UE 104.

[0065] In another embodiment, SN CU 204 may use a non-UE associated procedure (such as the Xn setup procedure or the NG RAN node configuration update procedure) to request MN CU 202 to transmit one or more candidate Pcell configuration modifications corresponding to each of the plurality of PScells.

[0066] Therefore, embodiments of this disclosure enable SN CU 204 to automatically detect the mobility of UE 104 based on the served cell information received during the Xn setup process. The method and system enable SN CU 204 to request configuration modifications for one or more candidate Pcells identified as candidate Pcells for MN CU 202.

[0067] In another embodiment, the MCG and SCG may be located within the coverage area of ​​one of the one or more MN DUs 206 and one of the one or more SN DUs 208 of the same CU 202, respectively. In this embodiment, CU 202 may act as both an MN CU and an SN CU. CU 202 may determine one or more candidate Pcell configuration modifications indicating one or more modifications requested at the at least one candidate PScell, and may transmit the one or more candidate Pcell configuration modifications to a second SN DU via an F1 interface.

[0068] In this embodiment, UE 104 may initially communicate with CU 202 via a first MN DU. UE 104 may later perform L3 measurements for DC and may transmit an L3 measurement report to CU 202. CU 202 may determine the DC configuration for UE 104. Furthermore, CU 202 may determine one or more candidate Pcell configuration modifications and may transmit these modifications to a second SN DU. Subsequently, the second SN DU may prepare a candidate cell configuration for at least one candidate PScell ​​(as associated with the second SN DU) based on the one or more candidate Pcell configuration modifications. The second SN DU may later autonomously perform LTM for UE 104 based on this candidate cell configuration.

[0069] Therefore, embodiments of this disclosure enable successful execution of LTM even when the UE 104 moves simultaneously between the first MN DU and the second MN DU of the same CU 202 and between the first SN DU and the second SN DU of the same CU 202 during LTM, without requiring any dynamic negotiation during the LTM execution phase.

[0070] Figures 4 to 6 An exemplary block diagram of one or more systems described in this disclosure is illustrated.

[0071] Figure 4 An exemplary block diagram of an MNCU 202 for enabling inter-node coordination for UE 104 mobility, according to an embodiment of the present disclosure, is illustrated.

[0072] The MN CU 202 includes at least one processor 402, an input / output (I / O) interface 404, a transceiver 406, and a memory 408. The at least one processor 402 may also include at least one modification determination module 410. The components of the MN CU 202 provided herein are not exhaustive, and the MN CU 202 may include more than... Figure 4The MN CU 202 may contain more or fewer components as described. Furthermore, two or more components may be embodied in a single component, and / or multiple sub-components may be used to configure a single component to achieve the desired functionality. Some components of the MN CU 202 may be configured using hardware elements, software elements, firmware elements, and / or combinations thereof.

[0073] In one embodiment, processor 402 may be embodied as a multi-core processor, a single-core processor, or a combination of one or more multi-core processors and one or more single-core processors. For example, processor 402 may be embodied as one or more of a variety of processing devices, such as a coprocessor, microprocessor, controller, digital signal processor (DSP), processing circuitry system with or without an accompanying DSP, or various other processing devices (including microcontroller unit (MCU), hardware accelerator, application-specific computer chip, etc.).

[0074] I / O interface 404 may include mechanisms configured to receive input from and provide output to peripheral devices. For example, I / O interface 404 may include at least one input interface and / or at least one output interface. Examples of input interfaces may include, but are not limited to, a keyboard, mouse, joystick, keypad, touchscreen, softkeys, microphone, etc. Examples of output interfaces may include, but are not limited to, user interface (UI) displays (such as light-emitting diode (LED) displays, thin-film transistor (TFT) displays, liquid crystal displays (LCDs), active-matrix organic light-emitting diode (AMOLED) displays, etc.), speakers, ringers, vibrators, etc.

[0075] In one embodiment, communication interface 406 includes a transceiver for wirelessly communicating or receiving information from SN CU 204, one or more MN DU 206, and one or more other network elements of the 5G communication architecture. This communication can be achieved through a communication network. Communication interface 406 may depend on the network functionality with which MN CU 202 communicates. For example, when communicating with SN CU 204, communication interface 406 may be an Xn interface; when communicating with one or more DU, communication interface 406 may be an F1 interface.

[0076] In operation, communication interface 406 may receive one of a mobility configuration indication and a mobility configuration request from SN CU 204 to determine one or more candidate Pcell configuration modifications. The mobility configuration indication may indicate enabling or disabling LTM for UE 104 at SN CU 204. Communication interface 406 may receive the mobility configuration indication after dual connectivity is established at UE 104 or at any subsequent time during communication with UE 104. The one or more candidate Pcell configuration modifications indicate one or more modifications to at least one candidate PScell ​​corresponding to a Pcell change for UE 104. The one or more candidate Pcell configuration modifications may include, but are not limited to, one or more shared resources or one or more dependent resources allocated to UE 104 between MN CU 202 and SN CU 204. Furthermore, communication interface 406 may transmit the one or more candidate Pcell configuration modifications to SN CU 204.

[0077] Memory 408 can be any type of storage device accessible to processor 402. For example, memory 408 may include volatile or non-volatile memory, or a combination thereof. In embodiments, memory 408 may store the one or more candidate Pcell configuration modifications after they have been determined by MN CU 202. Memory 408 may also include instructions 412 for performing one or more methods of MN CU 202 described in this disclosure. In a few embodiments, instructions 412 may cause processor 402 to perform one or more methods of MN CU 202.

[0078] The modification determination module 410 can determine the one or more candidate Pcell configuration modifications after receiving a mobility configuration indication or mobility configuration request used to determine the one or more candidate Pcell configuration modifications.

[0079] In this embodiment, MN CU 202 can function as both MN and SN, therefore MN CU 202 can be referred to as CU 202. The modification determination module 410 can determine the one or more candidate Pcell configuration modifications after detecting mobility of UE 104 between two MCG DUs and one or two SCG DUs. The communication interface 406 can transmit the one or more candidate Pcell configuration modifications to the SCG DUs, such as, but not limited to, SN DU 208-1.

[0080] Figure 5 An exemplary block diagram of an SNCU 204 for enabling inter-node coordination for UE 104 mobility, according to an embodiment of the present disclosure, is illustrated.

[0081] SN CU 204 includes at least one processor 502 communicatively coupled to an input / output (I / O) interface 504, a communication interface 506, and a memory 508. Processor 502 may include at least one mobility detection module 510 and a dependency resource derivation module 512. The components of SN CU 204 provided herein are not exhaustive, and SN CU 204 may include more than... Figure 5 The SN CU 204 may contain more or fewer components as described herein. Furthermore, two or more components may be embodied in a single component, and / or multiple sub-components may be used to configure a single component to achieve the desired functionality. Some components of the SN CU 204 may be configured using hardware elements, software elements, firmware elements, and / or combinations thereof. Additionally, the SN CU 204 may be communicatively coupled to the MN CU 202 and one or more SN DU 208s.

[0082] In one embodiment, processor 502 may be embodied as a multi-core processor, a single-core processor, or a combination of one or more multi-core processors and one or more single-core processors. For example, processor 502 may be embodied as one or more of a variety of processing devices, such as a coprocessor, microprocessor, controller, DSP, processing circuitry system with or without an accompanying DSP, or various other processing devices (including MCUs, hardware accelerators, dedicated computer chips, etc.).

[0083] I / O interface 504 may include mechanisms configured to receive input from and provide output to peripheral devices. For example, I / O interface 504 may include at least one input interface and / or at least one output interface. Examples of input interfaces may include, but are not limited to, a keyboard, mouse, joystick, keypad, touchscreen, softkeys, microphone, etc. Examples of output interfaces may include, but are not limited to, a UI display (such as an LED display, TFT display, LCD, AMOLED display, etc.), a speaker, a ringer, a vibrator, etc.

[0084] In one embodiment, communication interface 506 includes a transceiver for wirelessly communicating or receiving information from MN CU 202, one or more SN DU 208, and one or more other network elements of the 5G communication architecture. This communication can be achieved through a communication network. Communication interface 506 may depend on the network functionality with which SN CU 204 communicates. For example, when communicating with MN CU 202, communication interface 506 may be an Xn interface; when communicating with one or more SN DU 208, communication interface 506 may be an F1 interface.

[0085] In operation, communication interface 506 may transmit a mobility configuration indication to MN CU 202 after a DC is established at UE 104 or at a later time. This mobility configuration indication specifies whether mobility for the UE is enabled or disabled at SN CU 204. In an embodiment, communication interface 506 may transmit a mobility configuration request to MN CU 202 to determine one or more candidate Pcell configuration modifications. In response to the transmission of either the mobility configuration indication or the mobility configuration request, communication interface 506 may receive the one or more candidate Pcell configuration modifications. Communication interface 506 may also transmit the one or more candidate Pcell configuration modifications to a second SN DU. In addition to the one or more candidate Pcell configuration modifications, communication interface 506 may also transmit one or more dependent resources.

[0086] Memory 508 can be any type of storage device accessible to processor 502. For example, memory 508 may include volatile or non-volatile memory, or a combination thereof. In embodiments, memory 508 stores one or more packet detection rules and forwarding rules, as well as cached downlink data. Memory 508 may also include instructions 514 for performing one or more methods of SN CU 204 described in this disclosure. In some embodiments, instructions 514 may cause processor 502 to perform one or more methods of SN CU 204.

[0087] Memory 508 can be configured to store a mapping between each of the plurality of PScells in SN CU 204 and the corresponding plurality of Pcells in MN CU 202. Memory 508 can also store identifiers of the plurality of mutually mapped PScells and Pcells that require changes in MN configuration.

[0088] Mobility detection module 510 can be configured to detect the mobility of UE 104 between one or more MN DU 206. Mobility detection module 510 may include an ML model trained to detect the mobility of UE 104. This ML model may receive a mapping between multiple Pcells of MN CU 202 and multiple PScells of SN CU 204 as input, and may predict any Pcell changes based on this mapping as output. In another embodiment, mobility detection module 510 may be configured to detect the mobility of UE 104 based on served cell information received from MN CU 202 during the Xn setup process.

[0089] In some scenarios, when both MN CU 202 and SN CU 204 do not indicate one or more Pcell configuration modifications corresponding to a Pcell change, SN CU 204 may be unable to perform autonomous LTM. This could be due to the MN configuration change. In some embodiments, mobility detection module 510 may be configured to store mutually mapped identifiers of multiple PScells and multiple Pcells that require MN configuration changes. Mobility detection module 510 may retrieve this mapping and the corresponding identifiers at a later time point to request the one or more candidate Pcell configuration modifications in advance to prepare at least one candidate PScell ​​for LTM.

[0090] The dependency resource derivation module 512 can be configured to derive one or more dependency resources required by the at least one candidate PScell ​​for the LTM of UE 104. In one embodiment, the dependency resource derivation module 512 can derive the security key required for preparing the at least one candidate PScell ​​for the LTM. The dependency resource derivation module 512 can derive one or more security keys (also called SN security keys) for the at least one candidate PScell ​​based on one or more security keys (also called MN security keys) included in the configuration modification of the one or more candidate PScells. In some embodiments, each MN DU in the one or more MN DU 206 can have a unique MN security key, and therefore SN CU 204 can derive multiple SN security keys for the at least one candidate PScell. As a non-limiting example, Figure 3A and Figure 3B MN DU206-1 and MN DU 206-2 can have different MN security keys, so SN CU 204 can derive the first SN security key for cells 1 and 2 of SN DU 208-2, and derive the second SN security key for cells 3 and 4 of SN DU 208-2.

[0091] Figure 6 An exemplary block diagram of an SNDU 208 for enabling inter-node coordination for UE 104 mobility, according to an embodiment of the present disclosure, is shown.

[0092] SN DU 208 includes at least one processor 602 communicatively coupled to input / output (I / O) interface 604, communication interface 606, and memory 608. Processor 602 may include one or more components, such as, but not limited to, LTM configuration generation module 610. The components of SN DU 208 provided herein are not exhaustive, and SN DU 208 may include more than... Figure 6The SN DU 208 may contain more or fewer components as depicted. In a preferred embodiment, the SN DU 208 may include, but is not limited to, the SN DU 208-2, wherein at least one candidate PScell ​​corresponding to the UE 104 resides. Furthermore, two or more components may be embodied in a single component, and / or multiple sub-components may be used to configure a single component to achieve the desired functionality. Some components of the SN DU 208 may be configured using hardware elements, software elements, firmware elements, and / or combinations thereof. Additionally, the SN DU 208 is communicatively coupled to the MNCU 202.

[0093] In one embodiment, processor 602 may be embodied as a multi-core processor, a single-core processor, or a combination of one or more multi-core processors and one or more single-core processors. For example, processor 602 may be embodied as one or more of a variety of processing devices, such as a coprocessor, microprocessor, controller, DSP, processing circuitry system with or without an accompanying DSP, or various other processing devices, including MCUs, hardware accelerators, dedicated computer chips, etc.

[0094] I / O interface 604 may include mechanisms configured to receive input from and provide output to peripheral devices. For example, I / O interface 604 may include at least one input interface and / or at least one output interface. Examples of input interfaces may include, but are not limited to, a keyboard, mouse, joystick, keypad, touchscreen, softkeys, microphone, etc. Examples of output interfaces may include, but are not limited to, a UI display (such as an LED display, TFT display, LCD, AMOLED display, etc.), a speaker, a ringer, a vibrator, etc.

[0095] In one embodiment, communication interface 606 includes a means for wirelessly communicating information with or receiving information from MN CU 202 and one or more other network elements of the 5G system architecture. This communication can be achieved via a communication network. Communication interface 606 may depend on the network functionality with which SN DU 208 communicates. For example, when communicating with MN CU 202, communication interface 606 may be an N11 or N2 interface.

[0096] Communication interface 606 can receive at least one or more candidate Pcell configuration modifications and one or more dependent resources from SN CU 204. Communication interface 606 can also transmit LTM candidate cell configuration to the at least one candidate PScell.

[0097] Memory 608 can be any type of storage device accessible to processor 602. For example, memory 608 may include volatile or non-volatile memory, or a combination thereof. In embodiments, memory 608 stores one or more packet detection rules and forwarding rules, as well as cached downlink data. Memory 608 may also include instructions 612 for performing one or more methods of SN DU 208 described in this disclosure. In some embodiments, instructions 612 may cause processor 602 to perform one or more methods of SN DU 208.

[0098] LTM configuration generation module 610 can generate candidate PScell ​​configurations for the at least one candidate PScell ​​to perform LTM for UE 104. LTM configuration generation module 610 can generate candidate PScell ​​configurations based on one or more candidate PScell ​​configuration modifications received from SN CU 204 and the one or more dependent resources.

[0099] Figure 7 An exemplary data flow diagram for enabling inter-node coordination for UE 104 mobility is illustrated according to an embodiment of the present disclosure.

[0100] Method 700 can be described within the general context of computer-executable instructions. Typically, computer-executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions that perform specific functions or implement specific abstract data types.

[0101] The order in which method 700 is described is not intended to be construed as limiting, and any number of the described method blocks can be combined in any order to implement the method. Furthermore, individual steps can be removed from the method without departing from the spirit and scope of the subject matter described herein. Moreover, the method can be implemented in any suitable hardware, software, firmware, or a combination thereof.

[0102] Method 700 describes a sequence of steps for enabling MN CU 202 to determine the configuration modification of one or more candidate Pcells after receiving an indication from SN CU 204 that LTM has been enabled at SN CU 204.

[0103] At step 702, UE 104 may be configured with a single connection at MN CU 202 and optionally with LTM.

[0104] At step 704, UE 104 may transmit an L3 measurement report associated with one or more PS cells of SN CU 202 to MN CU 202. UE 104 may also transmit an L3 measurement report indicating a request to MN CU 202 to enable DC at UE 104.

[0105] At step 706, MN CU 202 can determine the DC configuration for UE 104 based on the L3 measurement report.

[0106] At step 708, MN CU 202 may transmit an S-node add request to one or more gNB-CUs that can act as secondary nodes to provide DC services to UE 104. In one embodiment, the one or more gNB-CUs may include, but are not limited to, SNCU 204.

[0107] At step 710, SN CU 204 may identify at least one SN DU that communicates with SN CU 204 and includes at least one candidate PScell. In one embodiment, the at least one SN DU may be a second SN DU. In a non-limiting embodiment, the at least one SN DU may be SN DU 208. SN CU 204 may transmit a UE context setting request to SN DU 208.

[0108] At step 712, in response to the UE context establishment request, SN DU 208 may transmit a UE context setting response. The UE context setting response may include a Cell Group Configuration Information (IE) element as defined in 3GPP TS 38.331. For example, the Cell Group Configuration IE may be used to configure an MCG or SCG. A cell group includes a MAC entity, a set of logical channels with associated RLC entities, and a primary cell (SpCell) and one or more secondary cells (SCells). Thereafter, MN CU 202 and SN CU 204 may provide DC services to UE 104.

[0109] At step 714, at any time after DC has been configured at UE 104, SN CU 204 may transmit a mobility configuration indication to MN CU 202. This mobility configuration indication may include, but is not limited to, an acknowledgment of the S-Node Addition request. This mobility configuration indication may indicate that SN CU 204 has enabled LTM for UE 104.

[0110] At step 716, MN CU 202 may transmit an RRC reconfiguration message to UE 104. This RRC reconfiguration message may include, but is not limited to, an SCG configuration for UE 104. In an embodiment, the SCG configuration may indicate that a DC is configured for UE 104, and indicate to UE 104 that SN CU 204 may be an SN, and that it communicates with one or more cells of SN DU 208 as one or more PScells for DC service.

[0111] At step 718, in response to the mobility configuration indication, MN CU 202 can determine the one or more candidate Pcell configuration modifications.

[0112] At step 720, MN CU 202 may transmit the one or more candidate Pcell configuration modifications to SN CU 204. In one embodiment, MN CU 202 may transmit the one or more candidate Pcell configuration modifications via an S-node modification request.

[0113] At step 722, SN CU 204 can transmit confirmation of the S-node modification request.

[0114] At step 724, SN CU 204 can deduce one or more dependent resources from the one or more candidate Pcell configuration modifications.

[0115] At step 726, SN CU 204 can transmit the one or more candidate Pcell configuration modifications and the one or more dependent resources to SN DU 208 via the F1 interface. In one embodiment, SN CU 204 can transmit the one or more candidate Pcell configuration modifications and the one or more dependent resources via a UE context modification request.

[0116] At step 728, SN DU 208 may prepare a candidate PScell ​​configuration based on one or more candidate Pcell configuration modifications and one or more dependent resources. The candidate PScell ​​configuration may be associated with at least one candidate PScell ​​of SN DU 208, from which UE 104 can move from the serving PScell ​​to that candidate PScell. The candidate PScell ​​configuration enables UE 104 to autonomously switch simultaneously from the serving Pcell to a candidate Pcell and from the serving PScell ​​to at least one candidate PScell.

[0117] At step 730, SN DU 208 may transmit a UE context modification response to SN CU 204, the response indicating that the candidate PScell ​​configuration of at least one candidate PScell ​​of SCG has been modified based on one or more candidate PScell ​​configuration modifications.

[0118] At step 732, SN CU 204 may transmit the candidate PScell ​​configuration to UE 104. In one embodiment, SNCU 204 may transmit the candidate PScell ​​configuration via signaling radio bearer 3 (SRB3) of the RRC reconfiguration message.

[0119] At step 734, SN DU 208 may communicate with UE 104 using one or more sub-steps to perform LTM for UE 104. In the first sub-step, UE 104 may transmit an L1 measurement report to SN DU 208. In the second sub-step, in response to the first sub-step, SN DU 208 may transmit a Media Access Control (MAC) control element (CE) indicating cell handover to UE 104. The MAC CE may include, but is not limited to, the cell identifier (ID), random access channel (RACH) preamble, and beam ID of at least one candidate PScell. In the third sub-step, UE 104 may request to initiate a RACH procedure with SN DU 208 to establish a connection between UE 104 and at least one candidate PScell.

[0120] At step 736, after receiving the RACH procedure initiation request from UE 104, SN DU 208 can perform an autonomous success LTM for UE 104 even if the Pcell configuration is modified.

[0121] At step 738, UE 104 may acknowledge the RRC reconfiguration message received in step 732 to SN CU 204, which indicates a successful LTM to at least one candidate PScell.

[0122] Figure 8 An exemplary data flow diagram for enabling inter-node coordination for UE 104 mobility is illustrated according to an embodiment of the present disclosure.

[0123] Method 800 can be described within the general context of computer-executable instructions. Typically, computer-executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions that perform a specific function or implement a specific abstract data type.

[0124] The order in which method 800 is described is not intended to be construed as limiting, and any number of the described method blocks can be combined in any order to implement the method. Furthermore, individual steps can be removed from the method without departing from the spirit and scope of the subject matter described herein. Moreover, the method can be implemented in any suitable hardware, software, firmware, or a combination thereof.

[0125] Method 800 describes a series of steps to enable SNCU 204 UE 104 to initiate a mobility configuration request to provide one or more candidate Pcell configuration modifications after detecting mobility of UE 104 between at least two Pcells and thus requesting modifications to one or more corresponding PScells (such as, but not limited to, at least one candidate PScell).

[0126] Steps 802-812 of method 800 are similar to steps 702-712 of method 700 described above, and therefore, for the sake of brevity of this disclosure, they are avoided from being described in the same way.

[0127] At step 814, SN CU 204 can confirm the S-node add request received from MN CU 202 at step 808.

[0128] At step 816, MN CU 202 may transmit an RRC reconfiguration message to UE 104. The RRC reconfiguration message may include, but is not limited to, SCG configuration for UE 104. In an embodiment, the SCG configuration may indicate that a DC is configured for UE 104, and indicate to UE 104 that SN CU 204 can act as an SN and communicate with one or more cells of SN DU 208 as one or more PScells for DC service.

[0129] At step 818, SN CU 204 enables LTM for UE 104 and detects the mobility of UE 104 between two Pcells based on the mapping between multiple Pcells and multiple PScells. SN CU 204 can then determine whether this mobility requires any modification in the corresponding PScell.

[0130] At step 820, SN CU 204 may transmit a mobility configuration request indication “request S-node modification” to MN CU 202, thereby triggering MN CU 202 to determine and share a request for configuration modification of one or more candidate P-cells corresponding to at least one candidate PS-cell.

[0131] At step 822, in response to the mobility configuration request, MN CU 202 may identify one or more candidate Pcell configuration modifications and transmit one or more candidate Pcell configuration modifications to SN CU 204.

[0132] Steps 824-838 of method 800 are similar to steps 724-738 of method 700 described above, and therefore, for the sake of brevity of this disclosure, they are avoided from being described in the same way.

[0133] Figure 9An exemplary data flow diagram for enabling inter-node coordination for UE 104 mobility is illustrated according to an embodiment of the present disclosure.

[0134] Method 900 can be described within the general context of computer-executable instructions. Typically, computer-executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions that perform a specific function or implement a specific abstract data type.

[0135] The order in which method 900 is described is not intended to be construed as limiting, and any number of the described method blocks can be combined in any order to implement the method. Furthermore, individual steps can be removed from the method without departing from the spirit and scope of the subject matter described herein. Moreover, the method can be implemented in any suitable hardware, software, firmware, or a combination thereof.

[0136] Method 900 can be implemented in a scenario where UE 104 moves between at least two Pcells and at least two PScells connected to the same or different gNB-DUs of the same CU 202. In one embodiment, method 900 can be implemented in a scenario similar to Figure 2B In the scenario, CU 202 can act as both MN and SN.

[0137] Steps 902-906 of method 900 are similar to steps 702-706 of method 700 described above, and therefore, for the sake of brevity of this disclosure, they are avoided from being described in the same way.

[0138] At step 908, CU 202 can detect that UE 104 is moving between at least two Pcells in MN DU 206, which may require modification of at least one candidate Pcell, and can determine one or more candidate Pcell configuration modifications. Furthermore, CU 202 can transmit a UE context setting request to SN DU 208. The UE context setting request may include one or more candidate Pcell configuration modifications.

[0139] Furthermore, steps 910-920 of method 900 are similar to steps 728-738 of method 700 described above, and therefore, for the sake of brevity of this disclosure, they are avoided from being described in the same way.

[0140] Figure 10 An exemplary flowchart of a method for implementing inter-node coordination for UE 104 mobility, according to an embodiment of the present disclosure, is illustrated.

[0141] Method 1000 can be described within the general context of computer-executable instructions. Typically, computer-executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions that perform a specific function or implement a specific abstract data type.

[0142] The order in which method 1000 is described is not intended to be construed as limiting, and any number of the described method blocks can be combined in any order to implement the method. Furthermore, individual steps can be removed from the method without departing from the spirit and scope of the subject matter described herein. Moreover, the method can be implemented in any suitable hardware, software, firmware, or a combination thereof.

[0143] At step 1002, MN CU 202 may receive one of a mobility configuration indication and a mobility configuration request from SN CU 204 to determine one or more candidate Pcell configuration modifications. The one or more candidate Pcell configuration modifications may indicate one or more modifications to at least one candidate PScell ​​corresponding to the Pcell change of UE 104.

[0144] At step 1004, MN CU 202 may determine one or more candidate Pcell configuration modifications based on the overlap between one or more candidate Pcells of MN CU 202 and at least one candidate PScell ​​of SN CU.

[0145] At step 1006, MN CU 202 may transmit one or more candidate Pcell configuration modifications to SN CU 204 to generate a PScell ​​configuration for at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications, in order to facilitate the mobility of UE 104 from the serving cell to at least one candidate PScell.

[0146] Figure 11 An exemplary flowchart of a method for implementing inter-node coordination for UE 104 mobility, according to another embodiment of the present disclosure, is illustrated.

[0147] Method 1100 can be described within the general context of computer-executable instructions. Typically, computer-executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions that perform a specific function or implement a specific abstract data type.

[0148] The order in which method 1100 is described is not intended to be construed as limiting, and any number of the described method blocks can be combined in any order to implement the method. Furthermore, individual steps can be removed from the method without departing from the spirit and scope of the subject matter described herein. Moreover, the method can be implemented in any suitable hardware, software, firmware, or a combination thereof.

[0149] At step 1102, SN CU 204 may receive one or more candidate Pcell configuration modifications from MN CU 202. The one or more candidate Pcell configuration modifications may indicate one or more modifications to at least one candidate PScell ​​corresponding to the Pcell change of UE 104.

[0150] At step 1104, SN CU 204 may transmit one or more candidate Pcell configuration modifications to at least one SN DU, such as, but not limited to, SN DU 208.

[0151] Figure 12 An exemplary flowchart of a method for implementing inter-node coordination for UE 104 mobility, according to yet another embodiment of the present disclosure, is illustrated.

[0152] Method 1200 can be described within the general context of computer-executable instructions. Typically, computer-executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions that perform a specific function or implement a specific abstract data type.

[0153] The order in which method 1200 is described is not intended to be construed as limiting, and any number of the described method blocks can be combined in any order to implement the method. Furthermore, individual steps can be removed from the method without departing from the spirit and scope of the subject matter described herein. Moreover, the method can be implemented in any suitable hardware, software, firmware, or a combination thereof.

[0154] At step 1202, SN DU 208 may receive one or more candidate Pcell configuration modifications from SN CU 204. The one or more candidate Pcell configuration modifications may indicate one or more modifications to at least one candidate PScell ​​corresponding to a Pcell change in UE 104. One or more candidate Pcell configuration modifications may be received in a UE context setting request from SN CU.

[0155] At step 1204, SN DU 208 can generate candidate PScell ​​configurations by modifying at least one or more candidate Pcell configurations.

[0156] At step 1206, SN DU 208 may perform UE 104 mobility from the serving PScell ​​to at least one candidate PScell ​​based on the candidate PScell ​​configuration.

[0157] Figure 13 An exemplary flowchart of a method for implementing inter-node coordination for UE 104 mobility, according to yet another embodiment of the present disclosure, is illustrated.

[0158] Method 1300 can be described within the general context of computer-executable instructions. Typically, computer-executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions that perform a specific function or implement a specific abstract data type.

[0159] The order in which method 1300 is described is not intended to be construed as limiting, and any number of the described method blocks can be combined in any order to implement the method. Furthermore, individual steps can be removed from the method without departing from the spirit and scope of the subject matter described herein. Moreover, the method can be implemented in any suitable hardware, software, firmware, or a combination thereof.

[0160] At step 1302, CU 202 may determine one or more candidate Pcell configuration modifications. The one or more candidate Pcell configuration modifications may indicate one or more modifications to at least one candidate PScell ​​corresponding to the Pcell change of UE 104.

[0161] At step 1304, CU 202 may transmit one or more candidate Pcell configuration modifications, such as but not limited to SN DU 208, to at least one SN DU to generate a PScell ​​configuration for at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications, in order to facilitate the mobility of UE 104 from the serving PScell ​​to at least one candidate PScell.

[0162] Figure 14 An exemplary illustration is shown of a device 1400 for implementing inter-node coordination for UE 104 mobility, according to yet another embodiment of the present disclosure.

[0163] like Figure 14 As shown, device 1400 may include, but is not limited to, processor 1410, memory 1420, storage component 1430, input component 1440, output component 1450, communication interface 1460, and bus 1470.

[0164] As used herein, processor 1410 means any type of computing circuit that may include hardware and software elements. Processor 1410 may be embodied as a multi-core processor, a single-core processor, or a combination of one or more multi-core processors and / or one or more single-core processors, a distributed processing system, etc. Processor 1410 may be a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), an application-specific integrated circuit (ASIC), or another type of processing component.

[0165] Memory 1420 includes non-transitory computer-readable media. Memory 1420 includes random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic storage, and / or optical storage) that stores information and / or instructions for use by processor 1410. Memory 1420 includes machine-readable instructions executable by processor 1410. When executed by processor 1410, these machine-readable instructions cause processor 1410 to perform one or more method steps of the embodiments described above.

[0166] Storage component 1430 stores information and / or software related to the operation and use of device 1400. For example, storage component 1430 may include hard disks (e.g., magnetic disks, optical disks, magneto-optical disks, and / or solid-state disks), optical disks (CDs), digital versatile disks (DVDs), floppy disks, cassette tapes, magnetic tapes, and / or other types of non-transitory computer-readable media, and corresponding drives.

[0167] Input component 1440 is configured to receive information, such as user input. For example, input component 1440 may include, but is not limited to, a touchscreen display, keyboard, keypad, mouse, button, switch, and / or microphone. Additionally or alternatively, input component 1440 may include sensors for sensing information (e.g., Global Positioning System (GPS), accelerometer, gyroscope, and / or actuator).

[0168] Output component 1450 is configured to provide output information from device 1400. For example, output component 1450 may be, but is not limited to, a display, a speaker, a command device to an external device, and / or one or more light-emitting diodes (LEDs).

[0169] Communication interface 1460 is an interface that provides communication connections to other devices, such as external and internal devices. The connection of communication interface 1460 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or an indirect connection via a communication network existing between device 1400 and other devices. In other words, the standard of communication interface 1460 is not limited.

[0170] Bus 1470 serves as an interconnect between the processor 1410, memory 1420, storage component 1430, input component 1440, output component 1450, and communication interface 1460 of device 1400. Bus 1470 may include wired or wireless interconnects.

[0171] Figure 14 The number and arrangement of components shown are provided as an example. In practice, device 1400 may include components with... Figure 14 The components shown are additional, fewer, different, or arranged differently compared to other components. Additionally or alternatively, a set of components (e.g., one or more components) of device 1400 may perform one or more functions described as being performed by another set of components of device 1400. Furthermore, one or more method steps described in any embodiment may be performed using multiple devices 1400 communicating with each other.

[0172] [Clause 1] In one aspect, a system is disclosed. The system is configured to receive one of a mobility configuration indication and a mobility configuration request from a secondary node (SN) control unit (CU) to determine one or more candidate primary cell (Pcell) configuration modifications. The one or more candidate Pcell configuration modification indications one or more modifications to at least one candidate primary / secondary cell (PScell) corresponding to a Pcell change of a user equipment (UE). The system is configured to determine one or more candidate Pcell configuration modifications based on the overlap between one or more candidate Pcells of the primary node (MN) CU and at least one candidate PScell ​​of the SN CU. The system is also configured to transmit one or more candidate Pcell configuration modifications to the SN CU for generating a PScell ​​configuration for at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications, to facilitate UE mobility from the serving PScell ​​to at least one candidate PScell.

[0173] [Clause 2] In one aspect, the system according to Clause 1, wherein the MN CU communicates with at least a first MN distributed unit (DU) and a second MN DU. One or more candidate Pcell configuration modifications include one or more modifications to one or more shared resources of one or more candidate Pcells compared to the serving Pcell. The Pcell change indicates the UE's mobility from the serving Pcell to the candidate Pcell. At least one candidate PScell ​​is associated with at least one SN DU of one or more SN DUs of the SN CU. The serving PScell ​​and the serving Pcell are within the service coverage of the first MN DU, and the candidate Pcell and at least one candidate PScell ​​are within the service coverage of the second MN DU.

[0174] [Clause 3] In one aspect, the system according to Clause 1 or Clause 2, wherein one or more SN DUs include one of the following: a DU including a serving cell and at least one candidate PScell; and a first DU including a serving cell and a second DU including at least one candidate PScell.

[0175] [Clause 4] In one aspect, in a system according to any of the preceding clauses, a mobility configuration indication is received when dual connectivity is established at the UE or after dual connectivity is established at the UE. The mobility configuration indication specifies whether mobility for the UE is enabled or disabled at the SN CU.

[0176] [Clause 5] In one aspect, the system according to Clause 2, wherein one or more shared resources include at least one of the following: one or more frequencies, one or more frequency bands, one or more frequency band combinations, or one or more carriers shared between the MN CU and the SN CU. One or more candidate Pcell configuration modifications also include one or more dependent resources. The one or more dependent resources include at least one security key of the first MN DU and the second MN DU of the MN CU.

[0177] [Article 6] In one aspect, the system according to any of the preceding articles is also configured to transmit one or more candidate Pcell configuration modifications to multiple CUs eligible to be configured as multiple SN CUs using non-UE associated messages. The non-UE associated message is a Next Generation Radio Access Network (NG-RAN) node configuration update message. The non-UE associated message indicates that negotiation of one or more shared resources should be avoided during a period when dual connectivity is configured at the UE and Layer 1 / Layer 2 triggered mobility is enabled.

[0178] [Clause 7] In one aspect, the system according to Clause 1, wherein the SN CU is configured to receive one or more candidate Pcell configuration modifications from the MN CU. The SN CU is configured to transmit one or more candidate Pcell configuration modifications to at least one SN DU, wherein the one or more candidate Pcell configuration modifications are transmitted to at least one SN DU in a UE context setting request.

[0179] [Clause 8] In one aspect, the system according to Clause 6 or Clause 7, wherein, in order to receive one or more candidate Pcell configuration modifications, the SN CU is further configured to detect the mobility of the UE and transmit a mobility configuration request to the MN CU to determine one or more candidate Pcell configuration modifications corresponding to at least one candidate PScell.

[0180] [Clause 9] In one aspect, the system according to Clause 8, wherein, for the purpose of detecting mobility, the SN CU is configured to identify a Pcell change corresponding to at least one candidate PScell ​​based on served cell information from at least a first MN DU and a second MN DU. Served cell information is received during the Xn setup process.

[0181] [Clause 10] In one aspect, the system according to Clause 8, wherein, for the purpose of detecting mobility, the SN CU is configured to determine a mapping between at least one candidate PScell ​​and one or more candidate Pcells. The SN CU is configured to use a machine learning model to predict configuration modifications of one or more candidate Pcells corresponding to the at least one candidate PScell, based on the mapping between the one or more candidate Pcells and the at least one candidate PScell.

[0182] [Clause 11] In one aspect, the system according to Clause 6 or Clause 7, wherein the SN CU is further configured to, in response to receiving one or more candidate Pcell configuration modifications, derive one or more dependent resources for at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications. The one or more dependent resources include at least one security key of a first MN DU and a second MN DU of the MN CU. The SN CU is also configured to transmit one or more dependent resources to at least one SN DU for generating the PScell ​​configuration.

[0183] [Clause 12] In one aspect, in a system according to any one of Clauses 7-11, wherein in response to transmitting one or more candidate Pcell configuration modifications to at least one SN DU, at least one SN DU is configured to receive one or more candidate Pcell configuration modifications from an SN CU. In a UE context setting request from the SN CU, one or more candidate Pcell configuration modifications are received. At least one SN DU is configured to generate a candidate PScell ​​configuration based at least on one or more candidate Pcell configuration modifications. At least one SN DU is also configured to perform UE mobility from a serving PScell ​​to at least one candidate PScell ​​based on the candidate PScell ​​configuration.

[0184] [Clause 13] In one aspect, in a system according to any one of Clauses 6-12, at least one SNDU is further configured to receive one or more dependent resources from an SN CU for generating a PScell ​​configuration. At least one SNDU is also configured to generate a PScell ​​configuration based on one or more candidate PScell ​​configuration modifications and one or more dependent resources.

[0185] [Article 14] In one aspect, in a system according to any one of Articles 6-12, at least one SNDU is further configured to generate a plurality of PScell ​​configurations corresponding to a plurality of candidate Pcells. At least one candidate PScell ​​overlaps with the plurality of candidate Pcells. At least one SNDU is further configured to transmit the plurality of PScell ​​configurations to the UE to facilitate the UE in selecting at least one PScell ​​configuration from the plurality of PScell ​​configurations based on the serving Pcell.

[0186] [Clause 15] In one aspect, a method is disclosed. The method includes receiving one of a mobility configuration indication and a mobility configuration request from a secondary node (SN) control unit (CU) to determine one or more candidate primary cell (Pcell) configuration modifications. The one or more candidate Pcell configuration modification indications one or more modifications to at least one candidate primary / secondary cell (PScell) corresponding to a Pcell change of a user equipment (UE). The method includes determining one or more candidate Pcell configuration modifications based on the overlap between one or more candidate Pcells of the primary node (MN) CU and at least one candidate PScell ​​of the SN CU. The method includes transmitting one or more candidate Pcell configuration modifications to the SN CU for generating a PScell ​​configuration of at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications to facilitate UE mobility from the serving PScell ​​to at least one candidate PScell.

[0187] [Clause 16] In one aspect, the method according to Clause 15, wherein the MN CU communicates with at least a first MN distributed unit (DU) and a second MN DU. One or more candidate Pcell configuration modifications include one or more modifications to one or more shared resources of one or more candidate Pcells compared to the serving Pcell. The Pcell change indicates UE mobility from the serving Pcell to the candidate Pcell. At least one candidate PScell ​​is associated with at least one SN DU of one or more SN DUs of the SN CU. The serving PScell ​​and the serving Pcell are within the service coverage of the first MN DU, and the candidate Pcell and at least one candidate PScell ​​are within the service coverage of the second MN DU.

[0188] [Clause 17] In one aspect, the method according to Clause 15 or Clause 16, wherein a mobility configuration indication is received when dual connectivity is established at the UE or after dual connectivity is established at the UE. The mobility configuration indication specifies whether mobility for the UE is enabled or disabled at the SN CU.

[0189] [Clause 18] In one aspect, the method according to Clause 16, wherein one or more shared resources include at least one of the following: one or more frequencies, one or more frequency bands, one or more frequency band combinations, or one or more carriers shared between the MN CU and the SN CU. One or more candidate Pcell configuration modifications also include one or more dependent resources. The one or more dependent resources include at least one security key of the first MN DU and the second MN DU of the MN CU.

[0190] [Clause 19] In one aspect, the method according to any of the preceding clauses further includes transmitting one or more candidate Pcell configuration modifications to multiple CUs eligible to be configured as multiple SN CUs using a non-UE associated message. The non-UE associated message is a Next Generation Radio Access Network (NG-RAN) node configuration update message. The non-UE associated message indicates that negotiation of one or more shared resources should be avoided during a period when dual connectivity is configured at the UE and Layer 1 / Layer 2 triggered mobility is enabled.

[0191] [Clause 20] In one aspect, the method according to Clause 15, wherein the method at the SN CU further includes receiving one or more candidate Pcell configuration modifications from the MN CU in response to transmitting one or more candidate Pcell configuration modifications to the SN CU. The method further includes transmitting one or more candidate Pcell configuration modifications to at least one SN DU. The one or more candidate Pcell configuration modifications are transmitted to at least one SN DU in a UE context setting request.

[0192] [Clause 21] In one aspect, the method according to Clause 20, wherein receiving one or more candidate Pcell configuration modifications includes detecting the mobility of the UE and transmitting a mobility configuration request to the MN CU to determine one or more candidate Pcell configuration modifications corresponding to at least one candidate PScell.

[0193] [Clause 22] In one aspect, the method according to Clause 21, wherein the detection includes identifying a Pcell change corresponding to at least one candidate PScell ​​based on served cell information based on at least a first MNDU and a second MNDU, wherein the served cell information is received during the Xn setting process.

[0194] [Clause 23] In one aspect, the method according to Clause 21, wherein the detection method includes determining a mapping between at least one candidate PScell ​​of the SNCU and one or more candidate Pcells. The method further includes using a machine learning model to predict configuration modifications of one or more candidate Pcells corresponding to the at least one candidate PScell, based on the mapping between the one or more candidate Pcells and the at least one candidate PScell.

[0195] [Clause 24] In one aspect, the method according to any one of Clauses 20-23 further includes, in response to receiving one or more candidate Pcell configuration modifications, deriving one or more dependent resources for at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications. The one or more dependent resources include at least one security key for a first MN DU and a second MN DU of the MN CU. The method further includes transmitting the one or more dependent resources to at least one SN DU for generating the PScell ​​configuration.

[0196] [Clause 25] In one aspect, the method according to any one of Clauses 20-24, wherein in response to transmitting one or more candidate Pcell configuration modifications to at least one SN DU, the method at the at least one SN DU further includes receiving one or more candidate Pcell configuration modifications from an SN CU. The one or more candidate Pcell configuration modifications are received in a UE context setting request from the SN CU. The method further includes generating a candidate PScell ​​configuration based at least on the one or more candidate Pcell configuration modifications. The method further includes performing UE mobility from a serving PScell ​​to at least one candidate PScell ​​based on the candidate PScell ​​configuration.

[0197] [Clause 26] In one aspect, the method according to Clause 25 further includes receiving one or more dependent resources from the SN CU for generating the PScell ​​configuration. The method also includes generating the PScell ​​configuration based on one or more candidate PScell ​​configuration modifications and the one or more dependent resources.

[0198] [Clause 27] In one aspect, the method according to Clause 25 further includes generating a plurality of PScell ​​configurations corresponding to a plurality of candidate Pcells, wherein at least one candidate PScell ​​overlaps with the plurality of candidate Pcells. The method further includes transmitting the plurality of PScell ​​configurations to the UE to facilitate the UE in selecting at least one PScell ​​configuration from the plurality of PScell ​​configurations based on the serving Pcell.

[0199] [Clause 28] In one aspect, a non-transitory computer-readable medium is disclosed, having stored thereon program instructions. The program instructions include receiving one of a mobility configuration indication and a mobility configuration request from a secondary node (SN) control unit (CU) to determine one or more candidate primary cell (Pcell) configuration modifications. The one or more candidate Pcell configuration modification indications one or more modifications to at least one candidate primary / secondary cell (PScell) corresponding to a Pcell change of a user equipment (UE). The program instructions include determining one or more candidate Pcell configuration modifications based on the overlap between one or more candidate Pcells of the primary node (MN) CU and at least one candidate PScell ​​of the SN CU. The program instructions include transmitting one or more candidate Pcell configuration modifications to the SN CU for generating a PScell ​​configuration of at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications to facilitate UE mobility from the serving PScell ​​to at least one candidate PScell.

[0200] [Clause 29] In one aspect, the non-transitory computer-readable medium according to Clause 28, wherein the MN CU communicates with at least a first MN distributed unit (DU) and a second MN DU. One or more candidate Pcell configuration modifications include one or more modifications to one or more shared resources of one or more candidate Pcells compared to the serving Pcell. The Pcell change indicates UE mobility from the serving Pcell to the candidate Pcell. At least one candidate PScell ​​is associated with at least one SN DU of one or more SN DUs of the SN CU. The serving PScell ​​and the serving Pcell are within the service coverage of the first MN DU, and the candidate Pcell and at least one candidate PScell ​​are within the service coverage of the second MN DU.

[0201] [Clause 30] In one aspect, a non-transitory computer-readable medium according to Clause 28 or 29, wherein a mobility configuration indication is received when or after dual connectivity is established at the UE. The mobility configuration indication specifies enabling or disabling mobility for the UE at the SN CU.

[0202] [Clause 31] In one aspect, a non-transitory computer-readable medium according to any of Clauses 28-30, wherein one or more shared resources include at least one of the following: one or more frequencies, one or more frequency bands, one or more frequency band combinations, or one or more carriers shared between the MN CU and the SN CU. One or more candidate Pcell configuration modifications also include one or more dependent resources. The one or more dependent resources include at least one security key of the first MN DU and the second MN DU of the MN CU.

[0203] [Clause 32] In one aspect, a non-transitory computer-readable medium according to any of Clauses 28-31, wherein the program instructions further include transmitting one or more candidate Pcell configuration modifications to a plurality of CUs eligible to be configured as a plurality of SN CUs using a non-UE associated message. The non-UE associated message is a Next Generation Radio Access Network (NG-RAN) node configuration update message. The non-UE associated message indicates that negotiation of one or more shared resources should be avoided during a period when dual connectivity is configured at the UE and Layer 1 / Layer 2 triggered mobility is performed.

[0204] [Clause 33] In one aspect, a non-transitory computer-readable medium according to any of Clauses 28-32, wherein in response to transmitting one or more candidate Pcell configuration modifications to an SN CU, the program instructions further include receiving one or more candidate Pcell configuration modifications from an MN CU. The program instructions further include transmitting one or more candidate Pcell configuration modifications to at least one SN DU. The one or more candidate Pcell configuration modifications are transmitted to at least one SN DU in a UE context setting request.

[0205] [Clause 34] In one aspect, a non-transitory computer-readable medium according to any of Clauses 28-33, wherein program instructions for receiving one or more candidate Pcell configuration modifications include detecting the mobility of the UE and transmitting a mobility configuration request to the MN CU to determine one or more candidate Pcell configuration modifications corresponding to at least one candidate PScell.

[0206] [Clause 35] In one aspect, the non-transitory computer-readable medium according to Clause 34, wherein the program instructions for detection include serving cell information based on at least a first MN DU and a second MN DU, identifying a Pcell change corresponding to at least one candidate PScell. The serving cell information is received during the Xn establishment process.

[0207] [Clause 36] In one aspect, the non-transitory computer-readable medium according to Clause 34, wherein the program instructions for detection include determining a mapping between at least one candidate PScell ​​and one or more candidate Pcells of the SN CU. The program instructions also include using a machine learning model to predict configuration modifications of one or more candidate Pcells corresponding to the at least one candidate PScell, based on the mapping between the one or more candidate Pcells and the at least one candidate PScell.

[0208] [Clause 37] In one aspect, the non-transitory computer-readable medium according to Clause 34, wherein the program instructions further include, in response to receiving one or more candidate Pcell configuration modifications, deriving one or more dependent resources for at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications. The one or more dependent resources include at least one security key for a first MN DU and a second MN DU of the MN CU. The program instructions further include transmitting one or more dependent resources to at least one SN DU for generating the PScell ​​configuration.

[0209] [Article 38] In one aspect, the non-transitory computer-readable medium according to Article 34, wherein in response to transmitting one or more candidate Pcell configuration modifications to at least one SN DU, the program instructions at at least one SN DU further include receiving one or more candidate Pcell configuration modifications from an SN CU. In a UE context setting request from the SN CU, one or more candidate Pcell configuration modifications are received. The program instructions further include generating a candidate PScell ​​configuration based at least on one or more candidate Pcell configuration modifications. The program instructions further include performing UE mobility from a serving PScell ​​to at least one candidate PScell ​​based on the candidate PScell ​​configuration.

[0210] [Clause 39] In one aspect, the non-transitory computer-readable medium according to Clause 38 further includes program instructions that include receiving one or more dependent resources from the SN CU for generating a PScell ​​configuration. The program instructions also include generating the PScell ​​configuration based on one or more candidate PScell ​​configuration modifications and one or more dependent resources.

[0211] [Clause 40] In one aspect, the non-transitory computer-readable medium according to Clause 38 further includes program instructions that generate a plurality of PScell ​​configurations corresponding to a plurality of candidate Pcells, wherein at least one candidate PScell ​​overlaps with the plurality of candidate Pcells. The program instructions also include transmitting the plurality of PScell ​​configurations to the UE to facilitate the UE in selecting at least one PScell ​​configuration from the plurality of PScell ​​configurations based on the serving Pcell.

[0212] [Clause 41] In one aspect, a system is disclosed. The system is configured to determine one or more candidate primary cell (Pcell) configuration modifications based on the overlap between one or more candidate Pcells of a first primary node (MN) distributed unit (DU) of a control unit (CU) and at least one candidate PScell ​​of at least one secondary node (SN) DU of that CU, and based on Pcell changes. The one or more candidate Pcell configuration modifications indicate one or more modifications to at least one candidate primary / secondary cell (PScell) corresponding to a Pcell change of a user equipment (UE). The system is configured to transmit one or more candidate Pcell configuration modifications to at least one SN DU for generating a PScell ​​configuration for at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications, to facilitate UE mobility from the serving PScell ​​to at least one candidate PScell.

[0213] [Clause 42] In one aspect, in the system according to Clause 41, a modification to the configuration of one or more candidate Pcells includes one or more modifications to one or more shared resources of the one or more candidate Pcells compared to the serving Pcell. The Pcell change indicates the UE's mobility from the serving Pcell to the candidate Pcell. At least one candidate PScell ​​is associated with at least one of one or more SN DUs. The serving PScell ​​and the serving Pcell are within the service coverage of a first MN DU, and the candidate Pcell and at least one candidate PScell ​​are within the service coverage of a second MN DU. The one or more SN DUs include one of the following: a DU including the serving cell and at least one candidate PScell; and a first DU including the serving cell and a second DU including at least one candidate PScell.

[0214] [Clause 43] In one aspect, in the system described in Clause 41 or Clause 42, one or more shared resources include at least one of the following: one or more frequencies, one or more frequency bands, one or more frequency band combinations, or one or more carriers shared between the MN DU and SN DU. The one or more candidate Pcell configuration modifications also include one or more dependent resources. The one or more dependent resources include at least one security key for the first MN DU and the second MN DU. The one or more candidate Pcell configuration modifications are transmitted to at least one SN DU in a UE context setting request.

[0215] [Clause 44] In one aspect, a method is disclosed. The method includes determining one or more candidate primary cell (Pcell) configuration modifications based on the overlap of one or more candidate Pcells of a first primary node (MN) distributed unit (DU) of a control unit (CU) with at least one candidate PScell ​​of at least one secondary node (SN) DU of the CU, and based on a Pcell change. The one or more candidate Pcell configuration modifications indicate one or more modifications to at least one candidate primary / secondary cell (PScell) corresponding to a Pcell change of a user equipment (UE). The method includes transmitting one or more candidate Pcell configuration modifications to at least one SN DU for generating a PScell ​​configuration of at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications, to facilitate UE mobility from the serving PScell ​​to at least one candidate PScell.

[0216] [Clause 45] In one aspect, the method according to Clause 44, wherein the modification of one or more candidate Pcell configurations includes one or more modifications to one or more shared resources of one or more candidate Pcells compared to the serving Pcell. The Pcell change indicates UE mobility from the serving Pcell to the candidate Pcell. At least one candidate PScell ​​is associated with at least one of one or more SN DUs. The serving PScell ​​and the serving Pcell are within the service coverage of a first MN DU, and the candidate Pcell and at least one candidate PScell ​​are within the service coverage of a second MN DU. The one or more SN DUs include one of the following: a DU including the serving cell and at least one candidate PScell; and a first DU including the serving cell and a second DU including at least one candidate PScell.

[0217] [Clause 46] In one aspect, the method according to Clause 44 or Clause 45, wherein one or more shared resources include at least one of the following: one or more frequencies, one or more frequency bands, one or more frequency band combinations, or one or more carriers shared between the MN DU and the SN DU. The one or more candidate Pcell configuration modifications also include one or more dependent resources. The one or more dependent resources include at least one security key for the first MN DU and the second MN DU. The one or more candidate Pcell configuration modifications are transmitted to at least one SN DU in a UE context setting request.

[0218] [Clause 47] In one aspect, a non-transitory computer-readable medium is disclosed, having stored thereon program instructions. The program instructions include determining one or more candidate primary cell (Pcell) configuration modifications based on the overlap of one or more candidate Pcells of a first primary node (MN) distributed unit (DU) of a control unit (CU) with at least one candidate PScell ​​of at least one secondary node (SN) DU of the CU, and based on Pcell changes. The one or more candidate Pcell configuration modifications indicate one or more modifications to at least one candidate primary / secondary cell (PScell) corresponding to a Pcell change of a user equipment (UE). The program instructions include transmitting one or more candidate Pcell configuration modifications to at least one SN DU for generating a PScell ​​configuration of at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications, for facilitating UE mobility from the serving PScell ​​to at least one candidate PScell.

[0219] [Clause 48] In one aspect, a non-transitory computer-readable medium according to Clause 47, wherein a modification to the configuration of one or more candidate Pcells includes one or more modifications to one or more shared resources of one or more candidate Pcells compared to the serving Pcell. The Pcell change indicates UE mobility from the serving Pcell to the candidate Pcell. At least one candidate PScell ​​is associated with at least one of one or more SN DUs. The serving PScell ​​and the serving Pcell are within the service coverage of a first MN DU, and the candidate Pcell and at least one candidate PScell ​​are within the service coverage of a second MN DU. The one or more SN DUs include one of the following: a DU including the serving cell and at least one candidate PScell; and a first DU including the serving cell and a second DU including at least one candidate PScell.

[0220] [Clause 49] In one aspect, the non-transitory computer-readable medium according to Clause 47 or Clause 48, wherein one or more shared resources include at least one of the following: one or more frequencies, one or more frequency bands, one or more frequency band combinations, or one or more carriers shared between the MN DU and SN DU. The one or more candidate Pcell configuration modifications also include one or more dependent resources. The one or more dependent resources include at least one security key for the first MN DU and the second MN DU. The one or more candidate Pcell configuration modifications are transmitted to at least one SN DU in a UE context setting request.

[0221] The steps illustrated are provided to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological developments will change the way particular functions are performed. These examples are presented herein for illustrative purposes and not for limitation. Furthermore, the boundaries of the functional building blocks are arbitrarily defined herein for the sake of description. Based on the teachings contained herein, alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to those skilled in the art. Such alternatives fall within the scope of the disclosed embodiments.

[0222] Furthermore, the words “comprising,” “having,” “including,” and “including,” as well as other similar forms, are intended to be semantically equivalent and open-ended, as one or more items following any of these words do not imply an exhaustive list of such items, nor do they imply limitation to the listed items. It must also be noted that, as used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural references unless the context explicitly specifies otherwise. Finally, the language used in the specification has been chosen primarily for readability and guidance purposes and may not have been chosen to depict or define the subject matter of the invention. Therefore, the disclosure of embodiments is intended to illustrate, not limit, the scope of this disclosure. Regarding the use of substantially any plural and / or singular terms herein, those skilled in the art may appropriately convert from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, various singular / plural permutations may be explicitly described herein.

[0223] Figure label:

Claims

1. A system configured as follows: Receive one of a mobility configuration indication and a mobility configuration request from a secondary node (SN) control unit (CU) to determine one or more candidate primary cell (Pcell) configuration modifications, wherein the one or more candidate Pcell configuration modification indications one or more modifications to at least one candidate primary / secondary cell (PScell) corresponding to a Pcell change of a user equipment (UE); Based on the overlap between one or more candidate Pcells of the master node (MN) CU and at least one candidate PScell ​​of the SN CU, the configuration modification of the one or more candidate Pcells is determined; as well as The one or more candidate Pcell configuration modifications are transmitted to the SN CU to generate the PScell ​​configuration of the at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications, so as to facilitate the mobility of the UE from the serving PScell ​​to the at least one candidate PScell.

2. The system of claim 1, wherein the MN CU communicates with at least the first MN distributed unit (DU) and the second MN DU. The configuration modifications to the one or more candidate Pcells include one or more modifications to one or more shared resources of the one or more candidate Pcells compared to the service Pcell. The Pcell change indicates the mobility of the UE from the serving Pcell to the candidate Pcell. The at least one candidate PScell ​​is associated with at least one SN DU of one or more SN DUs of the SN CU, and The service PScell ​​and the service Pcell are within the service coverage of the first MN DU, and the candidate Pcell and the at least one candidate PScell ​​are within the service coverage of the second MN DU.

3. The system of claim 2, wherein the one or more SN DUs comprise one of the following: The DU includes the service PScell ​​and the at least one candidate PScell; and The first DU includes the service PScell ​​and the second DU includes the at least one candidate PScell.

4. The system of claim 1, wherein the mobility configuration indication is received when a dual connection is established at the UE or after the dual connection is established at the UE, wherein the mobility configuration indication indicates enabling or disabling the mobility for the UE at the SN CU.

5. The system according to claim 2, The one or more shared resources include at least one of the following: one or more frequencies, one or more frequency bands, one or more frequency band combinations, one or more carriers shared between the MN CU and the SN CU. The one or more candidate Pcell configuration modifications also include one or more dependent resources, wherein the one or more dependent resources include at least one security key of the first MN DU and the second MN DU of the MN CU.

6. The system of claim 1, wherein the processor is further configured to: The one or more candidate Pcell configuration modifications are transmitted to multiple CUs that are eligible to be configured as multiple SN CUs using non-UE associated messages, wherein the non-UE associated messages are next-generation radio access network (NG-RAN) node configuration update messages, and wherein the non-UE associated messages indicate that negotiation of one or more shared resources should be avoided during one of dual connectivity and Layer 1 / Layer 2 triggered mobility configuration at the UE.

7. The system of claim 1, wherein the SN CU is further configured to: Receive the one or more candidate Pcell configuration modifications from the MN CU; and The one or more candidate Pcell configuration modifications are transmitted to the at least one SNDU, wherein the one or more candidate Pcell configuration modifications are transmitted to the at least one SNDU in the UE context setting request.

8. The system of claim 7, wherein, in order to receive the one or more candidate Pcell configuration modifications, the SN CU is further configured to: Detecting the mobility of the UE; and The mobility configuration request is transmitted to the MN CU to determine the configuration modification of one or more candidate Pcells corresponding to the at least one candidate PScell.

9. The system of claim 8, wherein, in order to detect the mobility, the SN CU is configured to: Based on the served cell information of at least the first MN DU and the second MN DU, the P cell change corresponding to the at least one candidate PScell ​​is identified, wherein the served cell information is received during the Xn setting process.

10. The system of claim 8, wherein, in order to detect the mobility, the SN CU is configured to: Determine the mapping between the at least one candidate PScell ​​and the one or more candidate Pcells of the SN CU; and Using a machine learning model, based on the mapping between the one or more candidate Pcells and the at least one candidate PScell, the configuration modification of the one or more candidate Pcells corresponding to the at least one candidate PScell ​​is predicted.

11. The system of claim 7, wherein the SN CU is further configured to: In response to receiving the one or more candidate Pcell configuration modifications, based on the one or more candidate Pcell configuration modifications, one or more dependent resources for the at least one candidate PScell ​​are derived, wherein the one or more dependent resources for the at least one candidate PScell ​​include at least one security key; and The one or more dependent resources are transferred to the at least one SN DU for generating the PScell ​​configuration.

12. The system of claim 7, wherein in response to transmitting the one or more candidate Pcell configuration modifications to the at least one SNDU, the at least one SNDU is configured to: The one or more candidate Pcell configuration modifications are received from the SN CU, wherein the one or more candidate Pcell configuration modifications are received in the UE context setting request from the SN CU; The candidate PScell ​​configuration is generated based on at least one or more candidate Pcell configuration modifications. as well as Based on the candidate PScell ​​configuration, the UE performs the mobility from the serving PScell ​​to the at least one candidate PScell.

13. The system of claim 12, wherein the at least one SN DU is further configured to: Receive one or more dependent resources from the SN CU for generating the PScell ​​configuration; and The PScell ​​configuration is generated based on the one or more candidate Pcell configuration modifications and the one or more dependent resources.

14. The system of claim 12, wherein the at least one SN DU is further configured to: Generate multiple PScell ​​configurations corresponding to multiple candidate Pcells, wherein at least one candidate PScell ​​overlaps with the multiple candidate Pcells; and The plurality of PScell ​​configurations are transmitted to the UE to facilitate the UE in selecting at least one of the plurality of PScell ​​configurations based on the serving Pcell.

15. A method comprising: Receive one of a mobility configuration indication and a mobility configuration request from a secondary node (SN) control unit (CU) to determine one or more candidate primary cell (Pcell) configuration modifications, wherein the one or more candidate Pcell configuration modification indications one or more modifications to at least one candidate primary / secondary cell (PScell) corresponding to a Pcell change of a user equipment (UE); Based on the overlap between one or more candidate Pcells of the master node (MN) CU and at least one candidate PScell ​​of the SN CU, the configuration modification of the one or more candidate Pcells is determined; as well as The one or more candidate Pcell configuration modifications are transmitted to the SN CU to generate the PScell ​​configuration of the at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications, so as to facilitate the mobility of the UE from the serving PScell ​​to the at least one candidate PScell.

16. The method of claim 15, wherein the MN CU communicates with at least the first MN distributed unit (DU) and the second MN DU. The configuration modifications to the one or more candidate Pcells include one or more modifications to one or more shared resources of the one or more candidate Pcells compared to the service Pcell. The Pcell change indicates the mobility of the UE from the serving Pcell to the candidate Pcell. The at least one candidate PScell ​​is associated with at least one SN DU of one or more SN DUs of the SN CU, and The service PScell ​​and the service Pcell are within the service coverage of the first MN DU, and the candidate Pcell and the at least one candidate PScell ​​are within the service coverage of the second MN DU.

17. The method of claim 15, wherein the mobility configuration indication is received when dual connectivity is established at the UE or after the dual connectivity is established at the UE, wherein the mobility configuration indication indicates enabling or disabling the mobility for the UE at the SN CU.

18. The method according to claim 16, The one or more shared resources include at least one of the following: one or more frequencies, one or more frequency bands, one or more frequency band combinations, one or more carriers shared between the MN CU and the SN CU. The one or more candidate Pcell configuration modifications also include one or more dependent resources, wherein the one or more dependent resources include at least one security key of the first MN DU and the second MN DU of the MN CU.

19. The method of claim 15, further comprising: The one or more candidate Pcell configuration modifications are transmitted to multiple CUs that are eligible to be configured as multiple SN CUs using non-UE associated messages, wherein the non-UE associated messages are next-generation radio access network (NG-RAN) node configuration update messages, and wherein the non-UE associated messages indicate that negotiation of one or more shared resources should be avoided during one of dual connectivity and Layer 1 / Layer 2 triggered mobility configuration at the UE.

20. The method of claim 15, wherein the method at the SN CU further comprises, in response to transmitting the one or more candidate Pcell configuration modifications to the CU: Receive the one or more candidate Pcell configuration modifications from the MN CU; as well as The one or more candidate Pcell configuration modifications are transmitted to the at least one SNDU, wherein the one or more candidate Pcell configuration modifications are transmitted to the at least one SNDU in the UE context setting request.

21. The method of claim 20, wherein receiving the one or more candidate Pcell configuration modifications comprises: Detect the mobility of the UE; as well as The mobility configuration request is transmitted to the MN CU to determine the configuration modification of one or more candidate Pcells corresponding to the at least one candidate PScell.

22. The method of claim 21, wherein the detection comprises: Based on the served cell information of at least the first MN DU and the second MN DU, the P cell change corresponding to the at least one candidate PScell ​​is identified, wherein the served cell information is received during the Xn setting process.

23. The method of claim 21, wherein the detection comprises: Determine the mapping between the at least one candidate PScell ​​and the one or more candidate Pcells of the SN CU; as well as Using a machine learning model, based on the mapping between the one or more candidate Pcells and the at least one candidate PScell, the configuration modification of the one or more candidate Pcells corresponding to the at least one candidate PScell ​​is predicted.

24. The method of claim 20, further comprising: In response to receiving the one or more candidate Pcell configuration modifications, based on the one or more candidate Pcell configuration modifications, one or more dependent resources for the at least one candidate PScell ​​are derived, wherein the one or more dependent resources for the at least one candidate PScell ​​include at least one security key; as well as The one or more dependent resources are transferred to the at least one SN DU for generating the PScell ​​configuration.

25. The method of claim 20, wherein, in response to transmitting the one or more candidate Pcell configuration modifications to the at least one SNDU, the method at the at least one SNDU further comprises: The one or more candidate Pcell configuration modifications are received from the SN CU, wherein the one or more candidate Pcell configuration modifications are received in the UE context setting request from the SN CU; The candidate PScell ​​configuration is generated based on at least one or more candidate Pcell configuration modifications. as well as Based on the candidate PScell ​​configuration, the UE performs the mobility from the serving PScell ​​to the at least one candidate PScell.

26. The method of claim 25, further comprising: Receive one or more dependent resources from the SN CU to generate the PScell ​​configuration; as well as The PScell ​​configuration is generated based on the one or more candidate Pcell configuration modifications and the one or more dependent resources.

27. The method of claim 25, further comprising: Generate multiple PScell ​​configurations corresponding to multiple candidate Pcells, wherein at least one candidate PScell ​​overlaps with the multiple candidate Pcells; as well as The plurality of PScell ​​configurations are transmitted to the UE to facilitate the UE in selecting at least one of the plurality of PScell ​​configurations based on the serving Pcell.

28. A non-transitory computer-readable medium having program instructions stored thereon, wherein the program instructions include: Receive one of a mobility configuration indication and a mobility configuration request from a secondary node (SN) control unit (CU) to determine one or more candidate primary cell (Pcell) configuration modifications, wherein the one or more candidate Pcell configuration modification indications one or more modifications to at least one candidate primary / secondary cell (PScell) corresponding to a Pcell change of a user equipment (UE); Based on the overlap between one or more candidate Pcells of the master node (MN) CU and at least one candidate PScell ​​of the SN CU, the configuration modification of the one or more candidate Pcells is determined; as well as The one or more candidate Pcell configuration modifications are transmitted to the SN CU to generate the PScell ​​configuration of the at least one candidate PScell ​​based on the one or more candidate Pcell configuration modifications, so as to facilitate the mobility of the UE from the serving PScell ​​to the at least one candidate PScell.

Images