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 of 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 PScell configuration of the at least one candidate PScell based on the one or more candidate Pcell configuration modifications for facilitating mobility of the UE from a serving PScell to the at least one candidate PScell.

Description

TITLESIMULTANEOUS LAYER 1 / LAYER 2 TRIGGERED MOBILITY IN MASTER AND SECONDARY NODESCROSS-REFERENCE TO RELATED APPLICATION (S)

[0001] This application claims priorities to Indian provisional application No. 202441027458, filed on April 2, 2024 and IN non provisional application No. 202441027458, filed on August 24, 2024, the entire contents of which are incorporated herein by reference.FIELD

[0002] The present disclosure relates to simultaneous Layer 1 / Layer 2 Triggered Mobility (LTM) in a master node and a secondary node.BACKGROUND

[0003] The information disclosed in this background section is only for enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0004] Fifth Generation (5G) advanced technology is configured with a disaggregated architecture of gNodeBs (gNBs), comprising gNB-Distributed Units (DUs), gNB-Control Units (CUs) and gNB-Radio Units (RUs), alternatively referred as cells communicating with one or more user equipments (UEs) and to provide efficient communication sendees to the one or more UEs.

[0005] Fig. 1 illustrates the disaggregated architecture of an exemplary gNB 102 as defined in Third Generation Partnership Project (3GPP) specifications for 5G. The gNB 102 may comprise one or more gNB DLTs 106 and 108 associated with a plurality of cells 109, 110, 111 and 112. The gNB-DU 106 hosts Radio Link Control (RLC), Medium Access Control (MAC) Layer 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 be communicating with one or more UEs, such as, but not limited to, the UE 104, indicating the cell 109, as a serving cell 109 for the UE 104. Each gNB-DU 106, 108, may host multiple such cells. For example, a maximum of 512 cells may be hosted in the current specifications of 3GPP. Further, the gNB 102 may also comprise a gNB-CU 115 including a gNB-CU-Control Plane (CP) 1 16, that hosts Packet Data Convergence Protocol -control (PDCP-c) and Radio Resource Control (RRC) layers and one or more gNB User Planes (UP) 118, that host PDCP-user and Service DataAdaptation Protocol (SDAP) layers. The gNB-CU-CP 116 may be connected to the one or more gNB- DUs 106 and 108 through an Fl-C interface. The one or more gNB-CU-UPs 118 may be connected to the one or more gNB-DUs 106 and 108 through an Fl -Li interface and to the gNB-CU-CP 116 through an El interface.

[0006] Various mobility techniques have been defined in the 5G advanced technology such as, but not limited to, LTM, also referred sometimes as Lower Layer Triggered mobility. LTM has been introduced, in Release (Rel) 18 of 3GPP specification to provide handover of signaling to a UE that moves from one serving cell to another cell, using Layer 1 / Layer 2 signaling.

[0007] During LTM, the UE sends a Measuremen tReport message to a serving gNB, also referred to 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 multiple LTM candidate target cells. The UE stores the configuration of LTM candidate target cell(s) and transmits an RRCReconfigurationComplete message to the gNB. The UE may perform Downlink (DL) synchronization and Timing Advance (TA) acquisition with candidate target cell(s) before receiving the LTM cell switch command. The UE performs Layer 1 (LI) measurements on the configured LTM candidate target cell(s) and transmits lower-layer measurement reports to the gNB. The gNB decides to execute LTM cell switch to a target cell and transmits a MAC Control Element (CE) triggering LTM ceil switch. The UE switches to the configuration of the LTM candidate target cell. The UE performs random access procedure towards the target cell if TA is not available. The UE indicates successful completion of the LTM ceil switch towards the target cell.

[0008] As the LTM is different in its execution compared to layer 3 mobility as the LTM performed by a gNB-DU using L1 / L2 protocols. Thus, the LTM avoids or minimizes significant modifications in configuration of upper layers and / or minimizing modifications configuration of the lower layers.

[0009] According to 3GPP standards, Dual Connectivity (DC) allows a User Equipment (UE) to connect to a first gNB-CU that acts as a Master Node (MN) and a second gNB-CU that acts as a Secondary Node (SN) simultaneously. A gNB-DU that may be associated with the MN and that provides communication services to the UE may be defined as a Master Cell Group (MCG). The MCG may comprise a plurality of cells including a Primary cell (Pcell) and a plurality of Secondary Cells (Scells). A cell, of the MCG, to which the UE may be connected, may be termed as the Pcell and the other plurality of cells may be defined as the Scells. A gNB-DU that may be associated with the SN and providing communication sendees to the UE may be defined as a Secondary Cell Group (SCG). The SCG may comprise a plurality of cells including a Primary Secondary Cell (PScell) and a plurality ofScells. A cell, of the SCG, to which the UE may be connected for DC may be defined as the PScell and the other plurality of cells of the SCG may be defined as the Scells. In few scenarios, the UE may be connected to two different gNB-DUs of the same gNB-CU for DC. In these scenarios, the gNB-CU may act as both MN and SN. Improvements to the techniques such as DC and LTM may be essential.SUMMARY

[0010] Embodiments of the present disclosure address a problem of enabling a smooth and seamless transition for the UE, when the UE, configured with LTM and DC, moves from a serving Pcell to a candidate Pcell of an MN CU and simultaneously from a serving PScell to a candidate PScell of an SN CU.

[0011] 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 Secondary7cell (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 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 further configured to transmit the one or more candidate Pcell configuration modifications to the SN CU for generating PScell configuration of the at least one candidate PScell based on the one or more candidate Pcell configuration modifications for facilitating mobility of the UE from a serving PScell to the at least one candidate PScell.

[0012] Disclosed herein also is a method that comprises 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 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 comprises determining 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 method comprises transmitting the one or more candidate Pcell configuration modifications to the SN CU for generating PScell configuration of the at least one candidate PScell based on the one or more candidate Pcell configuration modifications for facilitating mobility of the UE from a serving PScell to the at least one candidate PScell.

[0013] Disclosed further is a non-transitory computer-readable medium having program instructions stored thereon. The program instructions comprise 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 modifications indicate one or more modifications to at least one candidate Primary Secondary ceil (PScell) corresponding to a Pcell change of a User Equipment (UE). The program instructions comprise determining 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 program instructions comprise transmitting the one or more candidate Pcell configuration modifications to the SN CU for generating PScell configuration of the at least one candidate PScell based on the one or more candidate Pcell configuration modifications for facilitating mobility of the UE from a serving PScell to the at least one candidate PScell.BRIEF DESCRIPTION OF THE DRAWINGS

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

[0015] Fig. 1 illustrates an exemplary architecture of a gNodeB (gNB) as specified in the 3GPP standards;

[0016] Figs. 2A and 2B illustrate schematic diagrams depicting mobility of a User Equipment (UE) configured with Dual Connectivity (DC);

[0017] Figs. 3A and 3B illustrate schematic diagrams of enabling inter-node coordination for mobility of the UE in accordance with embodiments of the present disclosure;

[0018] Fig. 4 illustrates an exemplary block diagram of a Master Node (MN) Control Unit (CU) for enabling inter-node coordination for mobility of the UE, in accordance with an embodiment of the present disclosure;

[0019] Fig. 5 illustrates an exemplary block diagram of a Secondary Node (SN) CU for enabling internode coordination for mobility of the UE, in accordance with an embodiment of the present disclosure;

[0020] Fig. 6 illustrates an exemplary block diagram of an SN DU for enabling inter-node coordination for mobility of the UE, in accordance with an embodiment of the present disclosure;

[0021] Fig. 7 illustrates an exemplar}7data flow diagram for enabling inter-node coordination for mobility of the UE, in accordance with an embodiment of the present disclosure;

[0022] Fig. 8 illustrates an exemplary data flow diagram for enabling inter-node coordination for mobility of the UE, in accordance with another embodiment of the present disclosure;

[0023] Fig. 9 illustrates an exemplar}7data flow diagram for enabling inter-node coordination for mobility of the UE, in accordance w'ith yet another embodiment of the present disclosure;

[0024] Fig. 10 illustrates an exemplary flowchart of a method for enabling inter-node coordination for mobility of the UE, in accordance with an embodiment of the present disclosure;

[0025] Fig. 11 illustrates an exemplary flowchart of a method for enabling inter-node coordination for mobility of the UE, in accordance with another embodiment of the present disclosure;

[0026] Fig. 12 illustrates an exemplary flowchart of a method for enabling inter-node coordination for mobility of the UE, in accordance with yet another embodiment of the present disclosure;

[0027] Fig. 13 illustrates an exemplary flowchart of a method for enabling inter-node coordination for mobility of the UE, in accordance ’with yet another embodiment of the present disclosure; and

[0028] Fig. 14 show's exemplary components for enabling inter-node coordination for mobility of the UE, in accordance w'ith yet another embodiment of the present disclosure.DETAILED DESCRIPTION

[0029] The following detailed description of example embodiments refers to the accompanying drawings. The present disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the present disclosure or may be acquired from practice of the implementations. Further, 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 flowchart and description of operations provided below7relate to at least one of the embodiments in the present disclosure. It should be noted that it is possible to make other embodiments that do not exactly match the flowchart and its description. It is understood that in other embodiments one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least in part).

[0030] It will be apparent that systems and / or methods, described herein, may be implemented in different forms of hardware, software, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods should not limit their implementations. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0031] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, the particular combinations are not intended to limit the disclosure of implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Even if a dependent claim directly depends on only one claim, the present disclosure may indicate that the dependent claim is dependent on other claims in the claim set.

