Lossless path switching with side link relays

By implementing CU-CP to CU-UP instructions for packet buffering during inter-gNB route switching in U2N relay scenarios, the method addresses data loss and buffer overflows, ensuring efficient and lossless packet handling.

JP2026538954APending Publication Date: 2026-11-19TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2026518930
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-09-29
Filing Date
2024-09-26
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

In wireless communication networks, particularly in UE-Network (U2N) relay scenarios, route switching between indirect and direct routes can lead to data loss and service interruptions due to premature packet discarding or excessive buffering during inter-gNB scenarios, as there is a lack of end-to-end feedback mechanisms at the PDCP layer.

Method used

A method involving instructions from the gNB's control plane (CU-CP) to the user plane (CU-UP) via the E1 interface to buffer packets during inter-gNB route switching, ensuring packets are not discarded prematurely and are only forwarded or discarded based on specific conditions, such as timer expiration or PDCP status reports.

Benefits of technology

This approach prevents data loss and buffer overflows by ensuring packets are handled efficiently during route switching, maintaining data integrity and reducing service interruptions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026538954000001_ABST
    Figure 2026538954000001_ABST
Patent Text Reader

Abstract

In response to the triggering of inter-gNB route switching for a remote UE having an indirect connection to gNB(56) via a relay UE, the CU-UP entity(72) of gNB(56) receives instructions from the CU-CP entity(72) of gNB(56). In response to the above instructions, the CU-UP entity(72) buffers packets for the remote UE.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a method for controlling operation of a wireless communication network, as well as a corresponding device, system, and computer program.

Background Art

[0002] In wireless communication networks such as those specified by 3GPP (3rd Generation Partnership Project), it is known to provide a mode of direct wireless communication between user equipments (UEs). For example, such a direct communication mode is supported for 4G (4th Generation) LTE (Long Term Evolution) technology and for 5G (5th Generation) NR (New Radio) technology.

[0003] Sidelink As part of Release 12 (Rel-12), 3GPP specified LTE D2D (device-to-device) technology, also known as Sidelink (SL) or the PC5 interface. Its target use cases (UC) were proximity services (communication and discovery). Support for such services was extended in Rel-13 and in Rel-14, and LTE Sidelink was extensively redesigned to support vehicular communication commonly referred to as V2X ("Vehicle-to-Anything") or V2V (Vehicle-to-Vehicle). In Release 15 (Rel-15), further enhancements were made from the perspective of lower radio layers. LTE SL uses broadcast communication, i.e., transmissions from a UE target any receiver within range.

[0004] In Release 16 (Rel-16), 3GPP introduced sidelinks for 5G NR. The driving use case is vehicle communications with more stringent requirements than those typically served by LTE SL. To meet these stringent requirements, NR SL can implement broadcast, groupcast, and unicast communications. In groupcast communications, the intended receivers of the message are typically a subset of vehicles near the transmitter, while in unicast communications, there is a single intended receiver.

[0005] Both LTE SL and NR SL can operate with and without network coverage, including support for standalone, network-less operation, and with varying degrees of interaction between the UE and the NW (Network).

[0006] In 3GPP Release 17 (Rel-17), public safety was one of the most important use cases where it could benefit from the NR sidelink features already developed in Release 16. Therefore, 3GPP specified extensions relevant to public safety use cases that incorporated NR Rel-16 SL as a baseline. Furthermore, in several scenarios, such as indoor firefighting, forest firefighting, earthquake rescue, and maritime rescue, public safety services must operate with or without partial network coverage when infrastructure is (partially) destroyed or unavailable; therefore, coverage extensions are a critical enabler for public safety for both services communicated between UEs and cellular networks and services communicated between UEs via SL.

