WO2019242527A1 - 混合自动重传请求反馈信息harq-ack处理方法及装置 - Google Patents

混合自动重传请求反馈信息harq-ack处理方法及装置 Download PDF

Info

Publication number
WO2019242527A1
WO2019242527A1 PCT/CN2019/090658 CN2019090658W WO2019242527A1 WO 2019242527 A1 WO2019242527 A1 WO 2019242527A1 CN 2019090658 W CN2019090658 W CN 2019090658W WO 2019242527 A1 WO2019242527 A1 WO 2019242527A1
Authority
WO
WIPO (PCT)
Prior art keywords
ack
nack
harq process
harq
terminal device
Prior art date
Application number
PCT/CN2019/090658
Other languages
English (en)
French (fr)
Inventor
鲁智
潘学明
沈晓冬
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2019242527A1 publication Critical patent/WO2019242527A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]

Definitions

  • the present disclosure relates to the field of communication technologies, and in particular, to a HARQ-ACK processing method and device for hybrid automatic retransmission request feedback information.
  • the terminal device After receiving a Transport Block (TB) sent by a network device, the terminal device performs error detection on the received TB, and if the reception is correct, it sends an Acknowledgement (ACK) response to the network device, If the reception is incorrect, a Negative Acknowledgement (NACK) response is fed back to the network device. If the network device receives an ACK response, it continues to send new TBs. If the network device receives a NACK response, it retransmits the last TB sent.
  • TB Transport Block
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • the terminal device when feeding back ACK / NACK, the terminal device needs to first listen to the channel of the unlicensed spectrum. If the channel is idle, it sends ACK / NACK. If the listening channel is busy, ACK / NACK is not sent.
  • NR-U New Radio-Unlicensed Spectrum
  • the terminal device cannot feedback ACK / NACK to the network device, and the network device cannot obtain the corresponding ACK / NACK. In this case, the network device can only retransmit the previously transmitted TB, resulting in a waste of communication resources.
  • the purpose of the embodiments of the present disclosure is to provide a HARQ-ACK processing method and device for hybrid automatic retransmission request feedback information, so as to solve the technical problem of wasted communication resources in the related art.
  • a HARQ-ACK processing method for hybrid automatic retransmission request feedback information is proposed, which is applied to a terminal device, and the method includes:
  • the target DCI includes a first HARQ process indication field and a second HARQ process indication field
  • the first HARQ process indication field is used to indicate a HARQ process corresponding to a first ACK / NACK
  • the first The two HARQ process indication fields are used to indicate the HARQ process corresponding to the second ACK / NACK.
  • the first ACK / NACK is an ACK / NACK generated based on a currently transmitted transport block
  • the second ACK / NACK is based on a historical transmission.
  • An ACK / NACK generated by a transmission block, and the ACK / NACK generated by the transmission block based on history transmission is not fed back or feedback fails;
  • a HARQ-ACK processing method is proposed and is applied to a network device.
  • the method includes:
  • the target DCI includes a first HARQ process indication field and a second HARQ process indication field
  • the first HARQ process indication field is used to indicate the HARQ process corresponding to the first ACK / NACK
  • the second HARQ process indication field is used to indicate a HARQ process corresponding to a second ACK / NACK.
  • the first ACK / NACK is an ACK / NACK generated based on a currently transmitted transport block, and the second ACK / NACK is history-based. An ACK / NACK generated by the transmitted transmission block, and the ACK / NACK generated by the historically transmitted transmission block is not fed back or the feedback fails;
  • a HARQ-ACK processing device and an application terminal device are provided, and the device includes:
  • a first receiving module is configured to receive a target DCI, where the target DCI includes a first HARQ process indication field and a second HARQ process indication field, and the first HARQ process indication field is used to indicate a first ACK / NACK corresponding HARQ process, the second HARQ process indication field is used to indicate a HARQ process corresponding to a second ACK / NACK, the first ACK / NACK is an ACK / NACK generated based on a currently transmitted transport block, and the second ACK / NACK NACK is an ACK / NACK generated based on a historically transmitted transport block, and the ACK / NACK generated based on the historically transmitted transport block is not fed back or feedback fails;
  • a first sending module configured to send the first ACK / NACK and the second ACK / NACK to a network device.
  • a HARQ-ACK processing apparatus which is applied to network equipment, and the apparatus includes:
  • a second sending module is configured to send a target DCI to a terminal device, where the target DCI includes a first HARQ process indication field and a second HARQ process indication field, and the first HARQ process indication field is used to indicate a first ACK / A HARQ process corresponding to NACK, the second HARQ process indication field is used to indicate a HARQ process corresponding to a second ACK / NACK, the first ACK / NACK is an ACK / NACK generated based on a currently transmitted transport block, and the first The second ACK / NACK is an ACK / NACK generated based on a historically transmitted transmission block, and the ACK / NACK generated based on the historically transmitted transmission block is not feedback or feedback fails;
  • a third receiving module is configured to receive the first ACK / NACK and the second ACK / NACK from the terminal device.
  • a terminal device including: a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • the computer program is implemented by the processor to implement the foregoing. Steps of a HARQ-ACK processing method applied to a terminal device.
  • a network device including: a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • the computer program is implemented by the processor to implement the foregoing. Steps of a HARQ-ACK processing method applied to a network device.
  • a computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the HARQ-ACK processing method applied to a terminal device are implemented.
  • a computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the HARQ-ACK processing method applied to a network device are implemented.
  • the DCI can be used to instruct the terminal device to send the ACK / NACK of the currently transmitted PDSCH, as well as the ACK / NACK that has not been feedback or failed before, in order to avoid being unable to fail when the terminal device detects that the channel is busy.
  • the problem of PDSCH retransmission caused by sending ACK / NACK can achieve the purpose of saving communication resources and improving the efficiency of data transmission.
  • FIG. 1 is a flowchart of a HARQ-ACK processing method provided by some embodiments of the present disclosure
  • FIG. 2 is an example diagram of a HARQ-ACK processing method provided by some embodiments of the present disclosure
  • FIG. 3 is a flowchart of a HARQ-ACK processing method according to another embodiment of the present disclosure.
  • FIG. 4 is a schematic structural diagram of a HARQ-ACK processing apparatus according to some embodiments of the present disclosure.
  • FIG. 5 is a schematic structural diagram of a HARQ-ACK processing apparatus according to another embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a terminal device according to some embodiments of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a network device according to some embodiments of the present disclosure.
  • GSM Global System of Mobile
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WIMAX Global Interoperability for Microwave Access
  • the terminal device may include, but is not limited to, a mobile station (MS), a mobile terminal (Mobile), a mobile phone (Mobile), a user equipment (UE), and a handset (handset).
  • MS mobile station
  • Mobile mobile terminal
  • UE user equipment
  • handset handset
  • portable equipment portable equipment, vehicles
  • the terminal equipment can communicate with one or more core networks via a Radio Access Network (RAN).
  • RAN Radio Access Network
  • the terminal equipment can be a mobile phone (or (Referred to as a "cellular" phone), a computer with wireless communication functions, etc.
  • the terminal device may also be a portable, pocket-sized, handheld, computer-built or vehicle-mounted mobile device.
  • the network device involved in the embodiment of the present disclosure is a device that is deployed in a wireless access network to provide a wireless communication function for a terminal device.
  • the network device may be a base station, and the base station may include various forms of macro base stations, micro base stations, relay stations, access points, and the like.
  • the names of devices with base station capabilities may vary.
  • eNB Evolved NodeB
  • 3G 3rd Generation
  • the embodiments of the present disclosure provide a HARQ-ACK processing method and device for hybrid automatic retransmission request feedback information.
  • the HARQ-ACK processing method provided in the embodiment of the present application is first introduced below. To facilitate understanding, some concepts involved in the embodiments of the present disclosure are introduced.
  • ACK Acknowledgement
  • NACK Non-acknowledgement
  • a network device such as gNB
  • a transport block Transport block, TB
  • PDSCH physical downlink shared channel
  • DCI downlink control information
  • the DCI includes: uplink and downlink resource allocation, hybrid automatic repeat request (Hybrid, Automatic Repeat Request, HARQ) information, Transmit Power Control (TPC), and other information, that is, the DCI carries information about the correspondence between PDSCH, HARQ processes, and PUCCH or PUSCH.
  • Hybrid, Automatic Repeat Request, HARQ Hybrid, Automatic Repeat Request, HARQ
  • TPC Transmit Power Control
  • the terminal device will perform a blind detection to detect the PDCCH carrying DCI. After detecting the DCI, it determines which PDSCH receives the TB sent by the network device on the basis of the information carried in the DCI, and which HARQ process the buffered TB is received in. After the terminal device buffers the received TB into the corresponding HARQ process, the terminal device generates a corresponding ACK / NACK for the TB buffered in the HARQ process. In addition, the terminal device will determine which physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH) based on the information carried in the DCI, and then send ACK / NACK on ACK / NACK is sent on the corresponding PUCCH or PUSCH.
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • PDSCH is sometimes used to refer to “information transmitted on PDSCH, such as TB”
  • PDCCH is used to refer to “information transmitted on PDCCH”.
  • FIG. 1 is a flowchart of a HARQ-ACK processing method provided by some embodiments of the present disclosure. The method is applied to a terminal device. As shown in FIG. 1, the method may include the following steps: step 101 and step 102, where:
  • a target DCI is received, where the target DCI includes a first HARQ process indication field and a second HARQ process indication field.
  • the first HARQ process indication field is used to indicate the HARQ process corresponding to the first ACK / NACK, and the second HARQ.
  • the process indication field is used to indicate the HARQ process corresponding to the second ACK / NACK.
  • the first ACK / NACK is an ACK / NACK generated based on the currently transmitted transport block
  • the second ACK / NACK is an ACK / NACK generated based on the historically transmitted transport block.
  • NACK The ACK / NACK generated based on the historical transmission transport block is not fed back or the feedback fails.
  • the "currently transmitted transport block” and “historically transmitted transport block” are two relative concepts.
  • the “currently transmitted transport block” refers to the latest TB received by the terminal device.
  • Transport block refers to the TB previously received by the terminal device.
  • the first ACK / NACK is: the ACK / NACK generated by the terminal device based on the most recently received TB
  • the second ACK / NACK is: the terminal device is based on the previously received TB.
  • the generated ACK / NACK is not fed back or the feedback fails because the channel is busy.
  • the terminal device may be instructed to return the first ACK / NACK together with the second ACK / NACK by means of an explicit instruction, that is, to simultaneously feedback to the network device the data generated based on the latest received TB.
  • the DCI in the related technology only includes a first HARQ indication field.
  • the first HARQ indication field is used to indicate the HARQ process corresponding to the first ACK / NACK. Specifically, it can be used to indicate the HARQ process identifier corresponding to the first ACK / NACK.
  • the terminal After receiving the DCI in the related technology, the device will only feed back the first ACK / NACK, but not the second ACK / NACK. In other words, the terminal device will only feedback to the network device that is generated based on the latest received TB. ACK / NACK without sending back failed ACK / NACK to the network device.
  • an additional HARQ process indication field that is, a second HARQ process indication field, may be added to the DCI.
  • the field is used to indicate the HARQ process identifier corresponding to the second ACK / NACK.
  • PUCCH1 is associated with three PDSCHs (that is, ACK / NACK generated based on TB transmitted on the three PDSCHs is on PUCCH1 Transmission)
  • the HARQ processes used by PDSCH are: Processes 1, 2, and 3 (defined as PDSCH group 1 for convenience).
  • PUCCH2 is associated with 3 PDSCHs (that is, the ACK / NACK generated based on the TB transmitted on these 3 PDSCHs is transmitted on PUCCH2).
  • the HARQ processes used by PDSCH are: Processes 4, 5, 6 (defined for convenience of description) For PDSCH group 2).
  • the ACK / NACK corresponding to the PDSCH of processes 1, 2, and 3 needs to be fed back, but because the listening channel of the terminal device is busy, the corresponding ACK / NACK is not sent on PUCCH1.
  • the network device may add a second HARQ process indication field to the scheduling DCI of the PDSCH associated with the PUCCH2 that is subsequently transmitted, and the second HARQ process indication field is used to indicate the processes 1, 2, and 3, and the terminal device receives the DCI after receiving the DCI.
  • the ACK / NACK of the current schedule (HARQ process 4, 5, 6) and the ACK / NACK of the previous transmission failure (process 1, 2, 3) will be sent on PUCCH 2.
  • the second HARQ process indication field may include: a HARQ process bitmap corresponding to the second ACK / NACK.
  • the process bitmap is 1110000000000000, which represents HARQ process 1, 2, 3;
  • the process bitmap is 1111110000000000, Represents HARQ processes 1, 2, 3, 4, 5, and 6.
  • the total number of HARQ processes in the terminal device is 16, if you want to obtain complete flexibility, you need to add a 16-bit bitmap indicator field in the DCI to indicate whether you need to While transmitting the ACK / NACK generated based on the latest received TB, the ACK / NACK that was not previously transmitted or failed to transmit is transmitted together.
  • the second HARQ process indication field may include: a HARQ process group identifier corresponding to the second ACK / NACK.
  • the total number of HARQ processes in the terminal device is 16.
  • the second HARQ process indication field includes 2 bits, and 1 bit is used to indicate that the HARQ process ID is 1-8. One bit is used to indicate that the HARQ process ID is 9-16, so that only 2 bits are needed to implement the HARQ process indication.
  • the terminal device transmits an ACK / NACK corresponding to the HARQ process 1-8 while transmitting the ACK / NACK generated based on the newly received TB.
  • more fine-grained grouping can also be performed. For example, it can be divided into 4 groups and indicated by 4 bits, that is, the HARQ process ID of each group is 1-4, 5-8, 9-12, and 13-16.
  • a terminal device in an NR-U scenario may be restricted to use only part of a HARQ process. Specifically, the number of HARQ processes used by a terminal device in an NR-U scenario may be limited to reduce bit overhead in DCI. In addition, the following steps can be added before the above step 101:
  • RRC signaling is used to configure the number of available HARQ processes in the terminal device, and the number of available HARQ processes is greater than or equal to 2; according to RRC signaling, Sets the number of HARQ processes available on the terminal device.
  • the available HARQ process refers to a HARQ process in the terminal device that can be used to cache TB, and the terminal device generates an ACK / NACK for the TB cached in the available HARQ process.
  • the terminal device can be set to use only HARQ processes with IDs 1-8, so that only a 8-bit bitmap second HARQ process indication domain is added to the DCI.
  • the terminal device can be instructed to feed back the first ACK / NACK and the second ACK / NACK simultaneously through the PDCCH resource where the DCI is located.
  • the PDCCH-related information may include an identifier of a target control resource set (CORESET), where the target CORESET is a CORESET corresponding to the PDCCH, and the CORESET corresponding to the PDCCH refers to the CORESET where the PDCCH is located. .
  • CORESET target control resource set
  • the mapping relationship may include: an odd number of CORESET IDs correspond to HARQ processes 1-8, and an even number of CORESET IDs correspond to HARQ processes 9-16; or, the mapping relationship may include: a CORESET ID of modulo 3 being 0 corresponds to only Feedback the first ACK / NACK (that is, the ACK / NACK generated based on the most recently received TB), and the CORESET ID whose modulo 3 is 1 corresponds to the feedback of the first ACK / NACK and the second ACK / NACK corresponding to the HARQ process 1-8,
  • the CORESET ID with the mode 3 being 2 corresponds to the feedback of the first ACK / NACK and the second ACK / NACK corresponding to the HARQ process 9-16.
  • the PDCCH-related information may include an identifier of a target search space (search space), where the target search space is a search space corresponding to the PDCCH, and the search space corresponding to the PDCCH refers to the PDCCH.
  • search space there is a mapping relationship between the search space ID corresponding to the PDCCH where the DCI is located and the HARQ process.
  • the mapping relationship may include: an odd search space ID corresponding to the HARQ process 1-8, and an even number search space ID corresponding to the HARQ process 9-16; or, the mapping relationship may include: search space with modulo 3 being 0 ID corresponds to the feedback of only the first ACK / NACK, and the search space of modulo 3 is 1. ID corresponds to the feedback of the first ACK / NACK and the second ACK / NACK corresponding to HARQ process 1-8, and the search of space modulo 2 corresponds to the feedback.
  • the related information of the PDCCH may include an identifier of a target control channel element (Control Channel Element, CCE), where the target CCE is a starting CCE of the PDCCH. That is, there is a mapping relationship between the starting CCE ID of the PDCCH where the DCI is located and the HARQ process.
  • CCE Control Channel Element
  • the mapping relationship may include: an odd number of CCE IDs corresponds to the HARQ process 1-8, and an even number of CCE IDs corresponds to the HARQ process 9-16.
  • the related information of the PDCCH may include: ACK / NACK resource index (ARI) information in the DCI carried on the PDCCH. That is, there is a mapping relationship between the ARI in the DCI carried on the PDCCH and the HARQ process.
  • ARI NACK resource index
  • the mapping relationship may include: the first half of the total number of configured resources used by the ARI corresponds to the HARQ process 1-8, and the second half of the total number of configured resources used by the ARI corresponds to the HARQ process 9-16.
  • ARI indicates that the first third (rounded down) of the total number of configured resources corresponds to only the first ACK / NACK
  • ARI indicates that the middle third (down rounded) of the total number of configured resources corresponds to the first ACK / NACK and the corresponding
  • the second ACK / NACK of the HARQ process 1-8 when the ARI indicates that the remaining resources of the total number of resources are configured, the first ACK / NACK and the second ACK / NACK corresponding to the HARQ process 9-16 are correspondingly fed back.
  • the related information of the PDCCH may include: TPC information in the DCI carried on the PDCCH.
  • TPC information in the DCI carried on the PDCCH.
  • the mapping relationship may include: TPC indications 0 and 2 correspond to HARQ processes 1-8, and TPC indications 1 and 3 correspond to HARQ processes 9-16.
  • the related information of the PDCCH may include: Cyclic Redundancy Check (CRC) information of DCI carried on the PDCCH.
  • CRC Cyclic Redundancy Check
  • the CRC length used in the related technology is 24 bits, and the wireless network temporary identity (RNTI) of the terminal device scrambles 16 of them, and the remaining 8 bits can be used. At this time, a length of 8 bits can be designed. Sequences, such as ZC sequence, Walsh sequence, etc. scramble the 8bit to help indicate different packets. If the HARQ process is divided into three groups (for example, HARQ process 1-5, HARQ process 6-10, HARQ process 11-16), then the terminal device can be configured with 4 scrambling codes, and the terminal device can descramble the 4 scrambling codes to obtain Corresponding packet information, that is, HARQ process ID indication information corresponding to the second ACK / NACK. For example, the following four scrambling codes are used for scrambling:
  • Scrambling code 1 [1,1,1,1,1], instructs the terminal device to only feedback the ACK / NACK corresponding to the currently transmitted TB;
  • Scrambling code 2 [1, -1, -1, -1, -1], instructs the terminal device to feedback the ACK / NACK corresponding to the currently transmitted TB, and also the ACK / NACK corresponding to the HARQ process 1-5;
  • Scrambling code 3 [1, -1, -1, -1, -1], instructs the terminal device to feedback the ACK / NACK corresponding to the currently transmitted TB, and also the ACK / NACK corresponding to the HARQ process 6-10;
  • Scrambling code 4 [1, -1, -1, -1, -1, -1], instructs the terminal device to feedback the ACK / NACK corresponding to the currently transmitted TB, and also the ACK / NACK corresponding to the HARQ process 11-16.
  • the above information may also be carried on a PDCCH scheduling PUSCH or in a DCI.
  • the additional feedback HARQ process ID coincides with the currently scheduled HARQ ID
  • different processing behaviors of the terminal device can be standardized: while the terminal device feedbacks the ACK / NACK corresponding to the currently scheduled HARQ process ID, the additional feedback The ACK / NACK corresponding to the HARQ process ID corresponding to the ID; or only the ACK / NACK of the non-overlapping part of the HARQ process ID that is additionally fed back.
  • step 102 a first ACK / NACK and a second ACK / NACK are sent to the network device.
  • the terminal device determines the HARQ process corresponding to the first ACK / NACK and the HARQ process corresponding to the second ACK / NACK according to the DCI, and then according to the determined The HARQ process further determines a first ACK / NACK and a second ACK / NACK.
  • the terminal device determines the HARQ process corresponding to the second ACK / NACK according to the related information of the PDCCH resource where the DCI is located, and then determines the HARQ process according to the HARQ process ID. Second ACK / NACK.
  • the first ACK / NACK and the second ACK / NACK may be jointly encoded or independently encoded.
  • the first ACK / NACK and the second ACK / NACK may not be compressed. Or, in order to reduce the feedback load, the first ACK / NACK and the second ACK / NACK may be compressed and then fed back after compression.
  • step 102 may specifically include the following steps:
  • the binding method may include: performing AND operation on two ACKs / NACKs, wherein two ACKs are ANDed to obtain one ACK, and two NACKs are ANDed to obtain one NACK, one ACK, and one NACK is ANDed to get a NACK.
  • HARQ processes 1-4 4-bit ACK / NACK information needs to be fed back. If a binding method is used, ACK / NACK of HARQ process 1-2 is bound to form 1 bit, and HARQ process 3-4 ACK / NACK is bound to form 1 bit, so only 2 bits of ACK / NACK information need to be fed back.
  • the DCI can be used to instruct the terminal device to send the ACK / NACK of the currently transmitted PDSCH, as well as the ACK / NACK that has not been feedback or failed before, in order to avoid the channel detection by the terminal device.
  • the purpose of saving communication resources and improving the efficiency of data transmission can be achieved.
  • FIG. 3 is a flowchart of a HARQ-ACK processing method provided by some embodiments of the present disclosure. The method is applied to a terminal device. As shown in FIG. 3, the method may include the following steps: step 301 and step 302, where:
  • a target DCI is sent to a terminal device, where the target DCI includes a first HARQ process indication field and a second HARQ process indication field.
  • the first HARQ process indication field is used to indicate the HARQ process corresponding to the first ACK / NACK.
  • the second HARQ process indication field is used to indicate the HARQ process corresponding to the second ACK / NACK.
  • the first ACK / NACK is an ACK / NACK generated based on the currently transmitted transport block, and the second ACK / NACK is generated based on the historical transmission transport block.
  • ACK / NACK the ACK / NACK generated based on the historically transmitted transport block is not fed back or the feedback fails.
  • the "currently transmitted transport block” and “historically transmitted transport block” are two relative concepts.
  • the “currently transmitted transport block” refers to the latest TB received by the terminal device.
  • Transport block refers to the TB previously received by the terminal device.
  • the first ACK / NACK is: the ACK / NACK generated by the terminal device based on the most recently received TB
  • the second ACK / NACK is: the terminal device is based on the previously received TB
  • the generated ACK / NACK is not fed back or the feedback fails because the channel is busy.
  • the terminal device may be instructed to return the first ACK / NACK together with the second ACK / NACK by means of an explicit instruction, that is, to simultaneously feedback to the network device the data generated based on the latest received TB.
  • the DCI in the related technology only includes the first HARQ indication field. After receiving the DCI in the related technology, the terminal device will only feed back the first ACK / NACK, but not the second ACK / NACK. In other words, the terminal device Only the ACK / NACK generated based on the newly received TB will be fed back to the network device, and the failed ACK / NACK will not be fed back to the network device.
  • an additional HARQ process indication field that is, a second HARQ process indication field, may be added to the DCI.
  • the field is used to indicate the HARQ process identifier corresponding to the second ACK / NACK.
  • the second HARQ process indication field may include: a HARQ process bitmap corresponding to the second ACK / NACK.
  • the process bitmap is 1110000000000000, which represents HARQ process 1, 2, 3;
  • the process bitmap is 1111110000000000, Represents HARQ processes 1, 2, 3, 4, 5, and 6.
  • the total number of HARQ processes in the terminal device is 16, if you want to obtain complete flexibility, you need to add a 16-bit bitmap indication field in the DCI to indicate whether you need to While transmitting the ACK / NACK generated based on the latest received TB, the ACK / NACK that was not previously transmitted or failed to transmit is transmitted together.
  • the second HARQ process indication field may include: a HARQ process group identifier corresponding to the second ACK / NACK.
  • the total number of HARQ processes in the terminal device is 16.
  • the second HARQ process indication field includes 2 bits, and 1 bit is used to indicate that the HARQ process ID is 1-8. One bit is used to indicate that the HARQ process ID is 9-16, so that only 2 bits are needed to implement the HARQ process indication.
  • the terminal device transmits an ACK / NACK corresponding to the HARQ process 1-8 while transmitting the ACK / NACK generated based on the newly received TB.
  • more fine-grained grouping can also be performed. For example, it can be divided into 4 groups and indicated by 4 bits, that is, the HARQ process ID of each group is 1-4, 5-8, 9-12, and 13-16.
  • a terminal device in an NR-U scenario may be restricted to use only part of a HARQ process. Specifically, the number of HARQ processes used by a terminal device in an NR-U scenario may be limited to reduce bit overhead in DCI. In addition, the following steps can be added before the above step 301:
  • the RRC signaling is used to configure the number of available HARQ processes in the terminal device, and the number of available HARQ processes is greater than or equal to two.
  • the available HARQ process refers to a HARQ process in the terminal device that can be used to cache TB, and the terminal device generates an ACK / NACK for the TB cached in the available HARQ process.
  • the terminal device can be set to use only HARQ processes with IDs 1-8, so that only a 8-bit bitmap second HARQ process indication domain is added to the DCI.
  • the terminal device can be instructed to feed back the first ACK / NACK and the second ACK / NACK simultaneously through the PDCCH resource where the DCI is located.
  • the PDCCH-related information may include an identifier of a target control resource set (CORESET), where the target CORESET is a CORESET corresponding to the PDCCH, and the CORESET corresponding to the PDCCH refers to the CORESET where the PDCCH is located.
  • CORESET target control resource set
  • the mapping relationship may include: an odd number of CORESET IDs correspond to HARQ processes 1-8, and an even number of CORESET IDs correspond to HARQ processes 9-16; or, the mapping relationship may include: a CORESET ID of modulo 3 being 0 corresponds to only Feedback the first ACK / NACK (that is, the ACK / NACK generated based on the most recently received TB), and the CORESET ID whose modulo 3 is 1 corresponds to the feedback of the first ACK / NACK and the second ACK / NACK corresponding to the HARQ process 1-8,
  • the CORESET ID with the mode 3 being 2 corresponds to the feedback of the first ACK / NACK and the second ACK / NACK corresponding to the HARQ process 9-16.
  • the PDCCH-related information may include an identifier of a target search space (search space), where the target search space is a search space corresponding to the PDCCH, and the search space corresponding to the PDCCH refers to the PDCCH.
  • search space there is a mapping relationship between the search space ID corresponding to the PDCCH where the DCI is located and the HARQ process.
  • the mapping relationship may include: an odd search space ID corresponding to the HARQ process 1-8, and an even number search space ID corresponding to the HARQ process 9-16; or, the mapping relationship may include: search space with modulo 3 being 0 ID corresponds to the feedback of only the first ACK / NACK, and the search space of modulo 3 is 1. ID corresponds to the feedback of the first ACK / NACK and the second ACK / NACK corresponding to HARQ process 1-8, and the search of space modulo 2 corresponds to the feedback.
  • the related information of the PDCCH may include an identifier of a target control channel element (Control Channel Element, CCE), where the target CCE is a starting CCE of the PDCCH. That is, there is a mapping relationship between the starting CCE ID of the PDCCH where the DCI is located and the HARQ process.
  • CCE Control Channel Element
  • the mapping relationship may include: an odd number of CCE IDs corresponds to the HARQ process 1-8, and an even number of CCE IDs corresponds to the HARQ process 9-16.
  • the related information of the PDCCH may include: ACK / NACK resource index (ARI) information in the DCI carried on the PDCCH. That is, there is a mapping relationship between the ARI in the DCI carried on the PDCCH and the HARQ process.
  • ARI NACK resource index
  • the mapping relationship may include: the first half of the total number of configured resources used by the ARI corresponds to the HARQ process 1-8, and the second half of the total number of configured resources used by the ARI corresponds to the HARQ process 9-16.
  • ARI indicates that the first third (rounded down) of the total number of configured resources corresponds to only the first ACK / NACK
  • ARI indicates that the middle third (down rounded) of the total number of configured resources corresponds to the feedback of the first ACK / NACK and corresponds to
  • the second ACK / NACK of the HARQ process 1-8 when the ARI indicates that the remaining resources of the total number of resources are configured, the first ACK / NACK and the second ACK / NACK corresponding to the HARQ process 9-16 are correspondingly fed back.
  • the related information of the PDCCH may include: TPC information in the DCI carried on the PDCCH.
  • TPC information in the DCI carried on the PDCCH.
  • the mapping relationship may include: TPC indications 0 and 2 correspond to HARQ processes 1-8, and TPC indications 1 and 3 correspond to HARQ processes 9-16.
  • the related information of the PDCCH may include: Cyclic Redundancy Check (CRC) information of DCI carried on the PDCCH.
  • CRC Cyclic Redundancy Check
  • the CRC length used in the related technology is 24 bits, and the wireless network temporary identity (RNTI) of the terminal device scrambles 16 of them, and the remaining 8 bits can be used. At this time, a length of 8 bits can be designed. Sequences, such as ZC sequence, Walsh sequence, etc. scramble the 8bit to help indicate different packets. If the HARQ process is divided into three groups (for example, HARQ process 1-5, HARQ process 6-10, HARQ process 11-16), then the terminal device can be configured with 4 scrambling codes, and the terminal device can descramble the 4 scrambling codes to obtain Corresponding packet information, that is, HARQ process ID indication information corresponding to the second ACK / NACK. For example, the following four scrambling codes are used for scrambling:
  • Scrambling code 1 [1,1,1,1,1], instructs the terminal device to only feedback the ACK / NACK corresponding to the currently transmitted TB;
  • Scrambling code 2 [1, -1, -1, -1, -1], instructs the terminal device to feedback the ACK / NACK corresponding to the currently transmitted TB, and also the ACK / NACK corresponding to the HARQ process 1-5;
  • Scrambling code 3 [1, -1, -1, -1, -1], instructs the terminal device to feedback the ACK / NACK corresponding to the currently transmitted TB, and also the ACK / NACK corresponding to the HARQ process 6-10;
  • Scrambling code 4 [1, -1, -1, -1, -1, -1], instructs the terminal device to feedback the ACK / NACK corresponding to the currently transmitted TB, and also the ACK / NACK corresponding to the HARQ process 11-16.
  • the above information may also be carried on a PDCCH scheduling PUSCH or in a DCI.
  • the additional feedback HARQ process ID coincides with the currently scheduled HARQ ID
  • different processing behaviors of the terminal device can be standardized: while the terminal device feedbacks the ACK / NACK corresponding to the currently scheduled HARQ process ID, the additional feedback The ACK / NACK corresponding to the HARQ process ID corresponding to the ID; or only the ACK / NACK of the non-overlapping part of the HARQ process ID that is additionally fed back.
  • step 302 a first ACK / NACK and a second ACK / NACK are received from a terminal device.
  • the first ACK / NACK and the second ACK / NACK sent by the terminal device may be joint coding or independent coding.
  • the terminal device when feeding back to the network device, may not compress the first ACK / NACK and the second ACK / NACK. At this time, the ACK / NACK received by the network device is not compressed. Or, in order to reduce the feedback load, the terminal device may compress the first ACK / NACK and the second ACK / NACK, and then feedback after compression. At this time, the ACK / NACK received by the network device has been compressed.
  • the terminal device may bundle ACK / NACKs corresponding to different HARQ process IDs. Specifically, the second ACK / NACK The NACK is bound to obtain the bound ACK / NACK; and the first ACK / NACK and the bound ACK / NACK are sent to the network device. Correspondingly, the network device receives the first ACK / NACK and the bound ACK / NACK.
  • the binding method may include: performing AND operation on two ACKs / NACKs, wherein two ACKs are ANDed to obtain one ACK, and two NACKs are ANDed to obtain one NACK, one ACK, and one NACK is ANDed to get a NACK.
  • HARQ processes 1-4 4-bit ACK / NACK information needs to be fed back. If a binding method is used, ACK / NACK of HARQ process 1-2 is bound to form 1 bit, and HARQ process 3-4 ACK / NACK is bound to form 1 bit, so only 2 bits of ACK / NACK information need to be fed back.
  • the DCI can be used to instruct the terminal device to send the ACK / NACK of the currently transmitted PDSCH, as well as the ACK / NACK that has not been feedback or failed before, in order to avoid the channel detection by the terminal device.
  • the purpose of saving communication resources and improving the efficiency of data transmission can be achieved.
  • FIG. 4 is a schematic structural diagram of a HARQ-ACK processing apparatus provided by some embodiments of the present disclosure.
  • the HARQ-ACK processing apparatus is applied to a terminal device.
  • the HARQ-ACK processing apparatus 400 may include a first receiving module. 401 and a first sending module 402, where:
  • a first receiving module 401 is configured to receive a target DCI, where the target DCI includes a first HARQ process indication field and a second HARQ process indication field, and the first HARQ process indication field is used to indicate a first ACK / NACK correspondence.
  • a HARQ process, the second HARQ process indication field is used to indicate a HARQ process corresponding to a second ACK / NACK, the first ACK / NACK is an ACK / NACK generated based on a currently transmitted transport block, and the second ACK / NACK is an ACK / NACK generated based on a historically transmitted transport block, and the ACK / NACK generated based on the historically transmitted transport block is not feedback or feedback fails;
  • the first sending module 402 is configured to send the first ACK / NACK and the second ACK / NACK to a network device.
  • the DCI can be used to instruct the terminal device to send the ACK / NACK of the currently transmitted PDSCH, as well as the ACK / NACK that has not been feedback or failed before, in order to avoid the channel detection by the terminal device.
  • the purpose of saving communication resources and improving the efficiency of data transmission can be achieved.
  • the second HARQ process indication field is used to indicate a HARQ process identifier corresponding to the second ACK / NACK.
  • the second HARQ process indication field includes any one of the following:
  • the HARQ-ACK processing apparatus 400 may further include:
  • a second receiving module is configured to receive radio resource control RRC signaling, where the RRC signaling is used to configure the number of available HARQ processes in the terminal device, and the number of available HARQ processes is greater than or equal to 2;
  • a setting module configured to set the number of HARQ processes available in the terminal device according to the RRC signaling.
  • mapping relationship between the related information of the physical downlink control channel PDCCH where the DCI is located and the HARQ process;
  • the HARQ process corresponding to the second ACK / NACK is a HARQ process corresponding to related information of the PDCCH where the target DCI is located.
  • the related information of the PDCCH includes at least one of the following:
  • the target CORESET is the CORESET corresponding to the PDCCH
  • the target search space is the search space corresponding to the PDCCH
  • the target CCE is the starting CCE of the PDCCH.
  • the first sending module 402 may include:
  • a binding submodule configured to bind the second ACK / NACK to obtain a bound ACK / NACK
  • a sending submodule configured to send the first ACK / NACK and the bound ACK / NACK to a network device.
  • FIG. 5 is a schematic structural diagram of a HARQ-ACK processing apparatus according to another embodiment of the present disclosure.
  • the HARQ-ACK processing apparatus is applied to a network device.
  • the HARQ-ACK processing apparatus 500 may include: a second transmission Module 501 and a third receiving module 502, where:
  • a second sending module 501 is configured to send a target DCI to a terminal device, where the target DCI includes a first HARQ process indication field and a second HARQ process indication field, and the first HARQ process indication field is used to indicate a first ACK.
  • a HARQ process corresponding to / NACK the second HARQ process indication field is used to indicate a HARQ process corresponding to a second ACK / NACK
  • the first ACK / NACK is an ACK / NACK generated based on a currently transmitted transport block
  • the The second ACK / NACK is an ACK / NACK generated based on a historically transmitted transport block
  • the ACK / NACK generated based on the historically transmitted transport block is not feedback or feedback fails;
  • a third receiving module 502 is configured to receive the first ACK / NACK and the second ACK / NACK from the terminal device.
  • the DCI can be used to instruct the terminal device to send the ACK / NACK of the currently transmitted PDSCH, as well as the ACK / NACK that has not been feedback or failed before, in order to avoid the channel detection by the terminal device.
  • the purpose of saving communication resources and improving the efficiency of data transmission can be achieved.
  • the HARQ-ACK processing apparatus 500 may further include:
  • a third sending module configured to send RRC signaling to the terminal device, where the RRC signaling is used to configure the number of available HARQ processes in the terminal device, and the number of available HARQ processes is greater than Or equal to 2.
  • FIG. 6 is a schematic structural diagram of a terminal device provided by some embodiments of the present application.
  • the terminal device 600 includes: at least one processor 601, a memory 602, at least one network interface 604, and a user interface 603.
  • the various components in the terminal device 600 are coupled together via a bus system 605.
  • the bus system 605 is used to implement connection and communication between these components.
  • the bus system 605 includes a power bus, a control bus, and a status signal bus in addition to the data bus. However, for the sake of clarity, various buses are marked as the bus system 605 in FIG. 6.
  • the user interface 603 may include a display, a keyboard, or a pointing device (for example, a mouse, a trackball, a trackball, a touchpad, or a touch screen).
  • a pointing device for example, a mouse, a trackball, a trackball, a touchpad, or a touch screen.
  • the memory 602 in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), and an electronic memory. Erase programmable read-only memory (EPROM, EEPROM) or flash memory.
  • the volatile memory may be Random Access Memory (RAM), which is used as an external cache.
  • RAM Static Random Access Memory
  • DRAM Dynamic Random Access Memory
  • Synchronous Dynamic Random Access Memory Synchronous Dynamic Random Access Memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM, DDRSDRAM enhanced synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM synchronous connection dynamic random access memory
  • Synchronous DRAM synchronous dynamic random access memory
  • Synchlink DRAM SLDRAM
  • Direct RAMbus RAM Direct RAMbus RAM
  • the memory 602 of the systems and methods described in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.
  • the memory 602 stores the following elements, executable modules or data structures, or a subset of them, or their extended set: an operating system 6021 and an application program 6022.
  • the operating system 6021 includes various system programs, such as a framework layer, a core library layer, and a driver layer, etc., for implementing various basic services and processing hardware-based tasks.
  • the application program 6022 includes various application programs, such as a media player (Player), a browser (Browser), and the like, and is used to implement various application services.
  • a program for implementing the method in the embodiment of the present application may be included in the application program 6022.
  • the terminal device 600 further includes a computer program stored on the memory 602 and executable on the processor 601.
  • the computer program is executed by the processor 601, the following steps are implemented:
  • the target DCI includes a first HARQ process indication field and a second HARQ process indication field
  • the first HARQ process indication field is used to indicate a HARQ process corresponding to a first ACK / NACK
  • the first The two HARQ process indication fields are used to indicate the HARQ process corresponding to the second ACK / NACK.
  • the first ACK / NACK is an ACK / NACK generated based on a currently transmitted transport block
  • the second ACK / NACK is based on a historical transmission.
  • An ACK / NACK generated by a transmission block, and the ACK / NACK generated by the transmission block based on history transmission is not fed back or feedback fails;
  • the method disclosed in the foregoing embodiment of the present application may be applied to the processor 601, or implemented by the processor 601.
  • the processor 601 may be an integrated circuit chip and has a signal processing capability. In the implementation process, each step of the above method may be completed by using an integrated logic circuit of hardware in the processor 601 or an instruction in the form of software.
  • the processor 601 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • Various methods, steps, and logical block diagrams disclosed in the embodiments of the present application may be implemented or executed.
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present application may be directly implemented by a hardware decoding processor, or may be performed by using a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a mature computer-readable storage medium such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and the like in the art.
  • the computer-readable storage medium is located in the memory 602, and the processor 601 reads the information in the memory 602 and completes the steps of the foregoing method in combination with its hardware.
  • a computer program is stored on the computer-readable storage medium, and when the computer program is executed by the processor 601, each step of the HARQ-ACK processing method embodiment described above is implemented.
  • the embodiments described in the embodiments of the present application may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPD), programmable Logic device (Programmable Logic Device, PLD), Field-Programmable Gate Array (FPGA), general-purpose processor, controller, microcontroller, microprocessor, other for performing the functions described in this application Electronic unit or combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPD Digital Signal Processing Devices
  • PLD programmable Logic Device
  • FPGA Field-Programmable Gate Array
  • the technology described in the embodiments of the present application can be implemented by modules (such as procedures, functions, etc.) that perform the functions described in the embodiments of the present application.
  • Software codes may be stored in a memory and executed by a processor.
  • the memory may be implemented in the processor or external to the processor.
  • the second HARQ process indication field is used to indicate a HARQ process identifier corresponding to the second ACK / NACK.
  • the second HARQ process indication field includes any one of the following:
  • the method before the step of receiving the target downlink control information DCI, the method further includes:
  • Radio resource control RRC signaling where the RRC signaling is used to configure the number of available HARQ processes in the terminal device, and the number of available HARQ processes is greater than or equal to 2;
  • mapping relationship between the related information of the physical downlink control channel PDCCH where the DCI is located and the HARQ process;
  • the HARQ process corresponding to the second ACK / NACK is a HARQ process corresponding to related information of the PDCCH where the target DCI is located.
  • the related information of the PDCCH includes at least one of the following:
  • the target CORESET is the CORESET corresponding to the PDCCH
  • the target search space is the search space corresponding to the PDCCH
  • the target CCE is the starting CCE of the PDCCH.
  • the sending the first ACK / NACK and the second ACK / NACK to a network device includes:
  • the terminal device 600 can implement the processes implemented by the terminal device in the foregoing embodiments. To avoid repetition, details are not described herein again.
  • FIG. 7 is a schematic structural diagram of a network device according to some embodiments of the present disclosure.
  • the network device 700 includes: a processor 701, a transceiver 702, a memory 703, a user interface 704, and a bus interface, where:
  • the network device 700 further includes a computer program stored on the memory 703 and executable on the processor 701.
  • a computer program stored on the memory 703 and executable on the processor 701.
  • the target DCI includes a first HARQ process indication field and a second HARQ process indication field
  • the first HARQ process indication field is used to indicate the HARQ process corresponding to the first ACK / NACK
  • the second HARQ process indication field is used to indicate a HARQ process corresponding to a second ACK / NACK.
  • the first ACK / NACK is an ACK / NACK generated based on a currently transmitted transport block, and the second ACK / NACK is history-based. An ACK / NACK generated by the transmitted transmission block, and the ACK / NACK generated by the historically transmitted transmission block is not fed back or the feedback fails;
  • the bus architecture may include any number of interconnected buses and bridges, and one or more processors specifically represented by the processor 701 and various circuits of the memory represented by the memory 703 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, so they are not described further herein.
  • the bus interface provides an interface.
  • the transceiver 702 may be multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium.
  • the user interface 704 may also be an interface capable of externally connecting and connecting the required devices.
  • the connected devices include, but are not limited to, a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 701 is responsible for managing the bus architecture and general processing, and the memory 703 may store data used by the processor 701 when performing operations.
  • the embodiment of the present disclosure further provides a computer-readable storage medium, and the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, implements each process of the foregoing HARQ-ACK processing method embodiment applied to a terminal device And can achieve the same technical effect, in order to avoid repetition, it will not be repeated here.
  • the embodiment of the present disclosure further provides a computer-readable storage medium, and the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, implements each process of the foregoing HARQ-ACK processing method embodiment applied to a network device And can achieve the same technical effect, in order to avoid repetition, it will not be repeated here.
  • the computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
  • An embodiment of the present disclosure further provides a computer program product including instructions.
  • a computer runs the instructions of the computer program product
  • the computer executes the HARQ-ACK processing method applied to a terminal device.
  • the computer program product can run on the terminal device.
  • An embodiment of the present disclosure also provides a computer program product including instructions.
  • a computer runs the instructions of the computer program product, the computer executes the HARQ-ACK processing method applied to a network device.
  • the computer program product can run on the network device.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present disclosure is essentially a part that contributes to related technologies or a part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including several
  • the instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in various embodiments of the present disclosure.
  • the foregoing storage media include: U disks, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks or compact discs and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)