[0032] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” (in other words, nouns not mentioned in the plural) are intended to include one or more items and may be used interchangeably with “one or more.” Also, as used herein, the terms “has,” “have,” “having,” “include,” “including,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of [A] and [B] ,” “[A] and / or [B],” or “at least one of [A] or [B]” are to be understood as including only A, only B, or both A and B.

[0033] Embodiments of the present disclosure solve one or more problems envisaged when a UE, configured with LTM and DC, moves from a serving Pcell to a candidate Pcell of an MN CU and simultaneously from a serving PScell to a candidate PScell of an SN CU. In an embodiment, systems and methods that enable coordination between the MN CU and the SN CU are disclosed. The systems and methods enable the MN CU to share one or more candidate Pcell configuration modifications, corresponding to the candidate PS Cell of the UE, with the SN CU. The SN CU may further share the one or more candidate Pcell configuration modifications to an SN-DU associated with the candidate PScell. The SN DU may generate 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 change and / or configuration modifications and request the MN CU to provide the one or more candidate Pcell configuration modifications. In another embodiment, the systems and methods that enable coordination between a CU, acting as both MN and SN, and an SCG DU when both the serving Pcell and the serving PScell communicate with the same CU. The CU may determine the one or more candidate Pcellconfiguration modifications and transmit the one or more candidate Pcell configuration modifications to the SCG-DU to generate PScell configuration to perform LTM for the UE from the serving PScell to the candidate PScell.

[0034] Thus, embodiments of the present disclosure enable coordination between the MN CU and the SN CLi when the UE undergoes intra-SN LTM such as, but not limited to, LTM PScell change. The embodiments of the present disclosure also enable the SCG DU to perform autonomous LTM by providing the one or more candidate Pcell configuration modifications, corresponding to the candidate PScell, to the SCG DU during a preparation phase of the LTM.

[0035] Figs. 2A and 2B illustrate schematic diagrams depicting a User Equipment (UE) configured with Dual Connectivity (DC).

[0036] Fig. 2A illustrates a schematic diagram depicting the UE 104 connected to a gNB-CU 202, that may act as a Master Node (MN) and a gNB-CU 204, that may act as a Secondary Node (SN) for implementing DC. In one embodiment, the DC may be NR DC. In another embodiment, the DC may be any other type of DC. The gNB-CU 202 may be alternatively referred herein as MN CU 202, and the gNB-CU 204 may be alternatively referred herein as SN CU 204. Each of the gNB-CU 202 and the gNB-CU 204 may be similar to the gNB-CU 115 of Fig. 1. Further, the MN CU 202 may be connected to one or more gNB DUs, also referred to as one or more MN DUs 206 and the SN CU 204 may be connected to one or more gNB DUs, also referred to as, one or more SN DUs 208. Further, the UE 104 may be connected to the MN CU 202 via at least one MN DU (for e.g., MN DU 206-1) of the one or more MN DUs 206 and to the SN CU 204 via at least one SN DU (for e.g., SN DU 208-1) of the one or more SN DUs 208. The MN-DU 206-1 and the SN DU 208-1 may be similar in design and operation to the gNB-DU 106 or gNB-DU 108 of Fig. 1.

[0037] The MN DU 206-1 may comprise an MCG, and the SN DU 208-1 may comprise an SCG. As shown in Fig. 2A, the UE 104 may be connected to the Pcell 210 and the PScell 212 simultaneously for DC. The Pcell 210 and the PScell 212 may be similar to one or more of the plurality of cells 109-112 of Fig. 1.

[0038] Fig. 2B illustrates a schematic diagram depicting the UE 104 connected to the two different gNB-DUs of the same gNB-CU 202 for DC in another embodiment. For example, the UE 104 may be connected to the MN DU 206-1 comprising the MCG and the SN DU 208-1 comprising the SCG. In this case, the gNB-CU 202 may act as both MN and SN. In some embodiments, the MCG and the SCG may be located within the same gNB-DU, for example the gNB-DU 206-1 or the gNB-DU 208-1.

[0039] One or more problems envisaged during mobility of the UE 104 are explained herein below.

[0040] Rel-19 Technical Specification (TS) of the 3GPP standards specifies support for inter-CU Layer 1 / Layer 2 Triggered Mobility (LTM) for the UE 104. For example, the Rel-19 TS indicates support for inter-CU LTM when DC is configured, and a CU is acting as SN and MCG is unchanged. As another example, the Rel-19 TS indicates support for inter-CU LTM for the UE 104 when DC is configured, the CU is acting as MN and SCG is unchanged or SCG is released. Rel-19 also specifies that the case where LTM is configured in both MCG and SCG may be excluded. Further, during a discussion on coexistence of LTM and other features such as, but not limited to, DC, in RAN# 125 meetings, an agreement has been made as to no restriction of configuring MCG LTM and SCG LTM and no further enhancements in RAN2 on network interaction to better enable the LTM. The agreement may indicate that configuring LTM independently at the same time at MN and SN is permitted without any further discussion on MN-SN co-ordination w'ithin the scope of Rell8 work. One or more problems envisaged with the above implementation of the LTM is discussed below.

[0041] Figs. 3A and 3B illustrate schematic diagrams of enabling inter-node coordination for mobility of a UE in accordance with embodiments of the present disclosure.

[0042] As shown in Fig. 3 A, the UE 104 may be communicating using mobile communication network within a serving coverage region, also referred to as coverage, of the MN CU 202 and the SN CU 204 for DC. The coverage of a CU may be defined as a geographical region where the UE 104 may receive communication services through one or more cells associated with the CU. The arrangement of coverage of the MN CU 202 and the SN CU 204 has only been provided for illustration purpose and not to be construed as limiting. The MN CU 202 may comprise one or more MN DUs 206, such as, but not limited to, an MN DU 206-1 and an MN DU 206-2. In other embodiments, the MN CU 202 may comprise any number of MN DUs without limiting to the il lustration of Fig. 3 A.

[0043] Further, the SN CU 204 may comprise one or more SN DUs 208, such as, but not limited to, an SN DU 208-1 and an SN DU 208-2. The SN CU 204 may comprise any number of SN DUs, without limiting to the SN DU 208-1 and the SN DU 208-2 as illustrated in Fig. 3A. Furthermore, in one embodiment, the one or more MN DUs 206 may be larger in size (macro cells) compared to that of the one or more SN DUs 208, for example, as shown in Fig. 3A. In other embodiments, the one or more MN DUs 206 may be smaller in size compared to the one or more SN DUs 208. Each of the one or more MN DUs 206 and the one or more SN DUs 208 may comprise a plurality of cells serving a plurality of UEs, for example the plurality of cells 109-111 of Fig. 1. Further, a coverage of at least one of the one or more SN DUs 208 may overlap with the coverage of at least two of the one or more MN DUs206. As a non-limiting example, the coverage of the SN DU 208-2 may be overlapping with the coverage of the MN DU 206-1 as well as the MN DU 206-2.

[0044] Furthermore, the UE 104 may initially be connected to the Pcell associated with a first MN DU of the one or more MN DUs 206 and the PScell associated with a first SN DU of the one or more SN DUs 208 for DC. As a non-limiting example, the UE 104 may initially be connected to the MN DU 206-1 and the SN DU 208-1 simultaneously for DC. In this scenario, there could be shared resources between the MN CLT 202 and the SN CU 204 such as, but not limited to, frequencies, carriers, band combinations and the like. The first MN DU may be configured to control 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 the one or more resources for itself and a second set of the one or more resources to the first SN DU. The first MN DU may configure the UE 104 to communicate with the Pcell of the first MN DU and the PScell of the first SN DU simultaneously based on the allocation.

[0045] The one or more resources may comprise one or more shared resources such as, but not limited to, one or more frequencies, one or more frequency bands, one or more band combinations, and one or more carriers. As a non-limiting example, consider that the UE 104 is capable of communicating using frequency bands Bl, B2, B3, B4, B5 and B6 and the SN DU 208-1 may comprise 4 PScells-Cl, C2, C3 and C4. In this example, the MN DU 206-1 may allocate the frequency bands B4, B5, B6 to the MN DU 206-1 to configure the UE 104 and the frequency bands Bl, B2, B3 to the SN DET 208-1 comprising the cells Cl and C2. Whereas the MN DU 206-1 may change the allocation to the frequency bands Bl, B2, B3 to the MN DU 206-1 and the frequency bands B4, B5, B6 to the SN DU 208-1. Further, the frequency bands B 1 , B2, and B.3 may be configured by the SN DU 208- 1 to the UE 104 to communicate with the PScells Cl and C2 and B4, B5 and B6 to communicate with the PScells C3 and C4 of the SN DU 208-1.

[0046] Further, the UE 104 may undergo mobility, at step 312, from a serving PScell of the first SN DU to a candidate PScell of the second SN DU without a Pcell change within the coverage of the first MN DU. The candidate PScell may be defined as a PScell, of the second SN DU, which may act as a candidate cell for performing LTM. For example, the second SN DU may be the SN DU 208-2. In this scenario, the candidate PScell of the second SN DU may act as the serving PScell for the UE 104 upon mobility. In this case, the first MN DU may allocate the one or more shared resources to a plurality of PScells, including the candidate PScell, of the SN DU 208-2 to communicate with the UE 104 to perform successful LTM. In this scenario, though the PScell of the UE 104 changes, the Pcell remains same as the UE 104 remains in the coverage of the first MN DU. Hence, in this scenario, the secondSN DU may perform autonomous LTM for the UE 104 based on the allocation of the one or more shared resources by the first MN DU.

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

[0048] Consequently, there may be modifications to the one or more shared resources for the Pcells. Consequently, as the one or more shared resources for the PScells may be dependent on the one or more shared resources allocated to the Pcells, the one or more shared resources allocated to the candidate PScell may also be different from those of the serving PScell. As a non-limiting example, the UE 104 may use B4, B5, and B6 in association with the SN DU 208-2 based on the allocation of the MN DU 206-1, whereas the MN DU 206-2 may allocate Bl , B4 and B5 to the SN DU 208-2 for performing the LTM. However, as there is no coordination between the MN CU and the SN CU, the second SN DU may not be able to perform autonomous LTM for the UE 104.

