Method, device and terminal for determining hybrid automatic repeat request-acknowledgement HARQ-ACK codebook

Abstract

The present application discloses a method, apparatus, and terminal for determining a hybrid automatic repeat request-acknowledge HARQ-ACK codebook, which belong to the field of communication technology. In an embodiment of the present application, the method for determining a HARQ-ACK codebook includes: a terminal determines a target HARQ-ACK codebook based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel, where the HARQ-ACK codebook type corresponding to the physical downlink channel includes a type 1 HARQ-ACK codebook and a type 2 HARQ-ACK codebook, and the scenario type corresponding to the physical downlink channel includes a first scenario and a second scenario, in which the first scenario is that the terminal reports only HARQ-ACKs corresponding to a designated physical downlink channel that are received in a candidate PDSCH receiving occasion on one PUCCH, and the second scenario is a scenario other than the first scenario.

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This invention claims priority to a Chinese patent application submitted to the China Patent Office on May 06, 2022, bearing application number 202210488104.6 and titled "Method, apparatus and terminal for determining hybrid automatic repeat request-acknowledgement HARQ-ACK codebook", the entire contents of which are incorporated herein by reference.

[0002] The present application relates to the field of communications technology, and in particular to a method, apparatus and terminal for determining a hybrid automatic repeat request-acknowledgement HARQ-ACK codebook. [Background technology]

[0003] Currently, in the New Radio (NR) system, the unicast physical downlink control channel (PDCCH) and the unicast physical downlink shared channel (PDSCH) support Hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback, and the multicast PDSCH and multicast PDCCH also support HARQ-ACK feedback.

[0004] However, how a terminal realizes the HARQ-ACK codebook decision for multicast HARQ-ACK and / or unicast HARQ-ACK is currently a technical problem that needs to be urgently solved. Summary of the Invention [Problem to be solved by the invention]

[0005] The embodiments of the present application provide a hybrid automatic repeat request-acknowledge HARQ-ACK codebook determination method, device, and terminal, which can realize HARQ-ACK codebook determination for multicast HARQ-ACK and unicast HARQ-ACK. [Means for solving the problem]

[0006] According to a first aspect, a method for determining a hybrid automatic repeat request-acknowledge HARQ-ACK codebook is provided, the method including: a terminal determining a target HARQ-ACK codebook based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel, where the HARQ-ACK codebook type corresponding to the physical downlink channel includes a type 1 HARQ-ACK codebook and a type 2 HARQ-ACK codebook, the scenario type corresponding to the physical downlink channel includes a first scenario and a second scenario, the first scenario is that the terminal reports only HARQ-ACKs received in a candidate PDSCH reception occasion on one PUCCH and corresponding to a designated physical downlink channel, and the second scenario is a scenario other than the first scenario.

[0007] According to a second aspect, there is provided an apparatus for determining a hybrid automatic repeat request-acknowledge HARQ-ACK codebook, the apparatus including: a determining module for determining a target HARQ-ACK codebook based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel, where the HARQ-ACK codebook type corresponding to the physical downlink channel includes a type 1 HARQ-ACK codebook and a type 2 HARQ-ACK codebook, and the scenario type corresponding to the physical downlink channel includes a first scenario and a second scenario, in which the first scenario is that the terminal reports only HARQ-ACKs received in a candidate PDSCH reception occasion on one PUCCH and corresponding to a designated physical downlink channel, and the second scenario is a scenario other than the first scenario.

[0008] According to a third aspect, there is provided a terminal including a processor and a memory, the memory storing a program or instructions operable to run on the processor, the program or instructions being operable when executed by the processor to implement the steps of the method of the first aspect.

[0009] According to a fourth aspect, there is provided a terminal, the terminal comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, the processor being adapted to run a program or instructions and to implement the steps of the method according to the first aspect.

[0010] According to a fifth aspect, there is provided a wireless communication system, the wireless communication system including a terminal and a network side device, the terminal being adapted to perform steps of the method according to the first aspect.

[0011] According to a sixth aspect, there is provided a readable storage medium having stored thereon a program or instructions which, when executed by a processor, implements the steps of the method according to the first aspect.

[0012] According to a seventh aspect, there is provided a chip, the chip comprising a processor and a communication interface, the communication interface coupled to the processor, the processor running a program or instructions and adapted to implement the steps of the method according to the first aspect.

[0013] According to an eighth aspect, there is provided a computer program product / program product stored on a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the method according to the first aspect. Effect of the Invention

[0014] In an embodiment of the present application, the terminal determines a target HARQ-ACK codebook based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel, thereby providing an effective HARQ-ACK codebook determination method for multicast HARQ-ACK and / or unicast HARQ-ACK, and ensuring the performance of the communication system. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 is a structural schematic diagram of a wireless communication system according to an exemplary embodiment of the present application; [Diagram 2] 4 is a flowchart of a method for determining a HARQ-ACK codebook according to an exemplary embodiment of the present application; [Diagram 3] 4 is a flowchart of a method for determining a HARQ-ACK codebook according to another exemplary embodiment of the present application; [Figure 4]FIG. 2 is a structural schematic diagram of a HARQ-ACK codebook determining device according to an exemplary embodiment of the present application; [Diagram 5] FIG. 2 is a structural schematic diagram of a terminal according to an exemplary embodiment of the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] The following clearly describes the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art are within the scope of protection of the present application.

[0017] The terms "first," "second," etc. in the specification and claims of the present application are intended to distinguish between similar objects and are not intended to describe a particular order or sequence. It is to be understood that the terms so used are interchangeable where appropriate, such that the embodiments of the present application may be performed in an order other than that shown or described herein, and that the objects distinguished by "first" and "second" are generally of the same type and do not limit the number of objects, e.g., the first object may be one or more. It is to be noted that "and / or" in the specification and claims represents at least one of the objects connected, and the character " / " generally represents an "or" relationship between the related objects.

[0018] It should be noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be applied to other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are always used interchangeably, and the techniques described may be used in the above-mentioned systems and radio technologies, or may be used in other systems and radio technologies. Although the following description describes an NR system for illustrative purposes and uses NR terminology in most of the following description, these techniques may also be applied to applications other than NR system applications, such as sixth generation (6G) and 10G (11G) systems. th This may be applied to a 6G (6th Generation) communication system.

