CN114762264A

CN114762264A - Method and terminal equipment for generating hybrid automatic repeat request response codebook

Info

Publication number: CN114762264A
Application number: CN202080082145.4A
Authority: CN
Inventors: 吴作敏
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-03-03
Filing date: 2020-03-06
Publication date: 2022-07-15
Anticipated expiration: 2040-03-06
Also published as: CN114762264B; WO2021174557A1

Abstract

The embodiment of the application relates to a method and terminal equipment for generating a HARQ-ACK codebook. The method comprises the following steps: the terminal equipment receives a first downlink control information DCI format, the first DCI format schedules a first PUSCH for transmission, the first DCI format comprises an uplink DAI domain, a first HARQ-ACK codebook is multiplexed and transmitted in the first PUSCH, and the terminal equipment is configured with an eType-2 HARQ-ACK codebook; the terminal equipment generates a first HARQ-ACK codebook according to the uplink DAI domain, wherein the first HARQ-ACK codebook comprises first HARQ-ACK information, or the first HARQ-ACK codebook does not comprise the first HARQ-ACK information, and the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one PDSCH scheduled by DCI format 1_ 0. The method and the device are used for avoiding the problem of determining the HARQ-ACK codebook.

Description

Method and terminal equipment for generating hybrid automatic repeat request response codebook

The present application claims priority from chinese patent application entitled "method and terminal apparatus for generating hybrid automatic repeat request response codebook" filed by chinese patent office on 03/2020 and having application number 202010140791.3, which is incorporated herein by reference in its entirety.

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and a terminal device for generating a hybrid automatic repeat request response.

Background

In order to improve the reliability of communication, a retransmission mechanism is provided between the network device and the terminal device, where the retransmission mechanism includes a Hybrid Automatic Repeat Request (HARQ) mechanism. When the HARQ retransmission mechanism is adopted, the network device needs to indicate or configure the uplink feedback resource for the HARQ feedback information corresponding to the physical downlink channel scheduled by the terminal device, so as to transmit hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback information. In an NR system on an unlicensed spectrum, such as an NR-U system, if a terminal device receives at least one PDSCH which is scheduled by a DCI format 1_0 and does not belong to any group, first HARQ-ACK information corresponding to the at least one PDSCH is indicated to be fed back through a first PUCCH; in addition, the terminal device is scheduled to transmit a first PUSCH, and if the first PUCCH and the first PUSCH at least partially overlap in time domain, the terminal device may multiplex the first HARQ-ACK information onto the first PUSCH for transmission. However, in the NR-U system, the terminal device may be configured with multiple types of HARQ-ACK codebook feedback manners, and it is not yet determined how to determine the HARQ-ACK codebook feedback manner including the first HARQ-ACK information from the multiple types of HARQ-ACK codebook feedback manners configured with the terminal device.

Disclosure of Invention

In view of this, the embodiment of the present application provides a method for generating an HARQ-ACK codebook and a terminal device, which can reasonably and effectively determine the HARQ-ACK codebook.

The embodiment of the application provides a method for generating a HARQ-ACK codebook, which is applied to terminal equipment and comprises the following steps:

a terminal device receives a first downlink control information DCI format, wherein the first DCI format schedules transmission of a first Physical Uplink Shared Channel (PUSCH), the first DCI format comprises an uplink Downlink Allocation Indication (DAI) domain, a first hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook is multiplexed and transmitted in the first PUSCH, and the terminal device is configured with an enhanced type 2 eType-2 HARQ-ACK codebook;

the terminal equipment generates the first HARQ-ACK codebook according to the uplink DAI domain, wherein the first HARQ-ACK codebook comprises first HARQ-ACK information, or the first HARQ-ACK codebook does not comprise the first HARQ-ACK information, wherein the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one Physical Downlink Shared Channel (PDSCH) scheduled by DCI format 1_0, and/or the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one SPS PDSCH which is not scheduled by DCI format, and/or the first HARQ-ACK information comprises ACK feedback information corresponding to at least one SPS PDSCH releasing.

The embodiment of the application provides a method for generating a HARQ-ACK codebook, which is applied to network equipment and comprises the following steps:

configuring an enhanced type 2 eType-2 HARQ-ACK codebook for the terminal equipment;

sending a first DCI format to terminal equipment, wherein the first DCI format schedules PUSCH transmission of a first physical uplink shared channel, the first DCI format comprises an uplink Downlink Allocation Indication (DAI) domain, and a first HARQ-ACK codebook is multiplexed and transmitted in the first PUSCH; the uplink DAI domain is used for generating the first HARQ-ACK codebook, the first HARQ-ACK codebook comprises first HARQ-ACK information, or the first HARQ-ACK codebook does not comprise the first HARQ-ACK information, wherein the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one Physical Downlink Shared Channel (PDSCH) scheduled by DCI format 1_0, and/or the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one SPS PDSCH scheduled without DCI format, and/or the first HARQ-ACK information comprises ACK feedback information corresponding to at least one SPS PDSCH release.

An embodiment of the present application further provides a terminal device, where the terminal device includes:

a first receiving module, configured to receive a configuration signaling, where the configuration signaling is used to configure an enhanced type 2 eType-2 HARQ-ACK codebook;

A second receiving module, configured to receive a first DCI format, where the first DCI format schedules a PUSCH transmission for a first physical uplink shared channel, and the first DCI format includes a DAI field for uplink downlink assignment indication, and the first PUSCH multiplexes and transmits a first HARQ-ACK codebook;

a codebook generating module, configured to generate the first HARQ-ACK codebook according to the uplink DAI field, where the first HARQ-ACK codebook includes first HARQ-ACK information, or the first HARQ-ACK codebook does not include the first HARQ-ACK information, where the first HARQ-ACK information includes HARQ-ACK feedback information corresponding to at least one PDSCH of a DCI format 1_0, and/or the first HARQ-ACK information includes HARQ-ACK feedback information corresponding to at least one SPS PDSCH without DCI format scheduling, and/or the first HARQ-ACK information includes ACK feedback information corresponding to at least one SPS release.

An embodiment of the present application further provides a network device, where the network device includes:

a first sending module, configured to send a configuration signaling, where the configuration signaling is used to configure an enhanced type 2 eType-2 HARQ-ACK codebook;

a second sending module, configured to send a first DCI format, where the first DCI format schedules a first physical uplink shared channel, PUSCH, for transmission, and the first DCI format includes an uplink downlink assignment indication, DAI, field, and a first HARQ-ACK codebook is multiplexed and transmitted in the first PUSCH; the uplink DAI domain is used for generating the first HARQ-ACK codebook, the first HARQ-ACK codebook comprises first HARQ-ACK information, or the first HARQ-ACK codebook does not comprise the first HARQ-ACK information, wherein the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one Physical Downlink Shared Channel (PDSCH) scheduled by DCI format 1_0, and/or the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one SPS PDSCH scheduled without DCI format, and/or the first HARQ-ACK information comprises ACK feedback information corresponding to at least one SPS PDSCH release.

The embodiment of the present application further provides a terminal device, which includes a processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and execute the method for generating the HARQ-ACK codebook.

The embodiment of the present application further provides a network device, which includes a processor and a memory, where the memory is used to store a computer program, and the processor is used to invoke and run the computer program stored in the memory, and execute the method for generating the HARQ-ACK codebook.

The embodiment of the present application further provides a chip, where the chip includes a processor, and is configured to call and run a computer program from a memory, so that a device in which the chip is installed executes the method for generating an HARQ-ACK codebook.

An embodiment of the present application further provides a computer-readable storage medium for storing a computer program, where the computer program enables a computer to execute the method for generating an HARQ-ACK codebook.

An embodiment of the present application further provides a computer program product, which includes computer program instructions, and the computer program instructions enable a computer to execute the method for generating an HARQ-ACK codebook.

The embodiment of the application also provides a computer program, and the computer program enables a computer to execute the method for generating the HARQ-ACK codebook.

According to the method provided in the embodiment of the application, when the terminal device receives at least one PDSCH scheduled by the DCI format 1_0 and HARQ-ACK information corresponding to the at least one PDSCH is fed back through a PUSCH scheduled by the first DCI format, a HARQ-ACK codebook which the terminal device should generate can be determined through uplink DAI indication information in the first DCI format, so that ambiguity of understanding of the HARQ-ACK codebook by the terminal device and the network device is avoided.

Drawings

Fig. 1 is a schematic diagram of an application scenario of an embodiment of the present application.

Fig. 2 is a flowchart illustrating a method for generating a HARQ-ACK codebook according to an embodiment of the present application.

Fig. 3 is a flowchart illustrating another method for generating a HARQ-ACK codebook according to an embodiment of the present application.

Fig. 4 is a schematic structural block diagram of a terminal device according to an embodiment of the present application.

Fig. 5 is a schematic block diagram of a network device according to another embodiment of the present application.

Fig. 6 is a schematic block diagram of a communication device according to an embodiment of the present application.

Fig. 7 is a schematic block diagram of a chip of an embodiment of the present application.

Fig. 8 is a schematic block diagram of a communication system of an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

It should be noted that the terms "first," "second," and the like in the description and claims of the embodiments of the present application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. The objects described in the "first" and "second" may be the same or different.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an Advanced Long Term Evolution (LTE-A) System, a New Radio (NR) System, an Evolution System of an NR System, an LTE (LTE-based Access to unlicensed spectrum, an LTE-U) System, an NR (NR-based Access to unlicensed spectrum, an NR-based network (UMTS-U) System, a Non-Terrestrial communication network (UMTS-based network, UMTS) System, a UMTS-based Mobile communication System, WLAN), Wireless Fidelity (WiFi), next Generation communication (5th-Generation, 5G) system, or other communication systems.

Generally, the conventional Communication system supports a limited number of connections and is easy to implement, however, with the development of Communication technology, the mobile Communication system will support not only conventional Communication but also, for example, Device-to-Device (D2D) Communication, Machine-to-Machine (M2M) Communication, Machine Type Communication (MTC), Vehicle-to-Vehicle (V2V) Communication, or Vehicle-to-Vehicle wireless Communication (V2X), and the embodiments of the present application can also be applied to these Communication systems.

Optionally, the communication system in the embodiment of the present application may be applied to a Carrier Aggregation (CA) scenario, may also be applied to a Dual Connectivity (DC) scenario, and may also be applied to an independent (SA) networking scenario.

The application spectrum is not limited in the embodiments of the present application. For example, the embodiments of the present application may be applied to a licensed spectrum and may also be applied to an unlicensed spectrum. It should be understood that unlicensed spectrum is also referred to as unlicensed spectrum or shared spectrum.

The embodiments of the present application are described in conjunction with a network device and a terminal device, where: a terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, or a User Equipment, etc. The terminal device may be a Station (ST) in a WLAN, and may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, and a next generation communication system, for example, a terminal device in an NR Network or a terminal device in a future evolved Public Land Mobile Network (PLMN) Network, and the like.

By way of example and not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable equipment can also be called wearable intelligent equipment, is the general term of applying wearable technique to carry out intelligent design, develop the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. The wearable device may be worn directly on the body or may be a portable device integrated into the user's clothing or accessory. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.

The network device may be a device for communicating with the mobile device. The network device may be an Access Point (AP) in a WLAN, a Base Transceiver Station (BTS) in GSM or CDMA, a Base Station (NodeB, NB) in WCDMA, an evolved Node B (eNB or eNodeB) in LTE, a relay Station or an Access Point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network or a network device in a PLMN network that is evolved in the future.

The network device may have mobile characteristics, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite, balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a Medium Earth Orbit (MEO) satellite, a Geostationary Earth Orbit (GEO) satellite, a High Elliptical Orbit (HEO) satellite, or the like. Alternatively, the network device may be a base station installed on land, water, or the like.

In this embodiment, a network device provides a service for a Cell (Cell), and a terminal device communicates with the network device through a transmission resource (for example, a frequency domain resource or a frequency spectrum resource) used by the Cell, where the Cell may be a Cell corresponding to the network device (for example, a base station), and the Cell may belong to a macro base station or a base station corresponding to a Small Cell (Small Cell), where the Small Cell may include: urban cells (Metro cells), Micro cells (Micro cells), Pico cells (Pico cells), Femto cells (Femto cells), and the like, wherein the small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-rate data transmission services.

Fig. 1 exemplarily shows one network device 110 and two terminal devices 120, and optionally, the wireless communication system 100 may include a plurality of network devices 110, and each network device 110 may include other numbers of terminal devices 120 within the coverage area, which is not limited in this embodiment.

In addition, the wireless communication system 100 may further include other network entities such as a Mobility Management Entity (MME), an Access and Mobility Management Function (AMF), and the like, which is not limited in the embodiment of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" is used herein to describe the association relationship of the associated objects, for example, it means that there may be three relationships between the associated objects before and after, for example, a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" herein generally indicates a relationship in which the former and latter associated objects are "or".

To better describe the principle and the detailed description of the embodiments of the present application, the following description is provided for the related technical content of the embodiments of the present application. It should be understood that the methods provided by the embodiments of the present application include at least some of the following.

In the information transmission process between the network device and the terminal device, the terminal device sends HARQ response information (also referred to as HARQ-ACK information or HARQ-ACK feedback information) corresponding to a Physical Downlink Shared Channel (PDSCH) after receiving the PDSCH. The HARQ-ACK information is used to characterize whether the decoding of the PDSCH is correct. In some embodiments, the HARQ-ACK information comprises acknowledgement ACK information or negative acknowledgement NACK information.

The network device may schedule PDSCH transmission through Downlink Control Information (DCI), where the DCI includes indication Information of a Physical Uplink Control Channel (PUCCH) resource, and the PUCCH resource may be used to send HARQ-ACK feedback Information corresponding to the PDSCH.

