Method and apparatus for configuration replacement operation in cpac process

Abstract

Embodiments of the present application relate to methods and apparatuses for conditional primary cell in configuration replacement operation for primary secondary cell group (PSCell) addition and change (CPAC) procedure under 3rd Generation Partnership Project (3GPP) 5G system, etc. According to embodiments of the present application, a method performed by a radio access network (RAN) node can comprise receiving configuration information related to a CPAC procedure, and in response to the configuration information related to the CPAC procedure being modified, communicating the modified configuration information with another RAN node via an Xn interface or an X2 interface.

Description

Technical Field

[0001] Embodiments of this application generally relate to wireless communication technology, and more particularly to a method and apparatus for performing configuration replacement operations during Conditional Primary Cell Secondary Cell Group (PSCell) Addition and Change (CPAC) processes. Background Technology

[0002] Next-Generation Radio Access Networks (NG-RAN) support Multiple Radio Dual Connectivity (MR-DC) operation. In an MR-DC scenario, User Equipment (UE) with multiple transceivers can be configured to utilize resources provided by two different nodes via a non-ideal backhaul connection. One node can provide New Radio (NR) access, and the other can provide Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) (E-UTRA) or NR access. One node can act as the primary node (MN), and the other can act as the secondary node (SN). The MN and SN are connected via a network interface (e.g., the Xn interface as specified in the 3GPP standards document), and at least the MN is connected to the core network.

[0003] According to the 3GPP standard document, the CPAC procedure is defined as a PSCell addition or modification performed by the UE when execution conditions are met. The UE begins evaluating the execution conditions upon receiving CPAC configuration information and stops evaluating them once the PSCell addition and / or PSCell modification procedure is triggered. Currently, the details of the mechanism for configuration replacement operations during the CPAC procedure in MR-DC scenarios within 3GPP 5G systems or networks are not discussed in 3GPP 5G technologies. Summary of the Invention

[0004] Some embodiments of this application provide a method for wireless communication. The method can be performed by a radio access network (RAN) node, such as an MN, source SN, or target SN in an MR-DC scenario. The method includes: receiving configuration information related to a CPAC procedure; and, in response to a modification of the configuration information related to the CPAC procedure, communicating the modified configuration information to another RAN node via an Xn interface or an X2 interface.

[0005] Some embodiments of this application provide an apparatus for wireless communication. The apparatus includes: a non-transitory computer-readable medium having computer-executable instructions stored thereon; a receiving circuitry; a transmitting circuitry; and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry, and the transmitting circuitry, wherein the computer-executable instructions cause the processor to perform the methods described above, executed by a RAN node.

[0006] Details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description, the drawings, and the claims. Attached Figure Description

[0007] To describe the advantages and features of this application, the description of this application is presented by reference to specific embodiments illustrated in the accompanying drawings. These drawings depict only exemplary embodiments of this application and should therefore not be construed as limiting its scope.

[0008] Figure 1 This application illustrates a schematic diagram of a wireless communication system according to some embodiments of the present application.

[0009] Figure 2 An exemplary flowchart illustrating a method for communicating modified configuration information related to a CPAC process between RAN nodes according to some embodiments of this application;

[0010] Figure 3 An exemplary flowchart illustrating a CPAC replacement operation triggered by a target SN during a conditional PSCell Addition (CPA) process according to some embodiments of this application;

[0011] Figure 4 An exemplary flowchart illustrating a CPAC replacement operation triggered by a target SN during a conditional PSCell change (CPC) process between SNs starting from MN, according to some embodiments of this application;

[0012] Figure 5 An exemplary flowchart illustrating a CPAC replacement operation triggered by a target SN during a CPC process initiated by an SN, according to some embodiments of this application;

[0013] Figure 6 Further flowchart illustrating a CPAC replacement operation triggered by a target SN in a CPA process based on a PSCell cancellation message, according to some embodiments of this application;

[0014] Figure 7 An exemplary flowchart illustrating a CPAC replacement operation triggered by a target SN in a CPC process initiated by an MN based on a PSCell cancellation message, according to some embodiments of this application;

[0015] Figure 8 An exemplary flowchart illustrating a CPAC replacement operation triggered by a target SN in a CPC process initiated by a SN based on a PSCell cancellation message, according to some embodiments of this application;

[0016] Figure 9An exemplary flowchart illustrating the CPAC replacement operation triggered by MN in a CPA process based on an SN modification request message, according to some embodiments of this application;

[0017] Figure 10 Further flowchart illustrating the CPAC replacement operation triggered by MN in a CPA process based on a PSCell cancellation message, according to some embodiments of this application;

[0018] Figure 11 An exemplary flowchart illustrating an MN-triggered CPAC replacement operation in a CPC process initiated by an MN based on an SN modification request message, according to some embodiments of this application;

[0019] Figure 12 Further flowchart illustrating the MN-triggered CPAC replacement operation in a CPC process initiated by an MN based on a PSCell cancellation message, according to some embodiments of this application;

[0020] Figure 13 An exemplary flowchart illustrating a CPAC replacement operation triggered by the source SN in a CPC process initiated by an SN based on a SN modification request message, according to some embodiments of this application;

[0021] Figure 14 Further exemplary flowcharts illustrating a CPAC replacement operation triggered by the source SN in a CPC process initiated based on a PSCell cancellation message, according to some embodiments of this application; and

[0022] Figure 15 Exemplary block diagrams illustrating some embodiments of the device according to this application. Detailed Implementation

[0023] The detailed description of the accompanying drawings is intended to illustrate preferred embodiments of the present application and is not intended to represent the only form in which the present application may be practiced. It should be understood that the same or equivalent functionality may be achieved through different embodiments intended to be covered within the spirit and scope of the present application.

[0024] Reference will now be made in detail to some embodiments of this application, examples of which are illustrated in the accompanying drawings. For ease of understanding, embodiments are provided in specific network architectures and new service scenarios, such as 3GPP 5G, 3GPP LTE Release 8, etc. It has been considered that, with the development of network architectures and new service scenarios, all embodiments in this application are also applicable to similar technical problems; furthermore, the terminology stated in this application may be changed without affecting the principles of this application.

[0025] Figure 1 A schematic diagram illustrating a wireless communication system according to some embodiments of this application.

[0026] like Figure 1 As shown, the wireless communication system 100 may be a dual-connectivity system 100, comprising at least one UE 101, at least one MN 102, and at least one SN 103. Specifically, for illustrative purposes, Figure 1 The dual connectivity system 100 includes a UE 101 shown, an MN 102 shown, and an SN 103 shown. Although in Figure 1 A specific number of UEs 101, MN 102 and SN 103 are depicted, but it is understood that any number of UEs 101, MN 102 and SN 103 may be included in the wireless communication system 100.

[0027] refer to Figure 1 UE 101 can connect to MN 102 and SN 103 via a network interface (e.g., the Uu interface as specified in the 3GPP standard document). MN 102 and SN 103 can connect to each other via a network interface (e.g., the Xn interface as specified in the 3GPP standard document). MN 102 can connect to MN 102 and SN 103 via a network interface (e.g., the Xn interface as specified in the 3GPP standard document). Figure 1 (Not shown in the image) Connects to the core network. UE 102 can be configured to utilize resources provided by MN 102 and SN 103 to perform data transmission.

[0028] MN 102 can refer to a radio access node that provides control plane connectivity to the core network. In an embodiment of this application, in an E-UTRA-NR dual connectivity (EN-DC) scenario, MN 102 can be an eNB. In another embodiment of this application, in a next-generation E-UTRA-NR dual connectivity (NGEN-DC) scenario, MN 102 can be an ng-eNB. In yet another embodiment of this application, in an NR-E-UTRA dual connectivity (NE-DC) scenario or an NR-NR dual connectivity (NR-DC) scenario, MN 102 can be a gNB.

[0029] MN 102 may be associated with a primary cell group (MCG). An MCG may refer to a group of serving cells associated with MN 102, and may include the primary cell (PCell) of the MCG and one or more optional secondary cells (SCells). The PCell may provide control plane connectivity to UE 101.

[0030] SN 103 may refer to a radio access node that does not have a control plane connection to the core network but provides additional resources to UE 101. In an embodiment of this application, in an EN-DC scenario, SN 103 may be an en-gNB. In another embodiment of this application, in an NE-DC scenario, SN 103 may be an ng-eNB. In yet another embodiment of this application, in an NR-DC scenario or an NGEN-DC scenario, SN 103 may be a gNB.

[0031] SN 103 may be associated with a secondary cell group (SCG). An SCG may refer to a group of serving cells associated with SN 103, and may include a primary secondary cell (PSCell) and one or more optional secondary cells (SCells). The PCell of the MCG and the PSCell of the SCG may also be referred to as a special cell (SpCell).