[0019] 1 shows a block diagram of a wireless communication system to which an embodiment of the present application can be applied. The wireless communication system includes a terminal 11 and a network side device 12. Here, the terminal 11 may be a mobile phone, a tablet personal computer, a laptop computer (also called a notebook computer), a personal digital assistant (PDA), a palmtop computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR) / virtual reality (VR) device, a robot, a wearable device, an in-vehicle device (Vehicle User Equipment, VUE), a pedestrian user equipment (PUE), a smart home (home devices having a wireless communication function, such as a refrigerator, a television, a washing machine, or furniture), a game machine, a personal computer, a mobile phone, a mobile terminal (Mobile Internet Device, MID), an augmented reality (AR) / virtual reality (VR) device, a robot, a wearable device, a mobile user equipment (VUE), a pedestrian user equipment (PUE), a smart home (home devices having a wireless communication function, such as a refrigerator, a television, a washing machine, or furniture), a game machine, a personal computer, a mobile phone, a mobile terminal (Mobile Internet Device, MID), ... terminal (Mobile Internet Device, MID), a mobile phone, a mobile terminal (Mobile Internet Device, MID), a mobile phone, a mobile terminal (Mobile Internet Device, MID), a mobile phone, a mobile terminal (Mobile Internet Device, MID), a mobile phone, a mobile terminal (Mobile Internet Device, M The network side equipment 12 may be a terminal side equipment such as a terminal computer (PC), a deposit and withdrawal machine or a self-service machine. The wearable device includes a smart watch, a smart wristband, a smart earphone, a smart glasses, a smart accessory (smart bracelet, smart hand chain, smart finger ring, smart necklace, smart ankle bracelet, smart anklet, etc.), a smart band, a smart clothing, etc. It should be noted that the terminal 11 in the embodiment of the present application is not limited to a specific type. The network side equipment 12 may include an access network equipment or a core network equipment. Here, the access network equipment 12 may be called a radio access network equipment, a radio access network (Radio Access Network, RAN), a radio access network function, or a radio access network unit.The access network equipment 12 may include a base station, a Wireless Local Area Network (WLAN) access point, or a WiFi node, etc. The base station may be called a Node B, an evolved Node B (eNB), an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a home B node, a home evolved B node, a Transmitting Receiving Point (TRP), or some other suitable term in the art, and the base station is not limited to a specific technical term as long as the same technical effect is achieved. It should be noted that the embodiments of the present application only take the base station in the NR system as an example, and do not limit the specific type of the base station.

[0020] The following describes in detail the technical solutions according to the embodiments of the present application through several embodiments and their application scenarios in conjunction with the drawings.

[0021] As shown in Figure 2, a flowchart of a method 200 for determining a HARQ-ACK codebook according to an exemplary embodiment of the present application, the method 200 may be performed by a terminal, but is not limited to this, specifically may be performed by hardware and / or software installed in the terminal. In this embodiment, the method 200 may include at least the following steps:

[0022] S210, the terminal determines a target HARQ-ACK codebook based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel.

[0023] Here, the HARQ-ACK codebook type corresponding to the physical downlink channel includes a type 1 HARQ-ACK codebook (e.g., pdsch-HARQ-ACK-Codebook=semi-static) and a type 2 HARQ-ACK codebook (e.g., pdsch-HARQ-ACK-Codebook-Multicast=dynamic). For example, when the physical downlink channel includes a unicast physical downlink channel and a multicast physical downlink channel, the HARQ-ACK codebook type corresponding to the unicast physical downlink channel may be a type 1 HARQ-ACK codebook, and the HARQ-ACK codebook type corresponding to the multicast physical downlink channel may be a type 2 HARQ-ACK codebook. Also, for example, the HARQ-ACK codebook type corresponding to the unicast physical downlink channel may be a type 2 HARQ-ACK codebook. The HARQ-ACK codebook type corresponding to the multicast physical downlink channel may be a type 1 HARQ-ACK codebook. It can be understood that the HARQ-ACK codebook type corresponding to the physical downlink channel mentioned in this embodiment may be, but is not limited to, the above-mentioned multiple types.

[0024] The scenario type corresponding to the physical downlink channel includes a first scenario (which may be called a Fallback scenario) and a second scenario (which may be called a non-Fallback scenario), in which the terminal reports only a HARQ-ACK corresponding to a designated physical downlink channel received in a candidate PDSCH reception occasion on one Physical Uplink Control Channel (PUCCH) (e.g., the terminal is scheduled to feed back a HARQ-ACK corresponding to the designated physical downlink channel only on one PUCCH), and the second scenario is a scenario other than the first scenario (e.g., the terminal is scheduled to feed back a HARQ-ACK corresponding to a physical downlink channel other than the designated physical downlink channel on one PUCCH). Here, the first scenario and / or the second scenario may be realized by a protocol agreement, a configuration by a higher layer, or a configuration by a network side, and is not limited here.

[0025] Here, the physical downlink channel referred to in this embodiment may be a PDSCH and / or a PDCCH. For example, if the terminal needs to feed back a HARQ-ACK corresponding to a unicast physical downlink channel (e.g., unicast PDSCH, unicast PDCCH) and a HARQ-ACK corresponding to a multicast physical downlink channel (e.g., multicast PDCCH, multicast PDSCH) in the same time unit (e.g., slot, subslot, symbol, subsymbol, etc.), and the HARQ-ACK corresponding to the unicast physical downlink channel has the same priority as the HARQ-ACK corresponding to the multicast physical downlink channel, the physical downlink channel may include a unicast physical downlink channel and a multicast physical downlink channel, etc.

[0026] In addition, in this embodiment, the above-mentioned physical downlink channel may be a dynamic grant (DG) physical downlink channel or a semi-persistent scheduling (SPS) physical downlink channel, etc., and is not limited thereto.

[0027] It should be noted that if the physical downlink channel is a PDCCH, the terminal only needs to feed back a HARQ-ACK corresponding to a designated PDCCH, where the designated PDCCH may be a PDCCH instructing the release of an SPS PDSCH, a PDCCH instructing secondary cell dormancy and no PDSCH scheduled, a PDCCH instructing the update of a Transmission Configuration Indicator (TCI) state, etc.

[0028] In this embodiment, the terminal determines a target HARQ-ACK codebook based on a HARQ-ACK codebook type and / or scenario type corresponding to a physical downlink channel, thereby providing an effective HARQ-ACK codebook determination method for multicast HARQ-ACK and / or unicast HARQ-ACK, realizing reporting of HARQ-ACK information, and ensuring the performance of the communication system.

[0029] As shown in Figure 3, a flowchart of a method 300 for determining a HARQ-ACK codebook according to an exemplary embodiment of the present application, the method 300 may be performed by a terminal, but is not limited to this, specifically may be performed by hardware and / or software installed in the terminal. In this embodiment, the method 300 may include at least the following steps:

[0030] S310, the terminal determines a target HARQ-ACK codebook based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel.

[0031] Here, the HARQ-ACK codebook type corresponding to the physical downlink channel includes a type 1 HARQ-ACK codebook and a type 2 HARQ-ACK codebook, and the scenario type corresponding to the physical downlink channel includes a first scenario and a second scenario, in which the first scenario is for the terminal to report a HARQ-ACK corresponding to a specified physical downlink channel that is received in a candidate PDSCH reception occasion on one PUCCH, and the second scenario is a scenario other than the first scenario.

[0032] For understanding, the implementation process of S310 may be referred to the relevant description in the method embodiment 200. In addition, in one possible implementation manner, the designated physical downlink channel may include any one of the following (11) to (13):

[0033] (11) A specific PDCCH, the specific PDCCH carrying Downlink Control Information (DCI) of a first format, and the DCI of the first format indicates a release of an SPS PDSCH, where a Downlink assignment index (DAI) corresponding to the DCI of the first format is 1.

[0034] Alternatively, if the particular PDCCH is a unicast physical downlink channel (e.g. a PDCCH scrambled by a Configured Scheduling Radio Network Temporary Identifier (CS-RNTI)), the first format is DCI 1_0, or if the particular PDCCH is a multicast physical downlink channel (e.g. a PDCCH scrambled by a Group- Configured Scheduling-RNTI (G-CS-RNTI)), the second format DCI is DCI 4_1.

[0035] (12) A specific PDSCH, the specific PDSCH being scheduled by a DCI of a second format, and a DAI corresponding to the DCI of the second format being 1.

[0036] Alternatively, if the specific PDSCH is a unicast physical downlink channel (e.g., Cell RNTI (C-RNTI), Cell-Radio Network Temporary Identifier (C-RNTI) scrambled), the DCI of the second format is DCI 1_0, or if the specific PDSCH is a multicast physical downlink channel (e.g., group RNTI, G-RNTI scrambled), the DCI of the second format is DCI 4_1. The DAI is a Counter DAI (C-DAI).

[0037] In addition, in one implementation, the specific PDSCH may be located in a primary cell (PCell). For example, when the specific PDSCH is a unicast PDSCH, the unicast PDSCH is located in a PCell. Correspondingly, when the specific PDSCH is a multicast PDSCH, the multicast PDSCH may be located in a PCell or in a cell other than the PCell, for example, a cell in which multicast reception is configured.

[0038] (13) At least one SPS PDSCH.

[0039] Of course, in other implementation manners, the process of the terminal determining the target HARQ-ACK codebook according to the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel is different. The following describes the two different implementation manners in combination, and the contents are as follows:

[0040] Implementation method 1 When a HARQ-ACK codebook type corresponding to a first physical downlink channel is the type 1 HARQ-ACK codebook (which may also be referred to as a type 1 type or a semi-static codebook type) and a HARQ-ACK codebook type corresponding to a second physical downlink channel is the type 2 HARQ-ACK codebook (which may also be referred to as a type 2 type or a dynamic codebook type), the terminal generates at least two HARQ-ACK sub-codebooks from a first HARQ-ACK sub-codebook, a second HARQ-ACK sub-codebook, and a third HARQ-ACK sub-codebook, and cascades the generated HARQ-ACK sub-codebooks to obtain the target HARQ-ACK codebook.

[0041] Here, the first HARQ-ACK sub-codebook corresponds to the first physical downlink channel. As a possible implementation manner, when the scenario type corresponding to the first physical downlink channel is different, the manner in which the terminal generates the first HARQ-ACK sub-codebook may also be different. For example, when the scenario type corresponding to the first physical downlink channel is the first scenario, the terminal generates the first HARQ-ACK sub-codebook based on the received HARQ-ACK corresponding to the first physical downlink channel.

[0042] Also, for example, when the scenario type corresponding to the first physical downlink channel is the second scenario, the terminal determines a candidate PDSCH reception occasion based on a time domain resource assignment (TDRA) table corresponding to the first physical downlink channel, and generates the first HARQ-ACK sub-codebook based on the candidate PDSCH reception occasion. As can be understood, when the terminal determines the candidate PDSCH reception occasion based on TDRA, the terminal may realize the determination of the candidate PDSCH reception occasion in combination with a timing K1 from PDSCH to HARQ-ACK feedback, a semi-static uplink / downlink configuration, etc. Here, the K1 represents the number of time units from a time unit in which the PDSCH reception position of the terminal is located to HARQ feedback. That is, if the terminal receives a PDSCH in time unit n, it feeds back corresponding HARQ information in time unit n+K1.

[0043] In addition, the first HARQ-ACK sub-codebook may include a HARQ-ACK sub-codebook corresponding to a DG PDSCH in the first physical downlink channel and / or a HARQ-ACK sub-codebook corresponding to an SPS PDSCH, that is, for a type 1 HARQ-ACK codebook, the HARQ-ACKs of the DG PDSCH and the SPS PDSCH may both be determined according to candidate PDSCH receiving occasions.

[0044] The second HARQ-ACK sub-codebook corresponds to a DG PDSCH in the second physical downlink channel. In one implementation, the terminal may generate the second HARQ-ACK sub-codebook based on a type 2 codebook generation method (e.g., based on a DAI).

[0045] The third HARQ-ACK sub-codebook corresponds to the SPS PDSCH in the second physical downlink channel. In one implementation, the terminal may generate the third HARQ-ACK sub-codebook according to an SPS PDSCH HARQ-ACK codebook generation method. For example, the terminal may generate the third HARQ-ACK sub-codebook according to a serving cell index, an SPS PDSCH configuration index, a slot in which the SPS PDSCH is located, etc. It should be noted that the third HARQ-ACK sub-codebook only includes HARQ-ACK corresponding to the SPS PDSCH in the second physical downlink channel.

[0046] Of course, the first physical downlink channel mentioned in implementation method 1 is a unicast physical downlink channel (e.g., unicast PDSCH, unicast PDCCH), and the second physical downlink channel is a multicast physical downlink channel (e.g., multicast PDSCH, multicast PDCCH), or the first physical downlink channel is a multicast physical downlink channel, and the second physical downlink channel is a unicast physical downlink channel.

[0047] Furthermore, in one implementation, when the terminal cascades the generated HARQ-ACK sub-codebooks, the cascading order between the HARQ-ACK sub-codebooks may be realized by protocol agreement, by configuration by a higher layer, or by autonomous determination by the terminal, thereby ensuring that the terminal and the network side device have the same understanding of the order of the HARQ-ACK sub-codebooks, and when the network side device receives the target HARQ-ACK codebook sent by the terminal, it clarifies the position of the HARQ-ACK corresponding to the SPS PDSCH in the target HARQ-ACK codebook to realize the determined resource scheduling.

[0048] It should be noted that, when the cascading order between the HARQ-ACK sub-codebooks is autonomously determined by the terminal, the terminal may report the cascading order to a network side device.

[0049] Based on the description of the above implementation manner 1, if the unicast HARQ-ACK codebook is configured as type 1, i.e., pdsch-HARQ-ACK-Codebook=semi-static, the multicast HARQ-ACK codebook is configured as type 2, i.e., pdsch-HARQ-ACK-Codebook-Multicast=dynamic, and the unicast SPS PDSCH and multicast SPS PDSCH of the terminal are activated, the terminal may generate a target HARQ-ACK codebook according to the following example 1 or example 2, which is as follows:

[0050] Example 1 In a certain uplink time unit (e.g., slot or subslot), when a terminal is scheduled to feed back a HARQ-ACK corresponding to a unicast DG PDSCH, a HARQ-ACK corresponding to a unicast SPS PDSCH, a HARQ-ACK corresponding to a multicast DG PDSCH, and a HARQ-ACK for a multicast SPS PDSCH, the terminal may determine a HARQ-ACK codebook in the following manner:

[0051] (a) Since the scenario type corresponding to the unicast PDSCH (i.e., the first physical downlink channel) is the second scenario, the terminal may determine a candidate PDSCH receiving occasion corresponding to the unicast based on the TDRA table corresponding to the unicast PDSCH (which may be referred to as the TDRA table corresponding to the unicast DCI), K1 (which may be referred to as the K1 corresponding to the unicast DCI) and the uplink and downlink configuration, and may further generate a first HARQ-ACK sub-codebook corresponding to the unicast PDSCH based on the candidate PDSCH receiving occasion. The first HARQ-ACK sub-codebook includes HARQ-ACK corresponding to the unicast DG PDSCH and the unicast SPS PDSCH.

[0052] (b) The terminal may generate, based on the DAI, a second HARQ-ACK sub-codebook corresponding to the multicast DG PDSCH.

[0053] (c) The terminal may generate a third HARQ-ACK sub-codebook corresponding to the multicast SPS PDSCH based on the SPS PDSCH configuration index, the slot in which the SPS PDSCH is located, and so on.

[0054] (d) The terminal cascades the first HARQ-ACK sub-codebook, the second HARQ-ACK sub-codebook, and the third HARQ-ACK sub-codebook in a first order to obtain a target HARQ-ACK codebook, where the first order may be (first HARQ-ACK sub-codebook, second HARQ-ACK sub-codebook, third HARQ-ACK sub-codebook), (first HARQ-ACK sub-codebook, third HARQ-ACK sub-codebook, second HARQ-ACK sub-codebook), (third HARQ-ACK sub-codebook, second HARQ-ACK sub-codebook, first HARQ-ACK sub-codebook), etc., and is not limited thereto.

[0055] It should be noted that in example 1, the unicast DG PDSCH and the unicast SPS PDSCH belong to the aforementioned first physical downlink channel, and the multicast SPS PDSCH and the multicast DG PDSCH belong to the aforementioned second physical downlink channel.

[0056] Example 2 In a certain uplink time unit (for example, slot or subslot), the terminal is scheduled to feed back HARQ-ACK of unicast DG PDSCH (or unicast DG PDCCH), HARQ-ACK corresponding to multicast DG PDSCH, and HARQ-ACK corresponding to multicast SPS PDSCH. Here, the unicast DG PDSCH is a PDSCH scheduled by DCI 1_0 in Pcell, and DCI 1_0 corresponds to DAI=1 (or unicast DCI indicating release of SPS PDSCH or unicast DCI indicating Scell ​​dormancy). That is, the scenario type corresponding to the unicast DG PDSCH (or unicast PDCCH) is the first scenario. Then, the terminal may determine a target HARQ-ACK codebook in the following manner.

[0057] (a) The terminal generates a first HARQ-ACK sub-codebook corresponding to a unicast DG PDSCH (or a unicast DG PDCCH).

[0058] (b) The terminal may generate a second HARQ-ACK sub-codebook corresponding to a multicast DG PDSCH based on the DAI.

[0059] (c) The terminal may generate a third HARQ-ACK sub-codebook corresponding to the multicast SPS PDSCH based on an SPS PDSCH configuration index, a slot in which the SPS PDSCH is located, and so on.

[0060] (d) The terminal cascades the first HARQ-ACK sub-codebook, the second HARQ-ACK sub-codebook, and the third HARQ-ACK sub-codebook in a second order to obtain a target HARQ-ACK codebook.

[0061] Here, the second order may be (first HARQ-ACK sub-codebook, second HARQ-ACK sub-codebook, third HARQ-ACK sub-codebook), (first HARQ-ACK sub-codebook, third HARQ-ACK sub-codebook, second HARQ-ACK sub-codebook), (third HARQ-ACK sub-codebook, second HARQ-ACK sub-codebook, first HARQ-ACK sub-codebook), etc., and is not limited thereto.

[0062] In addition, when the unicast HARQ-ACK codebook is configured as type 2, i.e., pdsch-HARQ-ACK-Codebook-Multicast=dynamic, the multicast HARQ-ACK codebook is configured as type 1, i.e., pdsch-HARQ-ACK-Codebook=semi-static, and the unicast SPS PDSCH and multicast SPS PDSCH of the terminal are activated, the manner in which the terminal determines the target HARQ-ACK codebook is similar to that of Examples 1 and 2 described above, and will not be described further here in order to avoid repetition.

[0063] Implementation method 2 When a HARQ-ACK codebook type corresponding to a first physical downlink channel is the type 1 HARQ-ACK codebook and a HARQ-ACK codebook type corresponding to a second physical downlink channel is the type 2 HARQ-ACK codebook, the terminal executes the following (21) or (22).

[0064] (21) When a scenario type corresponding to the first physical downlink channel is the second scenario, generate at least two HARQ-ACK sub-codebooks from a first HARQ-ACK sub-codebook, a second HARQ-ACK sub-codebook, and a third HARQ-ACK sub-codebook, and cascade-connect the generated HARQ-ACK sub-codebooks to obtain the target HARQ-ACK codebook, where the first HARQ-ACK sub-codebook corresponds to the first physical downlink channel, the second HARQ-ACK sub-codebook corresponds to a DG PDSCH in the second physical downlink channel, and the third HARQ-ACK sub-codebook corresponds to a SPS PDSCH in the second physical downlink channel. Here, the first physical downlink channel is a unicast physical downlink channel and the second physical downlink channel is a multicast physical downlink channel, or the first physical downlink channel is a multicast physical downlink channel and the second physical downlink channel is a unicast physical downlink channel.

[0065] As can be understood, the implementation method mentioned in (21) has the same or corresponding technical characteristics as the above-mentioned implementation method 1, so for the implementation process of (21), please refer to the relevant description in the implementation method 1 of the method, and in order to avoid repetition, no further description will be given here.

[0066] (22) When a scenario type corresponding to the first physical downlink channel is the first scenario, or when the target HARQ-ACK that needs to be fed back includes only a HARQ-ACK corresponding to an SPS PDSCH in the first physical downlink channel, generate a fourth HARQ-ACK sub-codebook and / or a fifth HARQ-ACK sub-codebook, and cascade-connect the fourth HARQ-ACK sub-codebook and the fifth HARQ-ACK sub-codebook to obtain the HARQ-ACK codebook.

[0067] Wherein, the fourth HARQ-ACK sub-codebook corresponds to a DG PDSCH in the second physical downlink channel. In one implementation, the terminal may generate the fourth HARQ-ACK sub-codebook based on a type 2 codebook generation method (for example, based on a DAI).

[0068] The fifth HARQ-ACK sub-codebook corresponds to at least one of an SPS PDSCH in a first physical downlink channel, an SPS PDSCH in a second physical downlink channel, and the designated physical downlink channel in the first physical downlink channel. In one implementation, the terminal may generate the fifth HARQ-ACK sub-codebook according to an SPS PDSCH HARQ-ACK codebook generation method. For example, the terminal may generate the fifth HARQ-ACK sub-codebook according to a serving cell index, an SPS PDSCH configuration index, a slot in which an SPS PDSCH is located, etc.

[0069] Of course, the first physical downlink channel mentioned in implementation method 2 is a unicast physical downlink channel and the second physical downlink channel is a multicast physical downlink channel, or the first physical downlink channel is a multicast physical downlink channel and the second physical downlink channel is a unicast physical downlink channel.

[0070] Optionally, when the terminal cascades the generated fourth HARQ-ACK sub-codebook and the fifth HARQ-ACK sub-codebook, the involved cascading order may be realized by protocol agreement, configuration by a higher layer, configuration by a network side, or autonomous decision of the terminal, thereby ensuring that the terminal and the network side device have the same understanding of the order of the fourth HARQ-ACK sub-codebook and the fifth HARQ-ACK sub-codebook, and further, when the network side device receives the target HARQ-ACK codebook sent by the terminal, it clarifies the position of the HARQ-ACK corresponding to the SPS PDSCH in the target HARQ-ACK codebook.

[0071] It should be noted that when the cascading order between the fourth HARQ-ACK sub-codebook and the fifth HARQ-ACK sub-codebook is autonomously determined by the terminal, the terminal may report the cascading order to a network side device.

[0072] Based on the description of the above implementation manner 2, if the unicast HARQ-ACK codebook is configured as type 1 type, i.e., pdsch-HARQ-ACK-Codebook=semi-static, the multicast HARQ-ACK codebook is configured as type 2 type, i.e., pdsch-HARQ-ACK-Codebook-Multicast=dynamic, and the unicast SPS PDSCH and multicast SPS PDSCH of the terminal are activated, the terminal may generate a target HARQ-ACK codebook according to the following Example 3 or Example 4, which is as follows:

[0073] Example 3 In a certain uplink time unit (e.g., a slot or a subslot), when a terminal is scheduled to feed back a HARQ-ACK corresponding to a unicast SPS PDSCH, a HARQ-ACK corresponding to a multicast DG PDSCH, and a HARQ-ACK corresponding to a multicast SPS PDSCH, the terminal may determine a target HARQ-ACK codebook in the following manner:

[0074] (a) Since the scenario type corresponding to the unicast PDSCH (i.e., the first physical downlink channel) is the first scenario, the terminal may generate a first HARQ-ACK sub-codebook corresponding to the unicast SPS PDSCH based on a serving cell index, an SPS PDSCH configuration index, a slot in which the SPS PDSCH is located, etc.

[0075] (b) The terminal may generate a second HARQ-ACK sub-codebook corresponding to the multicast DG PDSCH based on the DAI.

[0076] (c) The terminal may generate a second HARQ-ACK sub-codebook corresponding to the multicast SPS PDSCH based on the SPS PDSCH configuration index, the slot in which the SPS PDSCH is located, and so on.

[0077] (d) The terminal cascades the first HARQ-ACK sub-codebook, the second HARQ-ACK sub-codebook, and the third HARQ-ACK sub-codebook in a third order to obtain a target HARQ-ACK codebook.

[0078] Here, the third order may be (first HARQ-ACK sub-codebook, second HARQ-ACK sub-codebook, third HARQ-ACK sub-codebook), (first HARQ-ACK sub-codebook, third HARQ-ACK sub-codebook, second HARQ-ACK sub-codebook), (third HARQ-ACK sub-codebook, second HARQ-ACK sub-codebook, first HARQ-ACK sub-codebook), etc., and is not limited thereto.

[0079] It should be noted that in example 3, the unicast SPS PDSCH belongs to the first physical downlink channel mentioned above, and the multicast SPS PDSCH and the multicast DG PDSCH belong to the second physical downlink channel.

[0080] Example 4 In a certain uplink time unit (e.g., slot or subslot), when a terminal is scheduled to feed back a HARQ-ACK of a unicast SPS PDSCH, a HARQ-ACK corresponding to a multicast DG PDSCH, and a HARQ-ACK corresponding to a multicast SPS PDSCH, the terminal may determine a target HARQ-ACK codebook in the following manner:

[0081] (a) The terminal may generate a fourth HARQ-ACK sub-codebook corresponding to the multicast DG PDSCH based on the DAI.

[0082] (b) The terminal may generate a fifth HARQ-ACK sub-codebook corresponding to the unicast SPS and multicast SPS PDSCH based on the serving cell index, the SPS PDSCH configuration index, the slot in which the SPS PDSCH is located, and so on.

[0083] (c) The terminal cascades the fourth HARQ-ACK sub-codebook and the fifth HARQ-ACK sub-codebook in a fourth order to obtain a final target HARQ-ACK codebook, where the fourth order may be (fourth HARQ-ACK sub-codebook, fifth HARQ-ACK sub-codebook) or (fifth HARQ-ACK sub-codebook, fourth HARQ-ACK sub-codebook), and is not limited thereto.

[0084] The method for determining a HARQ-ACK codebook according to this embodiment is applied to a codebook determination scenario when a unicast HARQ-ACK is configured as a type 1 HARQ-ACK codebook and a multicast HARQ-ACK is configured as a type 2 HARQ-ACK codebook, or when a unicast HARQ-ACK is configured as a type 2 HARQ-ACK codebook and a multicast HARQ-ACK is configured as a type 1 HARQ-ACK codebook, that is, the method for determining a HARQ-ACK codebook according to this embodiment can realize reporting of multicast HARQ-ACK and unicast HARQ-ACK in different codebook types and / or different scenarios.

[0085] In addition, compared to the HARQ-ACK feedback in the related art, the present application generates and feeds back a HARQ-ACK codebook for SPS PDSCH only once, thereby effectively avoiding the problem of repeatedly generating HARQ-ACK for SPS PDSCH that exists in the related art, reducing the size of the codebook, and improving the efficiency of the communication system.

[0086] In the HARQ-ACK codebook determining method 200-300 according to the embodiment of the present application, the execution body may be a HARQ-ACK codebook determining device. In the embodiment of the present application, the HARQ-ACK codebook determining device executes the HARQ-ACK codebook determining method as an example to describe the HARQ-ACK codebook determining device according to the embodiment of the present application.

[0087] As shown in Figure 4, it is a structural schematic diagram of an apparatus for determining a HARQ-ACK codebook according to an exemplary embodiment of the present application, the apparatus 400 includes: a determining module 410 for determining a target HARQ-ACK codebook according to a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel, where the HARQ-ACK codebook type corresponding to the physical downlink channel includes a type 1 HARQ-ACK codebook and a type 2 HARQ-ACK codebook, the scenario type corresponding to the physical downlink channel includes a first scenario and a second scenario, the first scenario is that the terminal reports only HARQ-ACKs corresponding to a designated physical downlink channel received in a candidate PDSCH receiving occasion on one PUCCH, and the second scenario is a scenario other than the first scenario.

[0088] Optionally, the apparatus 400 further includes a receiving module for receiving the physical downlink channel.

[0089] Optionally, the step of the determining module 410 determining a target HARQ-ACK codebook based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel includes: when a HARQ-ACK codebook type corresponding to a first physical downlink channel is the type 1 HARQ-ACK codebook and a HARQ-ACK codebook type corresponding to a second physical downlink channel is the type 2 HARQ-ACK codebook, generating at least two HARQ-ACK sub-codebooks, including a first HARQ-ACK sub-codebook, a second HARQ-ACK sub-codebook, and a third HARQ-ACK sub-codebook, and cascading the generated HARQ-ACK sub-codebooks to obtain the target HARQ-ACK codebook. Here, the first HARQ-ACK sub-codebook corresponds to the first physical downlink channel, the second HARQ-ACK sub-codebook corresponds to a dynamic grant physical downlink shared channel (DG PDSCH) in the second physical downlink channel, the third HARQ-ACK sub-codebook corresponds to a semi-persistent scheduling (SPS PDSCH) in the second physical downlink channel, and the first physical downlink channel is a unicast physical downlink channel and the second physical downlink channel is a multicast physical downlink channel, or the first physical downlink channel is a multicast physical downlink channel and the second physical downlink channel is a unicast physical downlink channel.

[0090] Optionally, the determining module 410 may generate a first HARQ-ACK sub-codebook based on a received HARQ-ACK corresponding to the first physical downlink channel when a scenario type corresponding to the first physical downlink channel is the first scenario, and may determine a candidate PDSCH receiving occasion based on a time domain resource allocation table TDRA corresponding to a first physical downlink channel when a scenario type corresponding to the first physical downlink channel is the second scenario, and generate the first HARQ-ACK sub-codebook based on the candidate PDSCH receiving occasion, where the first HARQ-ACK sub-codebook includes a HARQ-ACK sub-codebook corresponding to a DG PDSCH and / or a HARQ-ACK sub-codebook corresponding to a SPS PDSCH in the first physical downlink channel.

[0091] Optionally, the step of the determining module 410 determining a target HARQ-ACK codebook based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel includes, when a HARQ-ACK codebook type corresponding to a first physical downlink channel is the type 1 HARQ-ACK codebook and a HARQ-ACK codebook type corresponding to a second physical downlink channel is the type 2 HARQ-ACK codebook, performing one of the following steps: when a scenario type corresponding to the first physical downlink channel is the second scenario, generate at least two HARQ-ACK sub-codebooks, including a first HARQ-ACK sub-codebook, a second HARQ-ACK sub-codebook, and a third HARQ-ACK sub-codebook, and cascade the generated HARQ-ACK sub-codebooks to obtain the target HARQ-ACK codebook. Here, the first HARQ-ACK sub-codebook corresponds to the first physical downlink channel, the second HARQ-ACK sub-codebook corresponds to a DG PDSCH in the second physical downlink channel, the third HARQ-ACK sub-codebook corresponds to an SPS PDSCH in the second physical downlink channel, and if a scenario type corresponding to the first physical downlink channel is the first scenario, or if a target HARQ-ACK that needs to be fed back includes only a HARQ-ACK corresponding to an SPS PDSCH in the first physical downlink channel, a fourth HARQ-ACK sub-codebook and / or a fifth HARQ-ACK sub-codebook are generated, and the fourth HARQ-ACK sub-codebook and the fifth HARQ-ACK sub-codebook are cascaded to obtain the HARQ-ACK codebook.Wherein, the fourth HARQ-ACK sub-codebook corresponds to a DG PDSCH in the second physical downlink channel, and the fifth HARQ-ACK sub-codebook corresponds to at least one of an SPS PDSCH in the first physical downlink channel, an SPS PDSCH in the second physical downlink channel, and the designated physical downlink channel in the first physical downlink channel, wherein the first physical downlink channel is a unicast physical downlink channel and the second physical downlink channel is a multicast physical downlink channel, or the first physical downlink channel is a multicast physical downlink channel and the second physical downlink channel is a unicast physical downlink channel.

[0092] Optionally, the designated physical downlink channel is a specific PDCCH, the specific PDCCH carrying a DCI of a first format, and the DCI of the first format indicates the release of an SPS PDSCH, where the specific PDCCH includes any one of a specific PDSCH having a downlink allocation index DAI=1 corresponding to the DCI of the first format, a specific PDSCH, the specific PDSCH being scheduled by a DCI of a second format, and the specific PDSCH having DAI=1 corresponding to the DCI of the second format, and at least one SPS PDSCH.

[0093] Alternatively, when the specific PDCCH and / or the specific PDSCH are unicast physical downlink channels, the DCI of the first format and the DCI of the second format are both DCI1_0, and when the specific PDCCH and / or the specific PDSCH are multicast physical downlink channels, the DCI of the first format and the DCI of the second format are DCI4_1.

[0094] Optionally, the specific PDSCH is located in a primary cell Pcell.

[0095] Optionally, the physical downlink channels include a physical downlink shared channel and a physical downlink control channel.

[0096] The HARQ-ACK codebook determining apparatus 400 in the embodiment of the present application may be an electronic device, for example, an electronic device having an operating system, or may be a component in an electronic device, for example, an integrated circuit or chip. The electronic device may be a terminal, or other devices other than a terminal. Exemplarily, the terminal may include, but is not limited to, the types of terminals 11 listed above, and the other devices may be servers, network attached storage (NAS), etc., and the embodiment of the present application is not specifically limited.

[0097] The HARQ-ACK codebook determination apparatus 400 according to the embodiment of the present application can realize each process realized by the embodiment of the method of Figures 2 to 3, and achieve the same technical effects, and will not be further described here to avoid repetition.

[0098] The embodiment of the present application further provides a terminal, which includes a processor and a communication interface, the communication interface being coupled to the processor, and the processor is used to run a program or instruction to realize the steps of the method in the method embodiments 200 to 300. The embodiment of the terminal corresponds to the embodiment of the method on the terminal side, and each implementation process and realization manner of the embodiment of the method can be applied to the embodiment of the terminal, and the same technical effects can be achieved. Specifically, FIG. 5 is a schematic diagram of a hardware structure for realizing the terminal of the embodiment of the present application.

[0099] The terminal 500 includes at least some of the following components, but is not limited to: a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 507, an interface unit 508, a memory 509, and a processor 510.

[0100] As can be understood by those skilled in the art, the terminal 500 may further include a power source (e.g., a battery) for powering each component, and the power source may be logically connected to the processor 510 by a power management system, so that the power management system can realize functions such as charge / discharge management and power consumption management. The terminal structure shown in FIG. 5 does not constitute a limitation on the terminal, and the terminal may include more or less components than the number of components shown, or a combination of some components, or a different configuration of components, which will not be further described here.

[0101] It should be understood that in the embodiment of the present application, the input unit 504 may include a graphics processor (Graphics Processing Unit, GPU) 5041 and a microphone 5042, and the GPU 5041 processes image data of still or video images obtained by an image capture device (e.g., a camera) in a video capture mode or an image capture mode. The display unit 506 may include a display panel 5061, and the display panel 5061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 507 includes at least one of a touch panel 5071 and other input devices 5072. The touch panel 5071 is also called a touch screen. The touch panel 5071 may include two parts: a touch detection device and a touch controller. The other input devices 5072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control buttons, switch buttons, etc.), a trackball, a mouse, and an operation lever, which will not be described further herein.