[0007] Rel-17 introduced a Research Item Description (SID) for NR Sidelink Relays (see 3GPP document RP-193253) aimed at further exploring coverage enhancements for sidelink-based communications, including both UE-NW relays for cellular coverage enhancements and UE-UE relays for sidelink coverage enhancements. In contrast, the relevant Work Item Description (WID) (see 3GPP document RP-213585, 3GPP conference RAN#94-e) considered only UE-NW relays for Rel-17. In addition to public safety use cases, NR Sidelink Relays WI were designed to support other commercial use cases that would also greatly benefit from coverage enhancements. Two solutions for UE-NW relays were specified: Layer 2 (L2) UE-NW (U2N) relays and Layer 3 (L3) U2N relays.

[0008] As can be seen from 3GPP document R-213585, discussions were initiated in RAN#94 to identify the detailed motivations and work areas for the development of NR SL and NR SL relays in Rel-18. Regarding NR SL relays, support for indirect route-to-indirect route switching should be introduced, and the remaining topics regarding service continuity for L2 relays were agreed upon. Furthermore, the limitation in Rel-17 that service continuity was limited to intra-gNB scenarios was removed in Rel-18. Rel-18 should also introduce support for inter-gNB scenarios of route switching between direct and indirect routes.

[0009] Layer 2 UE - Network Relay 3GPP TR23.752 V17.0.0 (March 2021) and 3GPP TS38.300 V17.5.0 (June 2023) further describe L2-based UE-network (U2N) relay.

[0010] Figure 1 shows the protocol stack for user plane transport related to a PDU session, including a Layer 2 UE-Network Relay UE. The PDU layer corresponds to the PDUs carried between the remote UE and the data network (DN) via the PDU session. It is important to note that the two endpoints of the PDCP link are the remote UE and the gNB (i.e., the base station for NR technology). The relay function is performed under PDCP. This means that data security between the remote UE and the gNB is ensured without exposing raw data in the UE-Network Relay UE.

[0011] The adaptive layer within the UE network relay can distinguish between a signaling radio bearer (SRB) and a data radio bearer (DRB) for a particular remote UE. The adaptive relay layer is also responsible for mapping PC5 traffic to one or more DRBs of the UE.

[0012] Figure 2 shows the protocol stack for NAS connectivity for remote UEs to NAS (Non-Access Layer)-MM (NAS Mobility Management) and NAS-SM (NAS Session Management) components. NAS messages are transparently forwarded between the remote UE and 5G-AN via a Layer 2 UE-Network Relay UE. The role of the UE-Network Relay UE is to relay PDUs from the signaling radio bearer without modification.

[0013] Route switching procedure In Rel-17, only intra-gNB routing between indirect and direct routes is supported.

[0014] Figure 3 shows the gNB (golden network infrastructure) route switching procedure from indirect to direct routes, including the relevant RRC (Radio Resource Control) signaling. Step 1: Measurement setup and reporting Step 2: gNB determines whether to switch to a direct route. Step 3: RRC reconfiguration message to the remote UE Step 4: The remote UE performs random access to the gNB. Step 5: The remote UE uses the target configuration provided in the RRC reconfiguration message to send RRCReconfigurationComplete feedback to the gNB via the target route. Step 6: Reconfigure RRC to Relay UE Step 7: If necessary, the PC5 link between the remote UE and the relay UE is released. Step 8: The data path is switched. Note that the order of steps 6 / 7 / 8 is not restricted.

[0015] Issues to be further discussed in the WI (Work Item) phase include the following: - Whether the remote UE interrupts data transmission over the relay link after step 3. - Whether Step 6 may occur before or after Step 3, and whether Step 6 is necessary. - Whether Step 7 may occur after Step 3 or after Step 5, and whether Step 7 is necessary / can be replaced by PC5 reconfiguration. - Is it possible for Step 8 to occur after Step 5?

[0016] Figure 4 shows the procedure for switching routes within a gNB from a direct route to an indirect route. Step 1: The remote UE reports the (one or more) candidate relay UEs after it has measured / discovered them. - In step 1, the remote UE may filter out (one or more) suitable relay UEs that meet the higher-layer criteria when reporting. - In Step 1, the report may include the ID (identification information) and SL RSRP (reference signal received power) information of the relay UE, where the details of the measurements for PC5 may be left to the WI phase. Step 2: The gNB's decision to switch to the target relay UE and the target (re)setting are optionally sent to the relay UE (similar preparation). Step 3: RRC reconfiguration message to the remote UE. This may include the following information: 1) Identification information for the target relay UE, 2) Target Uu and PC5 settings. Step 4: If the remote UE has not yet set up a PC5 connection with the target relay UE, it establishes that connection. Step 5: The remote UE uses the target configuration provided during RRCReconfiguration to feed back RRCReconfigurationComplete to the gNB via the target route. Step 6: The data path is switched.

[0017] Issues to be further discussed in the WI phase include the following: - If step 2 has not yet occurred, should it occur after the relay UE is connected to the gNB (for example, after step 4)? - Is it possible for Step 4 to occur before Step 2 / 3?

[0018] SDU disposal According to 3GPP TS38.323 V17.5.0 (June 2023), the discarding of SDUs (Service Data Units) at the PDCP (Packet Data Convergence Protocol) layer is organized as follows:

[0019] When the timer indicated as discardTimer expires for a PDCP SDU, or when successful delivery of the PDCP SDU is confirmed by a PDCP status report, the transmitting PDCP entity shall discard the PDCP SDU along with the corresponding PDCP data PDU. If the corresponding PDCP data PDU has already been submitted to lower layers, the discard is indicated to the lower layers.

[0020] In the case of SRB, when upper layers request PDCP SDU discard, the PDCP entity shall discard all stored PDCP SDUs and PDCP PDUs.

[0021] It should be noted here that discarding a PDCP SDU that is already associated with a PDCP SN causes an SN gap in the transmitted PDCP data PDUs, which increases the PDCP reordering delay at the receiving PDCP entity. How the SN gap after SDU discard should be minimized is up to the UE implementation.

[0022] E1AP In current 3GPP networks, a distributed architecture may be utilized for NW nodes. For example, a gNB may be implemented based on a CU (Central Unit or centralized Unit) and one or more DUs (Distributed Units). Furthermore, the functions of the CP (Control Plane) and the functions of the UP (User Plane) may be distributed in different network nodes.

[0023] The E1 Application Protocol (E1AP), as specified in 3GPP37.483 V17.6.0 (September 2023), provides signaling services between gNB-CU-CP and gNB-CU-UP of gNBs in the NG-RAN in a split architecture, or between gNB-CU-CP and gNB-CU-UP of en-gNBs in the E-UTRAN (Extended UMTS Terrestrial Radio Access Network). The services provided by E1AP are divided into UE-related and non-UE-related services.

[0024] Figure 5 shows the interface protocol structure for E1. TNL is based on IP transport and has SCTP on top of IP. The Application Layer Signaling Protocol corresponds to E1AP.

[0025] Downlink data delivery status The Downlink Data Delivery Status (DDDS) is a procedure for communicating information about the successful or unsuccessful delivery of data from the network to the UE. The DDDS is intended to provide feedback from the corresponding node to the node hosting the NR PDCP entity, enabling the node hosting the NR PDCP entity to control the downlink (DL) user data flow for each data radio bearer via the corresponding node. The corresponding node may also forward uplink (UL) user data for that data radio bearer to the node hosting the NR PDCP entity, along with the DL data delivery status frame within the same GTP-U PDU (GPRS Tunneling Protocol Packet Data Unit).

[0026] The DDDS procedure is also used to provide feedback from the corresponding node to the node hosting the NR PDCP entity, enabling the node hosting the NR PDCP entity to control the successful delivery of DL control data to the corresponding node. Figure 6 shows an example of a successful DDDS.

[0027] Currently, there are (one or more) challenges. Rel-17 introduces support for L2 U2N relay, as described in the section above, allowing a remote UE to seek help from a neighboring relay UE to access the network, which is called an indirect route. A continuity of service aspect is also introduced, allowing a remote UE to continue providing the services it was running when switching between a direct (Uu) route and an indirect route via a relay UE. The protocol stack for Rel-17 L2 U2N relay has end-to-end PDCP termination, i.e., between the remote UE and the network (gNB), and hop-by-hop RLC (Radio Link Control) termination.

[0028] As a result, in DL transmission, the successful transmission of a packet from the gNB to the relay UE over the Uu link does not guarantee the successful transmission of the packet over the PC5 link between the relay UE and the remote UE. The same applies to UL transmission, where successful transmission over the PC5 link does not guarantee successful transmission over the Uu link. From the protocol stack, PDCP is E2E (end-to-end), but there is no feedback mechanism at the PDCP layer. Only lower layers, such as RLC, have a feedback / retransmission mechanism. Therefore, the feedback mechanism is hop-by-hop.

[0029] In a non-transmitting scenario, i.e., when the UE is connected to the network via a direct (Uu) link at the DL, the packet handling behavior at the PDCP layer is that the corresponding packet is discarded when a lower-layer ACK (acknowledgment) is received. Similarly, at the UL, the packet handling behavior is that the corresponding packet is discarded when either the discard timer has expired or the PDCP status report has confirmed the successful delivery of the packet or a successful lower-layer acknowledgment. Therefore, in a non-transmitting scenario, no problems are foreseen. The PDCP status of a packet is based on the assigned sequence number and buffer window, which should be consistent between the transmitter and receiver, i.e., between the gNB and the UE.

[0030] However, in relay scenarios, the lack of end-to-end feedback means that packets may be dropped too early (for example, a packet may fail through the second hop, but based on a successful transmission through the first hop) or stored for longer than necessary (which can lead to buffer overload). This is exacerbated during route switching scenarios where a route is switched from an indirect route to a direct route / another indirect route. In such scenarios, inconsistencies between the UE PDCP status and the gNB PDCP status can lead to data loss and service interruptions during the route switching procedure.

[0031] In Rel-17, this data loss was considered a corner case, and only intra-gNB scenarios were supported, so the PDCP status could easily be maintained when the route switching was within the same gNB. However, in Rel-18, inter-gNB scenarios should also be supported, and this data loss issue is more pronounced when switching between two different gNBs.

[0032] To prevent data loss due to premature packet discarding, the network can set a longer discard timer or wait for a PDCP status report before discarding. However, in both of these methods, packets will be buffered for a longer timer than necessary, even if the E2E transmission is successful. Furthermore, while indicators such as DDDS exist to help the network know the status of downlink data delivery, such indicators do not provide E2E status. Therefore, packet transmission through the first hop may be successful, but the associated DDDS does not provide the network with information about transmission through the second hop.

[0033] Therefore, a technique is needed that enables efficient handling of route switching in U2N relay scenarios. [Overview of the project]

[0034] Some aspects and exemplary embodiments of this disclosure may provide solutions to these or other problems. One aspect is a solution for preventing data loss during route switching scenarios by preventing premature discarding. Furthermore, the solution may also help prevent packets from being stored for too long.

[0035] According to one embodiment, a method is provided that is implemented by a gNB operating as a network node of a wireless communication network. According to this method, in response to the triggering of inter-gNB route switching for a remote UE having an indirect connection to the gNB via a relay UE, the CU-UP entity of the gNB receives instructions from the CU-CP entity of the gNB. In response to the instructions, the CU-UP entity buffers packets for the remote UE.

[0036] A further embodiment provides a method implemented by a gNB acting as a network node of a wireless communication network. According to this method, in response to the triggering of inter-gNB route switching for a remote UE having an indirect connection to the gNB via a relay UE, the CU-CP entity of the gNB provides instructions to the CU-UP entity of the gNB. These instructions cause the CU-UP entity to buffer packets for the remote UE.

[0037] In a further embodiment, a network node is provided. This network node is configured to perform the operations of a gNB in ​​a wireless communication network. These operations include the CU-UP entity of the gNB receiving instructions from the CU-CP entity of the gNB in ​​response to the triggering of inter-gNB route switching for remote UEs having an indirect connection to the gNB via a relay UE. Furthermore, these operations include the CU-UP entity buffering packets for the remote UE in response to the above instructions.

[0038] In a further embodiment, a network node is provided. This network node comprises a processing circuit and a power supply circuit configured to supply power to the processing circuit. The processing circuit is configured to perform the operations of a gNB of a wireless communication network. These operations include the CU-UP entity of the gNB receiving instructions from the CU-CP entity of the gNB in ​​response to the triggering of inter-gNB route switching for remote UEs having an indirect connection to the gNB via a relay UE. Furthermore, these operations include the CU-UP entity buffering packets for the remote UE in response to the instructions.

[0039] According to a further embodiment, a network node is provided. This network node is configured to perform the operations of a gNB in ​​a wireless communication network. These operations include the CU-CP entity of the gNB providing instructions to the CU-UP entity of the gNB in ​​response to the triggering of inter-gNB route switching for a remote UE having an indirect connection to the gNB via a relay UE. The instructions cause the CU-UP entity to buffer packets for the remote UE.

[0040] According to a further embodiment, a network node is provided. This network node comprises a processing circuit and a power supply circuit configured to supply power to the processing circuit. The processing circuit is configured to perform the operations of a gNB of a wireless communication network. These operations include the CU-CP entity of the gNB providing instructions to the CU-UP entity of the gNB in ​​response to the triggering of inter-gNB route switching for a remote UE having an indirect connection to the gNB via a relay UE. The instructions cause the CU-UP entity to buffer packets for the remote UE.

[0041] In a further embodiment, a computer program or computer program product comprising program code to be executed by a processing circuit of a network node for a communication network is provided, for example, in the form of a non-temporary storage medium. The program code may be stored in the memory of the network node. Execution of the program code causes the network node to perform operations of a gNB of a wireless communication network. These operations include the CU-UP entity of the gNB receiving instructions from the CU-CP entity of the gNB in ​​response to the triggering of inter-gNB route switching for remote UEs having an indirect connection to the gNB via a relay UE. Furthermore, these operations include the CU-UP entity buffering packets for the remote UE in response to the instructions.

[0042] According to a further embodiment, a computer program or computer program product comprising program code to be executed by a processing circuit of a network node for a communication network is provided, for example, in the form of a non-temporary storage medium. The program code may be stored in the memory of the network node. Execution of the program code causes the network node to perform the operations of a gNB of a wireless communication network. These operations include the CU-CP entity of the gNB providing instructions to the CU-UP entity of the gNB in ​​response to the triggering of inter-gNB route switching for a remote UE having an indirect connection to the gNB via a relay UE. The instructions cause the CU-UP entity to buffer packets for the remote UE.

[0043] Details of such embodiments and further embodiments will become apparent from the following embodiments for carrying out the invention. [Brief explanation of the drawing]

[0044] [Figure 1] This diagram shows the UP stack for L2 U2N relay. [Figure 2] This figure shows the CP stack for L2 U2N relay. [Figure 3] This diagram illustrates the gNB (golden network node) internal routing procedure, which involves switching from an indirect to a direct connection of the UE (Unified Entity). [Figure 4] This diagram illustrates the gNB (golden network node) internal routing procedure, which involves switching from a direct to an indirect connection to the UE (Unified Element). [Figure 5] This diagram shows the interface protocol structure of the E1 interface. [Figure 6] This figure shows an example of a successful DDDS procedure. [Figure 7] This figure schematically illustrates an example of a U2N relay scenario according to one embodiment. [Figure 8] This diagram schematically shows the details of a network node according to one embodiment. [Figure 9] This diagram schematically shows the details of the processing circuit of a network node according to one embodiment. [Figure 10] This figure schematically shows an example of a wireless communication network architecture according to one embodiment. [Figure 11] This figure schematically shows an example of a gNB architecture according to one embodiment. [Figure 12] This is a flowchart illustrating a method according to one embodiment. [Figure 13] This is a flowchart illustrating a method according to one embodiment. [Figure 14] This diagram schematically shows an example of a communication system according to one embodiment. [Figure 15] This figure schematically shows an example of a UE according to one embodiment. [Figure 16] This diagram schematically shows an example of a network node according to one embodiment. [Figure 17] This figure schematically shows an example of a host according to one embodiment. [Figure 18] This figure schematically illustrates an example of a virtualization environment according to one embodiment. [Modes for carrying out the invention]

[0045] The concepts of the present invention will be described below in more detail and with reference to the accompanying drawings, based on exemplary embodiments. The embodiments shown relate to the handling of route switching in a U2N relay scenario.

[0046] One or more solution embodiments introduce a new instruction from gNB-CU-CP to gNB-CU-UP, which may be sent via the E1 interface to instruct the triggering of a route switching procedure for the UE. Furthermore, using this new instruction, gNB-CU-UP can begin buffering packets at the source gNB. The source gNB can then forward only packets that were not successfully received at the UE, either by forwarding all packets to the target gNB or by exchanging PDCP status reports.

[0047] Some embodiments may provide one or more of the following technical advantages: The instructions mentioned above help the source gNB buffer packets only when necessary, which helps prevent buffer overload. The instructions above also help prevent premature dropping of packets during route switching scenarios, which would lead to data loss and cause interruptions.

[0048] Next, some of the embodiments intended herein will be described more thoroughly with reference to the accompanying drawings. Embodiments are provided as examples to convey the scope of the subject to those skilled in the art.

[0049] The embodiments are described in the context of NR, i.e., two or more SL UEs are deployed in the same or different NR cells. However, the same principle may be applied to LTE or any other technology that enables direct connectivity between two (or more) nearby devices. The embodiments are also applicable to relay scenarios including UE-network relay and / or UE-UE relay, where the remote UE and relay UE are obtained based on an LTE sidelink or NR sidelink, and the Uu connection between the relay UE and the base station may be an LTE Uu or an NR Uu. The embodiments are also applicable to L2-based U2N relay scenarios.

[0050] In the following explanation, the term "direct link / connection" refers to the link / connection between the (remote) UE and the base station (gNB) via the Uu(NR / LTE) interface. The term "indirect link / connection" refers to the link / connection between the (remote) UE and the base station (gNB) via the relay UE, that is, the connection / link between the (remote) UE and the relay UE is via the PC5 interface, and the connection / link between the relay UE and the base station (gNB) is via the Uu interface.

[0051] The embodiment reflects the perspectives of a (remote) UE, relay UE, source gNB, and target gNB. The (remote) UE is initially under the coverage of the source gNB and then performs route switching to the target gNB.

[0052] A source / target gNB may consist of multiple cells that a (remote) UE can reference. For simplicity, the following description assumes that the (remote) UE is performing a handover (HO) or route switching from a cell in the source gNB to a cell in the target gNB. As a result, the terms “(one or more) cells” and “(one or more) gNBs” are used interchangeably in the following description, but this interchangeability of terms does not imply any limitations on the techniques disclosed.

[0053] In the first embodiment, upon receiving a measurement report containing measurement results from a remote UE in order to initiate a route switching procedure, the control plane (CP) of the gNB, for example, CU-CP, sends an instruction to the corresponding user plane (UP), for example, CU-UP, regarding the initiation of the route switching procedure for the remote UE. The interface between the CP of the gNB or gNB-CU and the UP of the gNB or gNB-CU may be via E1, i.e., an E1 interface.

[0054] In a second embodiment, which may be an extension of the operation in the first embodiment, the UP of the gNB or gNB-CU, upon receiving this instruction, begins buffering even packets that have been successfully transmitted over the first hop (i.e., the Uu link).

[0055] In a third embodiment, which may be a further extension of the above operation, the UP of the gNB or gNB-CU, upon receiving this instruction, will discard the packet from its buffer without considering any successful acknowledgment received from either a lower layer of the UP protocol stack or the Downlink Data Delivery Status (DDDS).

[0056] In the fourth embodiment, the UP of the gNB or gNB-CU continues to buffer packets based on instructions from the CP of the gNB or gNB-CU until the UP of the gNB or gNB-CU does the following: - Receive another instruction from the CP of the gNB or gNB-CU-CU to stop buffering. - Receive an instruction to forward all buffered packets to another gNB's UP, or - Receive a PDCP status report from another gNB's UP.

[0057] In the fifth embodiment, instructions from the CP of the gNB or gNB-CU include a timer that notifies the UP of the gNB how long the packet needs to be buffered.

[0058] In the sixth embodiment, the CU-UP starts a timer after it has received the DDDS and determined how long the packet needs to be buffered. After the timer expires, the CU-UP discards all buffered packets.

[0059] In the seventh embodiment, if the route switching procedure fails, the CP of the gNB instructs the UP of the gNB to discard all buffered packets.

[0060] Therefore, in the exemplary scenario, the remote UE operates in an L2-based U2N relay scenario where the remote UE has an indirect connection to the first gNB. The relay UE supports the indirect connection by a first connection hop extending between the gNB and the relay UE, and by a second connection hop extending between the relay UE and the remote UE. In the case of a route switching procedure (handover) of the remote UE to the second gNB, the first gNB may be called the “source” gNB, and the second gNB may be called the “target” gNB.

[0061] In an exemplary embodiment of one or more solutions described herein, the central unit-control plane (CU-CP) of the source gNB provides the CU user plane (CU-UP) of the source gNB with instructions to initiate a route switching procedure. In a specific example, the source gNB CU-CP sends route switching instructions to the source gNB CU-UP via the E1 interface between the source gNB CU-CP and the source gNB CU-UP.

[0062] The source gNB CU-UP responds to the above instruction by buffering even packets that have been successfully transmitted via the first hop (i.e., via the Uu link between the source gNB and the relay UE). Therefore, the route switching instruction sent to the CU-UP by the CU-CP can also be understood as a buffer start instruction.

[0063] In at least one embodiment, the source gNB CU-UP modifies its normal packet dropping behavior in response to receiving the above instruction. For example, the source gNB CU-UP does not drop the corresponding packet from its buffer even though it has received an transmit ACK or DDDS from a lower layer of the source gNB CU-UP's protocol stack.

[0064] In one or more embodiments, the source gNB CU-UP continues to buffer packets for the UE until it receives one or more of the following: (a) a buffer stop instruction from the source gNB CU-CP, (b) an instruction to forward all packets buffered for the UE to another gNB (e.g., a target gNB), or (c) a PDCP status report from the CU-CP of another gNB (e.g., a target gNB).

[0065] In at least one embodiment, a route switching instruction provided by a source gNB CU-CP to a source gNB CU-UP includes a timer that instructs the source gNB CU-UP on how long it should buffer a packet. Where the route switching instruction includes a timer, it means, for example, that the instruction includes a value or other data item indicating the timer expiration period, and the CU-UP sets and starts a timer / counter with the instructed expiration period. Alternatively, the CU-UP determines the buffer duration and sets the expiration timer accordingly. In either method, the CU-UP discards the buffered packet upon timer expiration, and this behavior is an example of advantageous prevention or mitigation of buffer overflow problems in CU-CPs.

[0066] Furthermore, in at least one embodiment, the source gNB CU-CP is configured to provide a source gNB CU-UP with a signal that the route switching procedure for the UE was unsuccessful, and the CU-UP is configured to discard buffered packets in response to this signal.

[0067] Figure 7 shows an exemplary scenario in which network node 12 is connected to remote UE 14 via connection 16 in a communicative manner.

[0068] The connection 16 includes a first hop link 18 extending between the network node 12 and the relay UE 20, and a second hop link 22 extending between the relay UE 20 and the remote UE 14. The remote UE 14 operates in an L2-based U2N relay scenario with respect to the network node 12, where the network node 12 is, for example, an access point in a cellular network. In a particular example, the network node 12 is an eNB in ​​an LTE network, and in another example, the network node 12 is a gNB in ​​an NR 5G network.

[0069] An exemplary embodiment given in the context of Figure 7 relates to a route switching scenario in which the connection path of a remote UE 14 is switched from a network node 12 as a first node or source node to another network node 24 as a second node or target node. Network node 24 may be of the same type as network node 12, or network node 24 may be of a different type. In at least one example, network node 12 is a first gNB or source gNB of a wireless communication network operating in accordance with the 5G specifications published by 3GPP, and network node 24 is a second gNB or target gNB.

[0070] Figure 8 shows illustrative details for network node 12 or 24.

[0071] The illustrated node includes a processing circuit 30, a wireless communication circuit 32, and a network (NW) interface circuit 34. The processing circuit 30 is configured to perform overall control of the node and to perform communication processing for downlink (DL) data and uplink (DL) data, and the wireless communication circuit 32 includes one or more radio transmitters and receivers (radio frequency (RF) transceiver circuits) configured to transmit DL data and control signals in accordance with a defined air interface protocol and to receive UL data and control signals in accordance with such a protocol.

[0072] Network nodes 12 or 24 use, for example, a radio communication circuit 32 to provide communication service coverage in one or more cells, and network nodes 12 or 24 use a network interface circuit 34 to communicately connect to other nodes in the cellular network, for example, other radio access network (RAN) nodes or nodes in the core network (CN) of the cellular network. In this regard, the network interface circuit 34 may have two or more interfaces or may support multiple signaling schemes or types, and the network interface circuit 34 provides wired or wireless physical layer connectivity and associated timing and protocol processing for anchoring network connections to other nodes.

[0073] The processing circuit 30 comprises fixed circuits, programmatically configured circuits, or a combination of both. Figure 9 shows an example in which the processing circuit 30 comprises one or more microprocessors 40, which are specifically adapted to carry output operations that implement one or more of the solutions described herein, based on the execution of computer program instructions 42 contained in or optionally stored in storage 44 connected to the microprocessors 40. Here, “microprocessor” has a broad meaning and includes microcontrollers, digital signal processors, and the like.

[0074] The storage 44 may further contain one or more types of data 46, including dynamic data created and processed during live operation, such as provisioning information and configuration parameters, as well as / or persistent data. The storage 44 may comprise one or more types of computer-readable media and may include a mixture of working memory for live operation and program memory for longer-term storage of instructions and persistent data. Examples include any one or more DRAM, SRAM, flash, EEPROM, solid disk (SSD), etc.

[0075] Figure 10 shows an exemplary wireless communication network 50, which is illustrated in an exemplary context of 5G New Radio (NR). In this example, network 50 then includes a 5G core network (5GC) 52 and a next-generation (NG) radio access network (RAN) 54. The RAN 54 includes one or more gNBs 56 as an example of the network nodes 12 described above. Here, two gNBs 56-1 and 56-2 are shown as an example, and the two gNBs 56-1 and 56-2 are configured to perform the operations described above in the context of route switching for an L2-based U2N relay scenario.

[0076] As an example, each gNB56 includes a gNB central unit (gNB-CU)60 and one or more gNB distributed units (gNB-DU)62 connected to the CU via an F1 interface. The gNB-CU60 provides overall processing and control and network interfacing, while the gNB-DU62 includes the wireless interface. The gNB-CU60 supports an Xn-C interface for inter-gNB communication.

[0077] Figure 11 shows functional or logical entities within the gNB56, which are realized, for example, through underlying processing circuits and memory.

[0078] gNB-CU-CP70 is configured to handle control plane (CP) operations, and one or more instances of gNB-CU-UP72 handle user plane (UP) operations. gNB-DU62 has an F1-C interface to CU-CP70 and an F1-U interface to (one or more) CU-UP72. CU-CP70 has an E1 interface to CU-UP72, and in one or more exemplary embodiments, CU-CP70 uses the E1 interface to provide the route switching instructions and relational information described above for favorable buffering control of packets related to L2 relay-connected UEs undergoing inter-gNB route switching.

[0079] Such operation can be understood as the gNB or other network node providing lossless route switching in the downlink direction for UEs indirectly connected to the network via sidelink relay connections. That is, favorable buffering prevents the loss of downlink packets for the remote UE by buffering packets for the remote UE at the source network node, including packets indicated as successfully transmitted on the first hop of the remote UE's relay-based indirect connection. Furthermore, by providing timer-controlled retention of these buffered packets and / or other discard triggers at the source network node, the buffered packets are not retained indefinitely or unnecessarily at the source network node, and thus reduce buffer overflows that may occur with such retention.

[0080] Figure 12 shows a flowchart illustrating how the gNB operation, specifically a method that can be used to implement the concepts shown in a network node performing one of the operations of the gNB's CU-UP entities, such as the CU-UP entity 72 described above. This method can be used to implement the above-described functionality applicable to route switching in a U2N relay scenario.

[0081] When a processor-based implementation of the network node is used, at least some of the steps of the method in Figure 12 may be performed and / or controlled by one or more processors of the network node. Such one or more processors may implement the processing circuitry of the network node. Such a network node may also include memory for storing program code to implement at least some of the functions or steps of the method in Figure 12 described below.

[0082] In step 1210, in response to the triggering of inter-gNB routing for a remote UE having an indirect connection to the gNB via a relay UE, the CU-UP entity of the gNB receives instructions from the CU-CP entity of the gNB, for example, the CU-CP entity 70 described above. In some scenarios, the CU-UP entity may receive the above instructions via the E1 interface. Inter-gNB routing may involve a target gNB. The remote UE may correspond to the remote UE 14 described above, the relay UE may correspond to the relay UE 20 described above, and the gNB may correspond to the network node 12 described above. The gNB may be implemented based on a distributed architecture, for example, as described with respect to Figures 10 and 11.

[0083] In some scenarios, a CU-UP entity may start a timer in response to receiving the above instructions. These instructions may include timer settings, such as the timer's start value.

[0084] In step 1220, in response to the instructions in step 1210, the CU-UP entity buffers a packet for the remote UE.

[0085] Buffering packets for the remote UE in step 1220 may involve modifying the packet discard behavior of the CU-UP entity so that the CU-UP entity does not discard packets held in the CU-UP entity's buffer for the remote UE in response to instructions for the successful transmission of those packets to the relay UE. These instructions for successful transmission may be provided, for example, via DDDS information and / or include acknowledgments from lower protocol levels of the CU-UP entity.

[0086] In some scenarios, buffering the packet for the remote UE in step 1220 may involve the gNB holding the packet once it has received instructions for successful transmission to the relay UE.

[0087] In some scenarios, a CU-UP entity may discard a packet buffered for a remote UE in response to the expiration of a timer that was started in response to receiving the above instructions.

[0088] In some scenarios, the CU-UP entity may be able to determine the duration of the buffering.

[0089] In some scenarios, a CU-UP entity may discard a packet buffered for a remote UE in response to the earlier of the following events: timer expiration or the occurrence of a discard trigger.

[0090] In some scenarios, the discard trigger may be one or more of the following: receiving a discard command from a CU-CP entity, or receiving a PDCP status report from a target gNB for a remote UE.

[0091] In some scenarios, a CU-UP entity may discard a buffered packet for a remote UE in response to either forwarding the packet to another gNB or receiving a PDCP report from another gNB, for example, from the target gNB of a route switch.

[0092] In some scenarios, a CU-UP entity may discard a packet buffered for a remote UE in response to reaching a specified time limit for such buffering.

[0093] If the inter-gNB route switching involves a target gNB, the method may proceed to step 1230, which then involves forwarding the buffered packets for the remote UE to the target gNB.

[0094] Figure 13 shows a flowchart illustrating how the gNB operation, specifically a method that can be used to implement the concepts shown in a network node performing the operation of the gNB's CU-CP entity, for example, the CU-CP entity 70 described above. This method can be used to implement the above-described functionality applicable to route switching in a U2N relay scenario.

[0095] When a processor-based implementation of the network node is used, at least some of the steps of the method in Figure 13 may be performed and / or controlled by one or more processors of the network node. Such one or more processors may implement the processing circuitry of the network node. Such a network node may also include memory for storing program code to implement at least some of the functions or steps of the method in Figure 13 described below.

[0096] In step 1310, an inter-gNB route switching is triggered for a remote UE that has an indirect connection to the gNB via a relay UE. The inter-gNB route switching can be initiated by the CU-CP entity of the gNB, or the CU-CP entity of the gNB may, in some cases, become aware of the route switching triggering.

[0097] In step 1320, in response to the triggering of inter-gNB route switching for the remote UE, the CU-CP entity of the gNB provides instructions to the CU-UP entity of the gNB, for example, to one or more of the CU-UP entities 72 described above. The remote UE may correspond to the remote UE 14 described above, the relay UE may correspond to the relay UE 20 described above, and the gNB may correspond to the network node 12 described above. The gNB may be implemented based on a distributed architecture, for example, as described with respect to Figures 10 and 11.

[0098] The above instructions cause the CU-UP entity to buffer packets for the remote UE. The CU-CP entity may provide the above instructions via the E1 interface.

[0099] Buffering packets for a remote UE may involve modifying the packet discarding behavior of a CU-UP entity so that the CU-UP entity does not discard packets held in the CU-UP entity's buffer for the remote UE in response to instructions for the successful transmission of those packets to the relay UE. Instructions for successful transmission may be provided via DDDS information or may include acknowledgments from lower protocol levels of the CU-UP entity. Buffering packets for a remote UE may involve the gNB holding the packets once it has received instructions for successful transmission to the relay UE. If inter-gNB routing involves a target gNB, buffering may then involve forwarding the buffered packets for the remote UE to the target gNB, or buffering may be followed by forwarding.

[0100] Figure 14 shows an example of a communication system 1400 according to several embodiments.

[0101] In this example, the communication system 1400 includes a communication network 1402 which includes an access network 1404 such as a radio access network (RAN) and a core network 1406 which includes one or more core network nodes 1408. The access network 1404 includes one or more access network nodes (one or more of which may commonly be referred to as network nodes 1410), such as network nodes 1410a and 1410b, or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Furthermore, as will be understood by those skilled in the art, network nodes are not necessarily limited to implementations in which the radio portion and baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include separate implementations or parts thereof. For example, in some embodiments, the communication network 1402 includes one or more open RAN (ORAN) network nodes. An ORAN network node is a node in a communications network 1402 that supports the ORAN specification (for example, a specification published by the O-RAN Alliance or any similar organization) and may operate alone or with other nodes to implement one or more functions of any node in the communications network 1402, including one or more network nodes 1410 and / or core network node 1408.

[0102] One or more of the network nodes 1410 may be configured as described above for network node 12 / gNB56. That is, one or more of the network nodes 1410 are configured to support favorable packet buffering for L2 relay-connected UEs that undergo inter-NW node route switching. For example, UE 1412A or 1412B has an indirect route / connection to network node 1410 via the relay UE, and the route of UE 1412A or 1412B is switched to network node 1410B. Network node 1410A performs favorable packet buffering in this exemplary scenario.

[0103] Examples of ORAN network nodes include O-CUs (including open radio units (O-RUs), open distributed units (O-DUs), open central unit (O-CU) control planes (O-CU-CPs) or O-CU user planes (O-CU-UPs), RAN intelligent controllers (near-real-time or non-real-time) hosting software or software plugins such as quasi-real-time control applications (e.g., xApps) or non-real-time control applications (e.g., rApps), or any combination thereof (the adjective "open" specifies support for the ORAN specification). Network nodes may support the specification by supporting interfaces defined by the ORAN specification, such as A1, F1, W1, E1, E2, X2, Xn interfaces, open fronthaul user plane interfaces, or open fronthaul management plane interfaces. Furthermore, ORAN access nodes may be logical nodes within physical nodes. In addition, ORAN network nodes may be implemented in a virtualized environment in which one or more network functions are virtualized (as further described below). For example, the virtualized environment may include an O-cloud computing platform organized by a service management and orchestration framework via an O-2 interface defined by the O-RAN Alliance or equivalent technology. Network node 1410 facilitates direct or indirect connectivity of user equipment (UEs), such as by connecting UEs 1412a, 1412b, 1412c, and 1412d (one or more of which are commonly referred to as UE1412) to the core network 1406 over one or more wireless connections.

[0104] Exemplary wireless communication over a wireless connection involves transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without using wires, cables, or other material conductors. Furthermore, in different embodiments, the communication system 1400 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals, whether via a wired or wireless connection. The communication system 1400 may include and / or interface with any type of communication, telecommunication, data, cellular, wireless network, and / or other similar types of systems.

[0105] UE1412 may be any of a wide variety of communication devices, including a wireless device configured, set up, and / or operable to communicate wirelessly with network node 1410 and other communication devices. Similarly, network node 1410 is configured, capable, set up, and / or operable to communicate directly or indirectly with UE1412 and / or with other network nodes or devices in communication network 1402 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in communication network 1402.

[0106] In the illustrated example, the core network 1406 connects network node 1410 to one or more hosts, such as host 1416. These connections may be direct or indirect, via one or more intermediate networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1406 includes one or more core network nodes (e.g., core network node 1408) structured with hardware and software components. The characteristics of these components may be substantially similar to those described for UEs, network nodes, and / or hosts, and therefore their descriptions are generally applicable to the corresponding components of core network node 1408. An exemplary core network node includes one or more functions from among the following: Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscriber Identifier Decryption Function (SIDF), Unified Data Management (UDM), Security Edge Protected Proxy (SEPP), Network Exposure Function (NEF), and / or User Plane Function (UPF).

[0107] Host 1416 may be owned or under the control of a service provider other than the operator or provider of the access network 1404 and / or the communication network 1402, and may be operated by or on behalf of the service provider. Host 1416 may host a variety of applications to provide one or more services. Examples of such applications include data acquisition services such as extracting and compiling live and pre-recorded audio / video content, data on various ambient conditions detected by multiple UEs, analytical functions, social media, functions for controlling or possibly interacting with remote devices, functions for alarms and surveillance centers, or any other such functions performed by the server.

[0108] Overall, the communication system 1400 in Figure 14 enables connectivity between the UE, network nodes, and hosts. In this sense, the communication system may be configured to operate according to predefined rules or procedures, including, but not limited to, GSM (Global System for Mobile Communications), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future-generation standards, such as 6G (sixth generation), wireless local area network (WLAN) standards such as the IEEE 802.11 standard (WiFi), and / or any other suitable wireless communication standards such as global interoperability for microwave access (WiMAX), Bluetooth, Z-Wave, near-field communications (NFC) ZigBee, LiFi, and / or LoRa and Sigfox, or any low-power wide area network (LPWAN) standards.

[0109] In some examples, the communication network 1402 is a cellular network implementing 3GPP standardized features. Therefore, the communication network 1402 may support network slicing to provide different logical networks to different devices connected to the communication network 1402. For example, the communication network 1402 may provide ultra-high reliability low latency communication (URLLC) services to some UEs while providing extended mobile broadband (eMBB) services to other UEs, and / or also provide massive machine-type communication (mMTC) / massive IoT services to further UEs.

[0110] In some examples, UE1412 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to access network 1404 on a predetermined schedule when triggered by an internal or external event, or in response to a request from access network 1404. Furthermore, the UE may be configured to operate in single, multi-RAT, or multi-standard modes. For example, the UE may operate with one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Enhanced UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).

[0111] In this example, hub 1414 communicates with access network 1404 to facilitate indirect communication between one or more UEs (e.g., UE1412c and / or 1412d) and a network node (e.g., network node 1410b). In some examples, hub 1414 may be a controller, router, content source and content analysis, or any other communication device described herein with respect to the UE. For example, hub 1414 may be a broadband router that enables access to the core network 1406 for the UE. In another example, hub 1414 may be a controller that sends commands or instructions to one or more actuators in the UE. Commands or instructions may be received from the UE, network node 1410, or by executable code, scripts, processes, or other instructions in hub 1414. In yet another example, hub 1414 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform data analysis or other processing. In yet another example, hub 1414 may be a content source. For example, with respect to a UE that is a VR headset, display, loudspeaker, or other media distribution device, the hub 1414 can retrieve VR assets, video, audio, or other media or data related to sensory information via network nodes, which the hub 1414 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In yet another example, the hub 1414 acts as a proxy server or orchestrator for the UE, especially if one or more of the UEs are low-energy IoT devices.

[0112] Hub 1414 may have always-on / persistent or intermittent connections to network node 1410b. Hub 1414 may also allow different communication methods and / or schedules between Hub 1414 and UEs (e.g., UE 1412c and / or 1412d), and between Hub 1414 and the core network 1406. In other examples, Hub 1414 connects to the core network 1406 and / or one or more UEs via a wired connection. Furthermore, Hub 1414 may be configured to connect to an M2M service provider on the access network 1404 and / or another UE via a direct connection. In some scenarios, a UE may establish a wireless connection with network node 1410 while still connected via Hub 1414 via a wired or wireless connection. In some embodiments, Hub 1414 may be a dedicated hub, i.e., a hub whose primary function is to route communications from UEs to network node 1410b and from network node 1410b to UEs. In other embodiments, the hub 1414 may be a non-dedicated hub, i.e., a device that can operate to route communication between the UE and the network node 1410b, but can further operate as a communication start point and / or end point for several data channels.

[0113] Figure 15 shows the UE1500 in several embodiments. As used herein, UE refers to a device that is capable of, configured, and / or operable of communicating wirelessly with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), vehicles, vehicle-mounted or vehicle-embedded / integrated wireless devices, etc. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine-type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0114] A UE may support device-to-device (D2D) communication by implementing 3GPP standards for sidelink communication, dedicated short-range communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE does not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended to be sold to or operated by a human user, but may not be associated with a particular human user, or may not be associated with a particular human user in the first place. Alternatively, a UE may represent a device (e.g., a smart electricity meter) that is not intended to be sold to or operated by an end user, but may be associated with or operate for the benefit of a user.

