Control Plane Aspects of Dual Active Protocol Stack Handover Reporting

Enhanced DAPS handover reporting systems address information loss and failure analysis in DAPS scenarios, improving network performance by providing detailed failure reports for optimized handover parameter adjustments.

JP7579425B2Active Publication Date: 2024-11-07TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2023507583
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-08-06
Filing Date
2021-06-29
Publication Date
2024-11-07
Estimated Expiration
2041-06-29

AI Technical Summary

Technical Problem

Existing DAPS handover technologies in wireless communication systems face issues with information loss during handover failures, particularly in dual active protocol stack (DAPS) scenarios, leading to incomplete reporting of handover failures and suboptimal network parameter adjustments.

Method used

Enhanced DAPS handover reporting mechanisms that include storing and transmitting detailed information about DAPS handover failures and radio link failures to network nodes, allowing for improved analysis of failure causes and optimization of handover parameters.

Benefits of technology

Prevents information loss during handover failures, enables accurate identification of failure reasons, and facilitates proactive network adjustments to enhance handover performance and reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007579425000001
    Figure 0007579425000001
  • Figure 0007579425000002
    Figure 0007579425000002
  • Figure 0007579425000003
    Figure 0007579425000003
Patent Text Reader

Abstract

A method implemented by a wireless device includes declaring a radio link failure (RLF) in a source cell of a source network node during a dual active protocol stack handover (DAPS HO) from a source cell of the source network node to a target cell of the target network node. The wireless device stores information related to the DAPS HO and information related to the RLF. The wireless device transmits the information to an access node.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates generally to wireless communications, and more particularly to systems and methods relating to control plane aspects of Dual Active Protocol Stack (DAPS) handover reporting. [Background technology]

[0002] A simplified Third Generation Partnership Project (3GPP) wireless communication system is shown in Figure 1 and includes a user equipment (UE) that communicates with one or more access nodes that are connected to a network node, the access nodes being part of a wireless access network.

[0003] In a wireless communication system according to the 3GPP Evolved Packet System (EPS) standard specification (also called Long Term Evolution (LTE) or 4th Generation (4G)) as specified in 3GPP TS36.300 v.16.2.0 and related specifications, the access node generally corresponds to an Evolved Node B (eNB) and the network node generally corresponds to either a Mobility Management Entity (MME) and / or a Serving Gateway (SGW). The eNB is part of a radio access network, which in this case is an Enhanced Universal Terrestrial Radio Access Network (E-UTRAN), and the MME and SGW are both part of an Evolved Packet Core Network (EPC). The eNBs are interconnected via an X2 interface and connected to the EPC via an S1 interface, more specifically to the MME via S1-C and to the SGW via S1-U.

[0004] On the other hand, in a wireless communication system according to the 3GPP 5G System (5GS) standard specification (also called New Radio (NR) or 5th Generation (5G)) as specified in 3GPP TS38.300 v.16.2.0 and related specifications, the access node generally corresponds to a 5G Node B (gNB), and the network node generally corresponds to either an Access and Mobility Management Function (AMF) and / or a User Plane Function (UPF). The gNB is part of a radio access network, which in this case is a NG-RAN (Next Generation Radio Access Network), and both the AMF and the UPF are part of a 5G Core Network (5GC). The gNBs are interconnected via an Xn interface and connected to the 5GC via an NG interface, more specifically to the AMF via an NG-C and to the UPF via an NG-U.

[0005] To support fast mobility between NR and LTE and to avoid core network changes, LTE eNBs can also be connected to 5GC via NG-U / NG-C and support the Xn interface. eNBs connected to 5GC are called Next Generation eNBs (ng-eNBs) and are considered part of the Next Generation Radio Access Network (NG-RAN). LTE connected to 5GC is not further described herein, but it should be noted that most of the solutions / features described herein for LTE and NR also apply to LTE connected to 5GC. As used herein, the term LTE is used without further specification to refer to LTE-EPC.

[0006] Mobility in RRC_CONNECTED in LTE and NR Mobility in the RRC_CONNECTED state is also known as handover. The purpose of handover is, for example, to move a UE by mobility from a source access node using a source radio connection (also known as source cell connection) to a target access node using a target radio connection (also known as target cell connection). The source radio connection relates to a source cell controlled by the source access node. The target radio connection relates to a target cell controlled by the target access node. Thus, in other words, during handover, the UE moves from a source cell to a target cell. The source access node or source cell may be referred to as the "source" and the target access node or target cell may be referred to as the "target".

[0007] In some cases, the source and target access nodes are different nodes, such as different eNBs or gNBs. These cases are also referred to as inter-node, inter-eNB or inter-gNB handover. In other cases, the source and target access nodes are the same node, such as the same eNB and gNB. These cases are also referred to as intra-node, intra-eNB or intra-gNB handover, covering the case where the source and target cells are controlled by the same access node. In still other cases, the handover is performed within the same cell (and therefore within the same access node that controls that cell), which is also referred to as intra-cell handover.

[0008] It should therefore be understood that source access node and target access node refer to the roles served by a given access node during handover of a particular UE. For example, a given access node may act as a source access node during handover of one UE, but the access node also acts as a target access node during handover of a different UE. Also, in case of intranode or intracell handover of a given UE, the same access node acts as both source access node and target access node for that UE.

[0009] An RRC_CONNECTED UE in E-UTRAN or NG-RAN may be configured by the network to perform measurements of the serving cell and neighboring cells, and based on the measurement report sent by the UE, the network may determine to perform a handover of the UE to the neighboring cell. The network then sends a handover command message to the UE. In LTE, this message is an RRC connection reconfiguration message with a field called mobilityControlInfo. In NR, this message is an RRC reconfiguration message with a reconfigurationWithSync field.

[0010] These reconfigurations are in fact prepared by the target access node upon request from the source access node (via the X2 or S1 interface in case of EUTRA-EPC, or via the Xn or NG interface in case of NG-RAN-5GC) and take into account the existing RRC configuration and UE capabilities provided in the request from the source access node and its own capabilities and resource situation in the intended target cell and the target access node. The reconfiguration parameters provided by the target access node include information required by the UE to access the target access node, such as, for example, the random access configuration, the new C-RNTI allocated by the target access node, and security parameters enabling the UE to calculate new security keys related to the target access node, so that once the UE has accessed the target access node, it can send a handover complete message (in LTE, the RRC Connection Reconfiguration Complete message, and in NR, the RRC Reconfiguration Complete message) on SRB1 encrypted and integrity protected based on the new security key.

[0011] FIG. 2 shows the signaling flow between a UE, a source access node (also known as a source gNB, source eNB or source cell), and a target access node (also known as a target gNB, target eNB or target cell) during a handover procedure, using LTE as an example.

[0012] In detail, in step 1, a measurement report is sent from the UE to the source eNB. Then, user data is exchanged between the UE and the source eNB and between the source eNB and the SGW. In step 2, the source eNB performs a handover (HO) decision. In step 3, the source eNB sends a handover request to the target eNB. In step 4, the target eNB sends an HO request acknowledgement to the source eNB. In step 5, the source eNB sends an RCC connection reconfiguration message to the UE. In step 6, the UE detaches from the source cell. In step 7, the source eNB sends an SN status transfer message to the target eNB. Then, data is forwarded from the source eNB to the target eNB. In step 8, random access is performed between the UE and the target eNB. In step 9, an RRC connection reconfiguration complete message is sent from the UE to the target eNB. Then, user data is exchanged between the UE and the target eNB. In step 10, the target eNB sends a path switch request to the MME. In step 11, the MME and the SGW exchange path switching related signaling. After that, user data is exchanged between the target eNB and the SGW, and the SGW sends an end marker to the target eNB, which then forwards the end marker to the source eNB, which then returns the end marker to the target eNB. In step 12, the target eNB sends a path switching request acknowledgement to the MME. The target eNB then sends a UE context release message to the source eNB in ​​step 13.

[0013] Depending on the required Quality of Service (QoS), either seamless or lossless handover is performed for each user plane radio bearer accordingly, as described in the following subsections.

[0014] Seamless Handover Seamless handover applies to user plane radio bearers mapped on Radio Link Control (RLC) Unacknowledged Mode (UM). These types of data are generally reasonably tolerant to loss but not very tolerant to delay (e.g., voice services). Therefore, seamless handover is designed to minimize complexity and delay, but may result in the loss of some Packet Data Convergence Protocol (PDCP) Service Data Units (SDUs).

[0015] At handover, for radio bearers to which seamless handover applies, PDCP entities including header compression contexts are reset and the count values ​​are set to 0. There is no security reason to maintain the count values ​​anyway, since new keys are generated at handover. PDCP SDUs at the UE for which transmission has not yet started will be transmitted to the target access node after handover. At the source access node, PDCP SDUs that have not yet been transmitted can be forwarded to the target access node via the X2 / Xn interface. PDCP SDUs for which transmission has already started but not been successfully received will be lost. This minimizes complexity, since no context (i.e. configuration information) needs to be transferred between the source and target access nodes at handover.

[0016] Lossless Handover Based on the sequence number (SN) added to the PDCP data packet data units (PDUs), it is possible to guarantee in-order delivery during handover and even provide a fully lossless handover capability, performing retransmission of PDCP SDUs whose reception has not yet been acknowledged prior to the handover. This lossless handover capability is primarily used for delay-tolerant services such as file downloads, where the loss of one PDCP SDU can cause a sudden reduction in the data rate due to the Transmission Control Protocol (TCP) reaction.

[0017] Lossless handover applies for user plane radio bearers mapped on the RLC acknowledged mode (AM). When RLC AM is used, PDCP SDUs that have been transmitted but not yet acknowledged by the RLC layer are stored in a retransmission buffer in the PDCP layer.

[0018] To ensure lossless handover in the downlink (DL), the source access node forwards DL PDCP SDUs stored in a retransmission buffer, as well as fresh DL PDCP SDUs received from the gateway, to the target access node for (re)transmission. The source access node receives an indication from the core network gateway (SGW in LTE / EPC, UPF in LTE / 5GC and NR) indicating the last packet (the so-called "end marker" packet) to be sent to the source access node. The source access node also forwards this indication to the target access node, so that the target access node knows when it can start transmitting packets received directly from the gateway.

[0019] To ensure lossless handover in the uplink (UL), the UE retransmits UL PDCP SDUs stored in the PDCP retransmission buffer at the target access node. The retransmission is triggered by the PDCP re-establishment performed upon receipt of the handover command. The source access node will forward all PDCP SDUs received out of order to the target access node after decryption and restoration. Thus, the target access node can reorder the PDCP SDUs received from the source access node and the retransmitted PDCP SDUs received from the UE based on the PDCP SN maintained during the handover and deliver them to the gateway in the correct order.

[0020] An additional feature of lossless handover is the so-called selective retransmission. In some cases it may happen that a PDCP SDU is successfully received but the corresponding RLC acknowledgement is not successfully received. In this case, after the handover there may be unnecessary retransmissions initiated by the UE or the target access node based on an incorrect status received from the RLC layer. To avoid these unnecessary retransmissions, PDCP status reports may be sent from the target access node to the UE and from the UE to the target access node. Whether a PDCP status report should be sent after the handover is configured independently for each radio bearer and for each direction.

[0021] Rel-16 Dual Active Protocol Stack (DAPS) Handover To address the shortcomings of Rel-14 MBB and achieve interruption times of around 0 ms, an enhanced version of Make-Before-Break (MBB), also known as Dual Active Protocol Stack (DAPS) handover, is specified for Rel-16 for both LTE and NR.

[0022] DAPS handover is defined as a handover procedure in which the UE maintains the source gNB connection after reception of the RRC message for handover (i.e., RRC reconfiguration with reconfigurationWithSync for the Master Cell Group (MCG)) and until it releases the source cell after successful random access to the target gNB.

[0023] During DAPS handover, the UE is assumed to be capable of transmitting and receiving simultaneously from the source and target cells. In practice, this may require the UE to be equipped with dual Tx / Rx chains. Dual Tx / Rx chains also potentially allow DAPS handover to be supported in other handover scenarios, such as inter-frequency handover.

[0024] FIG. 3 shows an example of DAPS inter-node handover in the case of LTE. In detail, in step 1, a measurement report is sent from the UE to the source eNB. Then, user data is exchanged between the UE and the source eNB, and between the source eNB and the SGW. In step 2, the source eNB performs handover (HO) decision. In step 3, the source eNB sends a handover request to the target eNB. In step 4, the target eNB sends an HO request acknowledgement to the source eNB. In step 5, the source eNB sends an RCC connection reconfiguration message to the UE. In step 6, the source eNB sends an SN status transfer message to the target eNB. Then, data is forwarded from the source eNB to the target eNB, and user data is exchanged between the UE and the source eNB, and between the source eNB and the target eNB. In step 7, random access is performed between the UE and the target eNB. In step 8, an RRC connection reconfiguration complete message is sent from the UE to the target eNB. Then, user data is exchanged between the UE and the target eNB. In step 9, the target eNB sends a path switch request to the MME. In step 10, the MME and the SGW exchange path switch related signaling. After that, user data is exchanged between the target eNB and the SGW, and the SGW sends an end marker to the target eNB, which then forwards the end marker to the source eNB, which then returns the end marker to the target eNB. In step 11, the MME sends a path switch request acknowledgement to the target eNB. The target eNB then sends a UE context release message to the source eNB in ​​step 12. In step 13, the UE releases the source cell.

[0025] Please note that in step 5, upon receiving an RRC reconfiguration with "DAPS HO" indication in the handover command (set per bearer), e.g. reconfigurationWithSync for MCG, the UE maintains a connection to the source cell associated with the source access node while establishing a connection to the target cell associated with the target access node (for DAPS configured bearers). That is, the UE can send and receive DL / UL user plane data via the source access node during steps 5-8 without interruption for the respective bearers. Also, after step 8, the UE has a target link available for UL / DL user plane data transmission, similar to a normal HO procedure.

[0026] The DAPS configuration for a given bearer is provided as part of the RadioBearerConfig for each DRB for which DAPS should be configured, as described in TS38.331 v.16.1.0, and the RadioBearerConfig IE is included during RRC reconfiguration with reconfigurationWithSync for the MCG.

