Method and apparatus for early data forwarding in conditional handover of UE in multi-connection

Abstract

The disclosed method and apparatus advantageously provide early data forwarding in conditional handover of a user equipment (UE) (14) in a multi-connection scenario. The early data forwarding includes data from a multi-connection auxiliary node (12).

Description

Technical Field

[0001] Aspects of the present disclosure relate to early data forwarding in a wireless communication network in the context of conditional handover of a UE in multiple connectivity. Background Art

[0002] "Mobility" in wireless communication networks can refer to a wireless device being "handed over" from one radio access node to another, for example, when the quality of the radio connection between a user equipment (UE) and a serving radio access node degrades and a neighboring radio access node offers better quality. One issue is that handover commands or other signaling exchanged over the radio link between a UE and its serving node can be unreliable, given the prevailing radio conditions on the radio link.

[0003] One solution to improving mobility robustness discussed in the context of Fifth Generation (5G) New Radio (NR) is called "conditional handover" or "early handover command." To avoid undesirable reliance on the serving radio link (and radio conditions) when the UE should perform a handover, the possibility of providing the UE with RRC signaling for the handover earlier should be provided. To achieve this, it should be possible to associate a HO command with a condition, for example based on radio conditions similar to those associated with an A3 event, where a given neighbor becomes X dB better than a target. Once the condition is met, the UE performs the handover according to the provided handover command.

[0004] Currently, there are certain challenges with conditional handover ("CHO") or other conditional reconfiguration in the context of multiple connectivity, such as in scenarios involving multi-radio dual connectivity (MR-DC) between a UE and the network.

[0005] With conditional reconfiguration, the network sends a conditional reconfiguration to the UE (also known as a "wireless device") and specifies the conditions that trigger the UE to perform the conditional reconfiguration. The UE waits to perform the conditional reconfiguration until the UE detects that the conditions are met. Once the UE detects that the conditions are met, the UE can perform the conditional reconfiguration autonomously without receiving any additional signaling, which means that the reconfiguration provides robustness against deteriorating radio link conditions.

[0006] While this conditional reconfiguration approach can improve robustness against failures, its use has proven challenging in some contexts. For example, "multi-connectivity" refers to a situation where a wireless device is simultaneously connected (e.g., at the radio resource control (RRC) layer) to multiple different radio network nodes, or to multiple different cells provided by different radio network nodes. Known methods for conditional reconfiguration fail to fully account for the diversity of radio network nodes or cells involved in multiple connections.

[0007] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges. One or more embodiments provide certain technical advantages. For example, one or more embodiments disclosed herein enable a source master node (MN) in a wireless communication network to perform early data forwarding for a UE that is operating in an MR-DC and is configured with conditional reconfiguration (such as CHO). Summary of the Invention

[0008] The disclosed method and apparatus advantageously provide early data forwarding in conditional handover of a user equipment (UE) in a multi-connection scenario. The early data forwarding includes data from a multi-connection assisting node.

[0009] One embodiment includes a method performed by a first network node of a wireless communication network. The method includes: the first network node sending a handover request to a third network node, the handover request including an indication of a conditional handover of a wireless device to the third network node, wherein the first network node and the second network node have multiple connections with the wireless device. The method also includes: the first network node receiving an acknowledgment of the handover request from the third network node; sending a message to the second network node to initiate early data forwarding of data associated with the wireless device from the second network node to the first network node; and sending configuration information for the conditional handover to the wireless device.

[0010] Related embodiments include a first network node configured to operate in a wireless communication network. The first network node includes first communication interface circuitry configured to communicatively couple the first network node to one or more other network nodes, and second communication interface circuitry configured to communicatively couple the first network node to a wireless device. The first network node also includes processing circuitry operably associated with the first communication interface circuitry and the second communication interface circuitry.

[0011] The processing circuitry of the first network node is configured to send a handover request to a third network node, the handover request including an indication of a conditional handover of the wireless device to the third network node, wherein the first network node and the second network node have multiple connections with the wireless device. Furthermore, the processing circuitry of the first network node is configured to: receive a handover request acknowledgment from the third network node; send a message to the second network node to initiate early data forwarding of data associated with the wireless device from the second network node to the first network node; and send configuration information for the conditional handover to the wireless device.

[0012] Another embodiment includes a method performed by a second network node of a wireless communication network. The method includes: the second network node receiving a message from a first network node to initiate early data forwarding from the second network node to the first network node for data associated with a wireless device, the wireless device having multiple connections to the first network node and the second network node. The method also includes: the second network node initiating early data forwarding to the first network node in response to the message.

[0013] A related embodiment includes a second network node configured to operate in a wireless communication network. The second network node includes first communication interface circuitry configured to communicatively couple the second network node to one or more other network nodes, and second communication interface circuitry configured to communicatively couple the second network node to a wireless device. Furthermore, the second network node includes processing circuitry operably associated with the first communication interface circuitry and the second communication interface circuitry and configured to: receive a message from the first network node to initiate early data forwarding from the second network node (12-2) to the first network node for data associated with the wireless device, the wireless device being multi-connected to the first network node and the second network node. The processing circuitry of the second network node is further configured to initiate early data forwarding to the first network node in response to the message.

[0014] Of course, the present invention is not limited to the above features and advantages. In fact, those skilled in the art will recognize other features and advantages by reading the following detailed description and viewing the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a block diagram of one embodiment of a wireless communication network.

[0016] Figure 2 The present invention is a signal flow diagram of an embodiment of signaling between a first network node, a second network node, and a third network node for early data forwarding in conditional handover of a user equipment (UE) in a multi-connectivity scenario.

[0017] Figure 3 is a signal flow diagram of one embodiment of signaling between a first network node, a second network node, and a third network node for terminating early data forwarding.

[0018] Figures 4 to 8 is a signal flow diagram of various embodiments of signaling between a first network node and a second network node or between a first network node and a third network node for conditional handover and early data forwarding.

[0019] Figure 9 is a block diagram of one embodiment of a network node.

[0020] Figure 10is a block diagram of one embodiment of a wireless device.

[0021] Figure 11 is a logic flow diagram of one embodiment of a method performed by a first network node.

[0022] Figure 12 is a logic flow diagram of another embodiment of a method performed by a first network node.

[0023] Figure 13 is a logic flow diagram of one embodiment of a method performed by a second network node.

[0024] Figure 14 is a logic flow diagram of another embodiment of a method performed by a second network node.

[0025] Figure 15 is a block diagram of a wireless communication network according to some embodiments.

[0026] Figure 16 is a block diagram of user equipment according to some embodiments.

[0027] Figure 17 is a block diagram of a virtualization environment according to some embodiments.

[0028] Figure 18 is a block diagram of a communication network with host computers according to some embodiments.

[0029] Figure 19 is a block diagram of a host computer according to some embodiments.

[0030] Figure 20 is a flow chart illustrating a method implemented in a communication system according to one embodiment.

[0031] Figure 21 is a flow chart illustrating a method implemented in a communication system according to one embodiment.

[0032] Figure 22 is a flow chart illustrating a method implemented in a communication system according to one embodiment.

[0033] Figure 23 is a flow chart illustrating a method implemented in a communication system according to one embodiment. DETAILED DESCRIPTION

[0034] Figure 1An example wireless communication network 10 is shown having one or more network nodes 12, wherein the wireless communication network 10 provides multiple connections for wireless devices 14, also referred to as "user equipment" or "UE". The wireless device 14 is configured for multiple connection operation, where "multiple connections" in this context means that the wireless device 14 is simultaneously connected to multiple different network nodes 12 (e.g., at the radio resource control (RRC) layer), or to multiple different cells provided by different network nodes 12. The multiple different network nodes 12 or cells may use the same radio access technology (e.g., they may use Evolved Universal Terrestrial Radio Access (E-UTRA) or they may use New Radio (NR)). Alternatively, the multiple different network nodes 12 or cells may use different radio access technologies, e.g., one may use E-UTRA and another may use NR.

[0035] Figure 1 Three network nodes 12 are shown, depicted as "NW nodes" 12-1, 12-2, and 12-3, where the network nodes 12 may be radio network nodes in a radio access network (RAN) portion of a wireless communication network 10. In the figure, a wireless device 14, also referred to as a UE 14, is multi-connected to a first network node 12-1 and a second network node 12-2. Thus, Figure 1 An example of multi-connectivity is shown as dual connectivity (DC), where a wireless device 14 is simultaneously connected to two different network nodes 12, or to two different cells provided by two different network nodes 12. In this case, the wireless device 14 can be configured with a so-called master cell group (MCG) and a secondary cell group (SCG), where the MCG includes one or more cells provided by the network node 12 acting as a master node (MN) and the SCG includes one or more cells served by the network node 12 acting as a secondary node (SN). The master node can be a master node in the sense that it controls the secondary nodes and / or provides a control plane connection to the core network portion of the wireless communication network 10. For example, E-UTRA-NR (EN) DC means that the primary node uses E-UTRA and the secondary node uses NR, while NR-E-UTRA (NE) means that the primary node uses NR and the secondary node uses E-UTRA.

[0036] In multi-connectivity operation, a wireless device 14 with multiple receivers (Rx) and / or transmitters (Tx) can utilize radio resources in one or more radio access technologies (e.g., New Radio NR and / or E-UTRA) provided by multiple different schedulers connected via a non-ideal backhaul. In this regard, Multi-Radio Dual Connectivity (MR-DC) is a generalization of DC within E-UTRA, where a multi-Rx / Tx wireless device can be configured to utilize resources provided by two different network nodes 12 connected via a non-ideal backhaul, one providing NR access and the other providing E-UTRA access or NR access. One network node 12 acts as a mobile node (MN) and the other network node 12 acts as a network node (SN). For example, E-UTRAN supports MR-DC through E-UTRA-NR Dual Connectivity (EN-DC), where the wireless device is connected to one eNB acting as a mobile node (MN) and one en-gNB acting as a secondary node (SN). In either case, in MR-DC, the wireless device 14 can have a single radio resource control (RRC) state based on the MN RRC and a single control plane connection towards the core network.

[0037] exist Figure 1 In the example of FIG. 1 , first network node 12-1 can be understood as operating as a source MN (S-MN) for multiple connections with wireless device 14. Accordingly, second network node 12-2 operates as a source SN (S-SN) for the multiple connections. At some point during the multiple connection operation, first network node 12-1 decides to configure wireless device 14 for a conditional handover (CHO) to third network node 12-3. Third network node 12-3 is a candidate for selection as a new source node for wireless device 14, and may be one of two or more other network nodes 12 identified as prospective candidates for handover of wireless device 14.

[0038] Advantageously, the first network node 12-1 and the second network node 12-2 are configured to support early data forwarding in the context of CHO of a wireless device 14 having multiple connections with the first network node 12-1 and the second network node 12-2. Specifically, the early data forwarding includes data processed at the second network node 12-2 for the multiple connections with the wireless device 14 and data processed at the first network node 12-1 for the multiple connections with the wireless device 14.

[0039] Figure 1The “messaging / signaling for early data forwarding” depicted in the figure represents control signaling and data communications between the first network node 12-1 and the second network node 12-2 to support early data forwarding. The “CHO signaling / early data forwarding” depicted in the figure represents control signaling and data communications between the first network node 12-1 and the third network node 12-3 to support conditional handover and early data forwarding.

[0040] To understand the advantages of the contemplated arrangement for early data forwarding, consider early data forwarding in the context of CHO, where the wireless device 14 does not perform a handover to the target network node 12 that is the new serving node for the wireless device 14 unless / until a configured condition is met. Consequently, the current serving network node 12 of the wireless device 14 does not know whether or when the wireless device 14 will perform a handover, and therefore, to avoid possible data disruption to the wireless device 14, the current serving network node 12 may begin forwarding data intended for the wireless device 14 to the target network node 12 (in addition to sending the same data to the wireless device 14). See Section 9.2.3.4 of the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.300 V16.5.0 regarding conditional handover and early data forwarding from a single serving network node.

[0041] However, as a significant complication, with multiple connections, there is more than one serving network node 12, and typically data for the wireless device 14 exists at more than one serving network node 12. Advantageously, the techniques disclosed herein provide early data forwarding in the context of CHO with multiple connections, where the early data forwarding introduces or otherwise includes data for the involved wireless devices 14, which is processed by all network nodes 12 in the multiple connections. Figure 2 One example of advantageous signaling and supporting operations for early data forwarding in the context of CHO with multiple connections is provided.

[0042] Specifically, Figure 2Depicted are example signaling flows between a first network node 12-1, a second network node 12-2, and a third network node 12-3, as well as signaling exchanged with a wireless device 14 (illustrated as "UE" 14 in the figure) according to one or more embodiments. The signaling and operations supporting the signaling are particularly advantageous for addressing scenarios involving wireless devices 14 operating in MR-DC and source network nodes 12 involved in multi-connectivity that desire to configure conditional handover or CHO (also known as conditional reconfiguration) of the wireless device 14 via early data forwarding. Early data forwarding, as used herein, refers to data forwarding initiated before CHO is performed. The techniques disclosed herein for providing early data forwarding in the context of multi-connectivity operation include various actions between the involved network nodes 12 to enable early data forwarding in CHO scenarios during multi-connectivity.

[0043] exist Figure 2 In the context of FIGURE 1, a first network node 12-1 performs CHO preparation with respect to a wireless device 14. The first network node 12-1 and a second network node 12-2 have multiple connections with the wireless device 14, and the first network node 12-1 determines to configure the wireless device 14 with a conditional reconfiguration (item 1, "Determine to configure CHO"), here shown as CHO with respect to a third network node 12-3. As a specific example, the multiple connections are MR-DC, with the first network node 12-1 acting as an S-MN and the second network node 12-2 acting as an S-SN.

[0044] The first network node 12-1 sends a handover request (item 2, “HO Request (CHO Indication)”) to a third network node 12-3 (e.g., a target gNodeB) that is a target candidate node. The handover request includes an indication that the procedure is for CHO, and the first network node 12-1 receives a handover request confirmation (item 3, “HO Request Confirmation (in response to CHO Indication)”) from the third network node 12-3, which is sent in response to the handover request confirmation.