[0102] In the embodiment of the present application, the radio frequency unit 501 can receive downlink data from the network side device, and then transmit the data to the processor 510 for processing, and can transmit uplink data to the network side device. In general, the radio frequency unit 501 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0103] The memory 509 may be used to store software programs or instructions and various data. The memory 509 may include a first storage area that mainly stores programs or instructions and a second storage area that stores data. Here, the first storage area can store an operating system, an application program or instructions required for at least one function (e.g., a sound playback function, an image playback function, etc.), and the like. It should be noted that the memory 509 may include a volatile memory or a non-volatile memory, or the memory 509 may include both a volatile and a non-volatile memory. Here, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be Random Access Memory (RAM), Static Random Access Memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM, DRAM), Synchronous Dynamic Random Access Memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (Double Data Rate SDRAM, DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced SDRAM, ESDRAM), Synch link Dynamic Random Access Memory (Synch link DRAM, SLDRAM), and Direct Rambus Random Access Memory (Direct Rambus RAM, DRRAM). Memory 509 in embodiments of the present application may include, but is not limited to, these and any other suitable types of memory.

[0104] The processor 510 may include one or more processing units. Optionally, the processor 510 integrates an application processor and a modem processor, where the application processor mainly processes operations related to the operating system, user interface, application programs, etc., and the modem processor mainly processes wireless communication signals, such as a baseband processor. As can be understood, the modem processor does not have to be integrated into the processor 510.

