Enhancement of reporting for conditional handover with candidate secondary cell group failure

Abstract

A method (600) performed by a User Equipment, UE (112, 200), configured for a conditional handover, CHO, with candidate Secondary Cell Group, SCG, procedure, includes detecting (602) an event. In response to detecting the event, the UE logs (604) information associated with a Radio Link Failure, RLF, or a failure of the CHO with candidate SCG procedure, or a successful execution of the CHO with candidate SCG procedure.

Description

[0001] ENHANCEMENT OF REPORTING FOR CONDITIONAL HANDOVER WITHCANDIDATE SECONDARY CELL GROUP FAILURETECHNICAL FIELD The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for enhancement of reporting for Conditional Handover (CHO) with candidate Secondary Cell Group (SCG) failure. BACKGROUND A conditional handover (CHO) is defined as a handover that is executed by the User Equipment (UE) when one or more execution conditions are met. Upon receiving CHO configuration, UE starts evaluating the conditions and stops once the handover is executed. In CHO with candidate Secondary Cell Group (SCG), the UE is configured with two configurations, one for performing Primary Cell (PCell) handover and other for Primary Secondary Cell (PSCell) change. Upon receiving such configuration, the UE evaluates both conditions and attempts to perform handover once both execution conditions are satisfied. In this type of handover, the source Master Node (MN) configures conditions for the PCell CHO, while the candidate target MN configures conditions for the candidate PSCell change. Self-Organizing Networks Self-Organizing Networks (SON) are a collection of functions for automatic configuration, optimization, and healing of networks. The aim of the framework is to perform routine maintenance and optimization where necessary without additional configuration. To enable this functionality, multiple reports are defined and collected from the UE. Some relevant ones are introduced in the following:^ Successful Handover Report (SHR): Successful Handover Report (SHR) isgenerated by a UE performing a PCell handover if the conditions set by the network are fulfilled. Generation of SHR refers to UE being close to failure of the handover. ^Successful PSCell Report (SPR): Successful PSCell Report (SPR) is generated bya UE performing a PSCell change if the conditions set by the network are fulfilled. Generation of SPR refers to UE being close to failure of the PSCell change. ^Radio Link Failure (RLF) report: If a Radio Resource Control (RRC) connectedUE declares RLF, the UE creates a RLF report, and the network can fetch the RLFreport from the UE. In a RLF report, the UE includes necessary information andmeasurements for the network to analyze radio conditions and, possibly, thephysical location of the UE. Thus, the network can take appropriate action upon analyzing the RLF report. There are multiple scenarios where the UE may declare RLF. Details can be found in 3GPP TS 38.300 V18.0.0 and 3GPP TS 38.331V18.0.0. SCG Failure Information A UE operating in dual connectivity may encounter problems in the SCG and declare failure on the SCG leg. If the connection to the Master Cell Group (MCG) leg is active, the UEdoes not declare RLF. Rather, the UE sends a SCGFailureInformation message to the MN. Uponreceiving the message, the MN can take necessary actions to solve the problems. There currently exist certain challenge(s), however. For example, a UE generates an RLFreport when triggered by a failure of a mobility procedure. This includes mobility procedures of the type “CHO with candidate SCG” discussed above. However, the RLF report, as currently specified in 3GPP TS 38.331 v18.0.0 does not sufficiently take into account relevant aspects of a failed CHO with candidate SCG procedure.

