Dual active protocol stack and connection / link failure handling

Abstract

A wireless communication device and a method performed by the device enabling performing a dual active protocol stack handover (HO) from a source node / cell to a target node / cell is provided. In response to detecting a radio link failure (RLF) on a source link between the device and the source node / cell, an RLF report related to the source node / cell is generated (1101). In response to detecting an RLF on a target link between the device and the target node / cell, an RLF report related to the target node / cell is generated (1105). An indication that the device has one or more RLF reports related to a DAPS HO failure is included (1109) on a subsequent uplink RRC message to a network node. In response to receiving a request from the network node to send the one or more RLF reports, the one or more RLF reports are sent (1111) to the node.

Description

Technical Field

[0001] This disclosure relates generally to communications, and more specifically to communication methods supporting wireless communications, as well as related devices and nodes. Background Technology

[0002] In 3GPP, a dual connectivity (DC) solution has been specified for LTE (Long Term Evolution) and for the connection between LTE and NR (New Radio). DC involves two nodes: a primary node (MN or MeNB) and a secondary node (SN or SeNB). When more than two nodes are involved, it is called multi-connectivity (MC). 3GPP also proposes using DC in Ultra Reliable Low Latency Communication (URLLC) scenarios to enhance robustness and avoid connection interruptions.

[0003] like Figure 1 As shown, there are different ways to deploy 5G networks with or without interconnection with LTE (also known as Evolved Universal Terrestrial Radio Access (E-UTRA)) and the Evolved Packet Core (EPC). In principle, NR and LTE can be deployed without any interconnection (represented by NR Standalone (SA) operation), meaning that the gNB in ​​NR can connect to the 5G core network (5GC), while the eNB can connect to the EPC, both ( Figure 1 There is no interconnection between Options 1 and 2. On the other hand, the first supported NR version was the so-called EN-DC (Evolved Universal Terrestrial Radio Access Network (E-UTRAN) - NR Dual Connectivity), such as Figure 1 Option 3 is shown in the diagram. In this deployment, dual connectivity between NR and LTE uses LTE as the primary node and NR as the secondary node. The RAN node (gNB) supporting NR may not have a control plane connection to the core network (EPC) but instead relies on LTE as the primary node (MeNB). This is also known as "non-standalone NR". Note that in this case, the functionality of the NR cell is limited and will be used as an enhancement and / or diversity tributary for connected UEs, but RRC_IDLE UEs cannot camp on these NR cells.

[0004] With the introduction of 5GC, other options can also be valid. As mentioned earlier, Option 2 supports standalone NR deployments where the gNB connects to the 5GC. Similarly, LTE can also be used. Figure 1 Option 5 connects to 5GC (also known as eLTE, E-UTRA / 5GC, or LTE / 5GC). In these cases, both NR and LTE are considered part of NG-RAN. It is worth noting that... Figure 1Options 4 / 4A and 7 / 7A shown are other variations of dual connectivity between LTE and NR, which will be standardized as part of the NG-RAN connected to 5GC, represented by MR-DC (Multi-Radio Dual Connectivity). Options 6 and 8, in which gNB connects to EPC (with or without interconnection with LTE), are also possible, but appear less practical and have not been further pursued in 3GPP.

[0005] Under the general term MR-DC, we have:

[0006] • EN-DC (Option 3): LTE is the primary node, and NR is the secondary node (using EPC CN)

[0007] • NE-DC (Option 4): NR is the primary node, while LTE is the secondary node (using 5GCN)

[0008] • NGEN-DC (Option 7): LTE is the primary node, and NR is the secondary node (using 5GCN).

[0009] • NR-DC (variant of option 2): Dual connectivity of both master and slave nodes using NR (with 5GCN)

[0010] Because the migration of these options may vary across different operators, multiple options can be deployed in parallel within the same network. For example, eNB base stations supporting options 3, 5, and 7 and NR base stations supporting options 2 and 4 can coexist in the same network. Combining dual connectivity solutions between LTE and NR also supports CA (carrier aggregation) within each cell group (i.e., primary cell group (MCG) and secondary cell group (SCG)) and dual connectivity between nodes on the same RAT (e.g., NR-NRDC). For LTE cells, the result of these different deployments is the coexistence of LTE cells associated with eNBs connected to EPC, 5GC, or both EPC and 5GC.

[0011] DC has been standardized for LTE and E-UTRA-NR DC (EN-DC).

[0012] The designs of LTE DC and EN-DC differ in terms of which nodes control which content. Basically, there are two options:

[0013] 1. Centralized solutions (such as LTE-DC), and

[0014] 2. Decentralized solutions (such as EN-DC).

[0015] Figure 2The diagram illustrates a schematic control plane architecture that appears to be used for LTE DC and EN-DC. The main difference between LTE DC and EN-DC is that in EN-DC, the SN has a separate RRC entity (NR RRC). This means the SN can also control the UE; sometimes it is unaware of the MN, but the SN often needs to coordinate with the MN. In LTE DC, RRC decisions always originate from the MN (MN to UE). However, it should be noted that the SN still determines its own configuration, as only the SN itself knows what resources, capabilities, etc., it possesses.

[0016] For EN-DC, the significant changes compared to LTE DC are:

[0017] • Introduction of split bearers from SN (referred to as SCG split bearers)

[0018] • Introduction of segmented bearers for RRC

[0019] • Introduction of direct RRC from SN (also known as SCG SRB)

[0020] Figure 3 and Figure 4 The user plane (UP) and control plane (CP) architectures for EN-DC are shown.

[0021] The SN is sometimes referred to as SgNB (where gNB is the NR base station), and in the case where LTE is the master node and NR is the slave node, the MN is called MeNB. In another case where NR is the master node and LTE is the slave node, the corresponding terms are SeNB and MgNB.

[0022] Segmenting RRC messages is primarily used to create diversity, and the sender can decide whether to select one link to schedule the RRC message or to replicate the message on both links. In the downlink, path switching between MCG or SCG branches, or replication on both, is left to the network. On the other hand, for UL, the network configures the UE to use MCG, SCG, or both branches. The terms "branch," "path," and "RLC bearer" are used interchangeably in this specification.

[0023] Carrier aggregation

[0024] When CA is configured, the UE has only one RRC connection with the network. Furthermore, during RRC connection establishment / re-establishment / handover, one serving cell provides NAS mobility information, and during RRC connection re-establishment / handover, another serving cell provides security input. This cell is called the primary cell (PCell). Additionally, depending on the UE's capabilities, secondary cells (SCells) can be configured to form a serving cell set together with the PCell. The serving cell set configured for the UE therefore consists of one PCell and one or more SCells. Furthermore, when dual connectivity is configured, it's possible that one carrier under the SCG is used as the primary SCell (PSCell). Therefore, in this case, we have one PCell and one or more SCells on the MCG, and one PSCell and one or more SCells on the SCG.

[0025] SCell reconfiguration, addition, and removal can be performed via RRC. During intra-RAT handover, RRC can also add, remove, or reconfigure SCells for use with a target PCell. When a new SCell is added, dedicated RRC signaling is used to send all the system information required by the SCell (i.e., when in connected mode, the UE does not need to directly obtain broadcast system information from the SCell).

[0026] Radio Link Failure (RLF)

[0027] Radio link failure due to physical layer issues

[0028] The UE may lose coverage of the cell it is currently connected to. This can happen when the UE enters a fading dip, or when a handover is required but fails as described above. This is especially true if the "handover area" is very short.

[0029] In the UE, the quality of the radio link is typically monitored, for example at the physical layer, as described in 3GPP TS 38.300, TS38.331 and TS 38.133, and is summarized below.

[0030] When a problem is detected at the physical layer according to the criteria defined in TS 38.133, the physical layer sends an indication of the detected problem (asynchrony indication) using the RRC protocol. After a configurable number (N310) of such consecutive indications, a timer (T310) is started. If the link quality is not improved (restored) during T310 (i.e., there are no N311 consecutive "synchronization" indications from the physical layer), a radio link failure is declared in the UE.

[0031] The relevant timers and counters mentioned above are listed here for reference. The UE reads the timer values ​​from system information broadcast in the cell. Alternatively, dedicated signaling can be used to configure UE-specific values ​​and constants for the timers for the UE, i.e., specific values ​​are assigned to a specific UE, and the message is only for each specific UE.

[0032]

[0033]

[0034] Note: In NR, T310 is used for both MCG (Primary Cell Group) and SCG (Secondary Cell Group) (i.e., for NR-DC, (NG)EN-DC). However, for SN running LTE (i.e., LTE-DC, NE-DC), the timer associated with PSCell is T313.

[0035]

[0036]

[0037] If the T310 used for MCG expires, and if Figure 4 As shown, the UE will initiate a connection re-establishment to restore the ongoing RRC connection. This process now includes cell selection performed by the UE. That is, the RRC-connected UE should now attempt to autonomously find a better cell to connect to, since, according to the described measurements, the connection to the previous cell failed (it's possible the UE returned to the first cell anyway, but then performed the same procedure again). Once a suitable cell is selected (as further described in TS38.304), the UE requests to re-establish the connection in the selected cell. It is important to note the difference in mobility behavior, as RLF results in UE-based cell selection, which contrasts with the mobility-based network control typically applied.

[0038] If the reconstruction is successful (which, among other things, depends on the selected cell and whether the gNB controlling that cell is ready to maintain the connection with the UE), the connection between the UE and the gNB can be restored.

[0039] A failed reconstruction means the UE enters RRC IDLE and the connection is released. To continue communication, a new RRC connection must be requested and established.

[0040] The reason for introducing the aforementioned timer T31x and counter N31x is to add some degrees of freedom and hysteresis for configuring the criteria for when a radio link should be considered a failure (and recovery). This is desirable because prematurely abandoning the connection would harm the end-user's performance if the resulting loss of link quality is temporary and the UE successfully recovers the connection without any further action or procedure (e.g., before T310 expires, or before the count reaches the value N310).

[0041] RLF due to other reasons

[0042] In addition to the physical layer issues mentioned above, RLF can also be detected for the following reasons:

[0043] • When there is an indication from the MCG MAC regarding a random access problem; or

[0044] • When there is an indication from the MC RLC that the maximum number of retransmissions has been reached: or

[0045] • If connected as an Integrated Access Backhaul (IAB) node (i.e., a relay node connected to the network via a wireless link), then upon receiving a Backhaul RLF indication from the MCG (i.e., on the link to the parent node)

[0046] • When there is a consensus uplink listen-before-talk (LBT) failure indication from the MCG MAC (when operating in unlicensed spectrum)

[0047] Reduced mobility disruptions in LTE / NR Release 16

[0048] During handover, the duration between the time the UE stops transmitting / receiving with the source node and the time the target node resumes transmitting / receiving with the UE is called the mobility interruption time. The longer the mobility interruption time, the longer the service (user plane data radio bearer) interruption time. New services such as URLLC (Ultra-Reliable Low-Latency Communication) cannot tolerate long mobility interruption times. Therefore, in LTE / NR Release 16, mobility enhancements were specified to reduce mobility interruption time to almost 0 ms. Figure 6 The duration of mobility outages in legacy networks (prior to version 16 LTE / NR) is shown.

[0049] The mechanism proposed in version 16 is called Dual Active Protocol Stack (DAPS) handover. Even after receiving a handover request and simultaneously receiving user data from both the source and target cells, DAPS can continue to send data to / receive data from the source cell. Once a random access procedure and synchronization are performed on the target cell, UL data can be additionally sent to the target cell. Once the UE receives a message from the target cell indicating that the DAPS handover is complete, it stops sending / receiving data to / from the source cell.

[0050] Figure 7A and Figure 7B The DAPS switching process is illustrated. This process consists of the following steps.

[0051] Once the source node has decided to perform a DAPS handover (e.g., based on a received measurement indicating link deterioration between the UE and the source node), the source node sends a DAPS handover request to the target node. It should be noted that DAPS is not necessarily applicable to all DRBs (e.g., MBB bearers with only best-effort QoS and capable of handling mobility disruptions may not be included in DAPS handover, meaning that for such bearers, conventional operations will apply and handover disruptions will occur).

[0052] If the target node accepts the DAPS handover request, it will respond with a DAPS handover request response (alternatively, the target node may respond with a conventional handover request response that does not apply DAPS).

[0053] The source node sends a DAPS handover command to the UE indicating which DRBs are part of the DAPS handover.

[0054] Upon receiving an HO command with an indicator for performing DAPS switching (for each DRB in drb-ToAddModList), the UE:

[0055] • Continue sending and receiving user data on the DAPS DRB in the source cell.

[0056] • Handling DRBs without DAPS using traditional methods

[0057] • Suspend source cell SRB

[0058] • Establish a new connection to the target cell

[0059] The source node sends an Early Forwarding Transmission (for each DAPS DRB, the SN and HFN of the DL PDCP SDU are forwarded first) and begins forwarding DL data to the target node, while continuing to send DL data to the UE. The source node continues to forward UL data received from the UE to the EPC / 5GC on the old path.

[0060] After the RA is completed in the target cell, the UE (for each DAPS DRB):

[0061] • Switch UL data transmission from the source cell to the target cell (retransmit unacknowledged PDCP PDUs and send new PDCP PDUs).

[0062] - The UE sends a PDCP status report to the target node (for each DAPSDRB).

[0063] • Continue receiving DL data from the source cell.

[0064] The target node can perform PDCP duplication checks on the DL data forwarded from the source node based on the PDCP status report received from the UE, and avoid sending duplicate packets to the UE.

[0065] Upon receiving a HANDOVER SUCCESS message from the target node, the source node stops sending user data to / receiving user data from the UE and sends an SNSTATUS TRANSFER message with the final receiver and transmitter states. Traditional data forwarding for any pending DL data can also be performed.

[0066] Upon receiving the SN status transmission message, the target node sends a request to the UE to release the source cell connection (DAPSDRB and SRB). This triggers the UE to send a second PDCP status report (for each DAPS DRB mapped to RLC-AM).

[0067] From this point onward, the UE transmits and receives user data in the target cell. Summary of the Invention

[0068] During a DAPS HO, different types of failures can occur. For example, there can be an RLF to the source cell, an RLF to the target cell, or an RLF to both. An example of an RLF to both is when the UE receives a DAPS HO command and attempts to perform a RA on the target cell. If the RA procedure fails and the UE declares an RLF in the target cell but attempts to return to the source cell, but the timer T310 with the source node / cell has expired, then the UE declares an RLF with respect to the source node / cell. Therefore, the UE detects two RLFs, one for the source node / cell and the other for the target node / cell.

[0069] Currently, 3GPP only focuses on the handling of RLF in the source node / cell.

[0070] Various embodiments of the present invention provide a mechanism in which the UE report involved in the RLF is about the source cell and / or the target cell. The node receiving the RLF report (which may contain two RLF reports about the source cell and the target cell) will identify whether the source cell and / or the target cell does not belong to it, and if so, will pass the RLF report to the node serving the source cell and / or the target cell.

[0071] According to some embodiments of the present invention, a method performed by a wireless communication device to perform a Dual Active Protocol Stack (DAPS) handover (HO) from a source node / cell to a target node / cell includes: generating (1101) an RLF report associated with the source node / cell in response to detecting a Radio Link Failure (RLF) on a source link between the wireless communication device and the source node / cell. The method further includes: generating (1105) an RLF report associated with the target node / cell in response to detecting an RLF on a target link between the wireless communication device and the target node / cell. The method further includes: including (1109) an indication that the wireless communication device has one or more RLF reports associated with a DAPS HO failure on a subsequent uplink Radio Resource Control (RRC) message to a network node. The method further includes: sending (1111) the one or more RLF reports to the network node in response to receiving a request from the network node to send the one or more RLF reports.

[0072] A wireless communication device that performs similar operations is also provided.

[0073] In the absence of some embodiments of the various embodiments described herein, when an RLF occurs on the source cell, target cell, or both during DAPS HO, the typically important information reported by the RLF is not sent to the network after reconnection with the new cell / node (or recovery to the source cell / node), and this may result in suboptimal network decisions / configurations / operations.

[0074] According to other embodiments, a method performed by a first network node providing a connection to a wireless communication device in a wireless network includes: receiving (1201) a notification from the wireless communication device that the wireless communication device has a Radio Link Failure (RLF) report. The method further includes sending (1203) an instruction message to the wireless communication device instructing the wireless communication device to send an RLF report. The method further includes receiving (1205) an RLF report. The method further includes forwarding (1207) an RLF report to a source node serving a source cell in response to: the RLF report containing information about a failure during a Dual Active Protocol Stack (DAPS HO) handover, the RLF report containing failure information related to the source node serving the source cell, and the first network node being different from the source node serving the source cell. The method further includes forwarding (1209) an RLF report to a target node serving a target cell in response to: the RLF report containing information about a failure during a DAPS HO, the RLF report containing failure information related to the target node serving the target cell, and the first network node being different from the target node serving the target cell. The method also includes forwarding (1211) RLF reports to the source node serving the source cell and the target node serving the target cell in response to the following: the RLF report contains information about failures during DAPS HO, the RLF report contains failure information related to the source cell and the target cell, and the first network node is different from the source node serving the source cell and the target node serving the target cell.

[0075] It also provides a network node that performs similar operations. Attached Figure Description

[0076] The accompanying drawings illustrate certain non-limiting embodiments of the inventive concept. These drawings are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application. In the drawings:

[0077] Figure 1 This is a diagram illustrating LTE and NR interconnection options;

[0078] Figure 2 This is a block diagram illustrating the control plane architecture of dual connectivity in LTE DC and EN-DC;

[0079] Figure 3 This is a diagram illustrating the network-side protocol termination options for MCG, SCG, and segmented bearers in MR-DC (EN-DC) using EPC;

[0080] Figure 4 This is a diagram of the network architecture of the control plane in EN-DC;

[0081] Figure 5This is a diagram illustrating a radio link failure caused by a physical layer issue.

[0082] Figure 6 This is a signaling diagram showing the mobility interruption time;

[0083] Figure 7A and Figure 7B This shows the signaling diagram for DAPS handover;

[0084] Figure 8 This is a block diagram illustrating some embodiments of a wireless device (UE) according to the present invention;

[0085] Figure 9 This is a block diagram illustrating a radio access network (RAN) node (e.g., a base station eNB / gNB) according to some embodiments of the present invention.

[0086] Figure 10 This is a block diagram illustrating core network (CN) nodes (e.g., AMF nodes, SMF nodes, etc.) according to some embodiments of the concept of the present invention;

[0087] Figure 11 This is a flowchart illustrating the operation of a communication device (UE) according to some embodiments of the present invention;

[0088] Figure 12A and Figure 12B This is a flowchart illustrating the operation of a network node according to some embodiments of the concept of the present invention;

[0089] Figure 13 This is a block diagram of a wireless network according to some embodiments;

[0090] Figure 14 This is a block diagram of a user equipment according to some embodiments;

[0091] Figure 15 This is a block diagram of a virtualized environment according to some embodiments;

[0092] Figure 16 This is a block diagram of a telecommunications network connected to a host computer via an intermediate network, according to some embodiments;

[0093] Figure 17 This is a block diagram of a host computer that communicates with a user equipment via a base station through a partially wireless connection, according to some embodiments.

[0094] Figure 18 It is a block diagram of a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments;

[0095] Figure 19It is a block diagram of a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments;

[0096] Figure 20 This is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment, according to some embodiments; and

[0097] Figure 21 This is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment, according to some embodiments. Detailed Implementation

[0098] The inventive concept will be described more fully below with reference to the accompanying drawings, which illustrate examples of embodiments of the inventive concept. However, the inventive concept can be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the inventive concept to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be assumed by default to be present / used in another embodiment.

[0099] The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as illustrative examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the embodiments may be modified, omitted, or expanded without departing from the scope of the subject matter.

[0100] Figure 8 This is a block diagram illustrating the elements of a communication device UE 800 (also referred to as a mobile terminal, mobile communication terminal, wireless device, wireless communication equipment, wireless terminal, mobile device, wireless communication terminal, user equipment (UE), user equipment node / terminal / device, etc.) configured to provide wireless communication according to embodiments of the present invention. (The communication device 800 may be provided, for example, as described below regarding...) Figure 13 (As discussed in the wireless device 1310.) As shown in the figure, the communication device UE may include an antenna 807 (e.g., corresponding to...) Figure 13 Antenna 1311) and transceiver circuit 801 (also referred to as transceiver, for example, corresponding to Figure 13 The transceiver circuit 801 includes a transmitter and a receiver, which are configured to provide access to a base station of a radio access network (e.g., corresponding to a base station of a radio access network). Figure 13The network node 1360 (also referred to as the RAN node) provides uplink and downlink radio communication. The communication device UE may further include: a processing circuit 803 (also referred to as a processor, corresponding to processing circuit 1320 in Figure 13), coupled to the transceiver circuitry; and a memory circuit 805 (also referred to as a memory, corresponding to...). Figure 13 A device-readable medium 1330 is coupled to the processing circuitry. Memory circuitry 805 may include computer-readable program code that, when executed by processing circuitry 803, causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 803 may be defined to include memory, thereby eliminating the need for separate memory circuitry. The communication device UE may also include an interface (e.g., a user interface) coupled to processing circuitry 803, and / or the communication device UE may be incorporated into a vehicle.

[0101] As discussed herein, the operation of the communication device UE can be performed by processing circuitry 803 and / or transceiver circuitry 801. For example, processing circuitry 803 can control transceiver circuitry 801 to send communications to a radio access network node (also known as a base station) via a radio interface and / or to receive communications from a RAN node via a radio interface. Furthermore, modules can be stored in memory circuitry 805, and these modules can provide instructions such that when the instructions of the modules are executed by processing circuitry 803, processing circuitry 803 performs corresponding operations (e.g., the operations discussed below with respect to example embodiments related to wireless communication devices). According to some embodiments, communication device UE 800 and / or one or more of its elements / functions can be embodied as one or more virtual nodes and / or one or more virtual machines.

[0102] Figure 9 This is a block diagram illustrating the elements of a radio access network (RAN) node 900 (also referred to as a network node, base station, eNodeB / eNB, gNodeB / gNB, etc.) configured to provide cellular communications according to embodiments of the present invention. (RAN node 900 may be provided, for example, as described below regarding...) Figure 13 (As discussed in the network node 1360.) As shown in the figure, the RAN node may include transceiver circuitry 901 (also referred to as a transceiver, for example, corresponding to...) Figure 13 The transceiver circuit 901 (part of interface 1390) includes a transmitter and a receiver, configured to provide uplink and downlink radio communication with the mobile terminal. The RAN node may include network interface circuitry 907 (also referred to as the network interface, corresponding to...) Figure 13The network interface circuit 907 (part of interface 1390) is configured to provide communication with other nodes of the RAN and / or core network CN (e.g., other base stations). The RAN node may also include: a processing circuit 403 (also referred to as a processor, corresponding to processing circuit 1370) coupled to transceiver circuitry, and a memory circuit 905 (also referred to as a memory, corresponding to...) coupled to the processing circuitry. Figure 13 The device-readable medium 1380. The memory circuitry 905 may include computer-readable program code that, when executed by the processing circuitry 903, causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuitry 903 may be defined to include memory, thereby eliminating the need for separate memory circuitry.

[0103] As discussed herein, the operation of the RAN node can be performed by processing circuitry 903, network interface 907, and / or transceiver 901. For example, processing circuitry 903 can control transceiver 901 to transmit downlink communications to one or more mobile terminal UEs via a radio interface and / or receive uplink communications from one or more mobile terminal UEs via a radio interface. Similarly, processing circuitry 903 can control network interface 907 to transmit communications to one or more other network nodes and / or receive communications from one or more other network nodes via a network interface. Furthermore, modules can be stored in memory 905, and these modules can provide instructions such that when the instructions of the modules are executed by processing circuitry 903, processing circuitry 903 performs corresponding operations (e.g., the operations discussed below with respect to example embodiments related to the RAN node). According to some embodiments, RAN node 900 and / or one or more of its elements / functions can be embodied as one or more virtual nodes and / or one or more virtual machines.

[0104] According to some other embodiments, the network node can be implemented as a core network (CN) node without a transceiver. In this embodiment, transmission to the wireless communication device UE can be initiated by the network node, such that the transmission to the wireless communication device UE is provided through a network node including a transceiver (e.g., through a base station or RAN node). According to an embodiment in which the network node is an RAN node including a transceiver, initiating the transmission can include transmission performed via the transceiver.

[0105] Figure 10This is a block diagram illustrating elements of a CN node (e.g., SMF node, AMF node, etc.) of a core network configured to provide cellular communications according to an embodiment of the present invention. As shown, the CN node may include network interface circuitry 1007 (also referred to as a network interface) configured to provide communication with other nodes in the core network and / or radio access network (RAN). The CN node may also include: processing circuitry 1003 (also referred to as a processor) coupled to the network interface circuitry; and memory circuitry 505 (also referred to as a memory) coupled to the processing circuitry. The memory circuitry 1005 may include computer-readable program code that, when executed by the processing circuitry 1003, causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuitry 1003 may be defined to include memory, thereby eliminating the need for a separate memory circuitry.

[0106] As discussed herein, the operation of the CN node can be performed by processing circuitry 1003 and / or network interface circuitry 1007. For example, processing circuitry 1003 can control network interface circuitry 1007 to send communications to one or more other network nodes and / or receive communications from one or more other network nodes via network interface circuitry. Furthermore, modules can be stored in memory 1005, and these modules can provide instructions such that when the instructions of the modules are executed by processing circuitry 1003, processing circuitry 1003 performs corresponding operations (e.g., the operations discussed below with respect to example embodiments related to the core network node). According to some embodiments, CN node 1000 and / or one or more of its elements / functions can be embodied as one or more virtual nodes and / or one or more virtual machines.

[0107] Before describing various embodiments of the inventive concept, relevant RRC processes that can be used with the various embodiments will be described.

[0108] Radio link failure related actions

[0109] Detection of physical layer problems under RRC_CONNECTED

[0110] UE should:

[0111] 1> If dapsConfig is configured for any DRB, then when T304 is running, upon receiving N310 consecutive "out of sync" indications for the source cell from the lower layer:

[0112] 2> Start timer T310 for the source cell.

[0113] 1> When T300, T301, T304, T311, and T319 are not running, and N310 consecutive "out of sync" indications are received from the lower layer for SpCell:

[0114] 2> For the corresponding SpCell start timer T310.

[0115] Editor's Note: Regarding how / whether to capture the TBC of the stopped RLM in the source cell after a successful RACH to PCell.

[0116] Editor's Note: Further research is needed to examine whether "source cell" is suitable for all DAPS-related changes, or whether "source SpCell" should be used in certain places, such as the timer T310.

[0117] Recovery of physical layer problems

[0118] When the T310 is running, upon receiving N311 consecutive "synchronization" instructions for SpCell from the lower layer, the UE should:

[0119] 1> For the corresponding SpCell, stop timer T310.

[0120] 1> If timer T312 is running, stop timer T312 for the corresponding SpCell.

[0121] Note 1: In this case, the UE maintains the RRC connection without explicit signaling, that is, the UE maintains the entire radio resource configuration.

[0122] Note 2: The period during which L1 does not report “synchronization” or “asynchronization” will not affect the number of consecutive “synchronization” or “asynchronization” indications being evaluated.

[0123] Detection of wireless link failure

[0124] UE should:

[0125] 1> If dapsConfig is configured for any DRB:

[0126] 2> When T310 in the source cell expires; or

[0127] 2> When there is an indication of a random access problem from the source MCG MAC; or

[0128] 2> When there is an indication from the source MCG RLC that the maximum number of retransmissions has been reached; or

[0129] 2> When there is a consistent uplink LBT failure indication from the source MCG MAC:

[0130] 3> Consider the radio link failure to be detected for the source MCG, i.e., the source RLF;

[0131] 4> Suspend all DRBs in the source cell;

[0132] 4> Release the source connection.

[0133] 1> Otherwise:

[0134] 2> When T310 in PCell expires; or

[0135] 2> When T312 in PCell expires; or

[0136] 2> When T300, T301, T304, T311, and T319 are not running, and a random access problem indication exists from the MCG MAC; or

[0137] 2> When there is an indication from the MCG RLC that the maximum number of retransmissions has been reached: or

[0138] 2> If connected as an IAB node, then when a BH RLF indication is received from the MCG on the BAP entity; or

[0139] 2> When T304 is not running, and there is a consistency uplink LBT failure indication from the MCG MAC:

[0140] 3> If the instruction comes from MCG RLC, and CA replication is configured and activated, and only SCells are included for the corresponding logical channel allowedServingCells:

[0141] 4> Initiate the failure information procedure specified in 5.7.5 to report RLC failure.

[0142] 3> Otherwise:

[0143] 4> Consider radio link failures (i.e., RLF) that need to be detected for MCG;

[0144] 4> Discard any segments of the segmented RRC message stored according to 5.7.6.3;

[0145] 4> Store the following radio link failure information in the VarRLF-Report by setting its fields as follows:

[0146] 5. Remove any information included in the VarRLF report (if any);

[0147] 5> Set plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e., include RPLMNs);

[0148] 5> Based on the available SSB and CSI-RS measurements collected before the UE detects the radio link failure, set measResultLastServCell to include the RSRP, RSRQ, and available SINR of the source PCell;

[0149] 5> Set the ssbRLMConfigBitmap and / or csi-rsRLMConfigBitmap in measResultLastServCell to include the radio link monitoring configuration of the source PCell;

[0150] 5> For each NR frequency configured in which measurements are available:

[0151] 6> If measurements based on the SS / PBCH block are available:

[0152] 7> Set measResultListNR in measResultNeighCells to include all available measurements of the best measurement cell except the source PCell. The best measurement cell is based on available measurements collected before the UE detects a radio link failure, and is sorted as follows: if the SS / PBCH block RSRP measurement result is available, the cell with the highest SS / PBCH block RSRP is listed first; otherwise, if the SS / PBCH block RSRQ measurement result is available, the cell with the highest SS / PBCH block RSRQ is listed first; otherwise, the cell with the highest SS / PBCH block SINR is listed first.

[0153] 8> For each included neighboring cell, include available optional fields;

[0154] 6> If CSI-RS-based measurements are available:

[0155] 7> Set measResultListNR in measResultNeighCells to include all available measurements of the best measurement cell except the source PCell. The best measurement cell is based on available CSI-RS measurements collected before the UE detects a radio link failure, and is sorted as follows: if CSI-RS RSRP measurement results are available, the cell with the highest CSI-RS RSRP is listed first; otherwise, if CSI-RS RSRQ measurement results are available, the cell with the highest CSI-RS RSRQ is listed first; otherwise, the cell with the highest CSI-RS SINR is listed first.

[0156] 8> For each included neighboring cell, include available optional fields;

[0157] 5> For each EUTRA frequency configured in which measurements are available:

[0158] 6> Set measResultListEUTRA in measResultNeighCells to include the best measurement cell. The best measurement cell is based on measurements collected before the UE detects a radio link failure and is sorted in the following way: if RSRP measurement results are available, the cell with the highest RSRP is listed first; otherwise, the cell with the highest RSRQ is listed first.

[0159] Note: The measured quantities are filtered by the L3 filter configured in the mobility measurement configuration. If time-domain measurement resource constraints are configured, the measurements are based on those constraints. Reporting of blacklisted cells is not required.

[0160] 5> If detailed location information is available, set the content of locationInfo as follows:

[0161] 6> If available, set commonLocationInfo to include detailed location information;

[0162] 6> If available, set bt-LocationInfo in locationInfo to include Bluetooth measurement results in the order of decreasing RSSI of Bluetooth beacons;

[0163] 6> If available, set wlan-LocationInfo in locationInfo to include WLAN measurement results in the order of decreasing RSSI of WLAN APs;

[0164] 6> If available, set the sensor-LocationInfo in locationInfo to include sensor measurements;

[0165] 5> If available, set failedPCellId to the global cell identifier and tracking area code; otherwise, set it to the physical cell identifier and carrier frequency of the PCell in which the radio link failure was detected.

[0166] 5> If an RRCReconfiguration message including reconfigurationWithSync is received before the connection fails:

[0167] 6> If the last RRCReconfiguration message including reconfigurationWithSync involves an intra-NR handover:

[0168] 7> Include the previousPCellId and set it as the global cell identifier and tracking area code of the PCell, in which the last RRCReconfiguration message including reconfigurationWithSync is received;

[0169] 7> Set timeConnFailure to the elapsed time since the last RRCReconfiguration message, including reconfigurationWithSync, was received;

[0170] 5> Set connectionFailureType to rlf;

[0171] 5> Set c-RNTI to the C-RNTI used in PCell;

[0172] 5> Set the RLF reason to be used as a trigger for detecting wireless link failure;

[0173] 5> If the RLF reason is set to randomAccessProblem or beamFailureRecoveryFailure:

[0174] 6> Set absoluteFrequencyPointA to indicate the absolute frequency of the reference resource block associated with the random access resource;

[0175] 6> Set the locationAndBandwidth and subcarrierSpacing associated with the UL BWP for random access resources;

[0176] 6> Configure msg1-FrequencyStart, msg1-FDM, and msg1-SubcarrierSpacing associated with random access resources;

[0177] 6> In perRAInfoList, set the parameters associated with a single random access attempt in chronological order as follows:

[0178] 7> If the random access resource used is associated with an SS / PBCH block, then for one or more random access attempts, the associated random access parameters for consecutive random access attempts associated with the same SS / PBCH block are set as follows:

[0179] 8> Set the ssb index to include the SS / PBCH block index associated with the random access resources used;

[0180] 8> Set numberOfPreamblesSentOnSSB to indicate the number of consecutive random access attempts associated with an SS / PBCH block;

[0181] 8> For each random access attempt performed on the random access resource, the following parameters are included in the chronological order of the random access attempts:

[0182] 9> For the preamble sent, if the race condition is not resolved (as specified in TS 38.321[6]):

[0183] 10> Set contentionDetected to true;

[0184] 9> Otherwise:

[0185] 10> Set contentionDetected to false;

[0186] 9> If the SS / PBCH block RSRP of the SS / PBCH block corresponding to the random access resource used in the random access attempt is higher than rsrp-ThresholdS SB:

[0187] 10> Set dlRSRPAboveThreshold to true;

[0188] 9> Otherwise:

[0189] 10> Set dlRSRPAboveThreshold to false;

[0190] 7> Otherwise, if the random access resource used is associated with a CSI-RS, the associated random access parameters for consecutive random access attempts associated with the same CSI-RS will be set as follows for one or more random access attempts:

[0191] 8> Configure the CSI-RS index to include the CSI-RS index associated with the random access resources used;

[0192] 8> Set numberOfPreamblesSentOnCSI-RS to indicate the number of consecutive random access attempts associated with CSI-RS;

[0193] 8> For each random access attempt performed on the random access resource, the following parameters are included in the chronological order of the random access attempts:

[0194] 9> For the preamble sent, if the race condition is not resolved (as specified in TS 38.321[6]):

[0195] 10> Set contentionDetected to true;

[0196] 9> Otherwise:

[0197] 10> Set contentionDetected to false;

[0198] 9> If the CSI-RS RSRP corresponding to the random access resource used in the random access attempt is higher than rsrp-ThresholdCSI-RS:

[0199] 10> Set dlRSRPAboveThreshold to true;

[0200] 9> Otherwise:

[0201] 10> Set dlRSRPAboveThreshold to false;

[0202] 4> If AS security has not yet been activated:

[0203] 5> Upon entering RRC_IDLE, perform the action specified in 5.3.11, with the release reason set to "Other";

[0204] 4> Otherwise, if AS security has been activated, but SRB2 and at least one DRB or SRB2 (for IAB) have not yet been established:

[0205] 5> When entering RRC_IDLE, perform the action specified in 5.3.11, releasing the connection with the reason "RRC connection failed";

[0206] 4> Otherwise:

[0207] 5> If T316 is configured; and

[0208] 5> If SCG transmission is not paused; and

[0209] 5> If the PSCell change is not in progress (i.e., in the case of NR-DC, timer T304 of the NR PSCell is not running, or in the case of NE-DC, timer T307 of the E-UTRA PSCell is not running, as specified in section 5.3.10.10 of TS 36.331

[10] ):

[0210] 6> Initiate the MCG failure information procedure as specified in 5.7.3b to report radio link failure to the MCG.

[0211] 5> Otherwise:

[0212] 6> Initiate the connection reconstruction process specified in 5.3.7.

[0213] The UE can discard radio link failure information, that is, release the UE variable VarRLF-Report 48 hours after detecting a radio link failure.

[0214] UE should:

[0215] 1> When T310 in PSCell expires; or

[0216] 1> When T312 in PSCell expires; or

[0217] 1> When there is a random access problem indication from the SCG MAC; or

[0218] 1> When there is an indication from the SCG RLC that the maximum number of retransmissions has been reached: or

[0219] 1> If connected as an IAB node, then when a BH RLF indication is received from the SCG on the BAP entity; or

[0220] 1> When there is a consistent uplink LBT failure indication from the SCG MAC:

[0221] 2> If the instruction comes from the SCG RLC and CA replication is configured and activated; and for the corresponding logical channel, allowedServingCells only includes SCells:

[0222] 3> Initiate the failure information procedure specified in 5.7.5 to report RLC failure.

[0223] 2> Otherwise, if the MCG transmission is not paused:

[0224] 3> It is believed that a radio link failure was detected for the SCG, i.e., SCG RLF;

[0225] 3> Initiate the SCG failure information procedure specified in 5.7.3 to report SCG radio link failure.

[0226] 2> Otherwise:

[0227] 3> If the UE is in NR-DC:

[0228] 4> Initiate the connection reconstruction procedure specified in 5.3.7;

[0229] 3> Otherwise (UE is in (NG)EN-DC):

[0230] 4> Initiate the connection rebuilding procedure specified in Section 5.3.7 of TS 36.331

[10] .

[0231] As previously indicated, different types of failures can occur during a DAPS HO. For example, there may be an RLF to the source cell, an RLF to the target cell, or an RLF to both. For instance, suppose the UE receives a DAPS HO command and attempts to perform an RA procedure for the target cell. If the RA procedure fails and the UE declares an RLF in the target cell but attempts to return to the source node / cell, but the timer T310 with the source node / cell has expired, and the UE declares an RLF with respect to the source cell, then the UE detects two RLFs, one for the source cell and the other for the target cell.

[0232] Currently, 3GPP only pays attention to the handling of RLF in the source cell.

[0233] Various embodiments of the present invention provide a mechanism in which a wireless communication device (e.g., a UE) involved in an RLF reports an RLF about a source cell and / or a target cell. A node receiving the RLF report (which may contain two RLF reports about the source cell and the target cell) will identify whether the source cell and / or the target cell do not belong to it, and if so, will forward the RLF report to the node serving the source cell and / or the target cell.

[0234] In the absence of the various embodiments of the inventive concept described herein, when an RLF occurs on the source cell, target cell, or both during DAPS HO, the typically important information reported by the RLF is not sent to the network after reconnection with the new cell / node (or recovery to the source cell / node), and this may result in suboptimal network decisions / configurations / operations.

[0235] Some embodiments of the present invention will now be referenced. Figure 11 The flowchart is used to discuss the process from wireless communication device 800 (using Figure 8 The angle operation is implemented using a block diagram structure. For example, the module can be stored in... Figure 3 The memory 805 contains these modules, and these modules can provide instructions such that when the instructions of the modules are executed by the corresponding communication device processing circuit 803, the processing circuit 803 performs the corresponding operation of the flowchart.

[0236] Go to Figure 11 This illustrates a method for performing a dual active protocol stack (DAPS) handover from a source node / cell to a target node / cell at a wireless communication device (e.g., a user equipment (UE)), where the source node and the target node can be the same or different.

[0237] In block 1101, processing circuitry 803 generates an RLF report associated with the source node / cell in response to detecting a radio link failure (RLF) on the source link between the wireless communication device and the source node / cell. In block 1103, processing circuitry 803 stores the RLF report associated with the source node / cell.

[0238] In block 1105, processing circuitry 803 generates an RLF report related to the target node / cell in response to detecting a radio link failure (RLF) on the target link between the wireless communication device and the target node / cell. In block 1107, processing circuitry 803 stores the RLF report related to the target node / cell.

[0239] In some embodiments, storing RLF reports includes storing each RLF report within the same RLF report information element. For example, an RLF report can be enhanced to include both types of reports, as shown in bold and underlined text, while a UE variable contains only one entry, as shown below, for example...

[0240]

[0241]

[0242]

[0243]

[0244] In some other embodiments, storing RLF reports includes storing each RLF report in an RLF report information element such that each RLF report information element contains only one RLF report. Therefore, the RLF report is stored separately and no additional information elements are used. For example, in one embodiment, a wireless communication device 800 may store RLF reports as follows:

[0245]

[0246] In block 1109, processing circuitry 803 includes an indication on a subsequent uplink radio resource control (RRC) message to the network node that the wireless communication device has one or more RLF reports related to a DAPS HO failure. For example, the RRC message may be an RRCReconfigurationComplete message, an RRCResumeComplete message, an RRCSetupComplete message, an RRCReestablishmentComplete message, a UEAssistanceInformation message, etc. In one embodiment, the indication that the one or more RLF reports are related to a DAPS HO failure is included in the RLF cause value (e.g., the rlf-Cause IE in the modified / extended RLF-Report IE). In another embodiment, the indication that the one or more RLF reports are related to a DAPS HO failure is provided in the information element used to indicate the DAPS HO failure (i.e., a Boolean flag indicating whether the RLF report is related to a DAPS HO, and a conventional rlf-Cause IE for indicating the cause of the failure (e.g., t310-expiry, RA problem, etc.)).

[0247] A network node can be a node that serves the source cell, a node that serves the target cell, a node that serves both the source and target cells, or a node that serves neither the source nor the target cell.

[0248] In block 1111, processing circuitry 803, in response to receiving a request from the network node to send the one or more RLF reports, sends the one or more RLF reports to the network node. This request may be a UEInformationRequest. A response may then be sent using a UEInformationResponse message.

[0249] From Figure 11 The various operations in the flowchart may be optional for some embodiments of the communication device and related methods. For example, regarding the method of Example Embodiment 1 (described below), Figure 11The operations in boxes 1103 and 1105 can be optional.

[0250] Reference will now be made to some embodiments based on the concept of the present invention. Figure 12A and Figure 12B The flowchart is used to discuss the connection from the first network node 900 to the wireless communication device (using... Figure 9 Operations from the perspective of (structural implementation). For example, modules can be stored in... Figure 9 The memory 905 contains these modules, and these modules can provide instructions such that when the instructions of the modules are executed by the corresponding network node processing circuit 903, the processing circuit 903 performs the corresponding operation of the flowchart.

[0251] Turn Figure 12A In block 1201, processing circuitry 903 receives a notification from the wireless communication device via transceiver circuitry 901 and / or network interface circuitry 907 regarding a radio link failure (RLF) report from the wireless communication device. This notification may be an instruction as described above.

[0252] In block 1203, processing circuitry 903 sends an instruction message to wireless communication device via transceiver circuitry 901 and / or network interface circuitry 907, instructing the wireless communication device to send an RLF report. This request is sent in a UEInformationRequest message.

[0253] In block 1205, processing circuitry 903 receives RLF reports via transceiver circuitry 901 and / or network interface circuitry 907. An RLF report can be a single information element or multiple RLF reports from multiple information elements, as described above.

[0254] In block 1207, processing circuitry 903 forwards an RLF report to the source node serving the source cell via transceiver circuitry 901 and / or network interface circuitry 907 in response to the following: the RLF report contains information about failures during Dual Active Protocol Stack Switching (DAPSHO); the RLF report contains failure information related to the source node serving the source cell; and the first network node is different from the source node serving the source cell.

[0255] In some embodiments, forwarding an RLF report to a source node serving a source cell includes forwarding the RLF report to the source node serving the source cell via X2 / Xn messages / signaling. In other embodiments, forwarding an RLF report to a source node serving a source cell includes forwarding the RLF report to the source node serving the source cell via inter-node radio resource control (RRC) messages.

[0256] In other embodiments, in response to the source node employing a centralized cell / distributed cell (CU / DU) partitioned architecture, forwarding the RLF report includes forwarding the RLF report to the source node's CU. The CU may further forward (all or part of the information from the RLF) to the DU serving the source cell indicated in the RLF report. In other embodiments, sending the report to the source node's RLF includes sending the RLF report to the source node via a core network function / node. The core network function / node may be an Access and Mobility Management Function (AMF) function / node (e.g., via an NG interface, where a first network node sends a message to the AMF, and the AMF forwards the message to the source node serving the source cell).

[0257] In block 1209, processing circuitry 903 forwards an RLF report to the target node serving the target cell via transceiver circuitry 901 and / or network interface circuitry 907 in response to the following: the RLF report contains information about failures during dual active protocol stack handover (DAPS HO), the RLF report contains failure information related to the target node serving the target cell, and the first network node is different from the target node serving the target cell.

[0258] In some embodiments, forwarding an RLF report to a target node serving a target cell includes forwarding the RLF report to the target node serving the target cell via X2 / Xn messages / signaling. In other embodiments, forwarding an RLF report to a target node serving a target cell includes forwarding the RLF report to the target node serving the target cell via inter-node radio resource control (RRC) messages.

[0259] In other embodiments, in response to the target node employing a centralized cell / distributed cell (CU / DU) segmentation architecture, forwarding the RLF report includes forwarding the RLF report to the target node's CU. The CU may further forward (all or part of the information from the RLF) to the DU serving the target cell indicated in the RLF report. In other embodiments, sending the report to the target node's RLF includes sending the RLF report to the target node via a core network function / node. The core network function / node may be an Access and Mobility Management Function (AMF) function / node (e.g., via an NG interface, where a first network node sends a message to the AMF, and the AMF forwards the message to the target node serving the target cell).

[0260] Turn Figure 12BIn block 1211, processing circuit 903 forwards an RLF report to the source node serving the source cell and the target node serving the target cell via transceiver circuit 901 and / or network interface circuit 907 in response to the following: the RLF report contains information about failures during DAPS HO, the RLF report contains failure information related to the source cell and the target cell, and the first network node is different from the source node serving the source cell and the target node serving the target cell.

[0261] In box 1213, processing circuitry 903 forwards RLF reports to at least one network node that is processing self-organizing network / minimized drive test (SON / MDT) in a wireless network.

[0262] From Figure 12A and Figure 12B The various operations in the flowchart may be optional for some embodiments of the first network node and related methods. Regarding the method of Example Embodiment 19 (described below), for example, Figure 12A and Figure 12B The operation in box 1213 can be optional.

[0263] Therefore, when an RLF occurs in the source cell, target cell, or both during DAPS HO, the typically important information reported by the RLF is not sent to the network after the connection is re-established with the new cell / node (or restored to the source cell / node), and this may lead to better network decisions / configuration / operation.

[0264] The following discusses example implementations.

[0265] Example 1. A method executed by a wireless communication device for performing a dual active protocol stack (DAPS) handover (HO) from a source node / cell to a target node / cell, the method comprising:

[0266] In response to the detection of a radio link failure (RLF) on the source link between the wireless communication device and the source node / cell, an (1101) RLF report related to the source node / cell is generated;

[0267] In response to the detection of an RLF on the target link between the wireless communication device and the target node / cell, an RLF report related to the target node / cell is generated (1105);

[0268] The subsequent uplink radio resource control (RRC) message to the network node includes (1109) an indication that the wireless communication device has one or more RLF reports related to DAPS HO failure;

[0269] In response to receiving a request from the network node to send the one or more RLF reports, send (1111) the one or more RLF reports to the network node.

[0270] Example 2. The method according to Example 1 further includes storing (1103) an RLF report associated with the source node / cell.

[0271] Example 3. The method according to any one of Examples 1 to 2 further includes storing (1107) an RLF report associated with the target node / cell.

[0272] Example 4. The method according to any one of Examples 2 to 3, wherein storing (1103, 1107) RLF reports includes: storing each RLF report having the same RLF report information elements.

[0273] Example 5. The method according to any one of Examples 2 to 3, wherein storing (1103, 1107) RLF reports includes: storing each RLF report in an RLF report information element by making each RLF report information element contain only one RLF report.

[0274] Example 6. The method according to any one of Examples 1 to 5, wherein an indication related to the failure of the one or more RLF reports associated with DAPS HO is included in the RLF cause value.

[0275] Example 7. The method according to any one of Examples 1 to 5, wherein an indication related to the failure of the one or more RLF reports is provided in the information element used to indicate the failure of the DAP HO.

[0276] Example 8. A wireless communication device (800) suitable for performing operations, the operations including:

[0277] In response to the detection of a radio link failure (RLF) on the source link between the wireless communication device and the source node / cell, an (1101) RLF report related to the source node / cell is generated;

[0278] In response to the detection of an RLF on the target link between the wireless communication device and the target node / cell, an RLF report related to the target node / cell is generated (1105);

[0279] The subsequent uplink radio resource control (RRC) message to the network node includes (1109) an indication that the wireless communication device has one or more RLF reports related to DAPS HO failure;

[0280] In response to receiving a request from the network node to send the one or more RLF reports, send (1111) the one or more RLF reports to the network node.

[0281] Example 9. A wireless communication device (800) according to Example 8, wherein the wireless communication device is adapted to perform the operation described in any one of Examples 2 to 7.

[0282] Example 10. A wireless communication device (800), comprising:

[0283] Processing circuit (803); and

[0284] A memory (805), coupled to the processing circuitry, wherein the memory includes instructions that, when executed by the processing circuitry, cause the wireless communication device to perform operations, including:

[0285] In response to the detection of a radio link failure (RLF) on the source link between the wireless communication device and the source node / cell, an (1101) RLF report related to the source node / cell is generated;

[0286] In response to the detection of an RLF on the target link between the wireless communication device and the target node / cell, an RLF report related to the target node / cell is generated (1105);

[0287] The subsequent uplink radio resource control (RRC) message to the network node includes (1109) an indication that the wireless communication device has one or more RLF reports related to DAPS HO failure;

[0288] In response to receiving a request from the network node to send the one or more RLF reports, send (1111) the one or more RLF reports to the network node.

[0289] Example 11. The wireless communication device (800) according to Example 10, wherein the memory further includes instructions that, when executed by the processing circuit, cause the wireless communication device to perform an operation that further includes storing (1103) an RLF report associated with the source node / cell.

[0290] Example 12. A wireless communication device (800) according to any one of Examples 10 to 11, wherein the memory further includes instructions that, when executed by the processing circuit, cause the wireless communication device to perform an operation further including storing (1107) an RLF report associated with the target node / cell.

[0291] Example 13. A wireless communication device (800) according to any one of Examples 11 to 12, wherein, when storing (1103, 1107) the RLF report, the memory further includes instructions that, when executed by the processing circuit, cause the wireless communication device to perform an operation including storing each RLF report having the same RLF report information elements.

[0292] Example 14. A wireless communication device (800) according to any of Examples 11 to 12, wherein, when storing (1103, 1107) the RLF report, the memory further includes instructions that, when executed by the processing circuit, cause the wireless communication device to perform an operation, the operation including: storing each RLF report in an RLF report information element such that each RLF report information element contains only one RLF report.

[0293] Example 15. A wireless communication device (800) according to any one of Examples 10 to 14, wherein an indication related to the failure of the one or more RLF reports associated with DAPS HO is included in the RLF cause value.

[0294] Example 16. A wireless communication device (800) according to any one of Examples 10 to 14, wherein an indication related to the failure of the one or more RLF reports is provided in an information element for indicating a DAP HO failure.

[0295] Example 17. A computer program comprising program code to be executed by a processing circuitry (803) of a wireless communication device (800), wherein execution of the program code causes the wireless communication device (S00) to perform the operations described in any of Examples 1 to 7.

[0296] Example 18. A computer program product including a non-transitory storage medium including program code to be executed by a processing circuitry (803) of a wireless communication device (800), wherein execution of the program code causes the wireless communication device (800) to perform the operations described in any one of Examples 1 to 7.

[0297] Example 19. A method performed by a first network node providing a connection to a wireless communication device in a wireless network, the method comprising:

[0298] Receive (1201) a notification from the wireless communication device regarding a radio link failure (RLF) report from the wireless communication device;

[0299] Send an instruction message (1203) to the wireless communication device, instructing the wireless communication device to send the RLF report;

[0300] Receive the RLF report (1205);

[0301] The RLF report is forwarded to the source node serving the source cell in response to the following: the RLF report contains information about failures during the dual active protocol stack handover DAPS HO, the RLF report contains failure information related to the source node serving the source cell, and the first network node is different from the source node serving the source cell.

[0302] The RLF report is forwarded (1209) to the target node serving the target cell in response to the following: the RLF report contains information about a failure during the DAPS HO; the RLF report contains failure information related to the target node serving the target cell; and the first network node is different from the target node serving the target cell; and

[0303] The first network node is forwarded (1211) to the source node serving the source cell and the target node serving the target cell in response to the following: the RLF report contains information about failures during DAPS HO, the RLF report contains failure information related to the source cell and the target cell, and the first network node is different from the source node serving the source cell and the target node serving the target cell.

[0304] Example 20. The method according to Example 19 further includes: forwarding (1213) the RLF report to at least one network node that processes self-organizing network / minimized drive test SON / MDT in the wireless network.

[0305] Example 21. The method according to any one of Examples 19 to 20, wherein forwarding the RLF report to the source node serving the source cell includes: forwarding the RLF report to the source node serving the source cell via X2 / Xn messages / signaling.

[0306] Example 22. The method according to any one of Examples 19 to 20, wherein forwarding the RLF report to the target node serving the target cell includes: forwarding the RLF report to the target node serving the target cell via X2 / Xn messages / signaling.

[0307] Example 23. The method according to any one of Examples 19 to 20, wherein forwarding the RLF report to the source node serving the source cell includes: forwarding the RLF report to the source node serving the source cell via an inter-node radio resource control (RRC) message.

[0308] Example 24. The method according to any one of Examples 19 to 20, wherein forwarding the RLF report to the target node serving the target cell includes: forwarding the RLF report to the target node serving the target cell via an inter-node radio resource control (RRC) message.

[0309] Example 25. According to the method described in Examples 19 to 20, wherein, in response to at least one of the source node and the target node adopting a centralized unit / distributed unit (CU / DU) partitioning architecture, forwarding the RLF report includes: forwarding the RLF report to the CU of the at least one of the source node and the target node.

[0310] Example 26. The method according to any one of Examples 19 to 20, wherein sending the RLF report to the source node and sending the RLF report to the target node includes: sending the RLF report to the source node via a core network function / node, and sending the RLF report to the target node via the core network function / node.

[0311] Example 27. The method according to Example 26, wherein the core network function / node includes an Access and Mobility Management Function (AMF) function / node.

[0312] Example 28. A first network node (900) in a wireless network, the first network node (900) being adapted to perform operations including:

[0313] Receive (1201) a notification from the wireless communication device regarding a radio link failure (RLF) report from the wireless communication device;

[0314] Send an instruction message (1203) to the wireless communication device, instructing the wireless communication device to send the RLF report;

[0315] Receive the RLF report (1205);

[0316] The RLF report is forwarded to the source node serving the source cell in response to the following: the RLF report contains information about failures during the dual active protocol stack handover DAPS HO, the RLF report contains failure information related to the source node serving the source cell, and the first network node is different from the source node serving the source cell.

[0317] The RLF report is forwarded (1209) to the target node serving the target cell in response to the following: the RLF report contains information about a failure during the DAPS HO; the RLF report contains failure information related to the target node serving the target cell; and the first network node is different from the target node serving the target cell; and

[0318] The first network node is forwarded (1211) to the source node serving the source cell and the target node serving the target cell in response to the following: the RLF report contains information about failures during DAPS HO, the RLF report contains failure information related to the source cell and the target cell, and the first network node is different from the source node serving the source cell and the target node serving the target cell.

[0319] Example 29. The first network node (900) according to Example 28, wherein the first network node (900) is further adapted to perform the operations described in any of Examples 20 to 27.

[0320] Example 30. A first network node (900) in a wireless network, the first network node (900) comprising:

[0321] Processing circuit (903); and

[0322] A memory (905), coupled to the processing circuitry, wherein the memory includes instructions that, when executed by the processing circuitry, cause the first network section to perform an operation, the operation including:

[0323] Receive (1201) a notification from the wireless communication device regarding a radio link failure (RLF) report from the wireless communication device;

[0324] Send an instruction message (1203) to the wireless communication device, instructing the wireless communication device to send the RLF report;

[0325] Receive the RLF report (1205);

[0326] The RLF report is forwarded (1207) to the source node serving the source cell in response to the following: the RLF report contains information about failures during the dual active protocol stack handover DAPSHO, the RLF report contains failure information related to the source node serving the source cell, and the first network node is different from the source node serving the source cell;

[0327] The RLF report is forwarded (1209) to the target node serving the target cell in response to the following: the RLF report contains information about a failure during the DAPS HO; the RLF report contains failure information related to the target node serving the target cell; and the first network node is different from the target node serving the target cell; and

[0328] The first network node is forwarded (1211) to the source node serving the source cell and the target node serving the target cell in response to the following: the RLF report contains information about failures during DAPS HO, the RLF report contains failure information related to the source cell and the target cell, and the first network node is different from the source node serving the source cell and the target node serving the target cell.

[0329] Example 31. The first network node (900) according to Example 30, wherein the memory further includes instructions that, when executed by the processing circuit, cause the first network node to perform an operation, the operation further including forwarding (1213) the RLF report to at least one network node processing Ad Hoc Network / Minimized Drive Test (SON / MDT) in the wireless network.

[0330] Example 32. A first network node (900) according to any one of Examples 30 to 31, wherein, when forwarding the RLF report to a source node serving the source cell, the memory includes instructions that, when executed by the processing circuitry, cause the first network node to perform an operation including forwarding the RLF report to a source node serving the source cell via X2 / Xn messages / signaling.

[0331] Example 33. A first network node (900) according to any one of Examples 30 to 31, wherein, when forwarding the RLF report to a target node serving the target cell, the memory includes instructions that, when executed by the processing circuit, cause the first network node to perform an operation including forwarding the RLF report to the target node serving the target cell via X2 / Xn messages / signaling.

[0332] Example 34. A first network node (900) according to any of Examples 30 to 31, wherein, when forwarding the RLF report to a source node serving the source cell, the memory includes instructions that, when executed by the processing circuitry, cause the first network node to perform an operation including forwarding the RLF report to a source node serving the source cell via an inter-node radio resource control (RRC) message.

[0333] Example 35. A first network node (900) according to any one of Examples 30 to 31, wherein, when forwarding the RLF report to a target node serving the target cell, the memory includes instructions that, when executed by the processing circuitry, cause the first network node to perform an operation including forwarding the RLF report to the target node serving the target cell via an inter-node radio resource control (RRC) message.

[0334] Example 36. A first network node (900) according to Examples 30 to 31, wherein, in response to at least one of the source node and the target node adopting a centralized unit / distributed unit (CU / DU) partitioned architecture, when forwarding the RLF report, the memory includes instructions that, when executed by the processing circuitry, cause the first network node to perform an operation including forwarding the RLF report to the CU of at least one of the source node and the target node.

[0335] Example 37. A first network node (900) according to any one of Examples 30 to 31, wherein, when sending the RLF report to the source node and when sending the RLF report to the target node, the memory includes instructions that, when executed by the processing circuitry, cause the first network node to perform operations including sending the RLF report to the source node via a core network function / node and sending the RLF report to the target node via the core network function / node.

[0336] Example 38. The first network node (900) according to Example 26, wherein the core network function / node includes an Access and Mobility Management Function (AMF) function / node.

[0337] Example 39. A computer program comprising program code to be executed by a processing circuitry (903) of a first network node (900), wherein execution of the program code causes the first network node (900) to perform the operations described in any of Examples 19 to 27.

[0338] Example 40. A computer program product including a non-transitory storage medium, the storage medium including program code to be executed by a processing circuitry (903) of a first network node (900), whereby execution of the program code causes the first network node (900) to perform the operations described in any of Examples 19 to 27.

[0339] The following provides an explanation of the various abbreviations / acronyms used in this disclosure.

[0340] Explanation of Abbreviations

[0341] ACK response

[0342] AP Application Protocol

[0343] BH Return Trip

[0344] BSR Buffer Status Report

[0345] BWP bandwidth portion

[0346] C-RNTI (Cell Radio Network Temporary Identifier)

[0347] CA carrier aggregation

[0348] CE control elements

[0349] CP control plane

[0350] CQI Channel Quality Indicator

[0351] DC Dual Connection

[0352] DCI Downlink Control Information

[0353] DL downlink

[0354] DRB Data Radio Bearer

[0355] eNB (EUTRAN) base station

[0356] E-RAB EUTRAN Radio Access Bearer

[0357] FDD (Frequency Division Duplex)

[0358] gNB NR base station

[0359] GTP-U GPRS Tunneling Protocol - User Plane

[0360] IP Internet Protocol

[0361] LTE Long Term Evolution

[0362] MCG Main Cell Group

[0363] MAC Media Access Control

[0364] MeNB main eNB

[0365] MgNB main gNB

[0366] MN master node

[0367] NACK (Negative Response)

[0368] NR New Radio

[0369] PDCP (Packet Data Convergence Protocol)

[0370] Pcell main cell

[0371] PCI Physical Cell Identifier

[0372] PSCell main SCell

[0373] PUSCH Physical Uplink Shared Channel

[0374] RLC Radio Link Control

[0375] RLF radio link failure

[0376] RRC Radio Resource Control

[0377] SCell Auxiliary Community

[0378] SCG Auxiliary Community Group

[0379] SCTP (Stream Control Transfer Protocol)

[0380] SeNB and eNB

[0381] SINR (Signal-to-Interference-plus-Noise Ratio)

[0382] SN auxiliary node

[0383] SR scheduling request

[0384] SRB signaling radio bearer

[0385] SUL supplements uplink

[0386] TDD (Time Division Duplex)

[0387] TEID (Tunnel Endpoint Identifier)

[0388] TNL Transport Network Layer

[0389] UCI uplink control information

[0390] UDP User Datagram Protocol

[0391] UE User Equipment

[0392] UL uplink

[0393] UP User Plane

[0394] URLLC Ultra-Reliable Low-Latency Communication

[0395] Interface between X2 base stations

[0396] The references are as follows.

[0397] ********Full citation of references mentioned in the IvD***

[0398] Additional notes are provided below.

[0399] Generally, unless explicitly stated and / or implied from the context, all terms used herein shall be interpreted according to their common meaning in the relevant art. Unless otherwise expressly stated, all references to “an element, device, component, apparatus, step, etc.” shall be openly interpreted as referring to at least one instance of an element, device, component, apparatus, step, etc. Unless it must be explicitly described that a step is after or before another step and / or implicitly implied that a step must be after or before another step, the steps of any method disclosed herein need not be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. Further objects, features, and advantages of the appended embodiments will become apparent from the following description.

[0400] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. 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 the embodiments set forth herein; rather, these embodiments are provided by way of example only to convey the scope of the subject matter to those skilled in the art.

[0401] Figure 13 A wireless network according to some embodiments is shown.

[0402] While the subjects described herein can be implemented using any suitable components in any suitable type of system, the embodiments disclosed herein pertain to wireless networks (e.g., Figure 13 The example wireless network shown is described below. For simplicity, Figure 13The wireless network depicted only includes network 1306, network nodes 1360 and 1360b, and WD 1310, 1310b, and 1310c (also referred to as mobile terminals). In practice, the wireless network may also include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (e.g., a landline telephone, a service provider, or any other network node or terminal device). Among the components shown, network node 1360 and wireless device (WD) 1310 are depicted with additional details. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate access to and / or use of services provided by or via the wireless network.

[0403] Wireless networks can include any type of communications, telecommunications, data, cellular and / or radio networks or other similar systems, and / or interface with any type of communications, telecommunications, data, cellular and / or radio networks or other similar systems. In some embodiments, a wireless network can be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of a wireless network can implement communication standards 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; Wireless Local Area Network (WLAN) standards (e.g., IEEE 802.11); and / or any other suitable wireless communication standards such as Global Microwave Access Interoperability (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0404] Network 1306 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WAN), local area networks (LAN), wireless local area networks (WLAN), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0405] Network node 1360 and WD 1310 include various components described in more detail below. These components work together to provide network node and / or wireless device functionality, such as providing wireless connectivity in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components that can facilitate or participate in communication of data and / or signals (whether via wired or wireless connections).

[0406] As used herein, a network node refers to a device that is capable of, configured, positioned, and / or operable to communicate directly or indirectly with wireless devices and / or with other network nodes or devices in a wireless network to provide and / or enable radio access to wireless devices and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, NodeBs, evolved NodeBs (eNBs), and NR NodeBs (gNBs)). Base stations can be classified based on the coverage they provide (or, in other words, based on their transmit power levels), and thus they can also be referred to as femtocells, picocells, microcells, or macrocells. A base station can be a relay node or a relay donor node that controls a relay. A network node can also include one or more (or all) portions 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 headend (RRH). These remote radio units may be integrated with an antenna to form an antenna-integrated radio, or they may not be integrated with an antenna to form an antenna-integrated radio. A portion of a distributed radio base station can also be referred to as a node in a distributed antenna system (DAS). Further examples of network nodes include multi-standard radio (MSR) equipment (e.g., MSRBS), network controllers (e.g., Radio Network Controller (RNC) or Base Station Controller (BSC)), base transceiver stations (BTS), transmitting points, transmitting nodes, multi-cell / multicast coordination entities (MCE), core network nodes (e.g., MSC, MME), O&M nodes, OSS nodes, SON nodes, location nodes (e.g., E-SMLC), and / or MDTs. As another example, a network node can be a virtual network node, as described in more detail below. However, more generally, a network node can represent any suitable device (or group of devices) capable of, configured, arranged, and / or operable to enable and / or provide access to a wireless communication network for wireless devices, or to provide some service to wireless devices already connected to the wireless network.

[0407] exist Figure 13 In the network node 1360, processing circuitry 1370, device-readable medium 1380, interface 1390, auxiliary equipment 1384, power supply 1386, power supply circuitry 1387, and antenna 1362 are included. Although Figure 13The network node 1360 shown in the exemplary wireless network may represent a device including a combination of the illustrated hardware components, but other embodiments may include network nodes with different combinations of components. It should be understood that a network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Furthermore, while the components of network node 1360 are depicted as a single box within a larger box, or nested within multiple boxes, in practice, a network node may include multiple different physical components constituting a single illustrated component (e.g., device-readable medium 1380 may include multiple separate hard disk drives and multiple RAM modules).

[0408] Similarly, network node 1360 may consist of multiple physically separate components (e.g., Node B components and RNC components, BTS components and BSC components, etc.), each with its own respective components. In some scenarios where network node 1360 includes multiple separate components (e.g., BTS and BSC components), one or more of these separate components may be shared among multiple network nodes. For example, a single RNC may control multiple NodeBs. In such scenarios, each unique NodeB and RNC pair may be considered a single, separate network node in some cases. In some embodiments, network node 1360 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media 1380 for different RATs), and some components may be reused (e.g., the same antenna 1362 may be shared by the RATs). Network node 1360 may also include multiple sets of various illustrated components for integrating different wireless technologies (e.g., GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) into network node 1360. These wireless technologies can be integrated into the same or different chips or chipsets and other components within network node 1360.

