WO2018192091A1

WO2018192091A1 - Data transmission method and device

Info

Publication number: WO2018192091A1
Application number: PCT/CN2017/089650
Authority: WO
Inventors: 杜振国; 庄宏成
Original assignee: 华为技术有限公司
Priority date: 2017-04-21
Filing date: 2017-06-22
Publication date: 2018-10-25
Also published as: CN109565827A

Abstract

Embodiments of the present application provide a data transmission method and device. The method comprises: a network device receiving uplink data from a terminal device; and the network device determining, according to association information of the uplink data, the redundancy version (RV) of the terminal device and the uplink data, the association information of the uplink data being information related when the terminal device sends the uplink data. The data transmission method and device provided by the embodiments of the present application employ the association information of the uplink data, rather than only relying on pilot resource links to indicate the RV of the terminal device and the uplink data, and thus can avoid the problem that the network device cannot accurately distinguish uplink data from different terminal devices due to a limited number of pilot resource links, resulting in reduced reliability and lower accuracy of data transmissions.

Description

Method and device for data transmission

Technical field

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

Background technique

The Grant-based uplink data transmission method used in the traditional mobile communication system has the problems of large signaling overhead and long transmission delay. To avoid the above problems, in the fifth generation mobile communication system (5 ^th Generation, 5G), there is proposed a no authorization (Grant-free) data transmission based on the uplink. In the unlicensed uplink data transmission mode, the user equipment does not need to request the uplink transmission resource from the base station when there is data to be transmitted, but selects the transmission resource in the pre-configured resource pool to directly perform the uplink data transmission.

Due to the limited transmission resources in the resource pool, different users may select the same resource to transmit uplink data, which may cause data collision, which affects the reliability of data transmission. In order to ensure the reliability of data transmission, a Hybrid Automatic Repeat ReQuest (HARQ) mechanism can be adopted in the uplink data transmission process. In the HARQ mechanism, the user equipment acquires multiple redundancy versions (RVs) of the Transmission Block (TB), for example, as RV0, RV2, RV3, and RV1. The user equipment sends the RV0 of the TB to the base station. If the base station receives the RV0 but the decoding is unsuccessful, the user equipment sends the RV2 of the TB to the base station, and the base station performs the combined decoding according to the received RV0 and RV2 to obtain the data. If the decoding succeeds, the user ends. The HARQ process. If not successful, the user equipment sends the RV3 of the TB to the base station, and the base station combines and decodes RV0, RV2, and RV3. If still unsuccessful, the user equipment sends the RV1 of the TB to the base station.

In the unlicensed uplink data transmission mode, the base station cannot determine in advance which RV of the received data is the TB and the terminal device that transmits the data. Therefore, when the user equipment uses the HARQ mechanism for uplink data transmission, the base station can not only distinguish the RV of the received data, but also cannot determine which user equipment the RV data comes from, which reduces the reliability of data transmission.

Summary of the invention

The embodiment of the present invention provides a data transmission method and device, which are used to solve the problem that the network device in the prior art can not only distinguish the RV of the received data, but also cannot determine which user equipment the RV data comes from, and reduce the data transmission. The issue of reliability.

In a first aspect, an embodiment of the present application provides a data transmission method, including:

The network device receives uplink data from the terminal device;

The network device determines, according to the association information of the uplink data, a redundancy version of the terminal device and the uplink data, where the association information of the uplink data is information related to when the terminal device sends the uplink data.

By using the associated information of the uplink data instead of relying solely on the pilot mapping chain to indicate the RV of the terminal device and the uplink data, it can be avoided that the network device cannot correctly distinguish the uplink from different terminal devices because the number of pilot mapping chains is limited. Data reduces the reliability of data transmission.

In a possible design, the associated information of the uplink data includes the content of the uplink data, or includes the uplink data. At least two of the content, the time-frequency resource block used when transmitting the uplink data, and the pilot corresponding to the uplink data.

In a possible design, the uplink data association information includes a time-frequency resource block used for transmitting the uplink data and a pilot corresponding to the uplink data; and the network device determines the redundancy of the terminal device and the uplink data according to the associated information of the uplink data. The remaining versions include:

The network device determines a redundancy version of the uplink data according to the number of the time-frequency resource block in the associated time-frequency resource mapping chain;

The network device determines the terminal device according to the pilot, and a mapping relationship between the preset pilot and the terminal device in the network device;

The time-frequency resource mapping chain includes at least two time-frequency resource blocks, and different time-frequency resource blocks in the time-frequency resource mapping chain correspond to different redundancy versions of the same uplink data.

The RV carries the identifier in the uplink data, so that the network device can determine the RV of the uplink data according to the RV identifier carried in the uplink data. Since each uplink data itself carries its own corresponding RV, the network device determines that the terminal device and the RV are no longer affected by the small number of pilots, thereby improving the reliability of data transmission.

In a possible design, the association information of the uplink data includes the content of the time-frequency resource block and the uplink data used when the uplink data is sent, and the content of the uplink data carries the identity of the terminal device; and the associated information of the network device according to the uplink data. Determine the redundancy version of the terminal device and uplink data, including:

The network device determines the terminal device according to the identity identifier;

By carrying the identity identifier of the terminal device in the uplink data, the network device can determine the identity identifier for sending the uplink data according to the identity identifier carried in the uplink data. Since each uplink data itself carries its own identity identifier, the network device determines that the terminal device and the RV are no longer affected by the small number of pilots, thereby improving the reliability of data transmission.

In a possible design, the association information of the uplink data includes the content of the time-frequency resource block and the uplink data used when the uplink data is sent, and the content of the uplink data carries the identifier of the terminal device in the associated terminal device group; the network device Determining a redundancy version of the terminal device and the uplink data according to the associated information of the uplink data, including:

The network device determines the terminal device group to which the terminal device belongs according to the time-frequency resource mapping chain to which the time-frequency resource block belongs, and the mapping relationship between the time-frequency resource mapping chain and the terminal device group preset in the network device;

The network device determines the terminal device in the terminal device group according to the identifier of the terminal device in the associated terminal device group;

By binding a time-frequency resource mapping chain to a group of terminal devices, the identifier of the terminal device that can be carried only in the terminal device group in the uplink data, the number of bits used in the identifier is small, and the indication overhead can be saved.

In a possible design, the uplink data association information includes a time-frequency resource block used when transmitting uplink data. a pilot corresponding to the uplink data; the network device determines, according to the associated information of the uplink data, a redundancy version of the terminal device and the uplink data, including:

The network device determines the terminal device in the terminal device group according to the pilot information, the mapping relationship between the preset pilots in the network device and the terminal devices in the terminal device group;

By binding a time-frequency resource mapping chain to a group of terminal devices, terminal devices using different resource mapping chains can have the same pilot, so that the network device can determine the terminal device that transmits the uplink data, and avoid the number of pilots. Limited, the resulting network device can not correctly distinguish data from different user devices, reducing the reliability of data transmission.

In a possible design, the association information of the uplink data includes the content of the pilot data and the uplink data corresponding to the uplink data, and the content of the uplink data carries the identity identifier of the terminal device; the network device determines the terminal device according to the associated information of the uplink data. A redundant version of the upstream data, including:

The network device determines a redundancy version of the uplink data according to the number of the pilot in the associated pilot mapping chain;

The pilot mapping chain includes at least two pilots, and different pilots in the pilot mapping chain correspond to different redundancy versions of the same uplink data.

In a possible design, the uplink data association information includes a time-frequency resource block used for transmitting the uplink data, a content of the uplink data, and a pilot corresponding to the uplink data, and the content carrying terminal device of the uplink data is in the terminal device to which the terminal device belongs. The identifier of the group; the network device determines the redundancy version of the terminal device and the uplink data according to the associated information of the uplink data, including:

The network device determines, according to the time-frequency resource block, the mapping relationship between the preset time-frequency resource block and the terminal device group in the network device, the terminal device group to which the terminal device belongs;

By binding a time-frequency resource block to a group of terminal devices, the identifier of the terminal device that can be carried only in the terminal device group in the uplink data, the number of bits used in the identifier is small, and the indication overhead can be saved.

The network device determines the terminal device in the terminal device group according to the mapping relationship between the pilot mapping chain to which the pilot belongs, the preset pilot mapping chain in the network device, and the terminal device in the terminal device group;

By binding a time-frequency resource block to a group of terminal devices, the terminal devices using different time-frequency resource blocks can have the same pilot mapping chain, so that the network device can determine the terminal device and the uplink data that send the uplink data. RV avoids the limited pilot resources, and the network device cannot correctly distinguish the RV of data and uplink data from different user equipments, which reduces the reliability of data transmission.

In a possible design, the association information of the uplink data includes the content of the uplink data and the pilot corresponding to the uplink data, and the content of the uplink data carries the identifier of the redundancy version of the uplink data; the network device determines according to the association information of the uplink data. Redundant versions of terminal equipment and upstream data, including:

The network device determines a redundancy version of the uplink data according to the identifier of the redundancy version;

The network device determines the terminal device according to the pilot and the mapping relationship between the preset pilot and the terminal device in the network device.

The RV of the uplink data is carried in the uplink data, so that the network device can determine the RV of the uplink data according to the identifier of the RV carried in the uplink data. Since each uplink data itself carries its own RV, the pilot mapping chain is no longer used, so that the network device determines that the terminal device and the RV are no longer affected by the small number of pilot mapping chains, thereby improving the reliability of data transmission. .

In a possible design, the uplink data association information includes a time-frequency resource block used for transmitting the uplink data, a content of the uplink data, and a pilot corresponding to the uplink data, and the content of the uplink data carries a redundant version of the uplink data. The network device determines the redundancy version of the terminal device and the uplink data according to the associated information of the uplink data, including:

Determining, by the network device, the terminal device group to which the terminal device belongs according to the time-frequency resource block and the mapping relationship between the time-frequency resource block and the terminal device group preset in the network device;

The network device determines the terminal device in the terminal device group according to the mapping relationship between the pilot, the preset pilot in the network device, and the terminal device in the terminal device group.

By binding a time-frequency resource block to a group of terminal devices, the terminal devices using different time-frequency resource blocks can have the same pilot, so that the network device can determine the RV of the terminal device and the uplink data that send the uplink data, The number of pilots is limited, and the network device cannot correctly distinguish the RV of data and uplink data from different user equipments, thereby reducing the reliability of data transmission.

In a possible design, the association information of the uplink data includes the content of the uplink data, and the content of the uplink data includes the identifier of the terminal device and the identifier of the redundancy version of the uplink data; the network device determines the terminal according to the association information of the uplink data. Redundant versions of devices and upstream data, including:

The network device determines the terminal device according to the identity identifier.

By carrying the identifier of the terminal device and the identifier of the redundancy version in the uplink data, the network device can determine the RV of the terminal device that sends the uplink data and the uplink data, and the network device that is limited by the limited pilot resources cannot be correctly distinguished from different The uplink data of the user equipment and the RV of the uplink data reduce the reliability of the data transmission.

In a possible design, the uplink data association information includes the time-frequency resource block and the uplink data content used when transmitting the uplink data, and the content of the uplink data carries the identifier of the redundancy version of the uplink data and the terminal device belongs to The identifier in the terminal device group; the network device determines the redundancy version of the terminal device and the uplink data according to the association information of the uplink data, including:

The network device determines the terminal device in the terminal device group according to the identifier of the terminal device in the associated terminal device group.

In a possible design, the uplink data also includes a mixed cyclic redundancy check bit;

The N-bit bit in the hybrid cyclic redundancy check is obtained by X-biting the N-bit bit in the cyclic redundancy check of the uplink data with the N-bit bit in the identity of the terminal device;

Where N is a positive integer.

The N-bit bit in the hybrid cyclic redundancy check is obtained by X-biting the N-bit bit in the cyclic redundancy check of the uplink data with the N-bit in the identifier of the terminal device in the associated terminal device group;

Where N is a positive integer.

In one possible design, the method of data transmission further includes:

The network device determines, according to the association information of the uplink data, a hybrid automatic repeat request process for transmitting the uplink data.

In a possible design, before the network device receives the uplink data from the terminal device, the data transmission method further includes:

The network device establishes a time-frequency resource mapping chain, and sends the time-frequency resource mapping chain to the terminal device;

The different time-frequency resource blocks in the resource mapping chain belong to different contention transmission areas, and the time-frequency resources of the contention transmission areas do not overlap, and the time-frequency resource blocks belonging to the same contention transmission area correspond to the same redundancy version.

In one possible design, the uplink data includes a pilot, a control portion, and a data portion, and the content of the uplink data is the content of the control portion.

In a possible design, the pilot corresponding to the uplink data is used to indicate the modulation and coding mode used by at least one part of the uplink data.

The network device establishes a time-frequency resource mapping chain, a pilot mapping chain, a mapping relationship between a pilot and a terminal device, a mapping relationship between a time-frequency resource mapping chain and a terminal device group, an identifier of each terminal device in each terminal device group, and each terminal device. The mapping relationship between the pilots in the group and the terminal device, the identifier of the terminal device in the associated terminal device group, the pilot mapping chain and the terminal At least one of the mapping relationship of the terminal devices in the device group is sent to the terminal device.

In a second aspect, an embodiment of the present application provides a method for data transmission. The beneficial effects of the methods provided by the various possible designs of the second aspect described below can be seen in the beneficial effects of the various possible designs of the first aspect described above.

In a possible design of the second aspect, the method of data transmission includes:

The terminal device determines uplink data;

The terminal device sends the uplink data to the network device according to the identifier of the terminal device and the redundancy version of the uplink data, so that the network device determines the redundancy version of the terminal device and the uplink data according to the association information of the uplink data, where the uplink data is associated. The information is information related to when the uplink data is transmitted by the terminal device.

In a possible design, the association information of the uplink data includes the content of the uplink data, or at least two of the content of the uplink data, the time-frequency resource block used when transmitting the uplink data, and the pilot information corresponding to the uplink data. .

For the beneficial effects of the methods provided by the foregoing second aspect and the possible designs of the second aspect, reference may be made to the beneficial effects of the various possible designs of the first aspect described above, and details are not described herein again.

In a third aspect, in order to implement the data transmission method of the first aspect, the embodiment of the present application provides a device for data transmission. As a network device, the data transmission device has a function of implementing the foregoing data transmission method. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software herein includes one or more modules corresponding to the functions described above.

In a possible implementation manner of the third aspect, the apparatus for data transmission includes:

a receiving module, configured to receive uplink data from the terminal device;

The identification module is configured to determine, according to the association information of the uplink data, a redundancy version of the terminal device and the uplink data, where the association information of the uplink data is information related to when the terminal device sends the uplink data.

In a possible design, the association information of the uplink data includes the content of the uplink data, or at least two of the content of the uplink data, the time-frequency resource block used when transmitting the uplink data, and the pilot corresponding to the uplink data.

In a possible design, the association information of the uplink data includes a time-frequency resource block and a pilot corresponding to the uplink data used when the uplink data is sent; the identification module is specifically configured to:

Determining a redundancy version of the uplink data according to the number of the time-frequency resource block in the associated time-frequency resource mapping chain;

Determining the terminal device according to the pilot and the mapping relationship between the preset pilot and the terminal device in the network device;

In a possible design, the association information of the uplink data includes the content of the time-frequency resource block and the uplink data used when the uplink data is sent, and the content of the uplink data carries the identity of the terminal device; the identification module is specifically configured to:

Determining the terminal device according to the identity identifier;

In a possible design, the association information of the uplink data includes the content of the time-frequency resource block and the uplink data used when the uplink data is sent, and the content of the uplink data carries the identifier of the terminal device in the associated terminal device group; the identification module Specifically used for:

According to the time-frequency resource mapping chain to which the time-frequency resource block belongs, and the time-frequency resource mapping chain and the default preset in the network device Determining the mapping relationship between the end device groups and determining the terminal device group to which the terminal device belongs;

Determining the terminal device in the terminal device group according to the identifier of the terminal device in the associated terminal device group;

Determining, according to the time-frequency resource mapping chain to which the time-frequency resource block belongs, and the mapping relationship between the time-frequency resource mapping chain and the terminal device group preset in the network device, determining the terminal device group to which the terminal device belongs;

Determining the terminal device in the terminal device group according to the pilot information, the mapping relationship between the preset pilots in the network device and the terminal devices in the terminal device group;

In a possible design, the association information of the uplink data includes the content of the pilot and the uplink data corresponding to the uplink data, and the content of the uplink data carries the identity of the terminal device; the identification module is specifically configured to:

Determining a redundancy version of the uplink data according to the number of the pilot in the associated pilot mapping chain;

Determining the terminal device according to the identity identifier;

In a possible design, the uplink data association information includes a time-frequency resource block used for transmitting the uplink data, a content of the uplink data, and a pilot corresponding to the uplink data, and the content carrying terminal device of the uplink data is in the terminal device to which the terminal device belongs. The identification in the group; the identification module is specifically used to:

Determining, according to a time-frequency resource block, a mapping relationship between a preset time-frequency resource block and a terminal device group in the network device, determining a terminal device group to which the terminal device belongs;

Determining the terminal device in the terminal device group according to the mapping relationship between the pilot mapping chain to which the pilot belongs, the preset pilot mapping chain in the network device, and the terminal device in the terminal device group;

In a possible design, the association information of the uplink data includes the content of the uplink data and the pilot corresponding to the uplink data, and the content of the uplink data carries the identifier of the redundancy version of the uplink data; the identification module is specifically configured to:

Determining a redundancy version of the uplink data according to the identifier of the redundancy version;

The terminal device is determined according to the pilot and the mapping relationship between the preset pilot and the terminal device in the network device.

In a possible design, the uplink data association information includes a time-frequency resource block used for transmitting the uplink data, a content of the uplink data, and a pilot corresponding to the uplink data, and the content of the uplink data carries a redundant version of the uplink data. Identification; identification module is specifically used to:

Determining, according to a time-frequency resource block, a mapping relationship between a time-frequency resource block and a terminal device group preset in the network device, determining a terminal device group to which the terminal device belongs;

The terminal device is determined in the terminal device group according to the mapping relationship between the pilot, the preset pilot in the network device, and the terminal device in the terminal device group.

In a possible design, the association information of the uplink data includes the content of the uplink data, and the content of the uplink data includes the identifier of the terminal device and the identifier of the redundancy version of the uplink data; the identification module is specifically configured to:

Determine the terminal device based on the identity.

In a possible design, the uplink data association information includes the time-frequency resource block and the uplink data content used when transmitting the uplink data, and the content of the uplink data carries the identifier of the redundancy version of the uplink data and the terminal device belongs to The identifier in the terminal device group; the identification module is specifically used to:

The terminal device is determined in the terminal device group according to the identifier of the terminal device in the associated terminal device group.

In a possible design, the uplink data further includes a mixed cyclic redundancy check bit; the N-bit bit in the hybrid cyclic redundancy check is determined by the N-bit bit in the cyclic redundancy check of the uplink data and the identity of the terminal device. X-bit XOR in the identifier is obtained;

Where N is a positive integer.

In one possible design, the identification module is also used to:

The hybrid automatic repeat request process for transmitting the uplink data is determined according to the association information of the uplink data.

In a possible design, the device for data transmission further includes:

Establishing a module, configured to establish a time-frequency resource mapping chain, and send the time-frequency resource mapping chain to the terminal device;

In a possible design, the establishing module is further configured to establish a time-frequency resource mapping chain, a pilot mapping chain, a mapping relationship between a pilot and a terminal device, a mapping relationship between a time-frequency resource mapping chain and a terminal device group, and each terminal. The identifier of each terminal device in the device group, the mapping relationship between each pilot device and terminal device in each terminal device group, the identifier of the terminal device in the associated terminal device group, the mapping between the pilot mapping chain and the terminal device in the terminal device group. At least one of the relationships is sent to the terminal device.

For the beneficial effects of the methods provided by the foregoing third aspect and the possible designs of the third aspect, reference may be made to the beneficial effects of the various possible designs of the first aspect described above, and details are not described herein again.

In a fourth aspect, in order to implement the method for data transmission in the second aspect, the embodiment of the present application provides a device for data transmission, and as a terminal device, the device for data transmission has a function of implementing the method for data transmission. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software herein includes one or more modules corresponding to the functions described above.

In a possible implementation manner of the fourth aspect, the apparatus for data transmission includes:

An uplink data determining module, configured to determine uplink data;

a sending module, configured to send uplink data to the network device according to the identifier of the terminal device and the redundancy version of the uplink data, so that the network device determines, according to the associated information of the uplink data, a redundancy version of the terminal device and the uplink data; The associated information of the data is information related to when the device transmits the uplink data.

For the beneficial effects of the methods provided by the fourth aspect and the possible designs of the fourth aspect, reference may be made to the beneficial effects brought by the possible designs of the first aspect described above, and details are not described herein again.

In a fifth aspect, in order to implement the method for data transmission in the foregoing first aspect, the embodiment of the present application provides a network device, where the network device has a function of implementing the foregoing method for data transmission. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software herein includes one or more modules corresponding to the functions described above.

In a possible implementation manner of the fifth aspect, the network device includes:

a receiver, configured to receive uplink data from the terminal device;

The processor is configured to determine, according to the association information of the uplink data, a redundancy version of the terminal device and the uplink data, where the association information of the uplink data is information related to when the terminal device sends the uplink data.

In a possible design, the association information of the uplink data includes a time-frequency resource block and a pilot corresponding to the uplink data used when transmitting the uplink data; the processor is specifically configured to:

In a possible design, the association information of the uplink data includes the content of the time-frequency resource block and the uplink data used when the uplink data is sent, and the content of the uplink data carries the identity of the terminal device; the processor is specifically configured to:

Determining the terminal device according to the identity identifier;

In a possible design, the association information of the uplink data includes the content of the time-frequency resource block and the uplink data used when the uplink data is sent, and the content of the uplink data carries the identifier of the terminal device in the associated terminal device group; Specifically used for:

In a possible design, the association information of the uplink data includes the content of the pilot data and the uplink data corresponding to the uplink data, and the content of the uplink data carries the identity identifier of the terminal device; the processor is specifically configured to:

Determining the terminal device according to the identity identifier;

In a possible design, the uplink data association information includes a time-frequency resource block used for transmitting the uplink data, a content of the uplink data, and a pilot corresponding to the uplink data, and the content carrying terminal device of the uplink data is in the terminal device to which the terminal device belongs. The identifier in the group; the processor is specifically used to:

In a possible design, the association information of the uplink data includes the content of the uplink data and the pilot corresponding to the uplink data, and the content of the uplink data carries the identifier of the redundancy version of the uplink data; the processor is specifically configured to:

In a possible design, the uplink data association information includes a time-frequency resource block used for transmitting the uplink data, a content of the uplink data, and a pilot corresponding to the uplink data, and the content of the uplink data carries a redundant version of the uplink data. Identification; the processor is specifically used to:

In a possible design, the association information of the uplink data includes the content of the uplink data, and the content of the uplink data includes the identifier of the terminal device and the identifier of the redundancy version of the uplink data; the processor is specifically configured to:

Determine the terminal device based on the identity.

In a possible design, the uplink data association information includes the time-frequency resource block and the uplink data content used when transmitting the uplink data, and the content of the uplink data carries the identifier of the redundancy version of the uplink data and the terminal device belongs to The identifier in the terminal device group; the processor is specifically used to:

Where N is a positive integer.

In one possible design, the processor is also used to:

Establishing a time-frequency resource mapping chain, and sending the time-frequency resource mapping chain to the terminal device;

In a possible design, the processor is further configured to establish a time-frequency resource mapping chain, a pilot mapping chain, a mapping relationship between the pilot and the terminal device, a mapping relationship between the time-frequency resource mapping chain and the terminal device group, and each terminal. The identifier of each terminal device in the device group, the mapping relationship between each pilot device and terminal device in each terminal device group, the identifier of the terminal device in the associated terminal device group, the mapping between the pilot mapping chain and the terminal device in the terminal device group. At least one of the relationships is sent to the terminal device.

For the beneficial effects of the methods provided by the fifth aspect and the possible designs of the fifth aspect, reference may be made to the beneficial effects brought by the possible designs of the first aspect described above, and details are not described herein again.

In a sixth aspect, in order to implement the method for data transmission in the foregoing second aspect, the embodiment of the present application provides a terminal device, where the terminal device has a function of implementing the foregoing method for data transmission. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software herein includes one or more modules corresponding to the functions described above.

In a possible implementation manner of the sixth aspect, the terminal device includes:

a processor for determining uplink data;

a transmitter, configured to send uplink data to the network device according to the identifier of the terminal device and the redundancy version of the uplink data, so that the network device determines, according to the association information of the uplink data, a redundancy version of the terminal device and the uplink data; The associated information of the data is information related to when the device transmits the uplink data.

For the beneficial effects of the methods provided by the foregoing sixth aspect and the possible designs of the sixth aspect, reference may be made to the beneficial effects brought by the possible designs of the first aspect described above, and details are not described herein again.

In a seventh aspect, the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the network device, which includes a program designed to execute the foregoing first aspect.

In an eighth aspect, an embodiment of the present application provides a computer storage medium, configured to store computer software instructions used by the terminal device, and includes a program designed to execute the foregoing second aspect.

In a ninth aspect, the embodiment of the present application provides a computer program product, comprising instructions, when executed by a computer, causing a computer to perform the functions performed by the network device in the first aspect.

In a tenth aspect, an embodiment of the present application provides a computer program product, comprising instructions, when executed by a computer, causing a computer to perform the functions performed by the terminal device in the second aspect.

In an eleventh aspect, an embodiment of the present application further provides a chip system, where the chip system includes a processor, where The supporting network device implements the functions involved in the first aspect described above, for example, generating or processing data and/or information involved in the above methods. In one possible design, the chip system further includes a memory for holding program instructions and data necessary for the network device. The chip system can be composed of chips, and can also include chips and other discrete devices.

In a twelfth aspect, the embodiment of the present application further provides a chip system, where the chip system includes a processor for supporting a terminal device to implement the functions involved in the foregoing second aspect, for example, generating or processing the method involved in the foregoing method. Data and / or information. 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 shows a network architecture that may be applicable to an embodiment of the present application;

2 is a schematic flowchart of Embodiment 1 of a method for data transmission provided by the present application;

FIG. 3 is a schematic diagram of a time-frequency resource block according to an embodiment of the present application;

4 is a schematic diagram of a resource mapping chain provided by an embodiment of the present application;

FIG. 5 is a schematic flowchart of Embodiment 2 of a method for data transmission provided by the present application;

FIG. 6 is a schematic structural diagram of Embodiment 1 of a device for data transmission provided by the present application;

FIG. 7 is a schematic structural diagram of Embodiment 2 of a device for data transmission provided by the present application;

FIG. 8 is a schematic structural diagram of Embodiment 3 of a device for data transmission provided by the present application;

9 is a schematic structural diagram of a network device provided by the present application;

FIG. 10 is a schematic structural diagram of a terminal device provided by the present application;

FIG. 11 is a schematic diagram of a contention transmission area according to an embodiment of the present application;

FIG. 12 is a schematic structural diagram of a payload portion of Grant-free data according to an embodiment of the present application.

detailed description

The network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application. The technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

The possible network architecture of the embodiment of the present application is introduced below with reference to FIG. FIG. 1 shows a network architecture that may be applicable to an embodiment of the present application. As shown in FIG. 1, the network architecture provided by this embodiment includes a network device 10 and a terminal device 20.

The network device 10 is a device that accesses the terminal device to the wireless network, and may be in Global System of Mobile communication (GSM) or Code Division Multiple Access (CDMA). Base station (Base Transceiver Station, BTS for short), may also be a base station (NodeB, NB for short) in Wideband Code Division Multiple Access (WCDMA), or Long Term Evolution (LTE). Evolved Node B (eNB or eNodeB), or a relay station or access point, or a future 5G network The base station, or the macro base station, the micro base station, the hotspot, the home base station, the transmission point, and the like are not limited herein. FIG. 1 schematically depicts a possible schematic, and an exemplary network device may be a base station.

The terminal device 20 may be a wireless terminal, which may be a device that provides voice and/or other service data connectivity to the user, a handheld device with wireless connectivity, or other processing device that is connected to the wireless modem. The wireless terminal can communicate with one or more core networks via a Radio Access Network (RAN), and the wireless terminal can be a mobile terminal, such as a mobile phone (or "cellular" phone), a laptop, a hand. Rings, smart watches, data cards, sensors, and computers with mobile terminals, for example, can be portable, pocket, handheld, computer built, or in-vehicle mobile devices that exchange language and/or data with the wireless access network. For example, Personal Communication Service (PCS) telephone, cordless telephone, Session Initiation Protocol (SIP) telephone, Wireless Local Loop (WLL) station, personal digital assistant (Personal) Digital Assistant, PDA for short. The wireless terminal may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, and a remote terminal. The access terminal, the user terminal (User Terminal), and the user agent (User Agent) are not limited herein. Figure 1 schematically depicts a possible illustration of an exemplary terminal device that may be a mobile telephone. Illustratively, for a network architecture in which a secondary link exists, for example, a wristband-handset-base station, the wristband can also be regarded as the terminal device 20, and the mobile phone is regarded as a network device.

In the LTE communication system, in order to ensure the reliability of data transmission, the terminal device generates multiple RVs of uplink data, such as RV0, RV2, RV3, and RV1. The terminal device sends different RVs of the uplink data to the network device in the order of 0-2-3-1. Of course, the terminal device may also transmit in other orders, as long as the transmitting and receiving parties know the order in advance. In the LTE system, the network device can schedule resources, Modulation and Coding Scheme (MCS), RV, and HARQ process ID of each uplink device (UE) for uplink (UpLink) HARQ transmission. However, in the Grant-free transmission, the network device cannot predict in advance which UE will transmit, and since the Grant-free transmission is initialized and transmitted by the UE, there is no scheduling signaling from the network device before, so other methods are needed to determine Grant- The UE ID of the free transmission data and the HARQ process ID ensure that the network device combines the data of the same HARQ process of the same UE. The same HARQ process (HARQ process, identified by the HARQ process ID, also known as the HARQ process ID) is the retransmission data for the same TB. One solution is to use a pilot mapping chain to send RVs to facilitate the network device to distinguish the RV of the received data. However, since the number of pilot mapping chains is small, there is a case where the network device cannot distinguish which terminal device the RV data comes from, and the reliability of data transmission is reduced.

To solve the above problem, the embodiment of the present application provides a data transmission method. The network device determines the RV of the uplink data and the terminal device that sends the uplink data according to the association information of the received uplink data, to ensure the reliability of the data transmission.

The data transmission method provided by the present application is described in detail below in conjunction with specific embodiments. In the following specific embodiments, the same or similar concepts or processes may not be described in some embodiments.

FIG. 2 is a schematic flowchart diagram of Embodiment 1 of a method for data transmission provided by the present application. The execution body of the method is a network device. In this embodiment, when the network device receives the uplink data, the network device determines the RV of the terminal device that sends the uplink data and the uplink data according to the association information of the uplink data. As shown in Figure 2, the method includes:

S201. The network device receives uplink data from the terminal device.

Exemplarily, the network device receives the uplink data sent by the terminal device. To correctly decode the data, determine the RV of the uplink data, and determine the terminal device that sends the uplink data. The uplink data is transmitted in an unlicensed manner. Therefore, the network device cannot determine the RV of the uplink data and the information of the terminal device before receiving the uplink data.

S202. The network device determines, according to the association information of the uplink data, a redundancy version of the terminal device and the uplink data.

The related information of the uplink data is information related to when the terminal device sends the uplink data.

Specifically, the association information of the uplink data is information related to when the terminal device sends the uplink data. For example, the information carried by the uplink data itself or the information of the resources used for sending the uplink data may be used, so the associated information may be used to indicate the terminal device and the redundancy version of the uplink data. By using the associated information of the uplink data to indicate the terminal device and the redundancy version of the uplink data, instead of relying only on the pilot mapping chain to indicate the RV of the terminal device and the uplink data, it is avoided that the number of pilot mapping chains is limited. The network device cannot correctly distinguish the uplink data from different terminal devices, which reduces the reliability of data transmission.

The data transmission method provided by the embodiment of the present application, the network device receives the uplink data from the terminal device, and determines the redundancy version of the terminal device and the uplink data according to the association information of the uplink data, where the association information is that the uplink is sent with the terminal device. Information about the data. By using the associated information of the uplink data instead of relying solely on the pilot mapping chain to indicate the RV of the terminal device and the uplink data, it can be avoided that the network device cannot correctly distinguish the uplink from different terminal devices because the number of pilot mapping chains is limited. Data reduces the reliability of data transmission.

Optionally, the association information of the uplink data includes content of the uplink data, or at least two of the content of the uplink data, the time-frequency resource block used when transmitting the uplink data, and the pilot information corresponding to the uplink data.

For example, the content of the uplink data may be various types of indication information included in the uplink data, or may be a format adopted by the uplink data itself. For example, different terminal devices or RVs may be indicated by using uplink data in different formats. Optionally, the uplink data includes a DMRS and a payload portion. The payload portion includes a control portion and a data portion. Various types of indication information can be carried in the DMRS, control part or data part.

For example, the association information of the uplink data may also be a time-frequency resource block used when transmitting the uplink data. The network device and the terminal device can agree that different terminal devices use different time-frequency resource blocks, so that the network device can distinguish the terminal device and the RV according to the time-frequency resource block. The terminal device occupies a certain time-frequency resource to transmit uplink data, and the time-frequency resource occupied by the uplink data is called a time-frequency resource block. The time-frequency resource block may be a basic resource unit when the terminal device performs transmission, or a resource block composed of several basic resource units. A basic resource unit is uniquely determined by the start of the time domain, the length of the time domain, the start of the frequency domain, and the width of the frequency domain. Basic resource units can also be extended to resources defined in other dimensions. For example, if Sparse Code Multiple Access (SCMA) is used for uplink data transmission, the definition of basic resource units can be extended to the code domain. That is, the basic resource unit is defined as a combination of time-frequency resources and code domain resources. Illustratively, for SCMA, the basic resource unit is defined as a combination of time-frequency resources, SCMA codebooks, and pilot sequences. For convenience of description, in the following embodiments, the basic resource unit is described as an example of a time-frequency resource block, but it is easy to understand that all embodiments of the present application can be used in the case where the basic resource unit adopts other definitions.

Exemplarily, the association information of the uplink data may be pilot information corresponding to the uplink data. The network device and the terminal device can agree that different terminal devices use different pilots, so that the network device can distinguish the terminal device and the RV according to the pilot information. The pilot is a general term for various reference signals, and the exemplary pilot may be a Demodulation Reference Signal (DMRS). In the following embodiments, the pilot is a DMRS as an example for detailed description.

Further, on the basis of the foregoing embodiment shown in FIG. 2, a possible implementation manner of determining the RV of the terminal device and the uplink data is described in detail below.

The first possible implementation:

In this implementation manner, the association information of the uplink data includes a time-frequency resource block used for transmitting the uplink data and a pilot corresponding to the uplink data. Correspondingly, determining a redundancy version of the terminal device and the uplink data, specifically includes:

S11. The network device determines a redundancy version of the uplink data according to the number of the time-frequency resource block in the associated time-frequency resource mapping chain.

Specifically, the network device and the terminal device establish a time-frequency resource mapping chain, and each time-frequency resource mapping chain includes at least two time-frequency resource blocks, and different time-frequency resource blocks in one time-frequency resource mapping chain correspond to different RVs of the same TB. A time-frequency resource mapping chain corresponds to one TB of a terminal device. Exemplarily, when the number of RVs included in each TB is 4, the time-frequency resource mapping chain also includes 4 time-frequency resource blocks. The following embodiments of the present application describe a method for data transmission provided by the present application by taking a time-frequency resource mapping chain including four time-frequency resource blocks as an example.

For example, FIG. 3 is a schematic diagram of a time-frequency resource block according to an embodiment of the present application. FIG. 4 is a schematic diagram of a time-frequency resource mapping chain according to an embodiment of the present application. As shown in FIG. 3, in a time-frequency resource, there are multiple time-frequency resource blocks, and one time-frequency resource block may be referred to as a Contention Transmission Unit (CTU). One or more CTUs constitute a Contention Transmission Area (CTA). The CTA is defined as an air interface time-frequency resource defined by a specific time and frequency. Different CTAs do not overlap each other in time or frequency. It should be specially noted that there is no essential difference between CTU and CTA. CTU can be regarded as CTA with only one CTU. When the terminal device performs the unlicensed uplink data transmission, one or more CTUs are selected for transmission in a certain CTA, or one CTA is selected for transmission.

Exemplarily, before the terminal device performs the unlicensed uplink data transmission, the network device may configure multiple CTAs for the unlicensed uplink data, and each CTA includes one or more CTUs. These CTAs can occur periodically, called the CTA transmission cycle. The duration of the CTA transmission period can be configured by the network device. During the same CTA transmission period, mapping relationships can be established between CTUs in different CTAs to form a time-frequency resource mapping chain. Each CTU in the time-frequency resource mapping chain has a respective number, and different numbered CTUs are used to indicate different RVs of the uplink data, that is, different CTUs in the same time-frequency resource mapping chain correspond to different RVs. Therefore, the network device may determine the RV of the uplink data according to the number of the time-frequency resource block in the associated time-frequency resource mapping chain.

