Apparatus and method for managing subsequent conditional PScell addition conditions

Abstract

Example embodiments enable management of subsequent conditional PScell additions upon release of the secondary cell group. The primary node may be configured to send to the user node at least one execution condition for adding CPA for conditional primary and secondary cells (PScells) to be applied by the user node for an assessment of adding or changing SCPAC conditions for subsequent conditional PScells performed for CPA to be performed after release of a secondary cell group (SCG), and wherein the at least one execution condition for the CPA is configured to replace the at least one execution condition configured to the user node for changing the evaluation of the SCPAC condition of the CPC for the conditional PScell. An apparatus, method and computer program are disclosed.

Description

Technical Field

[0001] This application generally relates to information technology. In particular, some example embodiments of this application relate to the management of conditions used for subsequent conditional PScell ​​addition / modification during or after the release of a secondary cell group. Background Technology

[0002] MR-DC (Multiple Radio Dual Connectivity) refers to a series of different dual connectivity configuration options that can be associated with 5G. MR-DC with selective activation of cell groups is designed to enable subsequent CPC (Conditional PScell ​​Change) and CPA (Conditional PScell ​​Addition) after an SCG (Secondary Cell Group) change, without requiring network reconfiguration and reinitialization for CPC / CPA preparation. Summary of the Invention

[0003] This summary is provided to introduce a series of concepts in a simplified form, which will be further described in the detailed embodiments below. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter.

[0004] Example embodiments may enable the management of subsequent conditional PScell ​​additions / changes in conditional configurations to update CPC conditions to CPA conditions for CPA execution upon or after SCG release, wherein CPC conditions associated with the secondary node measurement configuration may be at least partially updated, or CPC conditions may be updated to conditions associated with the primary node measurement configuration. This can be achieved through the features of the independent claims. Other implementations are provided in the dependent claims, specification, and drawings.

[0005] According to a first aspect, a master node includes at least one processor; and at least one memory including instructions that, when executed by the at least one processor, cause the master node to at least: send to a user node at least one execution condition for adding a Conditional Primary / Secondary Cell (PSC) to a Conditional Primary / Secondary Cell (PSC) cell, the at least one execution condition being applied by the user node for an evaluation of subsequent Conditional PSC cell addition or modification SCPAC conditions for the execution of a CPA to be performed after the release of the Secondary Cell Group (SCG), and wherein the at least one execution condition for the CPA is configured to replace at least one execution condition configured to be given to the user node for an evaluation of SCPAC conditions for modifying a Conditional PSC cell.

[0006] According to the implementation of the first aspect, at least one execution condition for CPA includes at least one A4 event condition mapped to the primary cell group (MCG) configuration, wherein the at least one A4 event condition is defined for the candidate SCPAC configuration.

[0007] According to the implementation of the first aspect, at least one execution condition includes a common A4 event condition configured for all candidate SCPACs.

[0008] According to the implementation of the first aspect, at least one execution condition includes an A4 event condition specific to each candidate SCPAC configuration.

[0009] According to the implementation of the first aspect, at least one execution condition includes instructions for maintaining the measurement configuration and SCPAC condition evaluation associated with the released SCG, wherein the instructions instruct the user node, after the SCG is released, to continue the SCPAC condition evaluation using the measurement configuration associated with the released SCG based on at least one of the CPC's A3 event condition or A5 event condition.

[0010] According to an implementation of the first aspect, the at least one memory includes instructions that, when executed by the at least one processor, cause the master node to: send an indication to deactivate at least one execution condition; detect a need for SCG release; and send a reconfiguration message for SCG release to the user node, the reconfiguration message including an indication to activate at least one execution condition.

[0011] According to the implementation of the first aspect, at least one execution condition is sent in the Radio Resource Control (RRC) reconfiguration message for the release of the SCG.

[0012] According to the implementation of the first aspect, at least one execution condition is sent in a Radio Resource Control (RRC) reconfiguration message, which includes at least one of an initial conditional PScell ​​change CPC condition configuration or a subsequent CPC condition configuration.

[0013] According to the implementation of the first aspect, the at least one memory further includes instructions that, when executed by the at least one processor, cause the master node to send instructions to the user node to suspend the evaluation of at least one execution condition for the released SCG.

[0014] According to the implementation of the first aspect, the instructions sent to the user node include: instructions to suspend the evaluation of at least one execution condition of the released SCG for a specific period of time starting from the release of the SCG.

[0015] According to the implementation of the first aspect, the instructions sent to the user node include: suspending the evaluation of at least one execution condition for the released SCG until the user node executes at least one conditionally added PCell instruction.

[0016] According to a second aspect, a user node includes at least one processor; and at least one memory including instructions that, when executed by the at least one processor, cause the user node to at least: receive from a master node at least one execution condition for adding a Conditional Primary / Secondary Cell (PSC) to a Conditional Primary / Secondary Cell (PSC) cell, the at least one execution condition being applied by the user node for evaluating subsequent Conditional PSC additions or changes to SCPAC conditions for the execution of a CPA to be performed after the release of the Secondary Cell Group (SCG), wherein the at least one execution condition for the CPA is configured to replace at least one execution condition configured to be given to the user node for evaluating SCPAC conditions for changing a Conditional PSC to a Conditional PSC cell.

[0017] According to the second aspect of the implementation, at least one execution condition for CPA includes at least one A4 event condition mapped to the primary cell group (MCG) configuration, wherein the at least one A4 event condition is defined for the candidate SCPAC configuration.

[0018] According to the implementation of the second aspect, at least one execution condition for CPA includes configuring a common A4 event condition for all candidate SCPACs.

[0019] According to the implementation of the second aspect, at least one execution condition for CPA includes an A4 event condition specific to each candidate SCPAC configuration.

[0020] According to the second aspect of the implementation, at least one execution condition for CPA includes instructions for maintaining the measurement configuration associated with the released SCG and SCPAC condition evaluation, wherein the instructions instruct the user node, after the SCG is released, to continue the SCPAC condition evaluation using the measurement configuration associated with the released SCG based on at least one of the CPC's A3 event condition or A5 event condition.

[0021] According to the implementation of the second aspect, at least one execution condition for CPA is received in a Radio Resource Control (RRC) reconfiguration message, which includes at least one of an initial CPC condition configuration or a subsequent CPC condition configuration.

[0022] According to the implementation of the second aspect, at least one execution condition for CPA is received in the RRC reconfiguration message for SCG release.

[0023] According to the second aspect implementation, the at least one memory further includes instructions that, when executed by the at least one processor, cause the user node to: receive from the master node instructions for suspending the evaluation of at least one execution condition for CPA against the released SCG; and suspend the evaluation of at least one execution condition for CPA against the released SCG according to the instructions.

[0024] According to the second aspect of the implementation, the instructions received from the master node include: instructions for suspending the evaluation of at least one execution condition for CPA against the released SCG for a specific period of time starting from the release of the SCG.

[0025] According to the second aspect of the implementation, the instructions received from the master node include: suspending the evaluation of at least one execution condition for CPA against the released SCG until the user node executes at least one conditionally added PCell instruction.

[0026] According to the second aspect implementation, the at least one memory includes instructions that, when executed by the at least one processor, cause the user node to: receive a reconfiguration message for SCG release from the master node; perform SCG release, including: releasing the SCG configuration, releasing a measurement configuration of at least one of the initial CPC condition or the subsequent CPC condition, and releasing at least one of the CPC condition or the subsequent CPC condition; and cause the user node to: evaluate the SCPAC condition based on at least one execution condition for CPA; and, after the SCG release, perform CPA based on the evaluation.

[0027] According to the second aspect implementation, the at least one memory includes instructions that, when executed by the at least one processor, cause the user node to: receive from the master node at least one execution condition for CPA and an instruction to deactivate at least one execution condition for CPA; store at least one execution condition in a deactivated state; and receive from the master node a reconfiguration message for SCG release and an instruction to activate at least one execution condition for CPA.

[0028] According to the second aspect implementation, the at least one memory further includes instructions that, when executed by the at least one processor, cause the user node to: receive a reconfiguration message for SCG release from the master node before the initial conditional PScell ​​change has been executed; perform SCG release, including: releasing the SCG configuration, maintaining the measurement configuration of the initial CPC condition, and maintaining the initial CPC condition; and cause the user node to: update the initial CPC condition for CPA, wherein for the candidate SCPAC configuration, the initial CPC condition is evaluated using the released PScell ​​measurement as the serving PScell ​​measurement; and, at or after the SCG release, perform an evaluation of the conditional PScell ​​addition execution based on the update.

[0029] According to the second aspect implementation, the at least one memory includes instructions that, when executed by the at least one processor, cause the user node to: receive a reconfiguration message for SCG release from the master node after the initial conditional PScell ​​change has been executed; perform SCG release, including: maintaining the SCG configuration, maintaining the measurement configuration of subsequent conditional PScell ​​change CPC conditions, and maintaining subsequent CPC conditions; and cause the user node to: update subsequent CPC conditions for CPA, wherein for candidate SCPAC configurations, the initial CPC conditions are evaluated using the released PScell ​​measurement as a serving PScell ​​measurement; and, at or after SCG release, perform an evaluation of conditional PScell ​​addition execution based on the update.

[0030] According to a third aspect, a method executed by a master node is provided. The method includes: sending to a user node at least one execution condition for adding a Conditional Primary / Secondary Cell Permitted Charge (CPA) to a Conditional Primary / Secondary Cell (PSC) cell, the at least one execution condition being applied by the user node for an evaluation of subsequent Conditional PSC cell addition or modification SCPAC conditions for the execution of a CPA to be performed after the release of the Secondary Cell Group (SCG), and wherein the at least one execution condition for the CPA is configured to replace at least one execution condition configured to be given to the user node for an evaluation of SCPAC conditions for modifying a Conditional PSC cell.

