Network node, communication device and method for handling multi-hop configurations in wireless communication networks

Abstract

In a wireless communication network (500), a network node and a method thereof are provided for handling a multi-hop configuration of conditional primary-secondary cell change or primary-secondary cell group cell change (CPC) for communication devices (530, 531) configured with a dual connection of a master cell group (MCG) managed by a first network node (511) and a secondary cell group (SCG) managed by a second network node (512). Different solutions for enabling a multi-hop CPC configuration and implementations of these solutions are disclosed from the perspectives of the first network node (511), the second network node (512), the target candidate network node, and the communication devices (530, 531).

Description

[Technical Field]

[0001] The present embodiments relate to network nodes, communication devices and methods therefor, and in particular to handling multi-hop conditional primary secondary cell (PSCell) or primary secondary cell group cell change (CPC) configuration for communication devices operating in dual connectivity with a master cell group (MCG) and a secondary cell group (SCG) in a wireless communication network. [Background technology]

[0002] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STAs) and / or user equipment (UEs), communicate with one or more core networks (CNs) via a radio access network (RAN). The RAN covers a geographical area that is divided into service areas or cell areas, which may be referred to as beams or beam groups, and each service area or cell area is served by a radio network node, such as a radio access node, e.g., a Wi-Fi access point or radio base station (RBS), which may be referred to as a "NodeB" or "eNodeB" or "gNB" depending on the network. A service area or cell area is a geographical area where radio coverage is provided by a radio network node. The radio network node communicates with wireless devices within range of the radio network node over an air interface operating on radio frequencies.

[0003] The Universal Mobile Telecommunications System (UMTS) is a third-generation (3G) telecommunications network that evolved from the second-generation (2G) Global System for Mobile Communication (GSM). Fourth-generation (4G) networks or Long Term Evolution (LTE)The standardization of the Evolved Packet System (EPS), also known as the 5G (5G Mobile Radio) Network (5G), has been completed within the 3rd Generation Partnership Project (3GPP), and this work will be used in future 3GPP releases, such as the specification of the 5th Generation (5G) New Radio (NR) networks. and future releases Continued in.

[0004] 3GPP Dual Connectivity 3GPP Release 12 introduced the LTE feature Dual Connectivity (DC), allowing a UE to connect to two cell groups, each controlled by an eNB, an LTE access node known as the Master eNB (MeNB) and a Secondary eNB (SeNB). The UE still has only one Radio Resource Control (RRC) connection with the network. 3GPP has since evolved the Dual Connectivity (DC) solution and now specifies it for NR and between LTE and NR. With the introduction of 5G, the term Multi-Radio Dual Connectivity (MR-DC) (see also 3GPP TS37.340) was defined as a general term for all dual connectivity options involving at least one NR access node. Using the generalized term MR-DC, a UE connects to a Master Cell Group (MCG) controlled by a Master Node (MN) and a Secondary Cell Group (SCG) controlled by a Secondary Node (SN).

[0005] Furthermore, in MR-DC, when dual connectivity is configured for a UE, carrier aggregation can also be used in each of the two cell groups, MCG and SCG. In this case, in the MCG controlled by the master node (MN), the UE may use one primary cell (Pcell) and one or more secondary cells (SCells). And, in the SCG controlled by the secondary node (SN), the UE may use one primary SCell (PSCell) (also known as a primary SCG cell in NR) and one or more SCells. This combined case, i.e., dual connectivity combined with carrier aggregation in MR-DC, is shown in Figure 1, which shows a master node (MN) 110, a secondary node (SN) 120, a UE 130, a master cell group (MCG) 140, a secondary cell group (SCG) 150, a primary cell (PCell) 160 in the MCG 140, a primary SCell (PSCell) 170 in the SCG 150, and multiple SCells. In NR, a primary cell of a master cell group or a secondary cell group is also called a special cell (SpCell). Therefore, an SpCell in an MCG is a PCell, and an SpCell in an SCG is a PSCell.

[0006] There are various ways to deploy 5G networks, with or without interworking with LTE, also known as Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC). In principle, NR and LTE can be deployed without interworking, denoted as NR Standalone (SA) operation, also known as Option 2. That is, NR gNBs can be connected to the 5G Core Network (5GC) and LTE eNBs can be connected to the EPC without interconnection between the two (also known as Option 1).

[0007] On the other hand, the first supported version of NR will use dual connectivity, also known as Option 3, called Evolved Universal Terrestrial Radio Access Network-NR (E-UTRAN-NR) Dual Connectivity (EN-DC), as shown in Figure 2. In such a deployment, dual connectivity between NR and LTE will be applied, and the UE 210 will communicate over the LTE air interface. ( LTE Uu ) The EN-DC is connected to both an LTE access node (LTE MeNB) 220 with a NR radio interface (NR Uu) 221 and an NR access node (NR SgNB) 230 with an NR radio interface (NR Uu) 231. Furthermore, in the EN-DC, the LTE access node acts as the master node, known as the master eNB (MeNB) in this case, controlling the master cell group (MCG), and the NR access node acts as the secondary node, also known as the secondary gNB (SgNB) in this case, controlling the secondary cell group (SCG). The SgNB, in this case NR, may not have a control plane connection to the core network (EPC 240) and is instead provided by the MeNB. This is also referred to as "non-standalone NR," or "NSA NR" for short. In this case, the NR cells have limited functionality and are used as booster and / or diversity legs for connected mode UEs; however, note that UEs in RRC_IDLE that are powered on but do not have an established RRC connection cannot camp on these NR cells.

[0008] With the introduction of 5GC, other options may become available. As mentioned above, Option 2 supports standalone NR deployments where a gNB is connected to 5GC. Similarly, LTE can also connect to 5GC using Option 5, also known as eLTE, E-UTRA / 5GC, or LTE / 5GC, and the node is also referred to as ng-eNB. In these cases, both NR and LTE are considered part of the NG-RAN, and both the ng-eNB and gNB may be referred to as NG-RAN nodes.

[0009] There are other variations of dual connectivity between LTE and NR that have been standardized as part of NG-RAN connected to 5GC. These fall under the umbrella of MR-DC: EN-DC (Option 3): LTE is the master node, NR is the secondary node, and EPC CN is used, as shown in Figure 2. NE-DC (Option 4): NR is the master node, LTE is the secondary node, and 5GCN is used. NGEN-DC (Option 7): LTE is the master node, NR is the secondary node, and 5GCN is used. · NR-DC (variant of option 2): As shown in Figure 3, this is a dual connection where both the Master Node (MN) controlling the MCG and the Secondary Node (SN) controlling the SCG use NR 5GCN.

[0010] Conditional PSCell Change (CPC) in 3GPP Release-16 A solution for the CPC procedure was also standardized in Release 16. There, in a conditional reconfiguration, a UE operating in Multi-Radio Dual Connectivity (MR-DC) receives one or more RRC reconfigurations (e.g., RRCReconfiguration messages) containing SCG configurations, such as secondaryCellGroup in the CellGroupConfig information element (IE), along with reconfigurationWithSync, which is associated with and stored as an execution condition (such as an A3 / A5 event configuration). As a result, one of the stored messages is applied only if an execution condition associated with the serving PSCell is met, e.g., the UE performs a PSCell change if it finds a neighbor cell that is better than the current SpCell in the SCG. 3GPP Rel-16 standardizes only intra-SN CPC without MN involvement, i.e., when the target PSCell candidate is within the current serving SN.

[0011] Similar to a conditional handover, a random access is performed to the target PSCell and if the UE is configured with a CPC, the UE releases all stored conditional reconfigurations.

[0012] Conditional PSCell Addition (CPA) and Inter-SN CPC in 3GPP Rel-17: In 3GPP Rel-17, CPA and inter-SN CPC solutions are being considered and introduced. The CPA procedure is used to add a PSCell / SCG to a UE configuration that is currently configured with only an MCG, provided the associated execution conditions are met. CPA is initiated by the MN by requesting an SCG configuration from a target SN candidate (T-SN) to be provided as part of a conditional reconfiguration to the UE, and sending it to the UE in a conditional reconfiguration together with the associated execution conditions.

[0013] Inter-SN CPC can be initiated by the MN or the source SN (S-SN), and signaling towards the source SN and target SN candidates, and signaling towards the UE, are handled by the MN in both cases. As shown in the signaling flow of Figure 4 illustrating Inter-SN CPC in 3GPP Rel-17, one possible signaling sequence for configuring Inter-SN CPC is initiated by the source SN.

[0014] Also, in Rel-17 Conditional PSCell Change (CPC) / Conditional PSCell Addition (CPA), when completing random access to the target PSCell, a UE configured with CPC / CPA must release the CPC / CPA configuration.

