Faster local NACK triggering

Abstract

Systems and methods are disclosed that relate to Local Negative Acknowledgement, L-NACK, triggering. In one embodiment, a method performed by a first node comprises transmitting an uplink transmission to a second node and receiving a L-NACK request from the second node. The method further comprises, responsive to receiving the L-NACK request from 5 the second node, performing a Layer 2 (L2) retransmission of content contained in the uplink transmission. In this manner, the L-NACK timer, if used, can be shortcut such that the L2 retransmission is transmitted earlier than if the first node had waited for the L-NACK timer to expire, thereby reducing the retransmission delay. Also, if RLC with status reporting is used, the L2 retransmission is performed earlier than if the first node had to wait for the RLC status report 0 to arrive, thus reducing the retransmission delay.

Description

[0001] FASTER LOCAL NACK TRIGGERING

[0002] RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 755,715, filed February 7, 2025, the disclosure of which is hereby incorporated herein by reference in its entirety.

[0004] TECHNICAL FIELD

[0005] The present disclosure relates to a wireless communication system and, more specifically, to Hybrid Automatic Repeat Request (HARQ) in a wireless communications system.

[0006] BACKGROUND

[0007] Research on 6thGeneration (6G) as the next generation of mobile communication system is ongoing. The present disclosure relates to technical components of 6G which are described utilizing existing definitions and descriptions according to 5thGeneration (5G) specifications.

[0008] In regard to 5G user plane protocols, the 3rdGeneration Partnership Project (3GPP) 5G user-plane architecture and protocols are described with help of Figure 1. The User Equipment (UE) is connected over the air via the Uu protocol with the Radio Access Network (RAN), i.e., the gNodeB (gNB). The gNB may be separated into a Distributed Unit (DU) and Centralized Unit (CU), connected via Fl interface. The gNB is connected to the Core Network (CN) including the User-Plane Function (UPF). Typically, Internet Protocol (IP) data is transported via UE-gNB-UPF. The RAN protocol stack between the UE and the gNB includes the Service Data Adaptation Protocol (SDAP) protocol for handling mapping of Quality of Service (QoS) flows as established by the UPF to Data Radio Bearers (DRBs) as established by the gNB. The Protocol Data Convergence Protocol (PDCP) is among others responsible for encryption / integrity protection and handover forwarding and retransmission. For handovers between gNBs, the Xn interface is employed. The Radio Link Control (RLC) is among others responsible for segmentation of higher layer PDCP / IP data to fit within the Transport Blocks (TBs) available for the lower layer over-the-air transmission. Also, retransmissions are based on Automatic Repeat reQuest (ARQ) in acknowledged mode of RLC. The Medium Access Control (MAC) protocol supports scheduling of transmissions over the air and entails the Hybrid Automatic Repeat reQuest (HARQ) protocol. The physical layer (PHY) handles e.g. modulation and coding and the actual physical transmission.In 3GPP radio access networks, e.g. 5G New Radio (NR) networks, the HARQ protocol facilitates retransmissions of data in case of transmission errors over the air. A HARQ entity maintains multiple HARQ processes for data transmission.

[0009] In regard to 5G HARQ, for downlink HARQ, the gNB provides downlink (DL) assignments in the Downlink Control Information (DCI), which is carried on the Physical Downlink Control Channel (PDCCH). The DL data is transmitted on the Physical Downlink Shared Channel (PDSCH). The UE responds with HARQ feedback (HARQ-FB), either a positive acknowledgement (ACK) to confirm successful reception of the data or, if decoding failed, a negative acknowledgement (NACK) to request a retransmission from the gNB. HARQ-FB is provided as part of the Uplink Control Information (UCI), which is carried on the Physical Uplink Control Channel (PUCCH) or alternatively mapped to a Physical Uplink Shared Channel (PUSCH).

[0010] For uplink HARQ, the gNB can grant uplink (UL) data transmission on a HARQ process via Dynamic Grants (DGs) contained in the DCI or semi-statically via Configured Grants (CGs) using Radio Resource Control (RRC) messages. Data is transmitted on the PUSCH. Typically, different Modulation and Coding Schemes (MCS) are applied to PDCCH and PUSCH resulting in different error rates.

[0011] After the initial transmission based on DG or CG, HARQ retransmission(s) of a HARQ process is triggered upon request by gNB based on DCI on PDCCH. The HARQ process may alternatively be overridden by new data, either by dynamic grants with toggled New Data Indicator (NDI) or, if a CG resource is used, after expiry of the ConfiguredGrantTimer, which disallows reuse of a HARQ process while running.

[0012] Due to inaccurate MCS selection, the HARQ protocol may result in residual errors. After a certain number of retransmissions, the gNB may decide to give up on (i.e., suspend) a HARQ process, i.e. it will no longer grant UL retransmissions for that HARQ process, leading to data loss on HARQ. Furthermore, the UE may erroneously detect a false grant on PDCCH, even though the gNB did not send it, leading to undiscoverable HARQ process transmission for which data loss occurs as well.

[0013] For NR with access to shared spectrum (NR-U), the UE also starts the so-called CG-RetransmissionTimer for each UL transmission using the CG. The timer is stopped when the UE receives a HARQ-ACK in the Downlink Feedback Indicator (DFI) carried on PDCCH. If the timer expires, the UE uses the next CG opportunity for a HARQ retransmission.Due to DL / UL scheduling dependencies, PUCCH complexity in general, data loss caused by HARQ NACK-to-ACK errors, or inefficiencies caused by ACK-to-NACK errors, it is proposed for 6G to move UCI including the HARQ-FB from Layer 1 (LI), i.e. PUCCH or UCI on PUSCH, to Layer 2 (L2), i.e. UCI is conveyed in the PUSCH payload, comprising Cyclic Redundancy Check (CRC) and HARQ retransmissions, making HARQ-FB and thus DL HARQ reliable. Furthermore, to counteract against potential DCI misdetection of DL assignments, the network may use a so-called RTX-TimerNW for each HARQ process. The timer is stopped when HARQ-FB is received from the UE. At expiry, the network assumes NACK and triggers LI retransmission (same MCS and allowing soft combining).

[0014] In 5G, the RLC protocol, which resides on top of the HARQ protocol, in Acknowledged Mode (AM) is able to detect and correct HARQ residual errors. Therefore, RLC maintains its own state of which data packets are already successfully received using sequence numbers. This is based on RLC status reporting from the receiver. Counters and timers are employed to poll, trigger, and if needed retransmit RLC status reports and retransmit RLC data until reception success is ensured. RLC status reports are considered data in the HARQ protocol, meaning they undergo HARQ retransmissions in case of unsuccessful reception. The drawback of RLC retransmissions is increased latency.

