Enhancement method and apparatus for CPAC procedures - Patents.com

Abstract

The present application relates to an enhanced method and apparatus for a conditional secondary cell group primary cell (PSCell) addition and modification (CPAC) procedure. According to one embodiment of the present application, a user equipment (UE) includes a transceiver and a processor coupled to the transceiver, the processor configured to determine whether an operation status of a conditional primary secondary cell group cell (PSCell) modification (CPC) procedure of the user equipment (UE) is to change, and in response to determining that the operation status of the CPC procedure is to change, transmit a message to a secondary node (SN) via the transceiver, the message including an indication to indicate the change in the operation status of the CPC procedure.

Description

[Technical field]

[0001] TECHNICAL FIELD Embodiments of the present application generally relate to an enhanced method and apparatus for conditional primary cell of a secondary cell group (PSCell) addition and change (CPAC) procedure. [Background technology]

[0002] Next Generation Radio Access Networks (NG-RANs) support multi-radio dual connectivity (MR-DC) operation. In an MR-DC scenario, a user equipment (UE) with multiple transceivers may be configured to utilize resources provided by two different nodes connected through a non-ideal backhaul. One node may provide New Radio (NR) access and the other node may provide either Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) (E-UTRA) or NR access. One node may act as a master node (MN) and the other node may act as a secondary node (SN). The MN and SN are connected via a network interface (e.g., the Xn interface specified in the 3rd Generation Partnership Project (3GPP®) standard documents) to connect at least the MN to the core network.

[0003] Currently, a conditional PSCell addition (CPA) procedure and a conditional PSCell change (CPC) procedure are supported. 3GPP standard document TS38.331 introduces several measurement reporting events associated with a UE and their entering and exiting conditions, for example, Event A1, Event A2, Event A3, Event A4, Event A5, Event A6, Event B1, CondEvent A3, CondEvent A5, and Event B2, respectively.

[0004] According to the agreement of 3GPP standard documents, a conditional PSCell addition and modification (CPAC) procedure is defined as a PSCell addition or modification performed by a UE when an execution condition is met. When the UE receives CPAC configuration information, it starts evaluating the execution condition, and when the PSCell addition and / or modification procedure is triggered, it stops evaluating the execution condition.

[0005] In addition, a CPAC-based PSCell or SCG switching procedure will be supported. The CPAC-based PSCell or SCG switching procedure may also be referred to as a "CPAC-based PSCell / SCG switching procedure", a "CPAC-based fast PSCell switching procedure", a "CPAC-based fast SCG switching procedure", or an "extended CPAC procedure". Currently, details regarding the extension for the CPAC procedure in an MR-DC scenario in a 3GPP LTE system or a 5G system have not yet been considered. Summary of the Invention [Means for solving the problem]

[0006] Some embodiments of the present application provide a master node (MN), including a transceiver and a processor coupled to the transceiver, where the processor is configured to determine whether an operation status of a conditional primary secondary cell group cell (PSCell) change (CPC) procedure of a user equipment (UE) is to change, and in response to determining that the operation status of the CPC procedure is to change, transmit a first message via the transceiver to a first secondary node (SN), where the first message includes a first indication to indicate the change in the operation status of the CPC procedure.

[0007] In some embodiments, configurations related to a CPC procedure are not released by the UE upon switching to a PSCell by the UE during a CPC procedure.

[0008] In some embodiments, the change in the operational status of the CPC procedure includes at least one of starting a CPC procedure, starting a CPC procedure, stopping a CPC procedure, pausing a CPC procedure, restarting a CPC procedure, or a successful PSCell change during a CPC procedure.

[0009] In some embodiments, when the UE receives a configuration related to a CPC procedure, the UE is connected to a first SN, and a processor of the MN is configured to transmit, via the transceiver, a second message including the first indication to a second SN associated with a candidate PSCell of the UE.

[0010] In some embodiments, the first message is a SN modification request message and the second message is a SN addition request message.

[0011] In some embodiments, the first SN is associated with a candidate PSCell of the UE during the CPC procedure, and a processor of the MN is configured to receive, via the transceiver, a third message including the first indication from the SN to which the UE is connected when it receives a configuration related to the CPC procedure.

[0012] In some embodiments, the first message is a SN addition request message and the third message is a SN change required message.

[0013] In some embodiments, a third message is received prior to sending the first message, and the processor of the MN is configured to determine, based on the third message, that an operational status of the CPC procedure is to change.

[0014] In some embodiments, a processor of the MN is configured to receive, via the transceiver, from the UE, a first reconfiguration complete message associated with a CPC procedure.

[0015] In some embodiments, a processor of the MN is configured to receive, via the transceiver, from the UE, a second reconfiguration complete message associated with the CPC procedure.

[0016] In some embodiments, the first reconfiguration complete message and the second reconfiguration complete message relate to a same radio resource control (RRC) reconfiguration procedure identified by an RRC transaction identifier.

[0017] In some embodiments, the first reconfiguration procedure is not terminated by the UE upon transmission of at least one of the first reconfiguration complete message or the second reconfiguration complete message.

[0018] In some embodiments, a processor of the MN is configured to transmit, via the transceiver, at least one of the first reconfiguration complete message or the second reconfiguration complete message to a third SN associated with the target PSCell of the UE.

[0019] In some embodiments, at least one of the first reconfiguration complete message or the second reconfiguration complete message is encapsulated within an RRC message.

[0020] In some embodiments, the second reconfiguration procedure is not terminated by the third SN upon receipt of at least one of the first reconfiguration complete message or the second reconfiguration complete message.

[0021] In some embodiments, the first SN and the third SN are the same or different.

[0022] In some embodiments, a processor of the MN is configured to receive, via the transceiver, from the UE, one or more reconfiguration complete messages associated with a CPC procedure.

[0023] In some embodiments, one or more reconfiguration complete messages are generated by the UE upon receipt of a configuration related to a CPC procedure.

[0024] In some embodiments, one or more reconfiguration complete messages are generated by the UE upon both receipt of a configuration related to a CPC procedure and successful completion of a compliance check operation.

[0025] In some embodiments, when the processor of the MN triggers the UE to switch to a candidate PSCell during a CPC procedure, it is configured not to receive any reconfiguration complete message from the UE via the transceiver.

[0026] In some embodiments, a processor of the MN is configured, upon receipt of the one or more reconfiguration complete messages, to transmit, via the transceiver, each of the one or more reconfiguration complete messages to a fourth SN associated with the candidate PSCell of the UE.

[0027] In some embodiments, in response to the first SN connecting to the UE when receiving a configuration related to a CPC procedure, and in response to a change in the operational status of the CPC procedure including a successful PSCell change during the CPC procedure, a processor of the MN is configured to receive, via the transceiver, a fourth message from a fifth SN associated with a target PSCell of the UE, where the fourth message includes identifier (ID) information of the target PSCell, or receive, via the transceiver, an RRC message from the UE, different from the reconfiguration complete message, where the RRC message includes ID information of the target PSCell.

[0028] In some embodiments, the fourth message includes a second indication to indicate successful completion of the random access (RA) to the target PSCell.

[0029] In some embodiments, the first message includes ID information of the target PSCell.

[0030] In some embodiments, at least one of the first message or the fourth message is in a messaging procedure that requires a response from the peer node or is in a messaging procedure that does not require a response from the peer node.

[0031] In some embodiments, the first SN is associated with a target PSCell of the UE, and a processor of the MN is configured to receive, via the transceiver, a fifth message including the first indication from a sixth SN associated with a current serving PSCell of the UE or from a seventh SN to which the UE is connected when it receives a configuration related to a CPC procedure.

[0032] In some embodiments, the fifth message is at least one of a SN change required message, a SN release required message, or a SN modification required message.

[0033] In some embodiments, in response to a change in the operational status of a CPC procedure, including stopping the CPC procedure, a processor of the MN is configured to release one or more configurations of all PSCells involved in the CPC procedure, or to maintain a connection between the UE and the UE's current serving PSCell and release one or more configurations of other PSCells involved in the CPC procedure.

