BR112017003821B1 - METHODS, WIRELESS DEVICES AND NETWORK NODES OF A WIRELESS COMMUNICATION SYSTEM - Google Patents

Abstract

METHODS, WIRELESS DEVICES, NETWORK NODES OF A WIRELESS COMMUNICATION SYSTEM AND COMPUTER READABLE MEDIA. Techniques are described according to which a signal is transmitted from a wireless network to a wireless device, requesting automatic repeat request, ARQ, feedback to certain indicated ARQ processes. This asynchronous approach addresses a problem with irregular ARQ feedback for dynamic time-division duplexing, and also allows for relaxed processing time constraints on the wireless device. An example method, in a wireless device, comprises receiving (610), from a wireless communication network, in a first transmission time slot, an ARQ feedback request, the request indicating one or more ARQ processes. . The exemplary method further comprises transmitting (620), to the wireless communication network, in a second transmission time slot, ARQ feedback information for each of the one or more indicated ARQ processes.

Description

FIELD OF INVENTION

[001] The technology disclosed herein in the present invention relates, in general, to wireless communication networks, and, more particularly, relates to techniques involving automatic repeat request (ARQ) feedback in such networks.

FUNDAMENTALS OF THE TECHNIQUE

[002] Automatic Repeat Request (ARQ) is an error control technique used in many wireless networks. With ARQ, a receiver of data transmissions sends acknowledgments (ACKs) or negative acknowledgments (NACKs), referred to as "ARQ feedback", to inform the sender whether each message was correctly received. Incorrectly received messages, as well as messages that are not recognized, can then be retransmitted.

[003] Hybrid ARQ (HARQ), which can be understood as a refined form of ARQ, combines the basic ARQ techniques described above with forward error correction coding (FEC) of data messages, to improve the receiver's ability to receive and correctly decode transmitted messages. As with conventional ARQ, receivers employing HARQ send ACKs and NACKs, as appropriate, after each attempt to decode a message. These ACKs and NACKs are referred to as "HARQ feedback".

[004] The fourth generation system widely known as LTE (for Long Term Evolution) and more formally known as the Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) was developed and implemented by elements of the 3rd Generation Partnership Project Generation (3GPP). For downlink transmissions in LTE today, HARQ feedback is sent from the UE (user equipment - 3GPP terminology for a mobile terminal) to the network on both the Physical Uplink Control Channel (PUCCH) and the Link Shared Channel Physical Uplink (PUSCH), depending on whether or not the UE has been scheduled for uplink PUSCH transmission.

[005] For each downlink transmission to the UE, the UE will transmit an ACK or NACK, depending on whether the transmission was correctly received or not. The network may also, apart from detection of ACK or NACK, draw the conclusion that the UE did not properly receive the corresponding downlink assignment and thus did not even attempt to demodulate and decode the transmitted data message, if the network does not detect feedback from the UE when anticipated. Note, however, that a missing ACK/NACK detection on the network side may also be due to the failure of the network to receive it properly, even though it was transmitted by the UE.

[006] A NACK received by the network will trigger a retransmission, while reception of an ACK allows the corresponding HARQ transmission (Tx) process to be emptied and reused. That a Tx HARQ process has been emptied and is being reused is indicated to the UE from the network side by the toggling of the NDI indicator (New Data Indicator) on the next downlink assignment for the corresponding HARQ process, along with the new data . This, in turn, will cause the UE to empty the HARQ receive process (Rx) and associate the newly received data with the current HARQ Rx process.

[007] As described above, the failure of the network to receive an ACK/NACK from a UE when expected is an indication of a likely failure by the UE to correctly decode the downlink assignment message, which, in LTE, is sent on the Physical Downlink Control Channel (PDCCH) or enhanced PDCCH (ePDCCH). Detection of this condition in the network can thus be used for the purpose of adapting the PDCCH / ePDCCH link - that is, to adapt the robustness of the physical control channel that carries the downlink grant.

[008] Although LTE is based on a fixed (or semi-static) split between uplink and downlink, other systems, as well as future versions of LTE, may be based on a dynamically scheduled split between uplink and downlink. In such systems, there may not be a one-to-one correspondence between downlink transmissions and HARQ feedback messages.

[009] In future LTE enhancements, the mode of operation considered is dynamic time division duplexing (TDD), in which subframes can be dynamically allocated for uplink or downlink use. With this approach, the number of HARQ processes can increase quite significantly, because, for example, a relatively large number of transmission time slots (TTIs) on a line can be assigned to the downlink. This causes the number of required HARQ processes to grow, as there is a long gap between uplink feedback opportunities to free up HARQ processes.

SUMMARY OF THE INVENTION

[0010] Given a heavy downlink scenario for enhanced LTE systems using dynamic TDD, the TDD configuration will be such that many subframes are used for downlink use while relatively few are used for UL use. . Therefore, HARQ feedback can be provided on the uplink relatively less frequently, which further increases the importance of its successful deployment. Furthermore, due to the large number of active Rx HARQ processes in the UE, for which feedback may be required at any given time, HARQ feedback reports will be quite large. Some embodiments of the currently described techniques address these problems by using explicit requests for automatic repeat request feedback, ARQ, the request indicating one or more ARQ processes. In the context of LTE, this ARQ feedback can be HARQ feedback, but it will be appreciated that the techniques described here can be applied, more generally, to systems that support other forms of ARQ, with multiple simultaneous ARQ processes.

[0011] An example method, in a wireless device operating in a wireless communication network, includes receiving from the wireless communication network, in a first transmission time slot, a request for request feedback. automatic repeat, ARQ, the request indicating one or more ARQ processes. The method further includes transmitting to the wireless communication network, in a second transmission time slot, ARQ feedback information for each of the one or more indicated ARQ processes. The ARQ feedback request is received as part of or in association with a resource assignment message that allocates uplink resources in the wireless device, in some embodiments.

[0012] A corresponding example method, which may be implemented in a network node of a wireless communication network, includes transmitting to a wireless device, in a first transmission time slot, a request for request feedback. automatic repeat, ARQ, the request indicating one or more ARQ processes. This example method further includes receiving from the wireless device, in a second transmission time slot, ARQ feedback information for each of the one or more indicated ARQ processes. Again, the ARQ feedback request may be transmitted as part of or in association with a resource assignment message that allocates uplink resources in the wireless device, in some embodiments.

[0013] In the detailed description that follows, several modalities are described in detail. Following the detailed description is a listing of example embodiments of the techniques and apparatus described herein. However, it should be noted that this listing of example embodiments is intended to be illustrative and not exhaustive.

BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 illustrates components of an example wireless network.

[0015] Figure 2 is a block diagram illustrating components of a wireless device, according to some embodiments of the techniques and apparatus described.

[0016] Figure 3 is a block diagram illustrating components of an example base station, according to some embodiments of the techniques and apparatus described.

[0017] Figure 4 illustrates conventional HARQ feedback timing in an LTE system.

[0018] Figure 5 illustrates an example of HARQ downlink transmission, followed by a request for and HARQ feedback transmission.

[0019] Figure 6 is a process flowchart illustrating an example method.

[0020] Figure 7 is a process flowchart illustrating another example method.

[0021] Figure 8 is a block diagram that provides another view of an example wireless device.

[0022] Figure 9 is a block diagram that provides another view of an example base station.

DETAILED DESCRIPTION

[0023] Inventive concepts will now be described more fully below in relation to the attached drawings, in which examples of embodiments of the inventive concepts are shown. These inventive concepts can, however, be embodied in many different forms and should not be construed as limited to the embodiments presented herein. Instead, these embodiments are provided so that this disclosure is judicious and complete, and fully conveys the scope of the present inventive concepts to those skilled in the art. It should also be noted that these modalities are not mutually exclusive. Components of one modality may be tacitly considered to be present or used in another modality.

[0024] For purposes of illustration and explanation only, some embodiments of the present inventive concepts are described herein in the context of operation in or in association with a Radio Access Network (RAN) that communicates over radio communication channels with mobile terminals ( also referred to as wireless terminals or UEs).

[0025] In some embodiments of a RAN, several base stations may be connected (for example, by mobile lines or radio channels) with a radio network controller (RNC). A radio network controller, also sometimes called a base station controller (BSC), can supervise and coordinate various activities of the various base stations connected to it. A radio network controller can be connected to one or more core networks. According to some other embodiments of a RAN, base stations can be connected into one or more core networks without an intervening RNC, for example, with the functionality of an RNC implemented in base stations and/or the core network.

[0026] As used herein, the terms "mobile terminal", "wireless terminal", "user equipment" or "UE" may be used to refer to any device that receives data from and transmits data to a communication network, any of which may be, for example, a mobile telephone ("cell phone"), laptop/portable computer, pocket computer, handheld computer, desktop computer, a machine-to-machine (M2M) type device or machine-type communications (MTC), a sensor with a wireless communication interface, etc. Note that although specification terminology for Long Term Evolution (LTE), also referred to as the Evolved Universal Terrestrial Radio Access Network, or E-UTRAN, and/or the Universal Mobile Telecommunications System (UMTS) is used in this disclosure to exemplify embodiments of the inventive concepts, this should not be seen as limiting the scope of the techniques currently described only for these systems. Devices designed for use in other wireless systems, including variations and successors of 3GPP LTE and WCDMA systems, WiMAX (Worldwide Interoperability for Microwave Access), UMB (Ultra Broadband Mobile), HSDPA (Downlink Packet Access) High Speed), GSM (Global System for Mobile Communications), etc., may also benefit from exploring embodiments of the present inventive concepts described herein.

[0027] Note also that terminology such as "base station" (also referred to as a NodeB, eNodeB or Evolved Node B) and "wireless terminal" or "mobile terminal" (also referred to as a User Equipment Node or UE) , should be considered non-limiting, and unless the context clearly indicates otherwise, does not imply a particular hierarchical relationship between the two. In general, a base station (e.g., a "NodeB" or "eNodeB") and a wireless terminal (e.g., a "UE") can be considered as examples of respective different communications devices that communicate with each other. over a wireless radio channel. Thus, for example, although certain techniques described herein may be described as specifically applicable on the downlink or on the uplink, it is understood that the same or similar techniques may also be applicable on the uplink, on the same network or on other networks. Similarly, those skilled in the art will also appreciate that some of these techniques described in relation to a particular direction set forth herein may, in some cases, apply in any direction in a peer-to-peer or ad hoc network scenario.

[0028] Likewise, specific examples of the techniques and apparatus described here are described in the context of the LTE system, which uses multi-process HARQ. It is understood that the inventive techniques described here can also be applied to systems that use other forms of ARQ.

[0029] The Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) includes base stations called enhanced NodeBs (eNBs or eNodeBs), which provide protocol terminations in the user plane and E-UTRA control plane toward the HUH. The eNBs are interconnected with each other using the X2 interface. The eNBs are also connected, using the S1 interface with respect to the EPC (Evolved Packet Core). More specifically, eNBs are connected to the MME (Mobility Management Entity) through the S1-MME interface and to the Service Communication Port (S-GW) through the S1-U interface. The S1 interface supports many-to-many relationship between MMEs/S-GWs and eNBs. A simplified view of the E-UTRAN architecture is illustrated in figure 1.

[0030] The illustrated network 100 includes eNBs 110, whose host functionalities, such as Radio Resource Management (RRM), radio bearer control, admission control, user plane data header compression in the direction of a service communication port and/or routing user plane data toward the service communication port. The MMEs 120 are the control nodes that process signaling between UEs and the CN (core network). Significant functions of the MMEs 120 are related to connection management and bearer management, which are handled through Non-Access Stratum (NAS) protocols. The S-GWs 130 are the anchor points for UE mobility, and also include other functionalities, such as temporary downlink data buffering while the UE is being radiosignaled, packet routing and forwarding to the right eNB, and /or gathering information for legal collection and interception. The PDN Communication Port (P-GW, not shown in figure 1) is the node responsible for allocating the UE's IP address, as well as applying Quality of Service (QoS) (as further discussed below). The reader is referred to version 12.3.0 of 3GPP TS 36.300, available at www.3gpp.org/dynareport/36300.htm, and the references therein for additional details of functionality of the different nodes.

[0031] Several of the techniques and methods described herein are implemented using radio circuitry, electronic data processing circuitry, and other electronic hardware provided in a mobile terminal or other wireless device. Figure 2 illustrates features of an example mobile terminal 200 in accordance with various embodiments of the present invention. Mobile terminal 200, which may be a UE configured for operation with an LTE wireless communications network (E-UTRAN), for example, as well as for operation in a device-to-device mode, in some embodiments, comprises a wireless transceiver circuit. radio 220 configured to communicate with one or more base stations, as well as a processing circuit 210 configured to process signals transmitted and received by the transceiver unit 220. The transceiver circuit 220 includes a transmitter 225 coupled to one or more transmitting antennas 228 and receiver 230 coupled to one or more receiving antennas 233. The same antenna(s) 228 and 233 can be used for both transmission and reception.