[0015] After several DL transmission failures of the same HARQ process, the network may suspend the HARQ process and instead perform RLC retransmission, which allows for resegmentation and thus retransmission with a more robust MCS on HARQ, and any soft bits already received by the UE will be discarded for that HARQ process.

[0016] Another trigger for L2 retransmission is the use of a network internal Local-NACK-Timer-NW, which gives the HARQ process a certain time window to convey the DL data, so the timer is stopped when a HARQ-ACK is received from the UE. At expiry, a local NACK is triggered, implying a retransmission on L2 (RLC retransmission).

[0017] In downlink, the MAC Control Element (MAC CE) is used to convey control information which are CRC protected and subject to HARQ retransmissions. Examples for such downlink control information is activation / deactivation commands for carrier aggregation. Uplink control information comprises e.g. configured grant confirmation, recommended bit rate query, Beam Failure Reports (BFR), Timing Advance Reports (TAR), Listen-Before-Talk (LBT) failure reports, and Channel State Information (CSI) reports.SUMMARY

[0018] Systems and methods are disclosed that relate to Local Negative Acknowledgement, L-NACK, triggering. In one embodiment, a method performed by a first node comprises transmitting an uplink transmission to a second node and receiving a L-NACK request from the second node. The method further comprises, responsive to receiving the L-NACK request from the second node, performing a Layer 2 (L2) retransmission of content contained in the uplink transmission. In this manner, the L-NACK timer, if used, can be shortcut such that the L2 retransmission is transmitted earlier than if the first node had waited for the L-NACK timer to expire, thereby reducing the retransmission delay. Also, if Radio Link Control (RLC) with status reporting is used, the L2 retransmission is performed earlier than if the first node had to wait for the RLC status report to arrive, thus reducing the retransmission delay.

[0019] In one embodiment, receiving the L-NACK request comprises receiving Downlink Control Information (DCI) carrying an uplink grant or in a same format as used for an uplink grant, the DCI comprising information that indicates the L-NACK request. In another embodiment, receiving the L-NACK request comprises receiving DCI carrying an uplink grant or in a same format as used for an uplink grant, the DCI comprising an explicit indicator of the L-NACK request. In one embodiment, for either of the above, the DCI carries an uplink grant for the L2 retransmission.

[0020] In one embodiment, receiving the L-NACK request comprises receiving DCI using a same DCI format as used for an uplink grant, but without any uplink resource allocation. In one embodiment, the uplink grant without any uplink resource allocation is an implicit indicator of the L-NACK request. In one embodiment, the method further comprises receiving, from the second node, an uplink grant for the L2 retransmission. In one embodiment, the uplink grant has a toggled new data indicator.

[0021] In one embodiment, receiving the L-NACK request comprises receiving a resegmentation grant (RSG) that provides both the L-NACK request and an uplink grant of uplink resources for the L2 retransmission. In one embodiment, the RSG is realized by a DCI carrying the uplink grant, and the DCI either carries an explicit bit to indicate the RSG or contains a transport block size (TBS) that is different than that of an initial uplink grant for the uplink transmission. In one embodiment, a new data indicator associated with a DCI indicating the L-NACK request is not toggled.

[0022] In one embodiment, the method further comprises discarding one or more uplink grants with non-toggled new data indicator and different transport block size than that used for the uplinktransmission. In one embodiment, receiving the L-NACK request from the second node comprises receiving the L-NACK request from the second node via a payload of a downlink transmission. In either of the above, in one embodiment, the method further comprises, after receiving the L-NACK request without a simultaneous uplink grant, receiving, from the second node, an uplink grant for the L2 retransmission, the uplink grant having a toggled new data indicator. In one embodiment, the uplink grant is for a same HARQ process as that used for the uplink transmission. In another embodiment, the uplink grant is for a different HARQ process than that used for the uplink transmission.

[0023] In one embodiment, the method further comprises, subsequent to performing the L2 retransmission of content contained in the uplink transmission, receiving, from the second node, a HARQ-ACK comprising information that associates the HARQ-ACK to the retransmission.

[0024] In one embodiment, the method further comprises starting a timer upon transmitting the transmission to the second node, wherein the L-NACK request is received from the second node before the timer has expired. In one embodiment, the method further comprises, while the timer at the first node is running, ignoring or discarding any uplink grants received with new data indicator toggled for a same HARQ process as that used for the uplink transmission. In either of the above, in one embodiment, the method further comprises stopping the timer at the first node in response to receiving the L-NACK request.

[0025] In one embodiment, the first node is a User Equipment (UE), and the second node is a network node.

[0026] Corresponding embodiments of a first node are also disclosed. In one embodiment, a first node comprises a communication interface comprising a transmitter and a receiver. The first node further comprises processing circuitry associated with the communication interface. The processing circuitry is configured to cause the first node to transmit an uplink transmission to a second node, receive a L-NACK request from the second node, and, responsive to receiving the L-NACK request from the second node, perform a L2 retransmission of content contained in the uplink transmission.

[0027] In another embodiment, a method performed by a UE comprises transmitting an uplink transmission to a network node and receiving, from the network node, a HARQ-ACK comprising information that associates the HARQ-ACK to the uplink transmission. In one embodiment, the information that associates the HARQ-ACK to the uplink transmission can be transmitted on Layer 1 (LI) e.g. PDCCH, or on L2 as payload on PDSCH.In another embodiment, a method performed by a UE comprises transmitting an uplink transmission to a network node and, while a timer for L-NACK at the UE is running, ignoring or discarding any uplink grants received with new data indicator toggled for a same HARQ process as that used for the uplink transmission. In one embodiment, the method further comprises starting the timer at the UE upon transmitting the uplink transmission.

[0028] In one embodiment, a method performed by a second node comprises receiving an uplink transmission from a first node, failing to successfully decode the uplink transmission, and transmitting a L-NACK request to the first node. The method further comprises, responsive to the L-NACK request, receiving, from the first node, a L2 retransmission of content contained in the uplink transmission.

[0029] Corresponding embodiments of a second node are also disclosed. In one embodiment, a second node comprises processing circuitry configured to cause the second node to receive an uplink transmission from a first node, fail to successfully decode the uplink transmission, transmit a L-NACK request to the first node, and responsive to the L-NACK request, receive, from the first node, a L2 retransmission of content contained in the uplink transmission.

[0030] BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0032] Figure 1 illustrates the 3rdGeneration Partnership Project (3GPP) 5thGeneration (5G) userplane architecture and protocols.

[0033] Figure 2 illustrates a procedure in which a network node (NW) sends a Local Negative Acknowledgement (L-NACK) request to a User Equipment (UE) to trigger Layer 2 (L2) retransmission (RTX), in accordance with an embodiment of the present disclosure.

