Execution conditions for cho with associated pscell / scg

Abstract

A User Equipment (UE) performs an evaluation of a Conditional Handover (CHO) execution condition for a CHO target candidate cell configuration, wherein the evaluation is concurrent with at least another execution condition for one of a candidate PSCell or candidate Secondary Cell Group (SCG) configuration associated with the CHO target candidate cell configuration, wherein the PSCell / SCG execution condition is evaluated based on a measurement configuration which the UE receives The measurement configuration may alternatively be configured as UE's current measurement configuration, or as the measurement configuration within the CHO target candidate cell configuration.

Description

EXECUTION CONDITIONS FOR CHO WITH ASSOCIATED PSCELL / SCG TECHNICAL FIELD The present disclosure relates generally to wireless communication networks, and in particular to systems and methods for combining a Conditional Handover (CHO) configuration with one of an associated candidate PSCell configuration, or candidate Secondary Cell Group (SCG) configuration, with their measurement configurations and execution conditions. RELATED APPLICATIONS This application claims priority to U.S. Provisional Application No.63 / 446135, filed 16 February 2023, the entire disclosure of which is hereby incorporated by reference herein. BACKGROUND Wireless communication networks are ubiquitous in many parts of the world. As technology advances, the technical standards that define the operation of networks, and ensure interoperability of equipment from different vendors, evolve to both expand the networks’ capacity and sophistication, and to address new use cases. The Third Generation Partnership Project (3GPP) is a standards body that defines and promulgates technical standards for the operation of wireless cellular networks. Incremental advances are defined in numbered releases (e.g., Rel.16, Rel.17, etc.), and major advances are referred to as numbered generations. The Fourth Generation (4G), also known as Long Term Evolution (LTE) is widely deployed, and the Fifth Generation (5G) is in development. 5G is intended to serve use cases such as enhanced mobile broadband (eMBB), ultra- reliable and low latency communication (URLLC), NarrowBand Internet of Things (NB-IoT) and massive Machine Type Communications (mMTC).5G includes the New Radio (NR) access stratum interface and the 5G Core Network (5GC). The NR physical and higher layers are reusing parts of the LTE specification, and to that add needed components when motivated by new use cases. Carrier Aggregation Carrier Aggregation (CA) is a technology whereby multiple component carriers (CC) are aggregated, and which jointly carry data to or from a user terminal (referred to herein as User Equipment, or UE). CA combines two or more CC at the physical layer into one logical channel above the Media Access Control (MAC) layer, to enhance the data capacity of a network.3GPP specifications describe CA in terms of multiple “cells.” The Primary cell (PCell) is the cell which a UE discovers and connects to. When the UE is in connected mode with a PCell, one or multiple secondary cells (SCells) can be configured, and can be dynamically activated or deactivated as data transfer requirements dictate. The designation of PCell is UE-centric – that is, different UEs may designated different cells as their PCell. Dual Connectivity One type of CA is Dual Connectivity (DC), wherein a UE is connected to two cells, or more generally, two cell groups. A Master Cell Group (MCG) contains the PCell, and a Secondary Cell Group (SCG) includes SCells, one of which is the Primary cell of the SCG (PSCell). The PCell and PSCell are hence both the primary cells of their respective cell groups, referred to collectively as sPcell. The MCG and SCG may be handled by different base stations, known as eNB in LTE, and gNB in NR. Multi-Radio Dual Connectivity (MR-DC) refers to a class of DC configurations in 5G, in which the cell groups (MCG, SCG) employ different Radio Access Network (RAN) technologies, which may even be of different generations (e.g., 4G LTE and 5G NR). In MR- DC, a Master Node (MN) is the controlling network node (connected to the core network, or CN), and connects to a Secondary Node (SN) for additional data capacity. MR-DC configurations include EN-DC (E-UTRA – NR Dual Connectivity), NR-DC (New Radio Dual Connectivity), NGEN-DC (NG-RAN – E-UTRA Dual Connectivity) and NE-DC (NR – E- UTRA Dual Connectivity). Conditional Handover (CHO) In Rel-16, Conditional Handover (CHO) was standardized. In CHO, the UE is configured with execution conditions and handover target configurations. The UE monitors the execution conditions and when the conditions are fulfilled, the UE applies the configuration of the target cell. The target configuration was prepared in advance, which makes the execution of the handover faster and with lower risk of failures. For example, because the UE independently assesses conditions and executes the handover, communication with the current (source) gNB is not necessary. Hence, when channel conditions rapidly deteriorate, the risk of a dropped UE during handover, due to errors in communication with the source gNB, is eliminated. When the UE executes the CHO or a regular handover, all (other) conditional reconfigurations are released. FIG.1 is a signaling diagram depicting CHO. Conditional PSCell Change (CPC) in 3GPP Rel-16 A solution for Conditional PSCell Change (CPC) procedure was also standardized in Rel-16. Therein a UE operating in Multi-Radio Dual Connectivity (MR-DC) receives in aconditional reconfiguration one or multiple RRC Reconfiguration(s) (e.g. an RRCReconfiguration message) containing an SCG configuration (e.g., a secondaryCellGroup of IE CellGroupConfig) with a reconfigurationWithSync that is stored and associated to an execution condition (e.g. a condition like an A3 / A5 event configuration), so that one of the stored messages is only applied upon the fulfillment of the execution condition, e.g., associated with the serving PSCell, upon which the UE would perform PSCell change (in case it finds a neighbor cell that is better than the current PSCell of the SCG). Only intra-SN CPC without MN involvement is standardized in 3GPP Rel-16, i.e., for cases where the (candidate) target PSCells are located in the current serving SN. Similar to conditional handover, in case a random access was performed for a target PSCell and the UE was configured with CPC, the UE then releases all the conditional reconfigurations that it has stored. CPA and inter-SN CPC in 3GPP Rel-17 In 3GPP Rel-17 solutions for Conditional PSCell Addition (CPA) and inter-SN CPC are being discussed and introduced. The CPA procedure is used for adding a PSCell / SCG to the configuration for a UE that is currently only configured with an MCG, when associated execution conditions are fulfilled. CPA is initiated by the MN by requesting an SCG configuration, which is to be provided as part of a conditional reconfiguration to the UE, from a (candidate) target SN (T-SN), and then sending it in a conditional reconfiguration to the UE together with the associated execution conditions. Inter-SN CPC can be initiated either by the MN or by the source SN (S-SN), where the signaling towards the source SN and the (candidate) target SNs, as well as towards the UE, in both cases is handled by the MN. CHO with secondary node In 3GPP Rel-17, the possibility to configure CHO with a target configuration containing an SCG was introduced. The procedure is depicted in FIG.2, and is described in 3GPP TS 37.340 v 17.3.0, chapter 10.19: 10.19.2 MR-DC with 5GC The Conditional Handover with Secondary Node procedure is used for configuration and execution of CHO with SN. This procedure includes the cases where the SN is kept, changed, or added. If the SN is kept, the UE context at the SN is kept. If the SN is changed, the UE context at the source SN is moved to the target SN.CHO with candidate SCG As shown in chapter 2.2.4, in Rel-17 the configuration of a target candidate cell (e.g., condRRCReconfig of IE OCTET STRING (CONTAINING RRCReconfiguration), within a CHO configuration (e.g., the IE ConditionalReconfiguration, as defined in TS 38.331), may include an SCG configuration, to be applied by the UE when the execution condition for CHO is fulfilled. The network configures a specific PSCell for a target candidate cell configuration and the UE applies the configuration for the PSCell (and possibly associated SCG SCell(s)) when the CHO condition(s) are fulfilled. In Rel-17 there are no execution conditions related to the PSCell. In the Rel-18 work item for mobility enhancements, one objective is to configure CHO with candidate SCG wherein the UE receives, in addition to the CHO execution condition(s) related to the MCG (e.g., CHO candidate cell an offset better than the PCell), execution condition(s) related to the SCG (in addition to the CHO execution condition(s)). The following agreements have been made in RAN2 related to this objective: In RAN2#119: ^ Observation: Current RAN2 Stage-3 specifications can support CHO including target MCG and target SCG in Rel-17. ^ CHO configuration referring to or including CPC / CPA configuration (intended to be applicable together) can be supported. ^ For Future Study (FFS): When triggering CHO, UE perform CPC / CPA configuration to start CPC / CPA evaluation, FFS if CHO evaluation and CPC / CPA evaluation is concurrent or sequential. In RAN2#120: ^ Execution order: the UE doesn’t execute CPC / CPA unless CHO condition is fulfilled (regardless parallel or sequential evaluation) 3GPP has so far agreed on the following for the case the UE is configured with a CHO including a target MCG and candidate SCG(s) for CPC / CPA in NR-DC in RAN2#119-e: ^ CHO configuration referring to or including CPC / CPA configuration (intended to be applicable together) can be supported. ^ FFS: When triggering CHO, UE perform CPC / CPA configuration to start CPC / CPA evaluation, FFS if CHO evaluation and CPC / CPA evaluation is concurrent or sequential. As shown above, 3GPP is discussing whether the evaluation of the execution conditions for CHO and CPC performed by the UE is concurrent (e.g. performed in parallel) or sequential, in the case where a CHO configuration for a target candidate (to be applied during CHO execution) contains or is associated to the configuration of a candidate SCG.The execution conditions for CHO and / or CPC (or CPA) are independently configured in the form of one or more measurement identifiers (in the form of one or more MeasId(s)), pointing to the UE’s current measurement configuration, stored in the UE variable VarMeasconfig, associated to the UE’s current MCG and / or to the UE’s current SCG. However, it is not clear how the execution conditions for CHO target candidate and a candidate SCG associated to it are configured in the case the SCG execution depends on the CHO target candidate execution. In addition, at the network side, it is also not clear which nodes determine the execution conditions and / or the measurement configuration(s) associated to candidate SCG associated to a target candidate CHO configuration. And, consequently, it is not clear how that is signaled to the UE. SUMMARY According to aspects of the present disclosure described and claimed herein, a User Equipment (UE) performing an evaluation of an execution condition (CHO execution condition) for a CHO target candidate cell configuration, wherein the evaluation is concurrent (or in parallel) with at least another execution condition (CPC / CPA execution condition) for at least one candidate SCG candidate configuration associated with the CHO target candidate cell configuration, wherein the CPC / CPA execution condition is evaluated based on a measurement configuration (measConfig or IE MeasConfig, or nested IE(s) / fields / parameters with the IE MeasConfig) which the UE receives, wherein: Option a) the measurement configuration is configured as a UE’s current measurement configuration (denoted S-MN MeasConfig); or; Option b) the measurement configuration is configured as the measurement configuration within the CHO target candidate cell configuration (denoted candidate T-MN MeasConfig, or simply T-MN MeasConfig). In other words, there are two options a) and b) for defining a measurement configuration (e.g., including a MeasIdToAdd with the association between measId(s) and reporting configuration and measurement object configuration) in which the CPC / CPA execution conditions are configured, and how the UE can determine the MeasConfig which the measId refers to and how the UE can find the correct cells for performing measurements and for evaluation of the CPC / CPA execution conditions based on these measurements. One aspect relates to a method executed by a User equipment (UE), the method comprising:- Receiving a message (e.g. RRC Reconfiguration) including a CHO configuration, wherein the CHO configuration includes at least i) a CHO target candidate cell configuration (e.g., embedded RRCReconfiguration) and ii) a CHO execution condition associated to the CHO target candidate cell configuration, - wherein the CHO target candidate cell configuration is associated with a candidate SCG configuration (referred here as a CPC or CPA configuration), wherein the CPC / CPA configuration includes: i) a CPC / CPA target candidate configuration (e.g., candidate SCG configuration) and ii) an associated CPC / CPA execution condition (one or more measId(s) associated to the CPC / CPA target candidate configuration) - Evaluating whether the CHO execution condition is fulfilled and evaluating whether the CPC / CPA execution condition is fulfilled, - wherein the CPC / CPA execution condition comprises at least one measurement identity associated with (or referring to): o option a) an MCG measurement configuration (MCG MeasConfig, S-MN MeasConfig) in the UE’s current configuration (i.e. the configuration the UE operates with the S-MN, in the MCG VarMeasConfig); or o option b) one MCG measurement configuration within the CHO target candidate cell configuration (MCG MeasConfig of the candidate T-MN, candidate T-MN MeasConfig). - Applying the CHO target candidate cell configuration at least when the CHO execution condition is fulfilled and; - when the CPC / CPA execution condition is fulfilled, applying the candidate SCG configuration associated with the CHO target candidate cell configuration. The UE evaluating whether the CHO execution condition is fulfilled and evaluating whether the CPC / CPA execution condition is fulfilled further comprises the UE determining one or more measurements (e.g., measId(s) and associated configurations such as reporting configuration(s) and measurement object(s)) to be performed and to be used as input to the evaluation of the CPC / CPA execution condition(s) concurrent with the CHO execution condition(s). The UE evaluating whether the CHO execution condition is fulfilled and evaluating whether the CPC / CPA execution condition is fulfilled further comprises the UE determining one or more applicable cells to be considered as input to the CPC / CPA evaluation conditions (e.g. candidate PSCell(s) based on the CHO configuration. For example, an applicable PSCell is a PSCell whose cell identifier (physical cell identity – PCI) is configured in the serving cellcommon configuration (IE ServingCellConfigCommon) of the candidate SCG configuration for the SpCell configuration. In one dependent aspect, the CHO target candidate cell configuration is associated with a candidate SCG configuration (referred here as a CPC or CPA configuration) by one or more of: i) The candidate SCG configuration is a CPC or CPA configuration within the CHO target candidate cell configuration; ii) The candidate SCG configuration is a CPC or CPA configuration which contains a CHO configuration identifier matching the CHO configuration identifier of the associated CHO target candidate configuration. Notice that thanks to the CHO identifier within the CPC configuration the UE determines that this is a CPC configuration which depends on the CHO configuration. In one dependent aspect, the UE performs one or more measurements based on the CPC / CPA measurement configuration associated to the CPC / CPA execution condition but only starts the evaluation of the execution condition(s) associated to these measId(s) when the associated CHO execution condition is fulfilled. Thanks to that the UE does not need to evaluate the associated CPC / CPA execution until the CHO execution condition is fulfilled. In one dependent aspect of option a), the CHO execution condition comprises two measId(s), wherein the first measId is associated to the CHO execution condition (i.e., a measurement associated to an associated candidate PCell) and the second measId is associated to the CPC / CPA execution condition (i.e., a measurement associated to an associated candidate PSCell). In that case, the UE is aware that the combined execution condition for CHO and CPC is to be evaluated. In this case, the measurement object associated to the first measId is a measurement object associated to a first frequency, while the measurement object associated to the second measId is a measurement object associated to a second frequency (for the PSCell candidate). Aspects of the disclosure also comprise the corresponding network procedures. For option a) aspects of the disclosure comprise a method for a network node operating as a source Master Node (S-MN) serving a PCell the UE is connected to, and serving the UE, wherein the S-MN requests a candidate T-MN to configure CHO (e.g., by transmitting a Handover Request message for CHO over Xn interface) and in response receives a CHO target candidate cell configuration (e.g., in a Handover Request Ack message over Xn interface), an associated candidate SCG configuration (e.g., RRCReconfiguration message including an SCG configuration and an associated CPC / CPA execution conditions in the form or one or more measurement identifier(s)) and an associated CPC / CPA measurement configuration (configuring the measurements for the CPC / CPA execution condition(s)). Upon reception, the S-MN merges (or combines in a single message / IE or field) the associated CPC / CPA measurementconfiguration (configuring the measurements for the CPC / CPA execution condition(s)), denoted an MCG MeasConfig of a target candidate T-MN into the UE’s current MCG MeasConfig of the S-MN. The denoted MCG MeasConfig of the target candidate T-MN may correspond to information included in an IE in the inter-node message over Xn (e.g., to be translated by the S- MN into fields and IE(s) to be included in an RRC MeasConfig) or in the form of an RRC container to be included by the S-MN in an RRC message to the UE (e.g., in the form of a MeasConfig IE, MeasIdToAddModList, etc.). Still for option a), aspects of the disclosure also comprise a method for a network node operating as a target candidate Master Node (T-MN) comprising the T-MN receiving a request from the S-MN to configure a CHO target candidate cell (e.g., by receiving a Handover Request message for CHO over Xn interface) and in response, transmitting to the S-MN a CHO target candidate cell configuration (e.g., in a Handover Request Ack message over Xn interface), an associated candidate SCG configuration (e.g., RRCReconfiguration message including an SCG configuration and possibly an associated CPC / CPA execution conditions (in the form of one or more measurement identifier(s)) and an associated CPC / CPA measurement configuration (configuring the measurements for the CPC / CPA execution condition(s)). In one alternative, the T-MN does not include measurement identities for the associated CPC / CPA measurements / execution conditions and these are instead set by the S-MN. In this alternative, the T-MN provides information related to the measurements, such as information related to IEs MeasObjectToAddMod, ReportConfigToAddMod and / or ReportConfigNR. The T-MN then generates the measurement configuration, including setting the related identities, such as e.g. MeasId, MeasObjectId and / or ReportConfigId. For option b) aspects of the disclosure comprise a method for a network node operating as a target candidate Master Node (T-MN) comprising the T-MN receiving a request from the S- MN to configure a CHO target candidate cell (e.g., by receiving a Handover Request message for CHO over Xn interface) and in response, transmitting to the S-MN a CHO target candidate cell configuration (e.g., in a Handover Request Ack message over Xn interface), an associated candidate SCG configuration (e.g., RRCReconfiguration message including an SCG configuration and an associated CPC / CPA execution conditions in the form of one or more measurement identifier(s)) and, as part of the CHO target candidate configuration, its CPC / CPA measurement configuration (configuring the measurements for the CPC / CPA execution condition(s)). One aspect relates to a method, performed by a UE operative in a wireless communication network, for performing CHO with one of an associated candidate PSCell or candidate SCG. A message including a CHO configuration including at least a CHO target candidate cellconfiguration and associated CHO execution condition is received from a network node. The CHO target candidate cell configuration is associated with a target candidate PSCell or target candidate SCG configuration including a PSCell or SCG target candidate configuration and associated PSCell or SCG execution condition. The PSCell or SCG execution condition comprises at least one measurement identity associated with an MCG measurement configuration in the UE’s current configuration. Whether the CHO execution condition is fulfilled is evaluated. Whether the PSCell or SCG execution condition is fulfilled is evaluated. The CHO target candidate cell configuration is applied in response to the CHO execution condition being fulfilled. The target candidate PSCell or target candidate SCG configuration associated with the CHO target candidate cell configuration is applied in response to the PSCell or SCG execution condition being fulfilled. Another aspect relates to a UE operative in a wireless communication network. The UE includes communication circuitry configured to wirelessly communicate with one or more network nodes and processing circuitry operatively connected to the communication circuitry. The processing circuitry is configured to receive, from a network node, a message including a CHO configuration including at least a CHO target candidate cell configuration and associated CHO execution condition, wherein the CHO target candidate cell configuration is associated with a target candidate PSCell or target candidate SCG configuration including a PSCell or SCG target candidate configuration and associated PSCell or SCG execution condition, the PSCell or SCG execution condition comprising at least one measurement identity associated with an MCG measurement configuration in the UE’s current configuration; evaluate whether the CHO execution condition is fulfilled; evaluate whether the CPC or CPA execution condition is fulfilled; in response to the CHO execution condition being fulfilled, apply the CHO target candidate cell configuration; and in response to the PSCell or SCG execution condition being fulfilled, apply the target candidate PSCell or target candidate SCG configuration associated with the CHO target candidate cell configuration. Yet another aspect relates to a method executed by a network node operative in a wireless communication network. The network node is configured and acts as an S-MN for a UE. The method is one of performing CHO of the UE with one of an associated candidate PSCell or candidate SCG. It is determined to configure CHO for the UE towards a candidate T MN. A message containing a request for CHO is transmitted to the candidate T-MN. A message is received from the candidate T-MN containing a target configuration for a CHO candidate cell and an associated configuration for a candidate PSCell or candidate SCG and one or more parameters related to a PSCell or SCG execution condition. A reconfiguration messagecontaining the configuration of CHO and associated PSCell or SCG configuration is transmitted to the UE. A reply is received from the UE. Still another aspect relates to a network node operative in a wireless communication network and acting as a S-MN for a UE. The method is for performing CHO, of the UE with one of an candidate PSCell or candidate SCG. The network node includes communication circuitry configured to wirelessly communicate with one or more UEs and processing circuitry operatively connected to the communication circuitry. The processing circuitry is configured to determine to configure CHO for the UE towards a candidate T MN; transmit a message containing a request for CHO to the candidate T-MN; receive a message from the candidate T- MN containing a target configuration for a CHO candidate cell and an associated configuration for a candidate PSCell or candidate SCG and one or more parameters related to a PSCell or SCG execution condition; transmit, to the UE, a reconfiguration message containing the configuration of CHO and associated PSCell or SCG configuration; and receive a reply from the UE. Still another aspect relates to a method, performed by a network node operative in a wireless communication network and acting as a candidate T-MN for a UE, for performing CHO of the UE with one of an associated candidate PSCell or candidate SCG. A message containing a request for CHO with associated configuration of PSCell or SCG is received from a S-MN. It is determined to accept CHO configuration with associated PSCell or SCG configuration. A target CHO configuration is prepared. A configuration of PSCell or SCG is triggered. In response to a candidate target PSCell belonging to a different T-SN, a message containing a request to configure PSCell or SCG is transmitted to the T-SN. In response to sending the message to the T-SN, a reply containing a target PSCell or SCG configuration is received from the T-SN. Executions conditions for the PSCell or SCG are prepared. A message containing the target configuration for CHO and a PSCell or SCG configuration comprising execution conditions and a target PSCell or SCG configuration is transmitted to the S-MN. Still another aspect relates to a network node operative in a wireless communication network and acting as a candidate T-MN for a UE. The method is for performing CHO of the UE with one of an associated candidate PSCell or candidate SCG. The network node includes communication circuitry configured to wirelessly communicate with one or more UEs and processing circuitry operatively connected to the communication circuitry. The processing circuitry is configured to receive a message from a S-MN, the message containing a request for CHO with associated configuration of PSCell or SCG; determine to accept CHO configuration with associated PSCell or SCG configuration; prepare a target CHO configuration; trigger a configuration of PSCell or SCG; in response to a candidate target PSCell belonging to a different T-SN, transmit a message to the T-SN containing a request to configure PSCell or SCG; inresponse to sending the message to the T-SN, receive a reply from the T-SN containing a target PSCell or SCG configuration; prepare executions conditions for the PSCell or SCG; and transmit a message to the S-MN containing the target configuration for CHO and a PSCell or SCG configuration comprising execution conditions and a target PSCell or SCG configuration. BRIEF DESCRIPTION OF THE DRAWINGS FIG.1 is a known wireless communication network signaling diagram for CHO. FIG.2 is a known wireless communication network signaling diagram for CHO with a target configuration containing an SCG. FIG.3 is a diagram showing CPC configuration(s) within a CHO configuration in an RRC Reconfiguration message. FIG.4 is a diagram showing a CHO Reconfiguration and CPC configuration in an RRC Reconfiguration message. FIG.5 is a wireless communication network signaling diagram for CHO wherein execution conditions for CPC / CPA and the CPC / CPA related measurement configuration for these execution conditions are included in an RRC container sent from the candidate T-MN to S-MN. FIG.6 is a diagram showing different measConfig fields / IEs, one for UE’s CHO related measurements and one for CPC related measurements, in an RRC Reconfiguration message. FIG.7 is a diagram showing a CHO Reconfiguration and CPC configuration in an RRC Reconfiguration message. FIG.8 is a flow diagram of a method, by a UE, of performing CHO with one of an associated PSCell or SCG. FIG.9 is a flow diagram of a method, by a network node acting as a S-MN for a UE, of performing CHO for the UE with one of an associated PSCell or SCG. FIG.10 is a flow diagram of a method, by a network node acting as a T-MN for a UE, of performing CHO for the UE with one of an associated PSCell or SCG. FIG.11 is a block diagram of a wireless communication network. FIG.12 is a hardware block diagram of a wireless device. FIG.13 is a hardware block diagram of a network node. FIG.14 is a block diagram of a host device. FIG.15 is a diagram showing OTT data transfer between a host device and a UE in a wireless network. DETAILED DESCRIPTIONAspects of the disclosure herein describe different solutions for how to configure UE to evaluate the fulfillment of CHO execution condition(s) (one or more measId(s) and associated measurement configuration for these measId(s)) and CPC execution condition(s) (one or more measId(s) and associated measurement configuration for these measId(s)), wherein the CPC configuration (or the candidate SCG configuration) is associated with (dependent) of the CHO target candidate configuration in the CHO configuration, e.g., a CPC configuration is included within the CHO target candidate cell configuration, or it is associated with (e.g., by the SCG candidate configuration being associated to a CHO configuration identifier) so that the fulfillment of CHO condition may lead to a CHO followed by or together with a CPC execution. Aspects of the disclosure provide solutions for how the UE obtains the configuration(s) for the execution conditions for CHO with candidate SCG (and associated measurement configuration(s)), wherein the UE evaluates the execution conditions for both CHO and CPC (or CPA) in parallel (e.g., while connected to the source PCell, before the CHO execution) and selects the candidate PSCell based on execution condition(s) for CPC (or CPA) being fulfilled when the CHO condition(s) have been fulfilled for a PCell. There are sets of aspects for the UE, for a candidate T-MN (which configures CHO with an associated candidate SCG or CPC (e.g., CHO target candidate configuration including a CPC configuration), and for the S-MN (which receives information from the T-MN) and provides the CHO configuration (with associated CPC / CPA and CPC / CPA measurement configuration(s) for the CPC / CPA execution conditions) to the UE. In aspects of the disclosure described herein, the candidate T-SN may be the same network node as the S-SN or a different node. This is the case when the PCell changes, but the PSCell remains the same. In aspects of the disclosure the UE receives an RRC reconfiguration message (e.g., RRCReconfiguration) from the S-MN which includes a CHO configuration (e.g., in the IE ConditionalReconfiguration), comprising a CHO target candidate cell configuration (e.g., an RRCReconfiguration(CHO candidate), like in condRRCReconfig of IE OCTET STRING (CONTAINING RRCReconfiguration), including an MCG configuration to be applied upon fulfillment of an associated CHO execution condition, like in condExecutionCond of IE SEQUENCE (SIZE (1..2)) OF MeasId), wherein the CHO target candidate cell configuration is associated to a CPC or CPA configuration, wherein the CPC or CPA configuration includes i) a CPC / CPA target candidate cell configuration (e.g. denoted an RRCReconfiguration**) and a CPC / CPA execution condition (e.g. one or more measurement identities referred in a CPC related measurement configuration).Aspects of the disclosure define at least two ways to define this association between a CHO target candidate cell configuration and the CPC / CPA configuration: i) In a first option, the RRC Reconfiguration message the UE receives from the S-MN includes the CHO target candidate cell configuration (RRCReconfiguration(CHO candidate)), wherein the RRCReconfiguration(CHO candidate) includes a CPC / CPA configuration (e.g., in the MCG configuration of the RRCReconfiguration(CHO candidate)), i.e., the RRCReconfiguration(CHO candidate) includes the field of IE ConditionalReconfiguration including one or more SCG candidate cell configuration(s) associated to that CHO target candidate cell. The general idea of the signaling for the association is shown in FIG.3. ii) In a second option, the RRC Reconfiguration message the UE receives from the S-MN includes the CHO target candidate cell configuration (RRCReconfiguration(CHO candidate) associated to a CHO configuration identifier, e.g., conditional reconfiguration ID=x) and a CPC configuration including the CHO configuration identifier (e.g., conditional reconfiguration ID=x) to indicate that the CPC configuration is dependent or associated to that CHO target candidate cell configuration, or in other words, the candidate SCG configuration is a CPC or CPA configuration which contains a CHO configuration identifier matching the CHO configuration identifier of the associated CHO target candidate configuration. An example of this option is shown in FIG.4. The UE receives the RRC Reconfiguration from the S-MN including the CHO configuration including for a target candidate cell a CHO execution condition (one or more measId(s) associated to the UE’s current MCG MeasConfig, possibly included in the same RRC Reconfiguration message), a CHO target candidate cell configuration (e.g., RRCReconfigurartion*), and a conditional reconfiguration identifier (Id = y). Then, the UE also receives a CPC configuration for a given SCG candidate including: a CPC execution condition(s) (one or more measId(s) associated to the UE’s current MCG MeasConfig, in the case of the denoted option a), or one or more measId(s) associated to the T-MN’s MCG MeasConfig, in the case of the denoted option b), and the CHO’s conditional reconfiguration identifier (Id = y) matching the Id for the associated CHO target candidate cell. Configuration of execution conditions for CHO with candidate SCG configurations. In a first solution (option a), from a network perspective, the S-MN generates a single IE MeasConfig included in the RRC Reconfiguration message which is transmitted to the UE and is applied by the UE. That single MeasConfig is denoted an S-MN MeasConfig and include the CPC / CPA related measurement configuration, i.e., the measurement configuration configuring the one or more measId(s) per SCG candidate configuration (configured as CPC / CPA execution conditions) associated to the CHO target candidate cell configuration. The measurement configuration for the one or more measId(s) per SCG candidate configuration associated to theCHO target candidate cell configuration comprises at least an association between measId, a reporting configuration and a measurement object configuration, e.g., the IE MeasIdToAddMod including a measId value which matches the measId referred in a CPC execution condition, a reportConfigId, and a measObjectId, referring to a ReportConfigNR IE with matching reportConfigId, and to a MeasObjectNR IE with matching measObjectId, wherein the ReportConfigNR IE and the MeasObjectNR IE may also be part of the CPC / CPA related measurement configuration. In one option, the CPC / CPA related measurement configuration is part of the MCG measurement configuration(s), which upon reception the UE stores in a UE variable for the MCG configuration, e.g., MCG VarMeasConfig. There may be different ways the S-MN generates the single IE MeasConfig, denoted S-MN MeasConfig. In one alternative, the S-MN merges (and / or combines / includes in a single message and / or IE and / or measurement configuration to be provided to the UE) its own measurement configuration (from the S-MN, e.g., for CHO execution conditions and / or measurement reports) and a CPC / CPA related measurement configuration (or information related to a CPC / CPA related measurement configuration enabling the S-MN to generate an IE MeasConfig) received from the CHO candidate T-MN (during CHO configuration) into the single measurement configuration (denoted by the field measConfig and / or IE MeasConfig as the UE applies and perform measurements accordingly when receives the configuration) to be transmitted to the UE and to be applied by the UE at the moment of the configuration, wherein that measConfig to be transmitted to the UE includes the configuration of CPC related measurement(s) (as provided by the candidate T-MN or based on the information provided by the candidate T-MN) to be performed by the UE while the UE is connected to the S-MN and while the UE is also evaluating CHO execution conditions for a CHO target candidate cell associated to the CPC configuration, e.g., by the CHO target candidate cell includes the CPC configuration. In other words, the S-MN merges (or combines in a single message / IE or field) the associated CPC / CPA measurement configuration (configuring the measurements for the CPC / CPA execution condition(s) for the candidate SCG associated to the CHO target candidate cell), denoted an MCG MeasConfig of a target candidate T-MN for CPC / CPA into the UE’s current MCG MeasConfig of the S-MN. The denoted MCG MeasConfig of the target candidate T-MN for CPC / CPA may correspond to information included in an IE in the inter-node message over Xn (e.g., to be translated by the S- MN into fields and IE(s) to be included in an RRC MeasConfig) or in the form of an RRC container to be directly included by the S-MN in an RRC message to the UE (e.g., in the form of a MeasConfig IE, MeasIdToAddModList, etc.), wherein the container may be possibly transparent to the S-MN.Notice that the candidate T-MN may need to ensure that when CPC / CPA related measurements are configured, these would not exceed the UE capabilities (which is possibly by the fact that the candidate T-MN is aware of the UE capabilities and the UE’s current measurement configuration, provided in the Handover Request for CHO from the S-MN). This would prevent the S-MN to reject the configuration, but as the S-MN is supposed to generate the single MeasConfig to be transmitted to the UE, the S-MN can make sure the UE capabilities are not exceeded by the CPC / CPA related measurement configuration from the candidate T-MN. From the UE perspective, one example could be the UE receiving in an RRCReconfiguration from the S-MN an MCG MeasConfig (to add / or modify the one of UE’s current configurations) which includes at least one MeasIdToAddMod IE including a measId (measId=X), reportConfigId and MeasObjectId, wherein that measId (meaId=X) is referred as a CPC execution condition associated to an SCG candidate which is associated with (or within) a CHO target configuration the UE also receives in the RRCReconfiguration message from the S- MN. Thus, the UE receives in an RRCReconfiguration a CHO configuration including a CHO target candidate configuration which includes an associated CPC / CPA configuration within the CHO target candidate cell configuration. The UE determines the CPC / CPA related measurement configuring for evaluating CPC / CPA execution conditions based on the UE’s current MCG MeasConfig (configured in the UE variable MCG VarMeasConfig) thanks to the fact that the S- MN has merged the CPC / CPA related measurement configuration from the Candidate T-MN with the UE’s current measurement configuration, which the UE stores in the UE variable MCG VarMeasConfig. In one variant, execution conditions for CPC / CPA and the CPC / CPA related measurement configuration for these execution conditions may be included in an RRC container sent from the candidate T-MN to S-MN, e.g., one or more IE(s) which may not be interpreted by the S-MN. The S-MN includes the RRC container (which may comprise one or more field / parameters and IEs) containing the execution conditions for CPC / CPA and the related CPC / CPA measurement configuration. In this variant, special focus on UE capabilities is needed for the candidate T-MN to ensure that the UE capabilities are not exceeded by the CPC / CPA measurement configuration provided from the T-MN to the S-MN. To make this possible, the candidate T-MN receives the UE capabilities and the UE’s current measurement configuration in the Handover Request for CHO from the S-MN. FIG.5 shows an example of how some of these steps may be performed by the UE, the node operating as a Source Master Node (S-MN), a node operating as a candidate Target MN (T- MN), and a candidate Target SN (T-SN). A network node in this context may comprise at least a gNodeB or a 6G radio Access network node.Step 1. The S-MN determines to configure CHO and transmits a Handover Request message for CHO (over XnAP interface, including the UE’s current configuration and UE capabilities, e.g., UIE’s current measurement configuration S-MN measConfig) to a candidate T- MN. Step 2. The candidate T-MN receives the Handover Request for CHO and determines to configure a candidate SCG associated to a CHO target candidate configuration. The T-MN transmits an SN Addition request to a candidate T-SN (e.g., for CPA if the UE is not configured with MR-DC, or for CPC if the UE is configured with MR-DC). The T-MN receives from the candidate T-SN an SN Addition Request Ack message including the candidate SCG configuration(s), e.g., RRCRec(a)** for a PSCell candidate A, and RRCRec(b)** for a PSCell candidate B. In one option, upon determining to configure a candidate SCG associated to a CHO target candidate, the T-MN triggers a MN-initiated CPC or CPA. In one option, the S-MN includes the S-Mn measConfig to be, i.e., the configuration with which the S-MN intends to configure the UE, but it’s not necessarily configured yet. Step 3. The candidate T-MN receives the SN Addition Request Ack, and determines per SCG candidate (e.g., for candidate PSCell A) a CPC / CPA execution condition (one or more measId(s)) and a measurement configuration for configuring the measurements for the related CPC / CPA execution condition. The candidate T-MN may propose updates to the S-MN MeasConfig (UE’s current measurement configuration). Step 4. The candidate T-MN transmits to the S-MN in the Handover Request Ack for CHO the CHO target candidate cell configuration, the associated SCG candidate configuration, e.g., an RRCReconfiguration*(a) including the associated RRCReconfiguration**(a) for PSCell A, the associated CPC / CPA execution conditions and the associated CPC / CPA related measurement configuration. There could be at least two variants for the T-MN to provide the and the associated CPC / CPA related measurement configuration, as briefly mentioned above. In one variant, the associated CPC / CPA related measurement configuration is provided as an RRC container, possibly in the form of an inter-node RRC message / IE and / or field, which may possibly be transparent to the S-MN. Based on that, the S-MN simply includes the RRC container or parts of the RRC containers in the RRC Reconfiguration the UE receives and applies during the configuration of CHO. In another variant, the associated CPC / CPA related measurement configuration is provided as information in the XnAP message, as one or more XnAP IE(s) / parameters, not in RRC format. Thus, upon reception the S-MN generates the MeasConfig to be provided to the UE based on the information from the T-MN.Step 5. The S-MN generates a message, e.g. RRCReconfiguration, comprising the conditionalReconfiguration containing the configuration of CHO with associated CPC / CPA comprising the execution conditions and the message to be applied when the conditions are fulfilled, and transmits the message to the UE. Step 6. The UE applies the message received and starts evaluating the execution conditions for CHO and for the associated CPC / CPA. Step 7. When the execution conditions are fulfilled, the UE applies the target PCell configuration and the target PSCell configuration and sends a message, e.g., RRCReconfigurationComplete containing an SCG RRCReconfigurationComplete to the network to indicate that it has applied the target configuration(s). In the following, some of the steps described above are further detailed, wherein the focus is split for each network node (S-MN, T-MN, and UE) which performs relevant actions. In some aspects of the disclosure, a method is executed by a node acting as source Master Node (S-MN) for a User Equipment (UE) connected to the S-MN, the method comprises: Determining to configure CHO for a UE towards a target candidate Master Node (T-MN), wherein the candidate T-MN may determine to configure at least one candidate CHO target candidate cell including an associated CPA candidate cell (for a UE not in MR-DC) or CPC candidate cell (for a UE in MR-DC) candidates for a UE. In one option, the S-MN is aware that the UE is capable of being configured with CHO + CPA and / or CHO + CPC, meaning that the UE would be able to be configured with a CHO candidate cell whose RRC reconfiguration includes a CPA and / or CPC configuration within. The S-MN may be aware that, thanks to a UE capability IE and / or field and / or parameter, the UE reports to the S-MN, e.g., during an IDLE to CONNECTED transition in the S-MN. In another option, it is actually the S-MN that decides to configure CHO + CPC or CPA, e.g., based on a UE capability reported by the UE. In other words, the S-MN may indicate to the candidate T-MN that it wants to configure CHO including a candidate SCG configuration and a CPC / CPA execution condition. In another option, the T-MN includes within a CHO target candidate configuration, a CPC configuration (IE ConditionalReconfiguration including at least one candidate SCG configuration and an associated execution condition), and provides the resulting CHO target candidate configuration to the S-MN. Transmitting a message, e.g., HANDOVER REQUEST, to the target candidate Master Node (T-MN), the message containing a request for CHO (e.g., the message including an indication that the request is for CHO or conditional reconfiguration, such as a cause value).In one option, in response, the candidate T-MN may determine to configure at least one candidate CHO target candidate cell including / with an associated CPA candidate cell (for a UE not in MR-DC). In one option, in response, the candidate T-MN may determine to configure at least one candidate CHO target candidate cell including / with an associated CPC candidate cell (for a UE which is in MR-DC, i.e., it has already a configured SCG while connected to the S-MN). Note: Associated CPC / CPA configuration means that for a certain CHO target candidate PCell, there is related CPC or CPA configuration(s) of PSCell(s) for the specific CHO PCell. In one option, the current UE configuration may be included in the message, e.g., current MCG configuration and possibly the current SCG configuration if the UE is in MR-DC. In one option, the current UE configuration according to the S-SN, in case the UE is in Dual Connectivity, may be included in the message, e.g., the S-SN measurement configuration, also stored by the UE in the SCG VarMeasConfig. This may be relevant for the candidate T-MN in case it needs to determine which CPC execution conditions to configure (as some measurement identifiers may already be used in the UE’s current measurement configuration by the S-MN or S-SN), and which CPC / CPA related measurement configuration to configure, without exceeding UE capabilities. In one option, the message may contain the maximum number of CPC / CPA configurations that the target may prepare. In one option, the current S-MN measConfig is included in the message. In one option, the S-MN measConfig is the current UE’s measurement configuration, as in the UE variable VarMeasConfig as defined in TS 38.331 (as received from the S-MN by the UE), e.g., a measConfig, associated with MCG. In one option, the S-MN measConfig includes one or more measurement configuration(s) (e.g. MeasId(s) instances, reportConfigNR(s) instances, MeasObjectNR(s) instances, measIdToAddModList instances, MeasIdToAddMod instances) associated to an execution condition for a conditional reconfiguration, e.g., CHO. For example, that S-MN measConfig may include a MeasIdToAddMod instance, a measId of which is associated to a reportConfig whose reportType is set to ‘condTriggerConfig’ (e.g., a measurement identity which configures a measurement associated to an execution condition for CHO) and a measurement object. In one option, the message from the S-MN (e.g., HANDOVER REQUEST for CHO) includes a UE capability information (previously reported by the UE and / or obtained from a Core Network node or function (e.g., AMF in the 5GC) indicating to the candidate T-MN one or more of the following:^ that the UE is capable of being configured with an SCG candidate within a CHO configuration; and / or ^ that the UE is capable of being configured with CHO + CPC; and / or ^ that the UE is capable of being configured with CHO + CPA; and / or ^ that the UE is capable of being configured with CHO + CPC or CPA; ^ that the UE is capable of performing the evaluation of execution conditions associated to a CHO candidate cell and at least one associated CPC / CPA target candidate cell, wherein that is performed by the UE while the UE is connected to the S-MN. ^ that the UE is capable of performing the measurements associated with the execution conditions associated to a CHO candidate cell and at least one associated CPC / CPA target candidate cell, wherein that is performed by the UE while the UE is connected to the S-MN. In one option, the S-MN transmits requests to multiple T-MN(s). This may be done in parallel or sequentially. In one option, the S-MN waits for reply from one T-MN before requesting other T-MN(s). Receiving a message, HANDOVER REQUEST ACKNOWLEDGE, from the (candidate) T-MN, the message containing the target configuration for a CHO candidate cell and the associated SCG candidate configuration (e.g., including the configuration of target candidate PSCell(s) (CPC or CPA configurations)), for the CHO target candidate PCell. The CPC or CPA configurations comprise execution conditions and the target configuration for CPC / CPA, including the configuration of measId and measConfig. In one option, the measConfig is referring to the T-MN measConfig. In one option, the measConfig is referring to the S-MN measConfig. The T-MN may have used the S-MN measConfig received from the S-MN, e.g., in HANDOVER REQUEST, to define execution conditions(s) for CPC / CPA. In one option, the message may contain a proposed update of the S-MN measConfig, i.e., the T-MN may propose certain configuration of measConfig to the S-MN, for the execution condition(s) of CPC / CPA. The T-MN may or may not have used a received S-MN measConfig as input to the proposed measConfig. In one example, the proposed configuration consists of configuration that is part of ReportConfigNR and / or MeasObjectNR. In one option, in case of CPC, the measConfig is referring to the S-SN measConfig. This is an additional option in addition to the two main options a and b described in detail. The S-SN may be requested / invited to provide execution conditions, i.e., measId’s referring to the S-SN measConfig, for the CPC conditional reconfiguration. For this option, additional information may be sent to the S-MN, e.g. the T-SN measConfig may be transmitted in a message overXnAP, NGAP, F1, E1 message or in RRC inter-node message e.g. CG-CandidateList, CG- Config or CG-ConfigInfo. In one option, the HANDOVER REQUEST ACKNOWLEDGE, from the (candidate) T- MN, contains at least one CHO target configuration (e.g., RRCReconfiguration(MCG candidate) message) to be provided to the UE by the S-MN, wherein that CHO target configuration contains a CPC configuration. The CHO target configuration may be denoted by a RRCReconfiguration(MCG candidate) message and the CPC configuration may be denoted by the IE ConditionalReconfiguration, wherein the IE ConditionalReconfiguration includes an IE CondReconfigToAddModList which includes for a CPC candidate cell a CPC candidate cell configuration e.g. OCTET STRING (CONTAINING RRCReconfiguration), denoted RRCReconfiguration(CPC candidate) and, an includes an associated execution condition (comprising one or more measurement identifier(s) pointing to a CPC measurement configuration, also to be provide to the UE). In one sub-option that CPC measurement configuration (also to be provide to the UE) is an MCG measConfig associated to the CHO target candidate, i.e., it is the MCG measConfig within the denoted RRCReconfiguration(MCG candidate) message for the CHO target candidate, which is to be checked by the UE and monitored when the UE is configured with CHO including CPC. In one sub-option that CPC measurement configuration (also to be provide to the UE) is an MCG measConfig of the RRCReconfiguration which the UE receives from the S-MN when it is configured with CHO including CPC and / or CPA, which is to be checked by the UE and monitored when the UE is configured with CHO including CPC. The S-MN may receive information from the T-MN regarding the number of CPC / CPA configurations that have been configured. In one option, the S-MN may cancel the configuration of certain candidate PSCell(s) or PCell(s), e.g. if the UE capabilities are exceeded. Determining an S-MN measConfig configuration for the UE, also considering the UE capabilities related to measurements. If the S-MN received a T-MN measConfig from the T-MN, the S-MN may merge the S- MN and T-MN measConfig into one measConfig for the UE. The merging may, e.g., mean adding measurements, removing measurements, or modifying measurements in the measurement configuration. If the T-MN used the S-MN measConfig to define the execution condition(s) for CPC / CPA, the S-MN may use the measConfig received from the T-MN.If the T-MN proposed update of the S-MN measConfig, the S-MN may decide whether to accept or reject the proposal, e.g., taking UE capabilities into account. The S-MN may determine the final measConfig to be transmitted to the UE. In one option, the S-MN replies to the T-MN with information related to proposed update of the measConfig. The S-MN may, e.g., reply with an indication of acknowledge or not acknowledge of the proposal, or with transmission of the final measConfig to the T-MN. The reply may e.g. be sent in SN STATUS TRANSFER, or in other XnAP, NGAP, F1, E1 message or in RRC inter-node message, e.g., CG-CandidateList, CG-Config, or CG-ConfigInfo. Transmitting, to the UE, a reconfiguration message, e.g., RRCReconfiguration, the message containing the configuration of CHO and associated CPC / CPA configuration(s). Receiving a reply from the UE, e.g., RRCReconfigurationComplete. Aspects of the disclosure comprise a method executed by a node acting as candidate target Master Node (T-MN), the method comprising: Receiving a message, HANDOVER REQUEST, from a source Master Node (S-MN), the message containing a request for CHO with associated configuration of CPC / CPA. The current UE configuration may be included in the message. In one option, the S-MN measConfig is included in the message. Determining to accept the configuration of CHO with associated configuration of CPC / CPA. Preparing target configuration for CHO and triggering the configuration of CPC / CPA. If the target candidate PSCell belongs to a different node, transmitting a message, e.g., SN ADDITION REQUEST, to the T-SN, containing the request to configure CPC or CPA. If the target candidate PSCell belongs to a different node, receiving a reply from the other node, e.g., SN ADDITION REQUEST ACKNOWLEDGE, the message containing the target configuration of CPC or CPA. Preparing execution condition(s) for CPC / CPA, see different options below. Transmitting a message, HANDOVER REQUEST ACKNOWLEDGE, to the S-MN, the message containing the target configuration for CHO and the configuration of target candidate PSCell(s) (CPC or CPA configurations) for the CHO target candidate PCell(s). The CPC or CPA configurations comprise execution conditions and the target configuration for CPC / CPA, where the execution conditions comprise the configuration of measId and measConfig. In one option, the measConfig refers to the T-MN measConfig. In one option, the measConfig refers to the S-MN measConfig. The T-SN may have used the S-MN measConfig received from the S-MN, e.g. in HANDOVER REQUEST, to define execution conditions(s) for CPC / CPA.In one option, the message may contain a proposed update of the S-MN measConfig, i.e., the T-MN may propose certain configuration of measConfig to the S-MN, for the execution condition(s) of CPC / CPA. The T-MN may or may not have used a received S-MN measConfig as input to the proposed measConfig. In one option, in case of CPC, the measConfig is referring to the S-SN measConfig. This is an additional option in addition to the two main options a and b described in detail. The S-SN may be requested / invited to provide execution conditions, i.e., measId’s referring to the S-SN measConfig, for the CPC conditional reconfiguration. For this option, additional information may be sent to the S-MN, e.g., the T-SN measConfig may be transmitted in a message over XnAP, NGAP, F1, E1 message or in RRC inter-node message e.g. CG-CandidateList, CG- Config or CG-ConfigInfo. In one option, the HANDOVER REQUEST ACKNOWLEDGE, from the (candidate) T- MN, contains at least one CHO target configuration (e.g. RRCReconfiguration(MCG candidate) message) to be provided to the UE by the S-MN, wherein that CHO target configuration contains a CPC configuration. The CHO target configuration may be denoted by a RRCReconfiguration(MCG candidate) message and the CPC configuration may be denoted by the IE ConditionalReconfiguration, wherein the IE ConditionalReconfiguration includes an IE CondReconfigToAddModList which includes for a CPC candidate cell a CPC candidate cell configuration e.g. OCTET STRING (CONTAINING RRCReconfiguration), denoted RRCReconfiguration(CPC candidate) and, an includes an associated execution condition (comprising one or more measurement identifier(s) pointing to a CPC measurement configuration, also to be provide to the UE). In one sub-option that CPC measurement configuration (also to be provided to the UE) is an MCG measConfig associated to the CHO target candidate i.e. it is the MCG measConfig within the denoted RRCReconfiguration(MCG candidate) message for the CHO target candidate, which is to be checked by the UE and monitored when the UE is configured with CHO including CPC. In one sub-option that CPC measurement configuration (also to be provided to the UE) is an MCG measConfig of the RRCReconfiguration which the UE receives from the S-MN when it is configured with CHO including CPC and / or CPA, which is to be checked by the UE and monitored when the UE is configured with CHO including CPC. The T-MN may in the network message include information to the S-MN regarding the number of CPC configurations that have been configured (or corresponding information). If the T-MN proposed update of the S-MN measConfig, the T-MN may receive a reply from the S-MN. with information related to proposed update of the measConfig. The S-MN maye.g. reply with an indication of acknowledge or not acknowledge of the proposal, or with transmission of the final measConfig to the T-MN. The reply may, e.g., be sent in SN STATUS TRANSFER, or in other XnAP, NGAP, F1, E1 message or in RRC inter-node message e.g. CG- CandidateList, CG-Config or CG-ConfigInfo. C1. Aspects comprise a method executed by a User equipment (UE), the method comprising: Receiving a message (e.g. RRC Reconfiguration) including a CHO configuration, wherein the CHO configuration includes at least i) a CHO target candidate cell configuration (e.g. embedded RRC Reconfiguration) and ii) a CHO execution condition associated to the CHO target candidate cell configuration, wherein the CHO target candidate cell configuration is associated with a candidate SCG configuration (referred here as a CPC or CPA configuration), wherein the CPC / CPA configuration includes: i) a CPC / CPA target candidate configuration (e.g., candidate SCG configuration) and ii) an associated CPC / CPA execution condition (one or more measId(s) associated to the CPC / CPA target candidate configuration) Evaluating whether the CHO execution condition is fulfilled and evaluating whether the CPC / CPA execution condition is fulfilled, wherein the CPC / CPA execution condition comprises at least one measurement identity associated with (or referring to): option a) an MCG measurement configuration (MCG MeasConfig, S-MN MeasConfig) in the UE’s current configuration (i.e., the configuration the UE operates with the S-MN, in the MCG VarMeasConfig); or option b) one MCG measurement configuration within the CHO target candidate cell configuration (MCG MeasConfig of the candidate T-MN, candidate T-MN MeasConfig). Applying the CHO target candidate cell configuration at least when the CHO execution condition is fulfilled; and when the CPC execution condition is fulfilled, applying the candidate SCG configuration associated with the CHO target candidate cell configuration. In one dependent aspect, the CHO target candidate cell configuration is associated with a candidate SCG configuration (referred here as a CPC or CPA configuration) by one or more of: i) The candidate SCG configuration is a CPC or CPA configuration with the CHO target candidate cell configuration;ii) The candidate SCG configuration is a CPC or CPA configuration which contains a CHO configuration identifier matching the CHO configuration identifier of the associated CHO target candidate configuration. In one dependent aspect, the UE performs one or more measurements based on the CPC / CPA measurement configuration associated to the CPC / CPA execution condition but only starts the evaluation of the execution condition(s) associated to these measId(s) when the associated CHO execution condition is fulfilled. Thanks to that the UE does not need to evaluate the associated CPC / CPA execution until the CHO execution condition is fulfilled. In one dependent aspect of option a), the CHO execution condition comprises two measId(s), wherein the first measId is associated to the CHO execution condition (i.e. a measurement associated to an associated candidate PCell) and the second measId is associated to the CPC execution condition (i.e. a measurement associated to an associated candidate PSCell). In that case, the UE is aware that the combined execution condition for CHO and CPC is to be evaluated. In this case, the measurement object associated to the first measId is a measurement object associated to a first frequency, while the measurement object associated to the second measId is a measurement object associated to a second frequency (for the PSCell candidate). Option a): CPC execution condition configured in S-MN MeasConfig In some aspects of the disclosure, the UE receives in an RRC Reconfiguration message including the MCG measurement configuration (MCG MeasConfig, S-MN MeasConfig) for the UE’s current configuration (i.e., the configuration the UE operates with the S-MN, in the MCG VarMeasConfig) and applies it. That RRC Reconfiguration message (e.g., RRCReconfiguration) may be received from the S-MN, and including a measConfig of IE MeasConfig (including an instance of the IE MeasToAddModId with a measId, reportConfigId, and a measObjectId, referring respectively to a reporting configuration (e.g., instance of a ReportConfigNR) and to a measurement object (e.g., instance of a MeasObjectNR) the UE is configured or is being configured with), wherein the included measId has the same value as a measId configured as CPC execution condition for an SCG candidate within the CHO target candidate cell configuration. For example, the UE receives in an RRCReconfiguration message a CHO configuration with a CHO target candidate cell configuration and within that configuration, the UE receives a CPC configuration including the CPC target candidate configuration (e.g., for cell A) and its associated CPC execution condition, e.g., measId=X. Within the RRCReconfiguration message the UE also receives the MCG MeasConfig (S-MN MeasConfig) in which the measId=X is configured i.e. the instance of the IE MeasIdToAddMod including the measId=X and its association to a reportConfigId and measObjectId. The reportConfigId refers to aReportConfigNR IE whose reportType is set to an indication that this is for a conditional reconfiguration, e.g., condTriggerConfig, containing the configuration of one or more events, e.g., A4, A3, A5 and its associated parameters such as time to trigger, thresholds, hysteresis, etc. In one option (e.g., in the case the MCG MeasConfig is received in the same RRCReconfiguration message or in a previous message), the UE would include that configuration in a UE variable (MCG VarMeasConfig) which may be accessed to determine the configuration of the CPC execution condition. In one sub-option, the MeasIdToAddMod instance received by the UE within the MCG MeasConfig (S-MN MeasConfig), which refers to the CPC execution condition (within the CHO target candidate cell configuration), is received similarly to other MeasIdToAddMod instances configured for MCG measurements not referring to the CPC execution condition(s) e.g. CHO related measurements, or other events related to measurement reports for S-MN operation like for A3, or A5 events. However, there can be no repetition of measurement identifier: when the UE has in its UE’s current MCG MeasConfig a measId=Y, e.g., used to configure an A3 event for measurement reports, the T-MN cannot configure that measId=Y as a CPC execution condition, for the CPC configuration within its CHO target candidate cell configuration. That may be guaranteed by the S-MN transmitting the HANDOVER REQUEST (including the indication this is for CHO) including one or more of: The UE’s current configuration and / or the intended UE’s current configuration, so that the T-MN knows what measId(s) it is not allowed to use; or One or more values of measId(s) which the T-MN would be allowed to use, for that purpose of configuring CPC execution conditions, for a CPC configuration within the CHO target candidate cell configuration. In an alternative sub-option, the MeasIdToAddMod instance (or equivalent IE with similar parameters) received by the UE within the MCG MeasConfig (S-MN MeasConfig), which refers to the CPC execution condition (within the CHO target candidate cell configuration), is received in a different field and / or IE, compared to the MeasIdToAddMod instances configured for MCG measurements not referring to the CPC execution condition(s) e.g. CHO related measurements, or other events related to measurement reports for S-MN operation like for A3, or A5 events. When the UE receives the configuration for CPC measurements within the MCG MeasConfig (S-MN MeasConfig), which refers to the CPC execution condition (within the CHO target candidate cell configuration), the UE may store the configuration(s) in a different UE variable (e.g. MCG VarMeasConfig-CPC) which is different compared to the UE variable used for non- CPC related measurements MCG VarMeasConfig. In that case, this would be a new UE variable for measurement configuration(s) in addition to the existing ones MCG VarMeasConfig andSCG VarMeasConfig. The new variable may in one option comprise an MCG VarMeasConfig containing another UE variable SCG VarMeasConfig. Some examples of how the UE receives an RRCReconfiguration message including the CPC / CPA related measurement configuration for the CPC / CPA associated to the CHO target candidate configuration, are shown below: In one option, different measConfig fields / IEs, one for UE’s CHO related measurements (e.g. measConfig) and one for CPC related measurements (e.g. newly introduced measConfig- CPAC-r18):} In this example above, the measurement configuration for CPC related measurements is defined as an IE OCTET STRING (CONTAINING MeasConfig) to indicate that the S-MN may have received the whole container as generated by the T-MN e.g. in an RRC inter-node message included within the HANDOVER REQUEST ACK, received by the S-MN in response to the HANDOVER REQUEST for CHO. Another possible alternative would be to define the IE MeasConfig, for the new field measConfig-CPAC, allowing the S-MN to understand the CPC / CPA related measurement configuration generated by the T-MN. This is illustrated in FIG.6. The fact that there are different fields (measConfig and measConfig-CPAC-r18) allows the same measId(s) to be reused for CPC related measurements and non-CPC measurements. In other words, one advantage is that this could prevent the need for a measurement Id coordination between the S-MN and candidate(s) T-MN(s), which might be specially cumbersome in case there are multiple T-MN(s) candidate(s). This might be useful in case the S-MN may configure further measId(s) to the same UE. - Different list of measurement identifiers configurations fields / IEs, one for UE’s CPC related measurements (e.g. measIdToAddModList of IE MeasIdToAddModList) and one for CPC related measurements (e.g. newly introduced measIdToAddModList-r18):[…] } In this example above, the configuration of measId(s) for CPC related measurements is defined as an IE OCTET STRING (CONTAINING MeasIdToAddModList) to indicate that the S-MN may have received the whole container as generated by the T-MN, e.g., in an RRC inter- node message included within the HANDOVER REQUEST ACK, received by the S-MN in response to the HANDOVER REQUEST for CHO. Another possible alternative would be to define the IE MeasIdToAddModList, for the new field, allowing the S-MN to understand the CPC related measurement configuration generated by the T-MN. This might be useful in case the S-MN may configure further measId(s) to the same UE. Different lists of measurement identifiers configurations, reporting configurations and measurement object configurations, one set for UE’s CPC related measurements and one set for CPC related measurements (e.g., newly introduced lists):Note: In a), the S-MN may receive from the T-MN the CHO target candidate cell configuration including a CPC configuration (where the CPC execution condition for a an SCG candidate is configured), which the UE may determine by looking inside the CHO target candidate cell configuration. However, the S-MN receives from the T-MN, an MCG MeasConfig to be included in the S-MN’s MeasConfig for the UE’s current configuration, to be provided to the UE. Thus, when the UE receives the CHO target candidate cell configuration including a CPC configuration the UE identifies the measId for the CPC execution condition associated to an SCG candidate to be monitored, and within the UE’s MCG measConfig for the UE’s current configuration the UE finds the actual MeasIdToAddMod for that measId, and consequently the associated measObjectId pointing to the MeasObjectNR IE (indicating e.g. frequency information) and reportConfigId pointing to the ReportConfigNR IE (indicating, e.g., the event configuration, thresholds, etc.).In some aspects of the disclosure, the UE evaluating whether the CHO execution condition is fulfilled and evaluating whether the CPC / CPA execution condition is fulfilled further comprises the UE determining one or more measurements (e.g. measId(s) and associated configurations such as reporting configuration(s) and measurement object(s)) to be performed and to be used as input to the evaluation of the CHO execution condition(s) concurrent with the CPC / CPA execution condition(s). In some aspects of the disclosure, the UE determines the measurement configuration MeasConfig (S-MN MeasConfig for option a) for the measId to be evaluated for the CPC / CPA execution condition(s) as follows: The UE shall, for each conditional reconfiguration identifier for CHO (condReconfigId), within the UE variable including the CHO configuration (VarConditionalReconfig): If the CHO execution condition (condExecutionCond) is configured and; if the CHO target candidate configuration (RRCReconfiguration within condRRCReconfig) includes a CPC configuration (conditionalReconfiguration) i.e. CPC configuration within CHO: For each conditional reconfiguration identifier for the CPC withih the CHO (condReconfigId within the CPC configuration i.e. within conditionalReconfiguration): If the execution condition(s) for the CPC configuration within CHO target candidate configuration (condExecutionCondSCG) is configured: In the remainder of the procedure, consider each measId indicated as CPC execution condition (in the condExecutionCondSCG) as a measId in the VarMeasConfig associated with the MCG measConfig (option a), S-MN MeaConfig); An example of how this may be implemented in RRC specifications is shown below: ************************************************************************************* 5.3.5.13.4 Conditional reconfiguration evaluation The UE shall: 1> for each condReconfigId within the VarConditionalReconfig: [..] 2> if condExecutionCond is configured: [..] 3> if it is configured via SRB3 or configured within nr-SCG or within nr-SecondaryCellGroupConfig (specified in TS 36.331

[0010] ) via SRB1: 4> in the remainder of the procedure, consider each measId indicated in the condExecutionCond as a measId in the VarMeasConfig associated with the SCG measConfig; 3> else:4> in the remainder of the procedure, consider each measId indicated in the condExecutionCond as a measId in the VarMeasConfig associated with the MCG measConfig; 3> if the CHO target candidate configuration (RRCReconfiguration within condRRCReconfig) includes a CPC configuration (conditionalReconfiguration, (CPC configuration within CHO): 4> for each condReconfigId within the CPC configuration (i.e. within conditionalReconfiguration: 5> if condExecutionCond is configured (execution condition(s) for the CPC configuration within CHO target candidate configuration): 6> in the remainder of the procedure, consider each measId indicated as CPC execution condition (in the condExecutionCond) as a measId in the VarMeasConfig associated with the MCG measConfig; (S-MN MeasConfig); ************************************************************************************* An example of how this may be implemented in RRC specifications is shown below: ************************************************************************************* 5.3.5.13.4 Conditional reconfiguration evaluation The UE shall: 1> for each condReconfigId within the VarConditionalReconfig: [..] 2> if condExecutionCond is configured: [..] 3> if it is configured via SRB3 or configured within nr-SCG or within nr-SecondaryCellGroupConfig (specified in TS 36.331

[0010] ) via SRB1: 4> in the remainder of the procedure, consider each measId indicated in the condExecutionCond as a measId in the VarMeasConfig associated with the SCG measConfig; 3> else: 4> in the remainder of the procedure, consider each measId indicated in the condExecutionCond as a measId in the VarMeasConfig associated with the MCG measConfig; 3> if the CHO target candidate configuration (RRCReconfiguration within condRRCReconfig) is associated to a CPC configuration: 4> for each SCG candidate configuration: 5> if CPC execution condition is configured (execution condition(s) for the SCG candidate configuration associated to the CHO target candidate configuration): 6> in the remainder of the procedure, consider each measId indicated as CPC execution condition (in the condExecutionCond) as a measId in the VarMeasConfig associated with the MCG measConfig; (S-MN MeaConfig); ************************************************************************************* In some aspects of the disclosure, the UE determines the measurement configuration MeasConfig (S-MN MeasConfig for option a) for the measId to be evaluated for the CPC / CPA execution condition(s) as follows: *************************************************************************************5.3.5.13.4 Conditional reconfiguration evaluation The UE shall: 1> for each condReconfigId within the VarConditionalReconfig: 2> if condExecutionCond is configured: [..] 3> if it is configured via SRB3 or configured within nr-SCG or within nr-SecondaryCellGroupConfig (specified in TS 36.331

[0010] ) via SRB1: 4> in the remainder of the procedure, consider each measId indicated in the condExecutionCond as a measId in the VarMeasConfig associated with the SCG measConfig; 3> else: 4> in the remainder of the procedure, consider each measId indicated in the condExecutionCond as a measId in the VarMeasConfig associated with the MCG measConfig; 3> if the RRCReconfiguration within condRRCReconfig includes a conditionalReconfiguration (CPC configuration within CHO): 4> for each condReconfigId within the conditionalReconfiguration (CPC configuration): 5> if condExecutionCondSCG is configured (CPC configuration): 6> in the remainder of the procedure, consider each measId indicated in the condExecutionCondSCG as a measId in the VarMeasConfig associated with the MCG measConfig; (S-MN MeaConfig); ************************************************************************************ In some other aspects of the disclosure, the UE determines the measurement configuration MeasConfig (S-MN MeasConfig for option a) for the measId to be evaluated for the CPC / CPA execution condition(s) as follows: ***************************************************************************** 5.3.5.13.4 Conditional reconfiguration evaluation The UE shall: 1> for each condReconfigId within the VarConditionalReconfig: [..] 2> if condExecutionCond is configured: [..] 3> if it is configured via SRB3 or configured within nr-SCG or within nr-SecondaryCellGroupConfig (specified in TS 36.331

[0010] ) via SRB1: 4> in the remainder of the procedure, consider each measId indicated in the condExecutionCond as a measId in the VarMeasConfig associated with the SCG measConfig; 3> else: 4> in the remainder of the procedure, consider each measId indicated in the condExecutionCond as a measId in the VarMeasConfig associated with the MCG measConfig;3> if the RRCReconfiguration within condRRCReconfig includes a candidate SCG configuration associated to it: 4> for each candidate SCG configuration, if condExecutionCondSCG is configured (CPC configuration): 5> in the remainder of the procedure, consider each measId indicated in the condExecutionCondSCG as a measId in the VarMeasConfig associated with the MCG measConfig; (S-MN MeaConfig); ***************************************************************************** Option b): CPC execution condition configured in T-MN MeasConfig In some aspects of the disclosure, the UE receives in an RRC Reconfiguration message including the CHO target candidate cell configuration (denoted RRCReconfiguration*), wherein the RRCReconfiguration includes a measurement configuration (denoted candidate T-MN MCG MeasConfig, or simply T-MN MCG MeasConfig). In principle, that would have been a measurement configuration the UE would apply upon fulfillment of the CHO execution condition(s) associated to that CHO target candidate cell; however, according to these aspects, as the UE shall evaluate CPC execution condition(s) associated to a CPC configuration within that CHO target candidate cell configuration, the UE applies at least parts of that T-MN MCG MeasConfig (and / or operates according to that partial measurement configuration to perform measurements while the UE is connected to the S-MN). That RRCReconfiguration* (CHO target candidate cell configuration) may be received from the S-MN, and including a measConfig of IE MeasConfig (including an instance of the IE MeasToAddModId with a measId, reportConfigId, and a measObjectId, referring respectively to a reporting configuration (e.g. instance of a ReportConfigNR) and to a measurement object (e.g. instance of a MeasObjectNR) the UE is configured or is being configured with), wherein the included measId has the same value as a measId configured as CPC execution condition for an SCG candidate within the CHO target candidate cell configuration. For example, the UE receives in an RRCReconfiguration message a CHO configuration with a CHO target candidate cell configuration (RRCReconfiguration*) and within that configuration, the UE receives a CPC configuration including the CPC target candidate configuration (e.g. for cell A) and its associated CPC execution condition e.g. measId=X, and an MCG measurement configuration e.g. measConfig of IE MeasConfig. Within the MCG MeasConfig (T-MN MeasConfig) the measId=X is configured i.e. the instance of the IE MeasIdToAddMod including the measId=X and its association to a reportConfigId and measObjectId. The reportConfigId refers to a ReportConfigNR IE whose reportType is set to an indication that this is for a conditional reconfiguration, e.g., condTriggerConfig, containing the configuration of one or more events e.g. A4, A3, A5 and its associated parameters such as time to trigger, thresholds, hysteresis, etc. In one option (e.g., in the case the T-MN MCGMeasConfig is received in the same RRCReconfiguration message or in a previous message), the UE would include that configuration in a UE variable (T-MN MCG VarMeasConfig) which may be accessed to determine the configuration of the CPC execution condition. In one sub-option, the MeasIdToAddMod instance received by the UE within the T-MN MCG MeasConfig (T-MN MeasConfig), which refers to the CPC execution condition (within the CHO target candidate cell configuration), is received similarly to other MeasIdToAddMod instances configured for T-MN MCG measurements not referring to the CPC execution condition(s) e.g. CHO related measurements, or other events related to measurement reports for S-MN operation like for A3, or A5 events. One issue with this option is that these CPC related measurements for CPC within CHO, are measurements configured to be performed by the UE while the UE is still connected to the S-MN, and monitoring CHO; However, there would be other measurements configured in the T-MN MCG MeasConfig which would only be required to be performed when the CHO execution condition is fulfilled. There may be different ways to enable the UE to distinguish between these two types of measurements, and determine which measurements are for the CPC execution condition and are to be performed. For example: The UE performs the measurements configured by the measId(s) within MeasIdToAddMod associated to a reportConfigId whose ReportConfigNR has a reportType set to a conditional trigger (e.g. condTriggerConfig); and / or The UE performs the measurements configured by measId(s) within MeasIdToAddMod whose value is configured as a CPC execution condition in a CPC configuration within that RRCReconfiguration* and / or The UE performs the measurements configured by measId(s) within MeasIdToAddMod whose value is configured as a CPA execution condition in a CPC configuration within that RRCReconfiguration* and / or the UE performs the measurements configured by measId(s) within a different measurement configuration field and / or IE of the RRCReconfiguration*, compared to the measurement configuration field and / or IE of the RRCReconfiguration* to be performed only when the CHO execution condition is fulfilled. For example, the RRCReconfiguration* may include a measConfig and a measConfig-CPC or a measConfig-CPA (or a measConfig-CPAC), wherein while the UE is evaluating the CHO execution condition (and connected to the S-MN) the UE performs the measurements associated to the measConfig-CPC or measConfig-CPA (or measConfig-CPAC). FIG.7 illustrates the signaling structure. Note: In b), the S-MN may receive from the T-MN the CHO target candidate cell configuration including a CPC configuration (where the CPC execution condition for an SCG candidate is configured), which the UE may determine by looking inside the CHO target candidate cell configuration. Thus, when the UE receives the CHO target candidate cellconfiguration including a CPC configuration the UE identifies the measId for the CPC execution condition associated to an SCG candidate to be monitored, and within the UE’s MCG measConfig for the UE’s current configuration the UE finds the actual MeasIdToAddMod for that measId, and consequently the associated measObjectId pointing to the MeasObjectNR IE (indicating e.g. frequency information) and reportConfigId pointing to the ReportconfigNR IE (indicating, e.g., the event configuration, thresholds, etc.). In some aspects of the disclosure, for solution b), the UE determines the measurement configuration MeasConfig (S-MN MeasConfig for option a) for the measId to be evaluated for the CPC / CPA execution condition(s) as follows: The UE shall, for each conditional reconfiguration identifier for CHO (condReconfigId), within the UE variable including the CHO configuration (VarConditionalReconfig): If the CHO execution condition (condExecutionCond) is configured and; If the CHO target candidate configuration (RRCReconfiguration within condRRCReconfig) includes a CPC configuration (conditionalReconfiguration) i.e. CPC configuration within CHO: For each conditional reconfiguration identifier for the CPC withih the CHO (condReconfigId within the CPC configuration i.e. within conditionalReconfiguration): If the execution condition(s) for the CPC configuration within CHO target candidate configuration (condExecutionCondSCG) is configured: In the remainder of the procedure, consider each measId indicated as CPC execution condition (in the condExecutionCondSCG) as a measId in the VarMeasConfig associated with the MCG measConfig (option a), S-MN MeaConfig); In the remainder of the procedure, consider each measId indicated in the CPC execution condition (condExecutionCondSCG) as a measId in the MCG measConfig of the CHO target candidate cell configuration (RRCReconfiguration within condRRCReconfig for CPC), which is denoted T-MN MeaConfig. An example of how this may be implemented in RRC specifications is shown below: ************************************************************************************* 5.3.5.13.4 Conditional reconfiguration evaluation The UE shall: 1> for each condReconfigId within the VarConditionalReconfig: [..] 2> if condExecutionCond is configured: [..]3> if it is configured via SRB3 or configured within nr-SCG or within nr-SecondaryCellGroupConfig (specified in TS 36.331

[0010] ) via SRB1: 4> in the remainder of the procedure, consider each measId indicated in the condExecutionCond as a measId in the VarMeasConfig associated with the SCG measConfig; 3> else: 4> in the remainder of the procedure, consider each measId indicated in the condExecutionCond as a measId in the VarMeasConfig associated with the MCG measConfig; 3> if the RRCReconfiguration within condRRCReconfig includes a CPC configuration (conditionalReconfiguration)): 4> for each CPC configuration identifier (condReconfigId) within the CPC configuration (conditionalReconfiguration): 5> if a CPC execution condition (condExecutionCondSCG) is configured: 6> in the remainder of the procedure, consider each measId indicated in the CPC execution condition (condExecutionCondSCG) as a measId in the MCG measConfig of the RRCReconfiguration within condRRCReconfig for CPC (T- MN MeasConfig); ************************************************************************************* Another example is as follows: ************************************************************************************* 5.3.5.13.4 Conditional reconfiguration evaluation The UE shall: 1> for each condReconfigId within the VarConditionalReconfig: [..] 2> if condExecutionCond is configured: [..] 3> if it is configured via SRB3 or configured within nr-SCG or within nr-SecondaryCellGroupConfig (specified in TS 36.331

[0010] ) via SRB1: 4> in the remainder of the procedure, consider each measId indicated in the condExecutionCond as a measId in the VarMeasConfig associated with the SCG measConfig; 3> else: 4> in the remainder of the procedure, consider each measId indicated in the condExecutionCond as a measId in the VarMeasConfig associated with the MCG measConfig; 3> if the RRCReconfiguration within condRRCReconfig includes a conditionalReconfiguration (CPC configuration): 4> for each condReconfigId within the conditionalReconfiguration (CPC configuration): 5> if condExecutionCondSCG is configured (CPC configuration): 6> in the remainder of the procedure, consider each measId indicated in the condExecutionCondSCG as a measId in the MCG measConfig of the RRCReconfiguration within condRRCReconfig for CPC (T-MN MeaConfig); *************************************************************************************In one more options, in addition to option a) and option b), the execution conditions for CPC may comprise measId’s referring to the S-SN measConfig. The S-SN may be asked by the T-MN to provide execution conditions for CPC where the measId’s refer to the S-SN measConfig. In both option a) and option b), the UE needs to perform the measurements associated with each measId configured as CPC / CPA execution condition(s), for the CPC / CPA associated with (or within) the CHO target candidate cell configuration, in addition to the measurements performed according to the UE’s current MCG MeasConfig. These measurements need to be performed for the evaluation of the CPC execution conditions; one example of these measurements may be Synchronization Signal Block (SSB) based cell measurements of a PSCell candidate cell configured for CPC within CHO, and CSI-RS based cell measurements of a PSCell candidate cell configured for CPC within CHO. In addition, if the UE is in MR-DC and has a configured SCG, the UE needs to perform measurements for the current PSCell. In one set of aspects of the disclosure, at least related to option b), the UE perform one or more measurements (e.g., cell measurement results based on SSB(s) of the candidate PSCell) for each measurement identifier (measId) configured in the measIdToAddModList within the MeasConfig of at least one CHO target candidate configuration, wherein the CHO target candidate configuration has a CPC configuration within with an associated SCG candidate configuration, wherein the measId is for a CPC / CPA execution condition for that associated SCG candidate. An example implementation of the UE performing measurements according to the measId configured in the measConfig of the CHO target candidate configuration is as follows: ****************************************************************************** 5.5.3 Performing measurements 5.5.3.1 General [..] The UE shall: 1> for each measId included in the measIdToAddModList within the MeasConfig of each CHO target candidate with an associated candidate SCG with a CPC execution condition; or 1> for each measId included in the measIdList within VarMeasConfig: […] 2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the MCG measConfig and is indicated in the condExecutionCond associated to a condReconfigId in the MCG VarConditionalReconfig (for CHO, CPA or MN-initiated inter-SN CPC in NR-DC); or 2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the SCG VarMeasConfig and is indicated in the condExecutionCond associated to a condReconfigId in the SCG VarConditionalReconfig (for intra-SN CPC); or2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the SCG VarMeasConfig and is indicated in the condExecutionCondSCG associated to a condReconfigId in the MCG VarConditionalReconfig (for SN-initiated inter-SN CPC in NR-DC); or 2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the SCG VarMeasConfig and is indicated in the triggerConditionSN associated to a condReconfigurationId in VarConditionalReconfiguration as specified in TS 36.331