[0409] Processing circuitry 1370 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) provided by a network node as described herein. These operations performed by processing circuitry 1370 may include information acquired by processing circuitry 1370 through processes such as: converting the acquired information into other information, comparing the acquired or converted information with information stored in the network node, and / or performing one or more operations based on the acquired or converted information, and making a determination based on the result of said processing.

[0410] Processor circuitry 1370 may include a combination of one or more of the following: 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 coding logic, operable to provide network node 1360 functionality, either alone or together with other network node 1360 components (e.g., device-readable medium 1380). For example, processing circuitry 1370 may execute instructions stored in device-readable medium 1380 or in memory within processing circuitry 1370. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 1370 may include a system-on-a-chip (SoC).

[0411] In some embodiments, the processing circuitry 1370 may include one or more of a radio frequency (RF) transceiver circuitry 1372 and a baseband processing circuitry 1374. In some embodiments, the RF transceiver circuitry 1372 and the baseband processing circuitry 1374 may be on separate chips (or chipsets), boards, or units (e.g., radio units and digital units). In alternative embodiments, some or all of the RF transceiver circuitry 1372 and the baseband processing circuitry 1374 may be on the same chip or chipset, board, or unit group.

[0412] In some embodiments, some or all of the functions described herein as being provided by a network node, base station, eNB, or other such network device may be performed by processing circuitry 1370, which executes instructions stored on a device-readable medium 1380 or in memory within processing circuitry 1370. In alternative embodiments, some or all of the functions may be provided by processing circuitry 1370, for example, in a hard-wired manner, without executing instructions stored on separate or discrete device-readable media. In any of these embodiments, processing circuitry 1370 may be configured to perform the described functions regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functions are not limited to processing circuitry 1370 or other components of network node 1360, but are enjoyed as a whole by network node 1360 and / or generally by end users and wireless networks.