[0034] Figure 3 illustrates that, due to Physical Downlink Control Channel (PDCCH) errors leading to false detection of a Resegmentation Grant (RSG), data loss could occur when the RSG provides a larger Transport Block Size (TBS) to the UE.

[0035] Figure 4 illustrates an embodiment in which the network sends a local NACK request to trigger local NACK before the UE’s local NACK timer expires and thus accelerates the retransmission procedure.

[0036] Figure 5 illustrates an embodiment in which resegmentation grants are allowed, but the L2 Acknowledgement (ACK) is amended by including information defining the association of the L2Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) to the correct uplink (UL) transmission.

[0037] Figure 6 illustrates an embodiment in which the UE ignores reuse of the same HARQ process while the LocalNACK-TimerUE is running.

[0038] Figure 7 illustrates the operation of a UE and a network node, in accordance with at least some of the embodiments of the present disclosure.

[0039] Figure 8 shows an example of a communication system in accordance with some embodiments.

[0040] Figure 9 is another example of a communication system according to some embodiments. Figure 10 shows a wireless device, which may be configured to operate in communication system of Figure 8 or in communication system of Figure 9.

[0041] Figure 11 shows a network node in accordance with some embodiments.

[0042] Figure 12 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

[0043] DETAILED DESCRIPTION

[0044] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0045] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Additional information may also be found in the document(s) provided in the Appendix.

[0046] There currently exist certain challenge(s). A problem in 3rdGeneration Partnership Project (3GPP) 5thGeneration (5G) systems is that the User Equipment (UE) behavior is undefined when a UE receives an uplink (UL) retransmission grant in which the indicated Modulation and Coding Scheme (MCS) and granted resource allocation would result in a different Transport Block Size (TBS).Certain aspects of the disclosure and the various embodiments may provide solutions to these or other challenges. Embodiments of systems and methods are disclosed herein that allow faster local Negative Acknowledgement (NACK) triggering in the UE’s transmitter.

[0047] In one embodiment, an UL grant for an UL retransmission indicates a resegmentation request before retransmitting the UL data.

[0048] In another embodiment, a network node sends a local Negative Acknowledgement (NACK) request to a UE, which would in a response trigger local NACK in the UE’s Hybrid Automatic Repeat reQuest (HARQ) transmitter.

[0049] Certain embodiments may provide one or more of the following technical advantage(s). By defining new control information, the local NACK timer can be shortcut and Layer 2 (L2) retransmissions can be transmitted earlier to reduce the retransmission delay. By enhancing the UE behavior for the local NACK timer, error cases can be eliminated.

[0050] The teachings of certain embodiments may improve, e.g., data rate, latency, and / or power consumption.

[0051] Now, a more detailed description of some exemplary embodiments of the present disclosure will be provided.

[0052] Embodiments of the present disclosure relate to network-controlled local NACK requests. The local NACK timer in the UE, localNACK-TimerUE, would typically be configured with a duration that allows for one or more HARQ Round Trip Times (RTTs) plus potential scheduling delays to accommodate for multiple transmission attempts. Another alternative would be to restart the localNACK-TimerUE timer at each HARQ transmission (TX) attempt.

[0053] As an UL receiver, a network node (e.g., a Radio Access Network (RAN) node such as, e.g., a base station (e.g., gNB) or a RAN node that provides part of the functionality of a base station (e.g., a Distributed Unit (DU) such as, e.g., a gNB-DU or a Central Unit (CU) such as, e.g., a gNB-CU, in a RAN node having a distributed architecture) or some other RAN node (e.g., a Transmission-Reception Point (TRP)) may estimate a quality of an UL transmission and determine that the selected MCS was unsuitable even with UL retransmissions and may therefore decide to suspend the HARQ process. Instead of waiting for expiry of the localNACK-TmQx\JE to trigger local NACK, the network node instead sends an earlier request to the UE to perform local NACK, such that the content in the HARQ process will be retransmitted on L2.

[0054] Such a local NACK request can be transmitted in Downlink Control Information (DCI) by carrying an UL grant with an explicit bit to request local NACK or by simply sending an UL grant without any UL resources allocation, implying a Transport Block Size (TBS) of zero (i.e., TBS=0).In other words, the L-NACK request may be included in a DCI carrying an UL grant or in a DCI that uses a same format as an UL grant (but possibly without any UL resource allocation or a resource allocation of “null” or “0” or “empty” or “none” or the like). A later UL grant with different TBS would then trigger Radio Link Control (RLC) retransmission with resegmentation.

[0055] In this regard, Figure 2 illustrates a procedure in which a network node (NW) sends a Local NACK (L-NACK) request to a UE to trigger L2 retransmission (RTX), in accordance with an embodiment of the present disclosure. In this example, the network node transmits a UL grant to the UE. Using the UL grant, the UE transmits PUSCH. However, the network node is unable to successfully decode the PUSCH (i.e., there is a decoding error at the network node). In this example, the network node may estimate a quality of the PUSCH transmission and determine that the selected MCS (i.e., the MCS used for the PUSCH transmission) was unsuitable even with UL retransmissions and therefore decides to suspend the associated HARQ process. As discussed above, instead of waiting for expiry of the localNACK- mQv\JE to trigger local NACK, the network node instead sends an earlier request to the UE to perform local NACK such that the content of the HARQ process will be retransmitted on L2. More specifically, in the illustrated example, the network node transmits, to the UE, a resegmentation grant (RSG) on PDCCH, where the RSG requests local NACK and, in one embodiment, simultaneously provides the UE with UL resources for transmission. In the illustrated example, the UE then, in response to the RSG including the request for local NACK, transmits PUSCH using a smaller TBS, which is successfully decoded by the network node and acknowledged by a L2 ACK.

[0056] A special case of the local NACK request is the RSG (see, e.g., the embodiment of Figure 2) which requests local NACK and simultaneously provides the UE with UL resources for transmission. This can be realized by an UL grant DCI

[0057] a) carrying an explicit bit to indicate a resegmentation grant, or

[0058] b) containing a different TBS than the initial grant.

[0059] For both options, the New Data Indicator (NDI) remains non-toggled.

[0060] Due to PDCCH errors leading to false detection of an RSG, data loss could occur when the RSG provides a larger TBS to the UE as illustrated in Figure 3.

[0061] More specifically, as illustrated in Figure 3, first the network node provides a UL grant to the UE and subsequently correctly decodes the corresponding UL transmission. Before the L2 ACK from the network node is correctly received by the UE, the UE receives a false grant with a non-toggled NDI, leading to resegmentation and a transmission of a larger TBS (more data is transmitted than previously granted by the network node). Then, the UE decodes the L2 ACK,which was intended for the first transport block, but the UE interprets it as ACK for the larger transport block, leading to loss of the excess bits.

