WO2019028916A1

WO2019028916A1 - Data transmission method and device

Info

Publication number: WO2019028916A1
Application number: PCT/CN2017/097272
Authority: WO
Inventors: 南方; 余政; 赵越
Original assignee: 华为技术有限公司
Priority date: 2017-08-11
Filing date: 2017-08-11
Publication date: 2019-02-14
Also published as: CN110999153A; CN110999153B

Abstract

Provided in the present application are a data transmission method and device. The method comprises: a network device receiving uplink data transmitted by a terminal device; and the network device transmitting first downlink control information to the terminal device, wherein a value of a first bit of the first downlink control information is 1, the number of the first bit is greater than or equal to 1, and the first bit is used to indicate whether the first downlink control information indicates a positive acknowledgment or a negative acknowledgment to the uplink data by the network device. The embodiments of the present application can reduce delay on the feedback to uplink data.

Description

Data transmission method and device

Technical field

The present application relates to the field of communications, and in particular, to a data transmission method and apparatus in the field of communications.

Background technique

In a long term evolution (LTE) system, information exchanged between a terminal device and a network device is carried over a physical channel. The downlink data is carried by a physical downlink shared channel (PDSCH), and the uplink data is carried by a physical uplink shared channel (PUSCH). The network device indicates information such as resource allocation and modulation and coding mode of the PDSCH and the PUSCH to the terminal device by using downlink control information (DCI). The DCI can be carried by a physical downlink control channel (PDCCH).

The uplink and downlink data transmission of the LTE system adopts a hybrid automatic repeat request (HARQ) technology, and the HARQ technology is a technology that combines forward error correction and error detection retransmission. The specific processing flow is: Each time the data is sent contains error correction and error detection bits. If the number of error bits in the received data is within the error correction capability, the error is corrected by itself; when the error is serious and the error correction capability is exceeded, then Let the sender resend the data. LTE adopts the multi-process stop-and-wait HARQ implementation mode. That is, for a certain HARQ process, if the data received by the receiving end is correct and does not need to be retransmitted, the receiving end feeds back an acknowledgement (ACK) to the transmitting end, otherwise the feedback is negative. A negative acknowledgment (NACK) indicates a retransmission. When the sender waits for ACK/NACK feedback, the process temporarily suspends the transmission. When the feedback is received, it selects whether to send new data or retransmit the last data sent by the process according to whether the ACK or NACK is fed back. The ACK/NACK feedback of the uplink data is carried by a physical hybrid ARQ indicator channel (PHICH). The PDCCH and PHICH occupied by the LTE system may have a frequency width of the entire system and may reach a maximum of 20 MHz. When the receiving bandwidth of the terminal device is smaller than the system bandwidth, the DCI carried by the PDCCH and the ACK/NACK carried by the PHICH cannot be received.

The DCI can be carried by the MPDCCH because the bandwidth occupied by the physical downlink control channel (MPDCCH) of the machine type communication is not more than one narrowband. In an existing transmission method, a new data indicator (NDI) containing 1 bit in the DCI is used to indicate whether the uplink data scheduled by the DCI is newly transmitted data, or is the process retransmitted. The function of the ACK/NACK feedback in the DCI carried by the MPDCCH can be implemented by the NDI bit in the DCI carried by the MPDCCH, so that the terminal device does not need to receive the ACK/NACK of the PHICH bearer. .

However, the method for implicitly receiving the uplink data of the PUSCH by the NDI in the DCI is implicitly fed back. In order to indicate that the data sent by the terminal device is correctly received, the base station needs to wait until the next uplink data of the terminal device. The NDI indicates new uplink data. After the uplink data transmission is completed, the terminal device may need to wait for a period of time before the next uplink data needs to be sent. Therefore, the network device also needs to wait for a period of time. The NDI feedback in the DCI can be correctly received, so that the terminal device may not be able to know in time whether the uplink data is correctly received by the network device, that is, the network device has a large delay in the feedback of the uplink data.

Summary of the invention

The present application provides a data transmission method and apparatus, in order to reduce the feedback delay of network equipment to uplink data.

The first aspect provides a data transmission method, where the method includes: the network device receives the uplink data, and sends the first downlink control information, where the first bit of the first downlink control information has a value of 1, the first The number of one bit is greater than or equal to 1. The first bit is used to indicate that the first downlink control information is used to indicate that the network device acknowledges or negatively acknowledges the uplink data.

Correspondingly, the terminal device sends uplink data, and receives the first downlink control information.

Optionally, the terminal device may determine, according to the first downlink control information, whether the uplink data is correctly received by the network device.

Therefore, in the embodiment of the present application, after determining whether the network device correctly receives the uplink data sent by the terminal device, the network device may send the first downlink control information to the terminal device, and feedback the receiving condition of the uplink data, without The technology waits until the next time the terminal device needs to send uplink data, so that it is beneficial to reduce the feedback delay of the network device to the uplink data, thereby improving system performance.

Optionally, in an implementation manner of the first aspect, before the network device receives the uplink data sent by the terminal device, the method further includes:

The network device sends the second downlink control information to the terminal device. In the first bit of the second downlink control information, the value of the at least one bit is 0, and the second downlink control information is used by the network device to schedule the physical uplink. Shared channel

Correspondingly, the terminal device receives the second downlink control information that is sent by the network device, where the value of the at least one bit is 0 in the first bit of the second downlink control information, and the second downlink control information is used to schedule the physics. Uplink shared channel;

The terminal device sends the uplink data to the network device according to the second downlink control information.

Specifically, in the embodiment of the present application, the downlink control information that is sent by the network device to the terminal device may be divided into the first downlink control information and the second downlink control information. The first downlink control information is used by the network device to feed back whether the uplink data sent by the terminal device is correctly received. The first downlink control information may not be used by the network device to schedule a physical uplink shared channel. The first downlink control information may also be used for the physical uplink shared channel that the network device schedules retransmission. The second downlink control information is used by the network device to schedule a physical uplink shared channel. In view of this, the first downlink control information may be sent at any time after the network device determines whether the uplink data is correctly received. The second downlink control information can only be sent when the network device schedules the terminal device for data transmission. The value of the first bit in the first control information is set to 1 by using the first bit in the second downlink control information, and the value of the first bit is not 1. Therefore, the terminal device can distinguish the first downlink control information and the second downlink control information.

Specifically, when the value of the first bit is 1, the terminal device may determine that the received downlink control information is feedback control information, where the value of the first bit is not all 1, that is, at least one bit of the first bit. When the value is 0, the terminal device may determine that the downlink control information is the second downlink control information of the data scheduling.

Therefore, in the data transmission method of the embodiment of the present application, once the network device determines whether the uplink data sent by the terminal device is correctly received, the network device may send the first downlink control information to the terminal device, and feedback the receiving condition of the uplink data, without As in the prior art, the next time the terminal device needs to send uplink data, the feedback is delayed, which is beneficial to reducing the feedback delay of the network device to the uplink data, thereby improving system performance.

Optionally, in an implementation manner of the first aspect, the first downlink control information is only used to indicate a positive response to the uplink data, where the first downlink control information further includes a hybrid automatic repeat request (HARQ process). The number indication bit, the HARQ process number indication bit is used to indicate the HARQ process corresponding to the uplink data.

Optionally, in an implementation manner of the first aspect, in the bits of the first downlink control information, in addition to the existing padding bits, the first bit, and downlink control information used to distinguish the scheduled physical downlink shared channel The format and the flag of the downlink control information format of the physical uplink shared channel and the HARQ process number indication bit are used, and the remaining bits are reserved bits, or all values are 1, or all values are 0.

Specifically, when the network device needs to feed back the ACK for the correct reception of the uplink data, the first DCI is sent, and the first DCI is only used to indicate that the uplink data is correctly received, that is, an acknowledgement of the network device. When the network device needs to feed back NACK for the uplink data receiving error, the network device may retransmit the uplink data by using the NDI bit in the existing manner, that is, implicitly feedback the uplink data error receiving through the NDI bit, at this time in the DCI. The first bit is not all ones. When the terminal device receives the DCI, if the first bit in the DCI is detected to be 1, the UE considers that the DCI indicates an ACK, that is, the uplink data of the HARQ process for which the UE is correctly received by the network device.

Specifically, the first downlink control information may include, in addition to the first bit, a downlink control information format for scheduling the physical downlink shared channel and a downlink control information format for scheduling the physical uplink shared channel, and the HARQ. The process number indicates the bit. In the first downlink control information, padding bits may or may not be included. The padding bit is used to expand the number of bits included in the first downlink control information, so that the number of bits included in the first downlink control information reaches a target value. When the first downlink control information includes padding bits, the number of padding bits existing in the bits of the first downlink control information is greater than zero. When the first downlink control information does not include padding bits, the number of padding bits existing in the bits of the first downlink control information is 0. In the downlink control information, the flag of the downlink control information format for scheduling the physical downlink shared channel and the downlink control information format for scheduling the physical uplink shared channel are 0, which generally indicates that the format of the downlink control information is a scheduling physical uplink shared channel. The downlink control information format is used to distinguish between the downlink control information format for scheduling the physical downlink shared channel and the downlink control information format for scheduling the physical uplink shared channel, and the flag of the downlink control information format is 1, which generally indicates that the format of the downlink control information is a scheduled physical downlink shared channel. The downlink control information format. In the first downlink control information, the flag of the downlink control information format for scheduling the physical downlink shared channel and the downlink control information format for scheduling the physical uplink shared channel are 0. In addition, the remaining bits included in the first downlink control information may be reserved bits, and may all have a value of 1 or a value of 0, which is not limited in this embodiment of the present application. For the number of the remaining bits included in the first downlink control information, the embodiment of the present application does not limit this.