[0115] The UE1500 includes processing circuitry 1502 operably coupled via bus 1504 to an input / output interface 1506, a power supply 1508, memory 1510, a communication interface 1512, and / or any other components, or any combination thereof. Some UEs may utilize all or a subset of the components shown in Figure 15. The level of integration between components may vary from UE to UE. Furthermore, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, and receivers.

[0116] The processing circuit 1502 is configured to process instructions and data and may be configured to implement any sequential state machine capable of executing instructions stored in memory 1510 as a machine-readable computer program. The processing circuit 1502 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.), programmable logic with appropriate firmware, a microprocessor or digital signal processor (DSP) with appropriate software, one or more stored computer programs, a general-purpose processor, or any combination of the above. For example, the processing circuit 1502 may include multiple central processing units (CPUs).

[0117] In this example, the input / output interface 1506 may be configured to provide an input device, an output device, or one or more interfaces to one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, emitters, smart cards, other output devices, or any combination thereof. Input devices may allow a user to capture information to the UE1500. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, webcams, etc.), microphones, sensors, mice, trackballs, directional pads, trackpads, scroll wheels, smart cards, etc. A presence-sensitive display may include a capacitive or resistive touch sensor for detecting user input. Sensors may include, for example, an accelerometer, gyroscope, tilt sensor, force sensor, magnetometer, light sensor, proximity sensor, biosensor, or any combination thereof. Output devices may use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port may be used to provide input and output devices.