[0034] In some embodiments, a processor of the MN is configured to send, via the transceiver, an SN release request message to each SN within all SNs associated with all PSCells to release one or more configurations of all PSCells involved in the CPC procedure, or a processor of the MN is configured to send, via the transceiver, an SN release request message to each SN within a set of SNs associated with other PSCells to release one or more configurations of other PSCells involved in the CPC procedure.

[0035] In some embodiments, the first message sent by the MN to maintain the connection between the UE and the UE's current serving PSCell and to release one or more configurations of other PSCells related to the CPC procedure is a SN modification request message, in which the SN is associated with the UE's current serving PSCell.

[0036] In some embodiments, in response to a change in the operational status of a CPC procedure, including the suspension or resumption of the CPC procedure, the first message is a SN modification request message.

[0037] In some embodiments, in response to a change in the operational status of a CPC procedure, including suspension or resumption of the CPC procedure, a processor of the MN is configured to transmit, via the transceiver, an SN modification request message to each SN in a set of SNs associated with other PSCells, except for the UE's current serving PSCell.

[0038] Some embodiments of the present application provide a method performed by a MN, the method including the steps of determining whether an operation status of a conditional primary secondary cell group cell (PSCell) change (CPC) procedure of a user equipment (UE) is to change, and in response to determining that the operation status of the CPC procedure is to change, transmitting a first message to a secondary node (SN), the first message including a first indication to indicate the change in the operation status of the CPC procedure.

[0039] Some embodiments of the present application also provide a secondary node (SN), the SN including a transceiver and a processor coupled to the transceiver, the processor configured to communicate a first message with a master node (MN) via the transceiver, the first message including a first indication to indicate a change in an operation status of a conditional primary secondary cell group cell (PSCell) change (CPC) procedure of a user equipment (UE).

[0040] In some embodiments, configurations related to a CPC procedure are not released by the UE upon switching to a PSCell by the UE during a CPC procedure.

[0041] In some embodiments, the change in the operational status of the CPC procedure includes at least one of starting a CPC procedure, starting a CPC procedure, stopping a CPC procedure, pausing a CPC procedure, restarting a CPC procedure, or a successful PSCell change during a CPC procedure.

[0042] In some embodiments, the SN is connected to the UE, or associated with a candidate PSCell of the UE, or associated with a target PSCell of the UE, or associated with a current serving PSCell of the UE, when the UE receives a configuration related to a CPC procedure.

[0043] In some embodiments, the first message is at least one of a SN release request message, a SN add request message, a SN change required message, a SN release required message, a SN modification required message, a reconfiguration complete message, or a SN modification request message.

[0044] In some embodiments, to communicate the first message, a processor of the SN is configured to receive, via the transceiver, the first message from the MN and determine a change in an operational status of the CPC procedure based on a first indication in the first message.

[0045] In some embodiments, to communicate the first message, a processor of the SN is configured to determine whether an operational status of the CPC procedure is to change, and in response to a determination that the operational status of the CPC procedure is to change, transmit, via the transceiver, to the MN, a first message including a first indication.

[0046] In some embodiments, in response to a change in the operational status of the CPC procedure, including a stop of the CPC procedure, a processor of the SN is configured to receive, via the transceiver, an SN release request message from the MN.

[0047] In some embodiments, a processor of the SN is configured to receive, via the transceiver, from the MN, one or more reconfiguration complete messages associated with a CPC procedure.

[0048] In some embodiments, the one or more reconfiguration complete messages are encapsulated within a radio resource control (RRC) message.

[0049] In some embodiments, the one or more reconfiguration complete messages relate to the same RRC reconfiguration procedure, identified by an RRC transaction identifier.

[0050] In some embodiments, the first reconfiguration procedure is not terminated by the UE upon sending one or more reconfiguration complete messages to the MN.

[0051] In some embodiments, the processor of the SN is configured not to terminate the second reconfiguration procedure upon receipt of the one or more reconfiguration complete messages.

[0052] In some embodiments, one or more reconfiguration complete messages are generated by the UE upon receipt of a configuration related to a CPC procedure.

[0053] In some embodiments, one or more reconfiguration complete messages are generated by the UE upon both receipt of a configuration related to a CPC procedure and successful completion of a compliance check operation.

[0054] In some embodiments, the SN is associated with a target PSCell of the UE, and a processor of the SN is configured to transmit, via the transceiver, a fourth message to the MN, the fourth message including identifier (ID) information of the target PSCell.

[0055] In some embodiments, the fourth message includes a second indication to indicate successful completion of the random access (RA) to the target PSCell.

[0056] In some embodiments, at least one of the first message or the fourth message is in a messaging procedure that requires a response from the peer node or is in a messaging procedure that does not require a response from the peer node.

[0057] Some embodiments of the present application provide a method performed by a SN, the method including communicating a first message with a master node (MN), the first message including a first indication for indicating a change in an operational status of a conditional primary secondary cell group cell (PSCell) change (CPC) procedure of a user equipment (UE).

[0058] Some embodiments of the present application provide an apparatus for wireless communication, the apparatus comprising: a non-transitory computer-readable medium storing computer-executable instructions, a receiving circuit, a transmitting circuit, and a processor coupled to the non-transitory computer-readable medium, the receiving circuit, and the transmitting circuit, the computer-executable instructions causing the processor to perform the above-mentioned method executed by a network node (MN or SN).

[0059] The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will become apparent from the description and drawings, and from the claims.

[0060] To describe the manner in which the advantages and features of the present application may be obtained, the present application will be described by reference to specific embodiments thereof that are illustrated in the accompanying drawings. These drawings depict only exemplary embodiments of the present application and therefore should not be considered as limiting the scope of the present application. [Brief description of the drawings]

[0061] [Figure 1] 1 is a schematic diagram of a wireless communication system according to some embodiments of the present application. [Diagram 2] 1 is an exemplary flowchart illustrating changes in the operational status of a CPC procedure, according to some embodiments of the present application. [Diagram 3] 4 is a flowchart of an example procedure for wireless communication according to some embodiments of the present application. [Figure 4] 4 is a flowchart of an example procedure for wireless communication according to some embodiments of the present application. [Diagram 5] 4 is a flowchart of an example procedure for wireless communication according to some embodiments of the present application. [Figure 6] 4 is a flowchart of an example procedure for wireless communication according to some embodiments of the present application. [Figure 7] 4 is a flowchart of an example procedure for wireless communication according to some embodiments of the present application. [Figure 8] 4 is a flowchart of an example procedure for wireless communication according to some embodiments of the present application. [Figure 9] FIG. 1 is an example block diagram of an apparatus for a CPC procedure, according to some embodiments of the present application. [Figure 10] FIG. 13 is a further exemplary block diagram of an apparatus for a CPC procedure, according to some embodiments of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0062] The detailed description of the accompanying drawings is intended as an illustration of the preferred embodiment of the present application, and does not represent the only form in which the present application may be practiced. It is to be understood that the same or equivalent functions may be accomplished by different embodiments, which are encompassed within the spirit and scope of the present application.

[0063] Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. For ease of understanding, the embodiments are provided under specific network architectures and new service scenarios, such as 3GPP 5G, 3GPP LTE Release 8, etc. With the development of network architectures and new service scenarios, it is contemplated that all embodiments in the present application are also applicable to similar technical problems, and furthermore, the terms described in the present application may be changed, which should not affect the principles of the present application.

[0064] FIG. 1 illustrates a schematic diagram of a wireless communication system according to some embodiments of the present application.

[0065] As shown in Figure 1, the wireless communication system 100 may be a dual connectivity system 100 including at least one UE 101, at least one MN 102, and at least one SN 103. In particular, the dual connectivity system 100 in Figure 1 includes, for purposes of illustration, one illustrated UE 101, one illustrated MN 102, and one illustrated SN 103. Although a particular number of UEs 101, MNs 102, and SNs 103 are shown in Figure 1, it is contemplated that any number of UEs 101, MNs 102, and SNs 103 may be included within the wireless communication system 100.