[0027] In case of DAPS handover, the UE continues downlink user data reception from the source gNB until it releases the source cell, i.e., a daps-SourceRelease message sent by the target, and continues uplink user data transmission to the source gNB until a successful random access procedure to the target gNB. To do that, the UE should continue performing Radio Link Monitoring (RLM) with respect to the source cell for the entire duration of the handover, i.e., until an RRC Reconfiguration Complete containing HO completion information is sent. That implies, for example, that the UE should continue monitoring for possible out-of-sync indications, whether RLC retransmissions with the source exceed a threshold, etc. Obviously, if an RLF occurs in the source cell while performing DAPS, the UE releases the source connection, but the UE can continue the DAPS HO to the target.

[0028] As explained before, a UE with DAPS HO configured can continue UL transmission towards the source cell until the handover is completed at the target, i.e. until an RRC Reconfiguration Complete is sent to the target. In DL, instead, the source network node (e.g. source gNode B) can continue sending DL data until the source configuration release conveyed in the daps-SourceRelease message sent by the target (after receiving the RRC Reconfiguration Complete) is received by the UE. Thus, UL data transmission towards the source cell will not be extended beyond the handover completion, although some UL transmission towards the source cell, such as Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) / Negative Acknowledgement (NACK) and other possible Layer 1 control signaling, should be performed towards the source cell after the handover completion.

[0029] The RRC triggered handover mechanism, except for DAPS handover, requires the UE to at least reset the MAC entity and re-establish the RLC, where, upon receipt of the handover command, the UE: - creating a MAC entity for the target (i.e. a different / new MAC entity), - for each Data Radio Bearer (DRB) configured with DAPS, establish an RLC entity for the target and an associated Dedicated Traffic Channel (DTCH) logical channel; - for a DRB with DAPS configured, reconfiguring separate Security and Robust Header Compression (ROHC) functions for the source and target in the PDCP entity and associating them with the RLC entities configured by the source and target, respectively; - Preserve the rest of the source configuration until the source is released.

[0030] For a DRB with DAPS configured, the source gNB does not stop sending downlink packets until the source gNB receives a handover success message from the target gNB. In RRC, UE actions are specified in sections 5.3.5.5.2, 5.3.5.5.4, and 5.3.5.5.5 in 3GPP TS38.331 v.16.1.0.

[0031] For a DRB with DAPS configured, downlink PDCP SDUs are forwarded with the sequence number (SN) assigned by the source node (gNB) until the SN allocation is handed over to the target gNB (which only happens later in the execution procedure).

[0032] In step 6 of FIG. 3, the source access node sends an SN Status Transfer message to the target access node indicating the UL PDCP receiver status and the SN of the first forwarded DL PDCP SDU. The uplink PDCP SN receiver status includes at least the PDCP SN of the first lost UL SDU and may include a bitmap of the reception status of any out-of-order UL SDUs that the UE needs to retransmit in the target cell. The SN Status Transfer message also includes the Hyperframe Number (HFN) of the first lost UL SDU as well as the HFN DL status of the count storage at the target access node. In other words, for a DRB with DAPS configured, the source access node (or simply the source gNB) first sends an Early Status Transfer message. The DL count value conveyed in the Early Status Transfer message indicates the PDCP SN and HFN of the first PDCP SDU that the source gNB forwards to the target gNB. The source gNB does not stop allocating SNs to downlink PDCP SDUs until the source gNB sends an SN Status Transfer message to the target gNB in ​​step 8b.

[0033] Upon successful connection setup with the target access node, i.e. after sending the handover complete message in step 8 of FIG. 3, the UE maintains two data links (except in the UL where the UE uses only the target after successful random access), one to the source access node and one to the target access node. After step 8, the UE transmits UL user plane data on the target access node similar to a normal HO procedure using the target access node security key and compression context. Thus, there is no need for simultaneous UL user data transmission to both nodes, which avoids UE power splitting between the two nodes and further simplifies the UE implementation. In case of intra-frequency handover, transmitting UL user plane data to one node at a time also reduces UL interference, which increases the likelihood of successful decoding on the network side.

[0034] The UE needs to maintain the security and compression context for both the source and target access nodes until the source link is released. The UE can differentiate the security / compression context to be used for a PDCP PDU based on the cell in which the PDU is transmitted.

[0035] To avoid packet duplication, the UE may send a PDCP status report indicating the last received PDCP SN together with the handover complete message in step 408. Based on the PDCP status report, the target access node may avoid sending duplicate PDCP packets (i.e. PDCP PDUs with the same sequence number) to the UE, i.e. PDCP packets that have already been received by the UE in the source cell.

[0036] The release of the source cell in step 13 of FIG. 3 may be triggered, for example, by an explicit message from the target access node (not shown in the figure) or by some other event, such as expiry of a release timer.

[0037] As an alternative to the source access node initiating packet data forwarding after step 5 of FIG. 3 (i.e. after sending a handover command to the UE, also known as “early packet forwarding”), the target access node may instruct the source access node when to start packet data forwarding. For example, packet data forwarding may start at a later stage, when a link to the target cell is established, e.g. after the UE performs random access in the target cell, or when the UE sends an RRC connection reconfiguration complete message to the target access node (also known as “later packet forwarding”). By initiating packet data forwarding at a later stage at the source access node, the number of duplicated PDCP SDUs received by the UE from the target cell will potentially be smaller, thereby somewhat reducing DL latency. However, initiating packet data forwarding at a later stage is also a trade-off between robustness and reduced latency, e.g. if the connection between the UE and the source access node is lost before the connection to the target access node is established. In such a case, there will be a short interruption in DL data transfer to the UE.

[0038] FIG. 4 shows the protocol stack on the UE side in a DAPS handover.

[0039] Each user plane radio bearer has an associated PDCP entity, which has two associated RLC entities, two associated MACs, and two associated PHYs, one each for the source cell and the target cell. The PDCP entities use different security keys and ROHC contexts for the source and target cells, but the SN allocation (for UL transmission) and reordering / duplication detection (for DL ​​reception) are common. The PDCP entity performs SN allocation for UL and reordering / duplication detection for DL.

[0040] Note that for NR, there is an additional protocol layer above PDCP called Service Data Adaptation Protocol (SDAP) that is responsible for mapping QoS flows to bearers. This layer is not shown in Figure 4 and will not be described further herein.

[0041] DAPS handover failure In NR, a timer-based handover failure procedure is supported (i.e., the UE starts timer T304 upon receiving an RRC reconfiguration with reconfiguration with synchronization, stops the timer on success, and declares a handover failure upon expiry). To recover from a handover failure, the RRC connection re-establishment procedure is used.

[0042] However, when DAPS HO fails, the UE has the possibility to fall back to the source cell configuration without triggering RRC connection re-establishment if the source link is not released, resumes the connection with the source cell and reports DAPS HO failure via the source. Obviously, such fallback to the source cell can only occur if the RLF for the source cell has not yet been declared at the time T304 expires. When the UE falls back to the source cell, it issues failure information to the source cell for the UE to indicate that the DAPS HO towards the target has failed.

[0043] Otherwise, if an RLF with respect to the source cell has already occurred at the time that the DAPS handover to the target fails, i.e., at the time that T304 expires, the UE selects a third cell different from the source and target for re-establishment. This feature is described in 3GPP TS38.331 v16.1.0, sections 5.3.5.8.3 and 5.7.5.

[0044] Radio Link Monitoring (RLM) in LTE and NR Radio Link Monitoring (RLM) is a procedure in RRC_CONNECTED to track the radio link state to support the determination of whether RLF should be declared and to enable appropriate steps to be taken if RLF is declared.

[0045] Details regarding RLM for LTE are further specified in 3GPP TS36.133 v.16.6.0 section 7.11 and 3GPP TS36.213 v.16.2.0 section 4.2.1. Details regarding radio link monitoring for NR are further specified in 3GPP TS38.133 v.16.4.0 section 8.1 and 3GPP TS38.213 v.16.2.0 section 5. The main principles for RLM are similar for LTE and NR. As part of this RLM, the physical layer in the UE performs quality measurements on the radio link on defined reference signals and provides "out of sync" and "in sync" indications to the RRC layer.

[0046] Threshold as a criterion for providing an "out of sync" indication Qout is defined. When the quality falls below this threshold, the downlink radio link cannot be received reliably, which by default corresponds to a 10% block error rate of a hypothetical Physical Downlink Control Channel (PDCCH) transmission.

[0047] A threshold Q is used as the criterion for providing an "in sync" indication. in When the quality exceeds this threshold, the downlink radio link quality is defined as Q out , which by default corresponds to a 2% block error rate of a hypothetical PDCCH transmission.

[0048] Threshold Q out and Q in The details of how this is defined are further specified in TS 36.133 v.16.6.0 and TS 38.133 v.16.4.0 for LTE and NR, respectively.

[0049] In LTE, when in non-discontinuous reception (non-DRX) mode, the physical layer determines the threshold Q out and Q in The physical layer evaluates the radio link quality to the radio resource control (RRC) layer. out indicates “out of sync” when the wireless link quality is worse than the threshold Q in In LTE, when operating in discontinuous reception (DRX) mode, the physical layer in the UE shall assess the radio link quality at least once every DRX period.

[0050] In NR, the physical layer in the UE assesses the radio link quality once every indication period. When in non-DRX mode operation, the UE determines the indication period as the maximum between the shortest periodicity for the radio link monitoring resources and 10 ms. When in DRX mode operation, the UE determines the indication period as the maximum between the shortest periodicity for the radio link monitoring resources and the DRX period.

[0051] FIG. 5 shows the "out of sync" and "in sync" indications exchanged between the UE physical layer and the UE RRC layer. The "out of sync" and "in sync" indications from the physical layer are processed by the RRC layer (this processing is also known as "Layer 3 filtering" or "L3 filtering"). When a certain number of consecutive "out of sync" indications (known as parameter / counter N310) are generated by radio link monitoring in the physical layer, the RRC layer starts a timer (usually known as timer T310). If the physical layer then provides a certain number of consecutive "in sync" indications (known as parameter N311) while this timer is running, the UE recovers from the synchronization problem and stops timer T310.

[0052] When timer T310 expires, an RLF state is declared and the UE performs cell selection and RRC connection re-establishment. During cell selection, the UE finds a suitable cell that satisfies criterion S in 3GPP TS36.304 v.16.1 (for LTE cells) or in 3GPP TS38.304 v16.1 (for NR cells). According to those specifications, cell selection criterion S is met when Srxlev>0 and Squal>0. How Srxlev and Squal are defined is further specified in those specifications.

[0053] During handover, the UE does not perform RLM in the source cell. When a handover command is received by the UE, the UE starts timer T304. Timer T304 is stopped after successful handover (i.e., when the UE sends a handover complete to the target access node). If timer T304 expires, the UE determines that the handover has failed and initiates cell selection and RRC connection re-establishment.

[0054] Self-Organizing Networks (SON) in 3GPP Self-Organizing Networks (SON) is an automation technology designed to make planning, configuration, management, optimization and repair of mobile radio access networks easier and faster. SON functions and behaviors are defined and specified in accepted mobile industry recommendations produced by organizations such as 3GPP (3rd Generation Partnership Project) and NGMN (Next Generation Mobile Networks).

[0055] In 3GPP, processes within the SON area are classified into self-configuration and self-optimization processes, where a newly deployed node is configured by an automatic installation procedure to obtain the necessary basic configuration for system operation.

[0056] This process works in a pre-operational state, which is understood as the state from when the eNB is powered up and has backbone connectivity until the RF transmitter is switched on.

[0057] Figure 6 shows the branching of the self-configuration / self-optimization function as disclosed in 3GPP TS36.300 v.16.2.0. In detail, as shown in Figure 5, the functions handled in the pre-operational state are: Basic Setup; Initial wireless settings are covered by the self-configuration process.

[0058] The self-optimization process is defined as a process in which UE and access node measurements and performance measurements are used to automatically adjust the network.

[0059] This process works in the operating state, which is understood as the state in which the RF interface is also switched on.

[0060] As illustrated in FIG. 6, the functions handled in the operational state are as follows: - Optimization / Adaptation are covered by the self-optimization process.

[0061] LTE specifies support for self-configuration and self-optimization as described in 3GPP TS36.300 v.16.2.0 section 22.2, including features such as dynamic configuration, automatic neighbor relations (ANR), mobility load balancing, mobility robustness optimization (MRO), RACH optimization and support for energy savings.

[0062] In NR, support for self-configuration and self-optimization is specified as well, starting with self-configuration features such as dynamic configuration, automatic neighbor relations (ANR) in Rel-15 as described in 3GPP TS38.300 v.16.2.0 section 15. In NR Rel-16, more SON capabilities are specified, including self-optimization features such as mobility robustness optimization (MRO).

[0063] Mobility Robustness Optimization (MRO) in 3GPP Seamless handover is a key feature of 3GPP technology. A successful handover ensures that a UE can move around in the coverage areas of different cells without causing too many interruptions in data transmission. However, there will be scenarios where the network fails to handover the UE to the "correct" neighboring cell in time, and in such scenarios the UE will declare a Radio Link Failure (RLF) or Handover Failure (HOF).

[0064] During HOF and RLF, the UE may take autonomous actions, such as, for example, trying to select a cell and initiate a re-establishment procedure, so that the UE is trying to return as soon as possible and therefore may be reachable again. Since RLF is declared by the UE only when it realizes that there is no reliable communication channel (radio link) available between itself and the network, RLF will cause a poor user experience. Also, re-establishing a connection requires signaling (random access procedure, RRC re-establishment request, RRC re-establishment RRC re-establishment complete, RRC reconfiguration and RRC re-configuration complete) with the newly selected cell until the UE can exchange data with the network again, adding some latency.

[0065] According to at least 3GPP TS36.331 v.14.14.0, possible causes for a radio link failure could be one of the following: 1) expiry of radio link supervision related timer T310, 2) expiry of the measurement report related timer T312 (no handover command is received from the network within the duration of this timer despite having sent a measurement report when T310 was running); 3) When the maximum number of RLC retransmissions is reached, 4) Upon receiving a random access problem indication from a MAC entity.

[0066] Since RLF leads to re-establishment which degrades performance and user experience, it is for the network to understand the reason for RLF and try to optimize mobility related parameters (e.g. trigger conditions for measurement reports) to avoid later RLF. Before the standardization of MRO related report handling in the network, only the UE was aware of some information related to what the radio quality was at the time of RLF, what the actual reason for declaring RLF was, etc. In order for the network to identify the reason for RLF, the network needs more information from both the UE and also from neighboring base stations.