Optionally, in an implementation manner of the first aspect, the first downlink control information further includes a feedback indication bit, where the feedback indication bit is used to indicate that the network device acknowledges or negatively acknowledges the uplink data.

Optionally, in an implementation manner of the first aspect, the uplink data includes uplink data corresponding to N HARQ processes, where the number of the feedback indication bits is N, and N bits of the feedback indication bit are used respectively. Instructing the network device to acknowledge or negatively acknowledge the uplink data corresponding to the N HARQ processes, and N is an integer greater than 1.

Specifically, the foregoing first downlink control information may be correct for uplink data corresponding to one HARQ process. The feedback is received, and the uplink data corresponding to the multiple HARQ processes may be fed back. In the case that the first downlink control information is fed back for the correct reception of the uplink data corresponding to the N HARQ processes, the number of the feedback indication bits included in the first downlink control information is N, and one bit corresponds to one HARQ process. . In this way, the network device can feed back the uplink data corresponding to the multiple HARQ processes to the terminal device in a downlink control information, so as to reduce the feedback overhead of the network device and improve the feedback efficiency of the network device.

Optionally, in an implementation manner of the first aspect, in the first downlink control information,

The remaining bits are reserved except for the existing padding bits, the first bit, the downlink control information format for distinguishing the physical downlink shared channel, and the flag of the downlink control information format for scheduling the physical uplink shared channel, and the feedback indication bit. Bit, or a value of 1, or a value of 0; or

In addition to the existing padding bits, the first bit, a downlink control information format for distinguishing the scheduled physical downlink shared channel, and a flag bit for scheduling the downlink control information format of the physical uplink shared channel, the feedback indication bit, and the indication for retransmission The bits of the scheduling information of the uplink data are the reserved bits, or the values are all 1, or the value is 0. The bits of the scheduling information for indicating the retransmitted uplink data are included to indicate the following. At least one bit of information:

Resource allocation, modulation and coding mode, number of repetitions, and number of sub-frame repetitions of downlink control information.

Optionally, in an implementation of the first aspect, the N is equal to two.

Under normal circumstances, there are at most two HARQ processes corresponding to the uplink data. The number of the feedback indication bits is 2, and the 2 bits of the feedback indication bit are respectively used to indicate an acknowledgement or a negative response of the network device to the uplink data corresponding to the two HARQ processes.

Optionally, in an implementation manner of the first aspect, the number of the feedback indication bits is 1, and the first downlink control information further includes a HARQ process number indication bit, where the HARQ process number indication bit is used to indicate the The HARQ process corresponding to the uplink data.

Specifically, when the first downlink control information is used to feed back the uplink data corresponding to the one HARQ process, the first downlink control information may further carry a HARQ process number indication bit, which is used to indicate the current feedback. The corresponding HARQ process. When the first downlink control information is used to feed back the uplink data corresponding to the multiple HARQ processes, the network device and the terminal device may determine, according to a predetermined rule, each feedback indication bit in the first control information. One-to-one correspondence between the uplink data of each HARQ process in the HARQ process, or the network device allocates the one-to-one correspondence to the terminal device. After receiving the first downlink control information, the terminal device may directly determine, according to the one-to-one correspondence, a feedback indication bit corresponding to uplink data of each HARQ process in the multiple HARQ processes, and according to the feedback The indication bit determines whether the corresponding uplink data is correctly received by the network device.

Optionally, in an implementation manner of the first aspect, in a bit of the first downlink control information,

In addition to the existing padding bits, the first bit, a downlink control information format for distinguishing the scheduled physical downlink shared channel, and a flag bit for scheduling the downlink control information format of the physical uplink shared channel, the feedback indication bit, and the HARQ process number indication bit In addition, the remaining bits are reserved bits, or all values are 1, or the value is 0; or

In addition to the existing padding bits, the first bit, a downlink control information format for distinguishing the scheduled physical downlink shared channel, and a flag bit for scheduling the downlink control information format of the physical uplink shared channel, the feedback indication bit, and the indication for retransmission The bits of the scheduling information of the uplink data and the HARQ process number indication bits, the remaining bits are reserved bits, or all of the values are 1, or the value is 0, wherein the scheduling of the uplink data for indicating retransmission is used. informational The bits include bits for indicating at least one of the following:

Specifically, the foregoing first downlink control information may be used only for the network device to feed back whether the uplink data is correctly received, or may be used for the network device to feed back whether the uplink data is correctly received, and the network device feeds back the NACK. The method is further configured to schedule the terminal device to retransmit the uplink data. Therefore, the first downlink control information may further include a bit for indicating scheduling information of the retransmitted uplink data, but the embodiment of the present application does not limit this.

As an optional embodiment, the feedback indication bit is in a bit of the first downlink control information, except for a padding bit that exists, the first bit, a downlink control information format used to distinguish the scheduled physical downlink shared channel, and A flag of a downlink control information format of the physical uplink shared channel and a plurality of bits other than the hybrid automatic repeat request HARQ process number indication bit are scheduled.

Optionally, the multiple bits are in the bits of the first downlink control information, except for the existing padding bits, the first bit, the downlink control information format used to distinguish the scheduled physical downlink shared channel, and the scheduling of the physical uplink shared channel. The flag bits of the downlink control information format and all bits except the hybrid automatic repeat request HARQ process number indication bit.

The HARQ process number indication bit is used to indicate the HARQ process corresponding to the uplink data. Optionally, the value of the feedback indication bit is 1 for indicating a positive response to the uplink data, and the value of the feedback indication bit is 0 for indicating a negative response to the uplink data. Optionally, the value of the feedback indication bit is 0 to indicate an acknowledgement to the uplink data, and the value of the feedback indication bit is 1 to indicate a negative response to the uplink data. The number of the feedback indication bits is greater than one, and is used to indicate an acknowledgement or a negative acknowledgement of the uplink data corresponding to the HARQ process indicated by the HARQ process number indication bit. The values of the bits of the feedback indication bit are the same.

Optionally, in an implementation manner of the first aspect, the number of bits of the first downlink control information is equal to the number of bits of the second downlink control information, and the first bit of the first downlink control information is The location is the same as the location of the first bit of the second downlink control information; and/or,

The first downlink control information has the same format as the second downlink control information.

Therefore, in the embodiment of the present application, by setting the number of bits of the first downlink control information to be the same as the bit data of the DCI of the scheduling data, or the format is the same, the terminal device does not increase the blind detection of the first downlink control information. Degree, achieve compatibility with the DCI of the scheduled data.

Optionally, in an implementation manner of the first aspect, the first bit of the second downlink control information is a bit used to indicate a modulation and coding mode; and/or the number of the first bit is 4.

Optionally, in an implementation manner of the first aspect, the first bit of the second downlink control information is all bits or partial bits of the domain used to indicate resource allocation; or

The first bit of the second downlink control information is all bits or partial bits of a field for indicating resource allocation and modulation and coding mode.

Optionally, in an implementation manner of the first aspect, the resource of the physical uplink shared channel indicated by the first bit first state of the second downlink control information is a resource of less than 12 subcarriers.

Optionally, in an implementation manner of the first aspect, the number of the first bits is 9 or 11; or

The number of the first bits is greater than

or,

The number of the first bits is

among them,

Indicates the number of physical resource blocks included in the uplink system bandwidth.

Optionally, in an implementation manner of the first aspect, the downlink control information format for scheduling the physical downlink shared channel and the downlink control information for scheduling the physical uplink shared channel are used in the bit of the first downlink control information. The format flag has a value of 0.

Optionally, in an implementation manner of the first aspect, the downlink control information format used to distinguish the physical downlink shared channel and the downlink control information format of the physical uplink shared channel are used to distinguish the control information format. 0B and the flag of control information format 6-1B.

Therefore, in the embodiment of the present application, for the DCI of the 6-0B format, after determining whether the network device correctly receives the uplink data sent by the terminal device, the network device may send the first downlink control information to the terminal device, and feed back the uplink data. The receiving situation does not need to wait until the next time the terminal device needs to send uplink data as in the prior art, which is beneficial to reduce the feedback delay of the network device to the uplink data, thereby improving system performance.

In a third aspect, a network device is provided, and the network device provided by the present application has a function of implementing network device behavior in the foregoing method aspect, and includes a component corresponding to the step or function described in the foregoing method aspect. . The steps or functions may be implemented by software, or by hardware, or by a combination of hardware and software.

In one possible design, the network device described above includes one or more processors and transceiver units. The one or more processors are configured to support the network device to perform corresponding functions in the above methods. For example, generate a DCI. The transceiver unit is configured to support the network device to communicate with other devices to implement a receiving/transmitting function. For example, the DCI generated by the processor is transmitted.

It should be understood that in the present application, "/" may mean "and/or".

Optionally, the base station may further include one or more memories, where the memory is coupled to the processor, which stores necessary program instructions and data of the base station. The one or more memories may be integrated with the processor or may be separate from the processor. This application is not limited.

The network device may be a base station or a TRP, and the transceiver unit may be a transceiver or a transceiver circuit.

The network device can also be a communication chip. The transceiver unit may be an input/output circuit or interface of a communication chip.

In another possible design, the above network device includes a transceiver, a processor, and a memory. The processor is configured to control a transceiver transceiver signal for storing a computer program, the processor for calling and running the computer program from the memory, such that the network device performs the first aspect, any one of the first aspects The method of completing the network device in the mode.

According to a fourth aspect, a terminal device is provided. The terminal device provided by the present application has a function for implementing the behavior of the terminal device in the foregoing method aspect, and includes a component corresponding to the step or function described in the foregoing method aspect. . The steps or functions may be implemented by software, or by hardware, or by a combination of hardware and software.

