Method, apparatus and terminal for determining hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook

Abstract

The application discloses a kind of hybrid automatic repeat request-confirmation HARQ-ACK codebook determination method, device and terminal, belong to communication technical field, the HARQ-ACK codebook determination method of embodiment of the application includes: terminal determines target HARQ-ACK codebook according to the HARQ-ACK codebook type and / or scene type corresponding to physical downlink channel;Wherein, the HARQ-ACK codebook type corresponding to physical downlink channel includes type type 1HARQ-ACK codebook and type 2HARQ-ACK codebook;The scene type corresponding to physical downlink channel includes first scene and second scene, the first scene is that the terminal is only reported in a PUCCH HARQ-ACK corresponding to specified physical downlink channel received in candidate PDSCH reception occasion, the second scene is the scene except the first scene.

Description

Technical Field

[0001] This application belongs to the field of communication technology, and specifically relates to a method, apparatus and terminal for determining a hybrid automatic repeat request-acknowledgment (HARQ-ACK) codebook. Background Technology

[0002] Currently, in addition to the unicast Physical Downlink Control Channel (PDCCH) and unicast Physical Downlink Shared Channel (PDSCH) supporting Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback, the New Radio (NR) system also supports HARQ-ACK feedback for Multicast PDSCH and Multicast PDCCH.

[0003] However, how the terminal determines the HARQ-ACK codebook for multicast HARQ-ACK and / or unicast HARQ-ACK remains a pressing technical problem that needs to be solved. Summary of the Invention

[0004] This application provides a method, apparatus, and terminal for determining the HARQ-ACK codebook for hybrid automatic repeat request-acknowledgment (HARQ-ACK), which can determine the HARQ-ACK codebook for multicast HARQ-ACK and unicast HARQ-ACK.

[0005] In a first aspect, a method for determining a hybrid automatic repeat request-acknowledgment (HARQ-ACK) codebook is provided, comprising: a terminal determining a target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to a physical downlink channel; wherein, the HARQ-ACK codebook type corresponding to the physical downlink channel includes type 1 HARQ-ACK codebook and type 2 HARQ-ACK codebook; the scenario type corresponding to the physical downlink channel includes a first scenario and a second scenario, wherein the first scenario is that the terminal only reports the HARQ-ACK corresponding to a specified physical downlink channel received during a candidate PDSCH reception time on a PUCCH, and the second scenario is a scenario other than the first scenario.

[0006] Secondly, a device for determining a hybrid automatic repeat request-acknowledgment (HARQ-ACK) codebook is provided, comprising: a determining module, configured to determine a target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel; wherein the HARQ-ACK codebook type corresponding to the physical downlink channel includes type 1 HARQ-ACK codebook and type 2 HARQ-ACK codebook; the scenario type corresponding to the physical downlink channel includes a first scenario and a second scenario, wherein the first scenario is that the terminal only reports the HARQ-ACK corresponding to the specified physical downlink channel received during the candidate PDSCH reception time on a PUCCH, and the second scenario is a scenario other than the first scenario.

[0007] Thirdly, a terminal is provided, comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method described in the first aspect.

[0008] Fourthly, a terminal is provided, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method described in the first aspect.

[0009] Fifthly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method described in the first aspect.

[0010] In a sixth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect.

[0011] In a seventh aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being used to run programs or instructions to implement the steps of the method described in the first aspect.

[0012] Eighthly, a computer program product is provided, which is stored in a storage medium and is executed by at least one processor to perform the steps of the method described in the first aspect.

[0013] In the embodiments of this application, the terminal determines the target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel. This provides an effective HARQ-ACK codebook determination scheme for multicast HARQ-ACK and / or unicast HARQ-ACK, ensuring the performance of the communication system. Attached Figure Description

[0014] Figure 1 This is a schematic diagram of the structure of a wireless communication system provided in an exemplary embodiment of this application.

[0015] Figure 2 This is a flowchart illustrating a method for determining the HARQ-ACK codebook provided in an exemplary embodiment of this application.

[0016] Figure 3 This is a flowchart illustrating a method for determining the HARQ-ACK codebook provided in another exemplary embodiment of this application.

[0017] Figure 4 This is a schematic diagram of the structure of a device for determining the HARQ-ACK codebook provided in an exemplary embodiment of this application.

[0018] Figure 5 This is a schematic diagram of the structure of a terminal provided in an exemplary embodiment of this application. Detailed Implementation

[0019] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0020] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0021] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in 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 this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes NR systems for illustrative purposes, and NR terminology is used in most of the following description; however, these technologies can also be applied to applications other than NR systems, such as 6th generation (6G) wireless communication systems. th Generation 6G communication system.

[0022] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. Terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment. Network-side equipment 12 may include access network equipment or core network equipment. Access network equipment 12 may also be referred to as radio access network equipment, radio access network (RAN), radio access network function, or radio access network unit. Access network equipment 12 may include base stations, WLAN access points, or WiFi nodes, etc. Base stations may be referred to as Node B, evolved Node B (eNB), access point, base transceiver station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home B node, home evolved B node, Transmitting Receiving Point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this application embodiment, only a base station in an NR system is used as an example for description, and the specific type of base station is not limited.

[0023] The technical solutions provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0024] like Figure 2 The diagram shown illustrates a flowchart of a method 200 for determining a HARQ-ACK codebook provided in an exemplary embodiment of this application. This method 200 can be executed by, but is not limited to, a terminal, specifically by hardware and / or software installed in the terminal. In this embodiment, the method 200 may include at least the following steps.

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

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

[0027] The scenario types corresponding to the physical downlink channels include a first scenario (also known as a fallback scenario) and a second scenario (also known as a non-fallback scenario). The first scenario involves the terminal reporting only the HARQ-ACK corresponding to the designated physical downlink channel received during the candidate PDSCH reception on a Physical Uplink Control Channel (PUCCH) (e.g., the terminal is only scheduled to report the HARQ-ACK corresponding to the designated physical downlink channel on a single PUCCH). The second scenario is any scenario other than the first scenario (e.g., the terminal is scheduled to report the HARQ-ACK corresponding to a physical downlink channel other than the designated physical downlink channel on a single PUCCH). The first scenario and / or the second scenario can be implemented by protocol agreement, higher-layer configuration, or network-side configuration, and are not limited here.

