UE with configuration related to conditional handover with candidate secondary cell group procedure

Abstract

A method performed by a UE (10) for handling communication in a wireless communication network. The UE (10), when the UE is configured with a configuration related to CHO with a candidate SCG procedure, logs and / or sends information upon execution of an event, wherein the event is associated with or based on the configuration.

Description

[0001]NETWORK NODE, USER EQUIPMENT, AND METHODS PERFORMED THEREINTECHNICAL FIELDEmbodiments herein relate to a user equipment (UE), a network node, and methodsperformed therein regarding wireless communication. Furthermore, a computer program productand a computer readable storage medium are also provided herein. In particular, embodimentsherein relate to handling communication, such as handovers (HO), in a wireless communicationnetwork. BACKGROUND In a typical communication network, UEs, also known as wireless communication devices,mobile stations, stations (STA) and / or wireless devices, communicate via a Radio Access Network(RAN) with one or more core networks (CN). The RAN covers a geographical area which is dividedinto service areas or cells, with each service area or cell being served by a radio network nodesuch as an access node e.g. a Wi-Fi access point or a radio base station (RBS), which in somenetworks may also be called, for example, a NodeB, a gNodeB, or an eNodeB. The service area orcell is a geographical area where radio coverage is provided by the radio network node. The radionetwork node operates on radio frequencies to communicate over an air interface with the UEswithin range of the radio network node. The radio network node communicates over a downlink(DL) to the UE and the UE communicates over an uplink (UL) to the radio network node.A Universal Mobile Telecommunications System (UMTS) is a third generation (3G)telecommunication network, which evolved from the second generation (2G) Global System forMobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentiallya RAN using wideband code division multiple access (WCDMA) and / or High-Speed Packet Access(HSPA) for communication with user equipment. In a forum known as the Third GenerationPartnership Project (3GPP), telecommunications suppliers propose and agree upon standards forpresent and future generation networks and investigate e.g. enhanced data rate and radiocapacity. In some RANs, e.g. as in UMTS, several radio network nodes may be connected, e.g., bylandlines or microwave, to a controller node, such as a radio network controller (RNC) or a basestation controller (BSC), which supervises and coordinates various activities of the plural radionetwork nodes connected thereto. The RNCs are typically connected to one or more corenetworks. Specifications for the Evolved Packet System (EPS) have been completed within the 3GPPand coming 3GPP releases, such as New Radio (NR), are being worked on. The EPS comprisesthe Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known asSystem Architecture Evolution (SAE) core network. E-UTRAN / LTE is a 3GPP radio accesstechnology wherein the radio network nodes are directly connected to the EPC core network. Assuch, the Radio Access Network (RAN) of an EPS has an architecture comprising radio networknodes connected directly to one or more core networks.With the emerging 5G technologies such as NR, the use of very many transmit- andreceive-antenna elements may be of great interest as it makes it possible to utilize beamforming,such as transmit-side and receive-side beamforming. Transmit-side beamforming means that thetransmitter can amplify the transmitted signals in a selected direction or directions, whilesuppressing the transmitted signals in other directions. Similarly, on the receive-side, a receivercan amplify signals from a selected direction or directions, while suppressing unwanted signalsfrom other directions. NR is connected to the 5G Core Network (5GC) which comprises a numberof Network Functions (NF) such as Session Management Function (SMF), Access ManagementFunction (AMF), Authentication Service Function (AUSF), Policy Control Function (PCF), UnifiedData Manager (UDM), Network Repository Function (NRF), Network Exposure Function (NEF),just to mention some. In the 5GC, NFs can discover other NFs by using a discovery serviceprovided by the NRF.An overall 5G RAN (NG-RAN) architecture is depicted in Fig. 1.A conditional handover (CHO) is defined as a handover (HO) that is executed by the UEwhen one or more execution conditions are met. Upon receiving a CHO configuration, the UEstarts evaluating the conditions and stops once the handover is executed.In a configuration related to a CHO with candidate secondary cell group (SCG) procedure,the UE is configured with two configurations. One for performing primary cell (PCell) handover andanother for primary secondary cell (PSCell) change. Upon receiving such configuration, the UEevaluates both conditions and attempts to perform handover once both execution conditions aresatisfied. Self-Organizing Networks (SON) is a collection of functions for automatic configuration,optimization, and healing of networks. The aim of the framework is to perform routine maintenanceand 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 thefollowing: Successful Handover Report (SHR) is generated by a UE performing a PCell handover ifthe conditions set by the network are fulfilled. Generation of SHR refers to UE being close to failureof the handover.Successful PSCell Report (SPR) is generated by a UE performing a PSCell change if theconditions set by the network are fulfilled. Generation of SPR refers to the UE being close to failureof the PSCell change.If a radio resource control (RRC) connected UE declares radio link failure (RLF) it creates aRadio Link Failure report and network can fetch it from the UE. In an RLF report, the UE mayinclude necessary information and measurements for the network to analyze the radio conditionand possibly physical location of the UE. Network thus can take appropriate action or actions uponanalyzing the RLF report. There are multiple scenarios where the UE may declare radio link failure;and details can be found in 3GPP TS 38.300 V18.0.0 and 3GPP TS 38.331 V18.0.0.A UE operating in dual connectivity may encounter problems in the SCG and declare failureon a SCG leg. If the connection to a Master Cell Group (MCG) leg is active, the UE does notdeclare radio link failure, it sends a SCGFailureInformation message to a master node (MN). Uponreceiving the message, the MN can take necessary actions to solve the problems.SUMMARY As part of developing embodiments herein one or more issues have been identified. Incurrent standards, if the network configures the UE with a CHO with candidate SCG configurationand if the UE fails or nearly fails to execute the configuration, the network does not have anyinformation to analyse the root cause of such problem at the UE. Hence, the network is not able tooptimize its configuration resulting in a limited or reduced performance of the wirelesscommunication network.An object of embodiments herein is to improve performance of a wireless communicationnetwork. According to an aspect the object is achieved, according to some embodiments herein, byproviding a method performed by a UE for handling communication, such as enabling mobilitymanagement, in a wireless communication network. The UE, configured with a configurationrelated to a CHO with candidate SCG procedure, logs and / or sends information upon execution ofan event, wherein the event is associated with or based on the configuration.According to another aspect the object is achieved, according to some embodimentsherein, by providing a method performed by a network node, such as a radio network node, forhandling communication in a wireless communication network. The network node receivesinformation, or a report with information, from a UE, wherein the information comprises informationrelated to an event, wherein the event is associated with or based on a configuration related to aCHO with candidate SCG procedure. The network node performs an operation based on thereceived information, or the received report with information.It is furthermore provided herein a computer program product comprising instructions,which, when executed on at least one processor, cause the at least one processor to carry out themethods herein, as performed by the network node and the UE, respectively. It is additionallyprovided herein a computer-readable storage medium, having stored thereon a computer programproduct comprising instructions which, when executed on at least one processor, cause the at leastone processor to carry out the methods herein, as performed by the network node and the UE,respectively. Furthermore, according to another aspect the object is achieved, according to someembodiments herein, by providing a network node and a UE configured to perform the methodsherein, respectively.Thus, according to an aspect the object is achieved, according to some embodimentsherein, by providing a UE for handling communication, such as enabling mobility management, in awireless communication network. The UE is configured with a configuration related to a CHO withcandidate SCG procedure and is further configured to log and / or send information upon executionof an event, wherein the event is associated with or based on the configuration.According to another aspect the object is achieved, according to some embodimentsherein, by providing a network node, such as a radio network node, for handling communication ina wireless communication network. The network node is configured to receive information, or areport with information, from a UE, wherein the information comprises information related to anevent, wherein the event is associated with or based on a configuration related to a CHO withcandidate SCG procedure. The network node is configured to perform an operation based on thereceived information, or the received report with information.The information may comprise additional information, for example, in a SON report orreports, if the UE is configured with CHO with candidate SCG configuration and performs anevent based on it. The information may comprise timer related information, measurement resultsor some other form of indication based on different scenarios. The UE may succeed to perform ahandover based on the configuration and include the information in a given set of reports and / orthe UE may declare RLF or SCG failure and include the information in another set of reports.Upon reception of the report from UE, the network node receiving the report may identify thenetwork node where the optimization is required and may forward the report to that networknode. It is proposed herein to provide a solution allowing the UE to report time instances and / ordifference between fulfillment of the execution condition of one or more events configured in theCHO with candidate SCG configuration. With, for example, time information of the informationreported, the network node may be able to optimize the execution conditions of PCell handoverand PSCell change included in the CHO with candidate SCG configuration. Other information likemeasurement results or some form of indication as proposed in embodiments herein may also aidin performing network optimization. Such optimization may ensure less failure in the wirelesscommunication network and thus increase robustness and thereby performance of the wirelesscommunication network.BRIEF DESCRIPTION OF THE DRAWINGSEmbodiments will now be described in more detail in relation to the enclosed drawings, inwhich: Fig. 1 shows an overview depicting a 5G architecture;Fig. 2 shows an overview depicting a wireless communication network according toembodiments herein;Fig. 3a is a combined flowchart and signaling scheme according to some embodimentsherein; Fig. 3b is a flowchart of a method performed by a UE according to some embodimentsherein; Fig. 3c is a flowchart of a method performed by a network node according to someembodiments herein;Fig. 4 shows a block diagram depicting embodiments of a UE according to embodimentsherein; Fig. 5 shows a block diagram depicting embodiments of a network node according toembodiments herein;Fig. 6 schematically illustrates embodiments of a communication system,Fig. 7 is a generalized block diagram of embodiments of a wireless device,Fig. 8 is a generalized block diagram of embodiments of a network node, andFig. 9 is a generalized block diagram of embodiments of a virtualization environment.DETAILED DESCRIPTIONEmbodiments herein relate to communication networks in general. Fig. 2 is a schematicoverview depicting a wireless communication network 1. The communication network 1comprises one or more RANs and one or more CNs. The communication network 1 may use oneor a number of different technologies. Embodiments herein relate to recent technology trends thatare of particular interest in a New Radio (NR) context, however, embodiments are also applicablein further development of existing wireless communications systems such as e.g. 6G, LTE orWideband Code Division Multiple Access (WCDMA).In the wireless communication network 1, a user equipment (UE) 10 exemplified herein asa wireless device such as a mobile station, a non-access point (non-AP) station (STA), a STAand / or a wireless terminal, is comprised communicating via e.g. one or more Access Networks(AN), e.g. radio access network (RAN), to one or more core networks (CN). It should beunderstood by the skilled in the art that “UE” is a non-limiting term which means any terminal,wireless communications terminal, user equipment, narrowband internet of things (NB-IoT) device,Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smartphone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable ofcommunicating using radio communication with a radio network node within an area served by theradio network node.The wireless communication network 1 comprises a first radio network node 12 or justradio network node, providing radio coverage over a geographical area, a first service area 11 orfirst cell, of a first radio access technology (RAT), such as 6G, NR, LTE, or similar. The radionetwork node 12 may be a transmission and reception point such as an access node, an accesscontroller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B(eNB, eNode B), a NodeB, a master node, base transceiver station, a radio remote unit, an AccessPoint Base Station, a base station router, a Wireless Local Area Network (WLAN) access point oran Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a UE withinthe area served by the first radio network node depending e.g. on the first radio access technologyand terminology used. The first radio network node 12 may be referred to as a serving radionetwork node wherein the first service area 11 may be referred to as a serving cell or primary cell,and the serving radio network node 12 communicates with the UE 10 in form of DL transmissionsto the UE 10 and UL transmissions from the UE 10. It should be noted that a service area may bedenoted as cell, beam, beam group or similar to define an area of radio coverage.The wireless communication network 1 comprises a second radio network node 13 orjust radio network node, providing radio coverage over a geographical area, a second servicearea 14 or second cell, of a second radio access technology (RAT), such as 6G, NR, LTE, orsimilar. The second radio network node 13 may be a transmission and reception point such as anaccess node, an access controller, a base station, e.g. a radio base station such as a gNodeB(gNB), an evolved Node B (eNB, eNode B), a NodeB, a secondary node (SN), a base transceiverstation, a radio remote unit, an Access Point Base Station, a base station router, a Wireless LocalArea Network (WLAN) access point or an Access Point Station (AP STA), a transmissionarrangement of a radio base station, a stand-alone access point or any other network unit or nodecapable of communicating with a wireless device within the area served by the second radionetwork node depending e.g. on the first radio access technology and terminology used. Thesecond radio network node 13 may be referred to as a visiting radio network node or target radionetwork node, wherein the second service area 14 may be referred to as a visiting cell, secondaryprimary cell, or target cell, and the second radio network node 13 communicates with the UE 10 inform of DL transmissions to the UE 10 and UL transmissions from the UE 10. It should be notedthat a service area may be denoted as cell, beam, beam group or similar to define an area of radiocoverage. The first RAT may be the same RAT as the second RAT or the first RAT may be a differentRAT than the second RAT.The wireless communication network 1 may further comprise a number of core networknodes providing, e.g. in NR, NFs or actually instantiations of NFs also referred to as NF instances,such as a first network node 16 providing, for example, an instantiation of a mobility managemententity (MME) and a second network node 17 providing an instantiation of a AMF or an SMF; orany other NF instances in the communication network 1. The different NF instances may havedifferent tasks of same or different technologies such as 6G, NR and / or LTE.The respective node may be a standalone server, a cloud-implemented server, adistributed server or processing resources in a server farm or same node. Embodiments hereinmay be implemented as physical bare metal, virtual or cloud native such as Kubernetesenvironment in, e.g., hyper-cloud networks.According to embodiments herein a network node 150 is provided for communicating withthe UE 10. The network node 150 may comprise the first radio network node 12, the second radionetwork node 13, the first network node 16 and / or the second network node 17.According to embodiments herein additional information are included in one or morereports from the UE 10 to the network node 150, such as in SON report or reports, if the UE 10 isconfigured with a configuration related to CHO with candidate SCG -procedure and performs anevent based on the configuration. The configuration may comprise information such as timerrelated information, measurement results and / or some other form of indication based on differentscenarios. The UE 10 may succeed to perform the handover based on the configuration andinclude the information in, for example, a given set of reports or it may declare RLF or SCGfailure and include the information in another set of reports. Upon reception of the report from UE10, the network node 150 receiving the information may identify a certain network node whereoptimization is required and may forward the report to that certain network node.Thus, it is herein provided a method performed by the UE 10 in the wireless communicationnetwork 1, where the UE 10, configured with a configuration related to a CHO with candidate SCGprocedure, logs and / or sends information upon execution of an event, wherein the event isassociated with or based on the configuration. For example, the execution of the event may occurwhen one or more conditions of the configuration are fulfilled.According to embodiments herein the UE 10 may receive the configuration comprisingCHO with candidate SCG configuration from the network, such as the network node 150.^ The UE 10 may execute an event. Non limiting examples of the event are:o The UE 10 may declare radio link failure before executing the CHO with candidatecell configuration.o The UE 10 may declare handover failure during execution of the CHO withcandidate cell configuration.o The UE 10 may declare radio link failure upon successful execution of CHO withcandidate cell configuration.o The UE 10 may declare radio link failure in the SCG leg before execution of CHOwith candidate cell configuration.o The UE 10 may declare handover failure for the secondary leg during execution ofCHO with candidate cell configuration.o The UE 10 may declare radio link failure in the secondary leg upon execution ofCHO with candidate cell configuration.o The UE 10 may perform PCell handover and PSCell change based on the CHO withcandidate cell configuration.^ The UE 10 logs information in a report towards a RAN node, being an example of thenetwork node 150, and / or sends the information to the RAN node in a message.o The report where the UE 10 logs the information may be dependent on differentscenarios. Some non-limiting examples are:^ RLF report if the UE 10 declares radio link failure or handover failure.^ SHR and SPR report if the UE 10 successfully performs PCell and PSCellhandover. ^SCGFailureInformation message if the UE 10 declares radio link failure orhandover failure for the secondary leg to the PSCell.o Some examples of the information reported are:^ The information may comprise logging time difference between fulfilling theexecution condition for Handover and fulfilling the execution condition forPSCell change.^ If only one of the conditions is fulfilled, i.e., either the executioncondition for Handover or the execution condition for PSCell change;the UE 10 may log indication indicating which event condition wasfulfilled. ^If only one of the conditions is fulfilled, i.e., either the executioncondition for Handover or the execution condition for PSCell change;the UE 10 may log the measurement results based on which the UE10 was evaluating the execution condition that remained unfulfilled.^ The information may comprise logging time difference between fulfilling theexecution condition for Handover and fulfilling the execution condition forPSCell change and the measurement results, which the UE 10 used toevaluate the execution conditions.^ The information may comprise logging time instances of fulfilling theexecution conditions of Handover and PSCell change.^ The time instances may be absolute time instances when theexecution conditions are fulfilled.^ The time instances may be calculated as the time differencesbetween configuration of the CHO with candidate SCG configurationand the fulfillment of the execution conditions.^ The information may comprise logging time instances of fulfilling theexecution conditions of Handover and PSCell change and the measurementresults, which the UE 10 was using to evaluate the execution conditions.^ If none of the configured execution conditions are fulfilled, the UE 10 mayinclude the measurement results based on which the UE 10 was evaluatingthe execution conditions.The network node 150, such as the first 12 or the second radio network node 13, receivingthe report and / or information from the UE 10 may analyze the report and / or information reported bythe UE 10 and performs an operation based on the report and / or information. The network node150 may distribute the report and / or information to one or more RAN nodes in charge of theconfigurations and / or policies leading to suboptimal performance revealed by the report and / orinformation reported by the UE 10. The RAN node, also referred to herein as a certain networknode, receiving the information may analyze the information and may apply adjustments to, forexample, their policies, configurations, and / or resource handling procedures, so to improve UEperformance. It should be noted that a UE is referred to as any device using the service of a wirelesscommunication network. A network node is referred to a node capable of providing service to a UE.Execution of an event refers to any state change or mobility action performed by the UE 10.Fig.3a is a combined flow chart and signaling scheme according to some embodimentsherein. Actions performed in some embodiments are marked with dashed lines.Action 301. The network node 150 may transmit to the UE 10 the configuration related tothe CHO with candidate cell, such as SCG, procedure. Thus, the UE 10 may receive theconfiguration from one or more network nodes.Action 302. The UE 10 may execute an event taking the configuration into account.Examples of the event may be one or more of the following: the UE 10 may declare radio linkfailure before executing the CHO with candidate cell configuration; the UE 10 may declarehandover failure during execution of the CHO with candidate cell configuration; the UE 10 maydeclare radio link failure upon successful execution of CHO with candidate cell configuration; theUE 10 may declare radio link failure in the SCG leg before execution of CHO with candidate cellconfiguration; the UE 10 may declare handover failure for the secondary leg during execution ofCHO with candidate cell configuration; the UE 10 may declare radio link failure in the secondaryleg upon execution of CHO with candidate cell configuration; and / or the UE 10 may perform PCellhandover and PSCell change based on the CHO with candidate cell configuration. The UE 10may, for example, succeed to perform a handover and / or cell change based on the configuration.Action 303. The UE 10, configured with the configuration related to the CHO withcandidate cell or SCG procedure, logs and / or sends information upon execution of the event,wherein the event is associated with or based on the configuration. The UE 10 may log informationupon execution of the event, wherein the event is associated or based on the configuration.Additional information may thus be included in SON report(s) if the UE 10 is configured with CHOwith candidate SCG configuration and the UE 10 performs an event based on it. The informationmay comprise timer related information, measurement results or some other form of indicationbased on different scenarios. The information may indicate or be associated with RLF or SCGfailure. Action 304. The network node 150 may in some embodiments receive the report and / orinformation from the UE 10, wherein the information comprises the information related to the event,wherein the event is associated with or based on the configuration related to CHO with candidatecell, or SCG, procedure.Action 305. The network node 150 may in some embodiments analyze the report and / orinformation reported by the UE 10.Action 306. The network node 150 performs an operation based on the report and / orinformation. The UE 10 may include the information in a given set of reports or the UE 10 maydeclare RLF or SCG failure and include the information in another set of reports. Upon receptionof the report from UE 10, the network node 150 receiving the report may identify the certainnetwork node where optimization is required and forward the report to that certain network node.The network node 150 may optimize one or more parameters related to mobility and / or an eventbased on the report and / or information.The method actions performed by the UE 10 for handling communication in the wirelesscommunication network 1, according to embodiments herein will now be described with referenceto a flowchart depicted in Fig. 3b. The actions do not have to be taken in the order stated below,but may be taken in any suitable order. Actions performed in some embodiments are marked withdashed boxes.Action 311. The UE 10 may receive, from the network node 150, the configuration relatedto the CHO with candidate SCG procedure.Action 312. The UE 10 may execute the event taking the configuration into account.Action 313. The UE 10, when the UE 10 is configured with the configuration related toCHO with candidate SCG procedure, logs and / or sends information upon execution of the event,wherein the event is associated with or based on the configuration, e.g., as indicated in theconfiguration. The information may comprise timer related information, and / or measurementresults, which the UE 10 used to evaluate one or more execution conditions. The information maycomprise measurement results of PCells and PSCells and time information and may becomprised in SHR and SCGFailureInformation. The information may indicate a time intervalbetween a CHO execution fulfillment and a detection of at least one of an SCG Failure or an RLF.For example, the information may comprise elapsed time between a point in time of a first fulfilledcondition and RLF. The information may be sent in an RLF report and / or a SCG failure report. Theinformation may comprise one or more PCell identities and / or one or more PSCell identitiescorresponding to one or more cells for which an execution condition for PCell Handover and / or anexecution condition for PSCell Change were satisfied. For example, the information may compriseone or more identifiers of candidate PCell(s) which met the configured CHO execution conditionswhen the RLF is encountered, one or more identifiers of candidate PSCell(s) which met theconfigured conditional PSCell addition and change (CPAC) execution conditions when the RLF isencountered, and / or one or more identifiers of candidate PCell(s) or PSCell(s) that fulfilledexecution conditions before the RLF is encountered. The information may comprise a timeelapsed between a first time of a first fulfilled triggering event for a first fulfilled execution conditionand a second time of a fulfilled triggering event for a second execution condition. The informationmay comprise an indication indicating whether the first fulfilled execution condition is associatedwith a CHO configuration or with a conditional SCG configuration, and an indication indicatingwhether the second execution condition is associated with the CHO configuration or with theconditional SCG configuration.UE Embodiments:The network node 150 may configure the UE 10 with CHO with candidate SCGconfiguration, where the CHO with candidate SCG configuration comprises execution conditions,each may comprise two triggering events, for conditional PCell change and conditional PSCellchange. The UE 10, upon occurrence of an event and in response to the event, may comprise andlog a set of information in a report, where the report is specific to the event.Embodiments describing the information logged and / or sent to the network node 150:In an embodiment, the set of information comprise the time difference between thefulfillment of execution conditions for conditional PCell handover and / or PSCell changes, such asfulfillment of the execution conditions of CHO with candidate SCG, and the execution of PCellhandover and / or PSCell change.In another embodiment, the UE 10 includes two indications, e.g. two flags, the firstindication indicating whether the event associated with the CHO was fulfilled and the secondindication indicating whether the event associated with the conditional SCG was fulfilled. Forinstance, the UE 10 may report a bitmap comprising of two bits, with the value of the first bitindicating whether the event associated with the CHO was fulfilled or not, and the second bitindicating whether the event associated with the conditional SCG was fulfilled or not.In another embodiment, the UE 10 includes two indications, e.g., two flags, indicating theorder of fulfillment for CHO and conditional PSCell Change and whether there was a fulfillment forany of the CHO and Conditional PSCell Change related event. For instance, the first indicationindicates which one of CHO or Conditional PSCell Change was fulfilled first, and the secondindication indicating that Conditional PSCell Change event was fulfilled as second. Absence ofsecond flag implicitly indicates that Conditional PSCell Change related event was not fulfilled.In another embodiment, the UE 10 implicitly indicates that one of the events, for example,the one event associated with CHO, or the one event associated with the conditional SCG, wasfulfilled or not fulfilled. An example may be that the UE 10 logs, and may later report, oneindication, e.g., a flag, comprising of a single bit. In this example, when the flag is absent itindicates that the event associated with CHO was fulfilled. This may be used, e.g., to indicate thateven if CHO with candidate SCG was configured, the UE 10 may fallback to CHO. Instead, whenthe flag is present, and its value is X, e.g., ‘0’, it carries the meaning that the event associated withthe conditional SCG was fulfilled but the event associated with the CHO was not fulfilled, and if thevalue of the flag is Y, e.g., ‘1’, it carries the meaning that both the events associated with the CHOand the event associated with the candidate SCG were fulfilled.In another embodiment, the UE 10 logs, and may later report, a piece of informationspecific for the CHO with the candidate SCG, where the information explicitly or implicitly indicateswhether the event, also referred to as CHO related event, was fulfilled or not, and whether anotherevent, such as conditional SCG event, was fulfilled or not, by indicating information, e.g., theMeasId parameters, identifying the conditions for CHO, for example, a PCell handover, and theconditions for Conditional PSCell Change. For example, the UE 10 may log, and may later report,an indication that conveys the following two pieces of information: a first piece of information thatindicates whether only one triggering condition for CHO, or both triggering conditions for CHO werefulfilled, e.g., indicating the associated MeasId parameters; and a second piece of information thatindicates whether only one triggering condition associated to candidate SCG, or both triggeringconditions associated to conditional SCG were fulfilled.In one embodiment, when the UE 10 is configured with CHO with candidate SCG, the UE10 logs in a same report, e.g., an RLF report, or an SHR, or an SPR, the PCell identities and / or thePSCell identities corresponding to the cells for which the execution condition(s) for PCell Handoverand / or the execution condition(s) for PSCell Change were satisfied.In one embodiment, when the UE 10 is configured with CHO with candidate SCG, the UE10 may log in a same report, e.g., an RLF report, or an SHR, or an SPR, one or more PCellidentities and / or PSCell identities for cells not included in the list of candidate cells for ConditionalHandover nor in the list of candidate cells for Conditional PSCell Change, for example, in onevariant, only for those cells for which the respective execution conditions for CHO or PSCellChange were satisfied.In another embodiment, the UE 10 may include an indication indicating which triggeringevent was fulfilled first, i.e., the triggering event associated to the CHO and / or the triggering eventassociated to the conditional SCG.In another embodiment, the UE 10 may include an indication indicating which executioncondition, including one or two triggering events, was fulfilled first, i.e., the execution conditionsassociated with the CHO and / or the execution conditions associated with the conditional SCG.In another embodiment, the set of information may comprise of a finer granularity set ofdata such as:^ Time elapsed between the time of first fulfilled triggering event for the first fulfilled executionconditions to the time of first fulfilled triggering event for the second execution condition.The UE 10 may also include an indication indicating whether the first fulfilled executionconditions is associated with the CHO configuration or with the conditional SCGconfiguration, and an indication indicating whether the second fulfilled execution conditionsis associated with the CHO configuration or with the conditional SCG configuration.^ Time elapsed between the time of first fulfilled triggering event for the first fulfilled executionconditions to the time of last fulfilled triggering event for the second execution condition.The UE 10 may also include an indication indicating whether the first fulfilled triggeringevent is associated with the CHO configuration or with the conditional SCG configuration,and an indication indicating whether the last fulfilled triggering event is associated with theCHO configuration or with the conditional SCG configuration.^ Time elapsed between the time of a last fulfilled triggering event to the time of failure atPCell and / or PSCell.^ Time elapsed between the time of first fulfilled triggering event for the first fulfilled executionconditions to the time of second fulfilled triggering event for the first execution condition,and the time elapsed between the time of first fulfilled triggering event for the secondfulfilled execution conditions to the time of second fulfilled triggering event for the secondexecution condition.^ Time since CHO execution fulfillment and the detection of the SCG Failure or RLF^ Time since the fulfillment of the last triggering event associated with the CHO and thedetection of the SCG Failure or RLF^ Time since the fulfillment of the first triggering event associated with the CHO and thedetection of the SCG Failure or RLF^ Time since candidate SCG execution condition fulfillment and the detection of the SCGFailure or RLF^ Time since the fulfillment of the last triggering event associated with the candidate SCGexecution and the detection of the SCG Failure or RLF^ Time since the fulfillment of the first triggering event associated with the candidate SCGexecution condition and the detection of the SCG Failure or RLF^ Time since the last occurrence of fulfillment of at least one triggering condition for CHO andthe detection of the SCG Failure or RLF^ Time since the last occurrence of fulfillment of at least one triggering condition for executionof PSCell change and detection of SCG Failure or RLF^ Time since the of most recent fulfillment of at least one triggering condition for CHO and thetime of most recent fulfillment of at least one triggering condition for execution of PSCellchange and detection of SCG Failure or RLF^ Time since the fulfillment of at least one triggering condition for CHO and time of fulfillmentof at least one triggering condition for PSCell changeo In a variant of this, two optional fields are used, and absence of one of themindicates that conditions for the associated event (CHO or PSCell change) were notfulfilled. ^Time since the most recent fulfillment of at least one triggering condition for CHO and timeof the most recent fulfillment of at least one triggering condition for PSCell changeo In a variant of this, two optional fields are used, and absence of one of themindicates that conditions for the associated event (CHO or PSCell change) were notfulfilled. In another embodiment, the set of information comprises of a yet finer granularity set ofdata, taking into account that an execution condition may be fulfilled, corresponding to its enteringcondition being satisfied, and then unfulfilled, corresponding to its leaving condition being satisfied,then fulfilled again and later unfulfilled again, etc. That is, an execution may toggle between beingfulfilled and not being fulfilled. An execution condition, for the CHO for the PCell, or for a candidateSCG,may comprise of one or two conditions, each may be identified by a MeasId, and all theconditions, i.e., both conditions in case of two conditions, have to be fulfilled for the execution to betriggered. Furthermore, for a CHO with candidate SCG as a complete procedure to be executed,both the execution condition for the CHO and the execution condition for the candidate SCG haveto be fulfilled. One may therefore look at condition fulfillment on three different levels differentlevels of granularity:A. Condition fulfillment for the complete CHO with candidate SCG procedure. That is,condition fulfillment resulting in execution of the complete CHO with candidate SCGprocedure. B. Condition fulfillment per partial procedure, i.e., looking separately at condition fulfillment forCHO execution on the one hand and condition fulfillment for the candidate SCG on theother hand. Note that both have to be fulfilled for execution of both PCell handover andPSCell change to take place.C. Individual conditions constituting parts of an execution condition for a partial procedure.That is, for example, in case the execution condition for the CHO comprises of twoconditions, for example, identified by two MeasId parameters, the fulfillment of each ofthose conditions may be considered separately. Similarly, if the execution condition for acandidate SCG comprises of two conditions, for example, identified by two MeasIdparameters, the fulfillment of each of those conditions may be considered separately.Based on the above elaborated levels of granularity, such as A, B and C, a set ofinformation that takes toggling between fulfillment and unfulfillment into account on granularity levelB may include indications showing the times when each execution condition became fulfilled andthen became unfulfilled, i.e., the times of changes between unfulfillment and fulfillment and viceversa of an execution condition may be indicated in the set of information, and this may be donefor each of the execution condition for the CHO and the execution condition for the candidate SCG.Note that with this principle, if an execution condition is never fulfilled, no times may be indicated inthe set of information. An example of how such times may be indicated in the set of informationmay be e.g.:- One list of time indications per partial procedure, i.e., one list of time indications for theexecution condition for the CHO and one list of time indications for the execution conditionfor the candidate SCG, that is:o A list of time indications for the execution condition for the CHO, where the first timeindication indicates the first time the execution condition became fulfilled, thesecond time indication indicates the first time the execution condition went frombeing fulfilled to being unfulfilled, the third time indication indicates the second timethe execution condition went from being unfulfilled to being fulfilled, the fourth timeindication indicates the second time the execution condition went from being fulfilledto being unfulfilled, and so on.o A list of time indications for the execution condition for the candidate SCG, wherethe first time indication indicates the first time the execution condition becamefulfilled, the second time indication indicates the first time the execution conditionwent from being fulfilled to being unfulfilled, the third time indication indicates thesecond time the execution condition went from being unfulfilled to being fulfilled, thefourth time indication indicates the second time the execution condition went frombeing fulfilled to being unfulfilled, and so on.Note that each of the above two lists may comprise zero or more time indications,depending on how many times the respective execution condition changed itsfulfillment / unfulfillment status. A time indication in such a list may have various types. One exampleof a type of time indication may be that the indication indicates the elapsed time since the UE 10received the CHO with candidate SCG configuration. Another example of a type of time indicationmay be the elapsed time since the time indicated by the preceding time indication in the same list.These two types of time indication types may also be combined in a list, e.g., with the first timeindication in the list indicating the elapsed time since the UE 10 received the CHO with candidateSCG configuration, while the subsequent time indications in the same list indicate the elapsed timesince the time indicated by the preceding time indication in the same list.A similar principle may be used for taking toggling between condition fulfillment andcondition unfulfillment into account on granularity level C. That is, for each condition on granularitylevel C, where each condition is identified by a MeasId, there may be an associated list of timeindications indicating the times when the fulfillment / unfulfillment status changes for the condition.Each such list may for example include time indications according to the same principle and of thesame types as described above for lists used for granularity level B.In another embodiment, the set of information comprises information aboutfulfillment / unfulfillment of each execution condition and / or whether the different executionconditions were at any point in time both fulfilled, such that the execution of the complete CHO withcandidate SCG procedure was triggered. In an example of this embodiment, the set of informationmay comprise the following indications:- A BOOLEAN indication indicating whether the execution condition for the CHO was fulfilledat least one point in time (indication = TRUE) or not (indication = FALSE).- A BOOLEAN indication indicating whether the execution condition for the candidate SCGwas fulfilled at least one point in time (indication = TRUE) or not (indication = FALSE).- A BOOLEAN indication indicating whether the execution condition for the CHO and theexecution condition for the candidate SCG were at least one point in time both fulfilled(indication = TRUE) or not (indication = FALSE).- A BOOLEAN indication indicating whether the execution condition for the CHO was fulfilledat least one point in time AND none of the execution condition for the candidate SCG werefulfilled -A BOOLEAN indication indicating whether the execution condition for the CHO was neverfulfilled while at least one point in time one (or more) execution condition(s) for thecandidate SCG was(were) fulfilled.- A BOOLEAN indication indicating that neither the execution condition for the CHO nor anyexecution condition(s) for the candidate SCG were fulfilled.As a variation, the set of information may comprise information aboutfulfillment / unfulfillment of each granularity level C condition and / or whether the different granularitylevel C conditions, for the same execution condition, were at any point in time both fulfilled suchthat the execution condition the combination of the granularity level C conditions constitute wasfulfilled at that point in time. In an example of this variation of the embodiment, the set ofinformation comprises the following up to six indications:- A BOOLEAN indication indicating whether the first granularity level C condition being partof the execution condition for the CHO was fulfilled at least one point in time (indication =TRUE) or not (indication = FALSE).- A BOOLEAN indication indicating whether the second granularity level C condition beingpart of the execution condition for the CHO was fulfilled at least one point in time (indication= TRUE) or not (indication = FALSE). Note that this indication may be absent if theexecution condition for the CHO comprises of only one granularity level C condition, i.e., acondition identified by a MeasId.- A BOOLEAN indication indicating whether the first and the second granularity level C beingpart of the execution condition for the CHO were at least one point in time both fulfilled(indication = TRUE) or not (indication = FALSE). Note that this indication may be absent ifthe execution condition for the CHO comprises of only one granularity level C condition,i.e., a condition identified by a MeasId.- A BOOLEAN indication indicating whether the first granularity level C condition being partof the execution condition for the candidate SCG was fulfilled at least one point in time(indication = TRUE) or not (indication = FALSE).- A BOOLEAN indication indicating whether the second granularity level C condition beingpart of the execution condition for the candidate SCG was fulfilled at least one point in time(indication = TRUE) or not (indication = FALSE). Note that this indication may be absent ifthe execution condition for the candidate SCG comprises of only one granularity level Ccondition, i.e., a condition identified by a MeasId.- A BOOLEAN indication indicating whether the first and the second granularity level C beingpart of the execution condition for the candidate SCG were at least one point in time bothfulfilled (indication = TRUE) or not (indication = FALSE). Note that this indication may beabsent if the execution condition for the candidate SCG comprises of only one granularitylevel C condition, i.e., a condition identified by a MeasId.The above list of BOOLEAN indications might be complemented by a BOOLEAN indicationindicating whether all, i.e., up to 4, granularity level C conditions, i.e., the granularity level Ccondition(s) constituting the execution condition for the CHO and the granularity level C conditionsconstituting the execution for the candidate SCG, were at least one point in time all fulfilled.Alternatively, this BOOLEAN indication may replace the two BOOLEAN indications of simultaneousgranularity level C condition fulfillment in the list above.Note that using BOOLEAN type indications, as above, is only an example. Anotherexample to achieve the same purpose in ASN.1 is to use an optional ENUMERATED typeparameter with the only possible value being “true”.In another embodiment, the set of information includes the time difference between thefulfillment of execution condition of PCell handover and reception of the handover command fromthe source RAN node. The set of information further comprises of the time difference betweenfulfillment of execution condition of PSCell change and reception of the handover command fromthe source RAN node.In another embodiment, if one of the PCell handover or PSCell change execution conditionis fulfilled, the UE 10 includes the time difference between the fulfillment of the execution conditionand reception of the handover command from the source RAN nodeconfiguration . The UE 10includes an indication indicating the other execution condition was not fulfilled.In another embodiment, if one of the PCell handover or PSCell change execution conditionis fulfilled, the UE 10 includes the time difference between the fulfillment of the execution conditionand reception of the handover command from the source RAN node. The UE 10 includes the latestmeasurement results the UE 10 was evaluating for the unfulfilled execution condition. In anotherembodiment, if one or both of the PCell handover and / or PSCell change execution condition isfulfilled, the UE 10 includes the time difference between the fulfillment of the execution conditionand reception of the handover command from the source RAN node. For each fulfilled condition,the UE 10 includes the latest measurement results available. For example, for the PCell condition,the UE 10 includes the latest measurement on target PCell as well as measurements on neighbourcells; for the PSCell condition, the UE 10 includes the latest measurements on the target PSCell aswell as on neighbor cells. In a variant of this embodiment the UE 10 may include series of thelatest measurement results available. For example, for the PCell condition, the UE 10 includes alist of the latest n measurement on target PCell as well as measurements on neighbor cells; for thePSCell condition, the UE 10 includes a list of the latest m measurements on the target PSCell aswell as on neighbor cells. Such lists of measurements enable the RAN node receiving themeasurements to determine how the radio quality and signal strength of each measure cellprogressed. In one option, at least one of the maximum (or minimum) number n of latestmeasurements of target PCell and / or the maximum (or minimum) number m of latestmeasurements on the target PSCell is configured to the UE 10. In another option, at least one ofthe number n and / or the number m of described above is up to UE implementation. In one variantthe number n refers only to PCell, and not to neighbor cells, in another variant, the number n refersto the cumulative number of measurements for the PCell and the neighbor cells. Similarly, in onevariant the number m refers only to PSCell, and not to neighbor cells, in another variant, thenumber m refers to the cumulative number of measurements for the PSCell and the neighbor cells.This information is useful to understand what is the optimal time between signaling of the handovercommand and fulfillment of the conditions on target PCell and PSCell. One result of such analysismay for example be that the best elapsed time is the one where the cell measurements for targetPCell and PSCell are maximized.In another embodiment, if none of the configured execution conditions are fulfilled, the UE10 includes the measurement results based on which it was evaluating the execution conditions.In another embodiment the set of information includes the successfully or failed executedmobility type. In non-limiting examples:^ In a scenario, upon failure in execution of the CHO with candidate SCG, the UE 10 logs in areport (RLF report) that the last mobility / handover type was a “CHO with candidate SCG”.^ In another scenario, upon failure after successful execution of the CHO with candidateSCG, the UE 10 logs in a report (RLF report) that the last successfully executedmobility / handover type was a “CHO with candidate SCG”The above information reported by the UE 10 to the network node 150, in particular in thescenario of failure after successful execution of the CHO with candidate SCG, may assist thenetwork node 150 to conclude that the mobility control parameters associated to the CHO withcandidate SCG are not optimized and hence may tune these parameters instead of wrongly tuningother mobility control parameters related to the normal HO or CHO, or Dual Active Protocol Stack(DAPS) HOs.Embodiments describing the event in the configuration, such as the event executed inaction 312.In an embodiment, the event is detecting a radio link failure while monitoring / evaluating theexecution conditions (including one or two triggering events) of the CHO with candidate SCGconfiguration and the UE 10 logs an RLF report. The UE 10 may include the set of information inthe RLF report.In another embodiment, the UE 10 declares a handover failure and logs an RLF report. TheUE 10 may then include the set of information in the RLF report.In another embodiment, the event is performing both PCell handover and PSCell change,i.e., CHO with candidate SCG, and detecting a radio link failure in the PCell. The UE 10 logs anRLF report, and the UE 10 may include the set of information in the RLF report.In another embodiment, the event is performing both PCell handover and PSCell change,i.e., CHO with candidate SCG, and detecting a radio link failure in the PCell. The UE 10 may thensend a MCGFailureInformation message to the network node 150, and the UE 10 may include theset of information in the MCGFailureInformation message.In another embodiment, the event is successfully performing both PCell handover andPSCell change. The UE 10 logs a SHR in this scenario. The UE 10 includes the set of informationin the SHR.In another embodiment, the event is successfully performing both PCell handover andPSCell change. The UE 10 may log a SPR, and the UE 10 includes the set of information in theSPR. In another embodiment, the event is successfully performing both PCell handover andPSCell change, i.e., CHO with candidate SCG. The UE 10 logs both SHR and SPR, and the UE 10includes the set of information in the SHR and / or SPR.In another embodiment, the event is successfully performing both PCell handover andPSCell change, i.e., CHO with candidate SCG. The UE 10 logs an SHR but not an SPR, becausethe configured condition for logging an SPR was not fulfilled. The UE 10 may further include the setof information in the SHR.In another embodiment, the event is successfully performing both PCell handover andPSCell change, i.e., CHO with candidate SCG. The UE 10 logs an SPR but not an SHR, becausethe configured condition for logging an SHR was not fulfilled. The UE 10 may include the set ofinformation in the SPR.In another embodiment, the event is successfully performing the conditional PCell handoverbut failure in performing conditional PSCell change. The UE 10 may send a SCGFailureInformationto the network node 150, but does not generate an SHR because the configured condition forgenerating an SHR was not fulfilled. The UE 10 may include the set of information in theSCGFailureInformation message.In another embodiment, the UE 10 may perform PCell handover but fails PSCell change,generate a SHR and may send a SCGFailureInformation to the network node 150. The UE 10 mayfurther include the set of information in the SCGFailureInformation message and / or in thegenerated SHR.In another embodiment, the UE 10 declares radio link failure in the secondary leg andsends a SCGFailureInformation to the network node 150. The UE 10 may include the set ofinformation in the SCGFailureInformation message.In another embodiment, the UE 10 may perform both PCell handover and PSCell change,however, declares radio link failure in the secondary leg afterwards and sends aSCGFailureInformation to the network node 150. The UE 10 may include the set of information inthe SCGFailureInformation message.The method actions performed by the network node 150 for handling communication in thewireless communication network, according to embodiments herein will now be described withreference to a flowchart depicted in Fig.3c. The actions do not have to be taken in the order statedbelow, but may be taken in any suitable order. Actions performed in some embodiments aremarked with dashed boxes.Action 320. The network node 150 may transmit to the UE 10 the configuration related tothe CHO with candidate SCG procedure.Action 321. The network node 150 receives the information from the UE 10, wherein theinformation comprises information related to the event. The event is associated with or based on aconfiguration related to CHO with a candidate SCG procedure.Action 322. The network node 150 may analyze the information reported by the UE 10.Action 323. The network node 150 performs the operation based on the receivedinformation. As an example, the network node 150 may identify a certain network node where theoptimization is required based on the information, and may forward the information to that certainnetwork node. As another example, the network node 150 may optimize the one or moreparameters related to mobility and / or an event based on the information.Embodiments at the network node 150:As part of the information reported in the reports and logs described above, the UE 10 mayalso include identifiers of the cells involved in the events monitored. For example, the UE 10 mayinclude identifiers for the target PCell and PSCell as well as for the source PCell and PSCell maybe included in the report by the UE 10 according to current standards.Based on this, when a RAN node, being an example of the network node 150, receivesinformation from the UE 10 concerning the PCell handover and / or PSCell change, the RAN nodeanalyses the information and determines which RAN node should receive such information so tooptimize its configuration and policies to achieve a better UE performance.One important part of the failure cause analysis and of determining which RAN node shouldreceive the UE generated information is to analyze the time between reception at the UE 10 of thehandover command from the source RAN node and the time of PCell change condition and PSCellcondition. Additionally, the measurements reported by the UE 10 at the time of fulfilment of each ofsuch conditions may also be taken into account for such an analysis.A first issue that may be detected by the network node 150 is that the time betweenreception at the UE 10 of the handover command from the source RAN node and the time of PCellcondition fulfilment is different from the time between reception at the UE 10 of the handovercommand from the source RAN node and the time of PSCell Condition fulfilment. Such differencereveals that the conditions set by the source MN for PCell change and the conditions set by thetarget MN for PSCell change are different, e.g. one is more aggressive than the other. This is asuboptimal configuration because the UE 10 waits while the slowest condition is fulfilled, while thefirst is already fulfilled. A similar analysis may be conducted in case the UE 10 logs timing relatedinformation concerning how long the triggering conditions(s) for CHO was(were) fulfilled before thetriggering conditions for PSCell Change was(were) also fulfilled.The information reported by the UE 10 may be signaled from the RAN node to which theUE 10 reports the information to the RAN node responsible for configuring the slowest of theconditions to be fulfilled. The RAN node, also referred to as that certain network node, receivingthe information will attempt to set conditions in the future that may be fulfilled in a time similar tothe fulfilment time of the fastest condition. The above behavior may be followed if the UE 10performs a successful handover to both PCell and PSCell, but the UE 10 is subject to failureimmediately after successful handover for the cell whose condition executed the fastest. The lattermay indicate that, by the time the slowest of the conditions was fulfilled, the cell for which thecondition was fulfilled first became weaker and its signal strength degraded at the UE 10. A similaranalysis is possible when the UE 10 logs and reports a list of the latest n measurements for thetarget PCell and / or a list of the latest m measurements for the target PSCell.The UE measurements collected by the UE 10 at the time of each condition fulfilment mayalso be analyzed by the RAN node receiving the information. Such measurements reveal how thesignal strength of each cell was and therefore allow to understand what is the radio quality of thetarget PCell and PSCell at the time both conditions are fulfilled.The information reported by the UE 10 may be signaled from the RAN node to which theUE 10 reports the information to the RAN node responsible for configuring the fastest of theconditions to be fulfilled. The RAN node receiving the information from the RAN node, such as theradio network node 12, may attempt to set conditions in the future that may be fulfilled in a timesimilar to the fulfilment time of the slowest condition. The above behavior may be followed, ifcondition fulfilled first is then not fulfilled and then fulfilled again and so on, while the slowestcondition is finally fulfilled. Namely, the fastest condition bounces between fulfilled and not fulfilledstatuses, while the second condition is fulfilled only after a longer time. In this case, the networknode responsible for configuring the faster condition should correct its policy and set “slower”conditions, hence giving time to the target cell signal levels to stabilize and avoid ping pongs.The target RAN node may perform the analysis of the UE report(s) and may determine thatthere was at least one cell for which PSCell change was attempted but failed, or there has been acell for which PSCell Change succeed but the cell was not included in the initial list of candidatecells for PSCell change sent to the UE 10. Then, the RAN node receiving the information maymodify the list of candidate cells for PSCell change for subsequent candidate SCG configurationsto be used for other UE (or the same UE) when configuring such UE for CHO with candidate SCG.In some embodiments, the source RAN node, such as a source MN, and target RAN node,such as a target MN, may be configured with a timer. Such timer represents a maximum amount oftime that should elapse from the signaling of the HO command to the UE 10 to the fulfilment of thePCell and / or PSCell condition set by each RAN node. If the execution condition of a RAN node didnot exceed such time limit, and if the condition fulfilment derived into a successful handover (forPCell and / or PSCell), the RAN node does not need to analyze the UE information and adjust itsconfiguration and policies. If the execution condition of a RAN node did exceed such time limit, andif the condition fulfilment derived into a successful handover (for PCell or PSCell), the RAN nodeneeds to receive the UE generated information and use it to modify its policies so to achievefulfilment condition times within the configured maximum time limit.The target RAN node may analyze the information received from the UE 10 and maydetermine that the RAN node responsible for optimization that may prevent the issues captured inthe UE information is the source RAN node. In this case the RAN node serving the target PCellmay transmit a message to the source RAN node serving the source PCell. In one option, thetarget RAN node sends to the source RAN node – either reusing an existing message or a newmessage – one or more UE reports and for a given UE report, an indication indicating that the UEreport concerns the UE 10 that was configured with CHO and candidate SCG. Such a messagemay include the information reported by the UE 10 as well as indicating the SCG Failureexperienced by the UE 10 upon successfully executing the CHO with candidate SCG procedure.For example, upon successfully executing the CHO with candidate SCG procedure to a targetPCell and to a target PSCell, the UE 10 may experience an SCG failure and hence transmit aSCGFailureInformation to the target PCell. The SCGFailureInformation may comprise some of theabove time-related information, as well as the identity of the source PCell, and on the basis of thatthe target RAN node may determine whether to transmit said message to the source RAN node.For example, the target RAN node may determine if the time elapsed since the CHO withcandidate SCGs and the SCG Failure is larger than a certain value. If it is shorter, then the targetRAN node may conclude that the source RAN node should receive information about said SCGFailure, otherwise it will not. The message transmitted by the target RAN node to the source RANnode may comprise the SCGFailureInformation, or part of it. The SCGFailureInformation messagemay comprise the identity of the source PCell which configured the CHO with candidate SCG, andthe cell radio network temporary identifier (C-RNTI) of the UE 10 when the UE 10 was connectedto the source PCell.Example ImplementationIn the following, some non-limiting example implementation in 3GPP TS 38.331 is provided.Changes are marked as underlined italic text.5.7.10.6 Actions for the successful handover report determinationThe UE shall for the PCell:1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the ratio betweenthe value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the lastapplied RRCReconfiguration message including the reconfigurationWithSync, is greater thanthresholdPercentageT304 if included in the successHO-Config received before executing the last reconfigurationwith sync; or********************text omitted******************3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the targetPCell indicated in the last applied RRCReconfiguration message including reconfigurationWithSync:********************text omitted******************4> if the last applied RRCReconfiguration message including reconfigurationWithSync was included inthe stored condRRCReconfig:5> set the timeSinceCHO-Reconfig to the time elapsed between the initiation of the execution ofconditional reconfiguration for the target PCell and the reception of the lastconditionalReconfiguration including the condRRCReconfig of the target PCell in the sourcePCell; 4> if the last applied RRCReconfiguration message including reconfigurationWithSync includedcondExecutionCondPSCell: 5> set the TimeSinceCHOevent to the time elapsed between the initiation of the execution ofconditional reconfiguration for the target PCell and the reception of the lastconditionalReconfiguration including the condExecutionCondPSCell of the target PCell in thesource PCell;5> set the TimeSinceCPCevent to the time elapsed between the initiation of the execution ofconditional reconfiguration for the target PSCell and the reception of the lastconditionalReconfiguration including the condExecutionCondPSCell of the target PSCell in thesource PCell;********************text omitted******************1> release successHO-Config configured by the source PCell and thresholdPercentageT304 if configured by thetarget PCell.The UE may discard the successful handover information, i.e., release the UE variableVarSuccessHO-Report, 48 hours after the last successful handover information is added to theVarSuccessHO-Report. UEInformationResponse message---- UEInformationResponse-r16 ::= {rrc-TransactionIdentifier RRC-TransactionIdentifier,criticalExtensions CHOICE {ueInformationResponse-r16 UEInformationResponse-r16-IEs,criticalExtensionsFuture SEQUENCE {}} }UEInformationResponse-r16-IEs ::= {measResultIdleEUTRA-r16 MeasResultIdleEUTRA-r16OPTIONAL, measResultIdleNR-r16 MeasResultIdleNR-r16OPTIONAL, logMeasReport-r16 LogMeasReport-r16OPTIONAL, connEstFailReport-r16 ConnEstFailReport-r16OPTIONAL, ra-ReportList-r16 RA-ReportList-r16OPTIONAL, rlf-Report-r16 RLF-Report-r16OPTIONAL,mobilityHistoryReport-r16 MobilityHistoryReport-r16OPTIONAL, lateNonCriticalExtensionOPTIONAL, nonCriticalExtension UEInformationResponse-v1700-IEs {successHO-Report-r17 SuccessHO-Report-r17OPTIONAL, connEstFailReportList-r17 ConnEstFailReportList-r17OPTIONAL, coarseLocationInfo-r17 OPTIONAL, nonCriticalExtension UEInformationResponse-v1800-IEsOPTIONAL }UEInformationResponse-v1800-IEs ::= {flightPathInfoReport-r18 FlightPathInfoReport-r18OPTIONAL, successPSCell-Report-r18 SuccessPSCell-Report-r18OPTIONAL, nonCriticalExtension SEQUENCE {} measResultLastServCell-r16 MeasResultRLFNR-r16,measResultNeighCells-r16 SEQUENCE {measResultListNR-r16 MeasResultList2NR-r16measResultListEUTRA-r16 MeasResultList2EUTRA-r16 } c-RNTI-r16 RNTI-Value,previousPCellId-r16 CHOICE {nrPreviousCell-r16 CGI-Info-Logging-r16,eutraPreviousCell-r16 CGI-InfoEUTRALogging r16 CHOICE {nrFailedPCellId-r16 CHOICE {cellGlobalId-r16 CGI-Info-Logging-r16,pci-arfcn-r16 PCI-ARFCN-NR-r16}, eutraFailedPCellId-r16 CHOICE {cellGlobalId-r16 CGI-InfoEUTRALogging,pci-arfcn-r16 PCI-ARFCN-EUTRA-r16} }, reconnectCellId-r16 CHOICE {nrReconnectCellId-r16 CGI-Info-Logging-r16,eutraReconnectCellId-r16 CGI-InfoEUTRALogging timeUntilReconnection-r16 TimeUntilReconnection-r16OPTIONAL,reestablishmentCellId-r16 CGI-Info-Logging-r16timeConnFailure-r16 INTEGER (0..1023)OPTIONAL, timeSinceFailure-r16 TimeSinceFailure-r16,connectionFailureType-r16 ENUMERATED {rlf, hof},rlf-Cause-r16 ENUMERATED {t310-Expiry,randomAccessProblem, rlc-MaxNumRetx,beamFailureRecoveryFailure, lbtFailure-r16,bh-rlfRecoveryFailure,t312-expiry-r17, spare1},locationInfo-r16 LocationInfo-r16OPTIONAL, noSuitableCellFound-r16 ENUMERATED {true}ra-InformationCommon-r16 RA-InformationCommon-r16 timeSinceCHO-Reconfig-r17 TimeSinceCHO-Reconfig-r17choCellId-r17 CHOICE {cellGlobalId-r17 CGI-Info-Logging-r16,pci-arfcn-r17 PCI-ARFCN-NR-r16 choCandidateCellList-r17 ChoCandidateCellList-r17]], [[ pSCellId-r18 CHOICE {cellGlobalId-r18 CGI-Info-Logging-r16,pci-arfcn-r18 PCI-ARFCN-NR-r16 mcgRecoveryFailureCause-r18 ENUMERATED {t316-Expiry,scgDeactivated, spare2, spare1} 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 } measResultLastServCell-RSSI-r18 RSSI-Range-r16measResultNeighFreqList-RSSI-r18 MeasResultNeighFreqList-RSSI-r18 ]] } }SuccessHO-Report-r17 ::= SEQUENCE {sourceCellInfo-r17 SEQUENCE {sourcePCellId-r17 CGI-Info-Logging-r16,sourceCellMeas-r17 MeasResultSuccessHONR-r17rlf-InSourceDAPS-r17 ENUMERATED {true} targetCellInfo-r17 SEQUENCE {targetPCellId-r17 CGI-Info-Logging-r16,targetCellMeas-r17 MeasResultSuccessHONR-r17 measResultNeighCells-r17 SEQUENCE {measResultListNR-r17 MeasResultList2NR-r16measResultListEUTRA-r17 MeasResultList2EUTRA-r16 locationInfo-r17 LocationInfo-r16OPTIONAL, timeSinceCHO-Reconfig-r17 TimeSinceCHO-Reconfig-r17OPTIONAL, shr-Cause-r17 SHR-Cause-r17OPTIONAL, ra-InformationCommon-r17 RA-InformationCommon-r16OPTIONAL, upInterruptionTimeAtHO-r17 UPInterruptionTimeAtHO-r17OPTIONAL, c-RNTI-r17 RNTI-ValueOPTIONAL, ..., [[ eutraTargetCellInfo-r18 SEQUENCE {targetPCellId-r18 CGI-InfoEUTRALogging,targetCellMeas-r18 MeasQuantityResultsEUTRA measResultServCell-RSSI-r18 RSSI-Range-r16OPTIONAL, measResultNeighFreqList-RSSI-r18 MeasResultNeighFreqList-RSSI-r18 OPTIONAL,eutra-C-RNTI-r18 EUTRA-C-RNTIOPTIONAL, timeSinceSHR-r18 TimeSinceSHR-r18 pCellId-r18 CGI-Info-Logging-r16,sourcePSCellInfo-r18 sourcePSCellId-r18 CGI-Info-Logging-r16,sourcePSCellMeas-r18 MeasResultSuccessHONR-r17 {targetPSCellId-r18 {cellGlobalId-r18 CGI-Info-Logging-r16,pci-arfcn-r18 PCI-ARFCN-NR-r16}, targetPSCellMeas-r18 MeasResultSuccessHONR-r17 {measResultListNR-r18 MeasResultList2NR-r16measResultListEUTRA-r18 MeasResultList2EUTRA-r16 spr-Cause-r18 SPR-Cause-r18OPTIONAL, timeSinceCPAC-Reconfig-r18 TimeSinceCPAC-Reconfig-r18OPTIONAL, locationInfo-r18 LocationInfo-r16OPTIONAL, ra-InformationCommon-r18 RA-InformationCommon-r16OPTIONAL, OPTIONAL ]] } TimeSinceFailure-r16 ::= INTEGER (0..172800)MobilityHistoryReport-r16 ::= VisitedCellInfoList-r16TimeUntilReconnection-r16 ::= INTEGER (0..172800)TimeSinceCHO-Reconfig-r17 ::= INTEGER (0..1023)TimeSinceCPAC-Reconfig-r18 ::= INTEGER (0.. 1023)TimeConnSourceDAPS-Failure-r17 ::= INTEGER (0..1023)UPInterruptionTimeAtHO-r17 ::= INTEGER (0..1023)ElapsedTimeT316-r18 ::= INTEGER (0..2000)ElapsedTimeSCGFailure-r18 ::= INTEGER (0..1023)TimeSinceSHR-r18 ::= INTEGER (0..172800)---- Fig.4 is a block diagram depicting the UE 10 for handling communication in the wirelesscommunication network 1 according to embodiments herein.The UE 10 may comprise processing circuitry 401, e.g. one or more processors,configured to perform the methods herein.The UE 10 and / or the processing circuitry 401 may be configured to obtain theconfiguration related to the CHO with candidate SCG procedure, such as receive the configurationfrom one or more network nodes such as network node 150.The UE 10 and / or the processing circuitry 401 may be configured to execute an eventtaking the configuration into account. Examples of the event may be that the UE 10 may beconfigured to perform one or more of the following: declare radio link failure before executing theCHO with candidate cell configuration; declare handover failure during execution of the CHO withcandidate cell configuration; declare radio link failure upon successful execution of CHO withcandidate cell configuration; declare radio link failure in the SCG leg before execution of CHO withcandidate cell configuration; declare handover failure for the secondary leg during execution ofCHO with candidate cell configuration; declare radio link failure in the secondary leg uponexecution of CHO with candidate cell configuration; and / or perform PCell handover and PSCellchange based on the CHO with candidate cell configuration.The UE 10 and / or the processing circuitry 401 is configured to, when configured with theconfiguration related to CHO with candidate SCG procedure, log and / or send information uponexecution of an event, wherein the event is associated with or based on the configuration. The UE10 and / or the processing circuitry 401 may be configured to log information upon execution of theevent, wherein the event is associated with or based on the configuration. Additional informationmay thus be included in SON report or reports if the UE is configured with CHO with candidateSCG configuration and performs an event based on it. The information may comprise timerrelated information, and / or measurement results, which the UE 10 used to evaluate the one ormore execution conditions (or some other form of indication based on different scenarios). Theinformation may indicate RLF or SCG failure. The information may indicate a time intervalbetween the CHO execution fulfillment and the detection of at least one of an SCG Failure or anRLF. The information may be sent in a RLF report and / or a SCG failure report. The informationmay comprise one or more PCell identities and / or one or more PSCell identities corresponding toone or more cells for which an execution condition for PCell Handover and / or an executioncondition for PSCell Change were satisfied. The information may comprise the time elapsedbetween the first time of the first fulfilled triggering event for the first fulfilled execution condition tothe second time of the fulfilled triggering event for the second execution condition. The informationmay comprise an indication indicating whether the first fulfilled execution condition is associatedwith the CHO configuration or with the conditional SCG configuration, and an indication indicatingwhether the second execution condition is associated with the CHO configuration or with theconditional SCG configuration.The UE 10 may comprise a memory 405. The memory 405 comprises one or more units tobe used to store data on, such as data packets, indications, measurements, configuration,messages, support information, events and applications to perform the methods disclosed hereinwhen being executed, and similar. Furthermore, the UE 10 may comprise a communicationinterface 406 such as comprising a transmitter, a receiver, a transceiver and / or one or moreantennas. The methods according to the embodiments described herein for UE 10 are respectivelyimplemented by means of e.g. a computer program product 407 or a computer program,comprising instructions, i.e., software code portions, which, when executed on at least oneprocessor, cause the at least one processor to carry out the actions described herein, asperformed by the UE 10. The computer program product 407 may be stored on a computer-readable storage medium 408, e.g., a disc, a universal serial bus (USB) stick or similar. Thecomputer-readable storage medium 408, having stored thereon the computer program product,may comprise the instructions which, when executed on at least one processor, cause the at leastone processor to carry out the actions described herein, as performed by the UE 10. In someembodiments, the computer-readable storage medium may be a transitory or a non-transitorycomputer-readable storage medium. Thus, embodiments herein may disclose the UE for handlingcommunication in a communication network, wherein the UE comprises processing circuitry and amemory, said memory comprising instructions executable by said processing circuitry wherebysaid UE is operative to perform any of the methods herein.Fig.5 is a block diagram depicting the network node 150, such as the first radio networknode 12 or the second radio network node 13, for handling communication in the wirelesscommunication network 1 according to embodiments herein.The network node 150 may comprise processing circuitry 501, e.g. one or moreprocessors, configured to perform the methods herein.The network node 150 and / or the processing circuitry 501 may be configured to transmit tothe UE 10 the configuration related to the CHO with candidate cell, such as SCG, procedure.The network node 150 and / or the processing circuitry 501 is configured to receive thereport and / or information from the UE 10, wherein the information comprises information related tothe event, wherein the event is associated with or based on the configuration related to CHO withcandidate SCG procedure. The information may indicate RLF or SCG failure.The network node 150 and / or the processing circuitry 501 is configured to analyze thereport and / or information reported by the UE 10.The network node 150 and / or the processing circuitry 501 is configured to perform theoperation based on the received information, such as the received report. The UE 10 may includethe information in a given set of reports or it may declare RLF or SCG failure and include theinformation in another set of reports. Upon reception of the report from the UE 10, the networknode 150 and / or the processing circuitry 501 receiving the report may be configured to identify thecertain network node where the optimization is required and to forward the report to that certainnetwork node. The network node 150 and / or the processing circuitry 501 may be configured tooptimize one or more parameters related to mobility and / or an event based on the report and / orinformation The network node 150 may comprise a memory 505. The memory 505 comprises one ormore units to be used to store data on, such as data packets, indications, configuration, messages,support information, events and applications to perform the methods disclosed herein when beingexecuted, and similar. Furthermore, the network node 150 may comprise a communicationinterface 506 such as comprising a transmitter, a receiver, a transceiver and / or one or moreantennas. The methods according to the embodiments described herein for the network node 150 arerespectively implemented by means of e.g. a computer program product 507 or a computerprogram, comprising instructions, i.e., software code portions, which, when executed on at leastone processor, cause the at least one processor to carry out the actions described herein, asperformed by the network node 150. The computer program product 507 may be stored on acomputer-readable storage medium 508, e.g., a disc, a universal serial bus (USB) stick orsimilar. The computer-readable storage medium 508, having stored thereon the computer programproduct, may comprise the instructions which, when executed on at least one processor, cause theat least one processor to carry out the actions described herein, as performed by the network node150. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose thenetwork node 150 for handling communication in a communication network, wherein the networknode comprises processing circuitry and a memory, said memory comprising instructionsexecutable by said processing circuitry whereby said network node is operative to perform any ofthe methods herein.In some embodiments a more general term “network node” is used and it can correspond toany type of radio-network node or any network node, which communicates with a UE and / or withanother network node.In some embodiments the non-limiting term wireless device or user equipment (UE) is usedand it refers to any type of wireless device communicating with a network node and / or with anotherwireless device in a cellular or mobile communication system. Examples of UE are target device,device to device (D2D) UE, proximity capable UE (aka ProSe UE), IoT capable device, machinetype UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals,smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB donglesetc. Embodiments are applicable to any RAT or multi-RAT systems, where the wireless devicereceives and / or transmit signals (e.g. data) e.g. NR, Wi-Fi, LTE, LTE-Advanced, Wideband CodeDivision Multiple Access (WCDMA), Global System for Mobile communications / enhanced Datarate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax),or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.Fig.6 shows an example of a communication system 15100 in accordance with someembodiments. In the example, the communication system 15100 includes a telecommunications network15102 that includes an access network 15104, such as a radio access network (RAN), and a corenetwork 15106, which includes one or more core network nodes 15108. The access network15104 includes one or more access network nodes or base stations of various types, accessnetwork nodes 15110A and 15110B are depicted (which may be collectively referred to as networknodes 15110 or radio network node 12 or network node 150), or any other similar 3rd GenerationPartnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodimentsof the access network 15104 may include more than one access network technology. The networknodes 15110 of access network 15104 facilitate direct or indirect connection of wireless devices,also referred to as UEs, such as by connecting UEs 15112A, 15112B, 15112C, and 15112D (oneor more of which may be generally referred to as UEs 15112 or UE 10) to the core network 15106over one or more wireless connections.Moreover, a network node is not necessarily limited to an implementation in which a radioportion and a baseband portion are supplied and integrated by a single vendor. Thus, it will beunderstood that network nodes include disaggregated implementations or portions thereof. Forexample, in some embodiments, the telecommunications network 15102 includes one or moreOpen-RAN (ORAN) network nodes. An ORAN network node is a network node in thetelecommunications network 15102 that supports an ORAN specification (e.g., a specificationpublished by the O-RAN Alliance, or any similar organization) and may operate alone or togetherwith other network nodes to implement one or more functionalities of any network node in thetelecommunications network 15102, including one or more access network nodes 15110 and / orcore network nodes 15108 such as first / second network node.Examples of an ORAN network node include an open radio unit (O-RU), an opendistributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP)or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time)hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or anon-real time control application (e.g., rApp), or any combination thereof (the adjective “open”designating support of an ORAN specification). An ORAN network node may support aspecification by, for example, supporting an interface defined by the ORAN specification, such asan A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an openfronthaul management plane interface. Moreover, an ORAN network node may be a logical node ina physical node. Furthermore, an ORAN network node may be implemented in a virtualizationenvironment (described further below) in which one or more network functions are virtualized. Forexample, the virtualization environment may include an O-Cloud computing platform orchestratedby a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.The network nodes 15110 facilitate direct or indirect connection of one or more UEs 15112to the core network 15106 over one or more wireless connections. Example wirelesscommunications over a wireless connection include transmitting and / or receiving wireless signalsusing electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitablefor conveying information without the use of wires, cables, or other material conductors. Moreover,in different embodiments, the communication system 15100 may include any number of wired orwireless networks, network nodes, UEs, and / or any other components or systems that mayfacilitate or participate in the communication of data and / or signals whether via wired or wirelessconnections. The communication system 15100 may include and / or interface with any type ofcommunication, telecommunication, data, cellular, radio network, and / or other similar type ofsystem.The UEs 15112 may be any of a wide variety of communication devices, including wirelessdevices arranged, configured, and / or operable to communicate wirelessly with the network nodes15110 and other communication devices. Similarly, the network nodes 15108, 15110 are arranged,capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devicesof telecommunications network 15102) with the UEs 15112 and / or with other network nodes orequipment in the telecommunications network 15102 to enable and / or provide network access,such as wireless network access, and / or to perform other functions, such as administration in thetelecommunications network 15102. More specifically, UEs 15112 may send messages, data,and / or other signals to network nodes 15108, 15110 or other elements of the telecommunicationsnetwork 15102 by transmitting such signals to the relevant device directly without the signalspassing through any intervening devices or by transmitting such signals to the relevant deviceindirectly through an intervening device (or multiple intervening devices) that then transmit thesignal to the relevant device. Similarly, network nodes 15108, 15110 may send messages, data,and other signals to UEs 151122, other network nodes 15108, 15110, and other devices intelecommunications network 15102 directly or indirectly. As one specific example, a core networknode 108 may transmit a particular message to a UE 15112 by transmitting the message to anaccess network node 15110 that will then transmit the message to the intended UE 15112.Similarly, a core network node 108 may receive a particular message from a UE 15112 byreceiving the message from an access network node 15110 that itself received the message fromthe UE 15112.In the depicted example, the core network 15106 connects elements of the access network15104 (e.g., one or more of the network nodes 15110) to one or more host computing systems,such as host 15116. These connections may be direct or indirect via one or more intermediarynetworks or devices. In other examples, network nodes may be directly coupled to hosts. The corenetwork 15106 includes one or more core network nodes (e.g., core network node 15108) ofvarious types, one or more of which may be generally referred to as network nodes 15108.Network nodes 15108 are structured with hardware and software components. Features of thesecomponents may be substantially similar to those described with respect to the UEs, accessnetwork nodes, and / or hosts, such that the descriptions thereof are generally applicable to thecorresponding components of the core network node 15108. Example core network nodes providefunctions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME),Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), SessionManagement 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 15116 may be under the ownership or control of a service provider other than anoperator or provider of the access network 15104 and / or the telecommunications network 15102.The host 15116 may be operated by the service provider or on behalf of the service provider. Thehost 15116 may host a variety of applications to provide one or more service. Examples of suchapplications include live and pre-recorded audio / video content, data collection services such asretrieving and compiling data on various ambient conditions detected by a plurality of UEs,analytics functionality, social media, functions for controlling or otherwise interacting with remotedevices, functions for an alarm and surveillance center, or any other such function performed by aserver. As a whole, the communication system 15100 of Figure 6 enables connectivity between theUEs, network nodes, and hosts. In that sense, the communication system 15100 may beconfigured to operate according to predefined rules or procedures, such as specific standards thatinclude, but are not limited to: Global System for Mobile Communications (GSM); Universal MobileTelecommunications 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 areanetwork (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE)802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such asthe Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near FieldCommunication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standardssuch as LoRa and Sigfox. Moreover, the communication system 15100 may be configured tosupport multiple different standards, protocols, or other rule sets, with individual componentssupporting all of the relevant rule sets or with different components or sub-systems within thecommunication system 15100 supporting different standards, protocols, or rule sets.As one example, in certain embodiments, access network 15104 may contain some accessnetwork nodes 15110 that support 3GPP radio access technologies (RAT), such as LTE or NR,while other access network nodes 15110 support (or the same access network nodes 15110additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example,telecommunications network 15102 may support multiple generations of related communicationstandards, e.g., 4G and 5G 3GPP communication standards, and, as a result, may include anaccess network 104 and / or a core network 106 that supports multiple different standardgenerations or may include multiple access networks 104 and / or multiple core networks 106 withindividual networks 104, 106 supporting different standard generations.Telecommunications network 15102 may support network slicing to provide different logicalnetworks to different devices that are connected to the telecommunications network 15102. Forexample, the telecommunications network 15102 may provide Ultra Reliable Low LatencyCommunication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband(eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / MassiveIoT services to yet further UEs.In some examples, one or more of the UEs 15112 are configured to transmit and / or receiveinformation without direct human interaction. For instance, a UE may be designed to transmitinformation to the access network 15104 on a predetermined schedule, when triggered by aninternal or external event, or in response to requests from the access network 15104. Additionally,a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example,a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. beingconfigured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTSTerrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC).In the example, the hub 15114 communicates with the access network 15104 to facilitateindirect communication between one or more UEs (e.g., UE 15112C and / or 15112D) and networknodes (e.g., network node 15110B). In some examples, the hub 15114 may be a controller, router,content source and analytics, or any of the other communication devices described hereinregarding UEs. For example, the hub 15114 may be a broadband router enabling access to thecore network 15106 for the UEs. As another example, the hub 15114 may be a controller thatsends commands or instructions to one or more actuators in the UEs. Commands or instructionsmay be received from the UEs, network nodes 15110, or by executable code, script, process, orother instructions in the hub 15114.As another example, the hub 15114 may be a data collector that acts as temporary storagefor UE data and, in some embodiments, may perform analysis or other processing of the data. Asanother example, the hub 15114 may be a content source. For example, for a UE that is a VRheadset, display, loudspeaker or other media delivery device, the hub 15114 may retrieve VRassets, video, audio, or other media or data related to sensory information via a network node,which the hub 15114 then provides to the UE either directly, after performing local processing,and / or after adding additional local content. In still another example, the hub 15114 acts as a proxyserver or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoTdevices. The hub 15114 may have a constant / persistent or intermittent connection to the networknode 15110B. The hub 15114 may also allow for a different communication scheme and / orschedule between the hub 15114 and UEs (e.g., UE 15112C and / or 15112D), and between thehub 15114 and the core network 15106. In other examples, the hub 15114 is connected to the corenetwork 15106 and / or one or more UEs via a wired connection. Moreover, the hub 15114 may beconfigured to connect to an M2M service provider over the access network 15104 and / or toanother UE over a direct connection. In some scenarios, UEs may establish a wireless connectionwith the network nodes 15110 while still connected via the hub 15114 via a wired or wirelessconnection. In some embodiments, the hub 15114 may be a dedicated hub – that is, a hub whoseprimary function is to route communications to / from the UEs from / to the network node 15110B. Inother embodiments, the hub 15114 may be a non-dedicated hub – that is, a device which iscapable of operating to route communications between the UEs and network node 15110B, butwhich is additionally capable of operating as a communication start and / or end point for certaindata channels.Figure 7 shows a wireless device 15300 such as the UE 10, which may be configured tooperate in communication system 15100 of Figure 6. The wireless device 15300 may bealternatively referred to as a UE 15300, like a UE 15112 within the context of communicationsystem 15100, or as a station (STA) 15300 or as a non-access-point station (non-AP STA) 15300,in accordance with respective embodiments. As used herein, a wireless device refers to a devicecapable, configured, arranged and / or operable to communicate wirelessly with network nodesand / or other wireless devices. Examples of a wireless device include, but are not limited to, asmart 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, mobilestation, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME),smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicleembedded / integrated wireless device, and wireless terminal. Other examples include any type ofUE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internetof things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC(eMTC) UE.A wireless device 15300 may support device-to-device (D2D) communication, for exampleby implementing a 3GPP standard for sidelink communication, Dedicated Short-RangeCommunication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 15300 may not necessarily have a user in thesense of a human user who owns and / or operates the relevant device. Instead, wireless device15300 may represent a device that is intended for sale to, or operation by, a human user but whichmay not, or which may not initially, be associated with a specific human user (e.g., a smartsprinkler controller). Alternatively, wireless device 15300 may represent a device that is notintended for sale to, or operation by, an end user but which may be associated with or operated forthe benefit of a user (e.g., a smart power meter).In particular embodiments, wireless device 15300 includes processing circuitry 15302 thatis operatively coupled via a bus 15304 to an input / output interface 15306, a power source 15308, amemory 15310, a communication interface 15312, and / or any other component, or anycombination thereof. Certain embodiments of wireless device 15300 may include all or a subset ofthe components shown in Figure 7. The level of integration between the components may varyfrom one embodiment of wireless device 15300 to another. In general, in a particular embodimentof wireless device 15300, processing circuitry 15302, input / output interface 15306, power source15308, memory 15310, and communication interface 15312 may, in whole or in part, represent orinclude physical components common to or shared by one or more of the other elements ofwireless device 15300. Further, certain embodiments of wireless devices 15300 may containmultiple instances of a component, such as multiple processors, memories, transceivers,transmitters, receivers, etc.The processing circuitry 15302 is configured to process instructions and data and may beconfigured to implement any sequential state machine operative to execute instructions stored asmachine-readable computer programs in the memory 15310. The processing circuitry 15302 maybe 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), togetherwith appropriate software; or any combination of the above. For example, the processing circuitry15302 may include multiple central processing units (CPUs).In the example, the input / output interface 15306 may be configured to provide an interfaceor 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 wireless device 15300. Examples ofan input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digitalcamera, 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-sensitivedisplay may include a capacitive or resistive touch sensor to sense input from a user. A sensormay be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, amagnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combinationthereof. 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 15308 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 to supply power to circuitry or to charge anassociated battery. The power source 15308 may further include power circuitry for deliveringpower from the power source 15308 itself, and / or an external power source, to the various parts ofwireless device 15300 via input circuitry or an interface such as an electrical power cable. Powersource 15308 may perform any formatting, converting, or other modification to make accessiblepower suitable for the respective components of the wireless device 15300 to which power issupplied. The memory 15310 may be or be configured to include memory such as random accessmemory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasableprogrammable read-only memory (EPROM), electrically erasable programmable read-only memory(EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and soforth. In one example, the memory 15310 includes one or more programs 15314, such as anoperating system, web browser application, a widget, gadget engine, or other application, andcorresponding data 15316. The memory 15310 may store, for use by wireless device 15300, anyof a variety of various operating systems or combinations of operating systems.The memory 15310 may be configured to include a number of physical drive units, such asredundant array of independent disks (RAID), flash memory, USB flash drive, external hard diskdrive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical discdrive, 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 dynamic randomaccess memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamperresistant module in the form of a universal integrated circuit card (UICC) including one or moresubscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or anycombination 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 15310 may allowwireless device 15300 to access instructions, 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 asone utilizing a communication system may be tangibly embodied as or in the memory 15310, whichmay be or comprise a device-readable storage medium.The processing circuitry 15302 may be configured to communicate with an access networkor other network via or using the communication interface 15312. The communication interface15312 may comprise one or more communication subsystems and may include or becommunicatively coupled to an antenna 15322. The communication interface 15312 may includeone or more transceivers used to communicate, such as by communicating with one or moreremote transceivers of another device capable of wireless communication (e.g., another wirelessdevice or a network node in an access network). Each transceiver may include a transmitter 15318and / or a receiver 15320 appropriate to provide network communications (e.g., optical, electrical,frequency allocations, and so forth). Moreover, the transmitter 15318 and receiver 15320 may becoupled to one or more antennas (e.g., antenna 15322) and may share circuit components,software or firmware, or alternatively be implemented separately.In the illustrated embodiment, communication functions of the communication interface15312 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE802.11 family standard), LPWAN communication, data communication, voice communication,multimedia communication, short-range communications such as Bluetooth, near-fieldcommunication, location-based communication such as the use of the global positioning system(GPS) to determine a location, another like communication function, or any combination thereof.Communications may be implemented according to one or more communication protocols and / orstandards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CodeDivision 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.In particular embodiments, wireless device 15300 may provide an output of data capturedvia a sensor, through its communication interface 15312, via a wireless connection to a networknode, and / or in any appropriate manner. Data captured by sensors of a wireless device 15300 canbe communicated through a wireless connection to a network node via another wireless device15300. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if itreports the sensed temperature), random (e.g., to even out the load from reporting from severalsensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), inresponse to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feedof a patient).As another example, wireless device 15300 comprises an actuator, a motor, or a switch,related to a communication interface configured to receive wireless input from a network node via awireless connection. In response to the received wireless input the states of the actuator, themotor, or the switch may change. For example, wireless device 15300 may comprise a motor thatadjusts the control surfaces or rotors of a drone in flight according to the received input or to arobotic arm performing a medical procedure according to the received input.Wireless device 15300, when in the form of an Internet of Things (IoT) device, may be adevice for use in one or more application domains, these domains comprising, but not limited to,wearable technology, extended industrial application and healthcare. Non-limiting examples ofsuch an IoT device are a device which is or which is embedded in: a connected refrigerator orfreezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voicecontrolled smart speaker, a home security camera, a motion detector, a thermostat, a smokedetector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connecteddoorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillancesystem, a weather monitoring device, a vehicle parking monitoring device, an electric vehiclecharging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensoryenhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plantor 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. In particular embodiments, wirelessdevice 15300 represents an IoT device that comprises circuitry and / or software in dependence ofthe intended application of the IoT device in addition to other components as described in relationto the example embodiment of wireless device 15300 shown in Figure 7.As yet another specific example, in an IoT scenario, wireless device 15300 may represent amachine or other device that performs monitoring and / or measurements, and transmits the resultsof such monitoring and / or measurements to another wireless device and / or a network node.Wireless device 15300 may in this case be an M2M device, which may in a 3GPP context bereferred to as an MTC device. As one particular example, wireless device 15300 may implementthe 3GPP NB-IoT standard. In other scenarios, wireless device 15300 may represent a vehicle,such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable ofmonitoring and / or reporting on its operational status or other functions associated with itsoperation. In practice, any number of wireless devices 15300 may be used together with respect to asingle use case. For example, a first wireless device 15300 might be or be integrated in a droneand provide the drone’s speed information (obtained through a speed sensor) to a second wirelessdevice 15300 that is a remote controller operating the drone. When a user makes changes fromthe remote controller, the first wireless device 15300 may adjust the throttle on the drone (e.g. bycontrolling an actuator) to increase or decrease the drone’s speed. The first and / or the secondwireless device 15300 can also include more than one of the functionalities described above. Forexample, wireless device 15300 might comprise the sensor and the actuator, and handlecommunication of data for both the speed sensor and the actuators.Figure 8 shows a network node 15400 in accordance with some embodiments. As usedherein, network node refers to equipment capable, configured, arranged and / or operable tocommunicate directly or indirectly with a UE and / or with other network nodes or equipment, in atelecommunications network. In accordance with respective embodiments, network node 15400may be configured to operate in communication system 15100 of Figure 6, like network nodes15108 or 15110. 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 NodeBs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU,O-DU, O-CU).Network nodes 15400 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 ofcoverage, may be referred to as femto base stations, pico base stations, micro base stations, ormacro base stations. Network node 15400 may be a relay node or a relay donor node controlling arelay. Network nodes 15400 may also include one or more (or all) parts of a distributed radio basestation such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / orremote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remoteradio units may or may not be integrated with an antenna as an antenna integrated radio. Parts ofa distributed radio base station may also be referred to as nodes in a distributed antenna system(DAS).Other examples of network nodes 15400 include multiple transmission point (multi-TRP) 5Gaccess nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers suchas 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 LocationCenters (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).In particular embodiments, network node 15400 includes a processing circuitry 15402, amemory 15404, a communication interface 15406, and a power source 15408. In general, in aparticular embodiment of network node 15400, processing circuitry 15402, memory 15404,communication interface 15406, and power source 15408 may, in whole or in part, represent orinclude physical components common to or shared by one or more of the other elements ofnetwork node 15400.The network node 15400 may be composed of multiple distinct network entities (e.g., aNodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have orutilize their own respective physical components. In certain scenarios in which the network node15400 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entitiesmay be shared among several network nodes. For example, a single RNC may control multipleNodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances beconsidered a single separate network node. In some embodiments, the network node 15400 maybe configured to support multiple radio access technologies (RATs). In such embodiments, somecomponents may be duplicated (e.g., separate memories 15404 or portions of memory 15404 fordifferent RATs) and some components may be reused (e.g., a same antenna 15410 may beshared by different RATs). The network node 15400 may also include multiple sets of the variousillustrated components for different wireless technologies integrated into network node 15400, forexample GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard),Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wirelesstechnologies. These wireless technologies may be integrated into the same or different chip or setof chips and other components within network node 15400.The processing circuitry 15402 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit, digital signal processor,application-specific integrated circuit, field programmable gate array, or any other suitablecomputing device, resource, or combination of hardware, software and / or encoded logic operableto provide, either alone or in conjunction with other components, such as the memory 15404, toprovide network node 15400 functionality.In some embodiments, the processing circuitry 15402 includes a system on a chip (SOC).In some embodiments, the processing circuitry 15402 includes one or more of radio frequency(RF) transceiver circuitry 15412 and baseband processing circuitry 15414. In some embodiments,the RF transceiver circuitry 15412 and the baseband processing circuitry 15414 may be onseparate chips (or sets of chips), boards, or units, such as radio units and digital units. Inalternative embodiments, part or all of RF transceiver circuitry 15412 and baseband processingcircuitry 15414 may be on the same chip or set of chips, boards, or units.The memory 15404 may comprise any form of volatile or non-volatile computer-readablememory including, without limitation, persistent storage, solid-state memory, remotely mountedmemory, 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 storeinformation, data, and / or instructions that may be used by the processing circuitry 15402. Thememory 15404 may store any suitable instructions, data, or information, including a computerprogram, software, an application including one or more of logic, rules, code, tables, and / or otherinstructions capable of being executed by the processing circuitry 15402 and utilized by thenetwork node 15400. The memory 15404 may be used to store any calculations made by theprocessing circuitry 15402 and / or any data received via the communication interface 15406. Insome embodiments, the processing circuitry 15402 and memory 15404 is integrated.The communication interface 15406 is used in wired or wireless communication of signalingand / or data with UEs, other network nodes, and / or any other network equipment. In the illustratedembodiment, communication interface 15406 comprises port(s) / terminal(s) 15416 to send andreceive data, for example to and from a network over a wired connection. In particularembodiments, network node 15300 may be capable of wireless communication andcommunication interface 15406 may also include radio front-end circuitry 15418 that may becoupled to, or in certain embodiments a part of, an antenna 15410. Particular embodiments ofradio front-end circuitry 15418 include filter(s) 15420 and amplifier(s) 15422. The radio front-endcircuitry 15418 may be connected to an antenna 15410 and processing circuitry 15402. The radiofront-end circuitry may be configured to condition signals communicated between antenna 15410and processing circuitry 15402. The radio front-end circuitry 15418 may receive digital data that isto be sent out to other network nodes or UEs via a wireless connection. The radio front-endcircuitry 15418 may convert the digital data into a radio signal(s) having the appropriate channeland bandwidth parameters using a combination of filters 15420 and / or amplifiers 15422. The radiosignal(s) may then be transmitted via the antenna 15410. Similarly, when receiving data, theantenna 15410 may collect radio signals which are then converted into digital data by the radiofront-end circuitry 15418. The digital data may be passed to the processing circuitry 15402. Inother embodiments, the communication interface may comprise different components and / ordifferent combinations of components.In certain alternative embodiments, network node 15400 may be capable of wirelesscommunication but does not include separate radio front-end circuitry 15418, instead, theprocessing circuitry 15402 includes radio front-end circuitry and is connected to the antenna15410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 15412 is part ofthe communication interface 15406. In still other embodiments, the communication interface 15406includes one or more ports or terminals 15416, the radio front-end circuitry 15418, and the RFtransceiver circuitry 15412, as part of a radio unit (not shown), and the communication interface15406 communicates with the baseband processing circuitry 15414, which is part of a digital unit(not shown).The antenna 15410 may include one or more antennas, or antenna arrays, configured tosend and / or receive wireless signals. The antenna 15410 may be coupled to the radio front-endcircuitry 15418 and may be any type of antenna capable of transmitting and receiving data and / orsignals wirelessly. In certain embodiments, the antenna 15410 is separate from the network node15400 and connectable to the network node 15400 through one or more interfaces or ports.The antenna 15410, communication interface 15406, and / or the processing circuitry 15402may be configured to perform some or all of the receiving operations and / or obtaining operationsdescribed herein as being performed by the network node 15400. Any information, data and / orsignals may be received from a UE, another network node and / or any other network equipment.Similarly, the antenna 15410, the communication interface 15406, and / or the processing circuitry15402 may be configured to perform some or all of the transmitting or sending operationsdescribed herein as being performed by the network node 15400. Any information, data and / orsignals may be transmitted to a UE, another network node and / or any other network equipment.The power source 15408 provides power to the various components of network node15400 in a form suitable for the respective components (e.g., at a voltage and current level neededfor each respective component). The power source 15408 may further comprise, or be coupled to,power management circuitry to supply the components of the network node 15400 with power forperforming the functionality described herein. For example, the network node 15400 may beconnectable to an external power source (e.g., the power grid, an electricity outlet) via an inputcircuitry or interface such as an electrical cable, whereby the external power source supplies powerto power circuitry of the power source 15408. As a further example, the power source 15408 maycomprise a source of power in the form of a battery or battery pack which is connected to, orintegrated in, power circuitry. The battery may provide backup power should the external powersource fail.Embodiments of the network node 15400 may include additional components beyond thoseshown in Figure 8 for providing certain aspects of the network node’s functionality, including any ofthe functionality described herein and / or any functionality necessary to support the subject matterdescribed herein. For example, the network node 15400 may include user interface equipment toallow input of information into the network node 15400 and to allow output of information from thenetwork node 15400. This may allow a user to perform diagnostic, maintenance, repair, and otheradministrative functions for the network node 15400.Figure 9 is a block diagram illustrating a virtualization environment 15500 in whichfunctions implemented by some embodiments may be virtualized. In the present context,virtualizing means creating virtual versions of apparatuses or devices which may includevirtualizing hardware platforms, storage devices and networking resources. As used herein,virtualization can be applied to any device described herein, or components thereof, and relates toan implementation in which at least a portion of the functionality is implemented as one or morevirtual components. Some or all of the functions described herein may be implemented as virtualcomponents executed by one or more virtual machines (VMs) implemented in one or more virtualenvironments 15500 hosted by one or more of hardware nodes, such as a hardware computingdevice that operates as an access network node, UE, core network node, or host. Further, inembodiments in which a virtual node does not require radio connectivity (e.g., a core network nodeor host), then the node may be entirely virtualized. In some embodiments, the virtualizationenvironment 15500 includes components defined by the O-RAN Alliance, such as an O-Cloudenvironment orchestrated by a Service Management and Orchestration Framework via an O-2interface. Applications 15502 (which may alternatively be called software instances, virtualappliances, network functions, virtual nodes, virtual network functions, etc.) are run in thevirtualization environment Q400 to implement some of the features, functions, and / or benefits ofsome of the embodiments disclosed herein.Hardware 15504 includes processing circuitry, memory that stores software and / orinstructions executable by hardware processing circuitry, and / or other hardware devices asdescribed herein, such as a network interface, input / output interface, and so forth. Software maybe executed by the processing circuitry to instantiate one or more virtualization layers 15506 (alsoreferred to as hypervisors or virtual machine monitors (VMMs)), provide VM 15508A and VM15508B (which may be collectively referred to as VMs 15508), and / or perform any of the functions,features and / or benefits described in relation with some embodiments described herein. Thevirtualization layer 15506 may present a virtual operating platform that appears like networkinghardware to one or more of the VMs 15508.The VMs 15508 comprise virtual processing, virtual memory, virtual networking or interfaceand virtual storage, and may be run by virtualization layer 15506. Different embodiments of theinstance of a virtual appliance 15502 may be implemented on one or more of VMs 15508, and theimplementations may be made in different ways. Virtualization of the hardware is in some contextsreferred to as network function virtualization (NFV). NFV may be used to consolidate many networkequipment types onto industry standard high volume server hardware, physical switches, andphysical storage, which can be located in data centers, and customer premise equipment.In the context of NFV, each of the VMs 15508 may be a software implementation of aphysical machine that runs programs as if they were executing on a physical, non-virtualizedmachine. Each of the VMs 15508, and that part of hardware 15504 that executes that VM, be ithardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, formsseparate virtual network elements. Still in the context of NFV, a virtual network function isresponsible for handling specific network functions that run in one or more of the VMs 15508 ontop of the hardware 15504 and corresponds to an application 15502.Hardware 15504 may be implemented in a standalone network node with generic orspecific components. Hardware 15504 may implement some functions via virtualization.Alternatively, hardware 15504 may be part of a larger cluster of hardware (e.g. such as in a datacenter or CPE) where many hardware nodes work together and are managed via managementand orchestration 15510, which, among others, oversees lifecycle management of applications15502. In some embodiments, hardware 15504 is coupled to one or more radio units that eachinclude one or more transmitters and one or more receivers that may be coupled to one or moreantennas. Radio units may communicate directly with other hardware nodes via one or moreappropriate network interfaces and may be used in combination with the virtual components toprovide a virtual node with radio capabilities, such as a radio access node or a base station. Insome embodiments, some signaling can be provided with the use of a control system 15512 whichmay alternatively be used for communication between hardware nodes and radio units.Although the computing devices described herein (e.g., UEs, network nodes, hosts) mayinclude the illustrated combination of hardware components, other embodiments may comprisecomputing devices with different combinations of components. It is to be understood that thesecomputing devices may comprise any suitable combination of hardware and / or software needed toperform the tasks, features, functions and methods disclosed herein. Determining, calculating,obtaining or similar operations described herein may be performed by processing circuitry, whichmay process information by, for example, converting the obtained information into otherinformation, comparing the obtained information or converted information to information stored inthe network node, and / or performing one or more operations based on the obtained information orconverted information, and as a result of said processing making a determination. Moreover, whilecomponents are depicted as single boxes located within a larger box, or nested within multipleboxes, in practice, computing devices may comprise multiple different physical components thatmake up a single illustrated component, and functionality may be partitioned between separatecomponents. For example, a communication interface may be configured to include any of thecomponents described herein, and / or the functionality of the components may be partitionedbetween the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software orfirmware and computationally intensive functions may be implemented in hardware.In certain embodiments, some or all of the functionality described herein may be provided byprocessing circuitry executing instructions stored on in memory, which in certain embodiments maybe 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 processingcircuitry without executing instructions stored on a separate or discrete device-readable storagemedium, 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, theprocessing circuitry can be configured to perform the described functionality. The benefits providedby such functionality are not limited to the processing circuitry alone or to other components of thecomputing device, but are enjoyed by the computing device as a whole, and / or by end users and awireless network generally.In some embodiments a more general term “network node” is used and it can correspond toany type of radio network node or any network node, which communicates with a wireless deviceand / or with another network node. Examples of network nodes are NodeB, Master eNB,Secondary eNB, a network node belonging to Master cell group (MCG) or Secondary Cell Group(SCG), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB,network controller, radio network controller (RNC), base station controller (BSC), relay, donor nodecontrolling relay, base transceiver station (BTS), access point (AP), transmission points,transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributedantenna system (DAS), core network node e.g. Mobility Switching Centre (MSC), MobileManagement Entity (MME) etc., Operation and Maintenance (O&M), Operation Support System(OSS), Self-Organizing Network (SON), positioning node e.g. Evolved Serving Mobile LocationCentre (E-SMLC), Minimizing Drive Test (MDT), etc.In some embodiments, the non-limiting term wireless device or user equipment (UE) isused and it refers to any type of wireless device communicating with a network node and / or withanother UE in a cellular or mobile communication system. Examples of UE are target device,device-to-device (D2D) UE, proximity capable UE (aka ProSe UE), machine type UE or UEcapable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smartphone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.The embodiments are described for 5G. However the embodiments are applicable to anyRAT or multi-RAT systems, where the UE receives and / or transmit signals (e.g. data) e.g. LTE,LTE FDD / TDD, WCDMA / HSPA, GSM / GERAN, Wi Fi, WLAN, CDMA2000 etc.As will be readily understood by those familiar with communications design, functionsmeans or modules may be implemented using digital logic and / or one or more microcontrollers,microprocessors, or other digital hardware. In some embodiments, several or all of the variousfunctions may be implemented together, such as in a single application-specific integratedcircuit (ASIC), or in two or more separate devices with appropriate hardware and / or softwareinterfaces between them. Several of the functions may be implemented on a processor sharedwith other functional components of a wireless device or network node, for example.Alternatively, several of the functional elements of the processing means discussed maybe provided through the use of dedicated hardware, while others are provided with hardware forexecuting software, in association with the appropriate software or firmware. Thus, the term“processor” or “controller” as used herein does not exclusively refer to hardware capable ofexecuting software and may implicitly include, without limitation, digital signal processor (DSP)hardware, read-only memory (ROM) for storing software, random-access memory for storingsoftware and / or program or application data, and non-volatile memory. Other hardware,conventional and / or custom, may also be included. Designers of communications devices willappreciate the cost, performance, and maintenance trade-offs inherent in these design choices.It will be appreciated that the foregoing description and the accompanying drawingsrepresent non-limiting examples of the methods and apparatus taught herein. As such, theapparatus and techniques taught herein are not limited by the foregoing description andaccompanying drawings. Instead, the embodiments herein are limited only by the followingclaims and their legal equivalents.Embodiments:A1. A method performed by a UE 10 for handling communication in a wireless communicationnetwork 1, the method comprising:when the UE 10 being configured with a configuration related to CHO with candidate SCGprocedure, logging and / or sending information upon execution of an event, wherein the event isassociated or based on the configuration.B1. A method performed by a network node 150 for handling communication in a wirelesscommunication network 1, the method comprising:receiving a report and / or information from a UE 10, wherein the information comprisesinformation related to an event, wherein the event is associated or based on a configuration relatedto CHO with candidate SCG procedure;performing an operation based on the report and / or information.C1. The UE 10 for handling communication in a wireless communication network 1, wherein theUE is configured to:when the UE 10 being configured with a configuration related to CHO with candidate SCGprocedure, log and / or send information upon execution of an event, wherein the event isassociated or based on the configuration.D1. The network node 150 for handling communication in a wireless communication network 1,wherein the network node is configured to:receive a report and / or information from the UE 10, wherein the information comprisesinformation related to an event, wherein the event is associated or based on a configuration relatedto CHO with candidate SCG procedure; andperform an operation based on the report and / or information.E1. A computer program product comprising instructions, which, when executed on at least oneprocessor, cause the at least one processor to carry out the method according to any of theembodiments A1 or B1, as performed by the network node 150 and the UE 10, respectively.F1. A computer-readable storage medium, having stored thereon a computer program productcomprising instructions which, when executed on at least one processor, cause the at least oneprocessor to carry out the method according to any of the embodiments A1 or B1, as performed bythe network node 150 and the UE 10, respectively..References:1. TS 38.300 V18.0.0 NR; NR and NG-RAN Overall description; Stage-2, 3GPP2. TS 38.331 V18.0.0 NR; Radio Resource Control (RRC); Protocol specification, 3GPP