[0015] NR-DC selective activation of cell groups (at least SCGs) via L3 extensions of 3GPP Rel-18: In 3GPP Rel-18, RP-213565 (New WI: Further NR mobility enhancements, MediaTek, 3GPP TSG RAN Meeting #94e, December 6-17, 2021) In the work item description of Work has begun to introduce extensions for different mobility procedures. One of the current objectives is to "specify mechanisms and procedures for NR-DC with selective activation of cell groups (at least SCGs) with L3 extensions," which includes "enabling subsequent cell group changes after CG changes without CPC / CPA reconfiguration and restart."

[0016] Therefore, after the first cell group change, the conditional PSCell change (CPC) or conditional PSCell addition (CPA) can be reconfigured or re-configured. start It should be possible to perform subsequent cell group changes without having to reconfigure the UE. This is done to reduce the disruption time and signaling overhead of SCG changes, especially in the case of frequent SCG changes when operating in NR Frequency Range 2 (FR2), compared to previous releases where these configurations were released when the UE completed its random access to the target PSCell.

[0017] Full and Delta configurations: As part of the mobility preparation to the target node, the source node sends the current UE configuration to the target node. The target node prepares a target configuration for the UE based on the current configuration and the capabilities of the target node and the UE. The target configuration is sent from the target node to the source node and then sent to the UE in an RRCReconfiguration. A reasonable option is to provide the target configuration as a so-called delta configuration, which only shows the differences from the UE's current configuration in the source cell.

[0018] However, in some cases, if the target node does not recognize something in the UE's current configuration, for example if the target node does not support some features that the source node supports, the target node will trigger a full configuration. A full configuration means that the UE clears its current configuration and creates a new configuration from scratch. This is further explained in TS38.331 V16.7.0 section 5.3.5.11 and is referred to as "full configuration" or "fullConfig".

[0019] The full configuration can also be used during mobility if the network node prefers to signal the entire UE target configuration instead of signaling the delta configuration towards the source cell, e.g. when building the delta configuration is complex.

[0020] In the following, the terms "communication device" and "UE" are used interchangeably. The terms "network node", "gNB", "eNB", and "gNodeB" are used interchangeably. Summary of the Invention [Problem to be solved by the invention]

[0021] As part of the development of the present embodiment, a problem was first identified and first described.

[0022] According to the 3GPP Rel-17 solution, the CPC is configured "one hop away", i.e., a UE operating in MR-DC and configured with cell A as the source cell can receive one or more RRC reconfigurations for one or more target cells, e.g., cell B and cell C. However, existing solutions do not support "multiple hops away" CPC configuration. Therefore, existing 3GPP Rel-17 solutions do not support the reconfiguration or re-configuration of the CPC. start Subsequent cell group changes with only one SCG change are possible, and frequent SCG changes, which can occur when operating in FR2 of NR, can result in significant disruption time and signaling overhead.

[0023] Therefore, it is an object of the present embodiment to provide an improved method for handling multi-hop CPC configuration of a UE or communication device. [Means for solving the problem]

[0024] This embodiment includes a different solution for configuring a UE with a CPC configuration including a configuration of a target candidate PSCell including an SCG configuration and an MCG configuration, which is applied when a first CPC execution condition is met, and the configuration for the target candidate PSCell also includes at least one embedded CPC configuration that is valid for that new PSCell.

[0025] Specifically, the solution addresses the following: - the action that the MN needs to take, - the action that the source SN needs to take, - the action that the target candidate SN needs to take, - the action the UE needs to take, -Conditional reconstruction content, such as whether it contains information about multiple CPC hops or a single CPC hop; - Signaling when MN participates in CPC configuration, - Signaling when MN is not involved in CPC configuration, - Signaling when the CPC at each hop is initiated by the MN, - Signaling when the CPC at each hop is initiated by the SN, - Signaling in a CPC configuration where one hop is initiated by the MN and the other hop is initiated by the SN; - Signaling in case of inter-CPC multi-hop configuration, -Signaling in case of intra-CPC multi-hop configuration, Signaling in the case of hybrid, e.g., inter-intra or intra-inter CPC multihop configurations

[0026] According to one aspect of this embodiment, the object is achieved by a first network node and a method thereof for processing multi-hop CPC of a communication device configured with a dual connection between an MCG managed by the first network node and an SCG managed by a second network node in a wireless communication network. The first network node sends a CPC request to a second network node or a first target candidate secondary node (SN), and receives a message from the second network node or the first target candidate SN in response to the CPC request. The message may include one or more of the following information: i. An indication that the CPC configuration is a multi-hop CPC configuration; ii. Whether it is time-critical to constitute the First CPC of Indication; iii. An indication of how many hops away it consists of; iv. Identifiers of one or more target candidate primary secondary cells (PSCells) for second-hop CPC configuration; v. Identifiers of one or more target candidate secondary nodes (T-SN2) associated with one or more target candidate PSCells.

[0027] The first network node configures a multi-hop CPC for the communication devices 530, 531 based on the received message.

[0028] According to one aspect of this embodiment, the object is achieved by a second network node and a method thereof for processing multi-hop CPC of a communication device configured with a dual connection between an MCG managed by a first network node and an SCG managed by a second network node in a wireless communication network. The second network node sends a CPC request to the first network node or the communication device. The CPC request may include one or more of the following information: Indication that multi-hop CPC is allowed; Indication of the maximum number of CPC hops allowed; · First-hop intra-SN CPC configuration; · Configuration of subsequent hop intra-SN CPC; · Configuring a second-hop inter-SN CPC to another target candidate SN; An indication of whether next CPC hop configuration is allowed.

[0029] According to one aspect of this embodiment, the object is achieved by a first target candidate secondary node and a method thereof for processing a multi-hop CPC of a communication device configured with a dual connection between an MCG managed by a first network node and an SCG managed by a second network node in a wireless communication network. The first target candidate secondary node receives a CPC request from the first network node, configures the multi-hop CPC by configuring the first-hop CPC and including information of a second-hop CPC, or by configuring the first-hop CPC and initiating configuration of a second-hop CPC for a second-candidate secondary node (T-SN2), and sends a response message to the first network node. The response message may include one or more of the following information: i. an indication that it is a multi-hop CPC configuration; ii. Identifiers of one or more target candidate cells for next or subsequent hop CPC configuration; iii. Identifiers of one or more target candidate SNs associated with one or more target candidate cells.

[0030] According to one aspect of the present embodiment, the object is achieved by a communication device and a method for handling a multi-hop CPC configuration, wherein the communication device is configured in a wireless communication network with a MCG managed by a first network node and a SCG managed by a second network node.

[0031] According to some embodiments, the communications device may receive a reconfiguration message from a first network node or a second network node (512). The reconfiguration message includes information regarding the configuration of a first-hop CPC and encapsulated information regarding future CPC hops. The communications device may evaluate execution conditions for a CPC candidate based on the content of the reconfiguration message and transmit a completion message to the first network node or the second network node in response to the reconfiguration message. After execution of the first-hop CPC, the communications device may evaluate execution conditions for the first-hop CPC candidate and evaluate execution conditions for CPC candidates for future hops, such as the second hop.

[0032] According to some embodiments, a communications device may receive a first reconfiguration message from a first network node. The first reconfiguration message includes information regarding a first-hop CPC configuration. The communications device may evaluate an execution condition of a CPC candidate based on content of the first reconfiguration message. The communications device may receive a second reconfiguration message from the first network node. The second reconfiguration message includes information regarding a second-hop CPC configuration. After execution of the first-hop CPC, the communications device may evaluate an execution condition of a CPC candidate based on content of the second reconfiguration message and send a reconfiguration complete message to the first network node in response to the second reconfiguration message.

[0033] According to some embodiments, a communications device may receive a first reconfiguration message from a first network node. The first reconfiguration message includes information regarding a first-hop CPC configuration. The communications device may receive a second reconfiguration message from the first network node. The second reconfiguration message includes information regarding a second-hop CPC configuration and an indication that the CPC configuration applies to the second CPC hop. The communications device may evaluate an execution condition for a first-hop CPC candidate based on content of the first reconfiguration message. After execution of the first-hop CPC, the communications device may evaluate an execution condition for a second-hop CPC candidate based on content of the second reconfiguration message and send a completion message to the first network node.

[0034] Embodiments herein include various solutions for enabling multi-hop CPC configurations and describe the implications of these solutions from the perspective of the MN, source SN, T-SN, and UE.

[0035] According to embodiments herein, the CPC can be reconstructed or reassembled. start This allows for frequent SCG changes to be supported without any disruption, minimizing the disruption perceived by the UE.

[0036] Accordingly, embodiments herein provide improved methods for handling multi-hop CPC configurations of communication devices configured with dual connectivity.

[0037] Examples of embodiments herein will now be described in more detail with reference to the accompanying drawings. [Brief explanation of the drawings]

[0038] [Figure 1] Schematic block diagram showing dual connectivity combined with carrier aggregation in MR-DC. [Figure 2] Schematic block diagram showing E-UTRAN-NR dual connectivity. [Figure 3] Schematic block diagram showing NR-DC, where both the master node controlling the MCG and the secondary node controlling the SCG are NR. [Figure 4] Example of a signal sequence for configuring Inter-SN CPC in 3GPP Rel-17. [Figure 5] 1 is a schematic block diagram illustrating a wireless communication network. [Figure 6a] Signaling example for MN-initiated multi-hop CPC configuration, inter-SN case. [Figure 6b] Signaling example for MN-initiated multi-hop CPC configuration, inter-SN case. [Figure 6c] Signaling example for MN-initiated multi-hop CPC configuration, inter-SN case. [Figure 7a] Signaling example for MN-initiated multi-hop CPC configuration, inter-intra SN case. [Figure 7b] Signaling example for MN-initiated multi-hop CPC configuration, inter-intra SN case. [Figure 8a] Signaling example for MN-initiated multi-hop CPC configuration, intra- and inter-SN. [Figure 8b] Signaling example for MN-initiated multi-hop CPC configuration, intra- and inter-SN. [Figure 8c] Signaling example for MN-initiated multi-hop CPC configuration, intra- and inter-SN. [Figure 9a] Signaling example for MN-initiated multi-hop CPC configuration, intra-intra SN case. [Figure 9b] Signaling example for MN-initiated multi-hop CPC configuration, intra-intra SN case. [Figure 10a] Signaling example for SN-initiated multi-hop CPC configuration, inter-SN case. [Figure 10b] Signaling example for SN-initiated multi-hop CPC configuration, inter-SN case. [Figure 10c] Signaling example for SN-initiated multi-hop CPC configuration, inter-SN case. [Figure 11a] Signaling example for SN-initiated multi-hop CPC configuration, inter-intra SN case. [Figure 11b] Signaling example for SN-initiated multi-hop CPC configuration, inter-intra SN case. [Figure 12a] Signaling example for SN-initiated multi-hop CPC configuration, intra- and inter-SN cases. [Figure 12b] Signaling example for SN-initiated multi-hop CPC configuration, intra- and inter-SN cases. [Figure 12c] Signaling example for SN-initiated multi-hop CPC configuration, intra- and inter-SN cases. [Figure 13a]Signaling example for SN-initiated multi-hop CPC configuration with MN involvement in intra-intra-SN scenario. [Figure 13b] Signaling example for SN-initiated multi-hop CPC configuration with MN involvement in intra-intra-SN scenario. [Figure 14] Signaling example for SN-initiated multi-hop CPC configuration, intra-intra SN without MN involvement. [Figure 15a] Signaling example for MN-SN initiated multi-hop CPC configuration, inter-SN case. [Figure 15b] Signaling example for MN-SN initiated multi-hop CPC configuration, inter-SN case. [Figure 15c] Signaling example for MN-SN initiated multi-hop CPC configuration, inter-SN case. [Figure 16a] Signaling example for MN-SN initiated multi-hop CPC configuration, inter-intra SN case. [Figure 16b] Signaling example for MN-SN initiated multi-hop CPC configuration, inter-intra SN case. [Figure 17a] Signaling example for MN-SN initiated multi-hop CPC configuration, intra- and inter-SN cases. [Figure 17b] Signaling example for MN-SN initiated multi-hop CPC configuration, intra- and inter-SN cases. [Figure 17c] Signaling example for MN-SN initiated multi-hop CPC configuration, intra- and inter-SN cases. [Figure 18] (a) and (b) are examples of RRC reconfiguration messages in the case of a CPC multi-hop configuration within a CPC. [Figure 19] 4 is a flowchart illustrating a method performed in a first network node according to the present embodiment. [Figure 20] 4 is a flowchart illustrating a method performed in a second network node according to the present embodiment. [Figure 21] 10 is a flowchart illustrating a method performed at a first target candidate secondary node according to the present embodiment. [Figure 22] 4 is a flowchart illustrating a first method performed in a communication device according to the present embodiment. [Figure 23] 6 is a flowchart illustrating a second method performed by a communication device according to the present embodiment. [Figure 24] 10 is a flowchart illustrating a third method performed in a communication device according to the present embodiment. [Figure 25] 1 is a schematic block diagram illustrating an exemplary embodiment of a network node. [Figure 26] 1 is a schematic block diagram illustrating an exemplary embodiment of a communication device. DETAILED DESCRIPTION OF THE INVENTION

[0039] This embodiment refers to, for example, a first network node acting as a master node (MN) having a master cell group (MCG) configured for a UE, where the MN may be a gNodeB, or a central unit gNodeB (CU-gNB), or an eNodeB, or a central unit eNodeB (CU-eNB), or any network node and / or network function.

[0040] The present embodiment also refers to a second network node acting as, for example, a secondary node (SN) having a secondary cell group (SCG) pre-configured in the UE, i.e., not connected to the UE, or a source secondary node (S-SN), where the SN may be, for example, a gNodeB, or a central unit gNodeB (CU-gNB), or an eNodeB, or a central unit eNodeB (CU-eNB), or any network node and / or network function. It should be noted that the MN, S-SN, and T-SN may be from the same or different radio access technologies and may be associated with different core network nodes.

[0041] In this description, we often refer to a "Secondary Node (SN)" or target SN. This is equivalent to saying that this is a target candidate SN or a network node associated with a configured target candidate PSCell. When a UE connects to that cell, if the cell is associated with that node, transmissions to and from the UE will be handled by that node.

[0042] In this description, it is stated that a cell exists within a node, e.g., a target candidate cell exists within an S-SN or T-SN, which is the same as saying that the cell is managed by the node, or that the cell is associated with the node, or that the cell belongs to the node, or that the cell belongs to the node.

[0043] "MN-initiated CPC" corresponds to the procedure in which the MN of a UE configured with MR-DC decides to configure a CPC. The MN provides its recommended candidate cells via the latest measurement results and an upper limit on the number of PSCells for the SN to select and configure SCG cells. The SN determines a list of PSCells to prepare from the list of cells indicated in the measurement results indicated by the MN, determines other SCG SCells for each prepared PSCell, and provides the MN with the newly corresponding SCG radio resource configuration along with the prepared PSCell ID in an NR RRC configuration message, e.g., RRCReconfiguration, included in the SgNB addition request acknowledgement message. If forwarding is required, the target SN provides the MN with a forwarding address. The target SN includes an indication of full or delta RRC configuration. The target SN can accept or reject each of the candidate cells proposed by the MN, i.e., it cannot present alternative candidates.

[0044] "SN-initiated CPC" corresponds to the procedure where a source SN of a UE configured with MR-DC decides to configure a CPC. Once decided, the source SN selects one or more target candidate cells, e.g., target candidate PSCells, e.g., based on reported measurements, where at least one cell is associated with the source SN and at least another cell is associated with a neighboring SN. If all target candidate cells are associated with the source SN, it is said to be "SN-initiated intra-SN CPC", which is called the Release 16 solution. can If at least one target candidate cell is associated with a neighboring SN, it is said to be an "SN-initiated inter-SN CPC", which may be referred to as a Release 17 solution.

[0045] In this document, a candidate SN, or SN candidate, or SN, is an SCG configuration (e.g., RRCReconfiguration) that is prepared during the CPA procedure and provided to and stored in the UE along with its execution conditions. ** ), and the UE applies the message only if an execution condition is met. That candidate SN is associated with one or more PSCell candidate cells that may be configured for the UE. The UE can then execute the condition and access one of these candidate cells associated with the candidate SN that becomes the SN, or simply the SN, after execution (i.e., upon fulfillment of the execution condition).