[0032] Receiver 230 and transmitter 225 use known radio processing and signal processing components and techniques, typically in accordance with a particular telecommunications standard, such as 3GPP standards for LTE. Note also that the transceiver circuit 220 may comprise a system of separate radio and/or baseband circuits for each of two or more different types of Radio Access Network, in some embodiments. The same applies to antennas - although in some cases one or more antennas may be used to access multiple types of networks, in other cases one or more antennas may be specifically tailored to a particular Radio Access Network or Networks . Because various engineering details and proportionalities associated with the design and implementation of such a circuit system are well known and are unnecessary for a complete understanding of the invention, additional details are not shown here.

[0033] The processing circuit 210 comprises one or more processors 240 coupled to one or more memory devices 250 that constitute a data storage memory 255 and a program storage memory 260. The processor 240, identified as CPU 240 in Figure 6, may be a microprocessor, microcontroller or digital signal processor in some embodiments. More generally, the processing circuit 210 may comprise a combination of processor/embedded software or specialized digital hardware, or a combination thereof. Memory 250 may comprise one or several types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. Because terminal 200 may support multiple Radio Access Networks, including, for example, a wide area RAN, such as LTE, as well as a wireless local area network (WLAN), processing circuitry 210 may include separate processing resources dedicated to one or more radio access technologies, in some embodiments. Again, because the various engineering details and proportionalities associated with the design of the baseband processing circuitry system for mobile devices are well known and are unnecessary for a complete understanding of the invention, additional details are not shown here.

[0034] Typical functions of processing circuit 210 include modulation and encoding of transmitted signals and demodulation and decoding of received signals. In various embodiments of the present invention, processing circuit 210 is adapted, using suitable program code stored in program storage memory 260, for example, to perform one of the techniques specifically described herein, including, for example, one or more of the techniques illustrated in figures 4, 5 and 6, and variants thereof. Of course, it will be noticed that not all steps of these techniques are necessarily carried out on a single microprocessor or even on a single module.

[0035] The mobile terminal 200 may additionally include one or more additional interface circuits, depending on the specific application for the unit. Typically, mobile terminal 200 includes connector interface circuitry 270. In some embodiments, connector interface circuitry 270 may consist of no more than electrical terminals and associated hardware to support charging of an onboard battery. (not shown) or to provide direct current (DC) power for the circuits illustrated. More often, the connector interface circuitry system 270 additionally includes a wired communication and/or control interface, which may operate in accordance with proprietary signaling and message formats in some embodiments, or in accordance with a standardized interface definition. , in others. For example, the connector interface 270 may comprise electrical terminals and associated hardware to support the well-known Universal Serial Bus (USB) interface. It will be appreciated that although the circuitry of the connector interface 270 includes at least the receiver and driver circuitry necessary to support such an interface and may additionally comprise specialized embedded hardware/software, some of the functionality of the interface may be provided by the CPU 240 , configured with embedded software and/or appropriate software in memory 250, in some embodiments.

[0036] The mobile terminal 200 may additionally comprise local area network (LAN) interface circuitry system 280, in some embodiments. In some embodiments, for example, the LAN interface circuitry 280 may provide support for wireless LAN (WLAN) functionality, such as in accordance with well-known Wi-Fi standards. In some such embodiments, the circuitry of the LAN interface 280 may include an appropriate antenna or antennas. In other embodiments, the LAN interface circuitry system 280 may make use of one or more common antenna structures that provide for the reception and/or transmission of WLAN signals as well as wide area RAN signals. In some embodiments, the LAN interface circuitry system 280 may be relatively self-contained, in that it includes all hardware, embedded software, and/or software necessary to perform LAN functionality, including associated protocol stacks. In other embodiments, at least portions of the LAN functionality may be performed by processing circuit 210.

[0037] Still further, the mobile terminal 200 may include user interface circuitry 290, which may include, for example, circuitry and/or associated hardware for one or more switches, push buttons, numeric keypads, displays touch sensitive devices and the like, for user input, as well as one or more speakers and/or displays for output. Of course, some mobile terminals, such as those developed for machine-to-machine applications or for insertion into another device (e.g., a laptop computer) may have only a subset of these input/output devices, or none at all.

[0038] Figure 3 shows an example of a wireless network node, in this case, a base station 300 (e.g., a NodeB or an eNodeB), which can be used in some of the example embodiments described here. It will be appreciated that, although a macro eNB is not, in practice, identical in size and structure to a micro eNB, for the purposes of illustration, the base stations 300 in both cases are considered to include similar components. Thus, whether or not base station 300 corresponds to a macro base station or a micro base station, it comprises a processing module 310 that controls the operation of the base station 300. The processing module 310, which may include one or more microprocessors , microcontrollers, digital signal processors, specialized digital logic, etc., is connected to a transceiver module 320 with associated antenna(s) 340 that are used to transmit signals to, and receive signals from, from the UEs 200 during operation in a network, such as that illustrated in FIG. 1. The base station 300 also comprises a memory circuit 360 that is connected to the processing module 310 and that stores program and other information and data required for the operation of the base station 300. Together, the processing module 310 and the memory circuit 360 may be referred to as a "processing circuit", and are adapted, in various embodiments, to perform one or more of the techniques based on network described below.

[0039] The base station 300 also includes an eNodeB interface circuit 380, which comprises components and/or circuitry to allow the base station 300 to exchange information with other base stations 300 (e.g., via an X2 interface ), and further includes a core network interface circuit 390, which comprises components and/or circuitry for enabling the base station 300 to exchange information with nodes in the core network (e.g., via the S1 interface), such as with an MME 120 or S-GW 130, as illustrated in figure 1. It will be appreciated that base stations for use in other types of networks (e.g., UTRAN or WCDMA RAN) will include components similar to those shown in figure 3 and system appropriate interface circuitry 380, 390 to enable communications with other network nodes in these types of networks (e.g., other base stations, mobility management nodes, and/or nodes in the core network).