The determination method of the HARQ-ACK codebook (codebook) during the HARQ-ACK information feedback comprises at least One of determination of a Type 1 Type-1 HARQ-ACK codebook (also called semi-static HARQ-ACK codebook or semi-static HARQ-ACK codebook), determination of a Type 2 Type-2 HARQ-ACK codebook (also called dynamic HARQ-ACK codebook or dynamic codebook), determination of an enhanced Type 2 Type-2 HARQ-ACK codebook (also called enhanced dynamic HARQ-ACK codebook or enhanced dynamic codebook) and determination of a Type 3 Type-3 HARQ-ACK codebook (also called One Shot HARQ-ACK codebook or single feedback).

If the terminal equipment is configured with the eType-2 HARQ-ACK codebook, the network equipment can perform grouping on the scheduled PDSCH when the network equipment schedules PDSCH transmission to the terminal equipment by using the DCI format 1_1, and indicate the grouping information of the PDSCH through display signaling, so that the terminal equipment performs corresponding HARQ-ACK feedback according to different groupings after receiving the PDSCH. Or, DCI for scheduling the terminal device to receive the PDSCH includes indication information of a group index (PDSCH group index) and indication information of a new feedback indication nfi (new feedback indicator). In this way the PDSCH can be grouped into at most 2 groups, e.g. group 0 or group 1. When triggering the terminal device to perform HARQ-ACK feedback, the network device may trigger the feedback of one group, or may trigger the feedback of two groups at the same time. Specifically, the DCI information may include an information field (Number of requested PDSCH group (s)) of the Number of feedback request groups. If the terminal device receives DCI information sent by the network device and the information field of the number of feedback request groups in the DCI information is a preset value, for example, set to 1, the terminal device needs to perform HARQ-ACK feedback for two groups.

If the terminal device is configured with the eType-2 HARQ-ACK codebook, when the network device schedules PDSCH transmission to the terminal device using DCI format 1_0, since the DCI format 1_0 does not include the group index and the NFI indication in the scheduling, the DCI format 1_0 scheduling includes two cases:

Case 1: if the UE receives the scheduling of at least one DCI format 1_0 after the last PUCCH transmission opportunity for transmitting the HARQ-ACK feedback information including the group 0 and before the next PUCCH transmission opportunity, and receives the DCI indicating the NFI information of the group 0, the UE considers that the scheduling of the at least one DCI format 1_0 belongs to the group 0, and the NFI information corresponding to the scheduling of the at least one DCI format 1_0 is determined according to the NFI information corresponding to the group 0, wherein the next PUCCH transmission opportunity is determined according to the at least one DCI format 1_ 0.

Case 2: if the UE receives the scheduling of at least one DCI format 1_0 after the last PUCCH transmission opportunity for transmitting HARQ-ACK feedback information including group 0 but does not receive DCI indicating NFI information of group 0 before the next PUCCH transmission opportunity determined according to the at least one DCI format 1_0, the UE considers that the scheduling of the at least one DCI format 1_0 does not belong to any group (or does not belong to either group 0 or group 1).

Under the condition that the terminal device is configured with eType-2 HARQ-ACK codebook feedback, the terminal device can also be configured with a Type-1 HARQ-ACK codebook or a Type-2 HARQ-ACK codebook. Alternatively, if the terminal device is not configured with a Type-1 HARQ-ACK codebook and is not configured with a Type-2 HARQ-ACK codebook, the terminal device may use the Type-1 HARQ-ACK codebook by default.

For the above situation 1, under the condition that the UE considers that the scheduling of the DCI format 1_0 belongs to the group 0, the UE generates a HARQ-ACK codebook to be transmitted according to an eType-2 HARQ-ACK codebook, where the HARQ-ACK codebook to be transmitted includes HARQ-ACK information corresponding to the PDSCH scheduled by the at least one DCI format 1_ 0.

For the above case 2, in a case that the UE considers that the scheduling of the DCI format 1_0 does not belong to any group, the UE generates a HARQ-ACK codebook to be transmitted according to a Type-1 HARQ-ACK codebook or a Type-2 HARQ-ACK codebook, where the HARQ-ACK codebook to be transmitted includes HARQ-ACK information corresponding to the PDSCH scheduled by the at least one DCI format 1_ 0.

It should be understood that, for the case 2, the network device and the terminal device may not understand the codebook generation method of DCI format 1_0 in a consistent manner. For example, the network device sends DCI indicating NFI information of group 0 for the terminal device, but the terminal device does not receive the DCI indicating the NFI information of group 0, the network device may consider that the scheduling of the at least one DCI format 1_0 belongs to group 0, and the corresponding codebook generation manner is an eType-2 HARQ-ACK codebook, but the terminal device may consider that the scheduling of the at least one DCI format 1_0 does not belong to any group, and the corresponding codebook generation manner is a Type-1 HARQ-ACK codebook or a Type-2 HARQ-ACK codebook, so that the network device and the terminal device have inconsistency in understanding of the codebook generation manners of the HARQ-ACK feedback information corresponding to the at least one DCI format 1_ 0.

Under the condition that the terminal equipment is configured with eType-2 HARQ-ACK codebook feedback, if the terminal equipment receives at least one PDSCH which is scheduled by at least one DCI format 1_0 and does not belong to any group, first HARQ-ACK information corresponding to the at least one PDSCH is indicated to be fed back through a first PUCCH; in addition, the terminal equipment transmits a first PUSCH by scheduling of a first DCI format, and if the first PUCCH and the first PUSCH are at least partially overlapped in a time domain, the terminal equipment can multiplex the first HARQ-ACK information onto the first PUSCH for transmission. When the first DCI format includes an uplink Downlink Assignment Indication (DAI) field (e.g., the first DCI format includes DCI format 0_1 or DCI format 0_2), the terminal device may determine, according to the uplink DAI field in the first DCI format, a generation manner of a first HARQ-ACK codebook including first HARQ-ACK information, so as to solve a problem that the network device and the terminal device have inconsistent understanding of a codebook generation manner of HARQ-ACK feedback information corresponding to the at least one DCI format 1_ 0.

Embodiment mode 1:

the embodiment of the application provides a method for generating a HARQ-ACK codebook, which can be applied to terminal equipment. As shown in fig. 2, the method includes at least some of the following:

S210: the terminal equipment receives a first DCI format, the first DCI format schedules a first PUSCH for transmission, the first DCI format comprises an uplink DAI domain, and a first HARQ-ACK codebook is multiplexed and transmitted in the first PUSCH; the terminal equipment is configured with an eType-2 HARQ-ACK codebook;

s220: the terminal equipment generates a first HARQ-ACK codebook according to the uplink DAI domain, wherein the first HARQ-ACK codebook comprises first HARQ-ACK information, or the first HARQ-ACK codebook does not comprise the first HARQ-ACK information, the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one PDSCH scheduled by DCI format 1_0, and/or the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one SPS PDSCH without DCI format scheduling, and/or the first HARQ-ACK information comprises ACK feedback information corresponding to at least one SPS PDSCH release.

According to the embodiment of the present application, when the terminal device receives at least one PDSCH scheduled by DCI format 1_0, a situation may occur in which the terminal device considers that the at least one PDSCH does not belong to any group, but the network device considers that the at least one PDSCH belongs to group 0. In this case, when HARQ-ACK information corresponding to the at least one PDSCH is fed back through the PUSCH scheduled by DCI format 0_1, the HARQ-ACK codebook that the terminal device should generate may be determined through the uplink DAI indication information in DCI format 0_1, so as to avoid ambiguity of understanding of the HARQ-ACK codebook by the terminal device and the network device.

Under the condition that the terminal device is configured with eType-2 HARQ-ACK codebook feedback, the terminal device receives at least one PDSCH which does not belong to any group and is scheduled by at least one DCI format 1_0, and first HARQ-ACK information corresponding to the at least one PDSCH (or HARQ-ACK feedback information corresponding to the PDSCH scheduled by at least one DCI format 1_ 0) is indicated to be fed back through the first PUCCH. The terminal device may multiplex the first HARQ-ACK information onto a first PUSCH transmitted if the first PUCCH at least partially overlaps in time domain with the first PUSCH on which the terminal device is scheduled by the first DCI format. Wherein, optionally, the first DCI format includes DCI format 0_ 1.

According to an embodiment of the application, if a terminal device receives at least one Semi-persistent scheduling (SPS) PDSCH without DCI format scheduling, first HARQ-ACK information corresponding to the at least one SPS PDSCH is indicated to be fed back through a first PUCCH. The terminal device may multiplex the first HARQ-ACK information onto a first PUSCH transmitted if the first PUCCH at least partially overlaps in time domain with the first PUSCH on which the terminal device is scheduled by the first DCI format. Optionally, the first DCI format includes DCI format 0_ 1.

According to the embodiment of the application, if the terminal equipment receives at least one DCI format indicating SPS PDSCH release, first HARQ-ACK information such as ACK information corresponding to the SPS PDSCH release indicated by the at least one DCI format is indicated to be fed back through the first PUCCH. The terminal device may multiplex the first HARQ-ACK information for transmission on a first PUSCH scheduled by the first DCI format if the first PUCCH at least partially overlaps the first PUSCH in the time domain. Optionally, the DCI format indicating the SPS PDSCH release includes at least one of DCI format 1_0, DCI format 1_1, and DCI format 1_ 2. Optionally, the first DCI format includes DCI format 0_ 1.

Optionally, the terminal device is configured with a Type-1 HARQ-ACK codebook and an eType-2 HARQ-ACK codebook, or the terminal device is configured with a Type-2 HARQ-ACK codebook and an eType-2 HARQ-ACK codebook, or the terminal device is configured with an eType-2 HARQ-ACK codebook, is not configured with a Type-1 HARQ-ACK codebook, and is not configured with a Type-2 HARQ-ACK codebook.

Optionally, the terminal device generates a first HARQ-ACK codebook according to the uplink DAI field, including:

the terminal equipment determines a first codebook type according to the uplink DAI domain; the first codebook Type comprises one of a Type-1 HARQ-ACK codebook, a Type-2 HARQ-ACK codebook and an eType-2 HARQ-ACK codebook;

And the terminal equipment generates the first HARQ-ACK codebook according to the first codebook type.

In some embodiments, in the case that the terminal device is configured with a Type-1 HARQ-ACK codebook and an eType-2 HARQ-ACK codebook, the first codebook Type is a Type-1 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook.

In some embodiments, in the case that the terminal device is configured with an eType-2 HARQ-ACK codebook and is not configured with a Type-1 HARQ-ACK codebook and is not configured with a Type-2 HARQ-ACK codebook, the first codebook Type is a Type-1 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook.

Optionally, in this embodiment of the present application, the configuration signaling includes at least one of Radio Resource Control (RRC) signaling, Media Access Control Element (MAC CE) and physical layer signaling, for example, Downlink Control Information (DCI).

Optionally, the terminal device is configured with an eType-2 HARQ-ACK codebook, including: the terminal equipment is configured with feedback according to an eType-2 HARQ-ACK codebook; or the terminal equipment is configured to generate HARQ-ACK feedback information according to the eType-2 HARQ-ACK codebook; or, the terminal device is provided with pdsch-HARQ-ACK-Codebook ═ enhanced dynamic-r 16; or, the terminal device is provided with pdsch-HARQ-ACK-Codebook-r16 ═ enhanced dynamic.

Optionally, the terminal device is configured with a Type-1 HARQ-ACK codebook, which includes: the terminal equipment is configured with feedback according to a Type-1 HARQ-ACK codebook; or the terminal equipment is configured to generate HARQ-ACK feedback information according to the Type-1 HARQ-ACK codebook; or, the terminal device is provided with pdsch-HARQ-ACK-Codebook ═ semi-static.

Optionally, the terminal device is configured with a Type-2 HARQ-ACK codebook, including: the terminal equipment is configured with feedback according to the Type-2 HARQ-ACK codebook; or the terminal equipment is configured to generate HARQ-ACK feedback information according to the Type-2 HARQ-ACK codebook; alternatively, the terminal device is provided with pdsch-HARQ-ACK-Codebook ═ dynamic.

As an example, in the case that the terminal device is configured with eType-2 HARQ-ACK codebook feedback, the size of the uplink DAI field in DCI format 0_1 includes one of the cases shown in table 1:

TABLE 1

As shown in table 1, optionally, if the terminal device is not configured with the UL-total DAI-Included-r16 parameter, it indicates that the terminal device is not configured with the uplink DAI indicating two groups; or, if the terminal device is configured with UL-total DAI-Included-r16, for example, UL-total DAI-Included-r16 ═ true ", it means that the terminal device is configured with an uplink DAI indicating two groups.

If the terminal device is configured with eType-2 HARQ-ACK codebook feedback, in the case where only Transport Block (TB) based feedback is included in the HARQ-ACK information, the second uplink DAI field includes 0 bit (or does not include the second uplink DAI field), and for the first uplink DAI field:

if the uplink DAI indicating two groups is not configured, the first uplink DAI field includes 2 bits, or the first uplink DAI field includes one piece of DAI indication information;

if the HARQ-ACK information to be transmitted includes HARQ-ACK information of 2 groups, the 2 bits (or the DAI indication information) are used to determine the size of the HARQ-ACK codebook of the first group (or group 0);

if the HARQ-ACK information to be transmitted includes 1 group of HARQ-ACK information, the 2 bits (or the DAI indication information) are used to determine the size of the HARQ-ACK codebook for the group (group 0 or group 1) of HARQ-ACK information to be transmitted.

If configured to indicate the uplink DAI of two groups, the first uplink DAI field includes 4 bits, or the first uplink DAI field includes two DAI indication information;

wherein 2 bits (or one DAI indication information such as a3, a2) are used to determine the size of the HARQ-ACK codebook of the first group (or group 0), and 2 bits (or another DAI indication information such as a1, a0) are used to determine the size of the HARQ-ACK codebook of the second group (or group 1).