[0062] In one embodiment, such an error case is eliminated by disallowing such resegmentation grants, i.e. defining that the UE is to discard UL grants with non-toggled NDI and different TBS.

[0063] In a dependent embodiment, the NW sends a local NACK request to trigger local NACK before the UE’s local NACK timer expires and thus accelerates the retransmission procedure, as illustrated in Figure 4. The NW waits until this local NACK request (sent as payload on PDSCH) is correctly received before sending a new UL grant to the UE using another HARQ process or the same HARQ process as used for the original transmission, however with toggled NDI. When the UE receives a local NACK request from the NW, the UE stops its transmitter’s local NACK timer (localNACK-Timer UE).

[0064] In an alternative embodiment, resegmentation grants are allowed, but the L2 ACK is amended by including information defining the association of the L2 HARQ-ACK to the correct UL transmission as illustrated in Figure 5. One example is to use a timestamp, e.g. a slot identifier (ID) in the L2 HARQ-ACK. Another possibility would be to add a transmission indicator or index in the UL transmission (as part of the UL grant increasing the DCI) or as additional information carried in the PUSCH payload, and the NW adds this transmission ID to the L2 HARQ-ACK in the transmitted L2 HARQ-FB. The use of a transmission ID is expected to add less overhead than a timestamp.

[0065] In another embodiment, the UE ignores reuse of the same HARQ process while the LocalNACK-TimerUE is running as illustrated in Figure 6. This alleviates the risk of receiving false grants and overriding not yet received data. This embodiment allows the network to send a local NACK request (without extra grant) while the timer is running. The timer is stopped, and the L2 retransmission can be performed on any HARQ process (the same or a different HARQ process) at a later time sequence. Neither resegmentation grants nor new data grants would be allowed with this embodiment. Compared to the resegmentation grant only, the risk of receiving a false local NACK request plus a false grant for any HARQ process would be less likely.

[0066] Figure 7 illustrates the operation of a UE 700 and a network node 702, in accordance with at least some of the embodiments described above. Optional steps or actions are represented in Figure 7 by dashed lines or dashed boxes. Note that not all of the details provided above regarding the various embodiments described herein are repeated here with respect to Figure 7; however, it is to be understood that the details provided above are equally applicable to the corresponding steps or actions shown in Figure 7. It should also be noted that while the procedure of Figure 7 isdescribed with respect to the UE 700 (as the transmitting node) and the network node 702 (as the receiving node), the procedure may be used for transmission / retransmission between any two radio nodes (e.g., two UEs, a UE and a network node, or the like).

[0067] As illustrated, the UE 700 transmits a UL transmission (e.g., a PUSCH transmission) to the network node 702 (block 704). The UE 700 may, upon transmitting the UL transmission, start an L-NACK timer at the UE 700 (block 706). The network node 702 fails to successfully decode the UL transmission (block 708) and decides to transmit an L-NACK request to the UE 700. The network node 702 transmits an L-NACK request to the UE 700 (block 712). Further details regarding numerous variations / embodiments of the L-NACK request are described above and equally applicable here to step 712.

[0068] Note that, prior to the transmission of the L-NACK request by the network node 702 (and reception of the L-NACK request by the UE 700), the UE 700 may, in some embodiments, discard any received UL grants (e.g., in RSGs) with non-toggled NDI and different TBS than the TBS used for the UL transmission of step 704 (block 710). The action in Step 710 may be beneficial to address the problem of false resegmentation grants, as described above with respect to Figures 3 and 4.

[0069] Upon receiving the L-NACK request at the UE 700, the UE 700, in some embodiments, stops the L-NACK timer (block 714). In one embodiment (see Figure 6), the UE 716 may not stop the L-NACK timer upon receiving the L-NACK request, and the UE ignores or discards any UL grants with NDI toggled for the same as that used by the UL transmission of step 704, while the L-NACK timer 714 is running (block 716).

[0070] The network node 702, in some embodiments (see, e.g., Figure 4), transmits an UL grant for an L2 retransmission of the content of the UL transmission of step 704 (block 718).

[0071] In response to the L-NACK request and optionally the UL grant (if not already included with the L-NACK request), the UE 700 transmits an L2 retransmission of the content of the UL transmission (block 720). Optionally, the network node 702 transmits, to the UE 700, an L2 ACK (e.g., in response to successfully decoding the L2 retransmission) (block 722). In one embodiment (see, e.g., Figure 5), the L2 ACK includes information that associates the L2 ACK with the correct UL transmission.

[0072] Figure 8 shows an example of a communication system 800 in accordance with some embodiments.

[0073] In the example, the communication system 800 includes a telecommunications network 802 that includes an access network 804, such as a radio access network (RAN), and a core network806, which includes one or more core network nodes 808. The access network 804 includes one or more access network nodes or base stations of various types, access network nodes 810A and 81 OB are depicted (which may be collectively referred to as network nodes 810), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 804 may include more than one access network technology. The network nodes 810 of access network 804 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 812A, 812B, 812C, and 812D (one or more of which may be generally referred to as UEs 812) to the core network 806 over one or more wireless connections.

[0074] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 802 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 802 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 802, including one or more access network nodes 810 and / or core network nodes 808.

[0075] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or anon-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.The network nodes 810 facilitate direct or indirect connection of one or more UEs 812 to the core network 806 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 800 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 800 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0076] The UEs 812 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 810 and other communication devices. Similarly, the network nodes 808, 810 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 802) with the UEs 812 and / or with other network nodes or equipment in the telecommunications network 802 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 802. More specifically, UEs 812 may send messages, data, and / or other signals to network nodes 808, 810 or other elements of the telecommunications network 802 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 808, 810 may send messages, data, and other signals to UEs 8122, other network nodes 808, 810, and other devices in telecommunications network 802 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 812 by transmitting the message to an access network node 810 that will then transmit the message to the intended UE 812. Similarly, a core network node 108 may receive a particular message from a UE 812 by receiving the message from an access network node 810 that itself received the message from the UE 812.

[0077] In the depicted example, the core network 806 connects elements of the access network 804 (e.g., one or more of the network nodes 810) to one or more host computing systems, such as host 816. These connections may be direct or indirect via one or more intermediary networks ordevices. In other examples, network nodes may be directly coupled to hosts. The core network 806 includes one or more core network nodes (e.g., core network node 808) of various types, one or more of which may be generally referred to as network nodes 808. Network nodes 808 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 808. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0078] The host 816 may be under the ownership or control of a service provider other than an operator or provider of the access network 804 and / or the telecommunications network 802. The host 816 may be operated by the service provider or on behalf of the service provider. The host 816 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0079] As a whole, the communication system 800 of Figure 8 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 800 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 800 may be configured to support multiple different standards, protocols, or other rule sets, with individual componentssupporting all of the relevant rule sets or with different components or sub-systems within the communication system 800 supporting different standards, protocols, or rule sets.