[0040] As discussed previously, current LTE systems use HARQ for downlink transmissions, with HARQ feedback being sent by the UE on the uplink. Downlink scheduling is done on a 1 millisecond subframe basis. Scheduling messages are sent in each subframe, and the resource granted occupies all orthogonal frequency division multiplexing (OFDM) symbols allocated in the PDSCH in the resource block pairs allocated in the UE in the downlink resource grant. The processing time allowed for the terminal to complete all processing related to a transmission in a given subframe is 3 milliseconds, minus the timing advance, which is an adjustment of the transmission timing to account for the propagation delay between the terminal and the base station. The specifications for LTE thus specify that the ACK/NACK in response to a transmission on PDSCH in subframe n must be transmitted on the UL in subframe n+4, no matter the size of the transport block or the number of resource grants in additional downlinks. This is illustrated in Figure 4. Variations of this general synchronous scheme have been developed to accommodate time division duplexing (TDD) operation and carrier aggregation techniques, each of which may require ACK/NACK to multiple subframes and/or carriers. be transmitted in a single uplink subframe.

[0041] As discussed previously, future LTE systems (and other wireless systems) may use dynamic TDD, in which subframes (or other transmission time slots, TTIs) may be designated for downlink or uplink use in a dynamic basis. Given a heavy downlink scenario for enhanced LTE systems that use dynamic TDD, the use of TDD will be such that many subframes will be configured for downlink use, while relatively few will be configured for UL use. Therefore, HARQ feedback can be provided on the uplink relatively less frequently, which further increases the importance of its successful deployment. Furthermore, due to the large number of active Rx HARQ processes in the UE for which feedback may be required at any given time, HARQ feedback reports will be quite large.

[0042] In order for the network to have complete control over the HARQ feedback provided, it will therefore be desirable: a) that the network can explicitly request HARQ feedback from the UE, for specific HARQ processes; b) be able to make multiple request attempts for the same HARQ process, in the event that a report is not received successfully; c) limit reported HARQ processes to only those actually used; and d) relaxing the restrictions on the UE's downlink processing time by postponing the request by the desirable amount of extra processing time.

[0043] Neither of these is, however, possible under the current 3GPP LTE standard, as HARQ feedback is synchronous and transmitted only once per transmission attempt.

[0044] According to some embodiments of the currently described techniques, these problems are addressed by allowing the network to explicitly request HARQ feedback (or, more generally, ARQ feedback) from active HARQ processes (or, more generally, ARQ), that is, for those processes for which the network has attempted a transmission and, possibly, subsequent retransmissions. The request is made dynamically, for example, with explicit control signaling. This can be done, for example, by allowing each transmitted UL Scheduling Grant to contain an additional field that indicates whether HARQ feedback is requested and, if so, for which HARQ Rx processes states should be reported. In some embodiments, there may also be an independent scheduling grant that carries the HARQ request.

[0045] Addressing the individual Rx HARQ processes for which state must be reported can be done either: a) explicitly, for example, by a bitmap; as b) by defining a set of rules that specify in which order HARQ processes should be propagated and then simply indicating a total number of HARQ processes for which feedback is requested; and c) by specifying a range of subframes in the UL grant, and the UE then reporting all HARQ processes received in these subframes. An explicit indication of the Rx HARQ process for which status is to be reported may comprise an indicated process range, wherein the range is indicated, for example, by a starting HARQ process identifier and a HARQ process number, or by start and end HARQ process identifiers.

[0046] By allowing the network to explicitly request HARQ feedback for specific HARQ processes, rather than allowing the UE to provide it autonomously, better control is achieved in reporting HARQ feedback. This enables the network to know, with much higher reliability, which HARQ processes actually require a retransmission, thus reducing wasteful retransmissions on other HARQ processes due to incomplete HARQ information. Furthermore, in systems that use redundancy versions for retransmissions, according to which different combinations of encoded bits and forward error correction bits are transmitted in each retransmission of a block of data, the ideal redundancy version of the retransmission can be chosen with a much higher probability.

[0047] Better HARQ control also makes the system less vulnerable to undetected downlink grants, i.e., PDCCH/ePDCCH decoding failures, especially for retransmissions.

[0048] Furthermore, by making sure to provide feedback not on all, but only on the required subset of Rx HARQ processes, the size of HARQ reports is reduced and therefore uplink transmission resources are saved.

[0049] According to various embodiments of the currently described techniques, the above-described problems are addressed with a solution in which a signal is transmitted from the network to the UE, requesting HARQ feedback for certain indicated HARQ processes. This approach solves the problem with irregular HARQ feedback for dynamic TDD, while also providing a mechanism for robust HARQ reporting, by enabling retransmission of the feedback in the event that it is not correctly received by the network. This "on-demand" asynchronous reporting approach also allows for relaxed restrictions on processing time in the UE.

[0050] In accordance with some embodiments of the currently described techniques, the Scheduling Grant message in UL is amended with a 'HARQ Feedback Request' field used to explicitly indicate that HARQ feedback is requested for the Rx HARQ processes in the UE. The Scheduling Grant message can be used both for regular uplink data transmission and as a specific grant dedicated to scheduling uplink control information. In the latter case, the scheduling grant may be included in a downlink scheduling assignment. Reception of a field like this then triggers the UE to transmit HARQ feedback to the network.

[0051] An example of a HARQ feedback process according to this approach for a HARQ process - including successful reception of downlink assignment, downlink data, uplink granting and transmission of HARQ feedback - is shown in figure 5.

[0052] Downlink assignments (DL Assignments) for a given UE are transmitted in downlink subframes, using PDCCH or ePDCCH. Each of these DL assignments alerts the UE regarding the transmission of downlink data to the UE on the Physical Downlink Shared Channel (PDSCH). As seen in the figure, at some point after a particular downlink transmission, an uplink grant (UL grant) for the same UE is transmitted on the downlink, again using the PDCCH or ePDCCH. This UL grant, which is shown in subframe 25 of Figure 5, includes a HARQ feedback request. A certain number (g) of subframes later, the UE transmits HARQ feedback corresponding to one or more HARQ processes, each corresponding to previous downlink transmissions to the UE.

[0053] In the example shown in figure 5, the delay from receiving the HARQ Feedback Request to transmitting the HARQ feedback is denoted by g; This parameter may be system dependent, in some embodiments. It should be noted that Figure 5 illustrates a single HARQ process. In LTE and other systems, multiple processes can be active simultaneously so that the system does not need to wait for a HARQ process to complete before scheduling and sending additional data to the UE.