[0031] According to the implementation of the third aspect, at least one execution condition for CPA includes at least one A4 event condition mapped to the primary cell group (MCG) configuration, wherein the at least one A4 event condition is defined for the candidate SCPAC configuration.

[0032] According to the implementation of the third aspect, at least one execution condition includes a common A4 event condition configured for all candidate SCPACs.

[0033] According to the implementation of the third aspect, at least one execution condition includes an A4 event condition specific to each candidate SCPAC configuration.

[0034] According to the implementation of the third aspect, at least one execution condition includes instructions for maintaining the measurement configuration and SCPAC condition evaluation associated with the released SCG, wherein the instructions instruct the user node, after the SCG is released, to continue the SCPAC condition evaluation using the measurement configuration associated with the released SCG based on at least one of the CPC's A3 event condition or A5 event condition.

[0035] According to the third aspect of the implementation, the method includes: sending an indication to deactivate at least one execution condition; detecting a need for SCG release; and sending a reconfiguration message for SCG release to a user node, the reconfiguration message including an indication to activate at least one execution condition.

[0036] According to the implementation of the third aspect, at least one execution condition is sent in the Radio Resource Control (RRC) reconfiguration message for the release of the SCG.

[0037] According to the implementation of the third aspect, at least one execution condition is sent in a Radio Resource Control (RRC) reconfiguration message, which includes at least one of an initial conditional PScell ​​change CPC condition configuration or a subsequent CPC condition configuration.

[0038] According to the third aspect of the implementation, the method includes: sending an instruction to a user node to suspend the evaluation of at least one execution condition for the released SCG.

[0039] According to the implementation of the third aspect, the instructions sent to the user node include: instructions to suspend the evaluation of at least one execution condition of the released SCG for a specific period of time starting from the release of the SCG.

[0040] According to the implementation of the third aspect, the instructions sent to the user node include: suspending the evaluation of at least one execution condition for the released SCG until the user node executes at least one conditionally added PCell instruction.

[0041] According to a fourth aspect, a method executed by a user node is provided. The method includes: receiving from a master node at least one execution condition for adding a Conditional Primary / Secondary Cell Permitted Charge (CPA) to a Conditional Primary / Secondary Cell (PSC) cell, the at least one execution condition being applied by the user node for an evaluation of subsequent Conditional PSC cell addition or modification SCPAC conditions for the execution of a CPA to be performed after the release of the Secondary Cell Group (SCG), wherein the at least one execution condition for the CPA is configured to replace at least one execution condition configured to be given to the user node for an evaluation of SCPAC conditions for modifying a Conditional PSC cell.

[0042] According to the implementation of the fourth aspect, at least one execution condition for CPA includes at least one A4 event condition mapped to the primary cell group (MCG) configuration, wherein the at least one A4 event condition is defined for the candidate SCPAC configuration.

[0043] According to the implementation of the fourth aspect, at least one execution condition for CPA includes configuring a common A4 event condition for all candidate SCPACs.

[0044] According to the implementation of the fourth aspect, at least one execution condition for CPA includes an A4 event condition specific to each candidate SCPAC configuration.

[0045] According to the implementation of the fourth aspect, at least one execution condition for CPA includes instructions for maintaining the measurement configuration associated with the released SCG and SCPAC condition evaluation, wherein the instructions instruct the user node, after the SCG is released, to continue the SCPAC condition evaluation using the measurement configuration associated with the released SCG based on at least one of the CPC's A3 event condition or A5 event condition.

[0046] According to the implementation of the fourth aspect, at least one execution condition for CPA is received in a Radio Resource Control (RRC) reconfiguration message, which includes at least one of an initial CPC condition configuration or a subsequent CPC condition configuration.

[0047] According to the implementation of the fourth aspect, at least one execution condition for CPA is received in the RRC reconfiguration message for SCG release.

[0048] According to the fourth aspect, the method includes: receiving from a master node an instruction to suspend the evaluation of at least one execution condition for CPA against the released SCG; and suspending the evaluation of at least one execution condition for CPA against the released SCG according to the instruction.

[0049] According to the implementation of the fourth aspect, the instructions received from the master node include: instructions for suspending the evaluation of at least one execution condition for CPA against the released SCG for a specific period of time starting from the release of the SCG.

[0050] According to the implementation of the fourth aspect, the instructions received from the master node include: suspending the evaluation of at least one execution condition for CPA against the released SCG until the user node executes at least one conditionally added PCell instruction.

[0051] According to the implementation of the fourth aspect, the method includes: receiving a reconfiguration message for SCG release from the master node; performing SCG release, including: releasing the SCG configuration, releasing the measurement configuration of at least one of the initial CPC condition or the subsequent CPC condition, releasing the CPC condition or the subsequent CPC condition; applying an SCPAC condition evaluation based on at least one execution condition for CPA; and performing an evaluation of conditional PScell ​​addition execution based on at least one execution condition for CPA applied for the candidate SCPAC configuration during or after SCG release.

[0052] According to the implementation of the fourth aspect, the method includes: receiving from the master node at least one execution condition for CPA and an instruction to deactivate at least one execution condition for CPA; storing at least one execution condition in a deactivated state; and receiving from the master node a reconfiguration message for SCG release and an instruction to activate at least one execution condition for CPA.

[0053] According to the implementation of the fourth aspect, the method includes: receiving a reconfiguration message for SCG release from the master node before the initial conditional PScell ​​change has been executed; performing SCG release, including: maintaining the SCG configuration, maintaining the measurement configuration of the initial CPC condition, and maintaining the initial CPC condition; updating the initial CPC condition for CPA, wherein for the candidate SCPAC configuration, the initial CPC condition is evaluated using the released PScell ​​measurement as the service PScell ​​measurement; and performing an evaluation of the conditional PScell ​​addition execution based on the update at or after the SCG release.

[0054] According to the implementation of the fourth aspect, the method includes: receiving a reconfiguration message for SCG release from the master node after the initial conditional PScell ​​change is executed; performing SCG release, including: maintaining the SCG configuration, maintaining the measurement configuration of subsequent conditional PScell ​​change CPC conditions, and maintaining subsequent CPC conditions; updating subsequent CPC conditions for CPA, wherein for candidate SCPAC configurations, the initial CPC conditions are evaluated using the released PScell ​​measurement as a serving PScell ​​measurement; and performing an evaluation of conditional PScell ​​addition execution based on the update at or after SCG release.

[0055] According to a fifth aspect, an apparatus includes at least: components for sending to a user node at least one execution condition for adding a Conditional Primary / Secondary Cell Permitted Charge (CPA) to a Conditional Primary / Secondary Cell (PSC) cell, the at least one execution condition being applied by the user node for an evaluation of subsequent Conditional PSC cell addition or modification SCPAC conditions for the execution of a CPA to be performed after the release of the Secondary Cell Group (SCG), and wherein the at least one execution condition for the CPA is configured to replace at least one execution condition configured to be given to the user node for an evaluation of SCPAC conditions for modifying a Conditional PSC cell. The apparatus may further include components for performing any implementation of the method according to a third aspect.

[0056] According to the sixth aspect, a computer-readable medium includes instructions that, when executed by a means, cause the means to perform any implementation of the method according to the third aspect.

[0057] According to the seventh aspect, an apparatus includes at least: a component for receiving from a master node at least one execution condition for adding a Conditional Primary / Secondary Cell Permitted Charge (CPA) to a Conditional Primary / Secondary Cell (PSC) cell, the at least one execution condition being applied by a user node for an evaluation of subsequent Conditional PSC cell addition or modification SCPAC conditions for the execution of a CPA to be performed after the release of the Secondary Cell Group (SCG), and wherein the at least one execution condition for the CPA is configured to replace at least one execution condition configured to be given to the user node for an evaluation of SCPAC conditions for modifying a Conditional PSC cell. The apparatus may further include a component for performing any implementation of the method according to the fourth aspect.

[0058] According to the eighth aspect, a computer-readable medium includes instructions that, when executed by a means, cause the means to perform any implementation of the method according to the fourth aspect.

[0059] Many of the accompanying features will be more readily understood by referring to the following detailed description in conjunction with the accompanying drawings. Attached Figure Description

[0060] The accompanying drawings are provided to further illustrate the exemplary embodiments and form part of this specification. The drawings depict exemplary embodiments and, together with the specification, help to explain these exemplary embodiments. In the drawings:

[0061] Figure 1 An example of a communication system including a network node and at least one client node according to an exemplary embodiment is illustrated.

[0062] Figure 2 The illustration shows an example of a device configured to practice one or more example embodiments;

[0063] Figure 3 The illustration shows an example message sequence diagram for managing SCPAC conditions for CPA execution during or after SCG release, according to an example embodiment.

[0064] Figure 4 The illustration shows an example of a message sequence diagram for managing SCPAC conditions during SCG release, according to an example embodiment.

[0065] Figure 5 The illustration shows an example of a message sequence diagram for managing SCPAC conditions by partially releasing prior conditions during SCG release, according to an example embodiment.

[0066] Figure 6 The illustration shows an example of a method for a network node to manage SCPAC conditions for CPA execution during or after SCG release, according to an example embodiment.

[0067] Figure 7 An example of a method for a user node to manage SCPAC conditions for CPA execution during or after SCG release, according to an example embodiment, is illustrated.

[0068] In the accompanying drawings, the same reference numerals are used to denote the same parts. Detailed Implementation

[0069] Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. The detailed description provided below, in conjunction with the drawings, is intended as a description of the example and is not intended to represent the only form in which the example can be constructed or used. This description illustrates the functionality of the example and the possible sequences of operations for constructing and operating the example. However, the same or equivalent functionality and sequences can be implemented through different examples.