In the case where feedback based on a Code Block Group (CBG) is included in the HARQ-ACK information, for the second uplink DAI field:

if the uplink DAI indicating two groups is not configured, the second uplink DAI field includes 2 bits, or the second uplink DAI field includes one piece of DAI indication information;

if the HARQ-ACK information to be transmitted includes 2 groups of HARQ-ACK information, the 2 bits (or the DAI indication information) are used to determine the size of the second HARQ-ACK sub-codebook of the first group (or group 0);

if the HARQ-ACK information to be transmitted includes 1 group of HARQ-ACK information, the 2 bits (or the DAI indication information) are used to determine the size of the second HARQ-ACK sub-codebook for the group (group 0 or group 1) of HARQ-ACK information to be transmitted.

If configured to indicate the uplink DAI of two groups, the second uplink DAI field includes 4 bits, or the second uplink DAI field includes two DAI indication information;

wherein 2 bits (or one DAI indication information such as b3, b2) is used to determine the size of the second HARQ-ACK sub-codebook of the first group (or group 0), and 2 bits (or another DAI indication information such as b1, b0) is used to determine the size of the second HARQ-ACK sub-codebook of the second group (or group 1).

An embodiment when the first codebook Type is a Type-1 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook will be described below.

In some embodiments, the determining, by the terminal device, a first codebook type according to the uplink DAI field includes: and the terminal equipment determines the first codebook type according to the second uplink DAI domain.

Optionally, if k2 bits included in the second uplink DAI field are all set to 0, the first codebook Type is a Type-1 HARQ-ACK codebook, and k2 is an integer. For example, as shown in table 1, k2 is 2, and b1 and b0 are all set to 0. For another example, as shown in table 1, k2 is 4, and b3, b2, b1, and b0 are all set to 0.

Optionally, if the second uplink DAI field includes at least one piece of DAI indication information, and each piece of DAI indication information in the at least one piece of DAI indication information indicates a first preset value, the first codebook Type is a Type-1 HARQ-ACK codebook. For example, as shown in table 1, k2 ═ 2, b1 and b0 are each set to 1, indicating a first preset value, e.g., DAI ═ 4. For another example, as shown in table 1, k2 ═ 4, b3 and b2 are each set to 1, indicating that one DAI ═ 4, b1 and b0 are each set to 1, indicating that the other DAI ═ 4.

Optionally, if at least one bit of the k2 bits included in the second uplink DAI field is not set to 0, the first codebook type is an eType-2 HARQ-ACK codebook.

Optionally, if the second uplink DAI field includes at least one piece of DAI indication information and the at least one piece of DAI indication information in the second uplink DAI field does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook.

Optionally, if k2 bits included in the second uplink DAI field are all set to 0, the terminal device determines the first codebook type according to the first uplink DAI field.

Optionally, if the second uplink DAI field includes at least one piece of DAI indication information, and each piece of DAI indication information in the second uplink DAI field indicates a first preset value, the terminal device determines the first codebook type according to the first uplink DAI field.

Optionally, as shown in table 1, k2 takes a value of 0 or 2 or 4.

In some embodiments, the determining, by the terminal device, a first codebook type according to the uplink DAI field includes: and the terminal equipment determines the first codebook type according to the first uplink DAI domain.

Optionally, if (k1-1) high-order Bits (MSB) of the k1 Bits included in the first uplink DAI field are all set to 0, the first codebook Type is a Type-1 HARQ-ACK codebook, and k1 is an integer greater than 1. For example, as shown in table 1, k1 is 2, and a1 is set to 0. For another example, as shown in table 1, k1 is 4, and a3, a2, and a1 are all set to 0. Optionally, the first bit includes a0, where the first bit is used to generate a first HARQ-ACK codebook.

Optionally, if at least one bit of (k1-1) MSBs of the k1 bits included in the first uplink DAI field is not set to 0, the first codebook type is an eType-2 HARQ-ACK codebook.

Optionally, if the first uplink DAI field includes first DAI indication information and an MSB of the first DAI indication information is set to 0, the first codebook Type is a Type-1 HARQ-ACK codebook. For example, as shown in table 1, the first DAI indication information is represented by a1 and a0, in which a1 is set to 0. Optionally, the first bit includes a0, where the first bit is used to generate a first HARQ-ACK codebook.

Optionally, if the first uplink DAI field includes first DAI indication information and an MSB of the first DAI indication information is set to 1, the first codebook type is an eType-2 HARQ-ACK codebook. For example, as shown in table 1, the first DAI indication information is represented by a1 and a0, in which a1 is set to 1.

Optionally, if the first uplink DAI field includes first DAI indication information and second DAI indication information, the MSB of the first DAI indication information is set to 0, and the second DAI indication information indicates a first preset value, the first codebook Type is a Type-1 HARQ-ACK codebook. For example, as shown in table 1, the first DAI indication information is represented by a3 and a2, and the second DAI indication information is represented by a1 and a0, in which a3 is set to 0; a1 and a0 are both set to 1 indicating a first preset value, e.g., DAI-4. Optionally, the first bit includes a2, where the first bit is used to generate a first HARQ-ACK codebook.

Optionally, if the first uplink DAI field includes first DAI indication information and second DAI indication information, and an MSB of the first DAI indication information is set to 1, or the second DAI indication information does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook.

Optionally, if the first uplink DAI field includes first DAI indication information and second DAI indication information, where the first DAI indication information indicates a first preset value and an MSB of the second DAI indication information is set to 0, the first codebook Type is a Type-1 HARQ-ACK codebook. For example, as shown in table 1, the first DAI indication information is represented by a3 and a2, and the second DAI indication information is represented by a1 and a0, in which a1 is set to 0; a3 and a2 are both set to 1 indicating a first preset value, e.g., DAI-4. Optionally, the first bit includes a0, where the first bit is used to generate a first HARQ-ACK codebook.

Optionally, if the first uplink DAI field includes first DAI indication information and second DAI indication information, the first DAI indication information does not indicate a first preset value, or an MSB in the second DAI indication information is set to 1, the first codebook type is an eType-2 HARQ-ACK codebook.

Optionally, as shown in table 1, the value of k1 is 2 or 4.

In some embodiments, the terminal device generates the first HARQ-ACK codebook according to the uplink DAI field, including: and the terminal equipment generates a first HARQ-ACK codebook according to a first bit in the uplink DAI domain and the Type-1 HARQ-ACK codebook.

Optionally, the uplink DAI field includes a first uplink DAI field, and the first bit includes a bit in the first uplink DAI field.

Optionally, the first bit includes 1 low-order bit (LSB) of k1 Bits included in the first uplink DAI field, and k1 is an integer greater than 1. For example, as shown in table 1, the first bit includes a 0.

Optionally, if the first uplink DAI field includes first DAI indication information and second DAI indication information, the first bit includes an LSB in the first DAI indication information. For example, as shown in table 1, the first DAI indication information is represented by a3 and a2, the second DAI indication information is represented by a1 and a0, and the first bit includes a 2.

Optionally, if the first uplink DAI field includes first DAI indication information and second DAI indication information, the first bit includes an LSB in the second DAI indication information. For example, as shown in table 1, the first DAI indication information is represented by a3 and a2, the second DAI indication information is represented by a1 and a0, and the first bit includes a 0.

Optionally, the generating, by the terminal device, the first HARQ-ACK codebook according to the first bit in the uplink DAI domain and the Type-1 HARQ-ACK codebook includes:

if the first bit indicates a second preset value, the terminal equipment generates a first HARQ-ACK codebook according to a Type-1 HARQ-ACK codebook; or the like, or a combination thereof,

if the first bit indicates a third preset value and the PDSCH scheduled by the at least one DCI format 1_0 comprises the PDSCH scheduled by the DCI format 1_0, the terminal equipment generates the first HARQ-ACK codebook for the PDSCH; otherwise, the terminal equipment does not generate the first HARQ-ACK codebook according to the Type-1 HARQ-ACK codebook.

Optionally, the second preset value is 1, and the third preset value is 0; or,

the second preset value is 0, and the third preset value is 1.

In some embodiments, the above method further comprises: and if the terminal equipment does not generate the first HARQ-ACK codebook according to the Type-1 HARQ-ACK codebook, the terminal equipment generates the first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook.

In some embodiments, the above method further comprises: and if the terminal equipment does not generate the first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook, the terminal equipment generates the first HARQ-ACK codebook according to the Type-1 HARQ-ACK codebook.

In some embodiments, in the case that the terminal device is configured with a Type-2 HARQ-ACK codebook and an eType-2 HARQ-ACK codebook, the first codebook Type is a Type-2 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook.

In some embodiments, in the case that the terminal device is configured with an eType-2 HARQ-ACK codebook and is not configured with a Type-1 HARQ-ACK codebook and is not configured with a Type-2 HARQ-ACK codebook, the first codebook Type is a Type-2 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook.

An embodiment when the first codebook Type is a Type-2 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook will be described below.

Optionally, if k2 bits included in the second uplink DAI field are all set to 0, the first codebook Type is a Type-2 HARQ-ACK codebook, and k2 is an integer. For example, as shown in table 1, k2 is 2, and b1 and b0 are all set to 0. For another example, as shown in table 1, k2 is 4, and b3, b2, b1, and b0 are all set to 0.

Optionally, if the second uplink DAI field includes at least one piece of DAI indication information, and each piece of DAI indication information in the at least one piece of DAI indication information indicates a first preset value, the first codebook Type is a Type-2 HARQ-ACK codebook. For example, as shown in table 1, k2 ═ 2, b1 and b0 are each set to 1, indicating a first preset value, e.g., DAI ═ 4. For another example, as shown in table 1, k2 ═ 4, b3 and b2 are each set to 1, indicating that one DAI ═ 4, b1 and b0 are each set to 1, indicating that the other DAI ═ 4.

Optionally, if the second uplink DAI field includes at least one DAI indication information, and each DAI indication information in the second uplink DAI field indicates a first preset value, the terminal device determines the first codebook type according to the first uplink DAI field.

Optionally, as shown in table 1, k2 takes a value of 0 or 2 or 4.

In some embodiments, the determining, by the terminal device, a first codebook type according to the uplink DAI field includes:

and the terminal equipment determines the first codebook type according to the first uplink DAI domain.

Optionally, if (k1-2) high-order bits MSBs among the k1 bits included in the first uplink DAI field are all set to 0, and k1 is an integer greater than 2, the first codebook Type is a Type-2 HARQ-ACK codebook. For example, as shown in table 1, k1 ═ 4, and a3 and a2 are each set to 0. Optionally, the second bits include a1 and a0, where the second bits are used to generate the first HARQ-ACK codebook.

Optionally, if at least one bit of (k1-2) MSBs among k1 bits included in the first uplink DAI field is not set to 0, the first codebook type is an eType-2 HARQ-ACK codebook.

Optionally, if the first uplink DAI field includes first DAI indication information and second DAI indication information, and the second DAI indication information indicates a first preset value, the first codebook Type is a Type-2 HARQ-ACK codebook. For example, as shown in table 1, the first DAI indication information is represented by a3 and a2, and the second DAI indication information is represented by a1 and a0, where a1 and a0 are both set to 1, indicating a first preset value, e.g., DAI ═ 4. Optionally, the second bits include a3 and a2, where the second bits are used to generate the first HARQ-ACK codebook.

Optionally, if the first uplink DAI field includes first DAI indication information and second DAI indication information, and the second DAI indication information does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook.

Optionally, if the first uplink DAI field includes first DAI indication information and second DAI indication information, and the first DAI indication information indicates a first preset value, the first codebook Type is a Type-2 HARQ-ACK codebook. For example, as shown in table 1, the first DAI indication information is represented by a3 and a2, and the second DAI indication information is represented by a1 and a0, where a3 and a2 are both set to 1, indicating a first preset value, e.g., DAI ═ 4. Optionally, the second bits include a1 and a0, wherein the second bits are used to generate the first HARQ-ACK codebook.

Optionally, if the first uplink DAI field includes first DAI indication information and second DAI indication information, and the first DAI indication information does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook.

Optionally, as shown in table 1, the value of k1 is 2 or 4.

In some embodiments, the generating, by the terminal device, a first HARQ-ACK codebook according to the uplink DAI field includes: and the terminal equipment generates the first HARQ-ACK codebook according to the second bit in the uplink DAI domain and the Type-2 HARQ-ACK codebook.

Optionally, the uplink DAI field includes a first uplink DAI field, and the second bit is a bit in the first uplink DAI field.

Optionally, the second bit is 2 low-order bits LSB of k1 bits included in the first uplink DAI field, and k1 is an integer greater than or equal to 2. For example, as shown in table 1, the second bit includes a1 and a 0.

Optionally, if the first uplink DAI field includes first DAI indication information and second DAI indication information, the second bit includes a bit in the first DAI indication information. For example, as shown in table 1, the first DAI indication information is represented by a3 and a2, the second DAI indication information is represented by a1 and a0, and the second bit includes a3 and a 2.

Optionally, if the first uplink DAI field includes first DAI indication information and second DAI indication information, the second bit includes a bit in the second DAI indication information. For example, as shown in table 1, the first DAI indication information is represented by a3 and a2, the second DAI indication information is represented by a1 and a0, and the second bit includes a1 and a 0.

Optionally, the terminal device generates the first HARQ-ACK codebook according to a second bit in the uplink DAI domain and a Type-2 HARQ-ACK codebook, where a length of the first HARQ-ACK codebook is indicated by the second bit.

In some embodiments, the above method further comprises: and if the terminal equipment does not generate the first HARQ-ACK codebook according to the Type-2 HARQ-ACK codebook, the terminal equipment generates the first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook.

