WO2024030065A1 - Reporting of successful reconfiguration with sync (spcell change) involving lbt issues - Google Patents

Abstract

Methods for handling reporting of successful handovers in scenarios involving listen-before-talk, LBT, operations. In an example, a wireless network sends (410), to a wireless device, configuration information indicating at least one condition for triggering, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell, PSCell, a recording of information regarding LBT operations performed by the wireless device. The network may subsequently be informed of the availability of the report, and retrieve it from the wireless device. The triggering of the recording of information may be in response a predetermined quantity or rate of LBT failures in association with a mobility procedure or change or addition of PSCell.

Description

REPORTING OF SUCCESSFUL RECONFIGURATION WITH SYNC (SPCELL CHANGE) INVOLVING LBT ISSUES TECHNICAL FIELD The present disclosure is generally related to wireless networks and is more particularly related to reporting information related to handovers and other reconfigurations in such wireless networks. BACKGROUND The Self-Organizing Network (SON) is an automation technology designed to make the planning, configuration, management, optimization and healing of mobile radio access networks simpler and faster. SON functionality and behavior has been defined and specified in generally accepted mobile industry recommendations produced by organizations such as 3GPP (3rd Generation Partnership Project) and the NGMN (Next Generation Mobile Networks). In 3GPP, processes within the SON area are classified into self-configuration processes and self- optimization processes. Self-configuration processes are where newly deployed nodes are configured by automatic installation procedures to get the necessary basic configuration for system operation. The self-configuration processes work in the pre-operational state, where the pre- operational state is understood as the state from when the eNB (or other base station) is powered up and has backbone connectivity until the radio frequency (RF) transmitter is switched on. As illustrated in Figure 1, which generally illustrates the ramifications of self-configuration and self- optimization functionality, and which is taken from 3GPP TS 36.300 figure 22.1-1, functions handled in the pre-operational state like: ^ Basic Setup; and ^ Initial Radio Configuration. are covered by the self-configuration processes. Self-optimization processes are defined as processes where UE (wireless terminal) and access node measurements and performance measurements are used to auto-tune the network. These processes work in the operational state, where the operational state is understood as the state where the RF interface of the base station(s) is additionally switched on. As shown in Figure 1, functions handled in the operational state like: ^ Optimization / Adaptation are covered by the self-optimization processes. In LTE, support for self-configuration and self-optimization is specified, as described in 3GPP TS 36.300 section 22.2, including features such as dynamic configuration, automatic neighbour relation (ANR), mobility load balancing, mobility robustness optimization (MRO), RACH optimization, and support for energy saving. In NR, support for self-configuration and self-optimization is specified as well, starting with self-configuration features such as dynamic configuration, automatic neighbour relation (ANR) in Rel-15, as described in 3GPP TS 38.300 section 15. In NR Rel-16, more SON features are being specified, including self-optimization features such as mobility robustness optimization (MRO). Seamless handovers are a key feature of 3GPP technologies. Successful handovers ensure that the UE moves around in the coverage area of different cells without causing excessive interruptions in data transmission. However, there will be scenarios when the network fails to handover the UE to the ‘correct’ neighbor cell in time and in such scenarios the UE will declare radio link failure (RLF) or Handover Failure (HOF). Upon HOF and RLF, the UE may take various autonomous actions, such as trying to select a cell and initiate reestablishment procedure to ensure that the UE reestablishes connectivity as soon as it can, so that it can be reachable again. An RLF will cause a poor user experience, as the RLF is declared by the UE only when it realizes that there is no reliable communication channel (radio link) available between itself and the network. Also, reestablishing the connection requires signaling with the newly selected cell (random access procedure, RRC Reestablishment Request, RRC Reestablishment RRC Reestablishment Complete, RRC Reconfiguration and RRC Reconfiguration Complete) and adds some latency before the UE can exchange data with the network again. According to 3GPP specifications (3GPP TS 36.331), possible causes for radio link failure could be one of the following: 1) Expiry of the radio link monitoring related timer T310; 2) Expiry of the measurement reporting associated timer T312 (not receiving the handover command from the network within this timer’s duration despite sending the measurement report when T310 was running); 3) Upon reaching the maximum number of RLC retransmissions; 4) Upon receiving random access problem indication from the MAC entity. As RLF leads to reestablishment which degrades performance and user experience, it is in the interest of the network to understand the reasons for RLF and try to optimize mobility related parameters (e.g., trigger conditions of measurement reports) to avoid later RLFs. Before the standardization of MRO related report handling in the network, only the UE was aware of information such as how the radio quality looked like at the time of RLF, what was the actual reason for declaring RLF, etc. For the network to identify the reason for the RLF, the network needs more information, both from the UE and from neighboring base stations. As part of the MRO solution in LTE, an RLF reporting procedure was introduced in the RRC specification in Rel-9 RAN2 work. That impacted the RRC specifications (TS 36.331) in the sense that it was standardized that the UE would log relevant information at the moment of an RLF and later report to a target cell to which the UE successfully connected (e.g., after reestablishment). That has also impacted the inter-gNodeB interface, i.e., X2AP specifications (3GPP TS 36.423), since an eNodeB receiving an RLF report could forward the report to the eNodeB where the failure originated. The contents of the RLF report generated by the UE have been enhanced with more details in the subsequent releases of the specifications. The measurements included in the measurement report based on the latest LTE RRC specification are: 1) Measurement quantities (RSRP, RSRQ) of the last serving cell (PCell). 2) Measurement quantities of the neighbor cells in different frequencies of different RATs (EUTRA, UTRA, GERAN, CDMA2000). 3) Measurement quantity (RSSI) associated to WLAN Aps. 4) Measurement quantity (RSSI) associated to Bluetooth beacons. 5) Location information, if available (including location coordinates and velocity) 6) Globally unique identity of the last serving cell, if available, otherwise the PCI and the carrier frequency of the last serving cell. 7) Tracking area code of the PCell. 8) Time elapsed since the last reception of the ‘Handover command’ message. 9) C-RNTI used in the previous serving cell. 10) Whether or not the UE was configured with a DRB having QCI value of 1. After an RLF is declared, the RLF report is logged by the UE and included in the VarRLF-Report. Once the UE selects a cell and succeeds with a reestablishment, the UE includes an indication that it has an RLF report available in the RRC Reestablishment Complete message, to make the target cell aware of that availability. Then, upon receiving an UEInformationRequest message with a flag “rlf- ReportReq-r9,” the UE includes the RLF report (stored in a UE variable VarRLF-Report, as described above) in an UEInformationResponse message and sends it to the network. Based on the RLF report from the UE and the knowledge about the cell with which the UE reestablished itself, the original source cell can deduce whether the RLF was caused by a coverage hole or by handover-associated parameter configurations. If the RLF was deemed to be due to handover-associated parameter configurations, the original serving cell can further classify the handover related failure as too-early, too-late or handover to wrong cell classes. These handover failure classes are explained in brief below: 1) Whether the handover failure occurred due to the ‘too-late handover’ cases: a. The original serving cell can classify a handover failure to be ‘too late handover’ when the original serving cell fails to send the handover command to the UE associated to a handover towards a particular target cell and if the UE reestablishes itself in this target cell post RLF. b. An example corrective action from the original serving cell could be to initiate the handover procedure towards this target cell a bit earlier by decreasing the CIO (cell individual offset) towards the target cell that controls when the IE sends the event triggered measurement report that leads to taking the handover decision. 2) Whether the handover failure occurred due to the ‘too-early handover’ cases: a. The original serving cell can classify a handover failure to be ‘too early handover’ when the original serving cell is successful in sending the handover command to the UE associated to a handover however the UE fails to perform the random access towards this target cell. b. An example corrective action from the original serving cell could be to initiate the handover procedure towards this target cell a bit later by increasing the CIO (cell individual offset) towards the target cell that controls when the IE sends the event triggered measurement report that leads to taking the handover decision. 3) Whether the handover failure occurred due to the ‘handover-to-wrong-cell’ cases: a. The original serving cell can classify a handover failure to be ‘handover-to-wrong-cell’ when the original serving cell intends to perform the handover for this UE towards a particular target cell but the UE declares the RLF and reestablishes itself in a third cell. b. A corrective action from the original serving cell can be to initiate the measurement reporting procedure that leads to handover towards the target cell a bit later, by decreasing the CIO (cell individual offset) towards the target cell or via initiating the handover towards the cell in which the UE reestablished a bit earlier by increasing the CIO towards the reestablishment cell. 3GPP has standardized, for Release 17, a successful handover report (SHR, also referred to as handover success report) that may be sent by the UE to the network upon successful execution of a handover (e.g., reconfiguration with sync). As part of this work, 3GPP has defined a SHR configuration as a configuration that a UE should apply it when the UE is in an RRC_CONNECTED state, in order to report information (e.g., measurements) to the network about a successful handover under some specific conditions that are configured by the network. A key purpose of the successful HO report is to enable the network nodes to deduce sub-optimal performance of the underlaying procedures executed during the HO procedure. A network node, upon being interested in SHR, can configure the UE to report the SHR after successful execution of a HO, if at least one of the SHR triggering conditions/thresholds is met. The SHR triggering thresholds are defined as following: ^ Whether the T304 timer value was above a certain threshold at the time of successful HO execution (thresholdPercentageT304); ^ Whether the T310 timer value was above a certain threshold at the time of successful HO execution (thresholdPercentageT310); ^ Whether the T312 timer value was above a certain threshold at the time of successful HO execution (thresholdPercentageT312); ^ Whether the UE experienced RLF at source node while performing a DAPS HO (sourceDAPS-FailureReporting). These thresholds, which are expressed in terms of the ratio of the timer value to its configured time-out value, are shown in the following IE of the ASN.1 captured in TS 38.331. -------------------------------- begin 3GPP excerpt ---------------------------------------------------- SuccessHO-Config-r17 ::= SEQUENCE { thresholdPercentageT304-r17 ENUMERATED {p40, p60, p80, spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need R thresholdPercentageT310-r17 ENUMERATED {p40, p60, p80, spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need R thresholdPercentageT312-r17 ENUMERATED {p20, p40, p60, p80, spare4, spare3, spare2, spare1} OPTIONAL, --Need R sourceDAPS-FailureReporting-r17 ENUMERATED {true} OPTIONAL, --Need R ... } -----------------------------------end 3GPP excerpt ------------------------------------------------------- Note that among the above thresholds. the threshold concerning T304 is configured by the target RAN node and the rest of the thresholds are configured by the source RAN node, as part of the otherConfig information element (IE). The UE, upon fulfilment of any of the configured thresholds, compiles an SHR, when executing a reconfiguration with sync procedure toward the target cell was successful. In other words, upon completion of the random access procedure toward a target RAN node, if at least one of the configured triggering thresholds is fulfilled, the UE compiles the SHR. Compilation of the SHR report as part of RRC procedure is shown in the following excerpt from the 3GPP specifications. -------------------------------- begin 3GPP excerpt ---------------------------------------------------- 5.7.10.6 Actions for the successful handover report determination The UE shall for the PCell: 1> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last applied RRCReconfiguration message including the reconfigurationWithSync, is greater than thresholdPercentageT304 if included in the successHO-Config received before executing the last reconfiguration with sync; or 1> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT310 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync; or 1> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312 included in the successHO- Config if configured by the source PCell before executing the last reconfiguration with sync; or 1> if sourceDAPS-FailureReporting is included in the successHO-Config before executing the last reconfiguration with sync and is set to true and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running: 2> store the successful handover information in VarSuccessHO-Report and determine the content in VarSuccessHO-Report as follows: 3> clear the information included in VarSuccessHO-Report, if any; 3> set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e., includes the RPLMN); 3> set the c-RNTI to the C-RNTI assigned by the target PCell of the handover; 3> for the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied: 4> set the sourceCellID in sourceCellInfo to the global cell identity and tracking area code, if available, of the source PCell; 4> set the sourceCellMeas in sourceCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the source PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message; 4> set the rsIndexResults in sourceCellMeas to include all the available SSB and CSI-RS measurement quantities of the source PCell collected up to the moment the UE sends RRCReconfigurationComplete message; 4> if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running: 5> set the rlf-InSourceDAPS in sourceCellInfo to true; 3> for the target PCell indicated in the last applied RRCReconfiguration message including reconfigurationWithSync: 4> set the targetCellID in targetCellInfo to the global cell identity and tracking area code, if available, of the target PCell; 4> set the targetCellMeas in targetCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message; 4> set the rsIndexResults in targetCellMeas to include all the available SSB and CSI-RS measurement quantities of the target PCell collected up to the moment the UE sends RRCReconfigurationComplete message; 4> if the last applied RRCReconfiguration message including reconfigurationWithSync was included in the stored condRRCReconfig: 5> set the timeSinceCHO-Reconfig to the time elapsed between the initiation of the execution of conditional reconfiguration for the target PCell and the reception of the last conditionalReconfiguration including the condRRCReconfig of the target PCell in the source PCell; 3> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the T304 timer, included in the last applied RRCReconfiguration message including the reconfigurationWithSync, is greater than thresholdPercentageT304 if included in the successHO-Config received before executing the last reconfiguration with sync: 4> set t304-cause in shr-Cause to true; 4> set the ra-InformationCommon to include the random-access related information associated to the random access procedure in the target PCell, as specified in clause 5.7.10.5; 3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the T310 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT310 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync: 4> set t310-cause in shr-Cause to true; 3> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the T312 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync: 4> set t312-cause in shr-Cause to true; 3> if sourceDAPS-FailureReporting included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync is set to true, and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running: 4> set sourceDAPS-Failure in shr-Cause to true; 3> for each of the measObjectNR, configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied: 4> if measurements are available for the measObjectNR: 5> if the SS/PBCH block-based measurement quantities are available: 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS/PBCH block RSRP is listed first if SS/PBCH block RSRP measurement results are available, otherwise the cell with highest SS/PBCH block RSRQ is listed first if SS/PBCH block RSRQ measurement results are available, otherwise the cell with highest SS/PBCH block SINR is listed first, based on the available SS/PBCH block based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message; 6> for each neighbour cell included, include the optional fields that are available; 5> if the CSI-RS measurement quantities are available: 6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message; 6> for each neighbour cell included, include the optional fields that are available; 3> for each of the measObjectEUTRA, configured by the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied: 4> if measurements are available for the measObjectEUTRA: 5> set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, based on measurements collected up to the moment the UE sends the RRCReconfigurationComplete message; 5> for each neighbour cell included, include the optional fields that are available; 3> for each of the neighbour cells included in measResultNeighCells: 4> if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied: 5> set the choCandidate to true in measResultNR; 3> if available, set the locationInfo as in 5.3.3.7; 1> release successHO-Config configured by the source PCell before executing the last reconfiguration with sync. The UE may discard the successful handover information, i.e., release the UE variable VarSuccessHO-Report, 48 hours after the last successful handover information is added to the VarSuccessHO-Report.

excerpt ------------------------------------------------------- After the UE compiles the SHR, in response to a triggering condition having been met, it indicates the availability of the SHR to the network, in the same RRC Reconfiguration Complete message sent as part of the HO. The network can fetch the SHR via a solicitation mechanism i.e., UE Information Request/Response procedure. The ASN1. code defined by 3GPP for the SHR (successHO-Report) is shown in the following. -------------------------------- begin 3GPP excerpt ---------------------------------------------------- SuccessHO-Report-r17 ::= SEQUENCE { sourceCellInfo-r17 SEQUENCE { sourcePCellId-r17 CGI-Info-Logging-r16, sourceCellMeas-r17 MeasResultSuccessHONR- r17 OPTIONAL, rlf-InSourceDAPS-r17 ENUMERATED {true} OPTIONAL }, targetCellInfo-r17 SEQUENCE { targetPCellId-r17 CGI-Info-Logging-r16, targetCellMeas-r17 MeasResultSuccessHONR- r17 OPTIONAL }, measResultNeighCells-r17 SEQUENCE { measResultListNR-r17 MeasResultList2NR-r16 OPTIONAL, measResultListEUTRA-r17 MeasResultList2EUTRA- r16 OPTIONAL } OPTIONAL, locationInfo-r17 LocationInfo-r16 OPTIONAL, timeSinceCHO-Reconfig-r17 TimeSinceCHO-Reconfig-r17 OPTIONAL, shr-Cause-r17 SHR-Cause-r17 OPTIONAL, ra-InformationCommon-r17 RA-InformationCommon-r16 OPTIONAL, upInterruptionTimeAtHO-r17 UPInterruptionTimeAtHO-r17 OPTIONAL, c-RNTI-r17 RNTI-Value OPTIONAL, ... } MeasResultSuccessHONR-r17::= SEQUENCE { measResult-r17 SEQUENCE { cellResults-r17 SEQUENCE{ resultsSSB-Cell-r17 MeasQuantityResults OPTIONAL, resultsCSI-RS-Cell-r17 MeasQuantityResults OPTIONAL }, rsIndexResults-r17 SEQUENCE{ resultsSSB-Indexes-r17 ResultsPerSSB-IndexList OPTIONAL, resultsCSI-RS-Indexes-r17 ResultsPerCSI-RS- IndexList OPTIONAL

excerpt ------------------------------------------------------- Upon reception of a Successful HO Report, the receiving node is able to analyse whether its mobility configuration needs adjustment. Such adjustments may result in changes of mobility configurations, such as changes of RLM configurations or changes of mobility thresholds between the source and the target. In addition, target NG RAN node, in the performed handover, may further optimize the dedicated RACH-beam resources based on the beam measurements reported upon successful handovers. In 3GPP Release 18, the above functionalities will be extended to cover the case of Successful PSCell change/addition. The corresponding report may be referred to as a Successful PSCell Change/Addition Report (SPR). Other technology introduced in recent revisions of the 3GPP specifications involves the use of unlicensed spectrum by base stations and wireless devices in wireless networks. Many regions in the world require a device, when operating in unlicensed spectrum, to sense the medium as free before transmitting. This operation is often referred to as listen-before-talk (LBT). Listen-before-talk (LBT) is essential in the unlicensed spectrum to ensure a fair co-existence with other radio access technologies (RATs) operating in the same spectrum. In this mechanism, a radio device applies a clear channel assessment (CCA) check (i.e., channel sensing) before any transmission. There are many different flavors of LBT, depending on which radio technology the device uses and which type of data it wants to transmit. Common for all flavors is that the sensing is done in a particular channel (corresponding to a defined carrier frequency) and over a predefined bandwidth. For example, in the 5 GHz band, the sensing is done over 20 MHz channels. Many devices are capable of transmitting (and receiving) over a wide bandwidth including of multiple sub-bands/channels, e.g., LBT sub-band (i.e., the frequency part with bandwidth equals to LBT bandwidth). A device is only allowed to transmit on the sub-bands where the medium is sensed as free. Such LBT procedure has to be performed by both the base station, and the UE, whenever they intend to transmit something on the unlicensed spectrum, and that is also applicable to any UL/DL transmission, i.e. both data, layer-1/2/3 control signaling. More specifically, the LBT procedure implies that the transmitter performs energy detection (ED) over a time period, comparing the detected energy to a certain threshold (ED threshold) to determine whether a channel is idle. In case the channel is determined to be occupied, the transmitter performs a random back-off within a contention window before next CCA attempt. In order to protect the ACK transmissions, the transmitter must defer a period after each busy CCA slot prior to resuming back-off. As soon as the transmitter has grasped access to a channel, the transmitter is only allowed to perform transmission up to a maximum time duration (namely, the maximum channel occupancy time (MCOT)). For QoS differentiation, a channel access priority based on the service type has been defined. For example, there are four LBT priority classes are defined for differentiation of contention window sizes (CWS) and MCOT between services. Therefore, the LBT class selected for a transmission depends on the priority of the data to transmit or on the type of signal to transmit, e.g., if that is a PRACH, PUCCH, or RRC signal. SUMMARY The SHR or successful handover report is designed to enable the UE to log and report information and measurement concerning a successfully executed mobility procedure including regular HO, DAPS HO, or conditional HO, to reflect the sub-optimal execution of the procedure. The UE reports the SHR upon receiving an SHR configuration from the network nodes (either from the source node for the handover, or the target node, or both) if one of the SHR triggering conditions is met. The SHR triggering thresholds currently defined by 3GPP are the following: ^ Whether the T304 timer value was above a certain threshold at the time of successful HO execution (thresholdPercentageT304); ^ Whether the T310 timer value was above a certain threshold at the time of successful HO execution (thresholdPercentageT310); ^ Whether the T312 timer value was above a certain threshold at the time of successful HO execution (thresholdPercentageT312); ^ Whether the UE experienced radio link failure (RLF) at source node while performing a DAPS HO (sourceDAPS-FailureReporting). Considering that the use of unlicensed spectrum according to 3GPP specifications, which might be referred to as “NR-Unlicensed” or “NR-U” operation, supports mobility of the UEs, sub-optimal execution of the mobility procedure in NR-U might degrade the user’s quality of service (QoS) or experience (QoE). However as of now, there are no parameters that can be used to trigger collection of the SHR based on the peculiarities of the NR-U system and that take into account UE operations when operating in the unlicensed spectrum. The same issue exists for the dual connectivity operations such as successful PSCell addition or successful PSCell change in the NR-U band. Described herein are methods performed by a network node, where the network node configures the UE (as part of SHR/SPR configuration) with at least one SHR/SPR triggering condition concerning LBT issues, instructing the UE to collect/log SHR/SPR upon experiencing LBT-related issues. Also described herein are corresponding methods performed by the wireless terminal (so-called user equipment (UE)) to evaluate the SHR triggering condition(s) concerning LBT issues and, upon fulfilling SHR/SPR triggering condition(s), to log/store the SHR/SPR and report to the network node upon request. In an example method, a node in a wireless network sends, to a wireless device, configuration information indicating at least one condition for triggering, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell (PSCell), a recording of information regarding listen-before-talk (LBT) operations performed by the wireless device. The network may subsequently be informed of the availability of the report, and retrieve it from the wireless device. The triggering of the recording of information may be in response a predetermined quantity or rate of LBT failures in association with a mobility procedure or change or addition of PSCell. A corresponding method, performed by a wireless device operating in a wireless device, comprises receiving, from the wireless network, configuration information including or indicating one or more conditions for triggering, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell (PSCell), a recording of information regarding listen-before-talk (LBT) operations performed by the wireless device. The method further comprises subsequently determining that at least one of the one or conditions has occurred, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell (PSCell), and, responsive to this determination, recording information regarding LBT operations performed by the wireless device in association with the mobility procedure or change or addition of the PSCell. With the solutions described herein, the network can configure the UE to collect the measurement and information concerning sub-optimal mobility procedures such as legacy HO, CHO, DAPS HO in an NR unlicensed spectrum which might be performed with underlying issues like LBT failures. Hence the network nodes can use such information and measurements provided by the UE to optimize the mobility procedures in NR-U networks. One example of such optimization would be to reduce mobility towards a cell in NR-U band if the RSSI measurements on such a NR-U band is quite poor which might result in many LBT failures during RA procedure. BRIEF DESCRIPTION OF FIGURES Figure 1 illustrates the ramifications of self-configuration and self-optimization functionality in 3GPP networks. Figure 2 is a signal flow diagram illustrating an example procedure in a wireless network. Figure 3 is a process flow diagram illustrating an example method in a wireless device. Figure 4 is a process flow diagram illustrating an example method in a network node. Figure 5 shows an example of a communication system in accordance with some embodiments. Figure 6 shows a UE in accordance with some embodiments. Figure 7 shows a network node in accordance with some embodiments. Figure 8 is a block diagram of a host. Figure 9 is a block diagram illustrating a virtualization environment. Figure 10 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments. DETAILED DESCRIPTION Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. The following description of various techniques relies upon NR-related examples. However, this is for illustration purposes only, as the techniques are applicable in other radio access technologies, such as forthcoming sixth-generation wireless networks. Further, a primary targeted scenario is the HO procedure in a context involving the use of unlicensed spectrum, with the techniques herein involving the corresponding successful handover configuration and report, but the techniques is applicable to any other reconfiguration with sync (reconfigurationWithSync) procedures involving the use of unlicensed spectrum, including reconfiguration with sync on MCG or SCG in case of dual connectivity operations such as PSCell Addition or PSCell change, even if executed conditionally. Hence, when the target/source cell is mentioned it can be referred either to the target/source PCell of the HO, or target/source PSCell at PSCell change or the PCell and the new added PSCell in case of PSCell Addition. It should also be noted that this document uses the term “SHR configuration,” which may be mapped to the successHO-Config in the 3GPP specifications for Radio Resource Control (RRC), e.g., 3GPP 38.331 version 17.0.0. Likewise, “SHR” stands for successful handover report, which term may be mapped to the SuccessHO-Report defined in those same specifications. However, for purposes of describing the techniques herein, the term “SHR configuration” should also be understood to refer to a configuration relating to reporting for a successful PSCell change/addition, which is not currently defined in the 3GPP specifications. Likewise, the term “SHR” should be understood, for purposes of the present disclosure, to also refer to the successful PSCell change/addition report. In this document, a report relating specifically to a successful PSCell change addition might be referred to as a SPR. Nevertheless, when the terms “SHR” or “SHR configuration” are used alone in this document, they should be understood to encompass an SPR or SPR configuration, unless the context clearly indicates that the narrower meaning is meant. Various embodiments of the presently disclosed techniques include one or more of the following aspects: ^ SHR/SPR triggering conditions/thresholds concerning LBT issue configured by the network nodes (either source node or target node or even both of them) ^ SHR/SPR logging/storing by the UE upon fulfilment of the SHR/SPR triggering conditions/thresholds concerning LBT issue during HO execution or PSCell change/addition procedure ^ The said LBT issue can be an LBT issue experienced by the UE for UL transmission, or by the network for DL transmissions and detected by the UE due to missing DL signalling detection (e.g., missing reference signals). Figure 2 is a signal flow diagram illustrating several aspects of the techniques disclosed herein. As shown in the figure, a Radio Access Network (RAN) node, such as an eNB or gNB, sends, to a UE, configuration information for SHR and/or SHR reporting. As will be discussed in further detail below, this configuration information includes LBT-related triggering thresholds, to be used in connection with mobility procedures and/or procedures for changes/additions to PSCell. As also shown in the figure, the UE then evaluates LBT-related SHR/SPR triggering thresholds or other conditions indicated by or included in the SHR/SPR configuration information. In response to one (or more) of these conditions being met, the UE then logs, i.e., records for future use, SHR/SPR information, including LBT-related information. Details of this information are discussed in further detail below. Subsequently, as seen in the figure, the UE may send the SHR/SPR, including the LBT-related information, to the network. As will be discussed, this may be in response to a request for the report(s), which in turn may be in response to the UE informing the network of the availability of the report(s). Finally, the RAN node may analyze the SHR/SPR and use the information therein for adapting subsequent mobility procedures or other procedures involving reconfiguration with sync. Note that in the figure, this step is shown as being performed by the “RAN node.” This analysis and operation may be performed by one or more nodes other than the node that sent the SHR/SPR configuration in the first place. The techniques disclosed herein may be divided into network-side operations and wireless device- side operations although, as seen in Figure 2, these operations complement one another. On the network side, a network node, or multiple network nodes working together, configures the UE (as part of SHR configuration) with at least one SHR/SPR triggering condition/threshold concerning LBT issues during, for example, execution of an RRC Reconfiguration including a reconfigurationWithSync. The configuration instructs the UE to collect/log SHR/SPR upon experiencing LBT issues during a mobility procedure or PSCell addition/change, e.g., during execution of a RRCReconfiguration including the reconfigurationWithSync. The LBT-related SHR/SPR triggering condition/threshold that the network node configures the UE might include at least one of the following conditions/thresholds, in various embodiments or instances: ^ Triggering SHR/SPR if the UE experienced consistent uplink LBT failure at the target cell during reconfigurationWithSync execution ^ Triggering the SHR/SPR if the UE experienced at least N consecutive LBT failures at the target cell during the reconfigurationWithSync execution, where N can be configured by the RAN node or can be predefined or hard coded at the UE. N can be configured as the absolute number of LBT Failures or as a relative metric (e.g., a percentage value). When configured as a relative metric, it can be configured in relation to the number of LBT failures required to declare consistent LBT failure. N can be less than the number of LBT failures that leads to consistent LBT failure ^ Triggering the SHR/SPR if the UE experienced at least N non-consecutive LBT failures at the target cell during the reconfigurationWithSync execution, where N can be configured by the RAN node or can be predefined or hard coded at the UE. N can be configured as the absolute number of LBT Failures or as a relative metric (e.g., a percentage value). When configured as a relative metric, it can be configured in relation to the number of LBT failures required to declare consistent LBT failure. ^ Triggering the SHR/SPR if the UE experienced LBT failures for a certain period of time e.g., T at the target cell during the reconfigurationWithSync execution. T can be configured by the RAN node or can be predefined or hard coded at the UE. T can be configured as the total time or as a relative metric (e.g., a percentage value). When configured as a relative metric, it can be configured in relation to the configured T304 timer associated to the reconfigurationWithSync configuration that is being executed. ^ Triggering SHR/SPR if the UE experienced consistent LBT failure at the source cell during or right before (e.g., within a time interval before) reconfigurationWithSync execution toward target cell ^ In an embodiment the UE, as part of the reconfigurationWithSync, performs a DAPS HO namely the UE was configured with a DAPS bearer when performing HO toward target cell. ^ Triggering the SHR/SPR if the UE experienced at least N consecutive LBT failures at the source cell during or right before (e.g., within a time interval before) the reconfigurationWithSync execution. N can be configured by the RAN node or can be predefined or hard coded at the UE. N can be configured as the absolute number of LBT Failures or as a relative metric (e.g., a percentage value). When configured as a relative metric, it can be configured in relation to the number of LBT failures required to declare consistent LBT failure. N can be less than the number of LBT failures that leads to consistent LBT failure. This might apply, for example, where the UE, as part of the reconfigurationWithSync, performs a DAPS HO namely the UE was configured with a DAPS bearer when performing HO toward target cell. ^ Triggering the SHR/SPR if the UE experienced at least N non-consecutive LBT failures at the source cell during or right before (e.g., within a time interval before) the reconfigurationWithSync execution toward target cell. N can be configured by the RAN node or can be predefined or hard coded at the UE. N can be configured as the absolute number of LBT Failures or as a relative metric (e.g., a percentage value). When configured as a relative metric, it can be configured in relation to the number of LBT failures required to declare consistent LBT failure. Again, this might apply, for example, where the UE, as part of the reconfigurationWithSync, performs a DAPS HO, i.e., the UE was configured with a DAPS bearer when performing HO toward target cell. ^ Triggering the SHR/SPR if the UE experienced LBT failures for a certain period of time e.g., T at the source cell during or right before (e.g., within a time interval before) the reconfigurationWithSync execution. T can be configured by the RAN node or can be predefined or hard coded at the UE. T can be configured as the total time or as a relative metric (e.g., a percentage value). When configured as a relative metric, it can be configured in relation to the configured T304 timer associated to the reconfigurationWithSync configuration that is being executed or in relation to the configured T310 timer associated to the source PCell’s configuration or in relation to the configured T312 timer as configured by the source PCell for the associated measurement object of the target PCell. Once again, this approach might be used, for example, when the UE, as part of the reconfigurationWithSync, performs a DAPS HO, i.e., the UE was configured with a DAPS bearer when performing HO toward target cell. ^ Triggering the SHR/SPR if the UE missed decoding reference signals (RS) from the target cell for at least N consecutive or non-consecutive times during or right before (defined by a time interval) the reconfigurationWithSync execution. N can be configured by the RAN node or can be predefined or hard coded at the UE. ^ Triggering the SHR/SPR if the UE missed decoding reference signals (RS) from the source cell for at least N consecutive or non-consecutive times during or right before (defined by a time interval) the reconfigurationWithSync execution. N can be configured by the RAN node or can be predefined or hard coded at the UE. ^ Triggering the SHR/SPR if the UE missed decoding reference signals (RS) from the target cell for certain time T during or right before (defined by a time interval) the reconfigurationWithSync execution. T can be configured by the RAN node or can be predefined or hard coded at the UE. ^ Triggering the SHR/SPR if the UE missed decoding reference signals (RS) from the source cell for certain time T during or right before (defined by a time interval) the reconfigurationWithSync execution. T can be configured by the RAN node or can be predefined or hard coded at the UE. In some embodiments, the RRCReconfiguration including reconfigurationWithSync is applied for any mobility procedure over MCG or even SCG in case of dual connectivity operations. In other words, the SHR/SPR triggering conditions/thresholds can be applied to the successful PSCell change or successful PSCell addition even if executed conditionally, e.g., in the form of conditional PSCell Addition/Change (so-called CPAC). In some embodiments, the network node configuring the UE with the SHR/SPR triggering thresholds/conditions concerning the LBT issue/missing RSs issue can be the source node of a HO or any reconfiguration with sync (reconfigurationWithSync) procedure including PSCell change or PSCell addition. In a variant of this embodiment, the source node only configures the thresholds/conditions for LBT issues to be evaluated by the UE with respect to the source cell, e.g., LBT issues experienced while attempting to transmit to the source cell, or missing RSs from the source cell. In another variant of this embodiment, the source node configures the thresholds/conditions for LBT issues to be evaluated by the UE both with respect to the source cell and target cell. In this latter embodiment, the configured thresholds/conditions associated to the source cell LBT evaluation can be configured separately from the thresholds/conditions associated to the target cell LBT evaluation. In other embodiments, the network node configuring the UE with the SHR/SPR triggering thresholds/conditions concerning the LBT issue/missing RSs can be the target node of a HO or any reconfiguration with sync (reconfigurationWithSync) procedure including PSCell change or PSCell addition. In a variant of this embodiment, the target node only configures the thresholds/conditions for LBT issues to be evaluated by the UE with respect to the target cell, e.g., LBT issues experienced while attempting to transmit to the target cell, or missing RSs from the target cell. In another variant of this embodiment, the target node configures the thresholds/conditions for LBT issues to be evaluated by the UE both with respect to the source cell and target cell. In this latter embodiment, the configured thresholds/conditions associated to the source cell LBT evaluation can be configured separately from the thresholds/conditions associated to the target cell LBT evaluation. UE-side or wireless device-side embodiments comprise, of course, receiving configuration information like that described above. UE/wireless device-side embodiments further comprise he evaluation of LBT-related SHR triggering conditions/thresholds indicated by this configuration, logging the SHR (or SPR) by the wireless device, and reporting to the network. The present disclosure proposes another method performed by the wireless terminal (so-called user equipment (UE)). Thus, methods carried out by a wireless device may comprise: ^ Receiving an SHR configuration including at least one SHR triggering threshold or other condition related to LBT issues or missing reference signals (RSs). ^ Storing the SHR configuration including the SHR triggering thresholds/conditions related to the LBT issue/missing RSs in a memory. ^ Evaluating the SHR triggering conditions/thresholds concerning LBT issue or missing RSs issue, and upon fulfilling the SHR triggering condition(s) logging/storing the SHR e.g., successHO-Report or successful PSCell change/addition report. The evaluation of the said SHR triggering conditions/thresholds may be with respect to the target cell or to the source cell of the HO, depending on whether the corresponding conditions/thresholds were configured for the source and/or target cell evaluation. In various embodiments, the UE/wireless device logs at least one of the following information elements in the SHR: ^ the number of times it had received the LBT failure indication from lower layers while trying to perform the random access procedure, i.e. transmissions of PRACH msg1/msgA or msg3. In some embodiments, the UE includes a separate counter associated to msg1 related LBT failures and msg3 related LBT failures. ^ the duration for which the UE experienced the LBT issues while performing the handover. ^ the percentage of LBT failures with respect to the overall amount of attempted PRACH transmissions or msg3 transmissions. ^ the BWP ID(s) or the PRACH configuration(s) associated to the BWP(s) in which the UE detected LBT failures while performing random access. ^ for each RA attempt performed while T304 is running, an indication of whether LBT was experienced when attempting to transmit the msg1/msgA or the msg3. This information can be conveyed by including in the SHR the RA-InformationCommon IE which includes the perRAInfoList IE, i.e., the information associated to each RA attempt for this random access procedure while T304 is running. In some embodiments the aforementioned information associated to LBT failures is included in the SHR only if the amount of LBT failures is above a certain threshold, e.g., only if the UE experienced at least one consistent UL LBT failure in one UL BWP. In other embodiments, such LBT information is only included if the value of the T304 at HO completion is above a certain threshold. In other embodiments, such LBT information is only included if the value of the T304 at HO completion is above a certain threshold and the amount of LBT failures is above a certain threshold. Other variations are possible. In some embodiments, one or more of the above LBT evaluations may be performed with respect to the source cell. For example, in the case of DAPS HO, the UE may log the number of LBT failures experienced while attempting to transmit to the source cell after the execution of the reconfiguration with sync, or for how long LBT problems were experienced after the execution of the reconfiguration with sync. In another case, the UE may log the number of LBT failures it experienced in the source cell, right before the execution of the reconfiguration with sync. The UE may indicate the BWP ID(s) or the PRACH configuration(s) associated to the BWP(s) of the source cell in which the UE detected LBT failures. In some embodiments, the UE may include the number of times it had missed receiving RSs while trying to perform the random access procedure upon HO execution in the target cell, or the number of times it had missed receiving RS from the source cell right before the execution of the HO. In some embodiments, the UE includes for how long it did not receive any RS from the target cell while performing the handover, or from the source cell right before executing the HO. In some embodiment, the UE indicates, via the SHR or SPR, whether the fulfilled triggering condition for the SHR was an LBT-associated triggering condition or not, or whether it was related to missing RSs. The UE may also indicate whether the LBT issue/missing RS issue was detected in the source cell or in the target cell. Reporting of the SHR including the information concerning LBT issues/missing RSs to the network node may be performed according to a solicitation mechanism e.g., according to the UE information Request/Response procedure described in the 3GPP specifications for RRC, 3GPP TS 38.331. In view of the techniques described above, it will be appreciated that Figure 3 illustrates an example method in a wireless device, e.g., a UE operating in an LTE or NR or other wireless network, e.g., where the use of unlicensed spectrum is possible. The illustrated method is intended to be a generalization of the techniques described above and to encompass those techniques. Thus, where terminology used in the description of the method shown in Figure 2 differs somewhat from the examples and illustrations provided above, the terminology used below should be understood as interchangeable with or encompassing the similar terminology used above, except where the context makes it clear otherwise. As shown at block 310, the method shown in Figure 3 includes the step of receiving, from the wireless network, configuration information including or indicating one or more conditions for triggering, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell (PSCell), a recording of information regarding listen-before-talk (LBT) operations performed by the wireless device. As shown at block 320, the method further comprises subsequently determining that at least one of the one or conditions has occurred, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell (PSCell). As shown at block 330, the wireless device, responsive to this determination, records information regarding LBT operations performed by the wireless device in association with the mobility procedure or change or addition of the PSCell. In some embodiments or instances, the configuration information may comprise one or more parameters indicating that the recording of information is to be triggered in response to any one or more of: the wireless device encountering consistent uplink LBT failures in association with the mobility procedure or change or addition of PSCell, according to a predetermined criterion for consistent uplink LBT failures; the wireless device encountering at least N consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where N is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; the wireless device encountering at least M non-consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where M is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; and the wireless device encountering repeated LBT failures for a period of time T, in association with the mobility procedure or change or addition of PSCell, where T is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes. The phrase “in association with,” when referring to mobility procedures or changes/additions of PSCell, means during the procedure or, such as when associated with the source node, in a time period immediately prior to performing the procedure. In some embodiments or instances, at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change. In other embodiments or instances, such as when the mobility procedure is a dual-active protocol stack handover (DAPS HO), at least one of the one or more parameters included in or indicated by the configuration information may relate to LBT failures associated with communications to a source of the DAPS HO. In some embodiments or instances, the method may further comprise sending, to the wireless network, an indication that the wireless device has information for reporting in a Successful Handover Report (SHR) and/or in a Successful PSCell Change/Addition Report. This is shown at block 340, which is illustrated with a dashed line to indicate that it may not appear in all instances of the method. Note also that the indication may be sent to a different network node from the one that sent the configuration information to the wireless device. The method may further comprise, as shown at block 350, the step of receiving, in response to the indication, a request for the SHR and/or SPR. Likewise, the method may further comprise sending the SHR and/or SPR to the wireless network, as shown at block 360. The SHR and/or SPR, in various embodiments, may incude one or more parameters indicating any one or more of: a number of times the wireless device encountered an LBT failure in association with the mobility procedure or change or addition of the PSCell; a duration of time during which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; a ratio or percentage of LBT failures to attempted accesses encountered in association with the mobility procedure or change or addition of the PSCell; a bandwidth part identifier or a random access channel configuration identifier associated to a bandwidth part in which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; and whether an LBT failure was encountered while attempting to transmit a particular one of multiple messages in association with the mobility procedure or change or addition of the PSCell, for each of one or more attempts to perform the mobility procedure or change or add the PSCell. In some embodiments or instances, at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change. In some other embodiments or instances, such as where the mobility procedure is a dual-active protocol stack handover (DAPS HO), at least one of the one or more parameters in the SHR and/or SPR may relate to LBT failures associated with communications to a source of the DAPS HO. Figure 4 illustrates a corresponding method carried out by one or more network nodes, in a wireless network. This method may be implemented in one (or several) network nodes, in various embodiments or instances. As was the case with Figure 3, the method illustrated in Figure 4 is intended to be a generalization of the techniques described above and to encompass those techniques. Thus, where terminology used in the description of the method shown in Figure 4 differs somewhat from the examples and illustrations provided above, the terminology used below should be understood as interchangeable with or encompassing the similar terminology used above, except where the context makes it clear otherwise. As shown at block 410, the method comprises the step of sending, to a wireless device, configuration information including or indicating at least one condition for triggering, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell (PSCell), a recording of information regarding listen-before-talk (LBT) operations performed by the wireless device. As discussed above, the configuration information may comprise one or more parameters indicating that the recording of information is to be triggered in response to any one or more of: the wireless device encountering consistent uplink LBT failures in association with the mobility procedure or change or addition of PSCell, according to a predetermined criterion for consistent uplink LBT failures; the wireless device encountering at least N consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where N is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; the wireless device encountering at least M non-consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where M is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; the wireless device encountering repeated LBT failures for a period of time T, in association with the mobility procedure or change or addition of PSCell, where T is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes. Again, the phrase “in association with,” when referring to mobility procedures or changes/additions of PSCell, means during the procedure or, such as when associated with the source node, in a time period immediately prior to performing the procedure. In some embodiments or instances, for example, at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change. Likewise, in some other embodiments or instances, such as where the mobility procedure is a dual-active protocol stack handover (DAPS HO), at least one of the one or more parameters included in or indicated by the configuration information may relate to LBT failures associated with communications to a source of the DAPS HO. As shown at block 420, the method may further comprise, in some embodiments or instances, receiving, from the wireless device, an indication that the wireless device has information for reporting in a Successful Handover Report (SHR) and/or in a Successful PSCell Change/Addition Report. The one or more network nodes may then send to the wireless device, in response to the indication, a request for the SHR and/or SPR, as shown at block 430, and receive the SHR and/or SPR from the wireless device, as shown at block 440. In various embodiments or instances, the SHR and/or SPR may include one or more parameters indicating any one or more of: a number of times the wireless device encountered an LBT failure in association with the mobility procedure or change or addition of the PSCell; a duration of time during which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; a ratio or percentage of LBT failures to attempted accesses encountered in association with the mobility procedure or change or addition of the PSCell; a bandwidth part identifier or a random access channel configuration identifier associated to a bandwidth part in which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; and whether an LBT failure was encountered while attempting to transmit a particular one of multiple messages in association with the mobility procedure or change or addition of the PSCell, for each of one or more attempts to perform the mobility procedure or change or add the PSCell. In some embodiments or instances, at least one of the one or more parameters in the SHR and/or SPR may relate to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change. In some other embodiments or instances, such as where the mobility procedure is a dual-active protocol stack handover (DAPS HO), at least one of the one or more parameters in the SHR and/or SPR might relate to LBT failures associated with communications to a source of the DAPS HO. Figure 5 shows an example of a communication system 500 in accordance with some embodiments. The techniques detailed above may be carried out in such a communication system. In the example, the communication system 500 includes a telecommunication network 502 that includes an access network 504, such as a radio access network (RAN), and a core network 506, which includes one or more core network nodes 508. The access network 504 includes one or more access network nodes, such as network nodes 510a and 510b (one or more of which may be generally referred to as network nodes 510), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 510 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 512a, 512b, 512c, and 512d (one or more of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 500 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 500 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. The UEs 512 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 510 and other communication devices. Similarly, the network nodes 510 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 512 and/or with other network nodes or equipment in the telecommunication network 502 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 502. In the depicted example, the core network 506 connects the network nodes 510 to one or more hosts, such as host 516. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 506 includes one more core network nodes (e.g., core network node 508) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 508. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF). The host 516 may be under the ownership or control of a service provider other than an operator or provider of the access network 504 and/or the telecommunication network 502, and may be operated by the service provider or on behalf of the service provider. The host 516 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server. As a whole, the communication system 500 of Figure 5 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. In some examples, the telecommunication network 502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 502. For example, the telecommunications network 502 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive IoT services to yet further UEs. In some examples, the UEs 512 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 504. 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. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC). In the example, the hub 514 communicates with the access network 504 to facilitate indirect communication between one or more UEs (e.g., UE 512c and/or 512d) and network nodes (e.g., network node 510b). In some examples, the hub 514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 514 may be a broadband router enabling access to the core network 506 for the UEs. As another example, the hub 514 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 510, or by executable code, script, process, or other instructions in the hub 514. As another example, the hub 514 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 514 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 514 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 514 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices. The hub 514 may have a constant/persistent or intermittent connection to the network node 510b. The hub 514 may also allow for a different communication scheme and/or schedule between the hub 514 and UEs (e.g., UE 512c and/or 512d), and between the hub 514 and the core network 506. In other examples, the hub 514 is connected to the core network 506 and/or one or more UEs via a wired connection. Moreover, the hub 514 may be configured to connect to an M2M service provider over the access network 504 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 510 while still connected via the hub 514 via a wired or wireless connection. In some embodiments, the hub 514 may be a dedicated hub – that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 510b. In other embodiments, the hub 514 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 510b, but which is additionally capable of operating as a communication start and/or end point for certain data channels. Figure 6 shows a UE 600 in accordance with some embodiments. The illustrated UE 600 may be configured, e.g., with the processing circuitry detailed below, to carry out one or several of the techniques described above. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to- vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). The UE 600 includes processing circuitry 602 that is operatively coupled via a bus 604 to an input/output interface 606, a power source 608, a memory 610, a communication interface 612, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 6. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. The processing circuitry 602 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine- readable computer programs in the memory 610. The processing circuitry 602 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 602 may include multiple central processing units (CPUs). In the example, the input/output interface 606 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 600. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. In some embodiments, the power source 608 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 608 may further include power circuitry for delivering power from the power source 608 itself, and/or an external power source, to the various parts of the UE 600 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 608. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 608 to make the power suitable for the respective components of the UE 600 to which power is supplied. The memory 610 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 610 includes one or more application programs 614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 616. The memory 610 may store, for use by the UE 600, any of a variety of various operating systems or combinations of operating systems. The memory 610 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 610 may allow the UE 600 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 610, which may be or comprise a device-readable storage medium. The processing circuitry 602 may be configured to communicate with an access network or other network using the communication interface 612. The communication interface 612 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 622. The communication interface 612 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 618 and/or a receiver 620 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 618 and receiver 620 may be coupled to one or more antennas (e.g., antenna 622) and may share circuit components, software or firmware, or alternatively be implemented separately. In the illustrated embodiment, communication functions of the communication interface 612 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, 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 in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 612, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input. A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 600 shown in Figure 6. As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. Figure 7 shows a network node 700 in accordance with some embodiments. The network node 700 may be configured, e.g., with appropriately configured processing circuitry as described below, to carry out all or portions of the various network-side techniques described above. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self- Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs). The network node 700 includes a processing circuitry 702, a memory 704, a communication interface 706, and a power source 708. The network node 700 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 700 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 700 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 704 for different RATs) and some components may be reused (e.g., a same antenna 710 may be shared by different RATs). The network node 700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 700, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 700. The processing circuitry 702 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 700 components, such as the memory 704, to provide network node 700 functionality. In some embodiments, the processing circuitry 702 includes a system on a chip (SOC). In some embodiments, the processing circuitry 702 includes one or more of radio frequency (RF) transceiver circuitry 712 and baseband processing circuitry 714. In some embodiments, the radio frequency (RF) transceiver circuitry 712 and the baseband processing circuitry 714 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 712 and baseband processing circuitry 714 may be on the same chip or set of chips, boards, or units. The memory 704 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non- transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 702. The memory 704 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 702 and utilized by the network node 700. The memory 704 may be used to store any calculations made by the processing circuitry 702 and/or any data received via the communication interface 706. In some embodiments, the processing circuitry 702 and memory 704 is integrated. The communication interface 706 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 706 comprises port(s)/terminal(s) 716 to send and receive data, for example to and from a network over a wired connection. The communication interface 706 also includes radio front- end circuitry 718 that may be coupled to, or in certain embodiments a part of, the antenna 710. Radio front-end circuitry 718 comprises filters 720 and amplifiers 722. The radio front-end circuitry 718 may be connected to an antenna 710 and processing circuitry 702. The radio front- end circuitry may be configured to condition signals communicated between antenna 710 and processing circuitry 702. The radio front-end circuitry 718 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 718 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 720 and/or amplifiers 722. The radio signal may then be transmitted via the antenna 710. Similarly, when receiving data, the antenna 710 may collect radio signals which are then converted into digital data by the radio front-end circuitry 718. The digital data may be passed to the processing circuitry 702. In other embodiments, the communication interface may comprise different components and/or different combinations of components. In certain alternative embodiments, the network node 700 does not include separate radio front- end circuitry 718, instead, the processing circuitry 702 includes radio front-end circuitry and is connected to the antenna 710. Similarly, in some embodiments, all or some of the RF transceiver circuitry 712 is part of the communication interface 706. In still other embodiments, the communication interface 706 includes one or more ports or terminals 716, the radio front-end circuitry 718, and the RF transceiver circuitry 712, as part of a radio unit (not shown), and the communication interface 706 communicates with the baseband processing circuitry 714, which is part of a digital unit (not shown). The antenna 710 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 710 may be coupled to the radio front-end circuitry 718 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 710 is separate from the network node 700 and connectable to the network node 700 through an interface or port. The antenna 710, communication interface 706, and/or the processing circuitry 702 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 710, the communication interface 706, and/or the processing circuitry 702 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment. The power source 708 provides power to the various components of network node 700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 700 with power for performing the functionality described herein. For example, the network node 700 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 708. As a further example, the power source 708 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail. Embodiments of the network node 700 may include additional components beyond those shown in Figure 7 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 700 may include user interface equipment to allow input of information into the network node 700 and to allow output of information from the network node 700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 700. Figure 8 is a block diagram of a host 800, which may be an embodiment of the host 516 of Figure 5, in accordance with various aspects described herein. As used herein, the host 800 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 800 may provide one or more services to one or more UEs. The host 800 includes processing circuitry 802 that is operatively coupled via a bus 804 to an input/output interface 806, a network interface 808, a power source 810, and a memory 812. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 6 and 7, such that the descriptions thereof are generally applicable to the corresponding components of host 800. The memory 812 may include one or more computer programs including one or more host application programs 814 and data 816, which may include user data, e.g., data generated by a UE for the host 800 or data generated by the host 800 for a UE. Embodiments of the host 800 may utilize only a subset or all of the components shown. The host application programs 814 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 814 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 800 may select and/or indicate a different host for over- the-top services for a UE. The host application programs 814 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc. Figure 9 is a block diagram illustrating a virtualization environment 900 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 900 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. Applications 902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Hardware 904 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 908a and 908b (one or more of which may be generally referred to as VMs 908), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 906 may present a virtual operating platform that appears like networking hardware to the VMs 908. The VMs 908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 906. Different embodiments of the instance of a virtual appliance 902 may be implemented on one or more of VMs 908, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. In the context of NFV, a VM 908 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 908, and that part of hardware 904 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 908 on top of the hardware 904 and corresponds to the application 902. Hardware 904 may be implemented in a standalone network node with generic or specific components. Hardware 904 may implement some functions via virtualization. Alternatively, hardware 904 may be part of a larger cluster of hardware (such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 910, which, among others, oversees lifecycle management of applications 902. In some embodiments, hardware 904 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 912 which may alternatively be used for communication between hardware nodes and radio units. Figure 10 shows a communication diagram of a host 1002 communicating via a network node 1004 with a UE 1006 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 512a of Figure 5 and/or UE 600 of Figure 6), network node (such as network node 510a of Figure 5 and/or network node 700 of Figure 7), and host (such as host 516 of Figure 5 and/or host 800 of Figure 8) discussed in the preceding paragraphs will now be described with reference to Figure 10. Like host 800, embodiments of host 1002 include hardware, such as a communication interface, processing circuitry, and memory. The host 1002 also includes software, which is stored in or accessible by the host 1002 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1006 connecting via an over-the-top (OTT) connection 1050 extending between the UE 1006 and host 1002. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1050. The network node 1004 includes hardware enabling it to communicate with the host 1002 and UE 1006. The connection 1060 may be direct or pass through a core network (like core network 506 of Figure 5) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. The UE 1006 includes hardware and software, which is stored in or accessible by UE 1006 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1006 with the support of the host 1002. In the host 1002, an executing host application may communicate with the executing client application via the OTT connection 1050 terminating at the UE 1006 and host 1002. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1050 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1050. The OTT connection 1050 may extend via a connection 1060 between the host 1002 and the network node 1004 and via a wireless connection 1070 between the network node 1004 and the UE 1006 to provide the connection between the host 1002 and the UE 1006. The connection 1060 and wireless connection 1070, over which the OTT connection 1050 may be provided, have been drawn abstractly to illustrate the communication between the host 1002 and the UE 1006 via the network node 1004, without explicit reference to any intermediary devices and the precise routing of messages via these devices. As an example of transmitting data via the OTT connection 1050, in step 1008, the host 1002 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1006. In other embodiments, the user data is associated with a UE 1006 that shares data with the host 1002 without explicit human interaction. In step 1010, the host 1002 initiates a transmission carrying the user data towards the UE 1006. The host 1002 may initiate the transmission responsive to a request transmitted by the UE 1006. The request may be caused by human interaction with the UE 1006 or by operation of the client application executing on the UE 1006. The transmission may pass via the network node 1004, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1012, the network node 1004 transmits to the UE 1006 the user data that was carried in the transmission that the host 1002 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1014, the UE 1006 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1006 associated with the host application executed by the host 1002. In some examples, the UE 1006 executes a client application which provides user data to the host 1002. The user data may be provided in reaction or response to the data received from the host 1002. Accordingly, in step 1016, the UE 1006 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 1006. Regardless of the specific manner in which the user data was provided, the UE 1006 initiates, in step 1018, transmission of the user data towards the host 1002 via the network node 1004. In step 1020, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1004 receives user data from the UE 1006 and initiates transmission of the received user data towards the host 1002. In step 1022, the host 1002 receives the user data carried in the transmission initiated by the UE 1006. One or more of the various embodiments improve the performance of OTT services provided to the UE 1006 using the OTT connection 1050, in which the wireless connection 1070 forms the last segment. More precisely, the teachings of these embodiments may improve network performance and in particular reduce the number of handover failures and/or improve the ability of the wireless device to recover from such handover failures and thereby provide benefits such as improved reliability and data throughput. In an example scenario, factory status information may be collected and analyzed by the host 1002. As another example, the host 1002 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1002 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1002 may store surveillance video uploaded by a UE. As another example, the host 1002 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1002 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data. In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1050 between the host 1002 and UE 1006, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1002 and/or UE 1006. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1050 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1050 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1004. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1002. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1050 while monitoring propagation times, errors, etc. Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device- readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally. EXAMPLE EMBODIMENTS Embodiments of the techniques, apparatuses, and systems described herein include, but are not limited to, the following enumerated examples: 1. A method, performed by one or more network nodes, the method comprising: sending, to a wireless device, configuration information including or indicating at least one condition for triggering, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell (PSCell), a recording of information regarding listen-before-talk (LBT) operations performed by the wireless device. 2. The method of example embodiment 1, wherein the configuration information comprises one or more parameters indicating that the recording of information is to be triggered in response to any one or more of: the wireless device encountering consistent uplink LBT failures in association with the mobility procedure or change or addition of PSCell, according to a predetermined criterion for consistent uplink LBT failures; the wireless device encountering at least N consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where N is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; the wireless device encountering at least M non-consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where M is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; the wireless device encountering repeated LBT failures for a period of time T, in association with the mobility procedure or change or addition of PSCell, where T is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes. 3. The method of example embodiment 2, wherein at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change. 4. The method of example embodiment 2, wherein the mobility procedure is a dual-active protocol stack handover (DAPS HO) and at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a source of the DAPS HO. 5. The method of any one of example embodiments 1-4, further comprising: receiving, from the wireless device, an indication that the wireless device has information for reporting in a Successful Handover Report (SHR) and/or in a Successful PSCell Change/Addition Report; sending to the wireless device, in response to the indication, a request for the SHR and/or SPR; and receiving, from the wireless device, the SHR and/or SPR. 6. The method of example embodiment 5, wherein the SHR and/or SPR includes one or more parameters indicating any one or more of: a number of times the wireless device encountered an LBT failure in association with the mobility procedure or change or addition of the PSCell; a duration of time during which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; a ratio or percentage of LBT failures to attempted accesses encountered in association with the mobility procedure or change or addition of the PSCell; a bandwidth part identifier or a random access channel configuration identifier associated to a bandwidth part in which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; and whether an LBT failure was encountered while attempting to transmit a particular one of multiple messages in association with the mobility procedure or change or addition of the PSCell, for each of one or more attempts to perform the mobility procedure or change or add the PSCell. 7. The method of example embodiment 6, wherein at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change. 8. The method of example embodiment 6, wherein the mobility procedure is a dual-active protocol stack handover (DAPS HO) and at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a source of the DAPS HO. 9. A method, performed by a wireless device operating in a wireless device, the method comprising: receiving, from the wireless network, configuration information including or indicating one or more conditions for triggering, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell (PSCell), a recording of information regarding listen-before-talk (LBT) operations performed by the wireless device; subsequently determining that at least one of the one or conditions has occurred, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell (PSCell); and responsive to said determining, recording information regarding LBT operations performed by the wireless device in association with the mobility procedure or change or addition of the PSCell. 10. The method of example embodiment 9, wherein the configuration information comprises one or more parameters indicating that the recording of information is to be triggered in response to any one or more of: the wireless device encountering consistent uplink LBT failures in association with the mobility procedure or change or addition of PSCell, according to a predetermined criterion for consistent uplink LBT failures; the wireless device encountering at least N consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where N is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; the wireless device encountering at least M non-consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where M is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; the wireless device encountering repeated LBT failures for a period of time T, in association with the mobility procedure or change or addition of PSCell, where T is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes. 11. The method of example embodiment 10, wherein at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change. 12. The method of example embodiment 10, wherein the mobility procedure is a dual-active protocol stack handover (DAPS HO) and at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a source of the DAPS HO. 13. The method of any one of example embodiments 9-12, further comprising: sending, to the wireless network, an indication that the wireless device has information for reporting in a Successful Handover Report (SHR) and/or in a Successful PSCell Change/Addition Report; receiving, in response to the indication, a request for the SHR and/or SPR; and sending, to the wireless network, the SHR and/or SPR. 14. The method of example embodiment 13, wherein the SHR and/or SPR includes one or more parameters indicating any one or more of: a number of times the wireless device encountered an LBT failure in association with the mobility procedure or change or addition of the PSCell; a duration of time during which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; a ratio or percentage of LBT failures to attempted accesses encountered in association with the mobility procedure or change or addition of the PSCell; a bandwidth part identifier or a random access channel configuration identifier associated to a bandwidth part in which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; and whether an LBT failure was encountered while attempting to transmit a particular one of multiple messages in association with the mobility procedure or change or addition of the PSCell, for each of one or more attempts to perform the mobility procedure or change or add the PSCell. 15. The method of example embodiment 14, wherein at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change. 16. The method of example embodiment 14, wherein the mobility procedure is a dual-active protocol stack handover (DAPS HO) and at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a source of the DAPS HO. 17. A network node, comprising: radio circuitry configured to communicate with one or more wireless devices; and processing circuitry operatively coupled to the radio circuitry and configured to use the radio circuitry to: send, to a wireless device, configuration information including or indicating at least one condition for triggering, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell (PSCell), a recording of information regarding listen-before-talk (LBT) operations performed by the wireless device. 18. The network node of example embodiment 17, wherein the configuration information comprises one or more parameters indicating that the recording of information is to be triggered in response to any one or more of: the wireless device encountering consistent uplink LBT failures in association with the mobility procedure or change or addition of PSCell, according to a predetermined criterion for consistent uplink LBT failures; the wireless device encountering at least N consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where N is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; the wireless device encountering at least M non-consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where M is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; and the wireless device encountering repeated LBT failures for a period of time T, in association with the mobility procedure or change or addition of PSCell, where T is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes. 19. The network node of example embodiment 18, wherein at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change. 20. The network node of example embodiment 18, wherein the mobility procedure is a dual-active protocol stack handover (DAPS HO) and at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a source of the DAPS HO. 21. The network node of any one of example embodiments 17-20, wherein the processing circuitry is further configured to use the radio circuitry to: receive, from the wireless device, an indication that the wireless device has information for reporting in a Successful Handover Report (SHR) and/or in a Successful PSCell Change/Addition Report; send to the wireless device, in response to the indication, a request for the SHR and/or SPR; and receive, from the wireless device, the SHR and/or SPR. 22. The network node of example embodiment 21, wherein the SHR and/or SPR includes one or more parameters indicating any one or more of: a number of times the wireless device encountered an LBT failure in association with the mobility procedure or change or addition of the PSCell; a duration of time during which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; a ratio or percentage of LBT failures to attempted accesses encountered in association with the mobility procedure or change or addition of the PSCell; a bandwidth part identifier or a random access channel configuration identifier associated to a bandwidth part in which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; and whether an LBT failure was encountered while attempting to transmit a particular one of multiple messages in association with the mobility procedure or change or addition of the PSCell, for each of one or more attempts to perform the mobility procedure or change or add the PSCell. 23. The network node of example embodiment 22, wherein at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change. 24. The network node of example embodiment 22, wherein the mobility procedure is a dual-active protocol stack handover (DAPS HO) and at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a source of the DAPS HO. 25. A wireless device, comprising: radio circuitry configured to communicate with a wireless network; and processing circuitry operatively coupled to the radio circuitry and configured to: receive, from the wireless network, via the radio circuitry, configuration information including or indicating one or more conditions for triggering, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell (PSCell), a recording of information regarding listen-before-talk (LBT) operations performed by the wireless device; subsequently determine that at least one of the one or conditions has occurred, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell (PSCell); and responsive to said determining, record information regarding LBT operations performed by the wireless device in association with the mobility procedure or change or addition of the PSCell. 26. The wireless device of example embodiment 25, wherein the configuration information comprises one or more parameters indicating that the recording of information is to be triggered in response to any one or more of: the wireless device encountering consistent uplink LBT failures in association with the mobility procedure or change or addition of PSCell, according to a predetermined criterion for consistent uplink LBT failures; the wireless device encountering at least N consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where N is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; the wireless device encountering at least M non-consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where M is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; and the wireless device encountering repeated LBT failures for a period of time T, in association with the mobility procedure or change or addition of PSCell, where T is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes. 27. The wireless device of example embodiment 26, wherein at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change. 28. The wireless device of example embodiment 26, wherein the mobility procedure is a dual-active protocol stack handover (DAPS HO) and at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a source of the DAPS HO. 29. The wireless device of any one of example embodiments 25-28, further comprising: sending, to the wireless network, an indication that the wireless device has information for reporting in a Successful Handover Report (SHR) and/or in a Successful PSCell Change/Addition Report; receiving, in response to the indication, a request for the SHR and/or SPR; and sending, to the wireless network, the SHR and/or SPR. 30. The wireless device of example embodiment 29, wherein the SHR and/or SPR includes one or more parameters indicating any one or more of: a number of times the wireless device encountered an LBT failure in association with the mobility procedure or change or addition of the PSCell; a duration of time during which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; a ratio or percentage of LBT failures to attempted accesses encountered in association with the mobility procedure or change or addition of the PSCell; a bandwidth part identifier or a random access channel configuration identifier associated to a bandwidth part in which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; and whether an LBT failure was encountered while attempting to transmit a particular one of multiple messages in association with the mobility procedure or change or addition of the PSCell, for each of one or more attempts to perform the mobility procedure or change or add the PSCell. 31. The wireless device of example embodiment 30, wherein at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change. 32. The wireless device of example embodiment 30, wherein the mobility procedure is a dual-active protocol stack handover (DAPS HO) and at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a source of the DAPS HO. 33. A wireless device adapted to carry out a method according to any of example embodiments 9- 16. 34. A network node adapted to carry out a method according to any of example embodiments 1-8. 35. A computer program product comprising computer program instructions for execution on a processor, the computer program instructions being configured to cause the processor to carry out a method according to any of example embodiments 1-16. 36. A computer-readable medium comprising the computer program product of example embodiment 35. ABBREVIATIONS Abbreviation Explanation ANR Automatic Neighbour Relation BWP Bandwith Part C-RNTI Cell-Radio Network Temporary Identifier CHO Conditional Handover CIO Cell Individual Offset DAPS Dual Active Protocol Stack DL Downlink DRB Data Radio Bearer eNB evolved NodeB gNB gNodeB HO Handover HOF Handover Failure IE Information Element LBT Listen-Before-Talk LTE Long Term Evolution MHI Mobility History Report MCG Master Cell Group MRO Mobility Robustness Optimization NGMN Next Generation Mobile Networks NR New Radio PCell Primary cell PCI Physical Cell ID QCI Quality of Service Class Identifier RA Random Access RACH Random Access CHannel RAN Radio Access Network RAT Radio Access Technology RF Radio Frequency RLF Radio Link Failure RRC Radio Resource Control RS Reference Signal RSRP Reference Signal Received Power RSRQ Reference Signal Received Quality RSSI Received Signal Strength Indicator SHR Successful Handover Report SON Self-Organizing Network SPR Successful PSCell change/addition report UE User Equipment UL Uplink