[0046] Although this document refers to neighbor SNs and source SNs as different entities, both may be target candidate SNs for a CPC.

[0047] In this embodiment, subsequent CPC configurations are referred to as next-hop CPC configurations. In particular, the CPCs defined in Rel-17 are referred to as "first-hop" CPCs, and each subsequent CPC is referred to as a "next-hop" CPC.

[0048] The configuration of the CPC can be done using the same information elements (IEs) as conditional handover, and at some point may be called conditional configuration or conditional reconfiguration. The principle of configuration is the same as the configuration of trigger / execution conditions and the reconfiguration message that is applied when the trigger conditions are met. Configuration IEs in TS38.331: -ConditionalReconfiguration The IE ConditionalReconfiguration is used to add, modify and release configurations of conditional configurations. ConditionalReconfiguration information element

[0049] [Table 1]

[0050] [Table 2]

[0051] -CondConfigId The IE CondConfigId is used to identify the CHO or CPC configuration. CondConfigId Information Element

[0052] [Table 3]

[0053] -CondConfigToAddModList The IE CHO-ConfigToAddModList relates to the list of conditional configurations to add or modify, and for each entry contains a cho-ConfigId and associated condExecutionCond and condRRCReconfig. CondConfigToAddModList information element

[0054] [Table 4]

[0055] [Table 5]

[0056] The present embodiments generally relate to wireless communication networks. Figure 5 shows a schematic of a communication network 500. The communication network 500 may be a wireless communication network including one or more RANs and one or more CNs. The communication network 500 may use one or more different technologies, such as WiFi, Long Term Evolution (LTE), LTE-Advanced, NR, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile Communications / Enhanced Data Rates for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), to name a few possible implementations.

[0057] In the wireless communication network 500, one or more wireless communication devices 530, 531, such as UEs, mobile stations, or wireless terminals, communicate with one or more core networks (CNs) via one or more radio access networks (RANs). Those skilled in the art will appreciate that a "wireless communication device" refers to any terminal, such as a wireless communication terminal, user equipment, machine-type communication (MTC) device, device-to-device (D2D) terminal or node, for example, a smartphone, laptop, mobile phone, sensor, repeater, mobile tablet, or small base station communicating within a cell.

[0058] Network nodes operate in the wireless communication network 500, such as a first network node 511 and a second network node 512. The first and second network nodes 511, 512 may be any RAN node, such as a gNB, eNB, en-gNB, ng-eNB, gNB, etc. The first network node 511 is configured as a geographical area, which may also be referred to as a beam or beam group, that covers the coverage area of ​​a first radio access technology (RAT), such as 5G, LTE, Wi-Fi, etc. area , providing radio coverage over the service area 11. The second network node 512 is a geographical node, which may also be referred to as a beam or beam group, covering the service area of ​​a first or second radio access technology (RAT), such as 5G, LTE, or Wi-Fi. area , providing radio coverage over a service area 12. It should be noted that the network node may be a RAN node, a CN node, or an OAM node.

[0059] The first and second network nodes 511 and 512 may be, depending on the radio access technology used and the terminology used, e.g., Wireless Local Area Network (WLAN) access points or access point stations (AP STAs), access controllers or, e.g., Node Bs, evolved Node Bs (eNBs, eNodeBs), gNBs, base transceiver stations, wireless remote units, access point base stations, base station routers, transmitters of radio base stations, stand-alone Ron Base stations such as wireless base stations like access points, e.g. First and second network nodes 511, 512, respectively Services provided by area The first and second network nodes 511, 512 may be referred to as source and target network nodes, respectively, and may communicate with the wireless communication devices 530, 531 in downlink (DL) transmissions to the wireless communication devices 530, 531 and uplink (UL) transmissions from the wireless communication devices 530, 531.

[0060] Each of the first and second network nodes 511, 512 may be either a master node (MN) with a cell group MCG or a secondary node (SN) with a cell group SCG, as shown in FIG.

[0061] In this specification, terms such as SCG and PSCell are described as one of the cells associated with the SCG, which is, for example, a PSCell defined in the NR specifications (e.g., RRC TS38.331), and is defined as a special cell (SpCell) of the SCG, or as a primary SCG cell (PSCell) as follows: - Secondary cell group: For a UE configured with dual connectivity, a subset of serving cells consisting of a PSCell and zero or more secondary cells (SCells). - Special Cell: In the case of dual connection operation, the term special cell refers to the PC of MCG. ell or SCG PS Cell otherwise, the term special cell refers to PC ell Refers to... Primary SCG Cell (PSCell): In case of dual connectivity operation, this is the SCG cell that the UE randomly accesses when performing a reconfiguration procedure with synchronization.

[0062] The present embodiments include different methods for the network to configure a multi-hop CPC. These methods differ in the sequence of messages exchanged between the MN, S-SN, T-SN, and UE, and in the way the multi-hop CPC configuration is communicated to the UE, e.g., CPC-in-CPC or separate reconfiguration messages. This document describes the solutions from the perspective of the MN, S-SN, T-SN, and UE, as described below.

[0063] The configuration of a multi-hop CPC differs depending on whether the CPC hop is inter or intra and whether it is MN-initiated or SN-initiated.

[0064] a) In the first embodiment, the multi-hop CPC configuration is MN initiated. In this embodiment, there are different cases depending on the type of the first CPC configuration and the subsequent CPC configuration, i.e., inter or intra: i. An inter-inter configuration in which each next-hop CPC configuration is an inter-CPC configuration. ii. An inter-intra configuration, where the "first hop" is an inter-CPC configuration and the next hop is an intra-CPC configuration. iii. Intra-Inter configuration, where the "first hop" is an intra-CPC configuration and the next hop is an inter-CPC configuration. iv. Intra-intra configuration, where the "first hop" is an intra-CPC configuration and the next hop is also an intra-CPC configuration.