[0010] (for SN-initiated inter-SN CPC in EN- DC); or 2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the MCG MeasConfig of a CHO target candidate configuration is indicated in a CPC execution condition (condExecutionCondSCG) associated to a condReconfigId in the CHO target candidate configuration (for CHO associated to a CPC configuration): 3> if a measurement gap configuration is setup, or 3> if the UE does not require measurement gaps to perform the concerned measurements: 4> if s-MeasureConfig is not configured, or 4> if s-MeasureConfig is set to ssb-RSRP and the NR SpCell RSRP based on SS / PBCH block, after layer 3 filtering, is lower than ssb-RSRP, or 4> if s-MeasureConfig is set to csi-RSRP and the NR SpCell RSRP based on CSI-RS, after layer 3 filtering, is lower than csi-RSRP: 5> if the measObject is associated to NR and the rsType is set to csi-rs: 6> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured: 7> derive layer 3 filtered beam measurements only based on CSI-RS for each measurement quantity indicated in reportQuantityRS-Indexes, as described in 5.5.3.3a; 6> derive cell measurement results based on CSI-RS for the trigger quantity and each measurement quantity indicated in reportQuantityCell using parameters from the associated measObject, as described in 5.5.3.3; 5> if the measObject is associated to NR and the rsType is set to ssb: 6> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured: 7> derive layer 3 beam measurements only based on SS / PBCH block for each measurement quantity indicated in reportQuantityRS-Indexes, as described in 5.5.3.3a; 6> derive cell measurement results based on SS / PBCH block for the trigger quantity and each measurement quantity indicated in reportQuantityCell using parameters from the associated measObject, as described in 5.5.3.3; […] ****************************************************************************** In one set of aspects of the disclosure, related to option a), the UE perform one or more measurements (e.g., cell measurement results based on SSB(s) of the candidate PSCell) for each measurement identifier (measId) configured in the measIdToAddModList within the UE variable VarMeasConfig according to the S-MN’s MeasConfig, wherein the measId measId is associated to a CPC / CPA execution condition for a candidate SCG associated to a CHO target candidate cell configuration. The measId is a measId whose reportType for the associated reportConfig is condTriggerConfig, and the measId is within the MCG measConfig and the measId is indicatedin a new IE / field indicating this is for a candidate SCG associated to a CHO target candidate (denoted condExecutionCond-SCG-CHO) associated to a condReconfigId in the MCG VarConditionalReconfig (for a candidate SCG associated to CHO); ****************************************************************************** 5.5.3 Performing measurements 5.5.3.1 General [..] The UE shall: 1> for each measId included in the measIdList within VarMeasConfig: […] 2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the MCG measConfig and is indicated in the condExecutionCond associated to a condReconfigId in the MCG VarConditionalReconfig (for CHO, CPA or MN-initiated inter-SN CPC in NR-DC); or 2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the SCG VarMeasConfig and is indicated in the condExecutionCond associated to a condReconfigId in the SCG VarConditionalReconfig (for intra-SN CPC); or 2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the SCG VarMeasConfig and is indicated in the condExecutionCondSCG associated to a condReconfigId in the MCG VarConditionalReconfig (for SN-initiated inter-SN CPC in NR-DC); or 2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the SCG VarMeasConfig and is indicated in the triggerConditionSN associated to a condReconfigurationId in VarConditionalReconfiguration as specified in TS 36.331