[0045] At item 4, the first network node 12-1 determines that early data forwarding is to be performed, and in this example scenario, there are data radio bearers (DRBs) terminated at the multi-connected second network node 12-2, wherein data associated with these DRBs is to be included in the early forwarding. The "S-SN" in item 4 refers to the second network node 12-2 operating as a source secondary node or S-SN.

[0046] Accordingly, first network node 12-1 performs an early data forwarding procedure with second network node 12-2. In the illustrated example, first network node 12-1 sends information to second network node 12-2 to initiate early data forwarding (item 5, "Information for initiating early data forwarding"). For example, in response to receiving a handover request confirmation from third network node 12-3, first network node 12-1 may initiate an address indication procedure with second network node 12-2.

[0047] At this point, it may be helpful to review a few key points about early data forwarding. Because the wireless device 14 is multi-connected to the first network node 12-1 and the second network node 12-2, some data associated with the wireless device 14 is processed at the first network node 12-1—for example, downlink data for the wireless device 14 will be sent on a bearer terminated at the first network node 12-1—and some data associated with the wireless device is processed at the second network node 12-2—for example, downlink data for the wireless device 14 will be sent on a bearer terminated at the first network node 12-1.

[0048] Therefore, the early data forwarding to the third network node 12-3 before the wireless device 14 performs CHO is much more complex than if the wireless device 14 only had a single connection to the first network node 12-1. By sending information from the first network node 12-1 to the second network node 12-2 to initiate early data forwarding for the data in question by the second network node 12-2, the first network node 12-1 is able to forward the early data to the third network node 12-3 not only for data processed by the first network node 12-1 for the wireless device 14 in multiple connections, but also for data processed by the second network node 12-2 for the wireless device 14 in multiple connections.

[0049] Back to Figure 2After first network node 12-1 sends information to second network node 12-2 to initiate early data forwarding, first network node 12-1 receives an early data forwarding indication from second network node 12-2 (item 6, "Early Data Forwarding Indication") and may receive early forwarded data from second network node 12-2 (item 7, "Data"). First network node 12-1 sends an indication for early data forwarding to third network node 12-3 (item 8, "Early Data Forwarding Indication") and begins sending early data to third network node 12-3 (item 9, "Data (including data from S-SN)"). First network node 12-1 also sends an RRC reconfiguration message with a CHO configuration to wireless device 14 (item 10, "RRC Reconfiguration with CHO Configuration"). Wireless device 14 responds with an RRC reconfiguration complete message (item 11, "RRC Reconfiguration Complete") and monitors for the satisfaction of CHO triggering / execution conditions (item 12).

[0050] The early data subject to early data forwarding from the first network node 12-1 to the third network node 12-3 includes, for example, data for the wireless device 14 corresponding to a data radio bearer (DRB) terminated at the multi-connected first network node 12-1 and data for the wireless device 14 corresponding to a DRB terminated at the multi-connected second network node 12-2. Such data is early forwarded from the second network node 12-2 to the first network node 12-1, which then forwards it to the third network node 12-3.

[0051] Figure 3 It can be understood as Figure 2 Continuation of, or depiction of Figure 2 1 . An example signal flow in the context of ongoing early data forwarding established in the manner shown. Thus, early data forwarding is ongoing from the second network node 12-2 to the first network node 12-1 (item 1, "Data (ongoing early forwarding)"). Accordingly, early data forwarding is ongoing from the first network node 12-1 to the third network node 12-3, wherein the early data includes early data forwarded from the second network node 12-2 to the first network node 12-1 (item 2, "Data (ongoing early forwarding of data from the first and second NW nodes)").

[0052] At item 3, the wireless device 14 (illustrated in the figure as "UE 14") determines that a triggering / execution condition for a CHO to the third network node 12-3 is satisfied. Figure 2 Items 10 to 12 of , wherein the first network node 12-1 configures the CHO, including configuring or otherwise indicating a triggering / execution condition.

[0053] In response to determining that the triggering / execution conditions for CHO to third network node 12-3 are met, wireless device 14 sends an RRC reconfiguration complete message to third network node 12-3 (item 4, "RRC reconfiguration complete"), and third network node 12-3 sends a handover success message to first network node 12-1 (item 5, "Handover successful"). This message indicates the execution of CHO by wireless device 14 to third network node 12-3. First network node 12-1 then sends a release request to second network node 12-2 (item 6, "Release Request"), requesting the release of the bearers terminated at second network node 12-2 for the multi-connectivity with wireless device 14. Second network node 12-2 responds to the request by releasing the bearers, terminating early data forwarding, and confirming the release to first network node 12-1 (all shown as item 7, "Stop Early Data Forwarding").

[0054] The second network node 12-2 sends an acknowledgment of the release request (item 8, "Release Request ACK") back to the first network node 12-1 and forwards any data (item 9, "Data") intended for the wireless device 14. The first network node 12-1 then sends state transfer signaling (item 10, "State Transfer") to the third network node 12-3 and performs delayed data forwarding (item 11, "Data") to the third network node 12-3.

[0055] exist Figure 2 and Figure 3 In the context of , the first network node 12-1 can be an M-SN, such as a source master gNB (MgNB), the second network node 12-2 can be an S-SN, such as a source secondary gNB (SgNB), and the third network node 12-3 can be a target gNB, which is a candidate for serving as a new source node for the wireless device 14.

[0056] The depicted operations enable a source MN to perform early data forwarding for a UE operating in an MR-DC to enable the UE to be configured for conditional reconfiguration (e.g., conditional handover - CHO). In other words, the source MN can request CHO for a target candidate and initiate early data forwarding from the source SN to the source MN for SN-terminated bearers, enabling each target candidate to receive early data for a possible incoming UE with SN-terminated bearers.

[0057] Such an arrangement increases the data rate to the wireless device 14, as it can continue to operate in the MR-DC while having the potential to improve its robustness through the configured CHO. In particular, due to early data forwarding, the depicted operation allows a wireless device 14 configured with an SN-terminated bearer to be configured with CHO and still benefit from early data forwarding of data processed for the wireless device 14 at the MN and any SN involved in the multi-connectivity, thereby reducing the interruption time during CHO. The described data forwarding can provide lossless CHO.

[0058] Example embodiments include a first network node 12-1 operating as a source MN, the source MN including processing circuitry and first communication interface circuitry configured to communicatively couple the source MN to one or more other network nodes (e.g., a second network node 12-2 operating as a source SN) and another radio network node that is a handover target for a UE operating in an MR-DC with respect to the source MN and the source SN. In one or more embodiments, the source MN also includes second communication interface circuitry, such as radio frequency transmit and receive circuitry, for communicating with the UE via one or more radio access technologies (RATs). Such circuitry provides an "air interface" for transmitting downlink signaling to the UE and receiving uplink signaling from the UE.

[0059] In one or more embodiments, the source MN also includes storage devices, such as a mix of volatile and non-volatile memory circuits, and / or other types of storage devices, including any one or more of SRAM, DRAM, NVRAM, FLASH, EEPROM, solid-state drives (SSDs), magnetic disks, etc. Broadly speaking, in one or more embodiments, the source MN includes one or more types of computer-readable media, and the processing circuitry of the source MN includes one or more microprocessors or other digital processing circuits configured (particularly adapted) to perform operations as described herein based at least in part on executing program instructions of one or more computer programs stored in the storage devices. More broadly speaking, the processing circuitry is fixed or dedicated circuitry, or programmable configurable circuitry, or any combination thereof.

[0060] In one or more embodiments, if it is determined to perform early data forwarding, the source MN initiates an address indication procedure with the second network node (source SN) upon receiving the handover request confirm message.

[0061] The source MN may receive an early data forwarding indication from a second network node operating as a source secondary node SN (i.e., from an S-SN). In the same or other embodiments, the source MN may receive forwarded data of a first type from a second network node operating as a source secondary node SN (i.e., from an S-SN). For example, the "first type of forwarded data" corresponds to data forwarded from the source SN and associated with a bearer terminated by the SN.

[0062] In one or more embodiments, the source MN sends an early data forwarding indication to a third network node (which is a target candidate, such as a target gNodeB). In the same or other embodiments, the source MN sends forwarded data to the third network node (which is a target candidate, such as a target gNodeB). Here, "forwarded data" refers to data forwarded from the source SN and associated with the SN-terminated bearer.

[0063] Regarding the above details, for example, the processing circuitry of the source MN being configured to "send" or "receive" in one or more embodiments means that the processing circuitry is operable to send or receive messages or other signaling via the communication interface circuitry of the source MN. Furthermore, to the extent that the source MN is virtualized or implemented in a distributed manner, the processing circuitry of the source MN being configured to "send" or "receive" should be understood to mean that the processing circuitry is configured to send and / or receive signaling to and / or from other entities that are at least functionally external to the processing circuitry, and the nature of such signaling depends on the circuit configuration and medium / media interconnecting the processing circuitry with the external entities. The same or similar understanding applies to the example source SN.

[0064] At the second network node 12-2 operating as a source SN, the source SN includes processing circuitry and a first communication interface circuit configured to communicatively couple the source SN to one or more other network nodes, such as another radio network node operating as a source MN. In one or more embodiments, the source SN further includes a second communication interface circuit, such as a radio frequency transmit and receive circuit, for communicating with the UE via one or more radio access technologies (RATs). Such circuitry provides an "air interface" for transmitting downlink signaling to the UE and receiving uplink signaling from the UE.

[0065] In one or more embodiments, the source SN also includes a storage device, such as a mix of volatile and non-volatile memory circuits, and / or other types of storage devices, including any one or more of SRAM, DRAM, NVRAM, FLASH, EEPROM, solid-state drives (SSDs), magnetic disks, etc. Broadly speaking, in one or more embodiments, the source SN includes one or more types of computer-readable media, and the processing circuitry of the source MN includes one or more microprocessors or other digital processing circuits that are configured (particularly adapted) to perform operations as described herein based at least in part on executing program instructions of one or more computer programs stored in the storage device. More broadly speaking, the processing circuitry is a fixed or dedicated circuit, or a programmable configurable circuit, or any combination thereof.

[0066] With the above in mind, various solutions in this disclosure relate to scenarios where a UE is configured with multi-radio dual connectivity (MR-DC) when the UE receives a conditional handover (CHO) configuration. Certain embodiments described herein focus on NR-DC (i.e., when both the primary and secondary nodes are NR gNBs), but these solutions are equally applicable to other DC scenarios (e.g., NE-DC, (NG)EN-DC, and LTE DC).

[0067] As an example, consider three methods for three corresponding nodes in a mobile network, including a first network node 12-1, a second network node 12-2, and a third network node 12-3. Possible correspondences are:

[0068] -First network node 12-1: can correspond to (e.g., operate as) a source master node (MN) S-MN, a source gNodeB, a source eNodeB, a source NG-RAN node, an M-NG-RAN node indicating a gNodeB operating as a MN in an MR-DC and associated with an NG-RAN (e.g., connected to a 5GC); an M-NG-RAN node indicating an ng-eNodeB operating as a MN in an MR-DC and associated with an NG-RAN (e.g., connected to a 5GC); an LTE eNodeB connected to an EPC operating a MeNodeB or MeNB.

[0069] -Second network node 12-2: may correspond to (e.g., operate as) a source secondary node (SN) S-SN, a source secondary gNodeB (SgNB), a source secondary eNodeB (SeNB), an auxiliary source NG-RAN node, etc.

[0070] - Third network node 12-3: can correspond to (e.g., operate as) a target candidate node, a candidate target node, a target MN (T-MN), a target node, a target candidate gNodeB, a target candidate eNodeB, a target candidate NG-RAN node, a candidate target gNodeB, a candidate target eNodeB, a candidate target NG-RAN node, a target gNodeB, a target eNodeB, a target NG-RAN node; a target candidate NG-RAN node indicating a gNodeB associated with the NG-RAN (e.g., connected to a 5GC); a target candidate NG-RAN node indicating an ng-eNodeB associated with the NG-RAN (e.g., connected to a 5GC); a target candidate LTE eNodeB connected to the EPC, which may be a target candidate MeNodeB or a target candidate MeNB.

[0071] Unless explicitly stated otherwise, the terms target, target node, target candidate node, target candidate, candidate target node should be construed as synonyms.

[0072] For example, in an EN-DC configuration, the first network node 12-1 corresponds to a source eNodeB (S-eNB), the second network node 12-2 corresponds to an NR gNodeB operating as a secondary S-gNodeB (SgNB), and the third or target node 12-3 corresponds to a target eNodeB.

[0073] For example, in an NR-DC configuration, the first network node 12-1 corresponds to a source gNodeB (S-gNB), the second network node 12-2 corresponds to an NR gNodeB operating as a secondary S-gNodeB (SgNB), and the third or target network node 12-3 corresponds to a target gNodeB.

[0074] The term conditional handover or CHO appears frequently in this document. However, other terms can be considered synonymous, such as conditional reconfiguration or conditional configuration (because the message stored and applied when the condition is met is RRCReconfiguration or RRCConnectionReconfiguration). Broadly speaking, CHO is a conditional reconfiguration in which the triggering / execution conditions are configured and the reconfiguration message applied when the triggering conditions are met.

[0075] As an example, the process described herein is for a case where a UE operating in MR-DC is configured with CHO. Then, upon receiving the HO Request Confirmation ACK message, the source MN requests the source SN to initiate early data forwarding (e.g., using an Xn-U Address Indication message), for example, if the UE is configured with an SN-terminated bearer. However, the method is also applicable to the case where the UE is configured with CHO and the network (e.g., the source MN) determines to add an SN-terminated bearer. In this case, the early data forwarding request can be sent after the SN addition is complete.

[0076] An example method for CHO preparation performed at the first network node 12-1 operating as a source MN includes:

[0077] - determining to configure the UE with a conditional reconfiguration (e.g., conditional handover - CHO), wherein the UE operates in MR-DC with the first network node as a master node (e.g., source MN "S-MN");

[0078] o The determination may be based on measurement reports received at the source MN from the UE, including measurements of cells associated with neighboring nodes (e.g., neighboring gNodeBs) that may be target candidate nodes for CHO;