[0049] In some scenarios, as shown in Fig. 3B, the coverage of the first SN DU may overlap with the coverage of the second SN DU along the boundaries. Further, the UE 104 may move from the first SN DU to the second SN DU and consequently from the first MN DU to the second MN DU. For example, the UE 104 may move, at step 316, from the coverage of the SN DU 208-1 to the SN DU 208-2. Consequently, the UE 104 may also move between the coverage of the MN DU 206-1 and the MN DU 206-2. In this scenario, the Pcell of the UE 104 may be modified from the serving Pcell of the first MN DU to the candidate Pcell of the second MN DU and the PScell of the UE 104 may 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 may allocate one or more shared resources to the UE 104 that are different from those allocated by the first MN DU. Consequently, there may be modifications to the one or more shared resources allocated to the UE 104 for the Pcells, as well as the PScells. As a nonlimiting example, the UE 104 may use B4, B5, and B6 to communicate with the SN DU 208-2 based on the allocation of the MN DU 206-1, whereas the MN DU 206-2 may allocate Bl, B4 and B5 to theSN DU 208-2. However, as there is no coordination between the first MN CU and the first SN CU, the second SN DU may not be able to perform autonomous LTM for the UE 104.

[0051] Embodiments of the present disclosure address some of the above-described problems. Accordingly, in an embodiment, the SN CU 204 may indicate to the MN CU 202 when LTM is enabled at one of the one or more SN DUs 208 of the SN CU 204. The MN CU 202 may provide one or more candidate Peel! configuration modifications, indicating one or more modifications to the candidate PScell corresponding to the Pcell change of the UE 104. The SN CU 204 may receive the one or more candidate Pcell configuration modifications and may transmit the one or more candidate Pcell configuration modifications to the second SN DU. The second SN DU may receive the one or more candidate Pcell configuration modifications and may prepare the candidate PScell configuration based on the one or more candidate Pcell configuration modifications for performing the LTM mobility of the UE 104 from the serving PScell to the candidate PScell. Thereafter, the second SN DU may autonomously execute LTM regardless of the Pcell change of the UE 104. In another embodiment, the one or more candidate Pcell configuration modifications corresponding to each Pcell of a plurality of MN DUs of the MN CU 202 could be shared with a neighboring gNB CU, such as, but not limited to, the SN CU 204, during the Xn setup procedure itself. This avoids any negotiation-based communication during UE mobility. The second SN DU may generate the correct candidate PScell configuration based on the one or more Pcell configuration modifications indicated by the MN CU 202. Various embodiments of the present di sclosure are described in detail below.

[0052] In one embodiment, the MN CU 202 may transmit an identifier of each of the plurality of Pcelis of the one or more MN DUs 206 of the MN CU 202 within an Xn parameter to the SN CU 204 during an Xn setup procedure. The Xn setup procedure may include exchange of application-level configuration data needed for any two CUs to interoperate over an Xn-Control (Xn-C) interface. The Xn parameter may be, but not limited to, “served cell information”. Similarly, the SN CU 204 also may transmit the identifier of the plurality of PScells of the one or more SN DUs 208 of the SN CU 204 to the MN CU 204 during the Xn setup procedure within Xn parameter. The identifiers may be further used to generate a mapping of the plurality of PScells of the one or more SN DUs 208 PScell corresponding to each of the plurality of Pcelis of the one or more MN DUs 206.

[0053] Further, the UE 104 may be initially configured with single connectivity with the MN CU 202 and LTM. Thereafter, the UE 104 may measure and transmit at least a Layer 3 (L3) measurement report including one or more L3 measurements for one or more cells of the SN CU 204. The one or more L3 measurements may comprise, but not be limited to, Reference Signal Received Power (RSRP), and Reference Signal Received Quality (RSRQ). Further, the MN CU 202 may determine enabling DC forthe UE 104 based on the L3 measurement report and may configure intra-gNB DC and / or inter-gNB DC. The DC may be NR DC or EN DC. The intra-gNB DC may be defined as providing DC services to the UE 104 via a Pceil and a PScell of the same gNB CU. The inter-gNB DC may be defined as providing DC services to the UE 104 via a Pceil of a first gNB CU and a PScell of a second gNB CU. The intra-gNB arni / or inter-gNB NR DC may depend on a PScell that has been selected for the DC. In case of the intra-gNB NR DC, the same gNB-CU may act as both MN and SN.

[0054] Further, the SN CU 204 may indicate enabling LTM to the MN CU 202 while establishing the DC at the UE 104 or anytime later while providing DC services to the UE 104. The SN CU 204 may transmit the indication, also referred to herein as a mobility configuration indication, of LTM enabling via an Xn parameter. The Xn parameter may be any parameter transmitted from the SN CU 204 to the MN CU 202 via an Xn interface.

[0055] Further, the MN CU 202 may determine one or more candidate Pceil configuration modifications that may affect a configuration of at least one candidate PScell of the UE 104. In some embodiments, the at least one candidate PScell may be the target PScell for the LTM. In other embodiments, the at least one candidate PScell may be one or more candidate PScells for the LTM that may or may not be chosen as the target PScell. The one or more candidate Pceil configuration modifications may indicate one or more modifications required at the candidate PScell due to a Pceil change of the UE 104. When the UE 104 moves between the one or more MN DUs 206 and''or the one or more SN DUs 208 simultaneously, the Pceil and the PScell of the UE 104 may change. The MN CU 202 may determine one or more candidate Pceil configuration modifications required at the at least one candidate PScell due to the Pceil change. For example, the UE 104 may move from a Pceil of the first MN DU 206-1 to a Pceil of the second MN DU 206-2 and simultaneously between the PScells of the second SN DU 208-2. In another example, the UE 104 may move from the Pceil, also known as the serving Pceil, of the first MN DU 206-1 to the Pceil, also known as the candidate / target Pceil of second MN DU 206-2 and simultaneously between 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 may be defined as a serving PScell and the PScell of the second SN DU 208-2 to which the UE 104 moves, may be defined as the candidate / target PScell.

[0056] The one or more candidate Pceil configuration modifications may comprise indication of one or more shared resources the first MN DU has allocated to the first MN DU for configuring the UE 104 and one or more shared resources available for the first SN DU to configure the UE 104. The one or more shared resources corresponding to the at least one candidate PScell for LTM associated with the one or more SN DUs 208 of the SN CU 204 are configured to the UE 104. For example, the one ormore candidate Pcell configuration modifications may indicate one or more modifications required at the at least one candidate PScell of the second SN DU, in order to determine the LTM candidate cell configuration for the 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 comprise at least one of one or more frequencies, one or more frequency bands, one or more band combinations, one or more carriers shared between the MN CU 202 and the SN CU 204. In some embodiments, the one or more candidate Pcell configuration modifications may comprise one or more dependent resources including at least one security key of the first MN DU and the second MN DU of the MN CU 202.

[0057] The one or more resources may indicate the one or more resources available at the first MN DU and the second MN DU 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] Further, the MN CU 202 may determine the one or more candidate Pcell configuration modifications and transmit the one or more candidate Pcell configuration modifications to the SN CU 204. The SN CU 204 may further transmit the one or more candidate Pcell configuration modifications to the second SN DU to enable the second SN DU to perform autonomous LTM by issuing a PScell configuration that is determined based on a correct Pcell configuration. In addition, the SN CU 204 may derive one or more dependent resources for the at least one candidate PScell based on the one or more candidate Pcell configuration modifications. For example, the SN CU 204 may derive a security key for the at least one candidate PScell when the Pcell may be served by a different CU-UP.

[0059] In some other embodiments, when the coverage of the at least one candidate PScell overlaps with the coverage of a plurality of candidate Pcells, the second SN DU may prepare a plurality of PScell configurations corresponding to each of the plurality of Pcells. The second SN DU may transmit the plurality of PScell configurations to the UE 104. Upon receiving the plurality of PScell configurations, the UE 104 may select an appropriate PScell configuration among the plurality of PS cell configurations based on the serving Pcell at a current time period.

[0060] In some embodiments, the MN CU 202 may transmit the one or more candidate Pcell configuration modifications corresponding to each of the plurality of Pcells of the MN CU 202 to a plurality of gNB-CUs that may be eligible to be configured as SN CU 204 for the UE 104 in DC. The MN CU 202 may transmit the one or more candidate Pcell configuration modifications using a non-UE associated message during Xn setup or later. For example, the non-UE associated message may be a New Generation-Radio Access Network (NG-RAN) Node Configuration Update message. The non-UEassociated message may imply that a negotiation of the one or more shared resources need not be performed later at the time of configuring DC or LTM configuration for UEs.

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

[0062] Thus, the solutions of the present disclosure provide a coordination between the MN CU 202 and the SN CU 204 so as to enable smooth and seamless LTM for the UE 104 moving between coverage of the one or more MN DUs 206 and the one or more SN DUs 208 simultaneously, without requiring any dynamic negotiations. Furthermore, the methods and systems of the present disclosure enable providing the one or more candidate Pcell configuration modifications to the second SN DU so that the second SN DU may prepare the candidate PScell configuration based on the corresponding one or more candidate Pcell configuration modifications even when the UE 104 moves while performing the LTM. This provides forehand information on the configurations of various candidate Pcells to the second SN DU, which may enable the second SN DU to perform autonomous LTM without communicating with the MN CU 202 during an LTM execution phase. The embodiments of the present disclosure also enable the SN CU 204 or the candidate PScell to adopt the corresponding PScell configuration based on the one or more candidate Pcell configuration modifications, whenever a Pcell change is identified at the SN CU 204 based on topology information.

