Network coding handover between network coding devices

Abstract

Methods, systems, and devices for wireless communication are described. A first network coding device can determine to hand over a retransmission of a packet (e.g., a task to retransmit the packet) to a second network coding device, and the first network coding device can perform the handover using techniques described herein. In one aspect, the first network coding device can send a negative acknowledgement (NACK) to a user equipment (UE) that initially sends the packet, and the UE can send a request to take over a retransmission of the packet for any of the one or more network coding devices. In another aspect, the first network coding device can send a request to take over a retransmission of the packet for any of the one or more network coding devices.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. patent application No. 17 / 858,918, entitled “NETWORK CODING HANDOVER BETWEEN NETWORK CODING DEVICES,” filed by Liu et al. on July 6, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including network decoding handover between network decoding devices. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems), and fifth generation (5G) systems, which may be referred to as new radio (NR) systems. These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM).

[0005] A wireless multiple access communication system may include one or more network entities, each of which supports wireless communication of communication devices, which may be referred to as user equipment (UE). Some wireless communication systems may support retransmission of packets by a sending wireless device (e.g., a user equipment (UE) or a roadside unit (RSU)) to improve the chances of the packet being successfully received by one or more receiving wireless devices. In such systems, if a subset of one or more receiving wireless devices fails to receive a packet, the sending wireless device may be triggered to retransmit the packet. Improved techniques for retransmitting one or more packets in a wireless communication system may be desirable. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices, and apparatuses for supporting network decoding handover between network decoding devices. A first network decoding device is capable of determining to hand over the retransmission of a packet (e.g., the task of retransmitting the packet) to a second network decoding device, and the first network decoding device is capable of using the technology described herein to perform the handover. In one aspect, the first network decoding device may send a negative acknowledgement (NACK) to a user equipment (UE) (e.g., a source UE) that originally sent the packet, and the source UE may send a request to any one of one or more network decoding devices to take over the retransmission of the packet. In another aspect, the first network decoding device is capable of sending a request to any one of one or more network decoding devices to take over the retransmission of the packet. Because the first network decoding device can hand over the retransmission of the packet to the second network decoding device, if the target UE continues to fail to receive the packet, the first network decoding device can avoid repeatedly retransmitting the packet, thereby reducing overhead in the wireless communication system.

[0007] A method for wireless communication at a UE is described. The method includes: sending a first request to a network decoding device to retransmit a packet originally sent by the UE; receiving an acceptance message from a first network decoding device indicating that the first network decoding device is to retransmit the packet; receiving a negative acknowledgement from the first network decoding device triggering a handover of the retransmission of the packet from the first network decoding device; and sending a second request to the network decoding device to retransmit the packet originally sent by the UE based on receiving the negative acknowledgement.

[0008] An apparatus for wireless communication at a UE is described. The apparatus includes a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: send a first request to a network decoding device to retransmit a packet originally sent by the UE; receive an acceptance message from a first network decoding device indicating that the first network decoding device is to retransmit the packet; receive a negative acknowledgement from the first network decoding device that triggers a handover of the retransmission of the packet from the first network decoding device; and send a second request to the network decoding device to retransmit the packet originally sent by the UE based on receiving the negative acknowledgement.

[0009] Another apparatus for wireless communication at a UE is described. The apparatus includes: means for sending a first request to a network decoding device to retransmit a packet originally sent by the UE; means for receiving an acceptance message from the first network decoding device indicating that the first network decoding device is to retransmit the packet; means for receiving a negative acknowledgement from the first network decoding device triggering a handover of the retransmission of the packet from the first network decoding device; and means for sending a second request to the network decoding device to retransmit the packet originally sent by the UE based on receiving the negative acknowledgement.

[0010] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code includes instructions executable by a processor to perform the following operations: sending a first request to a network decoding device to retransmit a packet originally sent by the UE; receiving an acceptance message from a first network decoding device indicating that the first network decoding device is to retransmit the packet; receiving a negative confirmation from the first network decoding device triggering a handover of the retransmission of the packet from the first network decoding device; and sending a second request to the network decoding device to retransmit the packet originally sent by the UE based on receiving the negative confirmation.

[0011] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: sending a packet to one or more UEs; and determining that at least one of the one or more UEs failed to receive a packet from the UE, wherein sending a first request to the network decoding device to resend the packet may be based on the determination. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: sending an indication in a second request to the second network decoding device to resend the packet originally sent by the UE.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: sending an indication to at least one network decoding device to avoid retransmitting a packet originally sent by the UE in a second request. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: storing the packet in a buffer at the UE, wherein sending a second request to the network decoding device to retransmit the packet may be based on storing the packet in a buffer at the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first request to the network decoding device to retransmit the packet may be included in the first retransmission of the packet from the UE, and the second request to the network decoding device to retransmit the packet may be included in the second retransmission of the packet from the UE.

[0013] A method for wireless communication at a first network decoding device is described. The method includes: receiving a first request to the first network decoding device to retransmit a packet originally sent by a UE; sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet; determining to hand over the retransmission of the packet; and sending a negative acknowledgement to the UE based on the determination to trigger the handover of the retransmission of the packet from the first network decoding device to a second network decoding device.

[0014] An apparatus for wireless communication at a first network decoding device is described. The apparatus includes a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receive a first request to the first network decoding device to retransmit a packet originally sent by a UE; send an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet; determine to hand over the retransmission of the packet; and based on the determination, send a negative acknowledgement to the UE triggering the handover of the retransmission of the packet from the first network decoding device to a second network decoding device.

[0015] Another apparatus for wireless communication at a first network decoding device is described. The apparatus includes: means for receiving a first request to the first network decoding device to retransmit a packet originally sent by a UE; means for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet; means for determining to hand over the retransmission of the packet; and means for sending a negative acknowledgement to the UE triggering handover of the retransmission of the packet from the first network decoding device to a second network decoding device based on the determination.

[0016] A non-transitory computer-readable medium storing code for wireless communication at a first network decoding device is described. The code includes instructions executable by a processor to: receive a first request to the first network decoding device to retransmit a packet originally sent by a UE; send an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet; determine to hand over the retransmission of the packet; and send a negative acknowledgement to the UE based on the determination to trigger the handover of the retransmission of the packet from the first network decoding device to a second network decoding device.

[0017] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving a second request for the first network decoding device to retransmit a packet originally sent by the UE; and ignoring the second request based on determining the retransmission of the handover packet. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: determining that a first network decoding device in a set of multiple network decoding devices may be closest to the UE, wherein sending an acceptance message to the UE may be based on determining that the first network decoding device may be closest to the UE.

[0018] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving an indication of the location of each network decoding device in a set of multiple network decoding devices, wherein determining that the first network decoding device may be closest to the UE may be based on receiving an indication of the location of each network decoding device in the set of multiple network decoding devices. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of the location of each network decoding device may be received in a sidelink control information message, a medium access control control element, or a radio resource control message.

[0019] A method for wireless communication at a first network decoding device is described. The method includes: receiving a first request to the first network decoding device to retransmit a packet originally sent by a UE; sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet; determining to hand over the retransmission of the packet; and sending a second request to a second network decoding device to retransmit the packet based on the determination.

[0020] An apparatus for wireless communication at a first network decoding device is described. The apparatus includes a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receive a first request to the first network decoding device to retransmit a packet originally sent by a UE; send an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet; determine to hand over the retransmission of the packet; and send a second request to a second network decoding device to retransmit the packet based on the determination.

[0021] Another apparatus for wireless communication at a first network decoding device is described. The apparatus includes: means for receiving a first request to the first network decoding device to retransmit a packet originally sent by a UE; means for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet; means for determining to hand over the retransmission of the packet; and means for sending a second request to a second network decoding device to retransmit the packet based on the determination.

[0022] A non-transitory computer-readable medium storing code for wireless communication at a first network decoding device is described. The code includes instructions executable by a processor to perform the following operations: receiving a first request to the first network decoding device to retransmit a packet originally sent by a UE; sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet; determining to hand over the retransmission of the packet; and sending a second request to a second network decoding device to retransmit the packet based on the determination.

[0023] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: sending an indication to the second network decoding device to retransmit the packet in a second request based on the load of the second network decoding device. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving an indication of the load of the second network decoding device from the second network decoding device.

[0024] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: monitoring the transmissions from the second network decoding device to determine the number and size of transmissions from the second network decoding device; and determining the load of the second network decoding device based on the monitoring. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: determining that the second network decoding device sends another acceptance message to the UE to resend the packet; and determining that the second network decoding device may have stored the packet based on the second network decoding device sending another acceptance message to the UE to resend the packet.

[0025] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: sending an indication to the second network decoding device to retransmit the packet in a second request based on the second network decoding device being closest to the UE in the set of multiple network decoding devices. Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving an indication of the location of each network decoding device in the set of multiple network decoding devices; and determining that the second network decoding device in the set of multiple network decoding devices may be closest to the UE based on receiving an indication of the location of each network decoding device in the set of multiple network decoding devices.

[0026] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, an indication of the location of each network decoding device may be received in a sidelink control information message, a medium access control control element, or a radio resource control message. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: sending an indication in a second request to the second network decoding device to retransmit the packet based on determining that the second network decoding device may have stored the packet in a buffer.

[0027] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: sending an indication in the second request to the second network decoding device to retransmit the packet; and sending the packet to the second network decoding device based on determining that the packet may be lost from the buffer at the second network decoding device. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: sending an indication in the second request to a group of network decoding devices, each network decoding device in the group is a candidate for retransmitting the packet.

[0028] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending a second request for retransmission of a packet may include operations, features, components, or instructions for the following actions: retransmitting a packet originally sent by the UE together with the second request for retransmission of the packet. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending a second request for retransmission of a packet may include operations, features, components, or instructions for the following actions: sending a control message together with the second request for retransmission of the packet to a second network decoding device. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the control message includes a sidelink control information message, a medium access control control element, or a radio resource control message. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 An example of a wireless communication system supporting network coding handover between network coding devices according to one or more aspects of the present disclosure is illustrated.

[0030] Figure 2 An example of retransmission using network coding in accordance with one or more aspects of the present disclosure is illustrated.

[0031] Figure 3 An example of a process flow according to one or more aspects of the present disclosure is illustrated.

[0032] Figure 4 An example of a wireless communication system supporting network coding handover between network coding devices according to one or more aspects of the present disclosure is illustrated.

[0033] Figure 5 An example of a process flow for supporting network coding handover between network coding devices according to one or more aspects of the present disclosure is illustrated.

[0034] Figure 6 An example of a process flow for supporting network coding handover between network coding devices according to one or more aspects of the present disclosure is illustrated.

[0035] Figure 7 and Figure 8 A block diagram of a device supporting network coding handover between network coding devices according to one or more aspects of the present disclosure is shown.

[0036] Fig. 9 A block diagram of a communication manager that supports network coding handoff between network coding devices is shown in accordance with one or more aspects of the present disclosure.

[0037] Fig.10 A diagram of a system including a device supporting network coding handover between network coding devices in accordance with one or more aspects of the present disclosure is shown.

[0038] Fig.11 and Fig.12 A block diagram of a device supporting network coding handover between network coding devices according to one or more aspects of the present disclosure is shown.

[0039] Fig.13 A block diagram of a communication manager that supports network coding handoff between network coding devices is shown in accordance with one or more aspects of the present disclosure.

[0040] Fig.14 A diagram of a system including a device supporting network coding handover between network coding devices in accordance with one or more aspects of the present disclosure is shown.

