WO2023005583A1 - Feedback information indication method, and communication apparatus - Google Patents

Abstract

Provided in the present application are a feedback information indication method, and a communication apparatus, which are conducive to improving the reliability of uplink data transmission of a second priority. The method comprises: a network device sending first DCI, wherein the first DCI is used for scheduling downlink data transmission that is carried on a PDSCH of a first priority and/or for scheduling downlink data transmission that is carried on a PDSCH of a second priority, and correspondingly, a terminal device detecting the first DCI in a PDCCH; the network device sending second DCI, wherein the second DCI is used for scheduling a PUSCH of the second priority, and the second DCI comprises DAI_UL, and correspondingly, the terminal device receiving the second DCI; and the terminal device sending first HARQ information and/or second HARQ information on the PUSCH according to a detection situation of the first DCI, and the DAI_UL, and correspondingly, the network device receiving the first HARQ information and/or the second HARQ information.

Description

Indication method and communication device for feedback information

This application claims the priority of the Chinese patent application with the application number 202110865190.3 and the application title "Indication method and communication device for feedback information" submitted to the China Patent Office on July 29, 2021, the entire contents of which are incorporated by reference in this application middle.

technical field

The present application relates to the technical field of communication, and in particular to a method for indicating feedback information and a communication device.

Background technique

Hybrid automatic repeat request (HARQ) is an efficient transmission mechanism. In a communication system, when a terminal device receives downlink control information (DCI) for scheduling downlink data transmission carried on a physical downlink shared channel (PDSCH), it can feed back to the network device A HARQ acknowledgment (acknowledgment, ACK) or negative acknowledgment (non-acknowledgment, NACK) message. When a network device receives a feedback NACK message, it needs to retransmit data. This way of using the HARQ transmission mechanism to feed back whether data needs to be retransmitted, on the one hand, can greatly improve the reliability of downlink data transmission. On the other hand, the overall resource consumption of data transmission can be reduced.

At present, when transmission services of different priorities collide in the time domain, the HARQ feedback information corresponding to the transmission services of different priorities will be multiplexed, that is, the HARQ information of different priorities will pass through the physical uplink shared channel of the same priority. (physical uplink control channel, PUCCH) or physical uplink control channel (physical uplink shared channel, PUSCH) for transmission. In such a scenario where HARQ information of different priorities is multiplexed on the uplink channel of the same priority, if the terminal device misses the DCI of low priority, the load size of the feedback HARQ information will be wrong. If the terminal device uses the rate matching method to send control information and uplink data on the high-priority PUSCH, the mapping position of the high-priority uplink data will be wrong and cannot be successfully decoded, thus affecting the reliability of high-priority uplink data transmission .

Contents of the invention

The present application provides a method for indicating feedback information and a communication device, which are beneficial to improving the reliability of high-priority uplink data transmission.

In a first aspect, a method for indicating feedback information is provided, and the method includes: a terminal device detects first downlink control information (DCI) in a physical downlink control channel (physical downlink control channel, PDCCH), and the The first DCI is used for scheduling downlink data transmission carried on the PDSCH of the first priority and/or for scheduling downlink data transmission carried on the PDSCH of the second priority, and the second priority is higher than the First priority; the terminal device receives a second DCI from the network device, the second DCI is used to schedule the physical uplink shared channel PUSCH of the second priority, and the second DCI includes a downlink allocation indication Information DAI_UL; the terminal device sends the first hybrid automatic repeat transmission HARQ information and/or the second HARQ information on the PUSCH according to the detection of the first DCI and the DAI_UL, and the second HARQ information The priority is higher than the priority of the first HARQ information; wherein, the state value of the DAI_UL is a first preset value, and when the load size of the first HARQ information is 1, the PUSCH does not include the the first HARQ information; or, the state value of the DAI_UL is a first preset value, and when the payload size of the first HARQ information is 0, the PUSCH includes the first HARQ information with a fixed payload size , the fixed load is determined according to a predefined rule.

In the embodiment of the present application, the terminal device sends semi-static first HARQ information and/or second HARQ information to the network device according to the detection of the first DCI and the value of DCI_UL in the second DCI, effectively avoiding DCI_UL When the value is a preset value, the terminal device sends HARQ information with an incorrect payload size to the network device due to missing detection of the first DCI for scheduling downlink data transmission carried on the PDSCH with the second priority. The method helps to improve the reliability of the fed back HARQ information and the reliability of the second priority uplink data transmission by redefining the rules of the DCI_UL value and the load size of the HARQ information.

The above-mentioned second DCI may include one DAI_UL, or may include two DAI_ULs, which is not limited in this application.

The HARQ information in this embodiment of the present application includes ACK and/or NACK.

It should be understood that each first DCI sent by the above network device may have corresponding HARQ information with a payload size of 1. And the first DCI for scheduling the downlink data transmission carried on the PDSCH of the first priority, corresponding to the first HARQ information, is used for scheduling the first DCI of the downlink data transmission carried on the PDSCH of the second priority, Corresponding to the above second HARQ information.

With reference to the first aspect, in some implementation manners of the first aspect, the sending the first HARQ information and/or the second HARQ information on the PUSCH includes: the state value of the DAI_UL is the first preset value, when the payload size of the second HARQ information is 1, the terminal device does not send the second HARQ information on the PUSCH; or, the state value of the DAI_UL is the first preset value, the When the payload size of the second HARQ information is 1, the terminal device sends the second HARQ information with a payload size of 1 on the PUSCH.

With reference to the first aspect, in some implementation manners of the first aspect, the sending the HARQ information and/or the second HARQ information on the PUSCH includes: the state value of the DAI_UL is a second preset value, The terminal device sends the first HARQ information and/or the second HARQ information on the PUSCH according to a semi-static codebook rule.

It should be understood that the above-mentioned first preset value and second preset value can be any integer greater than or equal to 0, but the first preset value and the second preset value should be different values.

With reference to the first aspect, in some implementation manners of the first aspect, before the terminal device detects the first DCI in the physical downlink control channel PDCCH, the method further includes: the terminal device receives the DCI from the network device Indication information, the indication information is used to indicate the multiplexing of uplink control information (uplink control information, UCI) of two different priorities and the feedback type of the HARQ information is a semi-static codebook.

In a second aspect, another method for indicating feedback information is provided. The method includes: a terminal device detects first downlink control information DCI in a physical downlink control channel PDCCH, and the first DCI is used to schedule bearers in the first priority The downlink data transmission of the PDSCH of the second priority and/or for scheduling the downlink data transmission carried on the PDSCH of the second priority, the second priority is higher than the first priority; the terminal device receives from the The second DCI of the network device, the second DCI is used to schedule the physical uplink shared channel PUSCH of the second priority, the second DCI includes downlink allocation indication information DAI_UL; the terminal device according to the first DCI and the DAI_UL, sending the first hybrid automatic repeat transmission HARQ information and/or the second HARQ information on the PUSCH, the priority of the second HARQ information is higher than the priority of the first HARQ information ; Wherein, the value of the DAI_UL is a third preset value, and when the load size of the first HARQ information is 0, the PUSCH includes the first HARQ information with a load size of the third preset value .

In the embodiment of the present application, the terminal device sends dynamic first HARQ information and/or second HARQ information to the network device according to the detection of the first DCI and the value of DCI_UL in the second DCI, effectively avoiding that the value of DCI_UL When it is the third preset value, the terminal device sends HARQ information with an incorrect payload size to the network device due to missing detection of the first DCI used to schedule downlink data transmission carried on the PDSCH with the second priority. The method helps to improve the reliability of the fed back HARQ information and the reliability of the second priority uplink data transmission by redefining the rules of the DCI_UL value and the load size of the HARQ information.

It should be understood that the above third preset value may be 4 or other integers greater than or equal to 0, which is not limited in the present application.

With reference to the second aspect, in some implementation manners of the second aspect, the sending the first HARQ information and/or the second HARQ information on the PUSCH includes: the value of the DAI_UL is a third preset value, When the payload size of the second HARQ information is 0, the terminal device does not send the second HARQ information on the PUSCH; or, the value of the DAI_UL is a third preset value, and the second HARQ When the payload size of the information is 0, the terminal device sends the second HARQ information with a payload size of the third preset value on the PUSCH.

With reference to the second aspect, in some implementation manners of the second aspect, before the terminal device detects the first DCI in the physical downlink control channel PDCCH, the method further includes: the terminal device receives the DCI from the network device The indication information is used to indicate the multiplexing of uplink control information UCI of two different priorities and the feedback type of the HARQ information is a dynamic codebook.