[0118] In some embodiments, the power supply 1508 is structured as a battery or battery pack. Other types of power sources may be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. The power supply 1508 may further include a power circuit for distributing power from the power supply 1508 itself and / or from an external power source via an interface such as an input circuit or power cable. Distributing power may, for example, be for charging the power supply 1508. The power circuit may perform any formatting, conversion, or other modifications to the power from the power supply 1508 to make that power suitable for each component of the UE 1500 to which the power is supplied.

[0119] Memory 1510 may be memory, or configured to contain memory, such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, etc. In one example, memory 1510 may contain one or more application programs 1514, such as an operating system, a web browser application, a widget, a gadget engine, or other application, and corresponding data 1516. Memory 1510 may store any of a variety of operating systems or combinations of operating systems for use by UE 1500.

[0120] Memory 1510 may be configured to include several physical drive units, such as a redundant array of independent disks (RAID), flash memory, USB flash drives, external hard disk drives, thumb drives, pen drives, key drives, high-density digital versatile disk (HD-DVD) optical disk drives, internal hard disk drives, Blu-ray optical disk drives, holographic digital data storage (HDDS) optical disk drives, external mini dual in-line memory modules (DIMMs), synchronous dynamic random access memory (SDRAM), external microDIMM SDRAM, smart card memory such as a tamper-proof module in the form of a universal integrated circuit card (UICC) containing one or more subscriber identification modules (SIMs) such as USIM and / or ISIM, other memory, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a "SIM card". Memory 1510 may enable UE 1500 to access instructions, application programs, etc., stored in temporary or non-temporary memory media, to offload data, or to upload data. Products such as products utilizing a communication system may be tangibly embodied as memory 1510 or within memory 1510, and memory 1510 may be a device-readable storage medium or comprise a device-readable storage medium.