[0080] As one example, in certain embodiments, access network 804 may contain some access network nodes 810 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 810 support (or the same access network nodes 810 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 802 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

[0081] Telecommunications network 802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 802. For example, the telecommunications network 802 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0082] In some examples, one or more of the UEs 812 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 804. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0083] In the example, the hub 814 communicates with the access network 804 to facilitate indirect communication between one or more UEs (e.g., UE 812C and / or 812D) and network nodes (e.g., network node 810B). In some examples, the hub 814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 814 may be a broadband router enabling access to the core network 806 for the UEs. As another example, the hub 814 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 810, or by executable code, script, process, or other instructions in the hub 814.As another example, the hub 814 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 814 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 814 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 814 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0084] The hub 814 may have a constant / persistent or intermittent connection to the network node 810B. The hub 814 may also allow for a different communication scheme and / or schedule between the hub 814 and UEs (e.g., UE 812C and / or 812D), and between the hub 814 and the core network 806. In other examples, the hub 814 is connected to the core network 806 and / or one or more UEs via a wired connection. Moreover, the hub 814 may be configured to connect to an M2M service provider over the access network 804 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 810 while still connected via the hub 814 via a wired or wireless connection. In some embodiments, the hub 814 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 810B. In other embodiments, the hub 814 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 81 OB, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0085] Figure 9 is another example of a communication system 900 according to some embodiments. As used herein, the communication system 900 includes multiple access points (APs) 910 (with four exemplary APs 910A, 910B, 910C, and 910D being depicted) and multiple wireless devices, referred to in the context of communication system 900 as stations (STAs) 912 (referred to individually as STA 912A, STA 912B, STA 912C, STA 912D, and STA 912E). STA 912A is served by AP 910A in a first basic service set (BSS) 920 A. STA 910B and STA 910C are served by AP 910B in a second BSS, BSS 920B. STA 912D is served by AP 910C in a third BSS, BSS 920C. STA 912E is served by AP 910D in a fourth BSS, BSS 920D. Stations 912 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 912 could, for example,correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0086] Each of STAs 912 may connect through a radio link to one of APs 910. For example, depending on location or channel conditions experienced by a given STA 912, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0087] Each AP 910 may provide data connectivity to STAs 912 connected to a particular AP 910. As illustrated, APs 910 may be connected to a data network 930. In this way, APs 910 may also provide data connectivity between STAs 912 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 912 and its serving AP 910 may be used for providing various kinds of services to STA 912, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 912 and / or on a device linked to STA 912. By way of example, Figure 9 illustrates an application service platform 932 provided in data network 930. The application(s) executed on STA 912 and / or on one or more other devices linked to STA 912 may use the radio link for data communication with one or more other STA 912 and / or the application service platform 932, thereby enabling utilization of the corresponding service(s) at STA 912.

[0088] Figure 10 shows a wireless device 1000, which may be configured to operate in communication system 800 of Figure 8 or in communication system 900 of Figure 9. The wireless device 1000 may be alternatively referred to as a UE 1000, like a UE 812 within the context of communication system 800, or as a station (STA) 1000 or as a non-access-point station (non-AP STA) 1000, like a STA 912 within the context of the communication system 900, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smartdevice, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0089] A wireless device 1000 may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 1000 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 1000 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 1000 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0090] In particular embodiments, wireless device 1000 includes processing circuitry 1002 that is operatively coupled via a bus 1004 to an input / output interface 1006, a power source 1008, a memory 1010, a communication interface 1012, and / or any other component, or any combination thereof. Certain embodiments of wireless device 1000 may include all or a subset of the components shown in Figure 10. The level of integration between the components may vary from one embodiment of wireless device 1000 to another. In general, in a particular embodiment of wireless device 1000, processing circuitry 1002, input / output interface 1006, power source 1008, memory 1010, and communication interface 1012 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 1000. Further, certain embodiments of wireless devices 1000 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

[0092] In the example, the input / output interface 1006 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 1000. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0093] In some embodiments, the power source 1008 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 1008 may further include power circuitry for delivering power from the power source 1008 itself, and / or an external power source, to the various parts of wireless device 1000 via input circuitry or an interface such as an electrical power cable. Power source 1008 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 1000 to which power is supplied.

[0094] The memory 1010 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1010 includes one or more programs 1014, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1016. The memory 1010 may store, for use by wireless device 1000, any of a variety of various operating systems or combinations of operating systems.The memory 1010 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1010 may allow wireless device 1000 to access instructions, programs, and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1010, which may be or comprise a device-readable storage medium.

[0095] The processing circuitry 1002 may be configured to communicate with an access network or other network via or using the communication interface 1012. The communication interface 1012 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1022. The communication interface 1012 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 1018 and / or a receiver 1020 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1018 and receiver 1020 may be coupled to one or more antennas (e.g., antenna 1022) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0096] In the illustrated embodiment, communication functions of the communication interface 1012 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CodeDivision Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0097] In particular embodiments, wireless device 1000 may provide an output of data captured via a sensor, through its communication interface 1012, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 1000 can be communicated through a wireless connection to a network node via another wireless device 1000. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0098] As another example, wireless device 1000 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 1000 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0099] Wireless device 1000, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 1000 represents an loT device that comprises circuitry and / or software independence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 1000 shown in Figure 10.

[0100] As yet another specific example, in an loT scenario, wireless device 1000 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 1000 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 1000 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 1000 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0101] In practice, any number of wireless devices 1000 may be used together with respect to a single use case. For example, a first wireless device 1000 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 1000 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 1000 may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 1000 can also include more than one of the functionalities described above. For example, wireless device 1000 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0102] Figure 11 shows a network node 1100 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 1100 may be configured to operate in communication system 800 of Figure 8, like network nodes 808 or 810, or in communication system 900 of Figure 9, like an AP 910 or a station 912. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0103] Network nodes 1100 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 1100 may be a relay node or a relay donor node controlling a relay. Network nodes 1100 may also include one or more (or all) parts of a distributed radio basestation such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0104] Other examples of network nodes 1100 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0105] In particular embodiments, network node 1100 includes a processing circuitry 1102, a memory 1104, a communication interface 1106, and a power source 1108. In general, in a particular embodiment of network node 1100, processing circuitry 1102, memory 1104, communication interface 1106, and power source 1108 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 1100.

[0106] The network node 1100 may be composed of multiple distinct network entities (e.g., a NodeB entity and an RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 1100 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1100 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 1104 or portions of memory 1104 for different RATs) and some components may be reused (e.g., a same antenna 1110 may be shared by different RATs). The network node 1100 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1100, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wirelesstechnologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1100.

[0107] The processing circuitry 1102 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 1104, to provide network node 1100 functionality.