[0065] b) In a second embodiment, the multi-hop CPC configuration is SN-initiated, i.e., each SN decides whether to initiate the configuration of the next-hop CPC at the first hop S-SN and at each next hop T-SN. In this embodiment, there are different cases depending on the type of the first and subsequent CPC configuration, i.e., inter or intra: i. An inter-inter configuration in which each next-hop CPC configuration is an inter-CPC configuration. ii. An inter-intra configuration, where the "first hop" is an inter-CPC configuration and the next hop is an intra-CPC configuration. iii. Intra-Inter configuration, where the "first hop" is an intra-CPC configuration and the next hop is an inter-CPC configuration. iv. Intra-intra configuration, where the "first hop" is an intra-CPC configuration and the next hop is also an intra-CPC configuration. Here, there are two possible subcases: When MN is involved, the multi-hop CPC configuration is communicated to the UE via the MN. In this case, the MN is not involved, and the S-SN directly provides the UE with information about the multi-hop CPC configuration.

[0066] c) In a third embodiment, the multi-hop CPC configuration is MN-SN initiated, i.e., the first-hop CPC is MN-initiated and the subsequent-hop CPC is SN-initiated. In this embodiment, there are different cases depending on the type of the first and subsequent CPC configuration, i.e., inter or intra: i. An inter-inter configuration in which each next-hop CPC configuration is an inter-CPC configuration. ii. An inter-intra configuration, where the "first hop" is an inter-CPC configuration and the next hop is an intra-CPC configuration. iii. Intra-Inter configuration, where the "first hop" is an intra-CPC configuration and the next hop is an inter-CPC configuration.

[0067] Masternode implementation and actions: In relation to the multi-hop CPC configuration, the MN can perform the following actions:

[0068] a. Send a CPC SN addition request to the target candidate SN (e.g., T-SN1). i. In one option, this is triggered by the MN itself (MN initiated CPC). ii. In one option, this is SS N This is triggered by (SN initiated CPC), i.e., the S-SN sends an SN change request to the MN requesting a CPC, and the MN triggers an SN addition request to the T-SN1.

[0069] b. In response to the Add SN Request, receive an Add SN Request Ack from T-SN1 that includes: i) an indication that it is a multi-hop CPC; ii) Identifiers of one or more target candidate PSCells for second-hop CPC configuration; iii) Identifiers of one or more target candidate SNs (e.g., T-SN2) associated with one or more target candidate PSCells.

[0070] c. Trigger a CPC SN addition procedure for one or more target candidate SNs, eg, T-SN2, indicated by T-SN1 for one or more target candidate PSCells of the second-hop CPC configuration.

[0071] d. For one or more target candidate PSCells of the second-hop CPC configuration, one or more target candidate SNs indicated by T-SN1, e.g., SN release or S for T-SN2 CG Trigger the deactivation procedure.

[0072] e. In case of MN initiated intra-CPC first hop configuration, send SN modification request to S-SN.

[0073] f. In case of MN initiated inter-CPC configuration, send data forwarding address indication to SN, e.g., S-SN for first hop, T-SN for subsequent hops.

[0074] In the case of gS-SN initiated inter-CPC first hop configuration, a SN change request is received from the S-SN.

[0075] h In the case of S-SN initiated intra-CPC first hop configuration, receive SN modification requirement from S-SN.

[0076] Some exemplary embodiments are described below for MN:

[0077] Embodiment 1: A method for triggering a CPC SN addition procedure for one or more target candidate SNs, e.g., T-SN2, indicated by an MN or T-SN1 for one or more target candidate PSCells in a second hop, comprising: The MN sends to the T-SN2 a request to add an SN of the CPC, the request including an indication that the CPC is a second-hop CPC; In response, the MN receives an SN Addition Request Ack that includes at least one SCG configuration associated with at least one of the one or more target candidate PSCells requested by the MN.

[0078] Embodiment 2: The MN may send an SN addition request for a CPC to T-SN2 after executing the CPC of the current hop for T-SN1. In this case, the multi-hop CPC becomes a conventional single-hop CPC, that is, each CPC continues to be triggered only when the previous CPC is executed.

[0079] Embodiment 3: The MN may send a CPC SN addition request to T-SN2 before executing the current-hop CPC for T-SN1. In this case, there are different options for the MN to convey the multi-hop CPC configuration to the UE as part of the RRC reconfiguration message.

[0080] Option 1: The MN can wait to receive information about the SCG configurations of the next k-hop CPCs before sending an RRC reconfiguration message to the UE. In this case, the MN sends an RRC reconfiguration message to the UE that includes the CPC within the CPC configuration, i.e., the information about the next-hop CPC is encapsulated in the information about the previous-hop CPC. For example, in the case of a two-hop inter-CPC, the MN waits to receive an SN Addition Request Ack from T-SN2 that includes at least one SCG configuration for the second-hop CPC. Upon receiving such an SN Addition Request Ack, the MN creates an RRC reconfiguration message that includes information about both the first-hop and second-hop CPCs and sends this RRC reconfiguration message to the UE.

[0081] Option 2: The MN may send a first RRC reconfiguration message to the UE as soon as it obtains information about the first-hop CPC. Then, the MN may start configuring the next-hop CPC, for example, if the second-hop CPC is an inter-CPC, it may trigger an SN addition procedure for the CPC to T-SN2. When it receives information about the SCG configuration of the next-hop CPC, for example, when it receives an SN Addition Request Ack from T-SN2, the MN may do the following:

[0082] a) Create a new RRC reconfiguration message containing information about the CPC configurations for both the first hop (e.g., T-SN1) and subsequent hops (e.g., T-SN2) and send this RRC reconfiguration message to the UE. This RRC reconfiguration message has the same structure as the RRC reconfiguration message described in Option 1, containing the CPC encapsulated within the CPC configuration.

[0083] b) Create a new RRC reconfiguration message containing only information about the CPC configuration of the next hop (e.g., T-SN2) and send this RRC reconfiguration message to the UE. This RRC reconfiguration message must contain an indicator that the CPC configuration content relates to the future next-hop CPC configuration, i.e., it must be clear to the UE that the CPC configuration contained in this message applies to the second hop and not the first hop.

[0084] c) Store information about the next-hop CPC, for example, the CPC configuration information received in the SN Addition Request Ack from T-SN2, wait for the execution of the first-hop CPC, and after the execution of the first-hop CPC, i.e., immediately after T-SN1 becomes the SN of the inter-CPC example, send an RRC reconfiguration message including information about the next-hop CPC.

[0085] Embodiment 4: Deciding Between Embodiments 2 and 3 Based on Indication from the S-SN. When deciding when and how to communicate the multi-hop CPC configuration to the UE, i.e., which of the above options for creating and transmitting an RRC reconfiguration message to select, the MN needs to consider the indication sent from the S-SN as to whether it is time-critical to configure the first-hop CPC as soon as possible and how many hops away the S-SN wants the configuration to be. For example, if the S-SN indicates that the configuration of the first-hop CPC needs to be sent to the UE as soon as possible, the MN may decide to select one of the solutions shown in Option 2 of Embodiment 3 that does not delay communication of the first-hop CPC configuration to the UE.

[0086] Embodiment 5: Triggering an SN release or SCG deactivation procedure for one or more target candidate SNs, e.g., T-SN2, indicated by the MN or T-SN1. The MN may trigger the SN release procedure due to an MN change (handover), and the target MN may trigger the SN addition procedure described above to add a CPC hop. The MN may trigger the SCG deactivation procedure due to temporary unavailability of the SCG, e.g., due to overheating.

[0087] Embodiment 6: The SN addition request may include an indication of whether it is the first, second, third, etc. hop. Based on that indication, the requested candidate SN may decide whether to accept and, if so, how to set its timer and when to expect the UE to possibly arrive.

[0088] Embodiment 7: The SN addition request includes, together with the previous information, an indication of the maximum number of hops that the UE supports, so that subsequent candidates can know to what extent they can configure multi-hops. This information can be provided by the UE to the network, for example, by reporting a capability indicating the maximum number of hops that the UE supports. Alternatively, the UE can indicate its preferred number of hops to the network, for example, via UE assistance information.

[0089] Note: Further MN involvement may depend on the choice of multi-hop CPC configuration solution. For example, if a CPC in the CPC is configured as a legacy Rel-17 CPC, i.e., option 1 in embodiment 3, the CPC is part of the conditional reconfiguration of the MCG configuration, i.e., the messages generated by the MN and actually applied are also generated by the MN and include the MCG part. Therefore, the MN can only participate in the RRCReconfiguration of the second hop. ** When the SCG configuration for (hop2) is received, RRCReconfiguration containing RRCReconfiguration**(hop2) ** Next, the MN generates the RRCReconfiguration ** Generate a CPC configuration in (hop1), and the CPC configuration is RRCReconfiguration ** These include target candidate cells for (hop2). Since all relate to a single MN, if the MN changes, these are no longer valid and need to be cancelled and / or modified.

[0090] S-SN implementation and actions: In connection with the configuration of a multi-hop CPC, the S-SN may perform the following actions:

[0091] a. In the case of SN-initiated inter-CPC, send a CPC SN change request to the MN, including an indication of allowing multi-hop CPC and the maximum number of hops allowed, with T-SN1 as the target candidate; for example, if configuring the first hop as soon as possible is not time-critical, the SN may allow the configuration of a multi-hop CPC.

[0092] b. In the case of SN-initiated intra-CPC, send a CPC SN modification required to the MN. In the SN modification required message, the S-SN includes the configuration of the first-hop intra-CPC, but can also include the configuration of subsequent hop intra-CPCs, or can indicate that it wants to configure a second-hop inter-CPC, for example, T-SN1 as the target candidate. If the S-SN indicates that it wants to configure a second-hop inter-CPC, for example, with T-SN1 as the target candidate, it can also indicate to the MN whether it is allowed to configure the next hop, and if so, what the maximum number of hops allowed is.