[0067] As part of the MRO solution in LTE, the RLF reporting procedure was introduced in the RRC specification in the Rel-9 RAN2 work. It influenced the RRC specification in that it was specified that the UE will log the relevant information at the moment of RLF and report it later to the target cell to which the UE has successfully connected (e.g. after re-establishment). It also influenced the g-NodeB interface, i.e. the X2AP specification, since the eNodeB receiving the RLF report can forward it to the failed eNodeB.

[0068] Regarding the RLF report generated by the UE, the content of the RLF report has been extended with more details in subsequent releases. The measurements included in the measurement report based on the latest LTE RRC specification [Reference 1] are: 1) Measurement quantities (RSRP, RSRQ) of the last serving cell (PCell). 2) Measurements of neighboring cells at different frequencies of different RATs (EUTRA, UTRA, GERAN, Code Division Multiple Access 2000 (CDMA2000)). 3) Measurement quantities related to the WLAN Ap (RSSI). 4) Measurements related to Bluetooth beacons (RSSI). 5) Location information (including location coordinates and speed), if available 6) If available, the globally unique identity of the last serving cell; otherwise, the PCI and carrier frequency of the last serving cell. 7) Tracking area code of the PCell. 8) The time elapsed since the last receipt of a "Handover Command" message. 9) The C-RNTI used in the previous serving cell. 10) Whether or not a DRB with a QCI value of 1 has been configured for the UE.

[0069] The detection and logging of RLF related parameters is captured in section 5.3.11.3 of the LTE RRC specification 3GPP TS36.331 v.14.14.0.

[0070] After the RLF is declared, the RLF report is logged and once the UE has selected a cell and successfully re-established, the RLF report shall include an indication that it has an available RLF report in the RRC Re-establishment Complete message to make the target cell aware of its availability. Then, upon receiving a UEInformationRequest message with flag "rlf-ReportReq-r9", the UE shall include the RLF report (stored in the UE variable VarRLF-Report, as described above) in a UEInformationResponse message and send it to the network.

[0071] Based on the RLF report from the UE and its knowledge of which cell the UE has re-established itself with, the original source cell can infer whether the RLF was caused by a coverage hole or by handover-related parameter settings. If the RLF is deemed to be due to handover-related parameter settings, the original serving cell can further classify the handover-related failure as a handover that is too early, too late, or a handover to a wrong cell class. These handover failure classes are briefly described below.

[0072] For example, the original serving cell may classify a handover failure as "too late handover" when the original serving cell fails to send a handover command to a UE associated with a handover towards a particular target cell and if the UE re-establishes itself in this target cell after an RLF.

[0073] An exemplary corrective action from the original serving cell could be to initiate the handover procedure towards the target cell a little earlier by decreasing the CIO (Cell Individual Offset) towards this target cell, which controls when the IE sends the event triggered measurement report that leads to making the handover decision. However, the original serving cell can classify the handover failure as "premature handover" when the original serving cell successfully sends a handover command to the UE involved in the handover, but the UE has a failure to perform random access towards this target cell.

[0074] An exemplary corrective action from the original serving cell could be to trigger a handover procedure towards the target cell at a later time by increasing the CIO (Cell Individual Offset) towards this target cell, which controls when the IE sends the event triggered measurement report that leads to making the handover decision.

[0075] As another example, the original serving cell may classify a handover failure as "handover to wrong cell" when the original serving cell intends to perform a handover for this UE towards a particular target cell, but the UE declares RLF and re-establishes itself in a third cell.

[0076] The corrective action from the original serving cell could be to initiate a measurement reporting procedure leading to a slightly later handover towards the target cell by decreasing the CIO (Cell Individual Offset) towards the target cell, or via the UE initiating a handover towards the re-established cell a little earlier by increasing the CIO towards the re-established cell.

[0077] For that purpose in LTE, two different types of inter-node messages have been standardized in 3GPP TS 36.423 v.16.2.0: Radio Link Failure Indication and Handover Report.

[0078] The Radio Link Failure Indication procedure is used to transfer information between eNBs regarding an RRC re-establishment attempt or a received RLF report. This message is sent from an eNB where a UE performs a re-establishment to an eNB that was the UE's previous serving cell. The content of the RLF indication message is given below.

[0079] However, some problems exist. For example, there may be problems related to DAPS failure handling. In legacy DAPS, the UE starts timer T304 when it receives a HO command with DAPS while it continues to monitor the RLF trigger(s) at the source (timer T310 continues to run, if running, i.e. timer T310 is not stopped). If timer T304 expires and no RLF is declared for the PCell (i.e. T310 has not expired), the UE falls back to the source (sets back the configuration) and reports a DAPS failure via the source. Currently, the report is sent in a FailureInformation message (the procedure for sending is specified in RRC, 5.7.5 in 3GPP TS38.331 v.16.1.0) and consists only of an indication that the DAPS handover is failed.

[0080] Therefore, a first problem exists in that a scenario may occur in which the report / DAPS failure information may be lost. If the UE falls back to the source and before the UE is able to send the failure report, the UE declares RLF (T310 running may expire while the UE is doing the fallback) and triggers a re-establishment. Or, if RLF is declared while timer T304 is running, the RLF report is logged but does not mention anything about DAPS.

[0081] A second problem exists in that upon a successful Radio Access Channel (RACH) procedure towards a DAPS target cell, the T310 source goes down and the UE starts RLF monitoring in the target cell. An RLF in the target cell may occur before a DAPS release is received while data is being received from the source cell, but the UE cannot perform source cell fallback.

[0082] In summary, if T304 expires during a DAPS HO, the UE falls back to the source cell / network node, but RLF may be triggered in the source cell before the DAPS failure is reported to the source network node. Furthermore, even if the random access procedure of the DAPS HO towards the DAPS target cell is successful, RLF may occur in the target cell after some time. Summary of the Invention

[0083] Some aspects of the present disclosure and their embodiments may provide solutions to these or other problems. For example, some embodiments provide a method and system for enhancing a Dual Active Protocol Stack Handover (DAPS HO) decision by a network. In particular, some embodiments provide a method and system by a wireless device for reporting control plane (CP) related information in a successful handover report.

[0084] According to some embodiments, a method by a wireless device includes declaring a Radio Link Failure (RLF) in a source cell of a source network node during a DAPS HO from a source cell of the source network node to a target cell of a target network node. The wireless device stores information related to the DAPS HO and information related to the RLF. The wireless device transmits the information to an access node.

[0085] According to some embodiments, a method by a network node receiving, from a wireless device, information relating to a DAPS HO and an RLF, the RLF being in a source cell of a source network node and the DAPS HO being from a source cell of the source network node to a target cell of a target network node.

[0086] According to some embodiments, a wireless device includes a processing circuit, the processing circuit configured to declare an RLF in a source cell of a source network node during a DAPS HO from a source cell of the source network node to a target cell of the target network node. The processing circuit is configured to store information related to the DAPS HO and information related to the RLF. The processing circuit is configured to transmit the information to an access node.

[0087] According to some embodiments, the network node includes a processing circuit, the processing circuit configured to receive, from a wireless device, information relating to a DAPS HO and an RLF, the RLF being in a source cell of a source network node, and the DAPS HO being from a source cell of the source network node to a target cell of a target network node.

[0088] According to some embodiments, the network node is adapted to receive, from the wireless device, information related to a DAPS HO and an RLF, the RLF being in a source cell of a source network node and the DAPS HO being from a source cell of the source network node to a target cell of a target network node.

[0089] Some embodiments may provide one or more of the following technical advantages. For example, one technical advantage may be that some embodiments provide information to the network related to DAPS handover performance regarding underlying issues (e.g., DAPS handover failure, RLF). Another technical advantage may be that some embodiments enable identifying reasons for failed DAPS handovers and improving handover parameter adjustment and optimization based on DAPS handover failure message content in RLF reports.

[0090] As another example, a technical advantage may be that some embodiments may prevent information loss regarding the DAPS handover failure when falling back to the source cell, and then declare an RLF in the source cell and ensure that information regarding the DAPS handover failure (with corresponding measurements) is available to the network (e.g., the re-establishing or re-connecting cell).

[0091] As another example, a technical advantage may be that some embodiments may prevent information loss regarding an unsuccessful DAPS handover due to an RLF in the target cell that occurred prior to receipt of a daps-SourceRelease. Further root cause analysis of such information may indicate the reason for the failure (e.g., premature handover) and improve the handover configuration in the source or target cell.

[0092] Other advantages may be readily apparent to those skilled in the art. Some embodiments may have none, some, or all of the listed advantages.

[0093] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which: [Brief description of the drawings]

[0094] [Figure 1] FIG. 1 illustrates a simplified Third Generation Partnership Project (3GPP) wireless communication system. [Diagram 2] A diagram showing a signaling flow between a user equipment (UE) and a source and target access node during a handover procedure in a Long Term Evolution (LTE) network. [Diagram 3] FIG. 1 illustrates an example of a dual active protocol stack (DAPS) inter-node handover for LTE. [Figure 4] A diagram showing the protocol stack on the UE side in a DAPS handover. [Diagram 5] FIG. 2 illustrates an “out of sync” and “in sync” indications exchanged between the UE physical layer and the UE RRC layer. [Figure 6] FIG. 2 illustrates the branching of the self-configuration / self-optimization function as disclosed in 3GPP TS 36.300. [Figure 7] FIG. 1 illustrates an exemplary wireless network, according to some embodiments. [Figure 8] FIG. 1 illustrates an exemplary network node, according to some embodiments. [Figure 9] 1 illustrates an exemplary wireless device according to some embodiments. [Figure 10] FIG. 2 illustrates an exemplary user equipment, according to some embodiments. [Figure 11]FIG. 2 illustrates a virtualization environment in which functionality implemented by some embodiments may be virtualized, according to some embodiments. [Figure 12] FIG. 1 illustrates a communications network connected to a host computer through an intermediate network, according to some embodiments. [Figure 13] FIG. 2 is a generalized block diagram of a host computer communicating with user equipment via a base station over a partially wireless connection in accordance with some embodiments. [Figure 14] FIG. 1 illustrates a method implemented in a communication system according to one embodiment. [Figure 15] FIG. 1 illustrates another method implemented in a communication system according to one embodiment. [Figure 16] FIG. 1 illustrates another method implemented in a communication system according to one embodiment. [Figure 17] FIG. 1 illustrates another method implemented in a communication system according to one embodiment. [Figure 18] 1 illustrates an exemplary method by a wireless device according to some embodiments. [Figure 19] FIG. 1 illustrates an exemplary virtual computing device, according to some embodiments. [Figure 20] FIG. 1 illustrates an exemplary method by a network node, according to some embodiments. [Figure 21] FIG. 2 illustrates another exemplary virtual computing device, according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0095] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which: However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to only the embodiments described herein, but rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0096] Generally, all terms used herein should be interpreted according to the ordinary meaning of those terms in the relevant technical field, unless a different meaning is expressly given and / or implied from the context in which the term is used. All references to a / an / the element, apparatus, component, means, step, etc. should be openly interpreted as referring to at least one instance of that element, apparatus, component, means, step, etc., unless expressly stated otherwise. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is expressly described as following or preceding another step, and / or 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. Similarly, any advantage of any of the embodiments may be applied to any other embodiment, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will become apparent from the following description.

[0097] In some embodiments, the more general term "network node" may be used and may correspond to any type of radio network node or any network node that communicates with UEs (directly or via another node) and / or with another network node. Examples of network nodes are Node B, Master eNode B (MeNB), network nodes belonging to a Master Cell Group (MCG) or a Secondary Cell Group (SCG), base station (BS), MSR radio node such as a Multi-Standard Radio (MSR) BS, eNode B (eNB), gNode B, network controller, Radio Network Controller (RNC), Base Station Controller (BSC), relay, donor node controlled relay, base transceiver station (BTS), access point (AP), transmission point, transmitting node, remote radio unit (RRU), remote radio head (RRH), node in a distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operations and Maintenance (O&M), Operational Support System (OSS), Self-Optimizing Network (SON), positioning node (e.g. Evolved Serving Mobile Location Center (E-SMLC)), Minimize Drive Test (MDT), test equipment (physical node or software), etc.

[0098] In some embodiments, the non-limiting terms user equipment (UE) or wireless device may be used and may refer to any type of wireless device that communicates with a network node and / or another UE in a cellular or mobile communication system. Examples of UEs are target devices, D2D (device to device) UEs, machine type UEs or UEs capable of machine-to-machine (M2M) communication, PDAs, PADs, tablets, mobile terminals, smartphones, laptop embedded equipment (LEE), laptop mounted equipment (LME), USB dongles, UE category M1, UE category M2, ProSe UEs, V2V UEs, V2X UEs, etc.

[0099] Furthermore, terminology such as base station / gNodeB and UE should be considered non-limiting and do not specifically imply any hierarchical relationship between the two; generally, a "gNodeB" may be considered device 1 and a "UE" may be considered device 2, with these two devices communicating with each other via some wireless channel. Also, hereinafter, a transmitter or receiver may be either a gNB or a UE.

[0100] According to some embodiments, a method and system for enhancing a Dual Active Protocol Stack Handover (DAPS HO) decision by a network is provided. In particular, according to some embodiments, a method and system by a wireless device for reporting control plane (CP) related information in a successful handover report is provided.

[0101] For example, according to some embodiments, a method is provided by a wireless device for enhancing a DAPS HO decision. The method may include: Receiving a DAPS handover command from the first network node. · There is a failure to achieve access to the DAPS handover target before expiry of the T304 timer and therefore declares a DAPS handover failure. · Perform source fallback and attempt to send a DAPS handover failure message to the source. Declaring RLF before successfully sending a DAPS Handover Failure message to the source. Generating an RLF report and storing one or more sets of measurements in the RLF report including the measurements that were part of the DAPS handover failure message. The measurements further include: ○ Radio measurements from the source and target cells ○ Radio measurements from neighboring cells ○ The time between declaring the DAPS HOF and declaring the RLF. ○ Status of timer T310 while receiving a DAPS HO command Re-establish or reconnect. Indicate availability of RLF reports Receiving a request to send an RLF report Submitting RLF reports