[0105] Wherein, the processor 510 is used for determining a target HARQ-ACK codebook based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel, where the HARQ-ACK codebook type corresponding to the physical downlink channel includes a type 1 HARQ-ACK codebook and a type 2 HARQ-ACK codebook, and the scenario type corresponding to the physical downlink channel includes a first scenario and a second scenario, in which the first scenario is that the terminal reports only HARQ-ACKs corresponding to a designated physical downlink channel that are received in a candidate PDSCH reception occasion on one PUCCH, and the second scenario is a scenario other than the first scenario.

[0106] Optionally, the step of processor 510 determining a target HARQ-ACK codebook based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel includes, when a HARQ-ACK codebook type corresponding to a first physical downlink channel is the type 1 HARQ-ACK codebook and a HARQ-ACK codebook type corresponding to a second physical downlink channel is the type 2 HARQ-ACK codebook, generating at least two HARQ-ACK sub-codebooks from a first HARQ-ACK sub-codebook, a second HARQ-ACK sub-codebook, and a third HARQ-ACK sub-codebook, and cascading the generated HARQ-ACK sub-codebooks to obtain the target HARQ-ACK codebook. Here, the first HARQ-ACK sub-codebook corresponds to the first physical downlink channel, the second HARQ-ACK sub-codebook corresponds to a dynamic grant physical downlink shared channel (DG PDSCH) in the second physical downlink channel, the third HARQ-ACK sub-codebook corresponds to a semi-persistent scheduling (SPS PDSCH) in the second physical downlink channel, and the first physical downlink channel is a unicast physical downlink channel and the second physical downlink channel is a multicast physical downlink channel, or the first physical downlink channel is a multicast physical downlink channel and the second physical downlink channel is a unicast physical downlink channel.