Claims

CLAIMS What is claimed is: 1. A method, performed by one or more network nodes, the method comprising: sending (410), to a wireless device, configuration information including or indicating at least one condition for triggering, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell, PSCell, a recording of information regarding listen-before-talk, LBT, operations performed by the wireless device. 2. The method of claim 1, wherein the configuration information comprises one or more parameters indicating that the recording of information is to be triggered in response to any one or more of: the wireless device encountering consistent uplink LBT failures in association with the mobility procedure or change or addition of PSCell, according to a predetermined criterion for consistent uplink LBT failures; the wireless device encountering at least N consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where N is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; the wireless device encountering at least M non-consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where M is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; the wireless device encountering repeated LBT failures for a period of time T, in association with the mobility procedure or change or addition of PSCell, where T is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes. 3. The method of claim 2, wherein at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change. 4. The method of claim 2, wherein at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a source cell of the mobility procedure, encountered before the execution of the mobility procedure. 5. The method of claim 2, wherein the mobility procedure is a dual-active protocol stack handover (DAPS HO) and at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a source of the DAPS HO. 6. The method of any one of claims 1-5, further comprising: receiving (420), from the wireless device, an indication that the wireless device has information for reporting in a Successful Handover Report, SHR, and/or in a Successful PSCell Change/Addition Report, SPR; sending (430) to the wireless device, in response to the indication, a request for the SHR and/or SPR; and receiving (440), from the wireless device, the SHR and/or SPR. 7. The method of any one of claims 1-6, wherein the method comprises receiving, from the wireless device, a Successful Handover Report, SHR, and/or in a Successful PSCell Change/Addition Report, SPR, and wherein the SHR and/or SPR includes one or more parameters indicating any one or more of: a number of times the wireless device encountered an LBT failure in association with the mobility procedure or change or addition of the PSCell; an indication of whether consistent LBT failure was declared in association with the mobility procedure or change or addition of the PsCell; a duration of time during which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; a ratio or percentage of LBT failures to attempted accesses encountered in association with the mobility procedure or change or addition of the PSCell; a bandwidth part identifier or a random access channel configuration identifier associated to a bandwidth part in which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; and whether an LBT failure was encountered while attempting to transmit a particular one of multiple messages in association with the mobility procedure or change or addition of the PSCell, for each of one or more attempts to perform the mobility procedure or change or add the PSCell. 8. The method of claim 7, wherein at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change or relates to LBT failures associated with communications to a source cell of the mobility procedure, encountered before the execution of the mobility procedure. 9. The method of claim 7, wherein the mobility procedure is a dual-active protocol stack handover (DAPS HO) and at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a source of the DAPS HO. 10. A method, performed by a wireless device operating in a wireless device, the method comprising: receiving (310), from the wireless network, configuration information including or indicating one or more conditions for triggering, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell, PSCell, a recording of information regarding listen-before-talk, LBT, operations performed by the wireless device; subsequently determining (320) that at least one of the one or conditions has occurred, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell, PSCell; and responsive to said determining, recording (330) information regarding LBT operations performed by the wireless device in association with the mobility procedure or change or addition of the PSCell. 11. The method of claim 10, wherein the configuration information comprises one or more parameters indicating that the recording of information is to be triggered in response to any one or more of: the wireless device encountering consistent uplink LBT failures in association with the mobility procedure or change or addition of PSCell, according to a predetermined criterion for consistent uplink LBT failures; the wireless device encountering at least N consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where N is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; the wireless device encountering at least M non-consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where M is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; the wireless device encountering repeated LBT failures for a period of time T, in association with the mobility procedure or change or addition of PSCell, where T is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes. 12. The method of claim 11, wherein at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change. 13. The method of claim 11, wherein at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a source cell of the mobility procedure, encountered before the execution of the mobility procedure. 14. The method of claim 11, wherein the mobility procedure is a dual-active protocol stack handover, DAPS HO, and at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a source of the DAPS HO. 15. The method of any one of claims 10-14, further comprising: sending (340), to the wireless network, an indication that the wireless device has information for reporting in a Successful Handover Report, SHR, and/or in a Successful PSCell Change/Addition Report; receiving (350), in response to the indication, a request for the SHR and/or SPR; and sending (360), to the wireless network, the SHR and/or SPR. 16. The method of any one of claims 10-15, wherein the method comprises sending, to the wireless network, a Successful Handover Report, SHR, and/or a Successful PSCell Change/Addition Report, SPR, and the SHR and/or SPR includes one or more parameters indicating any one or more of: a number of times the wireless device encountered an LBT failure in association with the mobility procedure or change or addition of the PSCell; an indication of whether consistent LBT failure was declared in association with the mobility procedure or change or addition of the PsCell; a duration of time during which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; a ratio or percentage of LBT failures to attempted accesses encountered in association with the mobility procedure or change or addition of the PSCell; a bandwidth part identifier or a random access channel configuration identifier associated to a bandwidth part in which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; and whether an LBT failure was encountered while attempting to transmit a particular one of multiple messages in association with the mobility procedure or change or addition of the PSCell, for each of one or more attempts to perform the mobility procedure or change or add the PSCell. 17. The method of claim 16, wherein at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change or relates to LBT failures associated with communications to a source cell of the mobility procedure, encountered before the execution of the mobility procedure. 18. The method of claim 16, wherein the mobility procedure is a dual-active protocol stack handover, DAPS HO, and at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a source of the DAPS HO. 19. A network node (700), comprising: radio circuitry (718) configured to communicate with one or more wireless devices; and processing circuitry (702) operatively coupled to the radio circuitry and configured to use the radio circuitry to: send, to a wireless device, configuration information including or indicating at least one condition for triggering, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell, PSCell, a recording of information regarding listen-before-talk, LBT, operations performed by the wireless device. 20. The network node (700) of claim 19, wherein the configuration information comprises one or more parameters indicating that the recording of information is to be triggered in response to any one or more of: the wireless device encountering consistent uplink LBT failures in association with the mobility procedure or change or addition of PSCell, according to a predetermined criterion for consistent uplink LBT failures; the wireless device encountering at least N consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where N is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; the wireless device encountering at least M non-consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where M is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; and the wireless device encountering repeated LBT failures for a period of time T, in association with the mobility procedure or change or addition of PSCell, where T is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes. 21. The network node (700) of claim 20, wherein at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change. 22. The network node (700) of claim 20, wherein at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a source cell of the mobility procedure, encountered before the execution of the mobility procedure. 23. The network node (700) of claim 20, wherein the mobility procedure is a dual-active protocol stack handover, DAPS HO, and at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a source of the DAPS HO. 24. The network node (700) of any one of claims 19-23, wherein the processing circuitry (702) is further configured to use the radio circuitry (718) to: receive, from the wireless device, an indication that the wireless device has information for reporting in a Successful Handover Report, SHR, and/or in a Successful PSCell Change/Addition Report; send to the wireless device, in response to the indication, a request for the SHR and/or SPR; and receive, from the wireless device, the SHR and/or SPR. 25. The network node (700) of any one of claims 19-24, wherein the processing circuitry (702) is further configured to use the radio circuitry (718) to receive a Successful Handover Report, SHR, and/or a Successful PSCell Change/Addition Report, SPR, and wherein the SHR and/or SPR includes one or more parameters indicating any one or more of: a number of times the wireless device encountered an LBT failure in association with the mobility procedure or change or addition of the PSCell; an indication of whether consistent LBT failure was declared in association with the mobility procedure or change or addition of the PsCell; a duration of time during which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; a ratio or percentage of LBT failures to attempted accesses encountered in association with the mobility procedure or change or addition of the PSCell; a bandwidth part identifier or a random access channel configuration identifier associated to a bandwidth part in which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; and whether an LBT failure was encountered while attempting to transmit a particular one of multiple messages in association with the mobility procedure or change or addition of the PSCell, for each of one or more attempts to perform the mobility procedure or change or add the PSCell. 26. The network node (700) of claim 25, wherein at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change or relates to LBT failures associated with communications to a source cell of the mobility procedure, encountered before the execution of the mobility procedure. 27. The network node (700) of claim 25, wherein the mobility procedure is a dual-active protocol stack handover, DAPS HO, and at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a source of the DAPS HO. 28. A wireless device (600), comprising: radio circuitry (612) configured to communicate with a wireless network; and processing circuitry (602) operatively coupled to the radio circuitry and configured to: receive, from the wireless network, via the radio circuitry, configuration information including or indicating one or more conditions for triggering, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell (PSCell), a recording of information regarding listen-before-talk, LBT, operations performed by the wireless device; subsequently determine that at least one of the one or conditions has occurred, in connection with a successful mobility procedure or successful change or addition of a primary secondary cell, PSCell; and responsive to said determining, record information regarding LBT operations performed by the wireless device in association with the mobility procedure or change or addition of the PSCell. 29. The wireless device (600) of claim 28, wherein the configuration information comprises one or more parameters indicating that the recording of information is to be triggered in response to any one or more of: the wireless device encountering consistent uplink LBT failures in association with the mobility procedure or change or addition of PSCell, according to a predetermined criterion for consistent uplink LBT failures; the wireless device encountering at least N consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where N is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; the wireless device encountering at least M non-consecutive LBT failures in association with the mobility procedure or change or addition of PSCell, where M is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes; and the wireless device encountering repeated LBT failures for a period of time T, in association with the mobility procedure or change or addition of PSCell, where T is predefined or is indicated by a parameter configured for the wireless device by the one or more network nodes. 30. The wireless device (600) of claim 29, wherein at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change. 31. The wireless device (600) of claim 29, wherein at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a source cell of the mobility procedure, encountered before the execution of the mobility procedure. 32. The wireless device (600) of claim 29, wherein the mobility procedure is a dual-active protocol stack handover, DAPS HO, and at least one of the one or more parameters included in or indicated by the configuration information relates to LBT failures associated with communications to a source of the DAPS HO. 33. The wireless device (600) of any one of claims 28-32, wherein the processing circuitry (602) is further configured to use the radio circuitry (612): send, to the wireless network, an indication that the wireless device has information for reporting in a Successful Handover Report, SHR, and/or in a Successful PSCell Change/Addition Report; receive, in response to the indication, a request for the SHR and/or SPR; and send, to the wireless network, the SHR and/or SPR. 34. The wireless device (600) of any one of claims 28-33, wherein the processing circuitry (602) is configured to use the radio circuitry (612) to send, to the wireless network, a Successful Handover Report, SHR, and/or a Successful PSCell Change/Addition Report, SPR, and wherein the SHR and/or SPR includes one or more parameters indicating any one or more of: a number of times the wireless device encountered an LBT failure in association with the mobility procedure or change or addition of the PSCell; a duration of time during which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; a ratio or percentage of LBT failures to attempted accesses encountered in association with the mobility procedure or change or addition of the PSCell; a bandwidth part identifier or a random access channel configuration identifier associated to a bandwidth part in which the wireless device encountered LBT failures in association with the mobility procedure or change or addition of the PSCell; and whether an LBT failure was encountered while attempting to transmit a particular one of multiple messages in association with the mobility procedure or change or addition of the PSCell, for each of one or more attempts to perform the mobility procedure or change or add the PSCell. 35. The wireless device (600) of claim 34, wherein at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a target of the mobility procedure or target of the PSCell addition or change or relates to LBT failures associated with communications to a source cell of the mobility procedure, encountered before the execution of the mobility procedure. 36. The wireless device (600) of claim 34, wherein the mobility procedure is a dual-active protocol stack handover, DAPS HO, and at least one of the one or more parameters in the SHR and/or SPR relates to LBT failures associated with communications to a source of the DAPS HO. 37. A wireless device adapted to carry out a method according to any of claims 10-18. 38. A network node adapted to carry out a method according to any of claims 1-9. 39. A computer program product comprising computer program instructions for execution on a processor, the computer program instructions being configured to cause the processor to carry out a method according to any of claims 1-18. 40. A computer-readable medium comprising the computer program product of claim 39.