[0121] The processing circuit 1502 may be configured to communicate with an access network or other networks using a communication interface 1512. The communication interface 1512 may comprise one or more communication subsystems, including an antenna 1522, or may be communicatively coupled to the antenna 1522. The communication interface 1512 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or network node in the access network). Each transceiver may include a transmitter 1518 and / or receiver 1520 suitable for providing network communication (e.g., optical, electrical, frequency-allocated, etc.). Furthermore, the transmitter 1518 and receiver 1520 may be coupled to one or more antennas (e.g., antenna 1522), sharing circuit components, software, or firmware, or alternatively, being implemented separately.

[0122] In the embodiments shown, the communication functions of the communication interface 1512 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as the use of the Global Positioning System (GPS) to determine location, other similar communication functions, or any combination thereof. The communication may be implemented in accordance with one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMAX, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc.

[0123] Regardless of the sensor type, the UE may provide the output of data captured by the UE's sensors to network nodes via a wireless connection through the UE's communication interface 1512. The data captured by the UE's sensors may be communicated to network nodes via another UE through a wireless connection. The output may be periodic (e.g., once every 15 minutes if reporting detected temperature), in response to a triggering event (e.g., an alarm is sent when humidity is detected), in response to a request (e.g., a user-initiated request), random (e.g., to equalize the load from reports from several sensors), or a continuous stream (e.g., a live video feed of a patient).

[0124] As another example, the UE may include an actuator, motor, or switch relating to a communication interface configured to receive radio input from a network node via a wireless connection. In response to the received radio input, the state of the actuator, motor, or switch may change. For example, the UE may include a motor that adjusts the control surface or rotor of a drone in flight according to the received input, or a robotic arm that performs a medical procedure according to the received input.

[0125] When in the form of an Internet of Things (IoT) device, a UE can be a device for use in one or more application domains, which include, but are not limited to, urban wearable technology, augmented industrial applications, and healthcare. Non-exclusive examples of such IoT devices are devices that are connected refrigerators or freezers, TVs, connected lighting devices, energy meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, air conditioning systems such as heat pumps, autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearables for haptic augmentation or perceptual augmentation, water sprinklers, animal or product tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device such as a heart rate monitor or remotely controlled surgical robot, or devices embedded in them. The UE in the form of an IoT device comprises circuitry and / or software according to the intended application of the IoT device, in addition to the other components described with respect to the UE1500 shown in Figure 15.

[0126] In another specific example, in an IoT scenario, a UE 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 UE and / or network node. In this case, the UE could be an M2M device, which is sometimes called an MTC device in a 3GPP context. In one specific example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, the UE may represent a vehicle, such as a car, bus, truck, ship, and airplane, or other equipment capable of monitoring its operational status and / or reporting on its operational status, or performing other functions related to its operation.

[0127] In practice, any number of UEs can be used together for a single use case. For example, the first UE may be the drone itself, or integrated within the drone, providing the drone's speed information (obtained through a speed sensor) to the second UE, which is the remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (for example, by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UEs may also include two or more of the functions described above. For example, the UE may have sensors and actuators and handle the communication of data about both the speed sensor and the actuator.