[0066] Referring to Fig. 1, the UE 101 may be connected to the MN 102 and the SN 103 via a network interface, for example, a Uu interface specified in a 3GPP standard document. The MN 102 and the SN 103 may be connected to each other via a network interface, for example, an Xn interface specified in a 3GPP standard document. The MN 102 may be connected to a core network via a network interface (not shown in Fig. 1). The UE 101 may be configured to utilize resources provided by the MN 102 and the SN 103 to perform data transmission.

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

[0068] The MN 102 may be associated with a Master Cell Group (MCG). The MCG may refer to a group of serving cells associated with the MN 102 and may include a Primary Cell (PCell) and possibly one or more Secondary Cells (SCells) of the MCG. The PCell may provide a control plane connection to the UE 101.

[0069] The SN 103 may refer to a radio access node without a control plane connection to a core network but providing additional resources to the UE 101. In one embodiment of the present application, in an EN-DC scenario, the SN 103 may be an en-gNB. In another embodiment of the present application, in a NE-DC scenario, the SN 103 may be an ng-eNB. In yet another embodiment of the present application, in an NR-DC scenario or an NGEN-DC scenario, the SN 103 may be a gNB.

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

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

[0072] In some other embodiments of the present application, the UE 101 may include a wearable device, such as a smart watch, a fitness band, an optical head mounted display, etc. Additionally, the UE 101 may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or may be described using other terms used in the art.

[0073] More specifically, embodiments of the present application specify details regarding extensions for CPAC procedures in MR-DC scenarios. For example, some embodiments of the present application define new defined Xn / X2 messages, new indicators in existing Xn / X2 messages, or new information elements (IEs) to indicate changes in the operational status of a CPC procedure. Some embodiments of the present application consider how to indicate to an associated RAN node the initiation or start of a CPC procedure. Some further embodiments of the present application consider how to indicate to a source PSCell the execution of a PSCell change during a CPC procedure. Some other embodiments of the present application consider how to indicate to an associated RAN node the stop, suspension, or resumption of a CPC procedure. Further details regarding embodiments of the present application are provided in the following text in combination with the accompanying drawings.

[0074] 2 shows an example flowchart illustrating changes in the operational status of a CPC procedure according to some embodiments of the present application. The example procedure 200 in the embodiment of FIG. 2 may be performed by a MN, for example, the MN 102 as shown in FIG. 1. Although described with respect to a MN, it should be understood that other devices may be configured to perform a method similar to that of FIG. 2.

[0075] In an example procedure 200 as shown in Figure 2, in operation 201, the MN determines whether an operational status of a CPC procedure of a UE (e.g., UE 101 as shown in Figure 1) is to change. In operation 202, in response to determining that the operational status of the CPC procedure is to change, the MN transmits a message to an SN (e.g., SN 103 as shown in Figure 1, referred to as "1st SN" for simplicity) including an indication to indicate the change in the operational status of the CPC procedure (referred to as "1st indication" for simplicity).

[0076] In some embodiments, configurations related to the CPC procedure are not released by the UE upon switching to a PSCell by the UE during the CPC procedure. In some embodiments, the CPC procedure may be referred to as an "enhanced conditional PSCell change (eCPC) procedure," or a "consecutive conditional PSCell change (CCPC) procedure," etc. These embodiments may refer to a particular scenario in a CPAC-based PSCell / SCG switching procedure in which, after providing the UE with a conditional configuration (e.g., similar to that for CPAC) associated with a candidate PSCell, the UE may continue to perform the PSCell / SCG switching according to the conditional configuration and will not release the conditional configuration upon switching to a new PSCell during the PSCell / SCG switching procedure. For example, after providing the UE with a conditional configuration associated with a candidate PSCell during an eCPC procedure, the UE may perform a continuous or extended PSCell / SCG switching procedure according to the conditional configuration, and will not release the conditional configuration when switching to a new PSCell during the continuous or extended PSCell / SCG switching procedure. The unreleased conditional configuration may be reused by the UE in a subsequent switching operation to a PSCell in the eCPC procedure. During the eCPC procedure, the UE may switch between different PSCells according to the conditional configuration (e.g., consisting of an execution condition and / or a radio configuration for each candidate PSCell) configured by the network. When the eCPC procedure is initiated, the UE switches between the candidate PSCells according to the execution condition, and will not release the conditional configuration when switching between different PSCells.

[0077] In some embodiments, the change in the operational status of the CPC procedure includes at least one of starting a CPC procedure, starting a CPC procedure, stopping a CPC procedure, pausing a CPC procedure, restarting a CPC procedure, or a successful PSCell change during a CPC procedure.

[0078] In some embodiments, when the UE receives a configuration related to a CPC procedure, the MN connects to an SN and transmits a further message including a 1st indication to a further SN associated with the candidate PSCell of the UE. In one embodiment, the message in operation 202 is an SN modification request message and the further message is an SN addition request message. A specific example is described in the embodiment of FIG. 3 as follows.

[0079] In some other embodiments, the 1st SN is associated with the candidate PSCell of the UE during the CPC procedure, and the MN receives an additional message including a 1st indication from another SN to which the UE is connected when the UE receives a configuration related to the CPC procedure. In one embodiment, the message in operation 202 is an SN addition request message, and the additional message is an SN change required message. In one embodiment, the additional message is received by the MN before the MN sends the message in operation 202, and the MN may determine that the operation status of the CPC procedure is to change based on the additional message. A specific example is described in the embodiment of FIG. 4 as follows.

[0080] In some embodiments, the MN receives a reconfiguration complete message associated with a CPC procedure from the UE. In one embodiment, the MN may receive a further reconfiguration complete message associated with a CPC procedure from the UE. The reconfiguration complete message and the further reconfiguration complete message may relate to the same radio resource control (RRC) reconfiguration procedure identified by an RRC transaction identifier. For example, these two reconfiguration complete messages include the same RRC transaction identifier. A specific example is described in the embodiment of FIG. 5 as follows.

[0081] In some embodiments, the UE does not terminate the reconfiguration procedure (eg, an RRC reconfiguration procedure) upon transmission of the reconfiguration complete message and / or the further reconfiguration complete message.

[0082] In some embodiments, the MN sends a reconfiguration complete message and / or a further reconfiguration complete message to an SN (referred to as "2nd SN" for simplicity) associated with the UE's target PSCell. For example, the reconfiguration complete message and / or the further reconfiguration complete message may be encapsulated within an RRC message, e.g., an MN RRC message. In one embodiment, the 2nd SN does not terminate the reconfiguration procedure (e.g., RRC reconfiguration procedure) upon receipt of the reconfiguration complete message and / or the further reconfiguration complete message. For example, the 1st SN and the 2nd SN may be the same or different.

[0083] In some embodiments, the MN receives one or more reconfiguration complete messages associated with the CPC procedure from the UE. In one embodiment, such a message is generated by the UE upon receipt of a configuration related to the CPC procedure. In a further embodiment, such a message is generated by the UE upon both receipt of a configuration related to the CPC procedure and successful completion of a compliance check operation. In some other embodiments, the MN transmits each such message to an SN associated with a candidate PSCell of the UE upon receipt of such a message.

[0084] When the UE receives a configuration related to the CPC procedure, if it is connected to the 1st SN, and if the change in the operation status of the CPC procedure includes a successful PSCell change during the CPC procedure, in one embodiment, the MN may receive a message including the identifier (ID) information of the UE's target PSCell from the SN (referred to as "3rd SN" for simplicity) associated with the UE's target PSCell. For example, this message includes a further indication to indicate successful completion of the random access (RA) to the target PSCell. In another embodiment, the MN may receive an RRC message from the UE that is different from the reconfiguration complete message and includes the ID information of the target PSCell. In the above two embodiments, the message transmitted in operation 202 may include the ID information of the target PSCell.