[0413] Device-readable medium 1380 may include any form of volatile or non-volatile computer-readable storage, including but not limited to permanent storage devices, solid-state storage, remotely mounted storage, 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 drives, optical discs (CDs), or digital video discs (DVDs)) and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data, and / or instructions that can be used by processing circuitry 1370. Device-readable medium 1380 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions that can be executed by processing circuitry 1370 and used by network node 1360. Device-readable medium 1380 may be used to store any calculations performed by processing circuitry 1370 and / or any data received via interface 1390. In some embodiments, the processing circuitry 1370 and the device-readable medium 1380 may be considered as integrated.

[0414] Interface 1390 is used for wired or wireless communication of signaling and / or data between network node 1360, network 1306, and / or WD 1310. As shown, interface 1390 includes a port / terminal 1394 for sending and receiving data to and from network 1306, for example, via a wired connection. Interface 1390 also includes radio front-end circuitry 1392, which may be coupled to antenna 1362, or is part of antenna 1362 in some embodiments. Radio front-end circuitry 1392 includes a filter 1398 and an amplifier 1396. Radio front-end circuitry 1392 may be connected to antenna 1362 and processing circuitry 1370. Radio front-end circuitry 1392 may be configured to modulate the signals communicating between antenna 1362 and processing circuitry 1370. Radio front-end circuitry 1392 may receive digital data that will be transmitted wirelessly to other network nodes or WDs. The radio front-end circuit 1392 can use a combination of filter 1398 and / or amplifier 1396 to convert digital data into radio signals with suitable channel and bandwidth parameters. The radio signals can then be transmitted via antenna 1362. Similarly, when receiving data, antenna 1362 can collect radio signals, which are then converted into digital data by the radio front-end circuit 1392. The digital data can be passed to processing circuitry 1370. In other embodiments, the interface may include different components and / or different combinations of components.