[0028] In this case, the physical downlink channel mentioned in this embodiment can be PDSCH and / or PDCCH. If the terminal needs to feed back the HARQ-ACK corresponding to the unicast physical downlink channel (such as unicast PDSCH, unicast PDCCH) and the HARQ-ACK corresponding to the multicast physical downlink channel (such as multicast PDCCH, multicast PDSCH) on the same time unit (such as slot, sub-slot, symbol, sub-symbol, etc.), and the HARQ-ACK corresponding to the unicast physical downlink channel and the HARQ-ACK corresponding to the multicast physical downlink channel have the same priority, then the physical downlink channel can simultaneously include unicast physical downlink channel and multicast physical downlink channel, etc.

[0029] Furthermore, in this embodiment, the aforementioned physical downlink channel can also be a Dynamic Grant (DG) physical downlink channel or a Semi-Persistent Scheduling (SPS) physical downlink channel, etc., and there are no restrictions here.

[0030] It is worth noting that if the physical downlink channel is a PDCCH, then the terminal only needs to send back the HARQ-ACK corresponding to the specified PDCCH. The specified PDCCH can be a PDCCH indicating the release of the SPS PDSCH, a PDCCH indicating the secondary cell dormancy and without scheduled PDSCH, a PDCCH indicating the update of the Transmission Configuration Indicator (TCI) state, etc.

[0031] In this embodiment, the terminal determines the target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel. This provides an effective HARQ-ACK codebook determination scheme for multicast HARQ-ACK and / or unicast HARQ-ACK, enabling the reporting of HARQ-ACK information and ensuring the performance of the communication system.

[0032] like Figure 3 The diagram shown illustrates a flowchart of a method 300 for determining a HARQ-ACK codebook provided in an exemplary embodiment of this application. This method 300 can be executed by, but is not limited to, a terminal, specifically by hardware and / or software installed in the terminal. In this embodiment, the method 300 may include at least the following steps.

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

[0034] The HARQ-ACK codebook type corresponding to the physical downlink channel includes type 1 HARQ-ACK codebook and 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 the HARQ-ACK corresponding to the specified physical downlink channel received by the terminal during the reporting of the candidate PDSCH reception time on a PUCCH. The second scenario is any scenario other than the first scenario.

[0035] It is understood that, in addition to referring to the relevant description in method embodiment 200, in one possible implementation of S310, the designated physical downlink channel may include any one of the following (11)-(13).

[0036] (11) A specific PDCCH, wherein the specific PDCCH carries downlink control information (DCI) in a first format and the first format DCI indicates the release of the SPS PDSCH, wherein the downlink assignment index (DAI) corresponding to the first format DCI is 1.

[0037] Optionally, when the specific PDCCH is a unicast physical downlink channel (such as a PDCCH scrambled with a Configured Scheduling Radio Network Temporary Identifier (CS-RNTI)), the first format is DCI 1_0; or, when the specific PDCCH is a multicast physical downlink channel (such as a PDCCH scrambled with a Group-Configured Scheduling-RNTI (G-CS-RNTI)), the second format's DCI is DCI 4_1.

[0038] (12) A specific PDSCH, which is scheduled by a second format DCI and the DAI corresponding to the second format DCI is 1.

[0039] Optionally, when the specific PDSCH is a unicast physical downlink channel (e.g., scrambled with Cell RNTI (C-RNTI) or Cell-Radio Network Temporary Identifier (C-RNTI)), the second format DCI is DCI 1_0; or, when the specific PDSCH is a multicast physical downlink channel (e.g., scrambled with Group RNTI (G-RNTI)), the second format DCI is DCI 4_1. The DAI is a counter DAI (C-DAI).

[0040] Furthermore, in one implementation, the specific PDSCH can be located in the primary cell (PCell). For example, if the specific PDSCH is a unicast PDSCH, the unicast PDSCH is located in the PCell. Correspondingly, if the specific PDSCH is a multicast PDSCH, the multicast PDSCH can be located in the PCell, or it can be located in other cells besides the PCell, such as cells configured for multicast reception.

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

[0042] Of course, in another implementation, there are multiple ways for the terminal to determine the target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel. The following is an explanation of two different implementation methods.

[0043] Implementation Method 1

[0044] When the HARQ-ACK codebook type corresponding to the first physical downlink channel is the type 1 HARQ-ACK codebook (also referred to as type 1 or semi-static codebook type) and the HARQ-ACK codebook type corresponding to the second physical downlink channel is the type 2 HARQ-ACK codebook (also referred to as type 2 or dynamic codebook type), the terminal generates at least two of the following HARQ-ACK sub-codebooks: a first HARQ-ACK sub-codebook, a second HARQ-ACK sub-codebook, and a third HARQ-ACK sub-codebook, and concatenates the generated HARQ-ACK sub-codebooks to obtain the target HARQ-ACK codebook.

[0045] The first HARQ-ACK subcodebook corresponds to the first physical downlink channel. As one possible implementation, the terminal can generate the first HARQ-ACK subcodebook differently depending on the scenario type corresponding to the first physical downlink channel. For example, if the scenario type corresponding to the first physical downlink channel is the first scenario, the terminal generates the first HARQ-ACK subcodebook based on the received HARQ-ACK corresponding to the first physical downlink channel.

[0046] For example, when the scenario type corresponding to the first physical downlink channel is the second scenario, the terminal determines the candidate PDSCH reception occasion based on the Time Domain Resource Assignment (TDRA) table corresponding to the first physical downlink channel, and generates the first HARQ-ACK subcodebook based on the candidate PDSCH reception occasion. It can be understood that when determining the candidate PDSCH reception occasion based on the TDRA, the terminal can also combine the timing K1 of the PDSCH to HARQ-ACK feedback, semi-static uplink / downlink configuration, etc., to determine the candidate PDSCH reception occasion. Here, K1 represents the number of time units from the time unit where the terminal receives the PDSCH to the time unit where the HARQ feedback occurs; that is, when the terminal receives the PDSCH in time unit n, it feeds back its corresponding HARQ information in time unit n+K1.

