[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2024096801A1 - Indicating lbt results in failure report - Google Patents

Indicating lbt results in failure report Download PDF

Info

Publication number
WO2024096801A1
WO2024096801A1 PCT/SE2023/051107 SE2023051107W WO2024096801A1 WO 2024096801 A1 WO2024096801 A1 WO 2024096801A1 SE 2023051107 W SE2023051107 W SE 2023051107W WO 2024096801 A1 WO2024096801 A1 WO 2024096801A1
Authority
WO
WIPO (PCT)
Prior art keywords
random access
wireless device
bwp
failure
procedure
Prior art date
Application number
PCT/SE2023/051107
Other languages
French (fr)
Inventor
Ali PARICHEHREHTEROUJENI
Marco BELLESCHI
Mattias BERGSTRÖM
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2024096801A1 publication Critical patent/WO2024096801A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present disclosure generally relates to communication networks, and more specifically to indicating listen-before-talk (LBT) results in a failure report.
  • LBT listen-before-talk
  • BACKGROUND [0002] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise.
  • a self-organizing network 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 (Third Generation Partnership Project) and the NGMN (Next Generation Mobile Networks).
  • 3GPP Third Generation Partnership Project
  • NGMN Next Generation Mobile Networks
  • Self-configuration process is the process where newly deployed nodes are configured by automatic installation procedures to get the necessary basic configuration for system operation.
  • This process works in pre-operational state. Pre-operational state is the state from when the eNB is powered up and has network backbone connectivity until the radio frequency (RF) transmitter is switched on.
  • RF radio frequency
  • Self-optimization process is defined as the process where UE and access node measurements and performance measurements are used to auto-tune the network. [0008] This process works in operational state. Operational state is understood as the state where the RF interface is additionally switched on. [0009]
  • Figure 1 is a flow diagram illustrating self-configuration/self-optimization functionality. Figure 1 is reproduced from 3GPP TS 36.300 Figure 22.1-1. As described in Figure 1, functions handled in the operational state, like optimization/adaptation, are covered by the self-optimization process.
  • LTE Long Term Evolution
  • ANR automatic neighbor relation
  • MRO mobility robustness optimization
  • RACH random access channel
  • MRO mobility robustness optimization
  • MRO mobility robustness optimization
  • Successful handovers ensure that the user equipment (UE) moves around in the coverage area of different cells without causing too many interruptions in the data transmission.
  • the network fails to handover the UE to the correct neighbor cell in time and in such scenarios the UE will declare a radio link failure (RLF) or handover failure (HOF).
  • RLF radio link failure
  • HAF handover failure
  • the UE may take autonomous actions, e.g., trying to select a cell and initiate reestablishment procedure so that the UE is trying to get back as soon as it can, so that it can be reachable again.
  • the RLF causes a poor user experience because the RLF is declared by the UE only when the UE 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, Radio Resource Control (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.
  • RRC Radio Resource Control
  • the possible causes for the radio link failure may be one of the following: expiry of the radio link monitoring related timer T310; 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); upon reaching the maximum number of radio link control (RLC) retransmissions; and upon receiving random access problem indication from the medium access control (MAC) entity.
  • RLC radio link control
  • MAC medium access control
  • the RLF reporting procedure was introduced in the RRC specification in Rel-9. That has 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 that the UE succeeds to connect with (e.g., after reestablishment).
  • the measurements included in the measurement report include: ⁇ Measurement quantities (reference signal receive power (RSRP), reference signal receive quality (RSRQ)) of the last serving cell (PCell). ⁇ Measurement quantities of the neighbor cells in different frequencies of different radio access technologies (RATs) (EUTRA, UTRA, GERAN, CDMA2000).
  • RATs radio access technologies
  • Measurement quantity (received signal strength indication (RSSI)) associated to wireless local area network (WLAN) access points.
  • Measurement quantity (RSSI) associated to Bluetooth beacons.
  • Location information if available (including location coordinates and velocity).
  • PCI physical cell identifier
  • PCI physical cell identifier
  • Tracking area code of the PCell ⁇ Time elapsed since the last reception of the ‘Handover command’ message.
  • C-RNTI Cell radio network temporary identifier used in the previous serving cell. ⁇ Whether or not the UE was configured with a data radio bearer (DRB) having a quality of service class indicator (QCI) value of 1.
  • DRB data radio bearer
  • QCI quality of service class indicator
  • the RLF report is logged and included in the VarRLF-Report and, after the UE selects a cell and succeeds with a reestablishment, the UE includes an indication that the UE has an RLF report available in the RRC Reestablishment Complete message to alert the target cell of the availability. Then, upon receiving a UEInformationRequest message with a flag “rlf-ReportReq-r9,” the UE shall include the RLF report (stored in a UE variable VarRLF- Report, as described above) in a UEInformationResponse message sent to the network.
  • the original source cell can deduce whether the RLF was caused due to a coverage hole or due to handover associated parameter configurations. If the RLF is 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. [0020] In some cases, the handover failure occurred due to the ‘too-late handover’ cases.
  • 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 the target cell post RLF.
  • An example corrective action from the original serving cell could be to initiate the handover procedure towards the target cell a bit earlier by decreasing the CIO (cell individual offset) towards the target cell that controls when the UE sends the event triggered measurement report that leads to taking the handover decision.
  • the handover failure occurred due to the ‘too-early handover’ cases.
  • 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.
  • 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 towards the target cell that controls when the UE sends the event triggered measurement report that leads to taking the handover decision.
  • the handover failure occurred due to the ‘handover-to-wrong-cell’ cases.
  • 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 the UE towards a particular target cell but the UE declares the RLF and reestablishes itself in a third cell.
  • a corrective action from the original serving cell could be to initiate the measurement reporting procedure that leads to handover towards the target cell a bit later by decreasing the CIO 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 introduced the successful handover report (SHR).
  • the UE uses the SHR to report various information associated to successful handover.
  • the successful handover will not be reported always at every handover, but only when certain triggering conditions are fulfilled. For example, if while doing handover, the T310/T312/T304 timers exceed a certain threshold, then the UE shall store information associated to the handover. Similarly, if the handover was a dual active protocol stack (DAPS) handover, and the UE succeeded with the handover but an RLF was experienced in the source cell while doing the DAPS handover, then the UE stores information associated to the DAPS handover.
  • DAPS dual active protocol stack
  • the UE may include various information to aid the network to optimize the handover, such as measurements of the neighboring cells, the fulfilled condition that triggered the successful handover report (e.g. threshold on T310 exceeded, specific RLF issue in the source while doing DAPS handover), etc.
  • the SHR may be configured by a certain serving cell, and when triggering conditions for SHR logging are fulfilled, the UE stores the information until the network requests the information.
  • the UE may indicate availability of SHR information in certain RRC message, such as RRCReconfigurationComplete, RRCReestablishmentComplete, RRCSetupComplete, RRCResumeComplete, and the network may request such information via the UEInformationRequest message, upon which the UE transmits the stored SHR in the UEInformationResponse message.
  • RRCReconfigurationComplete a RRCReconfigurationComplete
  • RRCReestablishmentComplete RRCSetupComplete
  • RRCResumeComplete RRCResumeComplete
  • Both the RLF-Report and the SHR may include information associated to the random access (RA) procedure.
  • the RLF may be in fact due to random access problems, therefore by including the random access information, the network may optimize the random access procedure and possibly minimize the risk for RLF in future.
  • the SHR may also include RA information when the SHR is generated due to problems experienced during the handover, e.g. value of T304 reaching a value above a certain threshold.
  • the RA information includes information related to the bandwidth part (BWP) in which the random access was attempted, information about the downlink pathloss experienced at the time of initiating the random access procedure, information related to each preamble transmission attempt, e.g. whether a contention was experienced or not, the number of preamble transmission attempts in a certain synchronization signal block (SSB) or channel state information reference signal (CSI-RS).
  • BWP bandwidth part
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • the channel access procedure in NR unlicensed spectrum includes listen-before-talk (LBT).
  • a radio device applies a clear channel assessment (CCA) check (e.g., channel sensing) before transmission.
  • CCA clear channel assessment
  • the transmitter involves energy detection (ED) over a time period compared to a certain threshold (ED threshold) to determine if a channel is idle. If the channel is determined to be occupied, the transmitter performs a random back-off within a contention window before the next CCA attempt.
  • ACK acknowledgement
  • the transmitter must defer a period after each busy CCA slot prior to resuming back-off.
  • the transmitter After 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)).
  • a channel access priority based on the service type has been defined. For example, 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 physical random access channel (PRACH), physical uplink control channel (PUCCH), or RRC signal.
  • PRACH physical random access channel
  • PUCCH physical uplink control channel
  • RRC signal Radio Resource Control
  • the random access messages (including the PRACH) are subject to LBT before being transmitted.
  • NR- U specifies an LBT counter that is stepped whenever an uplink transmission fails in a certain BWP. When such LBT counter reaches a maximum value, within a certain time, the UE declares “consistent LBT failure” for the corresponding BWP. If the affected BWP is in the PCell or the PSCell, the UE deactivates the affected BWP and activates another already configured BWP in the PCell/PSCell and transmits random access therein.
  • the UE stops transmitting in this SCell, and can send a scheduling request (SR) on another serving cell (not yet affected by “consistent uplink LBT failures”) for further communications. Additionally, as a result of the consistent LBT failure, the UE issues a MAC control element (CE) to indicate to the network which are the problematic cells in which “consistent LBT failures” were experienced.
  • SR scheduling request
  • CE MAC control element
  • the UE declares SCG failure when consistent uplink LBT failures have been experienced in all the BWPs of the PSCell.
  • the conditional inclusion of the random access information e.g., ra-InformationCommon
  • the solution is specified as follows: 1>if connectionFailureType is rlf and the rlf-Cause is set to randomAccessProblem or beamFailureRecoveryFailure or lbtFailure; or 1>if connectionFailureType is hof and if the failed handover is an intra-RAT handover: 2> if consistent UL LBT failures were triggered and not cancelled at the time of the radio link failure or failed handover; or: 2> if the number of LBT failures experienced in the PCell at the time of the radio link failure
  • the method is applicable to the RLFs occurring without applying/executing a reconfiguration with synchronization mechanism.
  • the UE executes/performs a reconfiguration with synchronization it performs random access procedure, and thus the UE may log the random access related information in the RLF report for any reconfiguration with synchronization failure (such as a handover failure or PSCell change failure).
  • the same method including the random access related information in the RLF report
  • RLF due to consistent LBT failure
  • some embodiments include a method performed in an unlicensed spectrum (e.g., New Radio unlicensed (NR-U)) by a wireless terminal (e.g., user equipment (UE)) after declaring a radio link failure (RLF) on a master cell group (MCG) or a secondary cell group (SCG).
  • the method comprises, upon detection of a radio link failure on MCG or SCG, determining whether a consistent LBT failure occurred in a bandwidth part (BWP) used by the UE and that the LBT recovery configuration is configured by the network for a BWP configured with the random-access resources.
  • BWP bandwidth part
  • the method further comprises, in response to determining that a consistent LBT failure occurred in a BWP and the LBT recovery configuration was configured for a BWP configured with random access resources, including the random-access related information in a report logged by the UE.
  • the method further comprises sending the report including the random access related information to the network either immediately or based on a request received from the network node.
  • a method performed by a wireless device operating in shared spectrum comprises: detecting a radio link failure; determining a consistent LBT failure occurred in a BWP used by the wireless device and that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources; logging random access information in a failure report; and transmitting the failure report to a network node.
  • the random access information comprises random access information associated to a last random access procedure executed as part of a random access recovery procedure, random access information associated to a first random access procedure executed as part of a random access recovery procedure, a number of performed random access procedures as part of a beam failure recovery procedure, BWP identity information associated to a BWP toward which a random access procedure was performed, and/or frequency or bandwidth information of a BWP toward which a random access procedure was performed.
  • the method further comprises receiving a request from the network node to transmit the failure report to the network node.
  • determining a LBT problem occurred in the BWP comprises determining the rlf-cause is set to lbtFailure and determining that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources comprises determining lbt-failureRecoveryConfig was configured for the BWP in which a random access procedure was performed.
  • determining that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources comprises determining the wireless device performed a random access procedure to recover from an LBT failure.
  • a wireless device comprises processing circuitry operable to perform any of the wireless device methods described above.
  • a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless device described above.
  • a method performed by a network node comprises: configuring a wireless device for logging random access information associated with a consistent LBT failure for a BWP used by the wireless device and configured with random access resources; configuring the wireless device to perform LBT recovery based on a random access procedure for the BWP configured with random access resources; and receiving a failure report comprising random access information associated with LBT problems from the wireless device.
  • the method further comprises transmitting a request to the wireless device for the wireless device to transmit the failure report.
  • the random access information comprises random access information associated to a last random access procedure executed as part of a random access recovery procedure, random access information associated to a first random access procedure executed as part of a random access recovery procedure, a number of performed random access procedures as part of a beam failure recovery procedure, BWP identity information associated to a BWP toward which a random access procedure was performed, and/or frequency or bandwidth information of a BWP toward which a random access procedure was performed.
  • a network node comprises processing circuitry operable to perform any of the network node methods described above.
  • Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network node described above.
  • Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments limit the conditional inclusion of the random-access information in the RLF report to the scenarios in which the UE actually performs the random- access procedure, i.e., when the UE is configured with LBT recovery configuration for a BWP with configured random access resources.
  • Figure 1 is a flow diagram illustrating self-configuration/self-optimization functionality
  • Figure 2 shows an example of a communication system, according to certain embodiments
  • Figure 3 shows a user equipment (UE), according to certain embodiments
  • Figure 4 shows a network node, according to certain embodiments
  • Figure 5 is a block diagram of a host, according to certain embodiments
  • Figure 6 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized
  • Figure 7 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
  • Figure 8 is a flowchart illustrating an example method in a wireless device, according to certain embodiments
  • Figure 9 is a flowchart illustrating an example method in a network node, according to certain
  • some embodiments include a method performed in an unlicensed spectrum by a user equipment (UE) after declaring a radio link failure (RLF). The method comprises, upon detection of a radio link failure, determining whether a consistent LBT failure occurred in a bandwidth part (BWP) used by the UE and that the LBT recovery configuration is configured by the network for a BWP configured with the random-access resources.
  • BWP bandwidth part
  • the method further comprises, in response to determining that a consistent LBT failure occurred in a BWP and the LBT recovery configuration was configured for a BWP configured with random access resources, including the random-access related information in a report logged by the UE.
  • a consistent LBT failure occurred in a BWP and the LBT recovery configuration was configured for a BWP configured with random access resources including the random-access related information in a report logged by the UE.
  • Some embodiments include a method performed in an unlicensed spectrum (e.g., New Radio unlicensed (NR-U)) by a wireless terminal (e.g., UE) after declaring a RLF on master cell group (MCG) or a secondary cell group (SCG).
  • NR-U New Radio unlicensed
  • MCG master cell group
  • SCG secondary cell group
  • the method comprises, upon detection of a radio link failure on MCG or SCG, determining whether a consistent LBT failure occurred in a BWP used by the UE and the LBT recovery configuration is configured by the network for a BWP configured with the random-access resources. In response to determining that a consistent LBT failure occurred in a bandwidth part and the LBT recovery configuration was configured for a BWP configured with random access resources, the method further comprises including the random-access related information in a report logged by the UE.
  • the random access related information comprising at least any (or any combination) of the following: ⁇ A set of random-access information associated to the last random access procedure performed in a BWP of the PCell (if operating in the shared spectrum) executed as part of a LBT recovery procedure. ⁇ A set of random access information associated to the first random access procedure performed in a BWP of the PCell executed as part of LBT recovery procedure. ⁇ Multiple sets of random access information (i.e., a list of random access procedure information), wherein each set (or entry in the list) of random access information is associated to one of the multiple random access procedures performed in different BWPs of the PCell (if operating in the shared spectrum) executed during the LBT recovery procedure.
  • the method further comprises sending the report including the random access related information to the network either immediately (e.g., in MCGFailureInformation or SCGFailureInformation messages), or based on a request received from the network node (e.g., as part of UE Information Request/Response procedure) after indicating the availability of the report.
  • the above method may be formulated as the following.
  • the method further comprises including the random access related information in a report logged/generated by the UE.
  • the random access related information comprising at least any (or any combination) of the following: ⁇ A set of random-access information associated to the last random access procedure performed in a BWP of the PCell (if operating in the shared spectrum) executed as part of LBT recovery procedure.
  • Multiple sets of random access information i.e., a list of random access procedure information
  • each set (or entry in the list) of random access information is associated to one of the multiple random access procedures performed in different BWPs of the PCell (if operating in the shared spectrum) executed during the LBT recovery procedure.
  • the number of performed random access procedures as part of beam failure recovery procedure.
  • the method further comprises sending the report including the random access related information to the network either immediately (e.g., in MCGFailureInformation or SCGFailureInformation messages), or based on a request received from the network node (e.g., as part of UE Information Request/Response procedure) after indicating the availability of the report.
  • the above method can be formulated as the following. Upon detection of a radio link failure on MCG or SCG, determining whether the RLF cause in the logged RLF report is set to the LBT failure and the UE performed random access procedure to recover from LBT failure.
  • the random access related information comprising at least any (or any combination) of the following: [0061] A set of random-access information associated to the last random access procedure performed in a BWP of the PCell (if operating in the shared spectrum) executed as part of RBT recovery procedure ⁇ A set of random access information associated to the first random access procedure performed in a BWP of the PCell executed as part of LBT recovery procedure.
  • the method further comprises sending the report including the random access related information to the network either immediately (e.g., in MCGFailureInformation or SCGFailureInformation messages), or based on a request received from the network node (e.g., as part of UE Information Request/Response procedure) after indicating the availability of the report.
  • the above methods impacting the Abstract Syntax Notation 1 (ASN.1) of the RRC specification may be represented in TS 38.331as follows in the UEInformationResponse message conveying the RLF-Report or the SHR.
  • UEInformationResponse-r16 SEQUENCE ⁇ rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE ⁇ ueInformationResponse-r16 UEInformationResponse-r16-IEs, criticalExtensionsFuture SEQUENCE ⁇ ⁇ ⁇ [text omitted]
  • RA-InformationCommon-r16 :: SEQUENCE ⁇ absoluteFrequencyPointA-r16 ARFCN-ValueNR, locationAndBandwidth-r16 INTEGER (0..37949), subcarrierSpacing-r16 SubcarrierSpacing, msg1-FrequencyStart-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msg1-FrequencyStartCFRA
  • the measResultLastServCell includes the RPLMN); 1>set the measResultLastServCell to include the cell level RSRP, RSRQ and the available SINR, of the source PCell (in case HO failure) or PCell (in case RLF) based on the available SSB and CSI-RS measurements collected up to the moment the UE detected failure; 1> if the SS/PBCH block-based measurement quantities are available: 2>set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest SS/PBCH block RSRP is listed first if SS/PBCH block RSRP measurement results are available, otherwise the highest SS/PBCH block RSRQ is listed first if SS/PBCH block RSRQ measurement results are available, otherwise the highest SS/PBCH block SINR is listed first, based on the available SS/PBCH block
  • the measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported. 1>set the c-RNTI to the C-RNTI used in the source PCell (in case HO failure) or PCell (in case RLF); 1>if the failure is detected due to reconfiguration with sync failure as described in 5.3.5.8.3, set the fields in VarRLF-report as follows: 2>set the connectionFailureType to hof; 2> if the UE supports RLF-Report for DAPS handover and if any DAPS bearer was configured while T304 was running: 3>set lastHO-Type to daps; 3> if radio link failure was detected in the source PCell, according to clause 5.3.10.3: 4>set timeConnSourceDAPS-Failure to the time between the initiation of the DAPS handover execution and the radio link failure detected in the source PCell while T304 was running; 4>set the rlf-Cause to the trigger for detecting the source radio link failure in
  • the UE may discard the radio link failure information or handover failure information, i.e. release the UE variable VarRLF-Report, 48 hours after the radio link failure/handover failure is detected.
  • the term 'handover failure' has been used to refer to 'reconfiguration with sync failure'. IN ANOTHER EXAMPLE IMPLEMENTATION THE UE MAY LOG ONLY THE INFORMATION CONCERNING ONE RA PROCEDURE E.G., THE LAST RA PROCEDURE.
  • the UE shall determine the content in the VarRLF-Report as follows: 1>clear the information included in VarRLF-Report, if any; 1>set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e.
  • the measResultLastServCell includes the RPLMN); 1>set the measResultLastServCell to include the cell level RSRP, RSRQ and the available SINR, of the source PCell (in case HO failure) or PCell (in case RLF) based on the available SSB and CSI-RS measurements collected up to the moment the UE detected failure; 1> if the SS/PBCH block-based measurement quantities are available: 2>set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest SS/PBCH block RSRP is listed first if SS/PBCH block RSRP measurement results are available, otherwise the highest SS/PBCH block RSRQ is listed first if SS/PBCH block RSRQ measurement results are available, otherwise the highest SS/PBCH block SINR is listed first, based on the available SS/PBCH block
  • the measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported. 1>set the c-RNTI to the C-RNTI used in the source PCell (in case HO failure) or PCell (in case RLF); 1>if the failure is detected due to reconfiguration with sync failure as described in 5.3.5.8.3, set the fields in VarRLF-report as follows: 2>set the connectionFailureType to hof; 2> if the UE supports RLF-Report for DAPS handover and if any DAPS bearer was configured while T304 was running: 3>set lastHO-Type to daps; 3> if radio link failure was detected in the source PCell, according to clause 5.3.10.3: 4>set timeConnSourceDAPS-Failure to the time between the initiation of the DAPS handover execution and the radio link failure detected in the source PCell while T304 was running; 4>set the rlf-Cause to the trigger for detecting the source radio link failure in
  • the UE may discard the radio link failure information or handover failure information, i.e. release the UE variable VarRLF-Report, 48 hours after the radio link failure/handover failure is detected.
  • the term 'handover failure' has been used to refer to 'reconfiguration with sync failure'.
  • the SCGFailureInformation message is used to provide information regarding NR SCG failures detected by the UE.
  • the MCGFailureInformation message is used to provide information regarding NR MCG failures detected by the UE.
  • the UE shall set the contents of the MCGFailureInformation message as follows: 1>include and set failureType in accordance with 5.7.3b.3; 1>for each MeasObjectNR
  • FIG. 2 shows an example of a communication system 100 in accordance with some embodiments.
  • the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108.
  • an access network 104 such as a radio access network (RAN)
  • RAN radio access network
  • core network 106 which includes one or more core network nodes 108.
  • the access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • the network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.
  • UE user equipment
  • 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.
  • the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 110 and other communication devices.
  • the network nodes 110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 112 and/or with other network nodes or equipment in the telecommunication network 102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 102.
  • the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices.
  • the core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • UPF User Plane Function
  • the host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs
  • analytics functionality such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs
  • social media such as a plurality of UEs
  • 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.
  • 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.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 6G wireless local area network
  • WiFi wireless local area network
  • WiMax Worldwide Interoperability for Micro
  • the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive IoT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 112 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104.
  • a UE may be configured for operating in single- or multi-RAT or multi-standard mode.
  • 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).
  • MR-DC multi-radio dual connectivity
  • the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and/or 112d) and network nodes (e.g., network node 110b).
  • the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 114 may be a broadband router enabling access to the core network 106 for the UEs.
  • the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114.
  • the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.
  • the hub 114 may have a constant/persistent or intermittent connection to the network node 110b.
  • the hub 114 may also allow for a different communication scheme and/or schedule between the hub 114 and UEs (e.g., UE 112c and/or 112d), and between the hub 114 and the core network 106.
  • the hub 114 is connected to the core network 106 and/or one or more UEs via a wired connection.
  • the hub 114 may be configured to connect to an M2M service provider over the access network 104 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection.
  • the hub 114 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 110b.
  • the hub 114 may be a non- dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 3 shows a UE 200 in accordance with some embodiments.
  • 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.
  • VoIP voice over IP
  • LME laptop-embedded equipment
  • LME laptop-mounted equipment
  • CPE wireless customer-premise equipment
  • 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).
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • 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).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • the UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input/output interface 206, a power source 208, a memory 210, a communication interface 212, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 2.
  • the level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210.
  • the processing circuitry 202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 202 may include multiple central processing units (CPUs).
  • the input/output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 200.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device.
  • a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 208 may further include power circuitry for delivering power from the power source 208 itself, and/or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.
  • the memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216.
  • the memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.
  • the memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous 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.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • the memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium.
  • the processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212.
  • the communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222.
  • the communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 218 and/or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 212 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.
  • GPS global positioning system
  • 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.
  • a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • 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.
  • 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.
  • IoT Internet of Things
  • 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.
  • UAV Unmanned
  • a UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 200 shown in Figure 2.
  • 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.
  • the UE may implement the 3GPP NB-IoT standard.
  • 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.
  • 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.
  • 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.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • Figure 4 shows a network node 300 in accordance with some embodiments.
  • 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.
  • 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)).
  • APs access points
  • BSs base stations
  • Node Bs evolved Node Bs
  • gNBs NR NodeBs
  • 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).
  • DAS distributed antenna system
  • 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).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308.
  • the network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 300 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 300 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs).
  • the network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.
  • RFID Radio Frequency Identification
  • the processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.
  • the processing circuitry 302 includes a system on a chip (SOC).
  • the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314.
  • RF radio frequency
  • the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.
  • the memory 304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, 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 302.
  • 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-
  • the memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300.
  • the memory 304 may be used to store any calculations made by the processing circuitry 302 and/or any data received via the communication interface 306.
  • the processing circuitry 302 and memory 304 is integrated.
  • the communication interface 306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE.
  • the communication interface 306 comprises port(s)/terminal(s) 316 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310.
  • Radio front-end circuitry 318 comprises filters 320 and amplifiers 322.
  • the radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302.
  • the radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and/or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and/or different combinations of components. [0097] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310.
  • the RF transceiver circuitry 312 is part of the communication interface 306.
  • the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).
  • the antenna 310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.
  • the antenna 310, communication interface 306, and/or the processing circuitry 302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment.
  • the antenna 310, the communication interface 306, and/or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein.
  • the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308.
  • the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry.
  • Embodiments of the network node 300 may include additional components beyond those shown in Figure 4 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.
  • the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.
  • Figure 5 is a block diagram of a host 400, which may be an embodiment of the host 116 of Figure 1, in accordance with various aspects described herein.
  • the host 400 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 400 may provide one or more services to one or more UEs.
  • the host 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input/output interface 406, a network interface 408, a power source 410, and a memory 412.
  • 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 10 and 3, such that the descriptions thereof are generally applicable to the corresponding components of host 400.
  • the memory 412 may include one or more computer programs including one or more host application programs 414 and data 416, which may include user data, e.g., data generated by a UE for the host 400 or data generated by the host 400 for a UE.
  • Embodiments of the host 400 may utilize only a subset or all of the components shown.
  • the host application programs 414 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 414 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.
  • the host 400 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 414 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.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • Figure 6 is a block diagram illustrating a virtualization environment 500 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • 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 500 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.
  • VMs virtual machines
  • hardware nodes such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Hardware 504 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 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs 508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 506 may present a virtual operating platform that appears like networking hardware to the VMs 508.
  • the VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 506.
  • a virtual appliance 502 may be implemented on one or more of VMs 508, 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 network function virtualization
  • 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.
  • a VM 508 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 508, and that part of hardware 504 that executes that VM 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 508 on top of the hardware 504 and corresponds to the application 502.
  • Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 may be part of a larger cluster of hardware (e.g.
  • hardware 504 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 512 which may alternatively be used for communication between hardware nodes and radio units.
  • FIG. 7 shows a communication diagram of a host 602 communicating via a network node 604 with a UE 606 over a partially wireless connection in accordance with some embodiments.
  • UE such as a UE 112a of Figure 2 and/or UE 200 of Figure 2
  • network node such as network node 110a of Figure 2 and/or network node 300 of Figure 3
  • host such as host 116 of Figure 2 and/or host 400 of Figure 4
  • embodiments of host 602 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 602 also includes software, which is stored in or accessible by the host 602 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 606 connecting via an over-the-top (OTT) connection 650 extending between the UE 606 and host 602.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection 650.
  • the network node 604 includes hardware enabling it to communicate with the host 602 and UE 606.
  • the connection 660 may be direct or pass through a core network (like core network 106 of Figure 1) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 606 includes hardware and software, which is stored in or accessible by UE 606 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 606 with the support of the host 602.
  • 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 606 with the support of the host 602.
  • an executing host application may communicate with the executing client application via the OTT connection 650 terminating at the UE 606 and host 602.
  • 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 650 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 650.
  • the OTT connection 650 may extend via a connection 660 between the host 602 and the network node 604 and via a wireless connection 670 between the network node 604 and the UE 606 to provide the connection between the host 602 and the UE 606.
  • the connection 660 and wireless connection 670, over which the OTT connection 650 may be provided, have been drawn abstractly to illustrate the communication between the host 602 and the UE 606 via the network node 604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 602 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 606.
  • the user data is associated with a UE 606 that shares data with the host 602 without explicit human interaction.
  • the host 602 initiates a transmission carrying the user data towards the UE 606.
  • the host 602 may initiate the transmission responsive to a request transmitted by the UE 606.
  • the request may be caused by human interaction with the UE 606 or by operation of the client application executing on the UE 606.
  • the transmission may pass via the network node 604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 612, the network node 604 transmits to the UE 606 the user data that was carried in the transmission that the host 602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE 606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 606 associated with the host application executed by the host 602. [0117] In some examples, the UE 606 executes a client application which provides user data to the host 602. The user data may be provided in reaction or response to the data received from the host 602.
  • the UE 606 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 606.
  • the UE 606 initiates, in step 618, transmission of the user data towards the host 602 via the network node 604.
  • the network node 604 receives user data from the UE 606 and initiates transmission of the received user data towards the host 602.
  • the host 602 receives the user data carried in the transmission initiated by the UE 606.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 606 using the OTT connection 650, in which the wireless connection 670 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate and latency and thereby provide benefits such as reduced user waiting time, better responsiveness, and better QoE.
  • factory status information may be collected and analyzed by the host 602.
  • the host 602 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 602 may store surveillance video uploaded by a UE.
  • the host 602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 602 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.
  • 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.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 602 and/or UE 606.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 650 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 650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 604. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 602.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 650 while monitoring propagation times, errors, etc.
  • the computing devices described herein e.g., UEs, network nodes, hosts
  • 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.
  • processing circuitry 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.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • 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.
  • 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.
  • 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.
  • 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.
  • the processing circuitry can be configured to perform the described functionality.
  • FIGURE 8 is a flowchart illustrating an example method in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 8 may be performed by UE 200 described with respect to FIGURE 3. The wireless device is operating in shared spectrum. [0124] The method begins at step 812, where the wireless device (e.g., UE 200) detects a radio link failure.
  • the wireless device e.g., UE 200
  • the wireless device determines a consistent LBT failure occurred in a BWP used by the wireless device and that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources.
  • determining a LBT problem occurred in the BWP comprises determining the rlf-cause is set to lbtFailure and determining that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources comprises determining lbt-failureRecoveryConfig was configured for the BWP in which a random access procedure was performed.
  • determining that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources comprises determining the wireless device performed a random access procedure to recover from an LBT failure.
  • a particular advantage of the determining steps is to limit the conditional inclusion of the random-access information in the failure report to the scenarios in which the UE actually performs the random-access procedure i.e., when the UE is configured with LBT recovery configuration for a BWP with configured random access resources.
  • the wireless device logs random access information in a failure report.
  • the random access information comprises random access information associated to a last random access procedure executed as part of a random access recovery procedure, random access information associated to a first random access procedure executed as part of a random access recovery procedure, a number of performed random access procedures as part of a beam failure recovery procedure, BWP identity information associated to a BWP toward which a random access procedure was performed, and/or frequency or bandwidth information of a BWP toward which a random access procedure was performed.
  • the random access information may include any of the information described in the embodiments and examples described herein.
  • the wireless device may receive the request as part of UE Information Request/Response procedure. This step is optional, and in some embodiments the method may continue to step 820 where the wireless device transmits the failure report to the network node without receiving an explicit request.
  • the wireless device transmits the failure report to a network node.
  • the wireless device may transmit a MCGFailureInformation or SCGFailureInformation message.
  • the wireless device may transmit the failure report according to any of the embodiments and examples described herein.
  • Modifications, additions, or omissions may be made to method 800 of FIGURE 8. Additionally, one or more steps in the method of FIGURE 8 may be performed in parallel or in any suitable order.
  • FIGURE 9 is a flowchart illustrating an example method in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 9 may be performed by network node 300 described with respect to FIGURE 4.
  • the method begins at step 912, where the network node (e.g., network node 300) configures a wireless device for logging random access information associated with a consistent LBT failure for a BWP used by the wireless device and configured with random access resources.
  • the network node configures the wireless device to perform LBT recovery based on a random access procedure for the BWP configured with random access resources.
  • the network node may optionally transmit a request to the wireless device for the wireless device to transmit the failure report. In other embodiments, the method may continue to step 918. [0137] At step 918, the network node receives a failure report comprising random access information associated with LBT problems from the wireless device.
  • the random access information comprises random access information associated to a last random access procedure executed as part of a random access recovery procedure, random access information associated to a first random access procedure executed as part of a random access recovery procedure, a number of performed random access procedures as part of a beam failure recovery procedure, BWP identity information associated to a BWP toward which a random access procedure was performed, and/or frequency or bandwidth information of a BWP toward which a random access procedure was performed.
  • a method performed by a wireless device operating in shared spectrum comprising: ⁇ detecting a radio link failure; ⁇ determining a listen before talk (LBT) problem occurred and that the wireless device is able to perform LBT recovery for a random access procedure; ⁇ logging random access information in a failure report; and ⁇ transmitting the failure report to a network node.
  • the random access information comprises any one or more of the following: o A set of random-access information associated to the last random access procedure executed as part of a random access recovery procedure o A set of random access information associated to the first random access procedure executed as part of a random access recovery procedure o Multiple sets of random access information, wherein each set of random access information is associated to one of the multiple random access procedures performed in different BWPs executed during the LBT recovery procedure. o a number of performed random access procedures as part of beam failure recovery procedure o BWP identity information associated to a BWP toward which the random access procedure is performed o Frequency information of a BWP toward which the random access procedure is performed. 3.
  • a method performed by a wireless device comprising: ⁇ any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. 4.
  • the method of the previous embodiment further comprising one or more additional wireless device steps, features or functions described above. 5.
  • the method of any of the previous embodiments further comprising: ⁇ providing user data; and ⁇ forwarding the user data to a host computer via the transmission to the base station.
  • a method performed by a base station comprising: ⁇ configuring a wireless device for logging random access information associated with listen before talk (LBT) problems; ⁇ configuring the wireless device to perform LBT recovery for a random access procedure; and ⁇ receiving a failure report comprising random access information associated with LBT problems from the wireless device.
  • LBT listen before talk
  • the random access information comprises any one or more of the following: o A set of random-access information associated to the last random access procedure executed as part of a random access recovery procedure o A set of random access information associated to the first random access procedure executed as part of a random access recovery procedure o Multiple sets of random access information, wherein each set of random access information is associated to one of the multiple random access procedures performed in different BWPs executed during the LBT recovery procedure. o a number of performed random access procedures as part of beam failure recovery procedure o BWP identity information associated to a BWP toward which the random access procedure is performed o Frequency information of a BWP toward which the random access procedure is performed.
  • a method performed by a base station comprising: ⁇ any of the steps, features, or functions described above with respect to base station, either alone or in combination with other steps, features, or functions described above.
  • the method of the previous embodiment further comprising one or more additional base station steps, features or functions described above.
  • the method of any of the previous embodiments further comprising: ⁇ obtaining user data; and ⁇ forwarding the user data to a host computer or a wireless device.
  • Group C Embodiments 11 A mobile terminal comprising: ⁇ processing circuitry configured to perform any of the steps of any of the Group A embodiments; and ⁇ power supply circuitry configured to supply power to the wireless device. 12.
  • a base station comprising: ⁇ processing circuitry configured to perform any of the steps of any of the Group B embodiments; ⁇ power supply circuitry configured to supply power to the wireless device.
  • a user equipment comprising: ⁇ an antenna configured to send and receive wireless signals; ⁇ radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; ⁇ the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; ⁇ an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; ⁇ an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and ⁇ a battery connected to the processing circuitry and configured to supply power to the UE.
  • a communication system including a host computer comprising: ⁇ processing circuitry configured to provide user data; and ⁇ a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), ⁇ wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • the communication system of the pervious embodiment further including the base station.
  • ⁇ the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • ⁇ the UE comprises processing circuitry configured to execute a client application associated with the host application.
  • the method of the previous embodiment further comprising, at the base station, transmitting the user data.
  • a user equipment configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs any of the previous 3 embodiments.
  • a communication system including a host computer comprising: ⁇ processing circuitry configured to provide user data; and ⁇ a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), ⁇ wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.
  • the communication system of the previous embodiment wherein the cellular network further includes a base station configured to communicate with the UE.
  • the communication system of the previous 2 embodiments wherein: ⁇ the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and ⁇ the UE’s processing circuitry is configured to execute a client application associated with the host application.
  • a communication system including a host computer comprising: ⁇ communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, ⁇ wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • the communication system of the previous embodiment further including the UE.
  • the communication system of the previous 2 embodiments further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • ⁇ the processing circuitry of the host computer is configured to execute a host application
  • ⁇ the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • the communication system of the previous 4 embodiments wherein: ⁇ the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and ⁇ the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.
  • a method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: ⁇ at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
  • the method of the previous embodiment further comprising, at the UE, providing the user data to the base station.
  • the method of the previous 2 embodiments further comprising: ⁇ at the UE, executing a client application, thereby providing the user data to be transmitted; and ⁇ at the host computer, executing a host application associated with the client application.
  • the method of the previous 3 embodiments further comprising: ⁇ at the UE, executing a client application; and ⁇ at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, ⁇ wherein the user data to be transmitted is provided by the client application in response to the input data.
  • a communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • the communication system of the previous embodiment further including the base station.
  • the communication system of the previous 2 embodiments further including the UE, wherein the UE is configured to communicate with the base station.
  • the communication system of the previous 3 embodiments wherein: ⁇ the processing circuitry of the host computer is configured to execute a host application; ⁇ the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • the method of the previous embodiment further comprising at the base station, receiving the user data from the UE.
  • the method of the previous 2 embodiments further comprising at the base station, initiating a transmission of the received user data to the host computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