[0041] Figures 15 to 17 A flow chart illustrating a method of supporting network coding handover between network coding devices according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0042] Some wireless communication systems may support retransmission of packets by a transmitting device (e.g., a user equipment (UE) or a roadside unit (RSU)) to increase the chance that the packet is successfully received by one or more receiving devices. However, in such systems, the overhead associated with retransmitting packets may be high. In order to minimize the overhead, the wireless communication system may include network decoding devices that can aggregate packets from multiple wireless devices in a single retransmission. Therefore, the overhead of retransmissions in the wireless communication system can be reduced. However, in some cases, the network decoding device may repeatedly attempt to retransmit packets even if one or more target devices may continue to fail to receive the packet. In such cases, the reduction in the overhead associated with retransmissions using the network decoding device may be offset, and the overhead of retransmissions in the wireless communication system may remain high.

[0043] As described herein, a wireless communication system may support effective techniques for network decoding handover between network decoding devices (e.g., encoders). In some cases (e.g., after multiple failed retransmissions of a packet), a first network decoding device may determine to hand over the retransmission of a packet (e.g., the task of retransmitting a packet) to a second network decoding device, and the first network decoding device may use the techniques described herein to perform the handover. In one aspect, the first network decoding device may send a negative acknowledgement (NACK) to a user equipment (UE) (e.g., a source UE) that originally sent the packet, and the source UE may send a request to any one of one or more network decoding devices to take over the retransmission of the packet. In another aspect, the first network decoding device is capable of sending a request to any one of one or more network decoding devices to take over the retransmission of the packet. Because the first network decoding device can hand over the retransmission of the packet to the second network decoding device, if the target UE continues to fail to receive the packet, the first network decoding device can avoid repeatedly retransmitting the packet, thereby reducing overhead in the wireless communication system.

[0044] Various aspects of the present disclosure are first described in the context of a wireless communication system. Examples of processes and signaling exchanges that support network decoding handover between network decoding devices are then described. Various aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to network decoding handover between network decoding devices.

[0045] Figure 1 An example of a wireless communication system 100 that supports network decoding handover between network decoding devices according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 includes one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0046] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices in different forms or with different capabilities. In different examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0047] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0048] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

[0049] In some examples, the network entities 105 may communicate with the core network 130, or communicate with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other on the backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), and other examples or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0050] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0051] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0052] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.

[0053] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0054] Where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support a network decoding handover between network decoding devices as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0055] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0056] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 as shown in .

[0057] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a defined physical layer structure to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send", "receive", or "communicate" when referring to the network entity 105 may refer to any part of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0058] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be located according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0059] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115 (e.g., in a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH)), uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105 (e.g., in a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH)), or both, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry downlink communications and uplink communications (e.g., in TDD mode).

[0060] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communication on a particular carrier bandwidth or may be configurable to support communication on one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0061] The signal waveform sent on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0062] One or more parameter sets for a carrier may be supported, where the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications for a UE 115 may be limited to one or more active BWPs.

[0063] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0064] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0065] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0066] Physical channels may be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0067] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., on a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0068] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to a macro cell), and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with a small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications on one or more cells.

[0069] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0070] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0071] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may allow automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0072] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not support concurrent transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UE 115 include entering a power saving deep sleep mode when not engaged in active communications, operating over a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

[0073] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0074] In some examples, a UE 115 may be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), and the one or more UEs may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each other UE 115 in the group. In some examples, the network entity 105 may facilitate scheduling resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0075] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with the network using vehicle-to-network (V2N) communication via one or more network nodes (e.g., network entity 105, base station 140, RU 170), or both.

[0076] In some cases, the network entity 105 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink communications are performed between these UEs 115 without the participation of the network entity 105. According to some aspects, the sidelink communications may include the transmission of discovery expressions on a physical sidelink discovery channel (PSDCH) (e.g., to allow neighboring devices to discover each other's presence). According to some aspects, the sidelink communications may include the transmission of control information on a physical sidelink control channel (PSCCH). According to some aspects, the sidelink communications may include the transmission of data on a physical sidelink shared channel (PSSCH). According to some aspects, the sidelink communications may include the transmission of feedback on a physical sidelink feedback channel (PSFCH).

[0077] According to some aspects, the sidelink communication may include LTE V2X or cellular V2X (C-V2X), NR V2X or C-V2X, and NR sidelink. In NR-V2X, two modes may be defined for resource allocation. In a first mode (e.g., Mode 1), the network entity 105 may determine the resources used by the sidelink transmitting UE 115 for sidelink transmission (e.g., on PSCCH, PSSCH, or PSFCH). In a second mode (e.g., Mode 2), the sidelink transmitting UE (e.g., not the network entity 105) may determine the resources used for sidelink communication. For the second mode, procedures related to sensing and resource selection and reselection may be supported. Sensing procedures may be defined as decoding sidelink control information (SCI) from other UEs 115 and / or performing sidelink measurements. Decoding the SCI in the sensing procedure may provide at least some information about the sidelink resources indicated by the UE 115 that transmits the SCI.

[0078] NR-V2X may support initial transmission of a transport block from a sidelink UE 115 without reservation based on a sensing and resource selection procedure. NR-V2X may support reserving sidelink resources for initial transmission of a transport block based on a sensing and resource selection procedure at least through SCI associated with different transport blocks. In some cases, NR-V2X Mode 2 may support resource reservation for feedback-based PSSCH retransmissions (e.g., where the feedback may affect subsequent sensing and resource selection procedures) through signaling associated with a previous transmission of the same transport block. From the perspective of the transmitting sidelink UE 115, the use of hybrid automatic repeat request (HARQ) feedback to release unused resources may be supported (e.g., no additional signaling is defined for the purpose of releasing unused resources by the transmitting UE 115). Additionally, in Mode 2, the SCI payload may indicate subchannels and time slots used by the UE 115 or reserved by the UE 115 for PSSCH transmission or retransmission.

[0079] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity for managing access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity for routing packets or interconnecting to an external network (e.g., a serving gateway (S-GW)), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0080] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is approximately one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide service to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0081] The wireless communication system 100 may also operate in the ultra-high frequency (SHF) region (also known as the centimeter band) using a frequency band of 3 GHz to 30 GHz or in the extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as the millimeter band) of the spectrum. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and network entity 105 (e.g., base station 140, RU170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater atmospheric attenuation and shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0082] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands may be based on carrier aggregation configurations (e.g., LAA) in conjunction with component carriers operating in licensed bands. Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0083] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having antenna ports of a set of rows and columns that the network entity 105 can use to support beamforming for communication with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0084] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0085] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication of the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate on a logical channel. The MAC layer may perform priority processing and multiplexing of logical channels into transport channels. The MAC layer may also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer of user plane data between a UE 115 and a network entity 105 or a core network 130. At the PHY layer, a transport channel may be mapped to a physical channel.

[0086] UE 115 and network entity 105 may support retransmission of data to increase the possibility of data being successfully received. HARQ feedback is a technique for increasing the possibility of correctly receiving data through a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0087] In some cases, because the wireless communication system 100 can support retransmissions of packets by a transmitting device, the overhead in the wireless communication system 100 can increase as the number of transmitting devices in the wireless communication system 100 increases. In order to minimize the overhead, the wireless communication system 100 can include network decoding devices that can aggregate packets from multiple wireless devices in a single retransmission. Thus, multiple retransmissions can be replaced by a single retransmission using network decoding, and the overhead of retransmissions in the wireless communication system 100 can be reduced.

[0088] Figure 2 An example of retransmission 200 using network coding according to one or more aspects of the present disclosure is illustrated. Network coding may refer to encoding multiple packets to generate a single transmission at a network coding device, where each of the multiple packets may be associated with a communication of a different UE 115 (e.g., previously transmitted by a different UE 115). Network coding may be used to increase system capacity and improve resource utilization. Increased system capacity and improved resource utilization may be achieved by reducing the number of retransmissions in the system while maintaining performance metrics. Network coding may enable an increase in the number of UEs 115 or an increase in the traffic per UE 115. As illustrated in the first example 200-a, one or more source UEs 115 (e.g., UE0 and UE1) may transmit packets (e.g., Tx 10 ... a and Tx b ). Then, in the second example 200-b, the network decoding device may retransmit the packet to the one or more target UEs 115. That is, after the initial or original transmission, the retransmission by the source transmitter may be replaced by the retransmission by the network decoding device. The retransmission by the network decoding device may be a function of the original transmission from the one or more source UEs 115 (e.g., f(Tx a ,Tx b )). The network decoding device may be a network entity 105, an RSU or a UE 115.

[0089] In one example of network decoding, a single parity check code can correct for one erasure of a packet. For example, an input of [a,b,c] can be encoded as is then sent, where a, b, and c each correspond to a different packet. The receiving device can then recover an erasure from the network decoding transmission. In particular, if the received vector is The erased element (e.g., b) can be accessed by modifying other elements (e.g., ) are summed to recover. According to Equation 1 below, network decoding can be viewed as a linear system (e.g., on a Galois field) with three variables and four linearly independent constraints. Any three constraints (e.g., one erasure) may be sufficient to find these three variables. Therefore, a single network decoding transmission or encoding sequence from a network decoding device may replace multiple retransmissions or encoding sequences from multiple wireless devices.

[0090]

[0091] Figure 3 An example of a process flow 300 according to one or more aspects of the present disclosure is illustrated. The process flow 300 may be an example protocol using network decoding for sidelink communication. The process flow 300 includes UE 115-a and UE 115-b, which may be reference Figure 1 and Figure 2 The process flow 300 also includes a network decoding device 305, which can be a reference Figure 1 and Figure 2 An example of a network decoding device as described. The network decoding device 305 can be an RSU, a relay, a UE 115, or a network entity 105. At 310, a UE 115-a (e.g., a source UE) can send a packet or a transport block with a network decoding request flag. The network decoding device 305 can receive a packet or a transport block with a network decoding request flag from the UE 115-a, and at 315, the network decoding device 305 can send an acceptance message to the UE 115-a to accept the request (e.g., a request to resend the packet). That is, the network decoding device 305 can transmit a message to accept the request to include the packet as part of the network decoding transmission. At 320, the network decoding device 305 can then send the packet to the UE 115-b in the network decoding transmission.

[0092] In some cases, the network decoding device may repeatedly attempt to retransmit the packet even if one or more wireless devices may continue to fail to receive the packet. In such cases, the reduction in overhead associated with using the network decoding device for retransmission may be offset, and the overhead of retransmission in the wireless communication system may remain high. The wireless communication system 100 may support procedures for handing over packets between network decoding devices (e.g., encoders) for network decoding (e.g., in a mode 2 side link). The network decoding device may take over the retransmission of the packet. In some cases, a packet is taken over by only one network decoding device (such as an RSU), and it may be appropriate for a network decoding device to hand over the packet to another network decoding device or encoder (e.g., for improved transmission). The described techniques may enhance existing procedures and minimize signaling and transmission (e.g., retransmission). For example, the described techniques may minimize the transmission of packets between RSUs.

[0093] Figure 4 An example of a wireless communication system 400 supporting network decoding handover between network decoding devices according to one or more aspects of the present disclosure is illustrated. The wireless communication system 400 includes a first UE 115-c and a second UE 115-d, which may be reference UEs. Figures 1 to 3 The wireless communication system 400 also includes a first network decoding device 405-a and a second network decoding device 405-b, which can be reference Figures 1 to 3 The wireless communication system 400 may implement aspects of the wireless communication system 100. For example, the wireless communication system 400 may support efficient techniques for handing over packets between network decoding devices for network decoding.