[0102] According to some embodiments, there is provided a method by a network node in a re-establishing or re-connecting cell for enhancing a DAPS HO decision. The method may include: Receive indications regarding the availability of RLF reports Sending a request to send an RLF report Receive RLF reports Sending an RLF report to the failed PCell (the source cell of the DAPS HO) stored in the RLF report

[0103] According to some embodiments, there is provided a method by a network node in a source cell of a DAPS HO. The method may include: Receiving RLF reports from re-established or re-attached cells. Extracting information related to a failed DAPS handover and identifying the reason for the failed DAPS handover based on the DAPS handover failure message content in the RLF report. Adjusting the DAPS HO parameters

[0104] According to some embodiments, a method is provided by a wireless device for enhancing a DAPS HO decision by a network. The method may include: Receiving a DAPS handover command from the first network node. · Successfully access the DAPS handover target before the expiry of the T304 timer. Declare RLF before receiving daps-SourceRelease. Generate an RLF report and include one or more of the following measurements: ○ An indication that RLF was declared at the target of a DAPS handover, but the DAPS handover was not successful. ○ An indication that daps-SourceRelease was not received from the target o An indication that the UE has successfully sent RRC Reconfiguration Complete to the target cell. o An indication as to whether DL data reception from the source was available at the time of declaring RLF ○ Radio measurements of the source of DAPS handover ○ Time to send RRC reconfiguration complete message to DAPS target before declaring RLF (time XX) Re-establish or reconnect. Indicate availability of RLF reports Receiving a request to send an RLF report Submitting RLF reports

[0105] According to some embodiments, there is provided a method by a network node in a re-establishing or re-connecting cell for enhancing a DAPS HO decision. The method may include: Receive indications regarding the availability of RLF reports Sending a request to send an RLF report Receive RLF reports Sending an RLF report to the failed PCell (target cell of DAPS HO) stored in the RLF report

[0106] According to some embodiments, there is provided a method by a network node in a target cell of a DAPS HO. The method may include: Receiving RLF reports from re-established or re-attached cells. Analyze the information in the RLF report to determine whether the root cause of the failure is at the source of the DAPS handover or at the target of the DAPS handover. o As an example, determining whether a DAPS HO was a premature HO from the DAPS source (e.g., a small value of time XX) or whether the DAPS HO was a delayed release of the source itself (e.g., a large value of time XX). Furthermore, if the UE successfully connects to the target (second) network node, and if the second network node determines that the failure at the UE was not due to radio conditions or, in general, due to sub-optimal settings of DAPS handover parameters, the second network node may consider the problem to be contained within the second network node and avoid signaling measurements and information from the UE to the first network node. In this case, the second network node may apply changes to its own configuration to handle future similar failure cases. · If it is determined that the cause is due to the source of the DAPS handover (e.g. premature DAPS HO), send an RLF report to the source cell of the DAPS HO, indicating a premature DAPS HO. o In one example of such an embodiment, such transmission may be made over the Xn interface by means of a failure indication procedure. Alternatively, the access and mobility indication procedure may be used to transmit such information.

[0107] According to some embodiments, there is provided a method by a network node in a source cell of a DAPS HO. The method may include: Receiving an RLF report from the DAPS HO target cell and a premature DAPS HO indication o In one example of such an embodiment, such reception may occur over the Xn interface by means of a failure indication procedure. Alternatively, the access and mobility indication procedure may be used to receive such information. · Analyzing performance of a previous mobility decision based on the received one or more sets of information. Setting a new DAPS HO decision for one or more of the UEs based on the analyzed performance.

[0108] According to some embodiments, instead of storing the DAPS failure information in the RLF report, a new failure report is generated that captures information about the DAPS failure and the RLF report.

[0109] As part of the DAPS failure information included in the RLF report, the information further consists of any one or more of the following: · Cell identity of the target cell for the DAPS HO. This information may be useful to identify a failed DAPS handover target in the future when an RLF report containing DAPS failure information is received by the source of the failed DAPS HO. Radio measurement values ​​relating to the source cell and / or to the target cell, e.g. the latest available radio measurement values ​​at the time point at which the action of storing occurred together with the above-mentioned event. · Information related to UP performance during handover, such as HO interruption time during DAPS, packets lost in DAPS, etc. Status of RLM parameters related to the source network node, e.g. T310 status in the first network node, T304 in the second network node status (if the UE has declared HOF in the target with maximum number of RA attempts), number of RLC retransmissions in the source before declaring HOF. · Time indications relating to: o The time elapsed between receipt of a DAPS HO command and the fallback to the first network node. o The time elapsed between receipt of a DAPS HO command and the RLF in the first network node. o The time elapsed between receipt of the DAPS HO command and the handover failure in the second network node.

[0110] According to some other embodiments, as part of the DAPS targeted RLF report, the information may further comprise at least one of the following: ○ Radio measurement values ​​relating to the source cell and / or to the target cell, for example the latest available radio measurement values ​​at the point in time when the storing action occurred together with the above event. o Information related to UP performance during handover, such as HO interruption time during DAPS, packets lost in DAPS, etc. o Status of the RLM parameters related to the first network node at the time it stops monitoring the RLM towards the source (i.e. at the time it completes the RA procedure towards the DAPS HO target cell). This information is useful to know if the source link quality was quite good at the time it completed the DAPS HO. Such a status could be one or more of the following: T310 status, i.e. whether T310 has expired or not, and if not, whether T310 was running or not, and if so, the actual value of T310. The number of consecutive OOS (Out of Sync) indications from lower layers. · The number of consecutive IS (In-Sync) indications from the lower layer. · Whether beam failure recovery was in progress. o An indication that the previous HO was associated with a DAPS HO. ○ Time indications relating to: The time elapsed between receipt of the DAPS HO command and the HO completion, i.e. the sending of an RRC Reconfiguration Complete to the second network node. The time elapsed between HO completion and RLF declaration

[0111] In the exemplary embodiment described above, the report content may further be communicated within a node in a split architecture deployment. If the network node that needs to take action is a split gNB made of a gNB-DU and a gNB-CU, the gNB-CU of such network node may determine to signal such report content to the gNB-DU. The gNB-DU may take this information into account to optimize its configuration, e.g., to optimize parameters related to RACH, beam configuration, cell configuration.

[0112] FIG. 7 illustrates a wireless network, according to some embodiments. Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are described with respect to a wireless network, such as the exemplary wireless network illustrated in FIG. 7. For simplicity, the wireless network of FIG. 7 illustrates only the network 106, the network nodes 160 and 160b, and the wireless device 110. In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices, or between a wireless device and another communication device, such as a landline, a service provider, or any other network node or end device. Of the components shown, the network node 160 and the wireless device 110 are illustrated with additional details. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless device's access to the wireless network and / or use of services provided by or via the wireless network.

[0113] The wireless network may include and / or interface with any type of communication, telecommunication, data, cellular, and / or radio network, or other similar type of system. In some embodiments, the wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement a communications standard, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards, a wireless local area network (WLAN) standard, such as the IEEE 802.11 standard, and / or any other suitable wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0114] The network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks for enabling communication between devices.

[0115] The network node 160 and the wireless device 110 comprise various components, which are described in more detail below. These components cooperate to provide network node and / or wireless device functionality, such as providing wireless connectivity in a wireless network. In different embodiments, a wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, 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.

[0116] FIG. 8 illustrates an exemplary network node 160, according to some embodiments. A network node, as used herein, refers to a device capable of, set up, configured, and / or operable to communicate, directly or indirectly, with wireless devices and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless devices and / or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR Node Bs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated another way, the transmit power level of the base station), in which case they may be referred to as femto, pico, micro, or macro base stations. A base station may be a relay node or a relay donor node, which controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. A part of a distributed radio base station may also be referred to as a node in a distributed antenna system (DAS). Still further examples of a network node include MSR equipment such as a multi-standard radio (MSR) BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmitting node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an MDT. As another example, a network node may be a virtual network node, as described in more detail below.More generally, however, a network node may represent any suitable device (or group of devices) capable of, configured to, and / or operable to enable and / or provide wireless devices with access to a wireless network or to provide some service to wireless devices that have accessed the wireless network.

[0117] In FIG. 8, network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. Although network node 160 shown in the example wireless network of FIG. 8 may represent a device including the shown combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It should be understood that a network node comprises any suitable combination of hardware and / or software required to perform the tasks, features, functions and methods disclosed herein. Moreover, although the components of network node 160 are illustrated as a single box located within a larger box or nested within multiple boxes, in reality the network node may comprise multiple different physical components that make up a single shown component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).

[0118] Similarly, the network node 160 may be assembled from multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have their own respective components. In some scenarios in which the network node 160 comprises multiple separate components (e.g., a BTS component and a BSC component), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control several Node Bs. In such scenarios, each unique Node B and RNC pair may be considered as a single separate network node in some instances. In some embodiments, the network node 160 may be configured to support several radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media 180 for different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of the various shown components for different wireless technologies, such as, for example, Global System for Mobile Communications (GSM), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), New Radio (NR), WiFi, or Bluetooth wireless technologies, integrated into network node 160. These wireless technologies may be integrated in the same or different chips or sets of chips and other components within network node 160.

[0119] The processing circuitry 170 is configured to perform any of the decision, computation, or similar operations (e.g., some acquisition operations) described herein as being provided by a network node. These operations performed by the processing circuitry 170 may include processing information acquired by the processing circuitry 170, for example, by transforming the acquired information into other information, comparing the acquired or transformed information with information stored in the network node, and / or performing one or more operations based on the acquired or transformed information and as a result of said processing making a decision.

[0120] Processing circuitry 170 may comprise one or more combinations 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 coded logic operable to provide network node 160 functionality, either alone or in conjunction with other network node 160 components, such as device readable medium 180. For example, processing circuitry 170 may execute instructions stored on device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits described herein. In some embodiments, processing circuitry 170 may include a system on a chip (SOC).

[0121] In some embodiments, the processing circuitry 170 may include one or more of a radio frequency (RF) transceiver circuitry 172 and a baseband processing circuitry 174. In some embodiments, the radio frequency (RF) transceiver circuitry 172 and the baseband processing circuitry 174 may be on separate chips (or sets of chips), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuitry 172 and the baseband processing circuitry 174 may be on the same chip or set of chips, board, or unit.

[0122] In some embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by the processing circuitry 170 executing instructions stored in the device-readable medium 180, or in memory within the processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 170 without executing instructions stored in a separate or distinct device-readable medium, such as in a hardwired manner. In any of those embodiments, the processing circuitry 170 may be configured to perform the described functionality, whether or not it executes instructions stored in a device-readable storage medium. Benefits provided by such functionality are enjoyed by the processing circuitry 170 alone, or by other components of the network node 160, but by the network node 160 as a whole, and / or by end users and wireless networks generally.

[0123] The device readable medium 180 may comprise any form of volatile or non-volatile computer readable memory, including, but not limited to, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device readable and / or computer executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 170. The device readable medium 180 may store any suitable instructions, data or information, including applications including one or more of computer programs, software, logic, rules, codes, tables, etc., and / or other instructions that may be executed by the processing circuit 170 and utilized by the network node 160. The device readable medium 180 may be used to store calculations performed by the processing circuit 170 and / or data received via the interface 190. In some embodiments, the processing circuit 170 and the device-readable medium 180 may be considered to be integrated.

[0124] The interface 190 is used in wired or wireless communication of signaling and / or data between the network node 160, the network 106, and / or the wireless device 110. As shown, the interface 190 comprises a port(s) / terminal(s) 194 for sending and receiving data to and from the network 106, for example over a wired connection. The interface 190 also includes a radio front-end circuit 192 that is coupled to the antenna 162 or, in some embodiments, may be part of the antenna 162. The radio front-end circuit 192 comprises a filter 198 and an amplifier 196. The radio front-end circuit 192 may be connected to the antenna 162 and the processing circuit 170. The radio front-end circuit may be configured to condition signals communicated between the antenna 162 and the processing circuit 170. The radio front-end circuit 192 may receive digital data to be sent to other network nodes or wireless devices via a wireless connection. The radio front-end circuitry 192 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 198 and / or amplifiers 196. The radio signal may then be transmitted via the antenna 162. Similarly, when receiving data, the antenna 162 may collect the radio signal, which is then converted into digital data by the radio front-end circuitry 192. The digital data may be passed to the processing circuitry 170. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0125] In some alternative embodiments, the network node 160 may not include a separate radio front-end circuit 192; instead, the processing circuit 170 may comprise a radio front-end circuit and be connected to the antenna 162 without a separate radio front-end circuit 192. Similarly, in some embodiments, all or a portion of the RF transceiver circuit 172 may be considered part of the interface 190. In still other embodiments, the interface 190 may include one or more ports or terminals 194, the radio front-end circuit 192, and the RF transceiver circuit 172 as part of a radio unit (not shown), and the interface 190 may communicate with a baseband processing circuit 174 that is part of a digital unit (not shown).

[0126] The antenna 162 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. The antenna 162 may be coupled to the radio front-end circuitry 192 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, the antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit / receive wireless signals, for example, between 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit / receive wireless signals in any direction, a sector antenna may be used to transmit / receive wireless signals from devices in a particular area, and a panel antenna may be a line-of-sight antenna used to transmit / receive wireless signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In some embodiments, the antenna 162 may be separate from the network node 160 and may be connectable to the network node 160 through an interface or port.

[0127] The antenna 162, the interface 190, and / or the processing circuitry 170 may be configured to perform any receiving operation and / or some obtaining operation described herein as being performed by a network node. Any information, data, and / or signal may be received from a wireless device, another network node, and / or any other network equipment. Similarly, the antenna 162, the interface 190, and / or the processing circuitry 170 may be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data, and / or signal may be transmitted to a wireless device, another network node, and / or any other network equipment.

[0128] The power circuit 187 may comprise or be coupled to a power management circuit and is configured to supply power to the components of the network node 160 for performing the functions described herein. The power circuit 187 may receive power from the power source 186. The power source 186 and / or the power circuit 187 may be configured to provide power to the various components of the network node 160 in a form suitable for the respective components (e.g., at voltage and current levels required for each respective component). The power source 186 may either be included in the power circuit 187 and / or the network node 160 or be external to the power circuit 187 and / or the network node 160. For example, the network node 160 may be connectable to an external power source (e.g., an electrical outlet) via an input circuit or interface, such as an electrical cable, whereby the external power source provides power to the power circuit 187. As a further example, the power source 186 may comprise a power source in the form of a battery or battery pack connected to or integrated in the power circuit 187. Batteries can provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, can also be used.