In one possible design, the above terminal device includes one or more processors and transceiver units. The transceiver unit is configured to support the terminal device to communicate with other devices to implement a receiving/transmitting function. For example, receive DCI. The one or more processors are configured to support the terminal device to perform a corresponding function in the above method. For example, according to The DCI determines the feedback of the uplink data.

Optionally, the terminal device may further include one or more memories, and the memory is configured to be coupled to the processor, which stores necessary program instructions and data of the base station. The one or more memories may be integrated with the processor or may be separate from the processor. This application is not limited.

The terminal device may be a UE or the like, and the transceiver unit may be a transceiver or a transceiver circuit.

The terminal device can also be a communication chip. The transceiver unit may be an input/output circuit or interface of a communication chip.

In another possible design, the above terminal device includes a transceiver, a processor, and a memory. The processor is configured to control a transceiver transceiver signal for storing a computer program, the processor for calling and running the computer program from the memory, such that the terminal device performs any of the possible implementations of the first aspect of the first aspect The method in which the terminal device is completed.

In a fifth aspect, a system is provided, the system comprising the above terminal device and a network device.

In a sixth aspect, a computer program product is provided, the computer program product comprising: a computer program (which may also be referred to as a code, or an instruction), when the computer program is executed, causing the computer to perform the first aspect of the first aspect described above Any of the possible implementations.

In a seventh aspect, a computer readable medium storing a computer program (which may also be referred to as a code, or an instruction), when executed on a computer, causes the computer to perform the first aspect, first Any of the possible implementations of the aspect.

In an eighth aspect, the present application provides a chip system including a processor for supporting a network device to implement the functions involved in the above aspects, such as, for example, receiving or processing data and/or processing involved in the above method. information. In a possible design, the chip system further includes a memory for storing necessary program instructions and data of the network device. The chip system can be composed of chips, and can also include chips and other discrete devices.

In a ninth aspect, the present application provides a chip system including a processor for a terminal device to implement the functions involved in the above aspects, such as, for example, transmitting or processing data and/or information involved in the above method. . In a possible design, the chip system further comprises a memory for storing necessary program instructions and data of the terminal device. The chip system can be composed of chips, and can also include chips and other discrete devices.

DRAWINGS

FIG. 1 is a schematic diagram of a system scenario applicable to an embodiment of the present application.

2 is a schematic flow chart of a method of data transmission according to another embodiment of the present application.

FIG. 3 is a schematic block diagram of a terminal device according to an embodiment of the present application.

4 is a schematic block diagram of a network device in accordance with one embodiment of the present application.

Figure 5 is a schematic block diagram of an apparatus in accordance with one embodiment of the present application.

Detailed ways

The technical solutions in the present application will be described below with reference to the accompanying drawings.

The embodiments of the present application are applicable to various communication systems, and therefore, the following description is not limited to a specific communication system. For example, the embodiment of the present application can be applied to a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, and a wideband code division multiple access (wideband). Code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division double Time division duplex (TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, and future fifth generation (5th generation, 5G) ) System or new radio (NR), etc.

It should be understood that, in a communication system to which the embodiment of the present application is applicable, as long as one device (for example, a terminal device) transmits uplink data, another device (for example, a network device) needs to receive the uplink data, and the corresponding method is used. The uplink data is correctly received for feedback, and the embodiment of the present application is not limited to the communication system described above.

FIG. 1 shows a schematic block diagram of a wireless communication system 100 suitable for use with embodiments of the present application. The wireless communication system 100 can include a network device 110 and at least one terminal device. FIG. 1 shows a case where the at least one terminal device is three devices, which are the case of the

terminal devices

120, 130, and 140, respectively. The example is not limited to this.

It should be understood that the network device 110 in the embodiment of the present application may receive uplink data sent by the terminal device, where the network device may be global system of mobile communication (GSM) or code division multiple access (CDMA). The base transceiver station (BTS) may also be a base station (nodeB, NB) in wideband code division multiple access (WCDMA), or may be long term evolution (LTE). Evolved base station (eNB/eNodeB), or a relay station or access point, or an in-vehicle device, a wearable device, and a network-side device in a future 5G network or a public land mobile communication network in the future (public land) A network device or the like in a mobile network (PLMN), for example, a transmission point (TRP or TP) in an NR system, a base station (gNB) in an NR system, or one or a group of base stations in a 5G system (including a plurality of antenna panels) The antenna panel and the like are not particularly limited in this embodiment of the present application.

The terminal device in the embodiment of the present application may send uplink data to the network device. For example, the terminal device may be a device that performs a machine type communication (MTC) service, and the terminal device may also be referred to as a user device. , UE), for example, Bandwidth-reduced Low-complexity UE (BL UE), Coverage Enhancement UE (CE UE); the terminal device may also be referred to as an access terminal, Subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The access terminal may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), with wireless communication. Functional handheld device, computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a drone device, and a terminal device in a future 5G network or a terminal device in a future evolved PLMN, etc. This example is not limited to this.

In FIG. 1, a case where the terminal device 120 is a user device, the terminal device 130 is an in-vehicle device, and the terminal device 140 is a printer is shown.

It should be understood that the network device 110 in the embodiment of the present application may also be a terminal device as described above. In this case, the communication between the network device and the terminal device may be evolved into communication between the terminal devices. In this case, It may also be referred to as machine to machine (M2M), or inter-device communication (D2D). The embodiment of the present application is not limited thereto.

As shown in FIG. 1 , after the terminal device sends the uplink data, the network device needs to feed back whether the uplink data is correctly received, so that in case of feedback error reception, the terminal device needs to retransmit the data, and if the feedback is correctly received, No terminal device is required to retransmit data.

In the existing solution, the network device can indicate whether the uplink data scheduled by the DCI is newly transmitted data or the data transmitted last time by the process through the NDI of 1 bit in the DCI.

However, in the existing solution, the DCI is used to schedule data, that is, the network device sends the DCI only when there is data scheduling, and the network device can be scheduled by the network device if the network device incorrectly receives the uplink data. The DCI implicit feedback uplink data reception of the retransmission of the terminal device fails. However, in the case that the network device correctly receives the uplink data sent by the terminal device, when the network device does not have a new uplink data scheduling, the network device does not send a DCI scheduling new transmission, thereby feeding back the correct reception of the uplink data, only in the case of In the case of a new uplink data scheduling, the network device sends the DCI that schedules the new uplink data to implicitly receive the correct reception of the uplink data, so that the terminal device may not be able to know in time whether the uplink data is correctly received by the network device. That is, there is a large delay in the feedback of the network device to the uplink data.

The embodiment of the present application subtly proposes a data transmission method, which can provide timely feedback of uplink data by sending control information (for example, DCI), and can send control information without waiting for data scheduling, thereby reducing network equipment's uplink data. Feedback delay.

Hereinafter, for ease of understanding and explanation, the execution process and actions of the data transmission method in the present application in the communication system will be described by way of example and not limitation.

Specifically, the method shown in FIG. 2 includes:

210. The terminal device sends uplink data.

Accordingly, the network device receives the uplink data.

For example, the network device first generates downlink control information for uplink data scheduling, for example, second downlink control information, where the second downlink control information is used by the network device to schedule a physical uplink shared channel. Then, the network device sends the second downlink control information to the terminal device, and after acquiring the second downlink control information, the terminal device sends the uplink data to the network device according to the second downlink control information.

220. The network device sends first downlink control information to the terminal device.

The first bit of the first downlink control information has a value of 1, and the number of the first bit is greater than or equal to 1. The first bit is used to indicate that the first downlink control information is used. Instructing the network device to acknowledge or negatively acknowledge the uplink data.

Correspondingly, the terminal device receives the first downlink control information.

Specifically, the terminal device sends uplink data to the network device, and the network device receives the uplink data, and sends, to the terminal device, first downlink control information with a first bit value of 1. The terminal device receives the downlink control information sent by the network device, and determines that the downlink control information is the first downlink control information according to the first bit of the downlink control information, and further determines the first downlink control according to the first downlink control. The information determines whether the network device correctly receives the uplink data.

For example, the network device may send the first downlink control information by using a physical downlink channel, where the physical downlink channel may be a PDCCH or an MPDCCH, and the embodiment of the present application is not limited thereto.

It should be understood that, in the embodiment of the present application, the first downlink control information may also be referred to as downlink control information for feedback, where the first downlink control information indicates that the first downlink control is performed by using a first bit value of 1. The information is used to indicate a positive response or a negative response of the network device to the uplink data.

The second downlink control information is control information of the data scheduling, and the value of the at least one bit of the first bit in the second downlink control information is 0.

Specifically, when the value of the first bit is 1, the terminal device may determine that the received downlink control information is the first downlink control information for feedback, where the value of the first bit is not all one, that is, the first When the value of at least one bit in the bit is 0, the terminal device may determine that the downlink control information is the second downlink control information used for data scheduling.

Optionally, the format of the first downlink control information may be the same as the format of the second downlink control information, for example, 6-0B.

Optionally, in another embodiment, the number of bits of the first downlink control information is equal to the number of bits of the second DCI, and the location of the first bit of the first downlink control information and the DCI of the scheduling data. The position of the first bit is the same.

It should be understood that, since the format of the first downlink control information and the second downlink control information of the data scheduling are the same, the terminal device needs to distinguish whether the acquired control information is feedback control information or data scheduling control information.

First, in order to make the method for data transmission in this document easy to understand, the format of the downlink control information of the scheduling data, that is, the format of the second downlink control information DCI in the embodiment of the present application is first introduced in conjunction with Table 1 to Table 3. It should be understood that, in this document, DCI is used as an abbreviation of downlink control information, but the downlink control information of the present application is not limited thereto.

In the case of coverage enhancement mode B (CE mode B), the information included in the second DCI is as shown in Tables 1 to 3. The format of the second DCI of Table 1 is 6-0B. The format of the second DCI of Table 2 and Table 3 may be 6-0B, or may not be 6-0B.