[0002] SUMMARY Certain aspects of the disclosure and their embodiments may provide solutions to these orother challenges. For example, methods and systems are provided for an extension / enhancementof the RLF report. According to certain embodiments, a method by a UE configured for a CHO with candidate SCG procedure includes detecting an event. In response to detecting the event, the UE logs information associated with a RLF or a failure of the CHO with candidate SCG procedure or a successful execution of the CHO with candidate SCG procedure. According to certain embodiments, a UE for a CHO with candidate SCG procedureincludes a memory and a processor. The UE is configured to detect an event. In response todetecting the event, the UE is configured to log information associated with a RLF or a failure of the CHO with candidate SCG procedure or a successful execution of the CHO with candidate SCG procedure. In a particular embodiment, the UE transmits a RLF report to a network node, and the RLF report includes the logging information associated with the RLF or the failure of the CHO with candidate SCG procedure. In a particular embodiment, the event is associated with a RLF, a failure of the CHO with the candidate SCG procedure, or a successful execution of the CHO with the candidate SCG procedure. In a particular embodiment, the information comprises a list of candidate target PSCells at the time of the RLF or the failure of the CHO with candidate SCG procedure, or the successful execution of the CHO with candidate SCG procedure. In a particular embodiment, the information comprises an indication of a selected target PSCell in a failed execution of the CHO with candidate SCG. In a particular embodiment, the information comprises at least one of: a parameter indicating the RLF or the failure of the CHO with candidate SCG procedure, or the success of the CHO with candidate SCG procedure; a type of the failure of the CHO with the candidate SCG procedure; an indication of a connection failure type; a new connection failure type indication; and a RLF cause value. In a particular embodiment, the information comprises an indication of a type of a last handover executed before detection of the failure. In a particular embodiment, the information comprises at least one of: an indication of an amount of elapsed time between a reception by the UE of a CHO with candidate SCG configuration and detecting the event, at least one value associated with a channel quality measurement for at least one candidate PCell and / or at least one candidate PSCell, and location information associated with at least one of an MCG location configuration and a SCG location configuration. In a particular embodiment, the information comprises an indication of whether, acondition that was not fulfilled when the failure was detected, was fulfilled before the RLFoccurred and after the CHO with candidate SCG configuration was received at the UE. Additionally or alternatively, the information comprises the smallest measured margin tofulfillment of an execution condition for at least one of the non-selected / non-triggered candidatetarget PCell(s). Additionally or alternatively, the information comprises the smallest measured margin to fulfillment of an execution condition for at least one of the non-selected / non-triggered candidate target PSCell(s). In a particular embodiment, the information comprises at least one of: a list of candidate ,PCells for which an execution condition for CHO was fulfilled but the candidate PCells were notselected because an execution condition for a change for PSCell was not fulfilled, and a list ofcandidate PSCells for which an execution condition for change of PSCell was fulfilled but the candidate PSCells were not selected because an execution condition for CHO was not fulfilled. In a particular embodiment, the information comprises at least one of: an indication ofwhether an execution condition for the CHO was fulfilled, and an indication of whether anexecution condition for the Primary Secondary Cell, PSCell, change was fulfilled.In a particular embodiment, the information comprises at least one of: an indication ofwhether execution was attempted and successful for a CHO part of the CHO with candidate SCGconfiguration, an indication of whether execution was attempted and successful for a PrimarySecondary Cell, PSCell, part of the CHO with candidate SCG configuration, an indication ofwhether execution was successful for the CHO part of the CHO with candidate SCG configuration, an indication of whether execution was successful for the PSCell part of the CHO with candidate SCG configuration, an indication of whether execution was attempted for the CHO part of the CHO with candidate SCG configuration, and an indication of whether execution was attempted for the PSCell part of the CHO with candidate SCG configuration. In a particular embodiment, the event detected by the UE comprises an RLF event. According to certain embodiments, a method by a first network node for receiving information for an event detected by a UE includes receiving information associated with a RLF or a failure of a CHO with candidate SCG procedure or a successful CHO with candidate SCG procedure for the UE. According to certain embodiments, a first network node for receiving information for an event detected by a UE includes a memory and a processor. The first network node is configured to receive information associated with a RLF or a failure of a CHO with candidate SCG procedure or a successful CHO with candidate SCG procedure for the UE. In a particular embodiment, when receiving the information, the network node receives the information in one of a RLF report and SHR. In a particular embodiment, the network node configures the UE to detect an event and transmit the information to the network node in response to detecting the event, and wherein the event is associated with at least one of: the RLF, a failure of the CHO with the candidate SCG procedure, or a successful execution of the CHO with the candidate SCG procedure. In a particular embodiment, the information comprises a list of candidate target PSCells at the time of the failure of the RLF or the CHO with candidate SCG configuration. In a particular embodiment, the information comprises an indication of a selected target PSCell in a failed execution of the CHO with candidate SCG. In a particular embodiment, the information includes at least one of: a parameter indicating the RLF or the failure of the CHO with the candidate SCG procedure; a parameter indicating thesuccessful CHO with the candidate SCG procedure; a type of the failure of the CHO with thecandidate SCG procedure; an indication of a connection failure type; a new connection failure type indication; and a RLF cause value. In a particular embodiment, the information comprises at least one of: an indication of an amount of elapsed time between a reception by the UE of a CHO with candidate SCG configuration and the occurrence / detection of the failure, at least one value associated with a channel quality measurement for at least one candidate PCell and / or at least one candidate PSCell, and location information associated with at least one of an MCG location configuration and a SCG location configuration. In a particular embodiment, the information comprises an indication of whether, acondition that was not fulfilled when the failure was detected, was fulfilled before the RLF occurred and after the CHO with candidate SCG configuration was received at the UE. Additionally or alternatively, the information comprises the smallest measured margin tofulfillment of an execution condition for at least one of the non-selected / non-triggered candidatetarget PCell(s). Additionally or alternatively, the information comprises the smallest measured margin to fulfillment of an execution condition for at least one of the non-selected / non-triggered candidate target PSCell(s). In a particular embodiment, the information comprises at least one of: a list of candidate , PCells for which an execution condition for CHO was fulfilled but the candidate PCells were notselected because an execution condition a change for PSCell was not fulfilled, and a list ofcandidate PSCells for which an execution condition for change of PSCell was fulfilled but the candidate PSCells were not selected because an execution condition for CHO was not fulfilled. In a particular embodiment, the information comprises at least one of: an indication of whether an execution condition for the CHO was fulfilled, and an indication of whether an execution condition for the PSCell change was fulfilled. In a particular embodiment, the information comprises at least one of: an indication of whether execution was attempted and successful for a CHO part of the CHO with candidate SCG configuration, an indication of whether execution was attempted and successful for a Primary Secondary Cell, PSCell, part of the CHO with candidate SCG configuration, an indication of whether execution was successful for the CHO part of the CHO with candidate SCG configuration, an indication of whether execution was successful for the PSCell part of the CHO with candidate SCG configuration, an indication of whether execution was attempted for the CHO part of the CHO with candidate SCG configuration, and an indication of whether execution was attempted for the PSCell part of the CHO with candidate SCG configuration. In a particular embodiment, the network node transmits the information to a second network node. In a further particular embodiment, the first network node is a source network node for the CHO with the candidate SCG procedure, the second network node is a target network node for the CHO with the candidate SCG procedure, and the information is received from the UE.Alternatively, the first network node is a source network node for the CHO with the candidateSCG procedure, the second network node is a target network node for the CHO with the candidate SCG procedure, and the information is received from the second network node. Or alternatively, the first network node is a target network node for the CHO with the candidate SCG procedure, the second network node is a source network node for the CHO with the candidate SCG procedure, and the information is received from the UE. As still another alternative, the first network node is a target network node for the CHO with the candidate SCG procedure, the second network node is a source network node for the CHO with the candidate SCG procedure, and the information is received from the second network node. As yet another alternative, the first network node is an unselected target network node for the CHO with the candidate SCG procedure, the second network node is a source network node for the CHO with the candidate SCG procedure, and the information is received from the UE or the second network node. In a particular embodiment, based on the information, determining at least one CHO condition for a non-selected candidate Primary Cell, PCell, that was fulfilled while at least one condition of an associated Primary Secondary Cell, PSCell, was not fulfilled. Additionally or alternatively, the network node transmits, to the non-selected candidate PCell, at least one of: anindication of the associated PSCell for which the at least one condition was not fulfilled, and anindication of at least one condition that was not fulfilled. In a particular embodiment, the network node uses the information to determine, for a subsequent CHO with candidate SCG procedure, at least one Primary Secondary Cell, PSCell, and / or at least one execution condition. Certain embodiments may provide one or more of the following technical advantage(s). For example, certain embodiments may provide a technical advantage of enhancing an RLF report with information that is relevant in the analysis of the root cause of a failure in a CHO withcandidate SCG procedure. As another example, certain embodiments may provide a technicaladvantage of enhancing the network’s ability / possibility to take relevant and successful actionssuch as, for example, optimizing certain configuration aspects related to CHO with candidate SCG based on the analysis of the RLF report. Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages. BRIEF DESCRIPTION OF THE DRAWINGS For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which: FIGURE 1 illustrates an example communication system, according to certain embodiments; FIGURE 2 illustrates an example UE, according to certain embodiments; FIGURE 3 illustrates an example network node, according to certain embodiments; FIGURE 4 illustrates a virtualization environment in which functions implemented bysome embodiments may be virtualized, according to certain embodiments; FIGURE 5 illustrates an example method by a UE for transmitting an enhanced RLF report,according to certain embodiments; FIGURE 6 illustrates an example method by a UE configured for a CHO with candidateSCG procedure, according to certain embodiments; FIGURE 7 illustrates an example method by a network node for receiving an enhancedRLF report, according to certain embodiments; and FIGURE 8 illustrates an example method by a first network node for receiving informationfor an event detected by a UE according to certain embodiments. DETAILED DESCRIPTION Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. As used herein, ‘node’ can be a network node or a UE. A network node is referred to as a node capable of providing a service to a UE. Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB (eNB), gNodeB (gNB),Master eNB (MeNB), Secondary eNB (SeNB), integrated access backhaul (IAB) node, networkcontroller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operations & Maintenance (O&M), OperationsSupport System (OSS), Self-Organizing Network (SON), positioning node (e.g. E-SMLC), etc.The terms network node and radio network node are used interchangeably herein. Another example of a node is user equipment (UE), which is a non-limiting term and refers to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. More generally, a UE is any device using the service of a wireless network. Examples of UE are target device, device to device (D2D) UE, vehicular to vehicular (V2V), machine type UE, MTC UE or UE capable of machine to machine (M2M) communication, Personal Digital Assistant (PDA), Tablet, mobile terminals, smart phone, laptop embedded equipment (LEE), laptop mounted equipment (LME), Unified Serial Bus (USB) dongles, etc. The term radio access technology (RAT), may refer to any RAT such as, for example, Universal Terrestrial Radio Access Network (UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRA), narrow band internet of things (NB-IoT), WiFi, Bluetooth, next generation RAT, New Radio (NR), 4thGeneration (4G), 5thGeneration (5G), etc. Any of the equipment denoted by the terms node, network node or radio network node may be capable of supporting a single or multiple RATs. The term signal or radio signal used herein can be any physical signal or physical channel. Examples of downlink (DL) physical signals are reference signal (RS) such as Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Channel State Information-Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS) signals in SS / PBCH block (SSB), discovery reference signal (DRS), Cell Specific Reference Signal (CRS), Positioning Reference Signal (PRS), etc. RS may be periodic. For example, RS occasions carrying one or more RSs may occur with certain periodicity (e.g., 20 ms, 40 ms, etc.). The RS may also be aperiodic. Each SSB carries New Radio-Primary Synchronization Signal (NR-PSS), New Radio- Secondary Synchronization Signal (NR-SSS) and New Radio-Physical Broadcast Channel (NR- PBCH) in four successive symbols. One or multiple Synchronization Signal Blocks (SSBs) are transmitted in one SSB burst which is repeated with certain periodicity such as, for example, 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms. The UE is configured with information about SSB on cells of certain carrier frequency by one or more SS / PBCH block measurement timing configuration (SMTC) configurations. The SMTC configuration comprising parameters such as SMTC periodicity, SMTC occasion length in time or duration, SMTC time offset with regard to reference time (e.g., serving cell’s SFN) etc. Therefore, SMTC occasion may also occur with certain periodicity (e.g., 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms). Examples of uplink (UL) physical signals are reference signals such as Sounding Reference Signals (SRS), Demodulation Reference Signals (DMRS), etc. The term physical channel refers to any channel carrying higher layer information e.g. data, control etc. Examples of physical channels are Physical Broadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Short PUSCH (sPUCCH), Short PDSCH (sPDSCH), Short PUCCH (sPUCCH), Short PUSCH (sPUSCH), MTC PDCCH (MPDCCH),Narrowband PBCH (NPBCH), Narrowband PDCCH (NPDCCH), Narrowband PDSCH(NPDSCH), Narrowband PUSCH (NPUSCH), Enhanced PDCCH (E-PDCCH), etc. The term time resource used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time. Examples of time resources are symbol, time slot, subframe, radio frame, transmission time interval (TTI), interleaving time, slot, sub-slot, mini- slot, system frame number (SFN) cycle, hyper-SFN (H-SFN) cycle, etc. Herein, certain systems and methods are described as using NR as the radio technology of reference. This should be considered as non-limiting as the systems and methods herein apply to any radio access technology able to configure a UE with multiple mobility and / or cell change procedures requiring coordination for the successful execution of such procedures by the UE. According to certain embodiments, methods and systems are provided for anextension / enhancement of the RLF report. For example, in certain embodiments, the UE includesin the RLF report a number of new parameters and new types of information associated with an RLF experienced by the UE in conjunction with, or related to, a CHO with candidate SCG procedure execution (or execution attempt). According to certain embodiments, a network node that receives the RLF report is able to optimize the CHO with candidate SCG configurations subsequently provided to UEs. For example, according to certain embodiments, a method is provided that includes the UE providing an enhanced RLF report that includes at least one parameter associated with and / or reflecting relevant aspects of a CHO with candidate SCG configuration and / or a CHO with candidate SCG procedure execution. The method may be performed when the UE experiences an RLF that is related to a CHO with candidate SCG configuration and / or a CHO with candidate SCG procedure execution (or execution attempt). The UE logs these parameters in an RLF report, which the UE later sends to the network node, thereby enabling the network to optimize the CHO with candidate SCG configurations subsequently provided to UEs. Overview of an Example Solution In one example scenario, a UE is in RRC_CONNECTED state in a 5G / NR network and is configured to perform a CHO with candidate SCG procedure (i.e., to change both the PCell andthe PSCell when configured conditions are fulfilled). Zero, one or both of the conditions may befulfilled, which may lead to a number of cases such as that the CHO with candidate SCG procedure is fully executed, it fails, or it succeeds but shortly afterwards the UE loses its connection and declares RLF. Furthermore, even if, in this example scenario, both of the conditions are fulfilled (i.e. the CHO with candidate SCG procedure is “fully triggered”), the CHO with candidate SCG execution fails, or it succeeds but shortly afterwards the UE loses its connection and declares RLF. It is noted that if the UE declares RLF in the source cell while a conditional mobility procedure is configured, this may be considered to be related to the conditional mobility configuration in the sense that it is considered as a “too late handover” if the UE, as a result of the RLF, reestablishes its connection in one of the candidate target cells. According to certain embodiments described herein, as a result of the CHO with candidate SCG failure or RLF, the UE generates an RLF report, which includes information that is currentlynot specified in version 18.0.0 of 3GPP TS 38.331. This additional information that is not specifiedin version 18.0.0 of 3GPP TS 38.331 reflects aspects of the CHO with candidate SCG configuration and / or procedure that may be beneficial for the network nodes receiving the RLFreport (e.g., the gNB controlling the source PCell and / or the gNB controlling a candidate targetPCell) to optimize the CHO with candidate SCG configuration so to avoid future failures. According to certain embodiments, the UE subsequently indicates to the network that the RLF report is available and the network (e.g., a gNB) fetches the RLF report by transmitting aUEInformationRequest RRC message to the UE and the UE responds with aUEInformationResponse RRC message that includes the RLF report. If the gNB that fetched theRLF report is different from the one that configured the CHO with candidate SCG procedure inthe UE, the gNB may forward the RLF report to the gNB(s) that configured the UE for the CHO with candidate SCG procedure. It is noted that two gNBs may be involved in the CHO with candidate SCG configuration, where one gNB (the one controlling the source PCell) configures the CHO part of the CHO with candidate SCG configuration while another gNB (the one controlling the candidate target PCell) configures the PSCell change part of the CHO with candidate SCG configuration. According to certain embodiments, a gNB that receives the RLF report and has been involved in the configuration (and possible execution) of the CHO with candidate SCG mayanalyze the RLF report. In particular, the gNB may analyze the new information related to theCHO with candidate SCG configuration / procedure to determine the reason for the failure and to decide on possible corrective / improving actions such as, for example, modifications of subsequent configurations of CHO with candidate SCG. It is noted that either or both of the source network node and the (candidate) target networknode of the PCell change (i.e., the CHO part of the CHO with candidate SCG procedure) mayreceive the RLF report since the source gNB configures the CHO while the (candidate) target gNB provides configuration related to the PSCell change part of the CHO with candidate SCGprocedure. Note also that, if the source MN (i.e. the gNB controlling the source PCell) receivesthe RLF report, the source MN may forward the RLF report to the candidate target MN (i.e., thegNB controlling the candidate target PCell). Similarly, if the candidate target MN (i.e., the gNBcontrolling the candidate target PCell) receives the RLF report, the candidate target MN mayforward the RLF report to the source MN (i.e., the gNB controlling the source PCell).The new CHO with candidate SCG related information included in the RLF report iselaborated in more detail below. Enhancements of the RLF Report Related to CHO with Candidate SCG In certain scenarios, an RLF report will be generated in conjunction with an attempt toexecute a CHO with candidate SCG (i.e., no Successful Handover Report (SHR) or SPR, or atleast not both), or related to a CHO with candidate SCG configuration. According to certain embodiments described herein, to facilitate the analysis of the reason behind the failure, the UEenriches the RLF report by providing information related to the CHO with candidate SCGexecution attempt (if any attempt was made, or if the UE is configured with such a configurationwhen the failure occurred, and no attempt was made to execute the CHO with candidate SCG). In various particular embodiments, for example, the UE may include at least one of the following in the enriched / enhanced RLF report: -An indication of failure of a CHO with candidate SCG procedure, e.g., in the form ofone of: oA new parameter indicating failure of a CHO with candidate SCG procedure.o A new connection failure type indication (e.g. denoted asconnectionFailureTypeExt-r19). This could be, for example, anENUMERATED type parameter with a single possible value being “choWithCandScgFailure” or multiple values where one is “choWithCandScgFailure” while the other possible values are spare values. oA new RLF cause value (e.g. using one of the spare values of the rlf-Causefield, or introducing a new additional RLF cause parameter, e.g. a rlf-CauseExt-r19 field) indicating the new cause value of a failure of a CHO with candidateSCG procedure. -A new indication of last handover type (e.g., type “CHO with candidate SCG”), whichindicates the type of the last executed handover before the last detected connectionfailure. This may be realized in the RRC specification (3GPP TS 38.331) by utilizing one of the spare values of the lastHO-Type-r17 field, or by introducing a new parameterto indicate it, in various particular embodiments. -A list of the candidate target PSCells in the CHO with candidate SCG configurationthat was present at the time of the failure (or similarly, a list of candidate target PSCells for which one or more conditions for the execution of a conditional reconfiguration for CHO with candidate SCG(s) were included in the list of conditional reconfigurations at the time of the failure). Currently (in version 18.0.0 of 3GPP TS 38.331), the choCandidateCellList-r17 field in the RLF-Report-r16 IE includes a similar list ofcandidate target cells for a CHO configuration that existed in the UE at the time of the failure. A similar, or corresponding, list of candidate target PSCells could be introduced(e.g., denoted as candPSCellList-r19 or cpacCandidateCellList-r19 orchoWithCandSCG-CandidatePSCellList-r19). Alternatively, in a particularembodiment, the legacy choCandidateCellList-r17 is extended with a field indicatingwhether the candidate cell is a PSCell or PCell.- An indication of the elapsed time between the UE’s reception of the CHO withcandidate SCG configuration and the occurrence of the failure. This would be similar to the currently specified timeSinceCHO-Reconfig-r17 field (e.g., denoted astimeSinceCHO-WithCandSCG-Reconfig-r19). In various particular embodiments, thiselapsed time may, for example, be represented as per one or more of the followingmethods: oAn indication of the elapsed time between the UE’s reception of the lastconditional reconfiguration including the conditional reconfiguration of the target PCell (say first conditional reconfiguration) in which the RLF occurredand the occurrence of the failure in said PCell. This would be similar to the currently specified timeSinceCHO-Reconfig-r17 field (e.g., denoted astimeSinceCHO-WithCandSCG-Reconfig-r19). oAn indication of the elapsed time between the UE’s reception of the lastconditional reconfiguration including the conditional reconfiguration of the PSCell for which the CHO with candidate SCG(s) is executed (i.e., the target PSCell whose execution condition for the CHO with candidate SCG are fulfilled) (say second conditional reconfiguration) and the occurrence of the failure in the target PCell. oAn indication of the elapsed time between the UE’s reception of the first orsecond conditional reconfiguration whichever was received first and the occurrence of the failure in the target PCell. oAn indication of the elapsed time between the UE’s reception of the first orsecond conditional reconfiguration whichever was received last and the occurrence of the failure in the target PCell. oThe above methods, wherein the target PCell is the target PCell for which theCHO with candidate SCG(s) is executed or an ordinary non-conditional reconfiguration with sync is executed. oIn case an RLF is detected in a cell prior to the CHO with candidate SCGexecution, an indication of the time elapsed between the reception in the failed cell of the last conditional reconfiguration irrespective of whether it included the conditional execution condition for a candidate target PCell or candidate target PSCell.- An indication of the selected target PSCell in a failed CHO with candidate SCGexecution. In version 18.0.0 of 3GPP TS 38.331, the failedPCellId-r16 field indicatesthe PCell in which RLF is detected or the target PCell of the failed handover. In a particular embodiment, this is reused for the selected target PCell of a failed CHO with candidate SCG execution, and a new similar field (e.g., denoted as failedPSCellId-r19)could be introduced for identification of the selected target PSCell in a failed CHO with candidate SCG execution.- Information about the channel quality measurement results (e.g., the latestmeasurement results) such as, for example, in terms of Reference Signal ReceivedPower (RSRP), Reference Signal Received Quality (RSRQ), Signal Interference toNoise Ratio (SINR), Signal to Noise Ratio (SNR), Reference Signal Strength Indicator (RSSI) in cell level or beam level of any candidate target PCells or candidate targetPSCells which have not been reported to the network (e.g., the source gNB) prior tothe failure such as, for example, the last measurements available at the UE.o In a particular embodiment, the UE logs two sets of the measurements: oneset / list of measurements configured based on the MCG RRM measurement configurations (e.g., MCG measurement objects) and one set / list of measurements configured based on the SCG RRM measurement configurations (e.g., SCG measurement objects). oIn another particular embodiment, the UE logs one set / list of the measurementsbased on both MCG and SCG RRM measurement configurations (e.g., based on all the available measurements at the UE irrespective of the node configuring the measurement objects).- Information about the valid location information available at the time of failure. Suchmeasurements may include Bluetooth measurements and / or Wide Local Area Network (WLAN) measurements.o In a particular embodiment, the UE logs two sets of the location measurements:one set / list of measurements configured based on the MCG location configuration (e.g., Bluetooth name list and or WLAN name list configured bythe MCG), and one set / list of measurements configured based on the SCGlocation configuration (e.g., Bluetooth name list and or WLAN name list configured by the MCG). oIn another particular embodiment, the UE logs one set / list of the locationinformation based on both MCG and SCG location configurations (e.g., logging all the available Bluetooth measurements and the WLAN measurements at the UE irrespective of the node configuring the Bluetooth and / or WLAN name list).- Information about the source PSCell and target PSCell and the failed PSCello In a particular embodiment, the information about the cell identities is cellglobal identity (CGI) or the physical cell identity (PCI) and frequency information (ARFCN).- Information describing the UE configuration at the time the RLF occurred and detailsof the events that occurred. In a particular embodiment, this includes the executionconditions of each of the CHO and SCG change procedures, including details such as events each condition required fulfillment of source and target cell signal levels thresholds or signal level differences the event required to be reached and fulfilled.- Information concerning which of the configured conditions was fulfilled at the time theRLF occurred such as, for example, CHO conditions or SCG change conditions or bothor none. The UE may also include details of the resulting event, due to such partial fulfilment of the configured conditions, for example, one possible event might consist of an RLF incurred by the UE due to lack of fulfilment of a first condition or a second condition or both.- Information concerning whether, at the time the RLF occurred, a condition that was notfulfilled was then fulfilled before the RLF occurred and after the CHO with candidate SCG configuration was received at the UE. In this case, the information may include a measure of time from the RLF occurrence until the last point in time when the condition was fulfilled or from the last point in time when the condition was fulfilled until the RLF occurrence.- The smallest measured margin to fulfillment of the execution condition for each of thenon-selected / non-triggered candidate target PCell(s). Alternatively, this information could be restricted to a subset of the non-selected / non-triggered candidate targetPCell(s), e.g., the N non-selected / non-triggered candidate target PCell(s) that were / wasclosest to being triggered, or any non-selected / non-triggered candidate target PCell(s) for which the smallest measured margin to fulfillment of the execution condition was smaller than a certain threshold X (e.g., measured in dBm or dB or W, depending on the measurement quantity). As yet an alternative, the indications could have the form of a set of cell identities (where a cell identity may be , for example, an NR Cell GlobalIdentity (NCGI) or a combination of PCI and ARFCN) for the non-selected / non-triggered candidate target PCell(s) for which the smallest measured margin to fulfillment of the execution condition was smaller than a certain threshold X (i.e., with this alternative, no measurement margin or measurement result would be included in the information). (Note that the non-selected / non-triggered candidate target PCell(s) may include all configured candidate target PCell(s) if none of the execution condition(s) was fulfilled.)- The smallest measured margin to fulfillment of the execution condition for each of thenon-selected / non-triggered candidate target PSCell(s). Alternatively, this information could be restricted to a subset of the non-selected / non-triggered candidate target PSCell(s) such as, for example, the N non-selected / non-triggered candidate targetPSCell(s) that were / was closest to being triggered, or any non-selected / non-triggered candidate target PSCell(s) for which the smallest measured margin to fulfillment of the execution condition was smaller than a certain threshold X (e.g., measured in dBm or dB or W, depending on the measurement quantity). As yet an alternative, the indications could have the form of a set of cell identities (where a cell identity may be, for example, an NCGI or a combination of PCI and ARFCN or just a PCI) for the non- selected / non-triggered candidate target PSCell(s) for which the smallest measured margin to fulfillment of the execution condition was smaller than a certain threshold X (i.e., with this alternative, no measurement margin or measurement result would be included in the information). (Note that the non-selected / non-triggered candidate target PSCell(s) may include all configured candidate target PSCell(s) if none of the execution condition(s) was fulfilled.)- Various indications of trigger or non-trigger of execution conditions for the CHO andPSCell change (i.e., the candidate SCG) parts of the CHO with candidate SCGconfiguration. For instance, particular embodiments may include one or more of: oA list of candidate PCells for which the execution condition for CHO wasfulfilled (but they were not selected because the associated PSCell change part was not fulfilled), oA list of candidate PSCells for which the execution condition for PSCell wasfulfilled (but they were not selected because the associated execution condition for the CHO part was not fulfilled), oAn indication of whether the CHO part of the CHO with candidate SCGconfiguration was triggered (i.e., whether the execution condition for the CHO was fulfilled). This could be a BOOLEAN type parameter or an optional ENUMERATED type parameter with the only possible value being “true”. oAn indication of whether the PSCell change (candidate SCG) part of the CHOwith candidate SCG configuration was triggered (i.e., whether the executioncondition for the PSCell change (candidate SCG) was fulfilled). This could be a BOOLEAN type parameter or an optional ENUMERATED type parameter with the only possible value being “true”.- Various indications of successful execution or non-successful execution (including noattempted execution) of the CHO and PSCell change parts of the CHO with candidate SCG configuration. For instance, particular embodiments may include indications of one or more of: oWhether execution was attempted and successful for the CHO part of the CHOwith candidate SCG configuration. This could be a BOOLEAN type parameter or an optional ENUMERATED type parameter with the only possible value being “true.” oWhether execution was attempted and successful for the PSCell part of theCHO with candidate SCG configuration. This could be a BOOLEAN type parameter or an optional ENUMERATED type parameter with the only possible value being “true.”o Whether execution was successful for the CHO part of the CHO with candidateSCG configuration. This could be a BOOLEAN type parameter or an optional ENUMERATED type parameter with the only possible value being “true.” oWhether execution was successful for the PSCell part of the CHO withcandidate SCG configuration. This could be a BOOLEAN type parameter or an optional ENUMERATED type parameter with the only possible value being “true.” oWhether execution was attempted for the CHO part of the CHO with candidateSCG configuration. This could be a BOOLEAN type parameter or an optional ENUMERATED type parameter with the only possible value being “true.” oWhether execution was attempted for the PSCell part of the CHO withcandidate SCG configuration. This could be a BOOLEAN type parameter or an optional ENUMERATED type parameter with the only possible value being “true”. -A new IE may be introduced in the RLF report (i.e., in the RLF-Report IE), which couldinclude any one, any subset, or all of the above listed indications and / or information items related to a CHO with candidate SCG configuration and / or procedure. Such a new IE could, for example, be denoted as cho-WithCandSCG-Info-r19 and be of thenew type CHO-WithCandSCG-Info-r19, in a particular embodiment. Various Scenarios in which one or more pieces of the Information are Logged In a first scenario, the UE is configured with CHO with candidate SCG and declares a RLF (e.g., due to expiration of timer T310 or timer T312 or the maximum number of RLC retransmission) in the serving PCell and logs an RLF report including all or various parts of the above information in the RLF report. In another scenario, upon fulfilment of the execution conditions of the CHO with candidate SCG, the UE configured with the CHO with candidate SCG configuration executes the associated reconfiguration with sync toward the target PCell and PSCell, but the supervision timer of the reconfiguration with sync execution (T304) expires (in PCell or PSCell or both PCell and PSCell). The UE logs the RLF report with connection failure type set to CHO with candidate SCG failure and includes all or various parts of the above-mentioned information in the RLF report. In yet another scenario, the UE configured with the CHO with candidate SCG configuration upon fulfilment of the execution conditions of the CHO with candidate SCG, fails shortly after a successful execution of the associated reconfiguration with sync toward the target PCell and PSCell, the UE logs an RLF report and includes the one or more pieces of the above information in the RLF report. In yet another scenario, upon fulfilment of the execution conditions of the CHO with candidate SCG, the UE configured with the CHO with candidate SCG configuration successfully executes the associated reconfiguration with sync toward the target PCell and PSCell and logs a report (e.g., SHR) and logs the last handover / mobility procedure type was a CHO with candidate SCG. Additional Embodiments, Extensions and Variations According to certain embodiments, the network node that fetches from the UE an RLF report containing the enhanced information described herein, may be the source MN, the target MN one of the non-selected candidate target MN(s), one of the non-selected candidate target SN(s) or another network node. By reusing existing procedures, the RLF can be dispatched to the source gNB (that provided the CHO configuration) and to the target gNB (that provided the configuration for the PSCell change). Although the source gNB does not decide the candidate target cells / SNsto be considered for PSCell Change, the source gNB determines that CHO conditions for a non-selected / non-triggered candidate PCell(s) / target MN were fulfilled while the conditions of the associated PSCell(s) were not fulfilled. Therefore, in a particular embodiment, the source MN sends to the candidate target MNserving such non-selected / non-triggered candidate PCell(s) the indication of the PSCell(s) for which PSCell change could not be executed due to non-fulfillment of the associated conditions. The contacted non-selected candidate target MN (for CHO) can use this information in subsequentpreparations of candidate SCG to be used for CHO with candidate SCG. In another embodiment,the source gNB sends, to the candidate MN serving non-selected / non-triggered candidate PCell(s),information on which trigger condition was(were) not fulfilled and optionally associated radio measurements. In case one of the trigger conditions was fulfilled and the other was not, thissupports the non-selected candidate target gNB avoiding using one of the trigger conditions in the future (or adjust the event related parameters, e.g., A3 offset, or A5 thresholds (where A3 and A5 are triggering events specified in 3GPP TS 38.331 version 18.0.0)) In a particular embodiment, the candidate (target) MN for which CHO conditions werefulfilled uses the RLF report and, for example, removes from subsequent CHO with candidateSCG configurations for which it has to select the cells to be used as candidate SCG, those candidate PSCell(s) for which the condition for the PSCell change part of the CHO with candidate SCG was not fulfilled (while the CHO part of the condition was fulfilled). Example Implementation The following is an example of how an embodiment of the proposed solution could be implemented in ASN.1 code in the 3GPP RRC specification. The example is based on 3GPP TS 38.331 version 18.0.0 and the new ASN.1 code is indicated by italicized, bold, underlined font.RLF-Report-r16 ::= CHOICE {nr-RLF-Report-r16 SEQUENCE { measResultLastServCell-r16 MeasResultRLFNR-r16, csi-rsRLMConfigBitmap-v1650 BIT STRING (SIZE (96)) OPTIONAL ]], [[ lastHO-Type-r17 ENUMERATED {cho, daps, choWithCandScg, spare1} OPTIONAL, timeConnSourceDAPS-Failure-r17 TimeConnSourceDAPS-Failure-r17 OPTIONAL, timeSinceCHO-Reconfig-r17 TimeSinceCHO-Reconfig-r17 OPTIONAL, choCellId-r17 CHOICE { cellGlobalId-r17 CGI- pci-arfcn-r17 PCI- }OPTIONAL, choCandidateCellList-r17 ChoCandidateCellList-r17 OPTIONAL ]], [[ pSCellId-r18 CHOICE { cellGlobalId-r18 CGI-Info-Logging-r16,pci-arfcn-r18 PCI-ARFCN-NR-r16 } OPTIONAL, mcgRecoveryFailureCause-r18 ENUMERATED {t316-Expiry, scgDeactivated, spare2, spare1} OPTIONAL, scgFailureCause-r18 ENUMERATED {t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, synchReconfigFailureSCG, scg-ReconfigFailure, srb3-IntegrityFailure, scg-lbtFailure-r16, beamFailureRecoveryFailure-r16, t312-Expiry-r16, bh-RLF-r16, beamFailure-r17, spare3, spare2, spare1} OPTIONAL, elapsedTimeSCGFailure-r18 ElapsedTimeSCGFailure-r18 OPTIONAL, voiceFallbackHO-r18 ENUMERATED {true} OPTIONAL, measResultLastServCell-RSSI-r18 RSSI-Range-r16 OPTIONAL, measResultNeighFreqList-RSSI-r18 MeasResultNeighFreqList-RSSI-r18 OPTIONAL, bwp-Info-r18 AttemptedBWP-Info-r18 OPTIONAL, elapsedTimeT316-r18 ElapsedTimeT316-r18 OPTIONAL]], [[ cho-WithCandSCG-Info-r19 CHO-WithCandSCG-Info-r19 OPTIONAL ]] }, eutra-RLF-Report-r16 SEQUENCE { failedPCellId-EUTRA CGI-InfoEUTRALogging, measResult-RLF-Report-EUTRA-r16 OCTET STRING,..., [[measResult-RLF-Report-EUTRA-v1690 OCTET STRING OPTIONAL ]] } }CHO-WithCandSCG-Info-r19 ::= SEQUENCE {connectionFailureTypeExt-r19 ENUMERATED {choWithCandScgFailure, spare} OPTIONAL,candPSCellList-r19 CandPSCellList-r19 OPTIONAL, timeSinceCHO-WithCandSCG-Reconfig-r19 TimeSinceCHO-WithCandSCG-Reconfig-r19 OPTIONAL,choTriggered-r19 ENUMERATED {true} OPTIONAL, pscellChangeTriggered-r19 ENUMERATED {true} OPTIONAL, ... } CandPSCellList-r19 ::= SEQUENCE(SIZE (1..maxNrofCondCells-r16)) OF CandPSCell-r19 CandPSCell-r19 ::= CHOICE { cellGlobalId-r17 CGI-Info-Logging-r16, (0..1023) FIGURE 1 shows an example of a communication system 100 in accordance with someembodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 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 embodiments, the communication system 100 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 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system. The UEs 112 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 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 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 102. In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. 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 106 includes one more core network nodes (e.g., core network node 108) 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 108. 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 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102 and may be operated by the service provider or on behalf of the service provider. The host 116 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 100 of FIGURE 1 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 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 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 112 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 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may beconfigured for operating in single- or multi-RAT or multi-standard mode. For example, a UE mayoperate 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 RadioAccess Network) New Radio – Dual Connectivity (EN-DC).In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 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 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices. The hub 114 may have a constant / persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114may be a dedicated hub – that is, a hub whose primary function is to route communications to / fromthe UEs from / to the network node 110b. In other embodiments, the hub 114 may be a non-dedicated hub – that is, a device which is capable of operating to route communications betweenthe UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels. FIGURE 2 shows a UE 200, which may be an embodiment of the UE 112 of FIGURE 1, in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 2. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs). In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied. The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-onlymemory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives,and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems. The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such astamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium. The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and / or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately. In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communicationssuch as Bluetooth, near-field communication, location-based communication such as the use ofthe global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), inresponse to a triggering event (e.g., when moisture is detected, an alert is sent), in response to arequest (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or theswitch may change. For example, the UE may comprise a motor that adjusts the control surfacesor rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input. A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), awearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and / or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 200 shown in FIGURE 2. As yet another specific example, in an IoT scenario, a UE may represent a machine or otherdevice that performs monitoring and / or measurements and transmits the results of such monitoringand / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation. In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.When the user makes changes from the remote controller, the first UE may adjust the throttle onthe drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. FIGURE 3 shows a network node 300, which may be an embodiment of the network node 110 of FIGURE 1, in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs). The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300. The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality. In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units. The memory 304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory(ROM), mass storage media (for example, a hard disk), removable storage media (for example, aflash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated. The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front- end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front- end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components. In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown). The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port. The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 310, the communication interface 306, and / or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment. The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail. Embodiments of the network node 300 may include additional components beyond those shown in FIGURE 3 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.FIGURE 4 is a block diagram illustrating a virtualization environment 400 in whichfunctions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. Applications 402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. Hardware 404 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 408a and 408b (one or more of which may be generally referred to as VMs 408), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 406 may present a virtual operating platform that appears like networking hardware to the VMs 408. The VMs 408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 406. Different embodiments of the instance of a virtual appliance 402 may be implemented on one or more of VMs 408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. In the context of NFV, a VM 408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 408, and that part of hardware 404 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 408 on top of the hardware 404 and corresponds to the application 402. Hardware 404 may be implemented in a standalone network node with generic or specific components. Hardware 404 may implement some functions via virtualization. Alternatively, hardware 404 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 410, which, among others, oversees lifecycle management of applications 402. In some embodiments, hardware 404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 412 which may alternatively be used for communication between hardware nodes and radio units. FIGURE 5 illustrates an example method 500 by a UE 112, 200 for transmitting anenhanced RLF report, according to certain embodiments. In the illustrated embodiment, themethod includes a transmitting step at 502. For example, at step 502, the UE 112, 200 maytransmit, to a network node 110, 300, information associated with a failure of a CHO withcandidate SCG procedure. FIGURE 6 illustrates an example method 600 performed by a UE 112, 200 configured fora CHO with candidate SCG procedure, according to certain embodiments. In the Illustratedembodiment, the method begins at step 602 when the UE 112, 200 detects an event. At step 604,in response to detecting the event, the UE 112, 200 logs information associated with a RLF or a failure of the CHO with candidate SCG procedure, or a successful execution of the CHO with candidate SCG procedure. In a particular embodiment, the UE 112, 200 transmits a RLF report to a network node,and the RLF report includes the logging information associated with the RLF or the failure of theCHO with candidate SCG procedure. In a particular embodiment, the event is associated with a RLF, a failure of the CHO with the candidate SCG procedure, or a successful execution of the CHO with the candidate SCG procedure. In a particular embodiment, the information comprises a list of candidate target PSCells atthe time of the RLF or the failure of the CHO with candidate SCG procedure, or the successful execution of the CHO with candidate SCG procedure. In a particular embodiment, the information comprises an indication of a selected target PSCell in a failed execution of the CHO with candidate SCG. In a particular embodiment, the information comprises at least one of: a parameter indicating the RLF or the failure of the CHO with candidate SCG procedure, or the success of the CHO with candidate SCG procedure; a type of the failure of the CHO with the candidate SCGprocedure; an indication of a connection failure type; a new connection failure type indication; anda RLF cause value. In a particular embodiment, the information comprises an indication of a type of a last handover executed before detection of the failure. In a particular embodiment, the information comprises at least one of: an indication of an amount of elapsed time between a reception by the UE of a CHO with candidate SCG configuration and detecting the event, at least one value associated with a channel quality measurement for at least one candidate PCell and / or at least one candidate PSCell, and location information associatedwith at least one of an MCG location configuration and a SCG location configuration.In a particular embodiment, the information comprises an indication of whether, acondition that was not fulfilled when the failure was detected, was fulfilled before the RLFoccurred and after the CHO with candidate SCG configuration was received at the UE.Additionally or alternatively, the information comprises the smallest measured margin tofulfillment of an execution condition for at least one of the non-selected / non-triggered candidatetarget PCell(s). Additionally or alternatively, the information comprises the smallest measured margin to fulfillment of an execution condition for at least one of the non-selected / non-triggered candidate target PSCell(s). In a particular embodiment, the information comprises at least one of: a list of candidate ,PCells for which an execution condition for CHO was fulfilled but the candidate PCells were notselected because an execution condition for a change for PSCell was not fulfilled, and a list ofcandidate PSCells for which an execution condition for change of PSCell was fulfilled but the candidate PSCells were not selected because an execution condition for CHO was not fulfilled. In a particular embodiment, the information comprises at least one of: an indication ofwhether an execution condition for the CHO was fulfilled, and an indication of whether anexecution condition for the Primary Secondary Cell, PSCell, change was fulfilled.In a particular embodiment, the information comprises at least one of: an indication ofwhether execution was attempted and successful for a CHO part of the CHO with candidate SCGconfiguration, an indication of whether execution was attempted and successful for a PrimarySecondary Cell, PSCell, part of the CHO with candidate SCG configuration, an indication ofwhether execution was successful for the CHO part of the CHO with candidate SCG configuration, an indication of whether execution was successful for the PSCell part of the CHO with candidate SCG configuration, an indication of whether execution was attempted for the CHO part of the CHO with candidate SCG configuration, and an indication of whether execution was attempted for the PSCell part of the CHO with candidate SCG configuration. In a particular embodiment, the event detected by the UE comprises an RLF event. FIGURE 7 illustrates an example method 700 by a network node 110, 300 for receiving anenhanced RLF report, according to certain embodiments. In the illustrated embodiment, themethod includes a receiving step at 702. For example, at step 702, the network node may receiveinformation associated with a failure of a CHO with candidate SCG procedure for a UE 112, 200.FIGURE 8 illustrates an example method 800 by a first network node 110, 300 for receiving information for an event detected by a UE 112, 200, according to certain embodiments. In the illustrated embodiment, the method begins at step 802 when the first network node 110, 300 receives information associated with a RLF or a failure of a CHO with candidate SCG procedureor a successful CHO with candidate SCG procedure for the UE 112, 200.In a particular embodiment, when receiving the information, the network node receives theinformation in one of a RLF report and SHR. In a particular embodiment, the network node configures the UE to detect an event and transmit the information to the network node in response to detecting the event, and wherein the event is associated with at least one of: the RLF, a failure of the CHO with the candidate SCG procedure, or a successful execution of the CHO with the candidate SCG procedure. In a particular embodiment, the information comprises a list of candidate target PSCells at the time of the failure of the RLF or the CHO with candidate SCG configuration. In a particular embodiment, the information comprises an indication of a selected target PSCell in a failed execution of the CHO with candidate SCG. In a particular embodiment, the information includes at least one of: a parameter indicating the RLF or the failure of the CHO with the candidate SCG procedure; a parameter indicating thesuccessful CHO with the candidate SCG procedure; a type of the failure of the CHO with thecandidate SCG procedure; an indication of a connection failure type; a new connection failure type indication; and a RLF cause value. In a particular embodiment, the information comprises at least one of: an indication of an amount of elapsed time between a reception by the UE of a CHO with candidate SCG configuration and the occurrence / detection of the failure, at least one value associated with a channel quality measurement for at least one candidate PCell and / or at least one candidate PSCell, and locationinformation associated with at least one of an MCG location configuration and a SCG locationconfiguration. In a particular embodiment, the information comprises an indication of whether, acondition that was not fulfilled when the failure was detected, was fulfilled before the RLFoccurred and after the CHO with candidate SCG configuration was received at the UE.Additionally or alternatively, the information comprises the smallest measured margin tofulfillment of an execution condition for at least one of the non-selected / non-triggered candidatetarget PCell(s). Additionally or alternatively, the information comprises the smallest measuredmargin to fulfillment of an execution condition for at least one of the non-selected / non-triggered candidate target PSCell(s). In a particular embodiment, the information comprises at least one of: a list of candidate , PCells for which an execution condition for CHO was fulfilled but the candidate PCells were notselected because an execution condition a change for PSCell was not fulfilled, and a list ofcandidate PSCells for which an execution condition for change of PSCell was fulfilled but thecandidate PSCells were not selected because an execution condition for CHO was not fulfilled. In a particular embodiment, the information comprises at least one of: an indication of whether an execution condition for the CHO was fulfilled, and an indication of whether an execution condition for the PSCell change was fulfilled. In a particular embodiment, the information comprises at least one of: an indication of whether execution was attempted and successful for a CHO part of the CHO with candidate SCG configuration, an indication of whether execution was attempted and successful for a Primary Secondary Cell, PSCell, part of the CHO with candidate SCG configuration, an indication of whether execution was successful for the CHO part of the CHO with candidate SCG configuration, an indication of whether execution was successful for the PSCell part of the CHO with candidate SCG configuration, an indication of whether execution was attempted for the CHO part of the CHO with candidate SCG configuration, and an indication of whether execution was attempted for the PSCell part of the CHO with candidate SCG configuration. In a particular embodiment, the network node transmits the information to a second network node. In a further particular embodiment, the first network node is a source network node for the CHO with the candidate SCG procedure, the second network node is a target network node for the CHO with the candidate SCG procedure, and the information is received from the UE. Alternatively, the first network node is a source network node for the CHO with the candidate SCG procedure, the second network node is a target network node for the CHO with the candidateSCG procedure, and the information is received from the second network node. Or alternatively,the first network node is a target network node for the CHO with the candidate SCG procedure, the second network node is a source network node for the CHO with the candidate SCG procedure,and the information is received from the UE. As still another alternative, the first network node isa target network node for the CHO with the candidate SCG procedure, the second network node is a source network node for the CHO with the candidate SCG procedure, and the information isreceived from the second network node. As yet another alternative, the first network node is anunselected target network node for the CHO with the candidate SCG procedure, the second network node is a source network node for the CHO with the candidate SCG procedure, and the information is received from the UE or the second network node. In a particular embodiment, based on the information, determining at least one CHO condition for a non-selected candidate Primary Cell, PCell, that was fulfilled while at least one condition of an associated Primary Secondary Cell, PSCell, was not fulfilled. Additionally or alternatively, the network node transmits, to the non-selected candidate PCell, at least one of: an indication of the associated PSCell for which the at least one condition was not fulfilled, and an indication of at least one condition that was not fulfilled. In a particular embodiment, the network node uses the information to determine, for a subsequent CHO with candidate SCG procedure, at least one Primary Secondary Cell, PSCell, and / or at least one execution condition. Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readablestorage medium, such as in a hard-wired manner. In any of those particular embodiments, whetherexecuting instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to othercomponents of the computing device but are enjoyed by the computing device as a whole, and / orby end users and a wireless network generally. EXAMPLE EMBODIMENTS Group A Example Embodiments Example Embodiment A1. A method performed by a user equipment for transmitting anenhanced radio link failure (RLF) report for conditional handover (CHO) with candidateSecondary Cell Group (SCG) failure, the method comprising: any of the user equipment steps,features, or functions described above, either alone or in combination with other steps, features, or functions described above. Example Embodiment A2. The method of the previous embodiment, further comprisingone or more additional user equipment steps, features or functions described above. Example Embodiment A3. The method of any of the previous embodiments, furthercomprising: providing user data; and forwarding the user data to a host computer via thetransmission to the network node. Group B Example Embodiments Example Embodiment B1. A method performed by a network node for receiving anenhanced radio link failure (RLF) report for conditional handover (CHO) with candidateSecondary Cell Group (SCG) failure, the method comprising: any of the network node steps,features, or functions described above, either alone or in combination with other steps, features, or functions described above. Example Embodiment B2. The method of the previous embodiment, further comprisingone or more additional network node steps, features or functions described above.Example Embodiment B3. The method of any of the previous embodiments, furthercomprising: obtaining user data; and forwarding the user data to a host or a user equipment.Group C Example Embodiments Example Embodiment C1. A method performed by a user equipment (UE) fortransmitting an enhanced radio link failure (RLF) report, the method comprising: transmitting, toa network node, information associated with a failure of a conditional handover (CHO) with candidate Secondary Cell Group (SCG) procedure. Example Embodiment C2. The method of Example Embodiment C1, wherein theinformation is transmitted in the RLF report. Example Embodiment C3. The method of any one of Example Embodiments C1 to C2,wherein the information comprises at least one of: a parameter indicating the failure of the CHOwith the candidate SCG procedure; a type of the failure of the CHO with the candidate SCGprocedure; an indication of a connection failure type; a new connection failure type indication; aRLF cause value. Example Embodiment C4. The method of any one of Example Embodiments C1 to C3,comprising receiving, from the network node, a request for the information, and wherein the information is transmitted to the network node in response to the request. Example Embodiment C5. The method of Example Embodiment C4, wherein therequest is received in a UEInformationRequest message, and / or wherein the information is transmitted in a UEInformationResponse message. Example Embodiment C6. The method of any one of Example Embodiments C1 to C5,wherein the information comprises an indication of a type of a last handover executed before detection of the failure. Example Embodiment C7. The method of any one of Example Embodiments C1 to C6,wherein the information comprises a list of candidate target Primary Secondary Cells (PSCells) atthe time of the failure of the CHO with candidate SCG configuration. Example Embodiment C8. The method of any one of Example Embodiments C1 to C7,wherein the information comprises an indication of an amount of elapsed time between a reception by the UE of a CHO with candidate SCG configuration and the occurrence / detection of the failure.Example Embodiment C9. The method of any one of Example Embodiments C1 to C8,wherein the information comprises an indication of a selected target PSCell in a failed execution of the CHO with candidate SCG. Example Embodiment C10. The method of any one of Example Embodiments C1 to C9,wherein the information comprises at least one value associated with a channel quality measurement for at least one candidate PCell and / or at least one candidate PSCell. Example Embodiment C11. The method of any one of Example Embodiments C1 to C10,wherein the information comprises location information associated with at least one of an MCGlocation configuration and a SCG location configuration. Example Embodiment C12. The method of any one of Example Embodiments C1 to C11,wherein the information comprises information associated with at least one of: a source PSCell, a target PSCell, and a failed PSCell. Example Embodiment C13. The method of any one of Example Embodiments C1 to C12,wherein the information comprises at least one of: information associated with a UE configuration at the time the RLF occurred / was detected, and information associated with an RLF event. Example Embodiment C14. The method of any one of Example Embodiments C1 to C13,wherein the information comprises at least one of: an indication of at least one configuredcondition that was fulfilled at the time the failure occurred, and an indication of at least oneconfigured condition that was not fulfilled at the time the failure occurred. Example Embodiment C15. The method of any one of Example Embodiments C1 to C14,wherein the information comprises an indication of whether, a condition that was not fulfilled when the failure was detected, was fulfilled before the RLF occurred and after the CHO with candidate SCG configuration was received at the UE. Example Embodiment C16. The method of any one of Example Embodiments C1 to C15,wherein the information comprises the smallest measured margin to fulfillment of an executioncondition for at least one of the non-selected / non-triggered candidate target PCell(s). Example Embodiment C17. The method of any one of Example Embodiments C1 to C16,wherein the information comprises the smallest measured margin to fulfillment of an executioncondition for at least one of the non-selected / non-triggered candidate target PSCell(s). Example Embodiment C18. The method of any one of Example Embodiments C1 to C17,wherein the information comprises at least one of: a list of candidate PCells for which an execution condition for CHO was fulfilled but were not selected because an execution condition a changefor PSCell was not fulfilled, and a list of candidate PSCells for which an execution condition forchange of PSCell was fulfilled but were not selected because an execution condition for CHO was not fulfilled. Example Embodiment C19. The method of any one of Example Embodiments C1 to C18,wherein the information comprises at least one of: an indication of whether an execution conditionfor the CHO was fulfilled, and an indication of whether an execution condition for the PSCellchange was fulfilled, Example Embodiment C20. The method of any one of Example Embodiments C1 to C19,wherein the information comprises at least one of: an indication of whether execution wasattempted and successful for a CHO part of the CHO with candidate SCG configuration, anindication of whether execution was attempted and successful for the PSCell part of the CHO withcandidate SCG configuration, an indication of whether execution was successful for the CHO partof the CHO with candidate SCG configuration, an indication of whether execution was successfulfor the PSCell part of the CHO with candidate SCG configuration, an indication of whetherexecution was attempted for the CHO part of the CHO with candidate SCG configuration, and anindication of whether execution was attempted for the PSCell part of the CHO with candidate SCG configuration. Example Embodiment C21. The method of any one of Example Embodiments C1 to C20,comprising: detecting the event indicating the failure of the CHO with the candidate SCG procedure, and in response to detecting the event, logging the information in the RLF report. Example Embodiment C22. The method of any one of Example Embodiments C1 to C21,wherein the indication of the event detected by the UE comprises an indication of a RLF event detected by the UE. Example Embodiment C23. The method of Example Embodiments C1 to C22, furthercomprising: providing user data; and forwarding the user data to a host via the transmission to thenetwork node. Example Embodiment C24. A user equipment comprising processing circuitryconfigured to perform any of the methods of Example Embodiments C1 to C23. Example Embodiment C25. A user equipment configured to perform any of the methodsof Example Embodiments C1 to C23.Example Embodiment C26. A wireless device comprising processing circuitryconfigured to perform any of the methods of Example Embodiments C1 to C23. Example Embodiment C27. A computer program comprising instructions which whenexecuted on a computer perform any of the methods of Example Embodiments C1 to C23. Example Embodiment C28. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments C1 to C23. Example Embodiment C29. A non-transitory computer readable medium storinginstructions which when executed by a computer perform any of the methods of Example Embodiments C1 to 23. Group D Example Embodiments Example Embodiment D1. A method by a first network node for receiving an enhancedradio link failure (RLF), the method comprising: receiving information associated with a failureof a conditional handover (CHO) with candidate Secondary Cell Group (SCG) procedure for a User Equipment (UE). Example Embodiment D2. The method of Example Embodiment D1, wherein theinformation is transmitted in the RLF report. Example Embodiment D3. The method of any one of Example Embodiments D1 to D2,wherein the information comprises at least one of: a parameter indicating the failure of the CHOwith the candidate SCG procedure; a type of the failure of the CHO with the candidate SCGprocedure; an indication of a connection failure type; a new connection failure type indication; aRLF cause value. Example Embodiment D4. The method of any one of Example Embodiments D1 to D3,comprising transmitting, to the UE or another network node, a request for the information, and wherein the information is received in response to the request. Example Embodiment D5. The method of Example Embodiment D4, wherein therequest is transmitted in a UEInformationRequest message, and / or wherein the information is received in a UEInformationResponse message.Example Embodiment D6. The method of any one of Example Embodiments D1 to D5,wherein the information comprises an indication of a type of a last handover executed before detection of the failure. Example Embodiment D7. The method of any one of Example Embodiments D1 to D6,wherein the information comprises a list of candidate target Primary Secondary Cells (PSCells) atthe time of the failure of the CHO with candidate SCG configuration. Example Embodiment D8. The method of any one of Example Embodiments D1 to D7,wherein the information comprises an indication of an amount of elapsed time between a reception by the UE of a CHO with candidate SCG configuration and the occurrence / detection of the failure. Example Embodiment D9. The method of any one of Example Embodiments D1 to D8,wherein the information comprises an indication of a selected target PSCell in a failed execution of the CHO with candidate SCG. Example Embodiment D10. The method of any one of Example Embodiments D1 to D9,wherein the information comprises at least one value associated with a channel quality measurement for at least one candidate PCell and / or at least one candidate PSCell. Example Embodiment D11. The method of any one of Example Embodiments D1 toD10, wherein the information comprises location information associated with at least one of an MCG location configuration and a SCG location configuration. Example Embodiment D12. The method of any one of Example Embodiments D1 toD11, wherein the information comprises information associated with at least one of: a sourcePSCell, a target PSCell, and a failed PSCell. Example Embodiment D13. The method of any one of Example Embodiments D1 toD12, wherein the information comprises at least one of: information associated with a UE configuration at the time the RLF occurred / was detected, and information associated with an RLF event. Example Embodiment D14. The method of any one of Example Embodiments D1 toD13, wherein the information comprises at least one of: an indication of at least one configuredcondition that was fulfilled at the time the failure occurred, and an indication of at least oneconfigured condition that was not fulfilled at the time the failure occurred. Example Embodiment D15. The method of any one of Example Embodiments D1 toD14, wherein the information comprises an indication of whether, a condition that was not fulfilled when the failure was detected, was fulfilled before the RLF occurred and after the CHO with candidate SCG configuration was received at the UE. Example Embodiment D16. The method of any one of Example Embodiments D1 toD15, wherein the information comprises the smallest measured margin to fulfillment of anexecution condition for at least one of the non-selected / non-triggered candidate target PCell(s). Example Embodiment D17. The method of any one of Example Embodiments D1 to D16,wherein the information comprises the smallest measured margin to fulfillment of an executioncondition for at least one of the non-selected / non-triggered candidate target PSCell(s). Example Embodiment D18. The method of any one of Example Embodiments D1 toD17, wherein the information comprises at least one of: a list of candidate PCells for which anexecution condition for CHO was fulfilled but were not selected because an execution condition achange for PSCell was not fulfilled, and a list of candidate PSCells for which an executioncondition for change of PSCell was fulfilled but were not selected because an execution conditionfor CHO was not fulfilled. Example Embodiment D19. The method of any one of Example Embodiments D1 toD18, wherein the information comprises at least one of: an indication of whether an executioncondition for the CHO was fulfilled, and an indication of whether an execution condition for thePSCell change was fulfilled. Example Embodiment D20. The method of any one of Example Embodiments D1 toD19, wherein the information comprises at least one of: an indication of whether execution wasattempted and successful for a CHO part of the CHO with candidate SCG configuration, anindication of whether execution was attempted and successful for the PSCell part of the CHO withcandidate SCG configuration, an indication of whether execution was successful for the CHO partof the CHO with candidate SCG configuration, an indication of whether execution was successfulfor the PSCell part of the CHO with candidate SCG configuration, an indication of whetherexecution was attempted for the CHO part of the CHO with candidate SCG configuration, and anindication of whether execution was attempted for the PSCell part of the CHO with candidate SCG configuration. Example Embodiment D21. The method of any one of Example Embodiments D1 toD20, wherein the indication of the event detected by the UE comprises an indication of a RLF event detected by the UE. Example Embodiment D22. The method of any one of Example Embodiments D1 to D21, comprising transmitting the information to a second network node. Example Embodiment D23. The method of any one of Example Embodiments D1 toD22, wherein: the first network node is a source network node for the CHO with the candidateSCG procedure, the second network node is a target network node for the CHO with the candidateSCG procedure, and the information is received from the UE.Example Embodiment D24. The method of any one of Example Embodiments D1 toD22, wherein: the first network node is a source network node for the CHO with the candidateSCG procedure, the second network node is a target network node for the CHO with the candidateSCG procedure, and the information is received from the second network node.Example Embodiment D25. The method of any one of Example Embodiments D1 toD22, wherein: the first network node is a target network node for the CHO with the candidate SCGprocedure, the second network node is a source network node for the CHO with the candidate SCGprocedure, and the information is received from the UE.Example Embodiment D26. The method of any one of Example Embodiments D1 toD22, wherein: the first network node is a target network node for the CHO with the candidate SCGprocedure, the second network node is a source network node for the CHO with the candidate SCGprocedure, and the information is received from the second network node.Example Embodiment D27. The method of any one of Example Embodiments D1 toD22, wherein: the first network node is an unselected target network node for the CHO with thecandidate SCG procedure, the second network node is a source network node for the CHO withthe candidate SCG procedure, and the information is received from the UE or the second networknode. Example Embodiment D28. The method of any one of Example Embodiments D1 to D27, comprising transmitting the information to a second network node. Example Embodiment D29. The method of any one of Example Embodiments D1 toD28, comprising at least one of: based on the information, determining at least one CHO conditionfor a non-selected candidate PCell that was fulfilled while at least one condition of an associatedPSCell was not fulfilled; and transmitting, to the non-selected candidate PCell, at least one of: anindication of the associated PSCell for which the at least one condition was not fulfilled, and an indication of at least one condition that was not fulfilled.Example Embodiment D30. The method of any one of Example Embodiments D1 to D29comprising using the information to determine, for a subsequent CHO with candidate SCG procedure, at least one PSCell and / or at least one execution condition. Example Embodiment D31. The method of any one of Example Embodiments D1 toD30, wherein the network node comprises a gNodeB (gNB). Example Embodiment D32. The method of any of the previous Example Embodiments,further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.Example Embodiment D33. A network node comprising processing circuitry configuredto perform any of the methods of Example Embodiments D1 to D32. Example Embodiment D34. A network node configured to perform any of the methodsof Example Embodiments D1 to D32. Example Embodiment D35. A computer program comprising instructions which whenexecuted on a computer perform any of the methods of Example Embodiments D1 to D32. Example Embodiment D36. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments D1 to D32. Example Embodiment D38. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments D1 to D32. Group E Example Embodiments Example Embodiment E1. A user equipment for transmitting an enhanced radio linkfailure (RLF) report for conditional handover (CHO) with candidate Secondary Cell Group (SCG)failure, the UE comprising: processing circuitry configured to perform any of the steps of any ofthe Group A and C Example Embodiments; and power supply circuitry configured to supply powerto the processing circuitry. Example Embodiment E2. A network node for receiving an enhanced radio link failure(RLF) report for conditional handover (CHO) with candidate Secondary Cell Group (SCG) failure,the network node comprising: processing circuitry configured to perform any of the steps of; powersupply circuitry configured to supply power to the processing circuitry.Example Embodiment E3. A user equipment (UE) for transmitting an enhanced radiolink failure (RLF) report for conditional handover (CHO) with candidate Secondary Cell Group(SCG) failure, the UE comprising: an antenna configured to send and receive wireless signals;radio front-end circuitry connected to the antenna and to processing circuitry, and configured tocondition signals communicated between the antenna and the processing circuitry; the processingcircuitry being configured to perform any of the steps of any of the Group A and C ExampleEmbodiments; an input interface connected to the processing circuitry and configured to allowinput of information into the UE to be processed by the processing circuitry; an output interfaceconnected to the processing circuitry and configured to output information from the UE that hasbeen processed by the processing circuitry; and a battery connected to the processing circuitry andconfigured to supply power to the UE. Example Embodiment E4. A host configured to operate in a communication system toprovide an over-the-top (OTT) service, the host comprising: processing circuitry configured toprovide user data; and a network interface configured to initiate transmission of the user data to acellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A and C Example Embodiments to receive the user data from the host. Example Embodiment E5. The host of the previous Example Embodiment, wherein thecellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host. Example Embodiment E6. The host of the previous 2 Example Embodiments, wherein:the processing circuitry of the host is configured to execute a host application, thereby providingthe user data; and the host application is configured to interact with a client application executingon the UE, the client application being associated with the host application. Example Embodiment E7. A method implemented by a host operating in acommunication system that further includes a network node and a user equipment (UE), themethod comprising: providing user data for the UE; and initiating a transmission carrying the userdata to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.Example Embodiment E8. The method of the previous Example Embodiment, furthercomprising: at the host, executing a host application associated with a client application executingon the UE to receive the user data from the UE. Example Embodiment E9. The method of the previous Example Embodiment, furthercomprising: at the host, transmitting input data to the client application executing on the UE, theinput data being provided by executing the host application, wherein the user data is provided bythe client application in response to the input data from the host application. Example Embodiment E10. A host configured to operate in a communication system toprovide an over-the-top (OTT) service, the host comprising: processing circuitry configured toprovide user data; and a network interface configured to initiate transmission of the user data to acellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A and C Example Embodiments to transmit the user data to the host. Example Embodiment E11. The host of the previous Example Embodiment, wherein thecellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host. Example Embodiment E12. The host of the previous 2 Example Embodiments, wherein:the processing circuitry of the host is configured to execute a host application, thereby providingthe user data; and the host application is configured to interact with a client application executingon the UE, the client application being associated with the host application. Example Embodiment E13. A method implemented by a host configured to operate in acommunication system that further includes a network node and a user equipment (UE), themethod comprising: at the host, receiving user data transmitted to the host via the network nodeby the UE, wherein the UE performs any of the steps of any of the Group A and C Example Embodiments to transmit the user data to the host. Example Embodiment E14. The method of the previous Example Embodiment, furthercomprising: at the host, executing a host application associated with a client application executingon the UE to receive the user data from the UE. Example Embodiment E15. The method of the previous Example Embodiment, furthercomprising: at the host, transmitting input data to the client application executing on the UE, theinput data being provided by executing the host application, wherein the user data is provided bythe client application in response to the input data from the host application. Example Embodiment E16. A host configured to operate in a communication system toprovide an over-the-top (OTT) service, the host comprising: processing circuitry configured toprovide user data; and a network interface configured to initiate transmission of the user data to anetwork node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the networknode configured to perform any of the operations of any of the Group B and D ExampleEmbodiments to transmit the user data from the host to the UE. Example Embodiment E17. The host of the previous Example Embodiment, wherein: theprocessing circuitry of the host is configured to execute a host application that provides the userdata; and the UE comprises processing circuitry configured to execute a client applicationassociated with the host application to receive the transmission of user data from the host. Example Embodiment E18. A method implemented in a host configured to operate in acommunication system that further includes a network node and a user equipment (UE), themethod comprising: providing user data for the UE; and initiating a transmission carrying the userdata to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B and D Example Embodiments to transmit the user data from the host to the UE. Example Embodiment E19. The method of the previous Example Embodiment, furthercomprising, at the network node, transmitting the user data provided by the host for the UE. Example Embodiment E20. The method of any of the previous 2 Example Embodiments,wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application. Example Embodiment E21. A communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitryconfigured to provide user data for a user equipment (UE), the user data being associated with theover-the-top service; and a network interface configured to initiate transmission of the user datatoward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B and D Example Embodiments to transmit the user data from the host to the UE. Example Embodiment E22. The communication system of the previous ExampleEmbodiment, further comprising: the network node; and / or the user equipment.Example Embodiment E23. A host configured to operate in a communication system toprovide an over-the-top (OTT) service, the host comprising: processing circuitry configured toinitiate receipt of user data; and a network interface configured to receive the user data from anetwork node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B and D Example Embodiments to receive the user data from a user equipment (UE) for the host. Example Embodiment E24. The host of the previous 2 Example Embodiments, wherein:the processing circuitry of the host is configured to execute a host application, thereby providingthe user data; and the host application is configured to interact with a client application executingon the UE, the client application being associated with the host application. Example Embodiment E25. The host of the any of the previous 2 Example Embodiments,wherein the initiating receipt of the user data comprises requesting the user data. Example Embodiment E26. A method implemented by a host configured to operate in acommunication system that further includes a network node and a user equipment (UE), themethod comprising: at the host, initiating receipt of user data from the UE, the user data originatingfrom a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B and D Example Embodiments to receive the user data from the UE for the host. Example Embodiment E27. The method of the previous Example Embodiment, furthercomprising at the network node, transmitting the received user data to the host.

