WO2021035541A1

WO2021035541A1 - Data transmission method and related device

Info

Publication number: WO2021035541A1
Application number: PCT/CN2019/102874
Authority: WO
Inventors: 何朗; 彭振敬; 陈冬明; 杜婷
Original assignee: 华为技术有限公司
Priority date: 2019-08-27
Filing date: 2019-08-27
Publication date: 2021-03-04
Also published as: CN113966637A; CN113966637B

Abstract

Provided in embodiments of the present application are a data transmission method and a related device, the method comprising: a network device receiving a physical uplink shared channel (PUSCH) sent by the terminal device on a pre-allocated first time-frequency resource; sending first downlink control information (DCI) and resource scheduling information to the terminal device, the first DCI being used to indicate whether the PUSCH has been demodulated successfully, and the resource scheduling information being used by the terminal device to schedule a second time-frequency resource to transmit at least one data packet when the PUSCH has been demodulated successfully, or to schedule the second time-frequency resource to retransmit the PUSCH when the PUSCH fails to be demodulated. By using the embodiments of the present application, the utilization rate of network resources can be improved, and the success rate of data transmission can be improved.

Description

A data transmission method and related equipment

Technical field

This application relates to the field of network technology, and in particular to a data transmission method and related equipment.

Background technique

With the rapid development of wireless communication technology, there are more and more wireless communication adaptation services, and the requirements for time delay are getting higher and higher. In order to save time delay, many wireless technologies have proposed no scheduling technology. For example, long-term evolution (LTE) semi-persistent scheduling, fifth-generation mobile communication technology (5-Generation, 5G) grant free, ultra-long range wireless solution (LoRa) and discrete carrier Discrete spectrum aggregation (DSA), etc. all apply non-scheduling technology. However, this technology has a low utilization rate of network resources, and resources of different terminal equipment (user equipment, UE) are prone to collisions, resulting in data transmission failure.

Summary of the invention

This application provides a data transmission method and related equipment, which improves the utilization rate of network resources and improves the success rate of data transmission.

In the first aspect, an embodiment of the present application provides a data transmission method, including: a network device receives a physical uplink shared channel PUSCH sent by a terminal device on a pre-allocated first time-frequency resource; and sends a first downlink control to the terminal device Information DCI and resource scheduling information, the first DCI is used to indicate whether the PUSCH demodulation is successful, the resource scheduling information is used for the terminal equipment to schedule the second time-frequency resource to transmit at least one data packet when the PUSCH demodulation is successful, or demodulate the PUSCH When it fails, the second time-frequency resource is scheduled to retransmit the PUSCH. The terminal device transmits the PUSCH on the pre-allocated time-frequency resources, and the data transmission delay is reduced by adopting a non-scheduling method, and the network device uses the PDCCH for HARQ feedback without increasing the transmission delay. In addition, the resource scheduling information of the next data transmission is indicated while performing HARQ feedback, and the scheduling method is adopted to reduce the probability of uplink resource collision and improve the utilization rate of resources.

In a possible design, the network device can allocate the first time-frequency resource to the terminal device according to the service type of the terminal device, so that the terminal device can send the physical uplink shared channel PUSCH on the pre-allocated first time-frequency resource, Thereby reducing the transmission delay.

In another possible design, the first DCI includes first indication information, and the first indication information is used to indicate that the resource scheduling information is used to schedule the second time-frequency resource to transmit at least one data packet or to retransmit the PUSCH.

In another possible design, the first indication information is a new data indication NDI, and NDI is one bit.

In another possible design, the network device receives at least one data packet sent by the terminal device, and the tail packet in the at least one data packet includes the indicator value of the target field of the protocol data unit PDU, and the indicator value of the target field is used To instruct the network device to determine whether each data packet is successfully received and to generate a status report; send a second DCI to the terminal device, and the second DCI includes the status report. By carrying the indication value of the target field of the PDU in the tail packet, the terminal device does not need to send the Polling packet, thereby saving signaling overhead. And through DCI feedback status report, reduce resource overhead, reduce time delay, and improve network cell rate.

In another possible design, the second DCI further includes confirmation information, which is used to indicate whether the tail packet is successfully demodulated. The DCI is used to feedback whether the tail packet is successfully demodulated, which reduces resource overhead, reduces time delay, and improves network cell rate.

In another possible design, the second DCI further includes second indication information, and the second indication information is used to indicate whether the second DCI includes a status report.

In another possible design, the second indication information is one bit.

In the second aspect, an embodiment of the present application provides a data transmission method, including: a terminal device sends a PUSCH to a network device on a first pre-allocated time-frequency resource; and receives the first downlink control information DCI and resource sent by the network device Scheduling information, the first DCI is used to indicate whether the PUSCH demodulation is successful, and the resource scheduling information is used for the terminal equipment to schedule the second time-frequency resource to transmit at least one data packet when the PUSCH demodulation succeeds, or to schedule the second data packet when the PUSCH demodulation fails Time-frequency resources retransmit PUSCH. The terminal device transmits the PUSCH on the pre-allocated time-frequency resources, and the non-scheduling method is adopted to reduce the transmission delay, and the network device uses the PDCCH for HARQ feedback without increasing the delay. In addition, the resource scheduling information of the next data transmission is indicated while performing HARQ feedback, and the scheduling method is adopted to reduce the probability of uplink resource collision and improve the utilization rate of resources.