[0070] The goal is to manage subsequent PScell ​​addition or change conditions so that user nodes are configured to update the initial CPC conditions used to evaluate candidate subsequent PScell ​​addition or change configurations to CPA conditions, so that CPA can be performed at or after SCG release.

[0071] According to an example embodiment, the master node can be configured to configure user nodes for subsequent CPAs before or during the release of the SCG configuration. User nodes can update CPC conditions to enable CPA conditions when the SCG is released. CPC conditions can be updated by either updating A3 / A5 conditions that will partially apply to the configuration for subsequent CPAs and using the measurement of the released PScell ​​as the serving PScell; or updating A3 / A5 conditions to A4 conditions. This method can enable reductions in signaling overhead and downtime for SCG changes. When user nodes are pre-configured with CPA conditions before SCG release, they can evaluate the CPA conditions for SCPAC configuration in advance and perform CPA after a detected trigger, such as based on a trigger provided by the network or based on a single detected connection of the user node. This enables time savings for user nodes to establish new SCG links by performing SCPAC configurations that satisfy the CPA conditions if the CPA conditions are already met when the SCG is released.

[0072] Figure 1 An example of a communication system 100 including network nodes and at least one client node is illustrated. Communication system 100 may include one or more base stations, such as gNBs. One of the base stations may act as a primary node (MN) 104. Additionally, one or more other base stations may act as secondary nodes (SNs) 106. Communication system 100 may also include one or more client nodes, which may also be referred to as user nodes or UEs (user equipment). For example, the network may include UE 102. UE 102 may communicate with one or more base stations via radio channels(s). Communication between UE 102, MN 104, and SN 106 may be bidirectional. Therefore, any device can be configured to operate as a transmitter and / or receiver.

[0073] Base stations can be configured to communicate with core network elements (e.g., Access and Mobility Management Functions (AMF) and / or User Plane Functions (UPF)) via communication interfaces (e.g., control plane interface or user plane interface NG-C / U). Base stations can also be referred to as Radio Access Network (RAN) nodes, and they can be part of the radio access network between the core network and the UE. Network elements AMF / UPF and gNB can generally be referred to as network nodes or network devices. Although depicted as a single device, a network node may not be a standalone device, but rather a distributed computing system, for example, coupled to a remote radio headend.

[0074] The communication system 100 can be configured, for example, according to a fifth-generation digital cellular communication network as defined by the 3rd Generation Partnership Project (3GPP). In one example, the communication network 100 may operate according to 3GPP 5G-NR (New Radio). However, it should be understood that the example embodiments presented herein are not limited to this example network and can be applied to any current or future wireless or wired communication network or a combination thereof, such as other types of cellular networks, short-range wireless networks, broadcast or multicast networks, etc.

[0075] Dual connectivity (DC) allows a UE to simultaneously send and receive data from two serving nodes or cell groups on multiple component carriers. Dual connectivity can be enabled between two serving nodes operating with the same technology or different radio access technologies (RATs). UE 102 can be configured to communicate with MN 104 and SN 106 via the air interface and perform dual connectivity with the primary cell group (MCG) and secondary cell group (SCG). MN 104 and SN 106 can be configured to operate in the same RAT or different RATs. The scenario where nodes operate in different radio access technologies is referred to as multi-RAT dual connectivity. Example configurations of multi-radio dual connectivity (MR-DC) include EN-DC (E-UTRA-NR dual connectivity), NR-DC (New Radio Dual Connectivity), NGEN-DC (NG-RAN-EUTRA dual connectivity), and NE-DC (NR-E-UTRA dual connectivity).

[0076] In MR-DC, MN can refer to a radio access node configured to provide control plane connectivity to the core network. The primary node can be, for example, a primary gNB. The primary cell group (MCG) can refer to the serving cell group associated with the primary node. The secondary cell group (SCG) can refer to the serving cell group associated with the secondary node. A secondary node can refer to a radio access node without control plane connectivity to the core network. A secondary node can be configured to provide additional resources to the UE. A secondary node can be, for example, a secondary gNB. Each network node can have its own Radio Resource Control (RRC) entity, which can generate RRC Protocol Data Units (PDUs) to be sent to the UE. The primary / secondary cell (PScell) can refer to the secondary cell group cell in which the UE performs random access during reconfiguration using the synchronization procedure.

[0077] SCG reconfiguration can be performed through the RRC reconfiguration procedure. The RRC reconfiguration message may include conditional reconfiguration. Conditional reconfiguration may include the configuration of one or more candidate cells and one or more execution conditions. Conditional reconfiguration can be used for at least one of the following: conditional handover (CHO, e.g., change of primary cell), conditional PScell ​​change (CPC), or conditional PScell ​​addition (CPA). The UE can perform the conditional reconfiguration procedure when it has assessed that one or more execution conditions associated with the conditional reconfiguration are met. When one or more execution conditions are met, the UE can be configured to connect to the target cell.

[0078] For example, a mobility procedure pre-configured for a UE to change its PScell ​​can be referred to as a conditional PScell ​​change (CPC). During a CPC, the UE can be configured to change its SCG configuration from one cell group to another, where the PScells for each SCG can be different. The UE can perform a CPC when predefined execution conditions are met. For example, execution conditions may include one or more measurement events, such as event A3 or event A5 (if the conditions are determined by the SN). Event A3 is met when the offset of a neighboring PScell ​​is better than the serving PScell ​​based on the measurement results (e.g., RSRP) of the corresponding cell and the offset parameter defined for the event. Event A5 is met when the serving PScell ​​becomes worse than a first threshold based on the measurement results (e.g., RSRP) of the corresponding cell and the neighboring PScell ​​becomes better than a second threshold based on the measurement results (e.g., RSRP) of the corresponding cell. Events A3 and A5 can be configured as defined in TS 38.331. The UE can evaluate events or conditions A3 and A5 by using the serving SN measurement configuration.

[0079] For example, the UE can receive an RRC reconfiguration message with CPC configuration and begin evaluating CPC execution conditions for (multiple) candidate PScells. If at least one CPC candidate PScell ​​meets the corresponding CPC execution condition, the UE completes the CPC execution process. The UE detaches from the source PScell, applies the stored corresponding configuration, and synchronizes to the selected candidate PScell, i.e., the target PScell. The source PScell ​​can be included in a source SCG controlled by the source SN. The target PScell ​​can be included in a target SCG controlled by the target SN.

[0080] For example, the CPC type can be an intra-SN CPC or an inter-SN CPC. In an intra-SN CPC, the SN of the secondary cell group (SCG) configured to control the UE can be configured to remain unchanged. In other words, the source SN or the SN controlling the source SCG is the same as the target SN (i.e., the SN controlling the target SCG).

[0081] In inter-SN CPC, the SN controlling the SCG of the UE changes. In other words, the source SN, or the SN controlling the source SCG before CPC execution, is different from the target SN controlling the target SCG after CPC execution. For SN-initiated inter-SN SCG selective activation, the source SN can be configured to generate the execution conditions for the initial CPC. Furthermore, candidate SNs can be configured to generate execution conditions for subsequent CPCs.

[0082] A CPAC (Conditional PScell ​​Addition or Modification) can be defined as a UE having network configuration to initiate access to a candidate PScell ​​to determine whether the PScell ​​is suitable for SN addition or SN modification based on configured conditions(s). An SCPAC can refer to a subsequent CPAC following the initial CPAC. For example, a subsequent CPAC can refer to any CPAC following the initial CPAC. (S) The CPAC execution conditions and / or candidate PScell ​​configuration can be updated, for example, by modifying existing conditional configurations. One or more candidate PScells can be configured in one or more Radio Resource Control messages.

[0083] For subsequent CPACs initiated by MN, the execution condition configuration can be provided as follows, for example:

[0084] MN can be configured to generate execution conditions (e.g., A4 event) for the initial CPAC execution, and the measurement identifier can refer to the measurement configuration associated with MCG;

[0085] Candidate SNs can be configured to generate execution conditions for subsequent CPC executions (e.g., A3 / A5 events), and measurement identifiers can refer to measurement configurations associated with SCGs.

[0086] CPA can refer to a situation where the UE has no SCG configuration and then adds an SCG configuration. Therefore, the UE can move from single-connectivity to dual-connectivity. In the case of CPA, the execution conditions can be determined by the MN (because there is no SN) and can be configured with an A4 event. Event A4 is satisfied when a neighboring PScell ​​becomes higher than a threshold. For example, the signal level (Reference Received Power RSRP) or quality (Reference Received Quality RSRQ) of a neighboring PScell ​​can be higher than the threshold set for RSRP or RSRQ. Cell-specific offset, frequency-specific offset, and hysteresis can be considered before comparing the signal level or quality to the threshold. The UE can evaluate event A4 by using the measurement configuration of the serving MN. CPA conditional configuration can be used for CPC, but with different triggering conditions.

[0087] For example, when the execution conditions of a CPC candidate PScell ​​are met, the UE can be configured to perform CPC execution towards that candidate PScell. After completing the PScell ​​change, the UE may not use it for subsequent CPC release of other candidate PScells under conditional configuration, and the UE can continue to evaluate the execution conditions of other candidate PScells. When the execution conditions of a candidate PScell ​​are met, the UE can perform CPC execution towards that candidate PScell.

[0088] If the service SCG is released, the UE can release the SCG measurement configuration and conditions. This poses a problem for the execution of candidate SCPAC configurations, as the UE may not be able to determine the execution of a candidate configuration without any conditions. In one embodiment, the UE can be configured to modify at least one execution condition used for PScell ​​changes to at least one execution condition used for PScell ​​additions.