[0047] In addition, the first HARQ-ACK subcodebook may include the HARQ-ACK subcodebook corresponding to the DG PDSCH and / or the HARQ-ACK subcodebook corresponding to the SPS PDSCH in the first physical downlink channel. That is, for the type 1 HARQ-ACK codebook, the HARQ-ACK of the DG PDSCH and the SPS PDSCH can be determined according to the candidate PDSCH reception timing.

[0048] The second HARQ-ACK subcodebook corresponds to the DG PDSCH in the second physical downlink channel. In one implementation, the terminal can generate the second HARQ-ACK subcodebook according to a type 2 codebook generation method (e.g., according to DAI).

[0049] The third HARQ-ACK subcodebook corresponds to the SPS PDSCH in the second physical downlink channel. In one implementation, the terminal can generate the third HARQ-ACK subcodebook according to an SPS PDSCH HARQ-ACK codebook generation method. For example, the terminal can generate the third HARQ-ACK subcodebook based on the serving cell index, the SPS PDSCH configuration index, and the time slot where the SPS PDSCH is located. It is worth noting that the third HARQ-ACK subcodebook only contains the HARQ-ACK corresponding to the SPS PDSCH in the second physical downlink channel.

[0050] Of course, for implementation method 1, the first physical downlink channel is a unicast physical downlink channel (such as unicast PDSCH, unicast PDCCH), and the second physical downlink channel is a multicast physical downlink channel (such as 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.

[0051] Furthermore, in one implementation, when the terminal concatenates the generated HARQ-ACK subcodebooks, the concatenation order between the HARQ-ACK subcodebooks can be determined by protocol agreement, higher-layer configuration, or the terminal itself. This ensures that the terminal and network-side devices have a consistent understanding of the order of the HARQ-ACK subcodebooks, thereby enabling the network-side devices to clearly understand the position of the HARQ-ACK corresponding to SPS PDSCH in the target HARQ-ACK codebook when receiving the target HARQ-ACK codebook sent by the terminal, thus achieving determined resource scheduling.

[0052] It should be noted that if the concatenation order between the HARQ-ACK subcodebooks is determined autonomously by the terminal, then the terminal can report the concatenation order to the network-side device.

[0053] Based on the description of the aforementioned implementation method 1, assuming that 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 terminal is activated with unicast SPS PDSCH and multicast SPSPDSCH, then the terminal can generate the target HARQ-ACK codebook according to Example 1 or Example 2 as follows, with the following content.

[0054] Example 1

[0055] If, in a certain uplink time unit (such as a time slot or sub-time slot), the terminal is scheduled to send back HARQ-ACK for unicast DG PDSCH, HARQ-ACK for unicast SPS PDSCH, HARQ-ACK for multicast DG PDSCH, and HARQ-ACK for multicast SPSPDSCH, then the terminal can determine the HARQ-ACK codebook in the following manner.

[0056] (a) Since the scenario type corresponding to the unicast PDSCH (i.e. the first physical downlink channel) is the second scenario, the terminal can determine the candidate PDSCH reception timing corresponding to the unicast based on the TDRA table (also known as the TDRA table corresponding to the unicast DCI), K1 (also known as the K1 corresponding to the unicast DCI) and the uplink / downlink configuration, and then generate the first HARQ-ACK subcodebook corresponding to the unicast PDSCH based on the candidate PDSCH reception timing. The first HARQ-ACK subcodebook includes the HARQ-ACK corresponding to the unicast DG PDSCH and the unicast SPS PDSCH.

[0057] (b) The terminal can generate the second HARQ-ACK subcodebook corresponding to the multicast DG PDSCH based on the DAI.

[0058] (c) The terminal can generate the third HARQ-ACK subcodebook corresponding to the multicast SPS PDSCH based on the SPS PDSCH configuration index, the time slot where the SPS PDSCH is located, etc.

[0059] (d) The terminal concatenates the first HARQ-ACK subcodebook, the second HARQ-ACK subcodebook, and the third HARQ-ACK subcodebook in a first order to obtain the target HARQ-ACK subcodebook. The first order can be (first HARQ-ACK subcodebook, second HARQ-ACK subcodebook, third HARQ-ACK subcodebook), (first HARQ-ACK subcodebook, third HARQ-ACK subcodebook, second HARQ-ACK subcodebook), (third HARQ-ACK subcodebook, second HARQ-ACK subcodebook, first HARQ-ACK subcodebook), etc., and is not limited here.

[0060] It is worth noting that in Example 1, unicast DG PDSCH and unicast SPS PDSCH belong to the aforementioned first physical downlink channel; multicast SPS PDSCH and multicast DG PDSCH belong to the aforementioned second physical downlink channel.

[0061] Example 2

[0062] If, within a certain uplink time unit (e.g., a time slot or sub-time slot), the terminal is scheduled to send back HARQ-ACKs for unicast DG PDSCH (or unicast DG PDCCH), multicast DG PDSCH, and multicast SPS PDSCH, where the unicast DG PDSCH is a PDSCH scheduled by DCI 1_0 on the Pcell, and DCI 1_0 corresponds to DAI=1 (or a unicast DCI indicating the release of the SPS PDSCH or a unicast DCI indicating Scell ​​dormancy), meaning the scenario type corresponding to the unicast DG PDSCH (or unicast PDCCH) is the first scenario, then the terminal can determine the target HARQ-ACK codebook as follows.

[0063] (a) The terminal generates the first HARQ-ACK subcodebook corresponding to the unicast DG PDSCH (or unicast DG PDCCH).

[0064] (b) The terminal can generate a second HARQ-ACK subcodebook corresponding to the multicast DG PDSCH based on the DAI.

[0065] (c) The terminal can generate the third HARQ-ACK subcodebook corresponding to the multicast SPSPDSCH based on the SPPS PDSCH configuration index, the time slot where the SPPS PDSCH is located, etc.

[0066] (d) The terminal concatenates the first HARQ-ACK subcodebook, the second HARQ-ACK subcodebook, and the third HARQ-ACK subcodebook in the second order to obtain the target HARQ-ACK codebook.

[0067] The second order can be (first HARQ-ACK subcodebook, second HARQ-ACK subcodebook, third HARQ-ACK subcodebook), (first HARQ-ACK subcodebook, third HARQ-ACK subcodebook, second HARQ-ACK subcodebook), (third HARQ-ACK subcodebook, second HARQ-ACK subcodebook, first HARQ-ACK subcodebook), etc., and is not limited here.

[0068] Furthermore, if the unicast HARQ-ACK codebook is configured as type 2, i.e., pdsch-HARQ-ACK-Codebook-Multicast=dynamic, and the multicast HARQ-ACK codebook is configured as type 1, i.e., pdsch-HARQ-ACK-Codebook=semi-static, and the terminal is activated with both unicast SPS PDSCH and multicast SPS PDSCH, then the way the terminal determines the target HARQ-ACK codebook is similar to that in Examples 1 and 2 above, and will not be repeated here to avoid repetition.

[0069] Implementation Method 2

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

[0071] (21) When the scenario type corresponding to the first physical downlink channel is the second scenario, at least two items from the following HARQ-ACK subcodebooks are generated: a first HARQ-ACK subcodebook, a second HARQ-ACK subcodebook, and a third HARQ-ACK subcodebook. The generated HARQ-ACK subcodebooks are then concatenated to obtain the target HARQ-ACK codebook. The first HARQ-ACK subcodebook corresponds to the first physical downlink channel, the second HARQ-ACK subcodebook corresponds to the DG PDSCH in the second physical downlink channel, and the third HARQ-ACK subcodebook corresponds to the SPS PDSCH in the second physical downlink channel. 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.

[0072] It is understood that the implementation method mentioned in (21) has the same or corresponding technical features as the aforementioned implementation method 1. Therefore, the implementation process of (21) can be referred to the relevant description in the method implementation method 1. To avoid repetition, it will not be repeated here.

[0073] (22) When the 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 only includes the HARQ-ACK corresponding to the SPS PDSCH in the first physical downlink channel, generate a fourth HARQ-ACK subcodebook and / or a fifth HARQ-ACK subcodebook, and concatenate the fourth HARQ-ACK subcodebook and the fifth HARQ-ACK subcodebook to obtain the HARQ-ACK codebook.

[0074] The fourth HARQ-ACK subcodebook corresponds to the DG PDSCH in the second physical downlink channel. In one implementation, the terminal can generate the fourth HARQ-ACK subcodebook according to a type 2 codebook generation method (such as according to DAI).

[0075] The fifth HARQ-ACK subcodebook corresponds to at least one of the SPS PDSCH in the first physical downlink channel, the SPS PDSCH in the second physical downlink channel, and the designated physical downlink channel in the first physical downlink channel. In one implementation, the terminal can generate the fifth HARQ-ACK subcodebook according to an SPS PDSCH HARQ-ACK codebook generation method. For example, the terminal can generate the fifth HARQ-ACK subcodebook based on the serving cell index, the SPS PDSCH configuration index, and the time slot where the SPS PDSCH is located.

[0076] Of course, in implementation method 2, 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.

[0077] Optionally, when the terminal concatenates the generated fourth and fifth HARQ-ACK subcodebooks, the concatenation order can be determined by protocol agreement, higher-layer configuration, network-side configuration, or the terminal itself. This ensures that the terminal and network-side devices have a consistent understanding of the order of the fourth and fifth HARQ-ACK subcodebooks, thereby enabling the network-side devices to clearly understand the position of the HARQ-ACK corresponding to SPS PDSCH in the target HARQ-ACK codebook when receiving the target HARQ-ACK codebook sent by the terminal.

[0078] It should be noted that if the concatenation order between the fourth HARQ-ACK subcodebook and the fifth HARQ-ACK subcodebook is determined autonomously by the terminal, then the terminal can report the concatenation order to the network-side device.

[0079] Based on the description of the aforementioned implementation method 2, assuming that the unicast HARQ-ACK codebook is configured as type 1, i.e., pdsch-HARQ-ACK-Codebook = semi-static, and the multicast HARQ-ACK codebook is configured as type 2, i.e., pdsch-HARQ-ACK-Codebook-Multicast = dynamic, and the terminal is activated with unicast SPS PDSCH and multicast SPSPDSCH, then the terminal can generate the target HARQ-ACK codebook according to Example 3 or Example 4 below, with the following content.

[0080] Example 3

[0081] In a certain uplink time unit (such as a time slot or sub-time slot), the terminal is scheduled to send back the HARQ-ACK corresponding to the unicast SPS PDSCH, the HARQ-ACK corresponding to the multicast DG PDSCH, and the HARQ-ACK corresponding to the multicast SPS PDSCH. Then, the terminal can determine the target HARQ-ACK codebook in the following manner.

[0082] (a) Since the scenario type corresponding to the unicast PDSCH (i.e. the first physical downlink channel) is the first scenario, the terminal can generate the first HARQ-ACK subcodebook corresponding to the unicast SPSPDSCH according to the serving cell index, the SPS PDSCH configuration index, the time slot where the SPS PDSCH is located, etc.

[0083] (b) The terminal can generate the second HARQ-ACK subcodebook corresponding to the multicast DG PDSCH based on the DAI.

[0084] (c) The terminal can generate the second HARQ-ACK subcodebook corresponding to the multicast SPS PDSCH based on the SPS PDSCH configuration index, the time slot where the SPS PDSCH is located, etc.

[0085] (d) The terminal concatenates the first HARQ-ACK subcodebook, the second HARQ-ACK subcodebook, and the third HARQ-ACK subcodebook in the third order to obtain the target HARQ-ACK codebook.

[0086] The third order can be (first HARQ-ACK subcodebook, second HARQ-ACK subcodebook, third HARQ-ACK subcodebook), (first HARQ-ACK subcodebook, third HARQ-ACK subcodebook, second HARQ-ACK subcodebook), (third HARQ-ACK subcodebook, second HARQ-ACK subcodebook, first HARQ-ACK subcodebook), etc., and is not limited here.

[0087] It is worth noting that in Example 3, the unicast SPS PDSCH belongs to the aforementioned first physical downlink channel. The multicast SPS PDSCH and multicast DG PDSCH belong to the second physical downlink channel.

[0088] Example 4

[0089] If, within a certain uplink time unit (such as a time slot or sub-time slot), a terminal is scheduled to send back HARQ-ACKs for unicast SPS PDSCH, multicast DG PDSCH, and multicast SPS PDSCH, then the terminal can determine the target HARQ-ACK codebook as follows.

[0090] (a) The terminal can generate the fourth HARQ-ACK subcodebook corresponding to the multicast DG PDSCH based on the DAI.

[0091] (b) The terminal can generate the fifth HARQ-ACK subcodebook corresponding to the unicast SPS and multicast SPS PDSCH based on the serving cell index, SPS PDSCH configuration index, and the time slot where the SPS PDSCH is located.

[0092] (c) The terminal concatenates the fourth HARQ-ACK subcodebook and the fifth HARQ-ACK subcodebook in a fourth order to obtain the final target HARQ-ACK subcodebook. The fourth order can be (fourth HARQ-ACK subcodebook, fifth HARQ-ACK subcodebook) or (fifth HARQ-ACK subcodebook, fourth HARQ-ACK subcodebook), and is not limited thereto.

[0093] The HARQ-ACK codebook determination method provided in this embodiment is applicable to codebook determination scenarios where unicast HARQ-ACK is configured with a type1 HARQ-ACK codebook and multicast HARQ-ACK is configured with a type2 HARQ-ACK codebook, or unicast HARQ-ACK is configured with a type2 HARQ-ACK codebook and multicast HARQ-ACK is configured with a type1 HARQ-ACK codebook. In other words, the HARQ-ACK codebook determination method provided in this embodiment can report multicast HARQ-ACK and unicast HARQ-ACK under different codebook types and / or different scenarios.

[0094] Furthermore, compared to HARQ-ACK feedback in related technologies, this application only performs HARQ-ACK codebook generation and feedback for SPS PDSCH once, thereby effectively avoiding the problem of repeated HARQ-ACK generation for SPS PDSCH in related technologies, reducing codebook size, and improving the effectiveness of the communication system.

[0095] The HARQ-ACK codebook determination method 200-300 provided in this application embodiment can be executed by a HARQ-ACK codebook determination device. This application embodiment uses the execution of the HARQ-ACK codebook determination method by a HARQ-ACK codebook determination device as an example to illustrate the HARQ-ACK codebook determination device provided in this application embodiment.

[0096] like Figure 4The diagram shown is a schematic representation of a device for determining a HARQ-ACK codebook provided in an exemplary embodiment of this application. The device 400 includes a determining module 410, used to determine a target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel. The HARQ-ACK codebook type corresponding to the physical downlink channel includes type 1 HARQ-ACK codebook and 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 only reports the HARQ-ACK corresponding to the specified physical downlink channel received during the candidate PDSCH reception time on a PUCCH. The second scenario is a scenario other than the first scenario.

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

[0098] Optionally, the step of determining the target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel by the determining module 410 includes: when the HARQ-ACK codebook type corresponding to the first physical downlink channel is the type 1 HARQ-ACK codebook and the HARQ-ACK codebook type corresponding to the second physical downlink channel is the type 2 HARQ-ACK codebook, generating at least two of the following HARQ-ACK sub-codebooks: a first HARQ-ACK sub-codebook, a second HARQ-ACK sub-codebook, and a third HARQ-ACK sub-codebook, and concatenating 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 the Dynamic Grant Physical Downlink Shared Channel (DG PDSCH) in the second physical downlink channel, and the third HARQ-ACK sub-codebook corresponds to the Semi-Persistent Scheduling (SPS) in the second physical downlink channel. PDSCH correspondence; 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.

[0099] Optionally, the step of the determining module 410 generating the first HARQ-ACK subcodebook includes any one of the following: when the scenario type corresponding to the first physical downlink channel is the first scenario, generating the first HARQ-ACK subcodebook based on the received HARQ-ACK corresponding to the first physical downlink channel; when the scenario type corresponding to the first physical downlink channel is the second scenario, determining the candidate PDSCH reception timing based on the Time Domain Resource Allocation Table (TDRA) corresponding to the first physical downlink channel, and generating the first HARQ-ACK subcodebook based on the candidate PDSCH reception timing, wherein the first HARQ-ACK subcodebook includes the HARQ-ACK subcodebook corresponding to the DG PDSCH and / or the HARQ-ACK subcodebook corresponding to the SPS PDSCH in the first physical downlink channel.

[0100] Optionally, the step of determining the target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel by the determining module 410 includes: when the HARQ-ACK codebook type corresponding to the first physical downlink channel is the type 1 HARQ-ACK codebook and the HARQ-ACK codebook type corresponding to the second physical downlink channel is the type 2 HARQ-ACK codebook, performing any one of the following: when the scenario type corresponding to the first physical downlink channel is the second scenario, generating at least two of the following HARQ-ACK sub-codebooks: a first HARQ-ACK sub-codebook, a second HARQ-ACK sub-codebook, and a third HARQ-ACK sub-codebook, and concatenating 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 the DG PDSCH in the second physical downlink channel, and the third HARQ-ACK sub-codebook corresponds to the SPS in the second physical downlink channel. PDSCH correspondence; when the scenario type corresponding to the first physical downlink channel is the first scenario, or when the target HARQ-ACK to be fed back only includes the HARQ-ACK corresponding to SPSPDSCH in the first physical downlink channel, a fourth HARQ-ACK subcodebook and / or a fifth HARQ-ACK subcodebook are generated, and the fourth HARQ-ACK subcodebook and the fifth HARQ-ACK subcodebook are concatenated to obtain the HARQ-ACK codebook; wherein, the fourth HARQ-ACK subcodebook corresponds to the DG PDSCH in the second physical downlink channel, and the fifth HARQ-ACK subcodebook corresponds to at least one of the SPS PDSCH in the first physical downlink channel, the SPS PDSCH in the second physical downlink channel, and the specified 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.

[0101] Optionally, the designated physical downlink channel includes any one of the following: a specific PDCCH, which carries a DCI of a first format and the DCI of the first format indicates the release of an SPS PDSCH, wherein the downlink allocation index DAI corresponding to the DCI of the first format is 1; a specific PDSCH, which is scheduled by a DCI of a second format and the DAI corresponding to the DCI of the second format is 1; or at least one SPS PDSCH.

[0102] Optionally, when the specific PDCCH and / or the specific PDSCH is a unicast physical downlink channel, the DCI of the first format and the DCI of the second format are both DCI1_0; when the specific PDCCH and / or the specific PDSCH is a multicast physical downlink channel, the DCI of the first format and the DCI of the second format are both DCI4_1.

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

[0104] Optionally, the physical downlink channel includes a physical downlink shared channel and a physical downlink control channel.

[0105] The HARQ-ACK codebook determination device 400 in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or other devices besides a terminal. For example, the terminal can include, but is not limited to, the type of terminal 11 listed above; other devices can be servers, network attached storage (NAS), etc., and this application embodiment does not specifically limit the type.

[0106] The HARQ-ACK codebook determination device 400 provided in this application embodiment can achieve Figures 2 to 3 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0107] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method described in method embodiments 200-300. This terminal embodiment corresponds to the above-described terminal-side method embodiments, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. Specifically, Figure 5 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

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