According to some embodiments, a method performed by a wireless device operating in shared spectrum comprises: detecting (812) a radio link failure; determining (814) a consistent listen-before-talk, LBT, failure occurred in a bandwidth part, BWP, used by the wireless device and that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources; logging (816) random access information in a failure report; and transmitting (820) the failure report to a network node

Description

Indicating LBT Results in Failure Report TECHNICAL FIELD [0001] The present disclosure generally relates to communication networks, and more specifically to indicating listen-before-talk (LBT) results in a failure report. BACKGROUND [0002] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description. [0003] A 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 (Third Generation Partnership Project) and the NGMN (Next Generation Mobile Networks). [0004] In 3GPP, the processes within the SON area are classified into self-configuration process and self-optimization process. Self-configuration process is the process where newly deployed nodes are configured by automatic installation procedures to get the necessary basic configuration for system operation. [0005] This process works in pre-operational state. Pre-operational state is the state from when the eNB is powered up and has network backbone connectivity until the radio frequency (RF) transmitter is switched on. [0006] As illustrated in Figure 1, functions handled in the pre-operational state, like basic setup and initial radio configuration, are covered by the self-configuration process. [0007] Self-optimization process is defined as the process where UE and access node measurements and performance measurements are used to auto-tune the network. [0008] This process works in operational state. Operational state is understood as the state where the RF interface is additionally switched on. [0009] Figure 1 is a flow diagram illustrating self-configuration/self-optimization functionality. Figure 1 is reproduced from 3GPP TS 36.300 Figure 22.1-1. As described in Figure 1, functions handled in the operational state, like optimization/adaptation, are covered by the self-optimization process. [0010] Long Term Evolution (LTE) supports self-configuration and self-optimization as described in 3GPP TS 36.300 section 22.2, including features such as dynamic configuration, automatic neighbor relation (ANR), mobility load balancing, mobility robustness optimization (MRO), random access channel (RACH) optimization and support for energy saving. [0011] New Radio (NR) supports self-configuration and self-optimization as well, starting with self-configuration features such as dynamic configuration, ANR in Rel-15, as described in 3GPP TS 38.300 section 15. NR Rel-16 includes more SON features for self-optimization such as mobility robustness optimization (MRO). [0012] MRO is described in more detail as follows. Seamless handovers are a key feature of 3GPP technologies. Successful handovers ensure that the user equipment (UE) moves around in the coverage area of different cells without causing too many interruptions in the 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 a radio link failure (RLF) or handover failure (HOF). [0013] Upon HOF and RLF, the UE may take autonomous actions, e.g., trying to select a cell and initiate reestablishment procedure so that the UE is trying to get back as soon as it can, so that it can be reachable again. The RLF causes a poor user experience because the RLF is declared by the UE only when the UE 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, Radio Resource Control (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. [0014] According to 3GPP TS 36.331, the possible causes for the radio link failure may be one of the following: expiry of the radio link monitoring related timer T310; 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); upon reaching the maximum number of radio link control (RLC) retransmissions; and upon receiving random access problem indication from the medium access control (MAC) entity. [0015] Because 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 for measurement reports) to avoid later RLFs. Before the standardization of MRO related report handling in the network, only the UE was aware of information associated with the radio quality at the time of RLF, 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 also from neighboring base stations. [0016] As part of the MRO solution in LTE, the RLF reporting procedure was introduced in the RRC specification in Rel-9. That has 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 that the UE succeeds to connect with (e.g., after reestablishment). That has also impacted the inter-gNodeB interface, i.e., X2AP specifications (3GPP TS 36.423), because an eNodeB receiving an RLF report may forward the RLF report to the eNodeB where the failure originated. [0017] For the RLF report generated by the UE, its contents have been enhanced with more details in the subsequent releases. The measurements included in the measurement report based include: ^ Measurement quantities (reference signal receive power (RSRP), reference signal receive quality (RSRQ)) of the last serving cell (PCell). ^ Measurement quantities of the neighbor cells in different frequencies of different radio access technologies (RATs) (EUTRA, UTRA, GERAN, CDMA2000). ^ Measurement quantity (received signal strength indication (RSSI)) associated to wireless local area network (WLAN) access points. ^ Measurement quantity (RSSI) associated to Bluetooth beacons. ^ Location information, if available (including location coordinates and velocity). ^ Globally unique identity of the last serving cell, if available, otherwise the physical cell identifier (PCI) and the carrier frequency of the last serving cell. ^ Tracking area code of the PCell. ^ Time elapsed since the last reception of the ‘Handover command’ message. ^ Cell radio network temporary identifier (C-RNTI) used in the previous serving cell. ^ Whether or not the UE was configured with a data radio bearer (DRB) having a quality of service class indicator (QCI) value of 1. [0018] After the RLF is declared, the RLF report is logged and included in the VarRLF-Report and, after the UE selects a cell and succeeds with a reestablishment, the UE includes an indication that the UE has an RLF report available in the RRC Reestablishment Complete message to alert the target cell of the availability. Then, upon receiving a UEInformationRequest message with a flag “rlf-ReportReq-r9,” the UE shall include the RLF report (stored in a UE variable VarRLF- Report, as described above) in a UEInformationResponse message sent to the network. [0019] Based on the RLF report from the UE and the knowledge about which cell to which the UE reestablished itself, the original source cell can deduce whether the RLF was caused due to a coverage hole or due to handover associated parameter configurations. If the RLF is 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. [0020] In some cases, the handover failure occurred due to the ‘too-late handover’ cases. For example, 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 the target cell post RLF. [0021] An example corrective action from the original serving cell could be to initiate the handover procedure towards the target cell a bit earlier by decreasing the CIO (cell individual offset) towards the target cell that controls when the UE sends the event triggered measurement report that leads to taking the handover decision. [0022] In some cases, the handover failure occurred due to the ‘too-early handover’ cases. For example, 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. [0023] 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 towards the target cell that controls when the UE sends the event triggered measurement report that leads to taking the handover decision. [0024] In some cases, the handover failure occurred due to the ‘handover-to-wrong-cell’ cases. For example, 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 the UE towards a particular target cell but the UE declares the RLF and reestablishes itself in a third cell. [0025] A corrective action from the original serving cell could be to initiate the measurement reporting procedure that leads to handover towards the target cell a bit later by decreasing the CIO 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. [0026] As an enhancement to MRO in Rel.17, 3GPP introduced the successful handover report (SHR). Unlike the RLF-Report, which is used as described above to report the RLF or handover failure experienced by the UE, the UE uses the SHR to report various information associated to successful handover. The successful handover will not be reported always at every handover, but only when certain triggering conditions are fulfilled. For example, if while doing handover, the T310/T312/T304 timers exceed a certain threshold, then the UE shall store information associated to the handover. Similarly, if the handover was a dual active protocol stack (DAPS) handover, and the UE succeeded with the handover but an RLF was experienced in the source cell while doing the DAPS handover, then the UE stores information associated to the DAPS handover. When storing the successful handover report, the UE may include various information to aid the network to optimize the handover, such as measurements of the neighboring cells, the fulfilled condition that triggered the successful handover report (e.g. threshold on T310 exceeded, specific RLF issue in the source while doing DAPS handover), etc. [0027] The SHR may be configured by a certain serving cell, and when triggering conditions for SHR logging are fulfilled, the UE stores the information until the network requests the information. In particular, the UE may indicate availability of SHR information in certain RRC message, such as RRCReconfigurationComplete, RRCReestablishmentComplete, RRCSetupComplete, RRCResumeComplete, and the network may request such information via the UEInformationRequest message, upon which the UE transmits the stored SHR in the UEInformationResponse message. [0028] Both the RLF-Report and the SHR may include information associated to the random access (RA) procedure. The RLF may be in fact due to random access problems, therefore by including the random access information, the network may optimize the random access procedure and possibly minimize the risk for RLF in future. Similarly, the SHR may also include RA information when the SHR is generated due to problems experienced during the handover, e.g. value of T304 reaching a value above a certain threshold. The RA information includes information related to the bandwidth part (BWP) in which the random access was attempted, information about the downlink pathloss experienced at the time of initiating the random access procedure, information related to each preamble transmission attempt, e.g. whether a contention was experienced or not, the number of preamble transmission attempts in a certain synchronization signal block (SSB) or channel state information reference signal (CSI-RS). [0029] The channel access procedure in NR unlicensed spectrum includes listen-before-talk (LBT). LBT is designed for unlicensed spectrum to ensure a fair co-existence with other RATs. In this mechanism, a radio device applies a clear channel assessment (CCA) check (e.g., channel sensing) before transmission. The transmitter involves energy detection (ED) over a time period compared to a certain threshold (ED threshold) to determine if a channel is idle. If the channel is determined to be occupied, the transmitter performs a random back-off within a contention window before the next CCA attempt. To protect the acknowledgement (ACK) transmissions, the transmitter must defer a period after each busy CCA slot prior to resuming back-off. After 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)). [0030] For quality of service (QoS) differentiation, a channel access priority based on the service type has been defined. For example, 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 physical random access channel (PRACH), physical uplink control channel (PUCCH), or RRC signal. [0031] The following describes random access handling in NR-U. As described above, the random access messages (including the PRACH) are subject to LBT before being transmitted. NR- U specifies an LBT counter that is stepped whenever an uplink transmission fails in a certain BWP. When such LBT counter reaches a maximum value, within a certain time, the UE declares “consistent LBT failure” for the corresponding BWP. If the affected BWP is in the PCell or the PSCell, the UE deactivates the affected BWP and activates another already configured BWP in the PCell/PSCell and transmits random access therein. On the other hand, if the affected BWP is an SCell, the UE stops transmitting in this SCell, and can send a scheduling request (SR) on another serving cell (not yet affected by “consistent uplink LBT failures”) for further communications. Additionally, as a result of the consistent LBT failure, the UE issues a MAC control element (CE) to indicate to the network which are the problematic cells in which “consistent LBT failures” were experienced. [0032] For the PCell, after the UE has attempted random access in all the BWPs in the PCell with no success, the UE declares RLF and may attempt reestablishment. Similarly, for the PSCell, the UE declares SCG failure when consistent uplink LBT failures have been experienced in all the BWPs of the PSCell. [0033] There currently exist certain challenges. For example, when including random access related information or at least one random access procedure in the RLF report in shared spectrum, the conditional inclusion of the random access information (e.g., ra-InformationCommon) in the RLF report results in confusion because the solution is specified as follows: 1>if connectionFailureType is rlf and the rlf-Cause is set to randomAccessProblem or beamFailureRecoveryFailure or lbtFailure; or 1>if connectionFailureType is hof and if the failed handover is an intra-RAT handover: 2> if consistent UL LBT failures were triggered and not cancelled at the time of the radio link failure or failed handover; or: 2> if the number of LBT failures experienced in the PCell at the time of the radio link failure or handover failure is above a threshold: 3> set consistentLBTFailure to true 3> for each random access performed in different BWPs of the SpCell configured with PRACH resources, while consistent UL LBT failures were triggered and not cancelled at the time of the failure: 4> set ra-InformationCommon to include the random-access related information as described in clause 5.7.10.5 in the ra-InformationCommonList; 2> else the random access procedure is only performed in one BWP: 3> set the ra-InformationCommon to include the random-access related information as described in clause 5.7.10.5; [0034] In the solution above, the “lbtFailure” included in the first condition leads to a situation that a UE shall include the random access information even if the UE is not configured with LBT recovery configuration for a BWP configured with random access resources and cannot execute random access procedure to recover from the LBT failure. [0035] The method is applicable to the RLFs occurring without applying/executing a reconfiguration with synchronization mechanism. In fact, when the UE executes/performs a reconfiguration with synchronization it performs random access procedure, and thus the UE may log the random access related information in the RLF report for any reconfiguration with synchronization failure (such as a handover failure or PSCell change failure). However, assuming the same method (including the random access related information in the RLF report) for RLF due to consistent LBT failure is not always true. SUMMARY [0036] As described above, certain challenges currently exist with indicating listen-before- talk (LBT) results in a failure report. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, some embodiments include a method performed in an unlicensed spectrum (e.g., New Radio unlicensed (NR-U)) by a wireless terminal (e.g., user equipment (UE)) after declaring a radio link failure (RLF) on a master cell group (MCG) or a secondary cell group (SCG). The method comprises, upon detection of a radio link failure on MCG or SCG, determining whether a consistent LBT failure occurred in a bandwidth part (BWP) used by the UE and that the LBT recovery configuration is configured by the network for a BWP configured with the random-access resources. The method further comprises, in response to determining that a consistent LBT failure occurred in a BWP and the LBT recovery configuration was configured for a BWP configured with random access resources, including the random-access related information in a report logged by the UE. The method further comprises sending the report including the random access related information to the network either immediately or based on a request received from the network node. [0037] According to some embodiments, a method performed by a wireless device operating in shared spectrum comprises: detecting a radio link failure; determining a consistent LBT failure occurred in a BWP used by the wireless device and that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources; logging random access information in a failure report; and transmitting the failure report to a network node. [0038] In particular embodiments, the random access information comprises random access information associated to a last random access procedure executed as part of a random access recovery procedure, random access information associated to a first random access procedure executed as part of a random access recovery procedure, a number of performed random access procedures as part of a beam failure recovery procedure, BWP identity information associated to a BWP toward which a random access procedure was performed, and/or frequency or bandwidth information of a BWP toward which a random access procedure was performed. [0039] In particular embodiments, the method further comprises receiving a request from the network node to transmit the failure report to the network node. [0040] In particular embodiments, determining a LBT problem occurred in the BWP comprises determining the rlf-cause is set to lbtFailure and determining that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources comprises determining lbt-failureRecoveryConfig was configured for the BWP in which a random access procedure was performed. [0041] In particular embodiments, determining that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources comprises determining the wireless device performed a random access procedure to recover from an LBT failure. [0042] According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the wireless device methods described above. [0043] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless device described above. [0044] According to some embodiments, a method performed by a network node comprises: configuring a wireless device for logging random access information associated with a consistent LBT failure for a BWP used by the wireless device and configured with random access resources; configuring the wireless device to perform LBT recovery based on a random access procedure for the BWP configured with random access resources; and receiving a failure report comprising random access information associated with LBT problems from the wireless device. [0045] In particular embodiments, the method further comprises transmitting a request to the wireless device for the wireless device to transmit the failure report. [0046] In particular embodiments, the random access information comprises random access information associated to a last random access procedure executed as part of a random access recovery procedure, random access information associated to a first random access procedure executed as part of a random access recovery procedure, a number of performed random access procedures as part of a beam failure recovery procedure, BWP identity information associated to a BWP toward which a random access procedure was performed, and/or frequency or bandwidth information of a BWP toward which a random access procedure was performed. [0047] According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above. [0048] Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network node described above. [0049] Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments limit the conditional inclusion of the random-access information in the RLF report to the scenarios in which the UE actually performs the random- access procedure, i.e., when the UE is configured with LBT recovery configuration for a BWP with configured random access resources. BRIEF DESCRIPTION OF THE DRAWINGS [0050] The present disclosure may be best understood by way of example with reference to the following description and accompanying drawings that are used to illustrate embodiments of the present disclosure. In the drawings: Figure 1 is a flow diagram illustrating self-configuration/self-optimization functionality; Figure 2 shows an example of a communication system, according to certain embodiments; Figure 3 shows a user equipment (UE), according to certain embodiments; Figure 4 shows a network node, according to certain embodiments; Figure 5 is a block diagram of a host, according to certain embodiments; Figure 6 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized; Figure 7 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; Figure 8 is a flowchart illustrating an example method in a wireless device, according to certain embodiments; and Figure 9 is a flowchart illustrating an example method in a network node, according to certain embodiments. DETAILED DESCRIPTION [0051] As described above, certain challenges currently exist with indicating listen-before- talk (LBT) results in a failure report. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, some embodiments include a method performed in an unlicensed spectrum by a user equipment (UE) after declaring a radio link failure (RLF). The method comprises, upon detection of a radio link failure, determining whether a consistent LBT failure occurred in a bandwidth part (BWP) used by the UE and that the LBT recovery configuration is configured by the network for a BWP configured with the random-access resources. The method further comprises, in response to determining that a consistent LBT failure occurred in a BWP and the LBT recovery configuration was configured for a BWP configured with random access resources, including the random-access related information in a report logged by the UE. [0052] Particular embodiments are 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. [0053] Some embodiments include a method performed in an unlicensed spectrum (e.g., New Radio unlicensed (NR-U)) by a wireless terminal (e.g., UE) after declaring a RLF on master cell group (MCG) or a secondary cell group (SCG). The method comprises, upon detection of a radio link failure on MCG or SCG, determining whether a consistent LBT failure occurred in a BWP used by the UE and the LBT recovery configuration is configured by the network for a BWP configured with the random-access resources. In response to determining that a consistent LBT failure occurred in a bandwidth part and the LBT recovery configuration was configured for a BWP configured with random access resources, the method further comprises including the random-access related information in a report logged by the UE. [0054] The random access related information comprising at least any (or any combination) of the following: ^ A set of random-access information associated to the last random access procedure performed in a BWP of the PCell (if operating in the shared spectrum) executed as part of a LBT recovery procedure. ^ A set of random access information associated to the first random access procedure performed in a BWP of the PCell executed as part of LBT recovery procedure. ^ Multiple sets of random access information (i.e., a list of random access procedure information), wherein each set (or entry in the list) of random access information is associated to one of the multiple random access procedures performed in different BWPs of the PCell (if operating in the shared spectrum) executed during the LBT recovery procedure. ^ The number of performed random access procedures as part of beam failure recovery procedure. ^ The BWP identity information associated to the BWP toward which the random access procedure is performed. ^ Frequency information of the BWP toward which the random access procedure is performed. [0055] The method further comprises sending the report including the random access related information to the network either immediately (e.g., in MCGFailureInformation or SCGFailureInformation messages), or based on a request received from the network node (e.g., as part of UE Information Request/Response procedure) after indicating the availability of the report. [0056] In an embodiment, the above method may be formulated as the following. Upon detection of a radio link failure on MCG or SCG, determining whether a consistent LBT failure occurred in a bandwidth part used by the UE and the UE performed random access procedure to recover from LBT failure. In response to determining that a consistent LBT failure occurred in a bandwidth part and the UE performed random access procedure to recover from LBT failure, the method further comprises including the random access related information in a report logged/generated by the UE. [0057] The random access related information comprising at least any (or any combination) of the following: ^ A set of random-access information associated to the last random access procedure performed in a BWP of the PCell (if operating in the shared spectrum) executed as part of LBT recovery procedure. ^ A set of random access information associated to the first random access procedure performed in a BWP of the PCell executed as part of LBT recovery procedure. ^ Multiple sets of random access information (i.e., a list of random access procedure information), wherein each set (or entry in the list) of random access information is associated to one of the multiple random access procedures performed in different BWPs of the PCell (if operating in the shared spectrum) executed during the LBT recovery procedure. ^ The number of performed random access procedures as part of beam failure recovery procedure. ^ The BWP identity information associated to the BWP toward which the random access procedure is performed. ^ Frequency information of the BWP toward which the random access procedure is performed. [0058] The method further comprises sending the report including the random access related information to the network either immediately (e.g., in MCGFailureInformation or SCGFailureInformation messages), or based on a request received from the network node (e.g., as part of UE Information Request/Response procedure) after indicating the availability of the report. [0059] In another embodiment, the above method can be formulated as the following. Upon detection of a radio link failure on MCG or SCG, determining whether the RLF cause in the logged RLF report is set to the LBT failure and the UE performed random access procedure to recover from LBT failure. In response to determining that the RLF cause in the logged RLF report is set to the LBT failure and the UE performed random access procedure to recover from LBT failure, including the random access related information in a report logged/generated by the UE. [0060] The random access related information comprising at least any (or any combination) of the following: [0061] A set of random-access information associated to the last random access procedure performed in a BWP of the PCell (if operating in the shared spectrum) executed as part of RBT recovery procedure ^ A set of random access information associated to the first random access procedure performed in a BWP of the PCell executed as part of LBT recovery procedure. ^ Multiple sets of random access information (i.e., a list of random access procedure information), wherein each set (or entry in the list) of random access information is associated to one of the multiple random access procedures performed in different BWPs of the PCell (if operating in the shared spectrum) executed during the LBT recovery procedure. ^ The number of performed random access procedures as part of beam failure recovery procedure. ^ The BWP identity information associated to the BWP toward which the random access procedure is performed. ^ Frequency information of the BWP toward which the random access procedure is performed. [0062] The method further comprises sending the report including the random access related information to the network either immediately (e.g., in MCGFailureInformation or SCGFailureInformation messages), or based on a request received from the network node (e.g., as part of UE Information Request/Response procedure) after indicating the availability of the report. [0063] In one implementation example, the above methods impacting the Abstract Syntax Notation 1 (ASN.1) of the RRC specification may be represented in TS 38.331as follows in the UEInformationResponse message conveying the RLF-Report or the SHR. UEInformationResponse message -- ASN1START -- TAG-UEINFORMATIONRESPONSE-START UEInformationResponse-r16 ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { ueInformationResponse-r16 UEInformationResponse-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } [text omitted] RA-InformationCommon-r16 ::= SEQUENCE { absoluteFrequencyPointA-r16 ARFCN-ValueNR, locationAndBandwidth-r16 INTEGER (0..37949), subcarrierSpacing-r16 SubcarrierSpacing, msg1-FrequencyStart-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msg1-FrequencyStartCFRA-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msg1-SubcarrierSpacing-r16 SubcarrierSpacing OPTIONAL, msg1-SubcarrierSpacingCFRA-r16 SubcarrierSpacing OPTIONAL, msg1-FDM-r16 ENUMERATED {one, two, four, eight} OPTIONAL, msg1-FDMCFRA-r16 ENUMERATED {one, two, four, eight} OPTIONAL, perRAInfoList-r16 PerRAInfoList-r16, ..., [[ perRAInfoList-v1660 PerRAInfoList-v1660 OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndex-r16 ENUMERATED {kHz1dot25, kHz5, spare2, spare1} OPTIONAL ]], [[ msg1-SCS-From-prach-ConfigurationIndexCFRA-r16 ENUMERATED {kHz1dot25, kHz5, spare2, spare1} OPTIONAL ]], [[ msgA-RO-FrequencyStart-r17 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msgA-RO-FrequencyStartCFRA-r17 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msgA-SubcarrierSpacing-r17 SubcarrierSpacing OPTIONAL, msgA-RO-FDM-r17 ENUMERATED {one, two, four, eight} OPTIONAL, msgA-RO-FDMCFRA-r17 ENUMERATED {one, two, four, eight} OPTIONAL, msgA-SCS-From-prach-ConfigurationIndex-r17 ENUMERATED {kHz1dot25, kHz5, spare2, spare1} OPTIONAL, msgA-TransMax-r17 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL, msgA-MCS-r17 INTEGER (0..15) OPTIONAL, nrofPRBs-PerMsgA-PO-r17 INTEGER (1..32) OPTIONAL, msgA-PUSCH-TimeDomainAllocation-r17 INTEGER (1..maxNrofUL-Allocations) OPTIONAL, frequencyStartMsgA-PUSCH-r17 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, nrofMsgA-PO-FDM-r17 ENUMERATED {one, two, four, eight} OPTIONAL, dlPathlossRSRP-r17 RSRP-Range OPTIONAL, intendedSIBs-r17 SEQUENCE (SIZE (1..maxSIB)) OF SIB- Type-r17 OPTIONAL, ssbsForSI-Acquisition-r17 SEQUENCE (SIZE (1..maxNrofSSBs-r16)) OF SSB-Index OPTIONAL, msgA-PUSCH-PayloadSize-r17 BIT STRING (SIZE (5)) OPTIONAL, onDemandSISuccess-r17 ENUMERATED {true} OPTIONAL ]], } PerRAInfoList-r16 ::= SEQUENCE (SIZE (1..200)) OF PerRAInfo-r16 PerRAInfoList-v1660 ::= SEQUENCE (SIZE (1..200)) OF PerRACSI-RSInfo-v1660 PerRAInfo-r16 ::= CHOICE { perRASSBInfoList-r16 PerRASSBInfo-r16, perRACSI-RSInfoList-r16 PerRACSI-RSInfo-r16 } PerRASSBInfo-r16 ::= SEQUENCE { ssb-Index-r16 SSB-Index, numberOfPreamblesSentOnSSB-r16 INTEGER (1..200), perRAAttemptInfoList-r16 PerRAAttemptInfoList-r16 } PerRACSI-RSInfo-r16 ::= SEQUENCE { csi-RS-Index-r16 CSI-RS-Index, numberOfPreamblesSentOnCSI-RS-r16 INTEGER (1..200) } PerRACSI-RSInfo-v1660 ::= SEQUENCE { csi-RS-Index-v1660 INTEGER (1..96) OPTIONAL } PerRAAttemptInfoList-r16 ::= SEQUENCE (SIZE (1..200)) OF PerRAAttemptInfo-r16 PerRAAttemptInfo-r16 ::= SEQUENCE { contentionDetected-r16 BOOLEAN OPTIONAL, dlRSRPAboveThreshold-r16 BOOLEAN OPTIONAL, ..., [[ fallbackToFourStepRA-r17 ENUMERATED {true} OPTIONAL ]], } SIB-Type-r17 ::= ENUMERATED {sibType2, sibType3, sibType4, sibType5, sibType9, sibType10-v1610, sibType11-v1610, sibType12-v1610, sibType13-v1610, sibType14-v1610, spare6, spare5, spare4, spare3, spare2, spare1} RLF-Report-r16 ::= CHOICE { nr-RLF-Report-r16 SEQUENCE { measResultLastServCell-r16 MeasResultRLFNR-r16, measResultNeighCells-r16 SEQUENCE { measResultListNR-r16 MeasResultList2NR-r16 OPTIONAL, measResultListEUTRA-r16 MeasResultList2EUTRA-r16 OPTIONAL } OPTIONAL, c-RNTI-r16 RNTI-Value, previousPCellId-r16 CHOICE { nrPreviousCell-r16 CGI-Info-Logging-r16, eutraPreviousCell-r16 CGI-InfoEUTRALogging } OPTIONAL, failedPCellId-r16 CHOICE { nrFailedPCellId-r16 CHOICE { cellGlobalId-r16 CGI-Info-Logging-r16, pci-arfcn-r16 PCI-ARFCN-NR-r16 }, eutraFailedPCellId-r16 CHOICE { cellGlobalId-r16 CGI-InfoEUTRALogging, pci-arfcn-r16 PCI-ARFCN-EUTRA-r16 } }, reconnectCellId-r16 CHOICE { nrReconnectCellId-r16 CGI-Info-Logging-r16, eutraReconnectCellId-r16 CGI-InfoEUTRALogging } OPTIONAL, timeUntilReconnection-r16 TimeUntilReconnection-r16 OPTIONAL, reestablishmentCellId-r16 CGI-Info-Logging-r16 OPTIONAL, timeConnFailure-r16 INTEGER (0..1023) OPTIONAL, timeSinceFailure-r16 TimeSinceFailure-r16, connectionFailureType-r16 ENUMERATED {rlf, hof}, rlf-Cause-r16 ENUMERATED {t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, beamFailureRecoveryFailure, lbtFailure-r16, bh- rlfRecoveryFailure, t312-expiry-r17, spare1}, locationInfo-r16 LocationInfo-r16 OPTIONAL, noSuitableCellFound-r16 ENUMERATED {true} OPTIONAL, ra-InformationCommon-r16 RA-InformationCommon-r16 OPTIONAL, ..., [[ csi-rsRLMConfigBitmap-v1650 BIT STRING (SIZE (96)) OPTIONAL ]], [[ lastHO-Type-r17 ENUMERATED {cho, daps, spare2, spare1} OPTIONAL, timeConnSourceDAPS-Failure-r17 TimeConnSourceDAPS-Failure-r17 OPTIONAL, timeSinceCHO-Reconfig-r17 TimeSinceCHO-Reconfig-r17 OPTIONAL, choCellId-r17 CHOICE { cellGlobalId-r17 CGI-Info-Logging-r16, pci-arfcn-r17 PCI-ARFCN-NR-r16 } OPTIONAL, choCandidateCellList-r17 ChoCandidateCellList-r17 OPTIONAL ]], [[ ra-InformationCommonList-r18 SEQUENCE (SIZE (1..4)) RA- InformationCommon-r16 OPTIONAL ]] }, eutra-RLF-Report-r16 SEQUENCE { failedPCellId-EUTRA CGI-InfoEUTRALogging, measResult-RLF-Report-EUTRA-r16 OCTET STRING, ..., [[ measResult-RLF-Report-EUTRA-v1690 OCTET STRING OPTIONAL ]] } } s P
Figure imgf000020_0001
t of
Figure imgf000021_0001
t of es,
Figure imgf000021_0002
IN ONE IMPLEMENTATION EXAMPLE IN WHICH THE UE STORES MULTIPLE RA- INFORMATIONCOMMON, THE PROCEDURAL TEXT OF TS 38.331 MAY REQUIRE THE FOLLOWING CHANGES The UE shall determine the content in the VarRLF-Report as follows: 1>clear the information included in VarRLF-Report, if any; 1>set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN); 1>set the measResultLastServCell to include the cell level RSRP, RSRQ and the available SINR, of the source PCell (in case HO failure) or PCell (in case RLF) based on the available SSB and CSI-RS measurements collected up to the moment the UE detected failure; 1> if the SS/PBCH block-based measurement quantities are available: 2>set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest SS/PBCH block RSRP is listed first if SS/PBCH block RSRP measurement results are available, otherwise the highest SS/PBCH block RSRQ is listed first if SS/PBCH block RSRQ measurement results are available, otherwise the highest SS/PBCH block SINR is listed first, based on the available SS/PBCH block based measurements collected up to the moment the UE detected failure; 1> if the CSI-RS based measurement quantities are available: 2>set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected failure; >set the ssbRLMConfigBitmap and/or csi-rsRLMConfigBitmap in measResultLastServCell to include the radio link monitoring configuration of the source PCell (in case HO failure) or PCell (in case RLF), if available; >for each of the configured measObjectNR in which measurements are available: 2> if the SS/PBCH block-based measurement quantities are available: 3>set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), 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 detected failure; 4>for each neighbour cell included, include the optional fields that are available; 2> if the CSI-RS based measurement quantities are available: 3>set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), 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 detected radio link failure; 4>for each neighbour cell included, include the optional fields that are available; 2>for each neighbour cell, if any, included in measResultListNR in measResultNeighCells: 3> if the UE supports RLF-Report for conditional handover and if the neighbour cell is one of the candidate cells for which the reconfigurationWithSync is included in the masterCellGroup in VarConditionalReconfig at the moment of the detected failure: 4>set choConfig in MeasResult2NR to the execution condition for each measId within condTriggerConfig associated to the neighbour cell within VarConditionalReconfig; 4> if the first entry of choConfig corresponds to a fulfilled execution condition at the moment of conditional reconfiguration execution, or radio link failure; or 4>if the second entry of choConfig, if available, corresponds to a fulfilled execution condition at the moment of conditional reconfiguration execution, or radio link failure: 5> set firstTriggeredEvent to the execution condition condFirstEvent corresponding to the first entry of choConfig or to the execution condition condSecondEvent corresponding to the second entry of choConfig, whichever execution condition was fulfilled first in time; 5> set timeBetweenEvents to the elapsed time between the point in time of fulfilling the condition in choConfig that was fulfilled first in time, and the point in time of fullfilling the condition in choConfig that was fulfilled second in time, if both the first execution condition corresponding to the first entry and the second execution condition corresponding to the second entry in the choConfig were fulfilled; 1>for each of the configured EUTRA frequencies in which measurements are available; 2>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, and based on measurements collected up to the moment the UE detected failure; 3>for each neighbour cell included, include the optional fields that are available; NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported. 1>set the c-RNTI to the C-RNTI used in the source PCell (in case HO failure) or PCell (in case RLF); 1>if the failure is detected due to reconfiguration with sync failure as described in 5.3.5.8.3, set the fields in VarRLF-report as follows: 2>set the connectionFailureType to hof; 2> if the UE supports RLF-Report for DAPS handover and if any DAPS bearer was configured while T304 was running: 3>set lastHO-Type to daps; 3> if radio link failure was detected in the source PCell, according to clause 5.3.10.3: 4>set timeConnSourceDAPS-Failure to the time between the initiation of the DAPS handover execution and the radio link failure detected in the source PCell while T304 was running; 4>set the rlf-Cause to the trigger for detecting the source radio link failure in accordance with clause 5.3.10.4; 2> if the UE supports RLF-Report for conditional handover and if configuration of the conditional handover is available in VarConditionalReconfig at the moment of the handover failure: 3> if the UE executed a conditional handover toward target PCell according to the condRRCReconfig of the target PCell: 4>set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed conditional handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig of the target PCell of the failed conditional handover; 3>else: 4>set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig; 3>set choCandidateCellList to include the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of each of the candidate target cells for conditional handover included in condRRCReconfig within VarConditionalReconfig at the time of the failed handover, excluding the candidate target cells included in measResulNeighCells; 2> if the UE supports RLF-Report for conditional handover and if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover: 3>set lastHO-Type to cho; 2>set the nrFailedPCellId in failedPCellId to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover; 2> include nrPreviousCell in previousPCellId and set it to the global cell identity and tracking area code of the PCell where the last RRCReconfiguration message including reconfigurationWithSync was received; 2>set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync; >else if the failure is detected due to Mobility from NR failure as described in 5.4.3.5, set the fields in VarRLF-report as follows: 2>set the connectionFailureType to hof; 2> if last MobilityFromNRCommand concerned a failed inter-RAT handover from NR to E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA (NR to EUTRA): 3>set the eutraFailedPCellId in failedPCellId to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover; 2> include nrPreviousCell in previousPCellId and set it to the global cell identity and tracking area code of the PCell where the last MobilityFromNRCommand message was received; 2>set the timeConnFailure to the elapsed time since the initialization of the handover associated to the last MobilityFromNRCommand message; >else if the failure is detected due to radio link failure as described in 5.3.10.3, set the fields in VarRLF-report as follows: 2>set the connectionFailureType to rlf; 2>set the rlf-Cause to the trigger for detecting radio link failure in accordance with clause 5.3.10.4; 2>set the nrFailedPCellId in failedPCellId to the global cell identity and the tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the PCell where radio link failure is detected; 2>if an RRCReconfiguration message including the reconfigurationWithSync was received before the connection failure: 3> if the last RRCReconfiguration message including the reconfigurationWithSync concerned an intra NR handover: 4> include the nrPreviousCell in previousPCellId and set it to the global cell identity and the tracking area code of the PCell where the last executed RRCReconfiguration message including reconfigurationWithSync was received; 4>if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a DAPS handover: 5> set lastHO-Type to daps; 4>else if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover: 5> set lastHO-Type to cho; 4>set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync; 3>else if the last RRCReconfiguration message including the reconfigurationWithSync concerned a handover to NR from E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA: 4>include the eutraPreviousCell in previousPCellId and set it to the global cell identity and the tracking area code of the E-UTRA PCell where the last RRCReconfiguration message including reconfigurationWithSync was received embedded in E-UTRA RRC message MobilityFromEUTRACommand message as specified in TS 36.331 [10] clause 5.4.3.3; 4>set the timeConnFailure to the elapsed time since reception of the last RRCReconfiguration message including the reconfigurationWithSync embedded in E-UTRA RRC message MobilityFromEUTRACommand message as specified in TS 36.331 [10] clause 5.4.3.3; 2> if configuration of the conditional handover is available in VarConditionalReconfig at the moment of declaring the radio link failure: 3>set timeSinceCHO-Reconfig to the time elapsed between the detection of the radio link failure, and the reception, in the source PCell, of the last conditionalReconfiguration including the condRRCReconfig message; 3>set choCandidateCellList to include the global cell identity and tracking area code of all the candidate target cells for conditional handover included in condRRCReconfig within VarConditionalReconfig at the time of radio link failure, excluding the candidate target cells included in measResulNeighCells; 1> if connectionFailureType is rlf and the rlf-Cause is set to randomAccessProblem or beamFailureRecoveryFailure; or 1>if connectionFailureType is rlf and the rlf-Cause is set to lbtFailure and the lbtFailureRecoveryConfig was configured for at least one BWP configured with PRACH resources; or 1>if connectionFailureType is hof and if the failed handover is an intra-RAT handover: 2> for each random access performed in different BWPs of the SpCell configured with PRACH resources, while consistent UL LBT failures were triggered and not cancelled at the time of the failure: 3> set ra-InformationCommon to include the random-access related information as described in clause 5.7.10.5 in the ra-InformationCommonList; 2> else the random access procedure is only performed in one BWP: 3>set the ra-InformationCommon to include the random-access related information as described in clause 5.7.10.5; 1> if available, set the locationInfo as in 5.3.3.7. The UE may discard the radio link failure information or handover failure information, i.e. release the UE variable VarRLF-Report, 48 hours after the radio link failure/handover failure is detected. NOTE 2: In this clause, the term 'handover failure' has been used to refer to 'reconfiguration with sync failure'. IN ANOTHER EXAMPLE IMPLEMENTATION THE UE MAY LOG ONLY THE INFORMATION CONCERNING ONE RA PROCEDURE E.G., THE LAST RA PROCEDURE. THE NON-LIMITING EXAMPLE IMPLEMENTATION IS SHOWN IN THE FOLLOWING: The UE shall determine the content in the VarRLF-Report as follows: 1>clear the information included in VarRLF-Report, if any; 1>set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN); 1>set the measResultLastServCell to include the cell level RSRP, RSRQ and the available SINR, of the source PCell (in case HO failure) or PCell (in case RLF) based on the available SSB and CSI-RS measurements collected up to the moment the UE detected failure; 1> if the SS/PBCH block-based measurement quantities are available: 2>set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest SS/PBCH block RSRP is listed first if SS/PBCH block RSRP measurement results are available, otherwise the highest SS/PBCH block RSRQ is listed first if SS/PBCH block RSRQ measurement results are available, otherwise the highest SS/PBCH block SINR is listed first, based on the available SS/PBCH block based measurements collected up to the moment the UE detected failure; 1> if the CSI-RS based measurement quantities are available: 2>set the rsIndexResults in measResultLastServCell to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected failure; 1>set the ssbRLMConfigBitmap and/or csi-rsRLMConfigBitmap in measResultLastServCell to include the radio link monitoring configuration of the source PCell (in case HO failure) or PCell (in case RLF), if available; 1>for each of the configured measObjectNR in which measurements are available: 2> if the SS/PBCH block-based measurement quantities are available: 3>set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), 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 detected failure; 4>for each neighbour cell included, include the optional fields that are available; 2> if the CSI-RS based measurement quantities are available: 3>set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), 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 detected radio link failure; 4>for each neighbour cell included, include the optional fields that are available; 2>for each neighbour cell, if any, included in measResultListNR in measResultNeighCells: 3> if the UE supports RLF-Report for conditional handover and if the neighbour cell is one of the candidate cells for which the reconfigurationWithSync is included in the masterCellGroup in VarConditionalReconfig at the moment of the detected failure: 4>set choConfig in MeasResult2NR to the execution condition for each measId within condTriggerConfig associated to the neighbour cell within VarConditionalReconfig; 4> if the first entry of choConfig corresponds to a fulfilled execution condition at the moment of conditional reconfiguration execution, or radio link failure; or 4>if the second entry of choConfig, if available, corresponds to a fulfilled execution condition at the moment of conditional reconfiguration execution, or radio link failure: 5> set firstTriggeredEvent to the execution condition condFirstEvent corresponding to the first entry of choConfig or to the execution condition condSecondEvent corresponding to the second entry of choConfig, whichever execution condition was fulfilled first in time; 5> set timeBetweenEvents to the elapsed time between the point in time of fullfilling the condition in choConfig that was fulfilled first in time, and the point in time of fullfilling the condition in choConfig that was fulfilled second in time, if both the first execution condition corresponding to the first entry and the second execution condition corresponding to the second entry in the choConfig were fulfilled; 1>for each of the configured EUTRA frequencies in which measurements are available; 2>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, and based on measurements collected up to the moment the UE detected failure; 3>for each neighbour cell included, include the optional fields that are available; NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported. 1>set the c-RNTI to the C-RNTI used in the source PCell (in case HO failure) or PCell (in case RLF); 1>if the failure is detected due to reconfiguration with sync failure as described in 5.3.5.8.3, set the fields in VarRLF-report as follows: 2>set the connectionFailureType to hof; 2> if the UE supports RLF-Report for DAPS handover and if any DAPS bearer was configured while T304 was running: 3>set lastHO-Type to daps; 3> if radio link failure was detected in the source PCell, according to clause 5.3.10.3: 4>set timeConnSourceDAPS-Failure to the time between the initiation of the DAPS handover execution and the radio link failure detected in the source PCell while T304 was running; 4>set the rlf-Cause to the trigger for detecting the source radio link failure in accordance with clause 5.3.10.4; 2> if the UE supports RLF-Report for conditional handover and if configuration of the conditional handover is available in VarConditionalReconfig at the moment of the handover failure: 3> if the UE executed a conditional handover toward target PCell according to the condRRCReconfig of the target PCell: 4>set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed conditional handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig of the target PCell of the failed conditional handover; 3>else: 4>set timeSinceCHO-Reconfig to the time elapsed between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell of the failed handover, and the reception in the source PCell of the last conditionalReconfiguration including the condRRCReconfig; 3>set choCandidateCellList to include the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of each of the candidate target cells for conditional handover included in condRRCReconfig within VarConditionalReconfig at the time of the failed handover, excluding the candidate target cells included in measResulNeighCells; 2> if the UE supports RLF-Report for conditional handover and if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover: 3>set lastHO-Type to cho; 2>set the nrFailedPCellId in failedPCellId to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover; 2> include nrPreviousCell in previousPCellId and set it to the global cell identity and tracking area code of the PCell where the last RRCReconfiguration message including reconfigurationWithSync was received; 2>set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync; >else if the failure is detected due to Mobility from NR failure as described in 5.4.3.5, set the fields in VarRLF-report as follows: 2>set the connectionFailureType to hof; 2> if last MobilityFromNRCommand concerned a failed inter-RAT handover from NR to E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA (NR to EUTRA): 3>set the eutraFailedPCellId in failedPCellId to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover; 2> include nrPreviousCell in previousPCellId and set it to the global cell identity and tracking area code of the PCell where the last MobilityFromNRCommand message was received; 2>set the timeConnFailure to the elapsed time since the initialization of the handover associated to the last MobilityFromNRCommand message; >else if the failure is detected due to radio link failure as described in 5.3.10.3, set the fields in VarRLF-report as follows: 2>set the connectionFailureType to rlf; 2>set the rlf-Cause to the trigger for detecting radio link failure in accordance with clause 5.3.10.4; 2>set the nrFailedPCellId in failedPCellId to the global cell identity and the tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the PCell where radio link failure is detected; 2>if an RRCReconfiguration message including the reconfigurationWithSync was received before the connection failure: 3> if the last RRCReconfiguration message including the reconfigurationWithSync concerned an intra NR handover: 4> include the nrPreviousCell in previousPCellId and set it to the global cell identity and the tracking area code of the PCell where the last executed RRCReconfiguration message including reconfigurationWithSync was received; 4>if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a DAPS handover: 5> set lastHO-Type to daps; 4>else if the last executed RRCReconfiguration message including reconfigurationWithSync was concerning a conditional handover: 5> set lastHO-Type to cho; 4>set the timeConnFailure to the elapsed time since the execution of the last RRCReconfiguration message including the reconfigurationWithSync; 3>else if the last RRCReconfiguration message including the reconfigurationWithSync concerned a handover to NR from E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA: 4>include the eutraPreviousCell in previousPCellId and set it to the global cell identity and the tracking area code of the E-UTRA PCell where the last RRCReconfiguration message including reconfigurationWithSync was received embedded in E-UTRA RRC message MobilityFromEUTRACommand message as specified in TS 36.331 [10] clause 5.4.3.3; 4>set the timeConnFailure to the elapsed time since reception of the last RRCReconfiguration message including the reconfigurationWithSync embedded in E-UTRA RRC message MobilityFromEUTRACommand message as specified in TS 36.331 [10] clause 5.4.3.3; 2> if configuration of the conditional handover is available in VarConditionalReconfig at the moment of declaring the radio link failure: 3>set timeSinceCHO-Reconfig to the time elapsed between the detection of the radio link failure, and the reception, in the source PCell, of the last conditionalReconfiguration including the condRRCReconfig message; 3>set choCandidateCellList to include the global cell identity and tracking area code of all the candidate target cells for conditional handover included in condRRCReconfig within VarConditionalReconfig at the time of radio link failure, excluding the candidate target cells included in measResulNeighCells; > if connectionFailureType is rlf and the rlf-Cause is set to randomAccessProblem or beamFailureRecoveryFailure; or 1>if connectionFailureType is rlf and the rlf-Cause is set to lbtFailure and the lbtFailureRecoveryConfig was configured for at least one BWP configured with PRACH resources; or 1>if connectionFailureType is hof and if the failed handover is an intra-RAT handover: 2>set the ra-InformationCommon to include the random-access related information associated to the last random access procedure performed prior to the failure, as described in clause 5.7.10.5; 1> if available, set the locationInfo as in 5.3.3.7. The UE may discard the radio link failure information or handover failure information, i.e. release the UE variable VarRLF-Report, 48 hours after the radio link failure/handover failure is detected. NOTE 2: In this clause, the term 'handover failure' has been used to refer to 'reconfiguration with sync failure'. 1 Implementation for SCGFailureInformation – SCGFAILUREINFORMATION The SCGFailureInformation message is used to provide information regarding NR SCG failures detected by the UE. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network SCGFailureInformation message -- ASN1START -- TAG-SCGFAILUREINFORMATION-START SCGFailureInformation ::= SEQUENCE { criticalExtensions CHOICE { scgFailureInformation SCGFailureInformation- IEs, criticalExtensionsFuture SEQUENCE {} } } SCGFailureInformation-IEs ::= SEQUENCE { failureReportSCG OPTIONAL, nonCriticalExtension SCGFailureInformation-v1590-IEs OPTIONAL } SCGFailureInformation-v1590-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } FailureReportSCG ::= SEQUENCE { failureType ENUMERATED { t310-Expiry, randomAccessProblem, rlc- MaxNumRetx, synchReconfigFailureSCG, scg-ReconfigFailure, srb3- IntegrityFailure, other-r16, spare1}, measResultFreqList OPTIONAL, measResultSCG-Failure OCTET STRING (CONTAINING MeasResultSCG-Failure) OPTIONAL, ..., [[ locationInfo-r16 OPTIONAL, failureType-v1610 ENUMERATED {scg-lbtFailure-r16, beamFailureRecoveryFailure-r16, t312-Expiry-r16, bh- RLF-r16, beamFailure-r17, spare3, spare2, spare1} OPTIONAL ]], [[ previousPSCellId-r17 SEQUENCE { physCellId-r17 PhysCellId, carrierFreq-r17 ARFCN-ValueNR } OPTIONAL, failedPSCellId-r17 SEQUENCE { physCellId-r17 PhysCellId, carrierFreq-r17 ARFCN-ValueNR } OPTIONAL, timeSCGFailure-r17 INTEGER (0..1023) OPTIONAL, perRAInfoList-r17 PerRAInfoList-r16 OPTIONAL ]], [[ perRAInfoList-NRU-r18 SEQUENCE (SIZE (1..4)) PerRAInfoList- r16 OPTIONAL ]] } MeasResultFreqList ::= SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2NR 5.7.3.5 ACTIONS RELATED TO TRANSMISSION OF SCGFAILUREINFORMATION MESSAGE The UE shall set the contents of the SCGFailureInformation message as follows: 1>if the UE initiates transmission of the SCGFailureInformation message due to T310 expiry: 2>set the failureType as t310-Expiry; 1>else if the UE initiates transmission of the SCGFailureInformation message due to T312 expiry: 2>set the failureType as other and set the failureType-v1610 as t312-Expiry; >else if the UE initiates transmission of the SCGFailureInformation message to provide reconfiguration with sync failure information for an SCG: 2>set the failureType as synchReconfigFailureSCG; >else if the UE initiates transmission of the SCGFailureInformation message to provide random access problem indication from SCG MAC: 2>if the random access procedure was initiated for beam failure recovery: 3>set the failureType as other and set the failureType-v1610 as beamFailureRecoveryFailure; 2>else: 3>set the failureType as randomAccessProblem; >else if the UE initiates transmission of the SCGFailureInformation message to provide indication from SCG RLC that the maximum number of retransmissions has been reached: 2>set the failureType as rlc-MaxNumRetx; >else if the UE initiates transmission of the SCGFailureInformation message due to SRB3 IP check failure: 2>set the failureType as srb3-IntegrityFailure; >else if the UE initiates transmission of the SCGFailureInformation message due to Reconfiguration failure of NR RRC reconfiguration message: 2>set the failureType as scg-reconfigFailure; >else if the UE initiates transmission of the SCGFailureInformation message due to consistent uplink LBT failures: 2>set the failureType as other and set the failureType-v1610 as scg-lbtFailure; >else if connected as an IAB-node and the SCGFailureInformation is initiated due to the reception of a BH RLF indication on BAP entity from the SCG: 2>set the failureType as other and set failureType-v1610 as bh-RLF; >else if the UE initiates transmission of the SCGFailureInformation message due to beam failure of the PSCell while the SCG is deactivated: 2>set the failureType as other and set failureType-v1610 as beamFailure; > include and set MeasResultSCG-Failure in accordance with 5.7.3.4; >for each MeasObjectNR configured by a MeasConfig associated with the MCG, and for which measurement results are available: 2> include an entry in measResultFreqList; 2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to ssb: 3>set ssbFrequency in measResultFreqList to the value indicated by ssbFrequency as included in the MeasObjectNR; 2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to csi-rs: 3>set refFreqCSI-RS in measResultFreqList to the value indicated by refFreqCSI-RS as included in the associated measurement object; 2> if a serving cell is associated with the MeasObjectNR: 3>set measResultServingCell in measResultFreqList to include the available quantities of the concerned cell and in accordance with the performance requirements in TS 38.133 [14]; 2>set the measResultNeighCellList in measResultFreqList to include the best measured cells, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected the failure, and set its fields as follows; 3>ordering the cells with sorting as follows: 4>based on SS/PBCH block if SS/PBCH block measurement results are available and otherwise based on CSI-RS; 4>using RSRP if RSRP measurement results are available, otherwise using RSRQ if RSRQ measurement results are available, otherwise using SINR; 3>for each neighbour cell included: 4>include the optional fields that are available. NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported. NOTE 2: Field measResultSCG-Failure is used to report available results for NR frequencies the UE is configured to measure by SCG RRC signalling. 1> if available, set the locationInfo as in 5.3.3.7. 1> if the UE supports SCG failure for mobility robustness optimization: 2>if the failureType is set to synchReconfigFailureSCG; or 2>if the failureType is set to randomAccessProblem and the SCG failure was declared while T304 was running: 3>set perRAInfoList to indicate the performed random access procedure related information as specified in 5.7.10.5. 3>set the failedPSCellId to the physical cell identity and carrier frequency of the target PSCell of the failed PSCell change; 3>set the previousPSCellId to the physical cell identity and carrier frequency of the source PSCell associated to the last received RRCReconfiguration message including reconfigurationWithSync for the SCG; 3>set the timeSCGFailure to the elapsed time since reception of the last RRCReconfiguration message including the reconfigurationWithSync for the SCG until declaring the SCG failure; 2> if the failureType is set to lbtFailure and the lbtFailureRecoveryConfig was configured for at least one BWP configured with PRACH resources: 3> for each random access performed in different BWPs of the SpCell configured with PRACH resources, while consistent UL LBT failures were triggered and not cancelled at the time of the failure: 4>set perRAInfoList in perRAInfoList-NRU to indicate the performed random access procedure related information as specified in 5.7.10.5. 2>else: 3>set the failedPSCellId to the physical cell identity and carrier frequency of the PSCell in which the SCG failure was declared; 3>if the last RRCReconfiguration message including the reconfigurationWithSync for the SCG was received to enter the PSCell in which the SCG failure was declared: 4>set the timeSCGFailure to the elapsed time since reception of the last RRCReconfiguration message including the reconfigurationWithSync for the SCG until declaring the SCG failure; 4>set the previousPSCellId to the physical cell identity and carrier frequency of the source PSCell associated to the last received RRCReconfiguration message including reconfigurationWithSync for the SCG; The UE shall submit the SCGFailureInformation message to lower layers for transmission. 2 Implementation for MCGFailureInformation – MCGFAILUREINFORMATION The MCGFailureInformation message is used to provide information regarding NR MCG failures detected by the UE. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network MCGFailureInformation message -- ASN1START -- TAG-MCGFAILUREINFORMATION-START MCGFailureInformation-r16 ::= SEQUENCE { criticalExtensions CHOICE { mcgFailureInformation-r16 MCGFailureInformation-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } MCGFailureInformation-r16-IEs ::= SEQUENCE { failureReportMCG-r16 FailureReportMCG-r16 OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } FailureReportMCG-r16 ::= SEQUENCE { failureType-r16 ENUMERATED {t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, t312-Expiry-r16, lbt-Failure-r16, beamFailureRecoveryFailure-r16, bh-RLF-r16, spare1} OPTIONAL, measResultFreqList-r16 MeasResultList2NR OPTIONAL, measResultFreqListEUTRA-r16 MeasResultList2EUTRA OPTIONAL, measResultSCG-r16 OCTET STRING (CONTAINING MeasResultSCG- Failure) OPTIONAL, measResultSCG-EUTRA-r16 OCTET STRING OPTIONAL, measResultFreqListUTRA-FDD-r16 MeasResultList2UTRA OPTIONAL, ... [[ perRAInfoList-NRU-r18 SEQUENCE (SIZE (1..4)) PerRAInfoList- r16 OPTIONAL ]] } } MeasResultList2UTRA ::= SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2UTRA- FDD-r16 MeasResult2UTRA-FDD-r16 ::= SEQUENCE { carrierFreq-r16 ARFCN-ValueUTRA-FDD-r16, measResultNeighCellList-r16 MeasResultListUTRA-FDD-r16 } MeasResultList2EUTRA ::= SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2EUTRA-r16 The UE shall set the contents of the MCGFailureInformation message as follows: 1>include and set failureType in accordance with 5.7.3b.3; 1>for each MeasObjectNR configured by a measConfig associated with the MCG, and for which measurement results are available: 2> include an entry in measResultFreqList; 2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to ssb: 3>set ssbFrequency in measResultFreqList to the value indicated by ssbFrequency as included in the MeasObjectNR; 2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to csi-rs: 3>set refFreqCSI-RS in measResultFreqList to the value indicated by refFreqCSI-RS as included in the associated measurement object; 2> if a serving cell is associated with the MeasObjectNR: 3>set measResultServingCell in measResultFreqList to include the available quantities of the concerned cell and in accordance with the performance requirements in TS 38.133 [14]; 2>set the measResultNeighCellList in measResultFreqList to include the best measured cells, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected the failure, and set its fields as follows; 3>ordering the cells with sorting as follows: 4>based on SS/PBCH block if SS/PBCH block measurement results are available and otherwise based on CSI-RS; 4>using RSRP if RSRP measurement results are available, otherwise using RSRQ if RSRQ measurement results are available, otherwise using SINR; 3>for each neighbour cell included: 4>include the optional fields that are available. 1>for each EUTRA frequency the UE is configured to measure by measConfig for which measurement results are available: 2>set the measResultFreqListEUTRA to include the best measured cells, ordered such that the best cell is listed first using RSRP to order the cells if RSRP measurement results are available for cells on this frequency, otherwise using RSRQ to order the cells if RSRQ measurement results are available for cells on this frequency, otherwise using SINR to order the cells, based on measurements collected up to the moment the UE detected the failure, and for each cell that is included, include the optional fields that are available; 1>for each UTRA-FDD frequency the UE is configured to measure by measConfig for which measurement results are available: 2>set the measResultFreqListUTRA-FDD to include the best measured cells, ordered such that the best cell is listed first using RSCP to order the cells if RSCP measurement results are available for cells on this frequency, otherwise using EcN0 to order the cells, based on measurements collected up to the moment the UE detected the failure, and for each cell that is included, include the optional fields that are available; 1> if the UE supports SCG failure for mobility robustness optimization: 2>if the failureType is set to lbtFailure and the lbtFailureRecoveryConfig was configured for at least one BWP configured with PRACH resources: 3> for each random access performed in different BWPs of the SpCell configured with PRACH resources, while consistent UL LBT failures were triggered and not cancelled at the time of the failure: 4>set perRAInfoList in perRAInfoList-NRU to indicate the performed random access procedure related information as specified in 5.7.10.5. 1> if the UE is in NR-DC: 2>include and set measResultSCG in accordance with 5.7.3.4; 1> if the UE is in NE-DC: 2>include and set measResultSCG-EUTRA in accordance with TS 36.331 [10] clause 5.6.13.5; NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported. NOTE 2: Field measResultSCG-Failure is used to report available results for NR frequencies the UE is configured to measure by SCG RRC signalling. NOTE 3: Field measResultSCG-EUTRA is used to report available results for E-UTRAN frequencies the UE is configured to measure by E-UTRA RRC signalling. 1> if SRB1 is configured as split SRB and pdcp-Duplication is not configured: 2>if the primaryPath for the PDCP entity of SRB1 refers to the MCG: 3>set the primaryPath to refer to the SCG. The UE shall: 1>start timer T316; 1>if SRB1 is configured as split SRB: 2>submit the MCGFailureInformation message to lower layers for transmission via SRB1, upon which the procedure ends; 1>else (i.e. SRB3 configured): 2>submit the MCGFailureInformation message to lower layers for transmission embedded in NR RRC message ULInformationTransferMRDC via SRB3 as specified in 5.7.2a.3. ***************************************************************************** [0064] Figure 2 shows an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections. [0065] Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. [0066] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 112 and/or with other network nodes or equipment in the telecommunication network 102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 102. [0067] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF). [0068] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and/or the telecommunication network 102, and may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server. [0069] As a whole, the communication system 100 of Figure 2 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. [0070] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive IoT services to yet further UEs. [0071] In some examples, the UEs 112 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may 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). [0072] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and/or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices. [0073] The hub 114 may have a constant/persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and/or schedule between the hub 114 and UEs (e.g., UE 112c and/or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and/or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 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 110b. In other embodiments, the hub 114 may be a non- dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels. [0074] Figure 3 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. [0075] 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). [0076] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input/output interface 206, a power source 208, a memory 210, a communication interface 212, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 2. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. [0077] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs). [0078] In the example, the input/output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. [0079] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and/or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied. [0080] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems. [0081] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous 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 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium. [0082] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and/or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately. [0083] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range 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. [0084] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), 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). [0085] 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. [0086] 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 200 shown in Figure 2. [0087] 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. [0088] 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. [0089] Figure 4 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). [0090] 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). [0091] 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). [0092] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300. [0093] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality. [0094] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units. [0095] The memory 304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, 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 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and/or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated. [0096] The communication interface 306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 306 comprises port(s)/terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and/or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and/or different combinations of components. [0097] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown). [0098] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port. [0099] The antenna 310, communication interface 306, and/or the processing circuitry 302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 310, the communication interface 306, and/or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment. [0100] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail. [0101] Embodiments of the network node 300 may include additional components beyond those shown in Figure 4 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300. [0102] Figure 5 is a block diagram of a host 400, which may be an embodiment of the host 116 of Figure 1, in accordance with various aspects described herein. As used herein, the host 400 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 400 may provide one or more services to one or more UEs. [0103] The host 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input/output interface 406, a network interface 408, a power source 410, and a memory 412. 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 10 and 3, such that the descriptions thereof are generally applicable to the corresponding components of host 400. [0104] The memory 412 may include one or more computer programs including one or more host application programs 414 and data 416, which may include user data, e.g., data generated by a UE for the host 400 or data generated by the host 400 for a UE. Embodiments of the host 400 may utilize only a subset or all of the components shown. The host application programs 414 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 414 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 400 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 414 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. [0105] Figure 6 is a block diagram illustrating a virtualization environment 500 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 500 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. [0106] Applications 502 (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. [0107] Hardware 504 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 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs 508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 506 may present a virtual operating platform that appears like networking hardware to the VMs 508. [0108] The VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 506. Different embodiments of the instance of a virtual appliance 502 may be implemented on one or more of VMs 508, 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. [0109] In the context of NFV, a VM 508 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 508, and that part of hardware 504 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 508 on top of the hardware 504 and corresponds to the application 502. [0110] Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 510, which, among others, oversees lifecycle management of applications 502. In some embodiments, hardware 504 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 512 which may alternatively be used for communication between hardware nodes and radio units. [0111] Figure 7 shows a communication diagram of a host 602 communicating via a network node 604 with a UE 606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 112a of Figure 2 and/or UE 200 of Figure 2), network node (such as network node 110a of Figure 2 and/or network node 300 of Figure 3), and host (such as host 116 of Figure 2 and/or host 400 of Figure 4) discussed in the preceding paragraphs will now be described with reference to Figure 6. [0112] Like host 400, embodiments of host 602 include hardware, such as a communication interface, processing circuitry, and memory. The host 602 also includes software, which is stored in or accessible by the host 602 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 606 connecting via an over-the-top (OTT) connection 650 extending between the UE 606 and host 602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 650. [0113] The network node 604 includes hardware enabling it to communicate with the host 602 and UE 606. The connection 660 may be direct or pass through a core network (like core network 106 of Figure 1) 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. [0114] The UE 606 includes hardware and software, which is stored in or accessible by UE 606 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 606 with the support of the host 602. In the host 602, an executing host application may communicate with the executing client application via the OTT connection 650 terminating at the UE 606 and host 602. 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 650 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 650. [0115] The OTT connection 650 may extend via a connection 660 between the host 602 and the network node 604 and via a wireless connection 670 between the network node 604 and the UE 606 to provide the connection between the host 602 and the UE 606. The connection 660 and wireless connection 670, over which the OTT connection 650 may be provided, have been drawn abstractly to illustrate the communication between the host 602 and the UE 606 via the network node 604, without explicit reference to any intermediary devices and the precise routing of messages via these devices. [0116] As an example of transmitting data via the OTT connection 650, in step 608, the host 602 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 606. In other embodiments, the user data is associated with a UE 606 that shares data with the host 602 without explicit human interaction. In step 610, the host 602 initiates a transmission carrying the user data towards the UE 606. The host 602 may initiate the transmission responsive to a request transmitted by the UE 606. The request may be caused by human interaction with the UE 606 or by operation of the client application executing on the UE 606. The transmission may pass via the network node 604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 612, the network node 604 transmits to the UE 606 the user data that was carried in the transmission that the host 602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 614, the UE 606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 606 associated with the host application executed by the host 602. [0117] In some examples, the UE 606 executes a client application which provides user data to the host 602. The user data may be provided in reaction or response to the data received from the host 602. Accordingly, in step 616, the UE 606 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 606. Regardless of the specific manner in which the user data was provided, the UE 606 initiates, in step 618, transmission of the user data towards the host 602 via the network node 604. In step 620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 604 receives user data from the UE 606 and initiates transmission of the received user data towards the host 602. In step 622, the host 602 receives the user data carried in the transmission initiated by the UE 606. [0118] One or more of the various embodiments improve the performance of OTT services provided to the UE 606 using the OTT connection 650, in which the wireless connection 670 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate and latency and thereby provide benefits such as reduced user waiting time, better responsiveness, and better QoE. [0119] In an example scenario, factory status information may be collected and analyzed by the host 602. As another example, the host 602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 602 may store surveillance video uploaded by a UE. As another example, the host 602 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 602 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. [0120] 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 650 between the host 602 and UE 606, 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 602 and/or UE 606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 650 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 650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 604. 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 602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 650 while monitoring propagation times, errors, etc. [0121] 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. [0122] 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. [0123] FIGURE 8 is a flowchart illustrating an example method in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 8 may be performed by UE 200 described with respect to FIGURE 3. The wireless device is operating in shared spectrum. [0124] The method begins at step 812, where the wireless device (e.g., UE 200) detects a radio link failure. [0125] At step 814, the wireless device determines a consistent LBT failure occurred in a BWP used by the wireless device and that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources. [0126] In particular embodiments, determining a LBT problem occurred in the BWP comprises determining the rlf-cause is set to lbtFailure and determining that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources comprises determining lbt-failureRecoveryConfig was configured for the BWP in which a random access procedure was performed. [0127] In particular embodiments, determining that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources comprises determining the wireless device performed a random access procedure to recover from an LBT failure. [0128] A particular advantage of the determining steps is to limit the conditional inclusion of the random-access information in the failure report to the scenarios in which the UE actually performs the random-access procedure i.e., when the UE is configured with LBT recovery configuration for a BWP with configured random access resources. [0129] At step 816, the wireless device logs random access information in a failure report. In particular embodiments, the random access information comprises random access information associated to a last random access procedure executed as part of a random access recovery procedure, random access information associated to a first random access procedure executed as part of a random access recovery procedure, a number of performed random access procedures as part of a beam failure recovery procedure, BWP identity information associated to a BWP toward which a random access procedure was performed, and/or frequency or bandwidth information of a BWP toward which a random access procedure was performed. In particular embodiments, the random access information may include any of the information described in the embodiments and examples described herein. [0130] At step 818, the wireless device receives a request from the network node to transmit a failure report to the network node. For example, the wireless device may receive the request as part of UE Information Request/Response procedure. This step is optional, and in some embodiments the method may continue to step 820 where the wireless device transmits the failure report to the network node without receiving an explicit request. [0131] At step 820, the wireless device transmits the failure report to a network node. For example, the wireless device may transmit a MCGFailureInformation or SCGFailureInformation message. In particular embodiments the wireless device may transmit the failure report according to any of the embodiments and examples described herein. [0132] Modifications, additions, or omissions may be made to method 800 of FIGURE 8. Additionally, one or more steps in the method of FIGURE 8 may be performed in parallel or in any suitable order. [0133] FIGURE 9 is a flowchart illustrating an example method in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 9 may be performed by network node 300 described with respect to FIGURE 4. [0134] The method begins at step 912, where the network node (e.g., network node 300) configures a wireless device for logging random access information associated with a consistent LBT failure for a BWP used by the wireless device and configured with random access resources. [0135] At step 914, the network node configures the wireless device to perform LBT recovery based on a random access procedure for the BWP configured with random access resources. [0136] At step 916, the network node may optionally transmit a request to the wireless device for the wireless device to transmit the failure report. In other embodiments, the method may continue to step 918. [0137] At step 918, the network node receives a failure report comprising random access information associated with LBT problems from the wireless device. In particular embodiments, the random access information comprises random access information associated to a last random access procedure executed as part of a random access recovery procedure, random access information associated to a first random access procedure executed as part of a random access recovery procedure, a number of performed random access procedures as part of a beam failure recovery procedure, BWP identity information associated to a BWP toward which a random access procedure was performed, and/or frequency or bandwidth information of a BWP toward which a random access procedure was performed. [0138] Modifications, additions, or omissions may be made to method 900 of FIGURE 9. Additionally, one or more steps in the method of FIGURE 9 may be performed in parallel or in any suitable order. [0139] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation. [0140] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described. [0141] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below. [0142] Some example embodiments are described below. Group A Embodiments 1. A method performed by a wireless device operating in shared spectrum, the method comprising: − detecting a radio link failure; − determining a listen before talk (LBT) problem occurred and that the wireless device is able to perform LBT recovery for a random access procedure; − logging random access information in a failure report; and − transmitting the failure report to a network node. 2. The method of embodiment 1, wherein the random access information comprises any one or more of the following: o A set of random-access information associated to the last random access procedure executed as part of a random access recovery procedure o A set of random access information associated to the first random access procedure executed as part of a random access recovery procedure o Multiple sets of random access information, wherein each set of random access information is associated to one of the multiple random access procedures performed in different BWPs executed during the LBT recovery procedure. o a number of performed random access procedures as part of beam failure recovery procedure o BWP identity information associated to a BWP toward which the random access procedure is performed o Frequency information of a BWP toward which the random access procedure is performed. 3. A method performed by a wireless device, the method comprising: − any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. 4. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above. 5. The method of any of the previous embodiments, further comprising: − providing user data; and − forwarding the user data to a host computer via the transmission to the base station. Group B Embodiments 6. A method performed by a base station, the method comprising: − configuring a wireless device for logging random access information associated with listen before talk (LBT) problems; − configuring the wireless device to perform LBT recovery for a random access procedure; and − receiving a failure report comprising random access information associated with LBT problems from the wireless device. The method of the previous embodiment, wherein the random access information comprises any one or more of the following: o A set of random-access information associated to the last random access procedure executed as part of a random access recovery procedure o A set of random access information associated to the first random access procedure executed as part of a random access recovery procedure o Multiple sets of random access information, wherein each set of random access information is associated to one of the multiple random access procedures performed in different BWPs executed during the LBT recovery procedure. o a number of performed random access procedures as part of beam failure recovery procedure o BWP identity information associated to a BWP toward which the random access procedure is performed o Frequency information of a BWP toward which the random access procedure is performed. A method performed by a base station, the method comprising: − any of the steps, features, or functions described above with respect to base station, either alone or in combination with other steps, features, or functions described above. The method of the previous embodiment, further comprising one or more additional base station steps, features or functions described above. The method of any of the previous embodiments, further comprising: − obtaining user data; and − forwarding the user data to a host computer or a wireless device. Group C Embodiments 11. A mobile terminal comprising: − processing circuitry configured to perform any of the steps of any of the Group A embodiments; and − power supply circuitry configured to supply power to the wireless device. 12. A base station comprising: − processing circuitry configured to perform any of the steps of any of the Group B embodiments; − power supply circuitry configured to supply power to the wireless device. 13. A user equipment (UE) comprising: − an antenna configured to send and receive wireless signals; − radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; − the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; − an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; − an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and − a battery connected to the processing circuitry and configured to supply power to the UE. 14. A communication system including a host computer comprising: − processing circuitry configured to provide user data; and − a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), − wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. The communication system of the pervious embodiment further including the base station. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. The communication system of the previous 3 embodiments, wherein: − the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and − the UE comprises processing circuitry configured to execute a client application associated with the host application. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: − at the host computer, providing user data; and − at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments. The method of the previous embodiment, further comprising, at the base station, transmitting the user data. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs any of the previous 3 embodiments. A communication system including a host computer comprising: − processing circuitry configured to provide user data; and − a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), − wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE. The communication system of the previous 2 embodiments, wherein: − the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and − the UE’s processing circuitry is configured to execute a client application associated with the host application. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: − at the host computer, providing user data; and − at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station. A communication system including a host computer comprising: − communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, − wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments. The communication system of the previous embodiment, further including the UE. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station. The communication system of the previous 3 embodiments, wherein: − the processing circuitry of the host computer is configured to execute a host application; and − the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data. The communication system of the previous 4 embodiments, wherein: − the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and − the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: − at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station. The method of the previous 2 embodiments, further comprising: − at the UE, executing a client application, thereby providing the user data to be transmitted; and − at the host computer, executing a host application associated with the client application. The method of the previous 3 embodiments, further comprising: − at the UE, executing a client application; and − at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, − wherein the user data to be transmitted is provided by the client application in response to the input data. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. The communication system of the previous embodiment further including the base station. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. The communication system of the previous 3 embodiments, wherein: − the processing circuitry of the host computer is configured to execute a host application; − the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: − at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