[0079] - sending a handover request message to the third network node 12-3 (which is the target candidate node, e.g. a target gNodeB), including an indication that the procedure is for CHO;

[0080] o In one embodiment, the MN sends a Handover Request message to a single target candidate, including an indication that the procedure is for CHO;

[0081] • For example, a target candidate may have one target cell candidate associated with it.

[0082] o In one embodiment, the MN sends a Handover Request message to a single target candidate, including an indication that the procedure is for CHO;

[0083] • For example, a target candidate may have multiple target cell candidates associated with it. In this case, there may be one handover request message sent for each candidate target cell.

[0084] o In one embodiment, the MN sends a handover request message to a plurality of target candidates, including an indication that the procedure is for CHO;

[0085] For example, a target candidate may have multiple target cell candidates associated with it. In this case, there may be one handover request message sent for each candidate target cell. And there may be multiple candidate cells in different target candidate nodes.

[0086] - Receiving a handover request confirm message from the third network node 12-3 (which is the target candidate node, eg a target gNodeB).

[0087] o In one embodiment, the MN receives a handover request confirmation from a single target candidate;

[0088] • For example, a target candidate may have one target cell candidate associated with it.

[0089] o In one embodiment, the MN receives a handover request confirmation message from a single target candidate node;

[0090] • For example, a target candidate may have multiple target cell candidates associated with it. In this case, there may be one handover request confirm message received for each candidate target cell.

[0091] o In one embodiment, the MN receives handover request confirmation messages from multiple target candidates;

[0092] For example, a target candidate may have multiple target cell candidates associated with it. In this case, there may be one handover request confirmation message received for each candidate target cell. There may be multiple candidate cells in different target candidate nodes.

[0093] Early data forwarding steps involving the source SN

[0094] - Sending to the second network node operating as source secondary node SN (i.e. to the S-SN) enabling the second network node to initiate early data forwarding (from the source SN to the source MN)

[0095] Required information;

[0096] Additional actions can include any one or more of the following:

[0097] - determining to perform early data forwarding; and

[0098] - determining whether the UE is configured with an SN terminated bearer; and if the UE is configured with an SN terminated bearer, performing an early data forwarding procedure with the second network node 12-2 operating as a Source Secondary Node (S-SN).

[0099] If it is determined to perform early data forwarding, upon receiving the handover request confirm message, the first network node 12-1 (eg, source MN) may initiate an address indication procedure with the second network node 12-2.

[0100] In one or more embodiments, the "information required to initiate early data forwarding (from source SN to source MN)" corresponds to the information sent during the address indication process.

[0101] In at least one embodiment, the "information required to initiate early data forwarding (from the source SN to the source MN)" is a request to the second network node 12-2 (source SN) to initiate early data forwarding. The request may be accepted, and in this case, the second network node 12-2 (source SN) sends an Early Forwarding Transfer message. Alternatively, the second network node 12-2 may reject the request and send a message indicating a refusal to perform early data forwarding. The second network node 12-2 may reject the early data forwarding request by sending an "Error Indication" message to the first network node 12-1.

[0102] In one or more embodiments, the address indication procedure is an XN-U address indication procedure, as defined in TS 38.423 V16.5.0 (e.g., in subclause 8.2.6). In an example implementation, where early data forwarding is applied to SN-terminated bearers, the Xn-U address indication may be used to trigger the start of data forwarding for the SN-terminated bearers, in conjunction with sending an Early Forwarding Transport message from the S-SN to the S-MN.

[0103] The Xn-U address indication includes, for example, an indication that the procedure is for conditional handover. See, for example, the CHO MR-DC indicator described in TS 38.423. In the same or another example, the Xn-U address indication includes an indication that the procedure is associated with early data forwarding.

[0104] The Xn-U address indication may be triggered in parallel with an SN release request containing an indication that the procedure is for CHO and / or early data forwarding and / or early data forwarding for CHO.

[0105] In at least one embodiment, the first network node 12-1 corresponds to an M-NG-RAN node. Furthermore, in at least one embodiment, the first network node 12-1 indicates its own forwarding address (or addresses) to the second network node 12-2 (operating as a source SN) during an address indication procedure. In a specific example, the first network node 12-1 (e.g., an M-NG-RAN node) sends an XN-U address indication message.

[0106] For MR-DC with 5GC, the Xn-U address indication procedure is used to provide forwarding address and Xn-U bearer address information for completing the setup of SN-terminated bearers from the M-NG-RAN node to the S-NG-RAN node as specified in 3GPP TS 37.340 V16.5.0. Figure 4 The signaling for Xn-U address indication between the M-NG-RAN node and the S-NG-RAN node for MR-DC with 5GC is described.

[0107] The Xn-U Address Indication procedure is initiated by the M-NG-RAN node. Upon receiving the XN-U Address Indication message, in the case of data forwarding, the S-NG-RAN node shall forward pending downlink (DL) user data to the indicated TNL address; in the case of Xn-U bearer establishment for SN-terminated bearers, the S-NG-RAN node may start transmitting user data to the indicated TNL address. If the XN-U Address Indication message includes the DRB ID using IE, the S-NG-RAN node (if applicable) shall act as specified in TS 37.340 V16.5.0.

[0108] In the CHO context of a bearer with early data forwarding and SN termination, the Xn-U Address Indication procedure is initiated by the M-NG-RAN node. If the Early Data Forwarding Indicator IE or the Conditional Handover Information IE is included in the XN-U Address Indication message, the S-NG-RAN node shall forward pending DL user data to the indicated TNL address while continuing to send DL user data to the UE.

[0109] The XN-U address indication message to be sent from the source MN (M-NG-RAN node) to the source SN (S-NG-RAN node) may contain or otherwise indicate CHO information and / or include an early data forwarding indicator. In one or more embodiments, the message is sent by the M-NG-RAN node to provide the S-NG-RAN node with data forwarding or Xn-U bearer address information for SN-terminated bearers. Before receiving the Xn-U address indication, the S-SN cannot send packets to the S-MN, for example, in the case of packets from the user plane function (UPF) to the S-SN for SN-terminated bearers. Therefore, due to the presence of the GTP-U tunnel endpoint in the Xn-U address indication, the S-SN can perform data forwarding to the S-MN. Delayed data forwarding is performed when CHO is performed, that is, after the S-MN receives the handover success message.

[0110] One or more embodiments include the first network node 12-1 performing at least one of: receiving an SN status transmission from the second network node 12-2 operating as a source SN during CHO preparation; and sending an SN status transmission to a third network node 12-3 (e.g., target candidate node, target gNodeB) during CHO preparation.

[0111] Furthermore, the operation may include delaying the sending of an SN release request message to the second network node 12-2 operating as a source secondary node (S-SN). The delay in this signaling corresponds to the fact that the CHO is still in the preparation phase. When the CHO is executed, the source SN needs to be released, or the SN needs to be indicated to be retained in case the target candidate MN indicated in the HO request confirms to retain the SN when the CHO is executed.

[0112] Thus, in one or more embodiments, method operations at a first network node 12-1 acting as an S-MN, etc., with respect to a multiple connection with a wireless device 14 include the first network node 12-1 delaying triggering (i.e., refraining from initiating, refraining from starting) a SN release procedure, for example, upon receiving a handover request acknowledgment from a third network node 12-3 that is a target for CHO. The SN release procedure may correspond to a MeNB-initiated SgNB release procedure as defined in TS 36.423, subclause 8.7.9, for example, when the MN is an LTE node and the SN is an NR node (for a UE operating in EN-DC). The SN release procedure may correspond to an M-NG-RAN node-initiated S-NG-RAN node release procedure as defined in TS 38.423 V16.5.0, subclause 8.3.6, for example, when the MN is an NR node and the SN is an NR node (for a UE operating in NR-DC).

[0113] When the SN Release Request message is sent by the M-SN to the S-SN, the SN Release Request message may correspond to the SGNB Release Request message as defined in TS 36.423 V16.5.0, for example, when the MN is an LTE node and the SN is an NR node (for a UE operating in EN-DC). The SN Release Request message may correspond to the S-Node Release Request message as defined in TS 38.423 V16.5.0, for example, when the MN is an NR node and the SN is an NR node (for a UE operating in NR-DC).

[0114] In one or more embodiments, if a handover request acknowledgment in response to a handover request for a conventional reconfiguration (e.g., handover) has been received at the first network node 12-1, the first network node 12-1 initiates the SN release procedure (if the UE operates in MR-DC). However, if a handover request acknowledgment in response to a handover request for a conditional reconfiguration (e.g., CHO) has been received, the first network node 12-1 refrains from initiating the SN release procedure (if the UE operates in MR-DC).

[0115] In case the first network node 12-1 operates as an S-MN in an MR-DC scenario and there are multiple target network nodes that are respective candidates for receiving the wireless device 14 in CHO, the first network node 12-1 monitors reception of a first message from one of the target candidates and, upon receiving the first message, initiates an SN release procedure if the UE is still operating in MR-DC when the message is received.

[0116] The first network node 12-1 may be an LTE eNodeB operating as an MN that configures the UE with conditional reconfiguration such as CHO. Here, the first network node 12-1 sends an RRC reconfiguration message to the UE containing the CHO configuration (e.g., the conditionalReconfiguration field of the IE ConditionalReconfiguration defined in 3GPP TS 38.331).

[0117] Another example operation at the first network node 12-1 operating as an S-MN in a multi-connectivity scenario involving the second network node 12-2 operating as a multi-connectivity S-SN includes receiving an early data forwarding indication from the second network node 12-2. For example, the early data forwarding indication corresponds to an early forwarding transmission message received over an Xn interface. The early data forwarding indication is received in response to an indication for early data forwarding sent from the first network node 12-1 to the second network node 12-2.

[0118] In embodiments involving CHO in MR-DC operation, for SN terminated bearers, an Early Forwarding Transport procedure is used to transmit a count (COUNT) of first downlink SDUs forwarded by the source S-NG-RAN node in the case of Early Data Forwarding. Such a procedure may be used Figure 5 The signaling shown. Figure 6 The corresponding signaling between the source S-NG-RAN node (S-SN) and the source M-NG-RAN node (S-MN) can be seen in the figure.

[0119] The "DRB List Subject to Early Forward Transfer" information element (IE) included in the Early Forward Transfer message contains DRB IDs corresponding to DRBs that are subject to simultaneous service by the source and target NG-RAN nodes during DAPS handover or DRBs transferred during CHO.

[0120] For each DRB in the DRB List IE subject to early forwarding transmission, the target NG-RAN node or source M-NG-RAN node shall use the value of the DL Count Value IE as the count of the first downlink SDU forwarded by the source NG-RAN node or S-NG-RAN node to the target NG-RAN node or source M-NG-RAN node.

[0121] For each DRB in the DRB List Subject to Early Forward Transfer IE for which a Discard DL Count Value IE is received in the Early Forward Transfer message, the target NG-RAN node does not send forwarded downlink SDUs to the UE with a count less than the provided count and discards them if no transmission was attempted.

[0122] From the perspective of the second network node 12-2 operating as a source SN in a multi-connectivity scenario, example method steps or operations include: receiving information necessary to initiate early data forwarding (from the source SN to the source MN) from the first network node 12-1 (which is a source node, such as a source gNodeB), sending an early data forwarding indication to the first network node 12-1, and sending forwarded data to the first network node 12-1. The data forwarded by the second network node 12-2 to the first network node 12-1 may then be forwarded by the first network node 12-1 to a third network node 12-3 that is a CHO target.

[0123] Upon receiving signaling at the first network node 12-1 indicating a successful handover, i.e., performing a CHO by the wireless device 14 to the target third network node 12-3, further operations at the second network node 12-2 are associated with the successful handover, or at least with the signaling sent by the first network node 12-1 to the second network node 12-2. In the case where the first network node 12-1 operates as a source NG-RAN node and the third network node 12-3 operates as a target NG-RAN node, Figure 7 Example handover success signaling is depicted. For example, the signaling may be defined in 3GPP TS 38.423.

[0124] More generally, upon successful execution of a CHO of the wireless device 14 to the third network node 12-3, the signaling from the third network node 12-3 to the first network node 12-1 includes a message such as a UE context release message or a retrieve UE context request. Furthermore, the message to the first network node 12-1 indicating that the CHO has been performed may come from the target node or from the UE, and may be any message indicating to the first network node 12-1 that the CHO has been performed.

[0125] As previously described, when first network node 12-1 determines that a CHO handover has been performed, it sends a release request message (SN Release Request) to second network node 12-2 to terminate early data forwarding at second network node 12-2 and initiate the release of the DRBs for multi-connection termination at second network node 12-2. In one embodiment, upon receiving a handover success message, first network node 12-1 initiates the release of resources at second network node 12-2 by sending signaling to second network node 12-2 including a reason indicating MCG mobility. Second network node 12-2 acknowledges the release request. If (delayed) data forwarding is required, first network node 12-1 provides a data forwarding address to second network node 12-2. Receipt of such a message at second network node 12-2 triggers second network node 12-2 to stop providing user data to wireless device 14 and, if applicable, initiate delayed data forwarding.

[0126] Therefore, in one or more embodiments, the first network node 12-1 (e.g., S-MN) indicates a cause value of the SN release request to the second network node 12-2 (e.g., source SN "S-SN"), indicating that the release is triggered due to CHO. The cause value can be at least one of the following:

[0127] MN mobility;

[0128] o This can be used as a cause value in cases where the S-SN does not need to perform any distinction between CHO and legacy HO, for example, when sending an SN Release Request Ack.

[0129] Conditional MN mobility;

[0130] o This can be used as a cause value in cases where the S-SN needs to perform a distinction between CHO and legacy HO, for example, when sending an SN Release Request Acknowledgement including specific information;

[0131] MCG mobility;

[0132] o This can be used as a cause value in cases where the S-SN does not need to perform any distinction between CHO and legacy HO, for example, when sending an SN Release Request Ack.

[0133] Conditional MCG mobility;

[0134] o This can be used as a cause value in cases where the S-SN needs to perform a distinction between CHO and legacy HO, for example, when sending an SN Release Request Acknowledgement including specific information;