[0109] Those skilled in the art will understand that the terminal 500 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 510 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 5 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0110] It should be understood that, in this embodiment, the input unit 504 may include a graphics processing unit (GPU) 1041 and a microphone 5042. The GPU 5041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 506 may include a display panel 5061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. 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 a touch detection device and a touch controller. Other input devices 5072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0111] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 501 can transmit it to the processor 510 for processing; in addition, the radio frequency unit 501 can send uplink data to the network-side device. Typically, the radio frequency unit 501 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0112] The memory 509 can be used to store software programs or instructions, as well as various data. The memory 509 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 509 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 509 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0113] Processor 510 may include one or more processing units; optionally, processor 510 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 510.

[0114] The processor 510 is configured to determine a target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel; wherein the HARQ-ACK codebook type corresponding to the physical downlink channel includes type 1 HARQ-ACK codebook and type 2 HARQ-ACK codebook; the scenario type corresponding to the physical downlink channel includes a first scenario and a second scenario, wherein the first scenario is that the terminal only reports the HARQ-ACK corresponding to the specified physical downlink channel received during the candidate PDSCH reception time on a PUCCH, and the second scenario is a scenario other than the first scenario.

[0115] Optionally, the step of the processor 510 determining the target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel includes: when the HARQ-ACK codebook type corresponding to the first physical downlink channel is the type 1 HARQ-ACK codebook and the HARQ-ACK codebook type corresponding to the second physical downlink channel is the type 2 HARQ-ACK codebook, generating at least two of the following HARQ-ACK sub-codebooks: a first HARQ-ACK sub-codebook, a second HARQ-ACK sub-codebook, and a third HARQ-ACK sub-codebook; and concatenating 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 the Dynamic Grant Physical Downlink Shared Channel (DG PDSCH) in the second physical downlink channel, and the third HARQ-ACK sub-codebook corresponds to the Semi-Persistent Scheduling (SPS) in the second physical downlink channel. PDSCH correspondence; 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.