In another possible design, the terminal device sends at least one data packet to the network device, and the tail packet in the at least one data packet includes the indicator value of the target field of the protocol data unit PDU, and the indicator value of the target field is used to indicate the network device Determine whether each data packet is successfully received and generate a status report; receive the second DCI sent by the network device, and the second DCI includes the status report. By carrying the indication value of the target field of the PDU in the tail packet, the terminal device does not need to send a Polling packet, thereby saving signaling overhead. And through DCI feedback status report, reduce resource overhead, reduce time delay, and improve network cell rate.

In another possible design, the second indication information is one bit.

In the third aspect, the embodiments of the present application provide a first data transmission device, the first data transmission is configured to implement the methods and functions performed by the network device in the first aspect, and is implemented by hardware/software, and the hardware/software The software includes modules corresponding to the above-mentioned functions.

In a fourth aspect, the embodiments of the present application provide a second data transmission device configured to implement the methods and functions performed by the terminal device in the second aspect described above. The second data transmission device is implemented by hardware/software. /The software includes modules corresponding to the above-mentioned functions.

In a fifth aspect, an embodiment of the present application provides a network device, including: a processor, a memory, and a communication bus, where the communication bus is used to implement connection and communication between the processor and the memory, and the processor executes the program stored in the memory. To achieve the steps of the first aspect above.

In a possible design, the network device provided in this application may include a module corresponding to the behavior of the network device in the above method design. The module can be software and/or hardware.

In a sixth aspect, an embodiment of the present application provides a terminal device, including: a processor, a memory, and a communication bus, where the communication bus is used to implement connection and communication between the processor and the memory, and the processor executes the program stored in the memory. To achieve the steps provided in the second aspect above.

In a possible design, the terminal device provided in this application may include a module corresponding to the behavior of the terminal device in the above method design. The module can be software and/or hardware.

In a seventh aspect, the present application provides a computer-readable storage medium with instructions stored in the computer-readable storage medium, which when run on a computer, cause the computer to execute the methods of the above aspects.

In an eighth aspect, this application provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the methods of the above aspects.

In a ninth aspect, a chip is provided, including a processor, configured to call and execute instructions stored in the memory from the memory, so that a communication device installed with the chip executes the method of any one of the above aspects.

In a tenth aspect, the embodiments of the present application also provide another chip. The chip may be a chip in a network device or a terminal device. The chip includes: an input interface, an output interface, and a processing circuit. They are connected through internal connection paths, and the processing circuit is used to execute any of the above-mentioned methods.

In an eleventh aspect, another chip is provided, including: an input interface, an output interface, a processor, and optionally, a memory. The input interface, output interface, the processor and the memory are connected through an internal connection path, and the processor uses To execute the code in the memory, when the code is executed, the processor is used to execute the method in any of the foregoing aspects.

In a twelfth aspect, a device is provided to implement the method of any one of the above aspects.

Description of the drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background art, the following will describe the drawings that need to be used in the embodiments of the present application or the background art.

FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application;

2 is a schematic diagram of a non-scheduling method for random resource selection provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of a fixed resource non-scheduling method provided by an embodiment of the present application;

FIG. 4 is a schematic flowchart of a data transmission method provided by an embodiment of the present application;

FIG. 5 is a schematic structural diagram of a first data transmission device provided by an embodiment of the present application;

FIG. 6 is a schematic structural diagram of a second data transmission device provided by an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a network device proposed by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a terminal device proposed in an embodiment of the present application.

detailed description

The embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

As shown in FIG. 1, FIG. 1 is a schematic structural diagram of a communication system 100 provided by an embodiment of the present application. The communication system 100 may include a network device 110 and a terminal device 101 to a terminal device 106. It should be understood that the communication system 100 to which the method in the embodiments of the present application can be applied may include more or fewer network devices or terminal devices. The network device or terminal device can be hardware, software that is functionally divided, or a combination of the two. The network device and the terminal device can communicate with other devices or network elements. In the communication system 100, the network device 110 can send downlink data to the terminal device 101 to the terminal device 106. Of course, the terminal device 101 to the terminal device 106 may also send uplink data to the network device 110. The network equipment 110 may be a base station, an access point, a relay node, a base transceiver station (BTS), a node B (nodeB, NB), an evolved node (evolved node B, eNB), or a 5G base station, which refers to the A device in an access network that communicates with a wireless terminal through one or more sectors on the air interface. By converting received air interface frames into IP packets, the network device 110 can act as a router between the terminal device and the rest of the access network, and the access network can include an Internet Protocol network. The network device 110 may also coordinate the management of the attributes of the air interface. The terminal device 101 to the terminal device 106 may be cellular phones, smart phones, portable computers, handheld communication devices, handheld computing devices, satellite radio devices, global positioning systems, handheld computers (personal digital assistants, PDAs) and/or used in wireless Any other suitable devices for communication on the communication system 100 and so on. The communication system 100 can adopt a public land mobile network (PLMN), a device-to-device (D2D) network, a machine-to-machine (M2M) network, and the Internet of things (Internet of things). , IoT) or other networks. In addition, the terminal device 104 to the terminal device 106 may also form a communication system. In this communication system, the terminal device 105 can send downlink data to the terminal device 104 or the terminal device 106. The method in the embodiment of the present application can be applied to the communication system 100 shown in FIG. 1.