Claims

CLAIMS1. A method (600) performed by a User Equipment, UE, (112, 200) configured for aconditional handover, CHO, with candidate Secondary Cell Group, SCG, procedure, the methodcomprising: detecting (602) an event, and in response to detecting the event, logging (604) information associated with a Radio LinkFailure, RLF, or a failure of the CHO with candidate SCG procedure, or a successful execution ofthe CHO with candidate SCG procedure.

2. The method of Claim 1, comprising transmitting a Radio Link Failure, RLF, report to anetwork node (110, 300), the RLF report comprising the logging information associated with theRLF or the failure of the CHO with candidate SCG procedure.

3. The method of any one of Claims 1 to 2, wherein the event is associated with:a Radio Link Failure, RLF, a failure of the CHO with the candidate SCG procedure, or a successful execution of the CHO with the candidate SCG procedure.

4. The method of any one of Claims 1 to 3, wherein the information comprises a list ofcandidate target Primary Secondary Cells, PSCells, at the time of the RLF or the failure of theCHO with candidate SCG procedure, or the successful execution of the CHO with candidate SCGprocedure.

5. The method of any one of Claims 1 to 4, wherein the information comprises an indicationof a selected target PSCell in a failed execution of the CHO with candidate SCG.

6. The method of any one of Claims 1 to 5, wherein the information comprises at least oneof: aparameter indicating the RLF or the failure of the CHO with candidate SCG procedure,or the success of the CHO with candidate SCG procedure; a type of the failure of the CHO with the candidate SCG procedure;an indication of a connection failure type; anew connection failure type indication; anda RLF cause value.