To sum up, in the embodiment of the present application, by specifying the determination rules of the load size of the HARQ information fed back by the terminal equipment, the terminal equipment no longer depends on whether it can accurately receive the downlink data used for scheduling and carrying on the PDSCH of the second priority. The first DCI transmitted (i.e. low-priority DCI) is used to determine the payload size of the HARQ information that needs to be fed back, which ensures that the payload size of the HARQ information no longer has the problem of ambiguous payload size, and further ensures that the HARQ information is in the second priority. When the PUSCH is transmitted, the reliability of the uplink data transmission is the second priority.

In the third aspect, there is provided another method for indicating feedback information, the method includes: the network device sends the first downlink control information DCI to the terminal device on the physical downlink control channel PDCCH, and the first DCI is used for scheduling bearers in Downlink data transmission on the PDSCH of the first priority and/or for scheduling downlink data transmission carried on the PDSCH of the second priority, where the second priority is higher than the first priority; the network device Sending a second DCI to the terminal device, the second DCI is used to schedule the physical uplink shared channel PUSCH of the second priority, the second DCI includes downlink allocation indication information DAI_UL; the network device in the The first HARQ information and/or the second HARQ information from the terminal device are received on the PUSCH, and the priority of the second HARQ information is higher than the priority of the first HARQ information; wherein, the state of the DAI_UL is set to The value is a first preset value, and when the payload size of the first HARQ information is 1, the first HARQ information is not included on the PUSCH; or, the state of the DAI_UL is a first preset value, When the payload size of the first HARQ information is 0, the PUSCH includes the first HARQ information with a fixed payload size, and the fixed payload is determined according to a predefined rule.

With reference to the third aspect, in some implementation manners of the third aspect, the network device receives the first HARQ information and/or the second HARQ information from the terminal device on the PUSCH, including: the DAI_UL The state value is a first preset value, and when the payload size of the second HARQ information is 1, the network device receives the second HARQ information with a payload size of 1 on the PUSCH.

With reference to the third aspect, in some implementation manners of the third aspect, the network device receives the first HARQ information and/or the second HARQ information from the terminal device on the PUSCH, including: the DAI_UL The state value is a second preset value, and the network device receives the first HARQ information and the second HARQ information on the PUSCH according to a semi-static codebook rule.

With reference to the third aspect, in some implementation manners of the third aspect, before the network device sends the first downlink control information DCI to the terminal device on a physical downlink control channel PDCCH, the method further includes: the network device Sending indication information to the terminal device, where the indication information is used to indicate the multiplexing of uplink control information UCI of two different priorities and the feedback type of the HARQ information is a semi-static codebook.

In the fourth aspect, there is provided another method for indicating feedback information, the method includes: the network device sends the first downlink control information DCI to the terminal device on the physical downlink control channel PDCCH, and the first DCI is used for scheduling bearers in Downlink data transmission on the PDSCH of the first priority and/or for scheduling downlink data transmission carried on the PDSCH of the second priority, where the second priority is higher than the first priority; the network device Sending a second DCI to the terminal device, the second DCI is used to schedule the physical uplink shared channel PUSCH of the second priority, the second DCI includes downlink allocation indication information DAI_UL; the network device in the The first HARQ information and/or the second HARQ information from the terminal device are received on the PUSCH, and the priority of the second HARQ information is higher than the priority of the first HARQ information; wherein, the value of the DAI_UL is A third preset value, when the payload size of the first HARQ information is 0, the PUSCH includes the first HARQ information with a payload size of the third preset value.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, the network device receives the first HARQ information and/or the second HARQ information from the terminal device on the PUSCH, including: the DAI_UL value is a third preset value, and when the payload size of the second HARQ information is 0, the network device receives the second HARQ information with a payload size of the third preset value.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, before the network device sends the first downlink control information DCI to the terminal device on a physical downlink control channel PDCCH, the method further includes: the network device Sending indication information to the terminal device, where the indication information is used to indicate the multiplexing of uplink control information UCI of two different priorities and the feedback type of the HARQ information is a dynamic codebook.

In a fifth aspect, a communication device is provided, configured to execute the method in any possible implementation manner of the foregoing first aspect. Specifically, the communication device includes a module configured to execute the method in any possible implementation manner of the foregoing first aspect.

In a sixth aspect, another communication device is provided, configured to execute the method in any possible implementation manner of the second aspect above. Specifically, the communication device includes a module configured to execute the method in any possible implementation manner of the second aspect above.

In a seventh aspect, there is provided still another communication device, configured to execute the method in any possible implementation manner of the foregoing third aspect. Specifically, the communication device includes a module configured to execute the method in any possible implementation manner of the foregoing third aspect.

In an eighth aspect, there is provided another communication device, configured to execute the method in any possible implementation manner of the foregoing fourth aspect. Specifically, the communication device includes a module configured to execute the method in any possible implementation manner of the foregoing fourth aspect.

In one design, the communication devices provided in the fifth aspect to the eighth aspect may include modules corresponding to one-to-one execution of the methods/operations/steps/actions described in the above aspects. The modules may be hardware circuits or Software can also be realized by combining hardware circuits with software.

In another design, the above-mentioned communication device is a communication chip, and the communication chip may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

In another design, the communication described above is a communication device, and the communication device may include a transmitter for sending information or data, and a receiver for receiving information or data.

In a ninth aspect, a processor is provided, including: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method in any possible implementation manner of the first aspect above.

In a specific implementation process, the above-mentioned processor can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, a gate circuit, a flip-flop, and various logic circuits. The input signal received by the input circuit may be received and input by, for example but not limited to, the receiver, the output signal of the output circuit may be, for example but not limited to, output to the transmitter and transmitted by the transmitter, and the input circuit and the output The circuit may be the same circuit, which is used as an input circuit and an output circuit respectively at different times. The embodiment of the present application does not limit the specific implementation manners of the processor and various circuits.

In a tenth aspect, a communication device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the device executes the method in any possible implementation manner of any of the above aspects.

Optionally, there are one or more processors, and one or more memories.

Optionally, the memory may be integrated with the processor, or the memory may be separated from the processor.

In the specific implementation process, the memory can be a non-transitory (non-transitory) memory, such as a read-only memory (read only memory, ROM), which can be integrated with the processor on the same chip, or can be respectively arranged in different On the chip, the embodiment of the present application does not limit the type of the memory and the configuration of the memory and the processor.

The communication device in the tenth aspect above can be a chip, and the processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software When implemented, the processor may be a general-purpose processor, which is realized by reading the software code stored in the memory, and the memory may be integrated in the processor, or it may be located outside the processor and exist independently.

In an eleventh aspect, a computer program product is provided, and the computer program product includes: a computer program (also referred to as code, or instruction), which, when the computer program is run, causes the computer to perform any one of the above-mentioned aspects. method in the implementation.

In a twelfth aspect, a computer-readable storage medium is provided, and the computer-readable storage medium stores a computer program (also referred to as code, or an instruction) which, when run on a computer, causes the computer to perform any of the above-mentioned aspects A method in any of the possible implementations.

In a thirteenth aspect, there is provided a system-on-a-chip, which includes a processor, configured to implement the method involved in the above-mentioned first aspect or any possible implementation of the first aspect, or to implement any of the above-mentioned aspects The method involved in any of the possible implementations.

In a possible design, the system-on-a-chip further includes a memory for storing program instructions. The system-on-a-chip may consist of chips, or may include chips and other discrete devices.

In a fourteenth aspect, a communication system is provided, including a device for realizing the above-mentioned first aspect or any possible implementation method of the first aspect, and a device for realizing the above-mentioned third aspect or any of the third aspects or a device for realizing any possible method of the second aspect or the second aspect above, and any possible method for realizing the fourth aspect or the fourth aspect above A means of implementing the method.

Description of drawings

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

FIG. 2 is a schematic diagram of a feedback method of HARQ information;

FIG. 3 is a schematic diagram of a feedback mode of a semi-static codebook;

FIG. 4 is a schematic diagram of a feedback method of a dynamic codebook;

Fig. 5 is a schematic flowchart of a method for indicating feedback information provided by an embodiment of the present application;

Fig. 6 is a schematic block diagram of a communication device provided by an embodiment of the present application;

Fig. 7 is a schematic block diagram of another communication device provided by an embodiment of the present application.

Detailed ways

The technical solution in this application will be described below with reference to the accompanying drawings.

The technical solution provided by this application can be applied to various communication systems, such as: long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) system, universal mobile telecommunications system (UMTS), fifth generation (5th generation, 5G) mobile communication system, new radio (new radio, NR) system or other evolved communication systems, and 5G communication systems next-generation mobile communication systems, etc.