[0054] In some embodiments, the UL grant comprises a 'HARQ Feedback Request' field, which is included in an existing Downlink Control Information (DCI) format used for uplink scheduling grants (i.e., DCI format 0 or 4). This will be done by augmenting existing formats with additional fields. In other embodiments, the 'HARQ Feedback Request' field is included in a new DCI format to be used for uplink scheduling grants, in addition to the DCI formats 0 and 4 that are available today. In still other embodiments, the 'HARQ Feedback Request' field is included in one or more existing DCI formats used for downlink scheduling assignments. This will be done by augmenting the formats with additional fields. In still other embodiments, the 'HARQ feedback request' is signaled by providing to the UE an additional Radio Network Temporary Identifier (RNTI) used for this purpose. Whenever this new RNTI is used in a DCI message, bits that belong to existing fields in existing DCI formats can be reused for the additional information required for the 'HARQ feedback request'.

[0055] The contents of the 'HARQ Feedback Request' field may vary from one modality of the present techniques to another. In some embodiments, the 'HARQ Feedback Request' field is a one-bit field that simply indicates whether HARQ feedback is requested or not. This will indicate to the UE that feedback for all HARQ processes is requested. In other embodiments, the 'HARQ Feedback Request' field is a bitmap of size equal to the total number of HARQ processes. Considering this as T, then this bitmap can be indexed to 0...T-1, such that a set bit (e.g. a bit value of 1) at index t in this bitmap means that feedback is requested for HARQ process with index t. Similarly, a clear bit (e.g., a bit value of 0) at a certain point in the bitmap means that no feedback should be provided to the HARQ process corresponding to this point.

[0056] In still other embodiments, the 'HARQ Feedback Request' field is encoded to indicate information about a particular number of HARQ processes for which the UE is to provide feedback. As an example, it can be encoded as a 2-bit information field to be interpreted as {0, 2, 20, All}. In this case, 'All' means that all HARQ processes must be reported, while '0' means that no reports must be sent. For this to be fully usable, it is also required that the network ensures that HARQ processes are used in a predefined order, such as, for example, always allocating the free HARQ process that has the lowest index number. The network then also needs to ensure that all HARQ processes that are in progress at the time of a pre-request reconfiguration have time to finish in order to avoid confusion.

[0057] In some embodiments, the 'HARQ Feedback Request' is requested for a single or multiple processes selected by provision of the actual HARQ process number(s). In some embodiments, the 'HARQ Feedback Request' field indicates a range of processes. Thus, for example, it may have a format that includes a start value t and a range r, which indicates to the UE that HARQ processes numbered t through t+r-1 should be reported.

[0058] In still other embodiments, the 'HARQ Feedback Request' field indicates a range of subframes, thereby indicating a corresponding set of Rx HARQ processes, received in this range, for which feedback should be reported. Thus, for example, the 'HARQ Feedback Request' in some of these embodiments may include the last requested subframe k expressed as an offset from the granted received subframe n, and also include the number of subframes m to be included in the report. All subframes from n+k-m-1 through n+k will then be reported.

[0059] In various embodiments, the HARQ feedback transmitted by the UE may include explicit identifiers of the Rx HARQ processes for which feedback is reported. In some embodiments, the transmitted HARQ feedback may include a 'ReportSFN' Timestamp, which indicates a subframe number for each of one or more of the HARQ processes for which feedback is reported.

[0060] Given the detailed examples set forth of the techniques for reporting and processing HARQ feedback, it should be realized that these techniques can be applied more generally. Figure 6 illustrates an example method that can be performed on a wireless device operating in a wireless communication network, such as a UE operating in an LTE enhanced wireless network.

[0061] As shown in block 610, the illustrated method includes receiving, from the wireless communication network, in a first transmission time interval, a request by automatic repeat request (ARQ) feedback. The request indicates one or more ARQ processes. As shown in block 620, the method further includes transmitting to the wireless communication network, in a second transmission time slot, ARQ feedback information for each of the one or more indicated ARQ processes.

[0062] In some embodiments, the ARQ feedback request is received as part of or in association with a resource assignment message that allocates downlink resources on the wireless device. In other embodiments, the ARQ feedback request is received as part of or in association with a resource assignment message that allocates uplink resources in the wireless device. In some of these latter embodiments, the resource allocation message may allocate uplink resources to transmit ARQ feedback information. In some embodiments, the wireless communication network is an E-UTRAN network and the resource assignment message comprises a Downlink Control Information (DCI) format 0 message or a DCI format 4 message, augmented with one or more fields to port the request via ARQ feedback.

[0063] In some embodiments, the ARQ feedback request is received in a resource allocation message that includes a Radio Network Temporary Identifier (RNTI) for the wireless device that indicates that the resource allocation message contains the request by ARQ feedback.

[0064] Various techniques can be used to indicate the ARQ processes for which ARQ feedback should be provided. For example, in some embodiments, the request for ARQ feedback comprises a one-bit field that indicates whether ARQ feedback for all ARQ processes is requested or not. Other possibilities include that the request for ARQ feedback: includes a bitmap such that each bit in the bitmap corresponds to a particular ARQ process of a plurality of ARQ processes and indicates whether feedback is requested for the corresponding ARQ process ; indicate a number of ARQ processes for which the wireless device should provide feedback; indicate one or more specific ARQ process numbers; indicate a specific range of ARQ case numbers; or indicate a range of transmission time slots, which indicates that the wireless device must provide ARQ feedback to all active ARQ processes during the indicated range of transmission time slots.

[0065] Figure 7 illustrates an example method that can be performed on a network node of a wireless communication network, such as a base station (eNodeB) that operates in an enhanced LTE wireless network. It will be appreciated that the method in Figure 7 is complementary to, but closely corresponds to, the example method shown in Figure 6.

[0066] As shown in block 710, the illustrated method includes transmitting to a wireless device, in a first transmission time slot, a request by automatic repeat request (ARQ) feedback. The request indicates one or more ARQ processes. As shown in block 720, the method further includes receiving, from the wireless device, in a second transmission time slot, ARQ feedback information for each of the one or more indicated ARQ processes.

[0067] In some embodiments, the ARQ feedback request is transmitted as part of or in association with a resource assignment message that allocates downlink resources on the wireless device. In other embodiments, the ARQ feedback request is transmitted as part of or in association with a resource assignment message that allocates uplink resources in the wireless device. In some of these latter embodiments, the resource allocation message may allocate uplink resources to transmit ARQ feedback information. In some embodiments, the wireless communication network is an E-UTRAN network and the resource assignment message comprises a Downlink Control Information (DCI) format 0 message or a DCI format 4 message, augmented with one or more fields to port the request via ARQ feedback.

