WO2018228175A1

WO2018228175A1 - Acknowledgement information feedback method and device, and acknowledgement information receiving method and device

Info

Publication number: WO2018228175A1
Application number: PCT/CN2018/088768
Authority: WO
Inventors: 苟伟; 郝鹏; 斯尔⋅托尔斯腾; 毕峰; 赵宝; 李儒岳
Original assignee: 中兴通讯股份有限公司
Priority date: 2017-06-16
Filing date: 2018-05-28
Publication date: 2018-12-20
Also published as: CN108111263B; CN108111263A

Abstract

The present disclosure provides an acknowledgement information feedback method and device and an acknowledgement information receiving method and device. The acknowledgement information feedback method comprises: a receiving end device determining a manner for acknowledgement information feedback according to the decoding condition of the received transmission blocks or code block groups; in cases where it is determined that all the transmission blocks or the code block groups are correctly decoded or not correctly decoded, the receiving end device generating first acknowledgement information on the basis of the transmission block, and transmitting, in a first resource, the first acknowledgement information, or in cases where it is determined that all the transmission blocks or code block groups are not correctly decoded, the receiving end device generating second acknowledgement information on the basis of the code block group, and transmitting, in a second resource, the second acknowledgement information.

Description

Feedback method and device for confirming information, method and device for receiving confirmation information

Cross-reference to related applications

The present application is based on a Chinese patent application filed on Jan. 16, 2017, the entire disclosure of which is hereby incorporated by reference.

Technical field

The present disclosure relates to, but is not limited to, the field of communications.

Background technique

In the related art, the new generation of mobile communication (New Radio, NR for short) system under study is one of the current work priorities of 3GPP.

Among the currently determinable NR systems, there are three typical types of services in the future. Common services include: Enhanced Mobile BroadBand (eMBB), Ultra-Reliable and Low Latency Communications (URLLC) and Massive Machine Type Communications (massive Machine Type Communications). Referred to as mMTC). These services have different requirements for delay, coverage and reliability. For example, for eMBB, the emphasis is on high peak transmission rates, the requirements on latency are not high (no low latency is required), and the reliability is moderate. For URLLC, emphasis is placed on low latency, high reliability transmission, which is very demanding for latency. For mMTC, a large number of medium terminals are emphasized, the connection density is large and the transmission coverage is required, and there is almost no requirement for delay.

In addition, in the NR system, a new codec mode is discussed and is likely to be introduced. In this manner, the receiving end device is allowed to decode according to the received Orthogonal Frequency Division Multiplexing (OFDM) symbol, that is, decoding one OFDM symbol by receiving one OFDM is a “streaming” decoding method. In order to speed up the receiving end device to receive the last OFDM symbol data of the current transmission, the receiving device can quickly feed back the confirmation information to the transmitting device. Obviously, the "streaming" decoding can achieve the above-mentioned purpose of fast feedback confirmation information.

However, for the above decoding method, some better confirmation information feedback should be studied, so that the receiving end device can accurately report which part of the data has an error, instead of a transport block (Transport Block, TB for short). Feedback a confirmation message, if there is an error, it is not clear that the specific part of the data is wrong. In this way, the sender device can only send the entire TB again.

There is currently no effective solution to the problem of how to make more accurate and efficient feedback confirmation information in related technologies.

Summary of the invention

Embodiments of the present disclosure provide a method and apparatus for feeding back confirmation information, and a method and apparatus for receiving information.

According to an embodiment of the present disclosure, a method for feeding back confirmation information is provided, including: determining, by a receiving end device, feedback acknowledgement information according to a decoding condition of a received TB or Code Blocks Group (CBG) The method, wherein the confirmation information includes first confirmation information and second confirmation information; in a case where it is determined that both TB or CBG are correctly decoded or are not correctly decoded, the receiving end device generates a first confirmation based on the TB. Transmitting, in the first resource, the first acknowledgement information; or, in the case of determining that there is not correctly decoding all TBs or code block groups, the receiving end device generates a second acknowledgement based on the code block group And transmitting the second confirmation information in the second resource.

According to another embodiment of the present disclosure, a method for receiving acknowledgment information is provided, including: a transmitting end device transmitting data to a receiving end device; and the transmitting end device receiving the receiving according to the first resource and/or the second resource The acknowledgement information fed back by the terminal device, or the sender device receives the acknowledgement information fed back by the receiver device according to the first format and/or the second format.

According to another embodiment of the present disclosure, there is provided a feedback device for confirming information, comprising: a determining module configured to determine a manner of feedback confirmation information according to a decoding condition of a received TB or CBG, wherein the confirmation information The first confirmation information and the second confirmation information are included, and the feedback module is configured to: when the TB or the CBG is determined to be correctly decoded or not correctly decoded, generate the first confirmation information based on the TB, and transmit the information in the first resource. The first confirmation information; the feedback module is further configured to: when it is determined that there is not all TB or CBG correctly decoded, generate second confirmation information based on the code block group, and transmit the Second confirmation message.

According to another embodiment of the present disclosure, a receiving apparatus for providing acknowledgement information includes: a sending module configured to send data to a receiving end device; and a receiving module configured to receive the first resource and/or the second resource according to the first resource and/or the second resource The acknowledgement information fed back by the receiving device is configured; or the receiving module is further configured to receive the acknowledgement information fed back by the receiving device according to the first format and/or the second format.

According to another embodiment of the present disclosure, there is provided a receiving end device, comprising: a first processor configured to determine a manner of feedback acknowledgement information according to a decoding condition of a received TB or CBG, wherein the acknowledgement information And including, in the case of determining that the TB or the CBG are correctly decoded or not correctly decoded, generating the first confirmation information based on the TB, or configured to determine the presence If the TB or the CBG is not correctly decoded, the second confirmation information is generated based on the code block group; the first communication device is configured to transmit the first acknowledgement information in the first resource, or is further configured to Transmitting the second confirmation information in the second resource.

According to another embodiment of the present disclosure, a transmitting device is provided, including: a second communications device configured to send data to a receiving device; and a second processor configured to depend on the first resource and/or the second resource Receiving the acknowledgement information fed back by the receiving device; or the second processor is further configured to receive the acknowledgement information fed back by the receiving device according to the first format and/or the second format.

According to another embodiment of the present disclosure, a storage medium is provided, the storage medium including a stored program, wherein the program executes the method described above while it is running.

In accordance with another embodiment of the present disclosure, a processor is provided that is configured to execute a program, wherein the program executes the method described above while it is running.

Through the embodiment of the present disclosure, the receiving end device determines the manner of feeding back the confirmation information according to the decoding situation of the received TB or CBG; in the case of determining that both the TB or the CBG are correctly decoded or not correctly decoded, the receiving end device is based on The TB generates first acknowledgement information, and transmits the first acknowledgement information in the first resource; or, in the case that it is determined that all TBs or CBGs are not correctly decoded, the receiving end device generates second acknowledgement information based on the CBG And transmitting the second confirmation information in the second resource. The above technical solution solves the problem of how to perform more accurate and efficient feedback confirmation information in the related art, and the receiving end device generates different confirmation information according to different decoding situations, and accurately and efficiently feedbacks the decoding situation of the receiving end device.

DRAWINGS

The accompanying drawings, which are set forth in the claims In the drawing:

1 is a flowchart of a feedback method of confirmation information according to an embodiment of the present disclosure;

2 is a flowchart of a method of receiving confirmation information according to an embodiment of the present disclosure;

3 is a flow chart of a method 1 in accordance with an applied embodiment of the present disclosure;

4 is a flow chart of a method 4 in accordance with an applied embodiment of the present disclosure;

5 is a schematic diagram of a 1/2 bit UCI predefined format (14 symbol slot) according to an application 8 of the present disclosure;

6 is a schematic diagram (14 symbol slot) of a UCI predefined format greater than 2 bits according to an embodiment 8 of the present disclosure;

7 is a schematic diagram of a 4-symbol long PUCCH (greater than 2-bit UCI) hopping pattern according to an embodiment 8 of the present disclosure;

8 is a schematic diagram of a symbol length long PUCCH (greater than 2-bit UCI) hopping pattern according to an embodiment 8 of the present disclosure;

9 is a schematic diagram of an 11-symbol long PUCCH (greater than 2-bit UCI) hopping pattern according to Embodiment 8 of the present disclosure;

10 is a schematic diagram of a 14-symbol long PUCCH (greater than 2-bit UCI) hopping pattern according to an embodiment 8 of the present disclosure;

11 is a schematic diagram of a 4-symbol long PUCCH (greater than 2-bit UCI) hopping pattern according to an embodiment 8 of the present disclosure;

12 is a schematic diagram of a 7-symbol long PUCCH (greater than 2 bit UCI) hopping pattern according to an embodiment 8 of the present disclosure;

13 is a schematic diagram of an 11-symbol long PUCCH (greater than 2-bit UCI) hopping pattern according to an embodiment 8 of the present disclosure;

14 is a schematic diagram of a 14-symbol long PUCCH (greater than 2-bit UCI) hopping pattern according to an embodiment 8 of the present disclosure;

15 is a schematic diagram of a 4-symbol long PUCCH (greater than 2-bit UCI) hopping pattern according to Embodiment 8 of the present disclosure;