In order to facilitate understanding of the embodiment of the present application, a communication system applicable to the embodiment of the present application is first introduced in detail with reference to FIG. 1 .

FIG. 1 is a schematic diagram of a communication system 100 provided by an embodiment of the present application. As shown in FIG. 1 , the communication system 100 includes at least two communication devices, for example, a network device 110 and at least one terminal device 120 , where data communication can be performed between the network device 110 and at least one terminal device 120 through a wireless connection. Specifically, the network device 110 may send downlink data to the terminal device 120 ; the terminal device 120 may also send uplink data to the network device 110 .

The terminal equipment in the embodiment of the present application may also be referred to as: user equipment (user equipment, UE), mobile station (mobile station, MS), mobile terminal (mobile terminal, MT), access terminal, subscriber unit, subscriber station, Mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

A terminal device may be a device that provides voice/data connectivity to users, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like. At present, examples of some terminal devices include: mobile phone, tablet computer, notebook computer, palmtop computer, mobile internet device (mobile internet device, MID), wearable device, virtual reality (virtual reality, VR) device, enhanced Augmented reality (AR) equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, smart grid Wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, session initiation protocols protocol, SIP) telephone, wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, Vehicle-mounted devices, wearable devices, terminal devices in a 5G network, or terminal devices in a future evolving public land mobile network (PLMN), etc., are not limited in this application.

As an example but not a limitation, in this application, the terminal device may be a terminal device in an Internet of Things (Internet of Things, IoT) system. The Internet of Things is an important part of the development of information technology in the future. Its main technical feature is to connect objects to the network through communication technology, so as to realize the intelligent network of man-machine interconnection and object interconnection. Exemplarily, the terminal device in this embodiment of the present application may be a wearable device. Wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that can be worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also can achieve powerful functions through software support, data interaction, and cloud interaction. Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smart phones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.

As an example but not a limitation, in this embodiment of the present application, the terminal device may also be a terminal device in machine type communication (machine type communication, MTC). In addition, the terminal device can also be an on-board module, on-board module, on-board component, on-board chip, or on-board unit built into the vehicle as one or more components or units. The on-board component, on-board chip, or on-board unit can implement the method provided in this application. Therefore, the embodiments of the present application can also be applied to the Internet of Vehicles, such as vehicle to everything (V2X), vehicle-to-vehicle communication long-term evolution technology (long term evolution-vehicle, LTE-V), vehicle-to-vehicle (vehicle-to-vehicle vehicle, V2V) technology, etc.

The network device involved in this application may be a device that communicates with a terminal device. The network device may also be called an access network device or a wireless access network device. It may be a transmission reception point (transmission reception point, TRP), or a The evolved base station (evolved NodeB, eNB or eNodeB) in the LTE system can also be a home base station (for example, home evolved NodeB, or home Node B, HNB), a base band unit (base band unit, BBU), or a cloud A wireless controller in a wireless access network (cloud radio access network, CRAN) scenario, or the network device can be a relay station, an access point, a vehicle device, a wearable device, and a network device in a 5G network or a future evolved PLMN network The network equipment in the WLAN can also be the access point (access point, AP) in the WLAN, or the gNB in the NR system. The above-mentioned network equipment can also be a city base station, a micro base station, a pico base station, a femto base station, etc. etc., this application does not limit it.

In a network structure, the network device may include a centralized unit (centralized unit, CU) node, or a distributed unit (distributed unit, DU) node, or a wireless access network (radio access network, including a CU node and a DU node, RAN) device, or a RAN device including a control plane CU node (CU-CP node), a user plane CU node (CU-UP node) and a DU node.

The network device provides services for the cell, and the terminal device communicates with the cell through the transmission resources (for example, frequency domain resources, or spectrum resources) allocated by the network device. The cell may belong to a macro base station (for example, a macro eNB or a macro gNB, etc.) , can also belong to the base station corresponding to a small cell, where the small cell can include: a metro cell, a micro cell, a pico cell, a femto cell, etc. , these small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

It should be understood that FIG. 1 is only a simplified schematic diagram for easy understanding, and the communication system 100 may further include other devices, which are not shown in FIG. 1 .