[0135] In at least one embodiment, if the S-SN is forwarding data (e.g., for SN-terminated bearers) to the MN, the SN Release Request Acknowledge message instructs the S-SN to freeze PDCP and stop sending DL data to the wireless device 14. The SN Release Request Acknowledge message returned by the second network node 12-2 to the first network node 12-1 may confirm that the resources have been released. Figure 8 Example signaling for a release request and confirmation between a first network node and a second network node acting as M-NG-RAN and S-NG RAN nodes is shown. In one or more embodiments, if the S-NG-RAN node provides data forwarding related information in the S-Node Release Request Confirm message for a QoS flow mapped to a DRB with a bearer option configured with SN termination in the PDU Session List to be Released - SN Termination IE (which is received in the first network node S-MN), the M-NG-RAN node may decide to provide a data forwarding address to the S-NG-RAN node and trigger the Xn-U Address Indication procedure, as specified in TS 37.340 for CHO.

[0136] Additional operations may include: the first network node 12-1, operating as a source MN, receiving an SN Status Transfer from the second network node 12-2, operating as a source SN. For each corresponding DRB in the S-SN DRB configuration to which PDCP SN and HFN status preservation is applied, the source MN receives the uplink PDCP SN and HFN receiver status and the downlink PDCP SN and HFN transmitter status from the S-SN. The source MN receives the SN Status Transfer message from the S-SN at the point in time at which it considers the transmitter / receiver status to be frozen. In the case of MR-DC, if the source MN performs a PDCP SN length change or RLC mode change for a DRB as specified in TS 37.340, it should ignore the information received in the message for that DRB. For each DRB for which the source SN has accepted an uplink forwarding request from the S-MN, the source MN may receive, in the SN Status Transfer message, the missing and received uplink SDUs in the Receive Status of the UL PDCP SDU IE.

[0137] For each DRB in the DRB List Subject to Status Transfer IE, the source MN shall not transmit any uplink packets with a lower PDCP-SN than the value contained in the UL Count Value IE. For each DRB in the DRB List Subject to Status Transfer IE, the source MN shall use the value of the PDCP SN contained in the DL Count Value IE for the first downlink packet for which a PDCP-SN has not been assigned. If the reception status of the UL PDCP SDU IE for at least one DRB is included in the SN Status Transfer message, the source MN node may use it in a status report message sent over the radio interface to the wireless device 14. If the SN Status Transfer message contains the Old QoS Flow List - Expected UL End Marker IE in the DRB List Subject to Status Transfer IE, the source MN shall be prepared to receive the SDAP end marker for the QoS flow via the corresponding DRB, as specified in TS 38.300.

[0138] Note that the early data forwarded from the second network node 12-2 to the first network node 12-1 may include DL data that has not been acknowledged by the wireless device 14. More generally, the data subject to early forwarding from the second network node 12-2 to the first network node 12-1 for further forwarding to the third network node 12-3 targeted by the CHO may be DL data that the second network node 12-2 is still to receive from the UPF or UL data that it may still receive from the UE 14.

[0139] The second network node 12-2 may be informed that CHO is being configured at the wireless device 14 in question. For example, the second network node 12-2 receives a message (e.g., an SN Request Release message) from the first network node 12-1 indicating that this is triggered because the wireless device 14 has been configured with CHO. In this case, upon receipt, the source SN does not release the SN resources, but it prepares for such release (e.g., upon receiving another SN Request Release message later) and sends an SN Request Release Acknowledgement to the first network node 12-1.

[0140] The process of supporting early forwarding from the secondary network node 12 via the primary network node 12 in a multi-connectivity scenario may require changes to the 3GPP TS 38.423 specification, for example during a handover success procedure.

[0141] For example, for CHO in MR-DC operation, for SN terminated bearers, the Early Forward Transport procedure is used to transmit a count of the first downlink SDUs forwarded by the source S-NG-RAN node in case of Early Data Forwarding.

[0142] In addition, the DRB List Subject to Early Forward Transfer IE included in the Early Forward Transfer message contains DRB IDs corresponding to DRBs that are subject to simultaneous service by the source and target NG-RAN nodes during DAPS handover or DRBs transferred during CHO.

[0143] In addition, for each DRB in the DRB List Subject to Early Forward Transfer IE, the target NG-RAN node or source M-NG-RAN node shall use the value of the DL Count Value IE as the count of the first downlink SDU forwarded by the source NG-RAN node or S-NG-RAN node to the target NG-RAN node or source M-NG-RAN node. For each DRB in the DRB List Subject to Early Forward Transfer IE for which a Discard DL Count Value IE was received in the Early Forward Transfer message, the target NG-RAN node shall not send forwarded downlink SDUs to the UE with a count less than the provided one and shall discard them if no transmission was attempted.

[0144] The disclosed early data forwarding in multi-connectivity may also require changes to 3GGP TS 37.340. Specifically, in the signaling flow of the existing MN to ng-eNB / gNB change procedure, resource release at the S-SN is deferred until the S-MN receives an indication of successful CHO. The S-MN can use the XN-U address indication to indicate to the S-SN that early data forwarding will be used, i.e., SN-terminated bearers applied by the S-SN to the UEs involved. In this context, the S-SN sends an Early Forwarding Transfer message to the S-MN.

[0145] Furthermore, one or more embodiments disclosed herein address situations where a UE operating in MR-DC and a source node that wants to configure conditional handover (also known as conditional reconfiguration) want to perform early data forwarding, i.e., for a UE in MR-DC operation, data forwarding begins before CHO is performed. Example methods include different actions between network nodes to implement early data forwarding in this mobility scenario.

[0146] The example method enables a source MN to perform early data forwarding for a UE operating in an MR-DC such that the UE is configured with conditional reconfiguration (e.g., conditional handover - CHO). In other words, the source MN will be able to request CHO for a target candidate and initiate early data forwarding from the source SN to the source MN for SN-terminated bearers, enabling the target candidate to receive early data of a possible incoming UE with SN-terminated bearers.

[0147] Figure 9A network node 12-X, such as a radio network node, is shown configured to operate in a wireless communication network 10. The "-X" suffix indicates that the network node 12-X can be configured as a source primary node in a multi-connectivity scenario (e.g., the "first" network node 12-1 described in any of the aforementioned embodiments), or as a source secondary node in a multi-connectivity scenario (e.g., the "second" network node 12-2 described in any of the aforementioned embodiments).

[0148] Therefore, refer to Figure 9 , an example first network node 12-1 is configured for operating in a wireless communication network 10 and includes a first communication interface circuit 20-1 configured for communicatively coupling the first network node 12-1 to one or more other network nodes 12. Furthermore, the first network node 12-1 includes a second communication interface circuit 20-2 configured for communicatively coupling the first network node 12-1 to a wireless device 14. The second communication interface circuit 20-2 includes or is associated with one or more transmit / receive antennas 24.

[0149] Furthermore, the first network node 12-1 includes processing circuitry 26-1 operatively associated with the first and second communication interface circuitry 20-1 and 20-2, and may include or be associated with a storage device 28-1 including one or more types of computer-readable media.

[0150] The processing circuit 26-1 is configured to send a handover request to the third network node 12-3, the handover request including an indication of a conditional handover of the wireless device 14 to the third network node 12-3. In this context, the first network node 12-1 and the second network node 12-2 have multiple connections with the wireless device 14. Furthermore, the processing circuit 26-1 is configured to receive an acknowledgment of the handover request from the third network node 12-3 and send a message to the second network node 12-2 to initiate early data forwarding of data associated with the wireless device 14 from the second network node 12-2 to the first network node 12-1. Furthermore, the processing circuit 26-1 is configured to send configuration information for the conditional handover to the wireless device 14.

[0151] As illustrated, in one or more embodiments, for multi-connectivity, the first network node 12-1 operates as a source primary node (S-MN) with respect to the wireless device 14 and the second network node 12-2 operates as a source secondary node (S-SN).

[0152] The early data forwarding may be applied to one or more data radio bearers (DRBs) used in the multi-connectivity and terminated at the second network node 12-2, and the message sent to the second network node 12-2 includes, for example, a forwarding address associated with the data forwarding. In one or more embodiments, the message is an Xn-U address indication message.

[0153] Furthermore, in at least one embodiment, processing circuit 26-1 is configured to send early forwarded data to third network node 12-3. The early forwarded data includes first data associated with a multi-connected DRB terminated at first network node 12-1 and second data associated with a multi-connected DRB terminated at second network node 12-2. The second data is received at first network node 12-1 by early forwarding from second network node 12-2 to first network node 12-1.

[0154] Furthermore, in one or more embodiments, the processing circuit 26-1 is configured to receive an indication from the third network node 12-3 that the handover for the wireless device 14 was successful, and in response, send a release request to the second network node 12-2 requesting release of the multi-connected DRB terminated at the second network node 12-2.

[0155] In the same or yet another embodiment, processing circuitry 26-1 is configured to receive an early forwarding transfer message from second network node 12-2 in response to a message sent by first network node 12-1 to initiate early data forwarding. The early forwarding transfer message indicates a DRB at second network node 12-2 that is subject to early data forwarding by second network node 12-2 to first network node 12-1.

[0156] In one or more embodiments, the multiple connections with the wireless device 14 are MR-DC supported by the first network node 12-1 and the second network node 12-2. To support such multiple connections, in an example embodiment, the wireless device 14 includes Figure 10 In particular, the example wireless device 14 includes communication circuitry 30 and one or more associated transmit / receive antennas 32, as well as processing circuitry 34 and associated storage devices 36, which may include one or more types of computer-readable media.

[0157] Return to reference Figure 9However, with respect to the example second network node 12-2, the example network node 12-2 is configured for operation in the wireless communication network 10. Specifically, the second network node 12-2 includes a first communication interface circuit 20-1 configured for communicatively coupling the second network node 12-2 to one or more other network nodes 12, and a second communication interface circuit 20-2 configured for communicatively coupling the second network node 12-2 to the wireless device 14.

[0158] Furthermore, the second network node 12-2 includes a processing circuit 26-2 operatively associated with the first communication interface circuit 20-1 and the second communication interface circuit 20-2. The processing circuit 26-2 is configured to receive a message from the first network node 12-1 to initiate early data forwarding from the second network node 12-2 to the first network node 12-1 for data associated with the wireless device 14, the wireless device 14 being multi-connected to the first network node 12-1 and the second network node 12-2. The processing circuit 26-2 is configured to initiate early data forwarding to the first network node 12-1 in response to the message.

[0159] In one or more example embodiments, for multi-connectivity, second network node 12-2 operates as an S-SN and first network node 12-1 operates as an S-MN. Early data forwarding applies to one or more DRBs used in the multi-connectivity and terminated at second network node 12-2. The message received from first network node 12-1 for initiating early data forwarding is, for example, an Xn-U address indication message. In one or more embodiments, as part of initiating early data forwarding, processing circuitry 26-2 is configured to send an early forwarding transfer message to first network node 12-1, the early forwarding transfer message indicating the DRBs at second network node 12-2 that are subject to early data forwarding.

[0160] Furthermore, in one or more embodiments, the processing circuit 26-2 is configured to receive a release request from the first network node 12-1 after initiating early data forwarding and in response, terminate the early data forwarding and initiate release of the DRB terminating at the second network node 12-2 for the multi-connection.

[0161] In at least one embodiment, the message received at the second network node 12-2 to initiate early data forwarding by the second network node 12-2 includes an indication of CHO for the wireless device 14. Here, the processing circuit 26-2 is configured to initiate early data forwarding in response to the indication of CHO.

[0162] Figure 11 An example method 1100 is shown that is performed by a first network node 12-1 of a wireless communication network 10. The method 1100 includes:

[0163] - sending (block 1102) a handover request to the third network node 12-3, the handover request including an indication of a CHO of the wireless device 14 to the third network node 12-3, wherein the first network node 12-1 and the second network node 12-2 are multi-connected to the wireless device 14;

[0164] - receiving (block 1104) a handover request confirmation from the third network node (12-3);

[0165] - sending (block 1106) a message to the second network node 12-2 to initiate early data forwarding of data associated with the wireless device 14 from the second network node 12-2 to the first network node 12-1; and

[0166] - Sending (block 1108) configuration information for the CHO to the wireless device 14.

[0167] For multi-connectivity, first network node 12-1 may operate as an S-MN, and second network node 12-2 may operate as an S-SN. Early data forwarding applies to one or more DRBs terminated at second network node 12-2 and used for multi-connectivity. In one or more embodiments, a message sent to second network node 12-2 includes a forwarding address associated with early data forwarding. As a specific example, the message is an Xn-U Address Indication message.

[0168] In at least one embodiment, the method 1100 also includes the first network node 12-1 sending early forwarded data to the third network node 12-3, the early forwarded data including first data associated with the multi-connected DRB terminated at the first network node 12-1 and second data associated with the multi-connected DRB terminated at the second network node 12-2, the second data being received at the first network node 12-2 via early forwarding by the second network node 12-2 to the first network node 12-1.

[0169] Furthermore, in at least one embodiment, the method 1100 includes, in response to the first network node 12-1 receiving an indication from the third network node 12-3 that the handover of the wireless device 14 is successful, the first radio network node 12-1 sending a release request to the second network node 12-2 requesting release of the multi-connected DRB terminated at the second network node 12-2.

[0170] In one or more embodiments, the method 1100 further includes: in response to the message sent by the first network node 12-1 to initiate early data forwarding, the first network node 12-1 receiving an early forwarding transfer message from the second network node 12-2. The early forwarding transfer message indicates a DRB subject to early data forwarding at the second network node 12-2.

[0171] Figure 12 Another embodiment is shown comprising a method 1200 performed by a first network node 12-1 acting as an S-MN in a multi-connectivity arrangement including a second network node 12-2 acting as an S-SN in the multi-connectivity arrangement, and wherein a third network node 12-3 is a target for CHO of a wireless device 14 served over the multi-connectivity.

[0172] Method 1200 includes: a first network node 12-1 determines (block 1202) to configure the wireless device 14 with a conditional reconfiguration (e.g., a CHO configuration) and sends (block 1204) a handover request to a third network node 12-3, the request indicating CHO. The first network node 12-1 receives (block 1206) a handover confirmation from the third network node 12-3 and, in response, sends (block 1208) information to the second network node 12-2 enabling the second network node 12-2 to initiate early data forwarding. For example, the information sent is a message including a forwarding address associated with early data forwarding. In a specific example, the message is an Xn-U address indication message that includes an indication indicating CHO and / or that early forwarding is required.