Claims

CLAIMS 1. A method performed by a user equipment, UE, (10) for handling communication in awireless communication network, the method comprising:- when the UE is configured with a configuration related to a conditional handover, CHO, withcandidate secondary cell group, SCG, procedure, logging and / or sending (313) informationupon execution of an event, wherein the event is associated with or based on theconfiguration.

2. The method according to claim 1, wherein the information comprises timer relatedinformation, and / or measurement results, which the UE (10) used to evaluate one or moreexecution conditions.

3. The method according to any of the claims 1-2, wherein the information indicates a timeinterval between a CHO execution fulfillment and a detection of at least one of an SCGFailure or an RLF.

4. The method according to any of the claims 1-3, wherein the information is sent in a radiolink failure, RLF, report and / or a SCG failure report.

5. The method according to any of the claims 1-4, wherein the information comprises one ormore primary cell, PCell, identities and / or one or more primary secondary cell, PSCell,identities corresponding to one or more cells for which an execution condition for PCellHandover and / or an execution condition for PSCell Change were satisfied.

6. The method according to any of the claims 1-5, wherein the information comprises a timeelapsed between a first time of a first fulfilled triggering event for a first fulfilled executioncondition to a second time of a fulfilled triggering event for a second execution condition.

7. The method according to the claim 6, wherein the information comprises an indicationindicating whether the first fulfilled execution condition is associated with a CHOconfiguration or with a conditional SCG configuration, and an indication indicating whetherthe second execution condition is associated with the CHO configuration or with theconditional SCG configuration.