[0063] In some embodiments, when the MN CU 202 may be unable to provide the one or more candidate Pcell configuration modifications based on the mobility configuration indication from the SN CU 204, the SN CU 204 may transmit a mobility configuration request for the one or more candidate Pcell configuration modifications. The MN CU 202 may be unable to provide the one or more candidate Pcell configuration modifications either due to dynamicity of parameter or due to inability of the MN CU 202 to determine appropriate mapping between the plurality of Pcells and corresponding plurality of PScells or due to any other reason.

[0064] In one embodiment, the SN CU 204 may employ a Machine Learning (ML) model to detect mobility of the UE 104 between the first MN DU and the second MN DU and may request the MN CU 202 to provide the one or more candidate Pcell configuration modifications. The SN CU 204 mayidentify one of the one or more candidate Pcells corresponding to the at least one candidate PScell, based on the served cell information of the one or more MN DUs 206. Further, the SN CU 204 may determine a 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 the mapping. Thus, the SN CU 204 may detect mobility of the UE 104 between the first Pcell or a serving Pcell of the first MN DU and the second Pcell of the second MN DU and hence a change in the Pcell of the UE 104. The SN CU 204 may further transmit the mobility configuration request to the MN CU 202. The MN CU 202 may receive the mobility configuration request and may further determine the one or more candidate Pcell configuration modifications based on the mobility configuration request. The MN CU 202 may transmit the one or more candidate Pcell configuration modifications to the SN CU 204, which may further transmit the one or more candidate Pcell configuration modifications to the second SN DU to perform LTM for the UE 104.

[0065] In another embodiment, the SN CU 204 may request the MN CU 202 to transmit the one or more candidate Pcell configuration modifications corresponding to each of the plurality of PScells using a non-UE associated procedure, for example the Xn setup procedure or the NG RAN Node Configuration Update procedure.

[0066] Thus, embodiments of the present disclosure enable the SN CU 204 to automatically detect mobility of the UE 104 based on the served cell information received during the Xn setup procedure. The methods and systems thereby enable the SN CU 204 to request one or more candidate Pcell configuration modifications for the identified candidate Pcells of the MN CU 202.

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

[0068] In this embodiment, the UE 104 may be initially communicating with the CU 202 via the first MN DU. The UE 104 may later perform L3 measurements for DC and may transmit the L3 measurement report to the CU 202. The CU 202 may determine to configure the UE 104 for DC. Further, the CU 202 may determine the one or more candidate Pcell configuration modifications and may transmit the one or more candidate Pcell configuration modifications to the second SN DU. Thereafter, the second SN DU may prepare candidate cell configuration for the at least one candidate PScell,associated with the second SN DU, based on the one or more candidate Pcell configuration modifications. The second SN DU may later perform the LTM for the UE 104 autonomously based on the candidate cell configuration.

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

[0070] Figs. 4-6 illustrate exemplary block diagrams of one or more systems described in the present disclosure.

[0071] Fig. 4 illustrates an exemplary7block diagram of the MN CU 202 for enabling inter-node coordination for mobility of the UE 104, in accordance with an embodiment of the present disclosure.

[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 comprise at least a modifications determination module 410. The components of the MN CU 202 provided herein are not exhaustive, and that the MN CU 202 may include more or few7er components than that of depicted in Fig. 4. Further, two or more components may be embodied in one single component, and / or one component may be configured using multiple sub-components to achieve the desired functionalities. Some components of the MN CU 202 may be configured using hardware elements, software elements, firmware elements and / or a combination thereof.

[0073] In one embodiment, the 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, the processor 402 may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a Digital Signal Processor (DSP), a processing circuitry with or without an accompanying DSP, or various other processing devices including, a Microcontroller Unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like.

[0074] The I / O interface 404 may include mechanisms configured to receive inputs from and provide outputs to peripheral devices. For instance, the I / O interface 404 may include at least one input interface and / or at least one output interface. Examples of the input interface may include, but are not limited to, a keyboard, a mouse, a joystick, a keypad, a touch screen, soft keys, a microphone, and the like. Examples of the output interface may include, but are not limited to, a User Interface (UI) display (such as a Light Emitting Diode (LED) display, a Thin-Film Transistor (TFT) display, a Liquid CrystalDisplay (LCD), an Active-Matrix Organic Light-Emitting Diode (AMOLED) display, etc.), a speaker, a ringer, a vibrator, and the like.

[0075] In one embodiment, the communication interface 406 includes a transceiver for wirelessly communicating information to, or receiving information from, the SN CU 204, and the one or more MN DUs 206 and one or more other network elements of 5G communication architecture. The communication may be achieved over a communication network. The communication interface 406 may be dependent on the network function with which the MN CU 202 communicates with. For example, the communication interface 406 may be Xn interface when communicating with the SN CU 204, and Fl interface when communicating with the one or more DUs.

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

[0077] The memory 408 can be any type of storage accessible to the processor 402. For example, the memory 408 may include volatile or non-volatile memories, or a combination thereof. In an embodiment, the memory 408 may store the one or more candidate Pcell configuration modifications upon determination by the MN CU 202. The memory 408 may also include instructions 412 to perform one or more methods of the MN CU 202 as described in the present disclosure. In a few embodiments, the instructions 412 may cause the processor 402 to perform one or more methods of the MN CU 202.

[0078] The modifications determination module 410 may determine the one or more candidate Pcell configuration modifications upon receiving the mobility configuration indication or the mobility configuration request to determine the one or more candidate Pcell configuration modifications.

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

[0080] Fig. 5 illustrates an exemplary block diagram of the SN CU 204 for enabling inter-node coordination for mobility of the UE 104, in accordance with an embodiment of the present disclosure.

[0081] The SN CU 204 includes at least one processor 502 communicably coupled to, an Input / Output (I / O) interface 504, a communication interface 506 and a memory 508. The processor 502 may comprise at least a mobility detection module 510 and a dependent resource deduction module 512. The components of the SN CU 204 provided herein are not exhaustive, and that the SN CU 204 may include more or fewer components than that of depicted in Fig. 5. Further, two or more components may be embodied in one single component, and / or one component may be configured using multiple subcomponents to achieve the desired functionalities. Some components of the SN CU 204 may be configured using hardware elements, software elements, firmware elements and / or a combination thereof. Further, the SN CU 204 may be communicatively coupled with the MN CU 202, and the one or more SN DUs 208.

[0082] In one embodiment, the 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, the processor 502 may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a DSP, a processing circuitry with or without an accompanying DSP, or various other processing devices including, an MCU, a hardware accelerator, a special-purpose computer chip, or the like.

[0083] The I / O interface 504 may include mechanisms configured to receive inputs from and provide outputs to peripheral devices. For instance, the I / O interface 504 may include at least one input interface and / or at least one output interface. Examples of the input interface may include, but are not limited to, a keyboard, a mouse, a joystick, a keypad, a touch screen, soft keys, a microphone, and the like. Examples of the output interface may include, but are not limited to, a UI display (such as an LED display, a TFT display, an LCD, an AMOLED display, etc.), a speaker, a ringer, a vibrator, and the like.

[0084] In one embodiment, the communication interface 506 includes a transceiver for wirelessly communicating information to, or receiving information from, the MN CD 202, and the one or more SN DUs 208 and one or more other network elements of the 5G communication architecture. The communication may be achieved over a communication network. The communication interface 506may be dependent on the network function with which the SN CU 204 communicates with. For example, the communication interface 506 may be Xn interface when communicating with the MN CU 202, and Fl interface when communicating with the one or more SN DUs 208.

[0085] In operation, the communication interface 506 may transmit the mobility configuration indication to the MN CU 202 upon establishing DC at the UE 104 or at a later time. The mobility configuration indication indicates enabling or disabling the mobility for the UE 104 at the SN CU 204. In an embodiment, the communication interface 506 may transmit the mobility configuration request to the MN CU 202, to determine the one or more candidate Pcell configuration modifications. The communication interface 506 may, in response to the transmission of one of the mobility configuration indication and the mobility configuration request, receive the one or more candidate Pcell configuration modifications. The communication interface 506 may also transmit the one or more candidate Pcell configuration modifications to the second SN DU. The communication interface 506 may also transmit the one or more dependent resources in addition to the one or more candidate Pcell configuration modifications.

[0086] The memory 508 can be any type of storage accessible to the processor 502. For example, the memory 508 may? include volatile or non-volatile memories, or a combination thereof. In an embodiment, the memory? 508 stores the one or more packet detection rules and forwarding rules and buffered downlink data. The memory 508 may also include instructions 514 to perform one or more methods of the SN CU 204 as described in the present disclosure. In some embodiments, the instructions 514 may? cause the processor 502 to perform one or more methods of the SN CU 204.

[0087] The memory 508 may be configured to store a mapping of each of a plurality of PScells of the SN CU 204 with the corresponding plurality of Pcells of the MN CU 202. The memoiy 508 may? also store the identifiers of the plurality of PScells and the plurality of Pcells that are mapped with each other, which require an MN configuration change.

[0088] The mobility detection module 510 may? be configured to detect mobility of the UE 104 between the one or more MN DUs 206. The mobility detection module 510 may comprise an ML model trained to detect the mobility of the UE 104. The ML model may receive a mapping between the plurality of Pcells of the MN CU 202 and the plurality of PScells of the SN CU 204 as input and may predict any Pcell change as output based on the mapping. In another embodiment, the mobility? detection module 510 may be configured to detect the mobility of the UE 104 based on the served cell information received from the MN CU 202 during the Xn setup procedure.

[0089] In certain scenarios, when neither the MN CU 202 nor the SN CU 204 may indicate the one or more Pcell configuration modifications corresponding to the Pcell change, the SN CU 204 may not be able to perform autonomous LTM. This may be because of an MN configuration change. In some embodiments, the mobility detection module 510 may be configured to store the identifiers of the plurality of PScells and the plurality of Pcells that are mapped with each other which require the MN configuration change. The mobility detection module 510 may retrieve the mapping and the corresponding identifiers at a later point of time to request the one or more cand idate Pcell configuration modifications in advance to prepare the at least one candidate PScell for LTM.

[0090] The dependent resource deduction module 512 may be configured to derive one or more dependent resources required for the at least one candidate PScell for LTM of the UE 104. In one embodiment, the dependent resource deduction module 512 may derive a security key required for preparing the at least one candidate PScell for LTM. The dependent resource deduction module 512 may derive one or more security keys for the at least one candidate PScell, also referred as SN security key, based on one or more security keys included in the one or more candidate Pcell configuration modifications, also referred to as, MN security keys. In some embodiments, each of the one or more MN DUs 206 may have a unique MN security key and hence the SN CU 204 may derive multiple SN security keys for the at least one candidate PScell. As a non-limiting example, the MN DU 206-1 and the MN DU 206-2 of Figs 3A and 3B may have different MN security keys, thereby the SN CU 204 may derive a first SN security key for cells 1 and 2 of SN DU 208-2 and a second SN security key for cells 3 and 4 of SN DU 208-2.

[0091] Fig. 6 illustrates an exemplary block diagram of the SN DU 208 for enabling inter-node coordination for mobility of the UE 104, in accordance with an embodiment of the present disclosure.

[0092] The SN DU 208 includes at least one processor 602 communicably coupled to, an Input / Output (I / O) interface 604, a communication interface 606 and a memory 608. The processor 602 may comprise one or more components such as, but not limited to an LTM configuration generation module 610. The components of the SN DU 208 provided herein are not exhaustive, and that the SN DU 208 may include more or fewer components than that of depicted in Fig. 6. In a preferred embodiment, the SN DU 208 may include, but not limited to, the SN DU 208-2 where the at least one candidate PScell, corresponding to the UE 104, resides. Further, two or more components may be embodied in one single component, and / or one component may be configured using multiple sub-components to achieve the desired functionalities. Some components of the SN DU 208 may be configured using hardware elements, software elements, firmware elements and / or a combination thereof. Further, the SN DU 208 is communicatively coupled with the MN CU 202.

[0093] In one embodiment, the 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, the processor 602 may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a DSP, a processing circuitry with or without an accompanying DSP, or various other processing devices including, an MCU, a hardware accelerator, a special-purpose computer chip, or the like.

[0094] The I / O interface 604 may include mechanisms configured to receive inputs from and provide outputs to peripheral devices. For instance, the I / O interface 604 may include at least one input interface and / or at least one output interface. Examples of the input interface may include, but are not limited to, a keyboard, a mouse, a joystick, a keypad, a touch screen, soft keys, a microphone, and the like. Examples of the output interface may include, but are not limited to, a UI display (such as an LED display, a TFT display, an LCD, an AMOLED display, etc.), a speaker, a ringer, a vibrator, and the like.

[0095] In one embodiment, the communication interface 606 includes a transceiver for wirelessly communicating information to, or receiving information from, the MN CU 202, and one or more other network elements of the 5G system architecture. The communication may be achieved over a communication network. The communication interface 606 may be dependent on the network function with which the SN DU 208 communicates with. For example, the communication interface 606 may be Ni l or N2 interface when communicating with the MN CU 202.

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

[0097] The memory 608 can be any type of storage accessible to the processor 602. For example, the memory 608 may include volatile or non-volatile memories, or a combination thereof. In an embodiment, the memory 608 stores the one or more packet detection rules and forwarding rules and buffered downlink data. The memory 608 may also comprise instructions 612 to perform one or more methods of the SN DU 208 as described in the present disclosure. In some embodiments, the instructions 612 may cause the processor 602 to perform one or more methods of the SN DU 208.

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

[0099] Fig. 7 illustrates an exemplar}7data flow diagram for enabling inter-node coordination for mobility of the UE 104, in accordance with an embodiment of the present disclosure.