[0173] Figure 13 Another embodiment is shown, including a method 1300 performed by a second network node 12-2 of a wireless communication network 10. The method 1300 includes receiving (block 1302) a message from a first network node 12-1 for initiating early data forwarding from the second network node 12-2 to the first network node 12-1 for data associated with a wireless device 14, the wireless device 14 having multiple connections with the first network node 12-1 and the second network node 12-2. In response to the message, the second network node 12-2 initiates (block 1304) early data forwarding to the first network node 12-1. The message includes an indication of a CHO, e.g., such that the initiation of the early data forwarding by the second network node 12-2 is responsive to an indication of a conditional handover.

[0174] In at least one embodiment, for multi-connectivity, second network node 12-2 operates as an S-SN and first network node 12-1 operates as an S-MN. Early data forwarding is applicable to one or more DRBs used in the multi-connectivity and terminated at second network node 12-2. The multi-connectivity is, for example, MR-DC supported by first network node 12-1 and second network node 12-2.

[0175] Initiating (block 1304) early data forwarding includes, for example, sending an early forwarding transfer message to the first network node 12-1.The early forwarding transfer message indicates a DRB at the second network node 12-2 that is subject to early data forwarding.

[0176] The method 1300 may further include the second network node 12-2 receiving a release request from the first network node 12-1 after initiating the early data forwarding. In response to the release request, the second network node 12-2 terminates the early data forwarding and initiates release of the DRB terminated at the second network node 12-2 for the multi-connection.

[0177] Figure 14 Another embodiment is shown comprising a method 1400 performed by a second network node 12-2 acting as an S-MN in a multi-connectivity arrangement, the multi-connectivity arrangement comprising the second network node 12-2 acting as an S-MN in the multi-connectivity arrangement, and wherein the third network node 12-3 is a target for CHO of a wireless device 14 served over the multi-connectivity.

[0178] Method 1400 includes: a second network node 12-2 receiving (block 1402) information from a first network node 12-1 for initiating early data forwarding from the second network node 12-2 to the first network node 12-1. Here, early data forwarding refers to data associated with one or more bearers terminated at the second network node 12-2 for multiple connections, and the data may include downlink data and / or uplink data associated with a wireless device 14 served by the multiple connections. In at least one example, the data is downlink data that is pending for the wireless device 14 or has not been acknowledged by the wireless device 14.

[0179] The method 1400 further includes the second network node 12-2 sending (block 1404) an early data forwarding indication to the first network node 12-1. This sending may include details, such as the bearers involved in the early data forwarding. The method 1400 continues with the second network node 12-2 sending (block 1406) early data to the first network node 12-1. This sending may be an ongoing or continuous operation, at least until further signaling from the first network node 12-1 indicates termination of the early data forwarding.

[0180] In the broad view of the technology disclosed herein, it will be understood that some embodiments relate to methods of operation and other embodiments include corresponding apparatus. The embodiments herein include, for example, a wireless device (UE) configured to perform any steps of any embodiment described above for the wireless device 14.

[0181] Embodiments also include a wireless device comprising a processing circuit and a power supply circuit. The processing circuit is configured to perform any of the steps of any of the embodiments described above for the wireless device 14. The power supply circuit is configured to supply power to the wireless device.

[0182] Embodiments also include a wireless device comprising a processing circuit configured to perform any of the steps of any of the embodiments described above for the wireless device 14. In some embodiments, the wireless device further comprises a communication circuit.

[0183] The embodiment also includes a wireless device comprising a processing circuit and a memory. The memory contains instructions executable by the processing circuit, whereby the wireless device is configured to perform any of the steps of any of the embodiments described above with respect to the wireless device 14.

[0184] In addition, embodiments include user equipment (UE). The UE includes an antenna configured to send and receive wireless signals. The UE also includes a radio front-end circuit connected to the antenna and the processing circuit and configured to condition the signal transmitted between the antenna and the processing circuit. The processing circuit is configured to perform any steps of any embodiment described above for the wireless device 14. In some embodiments, the UE also includes an input interface connected to the processing circuit and configured to allow information to be input into the UE for processing by the processing circuit. The UE may include an output interface connected to the processing circuit and configured to output information processed by the processing circuit from the UE. The UE may also include a battery connected to the processing circuit and configured to power the UE.

[0185] The embodiments herein also include one or more network nodes configured to perform any of the method embodiments described above for the corresponding network nodes 12-1, 12-2, or 12-3. In one or more corresponding apparatus embodiments, the network node is a radio network node, such as a gNB in ​​a radio access network based on the 5G NR specification, or an ng-eNB configured for communication coupling to a fifth generation core (5GC) network.

[0186] The embodiment also includes a network node comprising a processing circuit and a power supply circuit. The processing circuit is configured to perform any of the steps of any of the embodiments described above for the network node 12-1, 12-2 or 12-3. The power supply circuit is configured to supply power to the radio network node.

[0187] Embodiments also include a network node that includes processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for network nodes 12-1, 12-2, or 12-3. In some embodiments, the network node also includes communication circuitry, such as communication circuitry for exchanging messages or other signaling with other network nodes of the same or different types and / or communication circuitry for providing an air interface including DL signal transmission and UL signal reception, for providing communication services to each wireless device 14. In at least one embodiment, the network nodes 12-1 and 12-2 support multiple connections, such as MR-DC, in which a wireless device 14 is served by two or more connections provided by the network node 12 participating in the multiple connections.

[0188] The embodiment also includes a network node comprising a processing circuit and a memory. The memory contains instructions executable by the processing circuit, whereby the network node is configured to perform any of the steps of any of the embodiments described above for any of the network nodes 12.

[0189] More specifically, the apparatus described above can perform the methods and any other processes described herein by implementing any functional devices, modules, units, or circuits. For example, in one embodiment, the apparatus includes corresponding circuits or circuits configured to perform the steps shown in the method figures. In this regard, the circuit or circuit system can include circuits dedicated to performing certain functional processes and / or one or more microprocessors in combination with memory. For example, the circuit can include one or more microprocessors or microcontrollers and other digital hardware, which can include digital signal processors (DSPs), dedicated digital logic, etc. The processing circuit can be configured to execute program code stored in a memory, which can include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. In several embodiments, the program code stored in the memory can include program instructions for executing one or more telecommunications and / or data communication protocols, as well as instructions for executing one or more techniques described herein. In embodiments employing memory, the memory stores program code that, when executed by one or more processors, performs the techniques described herein.

[0190] Those skilled in the art will also understand that the embodiments herein also include corresponding computer programs.

[0191] The computer program includes instructions that, when executed on at least one processor of a device, cause the device to perform any of the above-mentioned corresponding processes. In this regard, the computer program may include one or more code modules corresponding to the above-mentioned devices or units.

[0192] The embodiment also includes a carrier embodying such a computer program. The carrier may include one of an electric signal, an optical signal, a radio signal or a computer-readable storage medium.

[0193] In this regard, the embodiments herein also include a computer program product stored on a non-transitory computer-readable (storage or recording) medium, and the computer program product includes instructions that, when executed by a processor of a device, cause the device to perform as described above.

[0194] The embodiment also includes a computer program product, which includes a program code portion, and when the computer program product is executed by a computing device, the program code portion performs the steps of any embodiment herein. The computer program product can be stored on a computer readable recording medium.

[0195] Additional embodiments will now be described.For illustrative purposes, at least some of these embodiments may be described as applicable to certain contexts and / or wireless network types, but these embodiments are equally applicable to other contexts and / or wireless network types not explicitly described.

[0196] While the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein relate to wireless networks (e.g., Figure 15 For simplicity, Figure 15 The wireless network shown in FIG. 1 depicts only network QQ 106, network nodes QQ 160 and QQ 160b, and WDs QQ 110, QQ 110b, and QQ 110c. In practice, a wireless network may also include any additional components suitable for supporting communications between wireless devices or between a wireless device and another communication device (e.g., a landline phone, a service provider, or any other network node or terminal device). Of the components shown, network node QQ 160 and wireless device (WD) QQ 110 are depicted in additional detail. A wireless network may provide communication and other types of services to one or more wireless devices, facilitating the wireless devices to access and / or use services provided by or via the wireless network.

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

[0198] Network QQ106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0199] The network node QQ 160 and the WD QQ 110 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 various embodiments, a 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 or systems that can facilitate or participate in the communication of data and / or signals (whether via a wired connection or a wireless connection).

[0200] As used herein, a network node refers to a device that is capable of, configured, arranged, and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless device 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), base stations (BSs) (e.g., radio base stations, Node Bs (NodeBs), evolved NodeBs (eNBs), and NR NodeBs (gNBs)). Base stations can be classified based on the amount of coverage they provide (or in other words, based on their transmit power levels), and they can also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay host node that controls a relay.

[0201] A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU) (sometimes referred to as a remote radio head (RRH)). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Further examples of network nodes include a multi-standard radio (MSR) device (such as an MSR BS), a network controller (such as a radio network controller (RNC) or a base station controller (BSC)), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an MDT.

[0202] As another example, a network node may be a virtual network node, as described in more detail below. However, more generally, a network node may represent any suitable device (or group of devices) that is capable of, configured, arranged, and / or operable to enable and / or provide wireless devices with access to a wireless network, or to provide certain services to wireless devices that have accessed a wireless network.

[0203] According to certain embodiments, Figure 15 It can be understood as Figure 1 Thus, wireless device QQ 110 may be a specific embodiment of wireless device 14 described earlier herein, and network node QQ 160 may be a specific embodiment of any of network nodes 12-1, 12-2, or 12-3 described earlier herein.

[0204] exist Figure 15 In FIG, the network node QQ160 includes a processing circuit QQ170, a device readable medium QQ180, an interface QQ190, an auxiliary device QQ184, a power supply QQ186, a power supply circuit QQ187, and an antenna QQ162. Figure 15 The network node QQ160 shown in the example wireless network of FIG can represent a device that includes a combination of the hardware components shown, but other embodiments can include network nodes with different combinations of components. It should be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. In addition, although the components of the network node QQ160 are depicted as a single box within a larger box or nested within multiple boxes, in reality, the network node may include multiple different physical components that make up a single illustrated component (for example, the device readable medium QQ180 may include multiple separate hard drives and multiple RAM modules).

[0205] Similarly, network node QQ160 may be comprised of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own corresponding components. In certain scenarios where network node QQ160 includes multiple separate components (e.g., BTS and BSC components), one or more of these separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may be considered a single, separate network node in some instances. In some embodiments, network node QQ160 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be replicated (e.g., separate device-readable media QQ180 for different RATs), and some components may be reused (e.g., the same antenna QQ162 may be shared by all RATs). Network node QQ160 may also include multiple sets of the various components shown for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, or Bluetooth wireless technologies) integrated into network node QQ160. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node QQ 160 .

[0206] The processing circuitry QQ 170 is configured to perform any determinations, calculations, or similar operations (e.g., certain obtaining operations) described herein as being provided by the network node. These operations performed by the processing circuitry QQ 170 may include processing information obtained by the processing circuitry QQ 170 by, for example, converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information and making a determination based on the results of the processing.

[0207] The processing circuit QQ 170 may include one or more combinations of the following: a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic, operable to provide network node QQ 160 functionality, either alone or in combination with other network node QQ 160 components (e.g., device-readable medium QQ 180). For example, the processing circuit QQ 170 may execute instructions stored in the device-readable medium QQ 180 or in memory within the processing circuit QQ 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuit QQ 170 may include a system-on-chip (SOC).

[0208] In some embodiments, processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174. In some embodiments, radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 may reside on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, some or all of RF transceiver circuitry QQ172 and baseband processing circuitry QQ174 may reside on the same chip, chipset, board, or unit.

[0209] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by processing circuit QQ170 executing instructions stored on device-readable medium QQ180 or memory within processing circuit QQ170. In alternative embodiments, some or all of the functionality may be provided by processing circuit QQ170, for example, in a hardwired manner, without executing instructions stored on a separate or discrete device-readable medium. In any of these embodiments, processing circuit QQ170 may be configured to perform the described functionality regardless of whether or not it executes instructions stored on a device-readable storage medium. The benefits provided by such functionality are not limited to processing circuit QQ170 or other components of network node QQ160, but are enjoyed by network node QQ160 as a whole and / or by end users and the wireless network as a whole.

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

[0211] Interface QQ190 is used for wired or wireless communication of signaling and / or data between network node QQ160, network QQ106, and / or WD QQ110. As shown, interface QQ190 includes port / terminal QQ194 for sending and receiving data to and from network QQ106, for example, via a wired connection. Interface QQ190 also includes radio front-end circuitry QQ192, which may be coupled to antenna QQ162 or, in some embodiments, be part of antenna QQ162. Radio front-end circuitry QQ192 includes filter QQ198 and amplifier QQ196. Radio front-end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170. Radio front-end circuitry QQ192 may receive digital data, which is then transmitted to other network nodes or WDs via a wireless connection. The radio front-end circuit QQ192 can use a combination of filters QQ198 and / or amplifiers QQ196 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 can collect the radio signal, which is then converted into digital data by the radio front-end circuit QQ192. The digital data can be passed to processing circuit QQ170. In other embodiments, the interface may include different components and / or different combinations of components.

[0212] In certain alternative embodiments, network node QQ160 may not include a separate radio front-end circuit QQ192. Instead, processing circuit QQ170 may include the radio front-end circuit and be connected to antenna QQ162 without the need for a separate radio front-end circuit QQ192. Similarly, in some embodiments, all or some of the RF transceiver circuit QQ172 may be considered part of interface QQ190. In other embodiments, interface QQ190 may include one or more ports or terminals QQ194, radio front-end circuit QQ192, and RF transceiver circuit QQ172 (as part of a radio unit (not shown)), and interface QQ190 may communicate with baseband processing circuit QQ174 (as part of a digital unit (not shown)).