[0415] In some alternative embodiments, network node 1360 may not include a separate radio front-end circuitry 1392. Instead, processing circuitry 1370 may include radio front-end circuitry and may be connected to antenna 1362 without requiring a separate radio front-end circuitry 1392. Similarly, in some embodiments, all or some of RF transceiver circuitry 1372 may be considered part of interface 1390. In other embodiments, interface 1390 may include one or more ports or terminals 1394, radio front-end circuitry 1392, and RF transceiver circuitry 1372 as part of a radio unit (not shown), and interface 1390 may communicate with baseband processing circuitry 1374, which is part of a digital unit (not shown).

[0416] Antenna 1362 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 1362 may be coupled to radio front-end circuitry 1392 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 1362 may include one or more omnidirectional, sector, or planar antennas operable to transmit / receive radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas can be used to transmit / receive radio signals in any direction, sector antennas can be used to transmit / receive radio signals relative to a device within a specific area, and planar antennas can be line-of-sight antennas used to transmit / receive radio signals in a relatively straight line. In some cases, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 1362 may be separate from network node 1360 and may be connected to network node 1360 via an interface or port.

[0417] Antenna 1362, interface 1390, and / or processing circuitry 1370 can be configured to perform any receive operation and / or certain acquire operation described herein as being performed by a network node. Any information, data, and / or signals can be received from a wireless device, another network node, and / or any other network device. Similarly, antenna 1362, interface 1390, and / or processing circuitry 1370 can be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals can be transmitted to a wireless device, another network node, and / or any other network device.

