HARQ processing for single DCI multi-slot scheduling

Abstract

The network node causes a DCI to be sent, the DCI including information for scheduling two or more TBs on two or more communication time slots. The two or more TBs are associated with two or more HARQ process IDs. The information includes one or more of the following: a PUCCH resource indicator configured to indicate at least one resource for sending HARQ feedback associated with the two or more TBs; a DAI configured to indicate a HARQ feedback position associated with the two or more TBs in a HARQ codebook; a HARQ process ID indicator indicating two or more HARQ process IDs; and one or more NDIs configured to indicate whether at least one TB of the two or more TBs is a retransmission.

Description

Technical Field

[0001] Wireless communications, in particular, control information configured to schedule a plurality of transport blocks over a plurality of communication time slots associated with at least one hybrid automatic repeat request (HARQ) instance. Background Art

[0002] The New Radio (NR) (also referred to as "5G") standard of the Third Generation Partnership Project (3GPP) is designed to help provide services for a variety of use cases, such as enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and machine-type communications (MTC). Each of these services has different technical requirements. For example, the general requirements for eMBB are high data rates with medium latency and medium coverage, while URLLC services require low latency and high reliability transmission, but may require medium data rates.

[0003] One of the solutions for low-latency data transmission is a shorter transmission time interval. In NR, in addition to transmission in time slots, mini-slot transmission is allowed to reduce latency. Mini-slots (referred to as Class B scheduling in NR terminology) can include any number of 1 to 14 OFDM symbols in the uplink (UL) and 2, 4 or 7 symbols in the downlink (DL) (in 3GPP Release 15 (Rel-15)). It should be noted that the concepts of time slots and mini-slots are not specific to a specific service, which means that mini-slots can be used for eMBB, URLLC, or other services. Figure 1 is a schematic diagram of exemplary radio resources in NR.

[0004] Physical Channel

[0005] A downlink physical channel corresponds to a set of resource elements that carry information originating from a higher layer (i.e., the transport layer). The following exemplary downlink physical channels are defined:

[0006] - Physical downlink shared channel, PDSCH;

[0007] - Physical Broadcast Channel, PBCH; and

[0008] -Physical Downlink Control Channel, PDCCH.

[0009] The PDSCH is the primary physical channel used for unicast downlink data transmission, but is also used to send RAR (Random Access Response), certain System Information Blocks (SIBs), and paging information. The PBCH carries basic system information required for wireless devices to access the network and read the rest of the system information in SIB1. The PDCCH is used to send downlink control information (DCI), mainly scheduling decisions, which are required to receive the PDSCH, and uplink scheduling grants to enable transmissions on the PUSCH.

[0010] An uplink physical channel corresponds to a set of resource elements that carry information originating from higher layers. The following exemplary uplink physical channels are defined:

[0011] -Physical uplink shared channel, PUSCH;

[0012] - Physical Uplink Control Channel, PUCCH; and

[0013] -Physical Random Access Channel, PRACH.

[0014] PUSCH is the uplink counterpart of PDSCH. PUCCH is used by wireless devices to send uplink control information, including HARQ acknowledgments, channel state information reports, etc. PRACH is used for random access preamble transmission.

[0015] An example of the content of DL DCI 1-0 is provided below.

[0016] Example content of DCI format 1_0 with CRC scrambled by C-RNTI / CS_RNTI

[0017] - Identifier for DCI format - 1 bit

[0018] - The value of this bit field may always be set to 1, indicating that the DL DCI format

[0019] - Frequency domain resource allocation —— Bit

[0020] - is the size of the active DL bandwidth portion if DCI format 1_0 is monitored in the wireless device specific search space and satisfies

[0021] - For a cell, the total number of different DCI sizes configured for monitoring does not exceed four, and

[0022] - For a cell, the total number of different DCI sizes with C-RNTI configured for monitoring does not exceed three

[0023] otherwise, It is the size of control resource set (CORESET) 0.

[0024] - Time domain resource allocation - e.g. 4 bits, as defined in subclause 5.1.2.1 of 3GPP Technical Specification (TS) 38.214

[0025] - VRB to PRB mapping - e.g. 1 bit, according to e.g. Table 7.3.1.1.2-33 in 3GPP TS 38.214

[0026] - Modulation and coding scheme - e.g. 5 bits, as defined in subclause 5.1.3 of 3GPP TS 38.214

[0027] - New data indicator - 1 bit

[0028] - Redundancy version - e.g., 2 bits, as defined in e.g., Table 7.3.1.1.1-2 in 3GPP TS 38.214

[0029] -HARQ process number——4 bits

[0030] - Downlink Allocation Index (DAI) - e.g. 2 bits, as defined in subclause 9.1.3 of 3GPP TS 38.213, as a counter DAI

[0031] - TPC command for the scheduled PUCCH - e.g. 2 bits as defined in subclause 7.2.1 of 3GPP TS 38.213

[0032] - PUCCH resource indicator - e.g. 3 bits, as defined in subclause 9.2.3 of 3GPP TS 38.213

[0033] - PDSCH-to-HARQ_feedback timing indicator - e.g., 3 bits, as defined in subclause 9.2.3 of 3GPP TS 38.213 Slot aggregation DL:

[0034] When the wireless device is configured with aggregationFactorDL>1, the same symbol allocation applies over aggregationFactorDL consecutive slots.The wireless device may expect that transport blocks (TBs) are repeated within each symbol allocation in each aggregationFactorDL consecutive slots and that the PDSCH is restricted to a single transport layer.

[0035] If the wireless device process for determining slot configuration (eg, as defined in subclause 11.1 of 3GPP TS 38.213) determines that a symbol of a slot allocated for PDSCH is an uplink symbol, then for a multi-slot PDSCH transmission, transmission on that slot is omitted.

[0036] Time slot aggregation UL:

[0037] When the wireless device is configured with aggregationFactorUL>1, the same symbol allocation is applied over aggregationFactorUL consecutive slots and PUSCH is restricted to a single transmission layer.The wireless device may repeat TBs over aggregationFactorUL consecutive slots applying the same symbol allocation in each slot.

[0038] If the wireless device process for determining timeslot configuration (eg, as defined in subclause 11.1 of 3GPP TS 38.213) determines that a symbol of a timeslot allocated for PUSCH is a downlink symbol, then for multi-slot PUSCH transmission, transmission on that timeslot is omitted.

[0039] Multi-slot scheduling:

[0040] Some suggestions have been made to enable PDCCH scheduling opportunities to schedule multiple time slots (e.g., PDSCH) with basic resource indicators within the Scheduling Information (SI) (Radio Packet Scheduling (PS) for 3GPP Release 16 (Rel 16)). In this way, processing time can be reduced, and thus processing time at the radio can be reduced, which results in power savings. Figure 2 An example of this mechanism is provided in . Summary of the invention

[0041] Some embodiments advantageously provide methods, systems, network nodes, wireless devices and apparatus for transmitting downlink control information (DCI) for scheduling multiple transport blocks on multiple communication time slots associated with at least one hybrid automatic repeat request (HARQ) instance, i.e., for processing HARQ instances / processes.

[0042] A HARQ process setup for a single-DCI multi-slot scheduling for a PxSCH (i.e., PDSCH or PUSCH) setup is described, where the setup schedules multiple TBs over multiple slots. Examples of basic components and / or processes for a setup including one or more of PUCCH resources, HARQ codebooks, HARQ process IDs, and new data indicators are described in detail below.

[0043] According to one aspect of the present disclosure, a network node is provided. The network node includes a processing circuit, which is configured to: cause downlink control information (DCI) to be sent to a wireless device, wherein the DCI includes information for scheduling two or more transport blocks (TBs) on two or more communication time slots, and the two or more transport blocks are associated with two or more hybrid automatic repeat request (HARQ) process identifiers (IDs). The information for scheduling includes at least one of the following: a PUCCH resource indicator, configured to indicate at least one resource used by the wireless device to send HARQ feedback related to the two or more TBs; a downlink allocation indicator (DAI), configured to indicate a HARQ feedback position related to the two or more TBs in the HARQ codebook; a HARQ process ID indicator, which indicates a HARQ process ID; and one or more new data indicators (NDIs), configured to indicate whether at least one TB of the two or more TBs is a retransmission. The processing circuit is further configured to use the two or more TBs for communication based at least in part on the DCI.

[0044] According to one or more embodiments of the present aspect, the PUCCH resource indicator includes one or more K1 values. According to one or more embodiments of the present aspect, two or more communication time slots are scheduled on corresponding time-frequency resources. According to one or more embodiments of the present aspect, the HARQ feedback position associated with two or more TBs in the HARQ codebook is further based at least in part on the number of two or more communication time slots. According to one or more embodiments of the present aspect, the value of the DAI indicates a HARQ feedback position for one TB in the two or more TBs, and another HARQ feedback position for a second TB in the two or more TBs is indicated at least in part based on the value of the DAI.

[0045] According to one or more embodiments of the present aspect, the HARQ process ID indicator is based at least in part on the number of physical shared channel transmissions in two or more communication time slots. According to one or more embodiments of the present aspect, the HARQ process ID indicator is based at least in part on at least one time slot number used for physical shared channel transmissions in two or more communication time slots. According to one or more embodiments of the present aspect, the HARQ process ID indicator is one of the two or more HARQ process IDs.

[0046] According to one or more embodiments of the present aspect, the HARQ process ID indicator includes a number of HARQ process IDs that is less than the number of two or more communication time slots. According to one or more embodiments of the present aspect, one or more NDIs are configured to indicate whether at least one TB of the two or more TBs is a retransmission. According to one or more embodiments of the present aspect, the one or more NDIs are a single NDI applied to two or more TBs.