[0128] Figure 16 shows a network node 1600 according to several embodiments. As used herein, a network node refers to a device that is configured, set up, and / or operable to communicate directly or indirectly with UEs in a communication network and / or with other network nodes or devices. 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 B, evolved node B (eNB), and NR node B (gNB)), O-RAN nodes, or components of O-RAN nodes (e.g., O-RU, O-DU, O-CU). Network node 1600 may implement a CU-CP entity of a gNB, such as CU-CP entity 70 in Figure 11, or network node 1600 may implement a CU-UP entity of a gNB, such as one of CU-UP entities 72 in Figure 11.

[0129] Base stations can be categorized based on the amount of coverage they provide (or, in other words, the base station's transmit power level), and are therefore sometimes called femto base stations, pico base stations, micro base stations, or macro base stations, depending on the amount of coverage they provide. A base station can be a relay node or relay donor node that controls relays. Network nodes may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit, a distributed unit (e.g., one in an O-RAN access node), and / or a remote radio unit (RRU), sometimes called a remote radio head (RRH). Such remote radio units may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station are sometimes called nodes in a distributed antenna system (DAS).

[0130] Other examples of network nodes include multiple transmit point (multi-TRP) 5G access nodes, MSR equipment such as multi-standard radio (MSR) BS, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base station transceiver stations (BTSs), transmit points, transmit nodes, multi-cell / multicast coordinated entities (MCEs), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes (e.g., evolved serving mobile location centers (E-SMLCs)), and / or drive test minimization (MDTs).

[0131] Network node 1600 includes a processing circuit 1602, a memory 1604, a communication interface 1606, and a power supply 1608. Network node 1600 can be assembled from multiple physically distinct components (e.g., node B components and RNC components, or BTS components and BSC components), each of which may have its own respective components. In some scenarios where network node 1600 has multiple distinct components (e.g., BTS components and BSC components), one or more of the distinct components may be shared among several network nodes. For example, a single RNC may control multiple node Bs. In such a scenario, each unique node B-RNC pair may, in some cases, be considered a single distinct network node. In some embodiments, network node 1600 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1604 for different RATs), and some components may be reused (e.g., the same antenna 1610 may be shared by different RATs). The network node 1600 may also include multiple sets of various indicated components for different radio technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth radio technologies, which are integrated into the network node 1600. These radio technologies may be integrated into the same or different chips or sets of chips, and other components within the network node 1600.

[0132] The processing circuit 1602 may include one or more combinations of microprocessors, controllers, microcontrollers, central processing units, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, or any other suitable computing devices, resources, or combinations of hardware, software, and / or encoded logic, which are capable of operating to provide network node 1600 functionality, either on its own or in combination with other network node 1600 components such as memory 1604.

[0133] In some embodiments, the processing circuit 1602 includes a system-on-a-chip (SOC). In some embodiments, the processing circuit 1602 includes one or more of the radio frequency (RF) transceiver circuit 1612 and the baseband processing circuit 1614. In some embodiments, the radio frequency (RF) transceiver circuit 1612 and the baseband processing circuit 1614 may be on separate chips (or sets of chips), boards, or units such as radio and digital units. In alternative embodiments, some or all of the RF transceiver circuit 1612 and the baseband processing circuit 1614 may be on the same chip or set of chips, board, or unit.

[0134] Memory 1604 may include, but is not limited to, any form of volatile or non-volatile computer-readable memory, including persistent storage, solid memory, remote-mount memory, magnetic media, optical media, random-access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD), or digital video disc (DVD)), and / or any other volatile or non-volatile, non-temporary device-readable and / or computer-executable memory device for storing information, data, and / or instructions that may be used by the processing circuit 1602. Memory 1604 may store any suitable instructions, data, or information, including other instructions, that may be executed by the processing circuit 1602 and utilized by the network node 1600, including applications that include one or more computer programs, software, logic, rules, code, and tables. Memory 1604 may be used to store calculations performed by the processing circuit 1602 and / or data received via the communication interface 1606. In some embodiments, the processing circuit 1602 and the memory 1604 are integrated.

[0135] Communication interface 1606 is used in wired or wireless signaling and / or data between network nodes, access networks, and / or UEs. As shown, communication interface 1606 includes (one or more) ports / (one or more) terminals 1616 for sending and receiving data to and from the network, for example, over a wired connection. Communication interface 1606 also includes a wireless front-end circuit 1618, which is coupled to or, in some embodiments, may be part of antenna 1610. The wireless front-end circuit 1618 includes a filter 1620 and an amplifier 1622. The wireless front-end circuit 1618 may be connected to antenna 1610 and processing circuit 1602. The wireless front-end circuit may be configured to adjust signals communicated between antenna 1610 and processing circuit 1602. The wireless front-end circuit 1618 may receive digital data to be sent to other network nodes or UEs via the wireless connection. The wireless front-end circuit 1618 can convert digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filter 1620 and / or amplifier 1622. The radio signal can then be transmitted via antenna 1610. Similarly, when receiving data, antenna 1610 can collect a radio signal, which is then converted into digital data by the wireless front-end circuit 1618. The digital data can then be passed to processing circuit 1602. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0136] In some alternative embodiments, the network node 1600 does not include a separate radio front-end circuit 1618; instead, the processing circuit 1602 includes the radio front-end circuit and is connected to the antenna 1610. Similarly, in some embodiments, all or part of the RF transceiver circuit 1612 is part of the communication interface 1606. In yet another embodiment, the communication interface 1606, as part of a radio unit (not shown), includes one or more ports or terminals 1616, the radio front-end circuit 1618, and the RF transceiver circuit 1612, and the communication interface 1606 communicates with a baseband processing circuit 1614, which is part of a digital unit (not shown).

[0137] Antenna 1610 may include one or more antennas or antenna arrays configured to transmit and / or receive radio signals. Antenna 1610 may be coupled to the radio front-end circuit 1618 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, Antenna 1610 is separate from the network node 1600 and can be connected to the network node 1600 through an interface or port.

[0138] Antenna 1610, communication interface 1606, and / or processing circuit 1602 may be configured to perform any receiving operations and / or certain acquisition operations as described herein as being performed by a network node. Any information, data, and / or signals may be received from the UE, another network node, and / or any other network equipment. Similarly, antenna 1610, communication interface 1606, and / or processing circuit 1602 may be configured to perform any transmitting operations as described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to the UE, another network node, and / or any other network equipment.

[0139] Power supply 1608 provides power to the various components of network node 1600 in a form suitable for each component (for example, at the voltage and current levels required for each respective component). Power supply 1608 may further include, or be coupled to, a power management circuit for supplying power to the components of network node 1600 to perform the functions described herein. For example, network node 1600 may be connectable to an external power source (e.g., a power grid, an electrical outlet) via an input circuit or interface such as an electrical cable, thereby the external power source powers the power circuit of power supply 1608. As a further example, power supply 1608 may include a power source in the form of a battery or battery pack connected to or integrated into the power circuit. The battery may provide backup power in the event of an external power failure.

[0140] Embodiments of network node 1600 may include additional components other than those shown in Figure 16 to provide several aspects of the network node's functionality, including any of the functions described herein and / or any functions necessary to support the subject matter described herein. For example, network node 1600 may include user interface equipment for enabling information input to and output from network node 1600. This may enable a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1600.

[0141] Figure 17 is a block diagram of host 1700, which may be one embodiment of host 1416 in Figure 14, according to various aspects described herein. Host 1700 as used herein may be a variety of combinations of hardware and / or software, including standalone servers, blade servers, cloud implementation servers, distributed servers, virtual machines, containers, or processing resources in a server farm. Host 1700 may provide one or more services to one or more UEs.

[0142] The host 1700 includes a processing circuit 1702 operably coupled to an input / output interface 1706, a network interface 1708, a power supply 1710, and memory 1712 via a bus 1704. Other embodiments may include other components. The features of these components may be substantially similar to those described with respect to the devices in previous figures, such as Figures 15 and 16, and therefore their descriptions are generally applicable to the corresponding components of the host 1700.

[0143] Memory 1712 may include one or more computer programs, each containing one or more host application programs 1714 and data 1716, the data 1716 of which may include user data, for example, data generated by the UE for host 1700, or data generated by host 1700 for the UE. Embodiments of host 1700 may utilize only a subset or all of the components shown. Host application programs 1714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Multipurpose Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of the UE (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application program 1714 may also provide user authentication and license checks, and may periodically report health, route, and content availability to a central node, such as a device in the core network or a device at the edge of the core network. Thus, host 1700 may select and / or direct different hosts for over-the-top services for the UE. The host application program 1714 may support various protocols, including HTTP Live Streaming (HLS), Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), and Dynamic Adaptive Streaming over HTTP (MPEG-DASH).

[0144] Figure 18 is a block diagram showing a virtualized environment 1800 in which functions implemented by several embodiments may be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device, which may include virtualizing hardware platforms, storage devices, and networking resources. The virtualization used herein may apply to any device or its components described herein and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components, executed by one or more virtual machines (VMs) implemented in one or more virtualized environments 1800 hosted by one or more hardware nodes, such as network nodes, UEs, core network nodes, or hardware computing devices acting as hosts. Furthermore, in embodiments in which the virtual nodes do not require wireless connectivity (e.g., core network nodes or hosts), the nodes may be fully virtualized. In some embodiments, the virtualized environment 1800 includes components defined by the O-RAN Alliance, such as an O-cloud environment organized by a service management and orchestration framework via an O-2 interface.

[0145] Application 1802 (which may alternatively be referred to as a software instance, virtual appliance, network function, virtual node, virtual network function, etc.) runs in the virtualized environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0146] Hardware 1804 includes processing circuits, memory for storing software and / or instructions executable by the hardware processing circuits, and / or other hardware devices described herein, such as network interfaces and input / output interfaces. The software is executed by the processing circuits to instantiate one or more virtualization layers 1806 (also called hypervisors or virtual machine monitors (VMMs)), providing VM1808a and 1808b (one or more of which may commonly be referred to as VM1808), and / or may implement any of the functions, features, and / or benefits described with respect to some embodiments described herein. The virtualization layer 1806 may present VM1808 with a virtual operating platform that looks like networking hardware.

