Non-terrestrial network feedback disabling via downlink control information

Abstract

Methods and apparatus for NTN feedback disabling via downlink control information are disclosed. A UE comprises: a processor; and a transceiver coupled to the processor, where the processor is configured to cause the UE to receive a control message scheduling a set of transport blocks, where the set of transport blocks includes one or more transport blocks, the control message including a first field indicating whether hybrid automatic repeat request (HARQ) feedback is enabled or disabled for the set of transport blocks, the first field also indicates a modulation coding scheme (MCS) index, a resource associated with HARQ feedback, a HARQ process number, a new data indicator (NDI), or any combination thereof; and receive a set of transport blocks based at least in part on the received control message.

Description

Technical Field

[0001] The subject matter disclosed herein relates generally to wireless communications, and more particularly to methods and apparatus for NTN (Non-Terrestrial Network) feedback disabling via downlink control information. Background Art

[0002] The following abbreviations are defined herein, at least some of which are referred to in the following description: New Radio (NR), Very Large Scale Integration (VLSI), Random Access Memory (RAM), Read Only Memory (ROM), Erasable Programmable Read Only Memory (EPROM or Flash), Compact Disc Read Only Memory (CD-ROM), Local Area Network (LAN), Wide Area Network (WAN), User Equipment (UE), Evolved Node B (eNB), Next Generation Node B (gNB), Uplink (UL), Downlink (DL), Central Processing Unit (CPU), Graphics Processing Unit (GPU), Field Programmable Gate Array (FPGA), Orthogonal Frequency Division Multiplexing (OFDM), Radio Resource Control (RRC), Use User entity / equipment (mobile terminal), transmitter (TX), receiver (RX), non-terrestrial network (NTN), Internet of Things (IoT), machine type communication (MTC), enhanced MTC (eMTC), transport block (TB), physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), positive acknowledgement (ACK), negative acknowledgement (NACK), automatic repeat request (ARQ), hybrid automatic repeat request (HARQ), physical downlink shared channel (PDSCH), narrowband Internet of Things (NBIoT or NB-IoT), downlink control information (DCI), modulation and coding scheme (MCS), frequency division duplex (FDD), MTC PDCCH (MPDCCH), physical resource block (PRB), enhanced control channel element (ECCE), coverage enhancement (CE), most significant bit (MSB), least significant bit (LSB).

[0003] For the downlink data transmission process, the data signal is sent in units of transport blocks (TBs). A TB is repeatedly sent in one or more subframes. Subsequently, feedback (ACK or NACK) of the data signal is sent in an uplink feedback channel (e.g., PUCCH or PUSCH) to indicate whether the corresponding data signal is correctly received (i.e., ACK) or not correctly received (i.e., NACK) on the UE side. Each downlink data transmission process is associated with a process number. The feedback of the data signal is associated with the process number so that the base station unit (e.g., eNB) knows which TB (or which subframe) the feedback is associated with. The process number may also be referred to as the HARQ process number.

[0004] Disabling of HARQ feedback is already supported in NR NTN. Specifically, enabling and disabling of HARQ feedback for downlink transmissions (e.g., PDSCH transmissions) can be configured for each HARQ process at least via UE-specific RRC signaling. For example, the UE can be configured via RRC parameters to enable or disable HARQ feedback for each HARQ process (i.e., each HARQ process number) via a bitmap. Figure 1 As shown, assuming there are 8 HARQ processes (eg, HARQ processes are numbered #0 to #7), a bitmap with 8 bits can indicate HARQ feedback enablement or disablement of the 8 HARQ processes. For example, 0 indicates HARQ feedback disablement, and 1 indicates HARQ feedback enablement.

[0005] When HARQ feedback disabling is configured for a HARQ process number (or HARQ process), there is no explicit UL feedback confirmation of DL transmission for the successful transmission of the TB associated with the HARQ process with the HARQ process number. This means that the HARQ process number can be reused for new DL transmissions without waiting for HARQ feedback. This can avoid HARQ stagnation and therefore avoid throughput degradation. Correspondingly, retransmissions at the RLC layer (i.e., RLC ARQ) may be required to meet reliability requirements. Typically, ARQ retransmissions in the RLC layer can have high latency, which may be acceptable for IoT services (such as eMTC and NBIoT) because IoT services typically have delay tolerance.

[0006] In NR NTN, in order to ensure the efficiency and reliability of transmissions carrying certain critical signaling (such as RRC configuration), at least one HARQ process with feedback enabled should be reserved. For eMTC with limited HARQ processes, if the NR NTN HARQ feedback enabled or disabled for each HARQ process configured by RRC parameters is reused, it is difficult to guarantee at least one HARQ process with feedback enabled because the RRC reconfiguration will result in large signaling overhead.

[0007] The present invention is directed to a technical solution for NTN feedback disabling via downlink control information. Summary of the invention

[0008] Methods and apparatus for NTN feedback disabling via downlink control information are disclosed.

[0009] In one embodiment, a UE includes: a processor; and a transceiver coupled to the processor, wherein the processor is configured to cause the UE to: receive a control message that schedules a transport block set, wherein the transport block set includes one or more transport blocks, the control message includes a first field, the first field indicates whether hybrid automatic repeat request (HARQ) feedback is enabled or disabled for the transport block set, and the first field also indicates a modulation and coding scheme (MCS) index, resources associated with the HARQ feedback, a HARQ process number, a new data indicator (NDI), or any combination thereof; and receive the transport block set based at least in part on the received control message.

[0010] In some embodiments, the control message includes a second field; the first field also indicates an MCS index or an MCS set; and the second field indicates a resource associated with HARQ feedback, or an MCS sub-index within the MCS set, or any combination thereof.

[0011] In some embodiments, the control message also includes a second field; and the first field also indicates an MCS index, or a HARQ process number and NDI; and the second field indicates resources associated with the HARQ feedback, a HARQ process number and NDI, or indicates an MCS index.

[0012] In some embodiments, the first field includes a plurality of subfields, at least one of the plurality of subfields indicating whether HARQ feedback is enabled or disabled; the at least one subfield is based at least in part on the number of transport blocks in the transport block set.

[0013] In some embodiments, the resources associated with the HARQ feedback are based at least in part on the HARQ process number or the subframe number, or both.

[0014] In some embodiments, the processor is further configured to receive a radio resource control (RRC) message indicating whether HARQ feedback is enabled or disabled; the enabled or disabled HARQ feedback associated with the transport block set indicated by the first field overrides the enabled or disabled HARQ feedback indicated by the RRC message.

[0015] In some embodiments, the processor is further configured to receive a radio resource control (RRC) message indicating whether HARQ feedback is enabled or disabled; the first field indicates whether HARQ feedback is enabled or disabled by indicating whether to override or maintain the enabled or disabled HARQ feedback indicated by the RRC message.

[0016] This means that in order to enable or disable HARQ feedback based at least in part on an RRC message, the method includes overriding the enabling or disabling of HARQ feedback associated with a first field indicating whether HARQ feedback is enabled or disabled for a transport block set based on the RRC message; or maintaining the enabling or disabling of HARQ feedback associated with the first field indicating whether HARQ feedback is enabled or disabled for a transport block set.

[0017] In one embodiment, a method at a UE includes receiving a control message that schedules a transport block set, wherein the transport block set includes one or more transport blocks, the control message includes a first field that indicates whether hybrid automatic repeat request (HARQ) feedback is enabled or disabled for the transport block set, and the first field also indicates a modulation and coding scheme (MCS) index, resources associated with the HARQ feedback, a HARQ process number, a new data indicator (NDI), or any combination thereof; and receiving the transport block set based at least in part on the received control message.

[0018] In another embodiment, a network entity includes: a processor; and a transceiver coupled to the processor, wherein the processor is configured to cause the network entity to: send a control message that schedules a transport block set, wherein the transport block set includes one or more transport blocks, the control message includes a first field, the first field indicates whether hybrid automatic repeat request (HARQ) feedback is enabled or disabled for the transport block set, and the first field also indicates a modulation and coding scheme (MCS) index, resources associated with the HARQ feedback, a HARQ process number, a new data indicator (NDI), or any combination thereof; and send the transport block set based at least in part on the received control message.

[0019] In another embodiment, a method at a network entity (e.g., a base unit) includes sending a control message for scheduling a transport block set, wherein the transport block set includes one or more transport blocks, the control message includes a first field, the first field indicates whether hybrid automatic repeat request (HARQ) feedback is enabled or disabled for the transport block set, and the first field also indicates a modulation and coding scheme (MCS) index, resources associated with the HARQ feedback, a HARQ process number, a new data indicator (NDI), or any combination thereof; and sending the transport block set based at least in part on the received control message. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The embodiments briefly described above will be described in more detail with reference to specific embodiments illustrated in the accompanying drawings. Understanding that these drawings depict only some embodiments and are therefore not to be considered limiting in scope, these embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0021] Figure 1illustrates the NR NTN HARQ feedback disable indication;