[0213] Antenna QQ162 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna QQ162 may be coupled to radio front-end circuitry QQ190 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna QQ162 may include one or more omnidirectional, sectored, or flat panel antennas operable to transmit and receive radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas can be used to transmit and receive radio signals in any direction, sectored antennas can be used to transmit and receive radio signals to and from devices within a specific area, and flat panel antennas may be line-of-sight antennas for transmitting and receiving radio signals in a relatively straight line. In some cases, using more than one antenna may be referred to as MIMO. In some embodiments, antenna QQ162 may be separate from network node QQ160 and may be connected to network node QQ160 via an interface or port.

[0214] Antenna QQ162, interface QQ190, and / or processing circuitry QQ170 may be configured to perform any receive operations and / or certain obtain operations described herein as being performed by a network node. Any information, data, and / or signals may be received from a wireless device, another network node, and / or any other network device. Similarly, antenna QQ162, interface QQ190, and / or processing circuitry QQ170 may be configured to perform any transmit operations described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to a wireless device, another network node, and / or any other network device.

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

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

[0217] As used herein, a wireless device (WD) refers to a device that is capable of, configured to, arranged to, and / or operable to communicate wirelessly with a network node and / or other wireless devices. Unless otherwise specified, the term WD may be used interchangeably with user equipment (UE) in this article. Wireless transmission may include using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information through the air to send and / or receive wireless signals. In some embodiments, a WD may be configured to send 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 a 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, portable computers, portable embedded devices (LEEs), portable installation devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicle-mounted wireless terminal devices, and the like. A WD may, 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 the 3GPP standard for sidelink communication, and in this case may be referred to as a D2D communication device. As another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another WD and / or network node. In this case, the WD may be a machine-to-machine (M2M) device, which in the 3GPP context may be referred to as an MTC device. As a specific example, a WD may 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., electricity meters), industrial machines, or household or personal devices (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other device that is capable of monitoring and / or reporting its operating status or other functions associated with its operation. As described above, WD may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. In addition, as described above, WD may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

[0218] As shown, wireless device QQ 110 includes antenna QQ 111, interface QQ 114, processing circuitry QQ 120, device-readable medium QQ 130, user interface device QQ 132, auxiliary device QQ 134, power supply QQ 136, and power supply circuitry QQ 137. WD QQ 110 may include multiple groups of one or more of the components shown for different wireless technologies supported by WD QQ 110 (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, WiMAX, NB-IoT, or Bluetooth wireless technologies, to name a few). These wireless technologies may be integrated into the same or different chips or chipsets as the other components within WD QQ 110.

[0219] Antenna QQ111 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals and is connected to interface QQ114. In certain alternative embodiments, antenna QQ111 may be separate from WD QQ110 and may be connected to WD QQ110 via an interface or port. Antenna QQ111, interface QQ114, and / or processing circuit QQ120 may be configured to perform any receive or transmit operation described herein as being performed by a WD. Any information, data, and / or signal may be received from a network node and / or another WD. In some embodiments, the radio front-end circuit and / or antenna QQ111 may be considered an interface.

[0220] As shown, interface QQ114 includes radio front-end circuitry QQ112 and antenna QQ111. Radio front-end circuitry QQ112 includes one or more filters QQ118 and amplifier QQ116. Radio front-end circuitry QQ114 is connected to antenna QQ111 and processing circuitry QQ120 and is configured to condition signals transmitted between antenna QQ111 and processing circuitry QQ120. Radio front-end circuitry QQ112 may be coupled to antenna QQ111 or be part of antenna QQ111. In certain alternative embodiments, WD QQ110 may not include a separate radio front-end circuitry QQ112; instead, processing circuitry QQ120 may include radio front-end circuitry and be connected to antenna QQ111. Similarly, in some embodiments, some or all of RF transceiver circuitry QQ122 may be considered part of interface QQ114. Radio front-end circuitry QQ112 may receive digital data, which is then transmitted over a wireless connection to other network nodes or WDs. The radio front-end circuit QQ112 can use a combination of filters QQ118 and / or amplifiers QQ116 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be transmitted via antenna QQ112. Similarly, when receiving data, antenna QQ111 can collect the radio signal, which is then converted into digital data by the radio front-end circuit QQ112. The digital data can be passed to processing circuit QQ120. In other embodiments, the interface may include different components and / or different combinations of components.

[0221] The processing circuit QQ120 may include one or more combinations of the following: a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic, which is operable to provide WD QQ110 functionality alone or in combination with other WD QQ110 components (e.g., device readable medium QQ130). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit QQ120 may execute instructions stored in the device readable medium QQ130 or in memory within the processing circuit QQ120 to provide the functionality disclosed herein.

[0222] As shown, processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126. In other embodiments, the processing circuitry may include different components and / or different combinations of components. In some embodiments, processing circuitry 120 of WD QQ110 may include a system-on-chip (SoC). In some embodiments, RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be implemented on separate chips or chipsets. In alternative embodiments, part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into a single chip or chipset, while RF transceiver circuitry QQ122 may be implemented on a separate chip or chipset. In yet another alternative embodiment, part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be implemented on the same chip or chipset, while application processing circuitry QQ126 may be implemented on a separate chip or chipset. In other alternative embodiments, part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or chipset. In some embodiments, RF transceiver circuitry QQ122 may be part of interface QQ114. RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.

[0223] In certain embodiments, some or all of the functionality described herein as being performed by the WD may be provided by processing circuit QQ120 executing instructions stored on a device-readable medium QQ130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuit QQ120, for example, in a hardwired manner, without executing instructions stored on a separate or discrete device-readable storage medium. In any of these specific embodiments, processing circuit QQ120 may be configured to perform the described functionality regardless of whether or not instructions are executed on a device-readable storage medium. The benefits provided by such functionality are not limited to processing circuit QQ120 or to other components of WD QQ110, but are enjoyed by WD QQ110 as a whole and / or by the end user and the wireless network as a whole.

[0224] Processing circuitry QQ 120 may be configured to perform any determinations, calculations, or similar operations described herein as being performed by the WD (e.g., certain obtaining operations). These operations performed by processing circuitry QQ 120 may include processing information obtained by processing circuitry QQ 120 by, for example, converting the obtained information into other information, comparing the obtained information or the converted information with information stored by WD QQ 110, and / or performing one or more operations based on the obtained information or the converted information and making determinations based on the results of the processing.

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

[0226] User interface device QQ132 may provide components that allow a human user to interact with WD QQ110. This interaction may take various forms, such as visual, auditory, tactile, and the like. User interface device QQ132 is operable to generate output to the user and allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface device QQ132 installed in WD QQ110. For example, if WD QQ110 is a smartphone, interaction may occur via a touch screen; if WD QQ110 is a smart meter, interaction may occur through a screen that displays usage (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). User interface device QQ132 may include input interfaces, devices, and circuitry, as well as output interfaces, devices, and circuitry. User interface device QQ132 is configured to allow information to be input into WD QQ110 and is connected to processing circuit QQ120 to allow processing circuit QQ120 to process the input information. The user interface device QQ132 may include, for example, a microphone, proximity or other sensors, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. The user interface device QQ132 is also configured to allow information to be output from the WD QQ110 and to allow the processing circuitry QQ120 to output information from the WD QQ110. The user interface device QQ132 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone jack, or other output circuitry. By using one or more input and output interfaces, devices, and circuitry of the user interface device QQ132, the WD QQ110 may communicate with an end user and / or wireless network and allow them to benefit from the functionality described herein.

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

[0228] In some embodiments, power source QQ136 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., an electrical outlet), a photovoltaic device, or a battery cell. WD QQ110 may also include power circuitry QQ137 for delivering power from power source QQ136 to various components of WD QQ110 that require power from power source QQ136 to perform any of the functions described or indicated herein. In some embodiments, power circuitry QQ137 may include power management circuitry. Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in this case, WD QQ110 may be connected to the external power source (e.g., an electrical outlet) via input circuitry or an interface such as a power cable. In some embodiments, power circuitry QQ137 may also be operable to deliver power from the external power source to power source QQ136. This may be used, for example, to charge power source QQ136. Power circuitry QQ137 may perform any formatting, conversion, or other modifications to the power from power source QQ136 to make it suitable for the various components of WD QQ110 being powered.

[0229] Figure 16 One embodiment of a UE according to various aspects described herein is shown. As used herein, a "user equipment" or "UE" may not necessarily have a "user" in the sense of a human user who owns and / or operates the associated equipment. Alternatively, a UE may represent a device that is intended to be sold to or operated by a human user but may not be, or may not initially be, associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended 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 meter). The UE QQ2200 may be any UE identified by the Third Generation Partnership Project (3GPP), including an NB-IoT UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Figure 16 As shown, UE QQ200 is an example of a WD configured for communication according to one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE and / or 5G standards. As previously mentioned, the terms WD and UE may be used interchangeably. Therefore, although Figure 16 It is UE, but the components discussed in this article are also applicable to WD and vice versa.

[0230] exist Figure 16In the embodiment, UE QQ200 includes a processing circuit QQ201, which is operatively coupled to an input / output interface QQ205, a radio frequency (RF) interface QQ209, a network connection interface QQ211, a memory QQ215 including a random access memory (RAM) QQ217, a read-only memory (ROM) QQ219, and a storage medium QQ221, a communication subsystem QQ231, a power supply QQ233, and / or any other components, or any combination thereof. The storage medium QQ221 includes an operating system QQ223, an application QQ225, and data QQ227. In other embodiments, the storage medium QQ221 may include other similar types of information. Some UEs may use Figure 16 All of the components shown in the , or only a subset of these components may be used. The level of integration between components may vary from one UE to another. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0231] exist Figure 16 In the embodiment of the present invention, processing circuit QQ201 can be configured to process computer instructions and data. Processing circuit QQ201 can be configured to implement any sequential state machine that is operable to execute machine instructions stored as a machine-readable computer program in memory, such as: one or more hardware-implemented state machines (e.g., implemented in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) together with suitable software; or any combination thereof. For example, processing circuit QQ201 may include two central processing units (CPUs). The data may be information in a form suitable for use by a computer.

[0232] In the depicted embodiment, the input / output interface QQ205 can be configured to provide a communication interface to an input device, an output device, or both an input and an output device. The UE QQ200 can be configured to use an output device via the input / output interface QQ205. The output device can use the same type of interface port as the input device. For example, a USB port can be used to provide input to and output from the UE QQ200. The output device can be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE QQ200 can be configured to use an input device via the input / output interface QQ205 to allow a user to capture information into the UE QQ200. The input device can include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a touchpad, a scroll wheel, a smart card, etc. The presence-sensitive display can include a capacitive or resistive touch sensor to sense input from the user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0233] exist Figure 16 In the embodiment of the present invention, the RF interface QQ209 can be configured to provide a communication interface to RF components such as transmitters, receivers, and antennas. The network connection interface QQ211 can be configured to provide a communication interface to the network QQ243a. The network QQ243a can include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network QQ243a can include a Wi-Fi network. The network connection interface QQ211 can be configured to include a receiver and a transmitter interface, which are used to communicate with one or more other devices via a communication network according to one or more communication protocols (e.g., Ethernet, TCP / IP, SONET, ATM, etc.). The network connection interface QQ211 can implement receiver and transmitter functions suitable for a communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software, or firmware, or alternatively can be implemented separately.

[0234] RAM QQ217 can be configured to interface with processing circuit QQ201 via bus QQ202 to provide storage or caching of data or computer instructions during the execution of software programs such as an operating system, application programs, and device drivers. ROM QQ219 can be configured to provide computer instructions or data to processing circuit QQ201. For example, ROM QQ219 can be configured to store unchanged low-level system code or data for basic system functions stored in non-volatile memory, such as basic input and output (I / O), startup, or receiving keystrokes from a keyboard. Storage medium QQ221 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), magnetic disk, optical disk, floppy disk, hard disk, removable tape cartridge, or flash drive. In one example, storage medium QQ221 can be configured to include an operating system QQ223, an application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data files QQ227. The storage medium QQ 221 may store any one or a combination of various operating systems for use by the UE QQ 200 .

[0235] The storage medium QQ221 can be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory such as a subscriber identity module or a removable user identity (SIM / RUIM) module, other memory, or any combination thereof. The storage medium QQ221 can allow the UEQQ200 to access computer-executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to download or upload data. An article of manufacture, such as an article utilizing a communication system, can be tangibly embodied in the storage medium QQ221, which can include device-readable media.

[0236] exist Figure 16In the embodiment, processing circuit QQ201 can be configured to communicate with network QQ243b using communication subsystem QQ231. Network QQ243a and network QQ243b can be one or more identical networks or one or more different networks. Communication subsystem QQ231 can be configured to include one or more transceivers for communicating with network QQ243b. For example, communication subsystem QQ231 can be configured to include one or more transceivers for communicating with another device (e.g., another WD, UE) capable of wireless communication or one or more remote transceivers of a base station of a radio access network (RAN) according to one or more communication protocols (e.g., IEEE 802.11b, CDMA, WCDMA, GSM, LTE, UTRAN, WiMAX, etc.). Each transceiver can include a transmitter QQ233 and / or a receiver QQ235 to respectively implement transmitter or receiver functions suitable for a RAN link (e.g., frequency allocation, etc.). In addition, the transmitter QQ233 and receiver QQ235 of each transceiver can share circuit components, software, or firmware, or alternatively can be implemented separately.

[0237] In the illustrated embodiment, the communication functions of the communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication (such as use of a global positioning system (GPS) for determining location), another similar communication function, or any combination thereof. For example, the communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network QQ243b may include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network QQ243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE QQ200.

[0238] The features, benefits, and / or functionality described herein may be implemented in one of the components of UE QQ200, or divided among multiple components of UE QQ200. Furthermore, the features, benefits, and / or functionality described herein may be implemented in any combination of hardware, software, or firmware. In one example, the communication subsystem QQ231 may be configured to include any of the components described herein. Furthermore, the processing circuit QQ201 may be configured to communicate with any such component via bus QQ202. In another example, any such component may be represented by program instructions stored in memory that, when executed by the processing circuit QQ201, perform the corresponding functions described herein. In another example, the functionality of any such component may be divided between the processing circuit QQ201 and the communication subsystem QQ231. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, while the computationally intensive functions may be implemented in hardware.