[0418] Power supply circuit 1387 may include or be coupled to power management circuitry and is configured to provide power to the components of network node 1360 for performing the functions described herein. Power supply circuit 1387 may receive power from power source 1386. Power source 1386 and / or power supply circuit 1387 may be configured to provide power to various components of network node 1360 in a manner suitable for the individual components (e.g., at the voltage and current levels required by each respective component). Power source 1386 may be included in or external to power supply circuit 1387 and / or network node 1360. For example, network node 1360 may be connected to an external power source (e.g., a power outlet) via input circuitry or an interface such as a cable, wherein the external power source supplies power to power supply circuit 1387. As another example, power source 1386 may include a power source in the form of a battery or battery pack, which is connected to or integrated into power supply circuit 1387. The battery can provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0419] Alternative embodiments of network node 1360 may include more than Figure 13 Additional components of the components shown may be responsible for providing certain aspects of the functionality of the network node (including any of the functionalities described herein and / or any functionality required to support the subject matter described herein). For example, network node 1360 may include a user interface device to allow information to be input into and output from network node 1360. This can allow users to perform diagnostic, maintenance, repair, and other management functions on network node 1360.

[0420] As used herein, a wireless device (WD) means a device capable of, configured, positioned, and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise stated, the term WD is used interchangeably with User Equipment (UE) herein. Wireless communication may include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information through the air. In some embodiments, a WD may be configured to transmit and / or receive information without direct human interaction. For example, a WD may be designed to send information to a network in a predetermined schedule when triggered by an internal or external event or in response to a request from the network. Examples of WDs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), smart devices, wireless client devices (CPEs), in-vehicle wireless terminal devices, etc. A UE can, for example, support device-to-device (D2D) communication, vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, and vehicle-to-anything (V2X) communication by implementing 3GPP standards for sidelink communication, and in this case, it can be referred to as a D2D communication device. As yet another specific example, in the Internet of Things (IoT) scenario, a UE can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another UE and / or network node. In this case, the WD can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As a specific example, a WD can be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (e.g., power meters), industrial machines, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, a UE can represent a vehicle or other device capable of monitoring and / or reporting its operational status or other functions associated with its operation. As mentioned above, WD can represent a wireless connection endpoint, in which case the device can be referred to as a wireless terminal. Furthermore, as mentioned above, UE can be mobile, in which case it can also be referred to as a mobile device or mobile terminal.