[0022] Figure 2 The structure of the "Scheduled TB for Unicast" field is illustrated;

[0023] Figure 3 is a schematic flow chart illustrating an embodiment of a method;

[0024] Figure 4 is a schematic flow chart illustrating another embodiment of a method; and

[0025] Figure 5 is a schematic block diagram illustrating an apparatus according to one embodiment. DETAILED DESCRIPTION

[0026] As will be appreciated by those skilled in the art, certain aspects of the embodiments may be embodied as systems, devices, methods or program products. Therefore, the embodiments may take the form of a complete hardware embodiment, a complete software embodiment (including firmware, resident software, microcode, etc.) or an embodiment combining software and hardware aspects, which are generally referred to herein as "circuit", "module" or "system". In addition, the embodiments may take the form of a program product embodied in one or more computer-readable storage devices, which store machine-readable code, computer-readable code and / or program code (hereinafter referred to as "code"). The storage device may be tangible, non-transient and / or non-transmissive. The storage device may not embody a signal. In a certain embodiment, the storage device only uses a signal for accessing the code.

[0027] Certain functional units described in this specification may be labeled as "modules" to more specifically emphasize their independent implementation. For example, a module may be implemented as a hardware circuit, including a custom very large scale integrated circuit (VLSI) circuit or gate array, an off-the-shelf semiconductor (e.g., a logic chip, a transistor, or other discrete component). A module may also be implemented in a programmable hardware device such as a field programmable gate array, a programmable array logic, a programmable logic device, etc.

[0028] Modules may also be implemented in code and / or software for execution by various types of processors. The identified code modules may, for example, include one or more physical or logical executable code blocks, which may, for example, be organized as objects, processes, or functions. Nevertheless, the executable files of the identified modules need not be physically located together, but may include different instructions stored in different locations, which, when logically combined together, comprise the module and achieve the stated purpose of the module.

[0029] In fact, a code module may include a single instruction or multiple instructions, and may even be distributed across several different code segments, different programs, and across several storage devices. Similarly, operational data may be identified and described in this article within a module, and may be embodied in any suitable form and organized in a data structure of any suitable type. The operational data may be collected as a single data set, or may be distributed in different locations, including different computer-readable storage devices. When a module or a portion of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0030] Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example but not necessarily, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system, apparatus or device, or any suitable combination of the foregoing.

[0031] A non-exhaustive list of more specific examples of storage devices would include the following: an electrical connection having one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0032] The code for performing the operations of the embodiments may include any number of lines and may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, etc., as well as conventional procedural programming languages ​​such as the "C" programming language, etc., and / or machine languages ​​such as assembly language. The code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer, partially on the user's computer, partially on a remote computer, or entirely on a remote computer or server. In the last scenario, the remote computer may be connected to the user's computer via any type of network including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0033] Throughout the specification, references to "one embodiment," "an embodiment," or similar language mean that a particular feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment. Therefore, the phrases "in one embodiment," "in an embodiment," and similar language appearing throughout the specification may, but do not necessarily, refer to the same embodiment, but rather mean "one or more but not all embodiments," unless expressly provided otherwise. The terms "include," "comprising," "having," and variations thereof mean "including but not limited to," unless expressly provided otherwise. Unless expressly provided otherwise, an enumerated list of items does not mean that any or all items are mutually exclusive. Unless expressly provided otherwise, the terms "a," "an," and "the" also refer to "one or more."

[0034] In addition, the described features, structures or characteristics of the various embodiments may be combined in any suitable manner. In the following description, many specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, those skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific details, or may be practiced using other methods, components, materials, etc. In other cases, well-known structures, materials, or operations are not shown or described in detail to avoid obfuscating any aspect of the embodiments.

[0035] Aspects of different embodiments are described below with reference to schematic flow charts and / or schematic block diagrams of methods, devices, systems, and program products according to embodiments. It will be understood that each box in the schematic flow chart and / or schematic block diagram and the combination of boxes in the schematic flow chart and / or schematic block diagram can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to generate a machine, so that instructions executed by the processor of the computer or other programmable data processing device create means for implementing the functions of the boxes specified in the schematic flow chart and / or schematic block diagram.

[0036] The code may also be stored in a storage device capable of instructing a computer, other programmable data processing device, or other device to operate in a specific manner, so that the instructions stored in the storage device produce an article of manufacture, which includes instructions for implementing the functions specified in the schematic flowchart and / or one or more schematic block diagrams.

[0037] The code may also be loaded onto a computer, other programmable data processing device, or other device so that a series of operational steps are executed on the computer, other programmable device, or other device to produce a computer-implemented process, such that the code executed on the computer or other programmable device provides a process for implementing the functions specified in the flowchart and / or one or more block diagrams.

[0038] The schematic flow charts and / or schematic block diagrams in the figures illustrate the possible implementation architectures, functions and operations of the devices, systems, methods and program products according to various embodiments. In this regard, each box in the schematic flow charts and / or schematic block diagrams may represent a module, a segment or a part of code, which includes one or more executable instructions for implementing the code of the specified logical function.

[0039] It should also be noted that in some alternative implementations, the functions indicated in the blocks may be in a different order than indicated in the figures. For example, two blocks shown in succession may be executed substantially simultaneously, or the blocks may sometimes be executed in a reverse order, depending on the functions involved. Other steps and methods are contemplated that are equivalent in function, logic, or effect to one or more blocks or portions thereof in the figures shown.

[0040] Although various arrow types and line types can be used in flow charts and / or block diagrams, it should be understood that they do not limit the scope of the corresponding embodiments. In fact, some arrows or other connectors can be used to indicate only the logical flow of the depicted embodiments. For example, an arrow can indicate a waiting or monitoring period of unspecified duration between the enumeration steps of the depicted embodiments. It should also be noted that each frame of the block diagram and / or flow chart and the combination of frames in the block diagram and / or flow chart can be implemented by a special hardware system or a combination of special hardware and code that performs a specified function or action.

[0041] The description of the elements in each figure may refer to the elements in the previous figures. In all figures, the same reference numerals refer to the same elements, including alternative embodiments of the same elements.

[0042] eMTC CE Mode B supports 2 HARQ processes or 4 HARQ processes (if multiple TB scheduling is configured). This means that for eMTC, a control message (e.g., control signal, DCI format 6-1B) can schedule a transport block set, which can be one transport block for a single transport block transmission, or up to four (4) transport blocks for multiple transport block transmissions, where each transport block is associated with a different HARQ process (i.e., a HARQ process with a different HARQ process number). Each HARQ process can be HARQ feedback enabled by default.

[0043] According to the present disclosure, a control message (e.g., DCI format 6-1B) can indicate whether hybrid automatic repeat request (HARQ) feedback is enabled or disabled. The indication of whether HARQ feedback is enabled or disabled can be applied to a HARQ process associated with a single scheduled transport block or to all HARQ processes associated with a transport block set.

[0044] It is simple to add a field to DCI format 6-1B to indicate whether Hybrid Automatic Repeat Request (HARQ) feedback is enabled or disabled. However, the added field is not ideal considering the added overhead.

[0045] In view of the above, the present disclosure proposes several embodiments to indicate HARQ feedback enablement or disablement associated with a scheduled transport block without adding a field to the scheduling DCI (eg, DCI format 6-1B) or adding any additional bits to the scheduling DCI.

[0046] Some relevant fields of DCI format 6-1B are shown in Table 1.