Table 1

Table 1 shows the DCI format 6-0B a second DCI containing domain and the number of bits contained in each domain. The field included in the DCI format 6-0B includes the distinguishing flag bits of 6-0B and 6-1B, and the field for indicating resource block allocation, modulation and coding mode MCS, repetition number, HARQ process number, NDI, and DCI subframe repetition number. .

Table 2

Table 2 shows the fields contained in another second DCI and the number of bits contained in each field. The domain included in the DCI includes a DCI format for scheduling the PDSCH and a flag for the DCI format for scheduling the PUSCH, and a field for indicating the MCS and resource allocation, the number of repetitions, the HARQ process number, the NDI, and the number of DCI subframe repetitions. M is a positive integer. Optional, M is greater than

Optional,

or

table 3

Table 3 shows another domain included in the second DCI and the number of bits contained in each domain. The DCI includes a domain that includes a DCI format for scheduling a PDSCH and a flag for a DCI format for scheduling a PUSCH, a resource allocation for a narrowband indication and a narrowband, an MCS, a repetition number, a HARQ process number, an NDI, and a DCI subframe repetition number. area. N is a positive integer. Optional, N is greater than

The differences between Table 1, Table 2, and Table 3 are described below.

The granularity of resources allocated by resource block allocation in Table 1 is PRB, where, in Table 1,

The bits are used to indicate the assigned narrowband and 3 bits are used to indicate the physical resource blocks allocated in the narrowband.

In Table 2, the MCS and resources are assigned as one domain. In the second DCI indicating the resource allocation of the PUSCH, the MCS, and the like, the value of the MCS and the resource allocation bit indicates the MCS used by the PUSCH and the allocated resource. The value of the MCS and the allocated bits of the resource may be jointly encoded by the MCS used by the PUSCH and the allocated resources.

Optionally, the resources allocated by the MCS and the resource allocation bits for the PUSCH may be resources of S subcarriers, and S is a positive integer of <12. The MCS and resource allocated bits may indicate resources allocated for the PUSCH in units of PRBs, and may also indicate resources allocated for the PUSCH in units of one or more subcarriers. The resources allocated by the MCS and the resource allocation bits for the PUSCH may be resources allocated within the entire system bandwidth; or may be included in the MCS and resource allocation bits.

The bits are used for the narrow band of indication, and the remaining bits indicate the resources allocated within the narrow band.

In Table 3, the number of bits in the resource allocation field is N, where the number of Ns may be pre-configured by the system or calculated. The embodiment of the present application does not limit the value of N. For example, N may be

and many more.

The resource allocated for the PUSCH indicated by the bit of the resource allocation in the DCI may be a resource of S subcarriers, and S is a positive integer of <12. The resource allocation bits in the DCI may indicate resources allocated for the PUSCH in units of PRBs, and may also indicate resources allocated for the PUSCH in units of one or more subcarriers. Alternatively, the resource allocated bits are bits that only support the allocation of resources for the PUSCH in units of one or more subcarriers. The resource allocated for the PUSCH indicated by the bit of the resource allocation may be a resource allocated within the entire system bandwidth, or may be included in the bit allocated by the resource.

The bits are used for the narrow band of indication, and the remaining bits indicate the resources allocated within the narrow band. .

It should be noted that, in the second DCI shown in Tables 1 to 3 above, the values of the bits have invalid values. A value of a bit is an invalid value. In the second DCI, the value of the bit is not the value. The value of the bit is the binary value of the bit, or the value of the bit. For example, in Table 1, among the 16 kinds of 16-bit value states of the MCS, only 11 kinds of value states are valid states having actual meanings. The 4-digit representation of the MCS is the index I _{MCS of the MCS} . I _MCS >10 is an invalid value for the BL/CE UE of CE mode B.

For example, in Table 2, the values of the bits allocated by the MCS and the resource all are "1", which is a meaningless invalid value state.

For example, in Table 3, the value of the bit allocated by the resource is all "1", which is a meaningless invalid value state.

It should be understood that, in practical applications, the value of the bit existing in the second DCI used for data scheduling is not the above invalid value. Therefore, the embodiment of the present application proposes that the bit is used as the first bit, so that the value of the first bit of the first DCI is all one, and the value of the first bit in the second DCI is all the value of the invalid value. . In this way, the terminal device determines that the acquired DCI is the first DCI by using all the first bits, and the first bit is not all 1, and then determines that the acquired DCI is the second DCI. The first bit may be all bits or partial bits of the domain of the DCI.

Optionally, corresponding to Table 1, the first bit of the second downlink control information may be part or all of the bits used to indicate the modulation and coding mode.

Specifically, in a design of the embodiment of the present application, in order to enable the first downlink control information in the embodiment of the present application to be distinguished from the second downlink control information used for scheduling, The second downlink control information is used to indicate the 4 bits or partial bits of the MCS as the first bit. As long as the value of the first bit is 1, the value of the 4 bits of the MCS may be greater than 10.

Specifically, when the value of the 4 bits of the MCS is 1011, 1100, 1101, 1110, and 1111, the value is invalid, that is, in the second downlink control information of the data scheduling, the 4 bits of the MCS are taken. The value will not equal the above value. Therefore, in the embodiment of the present application, when the first bit is taken as 1, the value of the four bits can be ensured to be greater than 10. The first bit can be used to indicate that the downlink control information is used to indicate the positive response to the uplink data. Or negating the first downlink control information received by the response.

Optionally, in an implementation manner, for example, the first bit includes 4 bits, in this case, in the first DCI, the first bit takes a value of 1111; in the second DCI, the second DCI The first bit is used to indicate the MCS.