[0047] According to another aspect of the present disclosure, a method in a network node is provided. Downlink control information (DCI) is sent to a wireless device, wherein the DCI includes information for scheduling two or more transport blocks (TBs) on two or more communication time slots. The two or more transport blocks are associated with two or more hybrid automatic repeat request (HARQ) process identifiers (IDs). The information used for scheduling includes one or more of the following: a PUCCH resource indicator configured to indicate at least one resource used by the wireless device to send HARQ feedback associated with two or more TBs; a downlink allocation indicator (DAI) configured to indicate a HARQ feedback position associated with two or more TBs in a HARQ codebook; a HARQ process ID indicator indicating two or more HARQ process IDs; and one or more new data indicators (NDIs) configured to indicate whether at least one of the two or more TBs is a retransmission. Based at least in part on the DCI, two or more TBs are used for communication.

[0048] According to one or more embodiments of the present aspect, the PUCCH resource indicator includes one or more K1 values. According to one or more embodiments of the present aspect, two or more communication time slots are scheduled on corresponding time-frequency resources. According to one or more embodiments of the present aspect, the HARQ feedback position associated with the two or more TBs in the HARQ codebook is further based at least in part on the number of the two or more communication time slots.

[0049] According to one or more embodiments of the present invention, the value of the DAI indicates a HARQ feedback position for one TB in two or more TBs, and another HARQ feedback position for a second TB in the two or more TBs is indicated based at least in part on the value of the DAI. According to one or more embodiments of the present invention, the HARQ process ID indicator is based at least in part on the number of physical shared channel transmissions in two or more communication time slots.

[0050] According to one or more embodiments of the present aspect, the HARQ process ID indicator is based at least in part on at least one time slot number used for physical shared channel transmission in two or more communication time slots. According to one or more embodiments of the present aspect, the HARQ process ID indicator is one of two or more HARQ process IDs. According to one or more embodiments of the present aspect, the HARQ process ID indicator includes a number of HARQ process IDs that is less than the number of two or more communication time slots. According to one or more embodiments of the present aspect, one or more NDIs are configured to indicate whether at least one TB of the two or more TBs is a retransmission. According to one or more embodiments of the present aspect, one or more NDIs are a single NDI applied to two or more TBs.

[0051] According to another aspect of the present disclosure, a wireless device is provided. The wireless device includes a processing circuit configured to receive downlink control information (DCI), wherein the DCI includes information for scheduling two or more transport blocks (TBs) on two or more communication time slots. The two or more transport blocks are associated with two or more hybrid automatic repeat request (HARQ) process identifiers (IDs). The information for scheduling includes one or more of the following: a PUCCH resource indicator configured to indicate at least one resource used by the wireless device to send HARQ feedback associated with the two or more TBs; a downlink allocation indicator (DAI) configured to indicate a HARQ feedback position associated with the two or more TBs in the HARQ codebook; a HARQ process ID indicator indicating two or more HARQ process IDs; and one or more new data indicators (NDIs) configured to indicate whether at least one of the two or more TBs is a retransmission. Based at least in part on the DCI, two or more TBs are used for communication.

[0052] According to one or more embodiments of the present aspect, the PUCCH resource indicator includes one or more K1 values. According to one or more embodiments of the present aspect, two or more communication time slots are scheduled on corresponding time-frequency sources. According to one or more embodiments of the present aspect, the HARQ feedback position associated with two or more TBs in the HARQ codebook is further based at least in part on the number of two or more communication time slots. According to one or more embodiments of the present aspect, the value of the DAI indicates a HARQ feedback position for one TB in the two or more TBs, and another HARQ feedback position for a second TB in the two or more TBs is indicated at least in part based on the value of the DAI.

[0053] According to one or more embodiments of the present aspect, the HARQ process ID indicator is based at least in part on the number of physical shared channel transmissions in two or more communication time slots. According to one or more embodiments of the present aspect, the HARQ process ID indicator is based at least in part on at least one time slot number used for physical shared channel transmissions in two or more communication time slots. According to one or more embodiments of the present aspect, the HARQ process ID indicator is one of the two or more HARQ process IDs.

[0054] According to one or more embodiments of the present aspect, the HARQ process ID indicator includes a number of HARQ process IDs that is less than the number of two or more communication time slots. According to one or more embodiments of the present aspect, one or more NDIs are configured to indicate whether at least one TB of the two or more TBs is a retransmission. According to one or more embodiments of the present aspect, the one or more NDIs are a single NDI applied to two or more TBs.

[0055] According to another aspect of the present disclosure, a method implemented by a wireless device is provided. Downlink control information (DCI) is received. The DCI includes information for scheduling two or more transport blocks (TBs) on two or more communication time slots. The two or more transport blocks are associated with two or more hybrid automatic repeat request (HARQ) process identifiers (IDs). The information for scheduling includes one or more of the following: a PUCCH resource indicator configured to indicate at least one resource used by the wireless device (22) to send HARQ feedback associated with the two or more TBs; a downlink allocation indicator (DAI) configured to indicate a HARQ feedback position associated with the two or more TBs in a HARQ codebook; a HARQ process ID indicator indicating two or more HARQ process IDs; and one or more new data indicators (NDIs) configured to indicate whether at least one of the two or more TBs is a retransmission. The two or more TBs are used to communicate based at least in part on the DCI.

[0056] According to one or more embodiments of the present aspect, the PUCCH resource indicator includes one or more K1 values. According to one or more embodiments of the present aspect, two or more communication time slots are scheduled on corresponding time-frequency resources. According to one or more embodiments of the present aspect, the HARQ feedback position associated with two or more TBs in the HARQ codebook is further based at least in part on the number of two or more communication time slots. According to one or more embodiments of the present aspect, the value of the DAI indicates a HARQ feedback position for one TB in the two or more TBs, and another HARQ feedback position for a second TB in the two or more TBs is indicated at least in part based on the value of the DAI.

[0057] According to one or more embodiments of the present aspect, the HARQ process ID indicator is based at least in part on the number of physical shared channel transmissions in two or more communication time slots. According to one or more embodiments of the present aspect, the HARQ process ID indicator is based at least in part on at least one time slot number used for physical shared channel transmissions in two or more communication time slots. According to one or more embodiments of the present aspect, the HARQ process ID indicator is one of the two or more HARQ process IDs.

[0058] According to one or more embodiments of the present aspect, the HARQ process ID indicator includes a number of HARQ process IDs that is less than the number of two or more communication time slots. According to one or more embodiments of the present aspect, one or more NDIs are configured to indicate whether at least one TB of the two or more TBs is a retransmission. According to one or more embodiments of the present aspect, the one or more NDIs are a single NDI applied to two or more TBs. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] A more complete understanding of embodiments of the present invention and the attendant advantages and features thereof will be more readily appreciated when reference is made to the following detailed description considered in conjunction with the accompanying drawings, in which:

[0060] Figure 1 is a block diagram of radio resources in the new radio;

[0061] Figure 2 is an example of multi-slot scheduling;

[0062] Figure 3 is a schematic diagram illustrating an exemplary network architecture of a communication system connected to a host computer via an intermediate network according to the principles of the present disclosure;

[0063] Figure 4 is a block diagram of a host computer communicating with a wireless device via a network node over an at least partially wireless connection according to some embodiments of the present disclosure;

[0064] Figure 5 is a flow chart illustrating an exemplary method for executing a client application at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0065] Figure 6 is a flow chart illustrating an exemplary method for receiving user data at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0066] Figure 7is a flow chart illustrating an exemplary method for receiving user data from a wireless device at a host computer implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0067] Figure 8 is a flow chart illustrating an exemplary method for receiving user data at a host computer implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0068] Fig. 9 is a flow chart of an exemplary process in a network node according to some embodiments of the present disclosure;

[0069] Fig.10 is a flow chart of another exemplary process in a network node according to some embodiments of the present disclosure;

[0070] Fig.11 is a flow chart of an exemplary process in a wireless device according to some embodiments of the present disclosure;

[0071] Fig.12 is a flow chart of another exemplary process in a wireless device according to some embodiments of the present disclosure;

[0072] Fig.13 is a schematic diagram of an example of a multi-slot scheduled PDCCH opportunity with a single uplink and a single downlink scheduling DCI;

[0073] Fig.14 is a diagram illustrating an example of PUCCH resources in each slot for HARQ feedback. DETAILED DESCRIPTION

[0074] Multi-slot scheduling mechanisms, such as Figure 2 The multi-slot scheduling mechanism shown in , relies on a single DCI that includes scheduling indications of multiple, e.g., PDSCH slots, where each PDSCH slot may have different resource allocations, etc. This disadvantageously results in a large DCI size, thereby increasing the bandwidth burden of the wireless device and increasing the PDCCH blocking probability.

[0075] Slot aggregation, as an established form of multi-slot scheduling in 3GPP Rel-15, does not involve the complexity level of a multi-scheduling mechanism. However, slot aggregation has some problems that need to be solved. For example, the current slot aggregation mechanism relies on single-layer transmission and therefore does not address multi-layer transmission. In addition, the current slot aggregation mechanism only transmits one TB and therefore does not address the case of having multiple TBs. Since all slots may contain the same TB, 3GPP Rel-15 slot aggregation may operate with only a single HARQ process and provide PUCCH resources for a single TB in the DCI. However, this configuration may not be applicable to the case of multi-slot scheduling with different TBs.