[0093] Note: "Allowed" means that the S-SN is not the node that makes the decision to configure the multi-hop CPC. This decision is made by each requested target candidate SN, but there are different options for configuring the multi-hop: In one option, the MN assists in the configuration of the second hop as described above for each target candidate SN; In another option, each target candidate SN can directly request other candidates to configure a CPC; In yet another option, each target candidate SN may configure its own cell as a target candidate in the second hop.

[0094] Embodiments and actions of the first target candidate T-SN1: In connection with the configuration of a multi-hop CPC, the T-SN1 may perform the following actions:

[0095] a. Receive a first SN addition request for the CPC from the MN. i. In one option, this is triggered by the MN itself (MN initiated CPC). ii. In one option, this is SS N This is triggered by (SN initiated CPC), i.e., the S-SN sends an SN change request to the MN requesting a CPC, and the MN triggers an SN addition request to the T-SN1.

[0096] b. For example, in the case of an inter-CPC hop, it is determined to configure a multi-hop CPC in the second target candidate SN2 (T-SN2).

[0097] c. Respond to the CPC's first SN Addition Request with an SN Addition Request Ack to the MN, which includes: i) an indication that it is a multi-hop CPC; ii) Identifiers of one or more target candidate PSCells for second-hop CPC configuration; iii) Identifiers of one or more target candidate SNs (e.g., T-SN2) associated with one or more target candidate PSCells.

[0098] d. A message is received from the MN confirming that the second-hop CPC configuration has been successfully completed, for example, a message similar to the SN change confirmation in the inter-CPC case.

[0099] UE embodiments and actions: In relation to the multi-hop CPC configuration, the UE can perform the following actions:

[0100] a. Receiving an RRC reconfiguration message, the following cases can be distinguished:

[0101] i. The UE may receive an RRC reconfiguration message containing information about the configuration for the first-hop CPC and encapsulated information about future hops, i.e., the intra-CPC CPC configuration. If, prior to receiving the intra-CPC configuration, the UE received a configuration containing only information about the first-hop CPC, the UE should "rewrite" this previous message and apply the latest first-hop CPC configuration indicated in the RRC reconfiguration message containing the intra-CPC configuration.

[0102] ii. The UE may receive an RRC reconfiguration message for each hop separately. For example, the UE may first receive an RRC reconfiguration message that includes only information about the first-hop CPC configuration. Thereafter, the UE may receive an RRC reconfiguration message that includes only information about the second-hop CPC configuration.

[0103] In one option, the UE may receive the RRC reconfiguration message for the second hop before the first hop execution condition is met, in which case the RRC reconfiguration message for the second hop must include an explicit indication that the received CPC configuration applies to the second hop and not the first hop.

[0104] In another option, the UE may receive the second-hop RRC reconfiguration message immediately after applying the CPC configuration of the first-hop CPC, e.g., immediately after T-SN1 becomes S-SN in the case of inter-CPC, in which case the second-hop RRC reconfiguration message does not need to include an indication regarding the hop number to which the configuration applies.

[0105] b. Evaluate the execution conditions of the CPC candidates in the order specified by the content of the RRC reconfiguration message, i.e., first evaluate the execution conditions of the first-hop candidate, then evaluate the execution conditions of the second-hop candidate after the first-hop CPC execution, etc. For example, if a CPC configuration in a CPC is received, the UE only performs the evaluation of the execution conditions for the "first-hop" conditional reconfiguration. That is, the "second-hop" CPC configuration is stored, but the evaluation of the execution conditions is not performed.

[0106] c. In the case of an SN-initiated intra-intra multi-hop CPC configuration not involving the MN, an RRC reconfiguration complete message is sent in response to an RRC reconfiguration message sent by the MN or S-SN.

[0107] Multi-hop CPC solutions are intended to support CPC configurations across multiple hops. However, it is important to note that each next hop configuration may be less likely than the previous one unless the UE's travel route is known to the network in advance. An example scenario where the UE's travel route is known to the network in advance is train travel, i.e., UEs in a train traveling in a direction known to the network.

[0108] This embodiment also allows the option for the first conditional reconfiguration to be a conditional handover (CHO) and subsequent conditional reconfigurations to consist of one-hop or multi-hop CPC configurations.

[0109] In the following, signal examples for various solutions of multi-hop CPC configurations are described.

[0110] Figures 6(a), (b), and (c) show examples of signaling in an MN-initiated multi-hop CPC configuration, the inter-inter SN case, where (a) is a CPC within a CPC, (b) is a second-hop CPC before the first-hop CPC is executed, and (c) is a second-hop CPC immediately after the first-hop CPC is executed.

[0111] New and / or modified messages: ·SN addition request * (See Figures 6(a), (b) and (c)) are modified to make it clear that T-SN2 is a "second-hop" CPC candidate.

[0112] This can be done, for example, by adding a new IE of container CG-ConfigInfo to the S-NODE addition request, where the new container contains the target candidate configuration of the first CPC configuration created by T-SN1.

[0113] Another option is to add an indication that the request is a "second-hop" CPC candidate. The configuration that T-SN2 uses when creating the target candidate configuration may be included in the existing CG-ConfigInfo or in a new IE in a new container. RRC reconfiguration in Figure 6(a) * and RRC reconfiguration completed * is extended to include encapsulated information about the CPCs of the first and second hops, i.e., information about CPCs within CPCs. RRC reconfiguration in Figure 6(b) * and RRC reconfiguration completed * can be modified in two different ways: Option 1: Include information about the encapsulated first-hop and second-hop CPCs, i.e., information about CPCs within CPCs. Option 2: Include information about the CPC of the second hop so that it is clear that this is information about the future CPC that should be applied at the second hop, not the first hop.

[0114] Figures 7(a) and (b) show examples of signaling for an MN-initiated multi-hop CPC configuration, inter-intra SN, where (a) shows a CPC within a CPC, and (b) shows a second-hop CPC immediately after the first-hop CPC is executed.

[0115] New and / or modified messages: ·SN addition request * (See Figures 7(a) and (b)) is extended to include information on both inter "first hop" CPCs and subsequent intra "second hop" CPCs.

[0116] This can be done, for example, by adding a new IE of container CG-ConfigInfo to the S-NODE addition request, where the new container contains the target candidate configuration of the first CPC configuration created by T-SN1.

[0117] Another option is to add an indication that the request is a "second-hop" CPC candidate. The configuration that the second-hop T-SN1 uses when creating the target candidate configuration can be included in the existing CG-ConfigInfo or in a new IE in a new container. SN addition request acknowledgement * is extended to include configuration information for both the "first hop" CPC and any subsequent "second hop" CPCs.

[0118] This can be done, for example, by adding a new IE for the container CG-ConfigInfo or CG-CandidateList to the S-NODE addition request, where the new container contains the target candidate configuration for the first CPC configuration created by T-SN1.

[0119] Another option is to add an indication that the request is a "second-hop" CPC candidate. The configuration that the second-hop T-SN1 uses when creating the target candidate configuration may be included in the existing CG-ConfigInfo or CG-CandidateList, or in a new IE in a new container.

[0120] The request for additional cells as CPC candidates can be used to propose CPC candidates at the same "hop level" as other candidates configured by T-SN1. RRC reconfiguration in Figure 7(a) * and RRC reconfiguration completed * is extended to include encapsulated information about the CPCs of the first and second hops, i.e., information about CPCs within CPCs.

[0121] Figures 8(a), (b), and (c) show examples of signaling in an MN-initiated multi-hop CPC configuration, the intra- and inter-SN case, where (a) is a CPC within a CPC, (b) is a second-hop CPC before the first-hop CPC is executed, and (c) is a second-hop CPC immediately after the first-hop CPC is executed.

[0122] New and / or modified messages: ·SN addition request * (Figure 8(a) 、 (b) and (c) ) is modified to make it clear that T-SN1 is a "second-hop" CPC candidate.

[0123] This can be done, for example, by adding a new IE of container CG-ConfigInfo to the S-NODE addition request, where the new container contains the target candidate configuration of the second CPC configuration created by T-SN1.

[0124] Another option is to add an indication that the request is a "second-hop" CPC candidate. The configuration that the second-hop T-SN1 uses when creating the target candidate configuration can be included in the existing CG-ConfigInfo or in a new IE in a new container. RRC reconfiguration in Figure 8(a) * and RRC reconfiguration completed * is extended to include encapsulated information about the CPCs of the first and second hops, i.e., information about CPCs within CPCs. RRC reconfiguration in Figure 8(b) * and RRC reconfiguration completed * can be modified in two different ways: Option 1: Include information about the encapsulated first-hop and second-hop CPCs, i.e., information about CPCs within CPCs. Option 2: Include information about the CPC of the second hop so that it is clear that this is information about the future CPC that should be applied at the second hop, not the first hop.

[0125] Figures 9(a) and (b) show examples of signaling for an MN-initiated multi-hop CPC configuration, intra-intra SN, where (a) is a CPC within a CPC, and (b) is a second-hop CPC immediately after the first-hop CPC is executed.

[0126] New and / or modified messages: ·SN addition request * (See Figures 9(a) and (b)) is extended to include information on both the intra "first hop" CPC and the subsequent intra "second hop" CPC.

[0127] This can be done, for example, by adding a new IE of container CG-ConfigInfo to the S-NODE addition request, where the new container contains the target candidate configuration of the second CPC configuration created by the S-SN.

[0128] Another option is to add an indication that the request is for a "second-hop" CPC candidate. The configuration that the second-hop S-SN uses when creating the target candidate configuration may be included in the existing CG-ConfigInfo or in a new IE in a new container. SN addition request acknowledgement * is extended to include configuration information for both the "first hop" CPC and any subsequent "second hop" CPCs.

[0129] This can be done, for example, by adding a new IE of container CG-ConfigInfo or CG-CandidateList to the S-NODE addition request, where the new container contains the target candidate configuration of the first CPC configuration created by the S-SN.

[0130] Another option is to add an indication that the request is a "second-hop" CPC candidate. The configuration that the second-hop S-SN uses when creating the target candidate configuration may be included in the existing CG-ConfigInfo or CG-CandidateList, or in a new IE in a new container.

[0131] The request for additional cells as CPC candidates is the same as other candidates configured by S-SN. "Hop level" It can also be used to suggest CPC candidates. RRC reconfiguration in Figure 9(a) * and RRC reconfiguration completed * is extended to include information about multiple CPC configuration hops, i.e., CPCs within CPCs.