8. A method performed by a network node (150) for handling communication in a wirelesscommunication network, the method comprising:- receiving (321)information from a user equipment, UE, (10), wherein the informationcomprises information related to an event, wherein the event is associated with or based ona configuration related to a conditional handover, CHO, with candidate secondary cellgroup, SCG, procedure; and- performing (323) an operation based on the received information.

9. The method according to claim 8, further comprising:- transmitting (320) to the UE 10 the configuration related to the CHO with candidate SCGprocedure.

10. The method according to any of the claims 8-9, further comprising:- analyzing (322) the information reported by the UE (10).

11. The method according to any of the claims 8-10, wherein performing (323) the operationcomprises identifying a certain network node where the optimization is required based onthe information, and forwarding the information to that certain network node.

12. The method according to any of the claims 8-11, wherein performing (323) the operationcomprises optimizing one or more parameters related to mobility and / or an event basedon the information.

13. A user equipment, UE, (10) for handling communication in a wireless communicationnetwork, wherein the UE (10) is configured to:when the UE (10) is configured with a configuration related to conditional handover,CHO, with candidate secondary cell group, SCG, procedure, log and / or send informationupon execution of an event, wherein the event is associated with or based on theconfiguration.

14. The UE (10) according to claim 13, wherein the information comprises timer relatedinformation, and / or measurement results, which the UE (10) used to evaluate one or moreexecution conditions.