Claims

CLAIMS 1. A method performed by wireless device operating in shared spectrum, the method comprising: detecting (812) a radio link failure; determining (814) a consistent listen-before-talk, LBT, failure occurred in a bandwidth part, BWP, used by the wireless device and that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources; logging (816) random access information in a failure report; and transmitting (820) the failure report to a network node.
2. The method of claim 1, wherein the random access information comprises random access information associated to a last random access procedure executed as part of a random access recovery procedure prior to detecting the radio link failure.
3. The method of any one of claims 1-2, wherein the random access information comprises random access information associated to a first random access procedure executed as part of a random access recovery procedure.
4. The method of any one of claims 1-3, wherein the random access information comprises a number of performed random access procedures in different BWPs as part of a beam failure recovery procedure.
5. The method of any one of claims 1-4, wherein the random access information comprises BWP identity information associated to a BWP toward which a random access procedure was performed.
6. The method of any one of claims 1-5, wherein the random access information comprises frequency or bandwidth information of a BWP toward which a random access procedure was performed.
7. The method of any one of claims 1-6, further comprising receiving (818) a request from the network node to transmit the failure report to the network node.
8. The method of any one of claims 1-7, wherein determining a LBT problem occurred in the BWP comprises determining the rlf-cause is set to lbtFailure and determining that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources comprises determining lbt- failureRecoveryConfig was configured for the BWP in which a random access procedure was performed.
9. The method of any one of claims 1-8, wherein determining that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources comprises determining the wireless device performed a random access procedure to recover from an LBT failure.
10. A wireless device (200) comprising processing circuitry (202) operable to: detect a radio link failure; determine a consistent listen-before-talk, LBT, failure occurred in a bandwidth part, BWP, used by the wireless device and that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources; log random access information in a failure report; and transmit the failure report to a network node.
11. The wireless device of claim 10, wherein the random access information comprises random access information associated to a last random access procedure executed as part of a random access recovery procedure prior to detecting the radio link failure.
12. The wireless device of any one of claims 10-11, wherein the random access information comprises random access information associated to a first random access procedure executed as part of a random access recovery procedure.
13. The wireless device of any one of claims 10-12, wherein the random access information comprises a number of performed random access procedures in different BWPs as part of a beam failure recovery procedure.
14. The wireless device of any one of claims 10-13, wherein the random access information comprises BWP identity information associated to a BWP toward which a random access procedure was performed.
15. The wireless device of any one of claims 10-14, wherein the random access information comprises frequency or bandwidth information of a BWP toward which a random access procedure was performed.
16. The wireless device of any one of claims 10-15, the processing circuitry further operable to receive a request from the network node to transmit the failure report to the network node.
17. The wireless device of any one of claims 10-16, wherein the processing circuitry is operable to determine a LBT problem occurred in the BWP by determining the rlf-cause is set to lbtFailure and determining that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources comprises determining lbt-failureRecoveryConfig was configured for the BWP in which a random access procedure was performed.
18. The wireless device of any one of claims 10-17, wherein the processing circuitry is operable to determine that the wireless device is configured to perform LBT recovery based on a random access procedure for the BWP configured with random access resources by determining the wireless device performed a random access procedure to recover from an LBT failure.
19. A method performed by a network node, the method comprising: configuring (912) a wireless device for logging random access information associated with a consistent listen-before-talk, LBT, failure for a bandwidth part, BWP, used by the wireless device and configured with random access resources; configuring (914) the wireless device to perform LBT recovery based on a random access procedure for the BWP configured with random access resources; and receiving (918) a failure report comprising random access information associated with LBT problems from the wireless device.
20. The method of claim 19, further comprising transmitting (916) a request to the wireless device for the wireless device to transmit the failure report.
21. The method of any one of claims 19-20, wherein the random access information comprises random access information associated to a last random access procedure executed as part of a random access recovery procedure.
22. The method of any one of claims 19-21, wherein the random access information comprises random access information associated to a first random access procedure executed as part of a random access recovery procedure.
23. The method of any one of claims 19-22, wherein the random access information comprises a number of performed random access procedures in different BWPs as part of a beam failure recovery procedure.
24. The method of any one of claims 19-23, wherein the random access information comprises BWP identity information associated to a BWP toward which a random access procedure was performed.
25. The method of any one of claims 19-24, wherein the random access information comprises frequency or bandwidth information of a BWP toward which a random access procedure was performed.
26. A network node (300) comprising processing circuitry (302), the processing circuitry operable to: configure a wireless device for logging random access information associated with a consistent listen-before-talk, LBT, failure for a bandwidth part, BWP, used by the wireless device and configured with random access resources; configure the wireless device to perform LBT recovery based on a random access procedure for the BWP configured with random access resources; and receive a failure report comprising random access information associated with LBT problems from the wireless device.
27. The network node of claim 26, the processing circuitry further operable to transmit a request to the wireless device for the wireless device to transmit the failure report.
28. The network node of any one of claims 26-27, wherein the random access information comprises random access information associated to a last random access procedure for different BWPs executed as part of a random access recovery procedure.
29. The network node of any one of claims 26-27, wherein the random access information comprises random access information associated to a first random access procedure executed as part of a random access recovery procedure.
30. The network node of any one of claims 26-29, wherein the random access information comprises a number of performed random access procedures as part of a beam failure recovery procedure.
31. The network node of any one of claims 26-30, wherein the random access information comprises BWP identity information associated to a BWP toward which a random access procedure was performed.
32. The network node of any one of claims 26-31, wherein the random access information comprises frequency or bandwidth information of a BWP toward which a random access procedure was performed.
PCT/SE2023/051107 2022-11-02 2023-11-02 Indicating lbt results in failure report WO2024096801A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263381993P 2022-11-02 2022-11-02
US63/381,993 2022-11-02