[0076] Therefore, there is a need for an efficient single DCI multi-slot scheduling mechanism with low complexity that addresses HARQ processing in the case of multi-slot scheduling with multiple TBs. The disclosure herein provides an efficient process for HARQ processing in the case of single DCI multi-slot scheduling where multiple TBs are scheduled over multiple slot spans.

[0077] Before describing the exemplary embodiments in detail, it should be noted that the embodiments reside primarily in a combination of apparatus components and processing steps related to transmitting downlink control information (DCI) for scheduling multiple transport blocks on multiple communication slots associated with at least one hybrid automatic repeat request (HARQ) instance. Therefore, where applicable, components have been represented in the drawings by conventional symbols, and these components only show those specific details relevant to understanding the embodiments to avoid obscuring the details of the present disclosure that are obvious to those of ordinary skill in the art who benefit from the description herein. Like numbers refer to like elements throughout the specification.

[0078] As used herein, relational terms such as "first" and "second", "top" and "bottom", etc. may be used only to distinguish one entity or element from another entity or element, without requiring or implying any physical or logical relationship or order between such entities or elements. The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the concepts described herein. As used herein, the singular forms "a", "an", and "the" are also intended to include the plural forms unless the context indicates otherwise. It will be further understood that when used herein, the terms "include" and / or "comprise" specify the presence of the described features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0079] In the embodiments described herein, connection terms such as "in communication with..." may be used to indicate electrical or data communications, which may be achieved, for example, by physical contact, induction, electromagnetic radiation, radio signals, infrared signals, or optical signals. Those skilled in the art will appreciate that multiple components may interoperate and that modifications and variations may be made to achieve electrical and data communications.

[0080] In some embodiments described herein, the terms "coupled," "connected," and the like may be used herein to indicate a connection, although not a direct one, and may include wired and / or wireless connections.

[0081] The term "network node" used herein may be any kind of network node included in a radio network, and may also include a base station (BS), a radio base station, a base transceiver station (BTS), a base station controller (BSC), a radio network controller (RNC), a gNode B (gNB), an evolved Node B (eNB or eNodeB), a Node B, a multi-standard radio (MSR) radio node such as an MSR BS, a multi-cell / multicast coordination entity (MCE), a relay node, an integrated access and backhaul (IAB) node, a donor node controlling a relay, a radio access point (AP), a transmission point, a transmission node, a remote radio unit (RRU) remote radio head (RRH), a core network node (e.g., a mobile management entity (MME), a self-organizing network (SON) node, a coordination node, a positioning node, an MDT node, etc.), an external node (e.g., a third-party node, a node outside the current network), a node in a distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also include a test device. As used herein, the term "radio node" may also be used to refer to a wireless device (WD), such as a wireless device (WD) or a radio network node.

[0082] In some embodiments, the non-limiting terms "wireless device (WD)" or "user equipment (UE)" are used interchangeably. The WD herein may be any type of wireless device capable of communicating with a network node or another WD via a radio signal, such as a wireless device (WD). The WD may also be a radio communication device, a target device, a device-to-device (D2D) WD, a machine type WD, or a WD capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet computer, a mobile terminal, a smart phone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IOT) device, etc.

[0083] In addition, in some embodiments, the general term "radio network node" is used. It can be any kind of radio network node, including any one of a base station, a radio base station, a base transceiver station, a base station controller, a network controller, an RNC, an evolved Node B (eNB), a Node B, a gNB, a multi-cell / multicast coordination entity (MCE), a relay node, an IAB node, an access point, a radio access point, a remote radio unit (RRU), and a remote radio head (RRH).

[0084] The term "resource" as used herein may correspond to any type of physical resource or radio resource expressed in terms of time and / or frequency length. A radio node sends or receives a signal on a time resource. Examples of time resources are: symbol, time slot, subframe, radio frame, transmission time interval (TTI), interleaving time, etc.

[0085] An "indication" may generally indicate the information it indicates and / or indicates explicitly and / or implicitly. An implicit indication may be based, for example, on a location and / or resource used for transmission. An explicit indication may be based, for example, on parameterization with one or more parameters, and / or one or more indexes, and / or one or more bit patterns representing information. Control signaling based on a sequence of resources implicitly indicating a type of control signaling as described herein may be particularly contemplated.

[0086] Transmission in a downlink may involve transmission from a network or a network node to a terminal. Transmission in an uplink may involve transmission from a terminal to a network or a network node. Transmission in a sidelink may involve (direct) transmission from one terminal to another terminal. Uplink, downlink and sidelink (e.g., sidelink transmission and reception) may be considered as communication directions. In some variants, uplink and downlink may also be used to describe wireless communications between network nodes, such as for wireless backhaul and / or relay communication and / or (wireless) network communication between, for example, base stations or similar network nodes, in particular communications terminated therein. It may be considered that backhaul and / or relay communication and / or network communication are implemented as sidelink or uplink communication or in a form similar thereto.

[0087] Configuring a terminal or wireless device or node may involve indicating and / or causing the wireless device or node to change its configuration, for example, at least one setting and / or registration entry and / or operating mode. The terminal or wireless device or node may be adapted to configure itself, for example, according to information or data in a memory of the terminal or wireless device. Configuring a node or terminal or wireless device by another device or node or network may refer to and / or include sending information and / or data and / or instructions to the wireless device or node by another device or node or network, for example, allocation data (which may also be and / or include configuration data) and / or scheduling data and / or scheduling authorization. Configuring a terminal may include sending allocation / configuration data indicating the modulation and / or coding used to the terminal. The terminal may be configured with and / or for scheduling data, and / or configured to use scheduled and / or allocated uplink resources, for example, for sending, and / or use scheduled and / or allocated downlink resources, for example, for receiving. Uplink resources and / or downlink resources may be scheduled and / or provided with allocation or configuration data.

[0088] Data and / or information may refer to any kind of data, in particular any one and / or any combination of control data or user data or payload data. Control information (which may also be referred to as control data) may refer to data control and / or scheduling and / or data related to data transmission processes and / or network or terminal operations.

[0089] Note that while terminology from one particular wireless system may be used in the present disclosure, such as, for example, 3GPP LTE and / or New Radio (NR), this should not be considered to limit the scope of the present disclosure to only the aforementioned systems. Other wireless systems, including but not limited to Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM), may also benefit from utilizing the ideas encompassed within the present disclosure.

[0090] It should also be noted that the functions described herein as being performed by a wireless device or network node may be distributed across multiple wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network nodes and wireless devices described herein are not limited to the performance of a single physical device, but may in fact be distributed across multiple physical devices.

[0091] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the present disclosure belongs. It will also be further understood that, unless expressly defined herein, the terms used herein should be interpreted as having a meaning 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.

[0092] Embodiments provide for transmitting downlink control information (DCI) for scheduling a plurality of transport blocks over a plurality of communication time slots associated with at least one hybrid automatic repeat request (HARQ) instance.

[0093] Referring again to the drawings, wherein like elements are represented by like reference numerals, Figure 3 1 shows a schematic diagram of a communication system 10 according to an embodiment, such as a 3GPP type cellular network that can support standards such as LTE and / or NR (5G), which includes an access network 12 such as a radio access network, and a core network 14. The access network 12 includes a plurality of network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each of which defines a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c can be connected to the core network 14 via a wired or wireless connection 20. A first wireless device (WD) 22a located in the coverage area 18a is configured to be wirelessly connected to the corresponding network node 16c or to be paged by the corresponding network node 16c. A second WD 22b in the coverage area 18b can be wirelessly connected to the corresponding network node 16a. Although multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to situations where only a single WD is in the coverage area or where a single WD is connected to a corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include more WDs 22 and network nodes 16.

[0094] In addition, it is contemplated that the WD 22 may communicate with more than one network node 16 and more than one type of network node 16 simultaneously and / or be configured to communicate with more than one network node 16 and more than one type of network node 16, respectively. For example, the WD 22 may have dual connectivity with a network node 16 supporting LTE and with the same or different network node 16 supporting NR. As an example, the WD 22 may communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0095] The communication system 10 itself may be connected to a host computer 24, which may be implemented in hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24, or may extend via an optional intermediate network 30. The intermediate network 30 may be one of a public, private, or managed network, or a combination of more than one of a public, private, or managed network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may include two or more subnetworks (not shown).

[0096] Figure 3 The communication system as a whole realizes the connection between one of the connected WD 22a, 22b and the host computer 24. The connection can be described as an over-the-top (OTT) connection. The host computer 24 and the connected WD 22a, 22b are configured to use the access network 12, the core network 14, any intermediate network 30 and another infrastructure (not shown) as an intermediate medium to transmit data and / or signaling via the OTT connection. The OTT connection can be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes do not know the routes of the uplink and downlink communications. For example, the network node 16 may not or need not be notified of the past routes of the incoming downlink communications with data that will be forwarded (e.g., handed over) to the connected WD 22a from the host computer 24. Similarly, the network node 16 does not need to know the future routes of the outgoing uplink communications from the WD 22a to the host computer 24.

[0097] The network node 16 is configured to include a configuration unit 32, which is configured to perform one or more functions described herein, such as configuring control information, i.e., DCI, for associating with a HARQ process, i.e., providing multi-slot scheduling of HARQ processes for single-DCI multi-slot scheduling. The wireless device 22 is configured to include a control information unit 34, which is configured to perform one or more functions described herein, such as receiving control information, i.e., DCI.