[0094] The first UE 115-c may send the packet 410 to the second UE 115-d, and the second UE 115-d may fail to receive or decode the packet 410. The first UE 115-c may then determine to resend the packet 410 to the second UE 115-d using network coding, and the first UE 115-c may send a request for the network coding device to resend the packet 410 to the second UE 115-d. The first network coding device 405-a may send an acceptance message to the first UE 115-c indicating that the first network coding device 405-a is to resend the packet 410 to the second UE 115-d, and the first network coding device 405-a may then proceed to resend the packet 410 to the second UE 115-d. In some cases, after accepting the task of retransmitting packet 410, first network coding device 405-a may determine to hand over the task of retransmitting packet 410, and first network coding device 405-a may perform the handover using techniques described herein.

[0095] In one aspect, the first UE 115-c may send a request for the second network decoding device 405-b to take over retransmission of the packet 410. The first network decoding device 405-a (e.g., RSU) may send a NACK to the first UE 115-c (e.g., source device), and the first UE 115-c may retransmit the packet 410 based on receiving the NACK. The retransmission of the packet 410 from the first UE 115-c may include (e.g., inherently or by default) a request for the second network decoding device 405-b to take over retransmission of the packet 410 (e.g., a request for the retransmission to be taken over by the RSU). Using the NACK to trigger the first UE 115-c to send a request for the second network decoding device 405-b to take over retransmission of the packet 410 can be used for the handover of the packet 410 from the first network decoding device 405-a to the second network decoding device 405-b, and can utilize existing network decoding procedures. The first UE 115 - c may store the packet 410 (eg, a transport block) in its buffer in preparation for retransmitting the packet 410 along with a request for the second network decoding device 405 - b to take over retransmission of the packet 410 .

[0096] In some cases, the header of the retransmission of the packet 410 from the first UE 115-c may include a bit indicating or requesting that the network decoding device take over the retransmission of the packet 410. In addition, in order to hand over the retransmission of the packet 410 to a different device, the header may also include an identifier (e.g., an RSU ID) of a second network decoding device 405-b that is to take over the retransmission of the packet 410, wherein the second network decoding device 405-b is different from the first network decoding device 405-a (e.g., an RSU different from the first RSU). Additionally or alternatively, the header may include one or more identifiers (e.g., RSU IDs) of network decoding devices that may not take over the retransmission of the packet 410 (e.g., network decoding devices that are requested to avoid taking over the retransmission of the packet 410) in order to avoid handing over the packet 410 to a network decoding device (e.g., the first network decoding device 405-a) that has attempted to retransmit the packet 410 (e.g., so as not to hand over the packet 410 to the same RSU where the retransmission of the packet 410 has been unsuccessful).

[0097] In some examples, the first UE 115-c may send a request for a network decoding device to take over the retransmission of the packet 410, the request having an identifier of one or more network decoding devices that are excluded from taking over the retransmission of the packet 410. In some cases, the handover of the packet 410 may indicate that a handover will occur to the network decoding device with the shortest distance from the first UE 115-c (e.g., excluding those indicated by the identifier in the request). In such examples, each network decoding device or encoder may be able to identify its own location (e.g., a global navigation satellite system (GNSS) location) and the location of other network decoding devices (e.g., encoders). Each network decoding device in the wireless communication system 400 may support signaling that broadcasts its location to all other network decoding devices. The signaling may be performed using an SCI-2 format, a MAC control element (MAC-CE), a MAC header or subheader, or an RRC message. Each network decoding device may be able to identify the location of other network decoding devices within a region. For example, in some cases, each network decoding device is responsible for a cell with an explicit boundary.

[0098] In another aspect, the first network decoding device 405-a may send a request for the second network decoding device 405-b to take over retransmission of the packet 410 while retransmitting the packet 410 (e.g., the RSU may include a request for a handover when transmitting the network decoding packet). In this aspect, the second network decoding device 405-b may save the signaling, and if the packet 410 is not stored in a buffer at the second network decoding device 405-b (e.g., the destination RSU), the second network decoding device 405-b may decode the network decoding packet from the first network decoding device (e.g., and possibly other network decoding devices) to identify the packet 410 to be retransmitted. The header of the network decoding packet 410 including the request may include one bit indicating (e.g., triggering) a handover, and may include an identifier of the second network decoding device 405-b that is to take over retransmission of the packet 410 (e.g., an RSU ID indicating which RSU is to take over). In some examples, the first network decoding device 405-a may randomly select or specifically (e.g., based on metrics associated with other network decoding devices) select the second network decoding device 405-b to take over the retransmission of the packet 410. Alternatively, if the first network decoding device 405-a cannot determine which network decoding device to take over the retransmission of the packet 410, the network decoding device that receives the request from the first network decoding device 405-a may determine which network decoding device to take over the retransmission of the packet 410.

[0099] In some cases, the first network decoding device 405-a (e.g., the source RSU) may determine the second network decoding device 405-b (e.g., the best RSU) to take over the retransmission of the packet 410 based on monitoring the load of one or more network decoding devices (e.g., other RSUs), the location of one or more network decoding devices, or the transmission and reception of one or more network decoding devices. In order to identify the load of one or more network decoding devices, one or more network decoding devices may periodically report their average load to the first network decoding device 405-a, or the first network decoding device 405-a may monitor the number and size of network decoding packets transmitted by each of the one or more network decoding devices (e.g., the frequency of transmitting network decoding packets and the size of these packets). In addition, in order to identify the location of the one or more network decoding devices, each of the one or more network decoding devices may support signaling to broadcast its location to all other network decoding devices. Signaling may be performed using an SCI-2 format, a MAC-CE, a MAC header or subheader, or an RRC message.

[0100] Once the first network decoding device 405-a is able to identify the load of one or more network decoding devices, the first network decoding device 405-a can determine whether each of the one or more network decoding devices is sending a packet (e.g., a transport block) that can be effectively combined with the packet 410. In an example, the first network decoding device 405-a can select the second network decoding device 405-b to retransmit the packet 410 to the UE 115-d so that packets of the same size are combined. For example, the network decoding device may attempt to combine longer transport blocks due to the maximum transport block length being sent, and if such a combination can be avoided, combining a short transport block with a long transport block may be inefficient because combining a short transport block with a long transport block may increase overhead. Therefore, in order to allow effective combination of transport blocks to form a network decoding packet, it may be appropriate for the first network decoding device 405-a to identify the transport blocks in the buffers of the other network decoding devices.

[0101] In yet another aspect, the first network decoding device 405-a may explicitly signal other network decoding devices to take over the retransmission of the packet 410. The signaling may be performed using an SCI-2 format, a MAC-CE, or a MAC header or subheader. The signaling may include a bit indicating the handover of the packet 410 for network decoding. The signaling may also include an identifier (e.g., an RSU ID) of the second network decoding device 405-b to take over the retransmission of the packet 410 or an identifier (e.g., a set of RSU IDs) of a group of network decoding devices that are each candidates for taking over the retransmission of the packet 410 (e.g., an RSU may indicate a group of potential destination RSUs).

[0102] If the signaling includes an identifier of the second network decoding device 405-b (e.g., an RSU ID), the first network decoding device 405-a may determine the second network decoding device 405-b (e.g., calculate the best RSU) to take over the retransmission of the packet 410 based on monitoring whether the second network decoding device 405-b has the packet 410 in the buffer, monitoring the load of the second network decoding device 405-b, monitoring the location of one or more network decoding devices including the second network decoding device 405-b, and monitoring the transmission and reception of the second network decoding device 405-b. The first network decoding device 405-a may monitor whether the second network decoding device 405-b has the packet 410 in its buffer by monitoring the network decoding acceptance message transmitted by the other network decoding devices.

[0103] If the signaling includes an identifier of the group of network decoding devices (e.g., a group of RSU IDs), the network decoding devices in the group that determine to take over the retransmission of the packet 410 may transmit a confirmation or acceptance message to the first network decoding device after a backoff (e.g., a random backoff). The earliest (e.g., first in time) network decoding device that sends a confirmation statement to take over the retransmission of the packet 410 may prevent other network decoding devices from taking over the retransmission of the packet 410. For example, the confirmation or acceptance message may include an identifier of the packet 410 (e.g., a packet ID), and if the network decoding device receives a confirmation or acceptance message with a packet ID, the network decoding device may avoid sending a confirmation or acceptance message with the same packet ID.

[0104] Thus, after receiving a request for retransmission of packet 410, the second network decoding device 405-b may signal whether it will take over the retransmission of packet 410. If the second network decoding device 405-b determines to take over the retransmission of packet 410, the second network decoding device 405-b may signal the first network decoding device 405-a whether packet 410 is stored in a buffer at the second network decoding device 405-b (e.g., whether the second network decoding device has packet 410 in its buffer). The signaling may be performed using an SCI-2 format, a MAC-CE, a MAC header or subheader, or an RRC message. If the second network decoding device 405-b does not have packet 410 in its buffer, the first network decoding device 405-a may reselect another network decoding device to send or broadcast packet 410 to a receiver (e.g., UE 115-d) and to the second network decoding device 405-b.

[0105] Figure 5An example of a process flow 500 for supporting network decoding handover between network decoding devices according to one or more aspects of the present disclosure is illustrated. The process flow 500 includes UE 115-e and UE 115-f, which may be reference Figures 1 to 4 The process flow 500 also includes a first network decoding device 505-a and a second network decoding device 505-b, which can be reference Figures 1 to 4 The process flow 500 may implement aspects of the wireless communication system 100. For example, the process flow 500 may support efficient techniques for handing over packets between network decoding devices for network decoding.

[0106] In the following description of process flow 500, signaling exchanged between first UE 115-e, second UE 115-f, first network decoding device 505-a, and second network decoding device 505-b may be exchanged in a different order than the example order shown, or operations performed by first UE 115-e, second UE 115-f, first network decoding device 505-a, and second network decoding device 505-b may be performed in a different order or at a different time. Some operations may also be omitted from process flow 500, and other operations may be added to process flow 500.

[0107] At 510, the first UE 115-e may send a packet to one or more UEs 115 including UE 115-f. The first UE 115-e may determine that at least one UE 115 (e.g., the second UE 115-f) has failed to receive a packet from the first UE 115-e. At 515, the first UE 115-e may send a first request to a network decoding device to retransmit a packet originally sent by the first UE 115-e based on determining that at least one UE 115 has failed to receive a packet from the first UE 115-e. In some cases, the first UE 115-e may send the first request in a retransmission of the packet or separately from the packet. The first UE 115-e may send the first request to one or more network decoding devices including the first network decoding device 505-a (e.g., in a broadcast or multicast transmission).

[0108] At 520, the first UE 115-e may receive an acceptance message from the first network decoding device 505-a indicating that the first network decoding device 505-a is to retransmit the packet. In some cases, the first network decoding device 505-a may send the acceptance message to the first UE 115-e based on determining that the first network decoding device 505-a is closest to the first UE 115-e or the second UE 115-f among the one or more network decoding devices that can be used to retransmit the packet. In some cases, the first network decoding device 505-a may send the acceptance message to the first UE 115-e based on the load at the first network decoding device 505-a or whether the first network decoding device 505-a has a packet in the buffer. The one or more network decoding devices that can be used to retransmit the packet may include the network decoding device that receives the first request or a network decoding device within the area. The first network decoding device 505-a may receive an indication of the location of each of the one or more network decoding devices, and the first network decoding device 505-a may determine that it is closest to the first UE 115-e or the second UE 115-f based on the location of each of the one or more network decoding devices. The first network decoding device 505-a may receive an indication of the location of each network decoding device in an SCI message, a MAC-CE, or an RRC message.