[0108] In some embodiments, the processing circuitry 1102 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1102 includes one or more of radio frequency (RF) transceiver circuitry 1112 and baseband processing circuitry 1114. In some embodiments, the RF transceiver circuitry 1112 and the baseband processing circuitry 1114 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1112 and baseband processing circuitry 1114 may be on the same chip or set of chips, boards, or units.

[0109] The memory 1104 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1102. The memory 1104 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1102 and utilized by the network node 1100. The memory 1104 may be used to store any calculations made by the processing circuitry 1102 and / or any data received via the communication interface 1106. In some embodiments, the processing circuitry 1102 and memory 1104 is integrated.

[0110] The communication interface 1106 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 1106 comprises port(s) / terminal(s) 1116 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 1000 may be capable of wireless communication and communicationinterface 1106 may also include radio front-end circuitry 1118 that may be coupled to, or in certain embodiments a part of, an antenna 1110. Particular embodiments of radio front-end circuitry 1118 include filter(s) 1120 and amplifier(s) 1122. The radio front-end circuitry 1118 may be connected to an antenna 1110 and processing circuitry 1102. The radio front-end circuitry may be configured to condition signals communicated between antenna 1110 and processing circuitry 1102. The radio front-end circuitry 1118 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1118 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 1120 and / or amplifiers 1122. The radio signal(s) may then be transmitted via the antenna 1110. Similarly, when receiving data, the antenna 1110 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1118. The digital data may be passed to the processing circuitry 1102. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0111] In certain alternative embodiments, network node 1100 may be capable of wireless communication but does not include separate radio front-end circuitry 1118, instead, the processing circuitry 1102 includes radio front-end circuitry and is connected to the antenna 1110. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1112 is part of the communication interface 1106. In still other embodiments, the communication interface 1106 includes one or more ports or terminals 1116, the radio front-end circuitry 1118, and the RF transceiver circuitry 1112, as part of a radio unit (not shown), and the communication interface 1106 communicates with the baseband processing circuitry 1114, which is part of a digital unit (not shown).

[0112] The antenna 1110 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1110 may be coupled to the radio front-end circuitry 1118 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1110 is separate from the network node 1100 and connectable to the network node 1100 through one or more interfaces or ports.

[0113] The antenna 1110, communication interface 1106, and / or the processing circuitry 1102 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 1100. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 1110, the communication interface 1106, and / or the processing circuitry 1102 may be configured to perform some or all of the transmitting or sending operations describedherein as being performed by the network node 1100. Any information, data and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0114] The power source 1108 provides power to the various components of network node 1100 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1108 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1100 with power for performing the functionality described herein. For example, the network node 1100 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1108. As a further example, the power source 1108 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0115] Embodiments of the network node 1100 may include additional components beyond those shown in Figure 11 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1100 may include user interface equipment to allow input of information into the network node 1100 and to allow output of information from the network node 1100. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1100.

[0116] Figure 12 is a block diagram illustrating a virtualization environment 1200 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1200 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1200 includes components defined by the O-RAN Alliance, such as an O-Cloudenvironment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0117] Applications 1202 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1100 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0118] Hardware 1204 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1206 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 1208A and VM 1208B (which may be collectively referred to as VMs 1208), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1206 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 1208.

[0119] The VMs 1208 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 1206. Different embodiments of the instance of a virtual appliance 1202 may be implemented on one or more of VMs 1208, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0120] In the context of NFV, each of the VMs 1208 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1208, and that part of hardware 1204 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 1208 on top of the hardware 1204 and corresponds to an application 1202.

[0121] Hardware 1204 may be implemented in a standalone network node with generic or specific components. Hardware 1204 may implement some functions via virtualization. Alternatively, hardware 1204 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE)where many hardware nodes work together and are managed via management and orchestration 1210, which, among others, oversees lifecycle management of applications 1202. In some embodiments, hardware 1204 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1212 which may alternatively be used for communication between hardware nodes and radio units.

[0122] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0123] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readablestorage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0124] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

[0125] Group A Embodiments

[0126] Embodiment 1: A method performed by a first node, e.g. a User Equipment, UE, the method comprising: transmitting (704) an uplink transmission to a second node, e.g. a network node; receiving (712) a local Negative Acknowledgement, L-NACK, request from the second node (e.g., before a L-NACK timer at the first node, which was started upon transmitting the uplink transmission, has expired); and responsive to the L-NACK request received from the second node, performing (720) a Layer 2, L2, retransmission of content contained in the uplink transmission.

[0127] Embodiment 2: The method of embodiment 1, wherein receiving (712) the L-NACK request comprises receiving Downlink Control Information (DCI) (e.g., a DCI carrying an uplink grant or in a same format as used for an uplink grant) indicating the L-NACK request.

[0128] Embodiment 3: The method of embodiment 1, wherein receiving (712) the L-NACK request comprises receiving a DCI (e.g., a DCI carrying an uplink grant or in a same format as used for an uplink grant) including an explicit indicator (e.g., bit) of the L-NACK request.

[0129] Embodiment 4: The method of embodiment 1, wherein receiving (712) the L-NACK request comprises receiving a DCI using the same DCI format as used for an uplink grant, but without any uplink resource allocation.

[0130] Embodiment 5 : The method of embodiment 4, wherein the uplink grant without any uplink resource allocation is an implicit indicator of the L-NACK request.

[0131] Embodiment 6: The method of any of embodiments 2 to 5, further comprising receiving (718), from the network node, an uplink grant for the L2 retransmission.

[0132] Embodiment 7: The method of embodiment 1, wherein receiving (712) the L-NACK request comprises receiving a resegmentation grant, RSG, that provides both the L-NACK request and an uplink grant of uplink resources for the L2 retransmission.Embodiment 8: The method of embodiment 6 or 7, wherein a new data indicator associated with a DCI indicating the L-NACK request is not toggled.

[0133] Embodiment 9: The method of embodiment 1, further comprising discarding (710) one or more uplink grants with non-toggled new data indicator and different transport block size than that used for the uplink transmission.

[0134] Embodiment 10: The method of embodiment 9, wherein receiving (712) the L-NACK request from the network node comprises receiving (712) the L-NACK request from the network node via a payload of a downlink transmission (e.g., via a payload of a PDSCH).

[0135] Embodiment 11: The method of embodiment 10, wherein the discarding of uplink grants (710) is performed prior to receiving (712) the L-NACK request.

[0136] Embodiment 12: The method of embodiment 10 or 11, further comprising receiving (718), from the network node, an uplink grant for the L2 retransmission, the uplink grant having a toggled new data indicator.

[0137] Embodiment 13: The method of embodiment 12, wherein the uplink grant is for a same HARQ process as that used for the uplink transmission.