Publications (1)

Publication Number Publication Date
WO2024096801A1 true WO2024096801A1 (en) 2024-05-10

Family

ID=88731453

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/051107 WO2024096801A1 (en) 2022-11-02 2023-11-02 Indicating lbt results in failure report

Country Status (1)

Country Link
WO (1) WO2024096801A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220272585A1 (en) * 2019-08-14 2022-08-25 Vivo Mobile Communication Co.,Ltd. Method for reporting state information, terminal, and network device

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022031366A1 (en) * 2020-08-07 2022-02-10 Qualcomm Incorporated Channel access failure information on shared spectrum

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022031366A1 (en) * 2020-08-07 2022-02-10 Qualcomm Incorporated Channel access failure information on shared spectrum

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
3GPP TS 36.300
3GPP TS 36.331
3GPP TS 38.300
ERICSSON (SUMMARY RAPPORTEUR): "Pre-meeting summary of 8.13.5 SON for NR-U (Ericsson)", vol. RAN WG2, no. electronic; 20221010 - 20221019, 21 October 2022 (2022-10-21), XP052264107, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_119bis-e/Docs/R2-2210799.zip R2-2210799 - Summary of 8.13.5 SON for NRU_v02_Rapp.docx> [retrieved on 20221021] *
LENOVO: "Discussion on MRO for NR-U", vol. RAN WG2, no. Online; 20221010 - 20221019, 30 September 2022 (2022-09-30), XP052263282, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_119bis-e/Docs/R2-2209958.zip R2-2209958 Discussion on MRO for NR-U.docx> [retrieved on 20220930] *
NEC: "Corrections on the field descriptions of IEs for CEF-report and RLF-report request", vol. RAN WG2, no. electronic; 20211101 - 20211112, 22 October 2021 (2021-10-22), XP052066697, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_116-e/Docs/R2-2110252.zip R2-2110252 38331_CR on the field descriptions of IEs for CEF and RLF request.docx> [retrieved on 20211022] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220272585A1 (en) * 2019-08-14 2022-08-25 Vivo Mobile Communication Co.,Ltd. Method for reporting state information, terminal, and network device