[0132] Figures 10(a), (b), and (c) show examples of signaling in an SN-initiated multi-hop CPC configuration, the inter-inter SN case, where (a) is a CPC within a CPC, (b) is a second-hop CPC before the first-hop CPC is executed, and (c) is a second-hop CPC immediately after the first-hop CPC is executed.

[0133] New and / or modified messages: SN change required (T-SN1) * (See Figures 10(a), (b) and (c)) are extended to include whether multiple CPC hop configurations are allowed, and if so, the maximum number of hops allowed. SN addition request acknowledgement * (See Figures 10(a), (b) and (c)) is extended to also include a subsequent inter-CPC start indication for T-SN2 (i.e., it contains similar information as the SN change request message). ·SN addition procedure * (see Figures 10(a), (b) and (c)) are modified to make it clear that T-SN2 is a candidate CPC for the "second hop". · Check subsequent CPC *(See Figure 10(a), (b) and (c)) shows that T-SN1 sends an SN addition request acknowledgment * This is a response to a SN change request sent in a message (e.g., similar to a SN change confirmation). RRC reconfiguration in Figure 10(a) * and RRC reconfiguration completed * is extended to include information about multiple CPC configuration hops (ie, information about CPCs within CPCs). RRC reconfiguration in Figure 10(b) * and RRC reconfiguration completed * can be modified in two different ways: Option 1: Include information about the encapsulated first-hop and second-hop CPCs (i.e., information about CPCs within CPCs), Option 2: Include information about the CPC of the second hop so that it is clear that this is information about the future CPC that should be applied at the second hop, not the first hop.

[0134] Figures 11(a) and (b) show examples of signaling for an SN-initiated multi-hop CPC configuration, inter-intra SN, where (a) is a CPC within a CPC, and (b) is a second-hop CPC immediately after the first-hop CPC is executed.

[0135] New and / or modified messages: SN change required (T-SN1) * (see Figures 11(a) and (b)) is extended to include whether multiple CPC hop configurations are allowed, and if so, the maximum number of hops allowed. SN addition request acknowledgement * (see Figures 11(a) and (b)) is extended to include information on both the inter "first hop" CPC initiated by the S-SN and the subsequent "second hop" intra CPC initiated by the T-SN1. · Check subsequent CPC * (See Figure 11(a) and (b)) is an SN addition request acknowledgement *This is a response to T-SN1 regarding the subsequent CPC of the "second hop" initiated by RRC reconfiguration in Figure 11(a) * and RRC reconfiguration completed * is extended to include information about multiple CPC configuration hops (ie, information about CPCs within CPCs).

[0136] Figures 12(a), (b), and (c) show examples of signaling in an SN-initiated multi-hop CPC configuration, the intra- and inter-SN case, where (a) is a CPC within a CPC, (b) is a second-hop CPC before the first-hop CPC is executed, and (c) is a second-hop CPC immediately after the first-hop CPC is executed.

[0137] New and / or modified messages: SN correction required * (see Figures 12(a), (b) and (c)) is modified to include a "first hop" intra-CPC start indication followed by a "second hop" inter-CPC start indication. ·SN addition procedure * (See Figures 12(a), (b) and (c)) are T-SN1 is the 2H P C It will be changed to make it clear that it is a PC candidate. ·SN correction confirmation * (See Figures 12(a) and (b)) to check both "first hop" intra-CPC and "second hop" inter-CPC. Expansion will be done. RRC reconfiguration in Figure 12(a) * and RRC reconfiguration completed * is extended to include information about multiple CPC configuration hops (ie, information about CPCs within CPCs). RRC reconfiguration in Figure 12(b) * and RRC reconfiguration completed * can be modified in two different ways: Option 1: Include information about the encapsulated first-hop and second-hop CPCs (i.e., information about CPCs within CPCs), Option 2: Include information about the CPC of the second hop so that it is clear that this is information about the future CPC that should be applied at the second hop, not the first hop.

[0138] Figures 13(a) and (b) show examples of signaling for an SN-initiated multi-hop CPC configuration, intra-intra SN, where (a) is a CPC within a CPC, and (b) is a second-hop CPC immediately after the first-hop CPC is executed.

[0139] New and / or modified messages: SN correction required * (see Figures 13(a) and (b)) is modified to include a "first hop" intra-CPC start indication and a "second hop" intra-CPC start indication. · Check the SN correction in Figure 13(a) * to check both the "1st hop" intra CPC and the "2nd hop" intra CPC. Expansion will be done. RRC reconfiguration in Figure 13(a) * and RRC reconfiguration completed * is extended to include information about multiple CPC configuration hops (ie, information about CPCs within CPCs).

[0140] Figure 14 shows an example of signaling for an SN-initiated multi-hop CPC configuration, an intra-intra-SN case without MN involvement.

[0141] New and / or modified messages: Figure 1 of 4 RRC reconfiguration * and RRC reconfiguration completed * is extended to include information about multiple CPC configuration hops (ie, information about CPCs within CPCs).

[0142] Figures 15(a), (b), and (c) show examples of signaling in an MN-SN initiated multi-hop CPC configuration, the inter-inter SN case, where (a) is a CPC within a CPC, (b) is a second-hop CPC before the first-hop CPC is executed, and (c) is a second-hop CPC immediately after the first-hop CPC is executed.

[0143] New and / or modified messages: SN addition request acknowledgement * (See Figure 15(a), (b) and (c)) is extended to also include the subsequent inter-CPC start indication for T-SN2 (i.e., SN change request) Request (including similar information). ·SN addition procedure * (See Figures 15(a), (b) and (c)) are modified to make it clear that T-SN2 is a candidate CPC for the "second hop". · Check subsequent CPC * (See Figure 15(a), (b) and (c)) shows that T-SN1 sends an SN addition request acknowledgment * This is a response to a SN change request sent in a message (e.g., similar to a SN change confirmation). RRC reconfiguration in Figure 15(a) * and RRC reconfiguration completed * is extended to include information about multiple CPC configuration hops (ie, information about CPCs within CPCs). RRC reconfiguration in Figure 15(b) * and RRC reconfiguration completed * can be modified in two different ways: Option 1: Include information about the encapsulated first-hop and second-hop CPCs (i.e., information about CPCs within CPCs), Option 2: Include information about the CPC of the second hop so that it is clear that this is information about the future CPC that should be applied at the second hop, not the first hop.

[0144] Figures 16(a) and (b) show examples of signaling for an MN-SN initiated multi-hop CPC configuration, inter-intra SN, where (a) shows a CPC within a CPC and (b) shows a second-hop CPC immediately after the first-hop CPC is executed.

[0145] New and / or modified messages: SN addition request acknowledgement * (see Figures 16(a) and (b)) is extended to include information on both the inter "first hop" CPC initiated by the MN and the subsequent intra "second hop" CPC initiated by T-SN1. · Check subsequent CPC * (See Figure 16(a) and (b)) shows that T-SN1 is a SN addition request acknowledgment * This is a response to a SN change request sent in a message (e.g., similar to a SN change confirmation). RRC reconfiguration in Figure 16(a) * and RRC reconfiguration completed * is extended to include information about multiple CPC configuration hops (ie, information about CPCs within CPCs).

[0146] Figures 17(a), (b), and (c) show examples of signaling in an MN-SN initiated multi-hop CPC configuration, intra- and inter-SN cases, where (a) is a CPC within a CPC, (b) is a second-hop CPC before the first-hop CPC is executed, and (c) is a second-hop CPC immediately after the first-hop CPC is executed.

[0147] New and / or modified messages: SN modification request acknowledgement * (See Figures 17(a), (b) and (c)) is extended to include information on both intra "first hop" CPC initiated by the MN and subsequent inter "second hop" CPC initiated by the S-SN. ·SN addition procedure * (see Figures 17(a), (b) and (c)) are modified to make it clear that T-SN1 is a second-hop CPC candidate. · Check subsequent CPC* (See Figure 17(a), (b) and (c)) shows that SN is Fixes Request Acknowledgment * This is a response to a SN change request sent in a message (e.g., similar to a SN change confirmation). RRC reconfiguration in Figure 17(a) * and RRC reconfiguration completed * is extended to include information about multiple CPC configuration hops, i.e., information about CPCs within CPCs. RRC reconfiguration in Figure 17(b) * and RRC reconfiguration completed * can be modified in two different ways: Option 1: Include information about the encapsulated first-hop and second-hop CPCs (i.e., information about CPCs within CPCs), Option 2: Include information about the CPC of the second hop so that it is clear that this is information about the future CPC that should be applied at the second hop, not the first hop.

[0148] Example of ASN and procedure update for CPC-within-CPC solution: The following example shows some of the modifications to a TS38.331 implementation required to configure multi-hop CPC.

[0149] -CondReconfigToAddModList The IE CondReconfigToAddModList relates to a list of conditional reconfigurations to add or modify, with each entry having a condReconfigId and an associated condExecutionCond / condExecutionCondSCG and condRRCReconfig.

[0150] [Table 6]

[0151] [Table 7]

[0152] [Table 8]

[0153] -Reception of RRCReconfiguration by UE The UE shall perform the following actions upon receiving an RRCReconfiguration or upon performing a conditional reconfiguration (CHO, CPA or CPC): 1> RRCReconfiguration is performed even within mrdc-SecondaryCellGroup. E-UTRA is also used within RRCConnectionReconfiguration. If not received within RRCConnectionResume: 2>If RRCReconfiguration contains scg-State: 3>Perform SCG deactivation as specified in 5.3.5.13b; 2> Otherwise: 3>Perform SCG activation as specified in 5.3.5.13a. Editor's Note: The FFS, if included, provides a way to ensure that notifications to the MAC are processed only when the SCG configuration is processed. 1> If RRCReconfiguration is applied due to a conditional reconfiguration execution during cell selection while timer T311 is running, as defined in 5.3.7.3: 2> If RRCReconfiguration includes keepConditional: 3>Keep all entries in VarConditionalReconfig other than the one that triggered this conditional reconfiguration, if any; 2> Otherwise: 3>Delete all entries in VarConditionalReconfig, if any; ...