[0109] At 525, the first network decoding device 505-a may retransmit the packet (e.g., to be received by the second UE 115-f and any other UE 115 that failed to receive the packet). At 530, the first UE 115-e may receive a NACK from the first network decoding device that triggers a handover of the retransmission of the packet from the first network decoding device 505-a (e.g., a handover of the task of retransmitting the packet). In some cases, the first UE 115-e may receive the NACK based on the second UE 115-f failing to successfully receive the retransmission of the packet from the first network decoding device 505-a. At 535, the first UE 115-e may send a second request to the network decoding device to retransmit the packet originally sent by the first UE 115-e based on receiving the NACK. The first UE 115-e may send the second request to one or more network decoding devices including the second network decoding device 505-b (e.g., in a broadcast or multicast transmission).

[0110] In some cases, the first UE 115-e may send an indication in the second request to the second network decoding device 505-b to retransmit the packet originally sent by the first UE 115-e. In some cases, the first UE 115-e may send an indication in the second request to at least one network decoding device to avoid retransmitting the packet originally sent by the first UE 115-e. The first UE 115-e may store the packet in a buffer so that the first UE 115-e may send a second request to the network decoding device to retransmit the packet after the second UE 115-f fails to receive the packet from the first network decoding device in the retransmission. In some cases, the first UE 115-e may send the second request in the retransmission of the packet or separately from the packet.

[0111] In some cases, the first network decoding device 505-a may receive a second request to retransmit a packet originally sent by the first UE 115-e, and the first network decoding device 505-a may ignore the second request based on determining the retransmission of the handover packet. In one example, the first network decoding device 505-a may identify that the second request is for retransmitting a packet that has already been retransmitted (e.g., one or more times) by the first network decoding device 505-a based on storing the packet in a buffer and comparing the packet associated with the second request with the packet stored in the buffer. In another example, the first network decoding device 505-a may identify that the second request is for retransmitting a packet that has already been retransmitted (e.g., one or more times) by the first network decoding device 505-a based on receiving an indication that the first network decoding device 505-a is to avoid retransmitting the packet.

[0112] At 540, the first UE 115-e may receive an acceptance message from the second network decoding device 505-b indicating that the second network decoding device 505-b is to retransmit the packet. In some cases, the second network decoding device 505-b may send an acceptance message to the first UE 115-e based on determining that the second network decoding device 505-b is closest to the first UE 115-e or the second UE 115-f among the one or more network decoding devices that can be used to retransmit the packet. The one or more network decoding devices that can be used to retransmit the packet may include a network decoding device that receives the second request or a network decoding device within the area, excluding those network decoding devices that have already retransmitted the packet. The second network decoding device 505-b may receive an indication of the location of each of the one or more network decoding devices, and the second network decoding device 505-b may determine that it is closest to the first UE 115-e or the second UE 115-f based on the location of each of the one or more network decoding devices. The second network decoding device 505 - b may receive an indication of the location of each network decoding device in an SCI message, a MAC-CE, or an RRC message.

[0113] At 545, the second network decoding device 505-b may retransmit the packet (eg, to be received by the second UE 115-f and any other UEs 115 that failed to receive the packet).

[0114] Figure 6 An example of a process flow 600 for supporting network decoding handover between network decoding devices according to one or more aspects of the present disclosure is illustrated. The process flow 600 includes a first UE 115-g and a second UE 115-h, which may be reference Figures 1 to 4 The process flow 600 also includes a first network decoding device 605-a and a second network decoding device 605-b, which can be reference Figures 1 to 5 The process flow 600 may implement aspects of the wireless communication system 100. For example, the process flow 600 may support efficient techniques for handing over packets between network decoding devices for network decoding.

[0115] In the following description of process flow 600, signaling exchanged between the first UE 115-g, the second UE 115-h, the first network decoding device 605-a, and the second network decoding device 605-b may be exchanged in a different order than the example order shown, or operations performed by the first UE 115-g, the second UE 115-h, the first network decoding device 605-a, and the second network decoding device 605-b may be performed in a different order or at a different time. Some operations may also be omitted from process flow 600, and other operations may be added to process flow 600.

[0116] At 610, the first UE 115-g may send a packet to one or more UEs 115 including UE 115-h. The first UE 115-g may determine that at least one UE 115 (e.g., the second UE 115-h) has failed to receive a packet from the first UE 115-g. At 615, the first UE 115-g may send a first request to a network decoding device to retransmit a packet originally sent by the first UE 115-g based on determining that at least one UE 115 has failed to receive a packet from the first UE 115-g. In some cases, the first UE 115-g may send the first request in a retransmission of the packet or separately from the packet. The first UE 115-g may send the first request (e.g., in a broadcast or multicast transmission) to one or more network decoding devices including the first network decoding device 605-a.

[0117] At 620, the first UE 115-g may receive an acceptance message from the first network decoding device 605-a indicating that the first network decoding device 605-a is to retransmit the packet. In some cases, the first network decoding device 605-a may send an acceptance message to the first UE 115-g based on determining that the first network decoding device 605-a is closest to the first UE 115-g or the second UE 115-h among the one or more network decoding devices that can be used to retransmit the packet. The one or more network decoding devices that can be used to retransmit the packet may include a network decoding device that receives the first request or a network decoding device within the area. The first network decoding device 605-a may receive an indication of the location of each of the one or more network decoding devices, and the first network decoding device 605-a may determine that it is closest to the first UE 115-g or the second UE 115-h based on the location of each of the one or more network decoding devices. The first network decoding device 605 - a may receive an indication of the location of each network decoding device in an SCI message, a MAC-CE, or an RRC message.

[0118] At 625, the first network decoding device 605-a may retransmit the packet (e.g., to be received by the second UE 115-h and any other UEs 115 that failed to receive the packet). In some cases, the first network decoding device 605-a may determine a retransmission of the handover packet (e.g., based on the failure of the UE 115-h to receive a retransmission from the first network decoding device 605-a), and at 630, the first network decoding device 605-a may send a second request to the network decoding device to retransmit the packet. In some cases, the first network decoding device 605-a may send the second request in the retransmission of the packet or separately from the packet (e.g., in a control message such as an SCI message, a MAC-CE, or an RRC message).

[0119] In some cases, the first network decoding device 605-a may send an indication in a second request to the second network decoding device 605-b to retransmit the packet based on the load of the second network decoding device 605-b. In some cases, the first network decoding device 605-a may receive an indication of the load of the second network decoding device 605-b from the second network decoding device 605-b. Additionally or alternatively, the first network decoding device 605-a may monitor the transmissions from the second network decoding device 605-b to determine the number and size of the transmissions from the second network decoding device 605-b, and the first network decoding device 605-a may determine the load of the second network decoding device 605-b based on the monitoring. The first network decoding device 605-a may then select the second network decoding device 605-b to retransmit the packet based on the load of the second network decoding device 605-b.

[0120] In one example, the first network decoding device 605-a may select the second network decoding device 605-b to retransmit the packet based on the load of the second network decoding device 605-b, which includes packets of similar length to the packet to be retransmitted (e.g., the packet originally sent by UE 115-g at 610). The network decoding transmission including multiple transmission blocks can be as long as the longest transmission block in the multiple transmission blocks. Therefore, if the packet to be retransmitted is longer and the load of the third network decoding device includes short packets, the first network decoding device 605-a can avoid selecting the third network decoding device to retransmit the packet (e.g., to avoid increasing the size of the network decoding transmission from the third network decoding device). In another example, the first network decoding device 605-a may select the second network decoding device 605-b to retransmit the packet based on the load of the second network decoding device 605-b (e.g., the number of packets in the network decoding transmission from the second network decoding device 605-b) being less than a threshold.

[0121] In some cases, the first network decoding device 605-a may send an indication in a second request to the second network decoding device 605-b to retransmit the packet based on the second network decoding device 605-b being closest to the first UE 115-g or the second UE 115-h among the one or more network decoding devices available for retransmitting the packet. The first network decoding device 605-a may receive an indication of the location of each of the one or more network decoding devices, and the first network decoding device 605-a may determine that the second network decoding device 605-b is closest to the first UE 115-g or the second UE 115-h among the one or more network decoding devices based on receiving the indication of the location of each of the one or more network decoding devices. The first network decoding device 605-a may receive the indication of the location of each network decoding device in an SCI message, a MAC-CE, or an RRC message.

[0122] In some cases, the first network decoding device 605-a may send an indication to the second network decoding device 605-b to retransmit the packet in the second request based on determining that the second network decoding device 605-b has stored the packet in the buffer. The first network decoding device 605-a may determine that the second network decoding device 605-b has stored the packet in the buffer based on the second network decoding device 605-b sending an acceptance message to the first UE 115-g to retransmit the packet. In some examples, the first network decoding device 605-a or the second network decoding device 605-b may receive the packet (e.g., at 610) and store the packet in the buffer. In some cases, the first network decoding device 605-a may send an indication to the second network decoding device 605-b to retransmit the packet in the second request, and the first network decoding device 605-a may send the packet to the second network decoding device 605-b based on determining that the packet is lost from the buffer at the second network decoding device 605-b. In some cases, the first network coding device 605 - a may send in the second request an indication of a group of network coding devices, each network coding device in the group being a candidate for retransmitting the packet.

[0123] At 635, the second network decoding device 605-b may send an acceptance message to the first network decoding device 605-a, and at 640, the second network decoding device 605-b may resend the packet (e.g., to be received by the second UE 115-h and any other UE 115 that failed to receive the packet).

[0124] Figure 7 A block diagram 700 of a device 705 supporting network decoding handover between network decoding devices according to one or more aspects of the present disclosure is shown. The device 705 can be an example of various aspects of a UE 115 (e.g., a network decoding device) as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0125] The receiver 710 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to network decoding handover between network decoding devices), user data, control information, or any combination thereof. The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0126] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to network decoding handover between network decoding devices), user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0127] The communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of network decoding handover between network decoding devices as described herein. For example, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

[0128] In some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof, which is configured to or otherwise supports means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0129] Additionally or alternatively, in some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure).

[0130] In some examples, the communication manager 720 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 can receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0131] According to examples as disclosed herein, the communication manager 720 may support wireless communications at the UE. For example, the communication manager 720 may be configured to or otherwise support a component for sending a first request to a network decoding device to retransmit a packet originally sent by the UE. The communication manager 720 may be configured to or otherwise support a component for receiving an acceptance message from a first network decoding device indicating that the first network decoding device is to retransmit a packet. The communication manager 720 may be configured to or otherwise support a component for receiving a negative confirmation of a handover from the first network decoding device that triggers the retransmission of the packet from the first network decoding device. The communication manager 720 may be configured to or otherwise support a component for sending a second request to the network decoding device to retransmit the packet originally sent by the UE based on receiving the negative confirmation.

[0132] Additionally or alternatively, according to examples as disclosed herein, the communication manager 720 may support wireless communications at the first network decoding device. For example, the communication manager 720 may be configured to or otherwise support a component for receiving a first request to the first network decoding device to retransmit a packet originally sent by the UE. The communication manager 720 may be configured to or otherwise support a component for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. The communication manager 720 may be configured to or otherwise support a component for determining a retransmission of a handover packet. The communication manager 720 may be configured to or otherwise support a component for sending a negative confirmation of a handover of the retransmission of the triggering packet to the UE based on the determination from the first network decoding device to the second network decoding device.