[0068] In some embodiments, the ARQ feedback request is transmitted in a resource allocation message that includes a Radio Network Temporary Identifier (RNTI) to the wireless device that indicates that the resource allocation message contains the request by ARQ feedback.

[0069] Again, various techniques can be used to indicate the ARQ processes for which ARQ feedback should be provided. For example, in some embodiments, the request for ARQ feedback comprises a one-bit field that indicates whether ARQ feedback for all ARQ processes is requested or not. Other possibilities include that the request for ARQ feedback: includes a bitmap such that each bit in the bitmap corresponds to a particular ARQ process of a plurality of ARQ processes and indicates whether feedback is requested for the corresponding ARQ process ; indicate a number of ARQ processes for which the wireless device should provide feedback; indicate one or more specific ARQ process numbers; indicate a specific range of ARQ case numbers; or indicate a range of transmission time slots, which indicates that the wireless device must provide ARQ feedback to all active ARQ processes during the indicated range of transmission time slots.

[0070] Modalities of the techniques currently described include the various methods described above, including the methods illustrated in the process flowcharts of figures 6 and 7, as well as variants thereof. Other embodiments include mobile terminal apparatus and corresponding network node configured to perform one or more of these methods. In some embodiments of the invention, processing circuits, such as processing circuit 210 of Figure 2 or processing module 310 and memory circuit 360 of Figure 3, are configured to perform one or more of the techniques described in detail above. Likewise, other embodiments may include mobile terminals and network nodes that include one or more such processing circuits. In some cases, these processing circuits are configured with appropriate program code, stored in one or more suitable memory devices, to implement one or more of the techniques described herein. Of course, it will be noticed that not all steps of these techniques are necessarily carried out on a single microprocessor or even on a single module.

[0071] It will further be appreciated that various aspects of the above-described embodiments can be understood as being carried out by functional "modules" corresponding to the steps of the method illustrated in Figures 6 and 7. These functional modules can be program instructions executing in an appropriate processor circuit. , fixed code digital circuitry and/or analog circuitry, or appropriate combinations thereof, for example, in network nodes and wireless devices with hardware configurations such as those shown in Figures 2 and 3.

[0072] For example, Figure 8 is a block diagram illustrating another view of the example wireless device 200 shown in Figure 2, but in which the processing circuit is illustrated in accordance with this functional view. In Figure 8, the processing circuitry system 210 comprises a reception module 810, which is adapted to receive, from a wireless communication network, in a first transmission time interval, a request for feedback request. automatic repeat (ARQ), the request indicating one or more ARQ processes. The processing circuitry system 210 further comprises an ARQ feedback module 820, which is adapted to transmit to the wireless communication network, in a second transmission time slot, ARQ feedback information for each of the one or more processes. ARQ indicated.

[0073] Similarly, Figure 9 is a block diagram illustrating another view of the example base station 300 depicted in Figure 3, but in which the processing circuitry of the base station 300 is illustrated according to a functional view. 9, a processing circuit 910 comprises a feedback request module 920, which is adapted to transmit to a wireless device, in a first transmission time slot, an automatic repeat request (ARQ) feedback request. , the request indicating one or more ARQ processes. The processing circuit 910 further comprises an ARQ processing module 930 configured to receive, from the wireless device, in a second transmission time slot, ARQ feedback information for each of the one or more indicated ARQ processes. It will be appreciated by those skilled in the art that various modifications can be made to the above-described embodiments without departing from the scope of the present invention. For example, although embodiments of the present invention have been described with examples referencing a communication system conforming to LTE standards specified by 3GPP, it should be noted that the presented solutions may be equally well applicable in other networks. The specific embodiments described above, therefore, should be considered exemplary, rather than limiting the scope of the invention. Because it is certainly not possible to describe every conceivable combination of components or techniques, those skilled in the art realize that the present invention can be implemented in ways different from those specifically presented here, without departing from the essential characteristics of the invention. The present embodiments, therefore, should be considered, in all respects, as illustrative and not restrictive.

[0074] In the present description of various embodiments of the present inventive concepts, it should be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to limit the present inventive concepts. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning commonly understood by those skilled in the art to which the present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, are to be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant technology, and will not be interpreted in an idealized or overly formal sense, expressly in the manner defined here.

[0075] When an element is referred to as being "connected", "coupled", "responsive" or variants thereof in relation to another element, it may be directly connected, coupled or responsive to the other element or intervening elements may be present . Conversely, when an element is referred to as being "directly connected", "directly coupled", "directly responsive" or variants thereof in relation to another element, there are no intervening elements present. Equal numbers refer to equal elements throughout. Furthermore, "coupled", "connected", "responsive" or variants thereof, as used herein, may include coupled, connected or wireless responsive. As used herein, the singular forms "a", "a", "the" and "a" are intended to also include the plural forms, unless the context clearly indicates otherwise. Well-known functions or constructs may not be described in detail for brevity and/or clarity. The term "and/or" includes any and all combinations of one or more of the associated listed items.

[0076] It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations shall not be limited by these terms. These terms are only used to distinguish one element/operation from another element/operation. Thus, a first element/operation in some embodiments can be called a second element/operation in other embodiments without departing from the precepts of the present inventive concepts. The same reference numbers or reference designators denote the same or similar elements throughout the specification.

[0077] As used herein, the terms "comprise", "comprising", "comprises", "include", "including", "includes", "have", "has", "having" or variants thereof are open, and include one or more declared features, integers, elements, steps, components or functions, but do not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof . Furthermore, as used herein, the common abbreviation "e.g.", which derives from the Latin phrase "exempli gratia", may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended that is limiting for such an item. The common abbreviation "i. e.", which derives from the Latin phrase "id est", can be used to specify a particular item from a more general citation.

[0078] Example embodiments have been described herein, in relation to block diagrams and/or flowchart illustrations of methods implemented by computer, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, may be implemented by computer program instructions that are carried out by one or more circuits. computer. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, in such a manner that the instructions , which performs through the computer processor and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components in such circuit system to implement the functions/acts specified in block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure to implement the functions / acts specified in the block diagrams and/or flowchart block(s).

[0079] These computer program instructions may also be stored on a tangible computer-readable medium that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored on the medium computer readable produce an article of manufacture that includes instructions that implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. In this manner, embodiments of the present inventive concepts may be embodied in hardware and/or software (including embedded software, resident software, microcode, etc.) running on a processor, such as a digital signal processor, which may be collectively referred to as such as "system of circuits", "a module" or variants thereof.