[0147] VM1808 provides virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by the corresponding virtualization layer 1806. Different embodiments of instances of virtual appliance 1802 may be implemented on one or more of VM1808, and the implementation may be carried out in different ways. Hardware virtualization is referred to as network function virtualization (NFV) in several contexts. NFV can be used to consolidate many types of network equipment onto industry-standard high-volume server hardware, physical switches, and physical storage, which may reside in data centers and customer premises equipment.

[0148] In the context of NFV, VM1808 can be a software implementation of a physical machine, where programs run as if they were running on a physical, non-virtualized machine. Each VM1808 and its portion of the hardware 1804 on which it runs, whether that hardware is dedicated to the VM and / or shared by that VM with other VMs in the VM, form a separate virtual network element. Furthermore, in the context of NFV, the virtual network function is responsible for handling specific network functions running in one or more VM1808s on the hardware 1804, and corresponds to application 1802.

[0149] Hardware 1804 may be implemented in a standalone network node with general or specific components. Hardware 1804 may implement some functions through virtualization. Alternatively, hardware 1804 may be part of a larger cluster of hardware (such as in a data center or CPE) where many hardware nodes cooperate and are managed via management and orchestration 1810, which oversees the lifecycle management of applications 1802. In some embodiments, hardware 1804 is coupled to one or more radio units, each including one or more transmitters and one or more receivers, which may be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more suitable network interfaces and may be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station. In some embodiments, some signaling may be provided using a control system 1812, which may be used alternatively for communication between hardware nodes and radio units.

[0150] As can be seen, the concepts described above can be used for efficient handling of route switching in U2N relay scenarios. In particular, data loss can be avoided without relying on E2D feedback mechanisms.

[0151] It should be understood that the examples and embodiments described above are illustrative only and open to various modifications. For example, the concepts presented may apply to various types of communication technologies, not necessarily limited to wireless communication. Furthermore, it should be understood that the above concepts may be implemented by using correspondingly designed software to be executed by one or more processors in existing devices or apparatus, or by using dedicated device hardware. In addition, it should be noted that each of the apparatuses or devices presented may be implemented as a single device or as a system of multiple interacting devices or modules.

[0152] The computing devices described herein (e.g., UEs, network nodes, hosts) may include the shown combinations of hardware components, but other embodiments may comprise computing devices with different combinations of components. It should be understood that these computing devices may comprise any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determining, calculating, acquiring, or similar operations described herein may be performed by processing circuits, which may process information by, for example, converting acquired information to other information, comparing acquired or converted information to information stored in a network node, and / or performing one or more operations based on the acquired or converted information and as a result of the decisions made by the processing. Furthermore, although components are shown as a single box located within a larger box, or as a single box nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that constitute a single shown component, and functions may be separated between the distinct components. For example, a communication interface may be configured to include any of the components described herein, and / or the functions of those components may be separated between the processing circuit and the communication interface. In another example, the non-computation-intensive functions of any of such components may be implemented in software or firmware, while the computation-intensive functions may be implemented in hardware.

[0153] In some embodiments, some or all of the functions described herein may be provided by a processing circuit that executes instructions stored in memory, which in some embodiments may be a computer program product in the form of a non-temporary computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by a processing circuit without executing instructions stored in a separate or individual device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, whether or not it executes instructions stored in a non-temporary computer-readable storage medium, the processing circuit may be configured to perform the functions described. The benefits provided by such functions are enjoyed by the processing circuit alone, or by the computing device as a whole, but not limited to other components of the computing device, and / or generally by the end user and the wireless network.

[0154] In light of the foregoing, examples covered by this disclosure include, but are not limited to, the following: Group A example 1. A method performed by a user device (UE), the method comprising communicating with a network node of a wireless communication network via a relay UE, wherein the UE operates as a remote UE having a sidelink connection to the relay UE, and the relay UE has a connection to the network node. 2. Providing user data, To relay user data to a network node, the data is forwarded to the host via transmission to a relay UE. The method described in Example 1, further including the method described in Example 1. Example from Group B 3. A method implemented by a network node of a wireless communication network, the method being: Buffering packets for a remote UE having an indirect connection to a network node through a relay user device (UE) operating as a Layer 2 (L2) relay, in response to the triggering of a route switching procedure for the remote UE, wherein the route switching procedure is an inter-node switch of the remote UE from a network node as the source node to another network node as the target node. Methods that include... 4. The method of Example 3, wherein buffering packets for a remote UE includes buffering one or more packets that are instructed to be successfully transmitted from the network node to the relay UE, rather than discarding them. 5. A method performed by a network node of a wireless communication network, wherein the network node acts as a source node for a remote UE connected to the network node via a relay user device (UE), and the method is Correcting the source node's packet discard behavior with respect to packets for remote UEs by not discarding buffered packets for remote UEs that were instructed to be sent to the relay UE. Methods that include... 6. A method implemented by a gNB operating as a network node of a wireless communication network, the method being: The gNB's central unit-control plane (CU-CP) entity provides instructions to the gNB's CU-user plane (CU-UP) entity, the instructions being provided in response to the triggering of inter-gNB path switching for a remote UE having an indirect connection to the gNB via a relay UE. The CU-UP entity buffers packets for the remote UE in response to the above instructions. Methods that include... 7. Buffering packets for a remote UE is the method of Example 6, which includes holding packets for the remote UE in the gNB's buffer once the gNB has received instructions for successful transmission to the relay UE. 8. The method as described in Example 6 or 7, wherein a CU-CP entity sends the above instructions to a CU-UP entity via an E1 interface between the respective entities. 9. The method according to any one of Examples 6 to 8, wherein the inter-gNB route switching involves a target gNB, and the method subsequently includes forwarding the buffered packets for the remote UE to the target gNB. 10. The method in any one of Examples 6 to 9, wherein, in response to receiving the above instructions, the CU-UP entity starts a timer and, in response to the timer's expiration, discards the buffered packets for the remote UE. 11. The method according to Example 10, wherein the above instructions provided by the CU-CP include the above timer, and the CU-CP determines the duration of buffering. 12. The method used in Example 10 for determining the duration of buffering by CU-UP. 13. The method according to any one of Examples 10 to 12, wherein the CU-UP discards a buffered packet for the remote UE in response to the earlier of the timer expiration or the occurrence of a discard trigger. 14. The method of Example 13, wherein the discard trigger is one or more of the following: receiving a discard command from a CU-CP entity, or receiving a Packet Data Convergence Protocol (PDCP) status report from a target gNB for a remote UE. 15. The method of Example 6, further comprising the CU-UP discarding a buffered packet for a remote UE in response to either forwarding the packet to another gNB or receiving a Packet Data Convergence Protocol (PDCP) report from another gNB. 16. The method according to Example 6, further comprising the CU-UP discarding a buffered packet for a remote UE in response to reaching a specified time limit for buffering the packet, wherein the time limit is determined for buffering. 17. The method of Example 6, which includes temporarily modifying the packet discarding behavior of a CU-UP entity so that buffering packets for a remote UE does not cause the CU-UP entity to discard packets that are being held in the CU-UP entity's buffer for a remote UE in response to instructions for the successful transmission of those packets to a relay UE. 18. The method as in Example 17, wherein the above instructions include an ACK from the lower protocol level of the CU-UP entity or are provided via Downlink Data Delivery Status (DDDS) information. 19. Obtaining user data, Forwarding user data to the host or remote UE and The method described in any one of Examples 6 to 18, further including the method described in any one of Examples 6 to 18. Example of Group C 20. User equipment, A processing circuit configured to perform one of the steps described in any one of the examples in Group A, A power supply circuit configured to supply power to the processing circuit and User equipment equipped with these features. 21. A network node, A processing circuit configured to perform one of the steps described in any one of the examples in Group B, A power supply circuit configured to supply power to the processing circuit and A network node equipped with these features. 22. User equipment (UE), An antenna configured to send and receive wireless signals, A wireless front-end circuit connected to an antenna and a processing circuit, configured to adjust the signals communicated between the antenna and the processing circuit, The processing circuit is configured to perform one of the steps described in any one of the examples in Group A. Wireless front-end circuitry, An input interface connected to a processing circuit and configured to allow information input to the UE to be processed by the processing circuit, An output interface connected to a processing circuit and configured to output information from the UE processed by the processing circuit, A battery and a processing circuit connected to the UE, configured to supply power to the UE. User equipment (UE) equipped with these features. 23. A host configured to operate in a communication system for providing over-the-top (OTT) services, wherein the host is A processing circuit configured to provide user data, A network interface configured to initiate the transmission of user data to a network node in a cellular network for transmission to a user device (UE), wherein the network node has a communication interface and a processing circuit, and the processing circuit of the network node is configured to perform any of the operations described in any one of the examples in Group B in order to transmit user data from a host to a UE. A host equipped with these features. twenty four. The host's processing circuit is configured to run a host application that provides user data. The UE includes processing circuitry configured to run a client application associated with the host application in order to receive user data transmitted from the host. The host described in Example 23. 25. A method implemented on a host configured to operate in a communication system further including network nodes and user equipment (UE), the method being: To provide user data for UE, Initiating a transmission to transport user data to a UE via a cellular network comprising network nodes, wherein the network node performs one of the operations described in any one of the examples in Group B in order to transmit user data from a host to a UE. Methods that include... 26. The method of Example 25, further comprising transmitting user data provided by the host for the UE at a network node. 27. The method according to Example 25 or 26, wherein user data is provided on the host by running a host application that interacts with a client application running on the UE, and the client application is related to the host application. 28. A communication system configured to provide over-the-top (OTT) services, wherein the communication system is Being a host, A processing circuit configured to provide user data for a user equipment (UE), wherein the user data relates to over-the-top services, and the processing circuit is configured to provide user data for a user equipment (UE). A network interface configured to initiate the transmission of user data to a cellular network node for transmission to a UE, wherein the network node has a communication interface and a processing circuit, and the processing circuit of the network node is configured to perform any of the operations described in any one of the examples of Group B in order to transmit user data from the host to the UE. A communication system that includes a host. 29. Network nodes, and / or UE The communication system described in Example 28, further comprising the features described therein. 30. A host configured to operate in a communication system for providing over-the-top (OTT) services, wherein the host is A processing circuit configured to initiate the reception of user data, A network interface configured to receive user data from a network node in a cellular network, wherein the network node has a communication interface and a processing circuit, and the processing circuit of the network node is configured to perform any of the operations described in any one of the examples in Group B in order to receive user data from a user equipment (UE) on behalf of a host. A host equipped with these features. 31. The host processing circuit is configured to run a host application that receives user data. The host application is configured to interact with a client application running on the UE, and the client application is related to the host application. The host described in Example 30. 32. A host as described in Example 30 or 31, initiating the reception of user data includes requesting user data. 33. A method implemented by a host configured to operate in a communication system further including network nodes and user equipment (UE), the method being: Initiating reception of user data from the UE on a host, wherein the user data originates from a transmission received by the network node from the UE, and the network node initiates reception by performing one of the steps described in any one of the examples in Group B in order to receive user data from the UE for the host. Methods that include... 34. The method of Example 33, further comprising transmitting the received user data to a host at a network node. 35. A host configured to operate in a communication system for providing over-the-top (OTT) services, wherein the host is A processing circuit configured to provide user data, A network interface configured to initiate the transmission of user data to a cellular network for transmission to a user device (UE), wherein the UE comprises a communication interface and a processing circuit, and the UE's communication interface and processing circuit are configured to perform any of the operations described in any one of the examples in Group A in order to receive user data from a host. A host equipped with these features. 36. The host described in Example 35, further including network nodes configured to communicate with the UE in order to send user data from the host to the UE. 37. The host processing circuit is configured to execute the host application and thereby provide user data. The host application is configured to interact with a client application running on the UE, and the client application is related to the host application. The host described in Example 35 or 36. 38. A method implemented by a host operating in a communication system further including network nodes and user equipment (UE), the method being: To provide user data for UE, Initiating a transmission to transport user data to a UE via a cellular network comprising network nodes, wherein the UE performs one of the actions described in any one of the examples in Group A in order to receive user data from a host. Methods that include... 39. On the host, the host application is executed in relation to the client application running on the UE in order to receive user data from the host application. The method described in Example 38, further including the method described in Example 38. 40. On the host, sending input data to a client application running on the UE, wherein the input data is provided by running the host application. It further includes, The method according to Example 39, wherein user data is provided by the client application in response to input data from the host application. 41. A host configured to operate in a communication system for providing over-the-top (OTT) services, wherein the host is A processing circuit configured to provide user data, A network interface configured to initiate the transmission of user data to a cellular network for transmission to a user device (UE), wherein the UE comprises a communication interface and a processing circuit, and the UE's communication interface and processing circuit are configured to perform any of the steps described in any one of the examples in Group A in order to transmit user data to a host. A host equipped with these features. 42. The host described in Example 41, further including network nodes configured to communicate with the UE in order to send user data from the UE to the host. 43. The host processing circuit is configured to execute the host application and thereby provide user data. The host application is configured to interact with a client application running on the UE, and the client application is related to the host application. The host described in Example 41 or 42. 44. A method implemented by a host configured to operate in a communication system further including network nodes and user equipment (UE), the method being: Receiving user data on a host, which has been sent to the host by a UE via a network node, wherein the UE performs one of the steps described in any one of the examples in Group A in order to send the user data to the host. Methods that include... 45. On the host, in order to receive user data from the UE, the host application related to the client application running on the UE is executed. The method described in Example 44, further including the method described in Example 44. 46. On the host, sending input data to a client application running on the UE, wherein the input data is provided by running the host application. It further includes, The method described in Example 44 or 45, wherein user data is provided by the client application in response to input data from the host application.