[0100] The method 700 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform specific functions or implement specific abstract data types.

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

[0102] The method 700 describes a sequence of steps for enabling the MN CU 202 to determine the one or more candidate Pceli configuration modifications upon receiving the indication from the SN CU 204 that LTM has been enabled at the SN CU 204.

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

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

[0105] At step 706, the MN CU 202 may determine configuring the UE 104 with DC based on the L3 measurement report.

[0106] At step 708, the MN CU 202 may transmit an S-node addition request to one or more gNB- CUs that may provide DC services to the UE 104 as secondary nodes. In one embodiment, the one or more gNB-CUs may comprise, without limiting to, the SN CU 204.

[0107] At step 710, the SN CU 204 may identify at least one SN DU, communicating with the SN CU 204, comprising at least one candidate PScell. In one embodiment, the at least one SN DU may bethe second SN DU. In a non-limiting embodiment, the at least one SN DU may be the SN DU 208. The SN CU 204 may transmit a UE context setup request to the SN DU 208.

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

[0109] At step 714, at any point of time after the DC has been configured at the LIE 104, the SN CU 204 may transmit the mobility configuration indication to the MN CU 202. The mobility configuration indication may include, without limiting to, an acknowledgement to the S-node addition request. The mobility configuration indication may indicate that the SN CU 204 has enabled LTM for the UE 104.

[0110] At step 716, the MN CU 202 may transmit an RRC reconfiguration message to the UE 104. The RRC reconfiguration message may comprise, without limiting to, an SCG configuration for the UE 104. In an embodiment, the SCG configuration may indicate configuring the UE 104 with DC and indicating to the LIE 104 that the SN CU 204 may be the SN and to communicate with one or more cells of the SN DU 208 as the one or more PScells for the DC services.

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

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

[0113] At step 722, the SN CU 204 may transmit an acknowledgement to the S-Node modification request.

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

[0115] At step 726, the SN CU 204 may transmit the one or more candidate Pcell configuration modifications and the one or more dependent sources to the SN DU 208 through the Fl interface. In one embodiment, the SN CU 204 may transmit the one or more candidate Pcell configuration modifications and the one or more dependent sources via a LIE Context Modification Request.

[0116] At step 728, the SN DU 208 may prepare the candidate PScell configuration based on the one or more candidate Pcell configuration modifications and the one or more dependent sources. The candidate PSceli configuration may be related to the at least one candidate PScell of the SN DU 208 to which the UE 104 may move from the serving PScell. The candidate PScell configuration may enable the UE 104 to autonomously switch from the serving Pcell to the candidate Pcell and from the serving PScell to the at least one candidate PScell simultaneously.

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

[0118] At step 732, the SN CU 204 may transmit the candidate PScell configuration to the UE 104. In one embodiment, the SN CU 204 may transmit the candidate PScell configuration over Signal Radio Bearer 3 (SRB3) of an RRC Reconfiguration message.

[0119] At step 734, the SN DU 208 may communicate with the UE 104 using one or more sub-steps for performing LTM for the UE 104. At a first sub-step, the UE 104 may transmit an LI measurement report to the SN DU 208, At a second sub-step, in response to the first sub-step, the SN DU 208 may transmit a Medium Access Control (MAC) Control Element (CE) indicating cell switch to the UE 104. The MAC CE may comprise, without limitation, a Cell Identifier (ID) of the at least one candidate PScell, a Random Access Channel (RACH) preamble and a beam ID. At a third sub-step, the UE 104 may request initiating a RACH procedure with the SN DU 208 to establish a connection between the UE 104 and the at least one candidate PScell.

[0120] At step 736, the SN DU 208, upon receiving the RACH procedure initiating request from the UE 104, may perform an autonomous successful LTM for the UE 104 even when the Pcell configurations are modified.

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

[0122] Fig. 8 illustrates an exemplary data flow diagram for enabling inter-node coordination for mobility of the UE 104, in accordance with an embodiment of the present disclosure.

[0123] The method 800 may be described in the general context of computers executable instructions.Generally, computer executable instructions can include routines, programs, objects, components, datastructures, procedures, modules, and functions, which perform specific functions or implement specific abstract data tvoes.

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

[0125] The method 800 describes a sequence of steps for enabling the SN CU 204 to initiate a mobility configuration request to provide the one or more candidate Pcell configuration modifications upon detecting the mobility of the UE 104 between at least two Pcells thereby requiring a modification of corresponding one or more PScells, such as, but not limited to, the at least one candidate PScell.

[0126] The steps 802-812 of the method 800 are similar to the steps 702-712 respectively of the method 700 as described above and hence description of the same is avoided for brevity of disclosure.

[0127] At step 814, the SN GET 204 may acknowledge the S-Node addition request received from the MN CU 202 at step 808.

[0128] At step 816, the MN CU 202 may transmit the RRC reconfiguration message to the UE 104. The RRC reconfiguration message may comprise, without limiting to, an SCG configuration for the UE 104. In an embodiment, the SCG configuration may indicate configuring the UE 104 with DC and indicating to the UE 104 that the SN CU 204 may be the SN and to communicate with one or more cells of the SN DU 208 as the one or more PScells for DC services.

[0129] At step 818, the SN CU 204 may enable LTM for the UE 104 and detect a mobility of the UE 104 between two Pcells based on the mapping between the plurality of Pcells and the plurality of PScells. The SN CU 204 may subsequently determine if the mobility requires any modifications in corresponding PScells.