For example, compared with previous generations of mobile communication systems, the 5G communication system has higher requirements in terms of transmission rate, delay, and power consumption. The International Telecommunication Union (ITU) will enhance mobile broadband (enhanced m, mobile broadband, eMBB), massive machine type communication (massive machine type communication, mMTC) and ultra-reliable and low-latency communication (ultra-reliable and low- latency communication (URLLC) is defined as the three typical services of 5G in the future, which points out the direction for the formulation of 5G standards.

URLLC is one of the three typical services of 5G. Its main application scenarios include: driverless driving, telemedicine, etc. These application scenarios put forward stricter requirements in terms of reliability and delay. Requirements for the URLLC service include: data transmission reliability of 99.999%, transmission delay less than 1 millisecond (ms), and instruction overhead reduced as much as possible while meeting high reliability and low delay requirements.

Hybrid automatic repeat request (HARQ) is an efficient transmission mechanism. On the one hand, the reliability of downlink data transmission can be greatly improved through retransmission. On the other hand, the terminal device indicates whether it has received downlink data by feeding back an ACK or NACK message. When the network device receives the NACK feedback message, it needs to retransmit, thereby reducing the overall resource consumption of data transmission.

In the version (Release, R) 16 protocol, the URLLC service is defined as a high-priority service, and the eMBB service is defined as a low-priority service. At the same time, it also stipulates that when a time domain conflict occurs between high and low priority service transmission, the low priority service will be discarded to ensure that the high priority service will not be affected.

R17 proposes that when time-domain conflicts occur between services of different priorities, multiplexing in specific scenarios should be considered. For example, high-priority HARQ information and low-priority HARQ information can be multiplexed. At the 3GPP RAN1#105 meeting, it was discussed how to solve the problem of terminal equipment missing low-priority downlink control information (DCI) when high-priority HARQ information and low-priority HARQ information are multiplexed. question. This is because the high-priority HARQ information is multiplexed with the low-priority HARQ information, and when transmitted on the high-priority PUSCH, the payload size of the low-priority HARQ information will affect the decoding of the high-priority data.

At present, when the terminal equipment feeds back the HARQ information, it needs to perform the feedback on the uplink time slot. That is, multiple HARQ information are fed back together on the same uplink time slot. The terminal device can simultaneously feed back whether the data sent by the network device through multiple semi-persistent scheduling (semi-persistent scheduling, SPS) or DCI scheduling is received correctly. Therefore, it is necessary to define a combination and ordering manner of multiple HARQ information fed back together. In this application, the combined HARQ information is referred to as a HARQ codebook.

Fig. 2 shows a feedback mode of HARQ information. As shown in Figure 2, it includes three downlink (down, D) time slots (time slot n to time slot n+1) and one uplink (up, U) time slot (time slot n+3), in each downlink The time slot includes two physical downlink shared channels (physical downlink shared channel, PDSCH), and the downlink data on each PDSCH has corresponding HARQ information. Each uplink time slot includes two physical uplink control channels (physical uplink control channel, PUCCH), and each PUCCH corresponds to three HARQ information, that is, in the last uplink time slot shown in Figure 3, the feedback Two HARQ codebooks respectively use two resources of PUCCH1 and PUCCH2. Wherein, the HARQ codebook carried in PUCCH1 includes the feedback of HARQ information corresponding to the downlink data of PDSCH1-PDSCH3, and the HARQ codebook carried in PUCCH2 includes the feedback of HARQ information of PDSCH4-PDSCH6. Which corresponding PDSCHs are included in the HARQ codebook is determined by a set of pre-configured downlink time units (that is, a set of K values in FIG. 2 ). For example, K=6, indicating that the HARQ information corresponding to the data carried on the current channel is sent in the sixth time unit after the current channel.

It should be understood that the above time unit may be a time slot or a sub-slot.

The above-mentioned HARQ codebook can be divided into two types: a semi-static codebook and a dynamic codebook. It should be understood that the type of the HARQ codebook can be configured to the current cell through high-layer signaling. For example, the high layer signaling may be radio resource control (radio resource control, RRC).

The semi-static codebook and the dynamic codebook will be described in detail below with reference to FIG. 3 and FIG. 4 .

The semi-static codebook means that in the current time slot, all HARQ information that may be transmitted in the current time slot is fed back. This information includes not only the HARQ information corresponding to the downlink data sent through the PDSCH (feedback its real ACK or NACK), but also includes the HARQ information that there is a PDSCH transmission opportunity but no data is actually transmitted on the PDSCH (feedback NACK). Finally, the HARQ information in the above two cases can be sorted according to the rules shown in FIG. 2 to form a HARQ codebook.

Fig. 3 shows the feedback mode of the semi-static codebook. As shown in Figure 3, each carrier bears four time slots, where the white position indicates that there is PDSCH transmission, and the shaded position indicates that there is no PDSCH transmission. According to the above semi-static codebook rules, there are actually 8 HARQ codebooks that need to be fed back. bit. Specifically, the arrangement sequence is shown in 3. The N in the shaded position indicates that the NACK corresponding to the PDSCH is not transmitted, and the A/N in the blank position indicates that the real ACK or NACK corresponding to the PDSCH is transmitted.

The dynamic codebook means that in the current time slot, only the HARQ information corresponding to the sent PDSCH is fed back.

Fig. 4 shows the feedback mode of the dynamic codebook. As shown in Figure 4, each carrier bears four time slots, the white position indicates that there is PDSCH transmission, the position shaded by the slash indicates that there is no PDSCH transmission, and the position shaded by the grid indicates that the network device has sent a DCI and scheduled this time slot The PDSCH is transmitted, but the terminal device does not receive the DCI, therefore, the terminal device does not know that the PDSCH is transmitted at this position, that is, there will be no corresponding HARQ information.

In the existing embodiment, in view of the above-mentioned situation where the terminal device misses DCI detection, when the network device schedules the PDSCH, it will add a count downlink assignment index (counter downlink assignment index, C-DAI) and a total downlink assignment index (C-DAI) to the DCI. Assignment index (total downlink assignment index, T-DAI). Wherein, the C-DAI is used to indicate which DCI the current DCI is in the HARQ codebook, and the T-DAI is used to indicate how many DCIs have been sent in total up to the current time slot. As shown in Figure 4, the two numbers in each position represent the value of (C-DAI, T-DAI). When the terminal device misses the DCI corresponding to the grid shadow position, the received 4 DCIs respectively indicate (1, 1), (2, 3), (4, 5), and (5, 5). The terminal device can determine that the second DCI is missed according to the four values 1, 2, 4, and 5 of C-DAI; or the terminal device can determine that it should still There is a DCI indicating (3,3). Based on the above two methods, the terminal device can complete the HARQ information (NACK) at this position when feeding back the HARQ codebook.

Exemplarily, the above-mentioned C-DAI and T-DAI respectively occupy 2 bits in the DCI. Since 2 bits can only represent 4 values, in some embodiments, modulo 4 processing is adopted, that is, 00, 01, 10, 11 loop count. And the value of DAI is stipulated in the existing agreement: 00, 01, 10, 11, the corresponding actual values are 1, 2, 3, 4 respectively. For example, the binary representation of the above (2, 3) is (01, 10).

It should be understood that the above HARQ information is generally fed back on the PUCCH, and may also be fed back on the PUSCH. When feedback is performed on the PUSCH, there will be a DAI value in the UL grant for scheduling the PUSCH, which is recorded as the downlink allocation indication DAI_UL.

In some embodiments, for the semi-static codebook, the values of DAI_UL are only 0 and 1, which are used to indicate whether to send the HARQ codebook on the PUSCH. Among them, DAI_UL=1 means that the HARQ codebook is sent according to the rules shown in Figure 2; when DAI_UL=0, there are two situations, one is that the terminal device determines that the HARQ information that needs to be fed back is 1 bit according to the received downlink data, then the terminal device Instead of sending a complete codebook in the manner shown in FIG. 3 , only 1-bit HARQ information is sent. The other is that the terminal device determines that the HARQ information to be fed back is not 1 bit according to the received downlink data, and does not send the HARQ information.

In some embodiments, for a dynamic codebook, the value of DAI_UL indicates the payload size of the codebook fed back on PUSCH. The existing protocol stipulates that the value of DAI_UL is set to 4, and the terminal device determines that the HARQ information that needs to be fed back is 0 bit according to the received downlink data, and then does not send the HARQ information; or, the terminal device determines the HARQ information that needs to be fed back according to the received downlink data. If the information is greater than 0bit and less than or equal to 4bit, 4bit HARQ information is sent; or, the terminal device determines that the HARQ information to be fed back is greater than 4bit according to the received downlink data, then sends N*4bit HARQ information, where N is an integer greater than 1.

At present, the transmission reliability of control information and data information for high-priority services such as URLLC is relatively high, that is, the block error rate is required to reach 1e-5, while the transmission of control information and data information for low-priority services such as eMBB is reliable. The performance requirement is low, that is, the block error rate can be 1e-1 or 1e-2. In this way, in the scenario of mixed transmission of high and low priorities, the error probability of control information and data information of low priority is much greater than that of control information and data information of high priority. Therefore, in the high-priority multiplexing scenario, it is necessary to pay attention to whether the transmission error of low-priority control information or data information will affect the high-priority information.

Obviously, when a transmission error occurs in the above-mentioned low-priority control information or data information, it is likely to affect the high-priority information. Exemplarily, the DCI of low priority is wrong, or the terminal device does not receive the DCI of low priority, which will cause the terminal device to miss the HARQ information to be fed back, thus causing the payload size of the low priority HARQ codebook (payload size )mistake. According to the existing rules, when the high-priority HARQ codebook and the low-priority HARQ codebook are multiplexed on the high-priority PUSCH at the same time, the high-priority HARQ information will be mapped on the PUSCH first, and the high-priority After the end symbol of the HARQ information, continue to map the low-priority HARQ information, and continue to map the high-priority data after the end symbol of the low-priority HARQ information. Therefore, in the case of the above-mentioned payload size error in the HARQ information, the subsequent mapping will be misplaced to a large extent, so that the subsequent mapping data cannot be successfully decoded on the network device side.

For example, in the scenario where high priority and low priority are multiplexed on high priority PUSCH, for a semi-static codebook, regardless of whether low priority HARQ information has its own DAI_UL or shares 1 with high priority HARQ information DAI_UL, when DAI_UL=0, whether the terminal device feeds back the low-priority HARQ depends on whether the low-priority DCI is missed.

Exemplarily, in the scenario where high priority and low priority are multiplexed on the high priority PUSCH, for the dynamic codebook, if DAI_UL is used to indicate the payload size of the high priority HARQ and the payload size of the low priority HARQ at the same time, in When the DAI_UL value=4, according to the low-priority DCI sent by the network device, it is determined that the terminal device needs to feed back 1-bit low-priority HARQ information. When the terminal device misses low-priority DCI, do not send low-priority HARQ information: when the terminal device does not miss low-priority DCI, send low-priority HARQ information with a payload size of 4.

To sum up, in the scenario where high and low priorities are multiplexed on the high priority PUSCH, when the terminal device sends control information and uplink data in a rate matching manner, the wrong size of the low priority HARQ information payload will cause subsequent mapped data Unable to decode successfully.

In view of this, the present application provides an indication method and a communication device for feedback information. The network device multiplexes the high-priority UCI and the low-priority UCI on the PUSCH of the same level by configuring signaling, and for the semi-static codebook, the DCI indicates that the value of the DAI_UL of the high-priority HARQ is the second preset value ( For example, DAI_UL=0), the low-priority HARQ information is never sent, or the low-priority HARQ information with a payload size of 1 is always sent. For a dynamic codebook, high-priority HARQ and low-priority HARQ share a DAI_UL, and the value of DAI_UL is the first preset value, and the HARQ information with the payload size of the first preset value is sent, thereby effectively avoiding low-priority When the rate-match of high-level HARQ information is performed, the payload size error of low-priority HARQ information will cause the problem that the subsequent mapped high-priority uplink data cannot be successfully decoded, which is conducive to improving the transmission of high-priority uplink data reliability.

Before introducing the indication method of the feedback information provided by this application, the following points are explained first.

First, in the embodiments shown herein, various terms and English abbreviations, such as HARQ, PDCCH, or PDSCH, are all illustrative examples for convenience of description, and should not constitute any limitation to the present application. This application does not exclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

Second, the first, second and various numbers in the embodiments shown below are only for convenience of description, and are not used to limit the scope of the embodiments of the present application. For example, distinguishing between different DCIs. It should be noted that the embodiments of the present application use ordinal numerals such as "first" and "second" to distinguish multiple objects, and are not used to limit the sequence, timing, priority, or importance of multiple objects. For example, the first DCI, the second DCI, etc. are only for distinguishing different priorities, and do not mean that the two DCIs are different in importance.

Third, the "protocol" involved in this embodiment of the application may refer to a standard protocol in the communication field, for example, it may include LTE protocol, NR protocol and related protocols applied in future communication systems, which is not limited in this application.

Fourth, "plurality" means two or more. "And/or" describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the contextual objects are an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (one) of a, b and c may represent: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, wherein a, b, c can be single or multiple.

The method for indicating the feedback information provided by the embodiment of the present application will be described in detail below with reference to FIG. 5 . It should be understood that the method may be applied to the communication system 100 shown in FIG. 1 , but this embodiment of the present application is not limited thereto.

FIG. 5 shows a method 500 for indicating feedback information provided by an embodiment of the present application. As shown in FIG. 5, the method 500 may include the following steps:

S501. The network device sends indication information to the terminal device, where the indication information is used to indicate multiplexing of uplink control information (uplink control information, UCI) of two different priorities and a feedback type of HARQ information. Correspondingly, the terminal device receives the indication information.

The above indication information may be carried in radio resource control (radio resource control, RRC) signaling or other high-level signaling, which is not limited in this application.

The feedback types of the above HARQ information include: a semi-static codebook and a dynamic codebook.

The HARQ information in this embodiment of the present application includes ACK information and/or NACK information.

S502. The network device sends the first DCI to the terminal device on the PDCCH, where the first DCI is used for scheduling downlink data transmission carried on the PDSCH of the first priority and/or used for scheduling the transmission of the downlink data carried on the PDSCH of the second priority downlink data transmission, and the second priority is higher than the first priority. Correspondingly, the terminal device detects the first DCI from the network device in the PDCCH.

S503. The network device sends a second DCI to the terminal device, where the second DCI is used to schedule a PUSCH with a second priority, where the second DCI includes downlink allocation indication information DAI_UL. Correspondingly, the terminal device receives the second DCI.

It should be understood that the above-mentioned second DCI may include one DAI_UL, or may include two DAI_ULs at the same time, which itself is not limited.

S504. The terminal device sends the first HARQ information and/or the second HARQ information on the PUSCH according to the detection of the first DCI and the DAI_UL, where the priority of the second HARQ information is higher than that of the first HARQ information. Correspondingly, the network device receives the first HARQ information and/or the second HARQ information on the PUSCH.

It should be understood that each first DCI sent by the above network device may have corresponding HARQ information with a payload size of 1. Wherein, the first DCI for scheduling downlink data transmission carried on the PDSCH of the first priority corresponds to the first HARQ information, and is used for scheduling the first DCI of the downlink data transmission carried on the PDSCH of the second priority , corresponding to the above second HARQ information.

In this embodiment of the present application, the first priority may be called low priority, and the second priority may be called high priority. Exemplarily, the above-mentioned first priority PDSCH may be called a low priority PDSCH, the first HARQ information may be called a low priority HARQ information, and the second priority PDSCH may be called a high priority PDSCH. The second HARQ information may be referred to as high-priority HARQ information.

Further, when the above indication information indicates that the feedback type of the HARQ information is a semi-static codebook, the terminal device sends the first HARQ information and/or the second HARQ information on the PUSCH according to the detection situation of the first DCI and the above DAI_UL, and may Including the following four situations:

Case 1, the above-mentioned DAI_UL state value is the first preset value, and the load size of the first HARQ information is 1 (that is, the above-mentioned terminal device detects in the PDCCH that it is used to schedule and carry on the PDSCH with the first priority. During the first DCI) of downlink data transmission, the terminal device does not send the first HARQ information on the PUSCH.

In the second case, the above-mentioned DAI_UL state value is the first preset value, and the load size of the first HARQ information is 0 (that is, the above-mentioned terminal device has not detected in the PDCCH that it is used to schedule the downlink carried on the PDSCH with the first priority. During the first DCI of data transmission), the terminal device sends the first HARQ information with a fixed payload size on the PUSCH, and the fixed payload is determined according to a predefined rule. Correspondingly, the network device receives the first HARQ information with the fixed payload size.

It should be understood that the above DAI_UL state value is a first preset value, and when the payload size of the first HARQ information is not 0 or 1, the terminal device does not send the first HARQ information on the PUSCH.

In the third case, the above-mentioned DAI_UL state value is the first preset value, and the load size of the second HARQ information is 1 (that is, the above-mentioned terminal device detects in the PDCCH that it is used to schedule and bear on the PDSCH of the second priority. During the first DCI of downlink data transmission), the terminal device does not send the second HARQ information on the PUSCH, or the terminal device sends the second HARQ information with a payload size of 1 on the PUSCH. Correspondingly, the network device receives the second HARQ information with a payload size of 1.

It should be understood that, under the condition of the third case above, which of the two transmission modes is adopted by the terminal device may be determined by RRC signaling, other signaling or a predefined manner.

It should also be understood that the above DAI_UL state value is the first preset value, and when the payload size of the second HARQ information is not 1, the terminal device does not send the second HARQ information on the PUSCH.

Situation 4, when the above DAI_UL state value is the second preset value, the terminal device sends the first HARQ information and/or the second HARQ information on the PUSCH according to the semi-static codebook rule. Correspondingly, the network device receives the first HARQ information and/or the second HARQ information.

For the sending rules of the above-mentioned semi-static codebook, reference may be made to the relevant description in FIG. 3 above, and details are not repeated here.

It should be understood that when the indication information indicates that the feedback type of the HARQ information is a semi-static codebook, the second DCI may include one DAI_UL, or may include two DAI_ULs at the same time.

Further, when the above indication information indicates that the feedback type of the HARQ information is a dynamic codebook, the terminal device sends the first HARQ information and/or the second HARQ information on the PUSCH according to the detection of the above first DCI and the above DAI_UL, including the following Two situations:

Case 1, the value of the DAI_UL above is the third preset value, and the payload size of the first HARQ information is 0 (that is, the terminal device has not detected in the PDCCH that the downlink data transmission used to schedule the PDSCH carried on the first priority PDSCH When the first DCI), the terminal device sends the first HARQ information with a payload size of a third preset value on the PUSCH. Correspondingly, the network device receives the first HARQ information.

It should be understood that the above DAI_UL value is a third preset value, and when the payload size of the first HARQ information is not 0, the terminal device sends the first HARQ information with a payload size of N×the third preset value on the PUSCH, where N is An integer greater than 0.

Exemplarily, the above DAI_UL value is 4, and the payload size of the first HARQ information is X (X is an integer greater than 4 and less than 9), then the terminal device sends the first HARQ information with a payload size of 8 on the PUSCH.

Exemplarily, the above DAI_UL value is 4, and the payload size of the first HARQ information is Y (Y is an integer greater than 8 and less than 17), then the terminal device sends the first HARQ information with a payload size of 16 on the PUSCH.

Case 2, the value of the DAI_UL above is the third preset value, and the load size of the second HARQ information is 0 (that is, the terminal device has not detected in the PDCCH that the downlink data transmission used to schedule the PDSCH carried on the second priority PDSCH When the first DCI), the terminal device does not send the second HARQ information on the PUSCH, or the terminal device sends the second HARQ information with a payload size of a third preset value on the PUSCH. Correspondingly, the network device receives the second HARQ information whose payload size is the third preset value.

It should be understood that the value of the above DAI_UL is a third preset value, and when the payload size of the second HARQ information is not 0, the terminal device sends the second HARQ information with a payload size of N×the third preset value on the PUSCH.

It should also be understood that, under the condition of the second case above, which of the two transmission modes is adopted by the terminal device may be determined by RRC signaling, other signaling or a predefined manner.

It should be understood that when the indication information indicates that the feedback type of the HARQ information is a dynamic codebook, the second DCI includes one DAI_UL.

It should be understood that the above-mentioned first preset value, second preset value and third preset value may be arbitrary values, and the first preset value and the second preset value should be set to different values.

To sum up, in the embodiment of the present application, by specifying the determination rules of the load size of the HARQ information fed back by the terminal equipment, the terminal equipment no longer depends on whether it can accurately receive the downlink data used for scheduling and carrying on the PDSCH of the second priority. The first DCI transmitted (i.e. low-priority DCI) is used to determine the payload size of the HARQ information that needs to be fed back, which ensures that the payload size of the HARQ information no longer has the problem of ambiguous payload size, and further ensures that the HARQ information is in the second priority. When the PUSCH is transmitted, the reliability of the uplink data transmission is the second priority.

Exemplarily, the above-mentioned first preset value is 0, and the second preset value is 1. When the indication information indicates that the feedback type of the HARQ information is a semi-static codebook, the second DCI includes one DAI_UL for both the first HARQ information and the second HARQ information; or, the second DCI includes two DAI_ULs for the first HARQ information and second HARQ information. Regardless of whether the above-mentioned second DCI includes one DAI_UL or two DAI_ULs, the value of DAI_UL will always be 0. In this case, the terminal device also needs to determine the load size of the HARQ information sent to the network device according to the detected first DCI (for scheduling downlink data transmission carried on the PDSCH with the second priority), That is, upon detection of one first DCI (used to schedule downlink data transmission carried on the PDSCH of the second priority), the terminal device sends the first HARQ information with a payload size of one. If no first DCI (used to schedule downlink data transmission carried on the PDSCH with the second priority) is detected, the terminal device sends or not to send the first HARQ information. If the terminal device fails to detect the first DCI, it may cause an error in the payload size of the first HARQ information fed back. Therefore, in the embodiment of the present application, DAI_UL=0 is defined, and the terminal device sends the first HARQ information with a payload size of 0 or a fixed payload size, thereby effectively avoiding the load of the first HARQ information fed back due to the missed detection of DCI by the terminal device. An error occurs in the size, which affects the successful decoding of the second priority uplink data.

Exemplarily, the above-mentioned third preset value is 4. When the indication information indicates that the feedback type of the HARQ information is a dynamic type, the second DCI includes one DAI_UL which is used for both the first HARQ information and the second HARQ information. The DAI_UL may indicate the load size of the second HARQ information so that the first HARQ information matches the indication, or may indicate a larger value of the load in the first HARQ information and the second HARQ information. Therefore, the value of DAI_UL is 4, which is used to indicate the load size of the HARQ information of the second priority, when the terminal device misses a first DCI (used to schedule downlink data transmission carried on the PDSCH of the first priority) , when the network device only sends the first DCI, it also conforms to the instruction of DAI_UL=4 (that is, the first HARQ information is not sent), and when the terminal device maps data on the PUSCH according to the rate matching method, the uplink data that occurs will not be able to Successfully decoded. Therefore, in the embodiment of the present application, DAI_UL=4 is defined. In the case that the terminal device misses all the first DCIs from the network device, the terminal device sends the first HARQ information with a payload size of 4, thereby effectively avoiding Because the terminal equipment misses DCI detection, the load size of the first HARQ information fed back is wrong, which affects the successful decoding of the second priority uplink data.

It should be understood that the sequence numbers of the above processes do not mean the order of execution, and the execution order of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

The method for indicating the feedback information in the embodiment of the present application is described in detail above with reference to FIG. 5 . The communication device in the embodiment of the present application will be described in detail below in conjunction with FIG. 6 and FIG. 7 .

FIG. 6 shows a communication device 600 provided by an embodiment of the present application. As shown in FIG. 6 , the communication device 600 includes: a receiving module 610 and a sending module 620 .

In a possible implementation manner, the communication apparatus 600 is a terminal device, or a chip in the terminal device.

Wherein, in one design, the receiving module 610 is configured to: detect the first DCI in the PDCCH, the first DCI is used to schedule the downlink data transmission carried on the PDSCH with the first priority and/or to schedule the bearer Downlink data transmission on the PDSCH of the second priority, where the second priority is higher than the first priority; and used to receive a second DCI from the network device, the second DCI is used for Scheduling the PUSCH of the second priority, the second DCI includes DAI_UL; a sending module 620, configured to send a first hybrid automatic repeat transmission on the PUSCH according to the detection of the first DCI and the DAI_UL HARQ information and/or second HARQ information, the priority of the second HARQ information is higher than the priority of the first HARQ information; wherein, the state value of the DAI_UL is a first preset value, and the first When the load size of a HARQ information is 1, the PUSCH does not include the first HARQ information; or, the state value of the DAI_UL is a first preset value, and the load size of the first HARQ information is 0 , the PUSCH includes the first HARQ information with a fixed load size, and the fixed load is determined according to a predefined rule.

Optionally, the sending module 620 is further configured to: the state value of the DAI_UL is a first preset value, and when the payload size of the second HARQ information is 1, the second HARQ information is not sent on the PUSCH ; or, the state value of the DAI_UL is a first preset value, and when the payload size of the second HARQ information is 1, the second HARQ information with a payload size of 1 is sent on the PUSCH.

Optionally, the sending module 620 is further configured to: the state value of the DAI_UL is a second preset value, and the first HARQ information and/or the second HARQ information are sent on the PUSCH according to a semi-static codebook rule. HARQ information.

Optionally, the receiving module 610 is further configured to: receive indication information from the network device, the indication information is used to indicate the multiplexing of the uplink control information UCI of two different priorities and the feedback type of the HARQ information is semi-static codebook.

In another design, the receiving module 610 is configured to: detect the first DCI in the PDCCH, the first DCI is used to schedule downlink data Downlink data transmission on PDSCH with two priorities, where the second priority is higher than the first priority; and used to receive a second DCI from the network device, where the second DCI is used to schedule all The PUSCH with the second priority, the second DCI includes DAI_UL; the sending module 620 is configured to: send the first hybrid automatic repeat transmission HARQ information on the PUSCH according to the detection situation of the first DCI and the DAI_UL And/or second HARQ information, the priority of the second HARQ information is higher than the priority of the first HARQ information; wherein, the value of the DAI_UL is a third preset value, and the priority of the first HARQ information When the payload size is 0, the PUSCH includes the first HARQ information with the payload size being the third preset value.

Optionally, the sending module 620 is further configured to: the value of the DAI_UL is a third preset value, and when the payload size of the second HARQ information is 0, the second HARQ information is not sent on the PUSCH; Alternatively, the value of the DAI_UL is a third preset value, and when the payload size of the second HARQ information is 0, the second HARQ information with a payload size of the third preset value is sent on the PUSCH.

Optionally, the receiving module 610 is further configured to: receive indication information from the network device, the indication information is used to indicate the multiplexing of the uplink control information UCI of two different priorities and the feedback type of the HARQ information is dynamic codebook.

In an optional example, those skilled in the art can understand that the communication device 600 may specifically be the terminal device in the above embodiment, and the communication device 600 may be used to execute various procedures corresponding to the terminal device in the above method 500 and/or or steps, in order to avoid repetition, no more details are given here.

In another possible implementation manner, the communications apparatus 600 is a network device, or a chip in the network device.

Wherein, in one design, the sending module 620 is configured to send the first DCI to the terminal device on the PDCCH, and the first DCI is used for scheduling downlink data transmission carried on the PDSCH with the first priority and/or for Scheduling downlink data transmission carried on the PDSCH of the second priority, where the second priority is higher than the first priority; and sending a second DCI to the terminal device, where the second DCI is used for scheduling The PUSCH of the second priority, the second DCI includes downlink allocation indication information DAI_UL; the receiving module 610 is configured to: receive the first HARQ information and/or the second HARQ information from the terminal device on the PUSCH , the priority of the second HARQ information is higher than the priority of the first HARQ information; wherein, the state value of the DAI_UL is a first preset value, and the payload size of the first HARQ information is 1 , the PUSCH does not include the first HARQ information; or, the state value of the DAI_UL is a first preset value, and when the load size of the first HARQ information is 0, the PUSCH includes a fixed load The size of the first HARQ information, the fixed load is determined according to a predefined rule.

Optionally, the receiving module 610 is further configured to: the state value of the DAI_UL is a first preset value, and when the payload size of the second HARQ information is 1, receive all the messages with a payload size of 1 on the PUSCH. The second HARQ information is described.

Optionally, the receiving module 610 is further configured to: the state value of the DAI_UL is a second preset value, and the first HARQ information and the second HARQ information are received on the PUSCH according to a semi-static codebook rule .

Optionally, the sending module 620 is further configured to: send indication information to the terminal device, where the indication information is used to indicate that the multiplexing of uplink control information UCI of two different priorities and the feedback type of the HARQ information are half static codebook.

In another design, the sending module 620 is configured to: send the first DCI to the terminal device on the PDCCH, where the first DCI is used for scheduling downlink data transmission carried on the PDSCH with the first priority and/or for Scheduling downlink data transmission carried on the PDSCH of the second priority, where the second priority is higher than the first priority; and sending a second DCI to the terminal device, where the second DCI is used for scheduling The PUSCH of the second priority, the second DCI includes downlink allocation indication information DAI_UL; the receiving module 610 is configured to: receive the first HARQ information and/or the second HARQ information from the terminal device on the PUSCH , the priority of the second HARQ information is higher than the priority of the first HARQ information; wherein, the value of the DAI_UL is a third preset value, and when the payload size of the first HARQ information is 0, the The PUSCH includes the first HARQ information with a payload size of the third preset value.

Optionally, the receiving module 610 is further configured to: the value of the DAI_UL is a third preset value, and when the payload size of the second HARQ information is 0, the received payload size is the third preset value. Second HARQ information.

Optionally, the sending module 620 is further configured to: send indication information to the terminal device, where the indication information is used to indicate that the multiplexing of uplink control information UCI of two different priorities and the feedback type of the HARQ information are dynamic codebook.

In an optional example, those skilled in the art can understand that the communication device 600 may specifically be the network device in the above embodiment, and the communication device 600 may be used to execute various processes corresponding to the network device in the above method 500 and/or or steps, in order to avoid repetition, no more details are given here.

It should be understood that the communication device 600 here is embodied in the form of functional modules. The term "module" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor, or a group processor, etc.) and memory, incorporated logic, and/or other suitable components to support the described functionality. The communication apparatus 600 may be configured to execute various processes and/or steps corresponding to the terminal device or the network device in the foregoing method embodiments, and details are not repeated here to avoid repetition.