[0085] For example, the message including the 1st indication and / or the message including the further indication sent in operation 202 may be in a "messaging procedure that requires a response from the peer node" (e.g., class 1Xn / X2 messaging procedure, as specified in 3GPP standard document TS 38.423) or may be in a "messaging procedure that does not require a response from the peer node" (e.g., class 2Xn / X2 messaging procedure, as specified in 3GPP standard document TS 38.423). A specific example is described in the embodiment of FIG. 5 as follows.

[0086] In some embodiments, when the MN triggers the UE to switch to the candidate PSCell during the CPC procedure, the MN does not receive any reconfiguration complete message from the UE. A specific example is described in the embodiment of FIG. 5 as follows.

[0087] In one embodiment, the 1st SN is associated with the target PSCell of the UE, and the MN receives another message including the 1st indication from the SN associated with the current serving PSCell of the UE or from the SN to which the UE is connected when it receives the configuration related to the CPC procedure. The aforementioned another message may be a SN change required message, a SN release required message, and / or a SN modification required message.

[0088] If the change in the operation status of the CPC procedure includes stopping the CPC procedure, in some embodiments, the MN releases one or more configurations of all PSCells involved in the CPC procedure. For example, the MN sends an SN release request message to each SN in all SNs associated with all PSCells. In some other embodiments, the MN keeps the connection between the UE and the UE's current serving PSCell and releases one or more configurations of other PSCells involved in the CPC procedure. For example, the MN sends an SN release request message to each SN in the set of SNs associated with other PSCells. In the above-mentioned embodiment, the message sent in operation 202 may be an SN modification request message. A specific example is described in the embodiments of Figures 6 and 7 as follows.

[0089] In some embodiments, if the change in the operational status of the CPC procedure includes a suspension or resumption of the CPC procedure, the message sent in operation 202 may be an SN modification request message. In some other embodiments, if the change in the operational status of the CPC procedure includes a suspension or resumption of the CPC procedure, the MN sends an SN modification request message to each SN in the set of SNs associated with other PSCells, except for the UE's current serving PSCell. A specific example is described in the embodiments of Figures 7 and 8 as follows.

[0090] Those skilled in the art should appreciate that the order of operations in the exemplary procedure 200 may be changed and some of the operations in the exemplary procedure 200 may be removed or modified without departing from the spirit and scope of the present disclosure. Details described in all other embodiments of the present application (e.g., details regarding extensions for the CPAC procedure) are applicable to the embodiment of Figure 2. Moreover, details described in the embodiment of Figure 2 are applicable to all of the embodiments of Figures 1 and 3-10.

[0091] In addition, some embodiments of the present application provide an example flowchart that may be executed by an SN (e.g., SN 103 as shown in FIG. 1) to communicate an indication to indicate a change in the operational status of a CPC procedure according to some embodiments of the present application. Although described with respect to an SN, it should be understood that other devices may be configured to perform similar methods.

[0092] Those skilled in the art should appreciate that the order of operations in this exemplary flowchart of the SN may be changed, and some of the operations in this exemplary flowchart may be removed or modified, without departing from the spirit and scope of the present disclosure. In all other embodiments of the present application, for example, the details described in the embodiment of FIG. 2 (for example, all details related to the extension for the CPAC procedure) are applicable to this exemplary flowchart. Moreover, the details described in this exemplary flowchart are applicable to all of the embodiments of FIG. 1 to FIG. 10.

[0093] In particular, in this exemplary flowchart, an SN (e.g., SN 103 as shown in FIG. 1) communicates a message with an MN (e.g., MN 102 as shown in FIG. 1). The message includes an indication (referred to as a "1st indication" for simplicity) to indicate a change in the operation status of a CPC procedure of a UE (e.g., UE 101 as shown in FIG. 1).

[0094] In some embodiments, configurations related to a CPC procedure are not released by the UE when the UE switches to a PSCell during a CPC procedure. In some embodiments, a CPC procedure may be referred to as an "eCPC procedure" or a "CCPC procedure," etc.

[0095] In some embodiments, the change in the operational status of the CPC procedure includes at least one of starting a CPC procedure, starting a CPC procedure, stopping a CPC procedure, pausing a CPC procedure, restarting a CPC procedure, or a successful PSCell change during a CPC procedure.

[0096] In some embodiments, the SN may be connected to the UE, or may be associated with a candidate PSCell of the UE, or may be associated with a target PSCell of the UE, or may be associated with a current serving PSCell of the UE when the UE receives a configuration related to a CPC procedure.

[0097] In some embodiments, the message including the 1st indication may be at least one of a SN release request message, a SN add request message, a SN change required message, a SN release required message, a SN modification required message, a reconfiguration complete message, or a SN modification request message.

[0098] In some embodiments, the SN receives a message from the MN including a 1st indication and determines a change in the operational status of the CPC procedure based on the 1st indication in the message. In some other embodiments, the SN determines whether the operational status of the CPC procedure is to change. In response to determining that the operational status of the CPC procedure is to change, the SN transmits a message including the 1st indication to the MN.

[0099] In some embodiments, in response to a change in the operational status of a CPC procedure, including stopping the CPC procedure, the SN receives an SN release request message from the MN. A specific example is described in the embodiments of Figures 6 and 7 as follows.

[0100] In some embodiments, the SN receives from the MN one or more reconfiguration complete messages associated with the CPC procedure. In one embodiment, such messages are encapsulated within an RRC message, e.g., an MN RRC message. In one embodiment, such messages relate to the same RRC reconfiguration procedure identified by an RRC transaction identifier, e.g., including the same RRC transaction identifier. A specific example is described in the embodiment of FIG. 5 as follows.

[0101] In some embodiments, the UE does not terminate the reconfiguration procedure (e.g., the RRC reconfiguration procedure) upon transmission of one or more reconfiguration complete messages to the MN. In some embodiments, the SN does not terminate the reconfiguration procedure (e.g., the RRC reconfiguration procedure) upon receipt of one or more reconfiguration complete messages.

[0102] In some embodiments, the one or more reconfiguration complete messages are generated by the UE upon receipt of a configuration related to a CPC procedure. In some other embodiments, the one or more reconfiguration complete messages are generated by the UE upon both receipt of a configuration related to a CPC procedure and successful completion of a compliance check operation.

[0103] In some embodiments, the SN is associated with the target PSCell of the UE, and the SN sends a further message to the MN including the ID information of the target PSCell. In one embodiment, the further message includes a further indication to indicate successful completion of the RA to the target PSCell.

[0104] In some embodiments, the message including the 1st indication and / or the further message including the further indication may be in a "messaging procedure that requires a response from the peer node" (e.g., class 1Xn / X2 messaging procedure) or may be in a "messaging procedure that does not require a response from the peer node" (e.g., class 2Xn / X2 messaging procedure). A specific example is described in the embodiment of FIG. 5 as follows.

[0105] 3 and 4 show flowcharts of exemplary procedures for wireless communication according to some embodiments of the present application. The exemplary procedures 300 and 400 refer to the initiation or start of a CPC procedure between a MN and an SN. In the embodiments of FIG. 3 and FIG. 4, a new indicator or IE is used to indicate the start of a CPC procedure between a MN and an SN.