Illustratively, different RVs are denoted as RV0, RV2, RV3, RV1 according to the order of transmission. Exemplarily, the CTU numbered j in CTA _i is denoted as CTU _i,j , where i and j have values of 1, 2, 3, 4. As shown in Figure 4, CTU _1,1 , CTU _2,1 , CTU _3,1 and CTU _4,1 from different CTAs form a time-frequency resource mapping chain, and the instant frequency resource mapping chain CTU _1,1 (RV0)→ CTU _2,1 (RV2)→CTU _3,1 (RV3)→CTU _4,1 (RV1). Each CTU corresponds to a different RV. When a terminal device selects CTU _{1,1 to} send RV0 of data but receives a negative acknowledgement (Negative ACKnowledgment, NACK), the terminal device transmits RV2 on CTU _2,1 . Similarly, the terminal device transmits RV3 on CTU _3,1 and RV1 on CTU _4,1 . For network equipment, the data received on CTU _1,1 must be RV0 of a certain uplink data. If the decoding fails, the RV2 of the data is continuously received on CTU _2,1 after the NACK is sent, and try. The two are combined and decoded. If the decoding is still not successful, the RV3 on the CTU ₃ , ₁ is received, and the merge decoding is performed again.

Optionally, the network device successfully solves the data after receiving the RV0 on the CTU _1,1 , successfully obtains the data after receiving the RV2 on the CTU _2,1 , and successfully obtains the data after receiving the RV3 on the CTU _3,1 . Or _, when the data is successfully solved after receiving the RV1 on the CTU _{4, 1} , the network device sends an Acknowledgement (ACK) to the terminal device. After receiving the ACK, the terminal device ends the transmission of the current TB.

Optionally, as shown in FIG. 4, different CTUs in the same CTA may correspond to different RVs, and CTU _{1 in} CTA1 corresponds to a time-frequency resource mapping chain CTU _1,1 (RV0)→CTU _2,1 (RV2)→CTU _3,1 (RV3)→CTU _4,1 (RV1) on RV0, and CTU _1,2 corresponds to time-frequency resource mapping chain CTU _1,2 (RV3)→CTU _2,2 (RV1)→CTU _3,2 ( RV0) → RV3 on CTU _{4, 2} (RV2).

Optionally, the time-frequency resource blocks belonging to the same contention transmission area may correspond to the same redundancy version. Exemplarily, all CTUs in the same CTA may correspond to the same RV value. For example, all CTUs in CTA1 correspond to RV0, all CTUs in CTA2 correspond to RV2, all CTUs in CTA3 correspond to RV3, and all CTUs in CTA4 correspond to RV1.

Exemplarily, when the terminal device needs to transmit data in an unlicensed manner, the CTA transmission closest to the current time is generally selected. If the data RV corresponding to the available CTU in the CTA closest to the current time is not RV0, the terminal device can only transmit the RV corresponding to the current CTU. In other words, for a TB of upstream data, the first redundancy version transmitted by the terminal device may not be RV0. For example, if a terminal device has burst data to be transmitted before CTA3 in FIG. 4, and only CTU ₃ , _{1 is} available in CTA3, the terminal device can only transmit RV3 in CTU ₃ , ₁ , and the terminal device transmits the burst. The RV version order of the transmitted data is RV3, RV1, RV2, and RV0. Of course, the terminal device can also wait until the next CTA transmitting the RV0, that is, the first data version transmitted by the terminal device is always RV0.

S12. The network device determines the terminal device according to the pilot, and a mapping relationship between the preset pilot and the terminal device in the network device.

Among them, S12 and S11 have no strict sequence of execution, and can be executed simultaneously or sequentially.

Specifically, since the pilot mapping chain usually includes at least four different pilots, the number of terminal devices that the pilot can indicate is much larger than the number of terminal devices that can be indicated by the pilot mapping chain. Therefore, when the network device does not use the pilot mapping chain formed by the pilot to indicate the RV of the uplink data, the pilot may be used to indicate the terminal device that sends the uplink data.

Exemplarily, the terminal device and the network device agree in advance on the mapping relationship between the terminal device and the pilot. When the terminal device performs the unlicensed uplink data transmission, only the pilot corresponding to the pilot device can be used, and the network device receives a pilot in the CTU. The terminal device that sends the uplink data can be uniquely determined. Optionally, the network device may indicate, by using the high layer signaling, a mapping relationship between the terminal device and the pilot device and the terminal device. The mapping relationship between the pilot and the terminal device may be calculated by the terminal device. For example, the terminal device calculates its own corresponding pilot based on the identity identifier (ID) of the terminal device. The communication standard may be pre-defined in advance. For example, the identity of the terminal device is a Cell-Radio Network Temporary Identifier (C-RNTI), and the communication standard pre-defines a pilot corresponding to each C-RNTI.

In this embodiment, by carrying the RV identifier in the uplink data, the network device can determine the RV of the uplink data according to the RV identifier carried in the uplink data. Since each uplink data itself carries its own corresponding RV, the network device determines that the terminal device and the RV are no longer affected by the small number of pilots, thereby improving the reliability of data transmission.

Optionally, on the basis of the embodiment, before the network device receives the uplink data from the terminal device, the data transmission method further includes:

The network device establishes a mapping relationship between the pilot and the terminal device, and a time-frequency resource mapping chain, and sends the mapping relationship between the pilot and the terminal device and the time-frequency resource mapping chain to the terminal device.

The second possible implementation:

Compared with the first possible implementation manner, the difference is that the manner of determining the terminal device is different. In this manner, the terminal device is determined according to the identity identifier of the terminal device carried by the uplink data. Since the manner of determining the redundancy version of the uplink data is the same, the application will not be described again.

In this implementation manner, the association information of the uplink data includes the content of the time-frequency resource block and the uplink data used when the uplink data is sent, and the content of the uplink data carries the identity of the terminal device; correspondingly, determining the redundancy of the terminal device and the uplink data The remaining versions include:

S21. The network device determines, according to the number of the time-frequency resource block in the associated time-frequency resource mapping chain, a redundancy version of the uplink data.

S22. The network device determines the terminal device according to the identity identifier.

Exemplarily, the control part of the uplink data includes an identity (ID) of the terminal device, and the identity identifier may be a permanent identifier of the terminal device. The identity identifier may also be an identifier of the terminal in the cell to which it belongs, such as a Cell-Radio Network Temporary Identifier (C-RNTI) of the terminal device. When the network device receives the uplink data, the terminal device that sends the uplink data can be determined according to the identity identifier carried in the uplink data, and the number of the pilot mapping chain is limited, and the network device cannot correctly distinguish the data from different user devices. , reducing the reliability of data transmission.

In this embodiment, by carrying the identity identifier of the terminal device in the uplink data, the network device can determine the identity identifier for sending the uplink data according to the identity identifier carried in the uplink data. Since each uplink data itself carries its own identity identifier, the network device determines that the terminal device and the RV are no longer affected by the small number of pilots, thereby improving the reliability of data transmission.

The third possible implementation:

Compared with the second possible implementation manner, the difference is that the manner of determining the terminal device is different. Considering that the identity identifier is usually long, the terminal device is grouped in the manner, and the identifier of the terminal device carried only by the uplink data in the packet is . Since the manner of determining the redundancy version of the uplink data is the same, the application will not be described again.

In this implementation manner, the association information of the uplink data includes the content of the time-frequency resource block and the uplink data used when the uplink data is sent, and the content of the uplink data carries the identifier of the terminal device in the belonging terminal device group; correspondingly, the terminal is determined. A redundant version of the device and uplink data, including:

S31. The network device determines, according to the number of the time-frequency resource block in the associated time-frequency resource mapping chain, a redundancy version of the uplink data.

S32. The network device determines, according to the time-frequency resource mapping chain to which the time-frequency resource block belongs, and the mapping relationship between the time-frequency resource mapping chain and the terminal device group preset in the network device, the terminal device group to which the terminal device belongs.

S33. The network device determines the terminal device in the terminal device group according to the identifier of the terminal device in the associated terminal device group.

Exemplarily, the identity of the terminal device is usually long, and more bits are needed for indication. For example, the length of the C-RNTI is 16 bits. Taking the C-RNTI in the control part of the uplink data as an example, this will cause the control part of the uplink data to be too long, which increases the indication overhead. Therefore, each time-frequency resource mapping chain can be bound to a group of terminal devices, and the same terminal device can be bound to one or more time-frequency resource mapping chains at the same time, and the fewer terminal devices in a terminal device group are indicated in the group. The shorter the identification length of the terminal device. Therefore, the control part may include a short identifier of the terminal device, and the short identifier is an identifier of the terminal device in the belonging terminal device group. The short identifier of the terminal device is unique only in the associated terminal device group, thereby shortening the identity length of the terminal device. For example, if a time-frequency resource mapping chain allows binding of up to 8 terminal devices, the short identifier of each terminal device only needs 3 bits, which is far less than 16 bits of C-RNTI. The time-frequency resource mapping chain bound to each terminal device, the correspondence between the short identifier of the terminal device in the time-frequency resource mapping chain and the C-RNTI of the terminal device may be specified by the network device, for example, explicitly allocated by signaling. Or the terminal device calculates the time-frequency resource mapping chain bound to each terminal device based on the same rule according to the identifier of the terminal device, and the terminal device is in each bound resource block. Short logo. When the terminal device needs to perform the unlicensed uplink data transmission, only one time-frequency resource block can be selected for transmission in the time-frequency resource mapping chain bound to itself.

Exemplarily, when the network device receives the uplink data, the network device may determine, according to the time-frequency resource mapping chain to which the time-frequency resource block belongs, and the mapping relationship between the preset time-frequency resource mapping chain and the terminal device group in the network device. The terminal device group to which the terminal device belongs. Then, the network device determines the terminal device in the terminal device group according to the identifier of the terminal device carried in the uplink data in the terminal device group.

In this embodiment, by binding a time-frequency resource mapping chain to a group of terminal devices, the identifier of the terminal device that can be carried only in the uplink device group is smaller, and the identifier uses fewer bits. Saving instruction overhead.

The network device establishes a mapping relationship between the time-frequency resource mapping chain and the terminal device group, the identifier of each terminal device in each terminal device group, and the mapping relationship between the time-frequency resource mapping chain and the terminal device group, and the terminal devices in each terminal device group. The identity is sent to the terminal device.

The fourth possible implementation:

Compared with the first possible implementation manner, the difference is that the manner of determining the terminal device is different. In this method, considering the limited number of pilots, each time-frequency resource mapping chain can be bound to a group of terminal devices. The terminal devices in the terminal device group are distinguished by the pilots used respectively. Since the manner of determining the redundancy version of the uplink data is the same, the application will not be described again.

In this implementation manner, the association information of the uplink data includes a time-frequency resource block and a pilot corresponding to the uplink data used when the uplink data is sent; correspondingly, determining a redundancy version of the terminal device and the uplink data, specifically:

S41. The network device determines, according to the number of the time-frequency resource block in the associated time-frequency resource mapping chain, a redundancy version of the uplink data.

S42. The network device determines, according to the time-frequency resource mapping chain to which the time-frequency resource block belongs, and the mapping relationship between the time-frequency resource mapping chain and the terminal device group preset in the network device, the terminal device group to which the terminal device belongs.

S43. The network device determines the terminal device in the terminal device group according to the pilot information, the mapping relationship between the preset pilots in the network device, and the terminal device in the terminal device group.

Exemplarily, when the RV of the uplink data is determined according to the number of the time-frequency resource block in the associated time-frequency resource mapping chain, and the terminal device is determined according to the pilot of the uplink data, the number of the terminal devices that can be determined is controlled by the pilot. The number is limited. Considering that the number of time-frequency resource mapping chains is large, terminal devices using different time-frequency resource mapping chains may have the same pilot. Therefore, each time-frequency resource mapping chain can be bound to a group of terminal devices, and the same terminal device can be bound to one or more time-frequency resource mapping chains at the same time. The terminal devices in the same terminal device group can be distinguished by the pilots used by the respective terminal devices, and the terminal devices in different terminal device groups can adopt the same pilot. The time-frequency resource mapping chain bound to each terminal device, and the corresponding pilot when the terminal device uses the time-frequency resource mapping chain may be specified by the network device, for example, by signaling, or by the terminal device based on the terminal device The identifier is calculated according to a predefined rule, and the network device calculates a time-frequency resource mapping chain bound to each terminal device based on the same rule, and a pilot corresponding to the terminal device when the bound time-frequency resource mapping chain is used. When the terminal device needs to perform the unlicensed uplink data transmission, only one of the time-frequency resource mapping chains bound to itself can be selected for transmission, and the corresponding pilot is used.

Exemplarily, when the network device receives the uplink data, the network device may determine, according to the time-frequency resource mapping chain to which the time-frequency resource block belongs, and the mapping relationship between the preset time-frequency resource mapping chain and the terminal device group in the network device. The terminal device group to which the terminal device belongs. Then, the terminal device is determined in the terminal device group according to the pilot corresponding to the uplink data.

In this embodiment, by binding a time-frequency resource mapping chain to a group of terminal devices, the terminal devices using different resource mapping chains may have the same pilot, so that the network device can determine the terminal device that sends the uplink data. The number of pilots is limited, and the network device cannot correctly distinguish data from different user devices, which reduces the reliability of data transmission.

The network device establishes a mapping relationship between the time-frequency resource mapping chain and the terminal device group, the mapping relationship between the pilots and the terminal devices in each terminal device group, and the mapping relationship between the time-frequency resource mapping chain and the terminal device group, and each terminal device group The mapping relationship between each pilot and the terminal device is sent to the terminal device.

The fifth possible implementation:

Compared with the first to fourth possible implementation manners, the network device in this manner determines the redundancy version of the uplink data according to the number of the pilot in the associated pilot mapping chain. The manner of determining the terminal device in this manner is the same as that in the second possible implementation manner described above, and therefore is not described herein again.

In this implementation manner, the association information of the uplink data includes the content of the pilot data and the uplink data corresponding to the uplink data, and the content of the uplink data carries the identity identifier of the terminal device; correspondingly, the redundancy version of the terminal device and the uplink data is determined, specifically including :

S51. The network device determines a redundancy version of the uplink data according to the number of the pilot in the associated pilot mapping chain.

S52. The network device determines the terminal device according to the identity identifier.

Exemplarily, the network device can determine the RV of the uplink data according to the number of the pilot corresponding to the uplink data in the pilot mapping chain. Different terminal devices may use the same pilot mapping chain, and the network device cannot determine the number of uplinks sent. According to the terminal equipment. When the number of pilot mapping chains is small and a pilot device mapping link chain cannot be implemented, the network device can determine the terminal device according to the identity flag carried in the uplink data.

The network device establishes a pilot mapping chain and sends the pilot mapping chain to the terminal device.

The sixth possible implementation:

Compared with the fifth possible implementation manner, the difference is that the manner of determining the terminal device is different, and the manner of determining the terminal device in the third possible implementation manner is similar, considering that the identity identifier of the terminal device is generally long. In this method, the terminal devices are grouped, and the uplink data carries only the identifier of the terminal device in the packet. Since the manner of determining the redundancy version of the uplink data is the same, the application will not be described again.

In the implementation manner, the related information of the uplink data includes a time-frequency resource block used for transmitting the uplink data, a content of the uplink data, and a pilot corresponding to the uplink data, where the content carrying terminal device of the uplink data is in the belonging terminal device group. Identification; correspondingly, determining a redundancy version of the terminal device and the uplink data, specifically including:

S61. The network device determines a redundancy version of the uplink data according to the number of the pilot in the associated pilot mapping chain.

S62. The network device determines, according to the time-frequency resource block, a mapping relationship between the preset time-frequency resource block and the terminal device group in the network device, the terminal device group to which the terminal device belongs.

S63. The network device determines the terminal device in the terminal device group according to the identifier of the terminal device in the terminal device group to which the terminal device belongs.

Illustratively, with reference to the manner of determining the terminal device in the third possible implementation manner, each time-frequency resource block is bound to a group of terminal devices, and the same terminal device can be bound to one or more time-frequency resource blocks at the same time. The fewer terminal devices in a terminal device group, the shorter the identification length of the terminal devices in the group is indicated. Therefore, the uplink data may include a short identifier of the terminal device, and the short identifier is an identifier of the terminal device in the associated terminal device group.

In this embodiment, by binding a time-frequency resource block to a group of terminal devices, the identifier of the terminal device that can be carried only in the uplink data group is smaller, which saves the number of bits used by the terminal device. Indicates overhead.

The network device establishes a mapping relationship between the time-frequency resource block and the terminal device group, and the identifier of the terminal device in the associated terminal device group, and the mapping relationship between the time-frequency resource block and the terminal device group, and the terminal device in which the terminal device belongs The identity in the group is sent to the terminal device.

The seventh possible implementation:

Compared with the sixth possible implementation manner, the difference is that the manner of determining the terminal device is different. In this method, the number of pilot mapping chains is small, and each terminal device cannot be distinguished according to the pilot mapping chain. The time-frequency resource blocks are bound to a group of terminal devices, and the terminal devices in the same terminal device group are distinguished by respective pilot mapping chains. Due to The manner of determining the redundancy version of the uplink data is the same, so the application will not be described again.

S71. The network device determines a redundancy version of the uplink data according to the number of the pilot in the associated pilot mapping chain.

S72. The network device determines, according to the time-frequency resource block, the mapping relationship between the preset time-frequency resource block and the terminal device group in the network device, the terminal device group to which the terminal device belongs.

S73. The network device determines the terminal device in the terminal device group according to the mapping relationship between the pilot mapping chain to which the pilot belongs, the preset pilot mapping chain in the network device, and the terminal device in the terminal device group.

Exemplarily, when the RV of the uplink data is determined according to the number of the pilot in the associated pilot mapping chain, since the number of pilot mapping chains is limited, the number of terminal devices that can be determined is also limited. Considering that the number of time-frequency resource blocks is large, terminal devices using different time-frequency resource blocks can adopt the same pilot mapping chain. Therefore, each time-frequency resource block can be bound to a group of terminal devices, and the same terminal device can be bound to one or more time-frequency resource blocks at the same time. The terminal devices in the same terminal device group can be distinguished by the pilot mapping chain used by each, and the terminal devices in different terminal device groups can adopt the same pilot mapping chain. The time-frequency resource block to which each terminal device is bound, and the corresponding pilot mapping chain when the terminal device uses the time-frequency resource block may be specified by the network device, for example, by explicit signaling; or by the terminal device based on the terminal device The identifier is calculated according to a predefined rule, and the network device calculates a time-frequency resource block bound to each terminal device based on the same rule, and a corresponding pilot mapping chain when the terminal device uses the bound time-frequency resource block. When the terminal device needs to perform the unlicensed uplink data transmission, only one of the time-frequency resource blocks bound to itself can be selected for transmission, and the corresponding pilot mapping chain is adopted.