The above-mentioned communication device 600 has the function of realizing the corresponding steps performed by the terminal device or the network device in the above-mentioned method 500; the above-mentioned functions may be realized by hardware, or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions.

In the embodiment of the present application, the communication device 600 in FIG. 6 may also be a chip or a chip system, for example: a system on chip (system on chip, SoC), which is not limited in this application.

FIG. 7 shows another communication device 700 provided by the embodiment of the present application. The communication device 700 includes a processor 710 , a memory 720 and a transceiver 730 . Wherein, the processor 710, the memory 720 and the transceiver 730 are connected through an internal connection path, the memory 720 is used to store instructions, and the processor 710 is used to execute the instructions stored in the memory 720, so that the communication device 700 can execute the above methods. An example provides an indication method 500 of feedback information.

It should be understood that the functions of the communication device 600 in the above embodiments may be integrated into the communication device 700, and the communication device 700 may be used to execute various steps and/or processes corresponding to the terminal device in the above method embodiments, or the communication device 700 may also It can be used to execute various steps and/or processes corresponding to the network device in the foregoing method embodiments. Optionally, the memory 720 may include read-only memory and random-access memory, and provides instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. For example, the memory may also store device type information. The processor 710 may be used to execute instructions stored in the memory, and when the processor executes the instructions, the processor 710 may execute the various steps and/or processes corresponding to the terminal device in the above method embodiments, or the processor 710 may execute various steps and/or processes corresponding to network devices in the foregoing method embodiments.