[0010] (for SN-initiated inter-SN CPC in EN- DC); or 2> if the reportType for the associated reportConfig is condTriggerConfig, the measId is within the MCG VarMeasConfig and is indicated in the condExecutionCondSCG-CHO associated to a condReconfigId in the MCG VarConditionalReconfig; 3> if a measurement gap configuration is setup, or 3> if the UE does not require measurement gaps to perform the concerned measurements: 4> if s-MeasureConfig is not configured, or 4> if s-MeasureConfig is set to ssb-RSRP and the NR SpCell RSRP based on SS / PBCH block, after layer 3 filtering, is lower than ssb-RSRP, or 4> if s-MeasureConfig is set to csi-RSRP and the NR SpCell RSRP based on CSI-RS, after layer 3 filtering, is lower than csi-RSRP: 5> if the measObject is associated to NR and the rsType is set to csi-rs: 6> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured: 7> derive layer 3 filtered beam measurements only based on CSI-RS for each measurement quantity indicated in reportQuantityRS-Indexes, as described in 5.5.3.3a; 6> derive cell measurement results based on CSI-RS for the trigger quantity and each measurement quantity indicated in reportQuantityCell using parameters from the associated measObject, as described in 5.5.3.3; 5> if the measObject is associated to NR and the rsType is set to ssb:6> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured: 7> derive layer 3 beam measurements only based on SS / PBCH block for each measurement quantity indicated in reportQuantityRS-Indexes, as described in 5.5.3.3a; 6> derive cell measurement results based on SS / PBCH block for the trigger quantity and each measurement quantity indicated in reportQuantityCell using parameters from the associated measObject, as described in 5.5.3.3; […] ****************************************************************************** In a set of aspects of the disclosure, the UE evaluating whether the CHO execution condition is fulfilled and evaluating whether the CPC / CPA execution condition is fulfilled further comprises the UE determining one or more applicable cells (PSCells) to be considered as input to the CPC / CPA evaluation conditions (e.g. candidate PSCell(s) based on the CHO configuration. The reason this is needed is because the CPC related measConfig indidates a reporting configuration and measurement object configuration associated to the measId configured as CPC execution condition, but in principle would include any cell in the SSB frequency indicated in the measurement object, which is not desirable, as only the configured PSCell candidates are to be considered as applicable cells. That means the UE needs to consider as applicable cells the PSCells configured as candidates. For example, an applicable PSCell is a PSCell whose cell identifier (physical cell identity – PCI) is configured in the serving cell common configuration (IE ServingCellConfigCommon) of the candidate SCG configuration for the SpCell configuration. In other words, the UE needs to determine the PCI of the PSCell to be measured and evaluated. In one solution, the UE determines the PCI for the applicable cell as the PCI configured within the ServingCellConfigCommon of the candidate PSCell configuration within the CPC configuration within the CHO configuration, to be the applicable cell for the associated measId. This is valid either for option a) or option b), as in both cases, regardless if the UE uses the T-MN measConfig or S-MN MeasConfig the UE needs to determine the applicable PSCells. An example implementation of the UE determining the PCI of the PSCell is shown below: ************************************************************************************* 5.3.5.13.4 Conditional reconfiguration evaluation The UE shall: 1> for each condReconfigId within the VarConditionalReconfig: 2> for a CHO target candidate cell configuration, i.e. if the RRCReconfiguration within condRRCReconfig includes the masterCellGroup including the reconfigurationWithSync: 3> consider the cell which has a physical cell identity matching the value indicated in the ServingCellConfigCommon included in the reconfigurationWithSync within the masterCellGroup inthe received condRRCReconfig to be applicable cell for the associated CHO execution condition (condExecutionCond); 3> if the CHO target candidate configuration includes a CPC configuration i.e. if the RRCReconfiguration within condRRCReconfig includes a conditionalReconfiguration for CPC (assuming there is no CHO within CHO): 4> for each candidate SCG configuration (RRCReconfiguration**) within the CPC configuration (i.e. for each condReconfigId within the conditionalReconfiguration (CPC configuration)): 5> consider the cell which has a PCI matching the value indicated in the ServingCellConfigCommon included in the reconfigurationWithSync within the secondaryCellGroup in the condRRCReconfig (i.e., in the RRCReconfiguration**) associated with the condReconfigId within the CPC configuration to be applicable cell; ************************************************************************************* An example implementation of the UE determining the PCI of the PSCell for solution a) is shown below: ************************************************************************************* 5.3.5.13.4 Conditional reconfiguration evaluation The UE shall: 1> for each condReconfigId within the VarConditionalReconfig: 2> if the RRCReconfiguration within condRRCReconfig includes the masterCellGroup including the reconfigurationWithSync: 3> consider the cell which has a physical cell identity matching the value indicated in the ServingCellConfigCommon included in the reconfigurationWithSync within the masterCellGroup in the received condRRCReconfig to be applicable cell; 3> if the RRCReconfiguration within condRRCReconfig includes a conditionalReconfiguration (CPC configuration): 4> for each condReconfigId within the conditionalReconfiguration (CPC configuration): 5> consider the cell which has a physical cell identity matching the value indicated in the ServingCellConfigCommon included in the reconfigurationWithSync within the secondaryCellGroup in the condRRCReconfig associated with the condReconfigId within the CPC configuration to be applicable cell; ************************************************************************************* An example implementation of the UE determining the PCI of the PSCell for solution B: ************************************************************************************* 5.3.5.13.4 Conditional reconfiguration evaluation The UE shall: 1> for each condReconfigId within the VarConditionalReconfig: 2> if the RRCReconfiguration within condRRCReconfig includes the masterCellGroup including the reconfigurationWithSync: 3> consider the cell which has a physical cell identity matching the value indicated in the ServingCellConfigCommon included in the reconfigurationWithSync within the masterCellGroup in the received condRRCReconfig to be applicable cell;3> if the RRCReconfiguration within condRRCReconfig includes a conditionalReconfiguration (CPC configuration): 4> perform the action according to 5.3.5.13.4; ************************************************************************************* In some aspects of the disclosure, the UE receives an RRCReconfiguration message including a CHO configuration, which includes at least a CHO target candidate cell configuration and an associated CHO execution condition, wherein the CHO target candidate cell configuration further includes one or more CPC or CPA configuration(s). Each CPC or CPA configuration, in turn, includes a CPC / CPA target candidate configuration (e.g. candidate SCG configuration) and associated CPC / CPA execution conditions (such as one or more measId(s) associated to the CPC / CPA target candidate configuration), where the CPC / CPA execution condition comprises at least one measurement identity associated with (or referring to) an MCG measurement configuration (MCG MeasConfig, S-MN MeasConfig) in the UE’s current configuration and at least one measurement identity associated with (or referring to) an MCG measurement configuration within the CHO target candidate cell configuration (MCG MeasConfig of the candidate T-MN). In one alternative, the UE evaluates the CPC / CPA execution condition using the S-MN measurement configuration (i.e. the current UE configuration used when evaluating the associated CHO execution condition) as long as the associated CHO execution condition is still being evaluated (in other words, prior to fulfillment of the CHO execution condition), i.e. while the UE is still in the source PCell / source MN. When the CHO execution condition has been fulfilled, the UE continues evaluation of one or more of the CPC or CPA configurations that are included in the CHO candidate target cell configuration. The UE then evaluates the CPC or CPA configuration(s) using the T-MN measurement configuration and the associated execution condition. In one example, the UE continues (or restarts) the evaluation of the CPC or CPA configuration(s) only after the CHO execution. In one example, the UE performs evaluation of CPC or CPA configuration(s) also during the CHO execution. In another variant the UE determines that the CPC / CPA execution condition associated to the CHO target candidate configuration (denoted here as condExecutionCondSCG-CHO-r18) is within the IE CondReconfigToAddMod in which the CHO target candidate configuration is also included. An example is shown below: – CondReconfigToAddModList The IE CondReconfigToAddModList concerns a list of conditional reconfigurations to add or modify, with for each entry the condReconfigId and the associated condExecutionCond / condExecutionCondSCG and condRRCReconfig. CondReconfigToAddModList information element -- ASN1START-- TAG-CONDRECONFIGTOADDMODLIST-START CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddMod-r16 CondReconfigToAddMod-r16 ::= SEQUENCE { condReconfigId-r16 CondReconfigId-r16, condExecutionCond-r16 SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, -- Need M condRRCReconfig-r16 OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, -- Cond condReconfigAdd ..., [[ condExecutionCondSCG-r17 OCTET STRING (CONTAINING CondReconfigExecCondSCG-r17)OPTIONAL -- Need M]] [[ condExecutionCondSCG-CHO-r18 SEQUENCE (SIZE (1..2)) OF MeasId -- Need M ]] } CondReconfigExecCondSCG-r17 ::= SEQUENCE (SIZE (1..2)) OF MeasId -- TAG-CONDRECONFIGTOADDMODLIST-STOP -- ASN1STOP In this example above, if there are multiple SCG candidates for a given CHO target candidate, there would be an instance of the IE CondReconfigToAddMod for each SCG candidate, for the same CHO target candidate cell. Below is another option: – CondReconfigToAddModList The IE CondReconfigToAddModList concerns a list of conditional reconfigurations to add or modify, with for each entry the condReconfigId and the associated condExecutionCond / condExecutionCondSCG and condRRCReconfig. CondReconfigToAddModList information element -- ASN1START -- TAG-CONDRECONFIGTOADDMODLIST-START CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddMod-r16 CondReconfigToAddMod-r16 ::= SEQUENCE { condReconfigId-r16 CondReconfigId-r16, condExecutionCond-r16 SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, -- Need M condRRCReconfig-r16 OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, -- Cond condReconfigAdd ..., [[ condExecutionCondSCG-r17 OCTET STRING (CONTAINING CondReconfigExecCondSCG-r17) OPTIONAL -- Need M ]] CondReconfigToAddModList-CPC-r18 ::= SEQUENCE (SIZE (1..X)) OF CondReconfigToAddMod-r16 } CondReconfigExecCondSCG-r17 ::= SEQUENCE (SIZE (1..2)) OF MeasId-- TAG-CONDRECONFIGTOADDMODLIST-STOP -- ASN1STOP Technical Specification Impact Some example implementations may look like below. Updates to TS 38.331 v 17.2.0: Chapter 6.3.2 (first solution as described in 2.7.1.1): – CondReconfigToAddModList The IE CondReconfigToAddModList concerns a list of conditional reconfigurations to add or modify, with for each entry the condReconfigId and the associated condExecutionCond / condExecutionCondSCG and condRRCReconfig. CondReconfigToAddModList information element -- ASN1START -- TAG-CONDRECONFIGTOADDMODLIST-START CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddMod-r16 CondReconfigToAddMod-r16 ::= SEQUENCE { condReconfigId-r16 CondReconfigId-r16, condExecutionCond-r16 SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, -- Need M condRRCReconfig-r16 OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, -- Cond condReconfigAdd ..., [[ condExecutionCondSCG-r17 OCTET STRING (CONTAINING CondReconfigExecCondSCG-r17) OPTIONAL -- Need M ]], [[ condExecutionCondExt-r18 SEQUENCE (SIZE (1..2)) OF MeasId condRRCReconfigExt-r18 OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, -- Need M ]]} CondReconfigExecCondSCG-r17 ::= SEQUENCE (SIZE (1..2)) OF MeasId-- TAG-CONDRECONFIGTOADDMODLIST-STOP-- ASN1STOPCondReconfigToAddMod field descriptions condExecutionCond The execution condition that needs to be fulfilled in order to trigger the execution of a conditional reconfiguration for CHO, CPA, intra-SN CPC without MN involvement or MN initiated inter-SN CPC. When configuring 2 triggering events (Meas Ids) for a candidate cell, network ensures that both refer to the same measObject. For CHO, if network configures condEventD1 or condEventT1 for a candidate cell network configures a second triggering event condEventA3, condEventA4 or condEventA5 for the same candidate cell. Network does not configure both condEventD1 and condEventT1 for the same candidate cell. condExecutionCondExt This field contains the second set of execution condition(s) that need to be fulfilled when two conditional reconfigurations are to be executed at the same time. If this field is present, the conditional reconfiguration is only executed if the condition(s) in condExecutionCond are also fulfilled. condExecutionCondSCG Contains execution condition that needs to be fulfilled in order to trigger the execution of a conditional reconfiguration for SN initiated inter-SN CPC. The Meas Ids refer to the measConfig associated with the SCG. When configuring 2 triggering events (Meas Ids) for a candidate cell, network ensures that both refer to the same measObject. For each condReconfigId, the network always configures either condExecutionCond or condExecutionCondSCG (not both). condRRCReconfig The RRCReconfiguration message to be applied when the condition(s) are fulfilled. The RRCReconfiguration message contained in condRRCReconfig cannot contain the field conditionalReconfiguration or the field daps-Config. condRRCReconfigExt The RRCReconfiguration message to be applied when the condition(s) in condExecutionCondExt are fulfilled. The RRCReconfiguration message contained in condRRCReconfig cannot contain the daps-Config. Conditional Presence Explanation condReconfigAdd The field is mandatory present when a condReconfigId is being added. Otherwise the field is optional, need M. Chapter 6.3.2 (second solution as described in 2.7.1.2): – CondReconfigToAddModList The IE CondReconfigToAddModList concerns a list of conditional reconfigurations to add or modify, with for each entry the condReconfigId and the associated condExecutionCond / condExecutionCondSCG and condRRCReconfig. CondReconfigToAddModList information element -- ASN1START -- TAG-CONDRECONFIGTOADDMODLIST-START CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddMod-r16 CondReconfigToAddMod-r16 ::= SEQUENCE { condReconfigId-r16 CondReconfigId-r16, condExecutionCond-r16 SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, -- Need M condRRCReconfig-r16 OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, -- Cond condReconfigAdd ..., [[condExecutionCondSCG-r17 OCTET STRING (CONTAINING CondReconfigExecCondSCG-r17) OPTIONAL -- Need M ]], condExecutionCondMCG-r18 OCTET STRING (CONTAINING CondReconfigExecCondMCG-r18) OPTIONAL -- Need M ]] } CondReconfigExecCondSCG-r17 ::= SEQUENCE (SIZE (1..2)) OF MeasId -- TAG-CONDRECONFIGTOADDMODLIST-STOP -- ASN1STOP CondReconfigToAddMod field descriptions condExecutionCond The execution condition that needs to be fulfilled in order to trigger the execution of a conditional reconfiguration for CHO, CPA, intra-SN CPC without MN involvement or MN initiated inter-SN CPC. When configuring 2 triggering events (Meas Ids) for a candidate cell, network ensures that both refer to the same measObject. For CHO, if network configures condEventD1 or condEventT1 for a candidate cell network configures a second triggering event condEventA3, condEventA4 or condEventA5 for the same candidate cell. Network does not configure both condEventD1 and condEventT1 for the same candidate cell. condExecutionCondSCG Contains execution condition that needs to be fulfilled in order to trigger the execution of a conditional reconfiguration for SN initiated inter-SN CPC. The Meas Ids refer to the measConfig associated with the SCG. When configuring 2 triggering events (Meas Ids) for a candidate cell, network ensures that both refer to the same measObject. For each condReconfigId, the network always configures either condExecutionCond or condExecutionCondSCG (not both). condExecutionCondMCG Contains execution condition that needs to be fulfilled in order to trigger the execution of a conditional reconfiguration for MN initiated inter-SN CPC contained within a conditional reconfiguration for CHO. The Meas Ids refer to the measConfig associated with the target MCG. If this field is present, the conditional reconfiguration is only executed if the condition(s) in condExecutionCond are also fulfilled condRRCReconfig The RRCReconfiguration message to be applied when the condition(s) are fulfilled. The RRCReconfiguration message contained in condRRCReconfig cannot contain the field conditionalReconfiguration or the field daps-Config. Conditional Presence Explanation condReconfigAdd The field is mandatory present when a condReconfigId is being added. Otherwise the field is optional, need M. Chapter 11.2.2 (may be applicable for both solutions except for the update of HandoverPreparationInformation which is mainly related to first solution in 2.7.1.1): – CG-CandidateList This message is used to transfer the SCG radio configuration for one or more candidate cells for Conditional PSCell Addition (CPA) or Conditional PSCell Change (CPC) as generated by the candidate target SgNB or by the candidate target MgNB. Direction: Secondary gNB to master gNB or eNB or target gNB to source gNB.CG-CandidateList message -- ASN1START -- TAG-CG-CANDIDATELIST-START CG-CandidateList ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ cg-CandidateList-r17 CG-CandidateList-r17-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } CG-CandidateList-r17-IEs ::= SEQUENCE { cg-CandidateToAddModList-r17 SEQUENCE (SIZE (1..maxNrofCondCells-r16)) OF CG- CandidateInfo-r17 OPTIONAL, cg-CandidateToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofCondCells-r16)) OF CG- CandidateInfoId-r17 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } CG-CandidateInfo-r17 ::= SEQUENCE { cg-CandidateInfoId-r17 CG-CandidateInfoId-r17, candidateCG-Config-r17 OCTET STRING (CONTAINING CG-Config) } CG-CandidateInfoId-r17::= SEQUENCE {} -- TAG-CG-CANDIDATELIST-STOP -- ASN1STOP CG-CandidateList field descriptions cg-CandidateToAddModList Contains information regarding candidate target cells to be added or modified for Conditional PSCell Addition (CPA) or Conditional PSCell Change (CPC) from the candidate target secondary node to the master node or from a candidate target master node to the source master node. cg-CandidateToReleaseList Contains information regarding candidate target cells for CPC or CPA to be removed from the candidate target secondary node to the master node or from a candidate target master node to the source master node. This list is not used in CPC or CPA preparation.CG-CandidateInfo field descriptions cg-CandidateInfoId SSB frequency and Physical Cell Identity of the candidate target cell. candidateCG-Config CG-Config message corresponding to the cell indicated by cg-CandidateInfoId. – HandoverPreparationInformation This message is used to transfer the NR RRC information used by the target gNB during handover preparation or UE context retrieval, e.g. in case of resume or re-establishment, including UE capability information. This message is also used for transferring the information between the CU and DU. Direction: source gNB / source RAN to target gNB or CU to DU. HandoverPreparationInformation message -- ASN1START -- TAG-HANDOVER-PREPARATION-INFORMATION-START HandoverPreparationInformation ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ handoverPreparationInformation HandoverPreparationInformation-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } HandoverPreparationInformation-IEs ::= SEQUENCE { ue-CapabilityRAT-List UE-CapabilityRAT-ContainerList, sourceConfig AS-Config OPTIONAL, -- Cond HO rrm-Config RRM-Config OPTIONAL, as-Context AS-Context OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } AS-Config ::= SEQUENCE { rrcReconfiguration OCTET STRING (CONTAINING RRCReconfiguration), ..., [[ sourceRB-SN-Config OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, sourceSCG-NR-Config OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, sourceSCG-EUTRA-Config OCTET STRING OPTIONAL]], [[ sourceSCG-Configured ENUMERATED {true} OPTIONAL ]], [[ sdt-Config-r17 SDT-Config-r17 OPTIONAL ]]}AS-Context ::= SEQUENCE { reestablishmentInfo ReestablishmentInfo OPTIONAL, configRestrictInfo ConfigRestrictInfoSCGOPTIONAL, ..., [[ ran-NotificationAreaInfo RAN-NotificationAreaInfo OPTIONAL ]],[[ ueAssistanceInformation OCTET STRING (CONTAINING UEAssistanceInformation) OPTIONAL -- Cond HO2 ]], [[ selectedBandCombinationSN BandCombinationInfoSNOPTIONAL ]], [[ configRestrictInfoDAPS-r16 ConfigRestrictInfoDAPS-r16OPTIONAL,sidelinkUEInformationNR-r16 OCTET STRING OPTIONAL, sidelinkUEInformationEUTRA-r16 OCTET STRING OPTIONAL, ueAssistanceInformationEUTRA-r16 OCTET STRINGOPTIONAL, ueAssistanceInformationSCG-r16 OCTET STRING (CONTAINING UEAssistanceInformation) OPTIONAL, -- Cond HO2 needForGapsInfoNR-r16 NeedForGapsInfoNR-r16 OPTIONAL ]], [[ configRestrictInfoDAPS-v1640 ConfigRestrictInfoDAPS-v1640 OPTIONAL ]], [[ needForGapNCSG-InfoNR-r17 NeedForGapNCSG-InfoNR-r17 OPTIONAL, needForGapNCSG-InfoEUTRA-r17 NeedForGapNCSG-InfoEUTRA-r17OPTIONAL,mbsInterestIndication-r17 OCTET STRING (CONTAINING MBSInterestIndication-r17) OPTIONAL ]]} ConfigRestrictInfoDAPS-r16 ::= SEQUENCE { powerCoordination-r16 SEQUENCE { p-DAPS-Source-r16 P-Max, p-DAPS-Target-r16 P-Max, uplinkPowerSharingDAPS-Mode-r16 ENUMERATED {semi-static-mode1, semi-static- mode2, dynamic } } OPTIONAL}ConfigRestrictInfoDAPS-v1640 ::= SEQUENCE { sourceFeatureSetPerDownlinkCC-r16 FeatureSetDownlinkPerCC-Id, sourceFeatureSetPerUplinkCC-r16 FeatureSetUplinkPerCC-Id}ReestablishmentInfo ::= SEQUENCE {}RRM-Config ::= SEQUENCE { ue-InactiveTime ENUMERATED { s1, s2, s3, s5, s7, s10, s15, s20, s25, s30, s40, s50, min1, min1s20, min1s40,min2, min2s30, min3, min3s30, min4, min5, min6, min7, min8, min9, min10, min12, min14, min17, min20, min24, min28, min33, min38, min44, min50, hr1, hr1min30, hr2, hr2min30, hr3, hr3min30, hr4, hr5, hr6, hr8, hr10, hr13, hr16, hr20, day1, day1hr12, day2, day2hr12, day3, day4, day5, day7, day10, day14, day19, day24, day30, dayMoreThan30} OPTIONAL, candidateCellInfoList MeasResultList2NR OPTIONAL, ..., [[ candidateCellInfoListSN-EUTRA MeasResultServFreqListEUTRA-SCG OPTIONAL ]],[[ measConfig MeasConfig OPTIONAL, -- Need M ]]-- TAG-HANDOVER-PREPARATION-INFORMATION-STOP -- ASN1STOP HandoverPreparationInformation field descriptions as-Context Local RAN context required by the target gNB or DU. rrm-Config Local RAN context used mainly for RRM purposes. sourceConfig The radio resource configuration as used in the source cell. ue-CapabilityRAT-List The UE radio access related capabilities concerning RATs supported by the UE. A gNB that retrieves MRDC related capability containers ensures that the set of included MRDC containers is consistent w.r.t. the feature set related information. ue-InactiveTime Duration while UE has not received or transmitted any user data. Thus the timer is still running in case e.g., UE measures the neighbour cells for the HO purpose. Value s1 corresponds to 1 second, s2 corresponds to 2 seconds and so on. Value min1 corresponds to 1 minute, value min1s20 corresponds to 1 minute and 20 seconds, value min1s40 corresponds to 1 minute and 40 seconds and so on. Value hr1 corresponds to 1 hour, hr1min30 corresponds to 1 hour and 30 minutes and so on. AS-Config field descriptions rrcReconfiguration Contains the RRCReconfiguration configuration as generated entirely by the MN. sdt-Config Contains the IE SDT-Config as generated entirely by the last serving gNB. This field is only used during the SDT procedure with UE context relocation as defined in TS 38.300 [2], clause 18.2. sourceRB-SN-Config Contains the IE RadioBearerConfig as generated entirely by the SN. This field is only used when the UE is configured with SN terminated RB(s). sourceSCG-Configured Value true indicates that the UE is configured with NR or EUTRA SCG in source configuration. The field is only used in NR-DC and NE-DC and is included only if the fields sourceSCG-NR-Config and sourceSCG-EUTRA-Config are absent. sourceSCG-EUTRA-Config Contains the current dedicated SCG configuration in RRCConnectionReconfiguration message as specified in TS 36.331

[0010] and generated entirely by the SN. In this version of the specification, the E-UTRA RRCConnectionReconfiguration message can only include the field scg-Configuration . This field is only used in NE- DC. sourceSCG-NR-Config Contains the current dedicated SCG configuration in RRCReconfiguration message as generated entirely by the SN. In this version of the specification, the RRCReconfiguration message can only include fields secondaryCellGroup and measConfig. This field is only used in NR-DC.AS-Context field descriptions configRestrictInfoDAPS Includes fields for which source cell explicitly indicates the restriction to be observed by target cell during DAPS handover. mbsInterestIndication Includes the information last reported by the UE in the NR MBSInterestIndication message, where the plmn-Index (if included by the UE in tmgi) is replaced by the PLMN ID, if any. needForGapsInfoNR Includes measurement gap requirement information of the UE for NR target bands. selectedBandCombinationSN Indicates the band combination selected by SN in (NG)EN-DC, NE-DC, and NR-DC. sidelinkUEInformationEUTRA This field includes SidelinkUEInformation IE as specified in TS 36.331

[0010] . sidelinkUEInformationNR This field includes SidelinkUEInformationNR IE. ueAssistanceInformation Includes for each UE assistance feature the information last reported by the UE, if any. ueAssistanceInformationSCG Includes for each UE assistance feature associated with the SCG, the information last reported by the UE in the NR UEAssistanceInformation message for the SCG, if any. ConfigRestrictInfoDAPS field descriptions sourceFeatureSetPerUplinkCC / sourceFeatureSetPerDownlinkCC Indicates an index referring to the position of the FeatureSetUplinkPerCC / FeatureSetDownlinkPerCC selected by source in the featureSetsUplinkPerCC / featureSetsDownlinkPerCC. RRM-Config field descriptions candidateCellInfoList A list of the best cells on each frequency for which measurement information was available candidateCellInfoListSN-EUTRA A list of EUTRA cells including serving cells and best neighbour cells on each serving frequency, for which measurement results were available. This field is only used in NE-DC. measConfig Includes the measConfig of the MCG. Conditional Presence Explanation HO The field is mandatory present in case of handover within NR or UE context retrieval, e.g. in case of resume or re-establishment. The field is optionally present in case of handover from E-UTRA / 5GC. Otherwise the field is absent. HO2 The field is optionally present in case of handover within NR; otherwise the field is absent. NOTE 1: The following table indicates per source RAT whether RAT capabilities are included or not.Source RAT NR capabilities E-UTRA capabilities MR-DC capabilities UTRA capabilities NR May be included if UE May be included May be included May be included, Radio Capability ID as ignored by gNB if specified in 23.502

[0043] is received used for the UE. Included otherwise. E-UTRAN May be included if UE May be included May be included May be included, Radio Capability ID as ignored by gNB if specified in 23.502

[0043] is received used for the UE. Included otherwise. NOTE 2: The following table indicates, in case of inter-RAT handover from E-UTRA, which additional IEs are included or not: Source system sourceConfig rrm-Config as-Context E-UTRA / EPC Not included May be included Not included E-UTRA / 5GC May be included, but only May be included Not included radioBearerConfig is included in the RRCReconfiguration. – CG-Config This message is used to transfer the SCG radio configuration as generated by the SgNB or SeNB. It can also be used by a CU to request a DU to perform certain actions, e.g. to request the DU to perform a new lower layer configuration. Direction: Secondary gNB or eNB to master gNB or eNB, alternatively CU to DU, or target gNB to source gNB. CG-Config message An example implementation in TS 38.423 v 17.2.0 in HANDOVER REQUEST and HANDOVER REQUEST ACKNOWLEDGE may look like below. Similar updates may be done in other messages and messages in TS 38.314, 38.473 and 38.463. The updates may be applicable for both solutions. 9.1.1.1 HANDOVER REQUEST This message is sent by the source NG-RAN node to the target NG-RAN node to request the preparation of resources for a handover. Direction: source NG-RAN node ^ target NG-RAN node.IE / Group Name Presenc Range IE type Semantics Criticalit Assigned e and description y Criticality reference Message Type M 9.2.3.1 YES reject Source NG-RAN node UE M NG-RAN Allocated at the YES reject XnAP ID reference node UE source NG-RAN XnAP ID node 9.2.3.16 Cause M 9.2.3.2 YES reject Target Cell Global ID M 9.2.3.25 Includes either an YES reject E-UTRA CGI or an NR CGI GUAMI M 9.2.3.24 YES reject UE Context Information 1 YES reject >NG-C UE associated M AMF UE Allocated at the – Signalling reference NGAP ID AMF on the 9.2.3.26 source NG-C connection. >Signalling TNL M CP This IE indicates – association address at Transport the AMF’s IP source NG-C side Layer address of the Information SCTP association 9.2.3.31 used at the source NG-C interface instance. Note: If no UE TNLA binding exists at the source NG-RAN node, the source NG-RAN node indicates the TNL association address it would have selected if it would have had to create a UE TNLA binding. >UE Security Capabilities M 9.2.3.49 – >AS Security Information M 9.2.3.50 – >Index to O 9.2.3.23 – RAT / Frequency Selection Priority >UE Aggregate M 9.2.3.17 – Maximum Bit Rate>PDU Session 1 9.2.1.1 Similar to NG-C – Resources To Be Setup signalling, List containing UL tunnel information per PDU Session Resource; and in addition, the source side QoS flow ^ DRB mapping >RRC Context M OCTET Either includes – STRING the HandoverPrepara tionInformation message as defined in subclause 10.2.2. of TS 36.331

[0014] , or the HandoverPrepara tionInformation- NB message as defined in subclause 10.6.2 of TS 36.331

[0014] , if the target NG- RAN node is an ng-eNB, or the HandoverPrepara tionInformation message as defined in subclause 11.2.2 of TS 38.331

[0010] , if the target NG- RAN node is a gNB. >Location Reporting O 9.2.3.47 Includes the – Information necessary parameters for location reporting. >Mobility Restriction List O 9.2.3.53 – >5GC Mobility Restriction O 9.2.3.100 YES ignore List Container>NR UE Sidelink O 9.2.3.107 This IE applies YES ignore Aggregate Maximum Bit only if the UE is Rate authorized for NR V2X services. >LTE UE Sidelink O 9.2.3.108 This IE applies YES ignore Aggregate Maximum Bit only if the UE is Rate authorized for LTE V2X services. >Management Based O MDT PLMN YES ignore MDT PLMN List List 9.2.3.133 >UE Radio Capability ID O 9.2.3.138 YES reject >MBS Session O 9.2.1.36 YES ignore Information List >5G ProSe UE PC5 O NR UE This IE applies YES ignore Aggregate Maximum Bit Sidelink only if the UE is Rate Aggregate authorized for 5G Maximum ProSe services. Bit Rate 9.2.3.107 >UE Slice Maximum Bit O 9.2.3.167 YES ignore Rate List Trace Activation O 9.2.3.55 YES ignore Masked IMEISV O 9.2.3.32 YES ignore UE History Information M 9.2.3.64 YES ignore UE Context Reference at O YES ignore the S-NG-RAN node >Global NG-RAN Node M 9.2.2.3 – ID >S-NG-RAN node UE M NG-RAN – XnAP ID node UE XnAP ID 9.2.3.16 Conditional Handover O YES reject Information Request >CHO Trigger M ENUMERA – TED (CHO- initiation, CHO- replace, …) >Target NG-RAN node C- NG-RAN Allocated at the – UE XnAP ID ifCHOmo node UE target NG-RAN d XnAP ID node 9.2.3.16>Estimated Arrival O INTEGER – Probability (1..100) NR V2X Services O 9.2.3.105 YES ignore Authorized LTE V2X Services O 9.2.3.106 YES ignore Authorized PC5 QoS Parameters O 9.2.3.109 This IE applies YES ignore only if the UE is authorized for NR V2X services. Mobility Information O BIT Information YES ignore STRING related to the (SIZE (32)) handover; the source NG-RAN node provides it in order to enable later analysis of the conditions that led to a wrong HO. UE History Information O 9.2.3.110 YES ignore from the UE IAB Node Indication O ENUMERA YES reject TED (true, ...) No PDU Session O ENUMERA This IE applies YES ignore Indication TED only if the UE is (true, ...) an IAB-MT. Time Synchronisation O 9.2.3.153 YES ignore Assistance Information QMC Configuration O 9.2.3.156 YES ignore Information 5G ProSe Authorized O 9.2.3.159 YES ignore 5G ProSe PC5 QoS O 9.2.3.160 This IE applies YES ignore Parameters only if the UE is authorized for 5G ProSe services. Conditional PSCell O YES reject Addition Information Request >Maximum Number of M INTEGER Indicates the – PSCells To Prepare (1..8, ...) maximum number of PSCells that the target MN may prepare.Condition Explanation ifCHOmod This IE shall be present if the CHO Trigger IE is present and set to "CHO-replace". Range bound Explanation maxnoofMDTPLMNs PLMNs in the Management Based MDT PLMN list. Value is 16. 9.1.1.2 HANDOVER REQUEST ACKNOWLEDGE This message is sent by the target NG-RAN node to inform the source NG-RAN node about the prepared resources at the target. Direction: target NG-RAN nodesource NG-RAN node.IE / Group Name Presence Range IE type and Semantics Criticalit Assigned reference description y Criticality Message Type M 9.2.3.1 YES reject Source NG-RAN node UE M NG-RAN Allocated at the YES ignore XnAP ID node UE source NG-RAN XnAP ID node 9.2.3.16 Target NG-RAN node UE M NG-RAN Allocated at the YES ignore XnAP ID node UE target NG-RAN XnAP ID node 9.2.3.16 PDU Session Resources M 9.2.1.2 YES ignore Admitted List PDU Session Resources O 9.2.1.3 YES ignore Not Admitted List Target NG-RAN node To M OCTET Either includes the YES ignore Source NG-RAN node STRING HandoverCommand Transparent Container message as defined in subclause 10.2.2 of TS 36.331

[0014] , if the target NG-RAN node is an ng-eNB, or the HandoverCommand message as defined in subclause 11.2.2 of TS 38.331

[0010] , if the target NG-RAN node is a gNB. UE Context Kept Indicator O 9.2.3.68 YES ignore Criticality Diagnostics O 9.2.3.3 YES ignore DRBs transferred to MN O DRB List In case of DC, YES ignore 9.2.1.29 indicates that SN Status is needed for the listed DRBs from the S-NG-RAN node. DAPS Response O 9.2.1.34 YES reject Information Conditional Handover O YES reject Information Acknowledge>Requested Target Cell M Target Cell Target cell indicated – ID Global ID in the 9.2.3.25 corresponding HANDOVER REQUEST message >Maximum Number of O 9.2.3.101 – CHO Preparations MBS Session Information O 9.2.1.38 YES ignore Response List Conditional PSCell O YES ignore Addition Information Acknowledge >Candidate PSCell List 1 – >>Candidate PSCell Item 1.. – <maxno ofPSCel lCandid ate> >>>PSCell ID M NR – CGI 9.2.2.7 >>>Target NG-RAN node M OCTET Includes the CG- YES ignore To Source NG-RAN node STRING CandidateList Container for candidate message as PSCell defined in subclause 11.2.2 of TS 38.331

[0010] . For RRC impact please check the additions in the previous sections. Methods FIG.8 depicts the steps in a method 10 executed by a UE operative in a wireless communication system. The method is one of performing CHO with one of an associated CPC or CPA. A message including a CHO configuration including at least a CHO target candidate cell configuration and associated CHO execution condition is received from a network node (block 12). The CHO target candidate cell configuration is associated with a CPC or CPA configuration including a CPC or CPA target candidate configuration and associated CPC or CPA execution condition. The CPC or CPA execution condition comprises at least one measurement identity associated with one of an MCG measurement configuration in the UE’s current configuration and an MCG measurement configuration within the CHO target candidate cell configuration. Whether the CHO execution condition is fulfilled is evaluated (block 14). In response to the CHO execution condition being fulfilled, the CHO target candidate cellconfiguration is applied (block 16). Whether the CPC or CPA execution condition is fulfilled is evaluated (block 18). In response to the CPC or CPA execution condition being fulfilled, the candidate CPC or CPA target candidate configuration associated with the CHO target candidate cell configuration is applied (block 20). FIG.9 depicts the steps in a method 20 executed by a network node operative in a wireless communication network. The network node is configured and acts as an S-MN for a UE. The method is one of performing CHO of the UE with one of an associated CPC or CPA. It is determined to configure CHO for the UE towards a candidate T-MN, wherein the CHO is associated with a CPA candidate cell, for a UE not in MR-DC, or CPC candidate cell, for a UE in MR-DC (block 22). A message containing a request for CHO is transmitted to the candidate T-MN (block 24). A message is received from the candidate T-MN containing a target configuration for a CHO candidate cell and an associated CPC or CPA candidate configuration comprising executions conditions and target configurations for the CPC or CPA (block 26). A reconfiguration message containing the configuration of CHO and associated CPC or CPA configuration is transmitted to the UE (block 28). A reply is received from the UE (block 29). FIG.10 depicts the steps in a method 30 executed by a network node operative in a wireless communication network. The network node is configured and acts as a T-MN for a UE. The method is one of performing CHO of the UE with one of an associated CPC or CPA. A message is received from an S-MN, the message containing a request for CHO with associated configuration of CPC or CPA (block 32). It is determined to accept CHO configuration with associated CPC or CPA configuration (block 34). A target CHO configuration is prepared (block 36). A configuration of CPC or CPA is triggered (block 38). In response to a candidate target PSCell belonging to a different T-SN, a message containing a request to configure CPC or CPA is transmitted to the T-SN (block 40). In response to sending the message to the T-SN, a reply containing a target CPC or CPA configuration is received from the T-SN (block 42). Executions conditions for the CPC or CPA are prepared (block 44). A message containing the target configuration for CHO and a CPC or CPA configuration comprising execution conditions and a target CPC or CPA configuration is transmitted to the S-MN (block 46). Network and Apparatus Descriptions, and Over the Top Operation Additional aspects of the disclosure will now be described. At least some of these aspects may be described as applicable in certain contexts and / or wireless network types for illustrative purposes, but the aspects are similarly applicable in other contexts and / or wireless network types not explicitly described. FIG.11 shows an example of a communication system 1100 in accordance with some aspects.In the example, the communication system 1100 includes a telecommunication network 1102 that includes an access network 1104, such as a radio access network (RAN), and a core network 1106, which includes one or more core network nodes 1108. The access network 1104 includes one or more access network nodes, such as network nodes 1110a and 1110b (one or more of which may be generally referred to as network nodes 1110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 1110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1112a, 1112b, 1112c, and 1112d (one or more of which may be generally referred to as UEs 1112) to the core network 1106 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different aspects, the communication system 1100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system. The UEs 1112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 1110 and other communication devices. Similarly, the network nodes 1110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 1112 and / or with other network nodes or equipment in the telecommunication network 1102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 1102. In the depicted example, the core network 1106 connects the network nodes 1110 to one or more hosts, such as host 1116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1106 includes one more core network nodes (e.g., core network node 1108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF),Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF). The host 1116 may be under the ownership or control of a service provider other than an operator or provider of the access network 1104 and / or the telecommunication network 1102, and may be operated by the service provider or on behalf of the service provider. The host 1116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server. As a whole, the communication system 1100 of FIG.11 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z- Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. In some examples, the telecommunication network 1102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1102. For example, the telecommunications network 1102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive IoT services to yet further UEs. In some examples, the UEs 1112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1104. Additionally, a UE may beconfigured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC). In the example, the hub 1114 communicates with the access network 1104 to facilitate indirect communication between one or more UEs (e.g., UE 1112c and / or 1112d) and network nodes (e.g., network node 1110b). In some examples, the hub 1114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1114 may be a broadband router enabling access to the core network 1106 for the UEs. As another example, the hub 1114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1110, or by executable code, script, process, or other instructions in the hub 1114. As another example, the hub 1114 may be a data collector that acts as temporary storage for UE data and, in some aspects, may perform analysis or other processing of the data. As another example, the hub 1114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices. The hub 1114 may have a constant / persistent or intermittent connection to the network node 1110b. The hub 1114 may also allow for a different communication scheme and / or schedule between the hub 1114 and UEs (e.g., UE 1112c and / or 1112d), and between the hub 1114 and the core network 1106. In other examples, the hub 1114 is connected to the core network 1106 and / or one or more UEs via a wired connection. Moreover, the hub 1114 may be configured to connect to an M2M service provider over the access network 1104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1110 while still connected via the hub 1114 via a wired or wireless connection. In some aspects, the hub 1114 may be a dedicated hub – that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1110b. In other aspects, the hub 1114 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 1110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.FIG.12 is a hardware block diagram of a wireless device 1112 operative in a wireless communication network 1100, as implemented in accordance with one or more aspects of the present disclosure. A wireless device 1112 is any type of device capable of communicating with a network node 1110 and / or access point using radio signals. A wireless device 1112 may therefore refer to a machine-to-machine (M2M) device, a machine-type communications (MTC) device, a Narrowband Internet of Things (NB IoT) device, etc. The wireless device 1112 may also be referred to as a User Equipment (UE), such as a cellular telephone or “smartphone,” however, the term UE should be understood to encompass any wireless device 1112. A wireless device 1112 may also be referred to as a radio device, a radio communication device, a wireless device, a wireless terminal, or simply a terminal – unless the context indicates otherwise, the use of any of these terms is intended to include device-to-device UEs or devices, machine-type devices, or devices capable of machine-to-machine communication, sensors equipped with a wireless device, wireless-enabled table computers, mobile terminals, smart phones, laptop- embedded equipped (LEE), laptop-mounted equipment (LME), USB dongles, wireless customer- premises equipment (CPE), etc. In the discussion herein, the terms machine-to-machine (M2M) device, machine-type communication (MTC) device, wireless sensor, and sensor may also be used. It should be understood that these devices, although referred to as UEs, but may be configured to transmit and / or receive data without direct human interaction. In some aspects, the wireless device 1112 includes a user interface 1118 (display, touchscreen, keyboard or keypad, microphone, speaker, and the like); in other aspects, such as in many M2M, MTC, or NB IoT scenarios, the wireless device 1112 may include only a minimal, or no, user interface 1118 (as indicated by the dashed lines of block 1118 in FIG.12). The wireless device 1112 also includes processing circuitry 1120; memory 1122; and communication circuitry 1124 to effect wireless communication across an air interface to one or more radio network nodes 1110, such as a base station, and / or access points. The communication circuitry 1124 is connected to one or more antennas 1128. As indicated by the dashed lines, the antenna(s) 1128 may protrude externally from the wireless device 1112, or the antenna array 1128 may be internal. In some aspects, a wireless device 1112 may include a sophisticated user interface 1118, and may additionally include features such as a camera, accelerometer, satellite navigation signal receiver circuitry, vibrating motor, and the like (not depicted in FIG.12). FIG.13 is a hardware block diagram of a network node 1110 operative in a wireless communication network 1100, and configured to operate as a base station, as implemented in accordance with one or more aspects of the present disclosure. The base station 1110 may serve as a S-MN, T-MS, S-SN, T-SN, or the like, and may operate as a PCell, SCell, PSCell, or thelike for a UE 1112. The base station 1110 includes processing circuitry 1130; memory 1132; and communication circuitry 1134 to effect wireless communication across an air interface to one or more wireless devices 1112. The communication circuitry 1134 is connected to one or more antennas 1136. As indicated by the broken connection to the antenna(s) 1136, the antenna(s) 1136 may be physically located separately from the base station 1110, such as mounted on a tower, building, or the like. Although the memory 1132 is depicted as being internal to the processing circuitry 1130, those of skill in the art understand that the memory 1132 may also be external. Those of skill in the art additionally understand that virtualization techniques allow some functions nominally executed by the processing circuitry 1130 to actually be executed by other hardware, perhaps remotely located (e.g., in the so-called “cloud”). The base station 1110 is known in LTE as an eNodeB or eNB, and in New Radio (NR) as gNB. In general, in other wireless communication networks, the base station 1110 may be known as a Radio Base Station, Base Transceiver Station, Access Point, or the like. Note that apparatuses described herein may perform the methods 10, 20, 30 herein and any other processing by implementing any functional means, modules, units, or circuitry. In one aspect, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and / or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several aspects. In aspects that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein. Those skilled in the art will also appreciate that aspects herein further include corresponding computer programs. A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described herein. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.Aspects further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium. In this regard, aspects herein also include a computer program product stored on a non- transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above. Aspects further include a computer program product comprising program code portions for performing the steps of any of the aspects herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium. FIG.14 is a block diagram of a host 1400, which may be an aspect of the host 1116 of FIG.11, in accordance with various aspects described herein. As used herein, the host 1400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1400 may provide one or more services to one or more UEs. The host 1400 includes processing circuitry 1402 that is operatively coupled via a bus 1404 to an input / output interface 1406, a network interface 1408, a power source 1410, and a memory 1412. Other components may be included in other aspects. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such that the descriptions thereof are generally applicable to the corresponding components of host 1400. The memory 1412 may include one or more computer programs including one or more host application programs 1414 and data 1416, which may include user data, e.g., data generated by a UE for the host 1400 or data generated by the host 1400 for a UE. Aspects of the host 1400 may utilize only a subset or all of the components shown. The host application programs 1414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1400 may select and / orindicate a different host for over-the-top services for a UE. The host application programs 1414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc. FIG.15 shows a communication diagram of a host 1602 communicating via a network node 1604 with a UE 1606 over a partially wireless connection in accordance with some aspects. Example implementations, in accordance with various aspects, of the UE (such as a UE 1112a of FIG.11), network node (such as network node 1110a of FIG.11), and host (such as host 1116 of FIG.11) discussed in the preceding paragraphs will now be described with reference to FIG.15. Like host 1400, aspects of host 1602 include hardware, such as a communication interface, processing circuitry, and memory. The host 1602 also includes software, which is stored in or accessible by the host 1602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1606 connecting via an over-the-top (OTT) connection 1650 extending between the UE 1606 and host 1602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1650. The network node 1604 includes hardware enabling it to communicate with the host 1602 and UE 1606. The connection 1660 may be direct or pass through a core network (like core network 1106 of FIG.11) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. The UE 1606 includes hardware and software, which is stored in or accessible by UE 1606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1606 with the support of the host 1602. In the host 1602, an executing host application may communicate with the executing client application via the OTT connection 1650 terminating at the UE 1606 and host 1602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1650. The OTT connection 1650 may extend via a connection 1660 between the host 1602 and the network node 1604 and via a wireless connection 1670 between the network node 1604 and the UE 1606 to provide the connection between the host 1602 and the UE 1606. The connection 1660 and wireless connection 1670, over which the OTT connection 1650 may beprovided, have been drawn abstractly to illustrate the communication between the host 1602 and the UE 1606 via the network node 1604, without explicit reference to any intermediary devices and the precise routing of messages via these devices. As an example of transmitting data via the OTT connection 1650, in step 1608, the host 1602 provides user data, which may be performed by executing a host application. In some aspects, the user data is associated with a particular human user interacting with the UE 1606. In other aspects, the user data is associated with a UE 1606 that shares data with the host 1602 without explicit human interaction. In step 1610, the host 1602 initiates a transmission carrying the user data towards the UE 1606. The host 1602 may initiate the transmission responsive to a request transmitted by the UE 1606. The request may be caused by human interaction with the UE 1606 or by operation of the client application executing on the UE 1606. The transmission may pass via the network node 1604, in accordance with the teachings of the aspects described throughout this disclosure. Accordingly, in step 1612, the network node 1604 transmits to the UE 1606 the user data that was carried in the transmission that the host 1602 initiated, in accordance with the teachings of the aspects described throughout this disclosure. In step 1614, the UE 1606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1606 associated with the host application executed by the host 1602. In some examples, the UE 1606 executes a client application which provides user data to the host 1602. The user data may be provided in reaction or response to the data received from the host 1602. Accordingly, in step 1616, the UE 1606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 1606. Regardless of the specific manner in which the user data was provided, the UE 1606 initiates, in step 1618, transmission of the user data towards the host 1602 via the network node 1604. In step 1620, in accordance with the teachings of the aspects described throughout this disclosure, the network node 1604 receives user data from the UE 1606 and initiates transmission of the received user data towards the host 1602. In step 1622, the host 1602 receives the user data carried in the transmission initiated by the UE 1606. One or more of the various aspects improve the performance of OTT services provided to the UE 1606 using the OTT connection 1650, in which the wireless connection 1670 forms the last segment. More precisely, the teachings of these aspects may improve conditional handoff of multiple aggregated carriers, and thereby provide benefits such as fewer dropped connections, improved robustness to poor channel conditions, better throughput, greater user-perceived quality, and improved battery life by eliminating re-acquisition procedures. In an examplescenario, factory status information may be collected and analyzed by the host 1602. As another example, the host 1602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1602 may collect and analyze real- time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1602 may store surveillance video uploaded by a UE. As another example, the host 1602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data. In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more aspects improve. There may further be an optional network functionality for reconfiguring the OTT connection 1650 between the host 1602 and UE 1606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1602 and / or UE 1606. In some aspects, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1604. Such procedures and functionalities may be known and practiced in the art. In certain aspects, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1650 while monitoring propagation times, errors, etc. Advantages of the Proposed Solution Aspects of the present disclosure make it possible to configure execution conditions for CHO and CPC (one or more measId(s) associated to a candidate SCG configuration(s)) to be evaluated concurrently (in parallel) while the UE is still connected to the PCell and where the UE chooses the best PSCell when the CHO conditions are fulfilled. This decreases the risk of SCG failure in case the most suitable PSCell is not the same as when CHO was configured. Thesolution also ensures this is done without exceeding any UE capabilities related to monitoring of execution conditions. Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc., are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the aspects disclosed herein may be applied to any other aspect, wherever appropriate. Likewise, any advantage of any of the aspects may apply to any other aspects, and vice versa. Other objectives, features and advantages of the enclosed aspects will be apparent from the description. The term “unit” may have conventional meaning in the field of electronics, electrical devices and / or electronic devices and may include, for example, electrical and / or electronic circuitry, devices, modules, processors, memories, logic solid state and / or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and / or displaying functions, and so on, as such as those that are described herein. As used herein, the term “configured to” means set up, organized, adapted, or arranged to operate in a particular way; the term is synonymous with “designed to,” or with respect to processing circuitry, “programmed to.” Some of the aspects contemplated herein are described more fully with reference to the accompanying drawings. Other aspects, however, are contained within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as limited to only the aspects set forth herein; rather, these aspects are provided by way of example to convey the scope of the subject matter to those skilled in the art. The present disclosure may, of course, be carried out in other ways than those specifically set forth herein without departing from essential characteristics of the disclosure. The present aspects are to be considered in all respects as illustrative and not restrictive, and all changes coming within the meaning and equivalency range of the appended aspects are intended to be embraced therein.