[0129] Alternative embodiments of network node 160 may include additional components other than those shown in FIG. 8 that may be responsible for providing some aspects of the network node's functionality, including any of the functionality described herein and / or functionality necessary to support the subject matter described herein. For example, network node 160 may include user interface devices to enable input of information into network node 160 and output of information from network node 160. This may enable a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.

[0130] FIG. 9 illustrates an exemplary wireless device 110, according to some embodiments. A wireless device, as used herein, refers to a device capable of, configured to, and / or operable to wirelessly communicate with network nodes and / or other wireless devices. Unless otherwise noted, the term wireless device may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and / or receiving wireless signals using electromagnetic, radio, infrared, and / or other types of signals suitable for conveying information over the air. In some embodiments, a wireless device may be configured to transmit and / or receive information without direct human interaction. For example, a wireless device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to a request from the network. Examples of wireless devices include, but are not limited to, smartphones, mobile phones, cell phones, voice-over-IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), in-vehicle wireless terminal devices, etc. A wireless device may support device-to-device (D2D) communications, e.g., by implementing 3GPP standards for sidelink communications, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X), in which case it may be referred to as a D2D communications device. As yet another specific example, in an Internet of Things (IoT) scenario, a wireless device may represent a machine or other device that performs monitoring and / or measurements and transmits results of such monitoring and / or measurements to another wireless device and / or network node.The wireless device may in this case be a machine-to-machine (M2M) device, which may be referred to as an MTC device in a 3GPP context. As one particular example, the wireless device may be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, the wireless device may represent a vehicle or other equipment capable of monitoring and / or reporting on its operating status or other functions related to its operation. The wireless devices described above may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, the wireless devices described above may be mobile, in which case the device may be referred to as a mobile device or mobile terminal.

[0131] As shown, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device-readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136, and power circuitry 137. Wireless device 110 may include multiple sets of one or more of the shown components for different wireless technologies supported by wireless device 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to name a few. These wireless technologies may be integrated on the same or different chip or set of chips as other components in wireless device 110.

[0132] Antenna 111 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals and is connected to interface 114. In some alternative embodiments, antenna 111 may be separate from wireless device 110 and connectable to wireless device 110 through an interface or port. Antenna 111, interface 114, and / or processing circuit 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a wireless device. Any information, data, and / or signal may be received from a network node and / or another wireless device. In some embodiments, the wireless front-end circuit and / or antenna 111 may be considered an interface.

[0133] As shown, the interface 114 comprises a radio front-end circuit 112 and an antenna 111. The radio front-end circuit 112 comprises one or more filters 118 and an amplifier 116. The radio front-end circuit 112 is connected to the antenna 111 and the processing circuit 120 and is configured to condition signals communicated between the antenna 111 and the processing circuit 120. The radio front-end circuit 112 may be coupled to or part of the antenna 111. In some embodiments, the wireless device 110 may not include a separate radio front-end circuit 112; rather, the processing circuit 120 may comprise a radio front-end circuit and be connected to the antenna 111. Similarly, in some embodiments, some or all of the RF transceiver circuit 122 may be considered part of the interface 114. The radio front-end circuit 112 may receive digital data to be sent to other network nodes or wireless devices via a wireless connection. The radio front-end circuitry 112 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 118 and / or amplifiers 116. The radio signal may then be transmitted via the antenna 111. Similarly, when receiving data, the antenna 111 may collect the radio signal, which is then converted into digital data by the radio front-end circuitry 112. The digital data may be passed to the processing circuitry 120. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0134] The processing circuitry 120 may comprise one or more combinations 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, resources, or combinations of hardware, software, and / or coded logic operable to provide wireless device 110 functionality, either alone or in conjunction with other wireless device 110 components, such as device readable medium 130. Such functionality may include providing any of the various wireless features or benefits described herein. For example, the processing circuitry 120 may execute instructions stored on the device readable medium 130 or in a memory within the processing circuitry 120 to provide the functionality disclosed herein.

[0135] As shown, the processing circuitry 120 includes one or more of the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126. In other embodiments, the processing circuitry may comprise different components and / or different combinations of components. In some embodiments, the processing circuitry 120 of the wireless device 110 may comprise a SOC. In some embodiments, the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126 may be on separate chips or sets of chips. In alternative embodiments, some or all of the baseband processing circuitry 124 and the application processing circuitry 126 may be combined into one chip or set of chips, and the RF transceiver circuitry 122 may be on a separate chip or set of chips. In yet alternative embodiments, some or all of the RF transceiver circuitry 122 and the baseband processing circuitry 124 may be on the same chip or set of chips, and the application processing circuitry 126 may be on a separate chip or set of chips. In yet other alternative embodiments, some or all of the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126 may be combined in the same chip or set of chips. In some embodiments, the RF transceiver circuitry 122 may be part of the interface 114. The RF transceiver circuitry 122 may condition RF signals for the processing circuitry 120.

[0136] In some embodiments, some or all of the functionality described herein as being performed by the wireless device may be provided by the processing circuitry 120 executing instructions stored on a device-readable medium 130, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 120 without executing instructions stored on a separate or distinct device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, the processing circuitry 120 may be configured to perform the described functionality, whether or not it executes instructions stored on a device-readable storage medium. Benefits provided by such functionality are enjoyed by the processing circuitry 120 alone or by other components of the wireless device 110, but by the wireless device 110 as a whole, and / or by end users and wireless networks generally.

[0137] Processing circuitry 120 may be configured to perform any of the decision, computation, or similar operations (e.g., some acquisition operations) described herein as being performed by a wireless device. These operations as performed by processing circuitry 120 may include processing information acquired by processing circuitry 120, for example, by transforming the acquired information into other information, comparing the acquired or transformed information with information stored by wireless device 110, and / or performing one or more operations based on the acquired or transformed information and as a result of said processing making a decision.

[0138] The device-readable medium 130 may be operable to store applications including one or more of computer programs, software, logic, rules, codes, tables, etc., and / or other instructions that may be executed by the processing circuit 120. The device-readable medium 130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 120. In some embodiments, the processing circuit 120 and the device-readable medium 130 may be considered to be integrated.

[0139] The user interface equipment 132 may provide components that allow a human user to interact with the wireless device 110. Such interaction may be of many forms, such as visual, auditory, tactile, etc. The user interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to the wireless device 110. The type of interaction may vary depending on the type of user interface equipment 132 installed on the wireless device 110. For example, if the wireless device 110 is a smartphone, the interaction may be via a touch screen, and if the wireless device 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface equipment 132 may include input interfaces, devices and circuits, as well as output interfaces, devices and circuits. The user interface equipment 132 is configured to allow input of information to the wireless device 110 and is connected to the processing circuit 120 to allow the processing circuit 120 to process the input information. The user interface equipment 132 may include, for example, a microphone, proximity or other sensors, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. The user interface equipment 132 is also configured to enable output of information from the wireless device 110 and to enable the processing circuitry 120 to output information from the wireless device 110. The user interface equipment 132 may include, for example, a speaker, a display, vibration circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits of the user interface equipment 132, the wireless device 110 may communicate with an end user and / or a wireless network, enabling the end user and / or the wireless network to benefit from the functionality described herein.

[0140] The auxiliary device 134 is operable to provide more specific functionality that may not generally be implemented by wireless devices. It may comprise specialized sensors for taking measurements for various purposes, interfaces for additional types of communication such as wired communication, etc. The inclusion of components of the auxiliary device 134 and the types of components of the auxiliary device 134 may vary depending on the embodiment and / or scenario.

[0141] The power source 136 may be in the form of a battery or battery pack in some embodiments. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery cell. The wireless device 110 may further comprise a power circuit 137 for delivering power from the power source 136 to various portions of the wireless device 110 that require power from the power source 136 to perform any of the functions described or indicated herein. The power circuit 137 may comprise a power management circuit in some embodiments. The power circuit 137 may additionally or alternatively be operable to receive power from an external power source, in which case the wireless device 110 may be connectable to an external power source (such as an electrical outlet) via an input circuit or interface, such as a power cable. The power circuit 137 may also be operable in some embodiments to deliver power from the external power source to the power source 136. This may be for charging the power source 136, for example. Power circuitry 137 may perform any formatting, conversion, or other modification on the power from power source 136 to make the power suitable for the respective components of wireless device 110 to which it is supplied.

[0142] FIG. 10 illustrates an embodiment of a UE according to various aspects described herein. User equipment or UE as used herein does not necessarily have a user in the sense of a human user who owns and / or operates an associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user, but may not be associated with or may not be initially associated with a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user, but may be associated with or operated for the benefit of a user. The UE 200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including an NB-IoT UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. The UE 200 shown in Figure 8 is an example of a wireless device configured for communication according to one or more communications standards promulgated by the 3rd Generation Partnership Project (3GPP), such as the 3GPP's GSM, UMTS, LTE, and / or 5G standards. As previously mentioned, the terms wireless device and UE may be used interchangeably. Thus, although Figure 10 is a UE, the components described herein are equally applicable to a wireless device and vice versa.

[0143] In FIG. 10, UE 200 includes a processor 201 operatively coupled to an input / output interface 205, a radio frequency (RF) interface 209, a network connection interface 211, memory 215 including random access memory (RAM) 217, read only memory (ROM) 219, storage medium 221, etc., a communication subsystem 231, a power source 233, and / or any other components, or any combination thereof. Storage medium 221 includes operating system 223, application programs 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Some UEs may utilize all of the components shown in FIG. 10 or only a subset of those components. The level of integration between components may vary from UE to UE. Additionally, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0144] In Fig. 10, the processor 201 may be configured to process computer instructions and data. The processor 201 may be configured to implement any sequential state machine operable to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.), programmable logic with appropriate firmware, one or more pre-programmed, general-purpose processors, such as a microprocessor or digital signal processor (DSP) with appropriate software, or any combination of the above. For example, the processor 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0145] In the illustrated embodiment, the input / output interface 205 may be configured to provide an input device, an output device, or a communication interface to an input / output device. The UE 200 may be configured to use an output device via the input / output interface 205. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to and output from the UE 200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, another output device, or any combination thereof. The UE 200 may be configured to use an input device via the input / output interface 205 to allow a user to capture information on the UE 200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and a light sensor.

[0146] In FIG. 10, the RF interface 209 may be configured to provide a communication interface to RF components, such as a transmitter, a receiver, and an antenna. The network connection interface 211 may be configured to provide a communication interface to a network 243a. The network 243a may encompass a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communication network, another similar network, or any combination thereof. For example, the network 243a may comprise a Wi-Fi network. The network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP / IP, SONET, ATM, etc. The network connection interface 211 may implement receiver and transmitter functions appropriate for a communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components, software, or firmware, or may alternatively be implemented separately.

[0147] The RAM 217 may be configured to interface to the processor 201 via the bus 202 to provide storage or caching of data or computer instructions during execution of software programs, such as an operating system, application programs, and device drivers. The ROM 219 may be configured to provide computer instructions or data to the processor 201. For example, the ROM 219 may be configured to store invariant low-level system code or data for basic system functions, such as basic input / output (I / O), booting, or receiving keystrokes from a keyboard, stored in non-volatile memory. The storage medium 221 may be configured to include memory, such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cartridge, or flash drive. In one example, the storage medium 221 may be configured to include an operating system 223, an application program 225, such as a web browser application, a widget or gadget engine, or another application, and data files 227. The storage medium 221 may store any of a variety of different operating systems or combinations of operating systems for use by the UE 200.

[0148] The storage medium 221 may be configured to include several physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high density digital versatile disk (HD-DVD) optical disk drive, an internal hard disk drive, a Blu-Ray optical disk drive, a holographic digital data storage (HDDS) optical disk drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro-DIMM SDRAM, a smart card memory such as a subscriber identity module or a removable user identity (SIM / RUIM) module, other memory, or any combination thereof. The storage medium 221 may enable the UE 200 to access computer executable instructions, application programs, etc. stored in a temporary or non-transitory memory medium, offload data, or upload data. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied in the storage medium 221, and the storage medium 221 may comprise a device-readable medium.

[0149] In FIG. 10, the processor 201 may be configured to communicate with the network 243b using the communication subsystem 231. The networks 243a and 243b may be the same network or networks or different networks or networks. The communication subsystem 231 may be configured to include one or more transceivers used to communicate with the network 243b. For example, the communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication, such as another wireless device, UE, or base station of a radio access network (RAN), according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc. Each transceiver may include a transmitter 233 and / or a receiver 235 for implementing transmitter or receiver functions, respectively, appropriate for the RAN link (e.g., frequency allocation, etc.). Additionally, the transmitter 233 and receiver 235 of each transceiver may share circuit components, software, or firmware, or may alternatively be implemented separately.

[0150] In the illustrated embodiment, the communication capabilities of the communication subsystem 231 may include data communications, voice communications, multimedia communications, short-range communications such as Bluetooth, near-field communications, location-based communications such as using a global positioning system (GPS) to determine location, another similar communication capability, or any combination thereof. For example, the communication subsystem 231 may include cellular communications, Wi-Fi communications, Bluetooth communications, and GPS communications. The network 243b may encompass wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communications network, another similar network, or any combination thereof. For example, the network 243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 200.

[0151] The features, benefits and / or functions described herein may be implemented in one of the components of the UE 200 or distributed across multiple components of the UE 200. Furthermore, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 231 may be configured to include any of the components described herein. Furthermore, the processor 201 may be configured to communicate with any of such components over the bus 202. In another example, any of such components may be represented by program instructions stored in memory that, when executed by the processor 201, perform the corresponding functions described herein. In another example, the functions of any of such components may be distributed between the processor 201 and the communication subsystem 231. 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.

[0152] FIG. 11 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments may be virtualized. In this context, virtualizing means creating a virtual version of an apparatus or device, which may include virtualizing a hardware platform, storage devices, and networking resources. Virtualization as used herein may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device, or any other type of communication device) or a component of that device, and relates to implementations in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers running on one or more physical processing nodes in one or more networks).

[0153] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of the hardware nodes 330. Furthermore, in embodiments where the virtual nodes are not wireless access nodes or do not require wireless connectivity (e.g., core network nodes), the network nodes may be fully virtualized.