[0421] As shown in the figure, wireless device 1310 includes an antenna 1311, an interface 1314, processing circuitry 1320, a device-readable medium 1330, a user interface device 1332, auxiliary devices 1334, a power supply 1336, and a power circuit 1337. WD 1310 may include one or more of the components shown for various wireless technologies supported by WD 1310 (e.g., GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, to name just a few). These wireless technologies may be integrated into a chip or chipset that is the same as or different from other components within WD 1310.

[0422] Antenna 1311 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and connected to interface 1314. In some alternative embodiments, antenna 1311 may be separate from WD 1310 and may be connected to WD 1310 via an interface or port. Antenna 1311, interface 1314, and / or processing circuitry 1320 may be configured to perform any receive or transmit operations described herein as performed by a WD. Any information, data, and / or signals may be received from a network node and / or another WD. In some embodiments, radio front-end circuitry and / or antenna 1311 may be considered as an interface.

[0423] As shown in the figure, interface 1314 includes radio front-end circuitry 1312 and antenna 1311. Radio front-end circuitry 1312 includes one or more filters 1318 and amplifiers 1316. Radio front-end circuitry 1312 is connected to antenna 1311 and processing circuitry 1320 and is configured to modulate signals communicating between antenna 1311 and processing circuitry 1320. Radio front-end circuitry 1312 may be coupled to antenna 1311 or a portion thereof. In some embodiments, WD 1310 may not include separate radio front-end circuitry 1312; instead, processing circuitry 1320 may include radio front-end circuitry and may be connected to antenna 1311. Similarly, in some embodiments, some or all of RF transceiver circuitry 1322 may be considered part of interface 1314. Radio front-end circuitry 1312 can receive digital data that will be transmitted wirelessly to other network nodes or WD. The radio front-end circuit 1312 can use a combination of filter 1318 and / or amplifier 1316 to convert digital data into radio signals with suitable channel and bandwidth parameters. The radio signals can then be transmitted via antenna 1311. Similarly, when receiving data, antenna 1311 can collect radio signals, which are then converted into digital data by the radio front-end circuit 1312. The digital data can be passed to processing circuitry 1320. In other embodiments, the interface may include different components and / or different combinations of components.

[0424] Processor circuitry 1320 may include a combination of one or more of the following: 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 coding logic, operable to provide WD 1310 functionality, either alone or together with other WD 1310 components (e.g., device-readable medium 1330). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 1320 may execute instructions stored in device-readable medium 1330 or in memory within processing circuitry 1320 to provide the functionality disclosed herein.

[0425] As shown in the figure, the processing circuit 1320 includes one or more of an RF transceiver circuit 1322, a baseband processing circuit 1324, and an application processing circuit 1326. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 1320 of the WD 1310 may include a System-on-a-Chip (SOC). In some embodiments, the RF transceiver circuit 1322, the baseband processing circuit 1324, and the application processing circuit 1326 may be on a separate chip or chipset. In an alternative embodiment, some or all of the baseband processing circuit 1324 and the application processing circuit 1326 may be combined into a single chip or chipset, and the RF transceiver circuit 1322 may be on a separate chip or chipset. In another alternative embodiment, some or all of the RF transceiver circuit 1322 and the baseband processing circuit 1324 may be on the same chip or chipset, and the application processing circuit 1326 may be on a separate chip or chipset. In other alternative embodiments, some or all of the RF transceiver circuitry 1322, baseband processing circuitry 1324, and application processing circuitry 1326 may be combined in the same chip or chipset. In some embodiments, the RF transceiver circuitry 1322 may be part of interface 1314. The RF transceiver circuitry 1322 may regulate the RF signal used for processing circuitry 1320.

[0426] In some embodiments, some or all of the functions described herein as being performed by WD may be provided by processing circuitry 1320 that executes instructions stored on device-readable medium 1330, which may be a computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by processing circuitry 1320, for example, in a hard-wired manner, without executing instructions stored on separate or discrete device-readable storage media. In any of those particular embodiments, processing circuitry 1320 may be configured to perform the described functions regardless of whether instructions stored on device-readable storage media are executed. The benefits provided by such functions are not limited to processing circuitry 1320 or other components of WD 1310, but are enjoyed as a whole by WD 1310 and / or generally by end users and wireless networks.

[0427] Processing circuitry 1320 can be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by WD. These operations performed by processing circuitry 1320 may include information acquired by processing circuitry 1320 through processes such as: converting the acquired information into other information, comparing the acquired or converted information with information stored by WD 1310, and / or performing one or more operations based on the acquired or converted information, and making a determination based on the result of said processing.

[0428] Device-readable medium 1330 is operable to store computer programs, software, applications including one or more of logic, rules, code, tables, etc., and / or other instructions executable by processing circuitry 1320. Device-readable medium 1330 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., CD or 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 usable by processing circuitry 1320. In some embodiments, processing circuitry 1320 and device-readable medium 1330 may be considered integrated.

[0429] User interface device 1332 can provide components that allow a human user to interact with WD 1310. This interaction can take many forms, such as visual, auditory, tactile, etc. User interface device 1332 is operable to produce output to the user and allow the user to provide input to WD 1310. The type of interaction can vary depending on the type of user interface device 1332 installed in WD 1310. For example, if WD 1310 is a smartphone, interaction can be made via a touchscreen; if WD 1310 is a smart meter, interaction can be made via a screen providing a purpose (e.g., the number of gallons used) or a speaker providing an audible alarm (e.g., if smoke is detected). User interface device 1332 can include input interfaces, devices, and circuitry, as well as output interfaces, devices, and circuitry. User interface device 1332 is configured to allow information to be input into WD 1310 and is connected to processing circuitry 1320 to allow processing circuitry 1320 to process the input information. User interface device 1332 can include, for example, a microphone, proximity or other sensors, buttons / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface device 1332 is also configured to allow information output from WD 1310 and to allow processing circuitry 1320 to output information from WD 1310. User interface device 1332 may include, for example, a speaker, display, vibration circuitry, a USB port, a headphone jack, or other output circuitry. By using one or more input and output interfaces, devices, and circuitry of user interface device 1332, WD 1310 can communicate with end users and / or wireless networks, allowing them to benefit from the functionality described herein.

[0430] The auxiliary device 1334 is operable to provide more specific functions that may not typically be performed by the WD. This may include dedicated sensors for measuring for various purposes, interfaces for additional types of communication such as wired communication, etc. The contents and types of components of the auxiliary device 1334 may vary depending on the embodiment and / or scenario.

[0431] In some embodiments, power supply 1336 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., a power outlet), a photovoltaic device, or a battery cell. WD 1310 may also include power circuitry 1337 for supplying power from power supply 1336 to various parts of WD 1310 that require power from power supply 1336 to perform any functions described or indicated herein. In some embodiments, power circuitry 1337 may include power management circuitry. Power circuitry 1337 may additionally or alternatively be operable to receive power from an external power source; in this case, WD 1310 may be connected to an external power source (e.g., a power outlet) via input circuitry or an interface such as a power cable. In some embodiments, power circuitry 1337 may also be operable to supply power from an external power source to power supply 1336. This may be used, for example, for charging power supply 1336. Power circuitry 1337 may perform any formatting, conversion, or other modifications on the power from power supply 1336 to suit the power supply for the various components of WD 1310 that are powered thereto.

[0432] Figure 14 A user device according to some embodiments is shown.

[0433] Figure 14 An embodiment of a UE according to the various aspects described herein is illustrated. As used herein, "User Equipment" or "UE" may not necessarily have the meaning of a "user" in the sense of a human user who owns and / or operates the associated equipment. Alternatively, a UE may refer to a device intended to be sold to or operated by a human user but may not or initially be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may refer to a device not intended to be sold to or operated by an end user but may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 1400 can be any UE identified by the 3rd Generation Partnership Project (3GPP), including NB-IoT UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs. Figure 14 As shown, UE 1400 is an example of a WD configured for communication according to one or more communication standards (e.g., 3GPP's GSM, UMTS, LTE, and / or 5G standards) published by the 3rd Generation Partnership Project (3GPP). As previously stated, the terms WD and UE are used interchangeably. Therefore, although... Figure 14 This is for UE, but the components discussed in this article also apply to WD, and vice versa.

[0434] exist Figure 14In this embodiment, UE 1400 includes processing circuitry 1401 operable to be coupled to an input / output interface 1405, a radio frequency (RF) interface 1409, a network connectivity interface 1411, a memory 1415 including random access memory (RAM) 1417, read-only memory (ROM) 1419, and a storage medium 1421, a communication subsystem 1431, a power supply 1413, and / or any other component, or any combination thereof. Storage medium 1421 includes an operating system 1423, application programs 1425, and data 1427. In other embodiments, storage medium 1421 may include other similar types of information. Some UEs may use... Figure 14 All components are shown, or only a subset of components are used. The level of integration between components can vary from one UE to another. Furthermore, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0435] exist Figure 14 In this embodiment, processing circuitry 1401 can be configured to process computer instructions and data. Processor 1401 can be configured to execute any sequential state machine containing 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 and suitable firmware; one or more stored programs, a general-purpose processor (e.g., a microprocessor or digital signal processor (DSP)) and suitable software; or any combination thereof. For example, processing circuitry 1401 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0436] In the depicted embodiments, the input / output interface 1405 can be configured to provide a communication interface to an input device, an output device, or both input and output devices. The UE 1400 can be configured to use an output device via the input / output interface 1405. The output device can use an interface port of the same type as the input device. For example, a USB port can be used to provide input to and output from the UE 1400. The output device can be a speaker, sound card, video card, display, monitor, printer, actuator, transmitter, smart card, another output device, or any combination thereof. The UE 1400 can be configured to use an input device via the input / output interface 1405 to allow a user to capture information into the UE 1400. The input device can include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, digital camcorder, webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional keyboard, a touchpad, a scroll wheel, a smart card, etc. A presence-sensitive display can include a capacitive or resistive touch sensor to sense input from the user. Sensors can be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, optical sensors, proximity sensors, another type of sensor, or any combination thereof. For example, input devices can be accelerometers, magnetometers, digital cameras, microphones, and optical sensors.

[0437] exist Figure 14 In this configuration, RF interface 1409 can be configured to provide a communication interface to RF components such as transmitters, receivers, and antennas. Network interface 1411 can be configured to provide a communication interface to network 1443a. Network 1443a may include wired and / or wireless networks, such as local area networks (LANs), wide area networks (WANs), computer networks, wireless networks, telecommunications networks, another similar network, or any combination thereof. For example, network 1443a may include a Wi-Fi network. Network interface 1411 can be configured to include receiver and transmitter interfaces for communicating with one or more other devices over the communication network according to one or more communication protocols (e.g., Ethernet, TCP / IP, SONET, ATM, etc.). Network interface 1411 can implement receiver and transmitter functions suitable for the communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components or software, or alternatively, may be implemented separately.

[0438] RAM 1417 can be configured to interface with processing circuitry 1401 via bus 1402 to provide storage or cache of data or computer instructions during the execution of software programs such as operating systems, applications, and device drivers. ROM 1419 can be configured to provide computer instructions or data to processing circuitry 1401. For example, ROM 1419 can be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I / O), startup, or reception of keystrokes from a keyboard, stored in non-volatile memory. Storage medium 1421 can 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), disk, optical disk, floppy disk, hard disk, removable magnetic tape, or flash drive. In this example, storage medium 1421 can be configured to include operating system 1423, application 1425 such as a web browser application, widget or utility engine or another application, and data file 1427. Storage medium 1421 can store any one or a combination of various operating systems for use by UE 1400.

[0439] Storage medium 1421 can be configured to include: multiple physical drive units (e.g., redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile optical disc (HD-DVD) drive, internal hard disk drive, Blu-ray disc drive, holographic digital data storage (HDDS) disc drive), external mini dual in-line memory modules (DIMMs), synchronous dynamic random access memory (SDRAM), external micro DIMM SDRAM, smart card memory (e.g., user identity module or removable user identity (SIM / RUIM) module), other memory, or any combination thereof. Storage medium 1421 can allow UE 1400 to access computer-executable instructions, applications, etc., stored on transient or non-transient storage media to unload or upload data. Articles such as those utilizing communication systems can be tangibly embodied in storage medium 1421, which may include device-readable media.

[0440] exist Figure 14In this configuration, processing circuitry 1401 can be configured to communicate with network 1443b using communication subsystem 1431. Networks 1443a and 1443b can be one or more of the same networks or one or more different networks. Communication subsystem 1431 can be configured to include one or more transceivers for communicating with network 1443b. For example, communication subsystem 1431 can be configured to include one or more remote transceivers for communicating with another device (e.g., another WD, UE) or a base station of a radio access network (RAN) capable of wireless communication according to one or more communication protocols (e.g., IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver can include transmitter 1433 and / or receiver 1435 to implement transmitter or receiver functions (e.g., frequency allocation, etc.) suitable for the RAN link, respectively. Furthermore, transmitter 1433 and receiver 1435 of each transceiver can share circuit components, software, or firmware, or they can be implemented separately.

[0441] In the illustrated embodiment, the communication functions of the communication subsystem 1431 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication (such as the use of a Global Positioning System (GPS) for determining location), another type of communication function, or any combination thereof. For example, the communication subsystem 1431 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 1443b may include wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 1443b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 1413 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 1400.

[0442] The features, benefits, and / or functions described herein may be implemented in one of the components of UE 1400 or partitioned among multiple components of UE 1400. 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 1431 may be configured to include any of the components described herein. Additionally, the processing circuitry 1401 may be configured to communicate with any such component via bus 1402. In another example, any such component may be represented by program instructions stored in memory, which, when executed by the processing circuitry 1401, perform the corresponding functions described herein. In another example, the functionality of any such component may be partitioned between the processing circuitry 1401 and the communication subsystem 1431. In yet another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0443] Figure 15 A virtualized environment according to some embodiments is shown.

[0444] Figure 15 This is a schematic block diagram illustrating a virtualized environment 1500, in which functionality implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device that may include a virtualized hardware platform, storage devices, and network resources. As used herein, virtualization can be applied to nodes (e.g., virtualized base stations or virtualized radio access nodes) or devices (e.g., UEs, wireless devices, or any other type of communication equipment) or components thereof, and relates to an implementation in which at least some of the functionality is implemented as one or more virtual components (e.g., through one or more applications, components, functions, virtual machines, or containers executing on one or more physical processing nodes in one or more networks).