[0138] Embodiment 14: The method of embodiment 12, wherein the uplink grant is for a different HARQ process than that used for the uplink transmission.

[0139] Embodiment 15: The method of any of embodiments 1 to 14, further comprising receiving (722), from the network node, a L2 HARQ-ACK comprising information that associates the L2 HARQ-ACK to a correct transmission (e.g., the L2 retransmission).

[0140] Embodiment 16: The method of any of embodiments 1 to 15, further comprising, while a timer for L-NACK at the UE is running (e.g., while an L-NACK timer that is started upon transmitting the uplink transmission is running), ignoring or discarding (716) any uplink grants received with new data indicator toggled for a same HARQ process as that used for the uplink transmission.

[0141] Embodiment 17: The method of any of embodiments 1 to 16, further comprising stopping (714) a L-NACK timer at the UE in response to receiving the L-NACK request.

[0142] Embodiment 18: A method performed by a User Equipment, UE, the method comprising: transmitting (704) an uplink transmission to a network node; and receiving (722), from the network node, an HARQ-ACK (e.g., L2 HARQ-ACK) comprising information that associates the HARQ-ACK to the uplink transmission.

[0143] Embodiment 19: A method performed by a User Equipment, UE, the method comprising: transmitting (704) an uplink transmission to a network node; and while a timer for L-NACK at theUE is running (e.g., while an L-NACK timer that is started upon transmitting the uplink transmission is running), ignoring or discarding (716) any uplink grants received with new data indicator toggled for a same HARQ process as that used for the uplink transmission.

[0144] Embodiment 20: The method of embodiment 19, further comprising starting (706) an L-NACK timer at the UE upon transmitting the uplink transmission.

[0145] Embodiment 21: The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.

[0146] Group B Embodiments

[0147] Embodiment 22: A method performed by a network node, the method comprising: receiving (704) an uplink transmission (e.g., PUSCH transmission) from a User Equipment, UE; failing (708) to successfully decode the uplink transmission; transmitting (712) a local Negative Acknowledgement, L-NACK, request to the UE (e.g., before a L-NACK timer at the UE, which was started upon transmitting the uplink transmission, has expired); and responsive to the L-NACK request, receiving (720), from the UE, a Layer 2, L2, retransmission of content contained in the uplink transmission.

[0148] Embodiment 23: The method of embodiment 22, wherein transmitting (712) the L-NACK request comprises transmitting an uplink grant with an explicit indicator (e.g., bit) of the L-NACK request.

[0149] Embodiment 24: The method of embodiment 22, wherein transmitting (712) the L-NACK request comprises transmitting an uplink grant without any uplink resource allocation.

[0150] Embodiment 25: The method of embodiment 24, wherein the uplink grant without any uplink resource allocation is an implicit indicator of the L-NACK request.

[0151] Embodiment 26: The method of any of embodiments 23 to 25, further comprising transmitting (718), to the UE, an uplink grant for the L2 retransmission.

[0152] Embodiment 27: The method of embodiment 22, wherein transmitting (712) the L-NACK request comprises transmitting a resegmentation grant, RSG, that provides both the L-NACK request and an uplink grant of uplink resources for the L2 retransmission.

[0153] Embodiment 28: The method of embodiment 26 or 27, wherein a new data indicator associated with the uplink grant is not toggled.Embodiment 29: The method of embodiment 22, wherein transmitting (712) the L-NACK request to the UE comprises transmitting (712) the L-NACK request to the UE via a payload of a downlink transmission (e.g., via a payload of a PDSCH).

[0154] Embodiment 30: The method of embodiment 29, further comprising transmitting (718), to the UE, an uplink grant for the L2 retransmission, the uplink grant having a toggled new data indicator.

[0155] Embodiment 31: The method of embodiment 30, wherein the uplink grant is for a same HARQ process as that used for the uplink transmission.

[0156] Embodiment 32: The method of embodiment 30, wherein the uplink grant is for a different HARQ process than that used for the uplink transmission.

[0157] Embodiment 33: The method of any of embodiments 22 to 32, further comprising transmitting (722), to the UE, a L2 ACK comprising information that associates the L2 ACK to a correct transmission (e.g., the L2 retransmission).

[0158] Embodiment 34: A method performed by a network node, the method comprising: receiving (704) an uplink transmission from a User Equipment, UE; and transmitting (722), to the UE, an ACK (e.g., L2 ACK) comprising information that associates the ACK to the uplink transmission.

[0159] Embodiment 35: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

[0160] Group C Embodiments

[0161] Embodiment 36: A wireless device comprising: processing circuitry configured to perform any of the operations of any of the Group A embodiments; and a power source configured to supply power to the processing circuitry.

[0162] Embodiment 37: A network node comprising: processing circuitry configured to perform any of the operations of any of the Group B embodiments; and a power source circuitry configured to supply power to the processing circuitry.

[0163] Embodiment 38: A wireless device comprising: one or more antennas; communication interface connected to the one or more antennas and to processing circuitry; the processing circuitry being configured to perform any of the operations of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has beenprocessed by the processing circuitry; and a power source connected to the processing circuitry and configured to supply power to the UE.

Claims

CLAIMS1. A method performed by a first node, the method comprising:transmitting (704) an uplink transmission to a second node;receiving (712) a local Negative Acknowledgement, L-NACK, request from the second node; andresponsive to receiving (712) the L-NACK request from the second node, performing (720) a Layer 2, L2, retransmission of content contained in the uplink transmission.

2. The method of claim 1, wherein receiving (712) the L-NACK request comprises receiving Downlink Control Information, DCI, carrying an uplink grant or in a same format as used for an uplink grant, the DCI comprising information that indicates the L-NACK request.

3. The method of claim 1, wherein receiving (712) the L-NACK request comprises receiving Downlink Control Information, DCI, carrying an uplink grant or in a same format as used for an uplink grant, the DCI comprising an explicit indicator of the L-NACK request.

4. The method of claim 2 or 3, wherein the DCI carries an uplink grant for the L2 retransmission.

5. The method of claim 1, wherein receiving (712) the L-NACK request comprises receiving Downlink Control Information, DCI, using a same DCI format as used for an uplink grant, but without any uplink resource allocation.

6. The method of claim 5, wherein the uplink grant without any uplink resource allocation is an implicit indicator of the L-NACK request.

7. The method of claim 5 or 6, further comprising receiving (718), from the second node, an uplink grant for the L2 retransmission.

8. The method of claim 7, wherein the uplink grant has a toggled new data indicator.

9. The method of claim 1, wherein receiving (712) the L-NACK request comprises receiving a resegmentation grant, RSG, that provides both the L-NACK request and an uplink grant of uplinkresources for the L2 retransmission.