Claims

CLAIMS What is claimed is:

1. A method (10), performed by a user equipment, UE (1112), operative in a wireless communication network (1100), for performing Conditional Handover, CHO, with one of an associated candidate PSCell, or candidate Secondary Cell Group, SCG, the method (10) characterized by: receiving (12), from a network node (1110), a message including a CHO configuration including at least a CHO target candidate cell configuration and associated CHO execution condition; wherein the CHO target candidate cell configuration is associated with a target candidate PSCell or target candidate SCG configuration and a PSCell or SCG execution condition, the PSCell or SCG execution condition comprising at least one measurement identity associated with one of a Master Cell Group, MCG, measurement configuration in the UE’s current configuration; evaluating (14) whether the CHO execution condition is fulfilled; and evaluating (16) whether the PSCell or SCG execution condition is fulfilled; in response to the CHO execution condition being fulfilled, applying (18) the CHO target candidate cell configuration; in response to the PSCell or SCG execution condition being fulfilled, applying (19) the target candidate PSCell or target candidate SCG configuration associated with the CHO target candidate cell configuration.

2. The method (10) of claim 1 wherein the message including the CHO configuration is an RRC Reconfiguration message.

3. The method (10) of any preceding claim wherein the PSCell or SCG execution condition comprises one or more measId(s) associated to the target candidate PSCell or target candidate SCG configuration.