In some embodiments, the above method further comprises: and if the terminal equipment does not generate the first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook, the terminal equipment generates the first HARQ-ACK codebook according to the Type-2 HARQ-ACK codebook.

In this embodiment of the present application, optionally, the first preset value is 4.

In some embodiments, the case that the first HARQ-ACK codebook includes HARQ-ACK feedback information corresponding to at least one DCI format 1_0 scheduled PDSCH includes at least one of the following:

the first HARQ-ACK codebook only comprises HARQ-ACK feedback information corresponding to the PDSCH scheduled by the at least one DCI format 1_ 0;

the first HARQ-ACK codebook comprises HARQ-ACK feedback information corresponding to the PDSCH scheduled by the at least one DCI format 1_0, and at least one of ACK feedback information corresponding to SPS PDSCH release and HARQ-ACK feedback information corresponding to SPS PDSCH release;

the first HARQ-ACK codebook comprises HARQ-ACK feedback information corresponding to the PDSCH scheduled by the at least one DCI format 1_0 and does not comprise HARQ-ACK feedback information corresponding to the PDSCH scheduled by the DCI format 1_ 1.

In some embodiments, the terminal device generates a first HARQ-ACK codebook according to a Type-1 or Type-2 HARQ-ACK codebook, where the first HARQ-ACK codebook includes first HARQ-ACK information.

In some embodiments, the terminal device generates a first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook, wherein the first HARQ-ACK codebook does not include the first HARQ-ACK information.

Optionally, the length of the first HARQ-ACK codebook is determined according to the DAI indication information in the uplink DAI field. Optionally, the HARQ-ACK information included in the first HARQ-ACK codebook is all NACK. Optionally, when the first HARQ-ACK codebook includes HARQ-ACK information of group 0, the HARQ-ACK information of group 0 is all NACK.

It should be understood that, since the network device expects to receive the first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook generation manner, but the terminal device plans to generate the first HARQ-ACK codebook according to the Type-1 HARQ-ACK codebook or the Type-2 HARQ-ACK codebook generation manner, in this case, the terminal device cannot determine the position of the HARQ-ACK information to be fed back in the first HARQ-ACK codebook, and therefore, the terminal device may set all the corresponding HARQ-ACK information as NACK, so as to avoid ambiguity of understanding the HARQ-ACK information between the network device and the terminal device. Optionally, in this case, the terminal device still needs to send the first HARQ-ACK codebook to enable the network device to perform rate matching correctly.

In some embodiments, the method may further include: and the terminal equipment sends the first HARQ-ACK codebook through the first PUSCH.

Detailed description of the preferred embodiment 2

The embodiment of the application provides a method for generating a HARQ-ACK codebook, which can be applied to terminal equipment. The method comprises at least part of the following contents:

s1: the terminal equipment receives a second DCI format, the second DCI format schedules a second PUSCH for transmission, the second DCI format comprises an uplink DAI domain, and a second HARQ-ACK codebook is multiplexed and transmitted in the second PUSCH; the terminal equipment is configured with a Type-3 HARQ-ACK codebook;

s2, the terminal device generates the second HARQ-ACK codebook according to the uplink DAI domain, where the second HARQ-ACK codebook includes second HARQ-ACK information, or the second HARQ-ACK codebook does not include the second HARQ-ACK information, where the second HARQ-ACK information includes HARQ-ACK feedback information corresponding to at least one Physical Downlink Shared Channel (PDSCH), and/or HARQ-ACK feedback information, such as ACK feedback information, corresponding to SPS PDSCH release indicated by at least one DCI format.

In this case, the terminal device may not be restricted to receive the at least one PDSCH scheduled by DCI format 1_0, and consider that the at least one PDSCH does not belong to any group scenario. For example, the terminal device receives at least one PDSCH scheduled by the network device, where the at least one PDSCH corresponds to the second HARQ-ACK information. The at least one PDSCH may be scheduled through DCI format 1_0, may also be scheduled through DCI format 1_1, or is scheduled through another DCI format, for example, DCI format 1_2, or includes an SPS PDSCH without DCI format scheduling. For another example, the terminal device receives an SPS PDSCH release indicated by at least one DCI format sent by the network device, and the second HARQ-ACK information includes ACK information corresponding to the SPS PDSCH release. And the terminal equipment generates a second HARQ-ACK codebook, wherein the second HARQ-ACK codebook comprises the second HARQ-ACK information, or the second HARQ-ACK codebook does not comprise the second HARQ-ACK information.

Optionally, the terminal device is configured with a Type-3 HARQ-ACK codebook, which includes: the terminal equipment is configured with feedback according to a Type-3 HARQ-ACK codebook; or the terminal equipment is configured to generate HARQ-ACK feedback information according to the Type-3 HARQ-ACK codebook; or, the terminal equipment is provided with pdsch-HARQ-ACK-OneShotFeedback-r 16; or, the terminal equipment is configured with pdsch-HARQ-ACK-OneShotFeedback-r16 ═ true.

Optionally, the terminal device generates a second HARQ-ACK codebook according to the uplink DAI field, including:

the terminal equipment determines a second codebook type according to the uplink DAI domain; the second codebook Type comprises one of a Type-1 HARQ-ACK codebook, a Type-2 HARQ-ACK codebook, an eType-2 HARQ-ACK codebook and a Type-3 HARQ-ACK codebook;

and the terminal equipment generates the second HARQ-ACK codebook according to a second codebook type.

In some embodiments, the upstream DAI domain includes a first upstream DAI domain.

Optionally, if k1 bits included in the first uplink DAI field are set to a fourth preset value, the second codebook Type is a Type-3 HARQ-ACK codebook, and k1 is an integer.

Optionally, if k1 bits included in the first uplink DAI field are all set to 1, the second codebook Type is a Type-3 HARQ-ACK codebook, and k1 is an integer.

For example, as shown in table 1, k1 ═ 2, and a1 and a0 are each set to 1. For another example, as shown in table 1, k1 is 4, and a3, a2, a1, and a0 are all set to 1.

In some embodiments, the upstream DAI fields include a first upstream DAI field and a second upstream DAI field.

Optionally, if k1 bits included in the first uplink DAI field are set to a fourth preset value, and k2 bits included in the second uplink DAI field are set to a fifth preset value, the second codebook Type is a Type-3 HARQ-ACK codebook, and k1 and k2 are integers.

Optionally, if k1 bits included in the first uplink DAI field are all set to 1, and k2 bits included in the second uplink DAI field are all set to 1, the second codebook Type is a Type-3 HARQ-ACK codebook, and k1 and k2 are integers.

For example, as shown in table 1, k1 ═ 2, k2 ═ 2, a1 and a0 are both set to 1 and b1 and b0 are both set to 1. For another example, as shown in table 1, k1 is 4, k2 is 4, a3, a2, a1, and a0 are all set to 1, and b3, b2, b1, and b0 are all set to 1.

In some embodiments, the terminal device generates a second HARQ-ACK codebook according to the Type-3 HARQ-ACK codebook, wherein the second HARQ-ACK codebook includes second HARQ-ACK information.

Optionally, the terminal device generates a second HARQ-ACK codebook according to the Type-3 HARQ-ACK codebook, where the second HARQ-ACK codebook includes HARQ-ACK information corresponding to all HARQ processes on all configured carriers in one physical uplink control channel PUCCH group.

Optionally, the second DCI format includes at least one of DCI format 0_1 and DCI format 0_ 2.

Optionally, the terminal device is configured with an eType-2 HARQ-ACK codebook. In some embodiments, if the terminal device does not determine that the second codebook Type is a Type-3 HARQ-ACK codebook according to the uplink DAI field, the terminal device determines that the second codebook Type is an eType-2 HARQ-ACK codebook.

Optionally, the terminal device is configured with a Type-2 HARQ-ACK codebook. In some embodiments, if the terminal device does not determine that the second codebook Type is a Type-3 HARQ-ACK codebook according to the uplink DAI field, the terminal device determines that the second codebook Type is a Type-2 HARQ-ACK codebook.

Optionally, the terminal device is configured with a Type-1 HARQ-ACK codebook. In some embodiments, if the terminal device does not determine that the second codebook Type is a Type-3 HARQ-ACK codebook according to the uplink DAI field, the terminal device determines that the second codebook Type is a Type-1 HARQ-ACK codebook.

Optionally, the terminal device is configured with an eType-2 HARQ-ACK codebook and a Type-1 HARQ-ACK codebook. In some embodiments, if the terminal device does not determine that the second codebook Type is a Type-3 HARQ-ACK codebook according to the uplink DAI field, the terminal device may determine that the second codebook Type is one of an eType-2 HARQ-ACK codebook and a Type-1 HARQ-ACK codebook according to the method in embodiment 1.

Optionally, the terminal device is configured with an eType-2 HARQ-ACK codebook and a Type-2 HARQ-ACK codebook. In some embodiments, if the terminal device does not determine that the second codebook Type is a Type-3 HARQ-ACK codebook according to the uplink DAI field, the terminal device may determine that the second codebook Type is one of an eType-2 HARQ-ACK codebook and a Type-2 HARQ-ACK codebook according to the method in embodiment 1.

Optionally, the terminal device is configured with an eType-2 HARQ-ACK codebook and is not configured with a Type-1 HARQ-ACK codebook. In some embodiments, if the terminal device does not determine that the second codebook Type is a Type-3 HARQ-ACK codebook according to the uplink DAI field, the terminal device may determine that the second codebook Type is one of an eType-2 HARQ-ACK codebook and a Type-1 HARQ-ACK codebook according to the method in embodiment 1.

Optionally, the terminal device is configured with an eType-2 HARQ-ACK codebook and is not configured with a Type-1 HARQ-ACK codebook. In some embodiments, if the terminal device does not determine that the second codebook Type is a Type-3 HARQ-ACK codebook according to the uplink DAI field, the terminal device may determine that the second codebook Type is one of an eType-2 HARQ-ACK codebook and a Type-2 HARQ-ACK codebook according to the method in embodiment 1.

The present invention will be described in detail below with reference to specific examples.

The first embodiment is as follows:

in this embodiment, the terminal device is configured with a Type-1 HARQ-ACK codebook and an eType-2 HARQ-ACK codebook, or the terminal device is configured with an eType-2 HARQ-ACK codebook, is not configured with a Type-1 HARQ-ACK codebook, and is not configured with a Type-2 HARQ-ACK codebook, and the first codebook Type is a Type-1 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook.

And the terminal equipment receives at least one PDSCH which is scheduled by at least one DCI format 1_0 and does not belong to any group, wherein the at least one PDSCH corresponds to the first HARQ-ACK information. And the terminal equipment generates a first HARQ-ACK codebook, wherein the first HARQ-ACK codebook comprises the first HARQ-ACK information, or the first HARQ-ACK codebook does not comprise the first HARQ-ACK information.

The method for generating the first HARQ-ACK codebook by the terminal device includes one of the following:

if the first DCI format comprises a first uplink DAI domain and a second uplink DAI domain

If k2 bits included in the second uplink DAI field are all set to 0 (e.g., k2 takes the value of 0, 2, or 4), the terminal device generates a first HARQ-ACK codebook according to (two);

if at least one bit of the k2 bits included in the second uplink DAI field is not set to 0 (e.g., k2 is set to 2 or 4), the terminal device generates the first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook determination method.

(II) if the first uplink DAI field in the first DCI format includes k1 bits (for example, k1 is 2 or 4)

If (k1-1) MSBs of the k1 bits included in the first uplink DAI domain are all set to be 0, the terminal equipment generates a first HARQ-ACK codebook according to a Type-1 HARQ-ACK codebook determination mode;

if at least one bit of (k1-1) MSBs among k1 bits included in the first uplink DAI field is not set to 0, the terminal device generates a first HARQ-ACK codebook according to an eType-2 HARQ-ACK codebook determination manner.

Assuming that the first uplink DAI field includes { ak1-1, …, a1, a0}, the first bit includes the LSB, e.g., a0, in the first uplink DAI field, and in the case that the first codebook Type is determined to be a Type-1 HARQ-ACK codebook, the terminal device generates a first HARQ-ACK codebook according to the first bit a0 and the Type-1 HARQ-ACK codebook determination manner.

Optionally, if the a0 bit value is 1, the terminal device generates a first HARQ-ACK codebook according to a Type-1 HARQ-ACK codebook determination manner. Optionally, the first HARQ-ACK codebook includes the first HARQ-ACK information.

Optionally, if the a0 bit value is 0, the terminal device feeds back HARQ-ACK information for the PDSCH under the condition that the at least one PDSCH only includes one PDSCH; or, if the a0 bit is 0, the terminal device does not generate the first HARQ-ACK codebook according to the Type-1 HARQ-ACK codebook determination method when the at least one PDSCH includes multiple PDSCHs.

Optionally, if the a0 bit value is 0, the terminal device generates the first HARQ-ACK codebook according to an eType-2 HARQ-ACK codebook determination manner when the at least one PDSCH includes multiple PDSCHs.

And under the condition that the first codebook type is the eType-2 HARQ-ACK codebook, the terminal equipment generates a first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook determining mode. Optionally, the first HARQ-ACK codebook does not include the first HARQ-ACK information.

Optionally, all HARQ-ACK information included in the first HARQ-ACK codebook is NACK, or when the first HARQ-ACK codebook includes HARQ-ACK information of group 0, all HARQ-ACK information of group 0 is NACK.

Optionally, if the first uplink DAI field includes 1 DAI indication information { a1, a0}, when the terminal device determines to generate the first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook determination manner, the DAI indication information is used to indicate DAI information of group 0, and the terminal device generates the first HARQ-ACK codebook according to the DAI indication information.