[0133] Additionally or alternatively, according to examples as disclosed herein, the communication manager 720 may support wireless communications at the first network decoding device. For example, the communication manager 720 may be configured to or otherwise support a component for receiving a first request to the first network decoding device to retransmit a packet originally sent by the UE. The communication manager 720 may be configured to or otherwise support a component for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. The communication manager 720 may be configured to or otherwise support a component for determining the retransmission of the handover packet. The communication manager 720 may be configured to or otherwise support a component for sending a second request to the second network decoding device to retransmit the packet based on the determination.

[0134] By including or configuring the communication manager 720 according to the examples described herein, the device 705 (e.g., a processor controlling the receiver 710, the transmitter 715, the communication manager 720, or a combination thereof or otherwise coupled thereto) can support techniques for reduced processing, reduced power consumption, and more efficient utilization of communication resources. Because the device 705 can facilitate the handover of the retransmission of the packet from the first network decoding device to the second network decoding device, the overhead associated with the retransmission can be reduced, while the likelihood that the wireless device can successfully receive the packet can be increased. Therefore, the processing and power consumption associated with the retransmission of the packet can be reduced, and fewer resources can be used to retransmit the packet.

[0135] Figure 8 A block diagram 800 of a device 805 supporting network decoding handover between network decoding devices according to one or more aspects of the present disclosure is shown. The device 805 can be an example of aspects of the device 705 or UE 115 (e.g., a network decoding device) as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0136] The receiver 810 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to network decoding handover between network decoding devices), user data, control information, or any combination thereof. The information may be communicated to other components of the device 805. The receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0137] The transmitter 815 may provide means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to network decoding handover between network decoding devices), user data, control information, or any combination thereof. In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0138] Device 805 or its various components may be examples of components for performing various aspects of network decoding handover between network decoding devices as described herein. For example, communication manager 820 may include retransmission request manager 825, retransmission acceptance manager 830, NACK manager 835, retransmission handover manager 840, or any combination thereof. Communication manager 820 may be an example of various aspects of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using receiver 810, transmitter 815, or both or otherwise cooperate with them. For example, communication manager 820 may receive information from receiver 810, transmit information to transmitter 815, or integrate with receiver 810, transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0139] According to examples as disclosed herein, the communication manager 820 may support wireless communications at the UE. The retransmission request manager 825 may be configured to or otherwise support a component for sending a first request to a network decoding device to retransmit a packet originally sent by the UE. The retransmission acceptance manager 830 may be configured to or otherwise support a component for receiving an acceptance message from a first network decoding device indicating that the first network decoding device is to retransmit a packet. The NACK manager 835 may be configured to or otherwise support a component for receiving a negative confirmation from the first network decoding device triggering a handover of a retransmission of a packet from the first network decoding device. The retransmission request manager 825 may be configured to or otherwise support a component for sending a second request to the network decoding device to retransmit a packet originally sent by the UE based on receiving a negative confirmation.

[0140] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communications at the first network decoding device. The retransmission request manager 825 may be configured to or otherwise support a component for receiving a first request to the first network decoding device to retransmit a packet originally sent by the UE. The retransmission acceptance manager 830 may be configured to or otherwise support a component for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. The retransmission handover manager 840 may be configured to or otherwise support a component for determining a retransmission of the handover packet. The NACK manager 835 may be configured to or otherwise support a component for sending a negative confirmation of the handover of the retransmission of the triggering packet from the first network decoding device to the second network decoding device based on the determination to the UE.

[0141] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communications at the first network decoding device. The retransmission request manager 825 may be configured to or otherwise support a component for receiving a first request to the first network decoding device to retransmit a packet originally sent by the UE. The retransmission acceptance manager 830 may be configured to or otherwise support a component for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. The retransmission handover manager 840 may be configured to or otherwise support a component for determining the retransmission of the handover packet. The retransmission request manager 825 may be configured to or otherwise support a component for sending a second request to the second network decoding device to retransmit the packet based on the determination.

[0142] Fig. 9 A block diagram 900 of a communication manager 920 supporting a network decoding handover between network decoding devices according to one or more aspects of the present disclosure is shown. The communication manager 920 may be an example of aspects of the communication manager 720, the communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of components for performing various aspects of a network decoding handover between network decoding devices as described herein. For example, the communication manager 920 may include a retransmission request manager 925, a retransmission acceptance manager 930, a NACK manager 935, a retransmission handover manager 940, a packet manager 945, a buffer 950, a location manager 955, a load manager 960, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0143] According to examples as disclosed herein, the communication manager 920 may support wireless communications at the UE. The retransmission request manager 925 may be configured to or otherwise support a component for sending a first request to a network decoding device to retransmit a packet originally sent by the UE. The retransmission acceptance manager 930 may be configured to or otherwise support a component for receiving an acceptance message from a first network decoding device indicating that the first network decoding device is to retransmit a packet. The NACK manager 935 may be configured to or otherwise support a component for receiving a negative confirmation from the first network decoding device triggering a retransmission of the packet from the first network decoding device. In some examples, the retransmission request manager 925 may be configured to or otherwise support a component for sending a second request to the network decoding device to retransmit the packet originally sent by the UE based on receiving the negative confirmation.

[0144] In some examples, the packet manager 945 may be configured to or otherwise support means for sending a packet to one or more UEs. In some examples, the retransmission request manager 925 may be configured to or otherwise support means for determining that at least one of the one or more UEs failed to receive a packet from the UE, wherein sending a first request to the network decoding device to retransmit the packet is based on the determination.

[0145] In some examples, retransmission request manager 925 may be configured or otherwise support means for sending, in a second request, an indication to the second network coding device to retransmit a packet originally sent by the UE.

[0146] In some examples, retransmission request manager 925 may be configured or otherwise support means for sending, in a second request, an indication to at least one network coding device to avoid retransmitting a packet originally sent by the UE.

[0147] In some examples, buffer 950 may be configured as or otherwise support means for storing the packet in a buffer at the UE, wherein sending a second request to the network decoding device to retransmit the packet is based on storing the packet in the buffer at the UE.

[0148] In some examples, a first request for the network coding device to retransmit the packet is included in a first retransmission of the packet from the UE, and a second request for the network coding device to retransmit the packet is included in a second retransmission of the packet from the UE.

[0149] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at the first network decoding device. In some examples, the retransmission request manager 925 may be configured to or otherwise support a component for receiving a first request to the first network decoding device to retransmit a packet originally sent by the UE. In some examples, the retransmission acceptance manager 930 may be configured to or otherwise support a component for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. The retransmission handover manager 940 may be configured to or otherwise support a component for determining a retransmission of a handover packet. In some examples, the NACK manager 935 may be configured to or otherwise support a component for sending a negative confirmation of a handover of a retransmission of a triggering packet from the first network decoding device to the second network decoding device based on the determination to the UE.

[0150] In some examples, the retransmission request manager 925 may be configured or otherwise support means for receiving a second request to the first network decoding device to retransmit a packet originally sent by the UE. In some examples, the retransmission request manager 925 may be configured or otherwise support means for ignoring the second request based on determining to retransmit the handover packet.

[0151] In some examples, location manager 955 may be configured to or otherwise support means for determining that a first network coding device among a set of multiple network coding devices is closest to the UE, wherein sending an acceptance message to the UE is based on determining that the first network coding device is closest to the UE.

[0152] In some examples, the location manager 955 may be configured to or otherwise support a component for receiving an indication of the location of each network decoding device in a set of multiple network decoding devices, wherein determining that the first network decoding device is closest to the UE is based on receiving the indication of the location of each network decoding device in the set of multiple network decoding devices.

[0153] In some examples, an indication of the location of each network coding device is received in a sidelink control information message, a medium access control control element, or a radio resource control message.

[0154] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at the first network decoding device. In some examples, the retransmission request manager 925 may be configured to or otherwise support a component for receiving a first request to the first network decoding device to retransmit a packet originally sent by the UE. In some examples, the retransmission acceptance manager 930 may be configured to or otherwise support a component for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. In some examples, the retransmission handover manager 940 may be configured to or otherwise support a component for determining the retransmission of the handover packet. In some examples, the retransmission request manager 925 may be configured to or otherwise support a component for sending a second request to the second network decoding device to retransmit the packet based on the determination.

[0155] In some examples, retransmission request manager 925 may be configured or otherwise support means for sending, in a second request, an indication to the second network coding device to retransmit the packet based on a load of the second network coding device.

[0156] In some examples, load manager 960 may be configured or otherwise support means for receiving, from a second network coding device, an indication of a load of the second network coding device.

[0157] In some examples, the load manager 960 may be configured or otherwise support a component for monitoring transmissions from the second network decoding device to determine the number and size of transmissions from the second network decoding device. In some examples, the load manager 960 may be configured or otherwise support a component for determining a load of the second network decoding device based on the monitoring.

[0158] In some examples, the retransmission handover manager 940 may be configured to or otherwise support means for determining that the second network coding device sends another acceptance message to the UE to retransmit the packet. In some examples, the retransmission handover manager 940 may be configured to or otherwise support means for determining that the second network coding device has stored the packet (e.g., in a buffer) based on the second network coding device sending another acceptance message to the UE to retransmit the packet.

[0159] In some examples, the retransmission request manager 925 may be configured to or otherwise support means for sending an indication in a second request to the second network coding device to retransmit the packet based on the second network coding device being closest to the UE among the set of multiple network coding devices.

[0160] In some examples, the location manager 955 may be configured or otherwise support means for receiving an indication of the location of each network decoding device in the set of multiple network decoding devices. In some examples, the location manager 955 may be configured or otherwise support means for determining that a second network decoding device in the set of multiple network decoding devices is closest to the UE based on receiving an indication of the location of each network decoding device in the set of multiple network decoding devices.

[0161] In some examples, an indication of the location of each network coding device is received in a sidelink control information message, a medium access control control element, or a radio resource control message.

[0162] In some examples, retransmission request manager 925 may be configured or otherwise support means for sending in a second request an indication to the second network coding device to retransmit the packet based on determining that the second network coding device has stored the packet in a buffer.

[0163] In some examples, the retransmission request manager 925 may be configured to or otherwise support means for sending, in a second request, an indication to the second network decoding device to retransmit the packet. In some examples, the retransmission handover manager 940 may be configured to or otherwise support means for sending a packet to the second network decoding device based on determining that the packet is lost from a buffer at the second network decoding device.

[0164] In some examples, the retransmission request manager 925 may be configured or otherwise support means for sending, in the second request, an indication of a group of network coding devices, each network coding device in the group being a candidate for retransmitting the packet.

[0165] In some examples, to support sending a second request for retransmission of a packet, retransmission request manager 925 may be configured or otherwise support means for retransmitting a packet originally sent by the UE along with the second request for retransmission of the packet.

[0166] In some examples, to support sending a second request for retransmission of the packet, retransmission request manager 925 may be configured or otherwise support means for sending a control message with a second request to a second network coding device to retransmit the packet.

[0167] In some examples, the control message includes a sidelink control information message, a medium access control control element, or a radio resource control message.

[0168] Fig.10A diagram of a system 1000 including a device 1005 supporting network decoding handover between network decoding devices according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of a device 705, a device 805, or a UE 115 (e.g., a network decoding device) as described herein or include a component of these devices. The device 1005 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). The device 1005 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1045).