No scheduling technology: The UE does not need to send a schedule request (SR) and receive the scheduling information of the physical downlink control channel (PDCCH) sent by the network device. The UE can select pre-allocated time-frequency resources or randomly select The time-frequency resource sends data directly, and the SR request delay and the PDCCH scheduling delay can be saved through the non-scheduling technology. However, since the network equipment is required to allocate time-frequency resources to the UE in advance, when the UE has no service, it is easy to cause a waste of resources and reduce the utilization of network resources. In addition, in order to improve the utilization of network resources, network equipment can allocate different UEs to the same resources. This will introduce a new problem. When different UEs send services at the same time, the time-frequency resources of different UEs are prone to collisions, resulting in different The UE's data transmission failed. The following mainly introduces the specific application scenarios of the non-scheduling technology.

As shown in FIG. 2, FIG. 2 is a schematic diagram of a non-scheduling method for random resource selection according to an embodiment of the present application. The method includes but is not limited to the following steps:

Step 1: When the UE needs to send uplink data, the UE randomly selects time-frequency resources and sends the uplink data through multiple gateways.

Step 2: After multiple gateways receive the uplink data sent by the UE, they directly transmit the uplink data to the network server, and after receiving the uplink data, the network server sends the uplink data to the application server.

Step 3: After the application server receives the uplink data, within the acknowledgement (ACK) information feedback period, the application server selects the gateway with the strongest signal, and sends the confirmation message of the uplink data through the selected network management.

Step 4: In the ACK feedback period, if the UE does not receive the confirmation information sent by the application server, it resends the uplink data. If the confirmation message sent by the application server is received, this data transmission ends.

The above-mentioned LoRa technology is the most typical random resource selection without scheduling technology, which is mainly oriented to the low latency of the Internet of Things. When the UE needs to send uplink data, it randomly selects time-frequency resources and sends the uplink data directly. The UE does not need to send an SR request, the network device does not need to issue scheduling information, and does not need to feed back hybrid automatic repeat request (HARQ) information. In addition, LoRa uses multiple gateways to send at the same time, which improves the success rate of uplink data transmission. However, when the network load increases, the probability of resource collision in UE data transmission increases, and the success rate of data transmission decreases. In addition, LoRa does not have HARQ feedback and retransmission at the media access control (MAC) layer, and the success rate of air interface data transmission is low. Although the probability of resource collision in UE data transmission can be reduced by increasing network resources or reducing the number of network users, this will reduce the utilization of network resources.

As shown in FIG. 3, FIG. 3 is a schematic diagram of a fixed resource non-scheduling method provided by an embodiment of the present application. The method includes but is not limited to the following steps:

Step 1: The network equipment allocates time-frequency resources to the UE, and the time-frequency resources are used for unscheduled data transmission.

Step 2: When the UE needs to send uplink data, the UE sends a physical uplink shared channel (PUSCH) in a pre-allocated time-frequency resource.

Step 3: After receiving the PUSCH sent by the UE, the network device sends downlink control information (DCI) to the UE. The DCI includes ACK/NACK. If the DCI indicates ACK, the network device demodulates the PUSCH successfully. If NACK is indicated, it means that the network device has failed to demodulate the PUSCH, and the UE needs to resend the PUSCH.

Step 4: After the UE receives the DCI, if the DCI indicates an ACK, the UE can send the data packet on the pre-allocated time-frequency resources. If the DCI indicates NACK, the UE needs to retransmit the PUSCH using pre-allocated time-frequency resources.

Step 5: If it is determined that the network device demodulates the PUSCH successfully, the UE starts to send data packets on the PUSCH. After sending the tail packet in the data packet, the Polling packet is sent, and the Polling packet is used to instruct the network device to determine whether each data packet is received and to generate a status report.

Step 6: After receiving the Polling packet sent by the UE, the network device passes the received data packet to the RLC layer, and the RLC layer determines whether each data packet is received and generates a status report.

Step 7: The network device sends a status report to the UE. The status report is used to notify the UE whether the data packet is successfully received. Among them, the feedback mode of the status report is the downlink data transmission mode, which is transmitted on the PDSCH.