For example, each terminal device is bound to one or more CTAs within a CTA period. For a particular terminal device, in each CTA bound to it, the terminal device uniquely corresponds to a pilot mapping chain. Different CTAs bound to the same terminal device may correspond to the same or different pilot mapping chains. In different CTAs, the pilot map chain can be multiplexed. For example, if each CTA allows up to 4 versions of the RV to bind 10 terminal device data, only 10×4=40 pilots are needed. The pilot can be a DMRS. It should be noted again that there is no essential difference between the CTA and the CTU. When the CTA contains only one CTU, it is the CTU, so the CTA here can also be replaced with the CTU.

Exemplarily, 40 DMRSs are respectively named p1 to p40, wherein each adjacent 4 DMRSs constitute a pilot mapping chain, thereby forming 10 pilot mapping chains corresponding to 10 terminal devices in each CTA (each The short IDs of the ten terminal devices corresponding to the CTAs are denoted as UE1 to UE10). Suppose a terminal device USER0 is bound to two CTAs, the short ID in CTA1 is terminal device UE1, the corresponding pilot mapping chain is p1→p2→p3→p4, and the short ID in CTA2 is terminal device UE5. The corresponding pilot map chain is p17→p18→p19→p20, and CTA1 is located before CTA2 in the time domain. If the terminal device USER0 sends RV0 with p1 but receives NACK in CTA1, USER0 sends RV2 with p18 in CTA2. Since the short ID of USER0 in CTA1 and the short ID in CTA2 (or the corresponding pilot mapping chain) are known in advance with the network device, the network device detects the data of DMRS as p1 in CTA1, and in CTA2. When the data of DMRS is detected as p18, it can be known that they correspond to RV0 and RV2 of the same data of the terminal device User0, and then they are combined and decoded.

For example, when the network device receives the uplink data, the network device may determine the terminal device group to which the terminal device belongs according to the time-frequency resource block and the mapping relationship between the time-frequency resource block and the terminal device group preset in the network device. Then The terminal device is determined in the terminal device group according to the pilot mapping chain corresponding to the uplink data.

In this embodiment, by binding a time-frequency resource block to a group of terminal devices, the terminal devices using different time-frequency resource blocks may have the same pilot mapping chain, so that the network device can determine the terminal that sends the uplink data. The RV of the device and the uplink data avoids the limited pilot resources, and the network device cannot correctly distinguish the RV of data and uplink data from different user equipments, thereby reducing the reliability of data transmission.

The network device establishes a mapping relationship between the time-frequency resource block and the terminal device group, and a mapping relationship between the pilot mapping chain and the terminal device in the terminal device group, and the mapping relationship between the time-frequency resource block and the terminal device group, and the pilot mapping The mapping relationship between the chain and the terminal device in the terminal device group is sent to the terminal device.

The eighth possible implementation:

Compared with the first to seventh possible implementation manners, the network device in this manner determines the redundancy version of the uplink data according to the identifier of the redundancy version carried in the uplink data. The manner in which the terminal device is determined in this manner is the same as the manner in which the terminal device is determined in the first possible implementation manner.

In this implementation manner, the association information of the uplink data includes the content of the uplink data and the pilot corresponding to the uplink data, and the content of the uplink data carries the identifier of the redundancy version of the uplink data; correspondingly, the redundancy version of the terminal device and the uplink data is determined. Specifically, including:

S81. The network device determines, according to the identifier of the redundancy version, a redundancy version of the uplink data.

For example, when the terminal device sends the uplink data, the RV of the uplink data is carried in the control part of the uplink data, so that the network device can obtain the RV of the uplink data according to the RV identifier included in the control part of the uplink data. Since each uplink data itself carries its own RV, the pilot mapping chain is no longer used, so that the network device determines that the terminal device and the RV are no longer affected by the small number of pilot mapping chains, thereby improving the reliability of data transmission. .

For example, the uplink data includes a DMRS and a payload portion, the payload portion includes a control portion and a data portion, and the RV may be included in a control portion of the UL data. Optionally, the control part of the uplink data is transmitted at a fixed, lower rate, the data part is transmitted at a variable rate, and the control part indicates a Modulation and Coding Scheme (MCS) used in the data part; or The DMRS of the data indicates the MCS used by the control part; or the DMRS of the uplink data indicates the MCS used by the control part and the data part, that is, the control part and the data part adopt the same MCS.

S82. The network device determines the terminal device according to the pilot, and a mapping relationship between the preset pilot and the terminal device in the network device.

In this embodiment, the RV of the uplink data is carried in the uplink data, so that the network device can determine the RV of the uplink data according to the identifier of the RV carried in the uplink data. Since each uplink data itself carries its own RV, the pilot mapping chain is no longer used, so that the network device determines that the terminal device and the RV are no longer affected by the small number of pilot mapping chains, thereby improving the reliability of data transmission. .

The network device establishes a mapping relationship between the pilot and the terminal device, and sends the mapping relationship between the pilot and the terminal device to the terminal device.

The ninth possible implementation:

Compared with the eighth possible implementation manner, the difference is that the manner of determining the terminal device is different. Considering the limited number of pilots, each time-frequency resource block can be bound to a group of terminal devices, and the same terminal device group is The terminal equipment is distinguished by the pilots used by each. Since the manner of determining the redundancy version of the uplink data is the same, the application will not be described again.

In this implementation manner, the uplink data association information includes a time-frequency resource block, a content of the uplink data, and a pilot corresponding to the uplink data, where the content of the uplink data carries an identifier of the redundancy version of the uplink data; Determine the redundancy version of the terminal device and the uplink data, including:

S91. The network device determines, according to the identifier of the redundancy version, a redundancy version of the uplink data.

S92. The network device determines, according to the time-frequency resource block, a mapping relationship between the time-frequency resource block and the terminal device group preset in the network device, the terminal device group to which the terminal device belongs.

S93. The network device determines the terminal device in the terminal device group according to the mapping relationship between the pilot, the preset pilot in the network device, and the terminal device in the terminal device group.

Exemplarily, when the terminal device that transmits the uplink data is instructed as needed, since the number of pilots is limited, the number of terminal devices that can be determined according to the pilot is also limited. Considering that the number of time-frequency resource blocks is large, terminal devices using different time-frequency resource blocks can use the same pilot. Therefore, each time-frequency resource block can be bound to a group of terminal devices, and the same terminal device can be bound to one or more time-frequency resource blocks at the same time. The terminal devices in the same terminal device group can be distinguished by the pilots used by the respective terminal devices, and the terminal devices in different terminal device groups can adopt the same pilot. The time-frequency resource block to which each terminal device is bound, and the corresponding pilot when the terminal device uses the time-frequency resource block may be specified by the network device, for example, explicitly allocated by signaling; or the terminal device is based on the identity of the terminal device. According to the calculation of the predefined rules, the network device calculates the time-frequency resource block bound to each terminal device based on the same rule, and the corresponding pilot when the terminal device uses the bound time-frequency resource block. When the terminal device needs to perform the unlicensed uplink data transmission, only one of the time-frequency resource blocks bound to itself can be selected for transmission, and the corresponding pilot is used.

For example, when the network device receives the uplink data, the network device may determine the terminal device group to which the terminal device belongs according to the time-frequency resource block and the mapping relationship between the time-frequency resource block and the terminal device group preset in the network device. Then, the terminal device is determined in the terminal device group according to the pilot corresponding to the uplink data.

In this embodiment, by binding a time-frequency resource block to a group of terminal devices, the terminal devices using different time-frequency resource blocks may have the same pilot, so that the network device can determine the terminal device that sends the uplink data and The RV of the uplink data avoids the limited number of pilots, and the network device cannot correctly distinguish the RV of data and uplink data from different user equipments, thereby reducing the reliability of data transmission.

The network device establishes a mapping relationship between the time-frequency resource block and the terminal device group, and a mapping relationship between the pilot and the terminal device in the terminal device group, and maps the time-frequency resource block to the terminal device group, and the pilot and the terminal device group. The mapping relationship of the terminal device is sent to the terminal device.

The tenth possible implementation:

Compared with the eighth possible implementation manner, the difference is that the manner of determining the terminal device is different. The manner of determining the terminal device in this manner is the same as the manner for determining the terminal device in the second possible implementation manner. Since the manner of determining the redundancy version of the uplink data is the same, the application will not be described again.

In this implementation manner, the association information of the uplink data includes the content of the uplink data, and the content of the uplink data includes the identifier of the terminal device and the identifier of the redundancy version of the uplink data; correspondingly, determining the redundancy of the terminal device and the uplink data. Version, including:

S101. The network device determines, according to the identifier of the redundancy version, a redundancy version of the uplink data.

S102. The network device determines the terminal device according to the identity identifier.

In this embodiment, by carrying the identifier of the terminal device and the identifier of the redundancy version in the uplink data, the network device can determine the RV of the terminal device that sends the uplink data and the uplink data, and avoid the network device caused by the limited pilot resources. The RV of uplink data and uplink data from different user equipments cannot be correctly distinguished, which reduces the reliability of data transmission.

The eleventh possible implementation:

Compared with the eighth possible implementation manner, the difference is that the manner of determining the terminal device is different. In this manner, the manner of determining the terminal device is the same as the manner for determining the terminal device in the sixth possible implementation manner. Since the manner of determining the redundancy version of the uplink data is the same, the application will not be described again.

In this implementation manner, the association information of the uplink data includes the content of the time-frequency resource block and the uplink data used when the uplink data is sent, and the content of the uplink data carries the identifier of the redundancy version of the uplink data and the terminal device group to which the terminal device belongs. The identifier in the device; correspondingly, determining the redundancy version of the terminal device and the uplink data, specifically including:

S111. The network device determines, according to the identifier of the redundancy version, a redundancy version of the uplink data.

S112. The network device determines, according to the time-frequency resource block, a mapping relationship between the preset time-frequency resource block and the terminal device group in the network device, the terminal device group to which the terminal device belongs.

S113. The network device determines the terminal device in the terminal device group according to the identifier of the terminal device in the associated terminal device group.

The network device establishes a mapping relationship between the time-frequency resource block and the terminal device group, the identifier of the terminal device in the associated terminal device group, and the mapping relationship between the time-frequency resource block and the terminal device group, and the terminal device is in the belonging terminal device group. The identity is sent to the terminal device.

Further, when the uplink data includes the identifier of the terminal device that sends the uplink data in the terminal device group, the uplink data further includes a mixed cyclic redundancy check bit; and the N-bit bit in the mixed cyclic redundancy check is used by the uplink data. The N-bit bit in the cyclic redundancy check is XORed with the N-bit bit in the identity of the terminal device;

or,

The N-bit bit in the hybrid cyclic redundancy check is obtained by X-biting the N-bit bit in the cyclic redundancy check of the uplink data with the N-bit in the identifier of the terminal device in the associated terminal device group.

Where N is a positive integer.

Exemplarily, the uplink data carries a long ID (such as an identity identifier) or a short ID (such as an identifier of the terminal device in the associated terminal device group) of the terminal device. The long ID or short ID may be explicitly included in the control portion of the upstream data. For example, the control section has a preset bit for carrying the ID of the terminal device. Or XOR on the Cyclic Redundancy Check (CRC). For example, if the control part includes an 8-bit check digit and the ID of the terminal device is 3 bits, the ID of the terminal device and the 8-bit check can be verified. The 3 bits in the bit are XORed to obtain the CRC in the uplink data. When the network device receives the uplink data, it first calculates the CRC of the uplink data, and then calculates the calculated data. The CRC is XORed with the CRC carried in the uplink data. If the other 5 bits except the 3 bits corresponding to the ID of the terminal device are 0 in the XOR result, the 3 bits corresponding to the ID of the terminal device is the ID of the terminal device. Optionally, the ID of the terminal device may also be divided into two parts, one part is explicitly included in the control part, and the other part is XORed with the CRC of the control part.

Further, on the basis of any of the foregoing embodiments, when uplink data transmission is performed, data that may be sent in the terminal device may include multiple HARQ processes, and different HARQ processes correspond to different TBs. Therefore, it is also necessary to determine the HARQ process of the terminal device corresponding to the uplink data. Exemplarily, the data transmission method further includes:

Exemplarily, in consideration of the fact that the terminal device may perform the transmission of multiple HARQ processes at the same time, when receiving the uplink data, the network device also needs to determine the HARQ process ID of the uplink automatic retransmission request process for sending the uplink data, so that The network device determines the HARQ process to which the received uplink data belongs. Therefore, the HARQ process ID for transmitting the uplink data may be carried in the uplink data, and the HARQ process for transmitting the uplink data may also be used by using the pilot indication, with reference to the various possible methods for determining the terminal device. The HARQ process for transmitting the uplink data may be determined according to the mapping relationship between the preset pilot and the HARQ process in the network device, and the mapping relationship between the time-frequency resource block and the HARQ process preset in the network device. The HARQ process for transmitting uplink data may be determined according to the mapping relationship between the preset pilot and the HARQ process in the network device, and the mapping relationship between the time-frequency resource mapping chain and the HARQ process to which the preset time-frequency resource block belongs in the network device. .

The method for determining the terminal device may be the same as or different from the method for determining the HARQ process. Illustratively, when the same, one possible way is to bind each time-frequency resource block to a set of (end device ID, HARQ process ID) tuples. Within a time-frequency resource block, each of its bound (ID of the terminal device, HARQ process ID) corresponds to a different pilot mapping chain. In this way, the combination of the time-frequency resource block and the pilot mapping chain can determine the ID of the terminal device and the HARQ process ID, and the pilot used in the current transmission can determine the RV at the position of the pilot mapping chain. Each (end device ID, HARQ process ID) can be bound to one or more time-frequency resource blocks.

An embodiment of the present application further provides a method for transmitting uplink data, and FIG. 5 is a schematic flowchart of a second embodiment of a data transmission method provided by the present application. The execution body of the method is a terminal device. In this embodiment, when transmitting the uplink data, the terminal device determines, according to the identifier of the terminal device and the redundancy version of the uplink data, information required to transmit the uplink data or resources required to be used, and sends the uplink data to the network device. As shown in FIG. 5, the method includes:

S501. The terminal device determines uplink data.

S502. The terminal device sends uplink data to the network device according to the identifier of the terminal device and the redundancy version of the uplink data, so that the network device determines, according to the association information of the uplink data, a redundancy version of the terminal device and the uplink data. The associated information is information related to when the terminal device transmits uplink data.

Exemplarily, the association information of the uplink data includes the content of the uplink data, or at least two of the content of the uplink data, the time-frequency resource block used when transmitting the uplink data, and the pilot information corresponding to the uplink data.

A further aspect of the embodiments of the present application provides a data transmission apparatus, which is configured to perform the data transmission on the network device side in the foregoing embodiment, and has the same technical features and technical effects.

FIG. 6 is a schematic structural diagram of Embodiment 1 of a device for data transmission provided by the present application. The device for data transmission may be the network device in any of the above embodiments, and the device for data transmission may be implemented by software, hardware or a combination of software and hardware. As shown in FIG. 6, the apparatus for data transmission may include: a receiving module 11 and an identification module 12.

The receiving module 11 is configured to receive uplink data from the terminal device.

The identification module 12 is configured to determine, according to the association information of the uplink data, a redundancy version of the terminal device and the uplink data, where the association information of the uplink data is information related to when the terminal device sends the uplink data.

Optionally, the association information of the uplink data includes content of the uplink data, or at least two of the content of the uplink data, the time-frequency resource block used when transmitting the uplink data, and the pilot corresponding to the uplink data.

Optionally, the association information of the uplink data includes a time-frequency resource block and a pilot corresponding to the uplink data used when the uplink data is sent; the identification module 12 is specifically configured to:

Optionally, the association information of the uplink data includes the content of the time-frequency resource block and the uplink data that are used when the uplink data is sent, and the content of the uplink data carries the identity of the terminal device; the identification module 12 is specifically configured to:

Determining the terminal device according to the identity identifier;

Optionally, the association information of the uplink data includes the content of the time-frequency resource block and the uplink data used when the uplink data is sent, and the content of the uplink data carries the identifier of the terminal device in the belonging terminal device group; the identification module 12 is specifically used to :

Optionally, the association information of the uplink data includes the content of the pilot data and the uplink data corresponding to the uplink data, and the content of the uplink data carries the identity identifier of the terminal device; the identification module 12 is specifically configured to:

Determining the terminal device according to the identity identifier;

Optionally, the association information of the uplink data includes a time-frequency resource block, a content of the uplink data, and a pilot corresponding to the uplink data, where the content of the uplink data carries the identifier of the terminal device in the associated terminal device group. The identification module 12 is specifically configured to:

Optionally, the association information of the uplink data includes the content of the uplink data and the pilot corresponding to the uplink data, where the content of the uplink data carries the identifier of the redundancy version of the uplink data; the identification module 12 is specifically configured to:

Optionally, the association information of the uplink data includes a time-frequency resource block used for transmitting the uplink data, a content of the uplink data, and a pilot corresponding to the uplink data, where the content of the uplink data carries an identifier of the redundancy version of the uplink data; 12 is specifically used for:

Optionally, the association information of the uplink data includes the content of the uplink data, and the content of the uplink data includes the identifier of the terminal device and the identifier of the redundancy version of the uplink data. The identifier module 12 is specifically configured to:

Determine the terminal device based on the identity.

Optionally, the association information of the uplink data includes the content of the time-frequency resource block and the uplink data used when the uplink data is sent, where the content of the uplink data carries the identifier of the redundancy version of the uplink data, and the terminal device is in the terminal device group to which the terminal device belongs. Identification; the identification module 12 is specifically used to:

Optionally, the uplink data further includes a mixed cyclic redundancy check bit; the N-bit bit in the hybrid cyclic redundancy check is determined by the N-bit bit in the cyclic redundancy check of the uplink data and the N in the identity identifier of the terminal device. Bit bit XOR is obtained;

Where N is a positive integer.

Optionally, the uplink data further includes a mixed cyclic redundancy check bit;

Where N is a positive integer.

Optionally, the identification module 12 is further configured to:

Optionally, on the basis of the embodiment shown in FIG. 6, FIG. 7 is a schematic structural diagram of Embodiment 2 of the apparatus for data transmission provided by the present application. As shown in FIG. 7, the device for data transmission further includes:

The establishing module 13 is configured to establish a time-frequency resource mapping chain, and send the time-frequency resource mapping chain to the terminal device;

Optionally, the uplink data includes a pilot, a control part, and a data part, and the content of the uplink data is content of the control part.

Optionally, the pilot corresponding to the uplink data is used to indicate a modulation and coding mode used by at least one part of the uplink data.

Optionally, the establishing module 13 is further configured to: establish a time-frequency resource mapping chain, a pilot mapping chain, a mapping relationship between the pilot and the terminal device, a mapping relationship between the time-frequency resource mapping chain and the terminal device group, and each terminal device group The identifier of each terminal device, the mapping relationship between each pilot and terminal device in each terminal device group, the identifier of the terminal device in the associated terminal device group, and the mapping relationship between the pilot mapping chain and the terminal device in the terminal device group. At least one item is sent to the terminal device.

A still further aspect of the embodiments of the present application is to provide a data transmission apparatus, which is used to perform the data transmission method on the terminal device side, and has the same technical features and technical effects.

FIG. 8 is a schematic structural diagram of Embodiment 3 of an apparatus for data transmission provided by the present application. The device for data transmission may be the terminal device in any of the above embodiments, and the device for data transmission may be implemented by software, hardware or a combination of software and hardware. As shown in FIG. 8, the apparatus for data transmission may include: an uplink data determining module 21 and a sending module 22;

The uplink data determining module 21 is configured to determine uplink data.

The sending module 22 is configured to send the uplink data to the network device according to the identifier of the terminal device and the redundancy version of the uplink data, so that the network device determines the redundancy version of the terminal device and the uplink data according to the association information of the uplink data, where The association information of the uplink data is information related to when the device transmits the uplink data.

A further aspect of the embodiment of the present application is to provide a network device, which is used to perform network device side in the foregoing embodiment. The method of data transmission has the same technical features and technical effects.

FIG. 9 is a schematic structural diagram of a network device provided by the present application. The network device can include a memory 31, a processor 32, at least one communication bus 33, a transmitter 34, and a receiver 35. The communication bus 33 is used to implement a communication connection between components. The memory 31 may include a high speed RAM memory, and may also include a non-volatile memory NVM, such as at least one disk memory, in which various programs may be stored for performing various processing functions and implementing the method steps of the present embodiment. In this embodiment, the transmitter 34 may be a radio frequency processing module or a baseband processing module in the base station, and the receiver 33 may be a radio frequency processing module or a baseband processing module in the base station. The transmitter 34 and the receiver 33 described above may be provided separately, and may also be integrated to form a transceiver, and both the transmitter 34 and the receiver 33 may be coupled to the processor 32. The communication bus 33 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The above communication bus 33 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9, but it does not mean that there is only one bus or one type of bus. Fig. 9 shows a simplified schematic diagram of one possible design structure of the network device involved in the above embodiment. It will be appreciated that Figure 9 only shows a simplified design of the network device. In practical applications, the network device may include any number of transmitters, receivers, processors, memories, etc., and all network devices that can implement the present application are within the scope of the present application.

Specifically, in this embodiment, the receiver 33 is configured to receive uplink data from the terminal device.

The processor 32 is configured to determine, according to the association information of the uplink data, a redundancy version of the terminal device and the uplink data, where the association information of the uplink data is information related to when the terminal device sends the uplink data.

Optionally, the association information of the uplink data includes a time-frequency resource block and a pilot corresponding to the uplink data used when the uplink data is sent; the processor 32 is specifically configured to:

Optionally, the association information of the uplink data includes the content of the time-frequency resource block and the uplink data used when the uplink data is sent, and the content of the uplink data carries the identity of the terminal device; the processor 32 is specifically configured to:

Determining the terminal device according to the identity identifier;

Optionally, the association information of the uplink data includes the content of the time-frequency resource block and the uplink data used when the uplink data is sent, and the content of the uplink data carries the identifier of the terminal device in the belonging terminal device group; the processor 32 is specifically used to :

Optionally, the association information of the uplink data includes the content of the pilot data and the uplink data corresponding to the uplink data, and the content of the uplink data carries the identity identifier of the terminal device. The processor 32 is specifically configured to:

Determining the terminal device according to the identity identifier;

Optionally, the association information of the uplink data includes a time-frequency resource block, a content of the uplink data, and a pilot corresponding to the uplink data, where the content of the uplink data carries the identifier of the terminal device in the associated terminal device group. The processor 32 is specifically used to:

Optionally, the association information of the uplink data includes the content of the uplink data and the pilot corresponding to the uplink data, where the content of the uplink data carries the identifier of the redundancy version of the uplink data; the processor 32 is specifically configured to:

Optionally, the association information of the uplink data includes a time-frequency resource block used for transmitting the uplink data, a content of the uplink data, and a pilot corresponding to the uplink data, where the content of the uplink data carries an identifier of the redundancy version of the uplink data; 32 is specifically used to:

Optionally, the association information of the uplink data includes the content of the uplink data, where the content of the uplink data includes an identifier of the terminal device and an identifier of the redundancy version of the uplink data, where the processor 32 is specifically configured to:

Determine the terminal device based on the identity.

Optionally, the association information of the uplink data includes the content of the time-frequency resource block and the uplink data used when the uplink data is sent, where the content of the uplink data carries the identifier of the redundancy version of the uplink data, and the terminal device is in the terminal device group to which the terminal device belongs. The identifier of the processor 32 is specifically used for:

Where N is a positive integer.

Optionally, the processor 32 is further configured to:

Optionally, the processor 32 is further configured to: establish a time-frequency resource mapping chain, a pilot mapping chain, a mapping relationship between the pilot and the terminal device, a mapping relationship between the time-frequency resource mapping chain and the terminal device group, and each terminal device group The identifier of each terminal device, the mapping relationship between each pilot and terminal device in each terminal device group, and the identifier of the terminal device in the associated terminal device group. At least one of a mapping relationship between a pilot mapping chain and a terminal device in the terminal device group, and sent to the terminal device.

A further aspect of the embodiments of the present application further provides a terminal device, which is configured to perform the data transmission on the device side of the terminal device in the foregoing embodiment, and has the same technical features and technical effects.

FIG. 10 is a schematic structural diagram of a terminal device provided by the present application. The terminal device may include a memory 41, a processor 42, at least one communication bus 43, a transmitter 44, and a receiver 45. Communication bus 44 is used to implement a communication connection between the components. The memory 41 may include a high speed RAM memory, and may also include a non-volatile memory NVM, such as at least one disk memory, in which various programs may be stored for performing various processing functions and implementing the method steps of the present embodiment. In this embodiment, the transmitter 44 may be a radio frequency processing module or a baseband processing module in the base station, and the receiver 44 may be a radio frequency processing module or a baseband processing module in the base station. The transmitter 44 and the receiver 44 described above may be provided separately, and may also be integrated to form a transceiver, and both the transmitter 44 and the receiver 44 may be coupled to the processor 42. The communication bus 44 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The above communication bus 44 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 10, but it does not mean that there is only one bus or one type of bus. Fig. 10 is a simplified schematic diagram showing one possible design structure of the terminal device involved in the above embodiment. It will be understood that Figure 10 only shows a simplified design of the terminal device. In practical applications, the terminal device may include any number of transmitters, receivers, processors, memories, etc., and all terminal devices that can implement the present application are within the scope of the present application.

Specifically, in this embodiment, the processor 42 is configured to determine uplink data.

The transmitter 44 is configured to send the uplink data to the network device according to the identifier of the terminal device and the redundancy version of the uplink data, so that the network device determines the redundancy version of the terminal device and the uplink data according to the association information of the uplink data, where The association information of the uplink data is information related to when the device transmits the uplink data.

Still another aspect of the embodiments of the present application provides a computer storage medium for storing computer software instructions for use in the network device, including a program for executing the method on the network device side in any of the above embodiments. Embodiments of the present application also provide a computer program product comprising instructions that, when executed by a computer, cause the computer to perform functions performed by the network device.

The embodiment of the present application further provides a chip system, where the chip system includes a processor for supporting a network device to implement the functions involved in any of the foregoing embodiments, for example, generating or processing data involved in the foregoing method and/or Or information. In one possible design, the chip system further includes a memory for holding program instructions and data necessary for the network device. The chip system can be composed of chips, and can also include chips and other discrete devices.

Still another aspect of the embodiments of the present application provides a computer storage medium for storing computer software instructions for the terminal device, which includes a program for executing the method on the terminal device side in any of the above embodiments. Embodiments of the present application also provide a computer program product comprising instructions that, when executed by a computer, cause the computer to perform functions performed by the terminal device.

The embodiment of the present application further provides a chip system, including a processor, for supporting a terminal device to implement the functions involved in any of the foregoing embodiments, for example, generating or processing data involved in the foregoing method and/or Or information. In a possible design, the chip system further includes a memory for storing the terminal device The required program instructions and data. The chip system can be composed of chips, and can also include chips and other discrete devices.

The embodiment of the present application further provides a method for indicating a redundancy version RV of Grant-free transmission data. As described below:

A method of data transmission, the method comprising:

Receiving, by the base station, data sent by the first UE, where the data includes a DMRS and a payload part, where the first resource block or the payload part or the DMRS carries an RV indicating the data Instructions;

The base station determines an RV of the data according to the first resource block or the payload portion or the DMRS.

Exemplarily, the base station determines a redundancy version of the data according to the received transmission resource or payload content of the Grant-free data or the DMRS, so that different RV data can be combined and decoded, thereby improving the reliability of the Grant-free transmission.

2. The method according to 1, the determining, by the base station, the RV of the data according to the first resource block or the payload part or the DMRS, including:

The base station determines an RV of the data based on the payload portion, the payload portion including a control portion and a data portion, the control portion carrying indication information indicating an RV of the data.

Illustratively, the control portion of the payload portion explicitly indicates the RV of the Grant-free transmission data with high indication flexibility.

3. The method according to 1, the determining, by the base station, the RV of the data according to the first resource block or the payload part or the DMRS, including:

Determining, by the base station, an RV of the data according to the first resource block, where the first resource block indicates a first RV, and the first RV is an RV of the data.

Illustratively, the RV of the data implicitly indicated by the resource block used to transmit the Grant-free data has a small indication overhead.

4. The method according to 3, before the base station determines the RV of the data according to the first resource block or the payload part or the DMRS, the base station compares the first resource block and the second resource block Configured to include:

The base station indicates that the first resource block and the second resource block have a mapping relationship, the first resource block is different from the second resource block, and the second resource block corresponds to a second RV, where the The second RV is different from the first RV.

Exemplarily, different resource blocks correspond to different RVs, and the RVs may be determined according to the resource blocks, thereby combining and decoding different RVs, thereby improving the reliability of the Grant-free data transmission.

5. The method of any of 1-4, wherein the DMRS indicates part or all of the MCS of the payload portion.

Exemplarily, the MCS indicates part or all of the MCS of the payload part, so that the UE can determine the optimal MCS according to the channel state, thereby achieving the purpose of efficiently utilizing resources. Specifically, in the case where the payload portion includes only the data portion, the DMRS indicates the MCS of the data portion; in the case where the payload portion includes the control portion and the data portion, the DMRS indicates the MCS of the control portion, or the DMRS indicates the MCS of the data portion Or, the DMRS indicates the MCS of the control part and the data part.

6. The method of any of 1-5, wherein the payload portion comprises a control portion and a data portion, the control portion further comprising one of at least one of: a UE ID of the first UE, the data portion The HARQ process ID.

Illustratively, in the case where the payload portion includes the control portion and the data portion, the control portion includes the UE ID and/or the HARQ process ID, so that the base station can distinguish from which UE the Grant-free transmission data comes from and the corresponding HARQ process, thereby Enabling the base station to combine data of the same HARQ process from the same UE, and according to RV determines how to merge to improve transmission reliability. This way of indicating the UE ID and/or HARQ process ID has the greatest indication flexibility.

The method of any one of 1-6, wherein the first resource block is associated with a group of UEs, the group of UEs at least includes the first UE, and the UE ID of the first UE is the A short identifier of the first UE in the set of UEs.

Exemplarily, the group of UEs including the first UE is bound to the first resource, and the UE ID adopts a short identifier of the first UE in the group of UEs (ie, a relative identifier in the group of UEs), which is complete. The UE ID is short in length, thereby reducing the UE ID indication overhead, thereby reducing the length of the control portion and saving transmission overhead.

8. The method according to 1, the determining, by the base station, the RV of the data according to the first resource block or the payload part or the DMRS, including:

Determining, by the base station, the RV of the data according to the first resource block and the DMRS, where the first resource block corresponds to a group of UEs, the group of UEs at least includes the first UE, and the DMRS indication station The RV of the data.

Exemplarily, a group of UEs including the first UE is bound to the first resource block, and within the first resource block, the RV of the data is indicated by the DMRS, which has the advantage of indicating that the overhead is small.

9. The method according to any one of 1-4, 6-8, wherein the DMRS indicates a UE ID of the first UE and/or a HARQ process identifier of the data.

Exemplarily, the DMRS may also be used to indicate a UE ID or a (UE ID, HARQ process ID) with a small indication overhead.

10. The method according to any one of 1-9, before the base station determines an RV of the data according to the first resource block or the payload part or the DMRS, the base station is to use the first resource. The block and the first DMRS set are configured to the first UE, the first DMRS set includes at least the DMRS, and each DMRS in the first DMRS set corresponds to a different RV of the first UE sending data.

Exemplarily, in the first resource block, since the base station configures the first DMRS set only to the first UE, the base station can determine which RV of the current data data is based on the received DMRS, that is, the base station according to the DMRS. The (UE ID, RV) of the received data can be determined.

11. The method according to any one of 1-9, before the base station determines an RV of the data according to the first resource block or the payload part or the DMRS, the base station is to use the first resource. And the first DMRS set includes at least the DMRS, and each DMRS in the first DMRS set corresponds to the first UE sent by the first UE. Different RVs of the first HARQ process data are described.

Exemplarily, in the first resource block, since the base station configures the first DMRS set only to the first HARQ process of the first UE, the base station can determine which HARQ process of the current data data is based on the received DMRS. Which RV, that is, the base station can determine the received data (UE ID, HARQ process ID, RV) according to the DMRS.

12. The method of any of 10 or 11, before the base station determines an RV of the data according to the first resource block or the payload portion or the DMRS, the base station is to use a second resource block and The first DMRS set is configured to the second UE, where the second resource block is different from the first resource block, and each DMRS in the first DMRS set corresponds to a different RV of the second UE sending data. The second UE is the same UE or a different UE as the first UE.

Exemplarily, different resource blocks can reuse the same DMRS set, so the solution of the present application can be implemented without much DMRS. In other words, the signal sequence corresponding to the DMRS does not need to be too long. In addition, the same UE can be bound to different resource blocks at the same time, so that the UE can select resources more flexibly when performing Grant-free transmission, and the transmission waiting delay is also smaller.

13. A method of indicating a redundancy version RV of Grant-free transmission data, the method comprising:

The first UE generates data, the data including a DMRS and a payload portion;

The first UE sends the data to the base station on the first resource block, where the first resource block or the payload part or the DMRS carries indication information indicating an RV of the data.

Exemplarily, the first UE indicates the redundancy version of the data by transmitting the resource or the payload content or the DMRS, so that the base station can perform combined decoding on different RV data, thereby improving the Grant-free transmission reliability.

14. The method according to 13, wherein the first resource block or the payload part or the DMRS carries indication information indicating an RV of the data, including:

The payload portion includes a control portion and a data portion, the RV of the data portion being indicated in the control portion.

Illustratively, the control portion of the payload portion explicitly indicates the RV of the Grant-free transmission data with maximum indication flexibility.

15. The method according to 13, wherein the first resource block or the payload portion or the DMRS indicates an RV of the data, including:

The first resource block indicates a first RV, and the first RV is an RV of the data.

The method according to the above, the first UE receives the configuration of the first resource block and the second resource block by the base station, where the configuration includes:

17. The method of any of 13-16, wherein the DMRS indicates part or all of the MCS of the payload portion.

18. The method of any of clauses 13-17, wherein the payload portion comprises a control portion and a data portion, the control portion further comprising one of at least one of: a UE ID of the first UE, the data portion The HARQ process ID.

Illustratively, in the case where the payload portion includes the control portion and the data portion, the control portion includes the UE ID and/or the HARQ process ID, so that the base station can distinguish from which UE the Grant-free transmission data comes from and the corresponding HARQ process, thereby The base station can combine data of the same HARQ process from the same UE and determine how to merge according to the RV, thereby improving transmission reliability. This way of indicating the UE ID and/or HARQ process ID has the greatest indication flexibility.

The method according to any one of 13-18, wherein the first resource block is associated with a group of UEs, the group of UEs at least includes the first UE, and the UE ID of the first UE is the A short identifier of the first UE in the set of UEs.

Exemplarily, the group of UEs including the first UE is bound to the first resource, and the UE ID adopts a short identifier of the first UE in the group of UEs (ie, a relative identifier in the group of UEs), which is complete. UE ID length is short, which reduces The UE ID indicates the overhead, which in turn reduces the length of the control portion and saves transmission overhead.

20. The method according to 13, wherein the first resource block or the payload portion or the DMRS indicates an RV of the data, including:

Determining, by the first resource block and the DMRS, an RV of the data, the first resource block corresponding to a group of UEs, the group of UEs at least including the first UE, and the DMRS indicating an RV of the data .

21. The method of any of 13-16, 18-20, wherein the DMRS indicates a UE ID of the first UE and/or a HARQ process identifier of the data.

The method of any one of 13-21, before the first UE sends the data, the first UE receives first configuration information of the base station, where the first configuration information includes:

The base station configures the first resource block and the first DMRS set to the first UE, where the first DMRS set includes at least the DMRS, and each DMRS in the first DMRS set is sent by the first UE. Different RVs of the data.

The method of any one of 13-21, before the first UE sends the data, the first UE receives second configuration information of the base station, where the second configuration information includes:

The base station configures the first resource block and the first DMRS set to the first HARQ process of the first UE, where the first DMRS set includes at least the DMRS, and each DMRS in the first DMRS set Corresponding to different RVs of the first HARQ process data sent by the first UE.

24. A base station, the base station comprising:

Processor, memory, transceiver and bus;

The processor, the transceiver, and the memory communicate with each other through the bus;

The transceiver is configured to receive and send data;

The memory is configured to store an instruction;

The processor, configured to execute the instructions in the memory, to perform the method of any of claims 1-12.

25. According to 24, the transceiver comprises:

Transmitter and receiver;