[0169] I / O controller 1010 can manage input and output signals for device 1005. I / O controller 1010 can also manage peripheral devices that are not integrated into device 1005. In some cases, I / O controller 1010 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1010 can utilize an operating system such as or another known operating system. Additionally or alternatively, I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1010 may be implemented as part of a processor such as processor 1040. In some cases, a user may interact with device 1005 via I / O controller 1010 or via hardware components controlled by I / O controller 1010.

[0170] In some cases, the device 1005 may include a single antenna 1025. However, in some other cases, the device 1005 may have more than one antenna 1025, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1015 may communicate bidirectionally via one or more antennas 1025, a wired or wireless link, as described herein. For example, the transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1015 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1025 for transmission; and demodulating packets received from one or more antennas 1025. The transceiver 1015 or the transceiver 1015 and one or more antennas 1025 may be examples of transmitters 715, transmitters 815, receivers 710, receivers 810, or any combination thereof or components thereof as described herein.

[0171] The memory 1030 may include random access memory (RAM) and read-only memory (ROM). The memory 1030 may store computer-readable, computer-executable code 1035 including instructions that, when executed by the processor 1040, cause the device 1005 to perform various functions described herein. The code 1035 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 1035 may not be directly executable by the processor 1040, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, in addition to this, the memory 1030 may also contain a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0172] Processor 1040 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) to enable device 1005 to perform various functions (e.g., functions or tasks that support network decoding handover between network decoding devices). For example, device 1005 or a component of device 1005 may include processor 1040 and memory 1030 coupled to or coupled to processor 1040, and processor 1040 and memory 1030 are configured to perform various functions described herein.

[0173] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at the UE. For example, the communication manager 1020 may be configured to or otherwise support a component for sending a first request to a network decoding device to retransmit a packet originally sent by the UE. The communication manager 1020 may be configured to or otherwise support a component for receiving an acceptance message from a first network decoding device indicating that the first network decoding device is to retransmit a packet. The communication manager 1020 may be configured to or otherwise support a component for receiving a negative confirmation of a handover from the first network decoding device that triggers a retransmission of the packet from the first network decoding device. The communication manager 1020 may be configured to or otherwise support a component for sending a second request to the network decoding device to retransmit the packet originally sent by the UE based on receiving the negative confirmation.

[0174] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at the first network decoding device. For example, the communication manager 1020 may be configured to or otherwise support a component for receiving a first request to the first network decoding device to retransmit a packet originally sent by the UE. The communication manager 1020 may be configured to or otherwise support a component for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. The communication manager 1020 may be configured to or otherwise support a component for determining a retransmission of a handover packet. The communication manager 1020 may be configured to or otherwise support a component for sending a negative confirmation of a handover of the retransmission of the triggering packet to the UE based on the determination from the first network decoding device to the second network decoding device.

[0175] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at the first network decoding device. For example, the communication manager 1020 may be configured to or otherwise support a component for receiving a first request to the first network decoding device to retransmit a packet originally sent by the UE. The communication manager 1020 may be configured to or otherwise support a component for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. The communication manager 1020 may be configured to or otherwise support a component for determining the retransmission of the handover packet. The communication manager 1020 may be configured to or otherwise support a component for sending a second request to the second network decoding device to retransmit the packet based on the determination.

[0176] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 can support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communication resources. Because the device 1005 can facilitate the handover of the retransmission of the packet from the first network decoding device to the second network decoding device, the overhead associated with the retransmission can be reduced, while the probability that the wireless device can successfully receive the packet can be increased. Therefore, the processing and power consumption associated with the retransmission of the packet can be reduced, and fewer resources can be used to retransmit the packet.

[0177] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1015, one or more antennas 1025, or any combination thereof. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by the processor 1040, the memory 1030, the code 1035, or any combination thereof. For example, the code 1035 may include instructions that may be executed by the processor 1040 to cause the device 1005 to perform various aspects of a network decoding handover between network decoding devices as described herein, or the processor 1040 and the memory 1030 may be otherwise configured to perform or support such operations.

[0178] Fig.11 A block diagram 1100 of a device 1105 supporting network decoding handover between network decoding devices according to one or more aspects of the present disclosure is shown. The device 1105 can be an example of various aspects of a network entity 105 (e.g., a network decoding device) as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0179] The receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of the device 1105. In some examples, the receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0180] The transmitter 1115 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to the modem.

[0181] The communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of network decoding handover between network decoding devices as described herein. For example, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

[0182] In some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0183] Additionally or alternatively, in some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure).

[0184] In some examples, communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in conjunction with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0185] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at the first network decoding device. For example, the communication manager 1120 may be configured to or otherwise support a component for receiving a first request for the first network decoding device to retransmit a packet originally sent by the UE. The communication manager 1120 may be configured to or otherwise support a component for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. The communication manager 1120 may be configured to or otherwise support a component for determining a retransmission of a handover packet. The communication manager 1120 may be configured to or otherwise support a component for sending a negative confirmation of a handover of the retransmission of the triggering packet to the UE based on the determination from the first network decoding device to the second network decoding device.

[0186] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 may support wireless communications at the first network decoding device. For example, the communication manager 1120 may be configured to or otherwise support a component for receiving a first request to the first network decoding device to retransmit a packet originally sent by the UE. The communication manager 1120 may be configured to or otherwise support a component for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. The communication manager 1120 may be configured to or otherwise support a component for determining the retransmission of the handover packet. The communication manager 1120 may be configured to or otherwise support a component for sending a second request to the second network decoding device to retransmit the packet based on the determination.

[0187] By including or configuring the communication manager 1120 according to the examples as described herein, the device 1105 (e.g., a processor controlling the receiver 1110, the transmitter 1115, the communication manager 1120, or a combination thereof or otherwise coupled thereto) can support techniques for reduced processing, reduced power consumption, and more efficient utilization of communication resources. Because the device 1105 can hand over the retransmission of the packet to another network decoding device, the overhead associated with the retransmission can be reduced, while the likelihood that the wireless device can successfully receive the packet can be increased. Therefore, the processing and power consumption associated with the retransmission of the packet can be reduced, and fewer resources can be used to retransmit the packet.

[0188] Fig.12 A block diagram 1200 of a device 1205 supporting network decoding handover between network decoding devices according to one or more aspects of the present disclosure is shown. The device 1205 can be an example of aspects of the device 1105 or network entity 105 (e.g., a network decoding device) as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0189] The receiver 1210 may provide means for obtaining (e.g., receiving, determining, identifying) information (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof. The information may be communicated to other components of the device 1205. In some examples, the receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1210 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0190] The transmitter 1215 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1205. For example, the transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1215 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1215 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1215 and the receiver 1210 may be co-located in a transceiver, which may include a modem or be coupled to the modem.

[0191] Device 1205 or its various components may be examples of components for performing various aspects of network decoding handover between network decoding devices as described herein. For example, communication manager 1220 may include retransmission request manager 1225, retransmission acceptance manager 1230, retransmission handover manager 1235, NACK manager 1240, or any combination thereof. Communication manager 1220 may be an example of various aspects of communication manager 1120 as described herein. In some examples, communication manager 1220 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using receiver 1210, transmitter 1215, or both or otherwise cooperate with them. For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or integrate with receiver 1210, transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0192] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a first network decoding device. The retransmission request manager 1225 may be configured to or otherwise support a component for receiving a first request to the first network decoding device to retransmit a packet originally sent by the UE. The retransmission acceptance manager 1230 may be configured to or otherwise support a component for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. The retransmission handover manager 1235 may be configured to or otherwise support a component for determining a retransmission of a handover packet. The NACK manager 1240 may be configured to or otherwise support a component for sending a negative acknowledgement of a handover of a retransmission of a triggering packet from the first network decoding device to the second network decoding device based on the determination to the UE.

[0193] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1220 may support wireless communications at the first network decoding device. The retransmission request manager 1225 may be configured to or otherwise support a component for receiving a first request to the first network decoding device to retransmit a packet originally sent by the UE. The retransmission acceptance manager 1230 may be configured to or otherwise support a component for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. The retransmission handover manager 1235 may be configured to or otherwise support a component for determining a retransmission of the handover packet. The retransmission request manager 1225 may be configured to or otherwise support a component for sending a second request to the second network decoding device to retransmit the packet based on the determination.

[0194] Fig.13A block diagram 1300 of a communication manager 1320 supporting a network decoding handover between network decoding devices according to one or more aspects of the present disclosure is shown. The communication manager 1320 may be an example of aspects of the communication manager 1120, the communication manager 1220, or both as described herein. The communication manager 1320 or its various components may be examples of components for performing various aspects of a network decoding handover between network decoding devices as described herein. For example, the communication manager 1320 may include a retransmission request manager 1325, a retransmission acceptance manager 1330, a retransmission handover manager 1335, a NACK manager 1340, a location manager 1345, a load manager 1350, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0195] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a first network decoding device. The retransmission request manager 1325 may be configured to or otherwise support a component for receiving a first request to the first network decoding device to retransmit a packet originally sent by the UE. The retransmission acceptance manager 1330 may be configured to or otherwise support a component for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. The retransmission handover manager 1335 may be configured to or otherwise support a component for determining a retransmission of a handover packet. The NACK manager 1340 may be configured to or otherwise support a component for sending a negative acknowledgement of a handover of a retransmission of a triggering packet from the first network decoding device to the second network decoding device based on the determination to the UE.

[0196] In some examples, the retransmission request manager 1325 may be configured to or otherwise support means for receiving a second request to the first network decoding device to retransmit a packet originally sent by the UE. In some examples, the retransmission request manager 1325 may be configured to or otherwise support means for ignoring the second request based on determining to retransmit the handover packet.

[0197] In some examples, location manager 1345 may be configured to or otherwise support means for determining that a first network coding device among a set of multiple network coding devices is closest to the UE, wherein sending an acceptance message to the UE is based on determining that the first network coding device is closest to the UE.

[0198] In some examples, the location manager 1345 may be configured as or otherwise support a component for receiving an indication of the location of each network decoding device in a set of multiple network decoding devices, wherein determining that the first network decoding device is closest to the UE is based on receiving the indication of the location of each network decoding device in the set of multiple network decoding devices.

[0199] In some examples, an indication of the location of each network coding device is received in a sidelink control information message, a medium access control control element, or a radio resource control message.

[0200] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1320 may support wireless communications at the first network decoding device. In some examples, the retransmission request manager 1325 may be configured to or otherwise support a component for receiving a first request to the first network decoding device to retransmit a packet originally sent by the UE. In some examples, the retransmission acceptance manager 1330 may be configured to or otherwise support a component for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. In some examples, the retransmission handover manager 1335 may be configured to or otherwise support a component for determining the retransmission of the handover packet. In some examples, the retransmission request manager 1325 may be configured to or otherwise support a component for sending a second request to the second network decoding device to retransmit the packet based on the determination.

[0201] In some examples, the retransmission request manager 1325 may be configured or otherwise support means for sending, in a second request, an indication to the second network coding device to retransmit the packet based on a load of the second network coding device.

[0202] In some examples, load manager 1350 may be configured or otherwise support means for receiving, from a second network coding device, an indication of a load of the second network coding device.

[0203] In some examples, the load manager 1350 may be configured or otherwise support components for monitoring transmissions from the second network decoding device to determine the number and size of transmissions from the second network decoding device. In some examples, the load manager 1350 may be configured or otherwise support components for determining the load of the second network decoding device based on the monitoring.