7. The method of any one of Claims 1 to 6, wherein the information comprises an indicationof a type of a last handover executed before detection of the failure.

8. The method of any one of Claims 1 to 7, wherein the information comprises at least oneof: an indication of an amount of elapsed time between a reception by the UE of a CHO withcandidate SCG configuration and detecting the event, at least one value associated with a channel quality measurement for at least one candidate PCell and / or at least one candidate PSCell, and location information associated with at least one of an MCG location configuration and aSCG location configuration.

9. The method of any one of Claims 1 to 8, wherein at least one of:the information comprises an indication of whether, a condition that was not fulfilled whenthe failure was detected, was fulfilled before the RLF occurred and after the CHO with candidateSCG configuration was received at the UE; the information comprises a smallest measured margin to fulfillment of an executioncondition for at least one of the non-selected / non-triggered candidate target PCell(s); andthe information comprises a smallest measured margin to fulfillment of an execution condition for at least one of the non-selected / non-triggered candidate target PSCell(s).

10. The method of any one of Claims 1 to 9, wherein the information comprises at least oneof: alist of candidate Primary Cells, PCells, for which an execution condition for CHO wasfulfilled but the candidate PCells were not selected because an execution condition for a changefor Primary Secondary Cell, PSCell, was not fulfilled, anda list of candidate PSCells for which an execution condition for change of PSCell wasfulfilled but the candidate PSCells were not selected because an execution condition for CHO was not fulfilled.