[0116] Optionally, the step of the processor 510 generating the first HARQ-ACK subcodebook includes any one of the following: when the scenario type corresponding to the first physical downlink channel is the first scenario, generating the first HARQ-ACK subcodebook according to the received HARQ-ACK corresponding to the first physical downlink channel; when the scenario type corresponding to the first physical downlink channel is the second scenario, determining the candidate PDSCH reception timing according to the Time Domain Resource Allocation Table (TDRA) corresponding to the first physical downlink channel, and generating the first HARQ-ACK subcodebook according to the candidate PDSCH reception timing, wherein the first HARQ-ACK subcodebook includes the HARQ-ACK subcodebook corresponding to the DG PDSCH and / or the HARQ-ACK subcodebook corresponding to the SPS PDSCH in the first physical downlink channel.

[0117] Optionally, the step of the processor 510 determining the target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel includes: when the HARQ-ACK codebook type corresponding to the first physical downlink channel is the type 1 HARQ-ACK codebook and the HARQ-ACK codebook type corresponding to the second physical downlink channel is the type 2 HARQ-ACK codebook, performing any one of the following: when the scenario type corresponding to the first physical downlink channel is the second scenario, generating at least two of the following HARQ-ACK sub-codebooks: a first HARQ-ACK sub-codebook, a second HARQ-ACK sub-codebook, and a third HARQ-ACK sub-codebook, and concatenating 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 the DG PDSCH in the second physical downlink channel, and the third HARQ-ACK sub-codebook corresponds to the SPS in the second physical downlink channel. PDSCH correspondence; when the scenario type corresponding to the first physical downlink channel is the first scenario, or when the target HARQ-ACK to be fed back only includes the HARQ-ACK corresponding to SPSPDSCH in the first physical downlink channel, a fourth HARQ-ACK subcodebook and / or a fifth HARQ-ACK subcodebook are generated, and the fourth HARQ-ACK subcodebook and the fifth HARQ-ACK subcodebook are concatenated to obtain the HARQ-ACK codebook; wherein, the fourth HARQ-ACK subcodebook corresponds to the DG PDSCH in the second physical downlink channel, and the fifth HARQ-ACK subcodebook corresponds to at least one of the SPS PDSCH in the first physical downlink channel, the SPS PDSCH in the second physical downlink channel, and the specified 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.