Optionally, if 2 pieces of DAI indication information { a3, a2, a1, a0} are included in the first uplink DAI field, where the 1 st piece of DAI indication information includes { a3, a2}, and the 2 nd piece of DAI indication information includes { a1, a0}, when the terminal device determines to generate the first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook determination manner, the 2 pieces of DAI indication information are used to indicate DAI information of 2 groups, and the terminal device generates the first HARQ-ACK codebook according to the 2 pieces of DAI indication information. For example, the 1 st DAI indication information indicates the HARQ-ACK codebook length of the first group (group 0), the 2 nd DAI indication information indicates the HARQ-ACK codebook length of the second group (group 1), and the first HARQ-ACK codebook includes the HARQ-ACK codebook of group 0 and/or the HARQ-ACK codebook of group 1.

The second embodiment:

in this embodiment, the terminal device is configured with a Type-2 HARQ-ACK codebook and an eType-2 HARQ-ACK codebook, and the first codebook Type is a Type-2 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook.

And the terminal equipment receives at least one PDSCH which does not belong to any group and is scheduled by at least one DCI format 1_0, wherein the at least one PDSCH corresponds to the first HARQ-ACK information. And the terminal equipment generates a first HARQ-ACK codebook, wherein the first HARQ-ACK codebook comprises the first HARQ-ACK information, or the first HARQ-ACK codebook does not comprise the first HARQ-ACK information.

(III) if the first DCI format comprises a first uplink DAI domain and a second uplink DAI domain

If k2 bits included in the second uplink DAI field are all set to 0 (e.g., k2 takes the value of 0, 2, or 4), the terminal device generates a first HARQ-ACK codebook according to (iv);

if at least one bit of the k2 bits included in the second uplink DAI field is not set to 0 (e.g., the k2 value is 2 or 4), the terminal device generates a first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook determination manner.

(IV) if the first uplink DAI field in the first DCI format includes k1 bits (e.g., k1 takes on a value of 2 or 4)

If (k1-2) MSBs among the k1 bits included in the first uplink DAI field are all set to 0, or k1 is 2, the terminal device generates a first HARQ-ACK codebook according to a Type-2 HARQ-ACK codebook determination manner;

if at least one bit of (k1-2) MSBs among k1 bits included in the first uplink DAI field is not set to 0, the terminal device generates a first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook determination manner.

Assuming that the first uplink DAI field includes { ak1-1, …, a1, a0}, and the second bit includes 2 LSBs in the first uplink DAI field, for example { a1, a0}, in the case that the first codebook Type is determined to be a Type-2 HARQ-ACK codebook, the terminal device generates the first HARQ-ACK codebook according to the determination manner of the second bit { a1, a0} and the Type-2 HARQ-ACK codebook. Optionally, the first HARQ-ACK codebook includes the first HARQ-ACK information.

Optionally, the second bit { a1, a0} indicates a length of the first HARQ-ACK codebook.

And under the condition that the first codebook type is determined to be an eType-2 HARQ-ACK codebook, the terminal equipment generates a first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook determination mode. Optionally, the first HARQ-ACK codebook does not include the first HARQ-ACK information.

Optionally, the HARQ-ACK information included in the first HARQ-ACK codebook is all NACK, or when the first HARQ-ACK codebook includes HARQ-ACK information of group 0, the HARQ-ACK information of group 0 is all NACK.

Optionally, if the first uplink DAI field includes 1 DAI indication information { a1, a0}, when the terminal device determines to generate the first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook determination method, the DAI indication information is used to indicate the DAI information of group 0, and the terminal device generates the first HARQ-ACK codebook according to the DAI indication information.

Optionally, if the first uplink DAI field includes 2 DAI indication information { a3, a2, a1, a0}, where the 1 st DAI indication information includes { a3, a2}, and the 2 nd DAI indication information includes { a1, a0}, when the terminal device determines to generate the first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook determination manner, the 2 DAI indication information are used to indicate DAI information of 2 groups, and the terminal device generates the first HARQ-ACK codebook according to the 2 DAI indication information. For example, the 1 st DAI indication information indicates a HARQ-ACK codebook length of a first group (group 0), the 2 nd DAI indication information indicates a HARQ-ACK codebook length of a second group (group 1), and the first HARQ-ACK codebook includes a group 0 HARQ-ACK codebook and/or a group 1 HARQ-ACK codebook.

Example three:

in this embodiment, the terminal device is configured with a Type-2 HARQ-ACK codebook, an eType-2 HARQ-ACK codebook, and a Type-3 HARQ-ACK codebook, and the first codebook Type is one of the Type-2 HARQ-ACK codebook, the eType-2 HARQ-ACK codebook, and the Type-3 HARQ-ACK codebook.

And the terminal equipment receives at least one PDSCH, wherein the at least one PDSCH corresponds to the first HARQ-ACK information. And the terminal equipment generates a first HARQ-ACK codebook, wherein the first HARQ-ACK codebook comprises the first HARQ-ACK information, or the first HARQ-ACK codebook does not comprise the first HARQ-ACK information.

(V) if the first DCI format comprises a first uplink DAI domain and a second uplink DAI domain

If k2 bits included in the second uplink DAI field are all set to 0 or k2 bits are all set to 1 (for example, k2 takes the value of 0, 2, or 4), the terminal device generates a first HARQ-ACK codebook according to (six);

otherwise (for example, at least one bit of the k2 bits included in the second uplink DAI field is not set to 0 and at least one bit is not set to 1), the terminal device generates the first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook determination manner.

(VI) if the first uplink DAI field in the first DCI format includes k1 bits (e.g., k1 takes on a value of 2 or 4)

Under the condition that k2 bits included in the second uplink DAI field are all set to be 1, if k1 bits included in the first uplink DAI field are all set to be 1, the terminal device generates a first HARQ-ACK codebook according to a Type-3 HARQ-ACK codebook determination mode, otherwise, the terminal device generates the first HARQ-ACK codebook according to an eType-2 HARQ-ACK codebook determination mode.

In the case where k2 bits included in the second uplink DAI field are all set to 0, if (k1-2) MSBs among k1 bits included in the first uplink DAI field are all set to 0, or k1 ═ 2, the terminal device generates a first HARQ-ACK codebook according to the Type-2 HARQ-ACK codebook determination manner; if at least one bit of (k1-2) MSBs among k1 bits included in the first uplink DAI field is not set to 0, the terminal device generates a first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook determination manner.

And under the condition that the first codebook type is determined to be an eType-2 HARQ-ACK codebook, the terminal equipment generates a first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook determination mode.

Optionally, the first HARQ-ACK codebook does not include the first HARQ-ACK information. Optionally, the HARQ-ACK information included in the first HARQ-ACK codebook is all NACK, or when the first HARQ-ACK codebook includes HARQ-ACK information of group 0, the HARQ-ACK information of group 0 is all NACK.

Optionally, the first HARQ-ACK codebook includes the first HARQ-ACK information. Optionally, the first HARQ-ACK codebook includes HARQ-ACK information of group 1, wherein the HARQ-ACK information of group 1 may be considered as valid HARQ-ACK information.

Optionally, if 2 pieces of DAI indication information { a3, a2, a1, a0} are included in the first uplink DAI field, where the 1 st piece of DAI indication information includes { a3, a2}, and the 2 nd piece of DAI indication information includes { a1, a0}, when the terminal device determines to generate the first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook determination manner, the 2 pieces of DAI indication information are used to indicate DAI information of 2 groups, and the terminal device generates the first HARQ-ACK codebook according to the 2 pieces of DAI indication information. For example, the 1 st DAI indication information indicates a HARQ-ACK codebook length of a first group (group 0), the 2 nd DAI indication information indicates a HARQ-ACK codebook length of a second group (group 1), and the first HARQ-ACK codebook includes a group 0 HARQ-ACK codebook and/or a group 1 HARQ-ACK codebook.

And under the condition that the first codebook Type is determined to be the Type-3 HARQ-ACK codebook, the terminal equipment generates the first HARQ-ACK codebook according to the Type-3 HARQ-ACK codebook determination mode. Optionally, the first HARQ-ACK codebook includes at least part of the first HARQ-ACK information.

Optionally, the first HARQ-ACK codebook includes HARQ-ACK information corresponding to all HARQ processes on all configured carriers in one PUCCH group.

Correspondingly, in embodiment 3, the present application further provides a method for generating an HARQ-ACK codebook, where the method may be applied to a network device. As shown in fig. 3, the method includes at least some of the following:

s310: configuring an eType-2 HARQ-ACK codebook for the terminal equipment;

s320: sending a first DCI format to terminal equipment, wherein the first DCI format schedules transmission of a first PUSCH, the first DCI format comprises an uplink DAI domain, and a first HARQ-ACK codebook is multiplexed and transmitted in the first PUSCH; the uplink DAI domain is used for generating a first HARQ-ACK codebook, wherein the first HARQ-ACK codebook comprises first HARQ-ACK information, or the first HARQ-ACK codebook does not comprise the first HARQ-ACK information, wherein the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one PDSCH scheduled by DCI format 1_0, and/or the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one SPS scheduled by no DCI format, and/or the first HARQ-ACK information comprises ACK feedback information corresponding to at least one SPS PDSCH release.

Optionally, the method may further include: and configuring a Type-1 HARQ-ACK codebook for the terminal equipment, or configuring a Type-2 HARQ-ACK codebook for the terminal equipment.

Optionally, the uplink DAI field is used to generate the first HARQ-ACK codebook, and includes:

determining a first codebook type according to the uplink DAI domain; the first codebook Type comprises one of a Type-1 HARQ-ACK codebook, a Type-2 HARQ-ACK codebook and an eType-2 HARQ-ACK codebook;

and generating the first HARQ-ACK codebook according to the first codebook type.

Optionally, in a case that the terminal device is configured with a Type-1 HARQ-ACK codebook and an eType-2 HARQ-ACK codebook, the first codebook Type is a Type-1 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

and under the condition that the terminal equipment is not configured with a Type-1 HARQ-ACK codebook and is not configured with a Type-2 HARQ-ACK codebook, the first codebook Type is a Type-1 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook.

In some embodiments, the determining the first codebook type according to the uplink DAI field includes: determining the first codebook type according to the second uplink DAI field, wherein,

If k2 bits included in the second uplink DAI field are all set to 0, the first codebook Type is a Type-1 HARQ-ACK codebook, and k2 is an integer; or the like, or a combination thereof,

if the second uplink DAI domain comprises at least one DAI indication message and each DAI indication message in the at least one DAI indication message indicates a first preset value, the first codebook Type is a Type-1 HARQ-ACK codebook; or the like, or a combination thereof,

if at least one bit of the k2 bits included in the second uplink DAI field is not set to 0, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if the second uplink DAI domain comprises at least one DAI indication information and the at least one DAI indication information in the second uplink DAI domain does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if k2 bits included in the second uplink DAI field are all set to 0, the terminal device determines the first codebook type according to the first uplink DAI field; or

And if the second uplink DAI domain comprises at least one DAI indication message and each DAI indication message in the second uplink DAI domain indicates a first preset value, the terminal equipment determines the first codebook type according to the first uplink DAI domain.

In some embodiments, the determining the first codebook type according to the uplink DAI field includes: determining the first codebook type according to the first uplink DAI field, wherein,

if (k1-1) high-order bits MSB among the k1 bits included in the first uplink DAI field are all set to 0, the first codebook Type is a Type-1 HARQ-ACK codebook, and k1 is an integer greater than 1; or,

if at least one bit of (k1-1) MSBs among k1 bits included in the first uplink DAI field is not set to 0, the first codebook type is an eType-2 HARQ-ACK codebook; or,

if the first uplink DAI domain comprises first DAI indication information and the MSB in the first DAI indication information is set to be 0, the first codebook Type is a Type-1 HARQ-ACK codebook; or,

if the first uplink DAI domain comprises first DAI indication information and the MSB in the first DAI indication information is set to be 1, the first codebook type is an eType-2 HARQ-ACK codebook; or,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, MSB in the first DAI indication information is set to be 0, and the second DAI indication information indicates a first preset value, the first codebook Type is a Type-1 HARQ-ACK codebook; or,

If the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the MSB in the first DAI indication information is set to be 1, or the second DAI indication information does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the first DAI indication information indicates a first preset value, and MSB in the second DAI indication information is set to be 0, the first codebook Type is a Type-1 HARQ-ACK codebook; or,

and if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the first DAI indication information does not indicate a first preset value, or the MSB in the second DAI indication information is set to be 1, the first codebook type is an eType-2 HARQ-ACK codebook.

Optionally, the uplink DAI field is configured to generate the first HARQ-ACK codebook, and includes:

and generating the first HARQ-ACK codebook according to the first bit in the uplink DAI domain and the Type-1 HARQ-ACK codebook.

Optionally, the uplink DAI field comprises a first uplink DAI field, the first bit comprising a bit in the first uplink DAI field, wherein,

The first bit comprises 1 LSB of low order bits of k1 bits comprised by the first uplink DAI field, k1 is an integer greater than 1; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the first bit comprises the LSB in the first DAI indication information; or the like, or a combination thereof,

and if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the first bit comprises the LSB in the second DAI indication information.

In some embodiments, generating the first HARQ-ACK codebook according to the first bit in the uplink DAI field and a Type-1 HARQ-ACK codebook includes:

if the first bit indicates a third preset value and the PDSCH scheduled by the at least one DCI format 1_0 comprises a PDSCH scheduled by the DCI format 1_0, the terminal equipment generates the first HARQ-ACK codebook for the PDSCH; and otherwise, the first HARQ-ACK codebook is not generated according to the Type-1 HARQ-ACK codebook.

Optionally, the second preset value is 1, and the third preset value is 0.