16 is a schematic diagram of a 7-symbol long PUCCH (greater than 2-bit UCI) hopping pattern according to Embodiment 8 of the present disclosure;

17 is a schematic diagram of an 11-symbol long PUCCH (greater than 2-bit UCI) hopping pattern according to Embodiment 8 of the present disclosure;

18 is a schematic diagram of a 14-symbol long PUCCH (greater than 2-bit UCI) hopping pattern according to Embodiment 8 of the present disclosure;

19 is a schematic diagram showing the use of a process number when a retransmission CBG and a new TB are simultaneously transmitted according to Embodiment 9 of the present disclosure;

20 is a structural diagram of a feedback device for confirming information according to an embodiment of the present disclosure.

detailed description

A mobile communication network (including but not limited to a 5G mobile communication network) is provided in the embodiment of the present application, and the network architecture of the network may include a network side device (for example, a base station) and a terminal. In this embodiment, a feedback method and a receiving method for the acknowledgment information that can be run on the network architecture are provided. It should be noted that the feedback method and the receiving environment of the acknowledgment information provided in the embodiment of the present application are provided. It is not limited to the above network architecture.

It should be added that the base station in the above network architecture may be referred to as a sender device, and the terminal may be referred to as a sink device.

Based on the CBG feedback method, one TB can feed back a confirmation message, and the sending device can only send the entire TB again. That is, one TB is separately fed back to the acknowledgment information according to multiple CBGs. However, it also brings new problems. For example, the overhead of CBG-based acknowledgment information is relatively large, and in most cases each CBG is correctly decoded, so only a few cases actually use CBG-based feedback. Retransmission. This also means that in most cases, the determination information based on the CBG feedback does not improve the retransmission efficiency, and brings a large overhead. For example, if eight CBGs are configured for feedback confirmation, at least 8 bits of confirmation information needs to be sent each time.

One implementation is: one transmission, and the 1 bit ACK/NACK information is fed back if the receiving device decodes correctly. The formation of ACK/NACK information based on CBG is currently being discussed in the NR system, and each CBG corresponds to one ACK/NACK. For the CBG that decodes the error, the transmitting device can retransmit the decoded CBG, so that it is not necessary to retransmit all the data, thereby improving the efficiency of retransmission. However, the bit overhead of the corresponding ACK/NACK information is increased.

Generally, for a system, the probability that a transmission is correctly decoded by the receiving device is about 90%, that is, using CBG-based ACK/NACK feedback, the probability of each CBG feeding back ACK information is 90%. Thus, in practice, for a transmission, the probability of not requiring retransmission is 90%. However, based on the CBG feedback mechanism, the corresponding ACK/NACK overhead for each transmission is relatively large.

How to use the CBG feedback mechanism to improve the efficiency of retransmission, and at the same time reduce the necessary signaling overhead, remains to be studied.

Embodiment 1

In this embodiment, a feedback method for confirming information running in the network architecture is provided. FIG. 1 is a flowchart of a method for feeding back confirmation information according to an embodiment of the present disclosure. As shown in FIG. 1, the flow includes the following steps. :

Step S102: The manner in which the receiving end device determines the feedback confirmation information according to the decoding situation of the received TB or CBG, where the confirmation information includes the first confirmation information and the second confirmation information;

Step S104, in the case that it is determined that both the TB or the CBG are correctly decoded or not correctly decoded, the receiving end device generates the first acknowledgement information based on the TB, and transmits the first acknowledgement information in the first resource; or, in determining In the case where all TBs or CBGs are not correctly decoded, the receiving end device generates second acknowledgment information based on the CBG, and transmits the second acknowledgment information in the second resource.

Through the above steps, the problem of how to perform more accurate and efficient feedback confirmation information in the related art is solved. The receiving end device generates different confirmation information according to different decoding situations, and accurately and efficiently feedbacks the decoding situation of the receiving end device.

In an embodiment, the execution entity of the foregoing step may be a base station.

In an embodiment, in a case where it is determined that both the TB or the CBG are correctly decoded or not correctly decoded, the receiving end device generates the first acknowledgement information based on the TB, and transmits the first acknowledgement information in the first resource, including the following. one:

In a case where it is determined that both the TB or the CBG are correctly decoded, the receiving end device generates ACK information based on the TB, and transmits the ACK information in the first resource;

In a case where it is determined that neither the TB nor the CBG is correctly decoded, the receiving end device generates NACK information based on the TB, and transmits the NACK information in the first resource.

In an embodiment, transmitting the first confirmation information in the first resource, or transmitting the second confirmation information in the second resource, includes:

Transmitting, by using the first format, the first acknowledgment information in the first resource, where the first format is used to transmit uplink control information (Up Control Information, UCI for short) that is less than or equal to 2 bits;

Transmitting the second acknowledgement information in the second resource by using the second format, where the second format is used for transmitting UCI greater than 2 bits;

The UCI includes the first confirmation information or the second confirmation information.

In an embodiment, the first resource includes a resource configured by the sending end device for the receiving end device to transmit uplink control information of the first format, where the second resource includes the sending end device for receiving A resource configured by the end device to transmit uplink control information of the second format.

In an embodiment, the first resource is the same as the second resource, or the first resource is a subset of the second resource.

In an embodiment, the first resource or the second resource is a resource shared by the multiple receiving end devices.

In an embodiment, in a case where it is determined that both the TB or the CBG are correctly decoded or not correctly decoded, the receiving end device generates the first acknowledgement information based on the TB, and transmits the first acknowledgement information in the first resource, including :

When the first resource is a part of resources in the PUSCH of the receiving end device, the first resource is determined by the receiving end device to determine the specificity of transmitting the first acknowledgement information by puncturing or matching the PUSCH resource of the receiving end device. A resource, wherein the puncturing or rate matching rule is pre-agreed by the receiving device and the transmitting device.

The first confirmation information is transmitted in the specific resource.

In an embodiment, in the case that it is determined that the TB or the CBG is not correctly decoded, the receiving device generates the second acknowledgment information based on the CBG, and transmits the second acknowledgment information in the second resource, including:

The receiving device transmits the second acknowledgment information in the second resource by using the second format, where the second resource is a resource configured by the sending end device for the receiving end device, and the second format is used for transmitting more than 2 bits. UCI.

In an embodiment, the second resource is a resource shared by the plurality of receiving devices.

In an embodiment, in a case where the receiving end device lacks a specific resource for transmitting the first acknowledgment information, the receiving end device transmits the first acknowledgment information according to the first format in the second resource, where The first format is used to transmit UCI less than or equal to 2 bits.

In an embodiment, when the first resource and the second resource are part of resources in a physical uplink shared channel (PUSCH) of the receiving end device, the first resource and the second resource are Punching or rate matching the PUSCH resources of the receiving end device to determine specific resources for transmitting the first acknowledgement information or the second acknowledgement information, respectively. The puncturing or rate matching rule is pre-agreed by the receiving device and the transmitting device.

Optionally, the manner in which the receiving device determines the feedback confirmation information according to the decoding status of the received TB or CBG includes:

In a feedback confirmation message, when the receiving end device determines to transmit the confirmation information simultaneously with other UCI information, the receiving end device always generates the second confirmation information based on the CBG, and the second confirmation information is Other UCI information is encoded and transmitted.

FIG. 2 is a flowchart of a method for receiving confirmation information according to an embodiment of the present disclosure. As shown in FIG. 2, the method includes:

Step S202, the sending end device sends data to the receiving end device;

Step S204: The sending end device receives the acknowledgement information fed back by the receiving end device according to the first resource and/or the second resource, or the sending end device receives the feedback of the receiving end device according to the first format and/or the second format. Confirmation information.

In an embodiment, the sending end device receives the acknowledgement information fed back by the receiving end device according to the first resource and/or the second resource, including:

Receiving, by the sending end device, the first acknowledgement information fed back by the receiving end device, where the first acknowledgement information is generated by the receiving end device based on the received TB;

The sending end device receives the second acknowledgement information fed back by the receiving end device on the second resource, where the second acknowledgement information is generated by the receiving end device based on the received CBG.

In an embodiment, the sending end device receives the acknowledgement information fed back by the receiving end device according to the first format and/or the second format, including:

Receiving, by the sending end device, the first acknowledgement information fed back by the receiving end device according to the first format, where the first acknowledgement information is generated by the receiving end device based on the received TB;

The sending end device receives the second acknowledgement information fed back by the receiving end device according to the second format, where the second acknowledgement information is generated by the receiving end device based on the received CBG.

In an embodiment, the sending end device receives the first acknowledgement information fed back by the receiving end device according to the first format in the first resource, where the first acknowledgement information is generated by the receiving end device based on the received TB. of;

The sending end device receives, in the second resource, the second acknowledgement information fed back by the receiving end device according to the second format, where the second acknowledgement information is generated by the receiving end device based on the received CBG.

Optionally, the first resource includes a resource configured by the sending end device for the receiving end device to transmit uplink control information of the first format, where the second resource includes the sending end device is the receiving end device A resource configured to transmit uplink control information of the second format.

Optionally, the first format is used to transmit uplink control information that is less than or equal to 2 bits.

The second format is used to transmit uplink control information greater than 2 bits.

The uplink control information includes the first confirmation information or the second confirmation information.