[0445] 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 1500 hosted on one or more hardware nodes 1530. Furthermore, in embodiments where the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), the network node may then be fully virtualized.

[0446] These functionalities can be implemented by one or more applications 1520 (which may alternatively be referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.), operable to implement some of the features, functions, and / or benefits of some embodiments disclosed herein. Application 1520 runs in a virtualization environment 1500, which provides hardware 1530 including processing circuitry 1560 and memory 1590. Memory 1590 contains instructions 1595 executable by processing circuitry 1560, thereby enabling application 1520 to operate to provide one or more of the features, benefits, and / or functions disclosed herein.

[0447] The virtualization environment 1500 includes general-purpose or special-purpose network hardware devices 1530, which include one or more processors or processing circuitry 1560, which may be commercial off-the-shelf (COTS) processors, application-specific integrated circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special-purpose processors. Each hardware device may include memory 1590-1, which may be non-permanent memory for temporarily storing instructions 1595 or software executed by the processing circuitry 1560. Each hardware device may include one or more network interface controllers (NICs) 1570 (also referred to as network interface cards), which include physical network interfaces 1580. Each hardware device may also include non-transitory, permanent machine-readable storage media 1590-2 in which the software 1595 and / or instructions executable by the processing circuitry 1560 are stored. The software 1595 may include any type of software, including software for instantiating one or more virtualization layers 1550 (also referred to as hypervisors), software for executing virtual machines 1540, and software that allows them to perform the functions, features, and / or benefits described in relation to some embodiments described herein.

[0448] Virtual machine 1540 includes virtual processing, virtual memory, virtual networking or interface, and virtual storage, and can be run by a corresponding virtualization layer 1550 or hypervisor. Different embodiments of instances of virtual device 1520 can be implemented on one or more of virtual machines 1540, and this implementation can be done in different ways.

[0449] During operation, the processing circuitry 1560 executes software 1595 to instantiate the hypervisor or virtualization layer 1550, which may sometimes be referred to as a virtual machine monitor (VMM). The virtualization layer 1550 can present a virtual operating platform that appears as networked hardware of the virtual machine 1540.

[0450] like Figure 15As shown, hardware 1530 can be a standalone network node with general or specific components. Hardware 1530 may include antenna 15225 and may implement some functions through virtualization. Alternatively, hardware 1530 may be part of a larger hardware cluster (e.g., in a data center or customer premises equipment (CPE)) where many hardware nodes work together and are managed by management and coordination (MANO) 15100, which in particular oversees the lifecycle management of application 1520.

[0451] In some contexts, hardware virtualization is referred to as Network Functions Virtualization (NFV). NFV can be used to unify numerous network device types onto industry-standard high-capacity server hardware, physical switches, and physical storage that can reside in data centers and customer premises equipment (CPE).

[0452] In the context of NFV, virtual machine 1540 can be a software implementation of a physical machine, and its running programs are executed as if they were running on a physical, non-virtualized machine. Each virtual machine 1540, along with the portion of hardware 1530 that executes that virtual machine (whether it is hardware dedicated to that virtual machine and / or hardware shared by that virtual machine and other virtual machines in virtual machine 1540), forms a separate virtual network element (VNE).

[0453] Still within the context of NFV, Virtual Network Functions (VNFs) are responsible for handling one or more virtual machines 1540 running on top of the hardware network infrastructure 1530 and corresponding to Figure 15 The application of 1520 includes specific network functions.

[0454] In some embodiments, each of the one or more radio units 15200, including one or more transmitters 15220 and one or more receivers 15210, may be coupled to one or more antennas 15225. The radio unit 15200 may communicate directly with the hardware node 1530 via one or more suitable network interfaces and may be used in conjunction with virtual components to provide radio capabilities to the virtual node, such as a radio access node or base station.

[0455] In some embodiments, the control system 15230 may be used to implement some signaling, and the control system 15230 may alternatively be used for communication between the hardware node 1530 and the radio unit 15200.

[0456] Figure 16 A telecommunications network connected to a host computer via an intermediate network is shown according to some embodiments.

[0457] refer to Figure 16According to an embodiment, the communication system includes a telecommunications network 1610 (e.g., a 3GPP-type cellular network), which includes an access network 1611 (such as a radio access network) and a core network 1614. The access network 1611 includes multiple base stations 1612a, 1612b, and 1612c (e.g., NB, eNB, gNB, or other types of wireless access points), each base station defining a corresponding coverage area 1613a, 1613b, or 1613c. Each base station 1612a, 1612b, or 1612c can be connected to the core network 1614 via a wired or wireless connection 1615. A first UE 1691 located in coverage area 1613c is configured to wirelessly connect to or be paged by the corresponding base station 1612c. A second UE 1692 located in coverage area 1613a can wirelessly connect to the corresponding base station 1612a. Although multiple UEs 1691 and 1692 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is located in the coverage area or a single UE is connected to the corresponding base station 1612.

[0458] Telecommunications network 1610 is itself connected to host computer 1630, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server cluster. Host computer 1630 may be owned by or under the control of a service provider, or may be operated by or on behalf of a service provider. Connections 1621, 1622 between telecommunications network 1610 and host computer 1630 may extend directly from core network 1614 to host computer 1630, or may pass through optional intermediate network 1620. Intermediate network 1620 may be one or more of public, private, or hosted networks; intermediate network 1620 (if any) may be a backbone network or the Internet; specifically, intermediate network 1620 may include two or more subnetworks (not shown).

[0459] Figure 16The communication system as a whole implements the connection between connected UEs 1691 and 1692 and host computer 1630. This connection can be described as an over-the-top (OTT) connection 1650. Host computer 1630 and connected UEs 1691 and 1692 are configured to transmit data and / or signaling via OTT connection 1650 using access network 1611, core network 1614, any intermediate network 1620, and possibly other intermediate infrastructure (not shown). The participating communication devices through which OTT connection 1650 passes are unaware of the routes of uplink and downlink communications; in this sense, OTT connection 1650 can be transparent. For example, base station 1612 may not be informed or need not be informed of the past routes of incoming downlink communications containing data originating from host computer 1630 and to be forwarded (e.g., handed over) to connected UE 1691. Similarly, base station 1612 does not need to know the future routes of uplink communications originating from UE 1691 and outputting toward host computer 1630.

[0460] Figure 17 A host computer is shown that communicates with a user equipment via a base station through a partially wireless connection, according to some embodiments.

[0461] Now refer to Figure 17 The following describes an example implementation of the UE, base station, and host computer according to the embodiments discussed in the preceding paragraphs. In the communication system 1700, the host computer 1710 includes hardware 1715, which includes a communication interface 1716 configured to establish and maintain a wired or wireless connection with interfaces of different communication devices of the communication system 1700. The host computer 1710 also includes processing circuitry 1718, which may have storage and / or processing capabilities. In particular, the processing circuitry 1718 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations of such devices (not shown) adapted to execute instructions. The host computer 1710 also includes software 1711, which is stored in or accessible by the host computer 1710 and can be executed by the processing circuitry 1718. The software 1711 includes a host application 1712. Host application 1712 can be operated to provide services to remote users, such as UE 1730 connected via OTT connection 1750, which terminates between UE 1730 and host computer 1710. When providing services to remote users, host application 1712 can provide user data sent using OTT connection 1750.

[0462] The communication system 1700 also includes a base station 1720 installed in the telecommunications system. The base station 1720 includes hardware 1725 enabling it to communicate with the host computer 1710 and the UE 1730. Hardware 1725 may include: a communication interface 1726 for establishing and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 1700; and a radio interface 1727 for establishing and maintaining connections with the coverage area served by the base station 1720. Figure 17 At least one wireless connection 1770 of UE 1730 (not shown in the image). Communication interface 1726 can be configured to facilitate connection 1760 to host computer 1710. Connection 1760 can be a direct connection, or alternatively, the connection can be through the core network of a telecommunications network (…). Figure 17 (Not shown in the diagram) and / or via one or more intermediate networks outside the telecommunications network. In the illustrated embodiment, the hardware 1725 of base station 1720 also includes processing circuitry 1728, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. Base station 1720 also has software 1721 stored internally or accessible via an external connection.

[0463] The communication system 1700 also includes the previously mentioned UE 1730. The hardware 1735 of UE 1730 may include a radio interface 1737 configured to establish and maintain a wireless connection 1770 with a base station serving the coverage area currently occupied by UE 1730. The hardware 1735 of UE 1730 also includes processing circuitry 1738, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations of such devices (not shown) suitable for executing instructions. UE 1730 also includes software 1731, which is stored in or accessible from UE 1730 and can be executed by the processing circuitry 1738. Software 1731 includes a client application 1732. Client application 1732 can be operated to provide services to human or non-human users via UE 1730, supported by host computer 1710. In host computer 1710, the executing host application 1712 can communicate with the executing client application 1732 via OTT connection 1750, which terminates between UE 1730 and host computer 1710. When providing services to a user, client application 1732 can receive request data from host application 1712 and provide user data in response to the request data. OTT connection 1750 can transmit both request data and user data. Client application 1732 can interact with the user to generate the user data it provides.

[0464] It should be noted that Figure 17The host computer 1710, base station 1720, and UE 1730 shown can be respectively connected to... Figure 16 The host computer 1630, one of the base stations 1612a, 1612b, and 1612c, and one of the UEs 1691 and 1692 are similar to or equivalent to each other. That is, the internal workings of these entities can be as follows: Figure 17 As shown, and independently, the surrounding network topology can be Figure 16 The network topology.

[0465] exist Figure 17 The OTT connection 1750 is abstractly depicted to illustrate communication between host computer 1710 and UE 1730 via base station 1720, but no intermediate devices or the exact routing messages via these devices are explicitly mentioned. The network infrastructure can determine the routing, which can be configured to be hidden from UE 1730 or the service provider operating host computer 1710, or both. When OTT connection 1750 is active, the network infrastructure can also make dynamic decisions to change the routing (e.g., based on load balancing considerations or network reconfiguration).

[0466] The radio connection 1770 between UE 1730 and base station 1720 is consistent with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments can improve the performance of OTT services provided to UE 1730 using OTT connection 1750, in which radio connection 1770 forms the final part. More specifically, the teachings of these embodiments can improve random access speed and / or reduce random access failure rate, and thus provide benefits such as faster and / or more reliable random access.

[0467] Measurement procedures may be provided for monitoring data rates, latency, and other factors that are the subject of improvement in one or more embodiments. Optional network functionality may also be present for reconfiguring the OTT connection 1750 between the host computer 1710 and the UE 1730 in response to changes in measurement results. The measurement procedures and / or network functionality for reconfiguring the OTT connection 1750 may be implemented in the software 1711 and hardware 1715 of the host computer 1710, or in the software 1731 and hardware 1735 of the UE 1730, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices through which the OTT connection 1750 traverses; the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities illustrated above, or by providing values ​​of other physical quantities from which the software 1711, 1731 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 1750 may include message formatting, retransmission settings, preferred routing, etc.; the reconfiguration does not need to affect the base station 1720 and may be unknown or imperceptible to the base station 1720. Such processes and functions may be known and practiced in the art. In some embodiments, measurements may involve proprietary UE signaling, which facilitates the host computer 1710 in measuring throughput, propagation time, latency, etc. Measurements may be achieved by software 1711 and 1731 using the OTT connection 1750 to send messages (particularly empty messages or "virtual" messages) while simultaneously monitoring propagation time, errors, etc.

[0468] Figure 18 Methods implemented in a communication system including a host computer, a base station, and a user equipment, according to some embodiments, are illustrated.

[0469] Figure 18 This is a flowchart 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 referenced... Figure 16 and Figure 17 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include... Figure 18 Reference numerals are used in the accompanying drawings. In step 1810, the host computer provides user data. In sub-step 1811 of step 1810 (which may be optional), the host computer provides user data by executing a host application. In step 1820, the host computer initiates a transmission to the UE, which carries user data. In step 1830 (which may be optional), in accordance with the teachings throughout the embodiments described in this disclosure, the base station sends the user data carried in the host computer-initiated transmission to the UE. In step 1840 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0470] Figure 19 Methods implemented in a communication system including a host computer, a base station, and a user equipment, according to some embodiments, are illustrated.

[0471] Figure 19 This is a flowchart 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 referenced... Figure 16 and Figure 17 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include... Figure 19 Reference numerals are used in the accompanying drawings. In step 1910 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 1920, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, the transmission can be carried out via a base station. In step 1930 (which may be optional), the UE receives the user data carried in the transmission.

[0472] Figure 20 Methods implemented in a communication system including a host computer, a base station, and a user equipment, according to some embodiments, are illustrated.

[0473] Figure 20 This is a flowchart 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 referenced... Figure 16 and Figure 17 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include... Figure 20 Reference numerals are used in the accompanying drawings. In step 2010 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2020, the UE provides user data. In sub-step 2021 of step 2020 (which may be optional), the UE provides user data by executing a client application. In sub-step 2011 of step 2010 (which may be optional), the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner in which user data is provided, in sub-step 2030 (which may be optional), the UE initiates the transmission of user data to the host computer. In step 2040 of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the host computer receives user data sent from the UE.

[0474] Figure 21Methods implemented in a communication system including a host computer, a base station, and a user equipment, according to some embodiments, are illustrated.

[0475] Figure 21 This is a flowchart 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 referenced... Figure 16 and Figure 17 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include... Figure 21 Reference numerals are used in the accompanying drawings. In step 2110 (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 2120 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 2130 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0476] Any suitable steps, methods, features, functions, or benefits disclosed herein can be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented by processing circuitry, which may include one or more microprocessors or microcontrollers and other digital hardware (including digital signal processors (DSPs), application-specific digital logic, etc.). The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more techniques described herein. In some implementations, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions according to one or an embodiment of this disclosure.

[0477] The term "unit" may have a conventional meaning in the field of electronic, electrical and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing various tasks, processes, calculations, outputs and / or display functions, such as those described herein.

[0478] abbreviation

[0479] At least some of the following abbreviations may be used in this disclosure. In the event of inconsistencies between abbreviations, the usage above shall prevail. If listed multiple times below, the first listing shall take precedence over any subsequent listing.

[0480] 1x RTT CDMA2000 1x Radio Transmission Technology

[0481] 3GPP Third Generation Partnership Project

[0482] 5G (Fifth Generation)

[0483] ABS almost blank subframe

[0484] ARQ (Automatic Repeat Request)

[0485] AWGN Additive White Gaussian Noise

[0486] BCCH Broadcast Control Channel

[0487] BCH Broadcast Channel

[0488] CA carrier aggregation

[0489] CC carrier component

[0490] CCCH SDU Common Control Channel SDU

[0491] CDMA Code Division Multiple Access

[0492] CGI Cell Global Identifier

[0493] CIR channel impulse response

[0494] CP cyclic prefix