[0204] In some examples, the retransmission handover manager 1335 may be configured to or otherwise support a means for determining that the second network coding device sends another acceptance message to the UE to retransmit the packet. In some examples, the retransmission handover manager 1335 may be configured to or otherwise support a means for determining that the second network coding device has stored the packet based on the second network coding device sending another acceptance message to the UE to retransmit the packet.

[0205] In some examples, the retransmission request manager 1325 may be configured to or otherwise support means for sending an indication in a second request to a second network coding device to retransmit the packet based on the second network coding device being closest to the UE among the set of multiple network coding devices.

[0206] In some examples, the location manager 1345 may be configured to or otherwise support means for receiving an indication of the location of each network decoding device in the set of multiple network decoding devices. In some examples, the location manager 1345 may be configured to or otherwise support means for determining that a second network decoding device in the set of multiple network decoding devices is closest to the UE based on receiving an indication of the location of each network decoding device in the set of multiple network decoding devices.

[0207] In some examples, an indication of the location of each network coding device is received in a sidelink control information message, a medium access control control element, or a radio resource control message.

[0208] In some examples, retransmission request manager 1325 may be configured or otherwise support means for sending in a second request an indication to the second network coding device to retransmit the packet based on determining that the second network coding device has stored the packet in a buffer.

[0209] In some examples, the retransmission request manager 1325 may be configured to or otherwise support means for sending, in a second request, an indication to the second network decoding device to retransmit the packet. In some examples, the retransmission handover manager 1335 may be configured to or otherwise support means for sending a packet to the second network decoding device based on determining that the packet is lost from a buffer at the second network decoding device.

[0210] In some examples, the retransmission request manager 1325 may be configured or otherwise support means for sending, in the second request, an indication of a group of network coding devices, each network coding device in the group being a candidate for retransmitting the packet.

[0211] In some examples, to support sending a second request for retransmission of a packet, retransmission request manager 1325 may be configured or otherwise support means for retransmitting a packet originally sent by the UE along with the second request for retransmission of the packet.

[0212] In some examples, to support sending a second request for retransmission of the packet, retransmission request manager 1325 may be configured or otherwise support means for sending a control message along with a second request to a second network coding device to retransmit the packet.

[0213] In some examples, the control message includes a sidelink control information message, a medium access control control element, or a radio resource control message.

[0214] Fig.14 A diagram of a system 1400 including a device 1405 supporting network decoding handover between network decoding devices according to one or more aspects of the present disclosure is shown. Device 1405 may be an example of a device 1105, a device 1205, or a network entity 105 (e.g., a network decoding device) as described herein or a component including these devices. Device 1405 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. Device 1405 may include components that support output and obtain communications, such as a communication manager 1420, a transceiver 1410, an antenna 1415, a memory 1425, a code 1430, and a processor 1435. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1440).

[0215] The transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1410 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1410 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1405 may include one or more antennas 1415 that may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1410 may also include a modem that is used to: modulate a signal; provide the modulated signal for transmission (e.g., via one or more antennas 1415, via a wired transmitter); receive a modulated signal (e.g., from one or more antennas 1415, from a wired receiver); and demodulate a signal. The transceiver 1410, or the transceiver 1410 and one or more antennas 1415 or wired interfaces (if applicable) may be examples of transmitter 1115, transmitter 1215, receiver 1110, receiver 1210, or any combination thereof or components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0216] Memory 1425 may include RAM and ROM. Memory 1425 may store computer-readable, computer-executable code 1430 including instructions that, when executed by processor 1435, cause device 1405 to perform various functions described herein. Code 1430 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1430 may not be directly executable by processor 1435, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, memory 1425 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0217] Processor 1435 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1435 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1435. Processor 1435 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1425) to enable device 1405 to perform various functions (e.g., functions or tasks that support network decoding handover between network decoding devices). For example, device 1405 or a component of device 1405 may include processor 1435 and memory 1425 coupled to processor 1435, and the processor 1435 and memory 1425 are configured to perform various functions described herein. Processor 1435 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality for performing functions of device 1405 (e.g., by executing code 1430).

[0218] In some examples, bus 1440 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1440 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1405, or communications between different components of device 1405 that may be co-located or located in different locations (e.g., device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, memory 1425, code 1430, and processor 1435 may be located in one of the different components or divided between the different components).

[0219] In some examples, communication manager 1420 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1420 may manage the transfer of data communications for client devices such as one or more UEs 115. In some examples, communication manager 1420 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with UE 115 in collaboration with other network entities 105. In some examples, communication manager 1420 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0220] According to examples as disclosed herein, the communication manager 1420 may support wireless communications at the first network decoding device. For example, the communication manager 1420 may be configured to or otherwise support a component for receiving a first request for the first network decoding device to retransmit a packet originally sent by the UE. The communication manager 1420 may be configured to or otherwise support a component for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. The communication manager 1420 may be configured to or otherwise support a component for determining a retransmission of a handover packet. The communication manager 1420 may be configured to or otherwise support a component for sending a negative confirmation of a handover of the retransmission of the triggering packet to the UE based on the determination from the first network decoding device to the second network decoding device.

[0221] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1420 may support wireless communications at the first network decoding device. For example, the communication manager 1420 may be configured to or otherwise support a component for receiving a first request to the first network decoding device to retransmit a packet originally sent by the UE. The communication manager 1420 may be configured to or otherwise support a component for sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. The communication manager 1420 may be configured to or otherwise support a component for determining the retransmission of the handover packet. The communication manager 1420 may be configured to or otherwise support a component for sending a second request to the second network decoding device to retransmit the packet based on the determination.

[0222] By including or configuring the communication manager 1420 according to the examples described herein, the device 1405 can support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communication resources. Because the device 1405 can hand over the retransmission of the packet to another network decoding device, the overhead associated with the retransmission can be reduced, while the likelihood that the wireless device can successfully receive the packet can be increased. Therefore, the processing and power consumption associated with the retransmission of the packet can be reduced, and fewer resources can be used to retransmit the packet.

[0223] In some examples, the communication manager 1420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1410, one or more antennas 1415 (where applicable), or any combination thereof. Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the processor 1435, the memory 1425, the code 1430, the transceiver 1410, or any combination thereof. For example, the code 1430 may include instructions that may be executed by the processor 1435 to cause the device 1405 to perform various aspects of a network decoding handover between network decoding devices as described herein, or the processor 1435 and the memory 1425 may be otherwise configured to perform or support such operations.

[0224] Fig.15 1 is a flowchart illustrating a method 1500 for supporting network decoding handover between network decoding devices according to one or more aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 10 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0225] At 1505, the method includes sending a first request to a network decoding device to retransmit a packet originally sent by the UE. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig. 9 The retransmission request manager 925 is used to execute.

[0226] At 1510, the method includes receiving an acceptance message from a first network decoding device indicating that the first network decoding device is to resend the packet. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig. 9 The retransmission acceptance manager 930 is used to execute.

[0227] At 1515, the method includes receiving a negative acknowledgement from the first network decoding device that triggers the retransmission of the packet from the first network decoding device. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig. 9 The NACK manager 935 is used to perform the above operation.

[0228] At 1520, the method includes sending a second request to the network decoding device to retransmit the packet originally sent by the UE based on receiving the negative acknowledgement. The operations of 1520 can be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 can be performed as described in reference to Fig. 9 The retransmission request manager 925 is used to execute.

[0229] Fig.16 A flowchart illustrating a method 1600 for supporting network decoding handover between network decoding devices according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a network entity or a component thereof as described herein. Figures 1 to 10 The UE 115 or as referenced Figures 1 to 6 and Figures 11 to 14 In some examples, the UE or network entity may execute an instruction set to control the functional elements of the UE or network entity to perform the described functions. Additionally or alternatively, the UE or network entity may use dedicated hardware to perform various aspects of the described functions.

[0230] At 1605, the method includes receiving a first request to a first network decoding device to retransmit a packet originally sent by a UE. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig. 9 and Fig.13 The retransmission request manager 925 or the retransmission request manager 1325 is used for execution.

[0231] At 1610, the method includes sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig. 9 and Fig.13 The retransmission acceptance manager 930 or the retransmission acceptance manager 1330 is used for execution.

[0232] At 1615, the method includes determining a retransmission of the handover packet. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig. 9 and Fig.13 The retransmission handover manager 940 or the retransmission handover manager 1335 is used for execution.

[0233] At 1620, the method includes sending a negative acknowledgement to the UE of a handover of a retransmission of a triggering packet from the first network decoding device to the second network decoding device based on the determination. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Fig. 9 and Fig.13 The NACK manager 935 or the NACK manager 1340 is used for execution.

[0234] Fig.17 1700 is a flowchart illustrating a method 1700 for supporting network decoding handover between network decoding devices according to one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by a UE or a network entity or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or a network entity or a component thereof as described herein. Figures 1 to 10 The UE 115 or as referenced Figures 1 to 6 and Figures 11 to 14 In some examples, the UE or network entity may execute an instruction set to control the functional elements of the UE or network entity to perform the described functions. Additionally or alternatively, the UE or network entity may use dedicated hardware to perform various aspects of the described functions.

[0235] At 1705, the method includes receiving a first request to a first network decoding device to retransmit a packet originally sent by a UE. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig. 9 and Fig.13 The retransmission request manager 925 or the retransmission request manager 1325 is used for execution.

[0236] At 1710, the method includes sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig. 9 and Fig.13 The retransmission acceptance manager 930 or the retransmission acceptance manager 1330 is used for execution.

[0237] At 1715, the method includes determining a retransmission of the handover packet. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig. 9 and Fig.13 The retransmission handover manager 940 or the retransmission handover manager 1335 is used for execution.

[0238] At 1720, the method includes sending a second request to the second network decoding device to retransmit the packet based on the determination. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Fig. 9 and Fig.13 The retransmission request manager 925 or the retransmission request manager 1325 is used for execution.

[0239] The following provides an overview of various aspects of the disclosure:

[0240] Aspect 1: A method for wireless communication at a UE, comprising: sending a first request to a network decoding device to resend a packet originally sent by the UE; receiving an acceptance message from a first network decoding device indicating that the first network decoding device is to resend the packet; receiving a negative confirmation from the first network decoding device triggering a handover of the resending of the packet from the first network decoding device; and sending a second request to the network decoding device to resend the packet originally sent by the UE based at least in part on receiving the negative confirmation.

[0241] Aspect 2: The method according to Aspect 1 also includes: sending the packet to one or more UEs; and determining that at least one of the one or more UEs fails to receive the packet from the UE, wherein sending the first request to the network decoding device to resend the packet is at least partially based on the determination.

[0242] Aspect 3: The method according to aspect 1 or 2 further includes: sending, in the second request, an instruction to the second network decoding device to resend the packet originally sent by the UE.

[0243] Aspect 4: The method according to any one of aspects 1 to 3 further includes: sending, in the second request, an indication to at least one network decoding device to avoid retransmitting the packet originally sent by the UE.

[0244] Aspect 5: The method according to any one of Aspects 1 to 4 also includes: storing the packet in a buffer at the UE, wherein sending the second request to the network decoding device to resend the packet is at least partially based on storing the packet in the buffer at the UE.

[0245] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the first request for the network decoding device to resend the packet is included in a first resend of the packet from the UE, and the second request for the network decoding device to resend the packet is included in a second resend of the packet from the UE.

[0246] Aspect 7: A method for wireless communication at a first network decoding device, comprising: receiving a first request for the first network decoding device to retransmit a packet originally sent by a UE; sending an acceptance message to the UE indicating that the first network decoding device is to retransmit the packet; determining to hand over the retransmission of the packet; and sending a negative confirmation to the UE triggering the handover of the retransmission of the packet from the first network decoding device to a second network decoding device based at least in part on the determination.