Abstract

提供了一种混合自动重传请求反馈信息HARQ-ACK处理方法及装置，该方法包括：接收目标DCI，目标DCI包含第一HARQ进程指示域和第二HARQ进程指示域，第一HARQ进程指示域用于指示第一ACK/NACK对应的HARQ进程，第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程，第一ACK/NACK为基于当前传输的传输块生成的ACK/NACK，第二ACK/NACK为基于历史传输的传输块生成的ACK/NACK；向网络设备发送第一ACK/NACK和第二ACK/NACK。

Description

混合自动重传请求反馈信息HARQ-ACK处理方法及装置
相关申请的交叉引用
本申请主张在2018年6月21日在中国提交的中国专利申请号No.201810641481.2的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种混合自动重传请求反馈信息HARQ-ACK处理方法及装置。
背景技术
相关技术中，在接收到网络设备发送的传输块(Transport Block，TB)后，终端设备会对接收到的TB进行检错，如果接收正确，则向网络设备反馈确认(Acknowledgement，ACK)应答，如果接收错误，则向网络设备反馈不确认(Negative Acknowledgement，NACK)应答。如果网络设备接收到ACK应答，则继续发送新的TB，如果网络设备接收到NACK应答，则重新传输上次发送的TB。
在新空口-非授权频谱(New Radio in Unlicensed spectrum，NR-U)场景中，在反馈ACK/NACK时，终端设备需要先行侦听非授权频谱的信道，如果侦听到信道为空闲，则发送ACK/NACK，如果侦听到信道为忙，则不发送ACK/NACK。
可见，如果侦听到信道为忙，则终端设备将不能向网络设备反馈ACK/NACK，网络设备也就无法获得相应的ACK/NACK。此情况下，网络设备只能对之前发送的TB进行重传，造成通信资源的浪费。
发明内容
本公开实施例的目的是提供一种混合自动重传请求反馈信息HARQ-ACK处理方法及装置，以解决相关技术中存在的通信资源的浪费的技术问题。
第一方面，提出了一种混合自动重传请求反馈信息HARQ-ACK处理方 法，应用于终端设备，所述方法包括：
接收目标下行控制信息DCI，其中，目标DCI包含第一HARQ进程指示域和第二HARQ进程指示域，所述第一HARQ进程指示域用于指示第一ACK/NACK对应的HARQ进程，所述第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程，所述第一ACK/NACK为基于当前传输的传输块生成的ACK/NACK，所述第二ACK/NACK为基于历史传输的传输块生成的ACK/NACK，所述基于历史传输的传输块生成的ACK/NACK未反馈或反馈失败；
向网络设备发送所述第一ACK/NACK和所述第二ACK/NACK。
第二方面，提出了HARQ-ACK处理方法，应用于网络设备，所述方法包括：
向终端设备发送目标DCI，其中，所述目标DCI包含第一HARQ进程指示域和第二HARQ进程指示域，所述第一HARQ进程指示域用于指示第一ACK/NACK对应的HARQ进程，所述第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程，所述第一ACK/NACK为基于当前传输的传输块生成的ACK/NACK，所述第二ACK/NACK为基于历史传输的传输块生成的ACK/NACK，所述基于历史传输的传输块生成的ACK/NACK未反馈或反馈失败；
接收来自所述终端设备的所述第一ACK/NACK和所述第二ACK/NACK。
第三方面，提出了HARQ-ACK处理装置，应用终端设备，所述装置包括：
第一接收模块，用于接收目标DCI，其中，所述目标DCI包含第一HARQ进程指示域和第二HARQ进程指示域，所述第一HARQ进程指示域用于指示第一ACK/NACK对应的HARQ进程，所述第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程，所述第一ACK/NACK为基于当前传输的传输块生成的ACK/NACK，所述第二ACK/NACK为基于历史传输的传输块生成的ACK/NACK，所述基于历史传输的传输块生成的ACK/NACK未反馈或反馈失败；
第一发送模块，用于向网络设备发送所述第一ACK/NACK和所述第二 ACK/NACK。
第四方面，提出了一种HARQ-ACK处理装置，应用于网络设备，所述装置包括：
第二发送模块，用于向终端设备发送目标DCI，其中，所述目标DCI包含第一HARQ进程指示域和第二HARQ进程指示域，所述第一HARQ进程指示域用于指示第一ACK/NACK对应的HARQ进程，所述第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程，所述第一ACK/NACK为基于当前传输的传输块生成的ACK/NACK，所述第二ACK/NACK为基于历史传输的传输块生成的ACK/NACK，所述基于历史传输的传输块生成的ACK/NACK未反馈或反馈失败；
第三接收模块，用于接收来自所述终端设备的所述第一ACK/NACK和所述第二ACK/NACK。
第五方面，提出了一种终端设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述应用于终端设备的HARQ-ACK处理方法的步骤。
第六方面，提出了一种网络设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述应用于网络设备的HARQ-ACK处理方法的步骤。
第七方面，提出了一种计算机可读存储介质，所述计算机可读存储介质上存储计算机程序，所述计算机程序被处理器执行时实现上述应用于终端设备的HARQ-ACK处理方法的步骤。
第八方面，提出了一种计算机可读存储介质，所述计算机可读存储介质上存储计算机程序，所述计算机程序被处理器执行时实现上述应用于网络设备的HARQ-ACK处理方法的步骤。
由以上本公开实施例提供的技术方案可见，本公开实施例方案至少具备如下一种技术效果：
在本公开实施例中，可以通过DCI指示终端设备在发送当前传输的PDSCH的ACK/NACK的同时，也发送之前未反馈或反馈失败的ACK/NACK，以避免由于终端设备检测信道为忙时无法发送ACK/NACK所引起的PDSCH 重传的问题，可以达到节省通信资源和提高数据传输有效性的目的。
附图说明
为了更清楚地说明本公开实施例或相关技术中的技术方案，下面将对实施例或相关技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本公开的一些实施例提供的HARQ-ACK处理方法的流程图；
图2是本公开的一些实施例提供的HARQ-ACK处理方法的实例图；
图3是本公开的另一些实施例提供的HARQ-ACK处理方法的流程图；
图4是本公开的一些实施例提供的HARQ-ACK处理装置的结构示意图；
图5是本公开的另一些实施例提供的HARQ-ACK处理装置的结构示意图；
图6是本公开的一些实施例提供的终端设备的结构示意图；
图7是本公开的一些实施例提供的网络设备的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本公开中的技术方案，下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
应理解，本公开实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯系统(Global System of Mobile communication，GSM)，码分多址(Code Division Multiple Access，CDMA)系统，宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统，通用分组无线业务(General Packet Radio Service，GPRS)系统，长期演进(Long Term Evolution，LTE)系统、频分双工(Frequency Division Duplex，FDD)系统、时分双工(Time Division  Duplex，TDD)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、或全球互联微波接入(Worldwide Interoperability for Microwave Access，WIMAX)通信系统、5G系统，或者新空口(New Radio，NR)系统，及后续演进通信系统等。
在本公开实施例中，终端设备可以包括但不限于移动台(Mobile Station，MS)、移动终端(Mobile Terminal)、移动电话(Mobile Telephone)、用户设备(User Equipment，UE)、手机(handset)及便携设备(portable equipment)、车辆(vehicle)等，该终端设备可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，例如，终端设备可以是移动电话(或称为“蜂窝”电话)、具有无线通信功能的计算机等，终端设备还可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置。
本公开实施例中所涉及到的网络设备是一种部署在无线接入网中用以为终端设备提供无线通信功能的装置。所述网络设备可以为基站，所述基站可以包括各种形式的宏基站，微基站，中继站，接入点等。在采用不同的无线接入技术的系统中，具有基站功能的设备的名称可能会有所不同。例如在LTE网络中，称为演进的节点B(Evolved NodeB，eNB或eNodeB)，在第三代(3rd Generation，3G)网络中，称为节点B(Node B)，或者后续演进通信系统中网络侧的设备等等。
本公开实施例提供了一种混合自动重传请求反馈信息HARQ-ACK处理方法及装置。下面首先对本申请实施例提供的HARQ-ACK处理方法进行介绍。为了便于理解，对本公开实施例中涉及到的一些概念进行介绍。
确认应答(ACK)/不确认应答(NACK)的反馈过程：网络设备(例如gNB)在通过物理下行共享信道(Physical Downlink Shared Channel，PDSCH)向终端设备发送传输块(Transport Block，TB)之前，会通过物理下行控制信道(Physical Downlink Control Channel，PDCCH)向终端设备发送下行控制信息(Downlink Control Information，DCI)，该DCI中包括：上下行资源分配、混合自动重传请求(Hybrid Automatic Repeat Request，HARQ)信息、传输功率控制(Transmit Power Control，TPC)等信息，也就是说，DCI中携带了PDSCH、HARQ进程与PUCCH或PUSCH的对应关系信息。
终端设备会进行盲检，检测承载DCI的PDCCH，在检测到DCI后，根据DCI中携带的信息，确定在哪个PDSCH上接收网络设备发送的TB，以及将接收到的TB缓存到哪个HARQ进程中，终端设备在将接收到的TB缓存到对应的HARQ进程之后，会针对HARQ进程中缓存的该TB生成对应的ACK/NACK。此外，终端设备会根据DCI中携带的信息，确定在哪个物理上行链路控制信道(Physical Uplink Control Channel，PUCCH)或物理上行共享信道(Physical Uplink Shared Channel，PUSCH)上发送ACK/NACK，之后在相应的PUCCH或PUSCH上发送ACK/NACK。
需要说明的是，为了便于描述和理解，在一些场景中，有时会用“PDSCH”指代“PDSCH上传输的信息，例如TB”，用“PDCCH”指代“PDCCH上传输的信息”。
图1是本公开的一些实施例提供的HARQ-ACK处理方法的流程图，该方法应用于终端设备，如图1所示，该方法可以包括以下步骤：步骤101和步骤102，其中，
在步骤101中，接收目标DCI，其中，目标DCI包含第一HARQ进程指示域和第二HARQ进程指示域，第一HARQ进程指示域用于指示第一ACK/NACK对应的HARQ进程，第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程，第一ACK/NACK为基于当前传输的传输块生成的ACK/NACK，第二ACK/NACK为基于历史传输的传输块生成的ACK/NACK，基于历史传输的传输块生成的ACK/NACK未反馈或反馈失败。
本公开实施例中，“当前传输的传输块”和“历史传输的传输块”是两个相对的概念，“当前传输的传输块”指的是终端设备最新接收到的TB，“历史传输的传输块”指的是终端设备之前接收到的TB，第一ACK/NACK为：终端设备基于最新接收到的TB生成的ACK/NACK，第二ACK/NACK为：终端设备基于之前接收到的TB生成的ACK/NACK、且该ACK/NACK由于信道为忙而未被反馈或反馈失败。
本公开实施例中，可以通过显式指示的方式，指示终端设备在反馈第一ACK/NACK的同时，一并反馈第二ACK/NACK，即同时向网络设备反馈基于最新接收到的TB生成的ACK/NACK和之前反馈失败的ACK/NACK；或 者，也可以通过隐式指示的方式，指示终端设备在反馈第一ACK/NACK的同时，一并反馈第二ACK/NACK，本公开实施例对此不作限定。
下面分别对显式指示的方式和隐式指示的方式进行详细说明。
一、显式指示的方式：
相关技术中的DCI仅包含第一HARQ指示域，第一HARQ指示域用于指示第一ACK/NACK对应的HARQ进程，具体的，可以用于指示第一ACK/NACK对应的HARQ进程标识，终端设备在接收到相关技术中的DCI后，只会反馈第一ACK/NACK，而不会反馈第二ACK/NACK，换句话说，终端设备只会向网络设备反馈基于最新接收到的TB生成的ACK/NACK，而不会向网络设备反馈之前反馈失败的ACK/NACK。
为指示终端设备同时反馈第一ACK/NACK和第二ACK/NACK，本公开实施例中，可以在DCI中额外增加一个HARQ进程指示域，即第二HARQ进程指示域，该第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程标识。
为了便于理解，结合一个具体的实例对本公开实施例进行描述，如图2所示，PUCCH1关联3个PDSCH(也就是说，基于这3个PDSCH上传输的TB生成的ACK/NACK，在PUCCH1上传输)，PDSCH使用的HARQ进程分别为：进程1，2，3(为方便描述定义为PDSCH组1)。PUCCH2关联3个PDSCH(也就是说，基于这3个PDSCH上传输的TB生成的ACK/NACK，在PUCCH2上传输)，PDSCH使用的HARQ进程分别为：进程4，5，6(为方便描述定义为PDSCH组2)。
例如，在t1时刻需要反馈进程1，2，3的PDSCH对应的ACK/NACK，但由于终端设备侦听信道为忙，没有在PUCCH1上发送相应的ACK/NACK。网络设备可以在后续传输的PUCCH2关联的PDSCH的调度DCI中，增加第二HARQ进程指示域，该第二HARQ进程指示域用于指示进程1，2，3，那么终端设备在接收到该DCI后，会在PUCCH 2上发送当前调度(HARQ进程4，5，6)的ACK/NACK以及之前传输失败(进程1，2，3)的ACK/NACK。
本公开实施例中，第二HARQ进程指示域中可以包括：第二ACK/NACK对应的HARQ进程比特位图(bitmap)，例如，图2所示的实例中，进程比特 位图为1110000000000000，代表HARQ进程1，2，3；此外，考虑到bitmap用于指示需反馈的HARQ进程ID，此时可以连通当前调度的一同指示，例如，图2所示的实例中，进程比特位图为1111110000000000，代表HARQ进程1，2，3，4，5，6。
本公开实施例中，在终端设备中的HARQ进程总数为16的情况下，如果想要获得完全的灵活性，那么需要在DCI中增加16比特(bit)的bitmap指示域，来指示是否需要在传输基于最新接收到的TB生成的ACK/NACK的同时，一同传输之前未传输或传输失败的ACK/NACK。
本公开实施例中，为了降低DCI中bit的开销，可以对HARQ进程进行分组，此时，第二HARQ进程指示域中可以包括：第二ACK/NACK对应的HARQ进程分组标识。
在一个例子中，终端设备中的HARQ进程总数为16，例如，如果将HARQ进程分为2组，那么第二HARQ进程指示域中包括2bit，1bit用于指示HARQ进程ID为1-8，另一bit用于指示HARQ进程ID为9-16，这样实现HARQ进程的指示只需2bit。如果第二HARQ进程指示域中为：10，那么终端设备在传输基于最新接收到的TB生成的ACK/NACK的同时，额外一并传输HARQ进程1-8对应的ACK/NACK。可选地，也可以进行更精细化分组，例如，可以分为4组，用4bit指示，即每组的HARQ进程ID分别为1-4，5-8，9-12，13-16。
本公开实施例中，可以限制NR-U场景中的终端设备只使用部分HARQ进程，具体的，可以限制NR-U场景中终端设备使用的HARQ进程的数目，以降低DCI中bit的开销，此时，在上述步骤101之前还可以增加以下步骤：
接收无线资源控制(Radio Resource Control，RRC)信令，其中，RRC信令用于配置终端设备中可用的HARQ进程的个数，可用的HARQ进程的个数大于或等于2；根据RRC信令，设置终端设备中可用的HARQ进程的个数。
本公开实施例中，可用的HARQ进程指的是终端设备中可以用于缓存TB的HARQ进程，终端设备会针对可用的HARQ进程中缓存的TB生成ACK/NACK。
在一个例子中，例如，可以设置终端设备只使用ID为1-8的HARQ进程，这样DCI中只需增加8bit的bitmap第二HARQ进程指示域。
二、隐式指示的方式：
本公开实施例中，可以通过DCI所在的PDCCH资源，指示终端设备同时反馈第一ACK/NACK和第二ACK/NACK，此时，DCI所在PDCCH的相关信息与HARQ进程存在映射关系，该映射关系可以由网络配置；第二ACK/NACK对应的HARQ进程为目标DCI所在PDCCH的相关信息对应的HARQ进程。
可选地，本公开实施例中，PDCCH的相关信息可以包括：目标控制资源集(CORESET)的标识，其中，目标CORESET为PDCCH相对应的CORESET，PDCCH相对应的CORESET指的是PDCCH所在的CORESET。也就是说，DCI所在PDCCH相对应的CORESETID与HARQ进程存在映射关系。
在一个例子中，该映射关系可以包括：奇数的CORESET ID对应HARQ进程1-8，偶数的CORESET ID对应HARQ进程9-16；或者，该映射关系可以包括：模3为0的CORESET ID对应只反馈第一ACK/NACK(即基于最新接收到的TB生成的ACK/NACK)，模3为1的CORESET ID对应反馈第一ACK/NACK和相应于HARQ进程1-8的第二ACK/NACK，模3为2的CORESET ID对应反馈第一ACK/NACK和相应于HARQ进程9-16的第二ACK/NACK。
可选地，本公开实施例中，PDCCH的相关信息可以包括：目标搜索空间(search space)的标识，其中，目标search space为PDCCH相对应的search space，PDCCH相对应的search space指的是PDCCH所在的search space。也就是说，DCI所在PDCCH相对应的search space ID与HARQ进程存在映射关系。
在一个例子中，该映射关系可以包括：奇数的search space ID对应HARQ进程1-8，偶数的search space ID对应HARQ进程9-16；或者，该映射关系可以包括：模3为0的search space ID对应只反馈第一ACK/NACK，模3为1的search space ID对应反馈第一ACK/NACK和相应于HARQ进程1-8的第二ACK/NACK，模3为2的search space ID对应反馈第一ACK/NACK和相 应于HARQ进程9-16的第二ACK/NACK。
可选地，本公开实施例中，PDCCH的相关信息可以包括：目标控制信道单元(Control Channel Element，CCE)的标识，其中，目标CCE为PDCCH的起始CCE。也就是说，DCI所在PDCCH的起始CCE ID与HARQ进程存在映射关系。
在一个例子中，该映射关系可以包括：奇数的CCE ID对应HARQ进程1-8，偶数的CCE ID对应HARQ进程9-16。
可选地，本公开实施例中，PDCCH的相关信息可以包括：PDCCH上承载的DCI中的ACK/NACK资源索引(ARI)信息。也就是说，PDCCH上承载的DCI中的ARI与HARQ进程存在映射关系。
在一个例子中，该映射关系可以包括：ARI使用配置资源总数的前半部分对应HARQ进程1-8，ARI使用配置资源总数的后半部分对应HARQ进程9-16。或者ARI指示配置资源总数前三分之一(下取整)对应只反馈第一ACK/NACK，ARI指示配置资源总数中间三分之一(下取整)对应反馈第一ACK/NACK和相应于HARQ进程1-8的第二ACK/NACK，ARI指示配置资源总数的剩余资源时对应反馈第一ACK/NACK和相应于HARQ进程9-16的第二ACK/NACK。
可选地，本公开实施例中，PDCCH的相关信息可以包括：PDCCH上承载的DCI中的TPC信息。也就是说，DCI中的TPC与HARQ进程存在映射关系。
在一个例子中，该映射关系可以包括：TPC指示0，2对应HARQ进程1-8，TPC指示1，3对应HARQ进程9-16。
可选地，本公开实施例中，PDCCH的相关信息可以包括：PDCCH上承载的DCI的循环冗余校验(Cyclic Redundancy Check，CRC)信息。也就是说，DCI的CRC与HARQ进程存在映射关系。
在一个例子中，相关技术中采用的CRC长度为24bit，终端设备的无线网络临时标识(Radio Network Temporary Identity，RNTI)加扰其中的16bit，还剩余8bit可以使用，此时可以设计一个长为8bit的序列，例如ZC序列，Walsh序列等加扰该8bit，辅助指示不同的分组。如果将HARQ进程分为3 组(例如，HARQ进程1-5，HARQ进程6-10，HARQ进程11-16)，那么可以为终端设备配置4个扰码，终端设备解扰4个扰码获得相应的分组信息，即第二ACK/NACK对应的HARQ进程ID指示信息。例如，采用如下4个扰码进行加扰：
扰码1：[1 1 1 1 1 1 1 1]，指示终端设备只反馈当前传输的TB对应的ACK/NACK；
扰码2：[1 1 -1 -1 1 1 -1 -1]，指示终端设备反馈当前传输的TB对应的ACK/NACK的同时，一并反馈HARQ进程1-5对应的ACK/NACK；
扰码3：[1 1 1 1 -1 -1 -1 -1]，指示终端设备反馈当前传输的TB对应的ACK/NACK的同时，一并反馈HARQ进程6-10对应的ACK/NACK；
扰码4：[1 -1 -1 1 -1 1 1 -1]，指示终端设备反馈当前传输的TB对应的ACK/NACK的同时，一并反馈HARQ进程11-16对应的ACK/NACK。
需要说明的是，上述信息也可以承载在调度PUSCH的PDCCH或在DCI中承载。
需要说明的是，如果额外反馈的HARQ进程ID与当前调度的HARQ ID重合，那么可以规范终端设备不同的处理行为：终端设备在反馈当前调度的HARQ进程ID对应的ACK/NACK的同时，额外反馈的HARQ进程ID对应的ACK/NACK；或者仅反馈额外反馈的HARQ进程ID中不重合部分的ACK/NACK。
在步骤102中，向网络设备发送第一ACK/NACK和第二ACK/NACK。
本公开实施例中，在显式指示的情况下，终端设备在接收到DCI后，根据DCI确定第一ACK/NACK对应的HARQ进程和第二ACK/NACK对应的HARQ进程，再根据所确定的HARQ进程，进一步确定第一ACK/NACK和第二ACK/NACK。
本公开实施例中，在隐式指示的情况下，终端设备在接收到DCI后，根据DCI所在的PDCCH资源的相关信息，确定第二ACK/NACK对应的HARQ进程，再根据该HARQ进程ID确定第二ACK/NACK。
本公开实施例中，可以对第一ACK/NACK和第二ACK/NACK进行联合编码或独立编码。
本公开实施例中，在向网络设备反馈时，可以不对第一ACK/NACK和第二ACK/NACK进行压缩。或者为了降低反馈载荷，可以对第一ACK/NACK和第二ACK/NACK进行压缩，压缩之后再反馈。
本公开实施例中，当第二ACK/NACK为多个时，为降低反馈载荷，可以对不同HARQ进程ID对应的ACK/NACK进行绑定，此时，上述步骤102具体可以包括以下步骤：
对第二ACK/NACK进行绑定(bundling)，得到绑定后的ACK/NACK；向网络设备发送第一ACK/NACK和绑定后的ACK/NACK。
本公开实施例中，绑定方式可以包括：对两个ACK/NACK进行与运算，其中，两个ACK进行与运算，得到一个ACK，两个NACK进行与运算，得到一个NACK，一个ACK和一个NACK进行与运算，得到一个NACK。
在一个例子中，对于HARQ进程1-4，需要反馈4bit的ACK/NACK信息，如果采用绑定方式，对HARQ进程1-2的ACK/NACK进行绑定，形成1bit，对HARQ进程3-4的ACK/NACK进行绑定形成1bit，这样只需额外反馈2bit的ACK/NACK信息。
由上述实施例可见，该实施例中，可以通过DCI指示终端设备在发送当前传输的PDSCH的ACK/NACK的同时，也发送之前未反馈或反馈失败的ACK/NACK，以避免由于终端设备检测信道为忙时无法发送ACK/NACK所引起的PDSCH重传的问题，可以达到节省通信资源和提高数据传输有效性的目的。
图3是本公开的一些实施例提供的HARQ-ACK处理方法的流程图，该方法应用于终端设备，如图3所示，该方法可以包括以下步骤：步骤301和步骤302，其中，
在步骤301中，向终端设备发送目标DCI，其中，目标DCI包含第一HARQ进程指示域和第二HARQ进程指示域，第一HARQ进程指示域用于指示第一ACK/NACK对应的HARQ进程，第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程，第一ACK/NACK为基于当前传输的传输块生成的ACK/NACK，第二ACK/NACK为基于历史传输的传输块生成的ACK/NACK，基于历史传输的传输块生成的ACK/NACK未反馈或反馈失 败。
本公开实施例中，“当前传输的传输块”和“历史传输的传输块”是两个相对的概念，“当前传输的传输块”指的是终端设备最新接收到的TB，“历史传输的传输块”指的是终端设备之前接收到的TB，第一ACK/NACK为：终端设备基于最新接收到的TB生成的ACK/NACK，第二ACK/NACK为：终端设备基于之前接收到的TB生成的ACK/NACK、且该ACK/NACK由于信道为忙而未被反馈或反馈失败。
本公开实施例中，可以通过显式指示的方式，指示终端设备在反馈第一ACK/NACK的同时，一并反馈第二ACK/NACK，即同时向网络设备反馈基于最新接收到的TB生成的ACK/NACK和之前反馈失败的ACK/NACK；或者，也可以通过隐式指示的方式，指示终端设备在反馈第一ACK/NACK的同时，一并反馈第二ACK/NACK，本公开实施例对此不作限定。
首先对显式指示的方式进行详细说明：
相关技术中的DCI仅包含第一HARQ指示域，终端设备在接收到相关技术中的DCI后，只会反馈第一ACK/NACK，而不会反馈第二ACK/NACK，换句话说，终端设备只会向网络设备反馈基于最新接收到的TB生成的ACK/NACK，而不会向网络设备反馈之前反馈失败的ACK/NACK。
为指示终端设备同时反馈第一ACK/NACK和第二ACK/NACK，本公开实施例中，可以在DCI中额外增加一个HARQ进程指示域，即第二HARQ进程指示域，该第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程标识。
本公开实施例中，第二HARQ进程指示域中可以包括：第二ACK/NACK对应的HARQ进程比特位图(bitmap)，例如，图2所示的实例中，进程比特位图为1110000000000000，代表HARQ进程1，2，3；此外，考虑到bitmap用于指示需反馈的HARQ进程ID，此时可以连通当前调度的一同指示，例如，图2所示的实例中，进程比特位图为1111110000000000，代表HARQ进程1，2，3，4，5，6。
本公开实施例中，在终端设备中的HARQ进程总数为16的情况下，如果想要获得完全的灵活性，那么需要在DCI中增加16比特(bit)的bitmap 指示域，来指示是否需要在传输基于最新接收到的TB生成的ACK/NACK的同时，一同传输之前未传输或传输失败的ACK/NACK。
本公开实施例中，为了降低DCI中bit的开销，可以对HARQ进程进行分组，此时，第二HARQ进程指示域中可以包括：第二ACK/NACK对应的HARQ进程分组标识。
在一个例子中，终端设备中的HARQ进程总数为16，例如，如果将HARQ进程分为2组，那么第二HARQ进程指示域中包括2bit，1bit用于指示HARQ进程ID为1-8，另一bit用于指示HARQ进程ID为9-16，这样实现HARQ进程的指示只需2bit。如果第二HARQ进程指示域中为：10，那么终端设备在传输基于最新接收到的TB生成的ACK/NACK的同时，额外一并传输HARQ进程1-8对应的ACK/NACK。可选地，也可以进行更精细化分组，例如，可以分为4组，用4bit指示，即每组的HARQ进程ID分别为1-4，5-8，9-12，13-16。
本公开实施例中，可以限制NR-U场景中的终端设备只使用部分HARQ进程，具体的，可以限制NR-U场景中终端设备使用的HARQ进程的数目，以降低DCI中bit的开销，此时，在上述步骤301之前还可以增加以下步骤：
向终端设备发送RRC信令，其中，RRC信令用于配置终端设备中可用的HARQ进程的个数，可用的HARQ进程的个数大于或等于2。
本公开实施例中，可用的HARQ进程指的是终端设备中可以用于缓存TB的HARQ进程，终端设备会针对可用的HARQ进程中缓存的TB生成ACK/NACK。
在一个例子中，例如，可以设置终端设备只使用ID为1-8的HARQ进程，这样DCI中只需增加8bit的bitmap第二HARQ进程指示域。
接下来对隐式指示的方式进行详细说明：
本公开实施例中，可以通过DCI所在的PDCCH资源，指示终端设备同时反馈第一ACK/NACK和第二ACK/NACK，此时，DCI所在PDCCH的相关信息与HARQ进程存在映射关系，该映射关系可以由网络配置；第二ACK/NACK对应的HARQ进程为目标DCI所在PDCCH的相关信息对应的HARQ进程。
本公开实施例中，PDCCH的相关信息可以包括：目标控制资源集(CORESET)的标识，其中，目标CORESET为PDCCH相对应的CORESET，PDCCH相对应的CORESET指的是PDCCH所在的CORESET。也就是说，DCI所在PDCCH相对应的CORESET ID与HARQ进程存在映射关系。
在一个例子中，该映射关系可以包括：奇数的CORESET ID对应HARQ进程1-8，偶数的CORESET ID对应HARQ进程9-16；或者，该映射关系可以包括：模3为0的CORESET ID对应只反馈第一ACK/NACK(即基于最新接收到的TB生成的ACK/NACK)，模3为1的CORESET ID对应反馈第一ACK/NACK和相应于HARQ进程1-8的第二ACK/NACK，模3为2的CORESET ID对应反馈第一ACK/NACK和相应于HARQ进程9-16的第二ACK/NACK。
可选地，本公开实施例中，PDCCH的相关信息可以包括：目标搜索空间(search space)的标识，其中，目标search space为PDCCH相对应的search space，PDCCH相对应的search space指的是PDCCH所在的search space。也就是说，DCI所在PDCCH相对应的search space ID与HARQ进程存在映射关系。
在一个例子中，该映射关系可以包括：奇数的search space ID对应HARQ进程1-8，偶数的search space ID对应HARQ进程9-16；或者，该映射关系可以包括：模3为0的search space ID对应只反馈第一ACK/NACK，模3为1的search space ID对应反馈第一ACK/NACK和相应于HARQ进程1-8的第二ACK/NACK，模3为2的search space ID对应反馈第一ACK/NACK和相应于HARQ进程9-16的第二ACK/NACK。
可选地，本公开实施例中，PDCCH的相关信息可以包括：目标控制信道单元(Control Channel Element，CCE)的标识，其中，目标CCE为PDCCH的起始CCE。也就是说，DCI所在PDCCH的起始CCE ID与HARQ进程存在映射关系。
在一个例子中，该映射关系可以包括：奇数的CCE ID对应HARQ进程1-8，偶数的CCE ID对应HARQ进程9-16。
可选地，本公开实施例中，PDCCH的相关信息可以包括：PDCCH上承 载的DCI中的ACK/NACK资源索引(ARI)信息。也就是说，PDCCH上承载的DCI中的ARI与HARQ进程存在映射关系。
在一个例子中，该映射关系可以包括：ARI使用配置资源总数的前半部分对应HARQ进程1-8，ARI使用配置资源总数的后半部分对应HARQ进程9-16。或者ARI指示配置资源总数前三分之一(下取整)对应只反馈第一ACK/NACK，ARI指示配置资源总数中间三分之一(下取整)对应反馈第一ACK/NACK和相应于HARQ进程1-8的第二ACK/NACK，ARI指示配置资源总数的剩余资源时对应反馈第一ACK/NACK和相应于HARQ进程9-16的第二ACK/NACK。
可选地，本公开实施例中，PDCCH的相关信息可以包括：PDCCH上承载的DCI中的TPC信息。也就是说，DCI中的TPC与HARQ进程存在映射关系。
在一个例子中，该映射关系可以包括：TPC指示0，2对应HARQ进程1-8，TPC指示1，3对应HARQ进程9-16。
可选地，本公开实施例中，PDCCH的相关信息可以包括：PDCCH上承载的DCI的循环冗余校验(Cyclic Redundancy Check，CRC)信息。也就是说，DCI的CRC与HARQ进程存在映射关系。
在一个例子中，相关技术中采用的CRC长度为24bit，终端设备的无线网络临时标识(Radio Network Temporary Identity，RNTI)加扰其中的16bit，还剩余8bit可以使用，此时可以设计一个长为8bit的序列，例如ZC序列，Walsh序列等加扰该8bit，辅助指示不同的分组。如果将HARQ进程分为3组(例如，HARQ进程1-5，HARQ进程6-10，HARQ进程11-16)，那么可以为终端设备配置4个扰码，终端设备解扰4个扰码获得相应的分组信息，即第二ACK/NACK对应的HARQ进程ID指示信息。例如，采用如下4个扰码进行加扰：
扰码1：[1 1 1 1 1 1 1 1]，指示终端设备只反馈当前传输的TB对应的ACK/NACK；
扰码2：[1 1 -1 -1 1 1 -1 -1]，指示终端设备反馈当前传输的TB对应的ACK/NACK的同时，一并反馈HARQ进程1-5对应的ACK/NACK；
扰码3：[1 1 1 1 -1 -1 -1 -1]，指示终端设备反馈当前传输的TB对应的ACK/NACK的同时，一并反馈HARQ进程6-10对应的ACK/NACK；
扰码4：[1 -1 -1 1 -1 1 1 -1]，指示终端设备反馈当前传输的TB对应的ACK/NACK的同时，一并反馈HARQ进程11-16对应的ACK/NACK。
需要说明的是，上述信息也可以承载在调度PUSCH的PDCCH或在DCI中承载。
需要说明的是，如果额外反馈的HARQ进程ID与当前调度的HARQ ID重合，那么可以规范终端设备不同的处理行为：终端设备在反馈当前调度的HARQ进程ID对应的ACK/NACK的同时，额外反馈的HARQ进程ID对应的ACK/NACK；或者仅反馈额外反馈的HARQ进程ID中不重合部分的ACK/NACK。
在步骤302中，接收来自终端设备的第一ACK/NACK和第二ACK/NACK。
本公开实施例中，终端设备发送的第一ACK/NACK和第二ACK/NACK可以为联合编码或独立编码。
本公开实施例中，在向网络设备反馈时，终端设备可以不对第一ACK/NACK和第二ACK/NACK进行压缩，此时，网络设备接收到的ACK/NACK未被压缩。或者为了降低反馈载荷，终端设备可以对第一ACK/NACK和第二ACK/NACK进行压缩，压缩之后再反馈，此时，网络设备接收到的ACK/NACK已被压缩。
本公开实施例中，当第二ACK/NACK为多个时，为降低反馈载荷，终端设备可以对不同HARQ进程ID对应的ACK/NACK进行绑定(bundling)，具体的，对第二ACK/NACK进行绑定，得到绑定后的ACK/NACK；向网络设备发送第一ACK/NACK和绑定后的ACK/NACK。相应的，网络设备接收到第一ACK/NACK和绑定后的ACK/NACK。
本公开实施例中，绑定方式可以包括：对两个ACK/NACK进行与运算，其中，两个ACK进行与运算，得到一个ACK，两个NACK进行与运算，得到一个NACK，一个ACK和一个NACK进行与运算，得到一个NACK。
在一个例子中，对于HARQ进程1-4，需要反馈4bit的ACK/NACK信息，如果采用绑定方式，对HARQ进程1-2的ACK/NACK进行绑定，形成 1bit，对HARQ进程3-4的ACK/NACK进行绑定形成1bit，这样只需额外反馈2bit的ACK/NACK信息。
由上述实施例可见，该实施例中，可以通过DCI指示终端设备在发送当前传输的PDSCH的ACK/NACK的同时，也发送之前未反馈或反馈失败的ACK/NACK，以避免由于终端设备检测信道为忙时无法发送ACK/NACK所引起的PDSCH重传的问题，可以达到节省通信资源和提高数据传输有效性的目的。
图4是本公开的一些实施例提供的HARQ-ACK处理装置的结构示意图，该HARQ-ACK处理装置应用于终端设备，如图4所示，HARQ-ACK处理装置400可以包括：第一接收模块401和第一发送模块402，其中，
第一接收模块401，用于接收目标DCI，其中，所述目标DCI包含第一HARQ进程指示域和第二HARQ进程指示域，所述第一HARQ进程指示域用于指示第一ACK/NACK对应的HARQ进程，所述第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程，所述第一ACK/NACK为基于当前传输的传输块生成的ACK/NACK，所述第二ACK/NACK为基于历史传输的传输块生成的ACK/NACK，所述基于历史传输的传输块生成的ACK/NACK未反馈或反馈失败；
第一发送模块402，用于向网络设备发送所述第一ACK/NACK和所述第二ACK/NACK。
由上述实施例可见，该实施例中，可以通过DCI指示终端设备在发送当前传输的PDSCH的ACK/NACK的同时，也发送之前未反馈或反馈失败的ACK/NACK，以避免由于终端设备检测信道为忙时无法发送ACK/NACK所引起的PDSCH重传的问题，可以达到节省通信资源和提高数据传输有效性的目的。
可选地，作为示例，所述第二HARQ进程指示域用于指示所述第二ACK/NACK对应的HARQ进程标识。
可选地，作为示例，所述第二HARQ进程指示域中包括下述任一项：
所述第二ACK/NACK对应的HARQ进程比特位图，以及所述第二ACK/NACK对应的HARQ进程分组标识。
可选地，作为示例，HARQ-ACK处理装置400，还可以包括：
第二接收模块，用于接收无线资源控制RRC信令，其中，所述RRC信令用于配置所述终端设备中可用的HARQ进程的个数，所述可用的HARQ进程的个数大于或等于2；
设置模块，用于根据所述RRC信令，设置所述终端设备中可用的HARQ进程的个数。
可选地，作为示例，DCI所在物理下行控制信道PDCCH的相关信息与HARQ进程存在映射关系；
所述第二ACK/NACK对应的HARQ进程为所述目标DCI所在PDCCH的相关信息对应的HARQ进程。
可选地，作为示例，所述PDCCH的相关信息包括下述至少一项：
目标控制资源集CORESET的标识、目标搜索空间search space的标识、目标控制信道单元CCE的标识、所述PDCCH上承载的DCI中的ACK/NACK资源索引ARI信息、所述PDCCH上承载的DCI中传输功率控制TPC信息和所述PDCCH上承载的DCI的循环冗余校验CRC信息；
其中，目标CORESET为所述PDCCH相对应的CORESET，目标search space为所述PDCCH相对应的search space，目标CCE为所述PDCCH的起始CCE。
可选地，作为示例，所述第二ACK/NACK为多个；所述第一发送模块402可以包括：
绑定子模块，用于对所述第二ACK/NACK进行绑定，得到绑定后的ACK/NACK；
发送子模块，用于向网络设备发送所述第一ACK/NACK和所述绑定后的ACK/NACK。
图5是本公开的另一些实施例提供的HARQ-ACK处理装置的结构示意图，该HARQ-ACK处理装置应用于网络设备，如图5所示，HARQ-ACK处理装置500可以包括：第二发送模块501和第三接收模块502，其中，
第二发送模块501，用于向终端设备发送目标DCI，其中，所述目标DCI包含第一HARQ进程指示域和第二HARQ进程指示域，所述第一HARQ进 程指示域用于指示第一ACK/NACK对应的HARQ进程，所述第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程，所述第一ACK/NACK为基于当前传输的传输块生成的ACK/NACK，所述第二ACK/NACK为基于历史传输的传输块生成的ACK/NACK，所述基于历史传输的传输块生成的ACK/NACK未反馈或反馈失败；
第三接收模块502，用于接收来自所述终端设备的所述第一ACK/NACK和所述第二ACK/NACK。
由上述实施例可见，该实施例中，可以通过DCI指示终端设备在发送当前传输的PDSCH的ACK/NACK的同时，也发送之前未反馈或反馈失败的ACK/NACK，以避免由于终端设备检测信道为忙时无法发送ACK/NACK所引起的PDSCH重传的问题，可以达到节省通信资源和提高数据传输有效性的目的。
可选地，作为示例，HARQ-ACK处理装置500，还可以包括：
第三发送模块，用于向所述终端设备发送RRC信令，其中，所述RRC信令用于配置所述终端设备中可用的HARQ进程的个数，所述可用的HARQ进程的个数大于或等于2。
图6是本申请的一些实施例提供的终端设备的结构示意图，如图6所示，终端设备600包括：至少一个处理器601、存储器602、至少一个网络接口604和用户接口603。终端设备600中的各个组件通过总线系统605耦合在一起。可理解，总线系统605用于实现这些组件之间的连接通信。总线系统605除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图6中将各种总线都标为总线系统605。
其中，用户接口603可以包括显示器、键盘或者点击设备(例如，鼠标，轨迹球trackball、触感板、或者触摸屏)等。
可以理解，本申请实施例中的存储器602可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或 闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例描述的系统和方法的存储器602旨在包括但不限于这些和任意其它适合类型的存储器。
在一些实施方式中，存储器602存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：操作系统6021和应用程序6022。
其中，操作系统6021，包含各种系统程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务。应用程序6022，包含各种应用程序，例如媒体播放器(Media Player)、浏览器(Browser)等，用于实现各种应用业务。实现本申请实施例方法的程序可以包含在应用程序6022中。
在本申请实施例中，终端设备600还包括：存储在存储器602上并可在处理器601上运行的计算机程序，该计算机程序被处理器601执行时实现如下步骤：
接收目标下行控制信息DCI，其中，目标DCI包含第一HARQ进程指示域和第二HARQ进程指示域，所述第一HARQ进程指示域用于指示第一ACK/NACK对应的HARQ进程，所述第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程，所述第一ACK/NACK为基于当前传输的传输块生成的ACK/NACK，所述第二ACK/NACK为基于历史传输的传输块生成的ACK/NACK，所述基于历史传输的传输块生成的ACK/NACK未反馈或反馈失败；
向网络设备发送所述第一ACK/NACK和所述第二ACK/NACK。
上述本申请实施例揭示的方法可以应用于处理器601中，或者由处理器601实现。处理器601可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器601中的硬件的集成逻辑电路或者软件形式的指令完成。上述处理器601可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的计算机可读存储介质中。该计算机可读存储介质位于存储器602，处理器601读取存储器602中的信息，结合其硬件完成上述方法的步骤。具体地，该计算机可读存储介质上存储有计算机程序，计算机程序被处理器601执行时实现如上述HARQ-ACK处理方法实施例的各步骤。
可以理解的是，本申请实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processor，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本申请所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本申请实施例所述功能的模块(例如过程、函数等)来实现本申请实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
此外，计算机程序被处理器601执行时还可实现如下步骤：
可选地，作为示例，所述第二HARQ进程指示域用于指示所述第二 ACK/NACK对应的HARQ进程标识。
可选地，作为示例，所述第二HARQ进程指示域中包括下述任一项：
所述第二ACK/NACK对应的HARQ进程比特位图，以及所述第二ACK/NACK对应的HARQ进程分组标识。
可选地，作为示例，在所述接收目标下行控制信息DCI的步骤之前，还包括：
接收无线资源控制RRC信令，其中，所述RRC信令用于配置所述终端设备中可用的HARQ进程的个数，所述可用的HARQ进程的个数大于或等于2；
根据所述RRC信令，设置所述终端设备中可用的HARQ进程的个数。
可选地，作为示例，DCI所在物理下行控制信道PDCCH的相关信息与HARQ进程存在映射关系；
所述第二ACK/NACK对应的HARQ进程为所述目标DCI所在PDCCH的相关信息对应的HARQ进程。
可选地，作为示例，所述PDCCH的相关信息包括下述至少一项：
目标控制资源集CORESET的标识、目标搜索空间search space的标识、目标控制信道单元CCE的标识、所述PDCCH上承载的DCI中的ACK/NACK资源索引ARI信息、所述PDCCH上承载的DCI中传输功率控制TPC信息和所述PDCCH上承载的DCI的循环冗余校验CRC信息；
其中，目标CORESET为所述PDCCH相对应的CORESET，目标search space为所述PDCCH相对应的search space，目标CCE为所述PDCCH的起始CCE。
可选地，作为示例，所述第二ACK/NACK为多个；所述向网络设备发送所述第一ACK/NACK和所述第二ACK/NACK，包括：
对所述第二ACK/NACK进行绑定，得到绑定后的ACK/NACK；
向网络设备发送所述第一ACK/NACK和所述绑定后的ACK/NACK。
终端设备600能够实现前述实施例中终端设备实现的各个过程，为避免重复，这里不再赘述。
图7是本公开的一些实施例提供的网络设备的结构示意图，如图7所示， 网络设备700包括：处理器701、收发机702、存储器703、用户接口704和总线接口，其中：
在本公开实施例中，网络设备700还包括：存储在存储器上703并可在处理器701上运行的计算机程序，计算机程序被处理器701执行时实现如下步骤：
向终端设备发送目标DCI，其中，所述目标DCI包含第一HARQ进程指示域和第二HARQ进程指示域，所述第一HARQ进程指示域用于指示第一ACK/NACK对应的HARQ进程，所述第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程，所述第一ACK/NACK为基于当前传输的传输块生成的ACK/NACK，所述第二ACK/NACK为基于历史传输的传输块生成的ACK/NACK，所述基于历史传输的传输块生成的ACK/NACK未反馈或反馈失败；
接收来自所述终端设备的所述第一ACK/NACK和所述第二ACK/NACK。
在图7中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器701代表的一个或多个处理器和存储器703代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机702可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。针对不同的用户设备，用户接口704还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器701负责管理总线架构和通常的处理，存储器703可以存储处理器701在执行操作时所使用的数据。
本公开实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述应用于终端设备的HARQ-ACK处理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本公开实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述应用于网络设备 的HARQ-ACK处理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本公开实施例还提供一种包括指令的计算机程序产品，当计算机运行所述计算机程序产品的所述指令时，所述计算机执行上述应用于终端设备的HARQ-ACK处理方法。具体地，该计算机程序产品可以运行于上述终端设备上。
本公开实施例还提供一种包括指令的计算机程序产品，当计算机运行所述计算机程序产品的所述指令时，所述计算机执行上述应用于网络设备的HARQ-ACK处理方法。具体地，该计算机程序产品可以运行于上述网络设备上。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本公开所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方， 或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (22)

  1. 一种混合自动重传请求反馈信息HARQ-ACK处理方法，应用于终端设备，包括：
    接收目标下行控制信息DCI，其中，目标DCI包含第一HARQ进程指示域和第二HARQ进程指示域，所述第一HARQ进程指示域用于指示第一ACK/NACK对应的HARQ进程，所述第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程，所述第一ACK/NACK为基于当前传输的传输块生成的ACK/NACK，所述第二ACK/NACK为基于历史传输的传输块生成的ACK/NACK，所述基于历史传输的传输块生成的ACK/NACK未反馈或反馈失败；
    向网络设备发送所述第一ACK/NACK和所述第二ACK/NACK。
  2. 根据权利要求1所述的方法，其中，所述第二HARQ进程指示域用于指示所述第二ACK/NACK对应的HARQ进程标识。
  3. 根据权利要求2所述的方法，其中，所述第二HARQ进程指示域中包括下述任一项：
    所述第二ACK/NACK对应的HARQ进程比特位图，以及所述第二ACK/NACK对应的HARQ进程分组标识。
  4. 根据权利要求2所述的方法，在所述接收目标下行控制信息DCI的步骤之前，还包括：
    接收无线资源控制RRC信令，其中，所述RRC信令用于配置所述终端设备中可用的HARQ进程的个数，所述可用的HARQ进程的个数大于或等于2；
    根据所述RRC信令，设置所述终端设备中可用的HARQ进程的个数。
  5. 根据权利要求1所述的方法，其中，DCI所在物理下行控制信道PDCCH的相关信息与HARQ进程存在映射关系；
    所述第二ACK/NACK对应的HARQ进程为所述目标DCI所在PDCCH的相关信息对应的HARQ进程。
  6. 根据权利要求5所述的方法，其中，所述PDCCH的相关信息包括下 述至少一项：
    目标控制资源集CORESET的标识、目标搜索空间search space的标识、目标控制信道单元CCE的标识、所述PDCCH上承载的DCI中的ACK/NACK资源索引ARI信息、所述PDCCH上承载的DCI中传输功率控制TPC信息和所述PDCCH上承载的DCI的循环冗余校验CRC信息；
    其中，目标CORESET为所述PDCCH相对应的CORESET，目标search space为所述PDCCH相对应的search space，目标CCE为所述PDCCH的起始CCE。
  7. 根据权利要求1所述的方法，其中，所述第二ACK/NACK为多个；所述向网络设备发送所述第一ACK/NACK和所述第二ACK/NACK，包括：
    对所述第二ACK/NACK进行绑定，得到绑定后的ACK/NACK；
    向网络设备发送所述第一ACK/NACK和所述绑定后的ACK/NACK。
  8. 一种HARQ-ACK处理方法，应用于网络设备，包括：
    向终端设备发送目标DCI，其中，所述目标DCI包含第一HARQ进程指示域和第二HARQ进程指示域，所述第一HARQ进程指示域用于指示第一ACK/NACK对应的HARQ进程，所述第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程，所述第一ACK/NACK为基于当前传输的传输块生成的ACK/NACK，所述第二ACK/NACK为基于历史传输的传输块生成的ACK/NACK，所述基于历史传输的传输块生成的ACK/NACK未反馈或反馈失败；
    接收来自所述终端设备的所述第一ACK/NACK和所述第二ACK/NACK。
  9. 根据权利要求8所述的方法，在所述向终端设备发送目标DCI的步骤之前，还包括：
    向所述终端设备发送RRC信令，其中，所述RRC信令用于配置所述终端设备中可用的HARQ进程的个数，所述可用的HARQ进程的个数大于或等于2。
  10. 一种HARQ-ACK处理装置，应用终端设备，包括：
    第一接收模块，用于接收目标DCI，其中，所述目标DCI包含第一HARQ进程指示域和第二HARQ进程指示域，所述第一HARQ进程指示域用于指 示第一ACK/NACK对应的HARQ进程，所述第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程，所述第一ACK/NACK为基于当前传输的传输块生成的ACK/NACK，所述第二ACK/NACK为基于历史传输的传输块生成的ACK/NACK，所述基于历史传输的传输块生成的ACK/NACK未反馈或反馈失败；
    第一发送模块，用于向网络设备发送所述第一ACK/NACK和所述第二ACK/NACK。
  11. 根据权利要求10所述的装置，其中，所述第二HARQ进程指示域用于指示所述第二ACK/NACK对应的HARQ进程标识。
  12. 根据权利要求11所述的装置，其中，所述第二HARQ进程指示域中包括下述任一项：
    所述第二ACK/NACK对应的HARQ进程比特位图，以及所述第二ACK/NACK对应的HARQ进程分组标识。
  13. 根据权利要求11所述的装置，还包括：
    第二接收模块，用于接收无线资源控制RRC信令，其中，所述RRC信令用于配置所述终端设备中可用的HARQ进程的个数，所述可用的HARQ进程的个数大于或等于2；
    设置模块，用于根据所述RRC信令，设置所述终端设备中可用的HARQ进程的个数。
  14. 根据权利要求10所述的装置，其中，DCI所在物理下行控制信道PDCCH的相关信息与HARQ进程存在映射关系；
    所述第二ACK/NACK对应的HARQ进程为所述目标DCI所在PDCCH的相关信息对应的HARQ进程。
  15. 根据权利要求14所述的装置，其中，所述PDCCH的相关信息包括下述至少一项：
    目标控制资源集CORESET的标识、目标搜索空间search space的标识、目标控制信道单元CCE的标识、所述PDCCH上承载的DCI中的ACK/NACK资源索引ARI信息、所述PDCCH上承载的DCI中传输功率控制TPC信息和所述PDCCH上承载的DCI的循环冗余校验CRC信息；
    其中，目标CORESET为所述PDCCH相对应的CORESET，目标search space为所述PDCCH相对应的search space，目标CCE为所述PDCCH的起始CCE。
  16. 根据权利要求10所述的装置，其中，所述第二ACK/NACK为多个；所述第一发送模块包括：
    绑定子模块，用于对所述第二ACK/NACK进行绑定，得到绑定后的ACK/NACK；
    发送子模块，用于向网络设备发送所述第一ACK/NACK和所述绑定后的ACK/NACK。
  17. 一种HARQ-ACK处理装置，应用于网络设备，包括：
    第二发送模块，用于向终端设备发送目标DCI，其中，所述目标DCI包含第一HARQ进程指示域和第二HARQ进程指示域，所述第一HARQ进程指示域用于指示第一ACK/NACK对应的HARQ进程，所述第二HARQ进程指示域用于指示第二ACK/NACK对应的HARQ进程，所述第一ACK/NACK为基于当前传输的传输块生成的ACK/NACK，所述第二ACK/NACK为基于历史传输的传输块生成的ACK/NACK，所述基于历史传输的传输块生成的ACK/NACK未反馈或反馈失败；
    第三接收模块，用于接收来自所述终端设备的所述第一ACK/NACK和所述第二ACK/NACK。
  18. 根据权利要求17所述的装置，还包括：
    第三发送模块，用于向所述终端设备发送RRC信令，其中，所述RRC信令用于配置所述终端设备中可用的HARQ进程的个数，所述可用的HARQ进程的个数大于或等于2。
  19. 一种终端设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至7中任一项所述的HARQ-ACK处理方法的步骤。
  20. 一种网络设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求8或9中任一项所述的HARQ-ACK处理方法的步骤。
  21. 一种计算机可读存储介质，存储计算机程序，所述计算机程序被处理器执行时实现如权利要求1至7中任一项所述的HARQ-ACK处理方法的步骤。
  22. 一种计算机可读存储介质，存储计算机程序，所述计算机程序被处理器执行时实现如权利要求8或9所述的HARQ-ACK处理方法的步骤。