[0098] According to the embodiment, reference will now be made to Figure 410 to describe an exemplary implementation of the WD 22, network node 16, and host computer 24 discussed in the previous paragraphs. In the communication system 10, the host computer 24 includes hardware (HW) 38, which includes a communication interface 40 configured to establish and maintain a wired or wireless connection with different communication devices in the communication system 10. The host computer 24 also includes a processing circuit 42, which may have storage and / or processing capabilities. The processing circuit 42 may include a processor 44 and a memory 46. In particular, in addition to or in place of a processor such as a central processing unit and a memory, the processing circuit 42 may include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) suitable for executing instructions. The processor 44 may be configured to access (e.g., write to and / or read from) a memory 46, which may include any kind of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).

[0099] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein, and / or to cause such methods and / or processes to be performed, for example, by host computer 24. Processor 44 corresponds to one or more processors 44 for performing the functions of host computer 24 described herein. Host computer 24 includes memory 46, which is configured to store data, program software code, and / or other information described herein. In some embodiments, software 48 and / or host application 50 may include instructions that, when executed by processor 44 and / or processing circuitry 42, cause processor 44 and / or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with host computer 24.

[0100] The software 48 may be executed by the processing circuit 42. The software 48 includes a host application 50. The host application 50 may be operable to provide services to a remote user, such as a WD 22 connected via an OTT connection 52 terminated at the WD 22 and the host computer 24. In providing services to the remote user, the host application 50 may provide user data sent using the OTT connection 52. "User data" may be data and information described herein as implementing the described functions. In one embodiment, the host computer 24 may be configured to provide control and functionality to a service provider, and may be operated by or on behalf of the service provider. The processing circuit 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, send to and / or receive from the network node 16 and / or the wireless device 22. The processing circuit 42 of the host computer 24 may include an information unit 54, which is configured to enable the service provider to perform one or more of the information related to the control information described herein, such as providing, forwarding, transmitting, determining, receiving, etc.

[0101] The communication system 10 also includes a network node 16 provided in the communication system 10, and the network node 16 includes hardware 58 that enables it to communicate with the host computer 24 and the WD 22. The hardware 58 may include a communication interface 60 for establishing and maintaining a wired or wireless connection to the interface of different communication devices in the communication system 10, and a radio interface 62 for establishing and maintaining at least one wireless connection 64 with the WD 22 located in the coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct, or it may pass through the core network 14 of the communication system 10 and / or through one or more intermediate networks 30 external to the communication system 10.

[0102] In the illustrated embodiment, the hardware 58 of the network node 16 also includes a processing circuit 68. The processing circuit 68 may include a processor 70 and a memory 72. In particular, the processing circuit 68 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) adapted to execute instructions, in addition to or in place of a processor such as a central processing unit and a memory. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may include any kind of volatile and / or non-volatile memory, such as a buffer memory and / or a buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).

[0103] Therefore, the network node 16 also has software 74, which is stored internally, for example, in the memory 72, or stored in an external memory (e.g., a database, a storage array, a network storage device, etc.) accessible to the network node 16 via an external connection. The software 74 can be executed by the processing circuit 68. The processing circuit 68 can be configured to control any method and / or process described herein, and / or cause such a method and / or process to be performed, for example, by the network node 16. The processor 70 corresponds to one or more processors 70 for performing the functions of the network node 16 described herein. The memory 72 is configured to store data, programming software code, and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or the processing circuit 68, cause the processor 70 and / or the processing circuit 68 to perform the processes described herein with respect to the network node 16. The processing circuitry 68 of the network node 16 may include a configuration unit 32 configured to perform one or more functions described herein, such as configuring control information, ie DCI, for associating with a HARQ process, ie providing multi-slot scheduling of a HARQ process for single DCI multi-slot scheduling.

[0104] The communication system 10 also includes the already mentioned WD 22. The WD 22 may have hardware 80 that may include a radio interface 82 configured to establish and maintain a wireless connection 64 with a network node 16 serving the coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0105] The hardware 80 of the WD 22 also includes a processing circuit 84. The processing circuit 84 may include a processor 86 and a memory 88. In particular, in addition to or in place of a processor such as a central processing unit and a memory, the processing circuit 84 may include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) the memory 88, which may include any kind of volatile and / or non-volatile memory, for example, a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).

[0106] Therefore, WD 22 may also include software 90, which is stored in memory 88 at WD 22, for example, or in an external memory (e.g., a database, a storage array, a network storage device, etc.) accessible to WD. Software 90 may be executed by processing circuit 84. Software 90 may include client application 92. With the support of host computer 24, client application 92 may be operable to provide services to human or non-human users via WD 22. In host computer 24, executing host application 50 may communicate with executing client application 92 via OTT connection 52 terminated at WD 22 and host computer 24. When providing services to users, client application 92 may receive request data from host application 50 and provide user data in response to the request data. OTT connection 52 may transmit both request data and user data. Client application 92 may interact with users to generate user data it provides.

[0107] The processing circuit 84 may be configured to control any method and / or process described herein and / or cause such method and / or process to be performed, for example, by the WD 22. The processor 86 corresponds to one or more processors for performing the WD 22 functions described herein. The WD 22 includes a memory 88, which is configured to store data, program software codes, and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or the processing circuit 84, cause the processor 86 and / or the processing circuit 84 to perform the processes described herein. For example, the processing circuit 84 of the wireless device 22 may include a control information unit 34, which is configured to perform one or more functions described herein, such as receiving control information, i.e., DCI.

[0108] In some embodiments, the internal workings of network node 16, WD 22, and host computer 24 may be as follows: Figure 4 As shown in , and independently, the surrounding network topology can be Figure 3 network topology.

[0109] exist Figure 4 In the figure, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicitly involving any intermediate devices and the precise message routing via these devices. The network architecture can determine the route, which can be configured to be hidden from the WD 22, or from the service provider operating the host computer 24, or both. When the OTT connection 52 is active, the network architecture can further make decisions by which it dynamically changes the route (e.g., based on load balancing considerations or reconfiguration of the network).

[0110] The wireless connection 64 between WD 22 and network node 16 is in accordance with the teachings of the embodiments described in the present disclosure. One or more of the various embodiments use the OTT connection 52 to improve the performance of the OTT service provided to WD 22, where the wireless connection 64 can form the last leg. More specifically, the teachings of some of these embodiments can improve data rates, latency, and / or power consumption, thereby providing benefits such as reduced user waiting time, relaxed file size restrictions, better responsiveness, extended battery life, etc.

[0111] In some embodiments, a measurement process may be provided for the purpose of monitoring data rates, delays, and other factors improved by one or more embodiments. An optional network function may also be provided for reconfiguring the OTT connection 52 between the host computer 24 and the WD 22 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24, or in the software 90 of the WD 22, or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 52 passes; the sensor may participate in the measurement process by providing the values ​​of the monitored quantities of the above examples or providing the values ​​of other physical quantities from which the software 48, 90 can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 52 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such processes and functions may be known and practiced in the art. In some embodiments, the measurement may involve dedicated WD signaling, which facilitates throughput, propagation time, delay, etc. measurements of the host computer 24. In some embodiments, the measurement may be achieved by the software 48, 90 using the OTT connection 52 to cause a message, particularly an empty or "fake" message, to be sent while monitoring propagation time, errors, etc.

[0112] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes a network node 16 having a radio interface 62. In some embodiments, the network node 16 is configured to, and / or the processing circuitry 68 of the network node 16 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending transmissions to the WD 22, and / or preparing / terminating / maintaining / supporting / ending reception of transmissions from the WD 22.

[0113] In some embodiments, host computer 24 includes processing circuitry 42 and communication interface 40 configured to receive user data originating from transmissions from WD 22 to network node 16. In some embodiments, WD 22 is configured to, and / or includes a radio interface 82 and / or processing circuitry 84 configured to: perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending transmissions to network node 16, and / or preparing / terminating / maintaining / supporting / ending reception of transmissions from network node 16.

[0114] Although Figure 3 and Figure 4Various "units" such as configuration unit 32 and control information unit 34 are shown as being within the corresponding processor, but it is contemplated that these units may be implemented so that a portion of the unit is stored in a corresponding memory within the processing circuit. In other words, these units may be implemented within the processing circuit in hardware, or a combination of hardware and software.

[0115] Figure 5 is a diagram showing a method for performing a Figure 3 and Figure 4 Flow chart of an exemplary method implemented in a communication system of a communication system of FIG. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be reference Figure 4 Those devices described. In a first step of the method, host computer 24 provides user data (box S100). In an optional sub-step of the first step, host computer 24 provides user data by executing a host application such as, for example, host application 50 (box S102). In a second step, host computer 24 initiates a transmission to WD 22 carrying user data (box S104). In an optional third step, in accordance with the teachings of the embodiments described in the present disclosure, network node 16 sends the user data carried in the transmission initiated by host computer 24 to WD 22 (box S106). In an optional fourth step, WD 22 executes a client application associated with the host application 50 executed by host computer 24, such as, for example, client application 92 (box S108).

[0116] Figure 6 is a diagram showing a method for performing a Figure 3 and Figure 4 Flow chart of an exemplary method implemented in a communication system of a communication system of FIG. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be reference Figure 3 and Figure 4 Those devices described. In a first step of the method, host computer 24 provides user data (box S110). In an optional sub-step (not shown), host computer 24 provides user data by executing a host application such as, for example, host application 50. In a second step, host computer 24 initiates a transmission to WD 22 carrying the user data (box S112). According to the teachings of the embodiments described in the present disclosure, the transmission can pass through network node 16. In an optional third step, WD 22 receives the user data carried in the transmission (box S114).