It should be understood that, in the embodiment of the present application, the processor 710 may be a central processing unit (central processing unit, CPU), and the processor 710 may also be other general-purpose processors, digital signal processors (digital signal process, DSP) , application specific integrated circuit (ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor 710 may be a microprocessor or the processor 710 may be any conventional processor or the like.

During implementation, each step of the foregoing method 500 may be implemented by an integrated logic circuit of hardware in a processor or instructions in the form of software. The steps of the methods disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register. The storage medium is located in the memory, and the processor executes the instructions in the memory to complete the steps of the above method in combination with its hardware. To avoid repetition, no detailed description is given here.

Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

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

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

If the functions are realized in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims (30)

1. A method for indicating feedback information, comprising:

   The terminal device detects the first downlink control information DCI in the physical downlink control channel PDCCH, and the first DCI is used for scheduling downlink data transmission carried on the physical downlink shared channel PDSCH of the first priority and/or for scheduling the bearer Downlink data transmission on a PDSCH of a second priority, where the second priority is higher than the first priority;

   The terminal device receives a second DCI from a network device, the second DCI is used to schedule the physical uplink shared channel PUSCH of the second priority, and the second DCI includes downlink allocation indication information DAI_UL;

   The terminal device sends the first hybrid automatic repeat transmission HARQ information and/or the second HARQ information on the PUSCH according to the detection situation of the first DCI and the DAI_UL, and the priority of the second HARQ information is high Based on the priority of the first HARQ information;

   Wherein, the state value of the DAI_UL is a first preset value, and when the load size of the first HARQ information is 1, the PUSCH does not include the first HARQ information; or, the state value of the DAI_UL is The value is a first preset value, and when the payload size of the first HARQ information is 0, the PUSCH includes the first HARQ information with a fixed payload size, and the fixed payload is determined according to a predefined rule.
2. The method according to claim 1, wherein the sending the first HARQ information and/or the second HARQ information on the PUSCH comprises:

   The state value of the DAI_UL is a first preset value, and when the payload size of the second HARQ information is 1, the terminal device does not send the second HARQ information on the PUSCH; or,

   The state value of the DAI_UL is a first preset value, and when the payload size of the second HARQ information is 1, the terminal device sends the second HARQ information with a payload size of 1 on the PUSCH.
3. The method according to claim 1 or 2, wherein the sending HARQ information and/or second HARQ information on the PUSCH includes:

   The state value of the DAI_UL is a second preset value, and the terminal device sends the first HARQ information and/or the second HARQ information on the PUSCH according to a semi-static codebook rule.
4. The method according to any one of claims 1 to 3, wherein before the terminal device detects the first DCI in the Physical Downlink Control Channel (PDCCH), the method further comprises:

   The terminal device receives indication information from the network device, where the indication information is used to indicate the multiplexing of uplink control information UCI of two different priorities and the feedback type of the HARQ information is a semi-static codebook.
5. A method for indicating feedback information, comprising:

   The terminal device detects the first downlink control information DCI in the physical downlink control channel PDCCH, and the first DCI is used to schedule downlink data transmission carried on the physical downlink shared channel PDSCH with the first priority and/or used to schedule the transmission carried on the physical downlink shared channel PDSCH Downlink data transmission on the PDSCH of the second priority, where the second priority is higher than the first priority;

   The terminal device receives a second DCI from a network device, the second DCI is used to schedule the physical uplink shared channel PUSCH of the second priority, and the second DCI includes downlink allocation indication information DAI_UL;

   The terminal device sends the first hybrid automatic repeat transmission HARQ information and/or the second HARQ information on the PUSCH according to the detection situation of the first DCI and the DAI_UL, and the priority of the second HARQ information is high Based on the priority of the first HARQ information;

   Wherein, the value of the DAI_UL is a third preset value, and when the payload size of the first HARQ information is 0, the PUSCH includes the first HARQ information with a payload size of the third preset value.
6. The method according to claim 5, wherein the sending the first HARQ information and/or the second HARQ information on the PUSCH comprises:

   The value of the DAI_UL is a third preset value, and when the payload size of the second HARQ information is 0, the terminal device does not send the second HARQ information on the PUSCH; or,

   The value of the DAI_UL is a third preset value, and when the payload size of the second HARQ information is 0, the terminal device sends the second HARQ information with a payload size of the third preset value on the PUSCH .
7. The method according to claim 5 or 6, wherein before the terminal device detects the first DCI in the Physical Downlink Control Channel (PDCCH), the method further comprises:

   The terminal device receives indication information from the network device, where the indication information is used to indicate the multiplexing of uplink control information UCI of two different priorities and the feedback type of the HARQ information is a dynamic codebook.
8. A method for indicating feedback information, comprising:

   The network device sends first downlink control information DCI to the terminal device on the physical downlink control channel PDCCH, and the first DCI is used to schedule downlink data transmission carried on the first priority physical downlink shared channel PDSCH and/or use For scheduling downlink data transmission carried on the PDSCH of the second priority, the second priority is higher than the first priority;

   The network device sends a second DCI to the terminal device, the second DCI is used to schedule the physical uplink shared channel PUSCH of the second priority, and the second DCI includes downlink allocation indication information DAI_UL;

   The network device receives first HARQ information and/or second HARQ information from the terminal device on the PUSCH, where the priority of the second HARQ information is higher than the priority of the first HARQ information;

   Wherein, the state value of the DAI_UL is a first preset value, and when the load size of the first HARQ information is 1, the PUSCH does not include the first HARQ information; or, the state value of the DAI_UL is The value is a first preset value, and when the payload size of the first HARQ information is 0, the PUSCH includes the first HARQ information with a fixed payload size, and the fixed payload is determined according to a predefined rule.
9. The method according to claim 8, wherein the network device receives the first HARQ information and/or the second HARQ information from the terminal device on the PUSCH, comprising:

   The state value of the DAI_UL is a first preset value, and when the payload size of the second HARQ information is 1, the network device receives the second HARQ information with a payload size of 1 on the PUSCH.
10. The method according to claim 8 or 9, wherein the network device receives the first HARQ information and/or the second HARQ information from the terminal device on the PUSCH, comprising:

    The state value of the DAI_UL is a second preset value, and the network device receives the first HARQ information and the second HARQ information on the PUSCH according to a semi-static codebook rule.
11. The method according to any one of claims 8 to 10, wherein before the network device sends the first downlink control information DCI to the terminal device on the physical downlink control channel PDCCH, the method further includes:

    The network device sends indication information to the terminal device, where the indication information is used to indicate that the multiplexing of uplink control information UCI of two different priorities and the feedback type of the HARQ information is a semi-static codebook.
12. A method for indicating feedback information, comprising:

    The network device sends first downlink control information DCI to the terminal device on the physical downlink control channel PDCCH, and the first DCI is used to schedule downlink data transmission carried on the first priority physical downlink shared channel PDSCH and/or use For scheduling downlink data transmission carried on the PDSCH of the second priority, the second priority is higher than the first priority;

    The network device sends a second DCI to the terminal device, the second DCI is used to schedule the physical uplink shared channel PUSCH of the second priority, and the second DCI includes downlink allocation indication information DAI_UL;

    The network device receives first HARQ information and/or second HARQ information from the terminal device on the PUSCH, where the priority of the second HARQ information is higher than the priority of the first HARQ information;

    Wherein, the value of the DAI_UL is a third preset value, and when the payload size of the first HARQ information is 0, the PUSCH includes the first HARQ information with a payload size of the third preset value.
13. The method according to claim 12, wherein the network device receives the first HARQ information and/or the second HARQ information from the terminal device on the PUSCH, comprising:

    The value of the DAI_UL is a third preset value, and when the payload size of the second HARQ information is 0, the network device receives the second HARQ information with a payload size of the third preset value.
14. The method according to claim 12 or 13, wherein, before the network device sends the first downlink control information DCI to the terminal device on a physical downlink control channel (PDCCH), the method further comprises:

    The network device sends indication information to the terminal device, where the indication information is used to indicate the multiplexing of uplink control information UCI of two different priorities and the feedback type of the HARQ information is a dynamic codebook.
15. A communication device, characterized by comprising:

    The receiving module is configured to detect the first downlink control information DCI in the physical downlink control channel PDCCH, and the first DCI is used to schedule downlink data transmission carried on the physical downlink shared channel PDSCH of the first priority and/or use For scheduling downlink data transmission carried on the PDSCH of the second priority, the second priority is higher than the first priority; and for receiving the second DCI from the network device, the second DCI uses For scheduling the physical uplink shared channel PUSCH of the second priority, the second DCI includes downlink allocation indication information DAI_UL;

    A sending module, configured to send first hybrid automatic repeat transmission HARQ information and/or second HARQ information on the PUSCH according to the detection of the first DCI and the DAI_UL, and the priority of the second HARQ information higher than the priority of the first HARQ information;

    Wherein, the state value of the DAI_UL is a first preset value, and when the load size of the first HARQ information is 1, the PUSCH does not include the first HARQ information; or, the state value of the DAI_UL is The value is a first preset value, and when the payload size of the first HARQ information is 0, the PUSCH includes the first HARQ information with a fixed payload size, and the fixed payload is determined according to a predefined rule.
16. The device according to claim 15, wherein the sending module is also used for:

    The state value of the DAI_UL is a first preset value, and when the payload size of the second HARQ information is 1, the second HARQ information is not sent on the PUSCH; or,

    The state value of the DAI_UL is a first preset value, and when the payload size of the second HARQ information is 1, the second HARQ information with a payload size of 1 is sent on the PUSCH.
17. The device according to claim 15 or 16, wherein the sending module is also used for:

    The state value of the DAI_UL is a second preset value, and the first HARQ information and/or the second HARQ information are sent on the PUSCH according to a semi-static codebook rule.
18. The device according to any one of claims 15 to 17, wherein the receiving module is also used for:

    Receive indication information from the network device, where the indication information is used to indicate the multiplexing of uplink control information UCI of two different priorities and the feedback type of the HARQ information is a semi-static codebook.
19. A communication device, characterized by comprising:

    The receiving module is configured to detect the first downlink control information DCI in the physical downlink control channel PDCCH, and the first DCI is used to schedule downlink data transmission of the physical downlink shared channel PDSCH carried in the first priority and/or for Scheduling downlink data transmission carried on the PDSCH of the second priority, where the second priority is higher than the first priority; and for receiving a second DCI from the network device, where the second DCI is used for Scheduling the physical uplink shared channel PUSCH of the second priority, the second DCI includes downlink allocation indication information DAI_UL;

    A sending module, configured to send first hybrid automatic repeat transmission HARQ information and/or second HARQ information on the PUSCH according to the detection of the first DCI and the DAI_UL, and the priority of the second HARQ information higher than the priority of the first HARQ information;

    Wherein, the value of the DAI_UL is a third preset value, and when the payload size of the first HARQ information is 0, the PUSCH includes the first HARQ information with a payload size of the third preset value.
20. The device according to claim 19, wherein the sending module is also used for:

    The value of the DAI_UL is a third preset value, and when the payload size of the second HARQ information is 0, the second HARQ information is not sent on the PUSCH; or,

    The value of the DAI_UL is a third preset value, and when the payload size of the second HARQ information is 0, the second HARQ information with a payload size of the third preset value is sent on the PUSCH.
21. The device according to claim 19 or 20, wherein the receiving module is also used for:

    receiving indication information from the network device, where the indication information is used to indicate the multiplexing of uplink control information UCI of two different priorities and the feedback type of the HARQ information is a dynamic codebook.
22. A communication device, characterized by comprising:

    A sending module, configured to send first downlink control information DCI to a terminal device on a physical downlink control channel PDCCH, where the first DCI is used to schedule downlink data transmission and transmission carried on a physical downlink shared channel PDSCH with a first priority /or used to schedule downlink data transmission carried on a PDSCH of a second priority, where the second priority is higher than the first priority; and, sending a second DCI to the terminal device, the second The DCI is used to schedule the physical uplink shared channel PUSCH of the second priority, and the second DCI includes downlink allocation indication information DAI_UL;

    A receiving module, configured to receive first HARQ information and/or second HARQ information from the terminal device on the PUSCH, where the priority of the second HARQ information is higher than the priority of the first HARQ information;

    Wherein, the state value of the DAI_UL is a first preset value, and when the load size of the first HARQ information is 1, the PUSCH does not include the first HARQ information; or, the state value of the DAI_UL is The value is a first preset value, and when the payload size of the first HARQ information is 0, the PUSCH includes the first HARQ information with a fixed payload size, and the fixed payload is determined according to a predefined rule.
23. The device according to claim 22, wherein the receiving module is also used for:

    The state value of the DAI_UL is a first preset value, and when the payload size of the second HARQ information is 1, the second HARQ information with a payload size of 1 is received on the PUSCH.
24. The device according to claim 22 or 23, wherein the receiving module is also used for:

    The state value of the DAI_UL is a second preset value, and the first HARQ information and the second HARQ information are received on the PUSCH according to a semi-static codebook rule.
25. The device according to any one of claims 22 to 24, wherein the sending module is also used for:

    Sending indication information to the terminal device, where the indication information is used to indicate the multiplexing of uplink control information UCI of two different priorities and the feedback type of the HARQ information is a semi-static codebook.
26. A communication device, characterized by comprising:

    A sending module, configured to send first downlink control information DCI to a terminal device on a physical downlink control channel PDCCH, where the first DCI is used to schedule downlink data transmission and transmission carried on a physical downlink shared channel PDSCH with a first priority /or used to schedule downlink data transmission carried on a PDSCH of a second priority, where the second priority is higher than the first priority; and, sending a second DCI to the terminal device, the second The DCI is used to schedule the physical uplink shared channel PUSCH of the second priority, and the second DCI includes downlink allocation indication information DAI_UL;

    A receiving module, configured to receive first HARQ information and/or second HARQ information from the terminal device on the PUSCH, where the priority of the second HARQ information is higher than the priority of the first HARQ information;

    Wherein, the value of the DAI_UL is a third preset value, and when the payload size of the first HARQ information is 0, the PUSCH includes the first HARQ information with a payload size of the third preset value.
27. The device according to claim 26, wherein the receiving module is also used for:

    The value of the DAI_UL is a third preset value, and when the payload size of the second HARQ information is 0, the second HARQ information with a payload size of the third preset value is received.
28. The device according to claim 26 or 27, wherein the sending module is also used for:

    Sending indication information to the terminal device, where the indication information is used to indicate the multiplexing of uplink control information UCI of two different priorities and the feedback type of the HARQ information is a dynamic codebook.
29. A communication system, characterized by comprising the device described in any one of claims 15 to 18 and the device described in any one of claims 22 to 25; or comprising any one of claims 19 to 21 The device described in any one of claims 26 to 28.
30. A communication device, characterized by comprising: a processor, the processor is coupled with a memory, and the memory is used to store a computer program, and when the processor invokes the computer program, the communication device executes the following: A method as claimed in any one of claims 1 to 14.

Images