The semi-static tuning of LTE, the Grant free technology of 5G, and the non-scheduling technology of DSA are all fixed-resource non-scheduling technologies. The network equipment pre-allocates time-frequency resources of a fixed period and a fixed size to the UE. When the UE needs to send uplink data, it directly sends PUSCH and data packets. For the unscheduled technology of fixed resources, different UEs allocate different unscheduled resources, which will result in low network resource utilization. It is possible to improve resource utilization by allocating different users to the same resource. However, when the network load increases, different users send uplink data on the same resource, which is prone to resource collisions, resulting in data transmission failure.

The above two implementations are data transmission methods without a scheduling mechanism, but both methods have the problem of low network resource utilization, and the resources of different terminal equipment (user equipment, UE) are prone to collisions, resulting in data transmission failure. The following describes a data transmission method for authorized scheduling, including:

Step 1: When the UE needs to send uplink data, it sends an SR request to the network device;

Step 2: The network device sends DCI to the UE, and the DCI is used to indicate information such as time-frequency resources allocated to the UE.

Step 3: The UE sends the PUSCH on the allocated time-frequency resources.

Step 4: After receiving the PUSCH sent by the UE, the network device sends downlink control information (DCI) to the UE. The DCI includes ACK/NACK. If the DCI indicates ACK, the network device demodulates the PUSCH successfully. If NACK is indicated, it means that the network device has failed to demodulate the PUSCH, and the UE needs to resend the PUSCH.

Step 5: After the UE receives the DCI, if the DCI indicates an ACK, the UE can send a data packet on the time-frequency resource allocated above. If the DCI indicates NACK, the UE needs to resend the SR request and resend the PUSCH on the reallocated time-frequency resources.

Step 6: If it is determined that the network device demodulates the PUSCH successfully, the UE starts to send data packets. After sending the tail packet in the data packet, the Polling packet is sent, and the Polling packet is used to instruct the network device to determine whether each data packet is received and to generate a status report.

Step 7: After the network device receives the Polling packet sent by the UE, it passes the received data packet to the RLC layer, and the RLC layer determines whether each data packet is received and generates a status report.

Step 8: The network device sends a status report to the UE, and the status report is used to notify the UE whether the data packet is successfully received. Among them, the feedback mode of the status report is the downlink data transmission mode, which is transmitted on the PDSCH.

For the above-mentioned authorized scheduling data transmission mode, the network device allocates time-frequency resources to the UE only when the UE needs to send uplink data. This can avoid resource waste and will not cause resource collision problems. However, since there is no pre-determining for the UE. To allocate resources, each time uplink data needs to be sent, an SR request must be initiated first, which results in a large scheduling delay. Moreover, after the UE sends the tail packet, it needs to send a Polling packet to request the network device to issue a status report, which consumes network resources.

In order to solve the above technical problems, the embodiments of the present application provide the following solutions.

As shown in FIG. 4, FIG. 4 is a schematic flowchart of a data transmission method provided by an embodiment of the present application. The steps in the embodiment of this application at least include:

S401: The terminal device sends a PUSCH to the network device on the first pre-allocated time-frequency resource, and the network device receives the physical uplink shared channel PUSCH sent by the terminal device on the pre-allocated first time-frequency resource. After the network device receives the PUSCH, it can receive and demodulate the data packet sent by the terminal device on the PUSCH.

Optionally, before the terminal device sends the PUSCH to the network device on the pre-allocated first time-frequency resource, the network device may allocate the first time-frequency resource to the terminal device according to the service type of the terminal device. For terminal devices of different service types, network devices can allocate different time-frequency resources.

S402: The network device sends first downlink control information DCI and resource scheduling information to the terminal device, where the first DCI is used to indicate whether the PUSCH is successfully demodulated, and the resource scheduling information is used for the terminal device When the PUSCH demodulation succeeds, a second time-frequency resource is scheduled to transmit at least one data packet, or when the PUSCH demodulation fails, a second time-frequency resource is scheduled to retransmit the PUSCH.

In specific implementation, after receiving the PUSCH, the network device can perform HARQ feedback on the PDCCH channel, and send the first DCI and resource scheduling information, where the first DCI includes first indication information, and the first indication information is used to indicate all The resource scheduling information is used to schedule the second time-frequency resource to transmit the at least one data packet or retransmit the PUSCH. The resource scheduling information is used to instruct the terminal equipment to schedule time-frequency resources for the next data transmission.

Further, when the first DCI indicates ACK, it indicates that the network device successfully demodulates the PUSCH, the resource scheduling information is used to schedule the second time-frequency resource to transmit the at least one data packet, and S403 is executed. When the first DCI indicates NACK, it indicates that the network device has failed to demodulate the PUSCH, and the terminal device needs to be instructed to resend the PUSCH. The resource scheduling information is used to schedule the second time-frequency resource to retransmit the PUSCH. Wherein, the first indication information is a new data indicator (new data indicator, NDI), and the NDI is one bit. For example, when the bit is "1", it indicates that the PUSCH demodulation is successful, and the terminal device is instructed to schedule the second time-frequency resource to transmit at least one data packet. When the bit is "0", it indicates that the demodulation of the PUSCH fails, and the terminal device is instructed to schedule the second time-frequency resource to retransmit the PUSCH.