Optionally, the first bit may include a part of the bits in the second DCI for indicating the MCS, for example, the first bit includes the first two bits in the second DCI for indicating the MCS (also It can be referred to as two bits of the upper bit, that is, in the case where the first two bits are 1, the value of 11 bits of the bit for indicating the MCS is 11xx, where x can take 0 or 1 .

Optionally, the first bit may comprise three bits, for example comprising the first two of the four bits of the second DCI for indicating the bits of the MCS, and any one of the remaining bits. Alternatively, the first bit includes a first bit and a third and fourth bit of the second DCI for indicating the MCS.

Optionally, as another embodiment, corresponding to Table 2, the first bit of the second downlink control information may be all bits or partial bits of a field for indicating resource allocation and modulation and coding mode.

Optionally, as another embodiment, as shown in Table 3, the first bit of the second downlink control information is all bits or partial bits of the domain used to indicate resource allocation.

Further, as another embodiment, the number of the first bits is 9 or 11; or, the number of the first bits is greater than

Or, the number of the first bits is

Optionally, as an embodiment, in 220, the first downlink control information is only used to indicate a positive response to the uplink data, and the first downlink control information further includes a hybrid automatic repeat request (HARQ process). The number indication bit, the HARQ process number indication bit is used to indicate a HARQ process corresponding to the uplink data.

Optionally, in the bits of the first downlink control information, except for the existing padding bits, the first bit, a downlink control information format used to distinguish the scheduled physical downlink shared channel, and a downlink for scheduling the physical uplink shared channel. In addition to the flag bits of the control information format and the HARQ process number indication bits, the remaining bits are reserved bits, or all values are 1, or the values are all 0.

Optionally, when the network device needs to send an ACK to the uplink data, the first DCI is used to indicate that the uplink data is correctly received, that is, an acknowledgement of the network device. When the network device needs to feed back NACK for the uplink data receiving error, the network device may retransmit the uplink data by using the NDI bit in the existing manner, that is, implicitly feedback the uplink data error receiving through the NDI bit, at this time in the DCI. The first bit is not all ones. When the terminal device receives the DCI, if the first bit in the DCI is detected to be 1, the UE considers that the DCI indicates an ACK, that is, the uplink data of the HARQ process for which the UE is correctly received by the network device.

Specifically, the first downlink control information may include, in addition to the first bit, a downlink control information format for scheduling the physical downlink shared channel and a downlink control information format for scheduling the physical uplink shared channel, and the HARQ. The process number indicates the bit. In the first downlink control information, padding bits may or may not be included. The padding bit is used to expand the number of bits included in the first downlink control information, so that the number of bits included in the first downlink control information reaches a target value. When the first downlink control information includes padding bits, the number of padding bits existing in the bits of the first downlink control information is greater than zero. When the first downlink control information does not include padding bits, the number of padding bits existing in the bits of the first downlink control information is 0. In the downlink control information, the format of the downlink control information format for scheduling the physical downlink shared channel and the downlink control information format for scheduling the physical uplink shared channel are 0, which generally indicates that the format of the downlink control information is scheduling physical uplink sharing. The downlink control information format of the channel; the downlink control information format used to distinguish the physical downlink shared channel and the downlink control information format of the physical uplink shared channel are set to 1, which generally indicates that the format of the downlink control information is the scheduling physical downlink. The downlink control information format of the shared channel. In the first downlink control information, a flag for distinguishing between a downlink control information format for scheduling the physical downlink shared channel and a downlink control information format for scheduling the physical uplink shared channel is 0. In addition, the remaining bits included in the first downlink control information may be reserved bits, and may all have a value of 1 or a value of 0, which is not limited in this embodiment of the present application. For the number of the remaining bits included in the first downlink control information, the embodiment of the present application does not limit this.

For the content of the second DCI shown in Tables 1 to 3 above, the case where the first DCI is used only for indicating the ACK is described in conjunction with Tables 4 to 6.

Table 4

table 5

Table 6

Table 4 - Table 6 is a possible implementation manner of the first DCI and the second DCI in the embodiment of the present application. The first DCI is used to indicate a positive response of the network device to the uplink data. The domain included in the first DCI may be the same as the domain included in the second DCI, or may be different from the domain included in the second DCI or have a different name. The number of bits of the second DCI is the same as the number of bits of the first DCI. The bits of the second DCI correspond to the bits of the first DCI. Table 4 - Table 6 shows the values of the bits of each field in the second DCI in the first DCI. The distinguishing flag bit of the DCI formats 6-0B and 6-1B is 0, indicating that the format of the DCI is 6-0B. Or distinguish between the DCI format for scheduling the PDSCH and the flag for the DCI format for scheduling the PUSCH to be 0. The case where the first bit is the MCS field is shown in Table 4, and the case where the first bit is the all bits or partial bits of the MCS and the resource allocation field is shown in Table 5, and the first bit is shown as a resource in Table 6. The case where all bits or partial bits of a domain are allocated. And the first bit, all ones. In the first DCI and the second DCI, the field for indicating the HARQ process number includes one HARQ process number indication bit. It should be understood that, in the foregoing Tables 4 to 6, in the bits of the first downlink control information, except for the existing padding bits, the first bit, and the downlink control information format used to distinguish the scheduled physical downlink shared channel. And the flag bits of the downlink control information format and the HARQ process number indication bit of the physical uplink shared channel are scheduled, and the remaining bits are reserved bits, or all values are 1, or the values are all 0.

After the network device sends the DCIs in Tables 4 to 6 to the terminal device, the terminal device may first determine that the distinguishing flag bits of 6-0B and 6-1B in the DCI are 0 or distinguish the DCI format and the scheduling PUSCH of the scheduling PDSCH. The flag bit of the DCI format is 0, and according to the first bit being 1, the DCI is determined to be the first DCI, that is, the DCI used for feedback, because the first DCI is sent by the network device when the uplink data is correctly received. The terminal device can directly determine, according to the first DCI, that the network device has correctly received the uplink data, and does not need to indicate by using the feedback indication bit.

It should be understood that, in the foregoing Tables 4 to 6, in the bits of the first downlink control information, except for the existing padding bits, the first bit, and the downlink control information format used to distinguish the scheduled physical downlink shared channel. And the flag bits of the downlink control information format and the HARQ process number indication bit of the physical uplink shared channel are scheduled, and the remaining bits are reserved bits, or all values are 1, or the values are all 0.

The remaining bits in one of the embodiments DCI take a value of '1'.

Another embodiment is that the remaining bits are set to all '0'. The embodiments of the present application are not limited thereto.

Alternatively, as an embodiment, in 220, the first downlink control information further includes a feedback indication bit, where the feedback indication bit is used to indicate that the network device acknowledges or negatively responds to the uplink data. .

It should be understood that, in a case where the first downlink control information only indicates an acknowledgement to the uplink data, the first downlink control information may not carry a feedback indication bit, or feedback exists in the first downlink control information. Indication bit, However, the feedback indication bits have a value of 0 or both. The first downlink control information needs to include a feedback indication bit, where the first downlink control information is used to indicate a positive response or a negative response to the uplink data, where the feedback indication bit is specifically used to indicate a location of the network device. The feedback of the uplink data is a positive acknowledgement ACK or a negative acknowledgement NACK.

Further, as another optional embodiment, the uplink data includes uplink data corresponding to N HARQ processes, the number of the feedback indication bits is N, and the N bits of the feedback indication bit are used to indicate The network device acknowledges or negatively acknowledges the uplink data corresponding to the N HARQ processes, and N is an integer greater than 1.

Specifically, the first downlink control information may be used for feedback whether the uplink data corresponding to one HARQ process is correctly received, or may be fed back for whether the uplink data corresponding to multiple HARQ processes is correctly received. In the case that the first downlink control information is fed back for the correct reception of the uplink data corresponding to the N HARQ processes, the number of the feedback indication bits included in the first downlink control information is N, and one bit corresponds to one HARQ process. . In this way, the network device can feed back the uplink data corresponding to the multiple HARQ processes to the terminal device in a downlink control information, so as to reduce the feedback overhead of the network device and improve the feedback efficiency of the network device.

Alternatively, as an embodiment, N=2.

In the normal case of CE mode B, there are at most two HARQ processes corresponding to the uplink data. The number of the feedback indication bits is 2, and the 2 bits of the feedback indication bit are respectively used to indicate an acknowledgement or a negative response of the network device to the uplink data corresponding to the 2 HARQ processes.

Further, in the foregoing embodiment, in the first downlink control information,

The remaining bits are included in addition to the padding bits, the first bit, the downlink control information format for scheduling the physical downlink shared channel, and the flag of the downlink control information format for scheduling the physical uplink shared channel, and the feedback indication bit. Is a reserved bit, or a value of 1, or a value of 0; or

In addition to the existing padding bits, the first bit, a downlink control information format for distinguishing the scheduled physical downlink shared channel, and a flag bit for scheduling the downlink control information format of the physical uplink shared channel, the feedback indication bit, and the indication bit In addition to the bits of the scheduling information of the transmitted uplink data, the remaining bits are reserved bits, or all of the values are 1, or all values are 0, wherein the bits for indicating the scheduling information of the retransmitted uplink data include A bit indicating at least one of the following information:

As an optional embodiment, the number of the feedback indication bits is 1, the first downlink control information further includes a HARQ process number indication bit, and the HARQ process number indication bit is used to indicate that the uplink data corresponds to The HARQ process.

Specifically, when the first downlink control information is used to feed back the uplink data corresponding to the one HARQ process, the first downlink control information may further carry a HARQ process number indication bit, which is used to indicate the current feedback. The corresponding HARQ process. When the first downlink control information is used to feed back the receiving situation of the uplink data corresponding to the multiple HARQ processes, the network device and the terminal device may determine, according to a predetermined rule, each feedback indication bit in the first control information and the The one-to-one correspondence between the uplink data of each of the plurality of HARQ processes, or the one-to-one correspondence between the network devices and the terminal device. After receiving the first downlink control information, the terminal device may directly determine the feedback indication bit corresponding to the uplink data of each HARQ process in the multiple HARQ processes according to the one-to-one correspondence, and according to the The feedback indication bit determines the corresponding number of uplinks According to whether it is correctly received by the network device.

a flag bit, a first control bit, a downlink control information format for scheduling a physical downlink shared channel, and a downlink control information format for scheduling a physical uplink shared channel, the feedback indication bit, and the HARQ process. In addition to the number indication bit, the remaining bits are reserved bits, or all values are 1, or the value is 0; or

In addition to the existing padding bits, the first bit, a downlink control information format for distinguishing the scheduled physical downlink shared channel, and a flag bit for scheduling the downlink control information format of the physical uplink shared channel, the feedback indication bit, for indicating The bits of the scheduling information of the transmitted uplink data and the HARQ process number indication bits, the remaining bits are reserved bits, or all values are 1, or all values are 0, wherein the information is used to indicate retransmission. The bits of the scheduling information of the uplink data include bits for indicating at least one of the following:

As an optional embodiment, the feedback indication bit is in the bit of the first downlink control information, except for the existing padding bit, the first bit, and downlink control for distinguishing the scheduled physical downlink shared channel. The information format and the flag bits of the downlink control information format for scheduling the physical uplink shared channel and the multiple bits other than the hybrid automatic repeat request HARQ process number indication bit.

Optionally, the multiple bits are in the bits of the first downlink control information, except for the existing padding bits, the first bit, and the downlink control information format and scheduling used to distinguish the scheduled physical downlink shared channel. The flag of the downlink control information format of the physical uplink shared channel and all bits except the hybrid automatic repeat request HARQ process number indication bit.

The HARQ process number indication bit is used to indicate a HARQ process corresponding to the uplink data. Optionally, the value of the feedback indication bit is 1 for indicating a positive response to the uplink data, and the value of the feedback indication bit is 0 for indicating a negative response to the uplink data. Optionally, the value of the feedback indication bit is 0 to indicate a positive response to the uplink data, and the value of the feedback indication bit is 1 to indicate a negative response to the uplink data. The number of the feedback indication bits is greater than one, and is used to indicate an acknowledgement or a negative response to the uplink data corresponding to the HARQ process indicated by the HARQ process number indication bit. The values of the respective bits of the feedback indication bit are the same.

For the contents of the second DCI shown in Tables 1 to 3 above, the bit values of the first DCI for indicating ACK or NACK are described in conjunction with Tables 7 to 10, wherein the feedback is included in Tables 7 to 10. Indicates a bit, and the feedback indication bit is 1 bit, that is, a case corresponding to uplink data feedback for one HARQ process.

Table 7

Table 8

Table 9

Table 10

Table 7 - Table 10 is a possible implementation manner of the first DCI and the second DCI in the embodiment of the present application. The first DCI is used to indicate a positive or negative response of the network device to the uplink data. The domain included in the first DCI may be the same as the domain included in the second DCI, or may be different from the domain included in the second DCI or have a different name. The number of bits of the second DCI is the same as the number of bits of the first DCI. The bits of the second DCI correspond to the bits of the first DCI. Table 7 - Table 10 shows the values of the bits of each field in the second DCI in the first DCI. The distinguishing flag bit of the DCI formats 6-0B and 6-1B is 0, indicating that the format of the DCI is 6-0B. Or distinguish between the DCI format for scheduling the PDSCH and the flag for the DCI format for scheduling the PUSCH to be 0. Table 7 and Table 8 show the case where the first bit is the MCS field, and Table 9 shows the case where the first bit is the all bits or partial bits of the MCS and the resource allocation field, and the first table is shown in Table 10. The bit is the case where all bits or partial bits of the domain are allocated to the resource. And the first bit, all ones. In the first DCI and the second DCI, the field for indicating the HARQ process number includes one HARQ process number indication bit.

Table 7 to Table 10 further include a bit feedback indication bit, and the feedback indication bit may be a padding bit existing, a first bit, a downlink control information format used to distinguish the scheduled physical downlink shared channel, and a scheduling physical uplink. A flag bit of a downlink control information format of the shared channel, and any one of bits other than the bit indicating the HARQ process number. For example, the feedback indication bit in Table 7 is the upper one bit in the resource block allocation field, and one bit in the NDI field in Table 8 to Table 10. It should be understood that, in Tables 7 to 10, in addition to the existing padding bits, the first bit, the downlink control information format for distinguishing the scheduled physical downlink shared channel, and the flag of the downlink control information format for scheduling the physical uplink shared channel, In addition to the bit indicating the HARQ process number and the feedback indication bit, the remaining bits are reserved bits, or all values are 1, or all values are 0.

Optionally, in an embodiment, the remaining bits in the DCI take a value of '1'.

In another embodiment, the remaining bits in the DCI take a value of '0'.

It should be noted that, in Tables 7 to 10, the case where the remaining bits are reserved bits, or the value is all 1, or the value is 0 is described.

However, embodiments of the present application are not limited thereto.

The first DCI in the embodiment of the present application may be used to schedule the terminal device to retransmit the uplink data, when the feedback bit of the first DCI is fed back to the NACK. Therefore, the first downlink control information may further include a bit for indicating scheduling information of the retransmitted uplink data, but the embodiment of the present application does not limit this.

That is, in the embodiment of the present application, the padding bits existing in the first DCI, the first bit, the downlink control information format used to distinguish the scheduled physical downlink shared channel, and the downlink control information for scheduling the physical uplink shared channel The flag of the format, the feedback indication bit, the bit indicating the HARQ process number, and the bit of the scheduling information for indicating the retransmitted uplink data, the remaining bits are reserved bits, or the values are all 1, or values All are 0, wherein the bit of the scheduling information for indicating the retransmitted uplink data includes a bit for indicating at least one of the following information:

In the embodiment of the present application, when the first DCI is fed back to the NACK, the scheduling retransmission may be further indicated, and the DCI that schedules retransmission is avoided from being sent again, which can save signaling overhead.

After the network device sends the DCIs in Tables 7 to 10 to the terminal device, the terminal device may first determine the distinguishing flag bits of 6-0B and 6-1B in the DCI or distinguish the DCI format of the scheduled PDSCH and the DCI of the scheduled PUSCH. The flag of the format is 0, and according to the first bit is 1, the DCI is determined to be the first DCI, that is, the DCI used for feedback, and finally, the feedback of the network device is determined according to the 1-bit indication corresponding to the feedback indication bit. Is ACK or NACK.

For the contents of the second DCI shown in Tables 1 to 3 above, the bit values of the first DCI for indicating ACK or NACK are described in conjunction with Tables 11 to 13, wherein the feedback is included in Tables 11 to 13. Indicates a bit, and the feedback indication bit is 2 bits, that is, a case corresponding to feedback of uplink data of 2 HARQ processes.

Table 11

Table 12

Table 13

Table 11 - Table 13 are a possible implementation manner of the first DCI and the second DCI in the embodiment of the present application. The first DCI Used to indicate a positive or negative response from the network device to the upstream data. The domain included in the first DCI may be the same as the domain included in the second DCI, or may be different from the domain included in the second DCI or have a different name. The number of bits of the second DCI is the same as the number of bits of the first DCI. The bits of the second DCI correspond to the bits of the first DCI. Table 11 - Table 13 shows the values of the bits of each field in the second DCI in the first DCI. The distinguishing flag bit of the DCI formats 6-0B and 6-1B is 0, indicating that the format of the DCI is 6-0B. Or distinguish between the DCI format for scheduling the PDSCH and the flag for the DCI format for scheduling the PUSCH to be 0. The case where the first bit is the MCS field is shown in Table 11, and the case where the first bit is the all bits or partial bits of the MCS and the resource allocation field is shown in Table 12, and the first bit is shown as a resource in Table 13. The case where all bits or partial bits of a domain are allocated. And the first bit, all ones. In the first DCI, the feedback indication bit includes 2 bits, corresponding to two HARQ process numbers, and the 2 bits of the feedback indication bit are respectively used to indicate the uplink data corresponding to the 2 HARQ processes by the network device. A positive response or a negative response.

The feedback indication bits in Tables 11 to 13 may be a flag other than the existing padding bits, the first bit, a downlink control information format for distinguishing the scheduled physical downlink shared channel, and a downlink control information format for scheduling the physical uplink shared channel. Any two of the bits outside the bit. For example, the feedback indication bits in Table 11 are the upper and the next highest bits in the resource block allocation domain, where the upper 1 bit indicates the ACK feedback or the NACK feedback of the uplink data of the HARQ process #0, and the 1st bit of the next highest bit indicates the HARQ process #1. ACK feedback or NACK feedback of the uplink data. In Table 12, the feedback indication bit is the high order and the next highest bit in the repetition number indication field, wherein the upper 1 bit indicates the ACK feedback or the NACK feedback of the uplink data of the HARQ process #0, and the 1st bit of the next highest bit indicates the HARQ process #1. ACK feedback or NACK feedback of uplink data. In Table 13, the feedback indication bit is the upper and the next highest bit in the DCI subframe repetition number field, wherein the upper 1 bit indicates the ACK feedback or the NACK feedback of the uplink data of the HARQ process #0, and the 1st bit of the next highest bit indicates the HARQ process# 1 ACK feedback or NACK feedback of uplink data. It should be understood that, in Tables 11 to 13, except for the existing padding bits, the first bit, the downlink control information format for distinguishing the scheduled physical downlink shared channel, and the flag of the downlink control information format for scheduling the physical uplink shared channel, and In addition to the feedback indication bit, the remaining bits are reserved bits, or all values are 1, or all values are 0.

In another embodiment, the remaining bits in the DCI take a value of '0'.

It should be noted that, in the foregoing Tables 11 to 13, the case where the remaining bits are reserved bits, or the value is all 1, or the value is 0, the embodiment of the present application is not limited thereto.

That is, in the embodiment of the present application, the padding bits existing in the first DCI, the first bit, the downlink control information format used to distinguish the scheduled physical downlink shared channel, and the downlink control information for scheduling the physical uplink shared channel The flag of the format, the feedback indication bit, and the bit of the scheduling information for indicating the retransmitted uplink data, the remaining bits are reserved bits, or all values are 1, or the value is 0, wherein the The bits of the scheduling information for indicating the retransmitted uplink data include bits for indicating at least one of the following:

After the network device sends the DCI in Table 11 to Table 13 to the terminal device, the terminal device may first determine the The distinguishing flag bits of 6-0B and 6-1B in the DCI or the DCI format of the scheduling PDSCH and the DCI format of the scheduling PUSCH are 0, and then the DCI is determined to be the first DCI according to the first bit being 1. That is, the DCI used for the feedback, and finally, according to the 2-bit indication corresponding to the feedback indication bit, it is determined that the feedback of the uplink data corresponding to the two HARQs by the network device is ACK or NACK.

The content of the bit value when the first DCI is used to indicate ACK or NACK is described below with reference to Tables 14 to 16 for the contents of the second DCI shown in Tables 1 to 3 above. The reference indication bits are included in the table 14 to the table, and the feedback indication bits are multiple bits, and the values of the multiple bits are the same, and the uplink data of one HARQ process is fed back.

Table 14

Table 15

Table 16

Table 14 - Table 16 is a possible implementation manner of the first DCI and the second DCI in the embodiment of the present application. The first DCI is used to indicate a positive or negative response of the network device to the uplink data. The domain included in the first DCI may be the same as the domain included in the second DCI, or may be different from the domain included in the second DCI or have a different name. The number of bits of the second DCI is the same as the number of bits of the first DCI. The bits of the second DCI correspond to the bits of the first DCI. Table 14 - Table 16 shows the values of the bits of each field in the second DCI in the first DCI. The distinguishing flag bit of the DCI formats 6-0B and 6-1B is 0, indicating that the format of the DCI is 6-0B. Or distinguish between the DCI format for scheduling the PDSCH and the flag for the DCI format for scheduling the PUSCH to be 0. The case where the first bit is the MCS field is shown in Table 14, and the case where the first bit is the all bits or partial bits of the MCS and the resource allocation field is shown in Table 15, and the first bit is shown as a resource in Table 16. The case where all bits or partial bits of a domain are allocated. And the first bit, all ones. In the first DCI and the second DCI, the field for indicating the HARQ process number includes one HARQ process number indication bit. In the first DCI, the feedback indication bit is a flag bit in addition to the existing padding bits, the first bit, a downlink control information format for distinguishing the scheduled physical downlink shared channel, and a downlink control information format for scheduling the physical uplink shared channel, and The hybrid automatic repeat request requests all bits except the HARQ process number indication bit. Optionally, the value of the feedback indication bit is 1 for indicating a positive response to the uplink data, and the value of the feedback indication bit is 0 for indicating a negative response to the uplink data. Optionally, the value of the feedback indication bit is 0 to indicate a positive response to the uplink data, and the value of the feedback indication bit is 1 to indicate a negative response to the uplink data. The number of the feedback indication bits is greater than one, and is used to indicate an acknowledgement or a negative response to the uplink data corresponding to the HARQ process indicated by the HARQ process number indication bit. The values of the respective bits of the feedback indication bit are the same.

After the network device sends the DCIs in Tables 14 to 16 to the terminal device, the terminal device may first determine the distinguishing flag bits of 6-0B and 6-1B in the DCI or distinguish the DCI format of the scheduled PDSCH and the DCI of the scheduled PUSCH. The flag of the format is 0, and according to the first bit is 1, the DCI is determined to be the first DCI, that is, the DCI used for feedback, and finally, according to the indication of the feedback indication bit, it is determined that the network device feedback is ACK or NACK. .

It should be noted that the examples of the above embodiments are only intended to help those skilled in the art to understand the embodiments of the present application, and the embodiments of the present application are not limited to the specific numerical values or specific examples illustrated. Those skilled in the art according to the examples given above It is obvious that various equivalent modifications or changes can be made. For example, the above-described Tables 1 to 16 in the embodiments of the present application may be variously modified, split, or combined, and such modifications or variations are also within the scope of the embodiments of the present application.

The data transmission method according to the embodiment of the present application is described in detail above with reference to FIG. 1 to FIG. 2, and the data transmission apparatus according to the embodiment of the present application will be described in detail below with reference to FIG. 3 to FIG.

FIG. 3 is a schematic structural diagram of a terminal device according to an embodiment of the present disclosure. The terminal device can be adapted for use in the system shown in FIG. For the convenience of explanation, FIG. 3 shows only the main components of the terminal device. As shown in FIG. 3, the terminal device 10 includes a processor, a memory, a control circuit, an antenna, and an input and output device. The processor is mainly used for processing the communication protocol and the communication data, and controlling the entire terminal device, executing the software program, and processing the data of the software program, for example, for supporting the terminal device to perform the actions described in the foregoing method embodiments, such as And determining, according to the received downlink control information DCI, a feedback state of the uplink data. Memory is primarily used to store software programs and data. The control circuit is mainly used for converting baseband signals and radio frequency signals and processing radio frequency signals. The control circuit together with the antenna can also be called a transceiver, and is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, keyboards, etc., are primarily used to receive user input data and output data to the user.

After the terminal device is powered on, the processor can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program. When the data needs to be transmitted by wireless, the processor performs baseband processing on the data to be sent, and then outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal, and then sends the radio frequency signal to the outside through the antenna in the form of electromagnetic waves. When data is transmitted to the terminal device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor, which converts the baseband signal into data and processes the data.

Those skilled in the art will appreciate that FIG. 3 shows only one memory and processor for ease of illustration. In an actual terminal device, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, and the like.

As an optional implementation manner, the processor may include a baseband processor and a central processing unit, and the baseband processor is mainly used to process the communication protocol and the communication data, and the central processing unit is mainly used to control and execute the entire terminal device. A software program that processes data from a software program. The processor in FIG. 3 can integrate the functions of the baseband processor and the central processing unit. Those skilled in the art can understand that the baseband processor and the central processing unit can also be independent processors and interconnected by technologies such as a bus. Those skilled in the art will appreciate that the terminal device may include a plurality of baseband processors to accommodate different network standards, and the terminal device may include a plurality of central processors to enhance its processing capabilities, and various components of the terminal devices may be connected through various buses. The baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit can also be expressed as a central processing circuit or a central processing chip. The functions of processing the communication protocol and the communication data may be built in the processor, or may be stored in the storage unit in the form of a software program, and the processor executes the software program to implement the baseband processing function.

In an embodiment of the invention, the antenna and control circuitry having the transceiving function can be considered as the transceiving unit 101 of the terminal device 10, for example, for supporting the terminal device to perform the receiving function as described in the portion of FIG. The processor having the processing function is regarded as the processing unit 102 of the terminal device 10. As shown in FIG. 3, the terminal device 10 includes a transceiver unit 101 and a processing unit 102. The transceiver unit can also be referred to as a transceiver, a transceiver, a transceiver, and the like. Optionally, the device for implementing the receiving function in the transceiver unit 101 can be regarded as a receiving unit, and the device for implementing the sending function in the transceiver unit 101 is regarded as a sending unit, that is, the transceiver unit 101 includes a receiving unit and a sending unit. The receiving unit may also be referred to as a receiver, an input port, a receiving circuit, etc., and the transmitting unit may be referred to as a transmitter, a transmitter, or a transmitting circuit or the like.

The processor 102 can be configured to execute instructions stored in the memory to control the transceiver unit 101 to receive signals and/or transmit signals to perform the functions of the terminal device in the foregoing method embodiments. As an implementation manner, the function of the transceiver unit 101 can be implemented by a dedicated chip through a transceiver circuit or a transceiver.

FIG. 4 is a schematic structural diagram of a network device according to an embodiment of the present disclosure, which may be a schematic structural diagram of a base station. As shown in FIG. 4, the base station can be applied to the system shown in FIG. 1 to perform the functions of the network device in the foregoing method embodiment. The base station 20 includes one or more radio frequency units, such as a remote radio unit (RRU) 201 and one or more baseband units (BBUs) (also referred to as digital units, DUs) 202. . The RRU 201 may be referred to as a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc., which may include at least one antenna 2011 and a radio frequency unit 2012. The RRU 201 part is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals and baseband signals, for example, for transmitting DCI to a terminal device. The BBU 202 part is mainly used for performing baseband processing, controlling a base station, and the like. The RRU 201 and the BBU 202 may be physically disposed together or physically separated, that is, distributed base stations.

The BBU 202 is a control center of a base station, and may also be referred to as a processing unit, and is mainly used to perform baseband processing functions such as channel coding, multiplexing, modulation, spread spectrum, and the like. For example, the BBU (processing unit) can be used to control the base station to perform an operation procedure about the network device in the foregoing method embodiment.

In an example, the BBU 202 may be composed of one or more boards, and multiple boards may jointly support a single access standard radio access network (such as an LTE network), or may separately support different access modes of wireless. Access network (such as LTE network, 5G network or other network). The BBU 202 also includes a memory 2021 and a processor 2022. The memory 2021 is used to store necessary instructions and data. For example, the memory 2021 stores the correspondence relationship between the indication information and the combination information in the above embodiment and the like. The processor 2022 is configured to control the base station to perform necessary actions, for example, to control the base station to perform an operation procedure about the network device in the foregoing method embodiment. The memory 2021 and the processor 2022 can serve one or more boards. That is, the memory and processor can be individually set on each board. It is also possible that multiple boards share the same memory and processor. In addition, the necessary circuits can be set on each board.

FIG. 5 is a schematic structural diagram of a communication device 500. The device 500 can be used to implement the method described in the foregoing method embodiments. For details, refer to the description in the foregoing method embodiments. The communication device 500 can be a chip, a network device (such as a base station), a terminal device or other network device, and the like.

The communication device 500 includes one or more processors 501. The processor 501 can be a general purpose processor or a dedicated processor or the like. For example, it can be a baseband processor, or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processor can be used to control communication devices (eg, base stations, terminals, or chips, etc.), execute software programs, and process data of the software programs. The communication device may include a transceiver unit for implementing input (reception) and output (transmission) of signals. For example, the communication device can be a chip, and the transceiver unit can be an input and/or output circuit of the chip, or a communication interface. The chip can be used for a terminal or base station or other network device. For another example, the communication device may be a terminal or a base station or other network device, and the transceiver unit may be a transceiver, a radio frequency chip, or the like.

The communication device 500 includes one or more of the processors 501, and the one or more processors 501 can implement the method of the network device or the terminal device in the embodiments shown in FIG. 2.

In one possible design, the communication device 500 includes means for generating downlink control information DCI, and means for transmitting DCI. The function of generating the DCI and the function of transmitting the DCI may be implemented by one or more processors. For example, one or more processors can be generated The DCI is transmitted through a transceiver, or an input/output circuit, or an interface of a chip. For the DCI, refer to the related description in the foregoing method embodiment.

In one possible design, the communication device 500 includes means for receiving downlink control information DCI and means for determining a feedback status of the uplink data based on the DCI. The DCI and how to determine the receiving state of the uplink data are described in the related description in the foregoing method embodiments. The DCI may be received, for example, by a transceiver, or an input/output circuit, or an interface of a chip, and the reception status of the uplink data is determined based on the DCI by one or more processors.

Optionally, the processor 501 can implement other functions in addition to the methods of the embodiments shown in FIG. 2 .

Alternatively, in one design, the processor 501 may also include instructions 503 that may be executed on the processor such that the communication device 500 performs the methods described in the above method embodiments.

In yet another possible design, the communication device 500 can also include circuitry that can implement the functions of the foregoing method embodiments.

In yet another possible design, the communication device 500 can include one or more memories 502 having instructions 504 stored thereon that can be executed on the processor such that the communication device 500 executes The method described in the above method embodiments. Optionally, data may also be stored in the memory. Instructions and/or data can also be stored in the optional processor. The processor and the memory may be provided separately or integrated.

In yet another possible design, the communication device 500 may further include a transceiver unit 505 and an antenna 506. The processor 501 may be referred to as a processing unit to control a communication device (terminal or base station). The transceiver unit 505 can be referred to as a transceiver, a transceiver circuit, or a transceiver, etc., for implementing the transceiver function of the communication device through the antenna 506.

The embodiment of the present application further provides a communication system including the foregoing network device and one or more terminal devices.

It should be understood that, in the embodiment of the present application, the processor may be a central processing unit ("CPU"), and the processor may also be other general-purpose processors, digital signal processors (DSPs), and dedicated integration. Circuit (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory can include read only memory and random access memory and provides instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory.

The bus system may include a power bus, a control bus, and a status signal bus in addition to the data bus. However, for the sake of clarity, the various buses are labeled as bus systems in the figure.

In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software. The steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware processor, or may be performed by a combination of hardware and software modules in the processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method. To avoid repetition, it will not be described in detail here.

It is also to be understood that the first, second, third, fourth, and various reference numerals are in the

It should be understood that the term "and/or" herein is merely an association relationship describing an associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and A and B exist simultaneously. There are three cases of B alone.

It should be understood that, in the various embodiments of the present application, the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application. The implementation process constitutes any limitation.

Those of ordinary skill in the art will appreciate that the various illustrative logical blocks and steps described in connection with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. achieve. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)) or the like.

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application. It should be covered by the scope of protection of this application. Therefore, the scope of protection of the present application should be determined by the scope of the claims.