[0106] 3, UE 301, MN 302, and SN 303 may function as UE 101, MN 102, and SN 103, respectively, as shown in Fig. 1. SN 304 may be another SN not shown in Fig. 1. In particular, the exemplary procedure 300 refers to an MN-triggered initiation of a CPC procedure or an MN-triggered initiation of a CPC procedure, in which the following steps are performed: (1) Step 311: The UE 301, the MN 302, and the SN 303 perform an SN addition procedure, and the UE 301 is connected to the MN 302 and the SN 303. (2) Steps 312 to 315: The MN 302 requests the SN 303 to prepare multiple candidate PSCells for the CPC procedure in at least one of the following two methods, namely, Method #1 and Method #2. a) Method #1: In step 312, MN 302 sends an SN modification request message (e.g., an SN MODIFICATION REQUEST Xn message) to an existing or connected SN, i.e., SN 303. MN 302 adds an indicator or IE in the SN modification request message that implies initiation or initiation of a CPC procedure. In step 313, SN 303 sends an SN modification request acknowledgement message (e.g., an SN MODIFICATION REQUEST ACKNOWLEDGE Xn message) to MN 302, including the configuration of the candidate PSCell. b) Method #2: In step 314, the MN 302 sends an SN addition request message (e.g., an SN ADDITION REQUEST Xn message) to a new SN, e.g., the SN 304. The MN 302 adds an indicator or IE in the SN addition request message that implies the initiation or start of a CPC procedure. In step 315, the SN 304 sends an SN addition request acknowledgement message (e.g., an SN ADDITION REQUEST ACKNOWLEDGE Xn message) to the MN 302, including the configuration of the candidate PSCell. (3) Step 316: The MN 302 sends an RRC reconfiguration message to the UE 301, including the configuration of the candidate PSCell. (4) Step 317: The UE 301 sends an RRC reconfiguration complete message to the MN 302.

[0107] 4, UE 401, MN 402, and SN 403 may function as UE 101, MN 102, and SN 103, respectively, as shown in Fig. 1. SN 404 may be another SN not shown in Fig. 1. In particular, example procedure 400 refers to an SN-triggered initiation of a CPC procedure, or an SN-triggered initiation of a CPC procedure, in which the following steps are performed: (1) Step 411: The UE 401, the MN 402, and the SN 403 perform an SN addition procedure, and the UE 401 is connected to the MN 402 and the SN 403. a) In some embodiments, the SN 403 already connected to the MN 402 may be referred to as a "source SN" or the like, i.e., the UE 401 is connected to the source SN when it receives a configuration related to a CPC procedure. (2) After step 411, the SN 403 may indicate the initiation or start of a CPC procedure. There are two possible ways according to different embodiments: a) In the case of an SN initiated inter SN CPC procedure, steps 412 to 415 are executed. 1) In step 412, the SN 403 sends an SN CHANGE REQUIRED message (e.g., an SN CHANGE REQUIRED Xn message) to the MN 402. In the SN CHANGE REQUIRED message, the SN 403 adds an indicator or IE that implies the initiation or start of a CPC procedure along with a "set of suggested candidate PSCells to be prepared." 2) In step 413, the MN 402 sends an SN addition request message (e.g., an SN ADDITION REQUEST Xn message) to a new SN associated with the candidate PSCell of the UE 401, e.g., the SN 404. In one embodiment, the SN addition request message includes an indicator or IE that implies the initiation or start of a CPC procedure. 3) In step 414, the SN 404 sends to the MN 402 a SN addition request acknowledgement message (eg, a SN ADDITION REQUEST ACKNOWLEDGE Xn message) including the configuration of the candidate PSCell. 4) In step 415, the MN 402 sends an SN change confirmation message (eg, an SN CHANGE CONFIRM Xn message) to the SN 403. b) In case of SN initiated intra SN CPC procedure, only step 412 is executed. In step 412, the SN 403 sends a modification required message (e.g., SN MODIFICATION REQUIRED Xn message) to the MN 402. In the modification required message, the SN 403 adds an "indicator or IE implying initiation or start of a CPC procedure" along with the "SN RRC configuration to be sent to the UE 401". (3) Step 416: The MN 402 sends an RRC reconfiguration message to the UE 401, including the configuration of the candidate PSCell. (4) Step 417: The UE 401 sends an RRC reconfiguration complete message to the MN 402.

[0108] 5 shows a flowchart of an exemplary procedure for wireless communication according to some embodiments of the present application. The exemplary procedure 500 refers to a successful PSCell change during a CPC procedure between an MN and an SN. In the embodiment of FIG. 5, a new indicator or IE is used to indicate a successful PSCell change during a CPC procedure between an MN and an SN.

[0109] In the legacy CPAC procedure, the UE may generate and send an SN RRC Reconfiguration Complete Uu message to the MN after the switch to the new PSCell is triggered. In the embodiment of Figure 5, when the CPC procedure is triggered, the UE notifies the network about the switch to another PSCell. Triggering the CPC procedure means that the PSCell meets the execution condition and the UE starts a random access (RA) to the PSCell.

[0110] 5, UE 501, MN 502, and SN 503 may function as UE 101, MN 102, and SN 103, respectively, as shown in Fig. 1. SN 504 may be another SN not shown in Fig. 1. In particular, the following steps are performed in the exemplary procedure 500. (1) Step 511: UE 501, MN 502, and SN 503 execute an SN addition procedure, and UE 501 is connected to MN 502 and SN 503. (2) Step 512: CPC procedures are configured in UE 501, MN 502, SN 503, and SN 504. (3) Step 513: The UE 501 selects a PSCell, for example, managed by the SN 504. (4) Step 514: The UE 501 performs an RA to the selected PSCell managed by the SN 504. a) In some embodiments of Figure 5, each time the UE 501 switches to a particular PSCell during a CPC procedure, the UE 501 generates and transmits a reconfiguration complete message (e.g., an SN RRC Reconfiguration Complete message) encapsulated within a MN RRC message carrying the same RRC transaction identifier corresponding to the configuration related to the particular PSCell (e.g., a selected PSCell managed by the SN 504). The MN 502 will forward the reconfiguration complete message to the associated SN carried in an Xn message (e.g., an RRC Transfer Xn message). 1) From the perspective of UE 501, in the case of a CPC-related RRC reconfiguration procedure, UE 501 will send multiple reconfiguration complete messages (e.g., RRC Reconfiguration Complete messages) (including the same RRC-TransactionIdentifier) ​​for the same CPC-related RRC reconfiguration procedure. UE 501 will not terminate the associated RRC reconfiguration procedure once it has sent the reconfiguration complete message. 2) From the perspective of an associated SN (e.g., SN 504), in the case of a CPC-related RRC reconfiguration procedure, the associated SN will receive multiple reconfiguration complete messages (e.g., RRC Reconfiguration Complete messages) (containing the same RRC-TransactionIdentifier) ​​for the same CPC-related RRC reconfiguration procedure. The associated SN will not terminate the associated RRC reconfiguration procedure upon receipt of the reconfiguration complete messages. b) In some other embodiments of FIG. 5, when UE 501 receives an RRC configuration related to a CPC procedure, UE 501 generates and transmits one or more Reconfiguration Complete messages for all involved SNs (e.g., SN RRC Reconfiguration Complete messages) encapsulated within a MN RRC message. MN 502 goes on to forward the one or more Reconfiguration Complete messages to all associated SNs carried in an Xn message (e.g., RRC Transfer Xn message). 1) In one embodiment, once a switch to another PSCell is triggered, UE 501 does not send any further RRC message to indicate the triggered PSCell switch. The PSCell that receives the random access request message from UE 501 will understand that UE 501 is attempting to switch to a PSCell. (5) After step 514, there may be two options according to different embodiments: option 1 and option 2. a) Option 1: When the random access to the new PSCell is successful, the associated SN (e.g., SN 504) will inform the MN 502 about the performed PSCell switch using a new defined Xn / X2 message or adding a new indicator or IE in an existing Xn / X2 message that contains information about the new PSCell, e.g., a PSCell ID. It can be either a class 1 (requiring a response from the peer node) or class 2 (not requiring a response from the peer node) Xn / X2 messaging procedure. For example, 1) In a class 2 Xn / X2 messaging procedure, step 515a is executed, in which the SN 504 sends an indicator or IE to the MN 502, implying a successful PSCell change during the CPC procedure. 2) In the class 1 Xn / X2 messaging procedure, in addition to step 515a, step 515b is further executed, in which the MN 502 sends a response to the SN 504. b) Option 2: When the random access to the new PSCell is successful, UE501 generates and sends to MN502 an RRC message (not an RRC Reconfiguration Complete message) carrying information about the new PSCell to which UE501 will switch (e.g., PSCell ID). In step 515c, UE501 sends to MN502 an RRC message (not an RRC Reconfiguration Complete message) including an indicator or IE implying a successful PSCell change during the CPC procedure along with information about the new PSCell (e.g., PSCell ID). (6) After the MN 502 is aware of the triggered or successfully executed PSCell switching (for example, according to the embodiment in step 514) and the information of the new PSCell, the MN 502 notifies at least the SN (for example, SN 503) related to the old PSCell about the trigger or successful execution of the PSCell switching using a new defined Xn / X2 message or a new indicator or a new IE in an existing Xn / X2 message carrying information about the new PSCell. It can be either a class 1 (requiring a response from the peer node) or class 2 (not requiring a response from the peer node) Xn / X2 messaging procedure. a) In the class 2 Xn / X2 messaging procedure, step 516a is executed, in which the MN 502 sends to the SN 503 an indicator or IE implying a successful PSCell change during the CPC procedure. b) In the class 1 Xn / X2 messaging procedure, in addition to step 516a, step 516b is further executed, in which the SN 503 sends a response to the MN 502.