[0107] Optionally, the processor 510 may generate a first HARQ-ACK sub-codebook based on a received HARQ-ACK corresponding to the first physical downlink channel when a scenario type corresponding to the first physical downlink channel is the first scenario, and may determine a candidate PDSCH receiving occasion based on a time domain resource allocation table TDRA corresponding to a first physical downlink channel when a scenario type corresponding to the first physical downlink channel is the second scenario, and generate the first HARQ-ACK sub-codebook based on the candidate PDSCH receiving occasion, where the first HARQ-ACK sub-codebook includes a HARQ-ACK sub-codebook corresponding to a DG PDSCH and / or a HARQ-ACK sub-codebook corresponding to a SPS PDSCH in the first physical downlink channel.

[0108] Optionally, the step of processor 510 determining a target HARQ-ACK codebook based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel includes, when a HARQ-ACK codebook type corresponding to a first physical downlink channel is the type 1 HARQ-ACK codebook and a HARQ-ACK codebook type corresponding to a second physical downlink channel is the type 2 HARQ-ACK codebook, performing any one of the following steps: when a scenario type corresponding to the first physical downlink channel is the second scenario, generate at least two HARQ-ACK sub-codebooks, including a first HARQ-ACK sub-codebook, a second HARQ-ACK sub-codebook, and a third HARQ-ACK sub-codebook, and cascade-connect the generated HARQ-ACK sub-codebooks to obtain the target HARQ-ACK codebook. Here, the first HARQ-ACK sub-codebook corresponds to the first physical downlink channel, the second HARQ-ACK sub-codebook corresponds to a DG PDSCH in the second physical downlink channel, the third HARQ-ACK sub-codebook corresponds to an SPS PDSCH in the second physical downlink channel, and if a scenario type corresponding to the first physical downlink channel is the first scenario, or if a target HARQ-ACK that needs to be fed back includes only a HARQ-ACK corresponding to an SPS PDSCH in the first physical downlink channel, a fourth HARQ-ACK sub-codebook and / or a fifth HARQ-ACK sub-codebook are generated, and the fourth HARQ-ACK sub-codebook and the fifth HARQ-ACK sub-codebook are cascaded to obtain the HARQ-ACK codebook.Wherein, the fourth HARQ-ACK sub-codebook corresponds to a DG PDSCH in the second physical downlink channel, and the fifth HARQ-ACK sub-codebook corresponds to at least one of an SPS PDSCH in the first physical downlink channel, an SPS PDSCH in the second physical downlink channel, and the designated physical downlink channel in the first physical downlink channel, wherein the first physical downlink channel is a unicast physical downlink channel and the second physical downlink channel is a multicast physical downlink channel, or the first physical downlink channel is a multicast physical downlink channel and the second physical downlink channel is a unicast physical downlink channel.