[0118] Optionally, the designated physical downlink channel includes any one of the following: a specific PDCCH, which carries a DCI of a first format and the DCI of the first format indicates the release of an SPS PDSCH, wherein the downlink allocation index DAI corresponding to the DCI of the first format is 1; a specific PDSCH, which is scheduled by a DCI of a second format and the DAI corresponding to the DCI of the second format is 1; or at least one SPS PDSCH.

[0119] Optionally, when the specific PDCCH and / or the specific PDSCH is a unicast physical downlink channel, the DCI of the first format and the DCI of the second format are both DCI1_0; when the specific PDCCH and / or the specific PDSCH is a multicast physical downlink channel, the DCI of the first format and the DCI of the second format are both DCI4_1.

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

[0121] Optionally, the physical downlink channel includes a physical downlink shared channel and a physical downlink control channel.

[0122] The implementation process of each implementation method mentioned in this embodiment can refer to the implementation process in the aforementioned method embodiments 200-300, and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0123] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described method for determining the HARQ-ACK codebook and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0124] The processor is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0125] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run network-side device programs or instructions to implement the various processes of the above-described HARQ-ACK codebook determination method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

[0127] This application also provides a computer program product, which includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor. When the program or instructions are executed by the processor, they implement the various processes of the above-described method embodiment for determining the HARQ-ACK codebook and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0128] This application also provides a communication system, including a terminal and a network-side device. The terminal can be used to execute various processes of the HARQ-ACK codebook determination method embodiment described above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0129] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0130] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0131] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for determining a hybrid automatic repeat request-acknowledgment (HARQ-ACK) codebook, characterized in that, include: The terminal determines the target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel; The HARQ-ACK codebook types corresponding to the physical downlink channel include type 1 HARQ-ACK codebook and type 2 HARQ-ACK codebook; The scenario types corresponding to the physical downlink channel include a first scenario and a second scenario. The first scenario is that the terminal only reports the HARQ-ACK corresponding to the specified physical downlink channel received during the candidate PDSCH reception time on a PUCCH. The second scenario is any scenario other than the first scenario. The step of the terminal determining the target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel includes: When the HARQ-ACK codebook type corresponding to the first physical downlink channel is the type 1 HARQ-ACK codebook and the HARQ-ACK codebook type corresponding to the second physical downlink channel is the type 2 HARQ-ACK codebook, the terminal generates a first HARQ-ACK sub-codebook and at least one of the following HARQ-ACK sub-codebooks: a second HARQ-ACK sub-codebook and a third HARQ-ACK sub-codebook, and concatenates the generated HARQ-ACK sub-codebooks to obtain the target HARQ-ACK codebook; Wherein, the first HARQ-ACK subcodebook corresponds to the first physical downlink channel, the second HARQ-ACK subcodebook corresponds to the Dynamically Granted Physical Downlink Shared Channel (DG PDSCH) in the second physical downlink channel, and the third HARQ-ACK subcodebook corresponds to the Semi-Persistent Scheduling (SPS PDSCH) in the second physical downlink channel; 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. The step of the terminal generating the first HARQ-ACK subcodebook includes any one of the following: When the scenario type corresponding to the first physical downlink channel is the first scenario, the terminal generates the first HARQ-ACK subcodebook according to the HARQ-ACK corresponding to the received first physical downlink channel; When the scenario type corresponding to the first physical downlink channel is the second scenario, the terminal determines the candidate PDSCH reception timing according to the Time Domain Resource Allocation Table (TDRA) corresponding to the first physical downlink channel, and generates the first HARQ-ACK subcodebook according to the candidate PDSCH reception timing. The first HARQ-ACK subcodebook includes the HARQ-ACK subcodebook corresponding to the DG PDSCH and / or the HARQ-ACK subcodebook corresponding to the SPS PDSCH in the first physical downlink channel.