[0111] 6-8 show flow charts of exemplary procedures for wireless communication according to some embodiments of the present application. Exemplary procedures 600, 700, and 800 refer to stopping, suspending, or resuming a CPC procedure between a MN and an SN. In the embodiments of FIG. 6-8, a new indicator or IE is used to indicate stopping, suspending, or resuming a CPC procedure between a MN and an SN.

[0112] In particular, in some embodiments of the present application, the MN may trigger the stopping of the CPC procedure using a new defined Xn / X2 message or a new indicator or new IE in an existing Xn / X2 message. In one embodiment, the MN sends a new defined Xn / X2 message to an associated SN or adds a new indicator or new IE in an existing Xn / X2 message to stop the CPC procedure in that SN. A specific embodiment is shown in FIG. 6.

[0113] 6, UE 601, MN 602, and SN 603 may function as UE 101, MN 102, and SN 103, respectively, as shown in Fig. 1. SN 604 may be another SN not shown in Fig. 1. In particular, the exemplary procedure 600 refers to an MN-triggered suspension of a CPC procedure, in which the following steps are performed: (1) Step 611: The UE 601, the MN 602, and the SN 603 perform an SN addition procedure, and the UE 601 is connected to the MN 602 and the SN 603. (2) Step 612: CPC procedures are configured in the UE 601, the MN 602, the SN 603, and the SN 604. The UE 601 is connected to a PSCell managed by the SN 604. That is, the SN 604 is an SN associated with the serving PSCell of the UE 601, that is, the current serving SN. (3) After step 612, there may be different embodiments in different cases: a) Embodiment 1: When the MN 602 desires to stop the CPC procedure, the MN 602 may release one or more configurations of all PSCells related to the CPC procedure, so that the UE 601 will connect only to the MN 602. For example, the MN 602 will generate a release request message (e.g., an SN RELEASE REQUEST Xn message) and send it to all SNs, for example, to the SN 604 in step 613 and / or to the SN 603 in step 615. 1) The order of steps 613 and 615 may be changed in different scenarios, i.e., step 613 may be performed before or after step 615, or steps 613 and 615 may be performed simultaneously. 2) Upon receiving the release request message, SN 603 and SN 604 will release all configurations related to the candidate PSCell. SN 603 may then send a release request response message (e.g., a SN RELEASE REQUEST RESPONSE Xn message) in step 616, and SN 604 may send a release request response message (e.g., a SN RELEASE REQUEST RESPONSE Xn message) in step 613A (for example) or other steps not shown in FIG. 6. The order of steps 616 and 613A may be changed in different scenarios. b) Embodiment 2: If the MN 602 knows which PSCell the UE 601 is connected to at this moment, when the MN 602 wants to stop the CPC procedure, the MN 602 may stop the CPC procedure while making the UE 601 keep the connection to the current serving PSCell managed by the SN 604. The following steps may occur. 1) In step 613, the MN 602 sends a new indicator or a new IE to indicate the stop of the CPC procedure to the SN 604 associated with the current serving PSCell of the UE 601. There may be different embodiments as follows. - In a class 2 Xn / X2 messaging procedure, step 613 is performed, in which the MN 602 sends a new defined Xn / X2 message to the SN 604 associated with the current serving PSCell of the UE 601, including a new indicator or a new IE to indicate the stop of the CPC procedure. - In class 1 Xn / X2 messaging procedure, step 613 is performed, in which the MN 602 sends a new defined Xn / X2 message, or a modification request message (e.g., an SN MODIFICATION REQUEST message), including a new indicator or a new IE to indicate the stop of the CPC procedure, to the SN 604 associated with the current serving PSCell of the UE 601. Besides step 613, step 613A is also performed, in which the SN 604 may send a response (e.g., an SN MODIFICATION REQUEST ACKNOWLEDGE Xn message) to the MN 602. 2) Upon receiving the indicator to stop the CPC procedure, the SN 604 causes the SN 604 to release configurations related to the candidate PSCells except the current serving PSCell of the UE 601. The SN 604 also generates and sends an SN RRC message in step 614 to the UE 601, so that the UE 601 also causes the UE 601 to release configurations related to the candidate PSCells except the current serving PSCell. The order of steps 613A and 614 may be changed in different scenarios, i.e. step 613A may be performed before or after step 614, or steps 613A and 614 may be performed simultaneously. 3) If there are multiple SNs involved in the CPC procedure, the MN 602 will generate a release request message (e.g., a SN RELEASE REQUEST Xn message) and send it to all other SNs (e.g., SN 603) associated with the CPC procedure, but the UE 601 is not connected at that moment. For example, - In step 615, the MN 602 sends a release request (eg, an SN RELEASE REQUEST Xn message) to the SN 603. - In step 616, after releasing all configurations related to the candidate PSCell, the SN 603 sends a release request response message (eg, a SN RELEASE REQUEST RESPONSE Xn message) to the MN 602.

[0114] In some further embodiments of the present application, the SN may trigger the stop of the CPC procedure using a new defined Xn / X2 message or a new indicator or a new IE in an existing Xn / X2 message. In one embodiment, either the source SN of the UE (which initiates the CPC procedure, i.e., when the UE receives the configuration of the CPC procedure) or the SN associated with the UE's current serving PSCell can trigger the stop of the CPC procedure by sending to the MN via a new defined Xn / X2 message or by adding a new indicator or a new IE in an existing Xn / X2 message. In one example, the source SN may send to the MN a new defined Xn / X2 message or a SN CHANGE REQUIRED message with a new indicator or IE to trigger the stop of the CPC procedure. In another example, the source SN may send to the MN a SN RELEASE REQUIRED message if the UE is connected to a PSCell under another SN at that moment, which implicitly means the stop of the CPC procedure. Two examples of these could be Xn / X2 messaging procedures, either class 1 (requiring a response from the peer node) or class 2 (requiring no response from the peer node). A particular embodiment is shown in FIG.