The transmitter is configured to send the configuration information according to any one of claims 1-12;

The receiver is configured to receive, by the receiving terminal, the data of any one of claims 1-12.

26. A terminal, the terminal comprising:

Processor, memory, transceiver and bus;

The transceiver is configured to receive and send data;

The memory is for storing instructions;

The processor is operative to execute the instructions in the memory and to perform the method of any of claims 13-23.

27. According to 26, the transceiver comprises:

Transmitter and receiver;

The receiver is configured to receive, by the base station, the configuration information according to any one of claims 13-23;

The transmitter is configured to transmit the data according to any one of claims 13-23 according to the configuration information.

The embodiment of the present application further provides a base station, where the base station has a function of implementing the behavior of the base station in the foregoing method embodiments. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to each of the above-described functions.

The embodiment of the present application further provides a terminal, which has a function of implementing the behavior of the terminal in each of the foregoing method embodiments. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to each of the above-described functions.

The embodiment of the present application further provides a communication system, which includes the base station and the terminal described in the foregoing embodiments.

The embodiment of the present application further provides a computer storage medium for storing computer software instructions used by the base station, which includes a program designed to perform the functions implemented by the base station in the foregoing embodiments.

The embodiment of the present application further provides a computer storage medium for storing computer software instructions used by the terminal, which includes a program designed to perform the functions implemented by the terminal in the foregoing embodiments.

In the traditional cellular communication system, an uplink (UL) transmission adopts a Grant-based manner, that is, a resource that the base station schedules the UE to perform UL transmission and related transmission parameters, such as a time domain and a frequency domain used for UL transmission. Airspace resources and MCS. In this case, when a UE has uplink data to be transmitted, a scheduling request is first sent to the base station, the base station sends a scheduling grant based on the scheduling request, and then the UE performs UL transmission according to the resource allocation and the transmission parameter indicated in the scheduling grant. If the UE is in an idle state, the UE needs to perform random access (interaction process including four messages) before data can be transmitted. The above Grant-based UL transmission process requires more signaling overhead, and these signaling interactions inevitably bring delays.

Currently, the 5G standard for cellular communications is being developed, and the scenarios considered include Massive Machine Type Communication (mMTC) and Ultra-reliable and Low Latency Communications for mMTC. URLLC). The data generated by the mMTC service is usually small data. If the traditional Grant-based UL transmission method is adopted, the data transmission occupies much less resources than the signaling interaction before the data transmission (such as scheduling request + scheduling authorization process or random access procedure). Resources for signaling interactions, which leads to low resource utilization, especially in the case of a large number of mMTC devices, system resources will be largely occupied by interactive signaling; URLLC services require low latency, and the above Grant-based The signaling in the UL transmission process has a large delay due to Radio Resource Control (RRC) signaling, so the traditional Grant-based UL transmission method is also difficult to meet the requirements of the URLLC service.

For the above reasons, 5G introduced Grant-free in the new Radio (NR). Transmission method for UL transmission. The so-called Grant-free transmission mode means that the UE does not need to request the UL transmission resource from the base station when the data needs to be transmitted, but selects a resource for UL transmission based on a certain rule in the Grant-free resource pool pre-configured by the base station. UL transmission. In this way, the signaling interaction in the Grant-based UL transmission process can be omitted, thereby reducing signaling overhead and transmission delay, and is particularly suitable for packet transmission and delay sensitive services.

Currently, the 5G-NR standard has explicitly agreed that mMTC and URLLC support Grant-free transmission. In addition, the standard also reached the following agreement: The resource allocation of UL Grant-free transmission should include time-frequency resources, modulation and coding (MCS), reference signal parameters, and repetition transmission times.

The number of resources is always limited compared to the number of users. Therefore, no matter which rule is used to select the UL Grant-free resource in the Grant-free resource pool, it is always possible to select the same resource between different UEs, which causes the UL data of different UEs to collide. From this perspective, the reliability of Grant-free transmission is lower than that of Grant-based. Therefore, for Grant-free transmission, the retransmission mechanism is particularly important.

The traditional Grant-based transmission uses the HARQ mechanism to improve the transmission reliability. The base station can indicate the UL retransmission resource of the UE and the redundancy version (RV) of the UL transmission in Downlink Control Information (DCI). Of course, the UE can also The next RV to be transmitted is determined in a fixed order so that the base station combines and decodes different RVs of the same transport block (TB). For example, in UL non-adaptive HARQ, the order in which UEs transmit different RVs of the same TB is 0, 2, 3, 1. However, in Grant-free transmission, the base station does not know in advance who will transmit, so it is impossible to schedule which RV the UE transmits. In the Grant-free transmission, the base station cannot even determine whether the received UL data of the reception errors belong to the same TB, and therefore it is impossible to determine which UL data to merge. In summary, the traditional HARQ mechanism cannot be directly used for Grant-free transmission.

Illustratively, one way to indicate the RV of Grant-free transmission data is:

The base station divides the pilot into a plurality of sets P1, P2, P3, ... which do not overlap each other, and each set corresponds to one RV. Then, select a pilot from each set to form a pilot map chain. For example, p1 is selected from the set P1, p2 is selected from the set P2, p3, ... is selected from the set P3, and the pilot map chain p1 → p2 → p3 → ... is formed. According to the above rules, the base station can construct multiple pilot mapping chains, and the pilots in different pilot mapping chains do not overlap. The base station configures all pilot mapping chains to the UE. When the UE has data to transmit, a pilot mapping chain (for example, p1→p2→p3→...) is selected from the pilot mapping chain configured by the base station for the current transmission process. When the UE transmits RV0 of the current data, p1 is used; when RV2 is transmitted, p2 is used; when RV3 is transmitted, p3 is used; when RV1 is transmitted, p4 is used; when the base station receives multiple uplink data that is not correctly received, based on pilot The mapping chain determines whether these data belong to the same UE and determines the RV of each data. For example, if the base station receives the data of the pilots p1, p2, and p3, it considers that they belong to the same TB RV0, RV2, and RV3 of the same UE, thereby performing corresponding merge decoding. Among them, the pilot is a general term for various reference signals, for example, the pilot can be a DMRS.

However, the number of pilots available in the system is limited, so the configurable pilot mapping chain is also limited, which leads to the inevitable occurrence of different UEs selecting the same pilot mapping chain. When this happens, the base station will be unable to distinguish data from different UEs, which in turn will result in merge decoding errors. Considering the mMTC scenario, the number of UEs is particularly dense, and this situation is highly probable, which greatly reduces the efficiency of Grant-free transmission.

For the RV determination and indication problem when using HARQ in UL Grant-free transmission, the present application proposes a new scheme, so that the base station can accurately determine the RV of the currently received data, and can determine whether different RV data belong to the same transport block of the same user. And then perform the merge operation to improve the reliability of the Grant-free transmission.

Let's first define some basic concepts related to Grant-free:

Contention Transmission Unit (CTU): The basic resource unit when the UE performs Grant-free transmission. The CTU can be defined as a time-frequency resource block. The following can be simply referred to as a resource block. In this case, the time-frequency resource corresponding to one CTU is uniquely determined by the time domain start point, the time domain length, the frequency domain start point, and the frequency domain width. The CTU can also be extended to define resources in other dimensions. For example, if non-orthogonal multiple access technology (such as SCMA) is used for Grant-free transmission, the definition of CTU can also be extended to the code domain, that is, CTU is defined as time-frequency resources and A combination of code domain resources. Specifically for SCMA, CTU is defined as a combination of time-frequency resources, SCMA codebooks, and pilot sequences. In order to facilitate the description of our solution, the CTU is defined as a time-frequency resource block as an example, but it is easy to understand that all embodiments of the present application can be used in the case where the CTU adopts other definitions.

Contention Transmission Area (CTA): A CTA is defined as an air interface time-frequency resource defined by a specific time and frequency. 11 is a schematic diagram of a contention transmission area provided by an embodiment of the present application. As shown in FIG. 11, different CTAs do not overlap each other in time or frequency (but may be in close proximity, such as CTA1 and CTA2 in FIG. 11, or CTA2 and CTA3). ). Each CTA can contain one or more CTUs. When the UE performs a Grant-free transmission, one or more CTUs are selected for transmission in a certain CTA. It should be specially noted that there is no essential difference between the CTU domains, and the CTU can be regarded as a CTA containing only one CTU.

In the method for determining and indicating the RV of the Grant-free transmission data, the UE indicates the RV of the currently transmitted TB by implicit or explicit manner, and the base station determines the RV of the received data based on the same rule, thereby performing a merge operation. To improve the reliability of the transmitted data.

Specifically, the method for determining a redundancy version (RV) of Grant-free transmission data proposed by the present application is as follows: a base station receives data transmitted by a first UE on a first resource block, where the data includes a DMRS and a payload portion; Determining an RV of the data based on the first resource block or the payload portion or the DMRS.

The first resource block is a CTA in a CTA or a CTA configured by the base station for the UE. Unless otherwise stated, the first resource block, the second resource block, and the resource block mentioned in the present application refer to a CTA or a CTU configured by the base station for the UE.

When the base station performs the UL HARQ merging operation, the base station needs to determine that the data of the two different RVs currently received are from the same HARQ process of the same UE (HARQ process, which is identified by the HARQ process ID, and the HARQ process ID is also called the HARQ process number). That is, retransmission data for the same TB. In a legacy LTE system, a base station may schedule resources, MCS, RV, and HARQ process IDs for each UE to perform UL HARQ transmission. However, in the Grant-free transmission, the base station cannot predict in advance which UE will transmit, and since the Grant-free transmission is initialized and transmitted by the UE, there is no scheduling signaling from the base station before, so the Grant-free transmission needs to be determined by other methods. The UE ID of the data and the HARQ process ID ensure that the data of the same HARQ process of the same UE is merged by the base station.

The following gives an example of several possible ways to determine the UE ID:

The first method is to indicate the UE ID of the currently transmitted data through the DMRS. The UE and the base station need to agree on the correspondence between the UE ID and the DMRS in advance. The UE can only use the DMRS corresponding to itself when performing the Grant-free transmission. The base station can uniquely determine the UE ID of the transmitting UE by receiving a DMRS in the CTU. Considering that the Grant-free transmission is mainly small packets, there is a small possibility that there are multiple HARQ processes. Therefore, it is only necessary to indicate the UE ID through the DMRS without indicating the HARQ process ID. However, if it is considered that the UE may need to transmit multiple small packets and these small packets belong to delay sensitive services, then it is necessary to consider using multiple HARQ processes. For example, the UE has multiple small packets. Before receiving the acknowledgement information of the previous small packet, the UE sends the next small packet. At this time, the two small packets need to be distinguished by using different HARQ process IDs. In this case, the scheme based on the DMRS indication UE ID may be extended to indicate the HARQ process. ID, that is, each UE is bound to multiple DMRSs, where each DMRS corresponds to a different HARQ process ID. Multiple DMRSs bound by different UEs do not overlap. In other words, each DMRS corresponds to a (UE ID, HARQ process ID) tuple. Of course, the correspondence between the DMRS and the (UE ID, HARQ process ID) needs to be agreed in advance. Such a convention may be explicitly indicated by the base station to the UE, for example, by high-level signaling; or may be calculated by the UE itself based on a certain rule, for example, the UE calculates its own DMRS corresponding to each HARQ process ID based on its own UE ID. It may also be a standard pre-defined, for example, the UE ID is C-RNTI, and the standard pre-defines the DMRS corresponding to each (C-RNTI, HARQ process ID).

The second method is that the payload portion of the Grant-free data transmitted by the UE except the DMRS specifically includes two parts: a control part and a data part. Wherein, the control part transmits at a fixed, lower rate, the control part adopts variable rate transmission, the control part indicates the MCS used by the data part and the UE ID of the current UE; or the DMRS indication control part of the Grant-free data MCS, the control part indicates the MCS adopted by the data part and the UE ID of the current UE; or, the DMRS of the Grant-free data indicates the MCS of the control part and the data part (ie, the control part and the data part adopt the same MCS), and the control part indicates the current UE UE ID. The UE ID included in the control part may be the complete ID of the UE, such as the C-RNTI of the UE. However, since the full UE ID is usually long, for example, the length of the C-RNTI is 16 bits, this will cause the control part to be too long, which increases the indication overhead. Therefore, each resource block can be bound to a group of UEs, and the same UE can be bound to one or more resource blocks at the same time, and the control part includes the short ID of the UE, and the short ID of the UE is only in the UE bound to the current resource block. The group is unique, which shortens the UE ID length. For example, if a resource block is allowed to bind up to 8 UEs, the short ID can be only 3 bits, which is much smaller than the 16 bits of the C-RNTI. The resource block bound by each UE, the correspondence between the short ID of the UE in one resource block and the complete UE ID may be specified by the base station, for example, by explicit allocation by signaling; or by the UE based on the complete UE ID. The predefined rule is calculated, and the base station calculates a resource block bound by each UE and a short ID of the UE in each bound resource block based on the same rule. When the UE needs to perform Grant-free transmission, only one of the resource blocks bound to itself can be selected for transmission. The UE ID (possibly the short ID) included in the control part may be explicitly included in the control part, for example, there is a special N-bit in the control part for carrying the UE ID; or XOR on the CRC, for example, control The part includes an 8-bit CRC. If the length of the UE ID is 3 bits, the UE ID can be XORed with the 3 bits in the 8-bit CRC. When the base station receives the control part, the CRC is first calculated, and then the calculated CRC and the CRC carried therein are calculated. If the other 5 bits except the 3 bits corresponding to the UE ID are 0, the 3 bits corresponding to the UE ID are the UE ID; or the UE ID is divided into two parts, and some are explicitly included in the XOR. In the control section, the other part is XORed with the CRC of the control section. The HARQ process ID may also be included in the control part to indicate the HARQ process to which the current data belongs. The base station can combine and decode data from different RVs of the same UE and the same HARQ process to improve transmission reliability.

The third method is to bind each resource block to a group of UEs or a group of (UE ID, HARQ process ID) tuples, and in the same resource block, distinguish the UE ID or (UE ID) of the UE by DMRS. HARQ process ID). The same UE can simultaneously bind one or more resource blocks. For example, the first resource block is bound to the first group of UEs, and in the first resource block, different UEs or different (UE ID, HARQ process ID) are distinguished by different DMRSs; the second resource block is bound to the second group of UEs. In the second resource block, different UEs or different (UE ID, HARQ process ID) are distinguished by different DMRSs. The same UE may belong to the first group of UEs and the second group of UEs at the same time. Obviously, the third method is a combination of the first method and the second method. Compared to the first method, the method does not require too many DMRSs to implement any two UEs or any two (UE ID, HARQ process ID) distinctions because this method only requires Multiple UEs or multiple UEs (HIDs) can be multiplexed with different DMRSs. The number of UEs in the system exceeds the number of DMRSs. Corresponding question. In fact, the number of DMRS available in the system is indeed limited. Compared to the second method, the method does not require special bits to indicate the temporary ID, so the indication overhead is smaller. Similar to the second method, the resource block bound by each UE, the correspondence between the DMRS and the UE ID or the (UE ID, HARQ process ID) in each resource block may be specified by the base station, or may be based on the UE. The complete UE ID calculation is calculated according to predefined rules, or predefined by standards. For example, the standard specifies that each resource block is bound to a maximum of 8 UEs or 8 (UE ID, HARQ process ID), and 8 corresponding DMRSs are specified, and 8 DMRSs corresponding to all resource blocks may be identical or partially identical. It can also be completely different.

Exemplarily, if the definition of the second medium and short ID is adopted, or all resource blocks in the third method are defined to have the same DMRS, the UE is required to have a registration at the base station, otherwise the base station cannot be based on the short short ID or The DMRS distinguishes which device the received data belongs to which complete UE ID indication. This means that when a UE in idle state moves into the coverage of a new base station, Grant-free cannot be used for transmission immediately because the base station does not have the short ID or corresponding DMRS of the UE. At this time, the UE may first access through the traditional random access procedure, and after obtaining the short ID or the corresponding DMRS, the Grant-free can be used for access. In another solution, the standard reserves a temporary ID or reserves a DMRS for Grant-free access of such UEs. However, after the data transmission is completed, the base station should acquire the complete UE ID of the UE through other interaction procedures, and then allocate a temporary ID or DMRS for the UE.

It should be specially noted that the load portion may include the control portion and the data portion, or may only include the data portion.

Exemplarily, in the scenario shown in FIG. 1, the base station may receive UL data sent by the UE through the Grant-free mode. It is possible that not every UE supports Grant-free transmission. For example, UE1 and UE3 support Grant-free transmission, and UE2 does not support Grant-free transmission. From the perspective of product form, the base station is a device with central control function and capable of configuring Grant-free resources and receiving Grant-free data, such as a macro base station, a micro base station, a hotspot (pico), a home base station (Femeto), and a transmission point ( TP), relay, etc.; UE is a device with Grant-free transmission capability, especially terminal devices such as mobile phones, computers, wristbands, smart watches, data cards, sensors, and the like. For Sidelink (D2D), for example, the link between the wristband and the mobile phone in the wristband-mobile phone-base station, if the wristband also supports Grant-free transmission, the wristband can be regarded as the UE, and the mobile phone is regarded as the UE. Base station.

The manner in which the base station determines the RV of the transmission data will be described in detail below in conjunction with the specific embodiments.

Embodiment 1 of the present application: Explicitly indicating RV for transmitting data

It is assumed that the Grant-free data transmitted by the first UE in the first resource block includes a DMRS and a payload portion, and the payload portion is composed of a control portion and a data portion, and the control portion may include an RV indication for indicating the RV of the current data, and FIG. 12 is A schematic structural diagram of a payload portion of Grant-free data provided by an embodiment of the present application. Of course, Grant-free data also includes DMRS. Wherein, the control part transmits at a fixed, lower rate, the control part adopts variable rate transmission, the control part indicates the MCS used by the data part; or the DMRS of the Grant-free data indicates the MCS of the control part, and the control part indicates the data Partially adopted MCS; or, the DMRS of the Grant-free data indicates the MCS of the control part and the data part (ie, the control part and the data part adopt the same MCS). If the HARQ process of the Grant-free is allowed to be retransmitted by using multiple HARQ processes, the control part may further include a HARQ process ID, which is used to indicate the HARQ process to which the current data belongs. The base station can combine and decode data from different RVs of the same UE and the same HARQ process to improve transmission reliability. Note that in this embodiment, the RV of the current data actually refers to the RV of the data portion of the current data, and the HARQ process to which the current data belongs actually refers to the data portion of the current data. The genus of the HARQ process.