4. The method (10) of any preceding claim wherein an MCG measurement configuration in the UE’s current configuration comprises a Source Master Node, S-MN, (1110) MeasConfig in the MCG VarMeasConfig.

5. The method (10) of any preceding claim wherein the CHO target candidate cell configuration is associated with a candidate PSCell or candidate SCG configuration by beingincluded with the CHO target candidate cell configuration.

6. The method (10) of any preceding claim wherein evaluating (18) whether the PSCell or SCG execution condition is fulfilled is performed only after determining that the CHO execution condition is fulfilled.

7. A User Equipment, UE (1112), operative in a wireless communication network (1100), characterized by: communication circuitry (1124) configured to wirelessly communicate with one or more network nodes (1110); and processing circuitry (1120) operatively connected to the communication circuitry (1124) and configured to receive (12), from a network node (1110), a message including a Conditional Handover, CHO, configuration including at least a CHO target candidate cell configuration and associated CHO execution condition; wherein the CHO target candidate cell configuration is associated with a target candidate PSCell or target candidate Secondary Cell Group, SCG, configuration including a PSCell or SCG target candidate configuration and associated PSCell or SCG execution condition, the PSCell or SCG execution condition comprising at least one measurement identity associated with a Master Cell Group, MCG, measurement configuration in the UE’s current configuration; evaluate (14) whether the CHO execution condition is fulfilled; evaluate (18) whether the PSCell or SCG execution condition is fulfilled; in response to the CHO execution condition being fulfilled, apply (16) the CHO target candidate cell configuration; and in response to the PSCell or SCG execution condition being fulfilled, apply (20) the target candidate PSCell or target candidate SCG configuration associated with the CHO target candidate cell configuration.