[0154] Example of structure of RRC reconfiguration message: 18(a) and (b) show an example structure of an RRC reconfiguration message for an intra-CPC solution in a multi-hop CPC configuration. In particular, this example shows intra-CPC encapsulation in the RRC reconfiguration message sent to the UE.

[0155] Implementation example in XnAP TS38.423: 9.1.2.1 S-node addition request This message is sent from an M-NG-RAN node to an S-NG-RAN node to request the preparation of resources for dual connectivity operation for a particular UE. Direction: M-NG-RAN node → S-NG-RAN node

[0156] [Table 9]

[0157] [Table 10]

[0158] [Table 11]

[0159] [Table 12]

[0160] [Table 13]

[0161] [Table 14]

[0162] 9.1.2.2 S-node Addition Request Acknowledgment This message is sent by the S-NG-RAN node to confirm to the M-NG-RAN node about the readiness of the S-NG-RAN node to be added. Direction: S-NG-RAN node → M-NG-RAN node

[0163] [Table 15]

[0164] [Table 16]

[0165] [Table 17]

[0166] According to this embodiment, a method performed in a first network node 511 for processing a multi-hop configuration of a conditional primary secondary cell change or primary secondary cell group cell change (CPC) of a communication device 530, 531 is described with reference to Figure 19. The communication device 530, 531 is configured in a wireless communication network 500 to have dual connectivity with a master cell group (MCG) managed by the first network node 511 and a secondary cell group (SCG) managed by a second network node 512. The method comprises the following actions, which may be performed in any suitable order:

[0167] Action 1900 This action is optional. The first network node 511 may receive the SN change required from the second network node 512 when the inter SN-CPC first hop configuration is initiated by the second network node 512.

[0168] The first network node 511 may receive an SN modification required from the second network node 512 when an intra-SN-CPC first hop configuration is initiated by the second network node 512 .

[0169] Action 1910 The first network node 511 sends a request for CPC to the second network node 512 or the first target candidate secondary node T-SN1. The request for CPC includes: A first-hop configuration or a part of a configuration applied in the first-hop CPC; Indication of which CPC hops are required, and An indication of the maximum number of CPC hops supported by the communication device; and The information may include one or more of the following:

[0170] Action 1920 The first network node 511 receives a message from the second network node 512 or the first target candidate SN (T-SN1) in response to a request from the CPC. The message includes: an indication that the i.CPC configuration is a multi-hop CPC configuration; ii. An indication of whether configuring the first-hop CPC is time-critical; and ii. an indication of how many hops away it comprises; and iii. Identifiers of one or more target candidate primary secondary cells (PSCells) for second-hop CPC configuration; and iv. Identifiers of one or more target candidate secondary nodes (T-SN2) associated with one or more target candidate PSCells; The information may include one or more of the following:

[0171] Action 1930 Based on the received message, the first network node 511 configures a multi-hop CPC for the communication device 530, 531. This may be done by creating a reconfiguration message that includes information about both the first-hop CPC configuration and the next-hop CPC configuration and sending this reconfiguration message to the communication device 530, 531.

[0172] Based on the received message, the first network node 511 may configure the multi-hop CPC of the communication device 530, 531 by any one of the following: Creating a first reconfiguration message including information about a first-hop CPC configuration and sending the first reconfiguration message to the communication device, and then creating a second reconfiguration message including information about a next-hop CPC configuration and sending the second reconfiguration message to the communication device. · creating a first reconfiguration message including information about a first-hop CPC configuration, sending the first reconfiguration message to the communication device, storing information about a next-hop CPC configuration, and after performing the first-hop CPC, sending a second reconfiguration message including information about the next-hop CPC configuration to the communication device.

[0173] According to some embodiments, the method comprises: moreover, The following actions may also be included:

[0174] Action 1940 The first network node 511 triggers a CPC SN addition procedure for one or more target candidate SNs indicated by the second network node 512 or the first target candidate SN T-SN1 for one or more target candidate PSCells in the second-hop CPC configuration.

[0175] The first network node 511 may trigger the SN addition procedure for the CPC by sending an SN addition request for the CPC to the second target candidate SN (T-SN2) including an indication that this is a second-hop CPC, and receiving an SN addition request Ack including at least one SCG configuration associated with at least one of the one or more target candidate PSCells requested by the first network node 511. The sending of the SN addition request for the CPC to the second target candidate SN (T-SN2) may be performed before or after the first-hop CPC is performed for the first target candidate SN (T-SN1).

[0176] Action 1950 The first network node 511 sends an SN modification request to the second network node 512 when an intra-SN-CPC first hop configuration is initiated by the first network node 511 .

[0177] The first network node 511 sends a data forwarding address indication to the second network node 512 or the first target candidate SN (T-SN1) if inter-SN-CPC configuration is initiated by the first network node 511.

[0178] The first network node 511 sends an SN addition request to a first target candidate SN (T-SN1) when the inter-SN-CPC first-hop configuration is initiated by the first network node 511.

[0179] Action 1960 The first network node 511 triggers an SN release or SCG deactivation procedure for one or more target candidate SNs indicated by the second network node 512 or the first target candidate SN (T-SN1) for one or more target candidate PSCells in the second-hop CPC configuration.

[0180] According to this embodiment, a method performed in a second network node 512 for processing a multi-hop configuration of a conditional primary secondary cell change or primary secondary cell group cell change (CPC) of a communication device 530, 531 is described with reference to Figure 20. The communication device 530, 531 is configured in a wireless communication network 500 to have dual connectivity with a master cell group (MCG) managed by a first network node 511 and a secondary cell group (SCG) managed by a second network node 512. The method comprises the following actions, which may be performed in any suitable order:

[0181] Action 2010 The second network node 512 sends a request for CPC to the first network node 511 or the communication device 530. The request for CPC may include one or more of the following information: Indication that multi-hop CPC is allowed; Indication of the maximum number of CPC hops allowed; · First-hop intra-SN CPC configuration; · Configuration of subsequent hop intra-SN CPC; · Configuring a second-hop inter-SN CPC to another target candidate SN; An indication of whether next CPC hop configuration is allowed.

[0182] The CPC request can be one of the following messages: · an SN change required message sent to the first network node 511 when the second network node 512 decides to configure an inter-SN CPC for the first target candidate SN (T-SN1); The second network node 512 is an intra-SN CPC of composition Thenan SN modification required message sent to the first network node 511 when determining and initiating a second-hop intra-SN CPC configuration or inter-SN CPC configuration for the first target candidate SN (T-SN1); A reconfiguration message sent to the communication device 530 when the second network node 512 decides to modify the first-hop intra-CPC to include the configuration of the second-hop intra-CPC.

[0183] According to this embodiment, a method performed in a first target candidate secondary node (T-SN1) for processing a multi-hop configuration of a conditional primary secondary cell change or primary secondary cell group cell change (CPC) of a communication device 530, 531 is described with reference to Figure 21. The communication device 530, 531 is configured in a wireless communication network 500 to have dual connectivity with a master cell group (MCG) managed by a first network node 511 and a secondary cell group (SCG) managed by a second network node 512. The method comprises the following actions, which may be performed in any suitable order:

[0184] Action 2110 The first target candidate secondary node (T-SN1) receives a request for CPC from the first network node 511.

[0185] Action 2120 The first target candidate secondary node (T-SN1) configures a multi-hop CPC by configuring a first-hop CPC and including information about the second-hop CPC, or by configuring a first-hop CPC and initiating configuration of a second-hop CPC for the second target candidate secondary node (T-SN2).

[0186] Action 2130 The first target candidate secondary node (T-SN1) sends a response message to the first network node 511. The response message may include one or more of the following information: iv. an indication that it is a multi-hop CPC configuration; v. Identifiers of one or more target candidate cells for next or subsequent hop CPC configuration; vi. Identifiers of one or more target candidate SNs associated with one or more target candidate cells.

[0187] The method may further include the following actions:

[0188] Action 2140 The first target candidate secondary node (T-SN1) may receive a message from the first network node 511 confirming completion of the second-hop CPC configuration.

[0189] According to some embodiments, a first method performed in a communications device 530, 531 for processing a multi-hop configuration of a conditional primary secondary cell change or primary secondary cell group cell change (CPC) of the communications device 530, 531 is described with reference to Figure 22. The communications device 530, 531 is configured in a wireless communications network 500 to have dual connectivity with a master cell group (MCG) managed by a first network node 511 and a secondary cell group (SCG) managed by a second network node 512. The method includes the following actions, which may be performed in any suitable order:

[0190] Action 2210 The communication device 530, 531 receives a reconfiguration message from the first network node 511 or the second network node 512. The reconfiguration message includes information about the configuration of the first-hop CPC and encapsulated information about future CPC hops.

[0191] Action 2220 The communication devices 530, 531 evaluate the execution conditions of the CPC candidates based on the content of the reconfiguration message. The communication devices 530, 531 evaluate the execution conditions of the first-hop CPC candidates, and after executing the first-hop CPC, may evaluate the execution conditions of future CPC hops, such as second-hop CPC candidates.

[0192] Action 2230 The communications device 530, 531 sends a completion message to the first network node 511 or the second network node 512 in response to the reconfiguration message.

[0193] According to some embodiments, a second method performed in a communications device 530, 531 for processing a multi-hop configuration of a conditional primary secondary cell change or primary secondary cell group cell change (CPC) of the communications device 530, 531 is described with reference to Figure 23. The communications device 530, 531 is configured in a wireless communications network 500 to have dual connectivity with a master cell group (MCG) managed by a first network node 511 and a secondary cell group (SCG) managed by a second network node 512. The method includes the following actions, which may be performed in any suitable order:

[0194] Action 2310 The communication device 530, 531 receives a first reconfiguration message from the first network node 511. The first reconfiguration message includes information about the first-hop CPC configuration.

[0195] Action 2320 The communication devices 530, 531 evaluate the execution conditions of the CPC candidates based on the content of the first reconfiguration message.

[0196] Action 2330 The communication device 530, 531 receives a second reconfiguration message from the first network node 511. The second reconfiguration message includes information about the second-hop CPC configuration.

[0197] Action 2330 After executing the first-hop CPC, the communication devices 530 and 531 evaluate the execution conditions of the CPC candidate based on the content of the second reconfiguration message.

[0198] Action 2330 The communications device 530, 531 transmits a reconfiguration complete message to the first network node 511 in response to the second reconfiguration message.