Claims

A data transmission method, comprising:

The network device receives uplink data sent by the terminal device;

The network device sends the first downlink control information to the terminal device, where the first bit of the first downlink control information has a value of 1, and the number of the first bits is greater than or equal to 1, The first bit is used to indicate that the first downlink control information is used to indicate that the network device acknowledges or negatively responds to the uplink data.
A data transmission method, comprising:

The terminal device sends uplink data to the network device;

Receiving, by the terminal device, the first downlink control information that is sent by the network device, where the first bit of the first downlink control information has a value of 1, and the number of the first bits is greater than or equal to 1, and The first bit is used to indicate that the first downlink control information is used to indicate that the network device acknowledges or negatively responds to the uplink data.
A data transmission device, comprising:

a receiving unit, configured to receive uplink data sent by the terminal device;

a sending unit, configured to send the first downlink control information to the terminal device, where the first bit of the first downlink control information has a value of 1, and the number of the first bits is greater than or equal to 1, and The first bit is used to indicate that the first downlink control information is used to indicate that the network device acknowledges or negatively responds to the uplink data.
A data transmission device, comprising:

a sending unit, configured to send uplink data to the network device;

a receiving unit, configured to receive the first downlink control information that is sent by the network device, where the first bit of the first downlink control information has a value of 1, and the number of the first bits is greater than or equal to 1, And the first bit is used to indicate that the first downlink control information is used to indicate that the network device acknowledges or negatively responds to the uplink data.
The method according to claim 1 or 2, or the device according to claim 3 or 4, wherein the first downlink control information is only used to indicate an acknowledgement of the uplink data, The first downlink control information further includes a hybrid automatic repeat request HARQ process number indication bit, where the HARQ process number indication bit is used to indicate the HARQ process corresponding to the uplink data.
The method according to claim 5, or the apparatus according to claim 5, wherein in the bits of the first downlink control information, in addition to the existing padding bits, the first bit, Differentiating the downlink control information format for scheduling the physical downlink shared channel and the flag of the downlink control information format for scheduling the physical uplink shared channel and the HARQ process number indication bit, the remaining bits are reserved bits, or all values are 1, or The value is 0.
The method according to claim 1 or 2, or the device according to claim 3 or 4, wherein the first downlink control information further comprises a feedback indication bit, and the feedback indication bit is used to indicate the location A positive or negative response of the network device to the uplink data.
The method according to claim 7, or the device according to claim 7, wherein the uplink data comprises uplink data corresponding to N HARQ processes, and the number of the feedback indication bits is N, and The N bits of the feedback indication bit are respectively used to indicate an acknowledgement or a negative response of the network device to the uplink data corresponding to the N HARQ processes, where N is an integer greater than 1.
The method according to claim 7 or 8, or the device according to claim 7 or 8, wherein in the first downlink control information,