[0080] It should also be noted that, in some alternative implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in reverse order depending on the functionality/acts involved. Furthermore, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of the inventive concepts. Furthermore, although some of the diagrams include arrows on communication paths to show a primary communication direction, it should be understood that communication can occur in the opposite direction to the arrows depicted.

[0081] Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. It is intended that all such variations and modifications are herein included within the scope of the present inventive concepts. Accordingly, the subject matter described above should be considered illustrative, and not restrictive, and it is intended that the attached examples of embodiments cover all such modifications, improvements and other embodiments, which fall within the spirit and scope of the present inventive concepts. Accordingly, to the maximum extent permitted by law, the scope of the present inventive concepts shall be determined by the broadest permissible interpretation of the present disclosure, and shall not be restricted or limited by the detailed description set forth. Example Embodiments

[0082] Embodiments of currently disclosed techniques and apparatus include, but are not limited to, the following:

[0083] (a) A method, in a wireless device operating in a wireless communication network, the method comprising: receiving from the wireless communication network, in a first transmission time slot, a request for hybrid automatic repeat request (HARQ) feedback, the request indicating one or more HARQ processes; and transmitting to the wireless communication network, in a second transmission time slot, HARQ feedback information for each of the one or more indicated HARQ processes.

[0084] (b) The method, of example embodiment (a), wherein the HARQ feedback request is received as part of or in association with a resource assignment message that allocates uplink resources in the wireless device.

[0085] (c) The method, of example embodiment (b), wherein the resource allocation message allocates uplink resources to transmit HARQ feedback information.

[0086] (d) The method, of example embodiments (b) or (c), wherein the wireless communication network is an E-UTRAN network and wherein the resource assignment message comprises a Resource Information message. Downlink Control (DCI) format 0 or a DCI format 4 message, augmented with one or more fields to carry the HARQ feedback request.

[0087] (e) The method, of example embodiment (a), wherein the HARQ feedback request is received as part of or in association with a resource assignment message that allocates downlink resources in the wireless device.

[0088] (f) The method, of any of example embodiments (a) - (e), wherein the HARQ feedback request is received in a resource allocation message that includes a Temporary Radio Network Identifier ( RNTI) for the wireless device indicating that the resource allocation message contains the HARQ feedback request.

[0089] (g) The method, of any of example embodiments (a) - (f), wherein the request for HARQ feedback comprises a one-bit field indicating whether HARQ feedback for all HARQ processes is requested or no.

[0090] (h) The method, of any of example embodiments (a) - (f), wherein the HARQ feedback request comprises a bitmap, such that each bit in the bitmap corresponds to a particular HARQ process from a plurality of HARQ processes and indicates whether feedback is requested by the corresponding HARQ process.

[0091] (i) The method, of any of example embodiments (a) - (f), wherein the HARQ feedback request indicates a number of HARQ processes for which the wireless device must provide feedback.

[0092] (j) The method, of any of example embodiments (a) - (f), wherein the HARQ feedback request indicates one or more specific HARQ process numbers.

[0093] (k) The method, of any of example embodiments (a) - (f), wherein the HARQ feedback request indicates a specific range of HARQ process numbers.

[0094] (l) The method, of any of example embodiments (a) - (f), wherein the HARQ feedback request indicates a range of transmission time slots, which indicates that the wireless device must provide HARQ feedback for all active HARQ processes during the indicated range of transmission time slots.

[0095] (m) A method, at a network node of a wireless communication network, characterized in that the method comprises: transmitting to a wireless device, in a first transmission time slot, a request for hybrid automatic repeat request (HARQ) feedback, the request indicating one or more HARQ processes; and receiving, from the wireless device, in a second transmission time slot, HARQ feedback information for each of the one or more indicated HARQ processes.

[0096] (n) The method, of example embodiment (m), wherein the HARQ feedback request is transmitted as part of or in association with a resource assignment message that allocates uplink resources in the wireless device.

[0097] (o) The method, of example embodiment (n), wherein the resource allocation message allocates uplink resources to transmit HARQ feedback information.

[0098] (p) The method, of example embodiment (n) or (o), wherein the wireless communication network is an E-UTRAN network and wherein the resource assignment message comprises a Resource Information message. Downlink Control (DCI) format 0 or a DCI format 4 message, augmented with one or more fields to carry the HARQ feedback request.

[0099] (q) The method, of example embodiment (m), wherein the HARQ feedback request is transmitted as part of or in association with a resource assignment message that allocates downlink resources in the wireless device.

[00100] (r) The method, of any of example embodiments (m) - (q), wherein the HARQ feedback request is transmitted in a resource allocation message that includes a Temporary Radio Network Identifier ( RNTI) for the wireless device indicating that the resource allocation message contains the HARQ feedback request.

[00101] (s) The method, of any of example embodiments (m) - (r), wherein the request for HARQ feedback comprises a one-bit field indicating whether HARQ feedback for all HARQ processes is requested or no.

[00102] (t) The method, of any of example embodiments (m) - (r), wherein the HARQ feedback request comprises a bitmap, such that each bit in the bitmap corresponds to a particular HARQ process from a plurality of HARQ processes and indicates whether feedback is requested by the corresponding HARQ process.

[00103] (u) The method, of any of example embodiments (m) - (r), wherein the HARQ feedback request indicates a number of HARQ processes for which the wireless device must provide feedback.

[00104] (v) The method, of any of example embodiments (m) - (r), wherein the HARQ feedback request indicates one or more specific HARQ process numbers.

[00105] (w) The method, of any of example embodiments (m) - (r), wherein the HARQ feedback request indicates a specific range of HARQ process numbers.

[00106] (x) The method, of any of example embodiments (m) - (r), wherein the HARQ feedback request indicates a range of transmission time slots, which indicates that the wireless device must provide HARQ feedback for all active HARQ processes during the indicated range of transmission time slots.

[00107] (y) A wireless device arranged for operation in a wireless communication network, wherein the wireless device comprises: means for receiving, from the wireless communication network, in a first transmission time slot , a request by hybrid automatic repeat request (HARQ) feedback, the request indicating one or more HARQ processes; and means for transmitting to the wireless communication network, in a second transmission time slot, HARQ feedback information for each of the one or more indicated HARQ processes. (z) A wireless device adapted to operate in a wireless communication network, wherein the wireless device comprises a radio transceiver configured to communicate with a network node and further comprises a processing circuit adapted to use the radio transceiver radio for: receiving, from the wireless communication network, in a first transmission time slot, a request by hybrid automatic repeat request (HARQ) feedback, the request indicating one or more HARQ processes; and transmitting to the wireless communication network, in a second transmission time slot, HARQ feedback information for each of the one or more indicated HARQ processes.