[0199] According to some embodiments, a third method performed in a communications device 530, 531 for processing a multi-hop configuration of a conditional primary secondary cell change or primary secondary cell group cell change (CPC) of the communications device 530, 531 is described with reference to Figure 24. The communications device 530, 531 is configured in a wireless communications network 500 to have dual connectivity with a master cell group (MCG) managed by a first network node 511 and a secondary cell group (SCG) managed by a second network node 512. The method includes the following actions, which may be performed in any suitable order:

[0200] Action 2410 The communication device 530, 531 receives a first reconfiguration message from the first network node 511. The first reconfiguration message includes information about the first-hop CPC configuration.

[0201] Action 2420 The communication device 530, 531 receives a second reconfiguration message from the first network node (511), the second reconfiguration message including information about the second-hop CPC configuration and an indication that the CPC configuration applies to the second CPC hop.

[0202] Action 2430 The communication device 530, 531 evaluates the performance conditions of the first-hop CPC candidates based on the content of the first reconfiguration message.

[0203] Action 2431 After executing the first-hop CPC, the communication devices 530 and 531 evaluate the execution conditions of the second-hop CPC candidates based on the content of the second reconfiguration message.

[0204] Action 2440 The communication device 530 , 531 sends a completion message to the first network node 511 .

[0205] FIG. 25 is a schematic block diagram illustrating an exemplary embodiment of a network node, which may be a first network node 511, a second network node, or a first target candidate secondary node (T-SN1).

[0206] To perform the method in the first network node 511, the second network node 512, and the first target candidate secondary node (T-SN1), the first network node 511, the second network node 512, and the first target candidate secondary node (T-SN1) may include modules as shown in Figure 25. The first network node 511, the second network node 512, and the first target candidate secondary node (T-SN1) may include a receiving module 2510, a transmitting module 2520, a determining module 2530, a processing module 2540, a memory 2550, etc.

[0207] The network nodes 511, 512 are the MN, S-SN and target candidate T-SN1 and are configured to perform any one of the actions described above with respect to the MN, S-SN and target candidate T-SN1.

[0208] The method according to the present embodiment may be implemented via one or more processors, such as the processor 1960 in the network nodes 511, 512, with computer program code for performing the functions and actions of the present embodiment. The above program code may be provided as a computer program product, for example in the form of a computer-readable medium or data carrier 2580 as shown in FIG. 25, carrying computer program code 2570 for performing the present embodiment when loaded into the network nodes 511, 512. One form of such a carrier is a CD-ROM; however, other data carriers, such as a memory stick, are also possible. The computer program code may also be provided as pure program code on a server or cloud and downloaded to the network nodes 511, 512.

[0209] Figure 26 illustrates an exemplary embodiment of a communications device 530 in which the methods performed by the communications device 530 may be implemented. The communications device 530 is configured with modules as shown in Figure 26. The communications device 530 includes a receiving module 2610, a transmitting module 2620, a determining module 2630, a processing module 2640, a memory 2650, etc. The communications device 530 is configured to perform any one of the method actions described above with respect to a UE.

[0210] The method according to the present embodiment may be implemented via one or more processors, such as the processor 2660 in the UE 530, with computer program code for performing the functions and actions of the present embodiment. The above-mentioned program code may be provided as a computer program product, for example in the form of a computer-readable medium or data carrier 2680 as shown in FIG. 26, carrying computer program code 2670 for performing the present embodiment when loaded into the UE 530. One form of such a carrier is a CD-ROM. However, other data carriers, such as a memory stick, are also possible. The computer program code may also be provided as pure program code on a server or cloud and downloaded to the communication device 530.

Claims

1. 1. A method, performed in a first network node of a wireless communication network, for processing a conditional primary secondary cell change or conditional primary secondary cell group cell change (CPC) multi-hop configuration for a communication device configured with a dual connection to a master cell group (MCG) managed by the first network node and a secondary cell group (SCG) managed by a second network node, the method comprising: sending a request for CPC to the second network node or a first target candidate secondary node (SN); receiving a message from the second network node or the first target candidate SN in response to the request of a CPC, the message comprising: an indication that the CPC configuration is a multi-hop CPC configuration; an indication as to whether it is time-critical to configure the first-hop CPC; and An indication of how many hops it consists of; Identifiers of one or more target candidate primary secondary cells (PSCells) for second-hop CPC configuration; Identifiers of one or more target candidate SNs associated with the one or more target candidate PSCells; and configuring a multi-hop CPC of the communication device based on the received message; A method comprising:

2. 10. The method of claim 1, The CPC's request is A first-hop configuration or a part of a configuration applied in a first-hop CPC; an indication of which CPC hops are required; and an indication of a maximum number of CPC hops supported by the communications device; and The method includes one or more of:

3. 10. The method of claim 1, The method, wherein configuring a multi-hop CPC of the communication device based on the received message includes creating a reconfiguration message including information on both a first-hop CPC configuration and a next-hop CPC configuration, and sending the reconfiguration message to the communication device.

4. 10. The method of claim 1 further comprising: Triggering a CPC SN addition procedure for the one or more target candidate SNs indicated by the second network node or the first target candidate SN for the one or more target candidate PSCells in the second-hop CPC configuration.

5. 10. The method of claim 1 further comprising: Triggering an SN release or SCG deactivation procedure for the one or more target candidate SNs indicated by the second network node or the first target candidate SN for the one or more target candidate PSCells in the second-hop CPC configuration.

6. 10. The method of claim 1, Configuring a multi-hop CPC of the communication device based on the received message includes: creating a first reconfiguration message including information about a first-hop CPC configuration and sending the first reconfiguration message to the communication device, and then creating a second reconfiguration message including information about a next-hop CPC configuration and sending the second reconfiguration message to the communication device; creating a first reconfiguration message including information about a first-hop CPC configuration, sending the first reconfiguration message to the communication device, then storing information about a next-hop CPC configuration, and sending a second reconfiguration message to the communication device after the first-hop CPC has been performed, the second reconfiguration message including the information about the next-hop CPC configuration; A method comprising any one of the following:

7. 10. The method of claim 1 further comprising:

20. The method of claim 19, further comprising: if intra-SN-CPC first-hop configuration is initiated by the first network node, sending an SN modification request to the second network node.

8. 10. The method of claim 1 further comprising: If inter-SN-CPC configuration is initiated by the first network node, sending a data forwarding address indication to the second network node or the first target candidate SN.

9. 10. The method of claim 1 further comprising: If inter SN-CPC first hop configuration is initiated by the first network node, sending an SN addition request to the first target candidate SN.

10. 10. The method of claim 1 further comprising: If inter SN-CPC first hop configuration is initiated by the second network node, receiving an SN change need from the second network node.

11. 10. The method of claim 1 further comprising: If intra-SN-CPC first hop configuration is initiated by the second network node, receiving an SN modification need from the second network node.

12. 5. The method of claim 4, Triggering the SN addition procedure of the CPC includes: sending a CPC SN addition request to a second target candidate SN, the request including an indication that the CPC is a second-hop CPC; receiving an SN Addition Request Ack including at least one SCG configuration associated with at least one of the one or more target candidate PSCells requested by the first network node; A method comprising:

13. 13. The method of claim 12, The method, wherein sending a CPC SN addition request to the second target candidate SN is performed after performing a first-hop CPC for the first target candidate SN.

14. 13. The method of claim 12, The method, wherein sending a CPC SN addition request to the second target candidate SN is performed before performing a first-hop CPC for the first target candidate SN.

15. 1. A method performed in a communications device for processing a conditional primary secondary cell change or a conditional primary secondary cell group cell change (CPC) multi-hop configuration, the communications device being configured with a dual connection to a Master Cell Group (MCG) managed by a first network node of a wireless communications network and a Secondary Cell Group (SCG) managed by a second network node, the method comprising: receiving a reconfiguration message from the first network node or the second network node, the reconfiguration message including information about a configuration of a first-hop CPC and encapsulated information about future CPC hops; evaluating the execution conditions of the candidate CPCs based on the content of the reconfiguration message; sending a completion message to the first network node or the second network node in response to the reconfiguration message; A method comprising:

16. 16. The method of claim 15, The method, wherein evaluating the execution conditions of a candidate CPC includes evaluating the execution conditions of the candidate first-hop CPC, and after execution of the first-hop CPC, evaluating the execution conditions of the candidate second-hop CPC for the future CPC hop.

17. 1. A method performed in a communications device for processing a conditional primary secondary cell change or a conditional primary secondary cell group cell change (CPC) multi-hop configuration, the communications device being configured with a dual connection to a Master Cell Group (MCG) managed by a first network node of a wireless communications network and a Secondary Cell Group (SCG) managed by a second network node, the method comprising: receiving a first reconfiguration message from the first network node, the first reconfiguration message including information regarding a configuration of a first-hop CPC; Evaluating the execution conditions of the candidate CPCs based on the content of the first reconfiguration message; receiving a second reconfiguration message from the first network node, the second reconfiguration message including information regarding a configuration of a second-hop CPC; After the first-hop CPC is performed, Evaluating the execution conditions of the candidate CPC based on the content of the second reconfiguration message; sending a reconfiguration complete message to the first network node in response to the second reconfiguration message; A method comprising:

18. 1. A method performed in a communications device for processing a conditional primary secondary cell change or a conditional primary secondary cell group cell change (CPC) multi-hop configuration, the communications device being configured with a dual connection to a Master Cell Group (MCG) managed by a first network node of a wireless communications network and a Secondary Cell Group (SCG) managed by a second network node, the method comprising: receiving a first reconfiguration message from the first network node, the first reconfiguration message including information regarding a configuration of a first-hop CPC; receiving a second reconfiguration message from the first network node, the second reconfiguration message including information regarding a configuration of a second-hop CPC and an indication that a CPC configuration is applied to the second-hop CPC; evaluating performance conditions of the candidate first-hop CPCs based on the content of the first reconfiguration message; After the first-hop CPC is performed, evaluating performance conditions of the candidate second-hop CPCs based on the content of the second reconfiguration message; sending a completion message to the first network node; A method comprising:

19. A first network node configured to perform the method of any one of claims 1 to 14.

20. A communications device configured to perform the method of any one of claims 15 to 18.

Images