8. The UE (1112) of claim 7 wherein the message including the CHO configuration is an RRC Reconfiguration message.

9. The UE (1112) of any of claims 7-8 wherein the PSCell or SCG execution condition comprises one or more measId(s) associated to the target candidate PSCell or target candidateSCG configuration.

10. The UE (1112) of any of claims 7-9 wherein an MCG measurement configuration in the UE (1112)’s current configuration comprises a Source Master Node, S-MN, (1110) MeasConfig in the MCG VarMeasConfig.

11. The UE (1112) of any of claims 7-10 wherein the CHO target candidate cell configuration is associated with a candidate PSCell or candidate SCG configuration by being included with the CHO target candidate cell configuration.

12. The UE (1112) of any of claims 7-11 wherein the processing circuitry (1120) is configured to evaluate (18) whether the PSCell or SCG execution condition is fulfilled only after determining that the CHO execution condition is fulfilled.

13. A method (20), performed by a network node (1110) operative in a wireless communication network (1100) and acting as a Source Master Node, S-MN, (1110) for a user equipment, UE, (1112) for performing Conditional Handover, CHO, of the UE (1112) with one of an associated candidate PSCell or candidate Secondary Cell Group, SCG, the method (20) characterized by: determining (22) to configure CHO for the UE (1112) towards a candidate Target Master Node, T-MN (1110); transmitting (24) a message containing a request for CHO to the candidate T-MN (1110); receiving (26) a message from the candidate T-MN (1110) containing a target configuration for a CHO candidate cell and an associated configuration for a candidate PSCell or candidate SCG and one or more parameters related to a PSCell or SCG execution condition; transmitting (28), to the UE (1112), a reconfiguration message containing the configuration of CHO and associated PSCell or SCG configuration; and receiving (29) a reply from the UE (1112).