[0047] DCI format 6-1B field Number of digits Modulation and Coding Scheme (MCS) 4 HARQ process number 1 New Data Indicator 1 HARQ-ACK Resource Offset 2 Unicast Scheduling TB 10

[0048] Table 1

[0049] The 'MCS' field of DCI format 6-1B has 4 bits and indicates an MCS index. For eMTC, the candidate MCS index indicated by the 'MCS' field can be from 0 to 9 (ie, from '0000' to '1001'). This means that there are six (6) unused states of the 'MCS' field (eg, from 10 to 15, ie, from '1010' to '1111').

[0050] The 'HARQ process number' field indicates the HARQ process number.

[0051] The 'New Data Indicator' field indicates a new data indicator.

[0052] The 'HARQ-ACK Resource Offset' field indicates resources associated with HARQ feedback (eg, HARQ-ACK resources) of a transport block set. If HARQ feedback disabling is indicated, there is no need to indicate the HARQ-ACK resources of a transport block set.

[0053] The "Scheduled TB for unicast" field has 10 bits. The "Scheduled TB for unicast" field exists only for multi-TB scheduling.

[0054] According to the first embodiment, HARQ feedback enabling or disabling associated with a scheduled downlink transmission (ie, a scheduled TB) is indicated by a first field (eg, a joint field) having 6 bits.

[0055] The joint field can be a new field used to replace some existing (ie, traditional) fields of DCI format 6-1B. For example, the traditional "MCS" field (with 4 bits) and the traditional "HARQ-ACK resource offset" field (with 2 bits) can be replaced by the joint field. This means that when the HARQ disable function is configured, the new field (ie, the joint field) exists in DCI format 6-1B, while the traditional "MCS" field and the traditional "HARQ-ACK resource offset" field do not exist in DCI format 6-1B. Alternatively, the joint field can be composed of some existing fields of DCI format 6-1B. For example, the joint field consists of a traditional "MCS" field (with 4 bits) and a traditional "HARQ-ACK resource offset" field (with 2 bits). Specifically, the traditional "MCS" field can be used as the four most significant bits of the joint field, and the traditional "HARQ-ACK resource offset" field is used as the two least significant bits of the joint field.

[0056] According to the first embodiment, the joint field indicates HARQ feedback enablement or disablement associated with the scheduled downlink transmission in addition to the traditional indication. For example, if the joint field replaces the traditional 'MCS' field (having 4 bits) and the traditional 'HARQ-ACK resource offset' field (having 2 bits) (or alternatively, the traditional 'MCS' field (having 4 bits) and the traditional 'HARQ-ACK resource offset' field (having 2 bits) constitute the joint field), then the joint field indicates HARQ feedback enablement or disablement associated with the scheduled downlink transmission in addition to the MCS index and the HARQ-ACK resource.

[0057] The conventional 'HARQ-ACK Resource Offset' field (having 2 bits) indicates HARQ-ACK resources through 4 candidate values ​​(eg, '00', '01', '10', and '11').

[0058] The conventional 'MCS' field (having 4 bits) indicates an MCS index from 0 to 9 (ie, from '0000' to '1001'). Possible values ​​10 to 15 (ie, from '1010' to '1111') of the 'MCS' field are unused.

[0059] The joint field has 6 bits, which is equivalent to 64 states. 50 states are sufficient to indicate HARQ feedback enablement or disablement, MCS index, and HARQ-ACK resources associated with the scheduled downlink transmission. That is, 40 (= 4 * 10) states are used for HARQ feedback enablement and indicate MCS index and HARQ-ACK resources; and 10 states are used for HARQ feedback disablement and indicate MCS index. By the way, when HARQ feedback disablement is indicated, there is no need to indicate HARQ-ACK resources.

[0060] Table 2 illustrates an example of joint fields according to the first embodiment.

[0061]

[0062] Table 2

[0063] As shown in Table 2, if the joint field indicates 0 to 9, HARQ feedback is indicated as enabled; the MCS index is from 0 to 9 (ie, equal to the joint field value), and the HARQ-ACK resource is indicated as '00'.

[0064] If the Union field indicates 10 to 19, HARQ feedback is indicated as enabled; the MCS index is from 0 to 9 (ie, equal to the Union field value minus 10), and the HARQ-ACK resource is indicated as '01'.

[0065] If the joint field indicates 20 to 29, HARQ feedback is indicated as enabled; if the MCS index is from 0 to 9 (ie, equal to the joint field value minus 20), the HARQ-ACK resource is indicated as '10'.

[0066] If the joint field indicates 30 to 39, HARQ feedback is indicated as enabled; the MCS index is from 0 to 9 (ie, equal to the joint field value minus 30), and the HARQ-ACK resource is indicated as '11'.

[0067] If the joint field indicates 40 to 49, HARQ feedback is indicated as disabled; the MCS index is from 0 to 9 (i.e., equal to the joint field value minus 40), and the HARQ-ACK resource value is reserved (indicated as "X" in Table 2). This means that when HARQ feedback is disabled, there is no need to indicate HARQ-ACK resources.

[0068] It can be seen that according to the first embodiment, the UE receives a control message (e.g., DCI format 6-1B), which includes a joint field indicating at least HARQ feedback enable or disable associated with the scheduled downlink transmission, wherein the HARQ feedback enable or disable is based on the value of the joint field.

[0069] In the example of Table 2, the joint field indicates at least one of other indications (e.g., MCS index and HARQ-ACK resource) in addition to indicating HARQ feedback enablement or disablement associated with the scheduled downlink transmission, wherein if the joint field value is from 0 to 39, HARQ feedback enablement is indicated; and if the joint field value is from 40 to 49, HARQ feedback disablement is indicated. Specifically, the values ​​of 0 to 39 of the joint field indicate 3 indications (i.e., HARQ feedback enablement or disablement associated with the scheduled downlink transmission, MCS index, and HARQ-ACK resource); and the values ​​of 40 to 49 of the joint field indicate 2 indications (i.e., HARQ feedback enablement or disablement associated with the scheduled downlink transmission, and MCS index).

[0070] According to a second embodiment, the UE receives a control message (e.g., DCI format 6-1B), the control message including two (2) fields (e.g., a first field (e.g., a first joint field) and a second field (e.g., a second joint field)), wherein the first joint field indicates an MCS index or an MCS set index in addition to indicating HARQ feedback enablement or disablement associated with a scheduled downlink transmission, and the second joint field indicates a HARQ-ACK resource or an MCS sub-index of an MCS set having the MCS set index.

[0071] An example of the second embodiment is shown in Table 3.

[0072]

[0073] Table 3

[0074] As can be seen from Table 3, if the first joint field (e.g., by reusing the traditional 'MCS' field) indicates '0000' to '1001' (i.e., from 0 to 9), the first joint field indicates that the HARQ feedback of the HARQ process associated with the scheduled downlink transmission is enabled and also indicates the MCS index. In this case, the second joint field (e.g., the traditional 'HARQ-ACK resource offset' field) indicates the HARQ-ACK resource.

[0075] If the first joint field (e.g., the conventional 'MCS' field) indicates '1010 to '1100' (i.e., from 10 to 12), the first joint field indicates HARQ feedback disabling of the HARQ process associated with the scheduled downlink transmission, and also indicates the MCS set index (e.g., MCS set 0, MCS set 1, and MCS set 2) (i.e., the MCS set is selected). In this case, the second joint field (e.g., by reusing the conventional 'HARQ-ACK resource offset' field) indicates the MCS sub-index within the selected MCS set (e.g., MCS sub-index 0, MCS sub-index 1, MCS sub-index 2, MCS sub-index 3). This means that the MCS index can be obtained in the following manner: MCS index = 4*MCS set index + MCS sub-index. If HARQ feedback disabling is indicated, there is no need to indicate HARQ-ACK resources. There are three (3) candidate MCS sets and four (4) candidate MCS sub-indexes within each MCS set. This means that the total number of candidate MCS indexes can be up to 12 (=3*4), which is sufficient to cover MCS indexes from 0 to 9. Specifically, if the first joint field indicates '1010 to '1100', the combination of the first joint field and the second joint field indicates the MCS index. For example, if the first joint field indicates '1011' (ie, MCS set index = 1), and the second joint field indicates '01' (ie, MCS sub-index = 1), then MCS index = 4*MCS set index + MCS sub-index = 4*1+1 = 5.