[0130] At step 820, the SN CU 204 may transmit the mobility configuration request indication “S- node modification required” to the MN CU 202, thereby triggering a request to the MN CU 202 to determine and share the one or more candidate Pcell configuration modifications corresponding to the at least one candidate PScell.

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

[0132] The steps 824-838 of the method 800 are similar to the steps 724-738 respectively of the method 700 as described above and hence description of the same is avoided for brevity of disclosure.

[0133] Fig. 9 illustrates an exemplary data flow diagram for enabling inter-node coordination for mobility of the UE 104, in accordance with an embodiment of the present disclosure.

[0134] The method 900 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform specific functions or implement specific abstract data types.

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

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

[0137] The steps 902-906 of the method 900 are similar to the steps 702-706 of the method 700 respectively as described above and hence description of the same is avoided for brevity of disclosure.

[0138] At step 908, the CU 202 may detect that the UE 104 is moving between at least two Pcells of the MN DU 206 that may require modifications to the at least one candidate PScell and may determine the one or more candidate Pcell configuration modifications. Further, the CU 202 may transmit the UE Context Setup Request to the SN DU 208. The UE Context Setup Request may comprise the one or more candidate Pcell configuration modifications.

[0139] Further, the steps 910-920 of the method 900 are similar to the steps 728-738 of the method 700 respectively as described above and hence description of the same is avoided for brevity of disclosure.

[0140] Fig. 10 illustrates an exemplary' flowchart of a method for enabling inter-node coordination for mobility of the UE 104, in accordance with an embodiment of the present disclosure.

[0141] The method 1000 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform specific functions or implement specific abstract data types.

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

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

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

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

[0146] Fig. 11 illustrates an exemplary flowchart of a method for enabling inter-node coordination for mobility of the UE 104, in accordance with another embodiment of the present disclosure.

[0147] The method 1100 may be described in the general context of computer executable instructi ons. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform specific functions or implement specific abstract data types.

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

[0149] At step 1 102, the SN CU 204 may receive one or more candidate Pcell configuration modifications from the MN CU 202. The one or more candidate Pceli configuration modifications may indicate one or more modifications to the at least one candidate PSceil corresponding to the Pceil change of the I JE 104.

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

[0151] Fig. 12 illustrates an exemplary’ flowchart of a method for enabling inter-node coordination for mobility of the UE 104, in accordance with yet another embodiment of the present disclosure.

[0152] The method 1200 may be described in the general context of computers executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform specific functions or implement specific abstract data types.

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

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

[0155] At step 1204, the SN DU 208 may generate the candidate PScell configuration based at least on the one or more candidate Pcell configuration modifications.

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

[0157] Fig. 13 illustrates an exemplary flowchart of a method for enabling inter-node coordination for mobility of the UE 104, in accordance with yet another embodiment of the present disclosure.

[0158] The method 1300 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform specific functions or implement specific abstract data types.

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

[0160] At step 1302, the 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 the at least one candidate PScell corresponding to the Pcell change of the UE 104.

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

[0162] Fig. 14 shows an exemplary illustration of a device 1400 for enabling inter-node coordination for mobility of the UE 104, in accordance with yet another embodiment of the present disclosure.

[0163] As shown in Fig. 14, the device 1400 may include, without limiting to, a processor 1410, a memory 1420, a storage component 1430, an input component 1440, an output component 1450, a communication interface 1460, and a bus 1470.

[0164] The processor 1410, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 1410 may be embodied as a multicore 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, or the like. The 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 a non-transitory computer readable medium. Memory 1420 includes a random-access memory (RAM), a read only memory (ROM), and / or another type of dynamic or static storage device (e.g., a flash memory’, a magnetic memory, and / or an optical memory) that stores information and / or instructions for use by processor 1410. The memory 1420 comprises machine- readable instructions which are executable by the processor 1410. These machine-readable instructions when executed by the processor 1410 cause the processor 1410 to perform one or more method steps of an embodiment described above.

[0166] Storage component 1430 stores information and / or software related to the operation and use of the device 1400. For example, storage component 1430 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium, along with a corresponding drive.

[0167] Input component 1440 is configured to receive information, such as user input. For example, the input component 1440 may include, but not be limited to, a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone. Additionally, or alternatively, the input component 1440 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).

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

[0169] Communication interface 1460 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the 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 that exists between the device 1400 and other devices. In other words, the standard of the communication interface 1460 is not limited.

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

[0171] The number and arrangement of components shown in Fig. 14 are provided as an example. In practice, device 1400 may include additional components, fewer components, different components, or differently arranged components than those shown in Fig. 14. 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. Further, one or more method steps described in any of the embodiments may be performed utilizing a plurality of devices 1400 in communication with one another.

[0172] [Clause 1] In an 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 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 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 further configured to transmit the one or more candidate Pcell configuration modifications to the SN CU for generating PScell configuration of the at least one candidate PScell based on the one or more candidate Pcell configuration modifications for facilitating mobility of the UE from a seiwing PScell to the at least one candidate PScell.

[0173] [Clause 2] In an aspect, the system of clause 1, wherein the MN CU communicates with at least a first MN Distributed Unit (DU) and a second MN DU. The one or more candidate Pcell configuration modifications comprise one or more modificati ons to one or more shared resources of the one or more candidate Pcells compared to a serving Pcell. The Pcell change indicates the mobility of the UE from the serving Pcell to a 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. The serving PScell and the serving Pcell are within a serving coverage range of the first MN DU and the candidate Pcell and the at least one candidate PScell are within the serving coverage range of the second MN DU.

[0174] [Clause 3] In an aspect, the system of clause 1 or clause 2, wherein the one or more SN DUs comprises one of a DU comprising the serving cell and the at least one candidate PScell; and a first DU comprising the serving ceil and a second DU comprising the at least one candidate PSceil.

[0175] [Clause 4] In an aspect, the system of any of the preceding clauses, wherein the mobility configuration indication is received upon establishing a dual connectivity at the UE or later. The mobility configuration indication indicates enabling or disabling the mobility for a UE, at the SN CU.

[0176] [Clause 5] In an aspect, the system of clause 2, wherein the one or more shared resources comprises at least one of one or more frequencies, one or more frequency bands, one or more band combinations, one or more carriers shared between the MN CU and the SN CU. The one or more candidate Peel! configuration modifications further comprise one or more dependent resources. The one or more dependent resources comprise at least one security key of the first MN DU and the second MN DU of the MN CU.

[0177] [Clause 6] In an aspect, the system of clause any of the preceding clauses, further configured to transmit the one or more candidate Pcell configuration modifications to a plurality of CUs that are 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 avoiding negotiation of one or more shared resources during configuring one of Dual Connectivity and a layer 1 / layer 2 triggered mobility at the UE.

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

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

[0180] [Clause 9] In an aspect, the system of clause 8, wherein to detect the mobility, the SN CU is configured to identify the Pcell change, corresponding to the at least one candidate PScell, based on a served cell information of at least the first MN DU and the second MN DU. The served cell information is received during an Xn setup procedure.

[0181] [Clause 10] In an aspect, the system of clause 8, wherein to detect the mobility, the SN CU is configured to determine a mapping between the at least one candidate PScell of the SN CU and the one or more candidate Pcells. The SN CU is configured to predict the one or more candidate Pcell configuration modifications corresponding to the at least one candidate PScell, using a machine learning model, based on the mapping of the one or more candidate Pcells and the at least one candidate PScell.

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

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

[0184] [Clause 13] In an aspect, the system of any of clauses 6-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. The at least one SN DU is further configured to generate the PScell configuration based on the one or more candidate Pcell configuration modifications and the one or more dependent resources.

[0185] [Clause 14] In an aspect, the system of any of clauses 6-12, wherein the at least one SN DU is further configured to generate a plurality of PScell configurations corresponding to a plurality of candidate Pcells. The at least one candidate PScell overlaps with the plurality of candidate Pcells. The at least one SN DU is further configured to transmit the plurality of PScell configurations to the UE for facilitating the UE to select at least one of the plurality of PScell configurations based on a serving Pcell.

[0186] [Clause 15] In an aspect, a method is disclosed. The method comprises 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 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 comprises determining 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 method comprises transmitting the one or more candidatePcell configuration modifications to the SN CU for generating PScell configuration of the at least one candidate PScell based on the one or more candidate Pcell configuration modifications for facilitating mobility of the UE from a serving PScell to the at least one candidate PScell.

[0187] [Clause 16] In an aspect, the method of clause 15, wherein the MN CU communicates with at least a first MN Distributed Unit (DU) and a second MN DU. The one or more candidate Pcell configuration modifications comprise one or more modifications to one or more shared resources of the one or more candidate Pcells compared to a serving Pcell. The Pcell change indicates the mobility of the UE from the serving Pcell to a 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. The seiwing PScell and the serving Pcell are within a seiwing coverage range of the first MN DU and the candidate Pcell and the at least one candidate PScell are within the serving coverage range of the second MN DU.

[0188] [Clause 17] In an aspect, the method of clause 15 or clause 16, wherein the mobility configuration indication is received upon establishing a dual connectivity at the UE or later. The mobility configuration indication indicates enabling or disabling the mobility for a UE, at the SN CU.

[0189] [Clause 18] In an aspect, the method of clause 16, wherein the one or more shared resources comprises at least one of one or more frequencies, one or more frequency bands, one or more band combinations, one or more earners shared between the MN CU and the SN CU. The one or more candidate Pcell configuration modifications further comprise one or more dependent resources. The one or more dependent resources comprise at least one security key of the first MN DU and the second MN DU of the MN CU.

[0190] [Clause 19] In an aspect, the method of clause any of the preceding clauses, further comprises transmitting the one or more candidate Pcell configuration modifications to a plurality of CUs that are 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 avoiding negotiation of one or more shared resources during configuring one of Dual Connectivity and a layer 1 / layer 2 triggered mobility at the UE.

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

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