When the first resource is a part of the resources in the PUSCH of the receiving end device, the sending end device receives the first confirmation information according to the first preset puncturing rule or the rate matching pattern in the part of the resource, where the first A confirmation message is generated by the receiving device based on the received TB.

In an embodiment, in a case that the sending end device does not receive the first confirmation information in the part of the resources, the method includes:

The transmitting device receives the second acknowledgment information in the second resource according to the second format, where the second resource is a resource configured by the sending end device for the receiving end device, and the second acknowledgment information is the receiving end device Based on the CBG, the second format is used to transmit uplink control information greater than 2 bits.

In an embodiment, in the case that the sending end device detects that the receiving end device lacks the PUSCH for sending the first acknowledgement information, the method further includes:

The source device allocates resources for transmitting the first acknowledgement information to the receiver device.

In an embodiment, in a case that the sending end device does not receive the first acknowledgement information in the PUSCH resource, the method further includes:

The transmitting device receives the second acknowledgment information in the PUSCH resource according to the second preset puncturing rule or the rate matching pattern, where the second acknowledgment information is generated by the receiving end device based on the received CBG.

In an embodiment, in a case that the sending end device detects that the receiving end device lacks the PUSCH resource for sending the first acknowledgement information or the second acknowledgement information, the method further includes:

The sending end device allocates, for the receiving end device, a resource for transmitting the first confirmation information or the second confirmation information.

In an embodiment, after the sending device sends data to the receiving device, the method further includes:

When the sending end device determines that the acknowledgment information fed back by the receiving end device is transmitted simultaneously with other UCI information, the sending end device determines that the acknowledgment information is the second acknowledgment information, where the second acknowledgment information is the receiving end device Based on the received CBG generated.

The detailed description will be made below in conjunction with the application examples of the present disclosure.

It is to be noted that the resource 1 in the application embodiment of the present disclosure may be the first resource in the foregoing embodiment, the resource 2 may be the second resource, the format 1 may be the first format, and the format 2 may be the second format.

Method 1: Corresponding to the following application example 1

For a receiving end device, it allocates a resource 1 based on TB formation and sends an acknowledgment information ACK/NACK information; configures it to allocate and allocates ACK/NACK information based on CBG to allocate resource 2; for one transmission, when the receiving end device correctly decodes After all the received CBGs or the receiving end device correctly decode the received TB, the receiving end device forms corresponding ACK/NACK information based on the TB (each TB forms a 1-bit ACK/NACK information) and transmits it in the resource 1 using the format 1 . Otherwise, the receiving end device forms corresponding ACK/NACK information based on the CBG (each CBG forms a 1-bit ACK/NACK information) and transmits it in the resource 2 using the format 2. 3 is a flow chart of a method 1 in accordance with an applied embodiment of the present disclosure.

The format 1 is for 1 to 2 bits of uplink control information (referred to as UCI for short) information transmission. Generally, it adopts high reliability. Format 2 is for UCI information transmission greater than 2 bits. The uplink control information includes ACK/NACK information and other uplink feedback information (other uplink feedback information may refer to the definition in the NR system).

For one UE1, resource 1 is used with a higher probability, so UE1 uses resource 2 with a lower probability. In this way, more user terminals UE (for example, UE2, UE3, UE4) are configured to share the same resource 2 with UE1. That is, multiple UEs share the usage resource 2. For example, the UEs sharing the resources 2 may be UEs that are farther from the base station and UEs that are closer to the base station.

That is, the corresponding ACK/NACK formed in the resource 1 and the resource 2 is transmitted using the format 1 and the format 2, respectively. Then there are more UEs sharing resources 2.

If the resource 1 is located in the resource 2, or the resource 1 is a part of the resource 2, the specific embodiment 1 in this case will become the specific embodiment 3.

It should be noted that resource 1 is used to transmit a resource of format 1; resource 2 is a resource for transmitting a format 2. In general, resource 2 is greater than or equal to resource 1. Because there are more bits transmitted in resource 2, it is greater than 2 bits.

The transmitting device (for example, the base station) first receives the ACK formed based on the TB according to the format 1 in the resource 1 (because most of the information is ACK information here, and the NAKC information is a minority case), and if the ACK information is detected, the UE is considered to be formed based on the TB. ACK/NACK, and the UE is considered to correctly decode the transmitted data. If the ACK information is not detected in the resource 1, the base station further receives the ACK/NACK information formed based on the CBG in the resource 2 according to the format 2, and if the ACK/NACK is detected, the base station retransmits the CBG in which the UE decodes the error.

Method 2: Corresponding to the following application example 2

For one transmission, when the receiving end device correctly decodes all received CBGs or the receiving end device correctly decodes the received TB, the receiving end device forms corresponding ACK/NACK information based on the TB (each TB forms a 1-bit ACK/NACK information) And transmit it by puncturing or rate matching the receiving device's own PUSCH. Otherwise, the receiving end device forms corresponding ACK/NACK information based on the CBG (each CBG forms a 1-bit ACK/NACK information) and transmits it in the resource 2 using the format 2. Resource 2 is configured by the base station for the UE.

Wherein, format 2 is for transmitting UCI greater than 2 bits. The UCI includes ACK/NACK information and other uplink feedback information (other uplink feedback information can be referred to in the NR system).

For one UE1, the BER/NACK formed by the TB is transmitted through the puncturing or rate matching of the receiving device's own PUSCH, so the UE1 uses the resource 2 with a small probability, so that more UEs will be configured (for example, UE2, UE3) , UE4) shares the same resource 2 with UE1. That is, multiple UEs share the usage resource 2. For example, the UEs sharing the resource 2 can be UEs that are farther from the base station and UEs that are closer to the base station.

The transmitting device (for example, the base station) first receives the ACK formed based on the TB (because the ACK information is always here) according to the agreed puncturing rule or the rate matching pattern in the PUSCH of the UE, and if the ACK information is detected, the UE is considered to be based on TB/NACK formed by TB, and it is considered that the UE correctly decodes the transmitted data. If no ACK information is detected, the base station further receives the ACK/NACK information formed based on the CBG in the resource 2 according to the format 2, and if the ACK/NACK is detected, the base station retransmits the CBG in which the UE decodes the error.

It is to be noted that the base station can know whether the UE has the PUSCH transmission. If the base station finds that the UE does not transmit the PUSCH, but still needs to send the ACK/NACK, the UE is in the resource 2 if the UE does not transmit the PUSCH. The ACK/NACK information is formed according to the TB according to the format 1; or the base station allocates the resource 1 for transmitting the ACK/NAK information formed according to the TB in time (similar to the resource 1 in opt1).

Method 3: Corresponding to the following application example 4

For one transmission, when the receiving end device correctly decodes all received CBGs or the receiving end device correctly decodes the received TB, the receiving end device forms corresponding ACK/NACK information based on the TB (each TB forms a 1-bit ACK/NACK information) And transmit it by puncturing or rate matching the receiving device's own PUSCH. Otherwise, the receiving end device forms corresponding ACK/NACK information based on the CBG (each CBG forms a 1-bit ACK/NACK information) and transmits it through another puncturing rule or rate matching processing of the receiving device's own PUSCH.

The transmitting device (for example, the base station) first receives the ACK formed based on the TB (because the ACK information is always here) according to the agreed puncturing or rate matching pattern in the PUSCH of the UE, and if the ACK information is detected, the UE is considered to be based on the TB. The ACK/NACK is formed, and the UE is considered to correctly decode the transmitted data. If the ACK information is not detected, the base station receives the ACK/NACK information formed based on the CBG according to the agreed puncturing or rate matching pattern in the PUSCH of the UE, and if the ACK/NACK is detected, the base station retransmits the CBG that the UE decodes incorrectly. .

Similarly, if the base station finds that the UE does not have PUSCH transmission, but still has ACK/NACK to transmit, the base station can allocate resources for transmitting ACK/NACK according to TB and forming ACK/NACK according to CBG in time.

Method 4: Corresponding to the following application example 5

If the UE determines that the UE will need to transmit ACK/NACK information and other UCI information simultaneously in one feedback, the UE forms ACK/NACKs information according to the CBG, and performs joint coding with other UCIs for transmission. Since the transmission timing of ACK/NACK and other UCIs is configured by the base station, the base station always knows whether other UCIs and ACK/NACKs are transmitted simultaneously. If the base station determines that the UE will need to transmit ACK/NACK and other UCI information in one feedback, the base station considers that the ACK/NACK information in this feedback is an ACK/NACKs formed according to the CBG. 4 is a flow chart of a method 4 in accordance with an applied embodiment of the present disclosure.

When the UE is configured to work according to opt1, opt2, opt3 or opt4, if the UE finds that the UE will need to transmit ACK/NACK and other UCI information at the same time, the UE always forms multiple ACKs according to the CBG. /NACKs information and transmitted simultaneously with other UCIs. For example, when the UE finds that it is necessary to simultaneously transmit ACK/NACK and other UCI, even if the UE correctly decodes all CBGs or TBs, the UE does not form 1 bit ACK information at this time, but forms ACK/NACK according to CBG (each CBG is formed). An ACK message). The formed ACK/NACK and other UCIs are transmitted in a manner corresponding to multiple ACK/NACKs specified by opt1, opt2, opt3 or opt4. Since the transmission timing of ACK/NACK and other UCIs is configured by the base station, the base station always knows whether other UCIs and ACK/NACKs are transmitted simultaneously. Correspondingly, if the base station determines that the UE will need to transmit ACK/NACK and other UCI information in one feedback, the base station considers that the ACK/NACK information in this feedback is an ACK/NACKs formed according to the CBG.