[00108] (aa) The wireless device, of example embodiments (y) or (z), wherein the wireless device is further adapted to perform the method of any of example embodiments (b) - (l) .

[00109] (bb) A network node of a wireless communication system, wherein the network node comprises: means for transmitting to a wireless device, in a first transmission time interval, a request by request feedback hybrid autoretry (HARQ), the request indicating one or more HARQ processes; and means for receiving, from the wireless device, in a second transmission time slot, HARQ feedback information for each of the one or more indicated HARQ processes.

[00110] (cc) A network node of a wireless communication system, wherein the network node comprises a radio transceiver configured to communicate with wireless devices and further comprises processing adapted to use the radio transceiver to: transmitting to a wireless device, in a first transmission time slot, a request by hybrid automatic repeat request (HARQ) feedback, the request indicating one or more HARQ processes; and receiving, from the wireless device, in a second transmission time slot, HARQ feedback information for each of the one or more indicated HARQ processes.

[00111] (dd) The network node, of example embodiments (bb) or (cc), wherein the network node is further adapted to carry out the method of any of example embodiments (n) - (x) .

Claims (16)

1. Method, in a wireless device (200) operating in a wireless communication network, the method comprising: receiving (610), from the wireless communication network, in a first transmission time interval (n ), a request by automatic repeat request feedback, ARQ, the request indicating one or more ARQ processes; and transmitting (620), to the wireless communication network, in a second transmission time slot (n+g), ARQ feedback information for each of those one or more indicated ARQ processes, characterized by the fact that the request per ARQ feedback indicates a specific range of ARQ process numbers or a range of transmission time slots, indicating that the wireless device (200) must provide ARQ feedback to all active ARQ processes during the range of transmission time slots. indicated transmission. 2. The method of claim 1, wherein the ARQ feedback request is received as part of or in association with a resource assignment message that allocates uplink or downlink resources in the wireless device (200). 3. The method of claim 2, wherein the ARQ feedback request is received as part of or in association with a resource assignment message that allocates uplink resources, the resource assignment message allocates uplink resources ascending to transmit the ARQ feedback information. 4. The method of any one of claims 1 to 3, wherein the ARQ feedback request is received in a resource allocation message that includes a Radio Network Temporary Identifier, RNTI, for the wireless device ( 200) which indicates that the resource allocation message contains the ARQ feedback request. 5. Method, in a network node (300) of a wireless communication network, the method comprising the steps of: transmitting (710), to a wireless device (200), in a first transmission time slot (n), a request for feedback from an automatic repeat request, ARQ, the request indicating one or more ARQ processes; and receiving (720), from the wireless device (200), in a second transmission time interval (n+g), ARQ feedback information for each of the one or more indicated ARQ processes, characterized by the fact that : The ARQ feedback request indicates a specific range of ARQ process numbers or a range of transmission time slots, which indicates that the wireless device (200) should provide ARQ feedback to all active ARQ processes during the range. indicated transmission time slots. 6. The method of claim 5, wherein the ARQ feedback request is transmitted as part of or in association with a resource assignment message that allocates uplink or downlink resources in the wireless device (200). . 7. The method of claim 6, wherein the ARQ feedback request is transmitted as part of or in association with a resource assignment message that allocates uplink resources, the resource assignment message allocates resources uplink to transmit ARQ feedback information. 8. The method of any one of claims 5 to 7, wherein the ARQ feedback request is transmitted in a resource allocation message that includes a Radio Network Temporary Identifier, RNTI, to the wireless device ( 200) which indicates that the resource allocation message contains the ARQ feedback request. 9. Wireless device (200), arranged for operation on a wireless communication network, wherein the wireless device (200) is adapted to: receive, from the wireless communication network, in a first time slot transmission (n), a request for automatic repeat request feedback, ARQ, the request indicating one or more ARQ processes; and transmitting, to the wireless communication network, in a second transmission time slot (n+g), ARQ feedback information for each of those one or more indicated ARQ processes, characterized by the fact that the request for feedback ARQ indicates a specific range of ARQ process numbers or a range of transmission time slots, which indicates that the wireless device (200) must provide ARQ feedback to all active ARQ processes during the range of transmission time slots. indicated. 10. The wireless device (200) of claim 9, wherein the wireless device (200) is adapted to receive the ARQ feedback request as part of or in association with a resource assignment message that allocates uplink or downlink resources on the wireless device (200). 11. Wireless device (200) according to claim 10, characterized by the fact that, when the wireless device (200) is adapted to receive the ARQ feedback request as part of or in association with a message assignment message resource that allocates uplink resources, the resource allocation message allocates uplink resources to transmit ARQ feedback information. 12. Wireless device (200) according to any one of claims 9 to 11, characterized in that the wireless device (200) is adapted to receive the ARQ feedback request in a resource allocation message that includes an Identifier Radio Network Temporary, RNTI, for the wireless device (200) which indicates that such resource allocation message contains the ARQ feedback request. 13. Network node (300) of a wireless communication system, the network node (300) being adapted to: transmit to a wireless device (200), in a first transmission time slot (n), a request by automatic repeat request feedback, ARQ, the request indicating one or more ARQ processes; and receiving from the wireless device (200), in a second transmission time interval (n+g), ARQ feedback information for each of the one or more indicated ARQ processes characterized by the fact that: the request for ARQ feedback indicates a specific range of ARQ process numbers or a range of transmission time slots, which indicates that the wireless device (200) must provide ARQ feedback to all active ARQ processes during the range of transmission time slots. indicated transmission. 14. Network node (300) according to claim 13, characterized in that the network node (300) is adapted to transmit the ARQ feedback request as part of or in association with a resource assignment message that allocates uplink or downlink resources on the wireless device (200). 15. The network node (300) of claim 14, wherein the network node (300) is adapted to transmit the ARQ feedback request as part of or in association with a resource assignment message that allocates uplink resources, the resource allocation message allocates uplink resources to transmit ARQ feedback information. 16. Network node (300) according to any one of claims 13 to 15, characterized in that the network node (300) is adapted to transmit the ARQ feedback request in a resource allocation message that includes a Radio Network Temporary Identifier, RNTI, for the wireless device (200) that indicates that the resource allocation message contains the ARQ feedback request.