[0495] CPICH Common Pilot Channel

[0496] CPICH Ec / No CPICH per chip received energy divided by the power density within the frequency band

[0497] CQI Channel Quality Information

[0498] C-RNTI Community RNTI

[0499] CSI Channel State Information

[0500] DCCH Dedicated Control Channel

[0501] DL downlink

[0502] DM demodulation

[0503] DMRS demodulation reference signal

[0504] DRX discontinuous reception

[0505] DTX discontinuous transmission

[0506] DTCH Dedicated Service Channel

[0507] DUT (Device Under Test)

[0508] E-CID Enhanced Cell ID (Location Method)

[0509] E-SMLC Evolution Service Mobile Location Center

[0510] ECGI evolved from CGI

[0511] eNB E-UTRAN Node B

[0512] EPDCCH Enhanced Physical Downlink Control Channel

[0513] E-SMLC Evolution Service Mobile Location Center

[0514] E-UTRA evolved from UTRA

[0515] E-UTRAN evolved from UTRAN

[0516] FDD (Frequency Division Duplex)

[0517] FFS requires further research.

[0518] GERN GSM EDGE radio access network

[0519] Base stations in gNB NR

[0520] GNSS Global Navigation Satellite System

[0521] GSM Global Mobile Communication System

[0522] HARQ Hybrid Automatic Repeat Request

[0523] HO switch

[0524] HSPA High-Speed ​​Packet Access

[0525] HRPD High-Speed ​​Packet Data

[0526] LOS (Location of View)

[0527] LPP LTE positioning protocol

[0528] LTE Long Term Evolution

[0529] MAC Media Access Control

[0530] MBMS Multimedia Broadcast / Multicast Service

[0531] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0532] MBSFNABS MBSFN almost blank subframes

[0533] Minimum Drive Testing (MDT)

[0534] MIB (Master Information Block)

[0535] MME (Mobility Management Entity)

[0536] MSC Mobile Switching Center

[0537] PDCCH Narrowband Physical Downlink Control Channel

[0538] NR New Radio

[0539] OCNGOFDMA Channel Noise Generator

[0540] OFDM (Orthogonal Frequency Division Multiplexing)

[0541] OFDMA (Orthogonal Frequency Division Multiple Access)

[0542] OSS Operation Support System

[0543] OTDOA Observation Time Difference

[0544] O&M Operations and Maintenance

[0545] PBCH (Physical Broadcast Channel)

[0546] P-CCPCH Main Common Control Physical Channel

[0547] Pcell main cell

[0548] PCFICH Physical Control Format Indicator Channel

[0549] PDCCH (Physical Downlink Control Channel)

[0550] PDP distribution delay distribution

[0551] PDSCH (Physical Downlink Shared Channel)

[0552] PGW Packet Gateway

[0553] PHICH Physical Hybrid ARQ Indicator Channel

[0554] PLMN Public Land Mobile Network

[0555] PMI Precoding Matrix Indicator

[0556] PRACH (Physical Random Access Channel)

[0557] PRS Positioning Reference Signal

[0558] PSS Master Synchronization Signal

[0559] PUCCH (Physical Uplink Control Channel)

[0560] PUSCH Physical Uplink Shared Channel

[0561] PACH Random Access Channel

[0562] QAM Quadrature Amplitude Modulation

[0563] RAN (Radio Access Network)

[0564] RAT Radio Access Technology

[0565] RLM Radio Link Management

[0566] RNC Radio Network Controller

[0567] RNTI (Radio Network Temporary Identifier)

[0568] RRC Radio Resource Control

[0569] RRM Radio Resource Management

[0570] RS reference signal

[0571] RSCP Received Signal Code Power

[0572] RSRP reference symbol received power or

[0573] Reference signal received power

[0574] RSRQ reference signal reception quality or

[0575] Reference symbol reception quality

[0576] RSSI Received Signal Strength Indicator

[0577] RSTD (Reference Signal Time Difference)

[0578] SCH Synchronization Channel

[0579] Scell ​​auxiliary cell

[0580] SDU Service Data Unit

[0581] SFN system frame number

[0582] SGW Service Gateway

[0583] SI System Information

[0584] SIB System Information Block

[0585] SNR (Signal-to-Noise Ratio)

[0586] SON self-optimizing network

[0587] SS synchronization signal

[0588] SSS auxiliary synchronization signal

[0589] TDD (Time Division Duplex)

[0590] TDOA arrival time difference

[0591] TOA Arrival Time

[0592] TSS Level 3 Synchronization Signal

[0593] TTI Transmission Time Interval

[0594] UE User Equipment

[0595] UL uplink

[0596] UMTS (Universal Mobile Telecommunications System)

[0597] USIM Universal Subscriber Identification Module

[0598] UTDOA Uplink Time Difference

[0599] UTRA Universal Terrestrial Radio Access

[0600] UTRAN (Universal Terrestrial Radio Access Network)

[0601] WCDMA Wide CDMA

[0602] WLAN wide area network

[0603] Further definitions and examples are discussed below.

[0604] In the above description of various embodiments of the inventive concept, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the inventive concept. Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which the inventive concept pertains. It should also be understood that terms such as those defined in general dictionaries should be interpreted as having a meaning consistent with their meaning in the context of this specification and related art, and not as having an ideal or overly literal meaning, unless so expressly defined herein.

[0605] When an element is described as being “connected,” “coupled,” “responding,” or a variation thereof relative to another element, it may be directly connected, coupled to, or respond to the other element, or there may be intermediate elements. Conversely, when an element is described as being “directly connected,” “directly coupled,” “directly responding,” or a variation thereof relative to another element, there are no intermediate elements. Throughout the text, similar reference numerals are used to denote similar elements. Furthermore, the terms “coupled,” “connected,” “responding,” or variations thereof as used herein may include wireless coupling, connection, or response. As used herein, the singular forms “a,” “an,” and “described” are intended to also include the plural forms unless the context explicitly indicates otherwise. For the sake of brevity and / or clarity, well-known functions or structures may not be described in detail. The term “and / or” (abbreviated as “ / ”) includes any and all combinations of one or more of the associated listed items.

[0606] It will be understood that although the terms first, second, third, etc., may be used herein to describe various elements / operations, these elements / operations should not be limited by these terms. These terms are used only to distinguish one element / operation from another. Thus, a first element / operation in some embodiments may be referred to as a second element / operation in other embodiments without departing from the teachings of the inventive concept. Throughout the specification, the same reference numerals or reference symbols denote the same or similar elements.

[0607] As used herein, the terms “comprise,” “comprising,” “comprises,” “include,” “including,” “have,” “has,” or variations thereof are open-ended and include one or more of the stated features, integers, elements, steps, components, or functions, but do not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions, or combinations thereof. Furthermore, as used herein, the common abbreviation “eg” (for example) derives from the Latin phrase “exempligratia,” which can be used to introduce or specify a general example of a previously mentioned item, without being intended as a limitation on that item. The common abbreviation “ie” (i.e.) derives from the Latin phrase “idest,” and can be used to specify a specific item in a broader sense of reference.

[0608] This document describes exemplary embodiments with reference to block diagrams and / or flowcharts illustrating computer-implemented methods, apparatus (systems and / or devices), and / or computer program products. It should be understood that the blocks in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented by computer program instructions executed by one or more computer circuits. These computer program instructions can be provided to processor circuitry of general-purpose computer circuitry, special-purpose computer circuitry, and / or other programmable data processing circuitry to produce a machine, such that instructions executed by the processor of a computer and / or other programmable data processing apparatus translate and control transistors, values ​​stored in memory locations, and other hardware components within such circuitry to implement the functions / actions specified in the block diagrams and / or flowcharts, thereby creating means (functional bodies) and / or structures for implementing the functions / actions specified in the block diagrams and / or flowcharts.

[0609] These computer program instructions may also be stored in a tangible computer-readable medium capable of directing a computer or other programmable data processing apparatus to function in a specific manner, causing the instructions stored in the computer-readable medium to produce an article of writing, which includes instructions that implement the functions / actions specified in the blocks of a block diagram and / or flowchart. Therefore, embodiments of the inventive concept can be implemented in hardware and / or software (including firmware, stored software, microcode, etc.) running on a processor such as a digital signal processor, which may be collectively referred to as a "circuit," a "module," or a variation thereof.

[0610] It should also be noted that in some alternative implementations, the functions / actions marked in the boxes may not occur in the order indicated in the flowchart. For example, depending on the functions / actions involved, two boxes shown consecutively may actually be executed substantially simultaneously, or the boxes may sometimes be executed in reverse order. Furthermore, the functions of a given box in a flowchart and / or block diagram may be divided into multiple boxes, and / or the functions of two or more boxes in a flowchart and / or block diagram may be at least partially integrated. Finally, without departing from the scope of the inventive concept, other boxes may be added / inserted between the shown boxes, and / or boxes / actions may be omitted. Moreover, although some boxes include arrows indicating the main direction of communication regarding the communication path, it should be understood that communication may occur in the opposite direction to the indicated arrows.

[0611] Many changes and modifications can be made to the embodiments without substantially departing from the inventive concept. All such changes and modifications are intended to be included within the scope of the inventive concept herein. Therefore, the foregoing subject matter should be understood as exemplary rather than restrictive, and the examples of embodiments are intended to cover all such modifications, improvements, and other embodiments falling within the spirit and scope of the inventive concept. Therefore, to the fullest extent permitted by law, the scope of the inventive concept should be determined by the widest permissible interpretation of this disclosure, including examples of embodiments and their equivalents, and should not be limited to or restricted to the specific embodiments described above.

Claims

1. A method performed by a first network node providing a connection to a wireless communication device in a wireless network, the method comprising: Receive (1201) a notification from the wireless communication device regarding a radio link failure (RLF) report from the wireless communication device; Send an instruction message (1203) to the wireless communication device, instructing the wireless communication device to send the RLF report; Receive the RLF report (1205); The RLF report is forwarded to the source node serving the source cell in response to the following: the RLF report contains information about failures during the dual active protocol stack handover DAPS HO, the RLF report contains failure information related to the source node serving the source cell, and the first network node is different from the source node serving the source cell; The RLF report is forwarded to the target node serving the target cell in response to the following: the RLF report contains information about failures during DAPS HO, the RLF report contains failure information related to the target node serving the target cell, and the first network node is different from the target node serving the target cell; as well as The first network node is forwarded (1211) to the source node serving the source cell and the target node serving the target cell in response to the following: the RLF report contains information about failures during DAPS HO, the RLF report contains failure information related to the source cell and the target cell, and the first network node is different from the source node serving the source cell and the target node serving the target cell.

2. The method according to claim 1, further comprising: Forward (1213) the RLF report to at least one network node that is processing self-organizing network / minimized drive test SON / MDT in the wireless network.

3. The method according to claim 1 or 2, wherein, Forwarding the RLF report to the source node serving the source cell includes forwarding the RLF report to the source node serving the source cell via X2 / Xn messages / signaling, and forwarding the RLF report to the target node serving the target cell includes forwarding the RLF report to the target node serving the target cell via X2 / Xn messages / signaling.

4. The method according to claim 1 or 2, wherein, Forwarding the RLF report to the source node serving the source cell includes: forwarding the RLF report to the source node serving the source cell via an inter-node radio resource control (RRC) message.

5. The method according to claim 1 or 2, wherein, Forwarding the RLF report to the target node serving the target cell includes: forwarding the RLF report to the target node serving the target cell via an inter-node radio resource control (RRC) message.

6. The method according to claim 1 or 2, wherein, In response to at least one of the source node and the target node adopting a centralized unit / distributed unit (CU / DU) partitioned architecture, forwarding the RLF report includes: forwarding the RLF report to the CU of the at least one of the source node and the target node.

7. The method according to claim 1 or 2, wherein, Forwarding the RLF report to the source node and forwarding the RLF report to the target node includes: sending the RLF report to the source node via a core network function / node, and sending the RLF report to the target node via the core network function / node.

8. The method according to claim 7, wherein, The core network functions / nodes include Access and Mobility Management (AMF) functions / nodes.

9. A first network node (900) in a wireless network, the first network node (900) being adapted to perform operations including: Receive (1201) a notification from the wireless communication device regarding a radio link failure (RLF) report from the wireless communication device; Send an instruction message (1203) to the wireless communication device, instructing the wireless communication device to send the RLF report; Receive the RLF report (1205); The RLF report is forwarded to the source node serving the source cell in response to the following: the RLF report contains information about failures during the dual active protocol stack handover DAPS HO, the RLF report contains failure information related to the source node serving the source cell, and the first network node is different from the source node serving the source cell; The RLF report is forwarded to the target node serving the target cell in response to the following: the RLF report contains information about failures during DAPS HO, the RLF report contains failure information related to the target node serving the target cell, and the first network node is different from the target node serving the target cell; as well as The first network node is forwarded (1211) to the source node serving the source cell and the target node serving the target cell in response to the following: the RLF report contains information about failures during DAPS HO, the RLF report contains failure information related to the source cell and the target cell, and the first network node is different from the source node serving the source cell and the target node serving the target cell.

10. The first network node (900) according to claim 9, wherein, The first network node is also adapted to perform operations including forwarding (1213) the RLF report to at least one network node that processes self-organizing network / minimized drive test (SON / MDT) in the wireless network.

11. The first network node (900) according to claim 9 or 10, wherein, Forwarding the RLF report to the source node serving the source cell includes: forwarding the RLF report to the source node serving the source cell via X2 / Xn messages / signaling.

12. The first network node (900) according to claim 9 or 10, wherein, Forwarding the RLF report to the target node serving the target cell includes: forwarding the RLF report to the target node serving the target cell via X2 / Xn messages / signaling.

13. The first network node (900) according to claim 9 or 10, wherein, Forwarding the RLF report to the source node serving the source cell includes: forwarding the RLF report to the source node serving the source cell via an inter-node radio resource control (RRC) message.

14. The first network node (900) according to claim 9 or 10, wherein, Forwarding the RLF report to the target node serving the target cell includes: forwarding the RLF report to the target node serving the target cell via an inter-node radio resource control (RRC) message.

15. The first network node (900) according to claim 9 or 10, wherein, In response to at least one of the source node and the target node employing a centralized unit / distributed unit (CU / DU) partitioned architecture, when forwarding the RLF report, the first network node is also adapted to perform an operation including forwarding the RLF report to the CU of the at least one of the source node and the target node.

16. The first network node (900) according to claim 9 or 10, wherein, Forwarding the RLF report to the source node and forwarding the RLF report to the target node includes: sending the RLF report to the source node via a core network function / node, and sending the RLF report to the target node via the core network function / node.

17. The first network node (900) according to claim 16, wherein, The core network functions / nodes include Access and Mobility Management (AMF) functions / nodes.

18. A first network node (900) in a wireless network, the first network node (900) comprising: Processing circuit (903); as well as A memory (905) coupled to the processing circuitry, wherein the memory includes instructions that, when executed by the processing circuitry, cause the first network node to perform the method according to any one of claims 1 to 8.

Images