[0193] [Clause 22] In an aspect, the method of clause 21 , wherein the detecting comprises identifying the Pcell change, corresponding to the at least one candidate PScell, based on a served cell information of at least the first MN DU and the second MN DU, wherein the served cell information is received during an Xn setup procedure.

[0194] [Clause 23] In an aspect, the method of clause 21, wherein the method of detecting comprises determining a mapping between the at least one candidate PScell of the SN CU and the one or more candidate Pcells. The method further comprises predicting the one or more candidate Pcell configuration modifications corresponding to the at least one candidate PScell, using a machine learning model, based on the mapping of the one or more candidate Pcells and the at least one candidate PScell.

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

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

[0197] [Clause 26] In an aspect, the method of clause 25 further comprises receiving one or more dependent resources from the SN CU for generating the PScell configuration. The method further comprises generating the PScell configuration based on the one or more candidate Pcell configuration modifications and the one or more dependent resources.

[0198] [Clause 27] In an aspect, the method of clause 25 further comprises generating a plurality of PScell configurations corresponding to a plurality of candidate Pcells, wherein the at least one candidate PScell overlaps with the plurality of candidate Pcells. The method further comprises transmitting the plurality of PScell configurations to the UE for facilitating the UE to select at least one of the plurality of PScell configurations based on a serving Pcell.

[0199] [Clause 28] In an aspect, a non-transitory computer-readable medium having program instructions stored thereon is disclosed. The program instructions comprise 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 modifications indicate one or more modifications to at least one candidate Primary Secondary ceil (PScell) corresponding to a Pcell change of a User Equipment (UE). The program instructions comprise determining 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 program instructions comprise transmitting the one or more candidate Pcell configuration modifications to the SN CU for generating PScell configuration of the at least one candidate PScell based on the one or more candidate Pcell configuration modifications for facilitating mobility of the UE from a serving PScell to the at least one candidate PScell.

[0200] [Clause 29] In an aspect, the non-transitory computer readable medium of clause 28, wherein the MN CU communicates with at least a first MN Distributed Unit (DU) and a second MN DU. The one or more candidate Pcell configuration modifications comprise one or more modifications to one or more shared resources of the one or more candidate Pcells compared to a serving Pcell. The Pcell change indicates the mobility of the UE from the serving Pcell to a 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. The serving PScell and the serving Pcell are within a serving coverage range of the first MN DU and the candidate Pcell and the at least one candidate PScell are within the serving coverage range of the second MN DU.

[0201] [Clause 30] In an aspect, the non-transitory computer readable medium of clauses 28 or 29, wherein the mobility configuration indication is received upon establishing a dual connectivity at theUE or later. The mobility configuration indication indicates enabling or disabling the mobility for aUE, at the SN CU.

[0202] [Clause 31] In an aspect, the non-transitory computer readable medium of any of the clauses 28-30, the one or more shared resources comprises at least one of one or more frequencies, one or more frequency bands, one or more band combinations, one or more carriers shared between the MN CU and the SN CU. The one or more candidate Pcell configuration modifications further comprise one or more dependent resources. The one or more dependent resources comprise at least one security key of the first MN DU and the second MN DU of the MN CU.

[0203] [Clause 32] In an aspect, the non-transitory computer readable medium of any of the clauses 28-31, wherein the program instructions further comprise transmitting the one or more candidate Pcell configuration modifications to a plurality of CUs that are 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 avoiding negotiation of one or more shared resources during configuring one of Dual Connectivity and a layer 1 / layer 2 triggered mobility at the UE.

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

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

[0206] [Clause 35] In an aspect, the non-transitory computer readable medium of the clause 34, wherein the program instructions for the detecting comprise identifying the Pcell change, corresponding to the at least one candidate PScell, based on a served cell information of at least the first MN DU and the second MN DU. The served cell information is received during an Xn setup procedure.

[0207] [Clause 36] In an aspect, the non-transitory computer readable medium of the clause 34, wherein the program instructions for the detecting comprise determining a mapping between the at least one candidate PScell of the SN CU and the one or more candidate Pcells. The program instructions further comprise predicting the one or more candidate Pcell configuration modifications corresponding to the at least one candidate PScell, using a machine learning model, based on the mapping of the one or more candidate Pcells and the at least one candidate PScell.

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

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

[0210] [Clause 39] In an aspect, the non-transitory computer readable medium of the clause 38, wherein the program instructions further comprise receiving one or more dependent resources from the SN CU for generating the PScell configuration. The program instructions further comprise generating the PScell configuration based on the one or more candidate Pcell configuration modifications and the one or more dependent resources.

[0211] [Clause 40] In an aspect, the the non-transitory computer readable medium of the clause 38, wherein the program instructions further comprise generating a plurality of PScell configurations corresponding to a plurality of candidate Pcells, wherein the at least one candidate PScell overlaps with the plurality of candidate Pcells. The program instructions further comprise transmitting the pluralityof PScell configurations to the UE for facilitating the UE to select at least one of the plurality of PScell configurations based on a serving Pcell.

[0212] [Clause 41] In an aspect, a system is disclosed. The system is configured to determine one or more candidate Primary cell (Pcell) configuration modifications based on a Pcell change based on an overlap of one or more candidate Pcells of a first Master Node (MN) Distributed Unit (DU) of the Control Unit (CU) with at least one candidate PScell of at least one Secondary Node (SN) DU of the CU. 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 the one or more candidate Pcell configuration modifications to the at least one SN DU for generating PScell configuration of the at least one candidate PScell based on the one or more candidate Pcell configuration modifications for facilitating the mobility of the UE from a serving PScell to the at least one candidate PScell.

[0213] [Clause 42] In an aspect, the system of clause 41, wherein the one or more candidate Pcell configuration modifications comprise one or more modifications to one or more shared resources of the one or more candidate Pcells compared to a serving Pcell. The Pcell change indicates the mobility of the UE from the serving Pcell to a candidate Pcell. The at least one candidate PScell is associated with at least one SN DU of one or more SN DUs. The serving PScell and the serving Pcell are within a serving coverage range of the first MN DU and the candidate Pcell and the at least one candidate PScell are within the serving coverage range of the second MN DU. The one or more SN DUs comprises one of a DU comprising the serving cell and the at least one candidate PScell and a first DU comprising the serving ceil and a second DU comprising the at least one candidate PScell.

[0214] [Clause 43] In an aspect, the system of clauses 41 or clause 42, wherein the one or more shared resources comprises at least one of one or more frequencies, one or more frequency bands, one or more band combinations, one or more carriers shared between the at least MN DU and the SN DU. The one or more candidate Pcell configuration modifications further comprise one or more dependent resources. The one or more dependent resources comprise at least one security key of the first MN DU and the second MN DU. The one or more candidate Pcell configuration modifications are transmitted to the at least one SN DU in a UE context setup request.

[0215] [Clause 44] In an aspect, a method is disclosed. The method comprises determining one or more candidate Primary cell (Pcell) configuration modifications based on a Pcell change based on an overlap of one or more candidate Pcells of a first Master Node (MN) Distributed Unit (DU) of the Control Unit (CU) with at least one candidate PScell of at least one Secondary Node (SN) DU of theCU. 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 comprises transmitting the one or more candidate Pcell configuration modifi cations to the at least one SN DU for generating PScell configuration of the at least one candidate PScell based on the one or more candidate Pcell configuration modifications for facilitating the mobility of the UE from a serving PScell to the at least one candidate PScell.

[0216] [Clause 45] In an aspect, the method of clause 44, wherein the one or more candidate Peel! configuration modifications comprise one or more modifications to one or more shared resources of the one or more candidate Pcells compared to a serving Pcell. The Pcell change indicates the mobility of the UE from the serving Pcell to a candidate Pcell. The at least one candidate PScell is associated with at least one SN DU of one or more SN DUs. The seiwing PScell and the serving Pcell are within a serving coverage range of the first MN DU and the candidate Pcell and the at least one candidate PScell are within the serving coverage range of the second MN DU. The one or more SN DUs comprises one of a DU comprising the serving cell and the at least one candidate PScell and a first DU comprising the serving cell and a second DU comprising the at least one candidate PScell.

[0217] [Clause 46] In an aspect, the method of clauses 44 or clause 45, wherein the one or more shared resources comprises at least one of one or more frequencies, one or more frequency bands, one or more band combinations, one or more carriers shared between the at least MN DU and the SN DU. The one or more candidate Pcell configuration modifications further comprise one or more dependent resources. The one or more dependent resources comprise at least one security key of the first MN DU and the second MN DU. The one or more candidate Pcell configuration modifications are transmitted to the at least one SN DU in a UE context setup request.

[0218] [Clause 47] In an aspect, a non-transitory computer readable medium having program instructions stored thereon is disclosed. The program instructions comprise determining one or more candidate Primary cell (Pcell) configuration modifications based on a Pcell change based on an overlap of one or more candidate Pcells of a first Master Node (MN) Distributed Unit (DU) of the Control Unit (CU) with at least one candidate PScell of at least one Secondary Node (SN) DU of the CU. 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 comprise transmitting the one or more candidate Pcell configuration modifications to the at least one SN DU for generating PScell configuration of the at least one candidate PScell based on the one or more candidate Pcell configuration modifications for facilitating the mobility of the UE from a serving PScell to the at least one candidate PScell.