In the foregoing second method for indicating the UE ID, the UE ID may have multiple carrying modes in the control part, and the RV indication and/or the HARQ process ID may also adopt a similar carrying manner: it may be explicitly included in the control part, or It is XOR on the CRC, or the UE ID is divided into two parts, one part is explicitly included in the control part, and the other part is XORed with the CRC.

The UE from which the data comes from can be indicated by any of the above three methods, or by any other method.

Embodiment 2 of the present application: an RV that implicitly indicates transmission of data by using a transmission resource

The base station may configure multiple CTAs for Grant-free, each of which contains one or more CTUs. These CTAs can occur periodically, called the CTA transmission cycle, as shown in Figure 3. The duration of the CTA transmission period can be configured by the base station, for example, by using a System Information Block (SIB) to indicate the duration of the CTA transmission period.

During the same CTA transmission period, a mapping relationship may be established between CTUs in different CTAs, which is called a time-frequency resource mapping chain (resource mapping chain), which is used to implicitly indicate the RV of the transmitted data, that is, in the same resource mapping chain. Different resource blocks correspond to different RVs.

Exemplarily, the UE ID of the transmitting UE and the possible HARQ process ID may be indicated by using any one of the foregoing three methods for indicating the UE ID. It should be noted that in the second and third methods, “binding each resource block with a group of UEs, and the same UE can be bound to one or more resource blocks at the same time” is specifically embodied in this embodiment. A resource mapping chain is bound to a group of UEs, and the same UE can be bound to one or more resource mapping chains at the same time. Based on these methods, the base station can determine whether the received incorrectly decoded data belongs to the same UE, and further determines to combine and decode data of different RVs of the same UE.

Embodiment 3 of the present application: pilot implicitly indicates RV of transmission data, and each resource block is bound to a group of UEs

In order to realize that the base station can determine the transmitting UE and the RV of the current data according to the pilot, each UE needs to correspond to a pilot mapping chain, which requires that the number of configurable pilot mapping chains is not less than the number of UEs. To do this, the number of each pilot must be very long, which is not feasible in practical systems. On the premise that the number of pilot mapping chains is limited, in order to enable the base station to determine the UE ID and RV of the transmitting UE of the current data according to the pilot, each resource block may be bound to a group of UEs, for example, each UE is bound to the CTA. One or more CTAs within the period.

For a particular UE, in each CTA bound to it, the UE uniquely corresponds to a pilot mapping chain. Different CTAs bound to the same UE may correspond to the same or different pilot mapping chains. In different CTAs, the pilot mapping chain can be multiplexed. For example, each CTA is allowed to bind up to 10 UEs, and the RV of the data includes at most 4 versions, and only 10×4=40 pilots can be implemented to implement the solution of this embodiment. It should be noted again that there is no essential difference between the CTA and the CTU. When the CTA contains only one CTU, it is the CTU, so the CTA here can also be replaced with the CTU.

For example, 40 DMRSs are named p1 to p40, respectively, and each adjacent 4 DMRSs form a pilot mapping chain, thereby forming 10 pilot mapping chains, corresponding to 10 UEs in each CTA (each CTA corresponds to The short IDs of the 10 UEs are denoted as UE1 to UE10). Suppose a user is bound to two CTAs. The short ID in CTA1 is UE1, the corresponding pilot mapping chain is p1→p2→p3→p4, the short ID in CTA2 is UE5, and the corresponding pilot mapping chain is p17. → p18 → p19 → p20, CTA1 is in front of CTA2 in the time domain. If USER0 sends RV0 with p1 but receives NACK in CTA1, USER0 sends RV2 with p18 in CTA2. Since the short ID of USER0 in CTA1 and the short ID in CTA2 (or the corresponding pilot mapping chain) are known in advance with the base station, the base station detects the data of DMRS as p1 in CTA1 and detects it in CTA2. DMRS is the number of p18 According to this, they can know that they correspond to RV0 and RV2 of the same data of User0, and then combine them and decode them.

If it is considered that the UE may perform transmission of multiple HARQ processes at the same time, each resource block may also be bound to a set of (UE ID, HARQ process ID) tuples. Within a resource block, each of its bound (UE ID, HARQ process ID) corresponds to a different pilot mapping chain. In this way, the combination of the resource block and the pilot mapping chain can determine the UE ID and the HARQ process ID, and the pilot used in the current transmission can determine the RV in the position of the pilot mapping chain. Each (UE ID, HARQ process ID) can be bound to one or more resource blocks.

Of course, for the case where transmission of multiple HARQ processes is possible at the same time, the method in the first embodiment of determining the RV of the transmission data may be adopted, that is, the UL transmission of each UE includes a control part and a data part, and the control part carries the HARQ. Process ID.

For a specific UE, within the CTA bound to it, the CTU used by the current transmission may be selected according to a predefined rule, for example, a CTU is randomly selected for transmission.

Which resource block bindings the UE or (UE ID, HARQ process ID) can be configured by the base station, for example, by RRC signaling. The pilot mapping chain configuration, UE or (UE ID, HARQ process ID) corresponding to which pilot mapping chain in each bound resource block can be configured by the base station, for example, by RRC signaling, or can be standard predefined. For example, the standard specifies that all resource blocks are configured with the same pilot mapping chain and specifies the structure of each pilot mapping chain; for example, the standard specifies that one or more of the information such as the UE ID, the HARQ process ID, and the resource block identifier may be used. The corresponding mapping chain of the UE or (UE ID, HARQ process ID) in each bound resource block is calculated according to a predefined rule.

Exemplarily, the base station receives three possible reception results of data transmitted by a certain UE through Grant-free, and different results determine the feedback response of the base station:

The first possible result: the base station successfully detects the UE ID and corresponding data. At this time, the base station sends an ACK to the UE;

The second possible result: the base station successfully detected the UE ID but failed to receive the data correctly. At this time, the base station sends a NACK to the UE and waits for the UE to retransmit.

A third possible outcome: The base station did not successfully detect any information. At this point, the base station does not send any feedback.

The second possible result and the third possible result are both cases where the transmission fails, and the UE needs to perform retransmission. Based on the above analysis, the UE can determine which RV of the data to transmit based on the different response responses of the base station. After the UE sends the current RV of the data

If a NACK is received, the next RV of the data is sent;

If no feedback is received, the current RV of the data is still sent.

In the case that the UE determines and transmits the retransmission version of the data according to the above rules, after the base station receives the data that meets the second possible result and sends the NACK, the next received transmission from the UE must be the data. An RV. In this way, the base station can combine different retransmission versions of the same data to improve transmission reliability.

The data transmitted by the UE using the Grant-free may indicate the UE ID and the possible HARQ process ID by any one of the foregoing three methods, and may also explicitly or implicitly indicate the UE ID and the possible HARQ process ID by any other method. .

The embodiment of the present application may indicate the RV of the UL Grant-free HARQ transmission in an implicit or explicit manner, so that the base station can combine and decode different RVs of the same transport block from the same UE, thereby improving the reliability of the Grant-free transmission. .

Further, the UE ID of the data sender and the current data may also be indicated by implicit or explicit means. The HARQ process ID enables the base station to correctly determine whether the received data is from the same UE and the same HARQ process, and avoids errors caused by combining data of different UEs or data of different HARQ processes.

The relevant parts of the method embodiments of the present application may be referred to each other; the apparatus provided in each device embodiment is used to execute the method provided by the corresponding method embodiment, so each device embodiment may refer to related methods in the related method embodiments. Partial understanding.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. 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 terms "first", "second", "third", "fourth", etc. (if present) in the specification and claims of the present application and the above figures are used to distinguish similar objects, and are not necessarily used for Describe a specific order or order. It is to be understood that the data so used may be interchanged where appropriate, such that the embodiments of the present application described herein can be implemented, for example, in a sequence other than those illustrated or described herein. In addition, the terms "comprises" and "comprises" and "the" and "the" are intended to cover a non-exclusive inclusion, for example, a process, method, system, product, or device that comprises a series of steps or units is not necessarily limited to Those steps or units may include other steps or units not explicitly listed or inherent to such processes, methods, products or devices.

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.

The functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, and the program code can be stored. Medium.

Finally, it should be noted that the above embodiments are only for explaining the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that The technical solutions described in the foregoing embodiments may be modified, or some or all of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the technical solutions of the embodiments of the present application. range.

Claims

A method of data transmission, characterized in that the method comprises:

The network device receives uplink data from the terminal device;

Determining, by the network device, the redundancy version of the terminal device and the uplink data according to the association information of the uplink data, where the association information of the uplink data is related to when the terminal device sends the uplink data Information.
The method according to claim 1, wherein the association information of the uplink data includes content of the uplink data, or includes content of the uplink data, and a time-frequency resource block used when transmitting the uplink data. And at least two of the pilots corresponding to the uplink data.
The method according to claim 2, wherein the association information of the uplink data includes a time-frequency resource block used when the uplink data is sent, and a pilot corresponding to the uplink data; Determining, by the associated information of the uplink data, the redundancy version of the terminal device and the uplink data, including:

Determining, by the network device, a redundancy version of the uplink data according to a number of the time-frequency resource block in an associated time-frequency resource mapping chain;

Determining, by the network device, the terminal device according to the pilot, and a mapping relationship between a pilot and a terminal device preset in the network device;

The time-frequency resource mapping chain includes at least two time-frequency resource blocks, and different time-frequency resource blocks in the time-frequency resource mapping chain correspond to different redundancy versions of the same uplink data.
The method according to claim 2, wherein the association information of the uplink data includes a time-frequency resource block and a content of the uplink data used when the uplink data is sent, and a content carrying of the uplink data Determining an identity of the terminal device; the network device determining, according to the association information of the uplink data, the redundancy version of the terminal device and the uplink data, including:

Determining, by the network device, a redundancy version of the uplink data according to a number of the time-frequency resource block in an associated time-frequency resource mapping chain;

Determining, by the network device, the terminal device according to the identity identifier;

The time-frequency resource mapping chain includes at least two time-frequency resource blocks, and different time-frequency resource blocks in the time-frequency resource mapping chain correspond to different redundancy versions of the same uplink data.
The method according to claim 2, wherein the association information of the uplink data includes a time-frequency resource block and a content of the uplink data used when the uplink data is sent, and a content carrying of the uplink data The identifier of the terminal device in the associated terminal device group; the network device determining, according to the association information of the uplink data, the redundancy version of the terminal device and the uplink data, including:

Determining, by the network device, a redundancy version of the uplink data according to a number of the time-frequency resource block in an associated time-frequency resource mapping chain;

Determining, by the network device, a terminal device to which the terminal device belongs according to a time-frequency resource mapping chain to which the time-frequency resource block belongs, and a mapping relationship between a time-frequency resource mapping chain and a terminal device group preset in the network device group;

Determining, by the network device, the terminal device in the terminal device group according to the identifier of the terminal device in the associated terminal device group;

The time-frequency resource mapping chain includes at least two time-frequency resource blocks, and the time-frequency resource mapping chain is different. The time-frequency resource blocks correspond to different redundancy versions of the same uplink data.
The method according to claim 2, wherein the association information of the uplink data includes a time-frequency resource block used when the uplink data is sent, and a pilot corresponding to the uplink data; Determining, by the associated information of the uplink data, the redundancy version of the terminal device and the uplink data, including:

Determining, by the network device, a redundancy version of the uplink data according to a number of the time-frequency resource block in an associated time-frequency resource mapping chain;

Determining, by the network device, a terminal device to which the terminal device belongs according to a time-frequency resource mapping chain to which the time-frequency resource block belongs, and a mapping relationship between a time-frequency resource mapping chain and a terminal device group preset in the network device group;

Determining, by the network device, the terminal device in the terminal device group according to the pilot information, a mapping relationship between a preset pilot in the network device, and a terminal device in a terminal device group;

The time-frequency resource mapping chain includes at least two time-frequency resource blocks, and different time-frequency resource blocks in the time-frequency resource mapping chain correspond to different redundancy versions of the same uplink data.
The method according to claim 2, wherein the association information of the uplink data includes a pilot corresponding to the uplink data and content of the uplink data, and content of the uplink data carries an identity of the terminal device And determining, by the network device, the redundancy version of the terminal device and the uplink data according to the association information of the uplink data, including:

Determining, by the network device, a redundancy version of the uplink data according to a number of the pilot in an associated pilot mapping chain;

Determining, by the network device, the terminal device according to the identity identifier;

The pilot mapping chain includes at least two pilots, and different pilots in the pilot mapping chain correspond to different redundancy versions of the same uplink data.
The method according to claim 2, wherein the association information of the uplink data includes a time-frequency resource block used for transmitting the uplink data, a content of the uplink data, and a pilot corresponding to the uplink data. The content of the uplink data carries the identifier of the terminal device in the associated terminal device group; the network device determines, according to the association information of the uplink data, the redundancy version of the terminal device and the uplink data, include:

Determining, by the network device, a redundancy version of the uplink data according to a number of the pilot in an associated pilot mapping chain;

Determining, by the network device, the terminal device group to which the terminal device belongs according to the mapping relationship between the time-frequency resource block and the terminal device group in the network device according to the time-frequency resource block;

Determining, by the network device, the terminal device in the terminal device group according to the identifier of the terminal device in the associated terminal device group;

The pilot mapping chain includes at least two pilots, and different pilots in the pilot mapping chain correspond to different redundancy versions of the same uplink data.
The method according to claim 2, wherein the association information of the uplink data includes a time-frequency resource block used when the uplink data is sent, and a pilot corresponding to the uplink data; Determining, by the associated information of the uplink data, the redundancy version of the terminal device and the uplink data, including:

Determining, by the network device, a redundancy version of the uplink data according to a number of the pilot in an associated pilot mapping chain;

The network device presets a time-frequency resource block and a terminal device group in the network device according to the time-frequency resource block. a mapping relationship, determining a terminal device group to which the terminal device belongs;

Determining, by the network device, the mapping relationship between the pilot mapping chain to which the pilot belongs, the preset pilot mapping chain in the network device, and the terminal device in the terminal device group, in the terminal device group Terminal Equipment;

The pilot mapping chain includes at least two pilots, and different pilots in the pilot mapping chain correspond to different redundancy versions of the same uplink data.
The method according to claim 2, wherein the association information of the uplink data includes a content of the uplink data and a pilot corresponding to the uplink data, and content of the uplink data carries redundancy of the uplink data. And determining, by the network device, the redundancy version of the terminal device and the uplink data, according to the association information of the uplink data, including:

Determining, by the network device, a redundancy version of the uplink data according to the identifier of the redundancy version;

The network device determines the terminal device according to the pilot, and a mapping relationship between a preset pilot and a terminal device in the network device.
The method according to claim 2, wherein the association information of the uplink data includes a time-frequency resource block used for transmitting the uplink data, a content of the uplink data, and a pilot corresponding to the uplink data. The content of the uplink data carries an identifier of the redundancy version of the uplink data, and the network device determines, according to the association information of the uplink data, the redundancy version of the terminal device and the uplink data, including:

Determining, by the network device, a redundancy version of the uplink data according to the identifier of the redundancy version;

Determining, by the network device, the terminal device group to which the terminal device belongs according to the time-frequency resource block and the mapping relationship between the time-frequency resource block and the terminal device group preset in the network device;

The network device determines the terminal device in the terminal device group according to the mapping relationship between the pilot, the preset pilot in the network device, and the terminal device in the terminal device group.
The method according to claim 2, wherein the association information of the uplink data includes content of the uplink data, and the content of the uplink data includes an identity of the terminal device and redundancy of the uplink data. The identifier of the version, the network device determining, according to the association information of the uplink data, the redundancy version of the terminal device and the uplink data, including:

Determining, by the network device, a redundancy version of the uplink data according to the identifier of the redundancy version;

The network device determines the terminal device according to the identity identifier.
The method according to claim 2, wherein the association information of the uplink data includes a time-frequency resource block and a content of the uplink data used when the uplink data is sent, and a content carrying of the uplink data Determining an identifier of the redundancy version of the uplink data and an identifier of the terminal device in the associated terminal device group; the network device determining, according to the association information of the uplink data, the redundancy of the terminal device and the uplink data Version, including:

Determining, by the network device, a redundancy version of the uplink data according to the identifier of the redundancy version;

Determining, by the network device, the terminal device group to which the terminal device belongs according to the mapping relationship between the time-frequency resource block and the terminal device group in the network device according to the time-frequency resource block;

The network device determines the terminal device in the terminal device group according to the identifier of the terminal device in the associated terminal device group.
The method according to any one of claims 4, 7 and 12, wherein the uplink data further comprises a mixed cyclic redundancy check bit;

N bits in the mixed cyclic redundancy check are N bits in a cyclic redundancy check of the uplink data XORed with the N-bit bit in the identity of the terminal device;

Where N is a positive integer.
The method according to any one of claims 5, 8, and 13, wherein the uplink data further comprises a mixed cyclic redundancy check bit;

The N-bit bit in the hybrid cyclic redundancy check is obtained by X-bits of the cyclic redundancy check of the uplink data and the N-bit in the identifier of the terminal device in the associated terminal device group. ;

Where N is a positive integer.
The method according to any one of claims 1 to 15, wherein the method further comprises:

The network device determines, according to the association information of the uplink data, a hybrid automatic repeat request process that sends the uplink data.
The method according to any one of claims 3 to 6, wherein before the network device receives the uplink data from the terminal device, the method further includes:

The network device establishes a time-frequency resource mapping chain, and sends the time-frequency resource mapping chain to the terminal device;

The different time-frequency resource blocks in the resource mapping chain belong to different contention transmission areas, and the time-frequency resources of the contention transmission areas do not overlap, and the time-frequency resource blocks belonging to the same contention transmission area correspond to the same redundancy version.
The method according to any one of claims 2 to 17, wherein the uplink data comprises a pilot, a control part and a data part, and the content of the uplink data is the content of the control part.
The method according to claim 18, wherein the pilot corresponding to the uplink data is used to indicate a modulation and coding mode adopted by at least one part of the uplink data.
A method of data transmission, characterized in that the method comprises:

The terminal device determines uplink data;

The terminal device sends the uplink data to the network device according to the identifier of the terminal device and the redundancy version of the uplink data, so that the network device determines the terminal device according to the association information of the uplink data. And a redundancy version of the uplink data, where the association information of the uplink data is information related to when the terminal device sends the uplink data.
The method according to claim 20, wherein the association information of the uplink data includes content of the uplink data, or includes content of the uplink data, and a time-frequency resource block used when transmitting the uplink data. And at least two of the pilot information corresponding to the uplink data.
A device for data transmission, the device for data transmission is a network device, wherein the device comprises:

a receiving module, configured to receive uplink data from the terminal device;