PCT/CN2019/090658 2018-06-21 2019-06-11 混合自动重传请求反馈信息harq-ack处理方法及装置 WO2019242527A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810641481.2 2018-06-21
CN201810641481.2A CN110635868B (zh) 2018-06-21 2018-06-21 混合自动重传请求反馈信息harq-ack处理方法及装置

Publications (1)

Publication Number Publication Date
WO2019242527A1 true WO2019242527A1 (zh) 2019-12-26

Family

ID=68966195

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/090658 WO2019242527A1 (zh) 2018-06-21 2019-06-11 混合自动重传请求反馈信息harq-ack处理方法及装置

Country Status (2)

Country Link
CN (1) CN110635868B (zh)
WO (1) WO2019242527A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220078827A1 (en) * 2018-12-29 2022-03-10 Beijing Unisoc Communications Technology Co., Ltd. Downlink data scheduling harq-ack codebook feedback and generation methods and devices, and medium

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7466662B2 (ja) * 2020-02-14 2024-04-12 オッポ広東移動通信有限公司 ハイブリッド自動再送要求応答コードブックの決定方法、装置及びそのデバイス
WO2021163968A1 (zh) * 2020-02-20 2021-08-26 Oppo广东移动通信有限公司 用于确定混合自动重传请求信息的方法、终端设备和网络设备
CN113518350A (zh) * 2020-04-09 2021-10-19 维沃移动通信有限公司 调度方法和设备
CN115118389A (zh) * 2021-03-17 2022-09-27 上海推络通信科技合伙企业(有限合伙) 一种用于无线通信的节点中的方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106160950A (zh) * 2015-04-08 2016-11-23 普天信息技术有限公司 一种基于载波聚合的信息反馈方法及系统
CN106559187A (zh) * 2015-09-25 2017-04-05 北京三星通信技术研究有限公司 Harq-ack信息的反馈和接收方法及设备
WO2017171299A1 (en) * 2016-04-01 2017-10-05 Samsung Electronics Co., Ltd. Method and apparatus for feeding back harq-ack information
US20180131473A1 (en) * 2015-04-09 2018-05-10 Samsung Electronics Co., Ltd. Method for supporting harq in communication system using unlicensed frequency band and device having applied same

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102208967B (zh) * 2010-03-31 2014-04-09 中兴通讯股份有限公司 一种lte终端非自适应重传功率控制的方法及装置
CN101841403B (zh) * 2010-05-26 2013-05-08 新邮通信设备有限公司 数据传输方法和系统
US8848591B2 (en) * 2012-02-27 2014-09-30 Futurewei Technologies, Inc. System and method for message acknowledgment feedback for device-to-device communication overlaid on a cellular network
US10616886B2 (en) * 2015-08-25 2020-04-07 Idac Holdings, Inc. Framing, scheduling, and synchronization in wireless systems
CN106612557B (zh) * 2015-10-26 2020-02-18 中国移动通信集团公司 下行ack/nack信息的传输方法、基站及用户设备
CN107294663B (zh) * 2016-03-31 2020-07-21 展讯通信（上海）有限公司 上行传输的harq反馈方法、装置及接收方法
CN108023685B (zh) * 2016-11-03 2021-02-12 华为技术有限公司 混合自动重传harq切换方法及终端

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106160950A (zh) * 2015-04-08 2016-11-23 普天信息技术有限公司 一种基于载波聚合的信息反馈方法及系统
US20180131473A1 (en) * 2015-04-09 2018-05-10 Samsung Electronics Co., Ltd. Method for supporting harq in communication system using unlicensed frequency band and device having applied same
CN106559187A (zh) * 2015-09-25 2017-04-05 北京三星通信技术研究有限公司 Harq-ack信息的反馈和接收方法及设备
WO2017171299A1 (en) * 2016-04-01 2017-10-05 Samsung Electronics Co., Ltd. Method and apparatus for feeding back harq-ack information

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220078827A1 (en) * 2018-12-29 2022-03-10 Beijing Unisoc Communications Technology Co., Ltd. Downlink data scheduling harq-ack codebook feedback and generation methods and devices, and medium