14. The method (20) of claim 13 wherein determining (22) to configure the CHO comprises being aware of the UE capabilities for CHO with candidate PSCell or candidate SCG, and determining to configure the CHO based on the UE (1112) capabilities.

15. The method (20) of any of claims 13-14 wherein determining (22) to configure the CHOcomprises determining to indicate to the candidate T-MN (1110) that the S-MN (1110) wishes to configure CHO including a candidate PSCell or SCG configuration and execution condition.

16. The method (20) of any of claims 13-15 wherein determining (22) to configure the CHO comprises receiving from the T-MN (1110) a CHO target candidate configuration including an associated PSCell configuration or associated SCG configuration.

17. The method (20) of any of claims 13-16 wherein transmitting (24) a message containing a request for CHO to the candidate T-MN (1110) comprises transmitting a message containing the current MCG configuration of the UE (1112).

18. The method (20) of any of claims 13-17 wherein the message further contains a current SCG configuration of the UE (1112).

19. The method (20) of any of claims 13-18 wherein transmitting (24) a message containing a request for CHO to the candidate T-MN (1110) comprises transmitting a message containing a maximum number of PSCell or SCG configurations that the T-MN (1110) may prepare.

20. The method (20) of any of claims 13-19 wherein transmitting (24) a message containing a request for CHO to the candidate T-MN (1110) comprises transmitting a message containing a current S-MN measConfig of the UE (1112).