11. The method of any one of Claims 1 to 10, wherein the information comprises at least oneof: an indication of whether an execution condition for the CHO was fulfilled, andan indication of whether an execution condition for the Primary Secondary Cell, PSCell,change was fulfilled.

12. The method of any one of Claims 1 to 11, wherein the information comprises at least oneof: an indication of whether execution was attempted and successful for a CHO part of theCHO with candidate SCG configuration, an indication of whether execution was attempted and successful for a Primary SecondaryCell, PSCell, part of the CHO with candidate SCG configuration,an indication of whether execution was successful for the CHO part of the CHO with candidate SCG configuration, an indication of whether execution was successful for the PSCell part of the CHO with candidate SCG configuration, an indication of whether execution was attempted for the CHO part of the CHO with candidate SCG configuration, and an indication of whether execution was attempted for the PSCell part of the CHO with candidate SCG configuration.

13. The method of any one of Claims 1 to 12, wherein the event detected by the UE comprisesan RLF event.

14. A method (800) by a first network node (110, 300) for receiving information for an eventdetected by a User Equipment, UE (112, 200), the method comprising:receiving (802) information associated with a Radio Link Failure, RLF, or a failure of aconditional handover, CHO, with candidate Secondary Cell Group, SCG, procedure or a successfulCHO with candidate SCG procedure for the UE.