The following is a specific implementation of the application embodiment of the present disclosure:

Application Example 1

For a receiving end device, it allocates a resource 1 based on TB formation and sends an acknowledgment information ACK/NACK information; configures it to allocate and allocates ACK/NACK information based on CBG to allocate resource 2; for one transmission, when the receiving end device correctly decodes After all the received CBGs or the receiving end device correctly decode the received TB, the receiving end device forms corresponding ACK/NACK information based on the TB (each TB forms a 1-bit ACK/NACK information) and transmits it in the resource 1 using the format 1 . Otherwise, the receiving end device forms corresponding ACK/NACK information based on the CBG (each CBG forms a 1-bit ACK/NACK information) and transmits it in the resource 2 using the format 2.

Among them, the format 1 is for UCI information transmission of 1 to 2 bits, and generally, it adopts high reliability. Format 2 is for UCI information transmission greater than 2 bits. The uplink control information (abbreviated UCI) includes ACK/NACK information and other uplink feedback information (other uplink feedback information may refer to the definition in the NR system).

For one UE1, resource 1 is used with a higher probability, so UE1 uses resource 2 with a lower probability. In this way, more UEs (for example, UE2, UE3, UE4) are configured to share the same resource 2 with UE1. That is, multiple UEs share the usage resource 2. For example, the UEs sharing the resources 2 may be UEs that are farther from the base station and UEs that are closer to the base station.

If the resource 1 is located in the resource 2, or the resource 1 is part of the resource 2, the first embodiment in this case will become the third embodiment.

Application Example 2

Wherein, format 2 is used for transmitting UCI information greater than 2 bits. The UCI includes ACK/NACK information and other uplink feedback information (other uplink feedback information can be referred to in the NR system).

Application Example 3

In the application embodiment 3, the resource 1 is a subset of the resource 2, that is, the resource 1 is located in the resource 2, or the resource 1 is a part of the resource 2.

The format 1 is for UCI transmission of 1 to 2 bits. Generally, it adopts high reliability. Format 2 is for UCI information transmission greater than 2 bits. The UCI includes ACK/NACK information and other uplink feedback information (other uplink feedback information can be referred to in the NR system).

It should be noted that resource 1 is for transmitting a resource of format 1; resource 2 is for transmitting a resource of format 2. In general, resource 2 is greater than or equal to resource 1. Because there are more bits transmitted in resource 2, it is greater than 2 bits.

Application Example 4

Application Example 5

If the UE determines that the UE will need to transmit ACK/NACK information and other UCI information simultaneously in one feedback, the UE forms ACK/NACKs information according to the CBG, and performs joint coding with other UCIs for transmission. Since the transmission timing of ACK/NACK and other UCIs is configured by the base station, the base station always knows whether other UCIs and ACK/NACKs are transmitted simultaneously. If the base station determines that the UE will need to transmit ACK/NACK and other UCI information in one feedback, the base station considers that the ACK/NACK information in this feedback is an ACK/NACKs formed according to the CBG.

Application Example 6

For a receiving end device, it is configured to allocate and send ACK/NACK information based on TB to allocate resource 1; configure it to allocate and send ACK/NACK information based on CBG to allocate resource 2; for one transmission, for example, transmit one TB, when receiving end After the device correctly decodes all received CBGs or the receiving end device correctly decodes the received TB, the receiving end device forms corresponding ACK/NACK information based on the TB (each TB forms a 1-bit ACK information) and transmits it in resource 1 using format 1. Or; when the receiving end device does not correctly decode all received CBGs, the receiving end device forms corresponding ACK/NACK information based on the TB (each TB forms a 1-bit NACK information) and transmits it in the resource 1 using the format 1 . Otherwise, the receiving end device forms corresponding ACK/NACK information based on the CBG (each CBG forms a 1-bit ACK/NACK information) and transmits it in the resource 2 using the format 2.

The format 1 is for UCI transmission of 1 to 2 bits. Generally, it adopts high reliability. Format 2 is for UCI transmissions greater than 2 bits. The UCI includes ACK/NACK information and other uplink feedback information (other uplink feedback information can be referred to in the NR system).

For one UE1, resource 1 is used with a higher probability, so UE1 uses resource 2 with a lower probability. In this way, more UEs (for example, UE2, UE3, UE4) are configured to share the same resource 2 with UE1. That is, multiple UEs share the usage resource 2. For example, the UEs sharing the resource 2 can be UEs that are farther from the base station and UEs that are closer to the base station.

The emphasis is on the use of Format 1 and Format 2 to transmit the corresponding ACK/NACK formed in Resource 1 and Resource 2, respectively. Then there are more UEs sharing resources 2.

If resource 1 is in resource 2, or resource 1 is part of a resource, opt1 will become opt3.

Description: Resource 1 is a resource for transmitting a format 1; resource 2 is a resource for transmitting a format 2. In general, resource 2 is greater than or equal to resource 1. Because there are more bits transmitted in resource 2, it is greater than 2 bits.

The transmitting device (for example, the base station) first receives the ACK or NACK information formed based on the TB according to the format 1 in the resource 1. If the ACK information is detected, the UE is considered to be an ACK/NACK formed based on the TB, and the UE is considered to correctly decode the transmission. The data, if the NACK information is detected, considers that the UE is an ACK/NACK formed based on the TB, and considers that the UE does not correctly decode each CBG corresponding to the transmitted data. If the base station does not detect the ACK/NACK sent by the UE according to the format 1 in the resource 1, the base station receives the ACK/NACK information formed based on the CBG in the resource 2 according to the format 2, and if the ACK/NACK is detected, the base station retransmits the UE. Decode the wrong CBG.

Application Example 7

This embodiment provides a method for dividing a code block CB to CBG. One TB may include a plurality of code blocks CB, which are formed in units of CBG when forming acknowledgment information (ACK/NACK).

When a plurality of CBs are divided into a plurality of CBGs, a CBG placement position including a relatively large number of CBs is associated with an OFDM symbol position adjacent to the DMRS with respect to a CBG having a small number of CBs.

Or, the CBGs that contain a large number of CBs are placed before the CBGs with a small number of CBs (for example, the smaller the CBG number, the higher the CBG placement is in the scheduling unit, in time order), because Within the scheduling unit, the DMRS is in front of the data.

Alternatively, the OFDM symbol corresponding to the CB including the CBG having a large number of CBs is not later than the OFDM symbol corresponding to the CB including the CBG having a small number of CBs.

When the CBG feedback is used to confirm the information (that is, the confirmation information is formed in units of CBG, each CBG forms a confirmation information), in the CB to CBG division, the first CB (for example, the CB with the lowest number) is divided into the first CBG. (The lowest numbered CBG). The OFDM symbol used by the first CB includes the first OFDM symbol in the OFDM symbol occupied by its TB.

The first CBG (the lowest numbered CBG) contains at least one CB, and when a CB is included, the CB is the first CB in the transmission. The current transmission may be the (first) CB in one TB of the initial transmission, or may be the (first) CB in the CB in the retransmitted CBGs.

In one transmission, if num _CB CBs are included (numbered starting from 0) and is required to be divided into num _CBG CBG groups, then k (numbered from 0) CBG (denoted as CBG _k ) contains CB The number satisfies the following Equation 1 or Equation 2. The one transmission includes: one TB transmission, one data retransmitted according to CBG, data retransmitted at one time, data that is punctured in one TB transmission, or data remaining after being punctured in one TB transmission.

The equation 1 is:

R=num _CB mod num _CBG ;

The CB contained in CBG _k is:

among them,

or

If the value of n-1 or m-1 appears to be less than 0 in the calculation of the corresponding k value, then the CBG _k corresponding to the k value does not contain CB.

The equation 2 is:

R=num _CB mod num _CBG ;

The CB contained in CBGk is:

among them,

or

If some CBG _k does not contain CB, the acknowledgment information corresponding to these CBG _k is reserved for padding and needs to be sent. Or the acknowledgement information corresponding to these CBG _{k is} not transmitted (the number of bits actually transmitted will be reduced).

For a data transmission, the number of the first CB included in each CBG _k is the number of the corresponding CB in Equation 1 or Equation 2 where i is 0.

When the number of CBs is less than the number of CBGs in one transmission, the last CB does not belong to the last CBG; or, when the number of CBs is greater than the number of CBGs, the last CB belongs to the last CBG.

Application Example 8

This embodiment provides a scheme for acquiring PUCCHs of different symbol lengths, and gives symbols corresponding to some preferred PUCCH lengths, and DMRS patterns and frequency hopping modes.

It is to be noted that the drawings of the specific embodiment 8 are collectively listed in the latter half of the specific embodiment 8.