[0154] The functionality may be implemented by one or more applications 320 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The applications 320 are run in a virtualization environment 300, which provides a middleware (MW) 330 comprising a processing circuit 360 and a memory 390-1. The memory 390-1 includes instructions 395 executable by the processing circuit 360 such that the applications 320 are operable to provide one or more of the features, functions, and / or benefits of the embodiments disclosed herein.

[0155] The virtualization environment 300 includes general-purpose or dedicated network hardware devices 330 that include a set of one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, dedicated application-specific integrated circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or dedicated processors. Each hardware device 330 may include a memory 390-1, which may be a non-persistent memory for temporarily storing instructions 395 or software executed by the processing circuitry 360. Each hardware device 330 may include one or more network interface controllers (NICs) 370, also known as network interface cards, that include physical network interfaces 380. Each hardware device 330 may also include a non-transitory, persistent, machine-readable storage medium 390-2 that stores software 395 and / or instructions executable by the processing circuitry 360. The software 395 may include any type of software, including software for instantiating one or more virtualization layers 350 (also called hypervisors), software for running virtual machines (VMs) 340, and software that enables it to perform the functions, features and / or benefits described in connection with some of the embodiments described herein.

[0156] A VM 340 may comprise virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of virtual appliance 320 instances may be implemented on one or more of virtual machines 340, and the implementation may be done in different ways.

[0157] During operation, the processing circuitry 360 executes software 395 to instantiate a hypervisor or virtualization layer 350, which is sometimes referred to as a virtual machine monitor (VMM). The virtualization layer 350 may present to the virtual machines 340 a virtual operating platform that looks like networking hardware.

[0158] 11, the hardware 330 may be a standalone network node with general or specific components. The hardware 330 may include an antenna 3225 and may implement some functions via virtualization. Alternatively, the hardware 330 may be part of a larger cluster of hardware (e.g., as in the case of a data center or customer premises equipment (CPE)) where many hardware nodes work together and are managed via a management and orchestration (MANO) 3100 that, among other things, oversees the lifecycle management of the application 320.

[0159] Hardware virtualization is referred to in some contexts as network function virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage that may be located in data centers and customer premises equipment.

[0160] In the context of NFV, VMs 340 may be software implementations of physical machines that run programs as if they were running on a physical, non-virtualized machine. Each VM 340 and the portion of hardware 330 on which it runs, whether hardware dedicated to that VM and / or hardware shared by that VM with other ones of VMs 340, form a separate Virtual Network Element (VNE).

[0161] Further in the context of NFV, a Virtual Network Function (VNF) is responsible for handling a specific network function running in one or more virtual machines 340 on top of the hardware networking infrastructure 330 and corresponds to application 320 in FIG. 11.

[0162] In some embodiments, one or more radio units 3200, each including one or more transmitters 3220 and one or more receivers 3210, may be coupled to one or more antennas 3225. The radio units 3200 may communicate directly with the hardware node 330 via one or more suitable network interfaces and may be used in combination with a virtualization component to provide a virtual node with wireless capabilities, such as a wireless access node or base station.

[0163] In some embodiments, some signaling may be affected using a control system 3230, which may alternatively be used for communication between the hardware nodes 330 and the wireless unit 3200.

[0164] FIG. 12 illustrates a communication network connected to a host computer via an intermediate network, according to some embodiments. Referring to FIG. 12, according to one embodiment, a communication system includes a communication network 410, such as a 3GPP-type cellular network, comprising an access network 411, such as a wireless access network, and a core network 414. The access network 411 comprises a number of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c can be connected to the core network 414 over a wired or wireless connection 415. A first UE 491 located in the coverage area 413c is configured to wirelessly connect to or be paged by the corresponding base station 412c. A second UE 492 in the coverage area 413a can be wirelessly connected to the corresponding base station 412a. Although multiple UEs 491, 492 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in a coverage area or where only one UE is connected to a corresponding base station 412.

[0165] The communication network 410 is itself connected to a host computer 430, which may be embodied in hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 430 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. The connections 421 and 422 between the communication network 410 and the host computer 430 may extend directly from the core network 414 to the host computer 430, or may proceed through an optional intermediate network 420. The intermediate network 420 may be one of a public network, a private network, or a hosted network, or a combination of two or more of them, and the intermediate network 420 may be a backbone network or the Internet, if any, and in particular the intermediate network 420 may comprise two or more sub-networks (not shown).

[0166] The communication system of FIG. 12 as a whole enables connectivity between the connected UEs 491, 492 and the host computer 430. The connectivity may be described as an over-the-top (OTT) connection 450. The host computer 430 and the connected UEs 491, 492 are configured to communicate data and / or signaling via the OTT connection 450 using the access network 411, the core network 414, any intermediate networks 420, and possible further infrastructure (not shown) as intermediaries. The OTT connection 450 may be transparent in the sense that the participating communication devices through which the OTT connection 450 passes are unaware of the routing of the uplink and downlink communications. For example, the base station 412 may not be or need not be informed about the past routing of incoming downlink communications involving data originating from the host computer 430 to be forwarded (e.g., handed over) to the connected UE 491. Similarly, the base station 412 does not need to be aware of the future routing of outgoing uplink communications originating from the UE 491 and destined for the host computer 430 .

[0167] FIG. 13 illustrates a host computer communicating with user equipment via a base station over a partially wireless connection according to some embodiments.

[0168] Next, an exemplary implementation of the UE, base station and host computer described in the previous paragraph according to an embodiment will be described with reference to FIG. 13. In the communication system 500, the host computer 510 comprises hardware 515 including a communication interface 516 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 500. The host computer 510 further comprises a processing circuit 518, which may have storage and / or processing capabilities. In particular, the processing circuit 518 may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The host computer 510 further comprises software 511, which is stored in or accessible by the host computer 510 and is executable by the processing circuit 518. The software 511 includes a host application 512. The host application 512 may be operable to provide services to a remote user, such as a UE 530 that connects via an OTT connection 550 that terminates at the UE 530 and the host computer 510. In providing services to the remote user, the host application 512 may provide user data that is transmitted using the OTT connection 550.

[0169] The communication system 500 further includes a base station 520 provided in the communication system, the base station 520 comprising hardware 525 enabling the base station 520 to communicate with the host computer 510 and the UE 530. The hardware 525 may include a communication interface 526 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 500, as well as a wireless interface 527 for setting up and maintaining at least a wireless connection 570 with a UE 530 located in a coverage area (not shown in FIG. 13) served by the base station 520. The communication interface 526 may be configured to facilitate a connection 560 to the host computer 510. The connection 560 may be direct or the connection 560 may pass through a core network (not shown in FIG. 13) of the communication system and / or one or more intermediate networks outside the communication system. In the illustrated embodiment, the hardware 525 of the base station 520 further includes processing circuitry 528, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 520 further has software 521 stored internally or accessible via an external connection.

[0170] The communication system 500 further includes the UE 530 already mentioned. The hardware 535 of the UE 530 may include a wireless interface 537 configured to set up and maintain a wireless connection 570 with a base station serving a coverage area in which the UE 530 is currently located. The hardware 535 of the UE 530 further includes a processing circuit 538, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The UE 530 further includes software 531 stored in or accessible by the UE 530 and executable by the processing circuit 538. The software 531 includes a client application 532. The client application 532 may be operable to provide services to a human or non-human user via the UE 530 with the support of the host computer 510. At the host computer 510, a running host application 512 may communicate with a running client application 532 via an OTT connection 550 that terminates at the UE 530 and the host computer 510. In providing services to a user, the client application 532 may receive request data from the host application 512 and provide user data in response to the request data. The OTT connection 550 may transfer both the request data and the user data. The client application 532 may interact with the user to generate the user data that the client application 532 provides.

[0171] It should be noted that the host computer 510, base station 520 and UE 530 shown in Figure 13 may be similar or equivalent to the host computer 430, one of the base stations 412a, 412b, 412c, and one of the UEs 491, 492, respectively, of Figure 12. That is, the inner workings of these entities may be as shown in Figure 13, and separately, the surrounding network topology may be that of Figure 12.

[0172] 13, the OTT connection 550 is depicted abstractly to show communication between the host computer 510 and the UE 530 via the base station 520, without explicit reference to intermediary devices and the exact routing of messages through these devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing from the UE 530 or from the service provider operating the host computer 510, or both. The network infrastructure may also make decisions to dynamically change the routing while the OTT connection 550 is active (e.g., based on load balancing considerations or reconfiguration of the network).

[0173] The wireless connection 570 between the UE 530 and the base station 520 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 530 using the OTT connection 550 of which the wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments may improve data rates, latency, and / or power consumption, thereby providing benefits such as reduced user latency, relaxed limitations on file sizes, improved responsiveness, and / or extended battery life.

[0174] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve upon. There may further be an optional network function for reconfiguring the OTT connection 550 between the host computer 510 and the UE 530 in response to fluctuations in the measurement results. The measurement procedures and / or the network function for reconfiguring the OTT connection 550 may be implemented in the software 511 and hardware 515 of the host computer 510 or in the software 531 and hardware 535 of the UE 530, or both. In an embodiment, sensors (not shown) may be deployed in or in association with the communication device through which the OTT connection 550 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or other physical quantities from which the software 511, 531 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 550 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 520, and the reconfiguration may be unknown or imperceptible to the base station 520. Such procedures and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 510 measurements of throughput, propagation time, latency, etc. The measurements may be implemented in the software 511 and 531 causing messages, particularly empty or "dummy" messages, to be sent using the OTT connection 550 while the software 511 and 531 monitors propagation times, errors, etc.

[0175] FIG. 14 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 12 and FIG. 13. For simplicity of the disclosure, only drawing references to FIG. 14 are included in this section. In step 610, the host computer provides user data. In sub-step 611 of step 610 (which may be optional), the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission carrying the user data to the UE. In step 630 (which may be optional), the base station transmits the user data carried in the host computer initiated transmission to the UE according to the teachings of the embodiments described throughout this disclosure. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0176] FIG. 15 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 12 and FIG. 13. For simplicity of the disclosure, only drawing references to FIG. 15 are included in this section. In step 710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission carrying the user data to the UE. The transmission may proceed via the base station according to the teachings of the embodiments described throughout this disclosure. In step 730 (which may be optional), the UE receives the user data carried in the transmission.

[0177] FIG. 16 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 12 and FIG. 13. For simplicity of the disclosure, only drawing reference to FIG. 16 is included in this section. In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In sub-step 821 (which may be optional) of step 820, the UE provides the user data by executing a client application. In sub-step 811 (which may be optional) of step 810, the UE executes a client application that provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from the user. Regardless of the particular manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in sub-step 830 (which may be optional). In method step 840, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

[0178] FIG. 17 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 12 and FIG. 13. For simplicity of the disclosure, only drawing references to FIG. 17 are included in this section. In step 910 (which may be optional), the base station receives user data from the UE, according to the teachings of the embodiments described throughout this disclosure. In step 920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0179] 18 illustrates a method 1000 by a wireless device 110 according to some embodiments. In step 1002, the wireless device declares an RLF in a source cell of a source network node during a DAPS HO from a source cell of the source network node to a target cell of the target network node. In step 1004, the wireless device stores information related to the DAPS HO. In step 1006, the wireless device stores information related to the RLF. In step 1008, the wireless device transmits the information to the access node.

[0180] In a particular embodiment, at least a portion of the information is transmitted in an RLF report or a handover report.

[0181] In a particular embodiment, the wireless device 110 transmits an indication of the availability of information to an access node and receives a request to transmit the information. The information is transmitted in response to the request.

[0182] In a particular embodiment, the RLF is associated with a failed connection between the wireless device 110 and a source cell of a source network node.

[0183] In a particular embodiment, prior to declaring an RLF in the source cell of the source network node and during the DAPS HO of the wireless device, the wireless device 110 determines a handover failure and performs a fallback to the source cell of the source network node. The RLF is declared prior to successfully sending a handover failure message to the source network node.

[0184] As used herein, a handover is considered to be in progress while timer T304 is running or until a failure is declared. Thus, as used herein, a handover occurs between the time the UE gets the HO command and the time the UE sends an RRC reconfiguration complete message to the target network node.

[0185] As used herein, the terms fallback and procedure for fallback refer to the wireless device returning to the source cell settings and resuming connectivity with the source cell.

[0186] In a particular embodiment, the access node includes a network node 160 with which the wireless device 110 establishes a connection after the wireless device 110 declares a radio link failure with the source network node.

[0187] In a particular embodiment, prior to transmitting information, the wireless device 110 establishes a connection with an access node.

[0188] In a particular embodiment, the RLF is associated with a failed connection between the wireless device 110 and the target network node 160 .

[0189] In a particular embodiment, in response to a successful DAPS HO of the wireless device 110 to the target cell associated with the target node, the wireless device 110 prepares a handover message indicating the successful DAPS HO of the wireless device 110 to the target network node. The RLF is declared prior to successfully transmitting the handover message indicating the successful DAPS HO of the wireless device 110 to the target network node.

[0190] In a further particular embodiment, the access node comprises a source network node.

[0191] In a particular embodiment, the wireless device 110 receives a handover command from a source network node and initiates a DAPS HO in response to the handover command.

[0192] In a particular embodiment, the information includes the time between declaring the handover failure and declaring the RLF.

[0193] In a particular embodiment, the information includes at least one of radio measurements of a source cell of the dual active protocol stack handover, radio measurements of a target cell of the dual active protocol stack handover, radio measurements of at least one neighbouring cell, the time between sending an RRC reconfiguration complete message to the target node and declaring the RLF, and the status of a timer when the HO command was received from the source network node.

[0194] In a particular embodiment, the information includes at least one of an indication that a radio link failure was declared in a target cell of the dual active protocol stack handover but the dual active protocol stack handover was not successful, an indication that a source release message was not received from the target node, an indication that the wireless device successfully sent an RRC reconfiguration complete message to the target node of the target cell, and an indication as to whether downlink data reception from the source network node was available at the time of declaring the radio link failure.

[0195] In various particular embodiments, the method may additionally or alternatively include one or more of the steps or features of the exemplary embodiments of Groups A1, A2, and C described below.