[0117] Figure 7 is a diagram showing a method for performing a Figure 3 and Figure 4Flow chart of an exemplary method implemented in a communication system of a communication system of FIG. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be reference Figure 3 to Figure 4 Those devices described. In the optional first step of the method, WD 22 receives input data provided by host computer 24 (box S116). In the optional sub-step of the first step, WD 22 executes client application 92, which provides user data in response to the received input data provided by host computer 24 (box S118). Additionally or alternatively, in the optional second step, WD 22 provides user data (box S120). In the optional sub-step of the second step, WD provides user data by executing a client application such as, for example, client application 92 (box S122). When providing user data, the executed client application 92 can further consider user input received from the user. Regardless of the specific manner in which user data is provided, WD 22 can initiate the transmission of user data to host computer 24 in an optional third sub-step (box S124). In the fourth step of the method, according to the teachings of the embodiments described in the present disclosure, host computer 24 receives user data sent from WD 22 (box S126).

[0118] Figure 8 is a diagram showing a method for performing a Figure 3 and Figure 4 Flow chart of an exemplary method implemented in a communication system of a communication system of FIG. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be reference Figure 3 to Figure 4 In an optional first step of the method, network node 16 receives user data from WD 22 in accordance with the teachings of the embodiments described in the present disclosure (block S128). In an optional second step, network node 16 initiates transmission of the received user data to host computer 24 (block S130). In a third step, host computer 24 receives the user data carried in the transmission initiated by network node 16 (block S132).

[0119] Fig. 91 is a flow chart of an exemplary process in a network node 16 according to one or more embodiments of the present disclosure. One or more blocks and / or functions performed by the network node 16 may be performed by one or more elements of the network node 16, such as by the configuration unit 32 in the processing circuit 68, the processor 70, and the radio interface 62. In one or more embodiments, the network node 16 (such as via one or more of the processing circuit 68, the processor 70, and the radio interface 62) is configured to configure (block S134) downlink control information (DCI), wherein the DCI is configured to schedule multiple transport blocks on multiple communication time slots, and wherein the scheduling is associated with at least one hybrid automatic repeat request (HARQ) instance. As used herein, "HARQ instance" may be used interchangeably with "HARQ process ID" and / or "HARQ codebook". In one or more embodiments, the network node 16 (such as via one or more of the processing circuit 68, the processor 70, and the radio interface 62) is configured to optionally (block S136) transmit the DCI.

[0120] In one or more embodiments, multiple communication time slots are scheduled on the same (i.e., corresponding) time-frequency resources of a physical shared channel. For example, the time-frequency resource configuration in one communication time slot may correspond to the time-frequency resource configuration in at least another communication time slot in multiple communication time slots. In one or more embodiments, multiple communication time slots are used to provide a physical downlink shared channel. In one or more embodiments, at least one HARQ instance corresponds to multiple HARQ instances, wherein the multiple HARQ instances are sent using the same HARQ codebook. In one or more embodiments, the HARQ instance is associated with a new data indicator (NDI) bit applied to multiple transport blocks.

[0121] Fig.10is a flowchart of another exemplary process in the network node 16 according to one or more embodiments of the present disclosure. One or more blocks and / or functions performed by the network node 16 may be performed by one or more elements of the network node 16, such as the configuration unit 32 in the processing circuit 68, the processor 70, the radio interface 62, etc. In one or more embodiments, the network node 16 (such as via one or more of the processing circuit 68, the processor 70, and the radio interface 62) is configured to be configured so that (box S138) downlink control information (DCI) is sent to the wireless device, the DCI including information for scheduling two or more transport blocks (TBs) on two or more communication time slots, the two or more transport blocks being associated with two or more hybrid automatic repeat request (HARQ) process identifiers (IDs), the information for scheduling including one or more of the following: a PUCCH resource indicator, configured to indicate at least one resource used by the wireless device 22 to send HARQ feedback associated with the two or more TBs; a downlink allocation indicator (DAI), configured to indicate a HARQ feedback position associated with the two or more TBs in the HARQ codebook; a HARQ process ID indicator, which indicates two or more HARQ process IDs; and one or more new data indicators (NDIs), configured to indicate whether at least one TB of the two or more TBs is a retransmission, as described herein. In one or more embodiments, the network node 16 (such as via one or more of the processing circuit 68, the processor 70, and the radio interface 62) is configured to configure communication using two or more TBs based at least in part on the DCI (block S140), as described herein.

[0122] According to one or more embodiments of the present aspect, the PUCCH resource indicator includes one or more K1 values. According to one or more embodiments of the present aspect, two or more communication time slots are scheduled on corresponding time-frequency resources. According to one or more embodiments of the present aspect, the HARQ feedback position associated with two or more TBs in the HARQ codebook is further based at least in part on the number of two or more communication time slots. According to one or more embodiments of the present aspect, the value of the DAI indicates a HARQ feedback position for one TB in the two or more TBs, and another HARQ feedback position for a second TB in the two or more TBs is indicated at least in part based on the value of the DAI.

[0123] According to one or more embodiments of the present aspect, the HARQ process ID indicator is based at least in part on the number of physical shared channel transmissions in two or more communication time slots. According to one or more embodiments of the present aspect, the HARQ process ID indicator is based at least in part on at least one time slot number used for physical shared channel transmissions in two or more communication time slots. According to one or more embodiments of the present aspect, the HARQ process ID indicator is one of the two or more HARQ process IDs.

[0124] According to one or more embodiments of the present aspect, the HARQ process ID indicator includes a number of HARQ process IDs that is less than the number of two or more communication time slots. According to one or more embodiments of the present aspect, one or more NDIs are configured to indicate whether at least one TB of the two or more TBs is a retransmission. According to one or more embodiments of the present aspect, the one or more NDIs are a single NDI applied to two or more TBs.

[0125] Fig.11 is a flow chart of an exemplary process in the wireless device 22 according to one or more embodiments of the present disclosure. One or more blocks and / or functions performed by the wireless device 22 may be performed by one or more elements of the wireless device 22, such as by the control information unit 34 in the processing circuit 84, the processor 86, the radio interface 82, etc. In some embodiments, the wireless device 22 (such as via one or more of the processing circuit 84, the processor 86, and the radio interface 82) is configured to configure (block S142) receive downlink control information (DCI), wherein the DCI is configured to schedule a plurality of transport blocks on a plurality of communication time slots, and wherein the scheduling is associated with at least one hybrid automatic repeat request (HARQ) instance.

[0126] In one or more embodiments, multiple communication time slots are scheduled on the same time-frequency resources of a physical shared channel.

[0127] In one or more embodiments, a plurality of communication time slots are used to provide a physical downlink shared channel. In one or more embodiments, at least one HARQ instance corresponds to a plurality of HARQ instances, wherein the plurality of HARQ instances are transmitted using the same HARQ codebook. In one or more embodiments, the HARQ instance is associated with a new data indicator (NDI) bit applied to a plurality of transport blocks.

[0128] Fig.12is a flow chart of another exemplary process in the wireless device 22 according to one or more embodiments of the present disclosure. One or more blocks and / or functions performed by the wireless device 22 may be performed by one or more elements of the wireless device 22, such as the control information unit 34 in the processing circuit 84, the processor 86, the radio interface 82, etc. In one embodiment, the wireless device 22 (such as via one or more of the processing circuit 84, the processor 86 and the radio interface 82) is configured to receive (box S144) downlink control information (DCI), wherein the DCI includes information for scheduling two or more transport blocks (TBs) on two or more communication time slots, and wherein the two or more transport blocks are associated with two or more hybrid automatic repeat request (HARQ) process identifiers (IDs), and the information for scheduling includes one or more of the following: a PUCCH resource indicator, configured to indicate at least one resource used by the wireless device to send HARQ feedback related to the two or more TBs; a downlink allocation indicator (DAI), configured to indicate a HARQ feedback position related to the two or more TBs in the HARQ codebook; a HARQ process ID indicator, which indicates two or more HARQ process IDs; and one or more new data indicators (NDIs), configured to indicate whether at least one TB of the two or more TBs is a retransmission. In one or more embodiments, the wireless device 22 (such as via one or more of the processing circuit 84, the processor 86, and the radio interface 82) is configured to communicate using two or more TBs based at least in part on the DCI (block S146).

[0129] According to one or more embodiments of the present aspect, the PUCCH resource indicator includes one or more K1 values. According to one or more embodiments of the present aspect, two or more communication time slots are scheduled on corresponding time-frequency resources. According to one or more embodiments of the present aspect, the HARQ feedback position associated with two or more TBs in the HARQ codebook is further based at least in part on the number of two or more communication time slots. According to one or more embodiments of the present aspect, the value of the DAI indicates a HARQ feedback position for one TB in the two or more TBs, and another HARQ feedback position for a second TB in the two or more TBs is indicated at least in part based on the value of the DAI.

[0130] According to one or more embodiments of the present aspect, the HARQ process ID indicator is based at least in part on the number of physical shared channel transmissions in two or more communication time slots. According to one or more embodiments of the present aspect, the HARQ process ID indicator is based at least in part on at least one time slot number used for physical shared channel transmissions in two or more communication time slots. According to one or more embodiments of the present aspect, the HARQ process ID indicator is one of the two or more HARQ process IDs.

[0131] According to one or more embodiments of the present aspect, the HARQ process ID indicator includes a number of HARQ process IDs that is less than the number of two or more communication time slots. According to one or more embodiments of the present aspect, one or more NDIs are configured to indicate whether at least one TB of the two or more TBs is a retransmission. According to one or more embodiments of the present aspect, the one or more NDIs are a single NDI applied to two or more TBs.