[0089] According to the example embodiment, UE 102 can be configured for subsequent CPA conditional configuration evaluation performed by the network node (i.e., MN 104). In the example embodiment, a common measurement configuration and A4 conditions can be defined for all candidate subsequent conditional PScells to add / change configurations (common A4 CPA measurement configurations). For example, such a common A4 CPA measurement configuration can be pre-configured during CPC preparation. The common A4 CPA measurement configuration can be configured as part of the MCG configuration. The pre-configuration of the execution conditions (A4 conditions) enables the UE to begin evaluating the execution conditions before the SCG is released. In response to the SCG release, UE 102 can be configured to begin evaluating the A4 conditions of the reserved SCPAC configuration. Alternatively, this can be network-controlled, i.e., the network is configured to instruct activation / deactivation of the common A4 condition evaluation.

[0090] UE 102 can be configured to continuously perform evaluation of the common A4 condition. However, if the condition is met, UE 102 can be configured to perform a candidate SCPAC configuration upon network indication. Alternatively, if UE 102 is in a single-connection state, UE 102 can be configured to perform a candidate SCPAC configuration.

[0091] In one embodiment, instead of a common configuration, MN 104 can be configured to provide candidate PScell-specific A4 conditions and measurement configurations for UE 102.

[0092] In one embodiment, MN 104 can be configured to provide UE 102 with A4 conditions and measurement configurations in response to SCG release, such as upon SCG release. For example, the A4 condition configuration may be part of the measurement configuration. UE 102 can be configured to release the SCG configuration along with all associated measurement configurations and associated conditions. For example, UE 102 can be configured to release at least one of the initial or subsequent CPC condition configurations. UE 102 can be configured to apply the measurement configurations and A4 conditions provided by MN 104 to SCPAC candidate configurations retained after SCG release. This enables UE 102 to use the measurement configurations and conditions from MN 104 even if the CPAC is a subsequent CPAC, i.e., even after the initial CPC has been executed.

[0093] In one embodiment, when an SCG is released, the SCG configuration can be released, while the measurement configuration used for the candidate PScell ​​configuration (SCPAC configuration) can still be maintained at the UE (i.e., not released). Therefore, UE 102 can use the measurement configuration of the released SCG and the PScell ​​measurements of the released PScell ​​to continue evaluating the A3 / A5 execution conditions of other candidate SNs for CPA (in order to add new SNs). In this technical solution, a partial release mechanism on the UE side may be required. In partial release, UE 102 can be configured to release the SCG configuration but maintain the measurement configuration associated with the released SCG. UE 102 can be configured to use the released PScell ​​measurements for the service PScell ​​measurements defined in A3 / A5 to continue evaluating the A3 / A5 execution conditions.

[0094] In the event of an SCG release, a CPA may not be evaluated for the released SCG. Therefore, MN 104 can be configured to instruct UE 102 to suspend the evaluation of the released SCG. For example, MN 104 can be configured to instruct UE 102 to start a timer when an SCG is released, and when the timer expires, UE 102 can evaluate the CPA for the most recently released SCG / PScell.

[0095] Alternatively, the pause instruction may include marking the corresponding conditional configuration as deactivated for that PScell ​​after the SCG is released. As part of the conditional configuration deactivation, the CPA execution conditions of the released PScell ​​may not be evaluated. At DC, i.e., when adding another PScell, the conditional configuration of the released PScell ​​can be configured to be marked as activated by UE 102. Then, the CPC / CPA conditional evaluation of the released PScell ​​can begin. For example, UE 102 may receive the pause instruction in an RRC reconfiguration message for SCG release received from MN 104.

[0096] Figure 2 An example of a device 200 configured to practice one or more example embodiments is illustrated. Device 200 may include, for example, a client node, such as UE 102; or a network node, such as master node 104, and is configured to perform the respective functions of UE 102 or master node 104 described herein.

[0097] The device 200 may include at least one processor 202. For example, at least one processor 202 may include one or more of a variety of processing devices, such as a coprocessor, microprocessor, controller, digital signal processor (DSP), processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits, such as application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), microcontroller units (MCUs), hardware accelerators, dedicated computer chips, etc.

[0098] The device 200 may also include at least one memory 204. The memory 204 may be configured to store, for example, computer program code 206, such as operating system software and application software. The memory 204 may include one or more volatile memory devices, one or more non-volatile memory devices, and / or combinations thereof. For example, the memory 204 may be embodied as a magnetic storage device (such as a hard disk drive, magnetic tape, etc.), an optical storage device, or a semiconductor memory (such as a mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash ROM, RAM (random access memory), etc.).

[0099] Device 200 may also include one or more communication interfaces 208 configured to enable device 200 to send and / or receive information to / from other devices. Communication interface 208 may be configured to provide at least one wireless connection, such as a 3GPP mobile broadband connection (e.g., 3G, 4G, 5G, or higher). However, communication interface 208 may be configured to provide one or more other types of connections, such as a wireless local area network (WLAN) connection, such as a connection standardized by the IEEE 802.11 series or the Wi-Fi Alliance; a short-range wireless network connection, such as Bluetooth, NFC (Near Field Communication), or RFID connection; a wired connection, such as a local area network (LAN) connection, a Universal Serial Bus (USB) connection, or an optical network connection; or a wired Internet connection. Communication interface 208 may include or be configured to be coupled to at least one antenna to transmit and / or receive radio frequency signals. One or more of the various types of connections may also be implemented as a separate communication interface, which may be coupled to or configured to be coupled to multiple antennas.

[0100] The device 200 may also include a user interface, which includes input devices and / or output devices. Input devices may take various forms, such as a keyboard, a touchscreen, or one or more embedded control buttons. Output devices may include, for example, a display, a speaker, a vibration motor, etc.

[0101] When device 200 is configured to perform a certain function, one or more components of device 200 (such as, for example, at least one processor 202 and / or memory 204) can be configured to perform that function. Furthermore, when at least one processor 202 is configured to perform a certain function, that function can be implemented using, for example, instructions of program code 206 included in memory 204.

[0102] The functions described herein may be performed at least in part by one or more computer program product components, such as software components. According to an embodiment, device 200 includes a processor or processor circuitry, such as, for example, a microcontroller, configured by program code (when executed) to perform embodiments of the described operations and functions. Alternatively or additionally, the functions described herein may be performed at least in part by one or more hardware logic components. Examples, but not limited to, illustrative types of hardware logic components that may be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and graphics processing units (GPUs).

[0103] The apparatus 200 may include components for performing at least one method described herein. In one example, the components include at least one processor 202 and at least one memory 204 including instructions (e.g., program code 206) configured to cause the apparatus 200 to perform the method when executed by the at least one processor 202.

[0104] Device 200 may include, for example, computing devices such as base stations, network nodes, server devices, client nodes, mobile phones, tablet computers, laptop computers, etc. Although device 200 is illustrated as a single device, it should be understood that, where applicable, the functionality of device 200 may be distributed across multiple devices.

[0105] Apparatus 200 can be configured to manage SCPAC conditions(s) upon SCG release. Apparatus 200 can be configured to at least send or receive instructions for user nodes to apply one or more execution conditions for subsequent CPAs after SCG release. These instructions may include at least one of the following: updating the execution conditions to a common A4 condition and measurement configuration used for evaluation of all candidate SCPAC configurations; updating to a list of A4 conditions and measurement configurations specific to each candidate SCPAC configuration evaluation; or, after SCG release, continuing evaluation using the current CPC conditions with the released PScell ​​measurement as the serving PScell.

[0106] Figure 3 An example message sequence diagram for managing SCPAC conditions during SCG release, according to an exemplary embodiment, is illustrated. UE 102 may be pre-configured with at least one execution condition for CPA for subsequent CPAC condition evaluation. Pre-configuration may be performed, for example, during CPC preparation. UE 102 may also be pre-configured with a measurement configuration for CPA. UE 102 may evaluate whether at least one execution condition is met before, during, and / or after SCG release. However, even if the evaluation is performed before SCG release, UE 102 may be configured to perform CPA during or after SCG release. Evaluation-based CPA execution may be triggered based on an activation indication received from the master node. Alternatively, evaluation-based CPA execution may be triggered when UE 102 is in a single-connection state.

[0107] At point 300, a user node (such as UE 102) can be configured to send a measurement report to S-SN 106A (serving secondary node). S-SN 106A can be configured to initiate an inter-SN SCPAC based on the received measurement report.

[0108] At 302, S-SN 106A can be configured to send a message to MN 104 indicating the required SN change. This message may include initial CPC conditions (e.g., A3 / A5 event conditions).

[0109] At 304, MN 104 can be configured to send a request for SN addition to T-SN-1 106B (the first target secondary node). At 306, MN 104 can be configured to send a request for SN addition to T-SN-2 106C (the second target secondary node). At 308, MN 104 can be configured to send requests for SN addition to other potential target secondary nodes (such as to one or more T-SN-N 106D). S-SN 106A, T-SN-1 106B, T-SN-2 106C, and T-SN-N can be SN 106 of the SCG.

[0110] At 310, MN 104 can be configured to receive a response from T-SN-1 106B. T-SN-1 106B can be configured to respond with a request acknowledgment message appended with the SN. The response may include subsequent CPC conditions (e.g., A3 / A5 event conditions).

[0111] At 312, MN 104 can be configured to receive a response from T-SN-2 106C. T-SN-2 106C can be configured to respond with a request acknowledgment message appended with the SN. The response may include subsequent CPC conditions (e.g., A3 / A5 event conditions).

[0112] At 314, MN 104 can be configured to receive responses from (multiple) other potential T-SNs. For example, one or more T-SN-N 106Ds can be configured to respond with a request acknowledgment message added by the SN. The response may include subsequent CPC conditions (e.g., A3 / A5 event conditions).