[0032] In some embodiments of this application, UE 101 may include a computing device, such as a desktop computer, laptop computer, personal digital assistant (PDA), tablet computer, smart TV (e.g., a TV connected to the Internet), set-top box, game console, security system (including security cameras), in-vehicle computer, network device (e.g., router, switch, and modem), etc. In some other embodiments of this application, UE 101 may include a portable wireless communication device, smartphone, cellular phone, flip phone, device with subscriber identity module, personal computer, selective call reception circuitry system, or any other device capable of transmitting and receiving communication signals on a wireless network.

[0033] In some other embodiments of this application, UE 101 may include a wearable device, such as a smartwatch, fitness tracker, optical head-mounted display, etc. Furthermore, UE 101 may be referred to as a subscriber unit, mobile station, mobile base station, user, terminal, mobile terminal, wireless terminal, fixed terminal, subscriber station, user terminal, or device, or described using other terms used in the art.

[0034] Typically, during a SN change procedure in an MR-DC scenario, the source SN is changed to the target SN. The SN change procedure can be initiated by an MN or an SN. According to 3GPP standard document TS37.340, an MN-initiated SN change procedure is used to transfer the UE context from the source SN to the target SN and to change the SCG configuration in the UE from one SN to another. An SN-initiated SN change procedure is also used to transfer the UE context from the source SN to the target SN and to change the SCG configuration in the UE from one SN to another. 3GPP standard document TS37.340 also specifies SN addition and SN modification procedures. SN modification procedures can be MN-initiated SN modification procedures or SN modification procedures initiated by an SN involving an MN.

[0035] Currently, according to 3GPP standard documents, the protocols for the Conditional PSCell Addition (CPA) procedure and the Conditional PSCell Change (CPC) procedure between SNs are as follows.

[0036] In the CPA process:

[0037] 1. The MN can initiate the CPA process by sending SN Add Request messages to multiple candidate target SNs. In the SN Add Request message, the MN can indicate a list of cells that can be used as PSCells, such as cells 1, 2, 3, ... and 10.

[0038] 2. The candidate target SN selects several cells from the cell list provided by the MN as candidate PSCells, for example, cells 1, 2, 3, ... and 5. The candidate target SN will then reply with an SN Add Request Confirmation Message. The SN Add Request Confirmation Message may contain an RRC reconfiguration message, which provides the UE with the SN RRC reconfiguration to be used during the CPA procedure and when the UE accesses the corresponding target SN.

[0039] 3. The MN generates an MN RRC reconfiguration message. The MN RRC reconfiguration message may contain an RRC conditional reconfiguration element, which consists of an execution condition (generated by the MN) and an SN RRC reconfiguration message (generated by the candidate target SN). The MN sends the generated MN RRC reconfiguration message to the UE.

[0040] 4. Upon receiving a CPA-related RRC reconfiguration message, the UE begins to evaluate whether the execution conditions are met (e.g., whether the measured link quality of a candidate target SN is better than a threshold). If the execution conditions are met, the UE begins to access the corresponding target SN.

[0041] During the CPC process between SNs:

[0042] 1. An inter-SN CPC process can be initiated by either the MN or the source SN. The source SN can initiate an inter-SN CPC process by sending an SN change request message to the MN, and the SN change request message contains inter-SN CPC-related information. Upon receiving an SN change request message that triggers an inter-SN CPC process, or when the MN initiates an inter-SN CPC process, the MN sends SN add request messages to multiple candidate target SNs.

[0043] 2. The candidate target SN can reply with an SN Add Request Confirmation Message and access the corresponding target SN. The SN Add Request Confirmation Message contains an RRC Reconfiguration Message, which provides the UE with the SN RRC reconfiguration to be used during the execution of the inter-SN CPC procedure.

[0044] 3. The MN generates an MN RRC reconfiguration message. The MN RRC reconfiguration message contains an RRC conditional reconfiguration element, which consists of an execution condition (generated by the MN) and an SN RRC reconfiguration message (generated by the candidate target SN). The MN sends the generated MN RRC reconfiguration message to the UE.

[0045] 4. Upon receiving a CPC-related RRC reconfiguration message, the UE begins to evaluate whether the execution conditions are met (e.g., whether the measured link quality of a candidate target SN is better than a threshold). If the execution conditions are met, the UE begins to access the corresponding target SN.

[0046] According to the 3GPP Release 17 protocol, CPA and inter-SN CPC procedures will be supported. However, details regarding configuration replacement operations during the CPAC process have not been discussed in 3GPP 5G technologies. Some embodiments of this application provide a mechanism for implementing configuration replacement operations during the CPAC process in MR-DC scenarios such as 3GPP 5G systems. Configuration replacement operations during the CPAC process may also be referred to as replacement operations during the CPAC process, CPAC replacement operation, CPAC replacement process, configuration modification operation during the CPAC process, modification operation during the CPAC process, CPAC modification operation, CPAC modification process, etc.

[0047] Specifically, the CPAC procedure can be used to prepare multiple candidate PSCells within the same target SN. A CPAC replacement operation implies a modification to a previously configured CPAC preparation procedure. For example, a CPAC replacement operation is an operation that replaces the existing configuration of one or more PSCells. Some embodiments of this application design information elements within the Xn message in a manner that supports flexible CAPC replacement operations.

[0048] During the CPAC process, the MN or source SN may indicate the maximum or recommended total number of PSCells that can or should be prepared by the target SN. If the total number of PSCells prepared by a candidate target SN is less than the expected number, other candidate target SNs may prepare more PSCells, but it is unclear how different RAN nodes coordinate to modify the total number of PSCells that can be prepared by the candidate target SNs. Some embodiments of this application ensure that the overall total number of prepared PSCells is less than the maximum value determined by the starting RAN node (e.g., MN). For SN-initiated inter-SN CPC procedures, some embodiments of this application ensure appropriate inter-SN CPC replacement operations, such as modifying relevant execution conditions or modifying relevant SN measurement configurations, and ensure that the source SN is aware of the PSCells prepared by the candidate target SNs.

[0049] Some embodiments of this application provide a mechanism to support CPAC replacement procedures for the following scenarios: CPA procedures; CPC procedures initiated by an MN; and CPC procedures initiated by an SN. In these embodiments, the CPAC replacement procedure can be triggered by an MN, a source SN, or a target SN. These embodiments may include adding new information elements to existing Xn and / or X2 messages to support the CPAC replacement procedure, or introducing new Xn and / or X2 messages to support the CPAC replacement procedure. Thus, coordination between the involved RAN nodes (e.g., MN, source SN, and target SN) can be effectively performed. Further details regarding embodiments of this application will be described below in conjunction with the accompanying drawings.

[0050] Figure 2 An exemplary flowchart illustrating a method for communicating modified configuration information related to the CPAC process between RAN nodes according to some embodiments of this application. Figure 2 The exemplary method 200 in the embodiments can be executed by a RAN node, for example:

[0051] -MN (for example, respectively) Figures 3 to 14 The MN 320, MN 420, MN520, MN 620, MN 720, MN 820, MN 920, MN 1020, MN 1120, MN1220, MN1320 or MN 1420 described and shown in any of these; or