[0115] 7, UE 701, MN 702, and SN 703 may function as UE 101, MN 102, and SN 103, respectively, as shown in FIG 1. SN 704 may be another SN not shown in FIG 1. A particular embodiment of the exemplary procedure 700 (for simplicity, referred to as embodiment A) refers to a current serving SN triggered stop of the CPC procedure. In embodiment A, steps 711-715 are performed, and step 713A is optional. (1) Step 711: The UE 701, the MN 702, and the SN 703 execute an SN addition procedure, and the UE 701 is connected to the MN 702 and the SN 703. (2) Step 712: CPC procedures are configured in the UE 701, the MN 702, the SN 703, and the SN 704. The UE 701 is connected to a PSCell managed by the SN 704. That is, the SN 704 is an SN associated with the serving PSCell of the UE 701, that is, the current serving SN. (3) After step 712, the following different embodiments are possible: a) In the class 2 Xn / X2 messaging procedure, step 713 is executed, in which the SN 704 sends to the MN 702 a new defined Xn / X2 message including a new indicator or a new IE to indicate the stop of the CPC procedure. b) In class 1 Xn / X2 messaging procedure, step 713 is executed, in which the SN 704 sends to the MN 702 a new defined Xn / X2 message, or a change required message (e.g., an SN CHANGE REQUIRED message), or a modification required message (e.g., an SN MODIFICATION REQUIRED message), including a new indicator or a new IE to indicate the stop of the CPC procedure. Besides step 713, step 713A is further executed, in which the MN 702 sends a response (e.g., an SN CHANGE CONFIRM message or an SN MODIFICATION CONFIRM message) to the SN 704. (4) Step 714: The MN 702 sends a release request message (for example, an SN RELEASE REQUEST message) to the SN 703. The UE 701 is not connected to the PSCell under the SN 703 at that moment. (5) Step 715: After releasing all configurations related to the candidate PSCell, the SN 703 sends a release request response message (eg, a SN RELEASE REQUEST RESPONSE message) to the MN 702.

[0116] In some other embodiments of the present application, a configuration related to the CPC procedure is configured in the UE, and after the CPC procedure starts, the MN or SN may suspend the CPC procedure and resume it later. Particular embodiments are shown in Figures 7 and 8.

[0117] In some embodiments, the suspension or resumption of the CPC procedure is triggered by either the source SN (i.e., the SN to which the UE is connected when it receives the CPC configuration) or the UE's current serving SN. In an SN-triggered suspension or resumption of the CPC procedure, the SN first sends an Xn / X2 message including a new indicator to indicate the suspension or resumption of the CPC procedure. The Xn / X2 message can be either a class 1 (requiring a response from the peer node) or class 2 (not requiring a response from the peer node) Xn / X2 messaging procedure. The class 1 message can be an SN Modification Required Xn message. The MN will then inform other associated SNs about the suspension or resumption of the CPC procedure. A specific embodiment is shown in FIG. 7.

[0118] A particular embodiment of the exemplary procedure 700 refers to a "current serving SN triggered suspension of a CPC procedure" or a "current serving SN triggered resume of a CPC procedure" (for simplicity, referred to as embodiment B). In embodiment B, steps 711-714 are performed, and step 713A is optional. (1) Step 711: The UE 701, the MN 702, and the SN 703 execute an SN addition procedure, and the UE 701 is connected to the MN 702 and the SN 703. (2) Step 712: CPC procedures are configured in the UE 701, the MN 702, the SN 703, and the SN 704. The UE 701 is connected to a PSCell managed by the SN 704. That is, the SN 704 is an SN associated with the serving PSCell of the UE 701, that is, the current serving SN. (3) After step 712, the following different embodiments are possible: a) In the class 2 Xn / X2 messaging procedure, step 713 is executed, in which the SN 704 sends to the MN 702 a new defined Xn / X2 message including a new indicator or a new IE to indicate the suspension or resumption of the CPC procedure. b) In class 1 Xn / X2 messaging procedure, step 713 is executed, in which the SN 704 sends to the MN 702 a new defined Xn / X2 message, or a change required message (e.g., an SN CHANGE REQUIRED message), or a modification required message (e.g., an SN MODIFICATION REQUIRED message), including a new indicator or a new IE to indicate the suspension or resumption of the CPC procedure. Besides step 713, step 713A is further executed, in which the MN 702 sends a response (e.g., an SN CHANGE CONFIRM message or an SN MODIFICATION CONFIRM message) to the SN 704. (4) Step 714: The MN 702 sends a message including a new indicator or a new IE to indicate the suspension or resumption of the CPC procedure to the SN 703. The UE 701 is not connected to the PSCell under the SN 703 at that moment.

[0119] In some other embodiments, the suspension or resumption of the CPC procedure is triggered by the MN. The MN will send an Xn / X2 message to all SNs associated with the CPC procedure, including a new indicator or a new IE to indicate the suspension or resumption of the CPC procedure. The Xn / X2 message can be either a class 1 (requiring a response from the peer node) or class 2 (not requiring a response from the peer node) Xn / X2 messaging procedure. The class 1 message can be an SN Modification Request Xn message. A particular embodiment is shown in FIG. 8.

[0120] 8, a UE 801, a MN 802, and a SN 803 may function as the UE 101, the MN 102, and the SN 103, respectively, as shown in Fig. 1. The SN 804 may be another SN not shown in Fig. 1. In particular, the exemplary procedure 800 refers to a "MN-triggered suspension of a CPC procedure" or a "MN-triggered resumption of a CPC procedure," and the following steps are performed. (1) Step 811: The UE 801, the MN 802, and the SN 803 execute an SN addition procedure, and the UE 801 is connected to the MN 802 and the SN 803. (2) Step 812: A CPC procedure is configured in the UE 801, the MN 802, the SN 803, and the SN 804. The UE 801 is connected to a PSCell managed by the SN 804. That is, the SN 804 is an SN associated with the serving PSCell of the UE 801, that is, the current serving SN. (3) After step 812, the following different embodiments are possible: a) In the class 2 Xn / X2 messaging procedure, steps 813 and 814 are executed, in which the MN 802 sends to the SN 803 and SN 804, respectively, a new defined Xn / X2 message including a new indicator or a new IE to indicate the suspension or resumption of the CPC procedure. 1) The order of steps 813 and 814 may be changed in different scenarios, i.e., step 813 may be performed before or after step 814, or steps 813 and 814 may be performed simultaneously. b) In the class 1 Xn / X2 messaging procedure, steps 813, 813A, 814, and 814A are executed. In steps 813 and 814, the MN 802 transmits to the SN 803 and SN 804, respectively, a new defined Xn / X2 message including a new indicator or a new IE for indicating the suspension or resumption of the CPC procedure, or a modification request message (e.g., an SN MODIFICATION REQUEST Xn message). In step 813A, the SN 804 transmits a response to the MN 802. In step 814A, the SN 803 transmits a response (e.g., an SN MODIFICATION CONFIRM message) to the MN 802.

[0121] Details described in all other embodiments of the present application are applicable to the embodiments shown in any of Figures 3-8. Those skilled in the art should appreciate that the order of operations in any of the exemplary procedures 300-800 in Figures 3-8 may be changed and some of the operations in any of the exemplary procedures 300-800 in Figures 3-8 may be removed or modified without departing from the spirit and scope of the present disclosure.

[0122] For example, any of the exemplary procedures 300-800 in Figures 3-8 may also be applicable to an eCPC or CCPC procedure. In some embodiments, the exemplary procedures 300 and 400 may be applicable to initiating or starting an eCPC or CCPC procedure between an MN and an SN. In some embodiments, the exemplary procedure 500 may be applicable to a successful PSCell change during an eCPC or CCPC procedure between an MN and an SN. In some embodiments, the exemplary procedures 600, 700, and 800 may be applicable to stopping, suspending, or resuming an eCPC or CCPC procedure between an MN and an SN.

[0123] Some embodiments of the present application also provide a wireless communication device for a CPC procedure. For example, FIG. 9 shows an example block diagram of an apparatus 900 for a CPC procedure according to some embodiments of the present application.

[0124] 9, the apparatus 900 may include at least one non-transitory computer-readable medium 902, at least one receiving circuit 904, at least one transmitting circuit 906, and at least one processor 908 coupled to the non-transitory computer-readable medium 902, the receiving circuit 904, and the transmitting circuit 906. The at least one processor 908 may be a CPU, DSP, microprocessor, etc. The apparatus 900 may be a network node (e.g., MN or SN) configured to perform methods such as those presented above.

[0125] In this figure, elements such as at least one processor 908, receiving circuitry 904, and transmitting circuitry 906 are described in the singular, but the plural is contemplated unless limitation to the singular is expressly stated. In some embodiments of the present application, the receiving circuitry 904 and the transmitting circuitry 906 may be combined into a single device, such as a transceiver. In some embodiments of the present application, the apparatus 900 may further include an input device, a memory, and / or other components.