[0113] At 316, MN 104 can be configured to send an RRC reconfiguration message to UE 102. The RRC configuration message may include at least one of the following: initial conditions (A3 / A5), a list of subsequent CPC conditions for T-SN-1, T-SN-2 and / or one or more T-SN-Ns, one or more execution conditions of the CPA to be applied to the SCPAC evaluation, or an indication to deactivate one or more execution conditions used for the CPA.

[0114] One or more execution conditions may include common A4 CPA conditions and measurement configurations for all candidate SCPAC configurations. Alternatively, one or more execution conditions may include a list of A4 CPA conditions and measurement configurations for each candidate SCPAC configuration. Therefore, UE 102 can be configured to perform subsequent CPA evaluations based on A4 event conditions and measurement conditions that are common to all candidate SCPAC configurations, or based on A4 event conditions and measurement configurations specific to each candidate SCPAC configuration. Measurement configurations can be mapped to MCG configurations.

[0115] At 318, UE 102 can be configured to register one or more execution conditions (public A4 CPA conditions or a list of A4 CPA conditions) for SCPAC execution in a deactivated state. UE 102 can also be configured to evaluate initial CPC conditions (e.g., A3 / A5 events).

[0116] At 320, UE 102 can be configured to send a response to the RRC configuration message received from MN 104 at 316. UE 102 can be configured to respond to MN 104 with a message indicating that the RRC configuration is complete.

[0117] At 322, MN 104 can be configured to send an SN change confirmation message to S-SN 106A.

[0118] At 324, MN 104 can be configured to send an SN release request to S-SN 106A. This request can be sent due to throughput requirements or low load (below a predetermined threshold), and therefore the SN / DC may no longer be needed. Alternatively, the request can be sent because the link between UE 102 and the source SN is no longer strong (e.g., the parameter value indicating link strength is below a certain threshold), and therefore the link can be released before any failure.

[0119] At 326, S-SN 106A can be configured to acknowledge the SN release request to MN 104.

[0120] At 328, MN 104 can be configured to send an RRC reconfiguration message for SCG release to UE 102. The RRC reconfiguration message may include an indication to activate one or more execution conditions, namely, a common A4 CPA condition or a list of A4 CPA conditions.

[0121] At 330, UE 102 can be configured to perform an SCG release procedure. For example, if the SCG release is performed before the initial CPC is executed, UE 102 can be configured to perform at least one of the following: release the SCG configuration, release the measurement configuration of the initial CPC condition, release the initial CPC condition, or activate the public A4 CPA condition / A4CPA condition list for SCPAC evaluation.

[0122] At 332, UE 102 can be configured to respond to an RRC reconfiguration message received from MN 104 at 328, indicating that the RRC reconfiguration has been completed.

[0123] The SCG can also be released after the initial CPC execution. For example, at 334, UE 102 can be configured to perform the SCPAC configuration of T-SN-1 106B when the T-SN-1 CPC conditions are met. At 336, UE 102 performs the RACH (Random Access Channel) procedure with T-SN-1 106B.

[0124] At 338, UE 102 can be configured to begin evaluating subsequent CPC conditions (A3 / A5) for T-SN-1 106B.

[0125] At 340, UE 102 can be configured to send a message to MN 104 indicating that the RRC reconfiguration has been completed. This message includes an indication that the SN reconfiguration has been completed.

[0126] At position 342, MN 104 can be configured to send an SN release request to T-SN-1 106B. The SN release request can be configured to be sent due to throughput requirements or low throughput load. Therefore, an SN / DC may not be required. Alternatively, the SN release request can be configured to be sent because the link between UE 102 and the source SN is no longer strong.

[0127] At 344, T-SN-1 106B can be configured to send a response to MN 104 to acknowledge the SN release request received at 342.

[0128] At 346, MN 104 can be configured to send an RRC reconfiguration message for SCG release to UE 102. The RRC reconfiguration message may include an indication to activate the common A4 CPA condition or the A4 CPA condition list indicated at 316.

[0129] At 348, UE 102 can be configured to perform an SCG release procedure. In the case of an SCG release following the execution of the initial CPC, UE 102 can be configured to perform at least one of the following: release the SCG configuration, release the measurement configuration of subsequent CPC conditions, release subsequent CPC conditions, or activate the public A4 CPA conditions / A4 CPA condition list for SCPAC evaluation.

[0130] At 350, UE 102 can be configured to send a response to the RRC reconfiguration message received from MN 104 at 346 to notify MN 104 that the RRC reconfiguration has been completed.

[0131] At 352, UE 102 can be configured to use the MCG measurement configuration and evaluate the common A4 CPA conditions for all candidate SCPAC configurations. Alternatively, UE 102 can be configured to use the MCG measurement configuration and evaluate a list of A4 CPA conditions for each candidate SCPAC configuration.

[0132] At 354, UE 102 can be configured to perform T-SN-2SCPAC configuration when it is detected that the T-SN-2 CPA condition is met.

[0133] At 356, UE 102 can be configured to perform the RACH procedure with T-SN-2 106C.

[0134] Figure 4 The illustration shows another example of a message sequence diagram for managing SCPAC conditions during SCG release, according to an example embodiment. Here, instead of pre-configuring one or more execution conditions for subsequent CPA for UE 102 prior to SCG release, master node 104 can be configured to indicate one or more execution conditions for CPC-to-CPA transition for SCPAC evaluation during SCG release. Figure 3 and Figure 4 The corresponding operations are indicated by the corresponding figures.

[0135] At point 300, UE 102 can be configured to send a measurement report to S-SN 106A. S-SN 106A can be configured to initiate an inter-SN SCPAC based on the received measurement report.

[0136] At 302, S-SN 106A can be configured to send a message to MN 104 indicating the required SN change. This message may include initial CPC conditions (e.g., A3 / A5 event conditions).

[0137] At 304, MN 104 can be configured to send a request for SN addition to T-SN-1 106B. At 306, MN 104 can be configured to send a request for SN addition to T-SN-2 106C. At 308, MN 104 can be configured to send a request for SN addition to other potential target secondary nodes, such as to one or more T-SN-N 106D.

[0138] At 310, MN 104 can be configured to receive a response from T-SN-1 106B. T-SN-1 106B can be configured to respond with a request acknowledgment message appended with the SN. The response may include subsequent CPC conditions (e.g., A3 / A5 event conditions).

[0139] At 312, MN 104 can be configured to receive a response from T-SN-2 106C. T-SN-2 106C can be configured to respond with a request acknowledgment message appended with the SN. The response may include subsequent CPC conditions (e.g., A3 / A5 event conditions).

[0140] At 314, MN 104 can be configured to receive responses from (multiple) other potential T-SNs. For example, one or more T-SN-N 106Ds can be configured to respond with a request acknowledgment message added by the SN. The response may include subsequent CPC conditions (e.g., A3 / A5 event conditions).

[0141] At 400, MN 104 can be configured to send an RRC reconfiguration message to UE 102. The RRC configuration message may include at least one of the following: an initial condition (A3 / A5) for S-SN 106A, or a list of subsequent CPC conditions for T-SN-1 106B, T-SN-2 106C, and / or one or more T-SN-N 106D.

[0142] At 402, UE 102 can be configured to evaluate initial CPC conditions (e.g., A3 / A5 events).

[0143] At 404, UE 102 can be configured to send a response to the RRC configuration message received from MN 104 at 400. UE 102 can be configured to respond to MN 104 with a message indicating that the RRC configuration is complete.

[0144] At 322, MN 104 can be configured to send an SN change confirmation message to S-SN 106A.

[0145] At 324, MN 104 can be configured to send an SN release request to S-SN 106A. This request can be sent due to throughput requirements or low load (below a predetermined threshold), and therefore the SN / DC may no longer be needed. Alternatively, the request can be sent because the link between UE 102 and the source SN is no longer strong (e.g., the parameter value indicating link strength is below a certain threshold), and therefore the link can be released before any failure.

[0146] At 326, S-SN 106A can be configured to respond to MN 104 with an SN release request acknowledgment.

[0147] At 406, MN 104 can be configured to send an RRC reconfiguration message for SCG release to UE 102. The RRC reconfiguration message may include one or more execution conditions for subsequent CPA. The one or more execution conditions may include common A4 CPA conditions and measurement configurations for all candidate SCPAC configurations. Alternatively, the one or more execution conditions may include a list of A4 CPA conditions and measurement configurations for each candidate SCPAC configuration. Therefore, UE 102 can be configured to perform subsequent CPA evaluation based on A4 event conditions and measurement configurations that are common to all candidate SCPAC configurations, or based on A4 event conditions and measurement configurations specific to each candidate SCPAC configuration. Measurement configurations can be mapped to MCG configurations.

[0148] At 408, UE 102 can be configured to perform an SCG release procedure. For example, if the SCG release is performed before the initial CPC is executed, UE 102 can be configured to perform at least one of the following: release SCG configuration, release measurement configuration of initial CPC conditions, release initial CPC conditions, or apply common A4 CPA conditions / A4 CPA condition list to perform SCPAC evaluation.

[0149] At 410, UE 102 can be configured to respond to an RRC reconfiguration message received from MN 104 at 406, indicating that the RRC reconfiguration has been completed.

[0150] The SCG can also be released after the initial CPC execution. For example, at 334, UE 102 can be configured to perform the SCPAC configuration of T-SN-1 106B when the T-SN-1 CPC conditions are met. At 336, UE 102 performs the RACH (Random Access Channel) procedure with T-SN-1 106B.

[0151] At 338, UE 102 can be configured to begin evaluating subsequent CPC conditions (A3 / A5) for T-SN-1 106B.

[0152] At 340, UE 102 can be configured to send a message to MN 104 indicating that the RRC reconfiguration has been completed. This message includes an indication that the SN reconfiguration has been completed.