S403: The terminal device sends at least one data packet on the second time-frequency resource according to the resource scheduling information, and the network device receives the at least one data packet sent by the terminal device.

Wherein, the tail packet in the at least one data packet includes an indication value of a target field of a protocol data unit (PDU), and the indication value of the target field is used to instruct the network device to determine each of the data Whether the package is successfully received and a status report is generated. For example, the "P" position of the PDU of the radio link control (RLC) layer in the tail packet can be modified to "1". In this way, the terminal device does not need to send Polling packets, thereby saving signaling overhead. After the network device receives the tail packet sent by the terminal device, it first transmits the data packet to the higher layer (such as the RLC layer). The RLC layer of the network device determines that the "P" position of the PDU is "1" and confirms each data packet And generate a status report, and feed the status report back to the media access control (MAC) layer of the network device. Finally, the second DCI is sent through the MAC, and the second DCI includes a status report.

S404: The network device sends a second DCI to the terminal device, and the terminal device receives the second DCI sent by the network device, where the second DCI includes a status report.

Optionally, the MAC layer of the network device may place the confirmation information of the tail packet in the new data indicator (NDI) indicator bit in the second DCI, and the second DCI also includes the confirmation information, so The confirmation information is used to indicate whether the tail packet is successfully demodulated. Among them, the confirmation information can be "0" (NACK) or "1" (ACK). If the feedback confirmation information is ACK, it means that the tail packet demodulation is successful. After the terminal device receives the second DCI, if it is determined that the tail packet is successfully demodulated and each data packet is successfully received, the current data transmission ends. If it is determined that the demodulation of the tail packet fails or the reception of a certain data packet fails, the terminal device can resend the corresponding data packet.

Optionally, the second DCI further includes second indication information, and the second indication information is used to indicate whether the second DCI includes the status report. For example, the second indication information is a bit, such as "0" or "1", where "0" may indicate that the second DCI includes scheduling information for data transmission, and "1" indicates that the second DCI includes status In the report, the contents indicated by "0" and "1" can also be interchanged, which is not limited here. In addition, the remaining bits in the second DCI can be used to indicate the status report, that is, each bit represents whether each data packet is successfully received, for example, "0" indicates that the data packet is received successfully, and "1" indicates that the data packet has failed to be received. .

In the embodiment of the present application, the terminal device transmits the PUSCH on the pre-allocated time-frequency resources, using a non-scheduling manner, which reduces the data transmission delay, and the network device uses the PDCCH for HARQ feedback without increasing the delay. In addition, the resource scheduling information of the next data transmission is indicated while performing HARQ feedback, and the scheduling method is adopted to reduce the probability of uplink resource collision and improve the utilization rate of resources. In addition, adaptive modulation and coding (AMC) adjustments can be performed on resource scheduling information in real time, reducing AMC adjustment duration and radio resource control (radio resource control, RRC) signaling overhead.

The foregoing describes the method of the embodiment of the present application in detail, and the device of the embodiment of the present application is provided below.

Please refer to FIG. 5. FIG. 5 is a schematic structural diagram of a first data transmission device according to an embodiment of the present application. The first data transmission device may include a receiving module 501 and a sending module 502. The detailed description of each module is as follows .

The receiving module 501 is configured to receive the physical uplink shared channel PUSCH sent by the terminal equipment on the pre-allocated first time-frequency resource;

The sending module 502 is configured to send first downlink control information DCI and resource scheduling information to the terminal equipment, where the first DCI is used to indicate whether the PUSCH demodulation is successful, and the resource scheduling information is used for the terminal The device schedules a second time-frequency resource to transmit at least one data packet when the PUSCH demodulation succeeds, or schedules a second time-frequency resource to retransmit the PUSCH when the PUSCH demodulation fails.

Optionally, the sending module 502 is further configured to allocate the first time-frequency resource to the terminal device according to the service type of the terminal device.

Wherein, the first DCI includes first indication information, and the first indication information is used to indicate that the resource scheduling information is used to schedule the second time-frequency resource to transmit the at least one data packet, or to retransmit the PUSCH.

Wherein, the first indication information is a new data indication NDI, and the NDI is one bit.

Optionally, the receiving module 501 is further configured to receive the at least one data packet sent by the terminal device, and the tail packet in the at least one data packet includes the indication value of the target field of the protocol data unit PDU, and the target The indication value of the field is used to instruct the network device to determine whether each of the data packets is successfully received and to generate a status report; the sending module 502 is also used to send a second DCI to the terminal device, and the second DCI includes all State report.

Wherein, the second DCI further includes confirmation information, and the confirmation information is used to indicate whether demodulation of the tail packet is successful.