[0239] Figure 17 is a schematic block diagram illustrating a virtualization environment QQ300 in which the functions implemented by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device, which may include virtualized hardware platforms, storage devices, and network resources. As used herein, virtualization may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or a component thereof, and relates to an implementation in which at least a portion of the functions are implemented as one or more virtual components (e.g., by one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0240] 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 QQ 300 hosted by one or more hardware nodes QQ 330. Furthermore, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), the network nodes may be fully virtualized at this point.

[0241] These functions may be implemented by one or more applications QQ320 (which may alternatively be referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.), which are operable to implement some of the features, functions, and / or benefits of some embodiments disclosed herein. Applications QQ320 run in a virtualized environment QQ300, which provides hardware QQ330 including processing circuitry QQ360 and memory QQ390. Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360, thereby allowing applications QQ320 to operate to provide one or more of the features, benefits, and / or functions disclosed herein.

[0242] The virtualization environment QQ300 includes a general-purpose or specialized network hardware device QQ330, which includes a set of one or more processors or processing circuits QQ360, which can be commercial off-the-shelf (COTS) processors, application-specific integrated circuits (ASICs), or any other type of processing circuit including digital or analog hardware components or specialized processors. Each hardware device can include memory QQ390-1, which can be non-persistent storage for temporarily storing instructions QQ395 or software executed by the processing circuits QQ360. Each hardware device can include one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interfaces QQ380. Each hardware device can also include a non-transitory, permanent machine-readable storage medium QQ390-2 having stored therein software QQ395 and / or instructions executable by the processing circuits QQ360. The software QQ395 can include any type of software, including software for instantiating one or more virtualization layers QQ350 (also known as hypervisors), software for executing virtual machines QQ340, and software that enables them to perform the functions, features, and / or benefits described in connection with some embodiments described herein.

[0243] Virtual machine QQ 340 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be run by a corresponding virtualization layer QQ 350 or hypervisor. Different embodiments of instances of virtual device QQ 320 can be implemented on one or more of virtual machines QQ 340, and the implementation can be done in different ways.

[0244] During operation, processing circuit QQ 360 executes software QQ 395 to instantiate a hypervisor or virtualization layer QQ 350 , which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ 350 may present a virtual operating platform that appears to virtual machine QQ 340 as networked hardware.

[0245] like Figure 17As shown, hardware QQ 330 can be a standalone network node with general or specific components. Hardware QQ 330 can include antenna QQ 3225 and can implement some functions through virtualization. Alternatively, hardware QQ 330 can 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) QQ 3100, which oversees the lifecycle management of application QQ 320, etc.

[0246] In some contexts, hardware virtualization is referred to as network function 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 be located in data centers and customer premises equipment.

[0247] In the context of NFV, a virtual machine QQ 340 can be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtualized machine. Each virtual machine QQ 340 and the portion of hardware QQ 330 that executes the virtual machine (which can be hardware dedicated to the virtual machine and / or hardware shared by the virtual machine and other virtual machines in virtual machine QQ 340) form a separate virtual network element (VNE).

[0248] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions running in one or more virtual machines QQ340 on top of the hardware network infrastructure QQ330 and corresponds to Figure 17 Application QQ320.

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

[0250] In some embodiments, some signaling may be implemented using a control system QQ3230 , which may alternatively be used for communication between the hardware node QQ330 and the radio unit QQ3200 .

[0251] Figure 18 A telecommunications network connected to a host computer via an intermediate network according to some embodiments is shown. Figure 18According to an embodiment, a communications system includes a telecommunications network QQ410 (e.g., a 3GPP-type cellular network), which includes an access network QQ411 (e.g., a radio access network) and a core network QQ414. Access network QQ411 includes a plurality of base stations QQ412a, QQ412b, and QQ412c (e.g., NBs, eNBs, gNBs, or other types of wireless access points), each of which defines a corresponding coverage area QQ413a, QQ413b, and QQ413c. Each base station QQ412a, QQ412b, and QQ412c is connectable to the core network QQ414 via a wired or wireless connection QQ415. A first UE QQ491 located in coverage area QQ413c is configured to wirelessly connect to or be paged by the corresponding base station QQ412c. A second UE QQ492 located in coverage area QQ413a is also wirelessly connectable to the corresponding base station QQ412a. Although multiple UEs QQ491 , QQ492 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or only one UE is connected to the corresponding base station QQ412 .

[0252] Telecommunications network QQ410 itself is connected to a host computer QQ430, which can be implemented as 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 QQ430 can be owned or controlled by a service provider, or can be operated by or on behalf of the service provider. Connections QQ421 and QQ422 between telecommunications network QQ410 and host computer QQ430 can extend directly from core network QQ414 to host computer QQ430, or can be made via an optional intermediate network QQ420. Intermediate network QQ420 can be one or a combination of public, private, or carrier networks; if present, intermediate network QQ420 can be a backbone network or the Internet; specifically, intermediate network QQ420 can include two or more subnetworks (not shown).

[0253] Figure 18The communication system as a whole implements a connection between connected UEs QQ491 and QQ492 and a host computer QQ430. This connection can be described as an over-the-top (OTT) connection QQ450. The host computer QQ430 and the connected UEs QQ491 and QQ492 are configured to communicate data and / or signaling via the OTT connection QQ450, using the access network QQ411, the core network QQ414, any intermediate networks QQ420, and possibly other infrastructure (not shown) as intermediaries. The OTT connection QQ450 can be transparent, in the sense that the participating communication devices through which the OTT connection QQ450 passes are unaware of the routing of uplink and downlink communications. For example, the base station QQ412 may not be informed, or may not need to be informed, of the past routing of incoming downlink communications containing data originating from the host computer QQ430 to be forwarded (e.g., handed over) to the connected UE QQ491. Similarly, base station QQ412 need not be aware of the future routing of outgoing uplink communications originating from UE QQ491 to host computer QQ430.

[0254] Now refer to Figure 19 hereinafter, we will describe example implementations of the UE, base station, and host computer discussed in the previous paragraphs according to an embodiment. Figure 19 A host computer is shown communicating with a user device via a base station via a partially wireless connection according to some embodiments. In the communication system QQ500, the host computer QQ510 includes hardware QQ515, which includes a communication interface QQ516. The communication interface QQ516 is configured to establish and maintain a wired or wireless connection to the interface of different communication devices of the communication system QQ500. The host computer QQ510 also includes processing circuitry QQ518, which may have storage and / or processing capabilities. Specifically, the processing circuitry QQ518 may include one or more programmable processors, application-specific integrated circuits, field programmable gate arrays, or a combination thereof (not shown) suitable for executing instructions. The host computer QQ510 also includes software QQ511, which is stored in the host computer QQ510 or can be accessed by the host computer QQ510 and can be executed by the processing circuitry QQ518. The software QQ511 includes a host application QQ512. The host application QQ 512 is operable to provide services to a remote user (e.g., UE QQ 530), which is connected via an OTT connection QQ 550 terminated at the UE QQ 530 and the host computer QQ 510. In providing services to the remote user, the host application QQ 512 may provide user data sent using the OTT connection QQ 550.

[0255] The communication system QQ500 also includes a base station QQ520 provided in the telecommunication system, the base station QQ520 including hardware QQ525 that enables it to communicate with the host computer QQ510 and with the UE QQ530. The hardware QQ525 may include: a communication interface QQ526 for establishing and maintaining wired or wireless connections for interfacing with different communication devices of the communication system QQ500; and a radio interface QQ527 for establishing and maintaining connections with at least the communication devices located in the coverage area ( Figure 19 The communication interface QQ526 may be configured to facilitate a connection QQ560 to the host computer QQ510. The connection QQ560 may be direct, or it may pass through the core network ( Figure 19 (not shown) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware QQ525 of base station QQ520 also includes processing circuitry QQ528, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. Base station QQ520 also has software QQ521 stored internally or accessible via an external connection.

[0256] The communication system QQ500 also includes the UE QQ530 already mentioned. Its hardware QQ535 may include a radio interface QQ537 configured to establish and maintain a wireless connection QQ570 with a base station serving the coverage area in which the UE QQ530 is currently located. The hardware QQ535 of the UE QQ530 also includes processing circuitry QQ538, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or a combination thereof (not shown) adapted to execute instructions. The UE QQ530 also includes software QQ531, which is stored in the UE QQ530 or accessible by the UE QQ530 and executable by the processing circuitry QQ538. The software QQ531 includes a client application QQ532. The client application QQ532 is operable to provide services to human or non-human users via the UE QQ530 under the support of the host computer QQ510. In the host computer QQ 510, the executing host application QQ 512 can communicate with the executing client application QQ 532 via an OTT connection QQ 550 terminated at the UE QQ 530 and the host computer QQ 510. When providing services to users, the client application QQ 532 can receive request data from the host application QQ 512 and provide user data in response to the request data. The OTT connection QQ 550 can transmit both the request data and the user data. The client application QQ 532 can interact with the user to generate the user data it provides.

[0257] Notice, Figure 19 The host computer QQ510, base station QQ520 and UE QQ530 shown can be respectively Figure 18 The host computer QQ430, one of the base stations QQ412a, QQ412b, QQ412c and one of the UEs QQ491, QQ492 are similar or identical. That is, the internal workings of these entities can be similar to Figure 19 shown, and independently, the surrounding network topology can be Figure 18 network topology.

[0258] exist Figure 19 In FIG, OTT connection QQ550 has been abstractly drawn to illustrate communication between host computer QQ510 and UE QQ530 via base station QQ520, without explicitly mentioning any intermediate devices and the precise routing of messages via these devices. The network infrastructure can determine this routing, which can be configured to be hidden from UE QQ530, from the service provider operating host computer QQ510, or from both. While OTT connection QQ550 is active, the network infrastructure can also make decisions to dynamically change the routing (e.g., based on load balancing considerations or network reconfiguration).

[0259] The wireless connection QQ570 between the UE QQ530 and the base station QQ520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improves the performance of an OTT service provided to the UE QQ530 using the OTT connection QQ550, wherein the wireless connection QQ570 forms the last leg of the OTT connection QQ550.

[0260] For the purpose of monitoring the data rate, latency and other factors improved by one or more embodiments, a measurement process may be provided. There may also be an optional network function for reconfiguring the OTT connection QQ550 between the host computer QQ510 and the UE QQ530 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection QQ550 may be implemented in the software QQ511 and hardware QQ515 of the host computer QQ510 or in the software QQ531 and hardware QQ535 of the UE QQ530, or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with the communication device through which the OTT connection QQ550 passes; the sensor may participate in the measurement process by providing the values ​​of the monitoring quantities exemplified above or providing the values ​​of other physical quantities that the software QQ511 and QQ531 can use to calculate or estimate the monitoring quantities. Reconfiguration of the OTT connection QQ550 may include message formats, retransmission settings, preferred routing, etc.; this reconfiguration need not affect the base station QQ520 and may be unknown or imperceptible to the base station QQ520. Such processes and functions may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates host computer QQ510 to measure throughput, propagation time, latency, etc. This measurement may be implemented as follows: software QQ511 and QQ531 enable the use of OTT connection QQ550 to send messages (specifically, empty or "dummy" messages) while monitoring propagation time, errors, etc.

[0261] Figure 20 is a flow chart showing 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 a reference Figure 18 and Figure 19 For the sake of simplicity of this disclosure, only the host computer, base station and UE described in this section will be included. Figure 20 In step QQ610, the host computer provides user data. In sub-step QQ611 of step QQ610 (which may be optional), the host computer provides the user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying the user data to the UE. In step QQ630 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step QQ640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0262] Figure 21is a flow chart showing 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 a reference Figure 18 and Figure 19 For the sake of simplicity of this disclosure, only the host computer, base station and UE described in this section will be included. Figure 21 In step QQ710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step QQ720, the host computer initiates a transmission carrying the user data to the UE. In accordance with the teachings of the embodiments described throughout this disclosure, the transmission may be via a base station. In step QQ730 (which may be optional), the UE receives the user data carried in the transmission.

[0263] Figure 22 is a flow chart showing 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 a reference Figure 18 and Figure 19 For the sake of simplicity of this disclosure, only the host computer, base station and UE described in this section will be included. Figure 22 . In step QQ810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In sub-step QQ821 of step QQ820 (which may be optional), the UE provides user data by executing a client application. In sub-step QQ811 of step QQ810 (which may be optional), the UE executes a client application that provides user data in response to the input data provided by the received host computer. When providing user data, the executed client application may also take into account user input received from the user. Regardless of the specific manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in sub-step QQ830 (which may be optional). In step QQ840 of the method, the host computer receives user data sent from the UE in accordance with the teachings of the embodiments described throughout this disclosure.

[0264] Figure 23 is a flow chart showing 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 a reference Figure 18 and Figure 19 For the sake of simplicity of this disclosure, only the host computer, base station and UE described in this section will be included. Figure 23In step QQ910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step QQ920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step QQ930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

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

[0266] Thus, in view of the above, embodiments herein generally include a communication system comprising a host computer. The host computer may include processing circuitry configured to provide user data. The host computer may also include a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE). The cellular network may include a base station having a radio interface and processing circuitry, the processing circuitry of the base station being configured to perform any of the steps of any of the embodiments described above for the base station.

[0267] In some embodiments, the communication system further comprises a base station.

[0268] In some embodiments, the communication system further comprises a UE, wherein the UE is configured to communicate with the base station.

[0269] In some embodiments, the processing circuitry of the host computer is configured to execute a host application, thereby providing user data. In this case, the UE includes processing circuitry configured to execute a client application associated with the host application.

[0270] Embodiments herein also include a method implemented in a communication system including a host computer, a base station, and a user equipment (UE). The method includes providing user data at the host computer. The method may also include initiating, at the host computer, a transmission carrying the user data to the UE via a cellular network including the base station. The base station performs any of the steps of any of the embodiments described above for the base station.

[0271] In some embodiments, the method further includes: at the base station, sending user data.

[0272] In some embodiments, the user data is provided at the host computer by executing a host application. In this case, the method further comprises: at the UE, executing a client application associated with the host application.