[0196] FIG. 19 illustrates a schematic block diagram of a virtual device 1100 in a wireless network (e.g., the wireless network shown in FIG. 7). The device may be implemented in a wireless device or a network node (e.g., the wireless device 110 or the network node 160 shown in FIG. 7). The device 1100 is operable to perform the example method described with reference to FIG. 18 and, possibly, any other process or method disclosed herein. It should also be understood that the method of FIG. 18 is not necessarily performed solely by the device 1100. At least some operations of the method may be performed by one or more other entities.

[0197] The virtual device 1100 may comprise a processing circuit, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuit may be configured to execute program code stored in a memory, which may include one or several types of memory, such as a read-only memory (ROM), a random access memory, a cache memory, a flash memory device, an optical storage device, and the like. The program code stored in the memory includes, in some embodiments, program instructions for implementing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuit may be used to cause the declaration module 1110, the first storage module 1120, the second storage module 1130, the transmission module 1140, and any other suitable units of the device 1100 to perform corresponding functions according to one or more embodiments of the present disclosure.

[0198] According to some embodiments, the declaring module 1110 may perform some of the declaring functions of the apparatus 1100. For example, the declaring module 1110 may declare an RLF in a source cell of a source network node during a DAPS HO from a source cell of the source network node to a target cell of the target network node.

[0199] According to some embodiments, the first storage module 1120 may perform some of the storage functions of the device 1100. For example, the first storage module 1120 may store information related to the DAPS HO.

[0200] According to some embodiments, the second storage module 1120 may perform some of the storage functions of the device 1100. For example, the storage module 1120 may store information related to the RLF.

[0201] According to some embodiments, the transmitting module 1140 may perform some of the transmitting functions of the apparatus 1100. For example, the transmitting module 1140 may transmit information to an access node.

[0202] Optionally, in certain embodiments, the virtual device may further include one or more modules for performing any of the steps or providing any of the features in the exemplary embodiments of Group A1, Group A2, and Group C described below.

[0203] The term module or unit as used herein may have its usual meaning in the field of electronics, electrical devices, and / or electronic devices and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid and / or discrete devices, computer programs or instructions, etc., for performing respective tasks, procedures, computations, output and / or display functions, such as those described herein.

[0204] 20 illustrates a method 1200 by the network node 160 according to some embodiments. In step 1202, the network node 160 receives information related to a DAPS HO and an RLF from a wireless device. The RLF is in a source cell of a source network node, and the DAPS HO is from a source cell of the source network node to a target cell of a target network node.

[0205] In a particular embodiment, at least a portion of the information is received in an RLF report or a handover report.

[0206] In a particular embodiment, prior to receiving the information, the network node 160 receives an indication of the availability of the information and sends a request for the information to the wireless device 110.

[0207] In a particular embodiment, the network node 160 establishes a connection with the wireless device 110 after the wireless device 110 declares an RLF with a source cell of the source network node.

[0208] In a particular embodiment, the information indicates that a fallback to a source cell of the source network node has failed.

[0209] In a particular embodiment, the information indicates that a DAPS HO with a target cell of the target network node has failed.

[0210] In a particular embodiment, based on the information, the network node 160 determines at least one reason for the failure of the DAPS HO.

[0211] In a particular embodiment, the network node transmits the information to a source network node.

[0212] In certain embodiments, the network node 160 adjusts or optimizes at least one handover parameter based on the information.

[0213] In a particular embodiment, the first network node includes a source network node, the information indicates a successful handover to a target cell of the target network node, and the RLF relates to a failed connection between the wireless device and the target cell of the target network node.

[0214] In a particular embodiment, the information includes the time between declaring the handover failure and declaring the radio link failure.

[0215] In a particular embodiment, the information includes at least one of radio measurements of a source cell of the DAPS HO, radio measurements of a target cell of the DAPS HO, radio measurements of at least one neighbouring cell, the time between sending a radio resource control reconfiguration complete message to the target node and declaring the RLF, and the status of a timer when the handover command was received from the source network node.

[0216] In various particular embodiments, the method may include one or more of any of the steps or features of the exemplary embodiments of Group B1, Group B2, Group B3, and Group C described below.

[0217] FIG. 21 illustrates a schematic block diagram of a virtual device 1300 in a wireless network (e.g., the wireless network shown in FIG. 7). The device may be implemented in a wireless device or a network node (e.g., the wireless device 110 or the network node 160 shown in FIG. 7). The device 1300 is operable to perform the example method described with reference to FIG. 20 and, possibly, any other process or method disclosed herein. It should also be understood that the method of FIG. 20 is not necessarily performed solely by the device 1300. At least some operations of the method may be performed by one or more other entities.

[0218] The virtual device 1300 may comprise a processing circuit, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuit may be configured to execute program code stored in a memory, which may include one or several types of memory, such as a read-only memory (ROM), a random access memory, a cache memory, a flash memory device, an optical storage device, and the like. The program code stored in the memory includes, in some embodiments, program instructions for implementing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuit may be used to cause the receiving module 1310, and any other suitable units of the device 1300, to perform corresponding functions according to one or more embodiments of the present disclosure.

[0219] According to some embodiments, the receiving module 1310 may perform some of the receiving functions of the apparatus 1300. For example, the receiving module 1310 may receive information related to a DAPS HO and an RLF from the wireless device 110. The RLF is at a source cell of a source network node, and the DAPS HO is from a source cell of a source network node to a target cell of a target network node.

[0220] Optionally, in certain embodiments, the virtual device may further include one or more modules for performing any of the steps or providing any of the features in the exemplary embodiments of Group B1, Group B2, Group B3, and Group C described below.