10. The method of claim 9, wherein the RSG is realized by a Downlink Control Information, DCI, carrying the uplink grant, and the DCI either carries an explicit bit to indicate the RSG or contains a transport block size, TBS, that is different than that of an initial uplink grant for the uplink transmission.

11. The method of claim 10, wherein a new data indicator associated with a DCI indicating the L-NACK request is not toggled.

12. The method of claim 1, further comprising discarding (710) one or more uplink grants with non-toggled new data indicator and different transport block size than that used for the uplink transmission.

13. The method of claim 12, wherein receiving (712) the L-NACK request from the second node comprises receiving (712) the L-NACK request from the second node via a payload of a downlink transmission.

14. The method of claim 12 or 13, further comprising, after receiving the L-NACK request without a simultaneous uplink grant, receiving (718), from the second node, an uplink grant for the L2 retransmission, the uplink grant having a toggled new data indicator.

15. The method of claim 14, wherein the uplink grant is for a same HARQ process as that used for the uplink transmission.

16. The method of claim 14, wherein the uplink grant is for a different HARQ process than that used for the uplink transmission.

17. The method of any of claims 1 to 16, further comprising, subsequent to performing (720) the L2 retransmission of content contained in the uplink transmission, receiving (722), from the second node, a HARQ-ACK comprising information that associates the HARQ-ACK to the retransmission.

18. The method of any of claims 1 to 17, further comprising:starting (706) a timer upon transmitting (704) the transmission to the second node; wherein the L-NACK request is received from the second node before the timer has expired.

19. The method of claim 18, further comprising, while the timer at the first node is running, ignoring or discarding (716) any uplink grants received with new data indicator toggled for a same HARQ process as that used for the uplink transmission.

20. The method of claim 18 or 19, further comprising stopping (714) the timer at the first node in response to receiving the L-NACK request.

21. The method of any of claims 1 to 20, wherein the first node is a User Equipment, UE, and the second node is a network node.

22. A first node adapted to:transmit (704) an uplink transmission to a second node;receive (712) a local Negative Acknowledgement, L-NACK, request from the second node; andresponsive to receiving (712) the L-NACK request from the second node, perform (720) a Layer 2, L2, retransmission of content contained in the uplink transmission.

23. The first node of claim 22, further adapted to perform the method of any of claims 2 to 21.

24. A first node comprising:a communication interface (1012) comprising a transmitter (1018) and a receiver (1020); andprocessing circuitry (1002) associated with the communication interface (1012), the processing circuitry (1012) configured to cause the first node to:transmit (704) an uplink transmission to a second node;receive (712) a local Negative Acknowledgement, L-NACK, request from the second node; andresponsive to receiving (712) the L-NACK request from the second node, perform(720) a Layer 2, L2, retransmission of content contained in the uplink transmission.

25. The first node of claim 24, wherein the processing circuitry is further configured to cause the first node to perform the method of any of claims 2 to 21.

26. A method performed by a User Equipment, UE, the method comprising:transmitting (704) an uplink transmission to a network node; andreceiving (722), from the network node, a Hybrid Automatic Repeat Request, HARQ, -Acknowledgement, ACK, comprising information that associates the HARQ-ACK to the uplink transmission.

27. A method performed by a User Equipment, UE, the method comprising:transmitting (704) an uplink transmission to a network node; andwhile a timer for local Negative Acknowledgement, L-NACK, at the UE is running, ignoring or discarding (716) any uplink grants received with new data indicator toggled for a same Hybrid Automatic Repeat Request, HARQ, process as that used for the uplink transmission.

28. The method of claim 27, further comprising starting (706) the timer at the UE upon transmitting the uplink transmission.

29. A method performed by a second node, the method comprising:receiving (704) an uplink transmission from a first node;failing (708) to successfully decode the uplink transmission;transmitting (712) a local Negative Acknowledgement, L-NACK, request to the first node; andresponsive to the L-NACK request, receiving (720), from the first node, a Layer 2, L2, retransmission of content contained in the uplink transmission.

30. The method of claim 29, wherein transmitting (712) the L-NACK request comprises transmitting an uplink grant with an explicit indicator of the L-NACK request.

31. The method of claim 30, wherein the uplink grant comprises an uplink resource allocation for the L2 retransmission.

32. The method of claim 29, wherein transmitting (712) the L-NACK request comprises transmitting an uplink grant without any uplink resource allocation.

33. The method of claim 32, wherein the uplink grant without any uplink resource allocation is an implicit indicator of the L-NACK request.

34. The method of claim 32 or 33, further comprising transmitting (718), to the first node, an uplink grant for the L2 retransmission.

35. The method of claim 29, wherein transmitting (712) the L-NACK request comprises transmitting a resegmentation grant, RSG, that provides both the L-NACK request and an uplink grant of uplink resources for the L2 retransmission.

36. The method of claim 35, wherein a new data indicator associated with the uplink grant is not toggled.

37. The method of claim 29, wherein transmitting (712) the L-NACK request to the first node comprises transmitting (712) the L-NACK request to the first node via a payload of a downlink transmission.

38. The method of claim 37, further comprising transmitting (718), to the first node, an uplink grant for the L2 retransmission, the uplink grant having a toggled new data indicator.

39. The method of claim 38, wherein the uplink grant is for a same Hybrid Automatic Repeat Request, HARQ, process as that used for the uplink transmission.

40. The method of claim 38, wherein the uplink grant is for a different HARQ process than that used for the uplink transmission.

41. The method of any of claims 29 to 40, further comprising transmitting (722), to the first node, a ACK comprising information that associates the ACK to the L2 retransmission.

42. The method of any of claims 29 to 41, wherein the first node is a User Equipment, UE, and the second node is a network node.

43. A second node adapted to:receive (704) an uplink transmission from a first node;fail (708) to successfully decode the uplink transmission;transmit (712) a local Negative Acknowledgement, L-NACK, request to the first node; and responsive to the L-NACK request, receive (720), from the first node, a Layer 2, L2, retransmission of content contained in the uplink transmission.

44. The second node of claim 43, further adapted to perform the method of any of claims 30 to 42.

45. A second node comprising processing circuitry (1102) configured to cause the second node to:receive (704) an uplink transmission from a first node;fail (708) to successfully decode the uplink transmission;transmit (712) a local Negative Acknowledgement, L-NACK, request to the first node; and responsive to the L-NACK request, receive (720), from the first node, a Layer 2, L2, retransmission of content contained in the uplink transmission.

46. The second node of claim 45, wherein the processing circuitry is further configured to cause the second node to perform the method of any of claims 30 to 42.

47. A method performed by a second node, the method comprising:receiving (704) an uplink transmission from a first node; andtransmitting (722), to the first node, a Hybrid Automatic Repeat Request, HARQ, -Acknowledgement, ACK, comprising information that associates the HARQ-ACK to the uplink transmission.

Images