[0153] At position 342, MN 104 can be configured to send an SN release request to T-SN-1 106B. The SN release request can be configured to be sent due to throughput requirements or low throughput load. Therefore, an SN / DC may not be required. Alternatively, the SN release request can be configured to be sent because the link between UE 102 and the source SN is no longer strong.

[0154] At 344, T-SN-1 106B can be configured to send a response to MN 104 to acknowledge the SN release request received at 342.

[0155] At 412, MN 104 can be configured to send an RRC reconfiguration message for SCG release to UE 102. The RRC reconfiguration message may include one or more execution conditions applied by UE 102 for subsequent CPA, such as common A4 CPA conditions or a list of A4 CPA conditions.

[0156] At 414, UE 102 can be configured to perform an SCG release procedure. In the case of an SCG release following the execution of the initial CPC, UE 102 can be configured to perform at least one of the following: release the SCG configuration, release the measurement configuration of subsequent CPC conditions, release subsequent CPC conditions, or apply the common A4 CPA conditions / A4 CPA condition list for SCPAC evaluation.

[0157] At 416, UE 102 can be configured to send a response to the RRC reconfiguration message received from MN 104 at 412 to notify MN 104 that the RRC reconfiguration has been completed.

[0158] At 352, UE 102 can be configured to use the MCG measurement configuration and evaluate the common A4 CPA conditions for all candidate SCPAC configurations. Alternatively, UE 102 can be configured to use the MCG measurement configuration and evaluate a list of A4 CPA conditions for each candidate SCPAC configuration.

[0159] At 354, UE 102 can be configured to perform T-SN-2 SCPAC configuration when it is detected that the T-SN-2 106C CPA condition is met.

[0160] At 356, UE 102 can be configured to perform the RACH procedure with T-SN-2 106C.

[0161] Figure 5 An example message sequence diagram is illustrated according to an exemplary embodiment for managing SCPAC conditions by partially releasing previous conditions upon SCG release. Here, instead of indicating the A4CPA conditions(s) to be used for subsequent CPA evaluation / execution, master node 104 can be configured to instruct UE 102 to perform a partial release of initial or subsequent CPC conditions to evaluate candidate SCPAC configurations. Operations corresponding to those in the previous figures are illustrated using the same reference numerals.

[0162] At point 300, UE 102 can be configured to send a measurement report to S-SN 106A. S-SN 106A can be configured to initiate an inter-SN SCPAC based on the received measurement report.

[0163] At 302, S-SN 106A can be configured to send a message to MN 104 indicating the required SN change. This message may include initial CPC conditions (e.g., A3 / A5 event conditions).

[0164] At 304, MN 104 can be configured to send an SN add request to T-SN-1 106B. At 306, MN 104 can be configured to send an SN add request to T-SN-2 106C. At 308, MN 104 can be configured to send SN add requests to other potential target secondary nodes, such as to one or more T-SN-N 106D.

[0165] At 310, MN 104 can be configured to receive a response from T-SN-1 106B. T-SN-1 106B can be configured to respond with a request acknowledgment message appended with the SN. The response may include subsequent CPC conditions (e.g., A3 / A5 event conditions).

[0166] At 312, MN 104 can be configured to receive a response from T-SN-2 106C. T-SN-2 106C can be configured to respond with a request acknowledgment message appended with the SN. The response may include subsequent CPC conditions (e.g., A3 / A5 event conditions).

[0167] At 314, MN 104 can be configured to receive responses from (multiple) other potential T-SNs. For example, one or more T-SN-N 106Ds can be configured to respond with a request acknowledgment message added by the SN. The response may include subsequent CPC conditions (e.g., A3 / A5 event conditions).

[0168] At 500, MN 104 can be configured to send an RRC reconfiguration message to UE 102. The RRC reconfiguration message may include at least one of the following: an initial condition (A3 / A5) for S-SN 106A, or a list of subsequent CPC conditions for T-SN-1 106B, T-SN-2 106C, and / or one or more T-SN-N 106D. Optionally, the reconfiguration message may also include an instruction for performing a partial release of the relevant CPC condition (A3 / A5) in the event of an SCG release. This instruction may include instructions to continue the CPC conditions for SCPAC evaluation after the SCG release, using the released PScell ​​measurement as the PScell ​​measurement. The released PScell ​​measurement may be considered a servicing PScell ​​measurement.

[0169] At 502, UE 102 can be configured to evaluate initial CPC conditions (e.g., A3 / A5 events). UE 102 can also be configured to store instructions that will be applied when the SCG is released.

[0170] At 504, UE 102 can be configured to send a response to the RRC configuration message received from MN 104 at 500. UE 102 can be configured to respond to MN 104 with a message indicating that the RRC configuration is complete.

[0171] At 322, MN 104 can be configured to send an SN change confirmation message to S-SN 106A.

[0172] At 324, MN 104 can be configured to send an SN release request to S-SN 106A. This request can be sent due to throughput requirements or low load (below a predetermined threshold), and therefore the SN / DC may no longer be needed. Alternatively, the request can be sent because the link between UE 102 and the source / serving SN is no longer strong (e.g., the parameter value indicating link strength is below a certain threshold), and therefore the link can be released before any failure.

[0173] At 326, S-SN 106A can be configured to respond to MN 104 with an SN release request acknowledgment.

[0174] At 506, MN 104 can be configured to send an RRC reconfiguration message to UE 102 for SCG release. The RRC reconfiguration message may include instructions to execute one or more execution conditions, i.e., partial release of the relevant CPC (A3 / A5) conditions (if not already indicated at 500). For example, the reconfiguration message may include instructions for UE 102 to continue evaluating the A3 / A5 event and to use the released PScell ​​measurement as the serving PScell ​​measurement for the A3 / A5 evaluation. The released PScell ​​measurement can be considered a serving PScell ​​measurement.

[0175] At 508, UE 102 can be configured to perform the SCG release procedure. For example, if the SCG release is performed before the initial CPC is executed, UE 102 can be configured to perform at least one of the following based on instructions received from the master node in at least one of operations 500 or 506: release the SCG configuration, retain the measurement configuration of the initial CPC condition, retain the initial CPC condition, or use the released PScell ​​measurement as the serving PScell ​​measurement to continue evaluating the initial CPC condition of retaining the (candidate) SCPAC configuration.

[0176] At 510, UE 102 can be configured to respond to an RRC reconfiguration message received from MN 104 at 506, indicating that the RRC reconfiguration has been completed.

[0177] The SCG can also be released after the initial CPC execution. For example, at 334, UE 102 can be configured to perform the SCPAC configuration of T-SN-1 106B when the T-SN-1 CPC conditions are met. At 336, UE 102 performs the RACH (Random Access Channel) procedure with T-SN-1 106B.

[0178] At 338, UE 102 can be configured to begin evaluating subsequent CPC conditions (A3 / A5) for T-SN-1 106B.

[0179] At 340, UE 102 can be configured to send a message to MN 104 indicating that the RRC reconfiguration has been completed. This message includes an indication that the SN reconfiguration has been completed.

[0180] At position 342, MN 104 can be configured to send an SN release request to T-SN-1 106B. The SN release request can be configured to be sent due to throughput requirements or low throughput load. Therefore, an SN / DC may not be required. Alternatively, the SN release request can be configured to be sent because the link between the UE and the source SN is no longer strong.

[0181] At 344, T-SN-1 106B can be configured to send a response to MN 104 to acknowledge the SN release request received at 342.

[0182] At 512, MN 104 can be configured to send an RRC reconfiguration message to UE 102 for SCG release. The RRC reconfiguration message may include an indication to perform one or more execution conditions, namely, a partial release of the relevant CPC (A3 / A5) condition (if not already indicated at 500). For example, the reconfiguration message may include instructions for UE 102 to continue evaluating the A3 / A5 event and to use the released PScell ​​measurement as the serving PScell ​​measurement for A3 / A5 evaluation.

[0183] At 514, UE 102 can be configured to perform an SCG release procedure. In the case of an SCG release following the execution of the initial CPC, UE 102 can be configured to perform at least one of the following based on an instruction received from the master node in at least one of operations 500 or 512: retain the SCG configuration, retain the measurement configuration of the subsequent CPC conditions, retain the subsequent CPC conditions, or continue to evaluate the initial CPC conditions of the retained SCPAC configuration using the released PScell ​​measurement as the serving PScell ​​measurement.

[0184] At 516, UE 102 can be configured to send a response to the RRC reconfiguration message received from MN 104 at 512 to notify MN 104 that the RRC reconfiguration has been completed.

[0185] At 518, UE 102 can be configured to evaluate one or more A3 / A5 conditions for each candidate SCPAC configuration used for CPA using the SCG measurement configuration of the released SCG, wherein the released PScell ​​measurement is used as the service PScell ​​for A3 / A5 evaluation.

[0186] At 354, UE 102 can be configured to perform T-SN-2SCPAC configuration when it is detected that the T-SN-2 CPA condition is met.

[0187] At 356, UE 102 can be configured to perform the RACH procedure with T-SN-2 106C.

[0188] Figure 6 An example of a method 600 for a network node to manage SCPAC conditions for CPA execution during or after the release of an SCG, according to an example embodiment, is illustrated. The network node may include, for example, a master node 104.

[0189] At 602, the method may include: sending at least one execution condition for a CPA to a user node, the at least one execution condition being applied by the user node for evaluating SCPAC conditions to be performed during or after the release of the secondary cell group SCG. The at least one execution condition for a CPA may be configured to replace at least one execution condition configured to be given to the user node for evaluating SCPAC conditions for a CPC.

[0190] Figure 7 An example of a method 700 for a user node to manage SCPAC conditions for CPA execution during or after the release of an SCG, according to an example embodiment, is illustrated. The user node may include, for example, UE 102.