[0109] Optionally, the designated physical downlink channel is a specific PDCCH, the specific PDCCH carrying a DCI of a first format, and the DCI of the first format indicates the release of an SPS PDSCH, where the specific PDCCH includes any one of a specific PDSCH having a downlink allocation index DAI=1 corresponding to the DCI of the first format, a specific PDSCH, the specific PDSCH being scheduled by a DCI of a second format, and the specific PDSCH having DAI=1 corresponding to the DCI of the second format, and at least one SPS PDSCH.

[0110] Alternatively, when the specific PDCCH and / or the specific PDSCH are unicast physical downlink channels, the DCI of the first format and the DCI of the second format are both DCI1_0, and when the specific PDCCH and / or the specific PDSCH are multicast physical downlink channels, the DCI of the first format and the DCI of the second format are DCI4_1.

[0111] Optionally, the specific PDSCH is located in a primary cell Pcell.

[0112] Optionally, the physical downlink channels include a physical downlink shared channel and a physical downlink control channel.

[0113] The implementation process of each implementation method mentioned in this embodiment can be referred to the implementation process in embodiments 200 to 300 of the above-mentioned method, and will not be described further here in order to achieve the same technical effects and avoid repetition of description.

[0114] An embodiment of the present application further provides a readable storage medium, which stores a program or instruction, and when the program or instruction is executed by a processor, each process of the embodiment of the method for determining a HARQ-ACK codebook can be realized and the same technical effect can be achieved, and in order to avoid repetition, no further description will be given here.