2. The method as described in claim 1, characterized in that, The step of the terminal determining the target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel further includes: When the HARQ-ACK codebook type corresponding to the first physical downlink channel is the type 1 HARQ-ACK codebook and the HARQ-ACK codebook type corresponding to the second physical downlink channel is the type 2 HARQ-ACK codebook, the terminal performs any of the following: When the scenario type corresponding to the first physical downlink channel is the second scenario, at least two items of the following HARQ-ACK subcodebooks are generated: a first HARQ-ACK subcodebook, a second HARQ-ACK subcodebook, and a third HARQ-ACK subcodebook. The generated HARQ-ACK subcodebooks are concatenated to obtain the target HARQ-ACK codebook. The first HARQ-ACK subcodebook corresponds to the first physical downlink channel, the second HARQ-ACK subcodebook corresponds to the DG PDSCH in the second physical downlink channel, and the third HARQ-ACK subcodebook corresponds to the SPS PDSCH in the second physical downlink channel. When the scenario type corresponding to the first physical downlink channel is the first scenario, or when the target HARQ-ACK to be fed back only includes the HARQ-ACK corresponding to the SPS PDSCH in the first physical downlink channel, a fourth HARQ-ACK subcodebook and / or a fifth HARQ-ACK subcodebook are generated, and the fourth HARQ-ACK subcodebook and the fifth HARQ-ACK subcodebook are concatenated to obtain the HARQ-ACK codebook; wherein, the fourth HARQ-ACK subcodebook corresponds to the DG PDSCH in the second physical downlink channel, and the fifth HARQ-ACK subcodebook corresponds to at least one of the SPS PDSCH in the first physical downlink channel, the SPS PDSCH in the second physical downlink channel, and the specified 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.

3. The method according to any one of claims 1-2, characterized in that, The designated physical downlink channel includes any of the following: A specific PDCCH carries downlink control information (DCI) in a first format, and the first format DCI indicates the release of the SPS PDSCH, wherein the downlink allocation index (DAI) corresponding to the first format DCI is 1. A specific PDSCH, which is scheduled by a second-format DCI, and the DAI corresponding to the second-format DCI is 1; At least one SPS PDSCH.