Wherein, the second DCI further includes second indication information, and the second indication information is used to indicate whether the second DCI includes the status report.

Wherein, the second indication information is one bit.

It should be noted that the implementation of each module can also refer to the corresponding description of the method embodiment shown in FIG. 4 to execute the method and function performed by the network device in the above embodiment.

Please refer to FIG. 6, which is a schematic structural diagram of a second data transmission device provided by an embodiment of the present application. The second data transmission device may include a sending module 601 and a receiving module 602. The detailed description of each module is as follows .

The sending module 601 is configured to send the PUSCH to the network device on the first time-frequency resource allocated in advance;

The receiving module 602 is configured to receive first downlink control information DCI and resource scheduling information sent by the network device, where the first DCI is used to indicate whether the PUSCH demodulation is successful, and the resource scheduling information is used for the The terminal device schedules a second time-frequency resource to transmit at least one data packet when the PUSCH demodulation succeeds, or schedules a second time-frequency resource to retransmit the PUSCH when the PUSCH demodulation fails.

Optionally, the sending module 601 is further configured to send the at least one data packet to the network device, and the tail packet in the at least one data packet includes the indication value of the target field of the protocol data unit PDU, and the target field The indicating value of is used to instruct the network device to determine whether each of the data packets is successfully received and to generate a status report; the receiving module 602 is also used to receive a second DCI sent by the network device, and the second DCI includes all State report.

Wherein, the second indication information is one bit.

It should be noted that the implementation of each module can also refer to the corresponding description of the method embodiment shown in FIG. 4 to execute the methods and functions performed by the terminal device in the foregoing embodiment.

Please continue to refer to FIG. 7, which is a schematic structural diagram of a network device according to an embodiment of the present application. As shown in FIG. 7, the network device may include: at least one processor 701, at least one communication interface 702, at least one memory 703, and at least one communication bus 704.

The processor 701 may be a central processing unit, a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computing functions, for example, a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on. The communication bus 704 may be a standard PCI bus for interconnecting peripheral components or an extended industry standard structure EISA bus. The bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one thick line is used in FIG. 7, but it does not mean that there is only one bus or one type of bus. The communication bus 704 is used to implement connection and communication between these components. Among them, the communication interface 702 of the device in the embodiment of the present application is used for signaling or data communication with other node devices. The memory 703 may include volatile memory, such as nonvolatile random access memory (NVRAM), phase change RAM (PRAM), magnetoresistive random access memory (magetoresistive) RAM, MRAM), etc., may also include non-volatile memory, such as at least one disk storage device, electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), flash memory devices, such as reverse or flash memory (NOR flash memory) or NAND flash memory (NAND flash memory), semiconductor devices, such as solid state disk (SSD), etc. Optionally, the memory 703 may also be at least one storage device located far away from the foregoing processor 701. Optionally, the memory 703 may also store a group of program codes, and the processor 701 may optionally also execute the programs executed in the memory 703.

Receiving the physical uplink shared channel PUSCH sent by the terminal equipment on the pre-allocated first time-frequency resource;

Send first downlink control information DCI and resource scheduling information to the terminal device, where the first DCI is used to indicate whether the PUSCH demodulation is successful, and the resource scheduling information is used by the terminal device to decode the PUSCH on the PUSCH. When the modulation is successful, the second time-frequency resource is scheduled to transmit at least one data packet, or when the PUSCH demodulation fails, the second time-frequency resource is scheduled to retransmit the PUSCH.

Among them, the processor 701 is further configured to perform the following operations:

According to the service type of the terminal device, the first time-frequency resource is allocated to the terminal device.

Receiving the at least one data packet sent by the terminal device, where a tail packet in the at least one data packet includes an indication value of a target field of a protocol data unit PDU, and the indication value of the target field is used to indicate the network device Determining whether each of the data packets is successfully received and generating a status report;

Sending a second DCI to the terminal device, where the second DCI includes the status report.

Wherein, the second indication information is one bit.

Further, the processor may also cooperate with the memory and the communication interface to perform the operation of the network device in the above-mentioned application embodiment.

Please continue to refer to FIG. 8, which is a schematic structural diagram of a terminal device according to an embodiment of the present application. As shown in the figure, the terminal device may include: at least one processor 801, at least one communication interface 802, at least one memory 803, and at least one communication bus 804.

The processor 801 may be various types of processors mentioned above. The communication bus 804 may be a standard PCI bus for interconnecting peripheral components or an extended industry standard structure EISA bus. The bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of presentation, only one thick line is used in FIG. 8, but it does not mean that there is only one bus or one type of bus. The communication bus 804 is used to implement connection and communication between these components. Among them, the communication interface 802 of the device in the embodiment of the present application is used for signaling or data communication with other node devices. The memory 803 may be various types of memories mentioned above. Optionally, the memory 803 may also be at least one storage device located far away from the foregoing processor 801. The memory 803 stores a set of program codes, and the processor 801 executes the programs executed by the above-mentioned OAM in the memory 803.