[0132] Embodiments provide configuration control information for scheduling multiple transport blocks over multiple communication time slots associated with at least one hybrid automatic repeat request (HARQ) instance. Having generally described arrangements for configuring control information for scheduling multiple transport blocks over multiple communication time slots associated with at least one HARQ instance, details of examples of these arrangements, functions, and processes are provided below and may be implemented by a network node 16, a wireless device 22, and / or a host computer 24.

[0133] General framework of single DCI multi-slot scheduling:

[0134] Multi-slot scheduling is described, in which the network node 16, such as via one or more of the processing circuit 68, the processor 70, the radio interface 62, the configuration unit 32, etc., schedules the wireless device 22 to use a single DCI, i.e., a control information type, for multiple time slots. Each scheduled time slot can have the same time domain and frequency domain resource allocation for PxSCH (i.e., PDSCH or PUSCH), thereby, the network node 16 does not need to send multiple separate allocations. In addition to this, most (in extreme cases, all) other information in the DCI format remains unchanged for all time slots, such as MCS, number of layers, antenna ports, carrier indication, etc. Fig.13is a schematic diagram of an example of such a single DCI multi-slot scheduling mechanism. In this specific example, both DL and UL are scheduled for multiple time slots using a single DL / UL DCI. As used herein, PxSCH may include and / or correspond to one or more TBs. For example, in one or more embodiments, PDSCH may carry one or more TBs. For PDSCH, if there are two TBs, there may also be two HARQ processes, but the DCI may contain only one HARQ ID so that TB1 may use HARQ IDa and TB2 may use HARQ IDb, where the ID is signed in the DCI. In another example, in one or more embodiments, PUSCH may always correspond to a single TB. In another example, in one or more embodiments in the case of retransmission, there may be another PxSCH using the same TB (mapped to the same HARQ process), but in this context, the TBs may be considered to be different.

[0135] What may differ between time slots are the HARQ process ID of the associated TB, the PUCCH resources, and the details related to the HARQ codebook. This will be further described below.

[0136] What has been described above and the rest of this description about time units counted in slots can be generalized to count, for example, in symbols, or blocks of a certain number of symbols. This can be useful when having multi-half-slot scheduling.

[0137] HARQ processing:

[0138] PUCCH resource part

[0139] In one or more embodiments, the PUCCH resource portion may be applicable only for DL ​​transmissions.

[0140] Since multiple TBs may potentially be sent by the network node 16 to the wireless device 22, such as via one or more of the processing circuitry 68, the processor 70, the radio interface 62, the configuration unit 32, etc., it may be useful to have a suitable HARQ ACK / NACK process suitable for performing one or more HARQ instances and / or opportunities and / or processes.

[0141] In one or more embodiments, a PUCCH format that supports multiple bits, such as format 2 / 3 / 4, is used to send multiple ACK / NACKs in the same HARQ codebook. In this case, a single K1 value can be used to indicate the time slot used for the PUCCH, and a single PUCCH resource indicator can be used to indicate the PUCCH resource in the indicated time slot for combined HARQ feedback. In this case, the K1 value will be relative to a reference time slot, typically the last received or scheduled time slot of a multiple PDSCH assignment. This approach can be used for both frequency division duplex (FDD) and time division duplex (TDD), and may be particularly attractive for TDD. This embodiment is Fig.14 As illustrated in FIG. 1 , row (a) generally shows an example of PUCCH resources in each slot for HARQ feedback, where the time / frequency resources within the slot are not shown.

[0142] A variation of this embodiment is to send multiple ACK / NACKs until the maximum delay. The K1 value will then typically be associated with the first scheduled timeslot. All timeslots that are sent early enough to report ACK / NACK on this PUCCH resource may use this PUCCH resource (the number of timeslots required may be predefined or RRC configured). For all subsequent timeslots scheduled by a multi-slot DCI, the K1 value may point or indicate a new PUCCH resource to report ACK / NACK on. This embodiment is Fig.14 is illustrated in row (b).

[0143] In one or more embodiments, each time slot (or a group of time slots if a TB is mapped to a group of time slots) corresponds to its own PUCCH transmission. If a single K1 value and PUCCH resource indicator are provided, such as via one or more of the processing circuit 68, the processor 70, the radio interface 62, the configuration unit 32, etc., the time slot carrying the PUCCH for the TB is the K1 time slot after the (last) time slot carrying the TB. The same PUCCH resources are used in each time slot. This embodiment may be particularly attractive for FDD because for each DL time slot, a UL time slot exists after K1 time slots, which is not necessarily the case for TDD. This embodiment is particularly attractive for FDD, because for each DL time slot, a UL time slot exists after K1 time slots, which is not necessarily the case for TDD. Fig.14 is illustrated in row (c) of .

[0144] In one or more embodiments, multiple PUCCH resources are used in the same time slot. Here, one K1 value is used to indicate the PUCCH time slot for all TBs relative to a reference time slot (typically the last scheduled or received DL time slot of a multiple PDSCH assignment). If a single PUCCH resource indicator is provided, such as via one or more of the processing circuit 68, the processor 70, the radio interface 62, the configuration unit 32, etc., a rule is used to obtain multiple PUCCH resources, for example, a series of (contiguous or non-contiguous) PUCCH resources starting from the indicated resource. This embodiment is Fig.14 is illustrated in row (d) of .

[0145] In one or more embodiments, if the DL / UL configuration uses more DL than UL, the ACK / NACK of all adjacent DL time slots are combined together into the same PUCCH resource. Fig.14 is illustrated in row (e) of .

[0146] In the case where one parameter is used for one slot (a subset thereof), if at least one of the K1 value and the PUCCH resource indicator is provided for at least one additional slot, greater flexibility may be provided in resource selection for HARQ feedback. However, this flexibility may increase the size of the DCI.

[0147] Thus, as used herein in one or more embodiments, a PUCCH resource indicator is configured to indicate at least one resource, wherein the at least one resource is used to send HARQ feedback and may be associated with one or more of: a radio resource such as, for example, a resource element, and one or more PUCCH resources.

[0148] HARQ codebook part

[0149] In one or more embodiments, the HARQ codebook portion may be applicable only to DL transmissions.

[0150] In the HARQ codebook, one entry (1 bit or multiple bits, depending on the PDSCH configuration, such as multiple-input multiple-output (MIMO), code block group) may be required per PDSCH. In the case of a semi-statically configured HARQ codebook (type 1 codebook), each PDSCH within the HARQ association window is associated with one entry in the HARQ codebook. This principle can be reused even if there is only one PDCCH scheduling multiple PDSCHs.

[0151] For dynamic HARQ codebooks (type 2 codebooks), the positions of entries in the HARQ codebook can be obtained from the DCI (more specifically, from the counter DAI). In the case where a single DCI scheduling multiple PDSCHs contains multiple counter DAI values ​​(one for each PDSCH), each counter DAI can determine the position of the HARQ feedback for the corresponding PDSCH. If the DCI contains a single counter DAI, the position of the HARQ feedback for all scheduled PDSCHs can be obtained from a single counter DAI. For example, the position of the HARQ feedback associated with the first PDSCH is indicated by the counter DAI, and the remaining feedback entries are subsequently placed after the first feedback entry (more generally, the counter DAI together with the number of scheduled PDSCHs determines the positions of all HARQ feedback entries in the HARQ codebook corresponding to the scheduled PDSCH).

[0152] If the size of the HARQ codebook is not increased, bundling can be introduced. For example, instead of providing one feedback entry per PDSCH, feedback for multiple PDSCHs (in the extreme case of scheduling all PDSCHs with a single DCI) is combined (e.g., typically logically ANDed). In this case, fewer entries are needed in the HARQ codebook, and the positions of these fewer entries can be indicated by a single counter DAI value together with a rule or multiple counter DAI values.

[0153] The counter DAI value indicated in the DCI may be increased by 1 per scheduled PDSCH (and this means per scheduled DL DCI in existing systems, since one DCI schedules one PDSCH). In NR, such as in 3GPP Rel-15, the counter DAI value is represented by two bits and wraps around. When a single DCI schedules multiple PDSCHs, the signaled counter DAI may be increased by only 1 relative to the previous DL allocation DCI, but the wireless device 22 increases its internal counter DAI count by the number of scheduled PDSCHs, i.e., Counter_DAI_counter_UE = Counter_DAI_counter_UE + nbr_scheduled_PDSCH (compared to Counter_DAI_counter_UE = Counter_DAI_counter_UE + 1, current behavior). nbr_scheduled_PDSCH is the number of PDSCHs scheduled by a multi-PDSCH DCI and follows DCI, RRC signaling, MAC CE, or any combination thereof. Increasing the signaled counter DAI by only 1 relative to the previous DL allocation DCI may alleviate the wraparound problem that may occur with a two-bit representation.An alternative is to increase the bit size of the counter DAI, either for all DCIs or only for DCIs scheduling multiple PDSCHs.

[0154] HARQ process ID part

[0155] In one or more embodiments, the HARQ process ID portion may be applicable to both DL and UL transmissions.

[0156] In existing systems, DCI (in both UL and DL) may contain a HARQ process ID to associate the scheduled PxSCH with the HARQ process ID. In one or more embodiments, if the DCI schedules multiple PxSCHs, a mapping between multiple PxSCHs and multiple HARQ process IDs is required. An alternative approach is to include multiple HARQ process IDs into the DCI that schedules multiple PxSCHs, which provides greater flexibility at the expense of increased DCI size.