In the long PUCCH format configuration method based on the predefined puncturing, the predefined manner refers to the symbol position of the DMRS in the predefined 14 symbol length slots, and the remaining symbol positions are UCI, and the symbols in the defined time slot are numbered from left to right. 0, 1, 2, ..., 13 symbols. As shown in Figure 9 and Figure 10. The long PUCCH removes (14-N) symbols from the predetermined 14 symbols according to the required length N (number of symbols), and finally obtains a long PUCCH of N symbol lengths. For example, a long PUCCH will retain a certain length of the pre-defined format according to its starting position and duration while destroying symbols at other locations. A preferred way to eliminate the symbol is that the long PUCCH always ends at the end of the scheduling unit (if there is a short PUCCH symbol, the short PUCCH symbol is removed), such that the long PUCCH start can be determined according to the number of symbols of the long PUCCH. The symbol before the start symbol can be erased.

For a UCI of up to 2 bits, a slot structure having a length of 14 symbols is predefined. The predefined DMRS locations can be distributed in different ways while maintaining a 50% DMRS density. That is to say, half of the symbols are half of the DMRS symbol and UCI symbols. As shown in FIG. 5, the DMRS symbol and the UCI symbol are respectively distributed at odd symbol positions or even symbol positions. As shown in Figure 5.

For UCI greater than 2 bits, a slot structure having a length of 14 symbols is predefined. The predefined DMRS locations can also be distributed in different ways while maintaining a DMRS density of 20% to 30%. That is to say, there are 3 to 4 DMRS symbols in 14 symbols. In the various DMRS distribution modes shown in Figure 6, there are three DMRS symbols in (b), (c), and (d), (a), (e), (f), (g), (h) There are 4 DMRS symbols in it.

Figures 7-10 show examples of PUCCH structures with different lengths for pre-defined structure puncturing. As can be seen from Figs. 7 to 10, even in the long PUCCH of the same length, different composition structures are obtained depending on the position of the punching.

Example 1 of Application Example 8:

Based on the pre-defined format (e) of FIG. 6, a hopping pattern of a long PUCCH at different puncturing positions is provided when the length of the long PUCCH is 4, 7, 11, and 14.

The DMRS location set in the predefined format (e) is {0, 3, 7, 11}, and when the puncturing start symbol is DMRS or the adjacent UCI symbol on the left side of the DMRS, the long PUCCH structure of the pre-DMRS is obtained, so that The channel estimation is completed earlier, saving the demodulation processing time of the long PUCCH. Therefore, the optimal puncturing start symbol set of the arbitrarily long PUCCH between 4 and 14 symbol lengths in the pre-defined format (e) of FIG. 2 is {0, 2, 3, 6, 7, 10, 11}.

If considering the pattern of frequency hopping once in a time slot, the following principles should be followed: (1) The number of symbols included in the two hopping parts should be as equal as possible. If they are not equal, the difference of the number of symbols should be as small as possible; (2) The ratio of the number of DMRS symbols and UCI symbols in the two frequency hopping parts should be as close as possible or close to each other; (3) The two frequency hopping parts should follow the structure of the DMRS preamble as much as possible (the DMRS is located at the first or second symbol position) ).

In the following Tables 1-3, the hopping pattern x+y indicates that only one frequency hopping is performed in one time slot, and the number of symbols included in the two frequency hopping parts is x and y symbols, respectively. Under the same hopping pattern x+y, the structure of the specific hopping pattern is different because different long PUCCH structures (the number of DMRS and UCI symbols and the position distribution are different). For example, the long PUCCH frequency hopping with a length of 7 symbols in FIG. 4 has two hopping patterns 3+4 or 4+3, but under different puncturing start symbols, 3 symbol hopping in 3+4 or 4+3 The partial and 4-symbol frequency hopping sections have the same or different structural configurations. When the puncturing start symbol is 0, the hopping part DMRS symbol of the 3 symbols in the 3+4 hopping pattern is located at the first symbol position, and when the initial puncturing symbol is 2, the 3+4 hopping pattern is 3 The hopping portion of the symbol DMRS is located at the second symbol position.

"-" indicates that the long PUCCH format determined by this puncturing start symbol and length does not support frequency hopping.

"X" indicates that this punch start symbol and length combination does not exist. Table 1 is a hopping pattern table based on a predefined format (e) of Example 1 of Concrete Embodiment 8.

Table 1

Example 2:

Based on the pre-defined format (d) of FIG. 6, a hopping pattern of a long PUCCH at different puncturing positions is provided when the length of the long PUCCH is 4, 7, 11, and 14. The set of DMRS locations in the predefined format (d) is {3, 7, 11}, and the optimal puncturing start symbol set of any long PUCCH between 4 and 14 symbol lengths in the predefined format (d) of FIG. For {2, 3, 6, 7, 10, 11}. Table 2 is a hopping pattern table based on a predefined format (d) according to Example 2 of Concrete Embodiment 8.

Table 2

Example 3:

Based on the pre-defined format (g) of FIG. 6, a hopping pattern of a long PUCCH at different puncturing positions is provided when the length of the long PUCCH is 4, 7, 11, and 14. The DMRS location set in the predefined format (g) is {0, 4, 7, 11}, and the optimal puncturing start of any long PUCCH between 4 and 14 symbol lengths in the predefined format (g) of Figure 2. The symbol set is {0, 3, 4, 6, 7, 10, 11}. Table 3 is a pre-defined format (g) based hopping pattern table according to Example 3 of Concrete Embodiment 8.

table 3

5 is a schematic diagram of a 1/2 bit UCI predefined format (14 symbol slot) according to a specific embodiment 8 of the present disclosure.

6 is a schematic diagram (14 symbol slot) of a UCI predefined format greater than 2 bits according to a specific embodiment 8 of the present disclosure.

7 is a schematic diagram of a 4-symbol long PUCCH (greater than 2-bit UCI) hopping pattern (corresponding to Example 1) according to Embodiment 8 of the present disclosure.

8 is a schematic diagram of a symbol length long PUCCH (greater than 2-bit UCI) hopping pattern (corresponding to Example 1) according to Embodiment 8 of the present disclosure.

9 is a schematic diagram of a 11-symbol long PUCCH (greater than 2-bit UCI) hopping pattern (corresponding to Example 1) according to a specific embodiment 8 of the present disclosure.

10 is a schematic diagram of a 14-symbol long PUCCH (greater than 2-bit UCI) hopping pattern (corresponding to Example 1) according to Embodiment 8 of the present disclosure.

11 is a schematic diagram of a 4-symbol long PUCCH (greater than 2-bit UCI) hopping pattern (corresponding to Example 2) according to Embodiment 8 of the present disclosure.

12 is a schematic diagram of a 7-symbol long PUCCH (greater than 2-bit UCI) hopping pattern (corresponding to Example 2) according to Embodiment 8 of the present disclosure.

13 is a schematic diagram of a 11-symbol long PUCCH (greater than 2-bit UCI) hopping pattern (corresponding to Example 2) according to Embodiment 8 of the present disclosure.

14 is a schematic diagram of a 14-symbol long PUCCH (greater than 2-bit UCI) hopping pattern (corresponding to Example 2) according to Embodiment 8 of the present disclosure.

15 is a schematic diagram of a 4-symbol long PUCCH (greater than 2-bit UCI) hopping pattern (corresponding to Example 3) according to Embodiment 8 of the present disclosure.

16 is a schematic diagram of a 7-symbol long PUCCH (greater than 2-bit UCI) hopping pattern (corresponding to Example 3) according to Embodiment 8 of the present disclosure.

17 is a schematic diagram of a 11-symbol long PUCCH (greater than 2-bit UCI) hopping pattern (corresponding to Example 3) according to a specific embodiment 8 of the present disclosure.

18 is a schematic diagram of a 14-symbol long PUCCH (greater than 2-bit UCI) hopping pattern (corresponding to Example 3) according to Embodiment 8 of the present disclosure.

Application Example 9

CBG-based retransmission is discussed in the NR standard setting, and it is suggested that the DCI indicate which CBG is retransmitted or newly transmitted (referred to as CBG retransmission indication signaling). That is, each CBG will have a corresponding indication signaling indicating whether the CBG is a retransmitted CBG or a new transmitted CBG. One TB contains at least one CB, and one CBG contains one or more CBs.

The following provides a data transmission method, which can support multiple data blocks to be transmitted simultaneously, and particularly relates to CBG-based retransmission, which can effectively improve the efficiency of retransmission.

A plurality of data blocks are scheduled and transmitted through a downlink control information (DCI) in a scheduling unit by means of time division multiplexing. Wherein, one data block corresponds to one TB, or one data block corresponds to a part or all code blocks CB or CBG of one TB. For example, FIG. 19 is a schematic diagram showing the use of a process number when retransmitting a CBG and a new TB are simultaneously transmitted according to Embodiment 9 of the present disclosure. In FIG. 19, initially transmitting a TB#1 in the scheduling unit n, the TB can be divided. For 4 CBGs (or the TB corresponds to 4 CBGs, the actual transmission is still performed according to CB, but is divided into 4 CBG future feedback confirmation information). It is assumed that CBG#0 and CBG#2 of TB#1 are not correctly decoded by the receiving end device, and then CBG#0 and CBG#2 of TB#1 are retransmitted in the scheduling unit n+k1; meanwhile, in the scheduling unit n+k1 Zhongxin passed TB#2, and TB#2 was divided into 2 CBGs (the size of these two CBGs can be the same size as the CBG of TB#1, or they can be different sizes, and they need resources in the frequency domain and/or time. The fields are all tunable, but all CBGs in the scheduling unit must be required, including the CBGs of different TBs, and the relative order remains unchanged. CBG#0 and CBG#1, respectively, are in the scheduling unit. The sequential position replaces the sequential positions of CBG #1 (snowflake, tick) and CBG#3 (snowflake, tick) of TB#1 that have been correctly transmitted in the scheduling unit n. It is assumed that in the scheduling unit n+k1, CBG#0 of TB#1 is still not correctly received, CBG#2 is correctly received; in addition, CBG#1 of TB#2 is not correctly received in scheduling unit n+k1. CBG#0 is correctly received; then, in scheduling unit n+k2, CBG#0 of TB#1 continues to be retransmitted; CBG#1 of TB#2 is retransmitted; TB#3 is a new TB, which is first transmitted , including CBG#0 (backslash) and CBG#1 (backslash), their sequential positions replace CBG#2 of TB#1 that has been correctly transmitted in scheduling unit n+k1 (snow point, check mark) ) and the sequential position of CBG#0 (slanted line, tick) of TB#2.