The remaining bits are included in addition to the padding bits, the first bit, the downlink control information format for scheduling the physical downlink shared channel, and the flag of the downlink control information format for scheduling the physical uplink shared channel, and the feedback indication bit. Is a reserved bit, or a value of 1, or a value of 0; or

In addition to the existing padding bits, the first bit, a downlink control information format for distinguishing the scheduled physical downlink shared channel, and a flag bit for scheduling the downlink control information format of the physical uplink shared channel, the feedback indication bit, and the indication bit In addition to the bits of the scheduling information of the transmitted uplink data, the remaining bits are reserved bits, or all of the values are 1, or all values are 0, wherein the bits for indicating the scheduling information of the retransmitted uplink data include A bit indicating at least one of the following information:

Resource allocation, modulation and coding mode, number of repetitions, and number of sub-frame repetitions of downlink control information.
A method according to claim 8 or 9, or a device according to claim 8 or 9, wherein said N is equal to two.
The method according to claim 7, or the device according to claim 7, wherein the number of the feedback indication bits is 1, and the first downlink control information further includes a HARQ process number indication bit, The HARQ process number indication bit is used to indicate a HARQ process corresponding to the uplink data.
The method according to claim 11, or the device according to claim 11, wherein in the bits of the first downlink control information,

a flag bit, a first control bit, a downlink control information format for scheduling a physical downlink shared channel, and a downlink control information format for scheduling a physical uplink shared channel, the feedback indication bit, and the HARQ process. In addition to the number indication bit, the remaining bits are reserved bits, or all values are 1, or the value is 0; or