[0157] Another option is that the DCI contains fewer HARQ process ID fields than scheduled PxSCHs, in the extreme case one. In this case, fewer HARQ process IDs are used to obtain the HARQ process IDs for all scheduled PxSCHs. This could, for example, be that the signaled HARQ process IDs together with the number of scheduled PxSCHs define a (contiguous or non-contiguous) series of HARQ process IDs, e.g., where signaled_HARQ_ID=n and nbr_scheduled_PDSCH=4, the four scheduled PxSCHs are associated with HARQ process IDs n, n+1, n+2, n+3. If the HARQ process IDs exceed the number of specified / configured HARQ processes, the HARQ processes wrap around, e.g., n+3→mod(n+3,nbr_HARQ_processes). The four HARQ processes are associated with the four scheduled PxSCHs in a unique mapping, e.g., (1 st PxSCH,2 nd PxSCH,3 rd PxSCH,4thPxSCH)→(HARQ ID n,n+1,n+2,n+3).

[0158] In another embodiment, the signaled HARQ process ID and the number of scheduled PxSCHs together with the time slot number of the scheduled PxSCH determine the HARQ process ID. For example, the wireless device 22 is scheduled with PxSCH in time slots k1, k2, k3 and k4 and signaled with signaled_HARQ_ID=n, time slot k i The HARQ process ID for PxSCH is mod(k i + n, N), where N is a parameter to ensure that the HARQ process ID remains within the configured / specified number of HARQ processes, e.g., N = nbr_HARQ_processes.

[0159] New Data Indicator Section

[0160] In one or more embodiments, the new data indicator portion may be applicable to both DL and UL transmissions.

[0161] In existing systems, in the DL, the DCI may contain a New Data Indicator (NDI) field that indicates to the wireless device 22 whether the received TB is a new TB or a retransmission of a TB (associated with the indicated HARQ process ID). In one or more embodiments, the NDI is one bit, or two bits in the case of MIMO with two transport blocks, one bit per TB. In the UL, the NDI indicates whether the wireless device 22 should send a retransmission of a previous TB (associated with the indicated HARQ process ID) or a new TB.

[0162] If the DCI contains only a single (or in the case of MIMO, two) NDI bit, the same NDI bit is applied to multiple TBs. An alternative approach is to introduce multiple NDI bits in the multi-PxSCHDCI, one NDI bit for one TB (or at least one NDI bit for a group of TBs). In the DL, it can be beneficial to align the NDI configuration with the HARQ bundling configuration, for example, when the wireless device 22 (such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the control information unit 34, etc.) is configured to bundle HARQ feedback for TB1 and TB2 (or PDSCH1 and PDSCH2), a single NDI value for TB1 and TB2 (PDSCH1 and PDSCH2) can be used.

[0163] For example, during the first transmission and the subsequent transmission, the TB may always be associated with the same HARQ ID. The wireless device 22 (such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the control information unit 34, etc.) (and the network node 16) may soft combine information contained in different PDSCHs (PUSCHs) of the same HARQ process. If the network node 16 (such as via one or more of the processing circuit 68, the processor 70, the radio interface 62, the configuration unit 32, etc.) sends a retransmission, but indicates a different HARQ process ID than in the initial transmission, the wireless device 22 (such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the control information unit 34, etc.) may soft combine the retransmission with the content currently stored in the HARQ process ID associated with the initial transmission. However, in one or more embodiments, if the NDI is switched and indicates new data, soft combining may not occur.

[0164] Thus, one or more embodiments provide HARQ processing for single DCI multi-slot scheduling. The components and / or processes may be related to and / or include one or more of the following:

[0165] -PUCCH resources

[0166] -HARQ codebook

[0167] -HARQ process ID

[0168] -New Data Index (NDI)

[0169] Some examples

[0170] Example A1. A network node 16 configured to communicate with a wireless device 22 (WD 22), the network node 16 being configured to and / or including a radio interface 62 and / or a processing circuit 68 configured to:

[0171] configuring downlink control information (DCI), the DCI configured to schedule a plurality of transport blocks over a plurality of communication time slots, the scheduling being associated with at least one hybrid automatic repeat request (HARQ) instance; and

[0172] Transmitting this DCI is optional.

[0173] Example A2. The network node 16 of Example A1, wherein the plurality of communication time slots are scheduled on the same time-frequency resources of the physical shared channel.

[0174] Example A3. The network node 16 of Example A1, wherein a plurality of communication time slots are used to provide a physical downlink shared channel.

[0175] Example A4. The network node 16 of Example A1, wherein the at least one HARQ instance corresponds to a plurality of HARQ instances, the plurality of HARQ instances being transmitted using a same HARQ codebook.

[0176] Example A5. The network node 16 of Example A1, wherein the HARQ instance is associated with a new data indicator (NDI) bit applied to the plurality of transport blocks.

[0177] Example B1. A method implemented in a network node 16, the method comprising:

[0178] configuring downlink control information (DCI), the DCI configured to schedule a plurality of transport blocks over a plurality of communication time slots, the scheduling being associated with at least one hybrid automatic repeat request (HARQ) instance; and

[0179] Transmitting this DCI is optional.

[0180] Example B2. The method of Example B1, wherein the plurality of communication time slots are scheduled on the same time-frequency resources of the physical shared channel.

[0181] Example B3. The method of Example B1, wherein a plurality of communication time slots are used to provide a physical downlink shared channel.

[0182] Example B4. The method of Example B1, wherein the at least one HARQ instance corresponds to multiple HARQ instances, and the multiple HARQ instances are sent using the same HARQ codebook.

[0183] Example B5. The method of Example B1, wherein the HARQ instance is associated with a new data indicator (NDI) bit applied to multiple transport blocks.

[0184] Example C1. A wireless device 22 (WD 22) configured to communicate with a network node 16, the WD 22 being configured to and / or including a radio interface 82 and / or a processing circuit 84 configured to:

[0185] Downlink control information (DCI) is received, the DCI being configured to schedule a plurality of transport blocks over a plurality of communication time slots, the scheduling being associated with at least one hybrid automatic repeat request (HARQ) instance.

[0186] Example C2. WD 22 of Example C1, wherein the plurality of communication time slots are scheduled on the same time-frequency resources of the physical shared channel.

[0187] Example C3. WD 22 of Example C1, wherein a plurality of communication time slots are used to provide a physical downlink shared channel.

[0188] Example C4. WD 22 of Example C1, wherein the at least one HARQ instance corresponds to a plurality of HARQ instances, the plurality of HARQ instances being transmitted using a same HARQ codebook.

[0189] Example C5. WD 22 of Example C1, wherein the HARQ instance is associated with a new data indicator (NDI) bit applied to the plurality of transport blocks.

[0190] Example D1. A method implemented in a wireless device 22 (WD 22), the method comprising:

[0191] Downlink control information (DCI) is received, the DCI being configured to schedule a plurality of transport blocks over a plurality of communication time slots, the scheduling being associated with at least one hybrid automatic repeat request (HARQ) instance.

[0192] Example D2. The method of Example D1, wherein the plurality of communication time slots are scheduled on the same time-frequency resources of the physical shared channel.

[0193] Example D3. The method of Example D1, wherein a plurality of communication time slots are used to provide a physical downlink shared channel.

[0194] Example D4. The method of Example D1, wherein at least one HARQ instance corresponds to multiple HARQ instances, and the multiple HARQ instances are sent using the same HARQ codebook.

[0195] Example D5. The method of Example D1, wherein the HARQ instance is associated with a new data indicator (NDI) bit applied to multiple transport blocks.

[0196] As will be appreciated by those skilled in the art, the concepts described herein may be implemented as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Therefore, the concepts described herein may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware, all of which are generally referred to herein as "circuit" or "module". Any process, step, action, and / or function described herein may be performed and / or associated with a corresponding module, wherein the corresponding module may be implemented in software and / or firmware and / or hardware. In addition, the present disclosure may take the form of a computer program product on a tangible computer-usable storage medium having a computer program code that is embodied in the medium and can be executed by a computer. Any suitable tangible computer-readable medium may be used, including a hard disk, a CD-ROM, an electronic storage device, an optical storage device, or a magnetic storage device.

[0197] Some embodiments are described herein with reference to the flowcharts and / or block diagrams of methods, systems, and computer program products. It will be understood that each frame of the flowchart illustration and / or block diagram, and the combination of frames in the flowchart illustration and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer (thereby creating a special-purpose computer), a special-purpose computer, or other programmable data processing device to produce a machine, so that the instructions are created when executed via the processor of the computer or other programmable data processing device to implement the components of the function / action specified in the frame of the flowchart and / or block diagram.

[0198] These computer program instructions may also be stored in a computer-readable memory or storage medium, which can direct a computer or other programmable data processing device to work in a specific manner so that the instructions stored in the computer-readable memory produce a product including instruction components for implementing the functions / actions specified in the boxes of the flowchart and / or block diagram.

[0199] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus so that a series of operational steps are performed on the computer or other programmable apparatus to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable apparatus provide steps for implementing the functions / actions specified in the blocks of the flowchart and / or block diagram.

[0200] It should be understood that the functions / actions indicated in the blocks may not occur in the order indicated in the operational diagram. For example, two blocks shown in succession may actually be performed substantially simultaneously, or may sometimes be performed in the reverse order, depending on the functions / actions involved. Although some schematic diagrams include arrows on the communication paths to illustrate the primary direction of communication, it should be understood that communication may occur in the direction opposite to the arrows shown.

[0201] You can use methods such as The computer program code for the operation of the concept described herein can be written in an object-oriented programming language such as C++ or C++ instructions. However, the computer program code for the operation of the present disclosure can also be written in a conventional program programming language such as "C" programming language. The program code can be executed completely on the user's computer, partly on the user's computer, as an independent software package, partly on the user's computer and partly on a remote computer, or completely on a remote computer. In the latter scenario, the remote computer can be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, using an Internet service provider to establish a connection through the Internet).