Claims

1. A method carried out by a wireless communication network gNB (12; 56-1, 56-2; 56), wherein the method is In response to the triggering of inter-gNB path switching for a remote UE (14) having an indirect connection to the gNB (12;56-1, 56-2;56) via a relay user device (UE) (20), the central unit-user plane (CU-UP) entity (72) of the gNB (12;56-1, 56-2;56) receives instructions from the central unit-control plane (CU-CP) entity (70) of the gNB (12;56-1, 56-2;56), In response to the aforementioned instruction, the CU-UP entity (72) buffers packets for the remote UE (14) Methods that include...

2. The method according to claim 1, wherein buffering packets for the remote UE (14) includes modifying the packet discarding behavior of the CU-UP entity (72) such that the CU-UP entity (72) does not discard packets that are being held in the buffer of the CU-UP entity (72) for the remote UE (14) in response to instructions for the successful transmission of those packets to the relay UE (20).

3. The method according to claim 2, wherein the instruction for a successful transmission is provided via downlink data delivery status (DDDS) information.

4. The method according to claim 2 or 3, wherein the instruction for a successful transmission includes an acknowledgment from a lower protocol level of the CU-UP entity (72).

5. The method according to any one of claims 1 to 4, wherein buffering the packet for the remote UE(14) includes holding the packet after the gNB(12; 56-1, 56-2; 56) has received instructions for successful transmission to the relay UE(20).

6. The method according to any one of claims 1 to 5, wherein the CU-UP entity (72) receives the instruction via the E1 interface.

7. The method according to any one of claims 1 to 6, wherein the inter-gNB route switching involves a target gNB (24), and the method subsequently includes forwarding the buffered packets for the remote UE (14) to the target gNB (24).

8. The method according to any one of claims 1 to 7, wherein, in response to receiving the instruction, the CU-UP entity (72) starts a timer, and in response to the expiration of the timer, discards the buffered packets for the remote UE (14).

9. The method according to claim 8, wherein the instruction includes setting the timer.

10. The method according to claim 8 or 9, wherein the CU-UP entity (72) discards the buffered packet for the remote UE (14) in response to the earlier of the expiration of the timer or the occurrence of a discard trigger.

11. The method according to claim 10, wherein the discard trigger is one or more of receiving a discard command from the CU-CP entity or receiving a Packet Data Convergence Protocol (PDCP) status report from the target gNB (24) for the remote UE (14).

12. The method according to any one of claims 1 to 11, wherein the CU-UP entity (72) determines the duration of buffering.

13. The method according to any one of claims 1 to 12, further comprising the CU-UP entity (72) discarding the packet buffered for the remote UE (14) in response to either forwarding the packet to another gNB (24) or receiving a PDCP report from another gNB (24).

14. The method according to any one of claims 1 to 13, further comprising the CU-UP entity (72) discarding the buffered packets for the remote UE (14) in response to reaching a specified time limit for buffering.

15. A method carried out by a wireless communication network gNB (12; 56-1, 56-2; 56), wherein the method is In response to the triggering of inter-gNB path switching for a remote UE (14) having an indirect connection to the gNB (12;56-1, 56-2;56) via a relay user device (UE) (20), the central unit-control plane (CU-CP) entity (70) of the gNB (12;56-1, 56-2;56) provides instructions to the central unit-user plane (CU-UP) entity (72) of the gNB (12;56-1, 56-2;56). Includes, A method by which the instruction causes the CU-UP entity to buffer packets for the remote UE.

16. The method according to claim 15, wherein buffering packets for the remote UE (14) includes modifying the packet discarding behavior of the CU-UP entity (72) such that the CU-UP entity (72) does not discard packets that are kept in the buffer of the CU-UP entity (72) for the remote UE (14) in response to an instruction for the successful transmission of those packets to the relay UE (20).

17. The method according to claim 16, wherein the instruction for a successful transmission is provided via downlink data delivery status (DDDS) information.

18. The method according to claim 16 or 17, wherein the instruction for a successful transmission includes an acknowledgment from a lower protocol level of the CU-UP entity (72).

19. The method according to any one of claims 15 to 18, wherein buffering the packet for the remote UE(14) includes holding the packet for which the gNB(12;56-1,56-2;56) has received instructions for successful transmission to the relay UE(14).

20. The method according to any one of claims 15 to 19, wherein the CU-CP entity (70) provides the instructions via the E1 interface.

21. The method according to any one of claims 15 to 20, wherein the inter-gNB route switching involves a target gNB (24), and the buffering subsequently includes forwarding the buffered packets for the remote UE (14) to the target gNB (24).

22. A network node (1410A, 1410B; 1600) is configured to perform the operation of a gNB (12; 56-1, 56-2; 56) of a wireless communication network, and the operation is, In response to the triggering of inter-gNB path switching for a remote UE (14) having an indirect connection to the gNB (12;56-1, 56-2;56) via a relay user device (UE) (20), the central unit-user plane (CU-UP) entity (72) of the gNB (12;56-1, 56-2;56) receives instructions from the central unit-control plane (CU-CP) entity (70) of the gNB (12;56-1, 56-2;56), In response to the aforementioned instruction, the CU-UP entity (72) buffers packets for the remote UE (14) Network nodes including (1410A, 1410B; 1600).

23. A network node (1410A, 1410B; 1600) according to claim 22, further configured to perform operations according to any one of claims 2 to 14.

24. A processing circuit (30; 1602) configured to carry out the method described in any one of claims 1 to 14, A power supply circuit (1608) configured to supply power to the processing circuit (30; 1602) and A network node (1410A, 1410B; 1600) according to claim 22 or 23, comprising the above.

25. A network node (1410A, 1410B; 1600) is configured to perform the operation of a gNB (12; 56-1, 56-2; 56) of a wireless communication network, and the operation is, In response to the triggering of inter-gNB path switching for a remote UE (14) having an indirect connection to the gNB (12;56-1, 56-2;56) via a relay user device (UE) (20), the central unit-control plane (CU-CP) entity (70) of the gNB (12;56-1, 56-2;56) provides instructions to the central unit-user plane (CU-UP) entity (72) of the gNB (12;56-1, 56-2;56). Includes, The instructions cause the CU-UP entity (72) to buffer packets for the remote UE (14) on the network nodes (1410A, 1410B; 1600).

26. A network node (1410A, 1410B; 1600) according to claim 25, further configured to perform operations according to the method described in any one of claims 16 to 21.

27. A processing circuit (30; 1602) configured to carry out the method described in any one of claims 15 to 21, A power supply circuit (1608) configured to supply power to the processing circuit (30; 1602) and A network node (1410A, 1410B; 1600) according to claim 25 or 26, comprising the above.

28. A computer program or computer program product comprising program code to be executed by a processing circuit of a network node for a communication network, wherein the execution of the program code by the processing circuit causes the network node to carry out the method according to any one of claims 1 to 14.

29. A computer program or computer program product comprising program code to be executed by a processing circuit of a network node for a communication network, wherein the execution of the program code by the processing circuit causes the network node to carry out the method according to any one of claims 15 to 21.