[0076] According to a third embodiment, a UE receives a control message (e.g., DCI format 6-1B), the control message including two (2) fields (e.g., a first field (e.g., a first joint field) and a second field (e.g., a second joint field)), wherein the first joint field indicates an MCS index, or a HARQ process number and a new data indicator, in addition to indicating HARQ feedback enablement or disablement associated with a scheduled downlink transmission, and the second joint field indicates a HARQ-ACK resource, a HARQ process number and a new data indicator, or indicates an MCS index. The third embodiment is applied to eMTC CE mode B with one TB scheduling.

[0077] An example of the third embodiment is shown in Table 4.

[0078]

[0079] Table 4

[0080] As can be seen from Table 4, if the first joint field (e.g., by reusing the conventional 'MCS' field) indicates '0000' to '1001' (i.e., from 0 to 9), the first joint field indicates that HARQ feedback associated with the scheduled downlink transmission is enabled and also indicates the MCS index. In this case, the second joint field (e.g., by reusing a combination of the conventional 'HARQ-ACK resource offset' field, the conventional 'HARQ process number' field, and the conventional 'NDI' field) indicates the HARQ-ACK resource, the HARQ process number, and the new data indicator. This means that the second joint field can be considered to be composed of 3 subfields (for example, by reusing a subfield of the traditional 'HARQ-ACK resource offset' field, which has 2 bits; by reusing a subfield of the traditional 'HARQ process number' field, which has 1 bit; by reusing a subfield of the traditional 'NDI' field, which has 1 bit), wherein the HARQ-ACK resource is indicated by reusing a subfield of the traditional 'HARQ-ACK resource offset' field, the HARQ process number is indicated by reusing a subfield of the traditional 'HARQ process number' field, and the new data indicator is indicated by reusing a subfield of the traditional 'NDI' field.

[0081] If the first joint field (e.g., by reusing the traditional 'MCS' field) indicates '1010 to '1101' (i.e., from 10 to 13), the first joint field indicates HARQ feedback disabling associated with the scheduled downlink transmission, and also indicates the HARQ process number and the new data indicator. This means that the four states '1010 to '1101' are used to indicate the HARQ process number and the new data indicator. If HARQ feedback disabling is indicated, there is no need to indicate the HARQ-ACK resource. The second joint field (e.g., by reusing a combination of the traditional "HARQ-ACK resource offset" field, the traditional "HARQ process number" field, and the traditional "NDI" field) (having a total of 4 bits) indicates the MCS index, for example, from 0 to 9. For example, the traditional "HARQ process number" field is used as the most significant bit (MSB) of the second joint field; the traditional "NDI" field is used as the second bit of the second joint field; and the traditional "HARQ-ACK resource offset" field is used as the two least significant bits (LSB) of the second joint field.

[0082] The fourth embodiment relates to eMTC CE mode B with multi-TB scheduling through DCI format 6-1B.

[0083] In multi-TB scheduling, the 'Scheduled TB for unicast' field is present in DCI format 6-1B. The 'Scheduled TB for unicast' field includes 'MCS', 'HARQ' (ie 'HARQ1', 'HARQ2 Index' and 'HARQ3') and 'NDI' (ie 'N1', 'N2', 'N3' and 'N4') subfields. Figure 2 The structure of the 'Scheduled TB for Unicast' field is shown in the figure. Figure 2 It can be seen that the meaning of each of the ten (10) bits of the 'Scheduled TB for Unicast' field is different for different numbers of transport block sets (ie, different HARQs).