Optionally, the method further comprises: and if the first HARQ-ACK codebook is not generated according to the Type-1 HARQ-ACK codebook, generating the first HARQ-ACK codebook according to an eType-2 HARQ-ACK codebook.

Optionally, in a case that the terminal device is configured with a Type-2 HARQ-ACK codebook and an eType-2 HARQ-ACK codebook, the first codebook Type is a Type-2 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook.

if k2 bits included in the second uplink DAI field are all set to be 0, the first codebook Type is a Type-2 HARQ-ACK codebook, and k2 is an integer; or the like, or a combination thereof,

if the second uplink DAI domain comprises at least one DAI indication message and each DAI indication message in the at least one DAI indication message indicates a first preset value, the first codebook Type is a Type-2 HARQ-ACK codebook; or the like, or a combination thereof,

if at least one bit of the k2 bits included in the second uplink DAI field is not set to 0, the first codebook type is an eType-2 HARQ-ACK codebook; or,

If the second uplink DAI domain comprises at least one DAI indication information and the at least one DAI indication information in the second uplink DAI domain does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook; or,

if k2 bits included in the second uplink DAI domain are all set to 0, determining the first codebook type according to the first uplink DAI domain; or

And if the second uplink DAI domain comprises at least one DAI indication message and each DAI indication message in the second uplink DAI domain indicates a first preset value, determining the first codebook type according to the first uplink DAI domain.

In some embodiments, the determining the first codebook type according to the uplink DAI field includes:

determining the first codebook type according to the first uplink DAI field, wherein,

if (k1-2) high-order bits MSBs in the k1 bits included in the first uplink DAI field are all set to 0, and k1 is an integer greater than 2, the first codebook Type is a Type-2 HARQ-ACK codebook; or,

if at least one bit of (k1-2) MSBs among k1 bits included in the first uplink DAI field is not set to 0, the first codebook type is an eType-2 HARQ-ACK codebook; or,

If the first uplink DAI domain comprises first DAI indication information and second DAI indication information, and the second DAI indication information indicates a first preset value, the first codebook Type is a Type-2 HARQ-ACK codebook; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, and the second DAI indication information does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information and the first DAI indication information indicates a first preset value, the first codebook Type is a Type-2 HARQ-ACK codebook; or the like, or a combination thereof,

and if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, and the first DAI indication information does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook.

Optionally, the method further includes: configuring a Type-2 HARQ-ACK codebook for the terminal equipment;

the uplink DAI field is configured to generate the first HARQ-ACK codebook, and includes: and generating the first HARQ-ACK codebook according to the second bit in the uplink DAI domain and the Type-2 HARQ-ACK codebook.

In some embodiments, the uplink DAI field includes a first uplink DAI field, the second bit is a bit in the first uplink DAI field, wherein,

the second bit is a low order bit LSB of 2 bits of k1 bits included in the first uplink DAI field, and k1 is an integer greater than or equal to 2; or,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the second bit comprises a bit in the first DAI indication information; or,

and if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the second bit is a bit in the second DAI indication information.

Optionally, the first HARQ-ACK codebook is generated according to a second bit in the uplink DAI domain and a Type-2 HARQ-ACK codebook, where a length of the first HARQ-ACK codebook is indicated by the second bit.

Optionally, the first preset value is 4.

In some embodiments, only HARQ-ACK feedback information corresponding to the at least one DCI format 1_0 scheduled PDSCH is included in the first HARQ-ACK codebook; or,

the first HARQ-ACK codebook comprises HARQ-ACK feedback information corresponding to the PDSCH scheduled by the at least one DCI format 1_0, and at least one of ACK feedback information corresponding to SPS PDSCH release and HARQ-ACK feedback information corresponding to SPS PDSCH release; or,

By adopting the above mode, the terminal device can determine the HARQ-ACK codebook which the terminal device should generate through the uplink DAI indication information in the DCI format 0_1 indicated by the network device, thereby avoiding ambiguity of understanding the HARQ-ACK codebook by the terminal device and the network device.

It should be understood that the method of the network device side corresponds to at least one of the above methods applied to the embodiment of the terminal device, and for brevity, the description is omitted here.

Detailed description of preferred embodiment 4

S1: in this embodiment of the present application, for a terminal device, optionally, a network device may configure a Type-3 HARQ-ACK codebook for the terminal device.

The embodiment of the application provides a method for generating a HARQ-ACK codebook, which can be applied to terminal equipment.

Configuring an eType-2 HARQ-ACK codebook;

s2: sending a second DCI format to the terminal equipment, wherein the second DCI format schedules a second PUSCH for transmission, the second DCI format comprises an uplink DAI domain, and a second HARQ-ACK codebook is multiplexed and transmitted in the second PUSCH; the uplink DAI domain is used for generating a second HARQ-ACK codebook, wherein the second HARQ-ACK codebook comprises second HARQ-ACK information, or the second HARQ-ACK codebook does not comprise the second HARQ-ACK information, wherein the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one PDSCH scheduled by DCI format 1_0, or HARQ-ACK feedback information corresponding to at least one PDSCH scheduled by DCI format 1_1, or HARQ-ACK feedback information corresponding to at least one PDSCH scheduled by DCI format 1_2, or the at least one PDSCH comprises HARQ-ACK feedback information corresponding to SPS PDSCH not scheduled by DCI format. Or, the terminal device receives SPS PDSCH release indicated by at least one DCI format sent by the network device, and the second HARQ-ACK information further includes HARQ-ACK feedback information corresponding to the SPS PDSCH release.

S1: the terminal equipment receives a second DCI format, the second DCI format schedules the transmission of a second PUSCH, the second DCI format comprises an uplink DAI domain, and a second HARQ-ACK codebook is transmitted in the second PUSCH in a multiplexing manner; the terminal equipment is configured with a Type-3 HARQ-ACK codebook;

In this case, the terminal device may not be restricted to receive the at least one PDSCH scheduled in DCI format 1_0, and the terminal device considers that the at least one PDSCH does not belong to any group scenario. For example, the terminal device receives at least one PDSCH scheduled by the network device, where the at least one PDSCH corresponds to the first HARQ-ACK information. The at least one PDSCH may be scheduled through DCI format 1_0, may also be scheduled through DCI format 1_1, or is scheduled through another DCI format, for example, DCI format 1_2, or includes an SPS PDSCH without DCI format scheduling. For another example, the terminal device receives an SPS PDSCH release indicated by at least one DCI format sent by the network device, and the first HARQ-ACK information includes ACK information corresponding to the SPS PDSCH release. And the terminal equipment generates a second HARQ-ACK codebook, wherein the second HARQ-ACK codebook comprises the second HARQ-ACK information, or the second HARQ-ACK codebook does not comprise the second HARQ-ACK information.

Optionally, the terminal device is configured with a Type-3 HARQ-ACK codebook, which includes: the network equipment configures terminal equipment to feed back according to the Type-3 HARQ-ACK codebook; or the network equipment configures the terminal equipment to generate HARQ-ACK feedback information according to the Type-3 HARQ-ACK codebook; or, the network device configures the terminal device to provide pdsch-HARQ-ACK-OneShotFeedBack-r 16; or, the network device configures the terminal device pdsch-HARQ-ACK-OneShotFeedback-r16 ═ true.

The uplink DAI domain determines a second codebook type used for the terminal equipment according to the uplink DAI domain; the second codebook Type comprises one of a Type-1 HARQ-ACK codebook, a Type-2 HARQ-ACK codebook, an eType-2 HARQ-ACK codebook and a Type-3 HARQ-ACK codebook;

the second codebook type is used for generating the second HARQ-ACK codebook by the terminal equipment.

In some embodiments, the upstream DAI domain includes a second upstream DAI domain.

Optionally, if k1 bits included in the second uplink DAI field are set to a fourth preset value, the second codebook Type is a Type-3 HARQ-ACK codebook, and k1 is an integer.

Optionally, if k1 bits included in the second uplink DAI field are all set to 1, the second codebook Type is a Type-3 HARQ-ACK codebook, and k1 is an integer.

In some embodiments, the upstream DAI fields include a third upstream DAI field and a fourth upstream DAI field.

Optionally, if k1 bits included in the third uplink DAI field are set to a fourth preset value, and k2 bits included in the fourth uplink DAI field are set to a fifth preset value, the second codebook Type is a Type-3 HARQ-ACK codebook, and k1 and k2 are integers.

Optionally, if k1 bits included in the third uplink DAI field are all set to 1, and k2 bits included in the fourth uplink DAI field are all set to 1, the second codebook Type is a Type-3 HARQ-ACK codebook, and k1 and k2 are integers.

In some embodiments, the Type-3 HARQ-ACK codebook is used for generating a second HARQ-ACK codebook by the terminal device, wherein the second HARQ-ACK codebook comprises second HARQ-ACK information.

Optionally, the Type-3 HARQ-ACK codebook is used for the terminal device to generate a second HARQ-ACK codebook, where the second HARQ-ACK codebook includes HARQ-ACK information corresponding to all HARQ processes on all configured carriers in one physical uplink control channel PUCCH group.

In some embodiments, the above method further comprises: and if the uplink DAI field is used for the terminal equipment and the second codebook Type is not determined to be a Type-3 HARQ-ACK codebook, the second codebook Type is an eType-2 HARQ-ACK codebook.

In some embodiments, the above method further comprises: if the uplink DAI field is used for the terminal device and it is not determined that the first codebook Type is a Type-3 HARQ-ACK codebook, it may be determined that the second codebook Type is one of an eType-2 HARQ-ACK codebook, a Type-1 HARQ-ACK codebook, and a Type-2 HARQ-ACK codebook according to the method in the embodiment of the present application.

Embodiment 5 corresponds to the processing method of at least one of the above embodiments, and an embodiment of the present application further provides a terminal device 400, with reference to fig. 4, which includes:

a first receiving module 410, configured to receive a configuration signaling, where the configuration signaling is used to configure an enhanced type 2 eType-2 HARQ-ACK codebook;

a second receiving module 420, configured to receive a first DCI format, where the first DCI format schedules transmission of a first physical uplink shared channel PUSCH, and the first DCI format includes an uplink downlink assignment indication DAI field, and a first HARQ-ACK codebook is multiplexed and transmitted in the first PUSCH;

A codebook generating module 430, configured to generate the first HARQ-ACK codebook according to the uplink DAI field, where the first HARQ-ACK codebook includes first HARQ-ACK information, or the first HARQ-ACK codebook does not include the first HARQ-ACK information, where the first HARQ-ACK information includes HARQ-ACK feedback information corresponding to at least one physical downlink shared channel PDSCH scheduled by DCI format 1_ 0.

Corresponding to at least one method applied to the terminal device, the embodiment of the application further provides one or more terminal devices. The terminal device of the embodiment of the present application may implement any implementation manner of the foregoing method.

Detailed description of preferred embodiment 6

Corresponding to the processing method of at least one embodiment, an embodiment of the present application further provides a terminal device, which includes:

a first receiving unit, configured to receive a configuration signaling, where the configuration signaling is used to configure an enhanced type 2 eType-2 HARQ-ACK codebook;

a first receiving unit, configured to receive a second DCI format, where the second DCI format schedules a second PUSCH for transmission, and the second DCI format includes an uplink DAI field, and a second HARQ-ACK codebook is multiplexed and transmitted in the second PUSCH; the terminal equipment is configured with an eType-2 HARQ-ACK codebook;

A codebook generating unit, configured to generate the second HARQ-ACK codebook according to the uplink DAI field, where the second HARQ-ACK codebook includes second HARQ-ACK information, or the second HARQ-ACK codebook does not include the second HARQ-ACK information, where the second HARQ-ACK information includes HARQ-ACK feedback information corresponding to at least one pdcch PDSCH scheduled in DCI format 1_0, or HARQ-ACK feedback information corresponding to at least one PDSCH scheduled in DCI format 1_1, or HARQ-ACK feedback information corresponding to at least one PDSCH scheduled in DCI format 1_2, or the at least one PDSCH includes HARQ-ACK feedback information corresponding to an SPS PDSCH scheduled without DCI format. Or, the terminal device receives an SPS PDSCH release indicated by at least one DCI format sent by the network device, and the second HARQ-ACK information further includes HARQ-ACK feedback information corresponding to the SPS PDSCH release.

Embodiment 7 corresponds to the processing method of at least one embodiment, and an embodiment of the present application further provides a network device, referring to fig. 5, which includes:

A first sending module 510, configured to send a configuration signaling, where the configuration signaling is used to configure an enhanced type 2 eType-2 HARQ-ACK codebook;

a second sending module 520, configured to send a first DCI format, where the first DCI format schedules a first physical uplink shared channel, PUSCH, for transmission, and the first DCI format includes an uplink downlink assignment indication, DAI, field, and a first HARQ-ACK codebook is multiplexed and transmitted in the first PUSCH; the uplink DAI domain is used for generating the first HARQ-ACK codebook, the first HARQ-ACK codebook comprises first HARQ-ACK information, or the first HARQ-ACK codebook does not comprise the first HARQ-ACK information, wherein the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one Physical Downlink Shared Channel (PDSCH) scheduled by DCI format 1_0, and/or the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one SPS PDSCH scheduled without DCI format, and/or the first HARQ-ACK information comprises ACK feedback information corresponding to at least one SPS PDSCH release.

Corresponding to at least one method applied to the embodiment of the network device, the embodiment of the application also provides one or more network devices. The network device of the embodiment of the present application may implement any implementation manner of the foregoing method.

Best mode for carrying out the invention

Corresponding to the processing method of at least one of the above embodiments, an embodiment of the present application further provides a network device, which includes:

a third sending unit, configured to send a configuration signaling, where the configuration signaling is used to configure an enhanced type 2 eType-2 HARQ-ACK codebook;