An identification module, configured to determine, according to the association information of the uplink data, a redundancy version of the terminal device and the uplink data, where the association information of the uplink data is when the uplink data is sent by using the terminal device Relevant information.
The device according to claim 22, wherein the association information of the uplink data includes content of the uplink data, or includes content of the uplink data, and a time-frequency resource block used when transmitting the uplink data. And at least two of the pilots corresponding to the uplink data.
The apparatus according to claim 23, wherein the association information of the uplink data includes a time-frequency resource block used when the uplink data is sent, and a pilot corresponding to the uplink data; to:

Determining, according to the number of the time-frequency resource block in the associated time-frequency resource mapping chain, a redundancy version of the uplink data;

Determining the terminal device according to the pilot, and a mapping relationship between a pilot and a terminal device preset in the network device;

The time-frequency resource mapping chain includes at least two time-frequency resource blocks, and different time-frequency resource blocks in the time-frequency resource mapping chain correspond to different redundancy versions of the same uplink data.
The device according to claim 23, wherein the association information of the uplink data includes a time-frequency resource block and a content of the uplink data used when the uplink data is sent, and a content carrying device of the uplink data The identity of the terminal device; the identification module is specifically configured to:

Determining, according to the number of the time-frequency resource block in the associated time-frequency resource mapping chain, a redundancy version of the uplink data;

Determining the terminal device according to the identity identifier;

The time-frequency resource mapping chain includes at least two time-frequency resource blocks, and different time-frequency resource blocks in the time-frequency resource mapping chain correspond to different redundancy versions of the same uplink data.
The device according to claim 23, wherein the association information of the uplink data includes a time-frequency resource block and a content of the uplink data used when the uplink data is sent, and a content carrying device of the uplink data The identifier of the terminal device in the associated terminal device group; the identification module is specifically configured to:

Determining, according to the number of the time-frequency resource block in the associated time-frequency resource mapping chain, a redundancy version of the uplink data;

Determining, according to the mapping relationship between the time-frequency resource mapping chain to which the time-frequency resource block belongs, and the mapping relationship between the time-frequency resource mapping chain and the terminal device group in the network device, determining the terminal device group to which the terminal device belongs;

Determining, in the terminal device group, the terminal device according to the identifier of the terminal device in the associated terminal device group;

The time-frequency resource mapping chain includes at least two time-frequency resource blocks, and different time-frequency resource blocks in the time-frequency resource mapping chain correspond to different redundancy versions of the same uplink data.
The apparatus according to claim 23, wherein the association information of the uplink data includes a time-frequency resource block used when the uplink data is sent, and a pilot corresponding to the uplink data; to:

Determining, according to the number of the time-frequency resource block in the associated time-frequency resource mapping chain, a redundancy version of the uplink data;

Determining, according to the mapping relationship between the time-frequency resource mapping chain to which the time-frequency resource block belongs, and the mapping relationship between the time-frequency resource mapping chain and the terminal device group in the network device, determining the terminal device group to which the terminal device belongs;

Determining, according to the pilot information, a mapping relationship between a preset pilot in the network device and a terminal device in a terminal device group, determining the terminal device in the terminal device group;

The time-frequency resource mapping chain includes at least two time-frequency resource blocks, and different time-frequency resource blocks in the time-frequency resource mapping chain correspond to different redundancy versions of the same uplink data.
The device according to claim 23, wherein the association information of the uplink data includes a pilot corresponding to the uplink data and content of the uplink data, and content of the uplink data carries a body of the terminal device Identification; the identification module is specifically used to:

Determining, according to the number of the pilot in the associated pilot mapping chain, a redundancy version of the uplink data;

Determining the terminal device according to the identity identifier;

The pilot mapping chain includes at least two pilots, and different pilots in the pilot mapping chain correspond to different redundancy versions of the same uplink data.
The apparatus according to claim 23, wherein the association information of the uplink data includes a time-frequency resource block used for transmitting the uplink data, a content of the uplink data, and a pilot corresponding to the uplink data. The content of the uplink data carries the identifier of the terminal device in the terminal device group to which the terminal device belongs; the identification module is specifically configured to:

Determining, according to the number of the pilot in the associated pilot mapping chain, a redundancy version of the uplink data;

Determining, according to the time-frequency resource block, a mapping relationship between a preset time-frequency resource block and a terminal device group in the network device, determining a terminal device group to which the terminal device belongs;

Determining, in the terminal device group, the terminal device according to the identifier of the terminal device in the associated terminal device group;

The pilot mapping chain includes at least two pilots, and different pilots in the pilot mapping chain correspond to different redundancy versions of the same uplink data.
The apparatus according to claim 23, wherein the association information of the uplink data includes a time-frequency resource block used when the uplink data is sent, and a pilot corresponding to the uplink data; to:

Determining, according to the number of the pilot in the associated pilot mapping chain, a redundancy version of the uplink data;

Determining, according to the time-frequency resource block, a mapping relationship between a preset time-frequency resource block and a terminal device group in the network device, determining a terminal device group to which the terminal device belongs;

Determining, in the terminal device group, the terminal device according to a mapping relationship between a pilot mapping chain to which the pilot belongs, a preset pilot mapping chain in the network device, and a terminal device in the terminal device group;

The pilot mapping chain includes at least two pilots, and different pilots in the pilot mapping chain correspond to different redundancy versions of the same uplink data.
The device according to claim 23, wherein the association information of the uplink data includes a content of the uplink data and a pilot corresponding to the uplink data, and content of the uplink data carries redundancy of the uplink data. The identifier of the remaining version; the identification module is specifically used to:

Determining a redundancy version of the uplink data according to the identifier of the redundancy version;

Determining the terminal device according to the pilot, and a mapping relationship between a preset pilot and the terminal device in the network device.
The apparatus according to claim 23, wherein the association information of the uplink data includes a time-frequency resource block used for transmitting the uplink data, a content of the uplink data, and a pilot corresponding to the uplink data. The content of the uplink data carries an identifier of the redundancy version of the uplink data; the identification module is specifically configured to:

Determining a redundancy version of the uplink data according to the identifier of the redundancy version;

Determining, according to the time-frequency resource block, a mapping relationship between the time-frequency resource block and the terminal device group preset in the network device, determining the terminal device group to which the terminal device belongs;

Determining, according to the pilot, a mapping relationship between a preset pilot in the network device and a terminal device in a terminal device group, Determining the terminal device in the terminal device group.
The device according to claim 23, wherein the association information of the uplink data includes content of the uplink data, and the content of the uplink data includes an identity of the terminal device and redundancy of the uplink data. The identifier of the version; the identification module is specifically used to:

Determining a redundancy version of the uplink data according to the identifier of the redundancy version;

Determining the terminal device according to the identity identifier.
The device according to claim 23, wherein the association information of the uplink data includes a time-frequency resource block and a content of the uplink data used when the uplink data is sent, and a content carrying device of the uplink data The identifier of the redundancy version of the uplink data and the identifier of the terminal device in the associated terminal device group; the identification module is specifically configured to:

Determining a redundancy version of the uplink data according to the identifier of the redundancy version;

Determining, according to the time-frequency resource block, a mapping relationship between a preset time-frequency resource block and a terminal device group in the network device, determining a terminal device group to which the terminal device belongs;

Determining the terminal device in the terminal device group according to the identifier of the terminal device in the associated terminal device group.
The apparatus according to any one of claims 25, 28, or 33, wherein said uplink data further comprises a mixed cyclic redundancy check bit; and said N-bit bit in said mixed cyclic redundancy check The N-bit bit in the cyclic redundancy check of the uplink data is XORed with the N-bit bit in the identity identifier of the terminal device;

Where N is a positive integer.
The apparatus according to any one of claims 26, 29, and 34, wherein the uplink data further comprises a mixed cyclic redundancy check bit;

The N-bit bit in the hybrid cyclic redundancy check is obtained by X-bits of the cyclic redundancy check of the uplink data and the N-bit in the identifier of the terminal device in the associated terminal device group. ;

Where N is a positive integer.
The device according to any one of claims 23 to 36, wherein the identification module is further configured to:

And determining, according to the association information of the uplink data, a hybrid automatic repeat request process that sends the uplink data.
The device according to any one of claims 24 to 27, wherein the device further comprises:

Establishing a module, configured to establish a time-frequency resource mapping chain, and send the time-frequency resource mapping chain to the terminal device;

The different time-frequency resource blocks in the resource mapping chain belong to different contention transmission areas, and the time-frequency resources of the contention transmission areas do not overlap, and the time-frequency resource blocks belonging to the same contention transmission area correspond to the same redundancy version.
The apparatus according to any one of claims 23 to 38, wherein the uplink data comprises a pilot, a control section and a data section, and the content of the uplink data is content of the control section.
The apparatus according to claim 39, wherein the pilot corresponding to the uplink data is used to indicate a modulation and coding mode adopted by at least one portion of the uplink data.
A device for data transmission, wherein the device for data transmission is a terminal device, wherein the device comprises:

An uplink data determining module, configured to determine uplink data;

a sending module, configured to send the uplink data to the network device according to the identifier of the terminal device and the redundancy version of the uplink data, so that the network device determines the terminal according to the association information of the uplink data. Equipment And a redundancy version of the uplink data, where the association information of the uplink data is information related to when the device sends the uplink data.
The device according to claim 41, wherein the association information of the uplink data includes content of the uplink data, or includes content of the uplink data, and a time-frequency resource block used when transmitting the uplink data. And at least two of the pilot information corresponding to the uplink data.
A network device, comprising:

a receiver, configured to receive uplink data from the terminal device;

a processor, configured to determine, according to the association information of the uplink data, a redundancy version of the terminal device and the uplink data, where the association information of the uplink data is when the uplink data is sent by using the terminal device Relevant information.
The network device according to claim 43, wherein the association information of the uplink data includes content of the uplink data, or content of the uplink data, and time-frequency resources used when transmitting the uplink data. Block, at least two of the pilots corresponding to the uplink data.
The network device according to claim 44, wherein the association information of the uplink data includes a time-frequency resource block used when the uplink data is sent, and a pilot corresponding to the uplink data; Used for:

Determining, according to the number of the time-frequency resource block in the associated time-frequency resource mapping chain, a redundancy version of the uplink data;

Determining the terminal device according to the pilot, and a mapping relationship between a pilot and a terminal device preset in the network device;

The time-frequency resource mapping chain includes at least two time-frequency resource blocks, and different time-frequency resource blocks in the time-frequency resource mapping chain correspond to different redundancy versions of the same uplink data.
The network device according to claim 44, wherein the association information of the uplink data includes a time-frequency resource block and a content of the uplink data used when the uplink data is sent, and the content of the uplink data is carried. The identity of the terminal device; the processor is specifically configured to:

Determining, according to the number of the time-frequency resource block in the associated time-frequency resource mapping chain, a redundancy version of the uplink data;

Determining the terminal device according to the identity identifier;

The time-frequency resource mapping chain includes at least two time-frequency resource blocks, and different time-frequency resource blocks in the time-frequency resource mapping chain correspond to different redundancy versions of the same uplink data.
The network device according to claim 44, wherein the association information of the uplink data includes a time-frequency resource block and a content of the uplink data used when the uplink data is sent, and the content of the uplink data is carried. The identifier of the terminal device in the associated terminal device group; the processor is specifically configured to:

Determining, according to the number of the time-frequency resource block in the associated time-frequency resource mapping chain, a redundancy version of the uplink data;

Determining, according to the mapping relationship between the time-frequency resource mapping chain to which the time-frequency resource block belongs, and the mapping relationship between the time-frequency resource mapping chain and the terminal device group in the network device, determining the terminal device group to which the terminal device belongs;

Determining, in the terminal device group, the terminal device according to the identifier of the terminal device in the associated terminal device group;

The time-frequency resource mapping chain includes at least two time-frequency resource blocks, and different time-frequency resource blocks in the time-frequency resource mapping chain correspond to different redundancy versions of the same uplink data.
The network device according to claim 44, wherein the association information of the uplink data includes a time-frequency resource block used when the uplink data is sent, and a pilot corresponding to the uplink data; Used for:

Determining, according to the number of the time-frequency resource block in the associated time-frequency resource mapping chain, a redundancy version of the uplink data;

Determining, according to the mapping relationship between the time-frequency resource mapping chain to which the time-frequency resource block belongs, and the mapping relationship between the time-frequency resource mapping chain and the terminal device group in the network device, determining the terminal device group to which the terminal device belongs;

Determining, according to the pilot information, a mapping relationship between a preset pilot in the network device and a terminal device in a terminal device group, determining the terminal device in the terminal device group;

The time-frequency resource mapping chain includes at least two time-frequency resource blocks, and different time-frequency resource blocks in the time-frequency resource mapping chain correspond to different redundancy versions of the same uplink data.
The network device according to claim 44, wherein the association information of the uplink data includes a pilot corresponding to the uplink data and content of the uplink data, where content of the uplink data carries the terminal device Identity identifier; the processor is specifically used to:

Determining, according to the number of the pilot in the associated pilot mapping chain, a redundancy version of the uplink data;

Determining the terminal device according to the identity identifier;

The pilot mapping chain includes at least two pilots, and different pilots in the pilot mapping chain correspond to different redundancy versions of the same uplink data.
The network device according to claim 44, wherein the association information of the uplink data includes a time-frequency resource block used for transmitting the uplink data, a content of the uplink data, and a guide corresponding to the uplink data. The content of the uplink data carries the identifier of the terminal device in the associated terminal device group; the processor is specifically configured to:

Determining, according to the number of the pilot in the associated pilot mapping chain, a redundancy version of the uplink data;

Determining, according to the time-frequency resource block, a mapping relationship between a preset time-frequency resource block and a terminal device group in the network device, determining a terminal device group to which the terminal device belongs;

Determining, in the terminal device group, the terminal device according to the identifier of the terminal device in the associated terminal device group;

The pilot mapping chain includes at least two pilots, and different pilots in the pilot mapping chain correspond to different redundancy versions of the same uplink data.
The network device according to claim 44, wherein the association information of the uplink data includes a time-frequency resource block used when the uplink data is sent, and a pilot corresponding to the uplink data; Used for:

Determining, according to the number of the pilot in the associated pilot mapping chain, a redundancy version of the uplink data;

Determining, according to the time-frequency resource block, a mapping relationship between a preset time-frequency resource block and a terminal device group in the network device, determining a terminal device group to which the terminal device belongs;

Determining, in the terminal device group, the terminal device according to a mapping relationship between a pilot mapping chain to which the pilot belongs, a preset pilot mapping chain in the network device, and a terminal device in the terminal device group;

The pilot mapping chain includes at least two pilots, and different pilots in the pilot mapping chain correspond to different redundancy versions of the same uplink data.
The network device according to claim 44, wherein the association information of the uplink data includes a content of the uplink data and a pilot corresponding to the uplink data, and content of the uplink data carries the uplink data. The identifier of the redundancy version; the processor is specifically used to:

Determining a redundancy version of the uplink data according to the identifier of the redundancy version;

Determining the terminal device according to the pilot, and a mapping relationship between a preset pilot and the terminal device in the network device.
The network device according to claim 44, wherein the association information of the uplink data includes a time-frequency resource block used for transmitting the uplink data, a content of the uplink data, and a guide corresponding to the uplink data. The content of the uplink data carries an identifier of the redundancy version of the uplink data; the processor is specifically configured to:

Determining a redundancy version of the uplink data according to the identifier of the redundancy version;

Determining, according to the time-frequency resource block, a mapping relationship between the time-frequency resource block and the terminal device group preset in the network device, determining the terminal device group to which the terminal device belongs;

And determining, according to the pilot, a mapping relationship between a preset pilot in the network device and a terminal device in the terminal device group, determining the terminal device in the terminal device group.
The network device according to claim 44, wherein the association information of the uplink data includes content of the uplink data, and the content of the uplink data includes an identifier of the terminal device and redundancy of the uplink data. The identifier of the remaining version; the processor is specifically used to:

Determining a redundancy version of the uplink data according to the identifier of the redundancy version;

Determining the terminal device according to the identity identifier.
The network device according to claim 44, wherein the association information of the uplink data includes a time-frequency resource block and a content of the uplink data used when the uplink data is sent, and the content of the uplink data is carried. An identifier of the redundancy version of the uplink data and an identifier of the terminal device in the associated terminal device group; the processor is specifically configured to:

Determining a redundancy version of the uplink data according to the identifier of the redundancy version;

Determining, according to the time-frequency resource block, a mapping relationship between a preset time-frequency resource block and a terminal device group in the network device, determining a terminal device group to which the terminal device belongs;

Determining the terminal device in the terminal device group according to the identifier of the terminal device in the associated terminal device group.
The network device according to any one of claims 46, 49, 54 wherein the uplink data further comprises a mixed cyclic redundancy check bit; wherein the N-bit bit in the mixed cyclic redundancy check is And obtaining, by the X-bit in the cyclic redundancy check of the uplink data, an X-bit bit in the identity identifier of the terminal device;

Where N is a positive integer.
The network device according to any one of claims 47, 50, 55, wherein the uplink data further comprises a hybrid cyclic redundancy check bit;

The N-bit bit in the hybrid cyclic redundancy check is obtained by X-bits of the cyclic redundancy check of the uplink data and the N-bit in the identifier of the terminal device in the associated terminal device group. ;

Where N is a positive integer.
The network device according to any one of claims 44 to 57, wherein the processor is further configured to:

And determining, according to the association information of the uplink data, a hybrid automatic repeat request process that sends the uplink data.
The network device according to any one of claims 45 to 48, wherein the processor is further configured to:

Establishing a time-frequency resource mapping chain, and sending the time-frequency resource mapping chain to the terminal device;

The different time-frequency resource blocks in the resource mapping chain belong to different contention transmission areas, and the time-frequency resources of the contention transmission areas do not overlap, and the time-frequency resource blocks belonging to the same contention transmission area correspond to the same redundancy version.
The network device according to any one of claims 44 to 59, wherein the uplink data comprises a pilot, a control part and a data part, and the content of the uplink data is content of the control part.
The network device according to claim 60, wherein the pilot corresponding to the uplink data is used to indicate a modulation and coding mode used by at least one part of the uplink data.
A terminal device, comprising:

a processor for determining uplink data;

a transmitter, configured to send the uplink data to the network device according to the identifier of the terminal device and the redundancy version of the uplink data, so that the network device determines the terminal according to the association information of the uplink data. a redundancy version of the device and the uplink data, where the association information of the uplink data is information related to when the device sends the uplink data.
The terminal device according to claim 62, wherein the association information of the uplink data includes content of the uplink data, or includes content of the uplink data, and time-frequency resources used when transmitting the uplink data. Block, at least two of the pilot information corresponding to the uplink data.