15. The UE (10) according to any of the claims 13-14, wherein the information indicates atime interval between a CHO execution fulfillment and a detection of at least one of an SCGFailure or an RLF.

16. The UE (10) according to any of the claims 13-15, wherein the information is sent in aradio link failure, RLF, report and / or a SCG failure report.

17. The UE (10) according to any of the claims 13-16, wherein the information comprises oneor more primary cell, PCell, identities and / or one or more primary secondary cell, PSCell,identities corresponding to one or more cells for which an execution condition for PCellHandover and / or an execution condition for PSCell Change were satisfied.

18. The UE (10) according to any of the claims 13-17, wherein the information comprises atime elapsed between a first time of a first fulfilled triggering event for a first fulfilledexecution condition to a second time of a fulfilled triggering event for a second executioncondition.

19. The UE (10) according to the claim 18, wherein the information comprises an indicationindicating whether the first fulfilled execution condition is associated with a CHOconfiguration or with a conditional SCG configuration, and an indication indicating whetherthe second execution condition is associated with the CHO configuration or with theconditional SCG configuration.

20. A network node (150) for handling communication in a wireless communication network,wherein the network node (150) is configured to:receive information from a user equipment, UE, (10), wherein the informationcomprises information related to an event, wherein the event is associated with or based ona configuration related to a conditional handover, CHO, with candidate secondary cellgroup, SCG, procedure; andperform an operation based on the received information.

21. The network node (150) according to claim 20, wherein the network node (150) isconfigured to:transmit to the UE (10) the configuration related to the CHO with candidate SCGprocedure.

22. The network node (150) according to any of the claims 20-21, wherein the network node(150) is configured to:analyze the information reported by the UE (10).

23. The network node (150) according to any of the claims 20-22, wherein the network node(150) is configured to perform the operation by identifying a certain network node whereoptimization is required based on the information, and forwarding the information to thatcertain network node.

24. The network node (150) according to any of the claims 20-23, wherein the network node(150) is configured to perform the operation by optimizing one or more parameters relatedto mobility and / or an event based on the information.

25. A computer program product comprising instructions, which, when executed on at least oneprocessor, cause the at least one processor to carry out the method according to any of theclaims 1-12, as performed by the network node (150) and the UE (10), respectively.

26. A computer-readable storage medium, having stored thereon a computer program productcomprising instructions which, when executed on at least one processor, cause the at leastone processor to carry out the method according to any of the claims 1-12, as performed bythe network node (150) and the UE (10), respectively.

Images