15. The method of 14, wherein receiving the information comprises receiving the informationin one of a RLF report and Successful Handover Report.

16. The method of any one of Claims 14 to 15, comprising configuring the UE to detect anevent and transmit the information to the network node in response to detecting the event, andwherein the event is associated with at least one of:the RLF, a failure of the CHO with the candidate SCG procedure, and a successful execution of the CHO with the candidate SCG procedure.

17. The method of any one of Claims 14 to 16, wherein the information comprises a list ofcandidate target Primary Secondary Cells, PSCells, at the time of the failure of the RLF or the CHO with candidate SCG configuration.

18. The method of any one of Claims 14 to 17, wherein the information comprises an indicationof a selected target PSCell in a failed execution of the CHO with candidate SCG.

19. The method of any one of Claims 14 to 18, wherein the information comprises at least oneof: a parameter indicating the RLF or the failure of the CHO with the candidate SCG procedure; aparameter indicating the successful CHO with the candidate SCG procedure;a type of the failure of the CHO with the candidate SCG procedure; an indication of a connection failure type;a new connection failure type indication; anda RLF cause value.

20. The method of any one of Claims 14 to 19, wherein the information comprises at least oneof: an indication of an amount of elapsed time between a reception by the UE of a CHO with candidate SCG configuration and the occurrence / detection of the failure, at least one value associated with a channel quality measurement for at least one candidate PCell and / or at least one candidate PSCell, and location information associated with at least one of a MCG location configuration and a SCG location configuration.