Sending the PUSCH to the network device on the pre-allocated first time-frequency resource;

Receive first downlink control information DCI and resource scheduling information sent by the network device, where the first DCI is used to indicate whether the PUSCH demodulation is successful, and the resource scheduling information is used for the terminal device to perform the demodulation on the PUSCH When the demodulation succeeds, the second time-frequency resource is scheduled to transmit at least one data packet, or when the PUSCH demodulation fails, the second time-frequency resource is scheduled to retransmit the PUSCH.

Wherein, the processor 801 is further configured to perform the following operations:

The at least one data packet is sent to the network device, and a tail packet in the at least one data packet includes an indication value of a target field of a protocol data unit PDU, and the indication value of the target field is used to instruct the network device to determine Whether each of the data packets is successfully received and a status report is generated;

Receiving a second DCI sent by the network device, where the second DCI includes the status report.

Wherein, the second indication information is one bit.

Further, the processor may also cooperate with the memory and the communication interface to perform the operation of the terminal device in the above-mentioned application embodiment.

The embodiments of the present application also provide a chip system, which includes a processor, which is used to support network equipment or terminal equipment to realize the functions involved in any of the above embodiments, for example, to generate or process the functions involved in the above methods. Data and/or information. In a possible design, the chip system may further include a memory, and the memory is used for necessary program instructions and data for network devices or terminal devices. The chip system can be composed of chips, or include chips and other discrete devices.

The embodiments of the present application also provide a processor, which is configured to be coupled with a memory and used to execute any method and function involving a network device or a terminal device in any of the foregoing embodiments.

The embodiments of the present application also provide a computer program product containing instructions, which when running on a computer, enables the computer to execute any method and function involving a network device or a terminal device in any of the foregoing embodiments.

The embodiments of the present application also provide a device for executing any method and function involving a network device or a terminal device in any of the foregoing embodiments.

An embodiment of the present application also provides a wireless communication system, which includes at least one multi-network device and at least one terminal device involved in any of the foregoing embodiments.

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

The specific implementations described above further describe the purpose, technical solutions, and beneficial effects of the present application in further detail. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included in the protection scope of this application.

Claims

A data transmission method, characterized in that the method includes:

The network device receives the physical uplink shared channel PUSCH sent by the terminal device on the pre-allocated first time-frequency resource;

The network device sends first downlink control information DCI and resource scheduling information to the terminal device, where the first DCI is used to indicate whether the PUSCH demodulation is successful, and the resource scheduling information is used for the terminal device When the PUSCH demodulation succeeds, a second time-frequency resource is scheduled to transmit at least one data packet, or when the PUSCH demodulation fails, a second time-frequency resource is scheduled to retransmit the PUSCH.
The method according to claim 1, wherein before the network device receives the physical uplink shared channel PUSCH sent by the terminal device on the pre-allocated first time-frequency resource, the method further comprises:

The network device allocates the first time-frequency resource to the terminal device according to the service type of the terminal device.
The method according to claim 1 or 2, wherein the first DCI includes first indication information, and the first indication information is used to indicate that the resource scheduling information is used to schedule the second time-frequency resource Transmit the at least one data packet, or retransmit the PUSCH.
The method according to claim 3, wherein the first indication information is a new data indication NDI, and the NDI is one bit.
The method according to any one of claims 1 to 4, wherein after the network device sends downlink control information DCI and resource scheduling information to the terminal device, the method further comprises:

The network device receives the at least one data packet sent by the terminal device, and a tail packet in the at least one data packet includes an indication value of a target field of a protocol data unit PDU, and the indication value of the target field is used to indicate The network device determines whether each of the data packets is successfully received and generates a status report;

The network device sends a second DCI to the terminal device, where the second DCI includes the status report.
The method of claim 5, wherein the second DCI further includes confirmation information, and the confirmation information is used to indicate whether the tail packet is successfully demodulated.
The method according to any one of claims 5 or 6, wherein the second DCI further includes second indication information, and the second indication information is used to indicate whether the second DCI includes the status report .
The method according to claim 7, wherein the second indication information is one bit.
A data transmission method, characterized in that the method includes:

The terminal device sends the PUSCH to the network device on the first time-frequency resource allocated in advance;

The terminal device receives first downlink control information DCI and resource scheduling information sent by the network device, where the first DCI is used to indicate whether the PUSCH demodulation is successful, and the resource scheduling information is used for the terminal device When the PUSCH demodulation succeeds, a second time-frequency resource is scheduled to transmit at least one data packet, or when the PUSCH demodulation fails, a second time-frequency resource is scheduled to retransmit the PUSCH.
The method according to claim 9, wherein the first DCI includes first indication information, and the first indication information is used to indicate that the resource scheduling information is used to schedule the second time-frequency resource transmission. The at least one data packet, or retransmit the PUSCH.
The method according to claim 10, wherein the first indication information is a new data indication NDI, and the NDI is one bit.
The method according to any one of claims 9-11, wherein after the terminal device receives the first downlink control information DCI and resource scheduling information sent by the network device, the method further comprises:

The terminal device sends the at least one data packet to the network device, and the tail packet in the at least one data packet includes the indicator value of the target field of the protocol data unit PDU, and the indicator value of the target field is used to indicate the The network device determines whether each of the data packets is successfully received and generates a status report;

The terminal device receives a second DCI sent by the network device, where the second DCI includes the status report.
The method of claim 12, wherein the second DCI further includes confirmation information, and the confirmation information is used to indicate whether the tail packet is successfully demodulated.
The method according to any one of claims 12 or 13, wherein the second DCI further includes second indication information, and the second indication information is used to indicate whether the second DCI includes the status report .
The method according to claim 14, wherein the second indication information is one bit.
A first data transmission device, characterized in that the device includes:

The receiving module is configured to receive the physical uplink shared channel PUSCH sent by the terminal equipment on the first time-frequency resource allocated in advance;

A sending module, configured to send first downlink control information DCI and resource scheduling information to the terminal device, the first DCI is used to indicate whether the PUSCH demodulation is successful, and the resource scheduling information is used for the terminal device When the PUSCH demodulation succeeds, a second time-frequency resource is scheduled to transmit at least one data packet, or when the PUSCH demodulation fails, a second time-frequency resource is scheduled to retransmit the PUSCH.
The device of claim 16, wherein:

The sending module is further configured to allocate the first time-frequency resource to the terminal device according to the service type of the terminal device.
The apparatus according to claim 16 or 17, wherein the first DCI includes first indication information, and the first indication information is used to indicate that the resource scheduling information is used to schedule the second time-frequency resource Transmit the at least one data packet, or retransmit the PUSCH.
The apparatus according to claim 18, wherein the first indication information is a new data indication NDI, and the NDI is one bit.
The device according to any one of claims 16-19, wherein:

The receiving module is further configured to receive the at least one data packet sent by the terminal device, and the tail packet in the at least one data packet includes the indication value of the target field of the protocol data unit PDU, and the indication of the target field The value is used to instruct the network device to determine whether each of the data packets is successfully received and generate a status report;

The sending module is further configured to send a second DCI to the terminal device, where the second DCI includes the status report.
The apparatus according to claim 20, wherein the second DCI further comprises confirmation information, and the confirmation information is used to indicate whether the tail packet is successfully demodulated.
The apparatus according to any one of claims 20 or 21, wherein the second DCI further comprises second indication information, and the second indication information is used to indicate whether the second DCI includes the status report .
The method according to claim 22, wherein the second indication information is one bit.
A second data transmission device, characterized in that the device includes:

A sending module, configured to send the PUSCH to the network device on the first time-frequency resource allocated in advance;

The receiving module is configured to receive first downlink control information DCI and resource scheduling information sent by the network device, where the first DCI is used to indicate whether the PUSCH demodulation is successful, and the resource scheduling information is used for the terminal The device schedules a second time-frequency resource to transmit at least one data packet when the PUSCH demodulation succeeds, or schedules a second time-frequency resource to retransmit the PUSCH when the PUSCH demodulation fails.
The apparatus according to claim 24, wherein the first DCI includes first indication information, and the first indication information is used to indicate that the resource scheduling information is used to schedule the second time-frequency resource transmission. The at least one data packet, or retransmit the PUSCH.
The apparatus according to claim 25, wherein the first indication information is a new data indication NDI, and the NDI is one bit.
The device according to any one of claims 24-26, wherein

The sending module is further configured to send the at least one data packet to the network device, and the tail packet in the at least one data packet includes the indicator value of the target field of the protocol data unit PDU, and the indicator value of the target field Used to instruct the network device to determine whether each of the data packets is successfully received and to generate a status report;

The receiving module is further configured to receive a second DCI sent by the network device, where the second DCI includes the status report.
The apparatus according to claim 27, wherein the second DCI further comprises confirmation information, and the confirmation information is used to indicate whether the tail packet is successfully demodulated.
The apparatus according to any one of claims 27 or 28, wherein the second DCI further comprises second indication information, and the second indication information is used to indicate whether the second DCI includes the status report .
The device of claim 29, wherein the second indication information is one bit.
A network device, characterized by comprising: a memory, a communication bus, and a processor, wherein the memory is used to store program code, and the processor is used to call the program code to execute any of claims 1-8 The method described in one item.
A terminal device, characterized by comprising: a memory, a communication bus, and a processor, wherein the memory is used to store program code, and the processor is used to call the program code to execute any of claims 9-15 The method described in one item.
A computer-readable storage medium, characterized in that instructions are stored in the computer-readable storage medium, which when run on a computer, cause the computer to execute the method according to any one of claims 1-15.
A computer program product containing instructions, which is characterized in that when it runs on a computer, it causes the computer to execute the method according to any one of claims 1-15.