[0221] Exemplary embodiments Group A1 embodiment Exemplary embodiment 1. A method implemented by a wireless device, the method including: determining an HO failure and performing a fallback to a source node and / or source cell during a handover (HO) of the wireless device; declaring a Radio Link Failure (RLF) prior to successfully sending an HO failure message to the source network node, the HO failure message including one or more measurements related to the HO; generating an RLF report including the one or more measurements related to the HO; and sending the RLF report to an access node. Exemplary embodiment 2. The method according to embodiment 1, in which the type of HO is a dual active protocol stack handover. Exemplary embodiment 3. The method of embodiment 1 or 2, further comprising: sending an HO failure message, where the HO failure message includes one or more measurements related to the HO failure. Exemplary embodiment 4. The method of any one of embodiments 1 to 3, further comprising: receiving a HO command from a network node; and initiating a HO in response to the HO command. Exemplary embodiment 5. The method of any one of embodiments 1 to 4, wherein the one or more measurements related to the HO include at least one of radio measurements of a source cell of the HO, radio measurements of a target cell of the HO, radio measurements of at least one neighboring cell, a time between declaring an HO failure, declaring a radio link failure, and a status of a timer when the HO command is received from the network. Exemplary embodiment 6. The method of any one of embodiments 1 to 5, further comprising: re-establishing a connection with the source node prior to sending the RLF report; sending an indication of the availability of the RLF report to the source node; and receiving a request to send an RLF report, where the RLF report is sent in response to the request. Exemplary embodiment 7. The method of any one of embodiments 1 to 6, wherein the access node is a source node. Exemplary embodiment 8. A computer program comprising instructions for performing any of the methods according to embodiments 1 to 7 when executed on a computer. Exemplary embodiment 9. A computer program product comprising a computer program, the computer program comprising instructions for performing any of the methods described in embodiments 1 to 7 when the computer program is executed on a computer. Exemplary embodiment 10. A non-transitory computer-readable medium storing instructions that, when executed by a computer, perform any of the methods described in embodiments 1-7. Exemplary embodiment 11. A wireless device comprising a processing circuit configured to perform any of the methods described in embodiments 1 to 7. Group A2 embodiment Exemplary embodiment 12. A method implemented by a wireless device, the method including: preparing an HO message indicating successful HO of the wireless device to the target cell in response to a successful handover (HO) of the wireless device to the target cell, the HO message including one or more measurements related to the HO; declaring a Radio Link Failure (RLF) prior to sending the HO message and prior to receiving a source release message; generating an RLF report including the one or more measurements related to the HO message; and transmitting the RLF report. Exemplary embodiment 13. The method according to embodiment 12, wherein the type of HO is a dual active protocol stack handover. Exemplary embodiment 14. The method of embodiment 12 or 13, further comprising: sending an HO failure message, where the HO failure message includes one or more measurements related to the HO failure. Exemplary embodiment 15. The method of any one of embodiments 12 to 14, further comprising receiving a HO command and initiating HO in response to the HO command. Exemplary embodiment 16. The method of any one of embodiments 12 to 15, wherein the one or more measurements related to the HO include at least one of radio measurements of a source cell of the HO, radio measurements of a target cell of the HO, radio measurements of at least one neighboring cell, a time between declaring an HO failure, declaring a radio link failure, a time between sending an RRC reconfiguration complete message to the target node and declaring RLF, and a status of a timer when the HO command is received from the network. Exemplary embodiment 17. The method of any one of embodiments 12 to 16, wherein the RLF report includes at least one of an indication that RLF was declared in the target cell of the HO but the HO was not successful, an indication that there was no receipt of a source release message from the target node, an indication that the wireless device successfully sent an RRC reconfiguration complete message to the target node of the target cell, and an indication as to whether downlink data reception from the source was available at the time of declaring the RLF. Exemplary embodiment 18. The method of any one of embodiments 12 to 17, further comprising: re-establishing a connection with the source node prior to sending the RLF report; sending an indication of the availability of the RLF report to the source node; and receiving a request to send an RLF report, where the RLF report is sent in response to the request. Exemplary embodiment 19. A computer program comprising instructions for performing any of the methods according to embodiments 12 to 18 when executed on a computer. Exemplary embodiment 20. A computer program product comprising a computer program, the computer program comprising instructions for performing any of the methods described in embodiments 12 to 18 when the computer program is executed on a computer. Exemplary embodiment 21. A non-transitory computer-readable medium storing instructions that, when executed by a computer, perform any of the methods described in embodiments 12-18. Exemplary embodiment 22. A wireless device comprising a processing circuit configured to perform any of the methods described in embodiments 12-18. Group B1 embodiment Exemplary embodiment 23. A method implemented by a network node acting as a source network node during a handover (HO) of a wireless device from a source network node to a target network node, the method including receiving a Radio Link Failure (RLF) report from a wireless device that has performed a fallback to the source network node during the HO, the RLF report including one or more measurements related to the HO failure. Exemplary embodiment 24. The method of embodiment 23, wherein the type of handover is a dual active protocol stack handover. Exemplary embodiment 25. The method of embodiment 23 or 24, wherein the RLF report is not a handover failure message indicating a handover failure. Exemplary embodiment 26. The method of any one of embodiments 23 to 25, further comprising receiving an HO failure message, the HO failure message including one or more measurements related to the HO failure. Exemplary embodiment 27. The method of any one of embodiments 23 to 26, further comprising: sending an HO command to the wireless device, the HO being initiated by the wireless device in response to the HO command. Exemplary embodiment 28. The method of any one of embodiments 23 to 27, wherein the one or more measurements related to the HO include at least one of radio measurements of a source cell of the HO, radio measurements of a target cell of the HO, radio measurements of at least one neighboring cell, a time between declaring an HO failure, declaring a radio link failure, and a status of a timer when the HO command is received from the network. Exemplary embodiment 29. The method of any one of embodiments 23 to 28, further comprising re-establishing a connection between the source node and the wireless device prior to receiving the RLF report, receiving an indication of availability of the RLF report from the wireless device, and sending a request to the wireless device to send the RLF report. Exemplary embodiment 30. The method of any one of embodiments 23 to 29, further comprising: sending an RLF report to a target node associated with the HO. Exemplary embodiment 31. The method of embodiment 30, wherein the target node is identified in the RLF report. Exemplary embodiment 32. The method of any one of embodiments 23 to 31, further comprising determining at least one reason for the HO disorder based on the RLF report. Exemplary embodiment 33. The method of any one of embodiments 23 to 32, further comprising adjusting and / or optimizing at least one HO parameter based on the RLF report. Exemplary embodiment 34. A computer program comprising instructions for performing any of the methods according to embodiments 23 to 33 when executed on a computer. Exemplary embodiment 35. A computer program product comprising a computer program, the computer program comprising instructions for performing any of the methods according to embodiments 23 to 33 when the computer program is executed on a computer. Exemplary embodiment 36. A non-transitory computer-readable medium storing instructions that, when executed by a computer, perform any of the methods described in embodiments 23 to 33. Exemplary embodiment 37. A network node comprising processing circuitry configured to perform any of the methods described in embodiments 23 to 33. Group B2 embodiment Exemplary embodiment 38. A method implemented by a network node acting as a source network node during handover (HO) of a wireless device from a source network node to a target network node, the method including receiving a Radio Link Failure (RLF) report from the wireless device, the RLF report including one or more measurements related to the HO of the wireless device to the target node. Exemplary embodiment 39. The method of embodiment 38, wherein the HO is a dual active protocol stack handover. Exemplary embodiment 40. The method of embodiment 38 or 39, further comprising sending an HO command to the wireless device. Exemplary embodiment 41. The method of any one of embodiments 38 to 40, wherein the one or more measurements related to the HO include at least one of radio measurements of a source cell of the HO, radio measurements of a target cell of the HO, radio measurements of at least one neighboring cell, a time between declaring an HO failure, declaring a radio link failure, and a status of a timer when the HO command is received from the network. Exemplary embodiment 42. The method of any one of embodiments 38 to 41, further comprising re-establishing a connection between the source node and the wireless device prior to receiving the RLF report, receiving an indication of availability of the RLF report from the wireless device, and sending a request to the wireless device to transmit the RLF report. Exemplary embodiment 43. The method of any one of embodiments 38 to 42, further comprising sending an RLF report to a target node associated with the HO. Exemplary embodiment 44. The method of embodiment 43, wherein the target node is identified in the RLF report. Exemplary embodiment 45. The method of any one of embodiments 38 to 44, further comprising adjusting and / or optimizing at least one HO parameter based on the RLF report. Exemplary embodiment 46. A computer program comprising instructions for performing any of the methods according to embodiments 38 to 45 when executed on a computer. Exemplary embodiment 47. A computer program product comprising a computer program, the computer program comprising instructions for performing any of the methods described in embodiments 38 to 45 when the computer program is executed on a computer. Exemplary embodiment 48. A non-transitory computer-readable medium storing instructions that, when executed by a computer, perform any of the methods described in embodiments 38 to 45. Exemplary embodiment 49. A network node comprising processing circuitry configured to perform any of the methods described in embodiments 38 to 45. Embodiments of Group B3 Exemplary embodiment 50. A method implemented by a network node operating as a target network node during handover (HO) of a wireless device from a source network node to a target network node, the method including receiving a Radio Link Failure (RLF) report from the node, the RLF report including one or more measurements related to the HO of the wireless device to the target node, and performing at least one action based on the related one or more measurements. Exemplary embodiment 51. The method of embodiment 50, wherein the HO is a dual active protocol stack handover. Exemplary embodiment 52. The method of embodiment 50 or 51, wherein the one or more measurements related to the HO include at least one of radio measurements of a source cell of the HO, radio measurements of a target cell of the HO, radio measurements of at least one neighboring cell, a time between declaring an HO failure, declaring a radio link failure, and a status of a timer when the HO command is received from the network. Exemplary embodiment 53. The method of any one of embodiments 50-52, wherein the node comprises a node that has established a reconnection with the wireless device after a radio link failure (RLF). Exemplary embodiment 54. The method of any one of embodiments 50 to 53, wherein the node is a source node. Exemplary embodiment 55. The method of any one of embodiments 50 to 54, further comprising determining whether the cause of the failure is a source node and / or a source cell or a target node and / or a target cell based on one or more measurements. Exemplary embodiment 56. The method of any one of embodiments 50 to 55, further comprising sending an RLF report to a source node associated with the HO. Exemplary embodiment 57. A computer program comprising instructions for performing any of the methods according to embodiments 50 to 56 when executed on a computer. Exemplary embodiment 58. A computer program product comprising a computer program, the computer program comprising instructions for performing any of the methods described in embodiments 50 to 56 when the computer program is executed on a computer. Exemplary embodiment 59. A non-transitory computer-readable medium storing instructions that, when executed by a computer, perform any of the methods described in embodiments 50 to 56. Exemplary embodiment 60. A network node comprising processing circuitry configured to perform any of the methods described in embodiments 50 to 56. Group C Embodiments Exemplary embodiment 61. A wireless device comprising: a processing circuit configured to perform any of the steps recited in any one of the embodiments of groups A1 and A2; and a power supply circuit configured to supply power to the wireless device. Exemplary embodiment 62. A network node comprising: a processing circuit configured to perform any of the steps recited in any one of the embodiments of groups B1, B2, and B3; and a power supply circuit configured to supply power to a wireless device. Exemplary embodiment 63. A wireless device comprising: an antenna configured to send and receive wireless signals; a radio front-end circuit connected to the antenna and a processing circuit and configured to condition signals communicated between the antenna and the processing circuit, the processing circuit configured to perform any of the steps described in any one of the embodiments of groups A1 and A2; an input interface connected to the processing circuit and configured to enable information input to the wireless device to be processed by the processing circuit; an output interface connected to the processing circuit and configured to output information from the wireless device processed by the processing circuit; and a battery connected to the processing circuit and configured to power the wireless device. Exemplary embodiment 64. A communications system including a host computer, the host computer comprising a processing circuit configured to provide user data and a communications interface configured to forward the user data to a cellular network for transmission to a wireless device, the cellular network comprising a network node having a wireless interface and a processing circuit, the processing circuit of the network node configured to perform any of the steps described in any one of the embodiments of groups B1, B2, and B3. Exemplary embodiment 65. The communication system of embodiment 64, further comprising a network node. Exemplary embodiment 66. The communication system of embodiment 64 or 65, further comprising a wireless device, the wireless device configured to communicate with the network node. Exemplary embodiment 67. A communication system as described in any one of embodiments 64 to 66, wherein the processing circuitry of the host computer is configured to execute a host application thereby providing user data, and the wireless device comprises processing circuitry configured to execute a client application associated with the host application. Exemplary embodiment 68. A method implemented in a communications system including a host computer, a network node, and a wireless device, the method including: providing, at the host computer, user data; and initiating, at the host computer, a transmission conveying the user data to the wireless device over a cellular network comprising the network node, the network node performing any of the steps described in any one of the embodiments of groups B1, B2, and B3. Exemplary Embodiment 69. The method of embodiment 68, further comprising transmitting user data at the network node. Exemplary embodiment 70. The method of embodiment 68 or 69, wherein the user data is provided by executing a host application at the host computer, and the method further includes executing a client application associated with the host application at the wireless device. Exemplary embodiment 71. A wireless device configured to communicate with a network node, the wireless device comprising a radio interface and a processing circuit configured to implement any one of embodiments 68 to 70. Exemplary embodiment 72. A communications system including a host computer, the host computer comprising a processing circuit configured to provide user data and a communications interface configured to forward the user data to a cellular network for transmission to a wireless device, the wireless device comprising a wireless interface and a processing circuit, and components of the wireless device configured to perform any of the steps described in any one of the embodiments of groups A1 and A2. Exemplary Embodiment 73. The communication system of embodiment 72, wherein the cellular network further includes a network node configured to communicate with the wireless device. Exemplary embodiment 74. The communications system of embodiment 72 or 73, wherein the processing circuitry of the host computer is configured to execute a host application thereby providing user data, and the processing circuitry of the wireless device is configured to execute a client application associated with the host application. Exemplary embodiment 75. A method implemented in a communications system including a host computer, a network node, and a wireless device, the method including: providing user data at the host computer; and initiating a transmission at the host computer conveying the user data to the wireless device over a cellular network comprising the network node, the wireless device performing any of the steps described in any one of the embodiments of groups A1 and A2. Exemplary Embodiment 76. The method of embodiment 75, further comprising receiving, at the wireless device, user data from the network node. Exemplary embodiment 77. A communications system including a host computer, the host computer comprising a communications interface configured to receive user data originating from a transmission from a wireless device to a network node, the wireless device comprising a wireless interface and processing circuitry, the processing circuitry of the wireless device configured to perform any of the steps described in any one of the embodiments of groups A1 and A2. Exemplary Embodiment 78. The communication system of embodiment 77, further comprising a wireless device. Exemplary embodiment 79. The communication system of embodiment 77 or 78, further comprising a network node, the network node comprising a wireless interface configured to communicate with the wireless device, and a communication interface configured to forward user data carried by a transmission from the wireless device to the network node to a host computer. Exemplary embodiment 80. The communications system of any one of embodiments 77 to 79, wherein the processing circuitry of the host computer is configured to execute a host application and the processing circuitry of the wireless device is configured to execute a client application associated with the host application, thereby providing user data. Exemplary embodiment 81. A communication system as described in any one of embodiments 77 to 80, wherein processing circuitry of the host computer is configured to execute a host application thereby providing requested data, and processing circuitry of the wireless device is configured to execute a client application associated with the host application thereby providing user data in response to the requested data. Exemplary embodiment 82. A method implemented in a communications system including a host computer, a network node, and a wireless device, the method including receiving, at the host computer, user data transmitted from the wireless device to the network node, and the wireless device performing any of the steps described in any one of the embodiments of groups A1 and A2. Exemplary Embodiment 83. The method of embodiment 82, further comprising, at the wireless device, providing user data to the network node. Exemplary embodiment 84. The method of embodiment 82 or 83, further comprising: executing, at the wireless device, a client application thereby providing user data to be transmitted; and executing, at the host computer, a host application associated with the client application. Exemplary embodiment 85. The method of any one of embodiments 82 to 84, further comprising: executing a client application at the wireless device; and receiving input data at the wireless device to the client application, the input data being provided at the host computer by executing a host application associated with the client application, and the user data to be transmitted being provided by the client application in response to the input data. Exemplary embodiment 86. A communications system including a host computer, the host computer comprising a communications interface configured to receive user data originating from a transmission from a wireless device to a network node, the network node comprising a wireless interface and processing circuitry, the processing circuitry of the network node configured to perform any of the steps recited in any one of the embodiments of groups B1, B2, and B3. Exemplary Embodiment 87. The communication system of embodiment 86, further comprising a network node. Exemplary embodiment 88. The communication system of embodiment 86 or 87, further comprising a wireless device, the wireless device configured to communicate with the network node. Exemplary embodiment 89. The communications system of any one of embodiments 86 to 88, wherein the processing circuitry of the host computer is configured to execute a host application and the wireless device is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer. Exemplary embodiment 90. A method implemented in a communications system including a host computer, a network node, and a wireless device, the method including receiving, at the host computer, from a base station, user data originating from a transmission received by the network node from the wireless device, and the wireless device performing any of the steps described in any one of the embodiments of group A. Exemplary Embodiment 91. The method of embodiment 90, further comprising receiving, at the network node, user data from the wireless device. Exemplary embodiment 92. The method of embodiment 90 or 91, further comprising initiating, at the network node, transmission of the received user data to the host computer. Exemplary embodiment 93. The method of any one of embodiments 90 to 92, wherein the network node comprises a base station. Exemplary embodiment 94. The method of any one of embodiments 90 to 93, wherein the wireless device comprises a user equipment (UE).

[0222] Modifications, additions, or omissions may be made to the systems and devices described herein without departing from the scope of the present disclosure. Components of the systems and devices may be integrated or separated. Moreover, operations of the systems and devices may be performed by more, fewer, or other components. Furthermore, operations of the systems and devices may be performed using any suitable logic, including software, hardware, and / or other logic. As used herein, "each" refers to each member of a set or each member of a subset of a set.

[0223] Modifications, additions, or omissions may be made to the methods described herein without departing from the scope of the disclosure. The methods may include more, fewer, or other steps. Further, the steps may be performed in any suitable order.

[0224] Although the present disclosure has been described with respect to several embodiments, modifications and substitutions of the embodiments will be apparent to those skilled in the art. Therefore, the above description of the embodiments does not limit the present disclosure. Other changes, substitutions, and modifications are possible without departing from the spirit and scope of the present disclosure.

Claims

1. A method (1000) implemented by a wireless device (110), the method comprising: Declaring a radio link failure in a source cell of a source network node during a Dual Active Protocol Stack (DAPS) handover from a source cell of a source network node to a target cell of a target network node (1002); Declaring a DAPS handover failure; storing (1004) information related to the DAPS handover; storing (1006) information related to said radio link failure; sending the information related to the DAPS handover and the information related to the radio link failure in a radio link failure report to the source network node (1008); The method (1000).

2. sending an indication of the availability of the radio link failure report to the source network node; receiving a request to transmit the radio link failure report, the radio link failure report being transmitted in response to the request; The method of claim 1 further comprising:

3. The method of claim 1 or 2, wherein the radio link failure is related to a failed connection between the wireless device and the source cell of the source network node.

4. The method of claim 1 , wherein the source network node establishes a connection with the wireless device after the wireless device declares the radio link failure with the source network node.

5. The method of claim 4 , further comprising: establishing a connection with the source network node prior to sending the radio link failure report.

6. The method of claim 1 , further comprising receiving a handover command from the source network node and initiating the DAPS handover in response to the handover command.

7. The method of claim 1 , wherein the radio link failure report comprises a time between declaring a handover failure and declaring the radio link failure.

8. The radio link failure report comprises: radio measurements of the source cell of the DAPS handover; - radio measurements of a target cell of the DAPS handover; - radio measurements of at least one neighbouring cell; the time between sending an RRC reconfiguration complete message to the target network node and declaring the radio link failure; the status of the timer when the HO command is received from the source network node; The method according to claim 1 , comprising at least one of the following:

9. The method of claim 1 , wherein the information comprises a time elapsed between receipt of a DAPS handover command and a radio link failure in the source cell.

10. A method (1200) performed by a source network node during a Dual Active Protocol Stack (DAPS) handover from a source cell of the source network node to a target cell of a target network node, comprising: receiving information related to the DAPS handover and a radio link failure in a radio link failure report from a wireless device (110) (1202), the radio link failure being in a source cell of the source network node, and the DAPS handover being from the source cell of the source network node to the target cell of the target network node (1202); The method (1200).

11. receiving an indication of availability of the radio link failure report prior to receiving the radio link failure report; sending a request for the radio link failure report to the wireless device; The method of claim 10 further comprising:

12. The method of claim 10 or 11, wherein the source network node establishes a connection with the wireless device after the wireless device declares the radio link failure with the source cell of the source network node.

13. The method of claim 12 , wherein the radio link failure report indicates that the DAPS handover of the target network node with the target cell has failed.

14. The method of claim 13, further comprising adjusting or optimizing at least one handover parameter based on the radio link failure report.

15. The method of any one of claims 10 to 14, wherein the radio link failure report comprises a time between declaring a handover failure and declaring the radio link failure.

16. The radio link failure report comprises: radio measurements of a source cell of the DAPS handover; - radio measurements of a target cell of the DAPS handover; - radio measurements of at least one neighbouring cell; the time between sending a radio resource control reconfiguration complete message to the target network node and declaring the radio link failure; the status of the timer when a handover command is received from the source network node; The method according to any one of claims 10 to 15, comprising at least one of the following:

17. The method of any one of claims 10 to 16, wherein the radio link failure report comprises the time elapsed between receiving a DAPS handover command and a radio link failure in the source cell.

18. Processing circuit (120) A wireless device (110) comprising: Declaring a radio link failure in a source cell of a source network node during a Dual Active Protocol Stack (DAPS) handover from a source cell of a source network node to a target cell of a target network node; Declaring a DAPS handover failure; storing information related to the DAPS handover; storing information relating to said radio link failure; sending the information related to the DAPS handover and the information related to the radio link failure in a radio link failure report to the source network node; A wireless device (110) configured to:

19. 19. The wireless device of claim 18, wherein the processing circuitry is configured to perform any of the methods of claims 2 to 9.

20. A source network node in a dual active protocol stack (DAPS) handover from a source cell of the source network node to a target cell of a target network node, comprising: A processing circuit (120), The processing circuit (120) receiving information related to the DAPS handover and a radio link failure in a radio link failure report from a wireless device (110) (1202), the radio link failure being in the source cell of the source network node, and the DAPS handover being from the source cell of the source network node to a target cell of a target network node (1202); The source network node that is configured to

21. 21. A source network node according to claim 20, wherein the processing circuitry is configured to perform any of the methods according to claims 11 to 17.

Citation Information

Patent Citations

  • Radio base station device, communication control method and communication control program

    JP2013110653A

  • Mobility Robustness in a Cellular Network

    US20160285679A1