[0115] Wherein, the processor is the processor in the terminal according to the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read only memory ROM, a random access memory RAM, a magnetic disk, or an optical disk.

[0116] An embodiment of the present application further provides a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run a program or instruction of a network side equipment to realize each process of the embodiment of the above-mentioned HARQ-ACK codebook determination method, and the same technical effect can be achieved, and in order to avoid repetition of description, no further description will be given here.

[0117] It should be understood that the chips referred to in the embodiments of the present application may be referred to as system level chips, system chips, chip systems, or systems on chips.

[0118] An embodiment of the present application further provides a computer program product, which includes a processor, a memory, and a program or instruction stored in the memory and capable of running on the processor, and when the program or instruction is executed by the processor, each process of the embodiment of the method for determining a HARQ-ACK codebook can be realized and the same technical effect can be achieved, and in order to avoid repetition of description, no further description will be given here.

[0119] An embodiment of the present application further provides a communication system, including a terminal and a network side equipment, wherein the terminal may be used to perform each process of the embodiment of the HARQ-ACK codebook determination method described above, and can achieve the same technical effects, and will not be further described here to avoid repetition.

[0120] It should be explained that in this specification, the terms "comprise", "include", "includes" or any other variants thereof are intended to cover the non-exclusive "comprise", whereby a process, method, article or apparatus that includes a set of elements includes not only those elements, but also other elements not expressly listed or inherent to such process, method, article or apparatus. Absent any further limitations, an element limited by the phrase "comprises one or more" does not preclude the presence of other identical elements in the process, method, article or apparatus that includes the element. It should be noted that the scope of the methods and apparatus in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may include performing functions in an essentially simultaneous manner or in the reverse order based on the functions involved. For example, the described methods can be performed in a different order than described, and various steps can be added, omitted or combined. Also, features described with reference to some examples can be combined in other examples.

[0121] From the above description of the embodiments, it is clear to those skilled in the art that the methods of the above embodiments can be realized in the form of software and a necessary general-purpose hardware platform. Of course, they can also be realized in hardware, but in many cases the former is a more preferred embodiment. In light of this understanding, the technical proposal of the present application may be substantially or the part that contributes to the prior art may be embodied in the form of a computer software product, which is stored in a storage medium (e.g., ROM / RAM, magnetic disk, optical disk) and includes some instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0122] The above describes the embodiments of the present application in conjunction with the drawings, but the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not limiting. Those skilled in the art can take the suggestions of this application and make many forms without departing from the spirit and scope of the claims of this application, all of which belong to the protection scope of this application.

Claims

1. A method for determining a hybrid automatic repeat request-acknowledgement HARQ-ACK codebook, comprising: The terminal determines a target HARQ-ACK codebook based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel; The HARQ-ACK codebook type corresponding to the physical downlink channel includes a type 1 HARQ-ACK codebook and a type 2 HARQ-ACK codebook; A method in which a scenario type corresponding to the physical downlink channel includes a first scenario and a second scenario, the first scenario being for the terminal to report only a HARQ-ACK corresponding to a specified physical downlink channel received in a candidate PDSCH reception occasion on one PUCCH, and the second scenario being a scenario other than the first scenario.

2. The step of determining a target HARQ-ACK codebook by the terminal based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel includes: When a HARQ-ACK codebook type corresponding to a first physical downlink channel is the type 1 HARQ-ACK codebook and a HARQ-ACK codebook type corresponding to a second physical downlink channel is the type 2 HARQ-ACK codebook, the terminal generates at least two HARQ-ACK sub-codebooks from a first HARQ-ACK sub-codebook, a second HARQ-ACK sub-codebook, and a third HARQ-ACK sub-codebook, and cascades the generated HARQ-ACK sub-codebooks to obtain the target HARQ-ACK codebook; the first HARQ-ACK sub-codebook corresponds to the first physical downlink channel, the second HARQ-ACK sub-codebook corresponds to a dynamic grant physical downlink shared channel (DG PDSCH) in the second physical downlink channel, and the third HARQ-ACK sub-codebook corresponds to a semi-persistent scheduling (SPS PDSCH) in the second physical downlink channel; 2. The method of claim 1, wherein the first physical downlink channel is a unicast physical downlink channel and the second physical downlink channel is a multicast physical downlink channel, or the first physical downlink channel is a multicast physical downlink channel and the second physical downlink channel is a unicast physical downlink channel.

3. The step of generating a first HARQ-ACK sub-codebook by the terminal includes: When a scenario type corresponding to the first physical downlink channel is the first scenario, the terminal generates the first HARQ-ACK sub-codebook based on a HARQ-ACK corresponding to the first physical downlink channel received by the terminal; and when a scenario type corresponding to the first physical downlink channel is the second scenario, the terminal determines a candidate PDSCH receiving occasion based on a time domain resource allocation table TDRA corresponding to the first physical downlink channel, and generates the first HARQ-ACK sub-codebook based on the candidate PDSCH receiving occasion, wherein the first HARQ-ACK sub-codebook includes a HARQ-ACK sub-codebook corresponding to a DG PDSCH in the first physical downlink channel and / or a HARQ-ACK sub-codebook corresponding to an SPS PDSCH in the first physical downlink channel.

4. The step of determining a target HARQ-ACK codebook by the terminal based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel includes: When a HARQ-ACK codebook type corresponding to a first physical downlink channel is the type 1 HARQ-ACK codebook and a HARQ-ACK codebook type corresponding to a second physical downlink channel is the type 2 HARQ-ACK codebook, the terminal performs one of the following steps: When a scenario type corresponding to the first physical downlink channel is the second scenario, generate at least two HARQ-ACK sub-codebooks, including a first HARQ-ACK sub-codebook, a second HARQ-ACK sub-codebook, and a third HARQ-ACK sub-codebook, and cascade the generated HARQ-ACK sub-codebooks to obtain the target HARQ-ACK codebook, wherein the first HARQ-ACK sub-codebook corresponds to the first physical downlink channel, the second HARQ-ACK sub-codebook corresponds to a DG PDSCH in the second physical downlink channel, and the third HARQ-ACK sub-codebook corresponds to an SPS PDSCH in the second physical downlink channel; When a scenario type corresponding to the first physical downlink channel is the first scenario, or when the target HARQ-ACK that needs to be fed back includes only a HARQ-ACK corresponding to an SPS PDSCH in the first physical downlink channel, generate a fourth HARQ-ACK sub-codebook and / or a fifth HARQ-ACK sub-codebook, and cascade-connect the fourth HARQ-ACK sub-codebook and the fifth HARQ-ACK sub-codebook to obtain the HARQ-ACK codebook, wherein the fourth HARQ-ACK sub-codebook corresponds to a DG PDSCH in the second physical downlink channel, and the fifth HARQ-ACK sub-codebook corresponds to at least one of an SPS PDSCH in the first physical downlink channel, an SPS PDSCH in the second physical downlink channel, and the designated physical downlink channel in the first physical downlink channel; 2. The method of claim 1, wherein the first physical downlink channel is a unicast physical downlink channel and the second physical downlink channel is a multicast physical downlink channel, or the first physical downlink channel is a multicast physical downlink channel and the second physical downlink channel is a unicast physical downlink channel.