[0084] For a HARQ process (in Figure 2 In the embodiment, the TB is a scheduled TB associated with one HARQ process (indicated as '1 HARQ'), bits 1, 2 and 3 are always '0'; bits 4, 5, 6 and 7 are the 'MCS' subfield, which indicates the MCS index (from 0 to 9, i.e., from '0000' to '1001'); bits 8 and 9 ('HARQ1') indicate which of the four HARQ processes is one HARQ process; and bit 10 is the subfield 'NDI' (i.e., 'N1') of one HARQ process.

[0085] For two HARQ processes (in Figure 2 2 HARQ' in the TB, bit 1 is always '0'; bits 2, 3, 4 and 5 are 'MCS' subfields (indicated as ' ... Figure 2 bits 6, 7 and 8 ('HARQ2 index') indicate which two of the four HARQ processes are the two HARQ processes; and bits 9 and 10 are subfields 'NDI' (for example, for the first HARQ process of the two HARQ processes, bit 9 is the subfield 'NDI', i.e. 'N1'; and for the second HARQ process of the two HARQ processes, bit 10 is the subfield 'NDI', i.e. 'N2').

[0086] For three HARQ processes (in Figure 2 '3 HARQ' in the TB, bits 1, 2, 3, 4 and 5 are the 'MCS' subfield (in Figure 2'MCS+15' in the subfield), which indicates the MCS index plus 15 (from 15 to 24, i.e., from '01111' to '11000'); bits 6 and 7 ("HARQ3") indicate which three of the four HARQ processes are the three HARQ processes; bits 8, 9, and 10 are the subfield 'NDI' (for example, for the first HARQ process of the three HARQ processes, bit 8 is the subfield 'NDI', i.e., 'N1'; for the second HARQ process of the three HARQ processes, bit 9 is the subfield 'NDI', i.e., 'N2'; and for the third HARQ process of the three HARQ processes, bit 10 is the subfield 'NDI', i.e., 'N3').

[0087] For four HARQ processes (in Figure 2 4 HARQ) associated with four scheduled TBs, bits 1, 2, 3, 4, 5, and 6 are "MCS" ( Figure 2 bits 7, 8, 9, and 10 are the subfield 'NDI' (for example, for the first HARQ process of the four HARQ processes, bit 7 is the subfield 'NDI', i.e., 'N1'; for the second HARQ process of the four HARQ processes, bit 8 is the subfield 'NDI', i.e., 'N2'; for the third HARQ process of the four HARQ processes, bit 9 is the subfield 'NDI', i.e., 'N3'; and for the fourth HARQ process of the four HARQ processes, bit 10 is the subfield 'NDI', i.e., 'N4').

[0088] Correspondingly, the structure of the subfield is determined by the number of scheduled TBs (from 1 to 4).

[0089] Table 5 illustrates the detailed MCS subfield values, i.e., MCS index = 0 to 9 for each of 1 HARQ, 2 HARQ, 3 HARQ and 4 HARQ, where some unused states are merged between 1 HARQ and 2 HARQ, between 2 HARQ and 3 HARQ, between 3 HARQ and 4 HARQ, and after 4 HARQ.

[0090]

[0091]

[0092] Table 5

[0093] As can be seen from Table 5, "0001010" and "0001011" (for bits 1 to 7) are two unused states between 1 HARQ and 2 HARQ. Therefore, these two unused states can be used to indicate HARQ feedback disabling associated with a scheduled downlink transmission (i.e., associated with one scheduled TB). In addition, the combination of these unused states (2 states) and the "HARQ-ACK resource offset" field (with 2 bits) (not required for HARQ-ACK resources indicating HARQ feedback disabling) can indicate the first 8 or last 8 (i.e., 2 unused states + 2 bits = 8 states) MCS indexes (i.e., MCS index = 0 to 7 or MCS index = 2 to 9) and HARQ feedback disabling. The combination of these unused states (2 states) and the traditional "HARQ-ACK resource offset" field (with 2 bits) indicates that one MCS index from the first 8 MCS indexes or one MCS index from the last 8 MCS indexes may depend on the HARQ process number or subframe number. For example, if the HARQ process number is 0 or 1, the combination of these unused states (2 states) and the traditional "HARQ-ACK resource offset" field (with 2 bits) can indicate an MCS index from the first 8 MCS indexes (i.e., MCS index = 0 to 7); and if the HARQ process number is not 0 and 1, the combination of these unused states (2 states) and the "HARQ-ACK resource offset" field (with 2 bits) can indicate an MCS index from the last 8 MCS indexes (i.e., MCS index = 2 to 9).

[0094] In general, when bits 1 to 7 of the 'Scheduled TB for Unicast' field are from '0000000' to '0001011', one TB is scheduled. If bits 1 to 7 are from '0000000' to '0001001', HARQ feedback enablement is indicated, and bits 4 to 7 also indicate an MCS index, and if bits 1 to 7 are from '0001010' to '0001011', HARQ feedback disablement is indicated, and the MCS index is indicated by a combination of '0001010' or '0001011' (for bits 1 to 7) and the 'HARQ-ACK Resource Offset' field.

[0095] For two scheduled TBs, three bits (i.e., bits 6, 7, and 8) ('HARQ Index 2') indicate which two of the four HARQ processes are associated with the two scheduled TBs. Since only 6 states of three bits (e.g., from '000' to '101') are sufficient to indicate which two of the four HARQ processes are associated with the two scheduled TBs, there are two (2) unused states (e.g., '110' and '111') in the 'HARQ2 Index' subfield. Therefore, these two unused states of the 'HARQ2 Index' subfield can be used to indicate HARQ feedback disabling associated with the scheduled downlink transmission (i.e., associated with the two scheduled TBs). In addition, the combination of these unused states (2 states) of the 'HARQ2 Index' subfield and the 'HARQ-ACK Resource Offset' field (having 2 bits) (which is unnecessary for indicating HARQ-ACK resources for HARQ feedback disabling) can indicate which two of the four HARQ processes are associated with the two scheduled TBs, and HARQ feedback disabling. Specifically, two unused states and two bits of the 'HARQ-ACK Resource Offset' field can provide eight states, which are sufficient to indicate six candidate values ​​to indicate which two of the four HARQ processes are associated with the two scheduled TBs.

[0096] In general, when bits 1 to 5 of the 'Scheduled TB for unicast' field are from '00011' to '01100', if bits 6 to 8 of the 'Scheduled TB for unicast' field are from '000' to '101', it indicates that HARQ feedback is enabled, and bits 6 to 8 also indicate which two of the four HARQ processes are associated with the two scheduled TBs, and if bits 6 to 8 of the 'Scheduled TB for unicast' field are '110' to '111', it indicates that HARQ feedback is disabled, and which two of the four HARQ processes are associated with the two scheduled TBs is indicated by a combination of '110' or '111' (for bits 6 to 8) and the 'HARQ-ACK Resource Offset' field.

[0097] As can be seen from Table 5, '01101' and '01110' (for bits 1 to 5) are unused states between 2 HARQ and 3 HARQ, and '11001' (for bits 1 to 5) is an unused state between 3 HARQ and 4 HARQ. Therefore, two of the three unused states (e.g., '01110' and 11001') can be used to indicate HARQ feedback disabling associated with scheduled downlink transmission (i.e., associated with three scheduled TBs). In addition, the combination of two unused states and the "HARQ-ACK Resource Offset" field (with 2 bits) (which is unnecessary for HARQ-ACK resources indicating HARQ feedback disabling) can indicate the first 8 or last 8 (i.e., 2 unused states + 2 bits = 8 states) MCS indexes (i.e., MCS index = 0 to 7 or MCS index = 2 to 9), as well as HARQ feedback disabling. The combination of these unused states (2 states) and the "HARQ-ACK Resource Offset" field (2 bits) indicates whether one of the first 8 MCS indices or one of the last 8 MCS indices may depend on the HARQ process number or the subframe number.

[0098] In general, when bits 1 to 5 of the 'Scheduled TB for Unicast' field are from '01110' to '11001', 3 TBs are scheduled. If bits 1 to 5 are from '01111' to '11000', it indicates that HARQ feedback is enabled, and bits 1 to 5 further indicate an MCS index plus 15, and if bits 1 to 5 are '01110' or '11001', it indicates that HARQ feedback is disabled, and the MCS index is indicated by a combination of '01110' or '11001' (for bits 1 to 5) and the 'HARQ-ACK Resource Offset' field.

[0099] As can be seen from Table 5, "111110 and 111111" (for bits 1 to 6) are two unused states after 4 HARQs. Therefore, these two unused states can be used to indicate HARQ feedback disabling associated with scheduled downlink transmission (i.e., associated with four scheduled TBs). In addition, the combination of these unused states (2 states) and the "HARQ-ACK resource offset" field (with 2 bits) (not required for HARQ-ACK resources indicating HARQ feedback disabling) can indicate the first 8 or last 8 (i.e., 2 unused states + 2 bits = 8 states) MCS indexes (i.e., MCS index = 0 to 7 or MCS index = 2 to 9) and HARQ feedback disabling. The combination of these unused states (2 states) and the 'HARQ-ACK resource offset' field (2 bits) indicates whether one MCS index from the first 8 MCS indexes or one MCS index from the last 8 MCS indexes may depend on the HARQ process number or the subframe number.

[0100] In general, when bits 1 to 6 of the 'Scheduled TB for Unicast' field are from '110100' to '111111', 4 TBs are scheduled. If bits 1 to 6 are from '110100' to '111101', HARQ feedback is enabled, and bits 1 to 6 also indicate an MCS index plus 52, and if bits 1 to 6 are from '111110' to '111111', HARQ feedback is disabled, and the MCS index is indicated by a combination of '111110' or '111111' (for bits 1 to 6) and the 'HARQ-ACK Resource Offset' field.

[0101] Incidentally, the unused state in the 'Scheduled TB for unicast' field can be referred to as a flag of the 'Scheduled TB for unicast' field to indicate HARQ feedback disablement of a specific transmission.

[0102] The fifth embodiment relates to an FDD scenario and a configured serving cell. The UE transmits HARQ-ACK feedback using PUCCH resources, where if MPDCCH-PRB-set is configured for distributed transmission, the PUCCH resources are, for example,

[0103] Δ ARO It is determined by the 'HARQ-ACK Resource Offset' field in the DCI format of the corresponding MPDCCH, as shown in Table 6.

[0104] 'HARQ-ACK Resource Offset' field value <![CDATA[Δ ARO ]]> 0 0 1 -1 2 -2 3 2

[0105] Table 6

[0106] n ECCE，q is the number of the first ECCE in the last detected MPDCCH (i.e., the lowest ECCE index used to construct the MPDCCH) in the MPDCCH-PRB-set used to transmit the corresponding DCI allocation.

[0107] MPDCCH-PRB-set Configured by higher layer parameters.

[0108] In eMTC CE mode B, it has been proposed to use one state of the 'HARQ-ACK Resource Offset' field in DCI format 6-1B to indicate HARQ feedback disabling. If a predetermined one state is used, scheduling restrictions will be imposed on certain PUCCH resources.

[0109] In view of the above, according to the fifth embodiment, a state of the 'HARQ-ACK Resource Offset' field for indicating HARQ feedback disable is determined by a HARQ process number and / or a subframe number.

[0110] For the first example, for HARQ processes 0 and 1, the state (or value) of the 'HARQ-ACK Resource Offset' field indicating HARQ feedback disablement is 0, while for HARQ processes 2 and 3, the state (or value) of the 'HARQ-ACK Resource Offset' field indicating HARQ feedback disablement is 1.

[0111] For the second example, one state of the 'HARQ-ACK Resource Offset' field for indicating HARQ feedback disabling is subframe number %4.

[0112] For the third example, the HARQ process number and subframe number %4 are further added to the equation to determine the PUCCH resources.

[0113] According to the sixth embodiment, the UE is configured with an RRC message (e.g., a HARQ feedback enable / disable message) in a bitmap manner, wherein the RRC message indicates HARQ feedback enable or disable for each HARQ process, and the UE also receives a control message indicating that for downlink transmission scheduled by the control message, the HARQ feedback enable or disable indicated by the RRC message is overwritten or maintained.

[0114] The control message can be the control message according to any one of the first embodiment, the second embodiment, the third embodiment, the fourth embodiment, and the fifth embodiment.

[0115] Table 7 shows a first example of the sixth embodiment, which adopts the control message according to the second embodiment as a control message indicating to cover or maintain the HARQ feedback enabling or disabling indicated by the RRC message.

[0116]

[0117] Table 7

[0118] If the HARQ feedback enable / disable message indicates HARQ feedback enablement, the first field indicates a value ranging from 0 to 9 to maintain the RRC configuration (i.e., maintain the HARQ feedback enablement indicated by the HARQ feedback enable / disable message for the scheduled downlink transmission), or indicates a value ranging from '1010' to '1100' to override the RRC configuration (i.e., override the HARQ feedback enablement indicated by the HARQ feedback enable / disable message to the HARQ feedback disablement associated with the scheduled downlink transmission).

[0119] If the HARQ feedback enable / disable message indicates HARQ feedback disable, the first field indicates a value in the range of '1010' to '1100' to maintain the RRC configuration (i.e., maintain the HARQ feedback disable indicated by the HARQ feedback enable / disable message for the scheduled downlink transmission), or indicates a value in the range of 0 to 9 to override the RRC configuration (i.e., override the HARQ feedback disable indicated by the HARQ feedback enable / disable message to the HARQ feedback enable associated with the scheduled downlink transmission).

[0120] The sixth embodiment is also applied to NTN NB-IoT HARQ feedback disabling and enabling with DCI indication.

[0121] For NB-IoT, HARQ feedback enablement or disablement associated with scheduled downlink transmission should be indicated in DCI format N1. Some relevant fields of DCI format N1 are shown in Table 8.

[0122] DCI format N1 field Number of digits Modulation and Coding Scheme (MCS) 4 HARQ-ACK Resources 4

[0123] Table 8

[0124] The 'MCS' field of DCI format N1 has 4 bits. The 'MCS' field of DCI format N1 indicates the MCS index. For NB-IoT, the candidate MCS index indicated by the 'MCS' field can be from 0 to 13 (i.e., from '0000' to '1101'). This means that there are six (2) unused states of the 'MCS' field (e.g., from 14 to 15, i.e., from '1110' to '1111').

[0125] The 'HARQ-ACK Resource Offset' field of DCI format N1 has 4 bits and indicates HARQ-ACK resources. If HARQ feedback disable is indicated, there is no need to indicate HARQ-ACK resources for scheduled downlink transmission.

[0126] In view of the above, it is possible to indicate HARQ feedback enablement or disablement associated with scheduled downlink transmission as shown in Table 9.

[0127]

[0128] Table 9

[0129] As shown in Table 9, when the 'MCS' field indicates any value ranging from '0000' to '1101', it indicates that HARQ feedback associated with the scheduled downlink transmission is enabled. Any value ranging from '0000' to '1101' of the 'MCS' field also indicates an MCS index. When the 'MCS' field indicates any value ranging from '0000' to '1101', the 'HARQ-ACK Resource' field (having 4 bits) indicates a value ranging from '0000' to '1111', which indicates HARQ-ACK feedback resource information.

[0130] When the 'MCS' field indicates a value of '1110', HARQ feedback disable associated with the scheduled downlink transmission is indicated. In this case, the 'MCS' field is used as a HARQ feedback disable indicator. Since HARQ feedback disable associated with the scheduled downlink transmission is indicated, there is no need to indicate HARQ-ACK feedback resource information. Therefore, the 'HARQ-ACK resource' field can be reused to indicate the MCS index. As shown in Table 9, when the 'MCS' field indicates a value of '1110', the 'HARQ-ACK resource' field indicates that any one of '0000' to '1101' is used as the MCS index.

[0131] Table 10 shows a second example of the sixth embodiment, which adopts the control message shown in Table 9 as a control message indicating to cover or maintain the HARQ feedback enabling or disabling indicated by the RRC message.

[0132]

[0133] Table 10

[0134] If the HARQ feedback enable / disable message indicates HARQ feedback enablement, the 'MCS' field indicates a value ranging from '0000' to '1101' to maintain the RRC configuration (i.e., maintain the HARQ feedback enablement of the scheduled downlink transmission indicated by the HARQ feedback enable / disable message), or indicates a value of '1110' to override the RRC configuration (i.e., override the HARQ feedback enablement indicated by the HARQ feedback enable / disable message to the HARQ feedback disablement associated with the scheduled downlink transmission).

[0135] If the HARQ feedback enable / disable message indicates HARQ feedback disable, the 'MCS' field indicates a value of '1110' to maintain the RRC configuration (i.e., maintain the HARQ feedback disable for the scheduled downlink transmission indicated by the HARQ feedback enable / disable message), or indicates a value in the range of '0000' to '1101' to override the RRC configuration (i.e., override the HARQ feedback disable indicated by the HARQ feedback enable / disable message to the HARQ feedback enable associated with the scheduled downlink transmission).

[0136] By the way, the above-mentioned fifth embodiment is also applied to NTN NB-IoT HARQ feedback disabling and enabling with DCI indication. A fourth example of the fifth embodiment is described as follows: The "HARQ-ACK Resource" field has 4 bits, corresponding to states 0 to 15, where state 15 can be used for HARQ feedback disabling indication of HARQ process 0, and state 7 can be used for HARQ feedback disabling indication of HARQ process 1.

[0137] In the sixth embodiment described above, the control message indicates that the HARQ feedback enablement or disablement indicated by the RRC message is covered or maintained. According to a variation of the sixth embodiment, the control message indicates the HARQ feedback enablement or disablement associated with the TB scheduled by the control message, wherein the HARQ feedback enablement or disablement indicated by the control message covers the HARQ feedback enablement or disablement indicated by the RRC message. This means that if the control message indicates the HARQ feedback enablement or disablement, the HARQ feedback enablement or disablement indicated by the RRC message is not considered.

[0138] If only one TB is scheduled, the sixth embodiment and the variant of the sixth embodiment are able to indicate HARQ feedback enablement or disablement associated with the scheduled one TB with the same result. For example, assuming that one TB scheduled by the control message is associated with HARQ process 0, and HARQ process 0 is indicated by the RRC message as HARQ feedback disablement, the control message according to the sixth embodiment may maintain the RRC configuration (i.e., the result HARQ feedback disablement associated with the scheduled one TB) or overwrite the RRC configuration (i.e., the result HARQ feedback enablement associated with the scheduled one TB), while the control message according to the variant of the sixth embodiment may indicate HARQ feedback disablement associated with the scheduled one TB (i.e., the result HARQ feedback disablement associated with the scheduled one TB) or indicate HARQ feedback enablement associated with the scheduled one TB (i.e., the result HARQ feedback enablement associated with the scheduled one TB).

[0139] On the other hand, if multiple TBs are scheduled (e.g., two TBs: a first TB associated with one HARQ process (e.g., HARQ process 0) and a second TB associated with one HARQ process (e.g., HARQ process 1)), and the two HARQ processes (e.g., HARQ process 0 and HARQ process 1) are indicated by the RRC message as different HARQ feedback (e.g., HARQ process 0 has HARQ feedback enabled and HARQ process 1 has HARQ feedback disabled), the sixth embodiment and its variations will indicate the HARQ feedback enablement or disablement associated with the two scheduled TBs with different results. Specifically, the control message according to the sixth embodiment may maintain the RRC configuration (i.e., causing the HARQ feedback associated with the scheduled first TB to be enabled, and the HARQ feedback associated with the scheduled second TB to be disabled) or override the RRC configuration (i.e., causing the HARQ feedback associated with the scheduled first TB to be disabled, and the HARQ feedback associated with the scheduled second TB to be enabled), while the control message according to the variant of the sixth embodiment may indicate the HARQ feedback associated with the scheduled TB to be enabled (i.e., causing the HARQ feedback associated with both the scheduled first TB and the scheduled second TB to be enabled) or indicate the HARQ feedback associated with the scheduled TB to be disabled (i.e., causing the HARQ feedback associated with both the scheduled first TB and the scheduled second TB to be disabled).

[0140] Figure 3 300 is a schematic flow chart illustrating an embodiment of a method 300 according to the present application. In some embodiments, the method 300 is performed by a device such as a remote unit (UE). In some embodiments, the method 300 can be performed by a processor such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc. that executes program code.

[0141] Method 300 may include 302 receiving a control message scheduling a transport block set, wherein the transport block set includes one or more transport blocks, the control message including a first field, the first field indicating whether hybrid automatic repeat request (HARQ) feedback is enabled or disabled for the transport block set, the first field also indicating a modulation and coding scheme (MCS) index, resources associated with the HARQ feedback, a HARQ process number, a new data indicator (NDI), or any combination thereof; and 304 receiving the transport block set based at least in part on the received control message.

[0142] In some embodiments, the control message includes a second field; the first field also indicates an MCS index or an MCS set; and the second field indicates a resource associated with HARQ feedback, or an MCS sub-index within the MCS set, or any combination thereof.

[0143] In some embodiments, the control message also includes a second field; and the first field also indicates an MCS index, or a HARQ process number and NDI; and the second field indicates resources associated with the HARQ feedback, a HARQ process number and NDI, or indicates an MCS index.

[0144] In some embodiments, the first field comprises a plurality of subfields, at least one of the plurality of subfields indicating whether HARQ feedback is enabled or disabled; the at least one subfield being based at least in part on a number of transport blocks in the transport block set.

[0145] In some embodiments, the resources associated with the HARQ feedback are based at least in part on the HARQ process number or the subframe number, or both.

[0146] In some embodiments, the method also includes receiving a radio resource control (RRC) message indicating whether HARQ feedback is enabled or disabled; the enabled or disabled HARQ feedback associated with the transport block set indicated by the first field overrides the enabled or disabled HARQ feedback indicated by the RRC message.

[0147] In some embodiments, the method further includes receiving a radio resource control (RRC) message indicating whether HARQ feedback is enabled or disabled; the first field indicates whether HARQ feedback is enabled or disabled by indicating whether to override or maintain the enabled or disabled HARQ feedback indicated by the RRC message.

[0148] This means that HARQ feedback is enabled or disabled at least in part based on an RRC message, the method comprising overriding the enabling or disabling of HARQ feedback associated with a first field indicating whether HARQ feedback is enabled or disabled for a transport block set based on the RRC message; or maintaining the enabling or disabling of HARQ feedback associated with the first field indicating whether HARQ feedback is enabled or disabled for a transport block set.

[0149] In some examples, the UE may determine to keep HARQ feedback disabled or enabled, as indicated in the first field received in the control message. In these examples, the UE may ignore the indication received in the RRC message. In other words, the UE may avoid changing the HARQ feedback from enabled (as indicated in the first field of the received control message) to disabled (as indicated in the received RRC message). Alternatively, the UE may avoid changing the HARQ feedback from disabled (as indicated in the first field of the received control message) to enabled (as indicated in the received RRC message).

[0150] Additionally or alternatively, the UE may change (e.g., override, update, modify) the HARQ feedback from disabling to enabling, or from enabling to disabling, based on the RRC message. In some examples, the UE may switch the HARQ feedback from disabling to enabling based on the RRC message. In some other examples, the UE may switch the HARQ feedback from disabling to enabling based on the RRC message. In other words, the UE may change (e.g., override) the HARQ feedback to enable or disable, which may be different from the indication that the HARQ feedback is enabled or disabled received in the control message via the first field.

[0151] Figure 4 A schematic flow chart of another embodiment of a method 400 according to the present application is shown. In some embodiments, the method 400 is performed by a device such as a network entity (e.g., a base station unit). In some embodiments, the method 400 can be performed by a processor such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc. that executes program code.

[0152] Method 400 may include 402 sending a control message for scheduling a transport block set, wherein the transport block set includes one or more transport blocks, the control message includes a first field, the first field indicates whether hybrid automatic repeat request (HARQ) feedback is enabled or disabled for the transport block set, and the first field also indicates a modulation and coding scheme (MCS) index, resources associated with HARQ feedback, a HARQ process number, a new data indicator (NDI), or any combination thereof; and 404 sending the transport block set based at least in part on the received control message.

[0153] In some embodiments, the control message includes a second field; the first field also indicates an MCS index or an MCS set; and the second field indicates a resource associated with HARQ feedback, or an MCS sub-index within the MCS set, or any combination thereof.

[0154] In some embodiments, the control message also includes a second field; and the first field also indicates an MCS index, or a HARQ process number and NDI; and the second field indicates resources associated with the HARQ feedback, a HARQ process number and NDI, or indicates an MCS index.

[0155] In some embodiments, the first field comprises a plurality of subfields, at least one of the plurality of subfields indicating whether HARQ feedback is enabled or disabled; the at least one subfield being based at least in part on a number of transport blocks in the transport block set.

[0156] In some embodiments, the resources associated with the HARQ feedback are based at least in part on the HARQ process number or the subframe number, or both.

[0157] In some embodiments, the method further includes sending a radio resource control (RRC) message indicating whether HARQ feedback is enabled or disabled; the enabled or disabled HARQ feedback associated with the transport block set indicated by the first field overrides the enabled or disabled HARQ feedback indicated by the RRC message.

[0158] In some embodiments, the method further includes sending a radio resource control (RRC) message indicating whether HARQ feedback is enabled or disabled; the first field indicates whether HARQ feedback is enabled or disabled by indicating whether to override or maintain the HARQ feedback enablement or disablement indicated by the RRC message.

[0159] This means that in order to enable or disable HARQ feedback based at least in part on an RRC message, the method includes overriding the enabling or disabling of HARQ feedback associated with a first field indicating whether HARQ feedback is enabled or disabled for a transport block set based on the RRC message; or maintaining the enabling or disabling of HARQ feedback associated with the first field indicating whether HARQ feedback is enabled or disabled for a transport block set.

[0160] Figure 5 is a schematic block diagram illustrating an apparatus according to one embodiment.

[0161] refer to Figure 5 , UE (ie remote unit) includes a processor, a memory and a transceiver. Processor implementation Figure 3 The functions, processes and / or methods proposed in.

[0162] The UE includes: a processor; and a transceiver coupled to the processor, wherein the processor is configured to cause the UE to: receive a control message for scheduling a transport block set, wherein the transport block set includes one or more transport blocks, the control message includes a first field, the first field indicates whether hybrid automatic repeat request (HARQ) feedback is enabled or disabled for the transport block set, and the first field also indicates a modulation and coding scheme (MCS) index, resources associated with the HARQ feedback, a HARQ process number, a new data indicator (NDI), or any combination thereof; and receive the transport block set based at least in part on the received control message.

[0163] In some embodiments, the control message includes a second field; the first field also indicates an MCS index or an MCS set; and the second field indicates a resource associated with HARQ feedback, or an MCS sub-index within the MCS set, or any combination thereof.

[0164] In some embodiments, the control message also includes a second field; and the first field also indicates an MCS index, or a HARQ process number and NDI; and the second field indicates resources associated with the HARQ feedback, a HARQ process number and NDI, or indicates an MCS index.

[0165] In some embodiments, the first field comprises a plurality of subfields, at least one of the plurality of subfields indicating whether HARQ feedback is enabled or disabled; the at least one subfield being based at least in part on a number of transport blocks in the transport block set.

[0166] In some embodiments, the resources associated with the HARQ feedback are based at least in part on the HARQ process number or the subframe number, or both.

[0167] In some embodiments, the processor is further configured to receive a radio resource control (RRC) message indicating whether HARQ feedback is enabled or disabled; the enabled or disabled HARQ feedback associated with the transport block set indicated by the first field overrides the enabled or disabled HARQ feedback indicated by the RRC message.

[0168] In some embodiments, the processor is further configured to receive a radio resource control (RRC) message indicating whether HARQ feedback is enabled or disabled; the first field indicates whether HARQ feedback is enabled or disabled by indicating whether to override or maintain the enabled or disabled HARQ feedback indicated by the RRC message.

[0169] This means that in order to enable or disable HARQ feedback based at least in part on an RRC message, the method includes overriding the enabling or disabling of HARQ feedback associated with a first field indicating whether HARQ feedback is enabled or disabled for a transport block set based on the RRC message; or maintaining the enabling or disabling of HARQ feedback associated with the first field indicating whether HARQ feedback is enabled or disabled for a transport block set.

[0170] refer to Figure 5 , a gNB (i.e., a network entity, such as a base station unit) includes a processor, a memory, and a transceiver. The processor implements Figure 4 The functions, processes and / or methods proposed in.

[0171] The network entity includes: a processor; and a transceiver coupled to the processor, wherein the processor is configured to cause the network entity to: send a control message for scheduling a transport block set, wherein the transport block set includes one or more transport blocks, the control message includes a first field, the first field indicates whether hybrid automatic repeat request (HARQ) feedback is enabled or disabled for the transport block set, and the first field also indicates a modulation and coding scheme (MCS) index, resources associated with HARQ feedback, a HARQ process number, a new data indicator (NDI), or any combination thereof; and send the transport block set based at least in part on the received control message.

[0172] In some embodiments, the control message includes a second field; the first field also indicates an MCS index or an MCS set; and the second field indicates a resource associated with HARQ feedback, or an MCS sub-index within the MCS set, or any combination thereof.

[0173] In some embodiments, the control message further includes a second field; and the first field further indicates an MCS index, or a HARQ process number and NDI; and the second field indicates resources associated with the HARQ feedback, a HARQ process number and NDI, or indicates an MCS index.

[0174] In some embodiments, the first field comprises a plurality of subfields, at least one of the plurality of subfields indicating whether HARQ feedback is enabled or disabled; the at least one subfield being based at least in part on a number of transport blocks in the transport block set.

[0175] In some embodiments, the resources associated with the HARQ feedback are based at least in part on the HARQ process number or the subframe number, or both.

[0176] In some embodiments, the processor is further configured to send a radio resource control (RRC) message indicating whether HARQ feedback is enabled or disabled; the enabled or disabled HARQ feedback associated with the transport block set indicated by the first field overrides the enabled or disabled HARQ feedback indicated by the RRC message.

[0177] In some embodiments, the processor is further configured to send a radio resource control (RRC) message indicating whether HARQ feedback is enabled or disabled; the first field indicates whether HARQ feedback is enabled or disabled by indicating whether to override or maintain the enabled or disabled HARQ feedback indicated by the RRC message.

[0178] This means that in order to enable or disable HARQ feedback based at least in part on an RRC message, the method includes overriding the enabling or disabling of HARQ feedback associated with a first field indicating whether HARQ feedback is enabled or disabled for a transport block set based on the RRC message; or maintaining the enabling or disabling of HARQ feedback associated with the first field indicating whether HARQ feedback is enabled or disabled for a transport block set.

[0179] Each layer of the wireless interface protocol can be implemented by the processor. The memory is connected to the processor to store various information for driving the processor. The transceiver is connected to the processor to send and / or receive radio signals. Needless to say, the transceiver can be implemented as a transmitter for sending radio signals and a receiver for receiving radio signals.

[0180] The memory may be located inside or outside the processor and connected to the processor through various well-known means.

[0181] In the above-described embodiments, the components and features of the embodiments are combined in a predetermined form. Unless otherwise clearly stated, each component or feature should be considered as an option. Each component or feature can be implemented as not being associated with other components or features. In addition, the embodiment can be configured by associating some components and / or features. The order of operations described in the embodiment can be changed. Some components or features of any embodiment can be included in another embodiment or replaced with components and features corresponding to another embodiment. Obviously, claims that are not clearly cited in the claims can be combined to form embodiments or included in new claims.

[0182] Embodiments may be implemented by hardware, firmware, software or a combination thereof. In the case of implementation by hardware, according to the hardware implementation, the exemplary embodiments described herein may be implemented by using one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

[0183] Embodiments may be practiced in other specific forms. The described embodiments should be considered in all respects to be illustrative only and not restrictive. Therefore, the scope of the present invention is indicated not by the above description but by the appended claims. All changes within the equivalent meaning and scope of the claims are included within the scope of the present invention.

Claims

1. A user equipment (UE), comprising: processor; as well as a transceiver coupled to the processor, wherein the processor is configured to cause the UE to: receiving a control message scheduling a transport block set, wherein the transport block set includes one or more transport blocks, the control message including a first field indicating whether hybrid automatic repeat request (HARQ) feedback is enabled or disabled for the transport block set, the first field further indicating a modulation coding scheme (MCS) index, resources associated with the HARQ feedback, a HARQ process number, a new data indicator (NDI), or any combination thereof; and The set of transport blocks is received based at least in part on a received control message.

2. The UE according to claim 1, wherein: The control message comprises a second field; The first field also indicates the MCS index or MCS set; and The second field indicates the resource associated with the HARQ feedback, or an MCS sub-index within the MCS set, or any combination thereof.

3. The UE according to claim 1, wherein: The control message further includes a second field; and The first field further indicates the MCS index, or the HARQ process number and the NDI; and The second field indicates the resource, the HARQ process number, and the NDI associated with the HARQ feedback, or indicates the MCS index.

4. The UE according to claim 1, wherein: The first field includes a plurality of subfields. At least one subfield of the plurality of subfields indicates whether the HARQ feedback is enabled or disabled; The at least one subfield is based at least in part on a number of transport blocks in the transport block set.

5. The UE according to claim 1, wherein: The resources associated with the HARQ feedback are based at least in part on the HARQ process number or the subframe number, or both.

6. The UE according to claim 1, wherein: The processor is further configured to cause the UE to: receiving a radio resource control (RRC) message indicating whether the HARQ feedback is enabled or disabled; The enabled or disabled HARQ feedback associated with the transport block set indicated by the first field overrides the enabled or disabled HARQ feedback indicated by the RRC message.

7. The UE according to claim 1, wherein: The processor is further configured to cause the UE to: receiving a radio resource control (RRC) message indicating whether the HARQ feedback is enabled or disabled; The first field indicates whether the HARQ feedback is enabled or disabled by indicating whether to override or maintain the enabled or disabled HARQ feedback indicated by the RRC message.

8. A method of a user equipment (UE), comprising: receiving a control message scheduling a transport block set, wherein the transport block set includes one or more transport blocks, the control message including a first field indicating whether hybrid automatic repeat request (HARQ) feedback is enabled or disabled for the transport block set, the first field further indicating a modulation coding scheme (MCS) index, resources associated with the HARQ feedback, a HARQ process number, a new data indicator (NDI), or any combination thereof; and The set of transport blocks is received based at least in part on a received control message.

9. A network entity, comprising: processor; as well as a transceiver coupled to the processor, wherein the processor is configured to cause the network entity to: sending a control message scheduling a transport block set, wherein the transport block set includes one or more transport blocks, the control message including a first field, the first field indicating whether hybrid automatic repeat request (HARQ) feedback is enabled or disabled for the transport block set, the first field further indicating a modulation and coding scheme (MCS) index, resources associated with the HARQ feedback, a HARQ process number, a new data indicator (NDI), or any combination thereof; and The set of transport blocks is sent based at least in part on the received control message.

10. The network entity according to claim 9, wherein: The control message comprises a second field; The first field also indicates the MCS index or MCS set; and The second field indicates the resource associated with the HARQ feedback, or an MCS sub-index within the MCS set, or any combination thereof.

11. The network entity according to claim 9, wherein: The control message further includes a second field; and, The first field further indicates the MCS index, or the HARQ process number and the NDI; and The second field indicates the resource, the HARQ process number, and the NDI associated with the HARQ feedback, or indicates the MCS index.

12. The network entity according to claim 9, wherein: The first field includes a plurality of subfields. At least one subfield of the plurality of subfields indicates whether the HARQ feedback is enabled or disabled; The at least one subfield is based at least in part on a number of transport blocks in the transport block set.

13. The network entity according to claim 9, wherein: The resources associated with the HARQ feedback are based at least in part on the HARQ process number or the subframe number, or both.

14. The network entity according to claim 9, wherein: The processor is further configured to cause the UE to: receiving a radio resource control (RRC) message indicating whether the HARQ feedback is enabled or disabled; The enabled or disabled HARQ feedback associated with the transport block set indicated by the first field overrides the enabled or disabled HARQ feedback indicated by the RRC message.

15. The network entity according to claim 9, wherein: The processor is further configured to cause the UE to: receiving a radio resource control (RRC) message indicating whether the HARQ feedback is enabled or disabled; The first field indicates whether the HARQ feedback is enabled or disabled by indicating whether to override or maintain the enabled or disabled HARQ feedback indicated by the RRC message.

Images