a fourth sending unit, configured to send a second DCI format to the terminal device, where the second DCI format schedules a second PUSCH transmission, and the second DCI format includes an uplink DAI field, and a second HARQ-ACK codebook is multiplexed and transmitted in the second PUSCH; the uplink DAI domain is used for generating a second HARQ-ACK codebook, wherein the second HARQ-ACK codebook comprises second HARQ-ACK information, or the second HARQ-ACK codebook does not comprise the second HARQ-ACK information, wherein the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one PDSCH scheduled by DCI format 1_0, or HARQ-ACK feedback information corresponding to at least one PDSCH scheduled by DCI format 1_1, or HARQ-ACK feedback information corresponding to at least one PDSCH scheduled by DCI format 1_2, or the at least one PDSCH comprises HARQ-ACK feedback information corresponding to SPS PDSCH not scheduled by DCI format. Or, the terminal device receives an SPS PDSCH release indicated by at least one DCI format sent by the network device, and the second HARQ-ACK information further includes HARQ-ACK feedback information corresponding to the SPS PDSCH release.

Fig. 6 is a schematic block diagram of a communication device 600 according to an embodiment of the present application, where the communication device 600 includes a processor 610, and the processor 610 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, the communication device 600 may also include a memory 620. From the memory 620, the processor 610 may call and run a computer program to implement the method in the embodiment of the present application.

The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.

Optionally, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and in particular, may transmit information or data to or receive information or data transmitted by other devices.

The transceiver 630 may include a transmitter and a receiver, among others. The transceiver 630 may further include antennas, and the number of antennas may be one or more.

Optionally, the communication device 600 may be a network device according to this embodiment, and the communication device 600 may implement a corresponding process implemented by the network device in each method according to this embodiment, which is not described herein again for brevity.

Optionally, the communication device 600 may be a terminal device in this embodiment, and the communication device 600 may implement a corresponding process implemented by the terminal device in each method in this embodiment, which is not described herein again for brevity.

Fig. 7 is a schematic block diagram of a chip 700 according to an embodiment of the present application, where the chip 700 includes a processor 710, and the processor 710 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, chip 700 may also include memory 720. From the memory 720, the processor 710 can call and run a computer program to implement the method in the embodiment of the present application.

The memory 720 may be a separate device from the processor 710, or may be integrated into the processor 710.

Optionally, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, may obtain information or data transmitted by other devices or chips.

Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement a corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the chip may be applied to the terminal device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.

The aforementioned processors may be general purpose processors, Digital Signal Processors (DSPs), Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general purpose processor mentioned above may be a microprocessor or any conventional processor etc.

The above-mentioned memories may be either volatile or nonvolatile memories, or may include both volatile and nonvolatile memories. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM).

It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), Synchronous Link DRAM (SLDRAM), Direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Fig. 8 is a schematic block diagram of a communication system 800 according to an embodiment of the application, the communication system 800 comprising a terminal device 810 and a network device 820.

The terminal device 810 may be configured to implement the corresponding functions implemented by the terminal device in the methods of the embodiments of the present application, and the network device 820 may be configured to implement the corresponding functions implemented by the network device in the methods of the embodiments of the present application. For brevity, further description is omitted herein.

In the above embodiments, all or part of the implementation may be realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply any order of execution, and the order of execution of the processes should be determined by their functions and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

It can be clearly understood by those skilled in the art that, for convenience and simplicity of description, the specific working processes of the above-described systems, apparatuses, and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method for generating a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook is applied to a terminal device, and comprises the following steps:

a terminal device receives a first Downlink Control Information (DCI) format, wherein the first DCI format schedules transmission of a first Physical Uplink Shared Channel (PUSCH), the first DCI format comprises an uplink Downlink Allocation Indication (DAI) domain, a first hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook is multiplexed and transmitted in the first PUSCH, and the terminal device is configured with an enhanced type 2 eType-2 HARQ-ACK codebook;

The terminal device generates the first HARQ-ACK codebook according to the uplink DAI domain, wherein the first HARQ-ACK codebook comprises first HARQ-ACK information, or the first HARQ-ACK codebook does not comprise the first HARQ-ACK information, wherein the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one Physical Downlink Shared Channel (PDSCH) scheduled by a DCI format 1_0, and/or the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one SPS PDSCH scheduled without a DCI format, and/or the first HARQ-ACK information comprises ACK feedback information corresponding to at least one PDSCH release.
The method of claim 1, wherein the terminal device is further configured with a Type 1 Type-1 HARQ-ACK codebook, or the terminal device is further configured with a Type-2 HARQ-ACK codebook, or the terminal device is not configured with a Type-1 HARQ-ACK codebook and is not configured with a Type-2 HARQ-ACK codebook;

the terminal equipment generates a first HARQ-ACK codebook according to the uplink DAI domain, and the method comprises the following steps:

the terminal equipment determines a first codebook type according to the uplink DAI domain; the first codebook Type comprises one of a Type-1 HARQ-ACK codebook, a Type-2 HARQ-ACK codebook and an eType-2 HARQ-ACK codebook;

And the terminal equipment generates the first HARQ-ACK codebook according to the first codebook type.
The method of claim 2, wherein in the case that the terminal device is configured with a Type-1 HARQ-ACK codebook and an eType-2 HARQ-ACK codebook, the first codebook Type is a Type-1 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook; or,

and under the condition that the terminal equipment is not configured with a Type-1 HARQ-ACK codebook and is not configured with a Type-2 HARQ-ACK codebook, the first codebook Type is a Type-1 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook.
The method of claim 3, wherein the uplink DAI field includes a first uplink DAI field and a second uplink DAI field, and the determining, by the terminal device, a first codebook type according to the uplink DAI field comprises: the terminal device determines the first codebook type according to the second uplink DAI field, wherein,

if k2 bits included in the second uplink DAI field are all set to be 0, the first codebook Type is a Type-1 HARQ-ACK codebook, and k2 is an integer; or,

if the second uplink DAI domain comprises at least one DAI indication message and each DAI indication message in the at least one DAI indication message indicates a first preset value, the first codebook Type is a Type-1 HARQ-ACK codebook; or,

If at least one bit of the k2 bits included in the second uplink DAI field is not set to 0, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if the second uplink DAI domain comprises at least one DAI indication information and the at least one DAI indication information in the second uplink DAI domain does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if k2 bits included in the second uplink DAI field are all set to 0, the terminal device determines the first codebook type according to the first uplink DAI field; or

And if the second uplink DAI domain comprises at least one DAI indication message and each DAI indication message in the second uplink DAI domain indicates a first preset value, the terminal equipment determines the first codebook type according to the first uplink DAI domain.
The method of claim 3 or 4, wherein the uplink DAI field comprises a first uplink DAI field, and the determining, by the terminal device, a first codebook type according to the uplink DAI field comprises: the terminal device determines the first codebook type according to the first uplink DAI field, wherein,

if (k1-1) high-order bits MSB among the k1 bits included in the first uplink DAI field are all set to 0, the first codebook Type is a Type-1 HARQ-ACK codebook, and k1 is an integer greater than 1; or the like, or a combination thereof,

If at least one bit of (k1-1) MSBs among k1 bits included in the first uplink DAI field is not set to 0, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and the MSB in the first DAI indication information is set to be 0, the first codebook Type is a Type-1 HARQ-ACK codebook; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and the MSB in the first DAI indication information is set to be 1, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the MSB in the first DAI indication information is set to be 0, and the second DAI indication information indicates a first preset value, the first codebook Type is a Type-1 HARQ-ACK codebook; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, MSB in the first DAI indication information is set to be 1, or the second DAI indication information does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook; or,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the first DAI indication information indicates a first preset value, and MSB in the second DAI indication information is set to be 0, the first codebook Type is a Type-1 HARQ-ACK codebook; or,

If the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the first DAI indication information does not indicate a first preset value, or the MSB in the second DAI indication information is set to be 1, the first codebook type is an eType-2 HARQ-ACK codebook.
The method as claimed in any of claims 1 to 5, wherein the terminal device generating a first HARQ-ACK codebook according to the uplink DAI field comprises:

and the terminal equipment generates the first HARQ-ACK codebook according to the first bit in the uplink DAI domain and the Type-1 HARQ-ACK codebook.
The method of claim 6, wherein the upstream DAI field comprises a first upstream DAI field, the first bits comprising bits in the first upstream DAI field, wherein,

the first bit comprises 1 LSB of low order bits of k1 bits comprised by the first uplink DAI field, k1 is an integer greater than 1; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the first bit comprises the LSB in the first DAI indication information; or the like, or a combination thereof,

and if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the first bit comprises the LSB in the second DAI indication information.
The method of claim 6 or 7, wherein the generating, by the terminal device, the first HARQ-ACK codebook according to the first bit in the uplink DAI domain and the Type-1 HARQ-ACK codebook comprises:

if the first bit indicates a second preset value, the terminal equipment generates a first HARQ-ACK codebook according to a Type-1 HARQ-ACK codebook; or,

if the first bit indicates a third preset value and the PDSCH scheduled by the at least one DCI format 1_0 comprises a PDSCH scheduled by the DCI format 1_0, the terminal equipment generates the first HARQ-ACK codebook for the PDSCH; otherwise, the terminal equipment does not generate the first HARQ-ACK codebook according to the Type-1 HARQ-ACK codebook.
The method of claim 8, wherein the second preset value is 1 and the third preset value is 0.
The method of claim 8 or 9, wherein the method further comprises: and if the terminal equipment does not generate the first HARQ-ACK codebook according to the Type-1 HARQ-ACK codebook, the terminal equipment generates the first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook.
The method of claim 2, wherein the first codebook Type is a Type-2 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook in a case where the terminal device is configured with a Type-2 HARQ-ACK codebook and an eType-2 HARQ-ACK codebook.
The method of claim 11, wherein the uplink DAI field includes a first uplink DAI field and a second uplink DAI field, and the determining, by the terminal device, a first codebook type according to the uplink DAI field includes: the terminal equipment determines the first codebook type according to the second uplink DAI domain, wherein,

if k2 bits included in the second uplink DAI field are all set to 0, the first codebook Type is a Type-2 HARQ-ACK codebook, and k2 is an integer; or the like, or a combination thereof,

if the second uplink DAI domain comprises at least one DAI indication message and each DAI indication message in the at least one DAI indication message indicates a first preset value, the first codebook Type is a Type-2 HARQ-ACK codebook; or the like, or a combination thereof,

if at least one bit of the k2 bits included in the second uplink DAI field is not set to 0, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if the second uplink DAI domain comprises at least one piece of DAI indication information and the at least one piece of DAI indication information in the second uplink DAI domain does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if k2 bits included in the second uplink DAI field are all set to 0, the terminal device determines the first codebook type according to the first uplink DAI field; or

And if the second uplink DAI domain comprises at least one piece of DAI indication information and each piece of DAI indication information in the second uplink DAI domain indicates a first preset value, the terminal equipment determines the first codebook type according to the first uplink DAI domain.
The method of claim 11 or 12, wherein the uplink DAI field comprises a first uplink DAI field, and the determining, by the terminal device, a first codebook type according to the uplink DAI field comprises:

the terminal device determines the first codebook type according to the first uplink DAI field, wherein,

if (k1-2) high-order bits MSBs in the k1 bits included in the first uplink DAI field are all set to 0, and k1 is an integer greater than 2, the first codebook Type is a Type-2 HARQ-ACK codebook; or the like, or a combination thereof,

if at least one bit of (k1-2) MSBs among k1 bits included in the first uplink DAI field is not set to 0, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, and the second DAI indication information indicates a first preset value, the first codebook Type is a Type-2 HARQ-ACK codebook; or the like, or a combination thereof,

If the first uplink DAI domain comprises first DAI indication information and second DAI indication information, and the second DAI indication information does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information and the first DAI indication information indicates a first preset value, the first codebook Type is a Type-2 HARQ-ACK codebook; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, and the first DAI indication information does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook.
The method according to any of claims 1 and 11 to 13, wherein the terminal device is further configured with a Type-2 HARQ-ACK codebook, and the terminal device generates a first HARQ-ACK codebook according to the uplink DAI field, including:

and the terminal equipment generates the first HARQ-ACK codebook according to the second bit in the uplink DAI domain and the Type-2 HARQ-ACK codebook.
The method of claim 14, wherein the uplink DAI field comprises a first uplink DAI field, the second bit being a bit in the first uplink DAI field, wherein,

The second bit is 2 LSBs of lower bits among k1 bits included in the first uplink DAI field, and k1 is an integer greater than or equal to 2; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the second bit comprises a bit in the first DAI indication information; or the like, or a combination thereof,

and if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the second bit is a bit in the second DAI indication information.
The method of claim 14 or 15, wherein the terminal device generates the first HARQ-ACK codebook according to a second bit in the uplink DAI field and a Type-2 HARQ-ACK codebook, wherein a length of the first HARQ-ACK codebook is indicated by the second bit.
The method of any one of claims 4, 5, 12, 13, wherein the first preset value is 4.
The method of any one of claims 1 to 17,

the first HARQ-ACK codebook only comprises HARQ-ACK feedback information corresponding to the PDSCH scheduled by the at least one DCI format 1_ 0; or,

the first HARQ-ACK codebook comprises HARQ-ACK feedback information corresponding to the PDSCH scheduled by the at least one DCI format 1_0, and at least one of ACK feedback information corresponding to SPS PDSCH release and HARQ-ACK feedback information corresponding to SPS PDSCH release; or,

The first HARQ-ACK codebook comprises HARQ-ACK feedback information corresponding to the PDSCH scheduled by the at least one DCI format 1_0 and does not comprise HARQ-ACK feedback information corresponding to the PDSCH scheduled by the DCI format 1_ 1.
The method of any of claims 1 to 18, further comprising:

and the terminal equipment sends the first HARQ-ACK codebook through the first PUSCH.
A method for generating a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook is applied to a network device, and the method comprises the following steps:

configuring an enhanced type 2 eType-2 HARQ-ACK codebook for the terminal equipment;

sending a first DCI format to the terminal equipment, wherein the first DCI format schedules transmission of a first Physical Uplink Shared Channel (PUSCH), the first DCI format comprises an uplink Downlink Allocation Indication (DAI) domain, and the first PUSCH is multiplexed with a first hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook; the uplink DAI domain is used for generating the first HARQ-ACK codebook, the first HARQ-ACK codebook comprises first HARQ-ACK information, or the first HARQ-ACK codebook does not comprise the first HARQ-ACK information, wherein the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one Physical Downlink Shared Channel (PDSCH) scheduled by a DCI format 1_0, and/or the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one SPS PDSCH scheduled without a DCI format, and/or the first HARQ-ACK information comprises ACK feedback information corresponding to at least one SPS PDSCH release.
The method of claim 20, further comprising:

and configuring a Type 1 Type-1 HARQ-ACK codebook for the terminal equipment, or configuring a Type-2 HARQ-ACK codebook for the terminal equipment.
The method of claim 21, the uplink DAI field for generating the first HARQ-ACK codebook, comprising:

determining a first codebook type according to the uplink DAI domain; the first codebook Type comprises one of a Type-1 HARQ-ACK codebook, a Type-2 HARQ-ACK codebook and an eType-2 HARQ-ACK codebook;

and generating the first HARQ-ACK codebook according to the first codebook type.
The method of claim 22, wherein in case that the terminal device is configured with a Type-1 HARQ-ACK codebook and an eType-2 HARQ-ACK codebook, the first codebook Type is a Type-1 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook; or,

and under the condition that the terminal equipment is not configured with a Type-1 HARQ-ACK codebook and is not configured with a Type-2 HARQ-ACK codebook, the first codebook Type is a Type-1 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook.
The method of claim 23, wherein the uplink DAI field includes a first uplink DAI field and a second uplink DAI field, and determining a first codebook type according to the uplink DAI field comprises: determining the first codebook type according to the second uplink DAI field, wherein,

If k2 bits included in the second uplink DAI field are all set to 0, the first codebook Type is a Type-1 HARQ-ACK codebook, and k2 is an integer; or the like, or a combination thereof,

if the second uplink DAI domain comprises at least one DAI indication message and each DAI indication message in the at least one DAI indication message indicates a first preset value, the first codebook Type is a Type-1 HARQ-ACK codebook; or the like, or a combination thereof,

if at least one bit of the k2 bits included in the second uplink DAI field is not set to 0, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if the second uplink DAI domain comprises at least one DAI indication information and the at least one DAI indication information in the second uplink DAI domain does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook; or,

if k2 bits included in the second uplink DAI field are all set to 0, the terminal device determines the first codebook type according to the first uplink DAI field; or

And if the second uplink DAI domain comprises at least one DAI indication message and each DAI indication message in the second uplink DAI domain indicates a first preset value, the terminal equipment determines the first codebook type according to the first uplink DAI domain.
The method of claim 23 or 24, wherein the uplink DAI field includes a first uplink DAI field, and determining a first codebook type from the uplink DAI field comprises: determining the first codebook type according to the first uplink DAI field, wherein,

if (k1-1) high-order bits MSB among the k1 bits included in the first uplink DAI field are all set to 0, the first codebook Type is a Type-1 HARQ-ACK codebook, and k1 is an integer greater than 1; or the like, or a combination thereof,

if at least one bit of (k1-1) MSBs among k1 bits included in the first uplink DAI field is not set to 0, the first codebook type is an eType-2 HARQ-ACK codebook; or,

if the first uplink DAI domain comprises first DAI indication information and the MSB in the first DAI indication information is set to be 0, the first codebook Type is a Type-1 HARQ-ACK codebook; or,

if the first uplink DAI domain comprises first DAI indication information and the MSB in the first DAI indication information is set to be 1, the first codebook type is an eType-2 HARQ-ACK codebook; or,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, MSB in the first DAI indication information is set to be 0, and the second DAI indication information indicates a first preset value, the first codebook Type is a Type-1 HARQ-ACK codebook; or,

If the first uplink DAI domain comprises first DAI indication information and second DAI indication information, MSB in the first DAI indication information is set to be 1, or the second DAI indication information does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the first DAI indication information indicates a first preset value, and MSB in the second DAI indication information is set to be 0, the first codebook Type is a Type-1 HARQ-ACK codebook; or,

and if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the first DAI indication information does not indicate a first preset value, or the MSB in the second DAI indication information is set to be 1, the first codebook type is an eType-2 HARQ-ACK codebook.
The method of any of claims 20 to 25, wherein the uplink DAI field is used to generate the first HARQ-ACK codebook, comprising:

and generating the first HARQ-ACK codebook according to the first bit in the uplink DAI domain and the Type-1 HARQ-ACK codebook.
The method of claim 26, wherein the uplink DAI field comprises a first uplink DAI field, the first bit comprising a bit in the first uplink DAI field, wherein,

The first bit comprises 1 LSB of low order bits of k1 bits comprised by the first uplink DAI field, k1 is an integer greater than 1; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the first bit comprises the LSB in the first DAI indication information; or the like, or a combination thereof,

and if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the first bit comprises the LSB in the second DAI indication information.
The method of claim 26 or 27, wherein generating the first HARQ-ACK codebook according to the first bit in the uplink DAI domain and a Type-1 HARQ-ACK codebook comprises:

if the first bit indicates a second preset value, the terminal equipment generates a first HARQ-ACK codebook according to a Type-1 HARQ-ACK codebook; or,

if the first bit indicates a third preset value and the PDSCH scheduled by the at least one DCI format 1_0 comprises a PDSCH scheduled by the DCI format 1_0, the terminal equipment generates the first HARQ-ACK codebook for the PDSCH; otherwise, the first HARQ-ACK codebook is not generated according to the Type-1 HARQ-ACK codebook.
The method of claim 28, wherein the second preset value is 1 and the third preset value is 0.
The method of claim 28 or 29, wherein the method further comprises: and if the first HARQ-ACK codebook is not generated according to the Type-1 HARQ-ACK codebook, generating the first HARQ-ACK codebook according to the eType-2 HARQ-ACK codebook.
The method of claim 22, wherein the first codebook Type is a Type-2 HARQ-ACK codebook or an eType-2 HARQ-ACK codebook in case the terminal device is configured with a Type-2 HARQ-ACK codebook and an eType-2 HARQ-ACK codebook.
The method of claim 31, wherein the uplink DAI field includes a first uplink DAI field and a second uplink DAI field, and determining a first codebook type according to the uplink DAI field comprises: determining the first codebook type according to the second uplink DAI field, wherein,

if k2 bits included in the second uplink DAI field are all set to be 0, the first codebook Type is a Type-2 HARQ-ACK codebook, and k2 is an integer; or,

if the second uplink DAI domain comprises at least one DAI indication message and each DAI indication message in the at least one DAI indication message indicates a first preset value, the first codebook Type is a Type-2 HARQ-ACK codebook; or,

If at least one bit of the k2 bits included in the second uplink DAI field is not set to 0, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if the second uplink DAI domain comprises at least one piece of DAI indication information and the at least one piece of DAI indication information in the second uplink DAI domain does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if k2 bits included in the second uplink DAI field are all set to 0, determining the first codebook type according to the first uplink DAI field; or

And if the second uplink DAI domain comprises at least one DAI indication message and each DAI indication message in the second uplink DAI domain indicates a first preset value, determining the first codebook type according to the first uplink DAI domain.
The method of claim 31 or 32, wherein the uplink DAI field includes a first uplink DAI field, and determining a first codebook type from the uplink DAI field comprises:

determining the first codebook type according to the first uplink DAI field, wherein,

if (k1-2) high-order bits MSBs in the k1 bits included in the first uplink DAI field are all set to 0, and k1 is an integer greater than 2, the first codebook Type is a Type-2 HARQ-ACK codebook; or the like, or a combination thereof,

If at least one bit of (k1-2) MSBs among k1 bits included in the first uplink DAI field is not set to 0, the first codebook type is an eType-2 HARQ-ACK codebook; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, and the second DAI indication information indicates a first preset value, the first codebook Type is a Type-2 HARQ-ACK codebook; or the like, or a combination thereof,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, and the second DAI indication information does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook; or,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, and the first DAI indication information indicates a first preset value, the first codebook Type is a Type-2 HARQ-ACK codebook; or,

and if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, and the first DAI indication information does not indicate a first preset value, the first codebook type is an eType-2 HARQ-ACK codebook.
The method of any of claims 20, 31 to 33, further comprising: configuring a Type-2 HARQ-ACK codebook for the terminal equipment;

The uplink DAI field is configured to generate the first HARQ-ACK codebook, and includes:

and generating the first HARQ-ACK codebook according to the second bit in the uplink DAI domain and the Type-2 HARQ-ACK codebook.
The method of claim 34, wherein the uplink DAI field comprises a first uplink DAI field, the second bit being a bit in the first uplink DAI field, wherein,

the second bit is a low order bit LSB of 2 bits of k1 bits included in the first uplink DAI field, and k1 is an integer greater than or equal to 2; or,

if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the second bit comprises a bit in the first DAI indication information; or,

and if the first uplink DAI domain comprises first DAI indication information and second DAI indication information, the second bit is a bit in the second DAI indication information.
The method of claim 34 or 35, wherein the first HARQ-ACK codebook is generated according to a second bit in the uplink DAI field and a Type-2 HARQ-ACK codebook, wherein a length of the first HARQ-ACK codebook is indicated by the second bit.
The method of any of claims 24, 25, 32, 33, wherein the first preset value is 4.
The method of any one of claims 1 to 37,

the first HARQ-ACK codebook only comprises HARQ-ACK feedback information corresponding to the PDSCH scheduled by the at least one DCI format 1_ 0; or,

the first HARQ-ACK codebook comprises HARQ-ACK feedback information corresponding to the PDSCH scheduled by the at least one DCI format 1_0, and at least one of ACK feedback information corresponding to SPS PDSCH release and HARQ-ACK feedback information corresponding to SPS PDSCH release; or,

the first HARQ-ACK codebook comprises HARQ-ACK feedback information corresponding to the PDSCH scheduled by the at least one DCI format 1_0 and does not comprise HARQ-ACK feedback information corresponding to the PDSCH scheduled by the DCI format 1_ 1.
A terminal device, comprising:

a first receiving module, configured to receive a configuration signaling, where the configuration signaling is used to configure an enhanced type 2 eType-2 HARQ-ACK codebook;

a second receiving module, configured to receive a first DCI format, where the first DCI format schedules transmission of a first physical uplink shared channel PUSCH, and the first DCI format includes an uplink downlink assignment indication DAI field, and a first HARQ-ACK codebook is multiplexed and transmitted in the first PUSCH;

a codebook generating module, configured to generate the first HARQ-ACK codebook according to the uplink DAI field, where the first HARQ-ACK codebook includes first HARQ-ACK information, or the first HARQ-ACK codebook does not include the first HARQ-ACK information, where the first HARQ-ACK information includes HARQ-ACK feedback information corresponding to at least one PDSCH scheduled in DCI format 1_0, and/or the first HARQ-ACK information includes HARQ-ACK feedback information corresponding to at least one PDSCH scheduled without DCI format, and/or the first HARQ-ACK information includes ACK feedback information corresponding to at least one release of SPS PDSCH.
A network device, comprising:

a first sending module, configured to send a configuration signaling, where the configuration signaling is used to configure an enhanced type 2 eType-2 HARQ-ACK codebook;

a second sending module, configured to send a first DCI format, where the first DCI format schedules a first physical uplink shared channel, PUSCH, for transmission, and the first DCI format includes an uplink downlink assignment indication, DAI, field, and a first HARQ-ACK codebook is multiplexed and transmitted in the first PUSCH; the uplink DAI domain is used for generating the first HARQ-ACK codebook, the first HARQ-ACK codebook comprises first HARQ-ACK information, or the first HARQ-ACK codebook does not comprise the first HARQ-ACK information, wherein the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one Physical Downlink Shared Channel (PDSCH) scheduled by a DCI format 1_0, and/or the first HARQ-ACK information comprises HARQ-ACK feedback information corresponding to at least one SPS PDSCH scheduled without a DCI format, and/or the first HARQ-ACK information comprises ACK feedback information corresponding to at least one SPS PDSCH release.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor calling and executing the computer program stored in the memory, performing the steps of the method according to any one of claims 1 to 19.
A network device, comprising: a processor and a memory for storing a computer program, the processor calling and executing the computer program stored in the memory to perform the steps of the method according to any of claims 20 to 38.
A chip, comprising:

a processor for calling up and running a computer program from a memory so that a device on which the chip is installed performs the steps of the method of any one of claims 1 to 19.
A chip, comprising:

a processor for retrieving and running a computer program from memory to cause a device on which the chip is installed to perform the steps of the method of any of claims 20 to 38.
A computer-readable storage medium storing a computer program, wherein,

the computer program causes a computer to perform the steps of the method according to any one of claims 1 to 19.
A computer-readable storage medium storing a computer program, wherein,

the computer program causing a computer to perform the steps of the method of any of claims 20 to 38.
A computer program product comprising computer program instructions, wherein,

The computer program instructions cause a computer to perform the steps of the method of any one of claims 1 to 19.
A computer program product comprising computer program instructions, wherein,

the computer program instructions cause a computer to perform the steps of the method of any of claims 20 to 38.
A computer program for causing a computer to perform the steps of the method of any one of claims 1 to 19.
A computer program for causing a computer to perform the steps of the method of any one of claims 20 to 38.