[0126] In some embodiments of the present application, the non-transitory computer-readable medium 902 may store computer-executable instructions for causing a processor to perform a method with respect to a network node (e.g., MN or SN) as described or illustrated above. For example, the computer-executable instructions, when executed, cause a processor 908 interacting with the receiving circuitry 904 and the transmitting circuitry 906 to perform steps with respect to a network node (e.g., MN or SN) as described or illustrated above.

[0127] Figure 10 shows a further exemplary block diagram of an apparatus 1000 for a CPC procedure according to some embodiments of the present application. Referring to Figure 10, the apparatus 1000, e.g., an MN or an SN, may include at least one processor 1002 and at least one transceiver 1004 coupled to the at least one processor 1002. The transceiver 1004 may include at least one separate receiving circuit 1006 and transmitting circuit 1008, or at least one integrated receiving circuit 1006 and transmitting circuit 1008. The at least one processor 1002 may be a CPU, a DSP, a microprocessor, etc.

[0128] According to some other embodiments of the present application, when the apparatus 1000 is an MN, the processor 1002 may be configured to determine whether an operational status of a CPC procedure of the UE is to change, and in response to a determination that the operational status of the CPC procedure is to change, transmit a message via the transceiver 1004 to the SN, the message including an indication to indicate the change in the operational status of the CPC procedure.

[0129] According to some embodiments of the present application, when the apparatus 1000 is an SN, the processor 1002 is configured to communicate, via the transceiver 1004, a message with the MN, the message including an indication to indicate a change in the operation status of the UE's CPC procedure.

[0130] The methods of the present disclosure may be performed on a programmed processor. However, the controllers, flowcharts, and modules may also be implemented in hardware electronic or logic circuits such as general purpose or special purpose computers, programmed microprocessors or microcontrollers and peripheral integrated circuit elements, integrated circuits, discrete element circuits, programmable logic devices, etc. In general, any device having a finite state machine capable of implementing the flowcharts shown in the figures may be used to implement the processing functions of the present disclosure.

[0131] Although the present disclosure has been described with its specific embodiments, it is apparent that numerous alternatives, modifications, and variations may be apparent to those skilled in the art. For example, various components of the embodiments may be exchanged, added, or substituted in other embodiments. Also, not all elements of each figure are necessary for the operation of the disclosed embodiments. For example, those skilled in the art will be able to make and use the teachings of the present disclosure by simply adopting the elements of the independent claims. Thus, the embodiments of the present disclosure described herein are intended to be illustrative, not limiting. Various changes may be made without departing from the spirit and scope of the present disclosure.

[0132] As used herein, the terms "includes", "including", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements does not include only those elements, but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element preceded by "a", "an", etc., does not, without more constraints, preclude the existence of additional equivalent elements in the process, method, article, or apparatus that includes that element. Also, the term "another" is defined as at least a second or more. Terms such as "having" as used herein are defined as "including". A phrase such as "A and / or B" or "at least one of A and B" may include any and all combinations of the words listed with that phrase. For example, a phrase such as "A and / or B" or "at least one of A and B" may include A, B, or both A and B. The terms "first", "second", etc. are only used to clearly describe the embodiments of the present application, and are not used to limit the contents of the present application. [Explanation of symbols]

[0133] 100 Wireless Communication System, Dual Connectivity System 101, 301, 401, 501, 601, 701, 801UE 102, 302, 402, 502, 602, 702, 802MN 103, 303, 304, 403, 404, 503, 504, 603, 604, 703, 704, 803, 804 SN 900, 1000 devices 902 Non-transitory computer-readable medium 904, 1006 Receiver circuit 906, 1008 Transmitting circuit 908, 1002 processors 1004 Transceiver

Claims

1. A transceiver; a processor coupled to the transceiver; wherein the processor: determining whether an operation status of a conditional primary secondary cell group cell (PSCell) change (CPC) procedure of a user equipment (UE) is to change; transmitting a first message via the transceiver to a first secondary node (SN) in response to determining that the operational status of the CPC procedure will change, the first message including a first indication to indicate the change in the operational status of the CPC procedure; A master node (MN) configured to perform the above.

2. The MN of claim 1, wherein a configuration related to the CPC procedure is not released by the UE upon switching to a PSCell by the UE during the CPC procedure.

3. The change in the operational status of the CPC procedure, Initiating said CPC procedure; Initiation of the CPC procedure; the suspension of said CPC procedures; the suspension of said CPC procedures; the resumption of said CPC procedure; or Successful PSCell change during the CPC procedure The MN of claim 1, comprising at least one of:

4. When the UE receives a configuration related to the CPC procedure, the UE is connected to the first SN; The MN of claim 1, wherein the processor of the MN is configured to transmit, via the transceiver, a second message including the first indication to a second SN associated with a candidate PSCell of the UE.

5. The first SN is associated with a candidate PSCell of the UE during the CPC procedure; The MN of claim 1, wherein the processor of the MN is configured to receive, via the transceiver, a third message including the first indication from an SN to which the UE is connected when the UE receives a configuration related to the CPC procedure.

6. The MN of claim 1 , wherein the processor of the MN is configured to receive, via the transceiver, from the UE, a first reconfiguration complete message associated with the CPC procedure.

7. The MN of claim 6, wherein the processor of the MN is configured to receive, via the transceiver, from the UE, a second reconfiguration complete message associated with the CPC procedure.

8. 8. The MN of claim 7, wherein the first reconfiguration complete message and the second reconfiguration complete message relate to a same radio resource control (RRC) reconfiguration procedure identified by an RRC transaction identifier.

9. The first SN is associated with a target PSCell of the UE; The MN of claim 1, wherein the processor of the MN is configured to receive, via the transceiver, a fifth message including the first indication from a sixth SN associated with a current serving PSCell of the UE or from a seventh SN to which the UE is connected when it receives a configuration related to the CPC procedure.

10. The change in the operational status of the CPC procedure, the suspension of said CPC procedures; the interruption of said CPC procedures, or Resumption of the CPC procedure The MN of claim 9, comprising at least one of:

11. In response to the change in the operational status of the CPC procedure, including a stop of the CPC procedure, the processor of the MN: Releasing one or more configurations of all PSCells involved in said CPC procedure; or maintaining a connection between the UE and a current serving PSCell of the UE and releasing one or more configurations of other PSCells involved in the CPC procedure; The MN according to claim 1 or claim 9, configured to perform the following:

12. The processor of the MN is configured to send, via the transceiver, an SN release request message to each SN in all SNs associated with all of the PSCells to release the one or more configurations of all of the PSCells related to the CPC procedure; or The MN of claim 11, wherein the processor of the MN is configured to transmit, via the transceiver, the SN release request message to each SN in a set of SNs associated with the other PSCell, in order to release the one or more configurations of the other PSCell related to the CPC procedure.

13. The MN of claim 11 or claim 12, wherein the first message sent by the MN to maintain the connection between the UE and the current serving PSCell of the UE and to release the one or more configurations of the other PSCell related to the CPC procedure is an SN modification request message, and the SN is associated with the current serving PSCell of the UE.

14. A transceiver; a processor coupled to the transceiver; a secondary node (SN) comprising: a processor configured to communicate, via the transceiver, a first message with a master node (MN), the first message including a first indication to indicate a change in an operational status of a conditional primary secondary cell group cell (PSCell) change (CPC) procedure of a user equipment (UE).

15. A method performed by a master node (MN), comprising: determining whether an operation status of a conditional primary secondary cell group cell (PSCell) change (CPC) procedure of a user equipment (UE) is to change; sending a first message to a secondary node (SN) in response to determining that the operational status of the CPC procedure is to change, the first message including a first indication to indicate the change in the operational status of the CPC procedure; The method includes:

Images