[0052] - The target SN during the SN addition or SN change process (e.g., respectively such as Figures 3 to 14The T-SN 330, T-SN 430, T-SN 530, T-SN 630, T-SN 730, T-SN 830, T-SN 930, T-SN 1030, T-SN 1130, T-SN 1230, T-SN 1330 or T-SN 1430 described and shown in any of these documents; or

[0053] - The source SN during the SN addition or SN change process (e.g., respectively such as Figure 4 , 5 (S-SN 440, S-SN 540, S-SN 740, S-SN 840, S-SN 1140, S-SN 1240, S-SN 1340 or S-SN 1440 as described and shown in any of 7, 8 and 11 to 14).

[0054] Although the description pertains to RAN nodes, it should be understood that other devices can be configured to perform similar functions. Figure 2 The method is as follows. The source SN can also be called S-SN, source SN, etc. The target SN can also be called T-SN, target SN, etc. Figure 2 This embodiment assumes that the UE has already been configured with CPAC. The relevant RAN node wants to replace (i.e. modify) the previous CPAC configuration before performing the CPAC procedure. Figure 2 The embodiments assume that MN, source SN, or target SN can be combined in any of the EN-DC, NGEN-DC, NE-DC, and NR-DC scenarios.

[0055] In such Figure 2 In the exemplary method 200 shown, during operation 201, the RAN node receives configuration information related to the CPAC procedure. The RAN node may be an MN, S-SN, or T-SN. In an embodiment, during the CPA procedure, the MN may transmit an Xn or X2 message to the T-SN containing CPA-related configuration information (e.g., a cell list) provided by the MN to initiate the CPA procedure. The T-SN may transmit an Xn or X2 message to the MN conveying CPA-related configuration information (e.g., RRC configuration for each cell) provided by the T-SN.

[0056] In another embodiment, during an inter-SN CPC process initiated by the MN, the MN may transmit an Xn or X2 message to the T-SN containing CPC-related configuration information (e.g., a cell list) provided by the MN to initiate the inter-SN CPC process initiated by the MN. The T-SN may transmit an Xn or X2 message to the MN conveying CPC-related configuration information (e.g., RRC configuration for each cell) provided by the T-SN.

[0057] In an additional embodiment, during an inter-SN CPC process initiated by the S-SN, the S-SN may send an Xn or X2 message to the MN containing CPC-related configuration information (e.g., cell list and execution conditions) provided by the S-SN to initiate the S-SN-initiated inter-SN CPC process. The MN may send an Xn or X2 message to the T-SN conveying CPC-related configuration information (e.g., cell list) provided by the T-SN. Alternatively, the T-SN may send an Xn or X2 message to the MN conveying CPC-related configuration information (e.g., RRC configuration for each cell) provided by the T-SN. The MN may send an Xn or X2 message to the S-SN containing CPC-related configuration information (e.g., prepared cell list) provided by the T-SN.

[0058] In operation 202, in response to the modification of configuration information related to the CPAC process, the RAN node communicates the modified configuration information to another RAN node via the Xn interface or the X2 interface.

[0059] According to some embodiments of exemplary method 200, the RAN node is the MN in the MR-DC scenario (e.g., as...). Figure 1 As described and shown in the document (MN 102), and the other RAN node mentioned above is the target SN in the MR-DC scenario (e.g., as Figure 1 (SN 103 as described and shown in the document). According to some other embodiments of exemplary method 200, the RAN node is the target SN in the MR-DC scenario, and the other RAN node mentioned above is the MN in the MR-DC scenario.

[0060] In some embodiments, Figure 2 In operation 202, the MN transmits a message to the target SN to convey modified configuration information. For example, the message transmitted from the MN to the target SN could be an SN modification request message and / or an auxiliary gNB (SgNB) modification request message. Figures 3 to 5 Specific examples are described in 9, 11 and 13.

[0061] In an embodiment, a message transmitted from the MN to the target SN includes at least one updated measurement result associated with at least one PSCell of the target SN. For example, the message includes two updated measurement results associated with two PSCells prepared by the target SN.

[0062] In another embodiment, the message transmitted from MN to target SN includes at least one of the following:

[0063] (1) An indicator that indicates an operation to replace the existing configuration of one or more PSCells;

[0064] (2) Updated configuration information related to the MN's primary cell (PCell);

[0065] (3) Updated configuration information related to the PSCell of the source SN in the MR-DC scenario;

[0066] (4) The maximum number of PSCells allowed (e.g., by MN) prepared by the target SN;

[0067] (5) References to one or more PSCells to be added, for example, a list of PSCells to be added;

[0068] (6) A reference to one or more PSCells to be modified, for example, a list of PSCells to be modified;

[0069] (7) References to one or more PSCells to be cancelled, for example, a list of PSCells to be cancelled;

[0070] (8) The security key to be used by the target SN; and

[0071] (9) Reporting of measurement results related to the CPAC process.

[0072] In this example, if a message transmitted from MN to target SN contains a reference to a PSCell to be cancelled, then target SN cannot reject the reference to the PSCell to be cancelled. For example, target SN should reply with an acknowledgment message.

[0073] In some embodiments, Figure 2 In operation 202, the MN further receives messages from the target SN to convey the modified configuration information. For example, the messages received by the MN from the target SN may be: an SN modification request confirmation message; an SgNB modification request confirmation message; an SN modification request message; and / or an SgNB modification request message. Figures 3 to 5 Specific examples are described in 9, 11 and 13.

[0074] In this embodiment, the message received by the MN from the target SN includes at least one of the following:

[0075] (1) The maximum number of PSCells that can be prepared by the target SN; and

[0076] (2) References to one or more PSCells to be added, for example, a list of PSCells to be added;

[0077] (3) A reference to one or more PSCells to be modified, for example, a list of PSCells to be modified;

[0078] (4) References to one or more PSCells to be cancelled, for example, a list of PSCells to be cancelled; and

[0079] (5) A reference to one or more admitted PSCells, for example, a list of PSCells admitted by the target SN.

[0080] In this example, if a message received by the MN from the target SN contains a reference to a PSCell to be cancelled, then the MN cannot reject the reference to the PSCell to be cancelled. For example, the MN should reply with an acknowledgment message.

[0081] In another embodiment, the message received by the MN from the target SN further includes at least one of the following:

[0082] (1) A set of Radio Resource Control (RRC) containers, and each PSCell in the reference of the PSCell to be added is associated with an RRC container in this set of RRC containers;

[0083] (2) Another set of RRC containers, and each PSCell in the reference of the PSCell to be modified is associated with an RRC container in this other set of RRC containers; and

[0084] (3) Another set of RRC containers, and each PSCell in the reference of the admitted PSCell is associated with an RRC container in the other set of RRC containers mentioned above.

[0085] According to some embodiments, in Figure 2 In operation 202, the MN receives a PSCell cancellation message from the target SN to convey the modified configuration information. Figures 6 to 8 Specific examples are described herein. According to some other embodiments, in... Figure 2 In operation 202, the MN sends an additional PSCell cancellation message to the target SN to convey the modified configuration information. Figure 10 , 12 And specific examples are described in 14.

[0086] In an embodiment, the PSCell cancellation message and / or other PSCell cancellation messages include: a reference to the PSCell to be cancelled; and / or an indication of the PSCell to be cancelled. The indication of the PSCell to be cancelled may be the reason for PSCell cancellation. In an example, the indication of the PSCell to be cancelled in the PSCell cancellation message received by the MN from the target SN includes at least one of the following:

[0087] (1) Changes in CPA resources;

[0088] (2) CPA replacement operation is required during the CPAC process;

[0089] (3) Changes in CPC resources between SNs; and

[0090] (4) SN CPC replacement operation is required during the CPAC process.

[0091] In another instance, the indication for the PSCell to be cancelled in a separate PSCell cancellation message transmitted from the MN to the target SN includes: changes to the resources of the MN; and / or changes to the resources of the source SN.

[0092] According to some embodiments of exemplary method 200, the RAN node is the source SN in the MR-DC scenario (e.g., as...). Figure 1 As described and shown in the document (SN 103), and the other RAN node mentioned above is the MN in the MR-DC scenario (e.g., as...). Figure 1 (MN 102 as described and shown in the document). According to some other embodiments of exemplary method 200, the RAN node is the source SN in the MR-DC scenario, and the other RAN node is the MN in the MR-DC scenario.

[0093] In some embodiments, Figure 2 In operation 202, MN sends a message to the source SN to convey the modified configuration information.

[0094] In an embodiment, the message transmitted from MN to source SN may be an SN change confirmation message and / or an SgNB change confirmation message. Figure 13 and 14 The following describes a specific instance. In this instance, the message includes: a reference to a PSCell prepared by the target SN; and / or an RRC container. The RRC container in the message may include the reference to the PSCell prepared by the target SN. In another instance, the message further includes a set of RRC containers, and each PSCell in the reference to the PSCell prepared by the target SN is associated with an RRC container in this set of RRC containers.

[0095] In another embodiment, the message transmitted from MN to source SN may be: SN modification confirmation message; SgNB modification confirmation message; SN modification request message; and / or SgNB modification request message. Figure 13 A specific instance is described below. In this instance, the message transmitted from MN to source SN includes at least one of the following:

[0096] (1) The maximum number of PSCells that can be prepared by the target SN;

[0097] (2) The reference to the PSCell to be added;

[0098] (3) The reference of the PSCell to be modified; and

[0099] (4) Reference to the PSCell to be cancelled. For example, if this message contains a reference to the PSCell to be cancelled, then the source SN cannot reject the reference to the PSCell to be cancelled. That is, the source SN must accept the reference to the PSCell to be cancelled. For example, the source SN should reply with an acknowledgment message.

[0100] In another instance, this message transmitted from MN to source SN further includes: (1) a set of RRC containers, wherein each PSCell in the reference of the PSCell to be added is associated with an RRC container in this set of RRC containers; and / or (2) another set of RRC containers, wherein each PSCell in the reference of the PSCell to be modified is associated with an RRC container in this other set of RRC containers.

[0101] In some other embodiments, in Figure 2 In operation 202, the MN further receives a message from the source SN to convey the modified configuration information. In this embodiment, the message received by the MN from the source SN may be: an SN modification request confirmation message; an SgNB modification request confirmation message; an SN modification request message; and / or an SgNB modification request message. Figure 4 , 5 Specific examples are described in 11 and 13. In another embodiment, this message received by the MN from the source SN includes at least one of the following:

[0102] (1) An indicator that indicates the operation to replace the existing configuration of the PSCell;

[0103] (2) Updated configuration information related to the PSCell of the source SN in the MR-DC scenario;

[0104] (3) The maximum number of PSCells allowed (e.g., by MN) prepared by the target SN;

[0105] (4) The reference to the PSCell to be added;

[0106] (5) The reference of the PSCell to be modified; and

[0107] (6) Reference to the PSCell to be cancelled. For example, if this message contains a reference to the PSCell to be cancelled, then MN cannot reject the reference to the PSCell to be cancelled. That is, MN must accept the reference to the PSCell to be cancelled. For example, MN should reply with an acknowledgment message.

[0108] According to some embodiments, in Figure 2In operation 202, MN sends a PSCell cancellation message to the source SN to convey the modified configuration information. Figure 7 , 8 And specific examples are described in section 12. According to some other embodiments, in Figure 2 In operation 202, the MN receives an additional PSCell cancellation message from the source SN to convey the modified configuration information. Figure 14 Specific examples are described in the text.

[0109] In some embodiments, a PSCell cancellation message and / or an additional PSCell cancellation message includes: a reference to the PSCell to be cancelled; and / or an indication of the PSCell to be cancelled. For example, the indication of the PSCell to be cancelled is the reason for PSCell cancellation, which indicates the reason related to the PSCell cancellation operation. In an embodiment, the indication of the PSCell to be cancelled in a PSCell cancellation message transmitted from the MN to the source SN includes: (1) a change in inter-SN CPC resources; (2) an inter-SN CPC replacement operation requiring a CPAC process; and / or (3) a change in MN resources. In another embodiment, the indication of the PSCell to be cancelled in an additional PSCell cancellation message received by the MN from the source SN includes a change in source SN resources.

[0110] The details described in all other embodiments of this application (e.g., details conveying modified configuration information about the CPAC process) apply. Figure 2 Examples of implementations. Furthermore, in Figure 2 The details described in the embodiments are applicable Figure 1 and 3 All embodiments up to 15.

[0111] Specifically, some embodiments of this application provide a CPAC replacement process triggered by a target SN. These embodiments specifically provide methods for modifying the SN. Figures 3 to 5 and provide a method for cancellation based on CPAC. Figures 6 to 8 Specific examples are described below. These embodiments provide a CPAC replacement process triggered by a target SN, for example, when the target SN wants to add, remove, or modify a previously configured PSCell. In these embodiments, the target SN triggers the CPAC replacement process by sending an Xn message or an X2 message to the MN. In the embodiment (hereinafter referred to as "Embodiment 1"), the Xn or X2 message may contain any one or a combination of the following CPAC replacement-related information:

[0112] - The maximum number of PSCells that can be prepared by the target SN.

[0113] - A list of PSCells to be added, with each PSCell associated with an RRC container containing the corresponding RRC configuration.

[0114] - A list of PSCells to be modified, and each PSCell to be modified is associated with an RRC container containing the corresponding RRC configuration.

[0115] - List of PSCells to be cancelled.

[0116] In one embodiment of these embodiments, the list of PSCells to be added is selected from a list of target cells that were previously indicated by the initiating node (MN or SN) during the CPAC process but have not yet been prepared. For example, if the initiating node (MN or SN) indicates ten cells (e.g., cells 1, 2, 3, ..., 10) as target PSCells, and the target SN has already prepared five cells (e.g., cells 1, 2, 3, 4, and 5), then the target SN may decide to prepare the remaining five cells (e.g., cells 6, 7, 8, 9, and 10) as additional PSCells to be prepared.

[0117] In another embodiment of these embodiments, the total number of PSCells to be added is less than the difference between "the maximum number of PSCells allowed to be prepared by the target SN (instructed by the starting RAN node)" and "the total number of prepared PSCells," that is, the maximum number of allowed PSCells minus the total number of prepared PSCells. For example, if MN has instructed the target SN to prepare a maximum of 10 PSCells, and 6 PSCells have been prepared so far, 10-6=4, and therefore, 4 more PSCells can be added.

[0118] Figure 3 This document provides an exemplary flowchart illustrating a CPAC replacement operation triggered by a target SN during a Conditional PSCell Addition (CPA) process, according to some embodiments of this application.

[0119] like Figure 3 As shown in the embodiments, in operation 301, MN 320 (e.g., as Figure 1 As described and illustrated, MN 102 transmits an Xn or X2 message to T-SN 330 (i.e., the target SN) to provide updated measurement results associated with the PSCell. In one embodiment, MN 320 transmits an SN MODIFICATION REQUEST message via the Xn interface. In another embodiment, MN 320 transmits an SGNB MODIFICATION REQUEST message via the X2 interface. For example, the updated measurement results are conveyed in an RRC container within the Xn or X2 message, and each RRC container is associated with an associated PSCell identifier (ID).

[0120] After receiving the Xn or X2 message from MN 320, in response to the modification of configuration information related to the CPAC process, T-SN 330 sends a CPAC replacement related message to MN 320 carrying CPAC replacement related information as in Embodiment 1. The CPAC replacement related message may be an SN MODIFICATION REQUEST ACKNOWLEDGE (Xn) message, an SGNB MODIFICATION REQUEST ACKNOWLEDGE (X2) message, an SN MODIFICATION REQUIRED (Xn) message, and / or an SGNB MODIFICATION REQUIRED (X2) message.

[0121] Specifically, in operation 302, after receiving the updated PSCell measurement results from MN 320, T-SN 330 may decide to add, modify, or cancel any PSCells that have been prepared or are to be prepared. T-SN 330 may then respond to MN 320 via the Xn interface with an SN MODIFICATION REQUEST ACKNOWLEDGE message carrying CPAC replacement information as in Example 1 and / or via the X2 interface with an SGNB MODIFICATION REQUEST ACKNOWLEDGE message carrying CPAC replacement information as in Example 1.

[0122] Optionally, in operation 303, after confirming receipt of the updated PSCell measurement results from MN 320, T-SN 330 may further decide to add, modify, or cancel any PSCells that have been prepared or are to be prepared. T-SN 330 may then send an SN MODIFICATION REQUIRED (Xn) message and / or an SGNB MODIFICATION REQUIRED (X2) message to carry CPAC replacement information as in Example 1.

[0123] In operation 304, MN 320 may send an RRC reconfiguration message to UE 310. Then, in operation 305, UE 310 may send an RRC reconfiguration complete message to MN 320.

[0124] The details described in all other embodiments of this application (e.g., details regarding the CPAC replacement process) are applicable. Figure 3 Examples of implementations. Furthermore, Figure 3 The details described in the embodiments are applicable Figure 1 , 2 And all embodiments from 4 to 15.

[0125] Figure 4 This document provides an exemplary flowchart illustrating a CPAC replacement operation triggered by a target SN during a conditional PSCell change (CPC) process between SNs starting from MN, according to some embodiments of this application.

[0126] Similar to Figure 3 Operation 301, such as Figure 4 As shown in the embodiments, in operation 401, MN 420 transmits an SN MODIFICATION REQUEST (Xn) message or an SGNB MODIFICATION REQUEST (X2) message to T-SN 430 to provide updated measurement results associated with the PSCell. The updated measurement results can be conveyed in an RRC container within the Xn or X2 message, and each RRC container is associated with an associated PSCell ID.

[0127] Similar to Figure 3 In the embodiments, Figure 4 In one embodiment, T-SN 430 may, for example, communicate CPAC replacement information as in Embodiment 1 to MN 420 in SN MODIFICATIONREQUEST ACKNOWLEDGE (Xn) message, SGNB MODIFICATION REQUEST ACKNOWLEDGE (X2) message, SN MODIFICATION REQUIRED (Xn) message and / or SGNB MODIFICATION REQUIRED (X2) message.

[0128] Specifically, in operation 402, after receiving the updated PSCell measurement results from MN 420, T-SN 430 may decide to add, modify, or cancel any PSCells that have been prepared or are to be prepared. T-SN 430 may then respond to an SN MODIFICATION REQUEST ACKNOWLEDGE (Xn) message and / or an SGNB MODIFICATION REQUEST ACKNOWLEDGE (X2) message carrying CPAC replacement information as in Example 1.

[0129] Optionally, in operation 403, after confirming receipt of the updated PSCell measurement results from MN 420, T-SN 430 may further decide to add, modify, or cancel any PSCells that have been prepared or are to be prepared. T-SN 430 may then send an SN MODIFICATION REQUIRED (Xn) message and / or an SGNB MODIFICATION REQUIRED (X2) message to carry information related to CPAC replacement as in Example 1.

[0130] Similar to Figure 3 Operations 304 and 305 are performed. In operation 404, MN 420 may send an RRC reconfiguration message to UE 410. Then, in operation 405, UE 410 may send an RRC reconfiguration complete message to MN 420.

[0131] In operation 406, MN 420 may transmit an SN MODIFICATION CONFIRM message to T-SN 430.

[0132] In such Figure 4 In the MN-initiated inter-SN CPC process shown in the embodiments, when confirming an SN modification regarding the CPAC replacement process (i.e., sending an SN modification confirmation (Xn) message to T-SN 430 in operation 406), MN 420 can also notify S-SN 440 of the CPAC replacement process by sending an Xn message containing CPAC replacement-related information as in Embodiment 1. The Xn message can be an existing SN MODIFICATION REQUEST message or a new Xn message.

[0133] According to some embodiments, if an existing SN MODIFICATION REQUEST message is used to notify the source SN of a CPAC replacement process, an additional indicator can be added to the SN modification request message so that S-SN 440 understands that the CPAC replacement process is for an inter-SN CPC process originating from MN. In this case, S-SN 440 should not reject the SN modification request message, and S-SN 440 should reply with an SN modification confirmation message.

[0134] According to some embodiments, if a new Xn message is used to notify the S-SN 440 of the CPAC replacement process of the CPC process initiated by the MN, then the new Xn message is a one-way message that does not require any confirmation feedback from the S-SN 440.

[0135] Return to reference Figure 4Optionally, in operation 407, MN 420 may transmit an SN MODIFICATIONREQUEST message to S-SN 440. Optionally, in operation 408, S-SN 440 may transmit an SN MODIFICATION REQUESTACKNOWLEDGE message to MN 420.

[0136] The details described in all other embodiments of this application (e.g., details regarding the CPAC replacement process) are applicable. Figure 4 Examples of implementations. Furthermore, Figure 4 The details described in the embodiments are applicable Figures 1 to 3 And all embodiments from 5 to 15.

[0137] Figure 5 An exemplary flowchart illustrating a CPAC replacement operation triggered by a target SN during a CPC process initiated by an SN, according to some embodiments of this application.

[0138] Similar to Figure 3 Operation 301 and Figure 4 Operation 401, in such Figure 5 In the embodiment shown in operation 501, MN 520 transmits an SN MODIFICATION REQUEST (Xn) message or an SGNB MODIFICATION REQUEST (X2) message to T-SN 530 to provide updated measurement results associated with PSCell.

[0139] Similar to Figure 3 Operations 302 and 303 and Figure 4 Operations 402 and 403, in such Figure 5 In the operations 502 and 503 shown in the embodiments, T-SN 530 may, for example, communicate CPAC replacement related information as in Embodiment 1 to MN 520 in SN MODIFICATION REQUEST ACKNOWLEDGE (Xn) message, SGNB MODIFICATION REQUEST ACKNOWLEDGE (X2) message, SN MODIFICATION REQUIRED (Xn) message and / or SGNB MODIFICATION REQUIRED (X2) message.

[0140] exist Figure 5In some embodiments, if the CPAC replacement is for a CPC initiated by an SN, then upon receiving an SN modification request message for the CPAC replacement operation from T-SN 530, MN 520 forwards the CPAC replacement request to S-SN 540 via an SN modification request Xn message. The SN modification request message may contain CPAC-related information as in Embodiment 1. S-SN 540 can approve the CPAC replacement by replying with an SN modification request confirmation message.

[0141] Specifically, in operation 504, MN 520 may send an SN MODIFICATION REQUEST message to S-SN 540. In operation 505, S-SN 540 may send an SN MODIFICATION REQUEST ACKNOWLEDGE message to MN 520.

[0142] Similar to Figure 3 Operations 304 and 305 and Figure 4 Operations 404 and 405, in such Figure 5 In the embodiments shown in operations 506 and 507, RRC reconfiguration messages and RRC reconfiguration completion messages can be transmitted between MN 520 and UE 510.

[0143] The details described in all other embodiments of this application (e.g., details regarding the CPAC replacement process) are applicable. Figure 5 Examples of implementations. Furthermore, Figure 5 The details described in the embodiments are applicable Figures 1 to 4 And all embodiments from 6 to 15.

[0144] Figure 6 Further flowchart illustrating a CPAC replacement operation triggered by a target SN during a CPA process based on a PSCell cancellation message, according to some embodiments of this application.

[0145] like Figure 6 As shown in the embodiments, the T-SN 630 triggers the CPAC replacement process by sending a PSCell cancellation message to the MN 620 via the Xn or X2 interface. The PSCell cancellation message between the MN and the target SN may be referred to as a cancel PSCell message, a T-SN CPAC cancellation message, a CPAC cancellation message, a cancel CPAC message, etc.

[0146] Specifically, in operation 601, T-SN 630 transmits a PSCell cancellation message to MN 620 to convey CPAC replacement information. The PSCell cancellation message does not request feedback or confirmation messages from MN 620. In an embodiment (hereinafter referred to as "Embodiment 2"), the PSCell cancellation message may contain any or a combination of the following CPAC replacement information:

[0147] - List of PSCells to be cancelled.

[0148] - Reason. The reason may be related to the PSCell cancellation reason, indicating the reason related to the PSCell cancellation operation. For example, the reason may be "Change of CPA resource", "Requirement of CPA replacement process", "Change of CPC resource between SNs" and / or "Requirement of CPC replacement process between SNs".

[0149] Similar to Figures 3 to 5 In the embodiments, in such Figure 6 In the embodiments shown in operations 602 and 603, RRC reconfiguration messages and RRC reconfiguration completion messages can be transmitted between MN620 and UE610.

[0150] The details described in all other embodiments of this application (e.g., details regarding the CPAC replacement process) are applicable. Figure 6 Examples of implementations. Furthermore, Figure 6 The details described in the embodiments are applicable Figures 1 to 5 And all embodiments from 7 to 15.

[0151] Figure 7 This document provides an exemplary flowchart illustrating a CPAC replacement operation triggered by a target SN during a CPC process initiated by an MN based on a PSCell cancellation message, according to some embodiments of this application.

[0152] Similar to Figure 6 In the embodiments, in such Figure 7 In the embodiment shown in operation 701, T-SN 730 transmits a PSCell cancellation message (e.g., a T-SN CPAC cancellation message) to MN 720 to convey CPAC replacement information as in Embodiment 2. Similar to... Figures 3 to 6 In the embodiments, in such Figure 7 In the embodiments shown in operations 702 and 703, RRC reconfiguration messages and RRC reconfiguration completion messages can be transmitted between MN 720 and UE 710.

[0153] In some embodiments, in the case of a CPC procedure initiated by MN, after receiving a T-SN CPAC cancellation message from T-SN 730, MN 720 can notify S-SN 740 of the CPAC cancellation operation by sending a CPC cancellation message to S-SN 740 via the Xn or X2 interface. Specifically, optionally, in operation 704, MN 720 transmits an additional PSCell cancellation message to S-SN 740. This additional PSCell cancellation message between MN and the source SN may be referred to as an MN CPC cancellation message, an MN CPC PSCell cancellation message, a CPC cancellation message, a cancel CPC message, etc.

[0154] In this embodiment, the MN CPC cancellation message sent from MN 720 to S-SN 740 via the Xn or X2 interface is a one-way message that does not request feedback or acknowledgment from S-SN 740. The MN CPC cancellation message may contain any one or a combination of the following information:

[0155] - List of PSCells to be cancelled.

[0156] - Reason. The reason may be related to the PSCell cancellation reason, indicating the cause associated with the PSCell cancellation operation. For example, the reason could be "CPC resource change between SNs" and / or "CPC replacement between SNs is required".

[0157] The details described in all other embodiments of this application (e.g., details regarding the CPAC replacement process) are applicable. Figure 7 Examples of implementations. Furthermore, Figure 7 The details described in the embodiments are applicable Figures 1 to 6 And all embodiments from 8 to 15.

[0158] Figure 8 This document provides an exemplary flowchart illustrating a CPAC replacement operation triggered by a target SN during a CPC process initiated by a SN based on a PSCell cancellation message, according to some embodiments of this application.

[0159] Similar to Figure 6 and 7 In the embodiments, in such Figure 8 In the embodiment shown in operation 801, T-SN 830 transmits a PSCell cancellation message (e.g., T-SN CPAC cancellation message) to MN820 to convey CPAC replacement information as in embodiment 2.

[0160] In some embodiments, in the case of a CPC process initiated by the SN, after receiving a T-SN CPAC cancellation message from T-SN 830, MN 820 should notify S-SN 840 of the CPAC cancellation operation by sending an MN CPC cancellation message to S-SN 840 via the Xn or X2 interface. Specifically, in operation 802, MN 820 transmits an additional PSCell cancellation message to S-SN 840. This additional PSCell cancellation message between MN and the source SN may be referred to as an MN CPC cancellation message, an MN CPC PSCell cancellation message, a CPC cancellation message, a cancel CPC message, etc. In embodiments, the MN CPC cancellation message sent from MN 820 to S-SN 840 is a one-way message that does not request feedback or acknowledgment from S-SN 840. The MN CPC cancellation message may contain any or a combination of the following information: a list of PSCells to be cancelled; and a PSCell cancellation reason, indicating the reason related to the PSCell cancellation operation. For example, the reason could be "change in CPC resources between SNs" and / or "need to replace CPC between SNs".

[0161] After transmitting the MN CPC cancellation message from MN 820 to S-SN 840 in operation 802, in such Figure 8 In the embodiments shown in operations 803 and 804, RRC reconfiguration messages and RRC reconfiguration completion messages can be transmitted between MN 820 and UE 810, which is similar to Figures 3 to 7 Examples of implementations.

[0162] The details described in all other embodiments of this application (e.g., details regarding the CPAC replacement process) are applicable. Figure 8 Examples of implementations. Furthermore, Figure 8 The details described in the embodiments are applicable Figures 1 to 7 And all embodiments from 9 to 15.

[0163] Some embodiments of this application provide an MN-triggered CPAC replacement procedure. Specifically in... Figures 9 to 12 Specific examples are described below. These embodiments provide a CPAC replacement process triggered by the MN by sending an SN MODIFICATION REQUEST (Xn) message, an SGNB MODIFICATION REQUEST (X2) message, or an MN CPAC cancellation message (Xn or X2) to the target SN. In this embodiment (hereafter referred to as "Embodiment 3"), the SN MODIFICATION REQUEST (Xn) message or the SGNB MODIFICATION REQUEST (X2) message may contain any one or a combination of the following CPAC replacement related information:

[0164] - Indicators for the CPAC replacement process. Indicators may be called CPAC replacement indicators, etc. For example, an indicator indicates an operation to replace the existing configuration of a PSCell.

[0165] - Changes to configuration information related to the MN's PCell (e.g., loading in the MN RRC container).

[0166] - Changes to configuration information related to the PSCell of the source SN (e.g., loading in the MN RRC container).

[0167] - The maximum number of PSCells allowed to be prepared by the target SN.

[0168] - List of PSCells to add.

[0169] - The list of PSCells to be modified.

[0170] - List of PSCells to be cancelled.

[0171] - A security key to be used by the target SN.

[0172] - Measurement result reports related to the CPAC procedure. In this example, the measurement results in the measurement results report are beam level measurements. For instance, the MN notifies the target SN of a "CPAC replacement procedure" based on the measurement results. The target SN then prepares the corresponding new CPAC procedure. Beam level measurements should be included. The target SN can configure appropriate RACH resources associated with the appropriate downlink (DL) beam.

[0173] Figure 9 This document illustrates an exemplary flowchart of a CPAC replacement operation triggered by an MN during a CPA process based on a SN modification request message, according to some embodiments of this application.

[0174] like Figure 9 As shown in the embodiments, in operation 901, MN 920 communicates CPAC replacement related information as in Embodiment 3 to T-SN 930, for example, in an SNMODIFICATION REQUEST message via the Xn interface and / or an SGNB MODIFICATION REQUEST message via the X2 interface.

[0175] According to some embodiments, MN 920 can send Xn or X2 messages in operation 901 via methods such as... Figures 6 to 8This is caused by receiving a T-SN CPAC cancellation message from T-SN 930 and requesting a CPAC replacement procedure, as described in any of the embodiments. In this case, an explicit CPAC replacement indicator is required in the SN MODIFICATION REQUEST (Xn) message and / or the SGNB MODIFICATION REQUEST (X2) message.

[0176] After receiving an Xn or X2 message from MN 920 in operation 901, in operation 902, T-SN 930 may respond with an SN MODIFICATION REQUEST ACKNOWLEDGE message via the Xn interface and / or an SCGMODIFICATOIN REQUEST ACKNOWLEDGE message via the X2 interface. According to some embodiments, the message transmitted in operation 902 may contain any or a combination of the following CPAC replacement related information:

[0177] - A list of PSCells for admissions (e.g., by T-SN 930). Each admission's PSCell in the list is associated with an RRC container containing the corresponding RRC configuration.

[0178] - The maximum number of PSCells that can be prepared by T-SN 930.

[0179] Similar to Figures 3 to 8 In the embodiments, in such Figure 9 In the embodiments shown in operations 903 and 904, RRC reconfiguration messages and RRC reconfiguration completion messages can be transmitted between MN920 and UE910.

[0180] The details described in all other embodiments of this application (e.g., details regarding the CPAC replacement process) are applicable. Figure 9 Examples of implementations. Furthermore, Figure 9 The details described in the embodiments are applicable Figures 1 to 8 And all embodiments from 10 to 15.

[0181] Figure 10 Further flowchart illustrating the CPAC replacement operation triggered by MN in a CPA process based on a PSCell cancellation message, according to some embodiments of this application.

[0182] like Figure 10As shown in the embodiments, in operation 1001, MN 1020 initiates a CPAC replacement process by sending a PSCell cancellation message (e.g., an MN CPAC cancellation message) to T-SN 1030 via the Xn or X2 interface. The MN CPAC cancellation message does not request any feedback or acknowledgment from T-SN 1030. For example, the MN CPAC cancellation message may contain: a list of PSCells to be cancelled; and / or a reason. The reason may be related to the PSCell cancellation cause, indicating the reason associated with the PSCell cancellation operation. For example, the reason could be a change in MN resources.

[0183] Similar to Figures 3 to 9 In the embodiments, in such Figure 10 In the embodiments shown in operations 1002 and 1003, RRC reconfiguration messages and RRC reconfiguration completion messages can be transmitted between MN 1020 and UE 1010.

[0184] The details described in all other embodiments of this application (e.g., details regarding the CPAC replacement process) are applicable. Figure 10 Examples of implementations. Furthermore, Figure 10 The details described in the embodiments are applicable Figures 1 to 9 And all embodiments from 11 to 15.

[0185] Figure 11 This document provides an exemplary flowchart illustrating a CPCA replacement operation triggered by an MN in a CPC process initiated by an MN based on a modification request message, according to some embodiments of this application.

[0186] Similar to Figure 9 Operation 901, in such Figure 11 In the operation 1101 shown in the embodiment, MN 1220 transmits CPAC replacement related information, as in Embodiment 3, to T-SN 1130, for example, in an SN MODIFICATION REQUEST (Xn) message and / or an SGNB MODIFICATION REQUEST (X2) message.

[0187] Similar to Figure 9 Operation 902, in such Figure 11 In the embodiment shown in operation 1102, after receiving a message from MN 1120 in operation 1101, T-SN 1130 may respond to SN MODIFICATION REQUEST ACKNOWLEDGE (Xn) message and / or SCG MODIFICATOIN REQUEST ACKNOWLEDGE (X2) message.

[0188] Similar to Figure 9 Operations 903 and 904, in such Figure 11 In the embodiments shown in operations 1103 and 1104, RRC reconfiguration messages and RRC reconfiguration completion messages can be transmitted between MN 1120 and UE 1110.

[0189] According to some embodiments, after receiving an SN MODIFICATION REQUEST ACKNOWLEDGE (Xn) message or an SCG MODIFICATOIN REQUEST ACKNOWLEDGE (X2) message from T-SN 1130, MN 1120 may optionally notify S-SN 1140 of the CPAC replacement process by sending an Xn message containing CPAC replacement information as in Embodiment 1. The Xn message may be an existing SN MODIFICATION REQUEST message or a new Xn message.

[0190] In an embodiment, if an existing SN MODIFICATION REQUEST message is used to notify S-SN 1140 of the CPAC replacement process, an additional indicator can be added to the SN MODIFATION REQUEST message so that S-SN 1140 understands the CPAC replacement process as a CPC process initiated by MN 1120. In such an embodiment, S-SN 1140 should not reject the SN MODIFICATION REQUEST message, meaning S-SN 1140 should respond with an SN MODIFATION REQUESTACKNOWLEDGE message.

[0191] Specifically, return to reference Figure 11 Optionally, in operation 1105, MN 1120 may send an SNMODIFICATION REQUEST message to S-SN 1140. Optionally, in operation 1106, S-SN 1140 may send an SNMODIFICATION REQUEST ACKNOWLEDGE message to MN 1120.

[0192] In another embodiment, if the new Xn message is used to notify S-SN 1140 of the CPAC replacement process of the CPC process initiated by MN 1120, then the Xn message is a one-way message that does not require any feedback or acknowledgment from S-SN 1140.

[0193] The details described in all other embodiments of this application (e.g., details regarding the CPAC replacement process) are applicable. Figure 11 Examples of implementations. Furthermore, Figure 11The details described in the embodiments are applicable Figures 1 to 10 And all embodiments from 12 to 15.

[0194] Figure 12 Further flowchart illustrating the MN-triggered CPAC replacement operation in a CPC process initiated by an MN based on a PSCell cancellation message, according to some embodiments of this application.

[0195] Similar to Figure 10 Operation 1001, in such Figure 12 In the embodiment shown in operation 1201, MN 1220 sends a PSCell cancellation message (e.g., an MN CPAC cancellation message) to T-SN 1230. The MN CPAC cancellation message does not request any feedback or acknowledgment from T-SN 1230. The MN CPAC cancellation message may contain: a list of PSCells to be cancelled and / or a reason for PSCell cancellation. For example, the reason for PSCell cancellation may be a change in the resources of MN 1220.

[0196] Similar to Figure 10 In the embodiments, in such Figure 12 In the embodiments shown in operations 1202 and 1203, RRC reconfiguration messages and RRC reconfiguration completion messages can be transmitted between MN1220 and UE1210.

[0197] Optionally, according to some embodiments, in operation 1204, after MN 1220 notifies T-SN 1230 of the CPAC cancellation operation, MN 1220 may also notify S-SN 1240 by sending an MN CPC cancellation message to S-SN 1240 via the Xn or X2 interface. The MN CPC cancellation message may contain: a list of PSCells to be cancelled; and / or a reason for PSCell cancellation. The reason may be a change in the resources of MN 1220.

[0198] The details described in all other embodiments of this application (e.g., details regarding the CPAC replacement process) are applicable. Figure 12 Examples of implementations. Furthermore, Figure 12 The details described in the embodiments are applicable Figures 1 to 11 And all embodiments from 13 to 15.

[0199] Some embodiments of this application provide a CPAC replacement procedure triggered by a source SN. Specifically in... Figure 13 and 14Specific examples are described below. These embodiments provide a CPAC replacement process triggered by the source SN by sending an SN MODIFICATION REQUIRED (Xn) message, an SGNB MODIFICATION REQUIRED (X2) message, an SN CHANGE REQUIRED (Xn) message, an SGNB CHANGEREQUIRED (X2) message, and / or an S-SN cancellation message to the MN.

[0200] Figure 13 This document provides an exemplary flowchart illustrating a CPAC replacement operation triggered by the source SN during a CPC process initiated by an SN based on a SN modification request message, according to some embodiments of this application.

[0201] like Figure 13 As shown in the embodiment, in operation 1301, S-SN 1340 transmits an SN change request message to MN 1320. In operation 1302, MN 1320 transmits an SN add request message to T-SN 1330. In operation 1303, T-SN 1330 transmits an SN add request confirmation message to MN 1320. In operation 1304, MN 1320 transmits an RRC reconfiguration message to UE 1310. Then, in operation 1305, UE 1310 transmits an RRC reconfiguration complete message to MN 1320.

[0202] In some embodiments of this application, during a CPAC replacement process triggered by the source SN, the target SN can notify the source SN of the prepared PSCell list via an SN change confirmation message sent from the MN. The SN change confirmation message may contain the prepared PSCell list. The prepared PSCell list may be an information element of an Xn or X2 message, or it may be contained in an RRC container (e.g., within an SN RRC reconfiguration complete message). When the PSCell list is provided as an information element of an Xn or X2 message, each PSCell may be associated with its associated RRC configuration information (i.e., the RRC container).

[0203] refer to Figure 3 In operation 1306, MN 1320 may send an SN change confirmation message to S-SN 1340 to notify the PSCell list prepared by T-SN 1330.

[0204] In operation 1307, S-SN 1340 may transmit an SN MODIFICATION REQUIRED (Xn) message, an SGNB MODIFICATION REQUIRED (X2) message, an SN CHANGE REQUIRED (Xn) message, and / or an SGNBCHANGE REQUIRED (X2) message to MN 1320. In some embodiments, the messages transmitted in operation 1307 contain any or a combination of the following CPAC replacement related information:

[0205] (1) The indicator for the CPAC replacement process, i.e., the CPAC replacement indicator.

[0206] (2) Changes to configuration information related to the PSCell of S-SN 1340 (e.g., loading in the MN RRC container).

[0207] (3) The maximum number of PSCells allowed to be prepared by T-SN 1330.

[0208] (4) List of PSCells to be added.

[0209] (5) List of PSCells to be modified.

[0210] (6) List of PSCells to be cancelled.

[0211] According to some embodiments, S-SN 1340 can send messages in operation 1307 via, for example... Figures 3 to 5 This is caused by receiving an MN CPC replacement message from MN 1320 and requesting a CPC replacement procedure, as described in any of the embodiments. In this case, an explicit CPC replacement indicator may be required.

[0212] In operation 1308, upon receiving an Xn or X2 message from S-SN 1340, MN 1320 notifies T-SN 1330 of the CPC procedure triggered by S-SN 1340 using an SNMODIFICATION REQUEST (Xn) message and / or an SGNB MODIFICATION REQUEST (X2) message. The message sent from MN 1320 to T-SN 1330 contains any or a combination of the following CPAC replacement information:

[0213] (1) The indicator for CPAC substitution, i.e., the CPAC substitution indicator.

[0214] (2) Changes to configuration information related to the PCell of MN 1320 (e.g., loading in the MN RRC container).

[0215] (3) Changes to configuration information related to the PSCell of S-SN 1340 (e.g., loading in the MN RRC container).

[0216] (4) The maximum number of PSCells allowed to be prepared by T-SN 1330.

[0217] (5) List of PSCells to be added.

[0218] (6) List of PSCells to be modified.

[0219] (7) List of PSCells to be cancelled.

[0220] (8) The security key to be used by T-SN 1330.

[0221] (9) Measurement result reporting related to the CPAC procedure. In this example, the measurement results in the measurement result report are beam level measurements. For example, the MN 1320 notifies the T-SN 1330 of the "CPAC replacement procedure" based on the measurement results. The T-SN 1330 then prepares the corresponding new CPAC procedure. Beam level measurements should be included. The T-SN 1330 can be configured with appropriate RACH resources associated with the appropriate downlink (DL) beam.

[0222] In operation 1309, after receiving a message from MN 1320 in operation 1308, T-SN 1330 may respond with an SNMODIFICATION REQUEST ACKNOWLEDGE (Xn) message and / or an SCG MODIFICATOIN REQUEST ACKNOWLEDGE (X2) message. The message transmitted in operation 1309 may contain any or a combination of the following CPAC replacement related information:

[0223] (1) A list of admitted PSCells, and each admitted PSCell is associated with an RRC container containing the corresponding RRC configuration.

[0224] (2) The maximum number of PSCells that can be prepared by T-SN 1330.

[0225] Similar to Figure 12 In the embodiments, in such Figure 13 In the embodiments shown in operations 1310 and 1311, RRC reconfiguration messages and RRC reconfiguration completion messages can be communicated between MN1320 and UE 1310.

[0226] According to some embodiments, upon receiving an Xn message (e.g., an SN modification request confirmation) from T-SN 1330, MN 1320 knows that the CPC replacement process triggered by S-SN 1340 has been successful. MN 1320 can then notify S-SN 1340 of the updated list of prepared PSCells by sending a message containing CPC replacement information as in Embodiment 1. For example, in operation 1309, MN 1320 sends an SN CHANGE CONFIRM (Xn) message, an SGNB CHANGE CONFIRM (X2) message, an SN MODIFICATION CONFIRM (Xn) message, and / or an SGNB CHANGE CONFIRM (X2) message to S-SN 1340 to convey CPC replacement information as in Embodiment 1.

[0227] The details described in all other embodiments of this application (e.g., details regarding the CPAC replacement process) are applicable. Figure 13 Examples of implementations. Furthermore, Figure 13 The details described in the embodiments are applicable Figures 1 to 12 All embodiments of 14 and 15.

[0228] Figure 14 Further exemplary flowcharts illustrating a CPAC replacement operation triggered by the source SN in a CPC process initiated based on a PSCell cancellation message, according to some embodiments of this application.

[0229] like Figure 14 As shown in the embodiments, operations 1401 to 1406 performed by UE 1410, MN 1420, S-SN 1440, and T-SN 1430 are similar to... Figure 13 The operations 1301 to 1306 performed by UE 1310, MN 1320, S-SN 1340 and T-SN 1330 as shown in the embodiments are the same.

[0230] According to some embodiments, S-SN 1440 can trigger the CPAC replacement process by sending a PSCell cancellation message to T-SN 1430 via the Xn or X2 interface. In operation 1407, S-SN 1440 sends a PSCell cancellation message (e.g., an S-SN CPC cancellation message) to MN 1420. The S-SN CPC cancellation message does not request any feedback or acknowledgment from MN 1420. The S-SN CPC cancellation message may contain any or a combination of the following CPAC replacement-related information: a list of PSCells to be cancelled; and / or a reason, which may be related to the PSCell cancellation cause. The reason may be a change in the resources of S-SN 1440.

[0231] According to some embodiments, after MN 1420 receives an S-SN CPC cancellation message from S-SN 1440, MN 1420 can notify T-SN 1430 of the CPAC cancellation operation by sending an additional PSCell cancellation message to T-SN 1430 via the Xn or X2 interface. In operation 1408, MN 1420 transmits an additional PSCell cancellation message (e.g., an MN CPAC cancellation message) to T-SN 1430. The MN CPC cancellation message may contain: a list of PSCells to be cancelled; and / or a reason, which may be related to the PSCell cancellation cause. The reason may be a change in the resources of S-SN 1440.

[0232] In such Figure 14 In operation 1409 shown in the embodiment, MN 1420 may further transmit an RRC reconfiguration message to UE 1410. Then, in operation 1410, UE 1410 may transmit an RRC reconfiguration complete message to MN 1420.

[0233] The details described in all other embodiments of this application (e.g., details regarding the CPAC replacement process) are applicable. Figure 14 Examples of implementations. Furthermore, Figure 14 The details described in the embodiments are applicable Figures 1 to 13 And all embodiments of 15.

[0234] Figure 15 The illustration shows exemplary block diagrams of a device according to some embodiments of this application. In some embodiments of this application, device 1500 may be a RAN node (e.g., MN, source SN, or target SN), which can at least perform... Figures 2 to 14 The method described in any of them.

[0235] like Figure 15 As shown, device 1500 may include at least one receiver 1502, at least one transmitter 1504, at least one non-transitory computer-readable medium 1506, and at least one processor 1508 coupled to at least one receiver 1502, at least one transmitter 1504 and at least one non-transitory computer-readable medium 1506.

[0236] Despite Figure 15 Elements such as at least one receiver 1502, at least one transmitter 1504, at least one non-transitory computer-readable medium 1506, and at least one processor 1508 are described in the singular form, but the plural form may be considered unless explicitly stated otherwise. In some embodiments of this application, device 1500 may further include input devices, memory, and / or other components.

[0237] In some embodiments of this application, at least one receiver 1502 and at least one transmitter 1504 are combined into a single device, such as a transceiver, for example, a wireless radio transceiver coupled to at least one processor 1508. The wireless radio transceiver may be configured to at least perform... Figures 2 to 14 The method described in any of them.

[0238] In some embodiments of this application, at least one non-transitory computer-readable medium 1506 may have computer-executable instructions stored thereon, programmed to implement, for example, as given in view of, at least one receiver 1502, at least one transmitter 1504, and at least one processor 1508. Figures 2 to 14 The operation of the method described by any of them.

[0239] Those skilled in the art will understand that the steps of the methods described in connection with the aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or a combination of both. The software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. Furthermore, in some aspects, the steps of the method can reside as one or any combination or set of code and / or instructions on a non-transitory computer-readable medium that can be incorporated into a computer program product.

[0240] While this disclosure has been described with reference to specific embodiments, it will be apparent to those skilled in the art that many alternatives, modifications, and variations may be readily apparent. For example, various components of the embodiments may be interchanged, added, or substituted in other embodiments. Furthermore, not all elements in each figure are essential for the operation of the disclosed embodiments. For instance, those skilled in the art to which the disclosed embodiments pertain will be able to make and use the teachings of this disclosure by simply employing the elements of the independent claims. Therefore, the embodiments of this disclosure as described herein are intended to be illustrative and not restrictive. Various changes may be made without departing from the spirit and scope of this disclosure.

[0241] In this document, the term "includes" or any other variation thereof is intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements may include not only said elements but also other elements not expressly listed or inherent to such process, method, article, or apparatus. Unless otherwise specified, an element beginning with "a" or similar does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element. Furthermore, the term "another" is defined as at least a second or more. The terms "having" and similar terms as used herein are defined as "includes".

Claims

1. A radio access network (RAN) node for wireless communication, wherein the RAN node is a master node (MN) in a multi-radio dual-connectivity (MR-DC) scenario, and the RAN node comprises: At least one memory; and At least one processor, coupled to the at least one memory and configured such that the RAN node: Receive configuration information related to the process of adding and changing CPACs in the PSCell of the conditional primary cell and secondary cell group; and In response to a modification of the configuration information associated with the CPAC process, the modified configuration information is communicated via the Xn interface or the X2 interface. In order to convey the modified configuration information, the at least one processor is further configured such that the RAN node transmits a first message to the target auxiliary node SN in the MR-DC scenario and transmits a PSCell cancellation message to the source SN in the MR-DC scenario, wherein the first message is at least one of an SN modification request message or an auxiliary gNB SgNB modification request message, and wherein the first message indicates the maximum number of PSCells allowed to be prepared by the target SN.

2. The RAN node according to claim 1, wherein the first message further comprises at least one of the following: An indicator that indicates an operation to replace the existing configuration of one or more PSCells; Updated configuration information related to the primary cell PCell of the MN; Updated configuration information related to the PSCell of the source SN in the MR-DC scenario; To add one or more references to PSCell; The reference of one or more PSCells to be modified; To cancel references to one or more PSCells; The security key to be used by the target SN; or Measurement reports related to the CPAC process.

3. The RAN node of claim 1, wherein, in order to convey the modified configuration information, the at least one processor is further configured such that the RAN node receives a second message from the target SN, and wherein the second message is at least one of the following: SN modification request confirmation message; SgNB modification request confirmation message; SN modification requires a message; or SgNB modification requires a message.

4. The RAN node according to claim 3, wherein the second message includes at least one of the following: The maximum number of PSCells that can be prepared by the target SN; and To add one or more references to PSCell; The reference of one or more PSCells to be modified; To cancel references to one or more PSCells; or References for one or more admitted PSCells.

5. The RAN node of claim 1, wherein, in order to convey the modified configuration information, the at least one processor is further configured such that the RAN node receives a first PSCell cancellation message from the target SN.

6. The RAN node of claim 1, wherein, in order to convey the modified configuration information, the at least one processor is further configured such that the RAN node transmits a second PSCell cancellation message to the target SN.

7. The RAN node of claim 1, wherein, in order to convey the modified configuration information, the at least one processor is further configured such that the RAN node receives a PSCell cancellation message from the source SN.

8. A method performed by a radio access network (RAN) node, the RAN node being a master node (MN) in a multi-radio dual-connectivity (MR-DC) scenario, the method comprising: Receive configuration information related to the process of adding and changing CPACs in the PSCell of the Conditional Primary Cell Auxiliary Cell Group; and In response to a modification of the configuration information associated with the CPAC process, the modified configuration information is communicated via the Xn interface or the X2 interface. The transmission of the modified configuration information includes sending a first message to the target auxiliary node SN in the MR-DC scenario and sending a PSCell cancellation message to the source SN in the MR-DC scenario, wherein the first message is at least one of an SN modification request message or an auxiliary gNB SgNB modification request message, and wherein the first message indicates the maximum number of PSCells allowed to be prepared by the target SN.

9. The method of claim 8, wherein the first message further comprises at least one of the following: An indicator that indicates an operation to replace the existing configuration of one or more PSCells; Updated configuration information related to the primary cell PCell of the MN; Updated configuration information related to the PSCell of the source SN in the MR-DC scenario; To add one or more references to PSCell; The reference of one or more PSCells to be modified; To cancel references to one or more PSCells; The security key to be used by the target SN; or Measurement reports related to the CPAC process.

10. The method of claim 8, wherein conveying the modified configuration information further comprises receiving a second message from the target SN, and wherein the second message is at least one of the following: SN modification request confirmation message; SgNB modification request confirmation message; SN modification requires a message; or SgNB modification requires a message.

11. The method of claim 10, wherein the second message comprises at least one of the following: The maximum number of PSCells that can be prepared by the target SN; and To add one or more references to PSCell; The reference of one or more PSCells to be modified; To cancel references to one or more PSCells; or References for one or more admitted PSCells.

12. The method of claim 8, wherein conveying the modified configuration information further comprises receiving a first PSCell cancellation message from the target SN.

13. The method of claim 8, wherein conveying the modified configuration information further comprises transmitting a second PSCell cancellation message to the target SN.

14. The method of claim 8, wherein conveying the modified configuration information further comprises receiving a PSCell cancellation message from the source SN.

Images