Similar Documents

Publication Publication Date Title
EP4381884A1 (en) Random access partitioning and random access report
US20240214849A1 (en) Relaxed Measurement Mode of Operation when UE Performs High-Priority Actions
US20240195593A1 (en) Methods, Devices and Computer Program Products for Exploiting Predictions for Capacity and Coverage Optimization
WO2023014255A1 (en) Event-based qoe configuration management
WO2024096801A1 (en) Indicating lbt results in failure report
US20240340724A1 (en) Radio Link Failure Report Enhancements for Handover Failure
US20240306079A1 (en) Logging Different Failure Types for On-Demand System Information Request Procedures
US20240267972A1 (en) Prediction and Proactive Handling of Radio Link Failures
WO2022264090A1 (en) Logging and reporting of aerial ue-specific information
WO2022238838A1 (en) End marker for sdt
US20240214808A1 (en) Security Parameter Updates during Cell-Reselection for NR SDT
US20240196274A1 (en) Methods for Mobility Setting Adjustment based on Predictions
WO2024030065A1 (en) Reporting of successful reconfiguration with sync (spcell change) involving lbt issues
US20240276320A1 (en) Handling of rejection of candidate target cells for conditional pscell change
WO2023062509A1 (en) Temporary reference signal-based secondary cell activation via radio resource control
WO2024035306A1 (en) Conditional handover configuration storage
WO2023153975A1 (en) Methods and devives for conditional inclusion of random access information in secondary cell group (scg) failure information n
WO2024035288A1 (en) On ho type information associated to voice fallback handover
WO2023132782A1 (en) Supervision timers for successful handover reporting
WO2024043825A1 (en) Methods and apparatus for including information concerning the selected cell (suitable or acceptable cell) in a failure report
WO2023153993A1 (en) Logging and reporting multiple random access procedure information while performing dual active protocol stack handover
WO2024035307A1 (en) Handling failures while having conditional handover configuration
EP4437753A1 (en) Logged mdt reporting involving inter-rat mobility
WO2024028814A1 (en) Assistance information from the ue on how qoe is affected by network sleep
WO2023014259A1 (en) Optimized reporting of rlf information in case of consecutive connection failures

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23801947

Country of ref document: EP

Kind code of ref document: A1