Also Published As

Publication number Publication date
CN110635868A (zh) 2019-12-31
CN110635868B (zh) 2021-02-09

Similar Documents

Publication Publication Date Title
WO2019242527A1 (zh) 混合自动重传请求反馈信息harq-ack处理方法及装置
US20210091893A1 (en) Information Transmission Method and Communications Device
US20220224452A1 (en) Feedback Information Transmission Method and Apparatus
US11949514B2 (en) Method and apparatus for generating hybrid automatic repeat request HARQ information
WO2018201829A1 (zh) 一种传输方法、终端设备及基站
TWI741147B (zh) 傳輸回饋訊息的方法和終端設備
WO2022104519A1 (zh) 一种数据传输方法、设备及存储介质
US20210160839A1 (en) Communication method and communications apparatus
CN110730513B (zh) 一种通信方法及装置
WO2021159857A1 (zh) 码本传输方法及装置
WO2021147864A1 (zh) 确定旁链路反馈信息的方法和通信设备
WO2019242526A1 (zh) 上行控制信息发送方法、终端设备和网络侧设备
US10979171B2 (en) Data transmission method, network device, and terminal device
KR102317852B1 (ko) 데이터 손상 여부를 결정하기 위한 방법 및 장치
CN113661761A (zh) 发送、接收反馈信息的方法和设备
WO2019191939A1 (zh) 一种信道资源的确定方法、设备及计算机存储介质
WO2022078283A1 (zh) 信息传输、资源指示方法、装置、终端及网络侧设备
WO2021238941A1 (zh) Harq-ack反馈方法、终端设备和网络设备
WO2019228241A1 (zh) 信号处理的方法和装置
CN113892243A (zh) 对通过无线接入网络中的非授权频段信道进行的下行链路数据接收在上行链路上进行确认传输的方法、用户设备和基站
CN113141237B (zh) 上行资源的确定方法和通信设备
WO2022151073A1 (zh) 上行确认信息的传输方法及装置
US20240014943A1 (en) Network coding with hybrid automatic repeat request process
WO2020220317A1 (zh) 一种混合自动重传请求确认的传输方法、设备及存储介质
WO2021092949A1 (zh) 无线通信的方法和终端设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19822702

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19822702

Country of ref document: EP

Kind code of ref document: A1