[0247] Aspect 8: The method according to aspect 7 also includes: receiving a second request to the first network decoding device to resend the packet originally sent by the UE; and ignoring the second request based at least in part on determining to hand over the retransmission of the packet.

[0248] Aspect 9: The method according to Aspect 7 or 8 also includes: determining that the first network decoding device among multiple network decoding devices is closest to the UE, wherein sending the acceptance message to the UE is at least partly based on determining that the first network decoding device is closest to the UE.

[0249] Aspect 10: The method according to Aspect 9 also includes: receiving an indication of the location of each of the multiple network decoding devices, wherein determining that the first network decoding device is closest to the UE is at least partially based on receiving the indication of the location of each of the multiple network decoding devices.

[0250] Aspect 11: The method according to aspect 10, wherein the indication of the location of each network decoding device is received in a sidelink control information message, a medium access control control element, or a radio resource control message.

[0251] Aspect 12: A method for wireless communication at a first network decoding device, comprising: receiving a first request for the first network decoding device to resend a packet originally sent by a UE; sending an acceptance message to the UE indicating that the first network decoding device is to resend the packet; determining to hand over the retransmission of the packet; and sending a second request for a second network decoding device to resend the packet based at least in part on the determination.

[0252] Aspect 13: The method according to aspect 12 further comprises: sending an indication in the second request to the second network decoding device to resend the packet based at least in part on a load of the second network decoding device.

[0253] Aspect 14: The method according to aspect 13 further includes: receiving an indication of the load of the second network decoding device from the second network decoding device.

[0254] Aspect 15: The method according to Aspect 13 also includes: monitoring the transmission from the second network decoding device to determine the number and size of transmissions from the second network decoding device; and determining the load of the second network decoding device based at least in part on the monitoring.

[0255] Aspect 16: The method according to any one of Aspects 12 to 15 further includes: determining that the second network decoding device sends another acceptance message to the UE to resend the packet; and determining that the second network decoding device has stored the packet based at least in part on the second network decoding device sending the other acceptance message to the UE to resend the packet.

[0256] Aspect 17: The method according to any one of Aspects 12 to 16 also includes: sending an indication to the second network decoding device to resend the packet in the second request based at least in part on the second network decoding device being closest to the UE among multiple network decoding devices.

[0257] Aspect 18: The method according to Aspect 17 also includes: receiving an indication of the location of each of the multiple network decoding devices; and determining that the second network decoding device among the multiple network decoding devices is closest to the UE based at least in part on receiving the indication of the location of each of the multiple network decoding devices.

[0258] Aspect 19: The method according to aspect 18, wherein the indication of the location of each network decoding device is received in a sidelink control information message, a medium access control control element or a radio resource control message.

[0259] Aspect 20: The method according to any one of aspects 12 to 19 further includes: sending an indication in the second request to the second network decoding device to resend the packet based at least in part on determining that the second network decoding device has stored the packet in a buffer.

[0260] Aspect 21: The method according to any one of Aspects 12 to 19 further includes: sending an indication in the second request to the second network decoding device to resend the packet; and sending the packet to the second network decoding device based at least in part on determining that the packet is lost from a buffer at the second network decoding device.

[0261] Aspect 22: The method according to any one of aspects 12 to 21, further comprising: sending an indication of a group of network decoding devices in the second request, each network decoding device in the group being a candidate for retransmitting the packet.

[0262] Aspect 23: The method according to any one of aspects 12 to 22, wherein sending the second request for retransmission of the packet comprises: retransmitting the packet originally sent by the UE together with the second request for retransmission of the packet.

[0263] Aspect 24: The method according to any one of aspects 12 to 23, wherein sending the second request for retransmission of the packet comprises: sending a control message together with the second request for retransmission of the packet to the second network decoding device.

[0264] Aspect 25: The method according to aspect 24, wherein the control message comprises a sidelink control information message, a medium access control control element or a radio resource control message.

[0265] Aspect 26: An apparatus for performing wireless communications at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 6.

[0266] Aspect 27: An apparatus for wireless communication at a UE, comprising at least one component for performing the method according to any one of aspects 1 to 6.

[0267] Aspect 28: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 6.

[0268] Aspect 29: An apparatus for performing wireless communications at a network decoding device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 7 to 11.

[0269] Aspect 30: An apparatus for wireless communication at a network decoding device, comprising at least one means for performing the method according to any one of aspects 7 to 11.

[0270] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication at a network decoding device, the code comprising instructions executable by a processor to perform the method according to any one of aspects 7 to 11.

[0271] Aspect 32: An apparatus for performing wireless communication at a first network decoding device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 12 to 25.

[0272] Aspect 33: An apparatus for wireless communication at a first network decoding device, comprising at least one means for performing the method according to any one of aspects 12 to 25.

[0273] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a first network decoding device, the code comprising instructions executable by a processor to perform the method according to any one of aspects 12 to 25.

[0274] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0275] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0276] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0277] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0278] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored on or sent via a computer-readable medium as one or more instructions or codes. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that various parts of the functions are implemented at different physical locations.

[0279] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to transfer from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage or other magnetic storage device or can be used for carrying or storing desired program code member and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0280] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" may be based on condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0281] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and similar actions. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Additionally, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0282] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label, or other subsequent reference labels.

[0283] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific embodiments include specific details to provide an understanding of the technology. However, the technologies may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to suppress the concepts that obscure the examples.

[0284] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending a first request to a network decoding device to resend a packet originally sent by the UE; receiving an accept message from a first network decoding device indicating that the first network decoding device is to resend the packet; receiving from the first network decoding device a negative acknowledgement of handover from the first network decoding device triggering retransmission of the packet; as well as A second request is sent to a network decoding device to retransmit the packet originally sent by the UE based at least in part on receiving the negative acknowledgement.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: sending the packet to one or more UEs; and Determining that at least one of the one or more UEs failed to receive the packet from the UE, wherein sending the first request to the network coding device to retransmit the packet is based at least in part on the determination.

3. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: An indication is sent in the second request to a second network decoding device to resend the packet originally sent by the UE.

4. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: An indication is sent in the second request to at least one network decoding device to avoid retransmitting the packet originally sent by the UE.

5. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The packet is stored in a buffer at the UE, wherein sending the second request to the network coding device to retransmit the packet is based at least in part on storing the packet in the buffer at the UE.

6. The apparatus of claim 1, wherein the first request to the network decoding device to retransmit the packet is included in a first retransmission of the packet from the UE, and the second request to the network decoding device to retransmit the packet is included in a second retransmission of the packet from the UE.

7. An apparatus for wireless communication at a first network decoding device, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a first request to the first network decoding device to retransmit a packet originally sent by a user equipment (UE); Sending an acceptance message to the UE indicating that the first network decoding device is to resend the packet; Determining to hand over retransmission of the packet; as well as Based at least in part on the determination, a negative acknowledgement is sent to the UE triggering a handover of the retransmission of the packet from the first network coding device to a second network coding device.

8. The apparatus of claim 7, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a second request to the first network decoding device to retransmit the packet originally sent by the UE; and The second request is ignored based at least in part on determining to hand over retransmission of the packet.

9. The apparatus of claim 7, wherein the instructions are further executable by the processor to cause the apparatus to: Determining that the first network decoding device among a plurality of network decoding devices is closest to the UE, wherein sending the acceptance message to the UE is based at least in part on determining that the first network decoding device is closest to the UE.

10. The apparatus of claim 9, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of a location of each of the plurality of network decoding devices is received, wherein determining that the first network decoding device is closest to the UE is based at least in part on receiving the indication of the location of each of the plurality of network decoding devices.

11. The apparatus of claim 10, wherein the indication of the location of each network decoding device is received in a sidelink control information message, a medium access control control element, or a radio resource control message.

12. An apparatus for wireless communication at a first network decoding device, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a first request to the first network decoding device to retransmit a packet originally sent by a user equipment (UE); Sending an acceptance message to the UE indicating that the first network decoding device is to resend the packet; Determining to hand over retransmission of the packet; as well as A second request is sent to a second network coding device to retransmit the packet based at least in part on the determination.

13. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: An indication to the second network decoding device to retransmit the packet is sent in the second request based at least in part on a load of the second network decoding device.

14. The apparatus of claim 13, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of the load of the second network decoding device is received from the second network decoding device.

15. The apparatus of claim 13, wherein the instructions are further executable by the processor to cause the apparatus to: monitoring transmissions from the second network decoding device to determine the number and size of transmissions from the second network decoding device; and The load of the second network decoding device is determined based at least in part on the monitoring.

16. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: determining that the second network decoding device sends another acceptance message to the UE to resend the packet; and A determination is made that the second network coding device has stored the packet based at least in part on the second network coding device sending the other accept message to the UE to resend the packet.

17. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: An indication to the second network decoding device to retransmit the packet is sent in the second request based at least in part on the second network decoding device being closest to the UE among a plurality of network decoding devices.

18. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: receiving an indication of a location of each of the plurality of network decoding devices; and Based at least in part on receiving the indication of the location of each of the plurality of network coding devices, determining that the second of the plurality of network coding devices is closest to the UE.

19. The apparatus of claim 18, wherein the indication of the location of each network decoding device is received in a sidelink control information message, a medium access control control element, or a radio resource control message.

20. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: An indication to the second network coding device to resend the packet is sent in the second request based at least in part on a determination that the second network coding device has stored the packet in a buffer.

21. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: sending, in the second request, an instruction to the second network decoding device to resend the packet; and The packet is sent to the second network decoding device based at least in part on determining that the packet is missing from a buffer at the second network decoding device.

22. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of a group of network decoding devices is sent in the second request, each network decoding device in the group being a candidate for retransmitting the packet.

23. The apparatus of claim 12, wherein the instructions for sending the second request for retransmission of the packet are executable by the processor to cause the apparatus to: The packet originally sent by the UE is retransmitted along with the second request for retransmission of the packet.

24. The apparatus of claim 12, wherein the instructions for sending the second request for retransmission of the packet are executable by the processor to cause the apparatus to: A control message is sent along with the second request to the second network decoding device to resend the packet.

25. The apparatus of claim 24, wherein the control message comprises a sidelink control information message, a medium access control control element, or a radio resource control message.

26. A method for wireless communication at a user equipment (UE), the method comprising: sending a first request to a network decoding device to resend a packet originally sent by the UE; receiving an accept message from a first network decoding device indicating that the first network decoding device is to resend the packet; receiving from the first network decoding device a negative acknowledgement of handover from the first network decoding device triggering retransmission of the packet; as well as A second request is sent to a network decoding device to retransmit the packet originally sent by the UE based at least in part on receiving the negative acknowledgement.

27. The method according to claim 26, further comprising: Sending the packet to one or more UEs; as well as Determining that at least one of the one or more UEs failed to receive the packet from the UE, wherein sending the first request to the network coding device to retransmit the packet is based at least in part on the determination.

28. The method according to claim 26, further comprising: An indication is sent in the second request to a second network decoding device to resend the packet originally sent by the UE.

29. The method according to claim 26, further comprising: An indication is sent in the second request to at least one network decoding device to avoid retransmitting the packet originally sent by the UE.

30. The method of claim 26, further comprising: The packet is stored in a buffer at the UE, wherein sending the second request to the network coding device to retransmit the packet is based at least in part on storing the packet in the buffer at the UE.

Images