21. The method of any one of Claims 14 to 20, wherein at least one of:the information comprises an indication of whether, a condition that was not fulfilled whenthe failure was detected, was fulfilled before the RLF occurred and after the CHO with candidateSCG configuration was received at the UE; the information comprises a smallest measured margin to fulfillment of an executioncondition for at least one of the non-selected / non-triggered candidate target PCell(s); andthe information comprises a smallest measured margin to fulfillment of an execution condition for at least one of the non-selected / non-triggered candidate target PSCell(s).

22. The method of any one of Claims 14 to 21, wherein the information comprises at least oneof: alist of candidate Primary Cells, PCells, for which an execution condition for CHO wasfulfilled but the candidate PCells were not selected because an execution condition a change forPrimary Secondary Cell, PSCell, was not fulfilled, anda list of candidate PSCells for which an execution condition for change of PSCell wasfulfilled but the candidate PSCells were not selected because an execution condition for CHO was not fulfilled.

23. The method of any one of Claims 14 to 22, wherein the information comprises at least oneof: an indication of whether an execution condition for the CHO was fulfilled, and an indication of whether an execution condition for the Primary Secondary Cell, PSCell, change was fulfilled.

24. The method of any one of Claims 14 to 23, wherein the information comprises at least oneof: an indication of whether execution was attempted and successful for a CHO part of the CHO with candidate SCG configuration, an indication of whether execution was attempted and successful for a Primary SecondaryCell, PSCell, part of the CHO with candidate SCG configuration,an indication of whether execution was successful for the CHO part of the CHO with candidate SCG configuration, an indication of whether execution was successful for the PSCell part of the CHO with candidate SCG configuration, an indication of whether execution was attempted for the CHO part of the CHO with candidate SCG configuration, and an indication of whether execution was attempted for the PSCell part of the CHO with candidate SCG configuration.