[0273] The embodiments herein also include a user equipment (UE), the UE being configured to communicate with a base station. The UE comprises a radio interface and a processing circuit, the processing circuit being configured to execute any of the embodiments described above for the UE.

[0274] Embodiments herein also include a communication system comprising a host computer. The host computer includes processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE). The UE includes a radio interface and processing circuitry. Components of the UE are configured to perform any of the steps of any of the embodiments described above for the UE.

[0275] In some embodiments, the cellular network further includes a base station configured to communicate with the UE.

[0276] In some embodiments, the processing circuitry of the host computer is configured to execute a host application to provide user data. The processing circuitry of the UE is configured to execute a client application associated with the host application.

[0277] Embodiments also include a method implemented in a communication system including a host computer, a base station, and a user equipment (UE). The method includes: providing user data at the host computer; and initiating a transmission carrying the user data to the UE via a cellular network including the base station. The UE performs any of the steps of any of the embodiments described above for the UE.

[0278] In some embodiments, the method further includes: receiving, at the UE, user data from the base station.

[0279] Embodiments herein also include a communication system comprising a host computer. The host computer includes a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station. The UE includes a radio interface and processing circuitry. The processing circuitry of the UE is configured to perform any of the steps of any of the embodiments described above for the UE.

[0280] In some embodiments, the communication system further comprises a UE.

[0281] In some embodiments, the communication system further comprises a base station. In this case, the base station comprises: a radio interface configured to communicate with the UE; and a communication interface configured to forward user data carried in transmissions from the UE to the base station to the host computer.

[0282] In some embodiments, the processing circuitry of the host computer is configured to execute a host application, and the processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing user data.

[0283] In some embodiments, the processing circuitry of the host computer is configured to execute a host application to provide the request data, and the processing circuitry of the UE is configured to execute a client application associated with the host application to provide the user data in response to the request data.

[0284] Embodiments herein also include a method implemented in a communication system including a host computer, a base station, and a user equipment (UE). The method includes: receiving, at the host computer, user data transmitted from the UE to the base station. The UE performs any of the steps of any of the embodiments described above for the UE.

[0285] In some embodiments, the method further includes: at the UE, providing user data to the base station.

[0286] In some embodiments, the method further comprises: executing, at the UE, a client application to provide user data to be transmitted. The method may further comprise: executing, at the host computer, a host application associated with the client application.

[0287] In some embodiments, the method further includes: executing a client application at the UE; and receiving input data for the client application at the UE. The input data is provided at the host computer by executing a host application associated with the client application. The user data to be sent is provided by the client application in response to the input data.

[0288] Embodiments also include a communication system comprising a host computer. The host computer includes a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station. The base station includes a radio interface and processing circuitry. The processing circuitry of the base station is configured to perform any of the steps of any of the embodiments described above for the base station.

[0289] In some embodiments, the communication system further comprises a base station.

[0290] In some embodiments, the communication system further includes a UE, which is configured to communicate with the base station.

[0291] In some embodiments, the processing circuitry of the host computer is configured to execute a host application, and the UE is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0292] Furthermore, an embodiment includes a method implemented in a communication system including a host computer, a base station, and a user equipment (UE). The method includes: at the host computer, receiving user data from the base station, the user data originating from a transmission that the base station has received from the UE. The UE performs any of the steps of any of the embodiments described above for the UE.

[0293] In some embodiments, the method further comprises: receiving, at the base station, user data from the UE.

[0294] In some embodiments, the method further comprises: at the base station, initiating transmission of the received user data to the host computer.

[0295] Generally, unless clearly given and / or different meanings are implied from the context, all terms used in this article will be interpreted according to their ordinary meaning in the relevant technical field. Unless otherwise clearly stated, all references to "one / an / element, equipment, component, device, step, etc." should be openly interpreted as referring to at least one instance in an element, equipment, component, device, step, etc. Unless a step must be clearly described as being after or before another step and / or implicitly a step must be after or before another step, the steps of any method disclosed herein do not have to 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 applicable to any other embodiment, and vice versa. By description, other purposes, features and advantages of the attached embodiments will be apparent.

[0296] The term unit may have a conventional meaning in the field of electronic products, electrical devices 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, output and / or display functions, etc. (such as those described herein).

[0297] As used herein, the term "A and / or B" encompasses embodiments having solely A, solely B, or both A and B. Thus, the term "A and / or B" may equivalently mean "at least one of any one or more of A and B."

[0298] Some embodiments contemplated herein are described more fully with reference to the accompanying drawings. However, other embodiments are within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as being limited to the examples set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0299] It is worth noting that modifications and other embodiments of the disclosed invention will occur to those skilled in the art having benefit of the teachings presented in the foregoing description and the associated drawings. Therefore, it should be understood that the present invention is not limited to the specific embodiments disclosed, and modifications and other embodiments are intended to be included within the scope of the present disclosure. Although specific terms may be used herein, they are used in a general and descriptive sense only and are not intended to be limiting.

Claims

1. A method (1100) performed by a first network node (12-1) of a wireless communication network (10), the method (1100) comprising: sending (1102) a handover request to a third network node (12-3), the handover request including an indication of a conditional handover of a wireless device (14) to the third network node (12-3), wherein the first network node (12-1) and the second network node (12-2) are multi-connected to the wireless device (14); receiving (1104) a handover request confirmation from the third network node (12-3); sending (1106) an Xn-U address indication message including a conditional handover (CHO) indicator to the second network node (12-2) for initiating early data forwarding of data associated with the wireless device (14) from the second network node (12-2) to the first network node (12-1); receiving an early data forwarding indication (6) from the second network node (12-2) in response to sending the Xn-U address indication message; receiving data (7) from the second network node (12-2); Sending (1108) configuration information of the conditional handover (CHO) to the wireless device (14); receiving, after receiving the early data forwarding indication and the data from the second network node (12-2), an indication of a successful handover for the wireless device (14) from the third network node (12-3), wherein the indication of a successful handover is an indication for the wireless device (14) to perform the CHO to the third network node (12-3); and In response to receiving an indication of a successful handover for the wireless device (14) from the third network node (12-3), a release request is sent to the second network node (12-2), requesting the release of the multi-connected data radio bearer (DRB) terminated at the second network node (12-2).

2. The method (1100) of claim 1, wherein: With respect to the multi-connectivity, the first network node (12-1) operates as a source master node S-MN, and the second network node (12-2) operates as a source secondary node S-SN.

3. The method (1100) according to claim 1 or 2, wherein: The early data forwarding is applicable to one or more data radio bearers (DRBs) terminated at the second network node (12-2) and used for the multiple connections.

4. The method (1100) according to any one of claims 1 to 3, wherein: The Xn-U address indication message sent to the second network node (12-2) includes a forwarding address associated with the early data forwarding.

5. The method (1100) according to any one of claims 1 to 4, wherein: The method (1100) further comprises: the first network node (12-1) sending early forwarded data to the third network node (12-3), the early forwarded data comprising first data associated with a data radio bearer (DRB) of the multi-connection terminated at the first network node (12-1), and second data associated with a DRB of the multi-connection terminated at the second network node (12-2), the second data being received at the first network node (12-1) by early forwarding by the second network node (12-2) to the first network node (12-1).

6. The method (1100) according to any one of claims 1 to 5, wherein: The early data forwarding indication (6) is an early forwarding transmission message indicating a data radio bearer (DRB) at the second network node (12-2) that is subject to the early data forwarding.

7. The method (1100) according to any one of claims 1 to 6, wherein: The multi-connectivity is a multi-radio dual connectivity MR-DC supported by the first network node (12-1) and the second network node (12-2).

8. A first network node (12-1) configured to operate in a wireless communication network (10), the first network node (12-1) comprising: a first communication interface circuit (20-1) configured to communicatively couple the first network node (12-1) to one or more other network nodes (12); a second communication interface circuit (20-2) configured to communicatively couple the first network node (12-1) to a wireless device (14); as well as A processing circuit (26-1) operatively associated with the first communication interface circuit (20-1) and the second communication interface circuit (20-2) and configured to: sending a handover request to a third network node (12-3), the handover request including an indication of a conditional handover of the wireless device (14) to the third network node (12-3), wherein the first network node (12-1) and the second network node (12-2) are multi-connected to the wireless device (14); receiving a handover request confirmation from the third network node (12-3); Sending an Xn-U address indication message including a conditional handover (CHO) indicator to the second network node (12-2) to initiate early data forwarding of data associated with the wireless device (14) from the second network node (12-2) to the first network node (12-1); receiving an early data forwarding indication (6) from the second network node (12-2) in response to sending the Xn-U address indication message; receiving data (7) from the second network node (12-2); Sending configuration information of the conditional handover (CHO) to the wireless device (14); receiving, after receiving the early data forwarding indication and the data from the second network node (12-2), an indication of a successful handover for the wireless device (14) from the third network node (12-3), wherein the indication of a successful handover is an indication for the wireless device (14) to perform the CHO to the third network node (12-3); and In response to receiving an indication of a successful handover for the wireless device (14) from the third network node (12-3), a release request is sent to the second network node (12-2), requesting the release of the multi-connected data radio bearer (DRB) terminated at the second network node (12-2).

9. The first network node (12-1) according to claim 8, wherein With respect to the multi-connectivity, the first network node (12-1) operates as a source master node S-MN with respect to the wireless device (14), and the second network node (12-2) operates as a source secondary node S-SN.

10. The first network node (12-1) according to claim 8 or 9, wherein: The early data forwarding is applicable to one or more data radio bearers (DRBs) used in the multi-connectivity and terminated at the second network node (12-2).

11. The first network node (12-1) according to any one of claims 8 to 10, wherein: The Xn-U address indication message sent to the second network node (12-2) includes a forwarding address associated with data forwarding.

12. The first network node (12-1) according to any one of claims 8 to 11, wherein: The processing circuit (26-1) is configured to send early forwarded data to the third network node (12-3), the early forwarded data comprising first data associated with the multi-connected data radio bearer (DRB) terminated at the first network node (12-1), and second data associated with the multi-connected DRB terminated at the second network node (12-2), the second data being received at the first network node (12-1) by early forwarding by the second network node (12-2) to the first network node (12-1).

13. The first network node (12-1) according to any one of claims 8 to 12, wherein: The early data forwarding indication is an early forwarding transmission message indicating a data radio bearer (DRB) at the second network node (12-2) that is subject to early data forwarding by the second network node (12-2) to the first network node (12-1).

14. The first network node (12-1) according to any one of claims 8 to 13, wherein: The multi-connectivity is a multi-radio dual connectivity MR-DC supported by the first network node (12-1) and the second network node (12-2).

15. A method (1300) performed by a second network node (12-2) of a wireless communication network (10), the method (1300) comprising: Receiving (1302) an Xn-U address indication message including a conditional handover (CHO) indicator from a first network node (12-1) for initiating early data forwarding from the second network node (12-2) to the first network node (12-1) for data associated with a wireless device (14), the wireless device (14) being multi-connected to the first network node (12-1) and the second network node (12-2); In response to the Xn-U address indication message including the CHO indicator, initiating (1304) the early data forwarding to the first network node (12-1) by sending an early data forwarding indication and data to the first network node (12-1); as well as A release request is received from the first network node (12-1) after initiating the early data forwarding and, in response, the early data forwarding is terminated and a release of a data radio bearer (DRB) terminated at the second network node (12-2) for the multi-connection is initiated.

16. The method (1300) of claim 15, wherein: With respect to the multi-connectivity, the second network node (12-2) operates as a source secondary node S-SN, and the first network node (12-1) operates as a source master node S-MN.

17. The method (1300) according to claim 15 or 16, wherein: The early data forwarding is applicable to one or more data radio bearers (DRBs) used in the multi-connectivity and terminated at the second network node (12-2).

18. The method (1300) according to any one of claims 15 to 17, wherein: The multi-connectivity is a multi-radio dual connectivity MR-DC supported by the first network node (12-1) and the second network node (12-2).

19. The method (1300) according to any one of claims 15 to 18, wherein: The early data forwarding indication is an early forwarding transmission message, the early forwarding transmission message indicating a data radio bearer (DRB) at the second network node (12-2) that is subject to the early data forwarding.

20. A second network node (12-2) configured to operate in a wireless communication network (10), the second network node (12-2) comprising: a first communication interface circuit (20-1) configured to communicatively couple the second network node (12-2) to one or more other network nodes (12); a second communication interface circuit (20-2) configured to communicatively couple the second network node (12-2) to the wireless device (14); as well as A processing circuit (26-2) operatively associated with the first communication interface circuit (20-1) and the second communication interface circuit (20-2) and configured to: receiving an Xn-U address indication message including a conditional handover (CHO) indicator from a first network node (12-1) for initiating early data forwarding from the second network node (12-2) to the first network node (12-1) for data associated with a wireless device (14), the wireless device (14) being multi-connected to the first network node (12-1) and the second network node (12-2); In response to the Xn-U address indication message including the CHO indicator, initiating the early data forwarding to the first network node (12-1) by sending an early data forwarding indication and data to the first network node (12-1); as well as A release request is received from the first network node (12-1) after initiating the early data forwarding and, in response, the early data forwarding is terminated and a release of a data radio bearer (DRB) terminated at the second network node (12-2) for the multi-connection is initiated.

21. The second network node (12-2) according to claim 20, wherein: With respect to the multi-connectivity, the second network node (12-2) operates as a source secondary node S-SN, and the first network node (12-1) operates as a source master node S-MN.

22. The second network node (12-2) according to claim 20 or 21, wherein: The early data forwarding is applicable to one or more data radio bearers (DRBs) used in the multi-connectivity and terminated at the second network node (12-2).

23. The second network node (12-2) according to any one of claims 20 to 22, wherein: The multi-connectivity is a multi-radio dual connectivity MR-DC supported by the first network node (12-1) and the second network node (12-2).

24. The second network node (12-2) according to any one of claims 20 to 23, wherein: The early data forwarding indication is an early forwarding transmission message, the early forwarding transmission message indicating a data radio bearer (DRB) at the second network node (12-2) that is subject to the early data forwarding.

Images