[0219] [Clause 48] In an aspect, the non-transitory computer readable medium of clause 47, wherein the one or more candidate Pcell configuration modifications comprise one or more modifications to one or more shared resources of the one or more candidate Pcells compared to a serving Pcell. The Pcell change indicates the mobility of the UE from the serving Pcell to a candidate Pcell. The at least one candidate PScell is associated with at least one SN DU of one or more SN DUs. The serving PScell and the saving Pcell are within a serving coverage range of the first MN DU and the candidate Pcell and the at least one candidate PScell are within the serving coverage range of the second MN DU. The one or more SN DUs comprises one of a DU comprising the serving cell and the at least one candidate PScell and a first DU comprising the serving cell and a second DU comprising the at least one candidate PScell.

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

[0221] The illustrated steps are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope of the disclosed embodiments.

[0222] Also, the words "comprising," "having," "containing," and "including," and other similar forms are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items or meant to be limited to only the listed item or 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 clearly dictates otherwise. Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, the disclosure of the embodiments of the disclosure is intended to be illustrative, but not limiting, of the scope of the disclosure. With respect to the use ofsubstantially any plural and / or singular terms herein, those having skill in the art can translate from the plural to the singular and / or from the singular to the plural as is appropriate to the context and / or application. The various singular / plural permutations may be expressly set forth herein for sake of clarity.

[0223]

Claims

Claims:

1. 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, wherein 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); 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; and transmit the one or more candidate Pcell configuration modifications to the SN CU for generating PScell configuration of the at least one candidate PScell based on the one or more candidate Pcell configuration modifications for facilitating mobility of the UE from a serving PScell to the at least one candidate PScell.

2. The system of claim 1, wherein the MN CU communicates with at least a first MN Distributed Unit (DU) and a second MN DU, wherein the one or more candidate Pcell configuration modifications comprise one or more modifications to one or more shared resources of the one or more candidate Pcells compared to a serving Pcell, wherein the Pcell change indicates the mobility of the UE from the serving Pcell to a candidate Pcell, wherein 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 wherein the serving PScell and the serving Pcell are within a serving coverage range of the first MN DU and the candidate Pcell and the at least one candidate PScell are within the serving coverage range of the second MN DU.

3. The system of claim 2, wherein the one or more SN DUs comprises one of: a DU comprising the serving PScell and the at least one candidate PScell; and a first DU comprising the serving PScell and a second DU comprising the at least one candidate PScell.

4. The system of claim 1, wherein the mobility configuration indication is received upon establishing a dual connectivity at the UE or later, wherein the mobility configuration indication indicates enabling or disabling the mobility for the UE, at the SN CU.

5. The system of claim 2, wherein the one or more shared resources comprise at least one of one or more frequencies, one or more frequency bands, one or more band combinations, one or more carriers shared between the MN CU and the SN CU, and wherein the one or more candidate Pcell configuration modifications further comprise one or more dependent resources, wherein the one or more dependent resources comprise 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: transmit the one or more candidate Pcell configuration modifications to a plurality of CUs that are eligible to be configured as a plurality of SN CUs using a non-UE associated message, wherein the non-UE associated message is a Next Generation Radio Access Network (NG-RAN) node configuration update message, wherein the non-UE associated message indicates avoiding negotiation of one or more shared resources during configuring one of Dual Connectivity and a layer 1 / layer 2 triggered mobility 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 transmit the one or more candidate Pcell configuration modifications to the at least one SN DU, wherein the one or more candidate Pcell configuration modifications are transmitted to the at least one SN DU in a UE context setup request.

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

9. The system of claim 8, wherein to detect the mobility, the SN CU is configured to:identify the Pcell change, corresponding to the at least one candidate PScell, based on a served cell information of at least the first MN DU and the second MN DU, wherein the served cell information is received during an Xn setup procedure.

10. The system of claim 8, wherein to detect the mobility, the SN CU is configured to: determine a mapping between the at least one candidate PScell of the SN CU and the one or more candidate Pcells; and predict the one or more candidate Pcell configuration modifications corresponding to the at least one candidate PScell, using a machine learning model, based on the mapping of the one or more candidate Pcells and the at least one candidate PScell.

11. The system of claim 7, wherein the SN CU is further configured to: derive one or more dependent resources for the at least one candidate PScell based on the one or more candidate Pcell configuration modifications in response to receiving the one or more candidate Pcell configuration modifications, wherein the one or more dependent resources for the at least one candidate PScell comprise at least one security key; and transmit the one or more dependent resources 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 SN DU, the at least one SN DU is configured to: receive the one or more candidate Pcell configuration modifications from the SN CU, wherein the one or more candidate Pcell configuration modifications are received in the UE context setup request from the SN CU; generate the candidate PScell configuration based at least on the one or more candidate Pcell configuration modifications; and perform the mobility of the UE from the serving PScell to the at least one candidate PScell based on the candidate PScell configuration.

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 generate the PScell configuration 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 a plurality of PScell configurations corresponding to a plurality of candidate Pcells, wherein the at least one candidate PScell overlaps with the plurality of candidate Pcells; and transmit the plurality of PScell configurations to the UE for facilitating the UE to select at least one of the plurality of PScell configurations based on a serving Pcell.

15. 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, wherein 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); determining 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; and transmitting the one or more candidate Pcell configuration modifications to the SN CU for generating PScell configuration of the at least one candidate PScell based on the one or more candidate Pcell configuration modifications for facilitating mobility of the UE from a serving PScell to the at least one candidate PScell.

16. The method of claim 15, wherein the MN CU communicates with at least a first MN Distributed Unit (DU) and a second MN DU, wherein the one or more candidate Pcell configuration modifications comprise one or more modifications to one or more shared resources of the one or more candidate Pcells compared to a serving Pcell, wherein the Pcell change indicates the mobility of the UE from the serving Pcell to a candidate Pcell, wherein 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 wherein the serving PScell and the serving Pcell are within a saving coverage range of the first MN DU and the candidate Pcell and the at least one candidate PScell are within the serving coverage range of the second MN DU.

17. The method of claim 15, wherein the mobility configuration indication is received upon establishing a dual connectivity at the UE or later, wherein the mobility configuration indication indicates enabling or disabling the mobility for the UE, at the SN CU.

18. The method of claim 16, wherein the one or more shared resources comprise at least one of one or more frequencies, one or more frequency bands, one or more band combinations, one or more carriers shared between the MN CU and the SN CU, and wherein the one or more candidate Pcell configuration modifications further comprise one or more dependent resources, wherein the one or more dependent resources comprise 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 comprises: transmitting the one or more candidate Pcell configuration modifications to a plurality of CUs that are eligible to be configured as a plurality of SN CUs using a non-UE associated message, wherein the non-UE associated message is a Next Generation Radio Access Network (NG-RAN) node configuration update message, wherein the non-UE associated message indicates avoiding negotiation of one or more shared resources during configuring one of Dual Connectivity and a layer 1 / layer 2 triggered mobility at the UE.

20. The method of claim 15, wherein in response to transmitting the one or more candidate Pcell configuration modifications to the CU, the method at the SN CU further comprises: receiving the one or more candidate Pcell configuration modifications from the MN CU; and transmitting the one or more candidate Pcell configuration modifications to the at least one SN DU, wherein the one or more candidate Pcell configuration modifications are transmitted to the at least one SN DU in a UE context setup request.

21. The method of claim 20, wherein receiving the one or more candidate Pcell configuration modifications comprises: detecting the mobility of the UE; and transmitting the mobility configuration request, to the MN CU, to determine the one or more candidate Pcell configuration modifications corresponding to the at least one candidatePScell.

22. The method of ciaim 21, wherein the detecting comprises: identifying the Pceli change, corresponding to the at least one candidate PSceli, based on a served ceil information of at least the first MN DU and the second MN DU, wherein the served cell information is received during an Xn setup procedure.

23. The method of claim 21, wherein the detecting comprises: determining a mapping between the at least one candidate PScell of the SN CU and the one or more candidate Pceils; and predicting the one or more candidate Pceli configuration modifications corresponding to the at least one candidate PScell, using a machine learning model, based on the mapping of the one or more candidate Pceils and the at least one candidate PScell.

24. The method of claim 20, the method further comprises: deriving one or more dependent resources for the at least one candidate PSceli based on the one or more candidate Pceli configuration modifications in response to receiving the one or more candidate Pceli configuration modifications, wherein the one or more dependent resources for the at least one candidate PScell comprise at least one security key; and transmitting the one or more dependent resources 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 Pceli configuration modifications to the at least one SN DU, the method at the at least one SN DU further comprises: receiving the one or more candidate Pceli configuration modifications from the SN CU, wherein the one or more candidate Pceli configuration modifications are received in the UE context setup request from the SN CU; generating the candidate PScell configuration based at least on the one or more candidate Pceli configuration modifications; and performing the mobility of the UE from the serving PScell to the at least one candidate PScell based on the candidate PScell configuration.

26. The method of claim 25 further comprises: receiving one or more dependent resources from the SN CU for generating the PScell configuration; andgenerating the PSceli configuration based on the one or more candidate Pceli configuration modifications and the one or more dependent resources.

27. The method of claim 25 further comprises: generating a plurality of PScell configurations corresponding to a plurality of candidate Pcells, wherein the at least one candidate PScell overlaps with the plurality of candidate Pcells; and transmitting the plurality of PScell configurations to the UE for facilitating the UE to select at least one of the plurality of PScell configurations based on a serving Pceli.

28. A non-transitory computer-readable medium having program instructions stored thereon, wherein the program instructions comprise: 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 (Pceli) configuration modifications, wherein the one or more candidate Pceli configuration modifications indicate one or more modifications to at least one candidate Primary Secondary cell (PScell) corresponding to a Pceli change of a User Equipment (UE); determining the one or more candidate Pceli 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; and transmitting the one or more candidate Pceli configuration modifications to the SN CU for generating PScell configuration of the at least one candidate PScell based on the one or more candidate Pceli configuration modifications for facilitating mobility of the UE from a serving PScell to the at least one candidate PScell.

Images