[0202] Many different embodiments have been disclosed herein in conjunction with the above description and accompanying drawings. It will be understood that it would be unduly repetitive and confusing to describe and illustrate each and every combination and sub-combination of these embodiments one by one. Therefore, all embodiments may be combined in any manner and / or combination, and this specification (including the accompanying drawings) should be construed as constituting a complete written description of all combinations and sub-combinations of the embodiments described herein, as well as the manner and process of making and using them, and will support the claim for protection of any such combination or sub-combination.

[0203] Abbreviations that may be used in the preceding description include:

[0204] 3GPP Third Generation Partnership Project

[0205] 5G Fifth Generation

[0206] BB Baseband

[0207] BW Bandwidth

[0208] C-DRX / CDRX Connected mode DRX (i.e., DRX in RRC_CONNECTED state)

[0209] CRC Cyclic Redundancy Check

[0210] DCI Downlink Control Information

[0211] DL Downlink

[0212] DRX Discontinuous Reception

[0213] gNB Radio Base Station in 5G / NR

[0214] GTS goes to sleep

[0215] HARQ Hybrid Automatic Repeat Request

[0216] IoT

[0217] LO Local Oscillator

[0218] LTE Long Term Evolution

[0219] MAC Media Access Control

[0220] MCS Modulation and Coding Scheme

[0221] mMTC Massive MTC (refers to scenarios with widely deployed MTC devices)

[0222] ms milliseconds

[0223] MTC Machine Type Communication

[0224] NB Narrowband

[0225] NB-IoT Narrowband Internet of Things

[0226] NR New Radio

[0227] NW Network

[0228] PDCCH Physical Downlink Control Channel

[0229] PDSCH Physical Downlink Shared Channel

[0230] RF

[0231] RNTI Radio Network Temporary Identifier

[0232] RRC Radio Resource Control

[0233] RX Receiver / Receiver

[0234] SSB Synchronous Signal Block

[0235] T / F Time / Frequency

[0236] TX Transmitter / Send

[0237] UE User Equipment

[0238] UL Uplink

[0239] WU Wake Up

[0240] WUG Wake-up Group

[0241] WUR Wake-up Radio / Wake-up Receiver

[0242] WUS wake-up signal / wake-up signaling

[0243] Those skilled in the art will appreciate that the embodiments described herein are not limited to those embodiments that have been specifically shown and described above. In addition, unless otherwise mentioned above, it should be noted that all drawings are not drawn to scale. In view of the above teachings, various modifications and variations may be made without departing from the scope of the appended claims.

Claims

1. A network node (16), comprising a processing circuit (68), the processing circuit being configured to: The method causes downlink control information DCI to be sent to a wireless device (22), wherein the DCI includes information for scheduling two or more transport blocks TB on two or more communication time slots, wherein the two or more TBs are associated with two or more hybrid automatic repeat request HARQ process identifiers IDs and correspond to two or more PUSCHs, and the information for scheduling includes at least a HARQ process ID indicator, wherein the HARQ process ID indicator indicates the two or more HARQ process IDs, wherein: The HARQ process ID indicator is used to obtain two or more HARQ process IDs for two or more scheduled PUSCHs; as well as Based at least in part on the DCI, the two or more TBs are used for communication.

2. The network node (16) according to claim 1, wherein: The information used for scheduling further includes: a PUCCH resource indicator configured to indicate at least one resource used by the wireless device (22) to send HARQ feedback related to the two or more TBs; a downlink allocation indicator DAI configured to indicate a HARQ feedback position associated with the two or more TBs in a HARQ codebook; and One or more new data indicators NDI are configured to indicate whether at least one TB among the two or more TBs is a retransmission.

3. The network node (16) according to claim 2, wherein: The PUCCH resource indicator includes one or more K1 values.

4. The network node (16) according to any one of claims 1 to 3, wherein: The two or more communication time slots are scheduled on corresponding time-frequency resources.

5. The network node (16) according to claim 2, wherein: The HARQ feedback position associated with the two or more TBs in the HARQ codebook is further based at least in part on a number of the two or more communication time slots.

6. The network node (16) according to claim 2, wherein: The value of the DAI indicates a HARQ feedback position for one of the two or more TBs, and another HARQ feedback position for a second TB of the two or more TBs is indicated based at least in part on the value of the DAI.

7. A method in a network node (16), comprising: (S138) sending downlink control information DCI to the wireless device (22), the DCI including information for scheduling two or more transport blocks TB on two or more communication time slots, the two or more TBs being associated with two or more hybrid automatic repeat request HARQ process identifiers ID and corresponding to two or more PUSCHs, the information for scheduling including at least a HARQ process ID indicator, the HARQ process ID indicator indicating the two or more HARQ process IDs, wherein the HARQ process ID indicator is used to obtain two or more HARQ process IDs for two or more scheduled PUSCHs; and Based at least in part on the DCI, the two or more TBs are used for communication (S140).

8. The method according to claim 7, wherein: The information used for scheduling further includes: a PUCCH resource indicator configured to indicate at least one resource used by the wireless device (22) to send HARQ feedback related to the two or more TBs; a downlink allocation indicator DAI configured to indicate a HARQ feedback position associated with the two or more TBs in a HARQ codebook; and One or more new data indicators NDI are configured to indicate whether at least one TB among the two or more TBs is a retransmission.

9. The method according to claim 8, wherein: The PUCCH resource indicator includes one or more K1 values.

10. The method according to any one of claims 7 to 9, wherein: The two or more communication time slots are scheduled on corresponding time-frequency resources.

11. The method according to claim 8, wherein: The HARQ feedback position associated with the two or more TBs in the HARQ codebook is further based at least in part on a number of the two or more communication time slots.

12. The method according to claim 8, wherein: The value of the DAI indicates a HARQ feedback position for one of the two or more TBs, and another HARQ feedback position for a second TB of the two or more TBs is indicated based at least in part on the value of the DAI.

13. A wireless device (22) comprising a processing circuit (84) configured to: receiving downlink control information DCI, the DCI comprising information for scheduling two or more transport blocks TB on two or more communication time slots, the two or more TBs being associated with two or more hybrid automatic repeat request HARQ process identifiers IDs and corresponding to two or more PUSCHs, the information for scheduling comprising at least a HARQ process ID indicator, the HARQ process ID indicator indicating the two or more HARQ process IDs, wherein, The HARQ process ID indicator is used to obtain two or more HARQ process IDs for two or more scheduled PUSCHs; as well as Based at least in part on the DCI, the two or more TBs are used for communication.

14. The wireless device (22) of claim 13, wherein: The information used for scheduling further includes: a PUCCH resource indicator configured to indicate at least one resource used by the wireless device (22) to send HARQ feedback related to the two or more TBs; a downlink allocation indicator DAI configured to indicate a HARQ feedback position associated with the two or more TBs in a HARQ codebook; and One or more new data indicators NDI are configured to indicate whether at least one TB among the two or more TBs is a retransmission.

15. The wireless device (22) of claim 14, wherein: The PUCCH resource indicator includes one or more K1 values.

16. The wireless device (22) according to any one of claims 13 to 15, wherein: The two or more communication time slots are scheduled on corresponding time-frequency resources.

17. The wireless device (22) of claim 14, wherein: The HARQ feedback position associated with the two or more TBs in the HARQ codebook is further based at least in part on a number of the two or more communication time slots.

18. The wireless device (22) of claim 14, wherein: The value of the DAI indicates a HARQ feedback position for one of the two or more TBs, and another HARQ feedback position for a second TB of the two or more TBs is indicated based at least in part on the value of the DAI.

19. The wireless device (22) according to any one of claims 13 to 15, wherein: The HARQ process ID indicator is based at least in part on a number of physical shared channel transmissions used in the two or more communication time slots.

20. A method implemented by a wireless device (22), the method comprising: receiving (S144) downlink control information DCI, the DCI comprising information for scheduling two or more transport blocks TB on two or more communication time slots, the two or more TBs being associated with two or more hybrid automatic repeat request HARQ process identifiers ID and corresponding to two or more PUSCHs, the information for scheduling comprising at least a HARQ process ID indicator, the HARQ process ID indicator indicating the two or more HARQ process IDs, wherein the HARQ process ID indicator is used to obtain two or more HARQ process IDs for two or more scheduled PUSCHs; and Based at least in part on the DCI, the two or more TBs are used for communication (S146).

21. The method according to claim 20, wherein: The information used for scheduling further includes: a PUCCH resource indicator configured to indicate at least one resource used by the wireless device (22) to send HARQ feedback related to the two or more TBs; a downlink allocation indicator DAI configured to indicate a HARQ feedback position associated with the two or more TBs in a HARQ codebook; and One or more new data indicators NDI are configured to indicate whether at least one TB among the two or more TBs is a retransmission.

22. The method according to claim 21, wherein: The PUCCH resource indicator includes one or more K1 values.

23. The method according to any one of claims 20 to 22, wherein: The two or more communication time slots are scheduled on corresponding time-frequency resources.

24. The method according to claim 21, wherein: The HARQ feedback position associated with the two or more TBs in the HARQ codebook is further based at least in part on a number of the two or more communication time slots.

25. The method according to claim 21, wherein: The value of the DAI indicates a HARQ feedback position for one of the two or more TBs, and another HARQ feedback position for a second TB of the two or more TBs is indicated based at least in part on the value of the DAI.

26. The method according to any one of claims 20 to 22, wherein: The HARQ process ID indicator is based at least in part on a number of physical shared channel transmissions used in the two or more communication time slots.

Images