21. The method (20) of any of claims 13-20 wherein transmitting (24) a message containing a request for CHO to the candidate T-MN (1110) comprises transmitting a message containing UE (1112) capability information related to CHO with PSCell or SCG, and / or UE (1112) ability to perform measurements and evaluate execution conditions.

22. The method (20) of any of claims 13-21 wherein receiving (26) a message from the candidate T-MN (1110) comprises receiving a message including information regarding the number of PSCell or SCG configurations that have been configured.

23. The method (20) of claim 22 further comprising cancelling some configurations if they exceed the UE (1112) capabilities.

24. A network node (1110) operative in a wireless communication network (1100) and actingas a Source Master Node, S-MN (1110), for a user equipment, UE (1112), for performing Conditional Handover, CHO, of the UE (1112) with one of an associated candidate PSCell or candidate Secondary Cell Group, SCG, characterized by: communication circuitry (1134) configured to wirelessly communicate with one or more UEs (1112); and processing circuitry (1130) operatively connected to the communication circuitry (1134) and configured to determine (22) to configure CHO for the UE (1112) towards a candidate Target Master Node, T-MN (1110); transmit (24) a message containing a request for CHO to the candidate T-MN (1110); receive (26) a message from the candidate T-MN (1110) containing a target configuration for a CHO candidate cell and an associated configuration for a candidate PSCell or candidate SCG and one or more parameters related to a PSCell or SCG execution condition; transmit (28), to the UE (1112), a reconfiguration message containing the configuration of CHO and associated PSCell or SCG configuration; and receive (29) a reply from the UE (1112).

25. The S-MN (1110) of claim 24 wherein the processing circuitry (1130) is configured to determine (22) to configure the CHO by being aware of the UE (1112) capabilities for CHO with candidate PSCell or SCG, and determining to configure the CHO based on the UE (1112) capabilities.

26. The S-MN (1110) of any of claims 24-25 wherein the processing circuitry (1130) is configured to determine (22) to configure the CHO by determining to indicate to the candidate T-MN (1110) that the S-MN (1110) wishes to configure CHO including a candidate PSCell or candidate SCG configuration and execution condition.

27. The S-MN (1110) of any of claims 24-26 wherein the processing circuitry (1130) is configured to determine (22) to configure the CHO by receiving from the T-MN (1110) a CHO target candidate configuration including an associated PSCell configuration or associated SCG configuration.

28. The S-MN (1110) of any of claims 24-27 wherein the processing circuitry (1130) is configured to transmit (24) a message containing a request for CHO to the candidate T-MN(1110) by transmitting a message containing the current MCG configuration of the UE (1112).

29. The S-MN (1110) of any of claims 24-28 wherein the message further contains a current SCG configuration of the UE (1112).

30. The S-MN (1110) of any of claims 24-29 wherein the processing circuitry (1130) is configured to transmit (24) a message containing a request for CHO to the candidate T-MN (1110) by transmitting a message containing a maximum number of PSCell or SCG configurations that the T-MN (1110) may prepare.

31. The S-MN (1110) of any of claims 24-30 wherein the processing circuitry (1130) is configured to transmit (24) a message containing a request for CHO to the candidate T-MN (1110) by transmitting a message containing a current S-MN measConfig of the UE (1112).

32. The S-MN (1110) of any of claims 24-31 wherein the processing circuitry (1130) is configured to transmit (24) a message containing a request for CHO to the candidate T-MN (1110) by transmitting a message containing UE (1112) capability information related to CHO with PSCell or SCG, and / or UE (1112) ability to perform measurements and evaluate execution conditions.

33. The S-MN (1110) of any of claims 24-32 wherein the processing circuitry (1130) is configured to receive (26) a message from the candidate T-MN (1110) by receiving a message including information regarding the number of PSCell or SCG configurations that have been configured.

34. The S-MN (1110) of claim 33 further comprising cancelling some configurations if they exceed the UE (1112) capabilities.

35. A method (30), performed by a network node (1110) operative in a wireless communication network (1100) and acting as a candidate Target Master Node, T-MN (1110), for a user equipment, UE (1112), for performing Conditional Handover, CHO, of the UE (1112) with one of an associated candidate PSCell or candidate Secondary Cell Group, SCG, the method (40) comprising: receiving (32) a message from a Source Master Node, S-MN (1110), the message containing a request for CHO with associated configuration of PSCell or SCG;determining (34) to accept CHO configuration with associated PSCell or SCG configuration; preparing (36) a target CHO configuration; triggering (38) a configuration of PSCell or SCG; in response to a candidate target PSCell belonging to a different Target Secondary Node, T-SN (1110), transmitting (40) a message to the T-SN (1110) containing a request to configure PSCell or SCG; in response to sending the message to the T-SN (1110), receiving (42) a reply from the T- SN (1110) containing a target PSCell or SCG configuration; preparing (44) executions conditions for the PSCell or SCG; and transmitting (46) a message to the S-MN (1110) containing the target configuration for CHO and a PSCell or SCG configuration comprising execution conditions and a target PSCell or SCG configuration.

36. A network node (1110) operative in a wireless communication network (1100) and acting as a candidate Target Master Node, T-MN (1110), for a user equipment, UE (1112), for performing Conditional Handover, CHO, of the UE (1112) with one of an associated candidate PSCell or candidate Secondary Cell Group, SCG, the method (40) comprising: communication circuitry (1134) configured to wirelessly communicate with one or more UEs (1112); and processing circuitry (1130) operatively connected to the communication circuitry (1134) and configured to receive (32) a message from a Source Master Node, S-MN (1110), the message containing a request for CHO with associated configuration of PSCell or SCG; determine (34) to accept CHO configuration with associated PSCell or SCG configuration; prepare (36) a target CHO configuration; trigger (38) a configuration of PSCell or SCG; in response to a candidate target PSCell belonging to a different Target Secondary Node, T-SN (1110), transmit (40) a message to the T-SN (1110) containing a request to configure PSCell or SCG; in response to sending the message to the T-SN (1110), receive (42) a reply from the T-SN (1110) containing a target PSCell or SCG configuration; prepare (44) executions conditions for the PSCell or SCG; andtransmit (46) a message to the S-MN (1110) containing the target configuration for CHO and a PSCell or SCG configuration comprising execution conditions and a target PSCell or SCG configuration.

Images