A DCI is sent in the PDCCH of the scheduling unit, including a progress number, and the process number is always a new TB application. (Note that no new TB can be transmitted at the same time. For example, in the scheduling unit n+k1, only the CBG of TB#1 that needs to be retransmitted can be transmitted, and the process number in the DCI is the weight of the retransmitted data) The passed CBG defaults to the process number at the time of the initial transfer.

The order position of all CBGs in the scheduling unit remains unchanged, and the CBG of the newly transmitted TB replaces the sequential position of the CBG that has been correctly in the last transmission.

The receiving end device can learn whether each CBG in the primary transmission is a retransmission or a new transmission according to the CBG retransmission indication signaling. If retransmission, the UE further infers according to its sequential position in the scheduling unit and the number of consecutive retransmissions. Which TB of the scheduling unit belongs to the initial transmission of the CBG. For example, in the scheduling unit n+k2, the receiving end device finds that the first CBG#0 is retransmitted, and can find that the CBG#0 is still the first CBG in the scheduling unit n+k1, and is also a retransmission. , corresponding to retransmission 2 times in the same order position, the receiving end device finds the first CBG#0 in the scheduling unit n is the initial transmission, so the receiving end device can get, the first in the scheduling unit n+k2 The CBG #0 is the TB#1 that was originally transmitted in the scheduling unit n (only the TB#1 is transmitted in the scheduling unit n). Therefore, the receiving end device can combine the same CBG that was originally transmitted and retransmitted for decoding.

The modulation and coding information MCS and resource allocation information in the one DCI are shared as all TBs or CBGs in the scheduling unit.

The CB or CBG is mapped in the resources allocated in the slot according to the principle of frequency domain priority. In this way, the receiving device calculates the specific resources occupied by each CBG in the allocated resources according to the agreed mapping rules, the size of each CBG, the resource allocation information, the modulation and coding policy (MCS) information, and the order positions of all the CBGs.

It is assumed here that the relationship of the scheduling units n, n+k1 and n+k2 is that n+k1 is a retransmission scheduling unit of n, and n+k2 is a retransmission scheduling unit of n+k1.

The above assumptions can be directly or indirectly supported by the following methods.

In the first embodiment, the retransmission scheduling unit corresponding to the data in the scheduling unit n is configured, for example, configured to be interval k1 slots, that is, the retransmission scheduling unit corresponding to the data in the scheduling unit n is n+k1. The configuration may be through physical layer signaling or Radio Resource Control (RRC) messages, or a combination of the two. When used in combination, the RRC configures a set of values of k1, and then indicates a specific k1 value from the set of values of k1 through physical layer signaling such as DCI.

In the mode 2, the process ID corresponding to each of the plurality of TBs (or retransmitted CBGs) may be included in the DCI of each scheduling data. For example, in the scheduling unit n+k1, when the retransmitted CBG (from TB#1) and the new TB#2 are scheduled via one DCI, the DCI includes the process number corresponding to the retransmitted CBG (note that it is necessary to process with the initial transmission) The number is consistent), and also contains the process number corresponding to the new TB#2. Equivalent to the process number indirectly tells the UE which retransmission CBG comes from which scheduling unit.

Mode 3, retransmission using a hybrid hybrid automatic repeat request (HARQ) retransmission mechanism.

Mode 4, the retransmitted CBG and the new TB use the shared process ID. In this case, the DCI contains only one process number and is used to retransmit the CBG and the new TB. For example, the process number configured for TB#1 in scheduling unit n is 1, and the process number configured for retransmission CBG and new TB#2 in scheduling unit n+k1 is still 1 (because there is retransmission from TB#1) The CBG, retransmit CBG needs to keep the same process number as the initial transmission), so that the new TB#2 shares the process number with the retransmission CBG from TB#1. The UE determines, in which scheduling units, the retransmission CBG is transmitted or retransmitted by the number of retransmissions of the CBG and the process number. The relative order position of all CBGs in the scheduling unit remains unchanged, and the new TB always transmits instead of the sequential position of transmitting the correct CBG.

Application Example 10

The method for solving the ACK/NACK based on the CBG feedback in the embodiment is advantageous for improving the probability of correctly obtaining whether the data to be transmitted is correctly decoded.

Method A:

For one TB, the base station configures the UE to always form an ACK/NACK according to the TB (eg, each TB forms a 1-bit ACK/NACK). The base station receives the ACK/NACK. If the feedback is NACK, the base station retransmits the TB, and configures or implies that the receiving end device forms an ACK/NACK according to the CBG (for example, one ACK/NACK for each CBG) and feeds back.

For a TB, if it is an initial transmission, the UE forms an ACK/NACK according to the configuration or convention according to the TB and feeds back. If the TB is re-established, the UE forms an ACK/NACK according to the configuration or convention according to the CBG and feeds back.

That is, the UE and the base station agree that an ACK/NACK is always formed according to the CBG for the retransmitted TB, and is fed back. The base station configures the UE or the UE to agree to form an ACK/NACK with an CBG for the nth transmission of one TB. The special case is the first transmission (initial transmission) An=1, when retransmitting (n>1) , An>1.

Method B:

For one TB, if N bits of ACK/NACK information are formed based on the CBG, the UE and the base station agree that one or more states in the N-bit combination express TB-based ACK information, using multiples in the N-bit combination The state expresses NACK information based on TB. In the state of NACK, different states indicate the location of the specific error CBG. For example, when the error CBG is less than K, the bit of 1 indicates the location of the specific error CBG, and when the error CBG is greater than When it is equal to K, it is represented by 000, K<=N. For example, when N=3, the state 111, 110, 101, 011 using half of the total of 8 states is represented as ACK, and the state 000, 001, 010, 100 using half of the total of 8 states is represented as NACK (ie, TB). This is not correctly decoded. This improves the decoding accuracy of the base station. For example, partial bit decoding errors in 3 bits can correctly convey the information that the TB is correctly decoded. Further, in the state indicating NACK, the bit indicating that the bit is 1 indicates a specific error of the CBG, for example, 001 indicates that the TB is not correctly decoded, and the last CBG is not correctly decoded. In addition, 000 means that the TB is not correctly decoded.

Method C:

For a TB, if the UE forms an ACK/NACK according to the CBG, then it should be described which specific CBGs in the TB are not correctly decoded, and then the information on which CBGs are not correctly decoded is fed back to the base station. The information fed back by the UE includes: parameter 1, specifically describing the starting position of the CBG that is not correctly decoded; parameter 2, which is optional, describes the number of CBGs that are not correctly decoded or the number of CBGs that are not correctly decoded. Number range. That is, how many CBGs are not correctly decoded from the beginning of the described incorrectly decoded CBG. This method can be applied to the ACK/NACK feedback of the CBG of the punctured eMBB when the URLLC service punctured the eMBB service transmission. Parameter 1 and parameter 2 can be displayed or implied in different states. The combination of parameter 1 and parameter 2 can implicitly bring out information about TB ACK/NACK.

For example, in an eMBB slot, a plurality of OFDM symbols are punctured consecutively, so that consecutive CBGs cannot be correctly decoded by the receiving device. In this case, ACK/NACK feedback information may be formed according to the manner, for example, parameter 1 indication The starting CBG is not correctly decoded, and parameter 2 describes the number of CBGs that are not correctly decoded.

As a possible example, the base station knows the size of the URLLC TB, and the base station configures the CBG of the eMBB to be equal to the size of the URLLC TB. At this time, when the URLLC is transmitted, the CBG of one eMBB is always erased, so that it is always assumed that the CBG (ie, the punctured CBG) that is not correctly decoded continuously is one, and the parameter is omitted. At this point, option B can be used.

With the above technical solution, if the UE is allowed to form an ACK/NACK based on the CBG or the TB and is transmitted, the solution further provides a transmission mode to support the handover of the CBG or TB mechanism to transmit the corresponding ACK/NACK information. This type of transmission can improve the efficiency of retransmission and has less overhead.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the embodiments of the present disclosure may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic The disc, the optical disc, includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present disclosure.

Embodiment 2

In the embodiment, a feedback device for confirming information is provided, which is disposed at the receiving end device, and the device is configured to implement the foregoing embodiments and application embodiments, and details are not described herein. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

20 is a structural diagram of a feedback device for confirming information according to a preferred embodiment of the present disclosure. As shown in FIG. 20, the device includes:

The determining module 2002 is configured to determine a manner of the feedback confirmation information according to the decoding status of the received TB or the CBG, where the confirmation information includes the first confirmation information and the second confirmation information;

The feedback module 2004 is configured to: after determining that the TB or the CBG are correctly decoded or not correctly decoded, generating the first acknowledgement information based on the TB, and transmitting the first acknowledgement information in the first resource;

The feedback module 2004 is further configured to generate the second acknowledgement information based on the CBG and transmit the second acknowledgement information in the second resource if it is determined that there is no correct decoding of all TBs or CBGs.

In an embodiment, the feedback module 2004 is configured to: after determining that the TB or the CBG are correctly decoded or not correctly decoded, generate the first acknowledgement information based on the TB, and transmit the first acknowledgement information in the first resource, Includes one of the following:

In a case where it is determined that both the TB or the CBG are correctly decoded, the feedback module 2004 generates ACK information based on the TB, and transmits the ACK information in the first resource;

In the case where it is determined that neither TB nor CBG is correctly decoded, the feedback module 2004 generates NACK information based on the TB, and transmits the NACK information in the first resource.

In an embodiment, transmitting the first acknowledgement information in the first resource, or transmitting the second acknowledgement information in the second resource, includes: transmitting, by using the first format, the first acknowledgement information in the first resource, where The first format is used to transmit a UCI less than or equal to 2 bits; the second format is used to transmit the second acknowledgement information in a second format, where the second format is used to transmit a UCI greater than 2 bits; wherein the uplink control The information includes the first confirmation information or the second confirmation information.

In an embodiment, the first resource includes a resource configured by the sending end device for the receiving end device to transmit a UCI in the first format, and the second resource includes the sending end device as the receiving end device. Configured to transmit a UCI resource of the second format.

In an embodiment, the feedback module 2004, when determining that both the TB or the CBG are correctly decoded or not correctly decoded, generating the first acknowledgement information based on the TB, and transmitting the first acknowledgement information in the first resource, including :

The first confirmation information is transmitted in the specific resource.

In an embodiment, the feedback module 2004, in the case that it is determined that the TB or the CBG is not correctly decoded, the second confirmation information is generated based on the CBG, and the second confirmation information is transmitted in the second resource, including:

The second acknowledgment information is transmitted in the second resource, where the second resource is a resource configured by the sending end device for the receiving end device, and the second format is used to transmit a UCI greater than 2 bits.

In an embodiment, in the absence of a specific resource for transmitting the first acknowledgment information, the feedback module 2004 transmits the first acknowledgment information according to the first format in the second resource, where the first format is used. The uplink control information is less than or equal to 2 bits.

In an embodiment, when the first resource and the second resource are part of resources in the PUSCH of the receiving end device, the first resource and the second resource are received by the receiving end device by punching or rate matching. The PUSCH resource of the end device determines a specific resource for transmitting the first acknowledgement information or the second acknowledgement information, respectively. The puncturing or rate matching rule is pre-agreed by the receiving device and the transmitting device.

In an embodiment, the determining module 2002 determines the manner of feedback confirmation information according to the decoding status of the received TB or CBG, including:

In a feedback confirmation information, when the determining module 2002 determines to transmit the confirmation information simultaneously with other UCI information, the feedback module 2004 always generates the second confirmation information based on the CBG, and the second confirmation information and the other UCI The information is encoded and transmitted.

According to another embodiment of the present disclosure, there is provided a receiving device for confirming information, which is provided at a transmitting end device, and includes:

a sending module configured to send data to the receiving device;

The receiving module is configured to receive the acknowledgement information fed back by the receiving device according to the first resource and/or the second resource;

Alternatively, the receiving module is further configured to receive the acknowledgement information fed back by the receiving device according to the first format and/or the second format.

In an embodiment, the receiving module receives the acknowledgement information fed back by the receiving device according to the first resource and/or the second resource, including:

Receiving, by the receiving module, the first acknowledgement information fed back by the receiver device, where the first acknowledgement information is generated by the receiver device based on the received TB;

The receiving module receives the second confirmation information fed back by the receiving end device on the second resource, where the second confirmation information is generated by the receiving end device based on the received code block group.

In an embodiment, the receiving module receives the acknowledgement information fed back by the receiving device according to the first format and/or the second format, including:

The receiving module receives the first confirmation information fed back by the receiving device according to the first format, where the first confirmation information is generated by the receiving device based on the received TB;

The receiving module receives the second confirmation information fed back by the receiving end device according to the second format, where the second confirmation information is generated by the receiving end device based on the received CBG.

In an embodiment, the method further includes:

The receiving module receives, in the first resource, the first acknowledgement information fed back by the receiving device according to the first format, where the first acknowledgement information is generated by the receiver device based on the received TB;

The receiving module receives, in the second resource, the second acknowledgement information that is received by the receiver device according to the second format, where the second acknowledgement information is generated by the receiver device based on the received CBG.

In an embodiment, the first format is used to transmit UCI less than or equal to 2 bits;

The second format is used to transmit UCI greater than 2 bits;

In an embodiment, in a case that the receiving module does not receive the first confirmation information in the part of the resource, the method includes:

The receiving module receives, in the second resource, the second acknowledgment information according to the second format, where the second resource is a resource configured by the sending end device for the receiving end device, and the second acknowledgment information is that the receiving end device is based on Generated by the CBG, the second format is used to transmit uplink control information greater than 2 bits.

In an embodiment, in a case that the receiving module detects that the receiving end device lacks a PUSCH for sending the first acknowledgement information, the method further includes:

In an embodiment, in a case that the receiving module does not receive the first confirmation information in the PUSCH resource, the method further includes:

The receiving module receives the second confirmation information in the PUSCH resource according to the second preset puncturing rule or the rate matching pattern, where the second acknowledgment information is generated by the receiving end device based on the received CBG.

Optionally, if the receiving module detects that the receiving end device lacks the PUSCH resource for sending the first acknowledgement information or the second acknowledgement information, the method further includes:

The receiving module allocates resources for transmitting the first confirmation information or the second confirmation information to the receiving end device.

In an embodiment, after the sending module sends the data to the receiving device, the method further includes:

When the receiving module determines that the acknowledgment information fed back by the receiving end device is transmitted simultaneously with other UCI information, the receiving module determines that the acknowledgment information is the second acknowledgment information, wherein the second acknowledgment information is that the receiving end device is based on receiving The CBG is generated.

It should be noted that each of the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination. The forms are located in different processors.

Embodiment 3

According to another embodiment of the present disclosure, a receiving end device is provided, which is a hardware device, and the device includes:

The first processor is configured to determine a manner of the feedback confirmation information according to the decoding status of the received TB or the CBG, where the confirmation information includes the first confirmation information and the second confirmation information;

And configured to generate the first acknowledgment information based on the TB in the case of determining that both the TB or the CBG are correctly decoded or not correctly decoded, or configured to determine that there is no TB or CBG correctly decoded. Generating second confirmation information based on the CBG;

The first communication device is configured to transmit the first acknowledgement information in the first resource, or is further configured to transmit the second acknowledgement information in the second resource.

It should be added that the above-mentioned component hardware of the receiving device can be configured to perform the method steps performed by the receiving device in all the embodiments described above.

According to another embodiment of the present disclosure, a sender device is provided, the device comprising:

a second communication device configured to send data to the receiving device;

The second processor is configured to receive the acknowledgement information fed back by the receiver device according to the first resource and/or the second resource; or the second processor is further configured to receive the receive according to the first format and/or the second format Confirmation information fed back by the device.

It should be added that the above-mentioned component hardware of the transmitting device can be configured to perform the method steps performed by the transmitting device in all the embodiments described above.

Embodiment 4

According to another embodiment of the present disclosure, there is provided a processor configured to execute a program, wherein the program is executed to perform the method of any of the above embodiments.

Embodiment 5

According to another embodiment of the present disclosure, there is provided a storage medium comprising a stored program, wherein the program is executed to perform the method described in any of the above embodiments.

It will be apparent to those skilled in the art that the various modules or steps of the present disclosure described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. As such, the disclosure is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present disclosure, and is not intended to limit the disclosure, and various changes and modifications may be made to the present disclosure. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and scope of the present disclosure are intended to be included within the scope of the present disclosure.

Claims

A feedback method for confirming information, including:

And determining, by the receiving end device, the manner of the feedback confirmation information according to the decoding condition of the received transport block or the code block group, where the confirmation information includes the first confirmation information and the second confirmation information;

In the case that it is determined that the transport block or the code block group is correctly decoded or not correctly decoded, the receiving end device generates first acknowledgement information based on the transport block, and transmits the first acknowledgement information in the first resource;

Or, in a case of determining that there is not correctly decoding all the transport blocks or code block groups, the receiving end device generates second acknowledgement information based on the code block group, and transmits the second acknowledgement information in the second resource. .
The method according to claim 1, wherein in the case of determining that the transport block or the code block group is correctly decoded or not correctly decoded, the receiving end device generates first acknowledgement information based on the transport block, in the first resource. The first confirmation message is transmitted, including one of the following:

In the case that it is determined that the transport block or the code block group is correctly decoded, the receiving end device generates the acknowledgement information ACK information based on the transport block, and transmits the ACK information in the first resource;

In a case where it is determined that the transport block or the code block group is not correctly decoded, the receiving end device generates negative answer NACK information based on the transport block, and transmits the NACK information in the first resource.
The method of claim 1, wherein transmitting the first confirmation information in the first resource or transmitting the second confirmation information in the second resource comprises:

Transmitting, by using the first format, the first acknowledgement information, where the first format is used to transmit uplink control information that is less than or equal to 2 bits;

Transmitting the second acknowledgement information in a second format, where the second format is used to transmit uplink control information greater than 2 bits;

The uplink control information includes the first confirmation information or the second confirmation information.
The method according to claim 3, wherein the first resource comprises a resource configured by the source device for transmitting, by the receiving device, an uplink control information of the first format; the second resource And the resource that is configured by the sending end device to be used by the receiving end device to transmit uplink control information of the second format.
The method of claim 4, wherein the first resource is the same as the second resource or the first resource is a subset of the second resource.
The method according to claim 1, wherein the first resource or the second resource is a resource shared by a plurality of the receiving end devices.
The method according to claim 1, wherein, in the case of determining that the transport block or the code block group is correctly decoded or not correctly decoded, the receiving end device generates first acknowledgement information based on the transport block, Transmitting the first confirmation information in a resource, including:

When the first resource is a part of resources in the physical uplink shared channel (PUSCH) of the receiving end device, the first resource is that the receiving end device matches the PUSCH resource of the receiving end device by puncturing or rate. Determining a specific resource for transmitting the first acknowledgement information, where a rule of puncturing or rate matching is pre-agreed by the receiving end device and the sending end device;

Transmitting the first confirmation information in the specific resource.
The method according to claim 7, wherein in the case of determining that there is not correctly decoding all transport blocks or code block groups, the receiving end device generates second acknowledgement information based on the code block group, in the second Transmitting the second confirmation information in the resource, including:

The receiving end device uses the second format to transmit the second acknowledgement information in the second resource, where the second resource is a resource configured by the sending end device for the receiving end device, and the second format is It is used to transmit uplink control information UCI greater than 2 bits.
The method according to claim 8, wherein the second resource is a resource shared by a plurality of the receiving end devices.
The method according to claim 7, wherein in the case that the receiving end device lacks a specific resource for transmitting the first acknowledgement information, the receiving end device according to the first format in the second resource Transmitting the first acknowledgement information, where the first format is used to transmit uplink control information that is less than or equal to 2 bits.
The method of claim 1 wherein the method further comprises:

When the first resource and the second resource are part of the resources in the PUSCH of the receiving end device, the first resource and the second resource are the receiving end device through the puncturing or rate matching receiving end. The PUSCH resource of the device is used to determine a specific resource for transmitting the first acknowledgement information or the second acknowledgement information, where the puncturing or rate matching rule is pre-agreed by the receiving end device and the sending end device.
The method according to claim 1, wherein the manner in which the receiving end device determines the feedback confirmation information according to the decoding condition of the received transport block or the code block group includes:

In a feedback confirmation information, when the receiving end device determines to transmit the confirmation information simultaneously with other UCI information, the receiving end device always generates the second confirmation information based on the code block group, and The second confirmation information is encoded and transmitted after the other UCI information is encoded.
A method for receiving confirmation information, comprising:

The sending end device sends data to the receiving end device; the sending end device receives the acknowledgement information fed back by the receiving end device according to the first resource and/or the second resource, or the sending end device according to the first format and/or The second format receives the acknowledgement information fed back by the receiving device.
The method according to claim 13, wherein the receiving end device receives the confirmation information fed back by the receiving end device according to the first resource and/or the second resource, including:

The sending end device receives the first acknowledgement information fed back by the receiving end device on the first resource, where the first acknowledgement information is generated by the receiving end device based on the received transport block;

The sending end device receives the second acknowledgement information fed back by the receiving end device on the second resource, where the second acknowledgement information is generated by the receiving end device based on the received code block group.
The method according to claim 13, wherein the receiving end device receives the confirmation information fed back by the receiving end device according to the first format and/or the second format, including:

Receiving, by the sending end device, the first acknowledgement information fed back by the receiving end device according to the first format, where the first acknowledgement information is generated by the receiving end device based on the received transport block;

The sending end device receives the second acknowledgement information fed back by the receiving end device according to the second format, where the second acknowledgement information is generated by the receiving end device based on the received code block group.
The method of claim 14 or 15, wherein the method further comprises:

Receiving, by the sending end device, the first acknowledgement information fed back by the receiving end device according to the first format, where the first acknowledgement information is that the receiving end device is based on the received transport block Generated;

The sending end device receives, in the second resource, the second acknowledgement information that is received by the receiving end device according to the second format, where the second acknowledgement information is that the receiving end device is based on the received code. Block group generated.
The method of claim 13 wherein

The first resource includes a resource configured by the sending end device for the receiving end device to transmit uplink control information of the first format, and the second resource includes the sending end device is the A resource configured by the receiving device to transmit uplink control information of the second format.
The method of claim 13 wherein

The first format is used to transmit uplink control information that is less than or equal to 2 bits;

The second format is used to transmit uplink control information greater than 2 bits;

The uplink control information includes first confirmation information or second confirmation information.
The method according to claim 13, wherein the receiving end device receives the confirmation information fed back by the receiving end device according to the first resource and/or the second resource, including:

When the first resource is a part of the resources in the PUSCH of the receiving end device, the sending end device receives the first confirmation information in the part of the resources according to the first preset puncturing rule or the rate matching pattern, where The first confirmation information is generated by the receiving end device based on the received transport block.
The method according to claim 19, wherein, in a case where the transmitting device does not receive the first confirmation information in the partial resource, the method includes:

The sending end device receives, in the second resource, the second acknowledgment information according to the second format, where the second resource is a resource configured by the sending end device for the receiving end device, and the second acknowledgment The information is generated by the receiving end device based on the code block group, and the second format is used to transmit uplink control information greater than 2 bits.
The method according to claim 19, wherein, in the case that the transmitting end device detects that the receiving end device lacks a PUSCH for transmitting the first acknowledgement information, the method further includes:

And the sending end device allocates, by the sending end device, a resource for transmitting the first acknowledgement information.
The method according to claim 19, wherein, in a case that the source device does not receive the first acknowledgement information in the PUSCH resource, the method further includes:

The transmitting device receives the second acknowledgement information in the PUSCH resource according to the second preset punching rule or the rate matching pattern, where the second acknowledgement information is generated by the receiving device according to the received code block group. of.
The method according to claim 22, wherein, in a case where the transmitting end device detects that the receiving end device lacks a PUSCH resource for transmitting the first acknowledgement information or the second acknowledgement information, the method further include:

And the sending end device allocates, by the sending end device, a resource for transmitting the first acknowledgement information or the second acknowledgement information.
The method according to claim 13, wherein after the transmitting device sends the data to the receiving device, the method further includes:

In the case that the sending end device determines that the acknowledgment information fed back by the receiving end device is transmitted simultaneously with other UCI information, the sending end device determines that the acknowledgment information is the second acknowledgment information, wherein the second acknowledgment information The receiving end device is generated based on the received code block group.
A feedback device for confirming information, including:

a determining module, configured to determine a manner of feedback confirmation information according to a decoding condition of the received transport block or the code block group, where the confirmation information includes the first confirmation information and the second confirmation information;

a feedback module, configured to: after determining that the transport block or the code block group is correctly decoded or not correctly decoded, generating the first acknowledgement information based on the transport block, and transmitting the first acknowledgement information in the first resource;

The feedback module is further configured to generate second confirmation information based on the code block group and transmit the second confirmation information in the second resource, if it is determined that there is not correctly decoding all the transport blocks or code block groups .
A receiving device for confirming information, comprising:

a sending module configured to send data to the receiving device;

The receiving module is configured to receive the acknowledgement information fed back by the receiving end device according to the first resource and/or the second resource;

Alternatively, the receiving module is further configured to receive the acknowledgement information fed back by the receiving end device according to the first format and/or the second format.
A receiving device includes:

The first processor is configured to determine a manner of the feedback confirmation information according to the decoding condition of the received transport block or the code block group, where the confirmation information includes the first confirmation information and the second confirmation information;

And configured to generate first acknowledgement information based on the transport block if it is determined that the transport block or the code block group is correctly decoded or not correctly decoded, or is further configured to determine that there is not all transport blocks or When the code block group is correctly decoded, generating second confirmation information based on the code block group;

The first communication device is configured to transmit the first acknowledgement information in the first resource, or is further configured to transmit the second acknowledgement information in the second resource.
A transmitting device includes:

a second communication device configured to send data to the receiving device;

The second processor is configured to receive the acknowledgement information fed back by the receiver device according to the first resource and/or the second resource; or the second processor is further configured to receive according to the first format and/or the second format The confirmation information fed back by the receiving device.
A storage medium, the storage medium comprising a stored program, wherein the program is executed to perform the method of any one of claims 1 to 12, or the method of any one of claims 13 to 24.
A processor configured to execute a program, wherein the program is executed to perform the method of any one of claims 1 to 12, or the method of any one of claims 13 to 24.