25. The method of any one of Claims 14 to 24, comprising transmitting the information to asecond network node (110, 300).

26. The method of Claim 25, wherein:the first network node is a source network node for the CHO with the candidate SCG procedure, the second network node is a target network node for the CHO with the candidate SCG procedure, and the information is received from the UE.

27. The method of Claim 25, wherein:the first network node is a source network node for the CHO with the candidate SCG procedure, the second network node is a target network node for the CHO with the candidate SCG procedure, and the information is received from the second network node.

28. The method of Claim 25, wherein:the first network node is a target network node for the CHO with the candidate SCG procedure, the second network node is a source network node for the CHO with the candidate SCG procedure, and the information is received from the UE.

29. The method of Claim 25, wherein:the first network node is a target network node for the CHO with the candidate SCG procedure, the second network node is a source network node for the CHO with the candidate SCG procedure, and the information is received from the second network node.

30. The method of Claim 35, wherein:the first network node is an unselected target network node for the CHO with the candidate SCG procedure, the second network node is a source network node for the CHO with the candidate SCG procedure, and the information is received from the UE or the second network node.

31. The method of any one of Claims 14 to 30, comprising at least one of:based on the information, determining at least one CHO condition for a non-selectedcandidate Primary Cell, PCell, that was fulfilled while at least one condition of an associatedPrimary Secondary Cell, PSCell, was not fulfilled; andtransmitting, to the non-selected candidate PCell, at least one of: an indication of the associated PSCell for which the at least one condition was not fulfilled, and an indication of at least one condition that was not fulfilled.

32. The method of any one of Claims 14 to 31, comprising using the information to determine,for a subsequent CHO with candidate SCG procedure, at least one Primary Secondary Cell, PSCell, and / or at least one execution condition.

33. A User Equipment, UE, (112, 200) configured for a conditional handover, CHO, withcandidate Secondary Cell Group, SCG, procedure, the UE comprising a memory (210) andprocessor (202), the UE configured to:detect an event, and in response to detecting the event, log information associated with a Radio Link Failure, RLF, or a failure of the CHO with candidate SCG procedure, or a successful execution of the CHO with candidate SCG procedure.

34. The UE of Claim 33, wherein the UE is configured to perform any of the methods of Claims2 to 13.

35. A network node (110, 300) for receiving information for an event detected by a UserEquipment, UE (112, 200), the network node comprising memory (304) and a processor (302), thenetwork node configured to:receive information associated with a Radio Link Failure, RLF, or a failure of a conditionalhandover, CHO, with candidate Secondary Cell Group, SCG, procedure, or a successful CHO withcandidate SCG procedure for the UE.

36. The network node of Claim 36, wherein the network node is configured to perform any ofthe methods of Claims 15 to 32.

Images