[0191] At 702, the method may include: receiving from the master node at least one execution condition for adding a Conditional Primary / Secondary Cell Permitted Action (CPA) to a Conditional Primary / Secondary Cell (PSC) cell, the at least one execution condition being applied by the user node for evaluation of subsequent Conditional PSC addition or modification of SCPAC conditions performed during or after a CPA is released in the Secondary Cell Group (SCG). The at least one execution condition for the CPA may be configured to replace at least one execution condition configured to be given to the user node for evaluation of SCPAC conditions for modifying a Conditional PSC cell.

[0192] Other features of methods such as method 600 or method 700 derive directly from the functionality and parameters of these devices, as described in the appended claims and throughout the specification, and therefore will not be repeated here. It should be noted that one or more operations of the method may be performed in different orders.

[0193] An apparatus (e.g., a network node, such as master node 104; a user node or client node, such as UE 102) may be configured to perform or cause to perform any aspect of the methods(s) described herein. Furthermore, a computer program may include instructions for causing the apparatus to perform any aspect of the methods(s) described herein when executed. Additionally, an apparatus may include components for performing any aspect of the methods(s) described herein. According to an example embodiment, the components include at least one processor and at least one memory including program code configured to cause to perform any aspect of the methods(s) when executed by the at least one processor.

[0194] Any ranges or device values ​​given herein may be extended or modified without losing the desired effect. Furthermore, unless expressly prohibited, any embodiment may be combined with another embodiment.

[0195] Although the subject matter has been described in language specific to structural features and / or actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as examples of implementing the claims, and other equivalent features and actions are intended to be within the scope of the claims.

[0196] It should be understood that the above benefits and advantages may relate to one embodiment or several embodiments. The embodiments are not limited to embodiments that solve any or all of the described problems, nor are they limited to embodiments that have any or all of the described benefits and advantages. It should also be understood that references to "an" can refer to one or more of these items.

[0197] The methods described herein can be performed in any suitable order, or simultaneously where appropriate. Furthermore, individual blocks can be deleted from any method without departing from the scope of the subject matter described herein. Aspects of any of the above embodiments can be combined with aspects of any other of the above embodiments to form further embodiments without losing the desired effects.

[0198] The term “comprising” is used herein to mean including the identified method, block or element, but such block or element does not include an exclusive list, and the method or apparatus may include additional blocks or elements.

[0199] As used in this application, the term 'circuit system' may refer to one or more or all of the following: (a) a purely hardware circuit implementation (such as an implementation solely in analog and / or digital circuit systems), and (b) a combination of hardware circuitry and software, such as (if applicable): (i) a combination of (multiple) analog and / or digital hardware circuitry with software / firmware, and (ii) any portion of (multiple) hardware processors (including (multiple) digital signal processors), software, and (multiple) memories having software, which work together to enable a device (such as a mobile phone or a server) to perform various functions; and (c) (multiple) hardware circuitry and / or (multiple) processors, such as (multiple) microprocessors or portions thereof, which require software (e.g., firmware) to operate, but may be absent when the software is not required to operate. This definition of circuit system applies to all uses of the term in this application, including in any claim.

[0200] As another example, as used in this application, the term "circuit system" also encompasses implementations of hardware circuitry or processors (or processors) or a portion thereof and their accompanying software and / or firmware. For instance, if applicable to a particular claim element, the term "circuit system" also encompasses baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0201] It should be understood that the above description is given by way of example only, and various modifications can be made by those skilled in the art. The above specification, examples, and data provide a complete description of the structure and use of exemplary embodiments. Although various embodiments have been described above with a degree of clarity or by referring to one or more individual embodiments, those skilled in the art can make many modifications to the disclosed embodiments without departing from the scope of this specification.

Claims

1. A master node, comprising: At least one processor; as well as At least one memory, including instructions that, when executed by the at least one processor, cause the master node to at least: Send at least one execution condition for adding a Conditional Primary / Secondary Cell Permit (CPA) to a user node, the at least one execution condition being applied by the user node for evaluating subsequent Conditional PScell ​​Addition or Modification of SCPAC conditions for the execution of a CPA to be performed after the Secondary Cell Group (SCG) is released, and wherein the at least one execution condition for the CPA is configured to replace at least one execution condition configured to the user node for evaluating the SCPAC conditions for modifying a Conditional PScell ​​CPC.

2. The master node of claim 1, wherein the at least one execution condition for CPA includes at least one A4 event condition mapped to the primary cell group (MCG) configuration, wherein the at least one A4 event condition is defined for a candidate SCPAC configuration.

3. The master node of claim 2, wherein the at least one execution condition includes configuring a common A4 event condition for all candidate SCPACs.

4. The master node of claim 2, wherein the at least one execution condition includes an A4 event condition specific to each candidate SCPAC configuration.

5. The master node of claim 1, wherein the at least one execution condition includes instructions for maintaining the measurement configuration and SCPAC condition evaluation associated with the released SCG, wherein the instructions instruct the user node, after the SCG is released, to continue the SCPAC condition evaluation using the measurement configuration associated with the released SCG based on at least one of the CPC's A3 event condition or A5 event condition.

6. The master node according to any one of claims 1 to 4, wherein the at least one memory includes instructions that, when executed by the at least one processor, cause the master node to: Send an instruction to deactivate the at least one execution condition; The detection is required for SCG release; as well as A reconfiguration message for the release of the SCG is sent to the user node, the reconfiguration message including an indication to activate the at least one execution condition.

7. The master node according to any one of claims 1 to 5, wherein the at least one execution condition is sent in a Radio Resource Control (RRC) reconfiguration message for the release of the SCG.

8. The master node according to any one of claims 1 to 6, wherein the at least one execution condition is sent in a Radio Resource Control (RRC) reconfiguration message, the RRC reconfiguration message including at least one of an initial conditional PScell ​​change CPC condition configuration or a subsequent CPC condition configuration.

9. The master node according to any one of the preceding claims, wherein the at least one memory further comprises instructions, which, when executed by the at least one processor, cause the master node to: Send an instruction to the user node to suspend the evaluation of at least one execution condition for the released SCG.

10. The master node of claim 9, wherein the instructions sent to the user node include: Instructions for suspending the evaluation of at least one execution condition of the released SCG for a specific period of time starting from the release of the SCG.

11. The master node of claim 9, wherein the instructions sent to the user node include: The evaluation of at least one execution condition for the released SCG is paused until the user node executes at least one instruction added by a conditional PCell.

12. A user node, comprising: At least one processor; as well as At least one memory, including instructions that, when executed by the at least one processor, cause the user node to at least: The user node receives at least one execution condition for adding a Conditional Primary / Secondary Cell Permit (CPA) to a PScell, the at least one execution condition being applied by the user node for evaluating subsequent Conditional PScell ​​additions or changes to SCPAC conditions for the execution of a CPA to be performed after the secondary cell group (SCG) is released, wherein the at least one execution condition for the CPA is configured to replace at least one execution condition configured to the user node for evaluating the SCPAC conditions for changing a CPC to a Conditional PScell.

13. The user node of claim 12, wherein the at least one execution condition for CPA includes at least one A4 event condition mapped to the primary cell group (MCG) configuration, wherein the at least one A4 event condition is defined for a candidate SCPAC configuration.

14. The user of claim 13, wherein the at least one execution condition for CPA includes configuring a common A4 event condition for all candidate SCPACs.

15. The user node of claim 13, wherein the at least one execution condition for CPA includes an A4 event condition specific to each candidate SCPAC configuration.

16. The user node according to any one of claims 12 to 15, wherein the at least one memory includes instructions that, when executed by the at least one processor, cause the user node to: Receive a reconfiguration message for SCG release from the master node; Performing the SCG release includes: Release SCG configuration; Release the measurement configuration of at least one of the initial CPC conditions or subsequent CPC conditions; Release at least one of the CPC conditions or the subsequent CPC conditions; The user node is configured to: Evaluate the SCPAC conditions based on at least one execution condition for CPA; and After the SCG is released, the CPA is performed based on the assessment.

17. The user node of claim 16, wherein the at least one memory includes instructions that, when executed by the at least one processor, cause the user node to: Receive from the master node the at least one execution condition for CPA, and an instruction to deactivate the at least one execution condition for CPA; The at least one execution condition is stored in a deactivated state; as well as Receive from the master node the reconfiguration message for the release of the SCG, and an indication to activate the at least one execution condition for the CPA.

18. The user node of claim 12, wherein the at least one execution condition for CPA includes instructions for maintaining the measurement configuration and SCPAC condition assessment associated with the released SCG, wherein the instructions instruct the user node, after the SCG is released, to continue the SCPAC condition assessment using the measurement configuration associated with the released SCG based on at least one of the A3 event condition or A5 event condition of the CPC.

19. The user node according to any one of claims 12 to 18, wherein the at least one execution condition for CPA is received in a Radio Resource Control (RRC) reconfiguration message, the RRC reconfiguration message including at least one of an initial CPC condition configuration or a subsequent CPC condition configuration.

20. The user node according to any one of claims 12 to 18, wherein the at least one execution condition for CPA is received in an RRC reconfiguration message for the release of the SCG.

21. A user node according to any one of claims 12 to 20, wherein the at least one memory further comprises instructions, which, when executed by the at least one processor, cause the user node to: Receive from the master node an instruction to suspend the evaluation of at least one execution condition for the CPA against the released SCG; and The evaluation of at least one execution condition for the CPA against the released SCG is suspended according to the instruction.

22. The user node of claim 21, wherein the instruction received from the master node comprises: Instructions for suspending the evaluation of at least one execution condition of the CPA for the released SCG for a specific period of time starting from the release of the SCG.