In addition to the existing padding bits, the first bit, a downlink control information format for distinguishing the scheduled physical downlink shared channel, and a flag bit for scheduling the downlink control information format of the physical uplink shared channel, the feedback indication bit, for indicating The bits of the scheduling information of the transmitted uplink data and the HARQ process number indication bits, the remaining bits are reserved bits, or all values are 1, or all values are 0, wherein the information is used to indicate retransmission. The bits of the scheduling information of the uplink data include bits for indicating at least one of the following:

Resource allocation, modulation and coding mode, number of repetitions, and number of sub-frame repetitions of downlink control information.
The method according to claim 7, or the apparatus according to claim 7, wherein the feedback indication bit is in a bit of the first downlink control information, except for a padding bit that exists, a first bit, a flag for determining a downlink control information format for scheduling the physical downlink shared channel, and a flag for scheduling a downlink control information format of the physical uplink shared channel, and a plurality of bits other than the hybrid automatic repeat request HARQ process number indication bit; And the HARQ process number indication bit is used to indicate the HARQ process corresponding to the uplink data; the value of the feedback indication bit is 1 for indicating an acknowledgement to the uplink data; A value of 0 is used to indicate a negative acknowledgment of the upstream data.
The method according to any one of claims 1 to 5, wherein before the network device receives the uplink data sent by the terminal device, the method further includes:

The network device sends the second downlink control information to the terminal device, where the value of the at least one bit is 0 in the first bit of the second downlink control information, and the second downlink control information is used in the Network device scheduling physics Uplink shared channel;

The network device receives the uplink data sent by the terminal device, including:

The network device receives the uplink data that is sent by the terminal device according to the second downlink control information.
The method according to any one of claims 2 to 5, wherein before the terminal device sends the uplink data to the network device, the method further includes:

Receiving, by the terminal device, the second downlink control information that is sent by the network device, where the value of the at least one bit is 0 in the first bit of the second downlink control information, and the second downlink control information is used for scheduling Physical uplink shared channel;

The terminal device sends uplink data to the network device, including:

The terminal device sends the uplink data to the network device according to the second downlink control information.
The apparatus according to any one of claims 3 or 5 to 13, wherein the transmitting unit is further configured to:

Before the receiving the uplink data sent by the terminal device, sending, by the terminal device, second downlink control information, where at least one bit of the first bit of the second downlink control information is 0, the first The second downlink control information is used to schedule a physical uplink shared channel;

The receiving unit is specifically configured to:

Receiving, by the terminal device, the uplink data that is sent according to the second downlink control information.
The apparatus according to any one of claims 4 or 5 to 13, wherein the transmitting unit is further configured to:

Receiving, by the network device, the second downlink control information that is sent by the network device, where the value of the at least one bit is 0 in the first bit of the second downlink control information, The second downlink control information is used to schedule a physical uplink shared channel;

The sending unit is specifically configured to:

And transmitting, according to the second downlink control information, the uplink data to the network device.
A method according to claim 14 or 15, or a device according to claim 16 or 17, wherein

The number of bits of the first downlink control information is equal to the number of bits of the second downlink control information, and the location of the first bit of the first downlink control information and the first of the second downlink control information The positions of the bits are the same; and/or, the first downlink control information is the same as the format of the second downlink control information.
The method of any of claims 14-15 or 18, or the device of any of claims 16-18, wherein

The first bit of the second downlink control information is a bit used to indicate a modulation and coding mode; and/or,

The number of the first bits is 4.
The method of any of claims 14-15 or 18, or the device of any of claims 16-18, wherein

The first bit of the second downlink control information is all bits or partial bits of the domain used to indicate resource allocation; or

The first bit of the second downlink control information is all bits or partial bits of a field for indicating resource allocation and modulation and coding mode.
The method of claim 20, or the apparatus of claim 20, wherein

The resource of the physical uplink shared channel indicated by the first bit first state of the second downlink control information is a resource of less than 12 subcarriers.
The method according to claim 20 or 21, or the device according to claim 20 or 21, characterized in that

The number of the first bits is 9 or 11; or,

The number of the first bits is greater than
or,

The number of the first bits is
among them,
Indicates the number of physical resource blocks included in the uplink system bandwidth.
The apparatus of any one of claims 1-2, or 5-15, or 18-22, or the apparatus of any of claims 3-13, or 16-22, wherein The flag of the downlink control information format for scheduling the physical downlink shared channel and the downlink control information format for scheduling the physical uplink shared channel are 0 in the bit of the first downlink control information.
The method according to claim 23, or the device according to claim 23, wherein the downlink control information format for scheduling the physical downlink shared channel and the downlink control information format for scheduling the physical uplink shared channel are The flag bit is a flag bit that distinguishes the control information format 6-0B from the control information format 6-1B.
The apparatus of any of claims 1-2, or 5-15, or 18-24, or the apparatus of any of claims 3-13, or 16-24, wherein The format of the first downlink control information is 6-0B.
A computer readable storage medium, comprising a computer program, when executed on a computer, causing the computer to perform the method of any one of claims 1-2, or 5-15, or 18-25 method.
A computer program product comprising instructions which, when executed on a computer, cause the computer to perform the method of any of claims 1-2, or 5-15, or 18-25.