5. The designated physical downlink channel is A specific PDCCH, the specific PDCCH carrying downlink control information (DCI) of a first format, and the DCI of the first format instructs the release of an SPS PDSCH, and a downlink allocation index (DAI) corresponding to the DCI of the first format is 1; A specific PDSCH, the specific PDSCH being scheduled by a DCI of a second format, and a DAI corresponding to the DCI of the second format being 1; The method according to claim 1 , further comprising at least one of:

6. When the specific PDCCH and / or the specific PDSCH is a unicast physical downlink channel, the first format DCI and the second format DCI are both DCI 1_0; The method according to claim 5 , wherein, when the specific PDCCH and / or the specific PDSCH is a multicast physical downlink channel, the first format DCI and the second format DCI are DCI 4_1.

7. The method of claim 5 , wherein the specific PDSCH is located in a primary cell (Pcell).

8. The method according to claim 1 , wherein the physical downlink channels include a physical downlink shared channel and a physical downlink control channel.

9. An apparatus for determining a hybrid automatic repeat request-acknowledgement HARQ-ACK codebook, comprising: A determining module for determining a target HARQ-ACK codebook based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel; The HARQ-ACK codebook type corresponding to the physical downlink channel includes a type 1 HARQ-ACK codebook and a type 2 HARQ-ACK codebook; A scenario type corresponding to the physical downlink channel includes a first scenario and a second scenario, the first scenario being for a terminal to report only a HARQ-ACK corresponding to a specified physical downlink channel received in a candidate PDSCH reception occasion on one PUCCH, and the second scenario being a scenario other than the first scenario.

10. The determining module determines a target HARQ-ACK codebook based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel, when a HARQ-ACK codebook type corresponding to a first physical downlink channel is the type 1 HARQ-ACK codebook and a HARQ-ACK codebook type corresponding to a second physical downlink channel is the type 2 HARQ-ACK codebook, generating at least two HARQ-ACK sub-codebooks from a first HARQ-ACK sub-codebook, a second HARQ-ACK sub-codebook and a third HARQ-ACK sub-codebook, and cascading the generated HARQ-ACK sub-codebooks to obtain the target HARQ-ACK codebook; the first HARQ-ACK sub-codebook corresponds to the first physical downlink channel, the second HARQ-ACK sub-codebook corresponds to a dynamic grant physical downlink shared channel (DG PDSCH) in the second physical downlink channel, and the third HARQ-ACK sub-codebook corresponds to a semi-persistent scheduling (SPS PDSCH) in the second physical downlink channel; 10. The apparatus of claim 9, wherein the first physical downlink channel is a unicast physical downlink channel and the second physical downlink channel is a multicast physical downlink channel, or the first physical downlink channel is a multicast physical downlink channel and the second physical downlink channel is a unicast physical downlink channel.

11. The step of the determination module generating a first HARQ-ACK sub-codebook includes: generating the first HARQ-ACK sub-codebook based on a received HARQ-ACK corresponding to the first physical downlink channel when a scenario type corresponding to the first physical downlink channel is the first scenario; and generating the first HARQ-ACK sub-codebook based on the candidate PDSCH reception occasions when a scenario type corresponding to the first physical downlink channel is the second scenario, wherein the first HARQ-ACK sub-codebook includes a HARQ-ACK sub-codebook corresponding to a DG PDSCH in the first physical downlink channel and / or a HARQ-ACK sub-codebook corresponding to an SPS PDSCH in the first physical downlink channel.

12. The determining module determines a target HARQ-ACK codebook based on a HARQ-ACK codebook type and / or a scenario type corresponding to a physical downlink channel, When a HARQ-ACK codebook type corresponding to a first physical downlink channel is the type 1 HARQ-ACK codebook and a HARQ-ACK codebook type corresponding to a second physical downlink channel is the type 2 HARQ-ACK codebook, performing one of the following steps: When a scenario type corresponding to the first physical downlink channel is the second scenario, generate at least two HARQ-ACK sub-codebooks, including a first HARQ-ACK sub-codebook, a second HARQ-ACK sub-codebook, and a third HARQ-ACK sub-codebook, and cascade the generated HARQ-ACK sub-codebooks to obtain the target HARQ-ACK codebook, wherein the first HARQ-ACK sub-codebook corresponds to the first physical downlink channel, the second HARQ-ACK sub-codebook corresponds to a DG PDSCH in the second physical downlink channel, and the third HARQ-ACK sub-codebook corresponds to an SPS PDSCH in the second physical downlink channel; When a scenario type corresponding to the first physical downlink channel is the first scenario, or when the target HARQ-ACK that needs to be fed back includes only a HARQ-ACK corresponding to an SPS PDSCH in the first physical downlink channel, generate a fourth HARQ-ACK sub-codebook and / or a fifth HARQ-ACK sub-codebook, and cascade-connect the fourth HARQ-ACK sub-codebook and the fifth HARQ-ACK sub-codebook to obtain the HARQ-ACK codebook, wherein the fourth HARQ-ACK sub-codebook corresponds to a DG PDSCH in the second physical downlink channel, and the fifth HARQ-ACK sub-codebook corresponds to at least one of an SPS PDSCH in the first physical downlink channel, an SPS PDSCH in the second physical downlink channel, and the designated physical downlink channel in the first physical downlink channel; 10. The apparatus of claim 9, wherein the first physical downlink channel is a unicast physical downlink channel and the second physical downlink channel is a multicast physical downlink channel, or the first physical downlink channel is a multicast physical downlink channel and the second physical downlink channel is a unicast physical downlink channel.

13. The designated physical downlink channel is A specific PDCCH, the specific PDCCH carrying a DCI of a first format, and the DCI of the first format indicates the release of an SPS PDSCH, and a downlink allocation index DAI corresponding to the DCI of the first format is 1; A specific PDSCH, the specific PDSCH being scheduled by a DCI of a second format, and a DAI corresponding to the DCI of the second format being 1; The apparatus of claim 9 , further comprising at least one SPS PDSCH.

14. When the specific PDCCH and / or the specific PDSCH is a unicast physical downlink channel, the first format DCI and the second format DCI are both DCI1_0; The apparatus according to claim 13 , wherein when the specific PDCCH and / or the specific PDSCH is a multicast physical downlink channel, the first format DCI and the second format DCI are DCI 4_1.

15. The apparatus of claim 13 , wherein the specific PDSCH is located in a primary cell (Pcell).

16. The apparatus of claim 9 , wherein the physical downlink channels include a physical downlink shared channel and a physical downlink control channel.

17. A terminal including a processor and a memory, the memory storing a program or instructions operable on the processor, the terminal implementing steps of a method for determining a HARQ-ACK codebook according to any one of claims 1 to 8, when the program or instructions are executed by the processor.

18. A readable storage medium having a program or instructions stored therein, the program or instructions implementing the steps of the method for determining a HARQ-ACK codebook according to any one of claims 1 to 8 when executed by a processor.

19. A chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor running a program or instructions, and used to realize the method for determining a HARQ-ACK codebook described in any one of claims 1 to 8.

20. A computer program product / program product, (the computer program product / program product is stored in a storage medium), the computer program product / program product being executed by at least one processor to realize the method for determining a HARQ-ACK codebook according to any one of claims 1 to 8.

Images