23. The user node of claim 21, wherein the instruction received from the master node comprises: The evaluation of at least one execution condition for CPA against the released SCG is paused until the user node executes at least one conditionally added PCell instruction.

24. The user node according to any one of claims 18 to 23, wherein the at least one memory includes instructions that, when executed by the at least one processor, cause the user node to: Before the initial conditional PScell ​​change has been executed, receive a reconfiguration message for SCG release from the master node; Performing the SCG release includes: Release SCG configuration; The measurement configuration maintains the initial CPC conditions; and Maintain the initial CPC conditions; The user node is configured to: Update the initial CPC conditions for CPA, wherein, for the candidate SCPAC configuration, the initial CPC conditions are evaluated using the released PScell ​​measurement as the service PScell ​​measurement; and When or after the SCG is released, an evaluation of the conditional PScell ​​addition is performed based on the update.

25. The user node according to any one of claims 18 to 23, wherein the at least one memory includes instructions that, when executed by the at least one processor, cause the user node to: After the initial conditional PScell ​​change has been executed, a reconfiguration message for SCG release is received from the master node; Performing the SCG release includes: Maintain SCG configuration; Maintain the measurement configuration for subsequent conditional PScell ​​changes to CPC conditions; Maintain the subsequent CPC conditions; and The user node is configured to: Update the subsequent CPC conditions for CPA, wherein the subsequent CPC conditions are evaluated for the candidate SCPAC configuration using the released PScell ​​measurement as the service PScell ​​measurement; and When or after the SCG is released, an evaluation of the conditional PScell ​​addition is performed based on the update.

26. A method to be executed by a master node, comprising: Send at least one execution condition for adding a Conditional Primary / Secondary Cell Permit (CPA) to a user node, the at least one execution condition being applied by the user node for evaluating subsequent Conditional PScell ​​Addition or Modification of SCPAC conditions for the execution of a CPA to be performed after the Secondary Cell Group (SCG) is released, and wherein the at least one execution condition for the CPA is configured to replace at least one execution condition configured to the user node for evaluating the SCPAC conditions for modifying a Conditional PScell ​​CPC.

27. The method of claim 26, wherein the at least one execution condition for CPA includes at least one A4 event condition mapped to a primary cell group (MCG) configuration, wherein the at least one A4 event condition is defined for a candidate SCPAC configuration.

28. The method of claim 27, wherein the at least one execution condition comprises configuring a common A4 event condition for all candidate SCPACs.

29. The method of claim 27, wherein the at least one execution condition includes an A4 event condition specific to each candidate SCPAC configuration.

30. The method of claim 26, wherein the at least one execution condition includes instructions for maintaining the measurement configuration and SCPAC condition assessment associated with the released SCG, wherein the instructions instruct the user node, after the SCG is released, to continue the SCPAC condition assessment using the measurement configuration associated with the released SCG based on at least one of the CPC's A3 event condition or A5 event condition.

31. The method according to any one of claims 26 to 29, comprising: Send an instruction to deactivate the at least one execution condition; The detection is required for SCG release; as well as A reconfiguration message for the release of the SCG is sent to the user node, the reconfiguration message including an indication to activate the at least one execution condition.

32. The method according to any one of claims 26 to 30, wherein the at least one execution condition is sent in a Radio Resource Control (RRC) reconfiguration message for release of the SCG.

33. The method according to any one of claims 26 to 31, wherein the at least one execution condition is sent in a Radio Resource Control (RRC) reconfiguration message, the RRC reconfiguration message including at least one of an initial conditional PScell ​​change CPC condition configuration or a subsequent CPC condition configuration.

34. The method according to any one of claims 26 to 33, comprising: Send an instruction to the user node to suspend the evaluation of at least one execution condition for the released SCG.

35. The method of claim 34, wherein the instruction sent to the user node comprises: Instructions for suspending the evaluation of at least one execution condition of the released SCG for a specific period of time starting from the release of the SCG.

36. The method of claim 34, wherein the instruction sent to the user node comprises: The evaluation of at least one execution condition for the released SCG is paused until the user node executes at least one instruction added by a conditional PCell.

37. A method to be executed by a user node, comprising: The user node receives at least one execution condition for adding a Conditional Primary / Secondary Cell Permit (CPA) to a PScell, the at least one execution condition being applied by the user node for evaluating subsequent Conditional PScell ​​additions or changes to SCPAC conditions for the execution of a CPA to be performed after the secondary cell group (SCG) is released, wherein the at least one execution condition for the CPA is configured to replace at least one execution condition configured to the user node for evaluating the SCPAC conditions for changing a CPC to a Conditional PScell.

38. The method of claim 37, wherein the at least one execution condition for CPA includes at least one A4 event condition mapped to a primary cell group (MCG) configuration, wherein the at least one A4 event condition is defined for a candidate SCPAC configuration.

39. The method of claim 38, wherein the at least one execution condition for CPA includes configuring a common A4 event condition for all candidate SCPACs.

40. The method of claim 38, wherein the at least one execution condition for CPA includes an A4 event condition specific to each candidate SCPAC configuration.

41. The method according to any one of claims 37 to 40, comprising: Receive a reconfiguration message for SCG release from the master node; Performing the SCG release includes: Release SCG configuration; Release the measurement configuration of at least one of the initial CPC conditions or subsequent CPC conditions; Release at least one of the CPC conditions or the subsequent CPC conditions; Evaluate the SCPAC conditions based on at least one execution condition for CPA; and After the SCG is released, the CPA is performed based on the assessment.

42. The method of claim 41, comprising: Receive from the master node the at least one execution condition for CPA, and an instruction for deactivating the at least one execution condition for CPA for execution of CPA; The at least one execution condition is stored in a deactivated state; as well as The master node receives the reconfiguration message for the release of the SCG, and an indication for activating the execution of the CPA for the at least one execution condition.

43. The method of claim 37, wherein the at least one execution condition for CPA includes instructions for maintaining the measurement configuration and SCPAC condition assessment associated with the released SCG, wherein the instructions instruct the user node, after the SCG is released, to continue the SCPAC condition assessment using the measurement configuration associated with the released SCG based on at least one of the A3 event condition or A5 event condition of the CPC.

44. The method of any one of claims 37 to 43, wherein the at least one execution condition for CPA is received in a Radio Resource Control (RRC) reconfiguration message, the RRC reconfiguration message including at least one of an initial CPC condition configuration or a subsequent CPC condition configuration.

45. The method according to any one of claims 37 to 43, wherein the at least one execution condition for CPA is received in an RRC reconfiguration message for the release of the SCG.

46. ​​The method according to any one of claims 37 to 45, comprising: Receive from the master node an instruction to suspend the evaluation of at least one execution condition for CPA for the released SCG; as well as The evaluation of at least one execution condition for the CPA against the released SCG is suspended according to the instruction.

47. The method of claim 46, wherein the instruction received from the master node comprises: Instructions for suspending the evaluation of at least one execution condition of the CPA for the released SCG for a specific period of time starting from the release of the SCG.

48. The method of claim 46, wherein the instruction received from the master node comprises: The evaluation of at least one execution condition for CPA against the released SCG is paused until the user node executes at least one conditionally added PCell instruction.

49. The method according to any one of claims 43 to 48, comprising: Before the initial conditional PScell ​​change has been executed, receive a reconfiguration message for SCG release from the master node; Performing the SCG release includes: Release SCG configuration; The measurement configuration maintains the initial CPC conditions; and Maintain the initial CPC conditions; Update the initial CPC conditions for CPA, wherein, for the candidate SCPAC configuration, the initial CPC conditions are evaluated using the released PScell ​​measurement as the service PScell ​​measurement; and When or after the SCG is released, an evaluation of the conditional PScell ​​addition is performed based on the update.

50. The method according to any one of claims 37 to 48, comprising: After the initial conditional PScell ​​change has been executed, a reconfiguration message for SCG release is received from the master node; Performing the SCG release includes: Maintain SCG configuration; Maintain the measurement configuration for subsequent conditional PScell ​​changes to CPC conditions; Maintain the subsequent CPC conditions; and Update the subsequent CPC conditions for CPA, wherein the subsequent CPC conditions are evaluated for the candidate SCPAC configuration using the released PScell ​​measurement as the service PScell ​​measurement; and When or after the SCG is released, an evaluation of the conditional PScell ​​addition is performed based on the update.

51. An apparatus comprising at least components for sending to a user node at least one execution condition for adding a Conditional Primary / Secondary Cell (PSC) to a Conditional Primary / Secondary Cell (PSC) cell, the at least one execution condition being applied by the user node for an evaluation of subsequent Conditional PSC cell addition or modification SCPAC conditions for the execution of a CPA to be performed after a Secondary Cell Group (SCG) release, and wherein the at least one execution condition for the CPA is configured to replace at least one execution condition configured to be given to the user node for an evaluation of the SCPAC conditions for modifying a Conditional PSC cell (CPC).

52. An apparatus comprising at least components for receiving from a master node at least one execution condition for adding a Conditional Primary / Secondary Cell (PSC) to a Conditional Primary / Secondary Cell (PSC) cell, the at least one execution condition being applied by the user node for an evaluation of subsequent Conditional PSC cell addition or modification SCPAC conditions for the execution of a CPA to be performed after a Secondary Cell Group (SCG) release, wherein the at least one execution condition for the CPA is configured to replace at least one execution condition configured to the user node for an evaluation of the SCPAC conditions for modifying a Conditional PSC cell (CPC).

53. A computer-readable medium comprising instructions that, when executed by a device, cause the device to perform at least the method according to any one of claims 26 to 36.

54. A computer-readable medium comprising instructions that, when executed by a device, cause the device to perform at least the method according to any one of claims 37 to 50.

Images