4. The method as described in claim 3, characterized in that, When the specific PDCCH and / or the specific PDSCH is a unicast physical downlink channel, both the first format DCI and the second format DCI are DCI 1_0. When the specific PDCCH and / or the specific PDSCH is a multicast physical downlink channel, the DCI of the first format and the DCI of the second format are DCI 4_1.

5. The method as described in claim 3, characterized in that, The specific PDSCH is located in the primary cell Pcell.

6. The method according to any one of claims 1-5, characterized in that, The physical downlink channel includes the physical downlink shared channel and the physical downlink control channel.

7. A device for determining a hybrid automatic repeat request-acknowledgment (HARQ-ACK) codebook, characterized in that, include: The determination module is used to determine the target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel; The HARQ-ACK codebook types corresponding to the physical downlink channel include type 1 HARQ-ACK codebook and type 2 HARQ-ACK codebook; The scenario types corresponding to the physical downlink channel include a first scenario and a second scenario. The first scenario is that the terminal only reports the HARQ-ACK corresponding to the specified physical downlink channel received during the candidate PDSCH reception time on a PUCCH. The second scenario is any scenario other than the first scenario. The step of determining the target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel includes: When the HARQ-ACK codebook type corresponding to the first physical downlink channel is the type 1 HARQ-ACK codebook and the HARQ-ACK codebook type corresponding to the second physical downlink channel is the type 2 HARQ-ACK codebook, a first HARQ-ACK sub-codebook and at least one of the following HARQ-ACK sub-codebooks are generated: a second HARQ-ACK sub-codebook and a third HARQ-ACK sub-codebook, and the generated HARQ-ACK sub-codebooks are concatenated to obtain the target HARQ-ACK codebook; Wherein, the first HARQ-ACK subcodebook corresponds to the first physical downlink channel, the second HARQ-ACK subcodebook corresponds to the Dynamically Granted Physical Downlink Shared Channel (DG PDSCH) in the second physical downlink channel, and the third HARQ-ACK subcodebook corresponds to the Semi-Persistent Scheduling (SPS PDSCH) in the second physical downlink channel; 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. The step of the determining module generating the first HARQ-ACK subcodebook includes any one of the following: When the scenario type corresponding to the first physical downlink channel is the first scenario, the first HARQ-ACK subcodebook is generated according to the HARQ-ACK corresponding to the received first physical downlink channel; When the scenario type corresponding to the first physical downlink channel is the second scenario, the candidate PDSCH reception timing is determined according to the Time Domain Resource Allocation Table (TDRA) corresponding to the first physical downlink channel, and the first HARQ-ACK subcodebook is generated according to the candidate PDSCH reception timing. The first HARQ-ACK subcodebook includes the HARQ-ACK subcodebook corresponding to the DG PDSCH and / or the HARQ-ACK subcodebook corresponding to the SPS PDSCH in the first physical downlink channel.

8. The apparatus as claimed in claim 7, characterized in that, The step of determining the target HARQ-ACK codebook based on the HARQ-ACK codebook type and / or scenario type corresponding to the physical downlink channel includes: If the HARQ-ACK codebook type corresponding to the first physical downlink channel is the type 1 HARQ-ACK codebook and the HARQ-ACK codebook type corresponding to the second physical downlink channel is the type 2 HARQ-ACK codebook, perform any of the following: When the scenario type corresponding to the first physical downlink channel is the second scenario, at least two items of the following HARQ-ACK subcodebooks are generated: a first HARQ-ACK subcodebook, a second HARQ-ACK subcodebook, and a third HARQ-ACK subcodebook. The generated HARQ-ACK subcodebooks are concatenated to obtain the target HARQ-ACK codebook. The first HARQ-ACK subcodebook corresponds to the first physical downlink channel, the second HARQ-ACK subcodebook corresponds to the DG PDSCH in the second physical downlink channel, and the third HARQ-ACK subcodebook corresponds to the SPS PDSCH in the second physical downlink channel. When the scenario type corresponding to the first physical downlink channel is the first scenario, or when the target HARQ-ACK to be fed back only includes the HARQ-ACK corresponding to the SPS PDSCH in the first physical downlink channel, a fourth HARQ-ACK subcodebook and / or a fifth HARQ-ACK subcodebook are generated, and the fourth HARQ-ACK subcodebook and the fifth HARQ-ACK subcodebook are concatenated to obtain the HARQ-ACK codebook; wherein, the fourth HARQ-ACK subcodebook corresponds to the DG PDSCH in the second physical downlink channel, and the fifth HARQ-ACK subcodebook corresponds to at least one of the SPS PDSCH in the first physical downlink channel, the SPS PDSCH in the second physical downlink channel, and the specified 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.

9. The apparatus as described in any one of claims 7-8, characterized in that, The designated physical downlink channel includes any of the following: A specific PDCCH carries a DCI of a first format, and the DCI of the first format indicates the release of SPSPDSCH, wherein the downlink allocation index DAI corresponding to the DCI of the first format is 1; A specific PDSCH, which is scheduled by a second-format DCI, and the DAI corresponding to the second-format DCI is 1; At least one SPS PDSCH.

10. The apparatus as claimed in claim 9, characterized in that, When the specific PDCCH and / or the specific PDSCH is a unicast physical downlink channel, the DCI of the first format and the DCI of the second format are both DCI1_0; When the specific PDCCH and / or the specific PDSCH is a multicast physical downlink channel, the DCI of the first format and the DCI of the second format are DCI 4_1.

11. The apparatus as claimed in claim 9, characterized in that, The specific PDSCH is located in the primary cell Pcell.

12. The apparatus according to any one of claims 7-11, characterized in that, The physical downlink channel includes the physical downlink shared channel and the physical downlink control channel.

13. A terminal, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method for determining the HARQ-ACK codebook as described in any one of claims 1 to 6.

14. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the method for determining the HARQ-ACK codebook as described in any one of claims 1-6.

Images