HARQ-ACK codebook generation method, information transmission method and device

Abstract

The present application provides a HARQ-ACK codebook generation method, an information transmission method, a terminal, and a network side device, the method including: receiving first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI including a first data allocation indicator (DAI); determining second data allocation indicators (DAIs) corresponding to each PDSCH group among N physical downlink shared channel (PDSCH) groups according to the first DCI; and generating a dynamic codebook to be transmitted on the first PUSCH according to the determined N second DAIs, where the dynamic codebook includes HARQ-ACK bit sequences for the N PDSCH groups, where N is a positive integer.

Description

[Technical field]

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a HARQ-ACK codebook generation method, an information transmission method, a terminal, and a network side device. [Background technology]

[0002] When the UE organizes the HARQ-ACK bit sequence that needs to be reported at a certain feedback time, the UE determines the correspondence between each Physical Downlink Shared Channel (PDSCH) transmission and some / some bits in the organized HARQ-ACK bit sequence according to a predefined rule and a scheduling situation of a Physical Downlink Shared Channel (PDSCH) transmitted on a single / multiple carriers that needs to report HARQ-ACK at this feedback time, and such an operation is called constructing a HARQ-ACK codebook. The HARQ-ACK codebook includes a semi-static codebook and a dynamic codebook.

[0003] The HARQ-ACK Codebook is generally transmitted on the PUCCH, but when the PUCCH transmission overlaps with a certain PUSCH transmission in the time domain, some or all of the UCI carried on the PUCCH is multiplexed and transmitted on the PUSCH. In the DCI format 0_1 ​​for scheduling the PUSCH, the DAI corresponding to the HARQ-ACK Codebook to be multiplexed and transmitted may be indicated, and may be called the UL DAI.

[0004] Currently, a terminal can be configured to perform HARQ-ACK feedback for at most two PDSCH groups using one dynamic codebook, but when there is only a single or single group of UL DAI in uplink DCI format 0_1, there is currently no corresponding solution as to how this UL DAI is used to generate this dynamic codebook. Summary of the Invention [Problem to be solved by the invention]

[0005] The embodiments of the present application provide a HARQ-ACK codebook generation method, an information transmission method, a terminal, and a network side device to solve the problem of how to generate a dynamic codebook for performing HARQ-ACK feedback for at most two PDSCH groups based on UL DAI. [Means for solving the problem]

[0006] According to a first aspect, an embodiment of the present application provides a method for generating a HARQ-ACK codebook, the method comprising: receiving first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI including a first DAI; determining a second DAI corresponding to each PDSCH group among the N physical downlink shared channel (PDSCH) groups based on the first DAI; generating a dynamic codebook to be transmitted on the first PUSCH based on the determined N second DAIs; Wherein, the dynamic codebook includes HARQ-ACK bit sequences of the N PDSCH groups, where N is a positive integer.

[0007] According to a second aspect, an embodiment of the present application provides an information transmission method, the method comprising: transmitting first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI including a first DAI, the first DAI being used to generate a dynamic codebook transmitted on the first PUSCH; Wherein, the dynamic codebook includes HARQ-ACK bit sequences of N PDSCH groups, where N is a positive integer.

[0008] According to a third aspect, an embodiment of the present application further provides a terminal, the terminal comprising: A receiving module for receiving first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI including a first DAI; a determining module for determining a second DAI corresponding to each PDSCH group among the N physical downlink shared channel (PDSCH) groups according to the first DAI; and a generating module for generating a dynamic codebook to be transmitted on the first PUSCH based on the determined N second DAIs; Wherein, the dynamic codebook includes HARQ-ACK bit sequences of the N PDSCH groups, where N is a positive integer.

[0009] According to a fourth aspect, the embodiment of the present application further provides a network side device, the network side device comprising: A transmitting module for transmitting first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI including a first DAI, the first DAI being used to generate a dynamic codebook transmitted on the first PUSCH; Wherein, the dynamic codebook includes HARQ-ACK bit sequences of N PDSCH groups, where N is a positive integer.

[0010] According to a fifth aspect, an embodiment of the present application further provides a terminal, which includes a processor, a memory, and a computer program stored in the memory and operable on the processor, and which, when executed by the processor, realizes the steps of the above-mentioned HARQ-ACK codebook generation method.

[0011] According to a sixth aspect, an embodiment of the present application further provides a network side device, which includes a processor, a memory, and a computer program stored in the memory and operable on the processor, and which, when executed by the processor, realizes the steps of the above-mentioned information transmission method.

[0012] According to a seventh aspect, an embodiment of the present application further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, realizes the steps of the above-mentioned HARQ-ACK codebook generation method for use in a terminal or the steps of the information transmission method for use in a network side device. Effect of the Invention

[0013] In an embodiment of the present application, after receiving a first downlink control information DCI including a first DAI for scheduling a first physical uplink shared channel PUSCH, the terminal can determine a second DAI corresponding to each PDSCH group among N physical downlink shared channel PDSCH groups according to the first DAI, and further generate a dynamic codebook transmitted on the first PUSCH according to the determined N second DAIs, where the dynamic codebook includes HARQ-ACK bit sequences of the N PDSCH groups, where N is a positive integer. As can be seen, the embodiment of the present application provides a solution for generating a dynamic codebook including HARQ-ACK bit sequences of the N PDSCH groups according to the first DAI, and can further ensure the reliability of transmission of the dynamic codebook and avoid or reduce the effect of decoding other information multiplexed and transmitted on the PUSCH. [Brief description of the drawings]

[0014] In order to more clearly describe the technical solutions of the embodiments of the present application, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments of the present application. It is obvious that the accompanying drawings in the following description are only some embodiments of the present application, and those skilled in the art can obtain other accompanying drawings based on these accompanying drawings without making creative efforts. [Figure 1] FIG. 1 is a structural diagram of a network system to which the embodiments of the present application can be applied. [Diagram 2] 4 is a flowchart of a HARQ-ACK codebook generation method according to an embodiment of the present application; [Diagram 3] 2 is a flowchart of an information transmission method according to an embodiment of the present application. [Figure 4] FIG. 2 is a schematic diagram of a dynamic codebook transmission according to an embodiment of the present application; [Diagram 5] 1 is a structural diagram of a terminal according to an embodiment of the present application; [Figure 6] 1 is a structural diagram of a network side device according to an embodiment of the present application; [Figure 7] 2 is a second structural diagram of a terminal according to an embodiment of the present application. [Figure 8] 2 is a second structural diagram of a network side device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] The following clearly describes the technical solutions in the embodiments of the present application in conjunction with the accompanying 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 without any creative effort are all within the scope of protection of the present application.

[0016] The terms "first", "second", etc., used in this application are intended to distinguish between similar objects and not necessarily to describe a particular order or sequence. The terms "comprise" and "have" and any variations thereof are intended to cover non-exclusive "comprises", e.g., a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to the process, method, product, or device. The term "and / or" used in this application refers to at least one of the connected objects, e.g., A and / or B and / or C includes seven cases: A alone, B alone, C alone, a combination of A and B, a combination of B and C, a combination of A and C, and a combination of A, B, and C.

[0017] Referring to Fig. 1, Fig. 1 is a structural diagram of a network system applicable to the embodiment of the present application. As shown in Fig. 1, it includes a terminal 11 and a network side device 12, among which, the terminal 11 and the network side device 12 can communicate with each other.

[0018] In the embodiment of the present application, the terminal 11 may be referred to as a user equipment (UE). In practical applications, the terminal 11 may be a mobile phone, a tablet personal computer, a laptop computer, a personal digital assistant (PDA), a mobile internet device (MID), a wearable device, or an in-vehicle device, etc. The network side equipment 12 may be a base station, a relay, or an access point, etc. Furthermore, the base station may be a 5G base station (gNB), or a base station in another communication system (e.g., an evolved Node B (eNB)), etc.

[0019] For ease of understanding, the following provides some details regarding the embodiments of the present application.

[0020] 1. New Radio (NR) Hybrid Automatic Repeat reQuest Acknowledgement (HARQ-ACK) dynamic codebook.

[0021] When a UE organizes a HARQ-ACK bit sequence that needs to be reported at a certain feedback time, the UE determines the correspondence between each Physical Downlink Shared Channel (PDSCH) transmission and some / any bits in the organized HARQ-ACK bit sequence based on a predefined rule and the scheduling situation of PDSCH transmissions on single / multiple carriers on which HARQ-ACK needs to be reported at this feedback time, and such an operation is called constructing a HARQ-ACK codebook.

[0022] When Downlink Control Information (DCI) indicates the release of a Semi-Persistent Scheduling (SPS) PDSCH, the UE also needs to acknowledge its reception using the HARQ-ACK bit to ensure that both parties agree on whether the SPS PDSCH is activated or not.

[0023] The HARQ-ACK Codebook includes a semi-static codebook (Type-1) and a dynamic codebook (Type-2). The former provides feedback for all possible DCI indications and PDSCH transmissions, and is mainly used to ensure transmission reliability, and the feedback overhead is relatively large. The latter provides feedback only for actual DCI indications and PDSCH transmissions, and the feedback overhead is relatively small. When DCI check omissions are relatively common, the transmission reliability will be affected to a certain extent.

[0024] The dynamic codebook reserves a HARQ-ACK feedback bit for each actually used DAI value by counting a Downlink Assignment Index (DAI) for an actually scheduled PDSCH transmission or an SPS PDSCH release indication.

[0025] If the UE infers through the detected other DAIs that a PDSCH allocation indication or an SPS PDSCH release indication corresponding to some DAIs has not been received, then it sets the corresponding feedback bit to NACK; otherwise, it sets the corresponding HARQ-ACK feedback bit according to the decoding result of the PDSCH transmission corresponding to each PDSCH allocation indication, and sets the corresponding feedback bit to ACK for the detected SPS PDSCH release indication.

[0026] DAI adopts a limited number of bits (a single DAI generally occupies 2 bits) to indicate, and in order to extend its indication range, modulo operation is introduced, that is, first counting from 1, and then modulo to obtain a DAI value corresponding to a certain count value. The processing of DAI in downlink scheduling can be seen in the table below.

[0027] Counter DAI value and DAI in DCI format 1_0 Counter DAI or total number DAI value in DCI format 1_1 [Table 1]

[0028] In the above table, Most Significant Bit (MSB), Least Significant Bit (LSB), Counter DAI (C-DAI), Total DAI (T-DAI).

[0029] Y is the number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH transmission(s) associated with PDCCH or PDCCH indicating SPS PDSCH release is present, denoted as Y, where Y≧1.

[0030] When the UE is configured with only a single serving cell, the aforesaid DAI counts sequentially in the time priority indicated by the DCI for only a single carrier, and may be referred to as C-DAI.

[0031] To further increase reliability when a UE has multiple serving cells, T-DAI is newly introduced, which is used to indicate the number indicated by all DCIs received up to the current time domain detection position, and contains all DCI indications received on each serving cell at the current time domain detection position, so the value of T-DAI is updated only when the time domain detection position changes.

[0032] The combined use of T-DAI and C-DAI can effectively avoid inconsistent UE and gNB understanding of DCI-indicated transmissions when DCI indications are lost on one or some serving cells of a certain time domain detection position (unless all DCI indications on all serving cells are lost).

[0033] In the embodiment of the present application, the following describes a method for determining the HARQ-ACK bit sequence corresponding to each DAI.

[0034] In the first case, when the network side device configures the parameter PDSCH-Code Block Group Transmission for a serving cell of the UE and turns on HARQ transmission based on the code block group (CBG), Scheme 1: PDSCH transmission scheduled by DCI format 1_1 supports HARQ transmission based on CBG, and a single DAI is TIFF0007671934000002.tif corresponds to 6161 HARQ-ACK feedback bits.

[0035] Among them, TIFF0007671934000003.tif6161 is where the parameter PDSCH-CodeBlockGroupTransmission is placed. TIFF0007671934000004.tif616For 1 serving cell TIFF0007671934000005.tif6161 is the maximum value of TIFF0007671934000006.tif6161 is a serving cell This is the value of the parameter maxNrofCodeWordsScheduledByDCI in TIFF0007671934000007.tif6161, which indicates the maximum number of transmission blocks that a single DCI can simultaneously schedule. TIFF0007671934000008.tif8161 is a serving cell This is the possible value of the parameter maxCodeBlockGroupsPerTransportBlock in TIFF0007671934000009.tif6161, which indicates the maximum number of CBGs that can be divided by a single transport block.

[0036] A serving cell Regarding TIFF0007671934000010.tif6161,

number

number

[0037] Previous TIFF0007671934000014.tif6161 bits are set based on the decoding status of each CBG corresponding to the actually received transmission block.

[0038] In mode 2, PDSCH transmission scheduled by DCI format 1_0 only supports HARQ transmission based on transport block (TB), which is similar to SPS PDSCH release indication and SPS PDSCH reception, and only one HARQ-ACK bit is fed back for a single transport block. These cases belong to the case where a single DCI indication or PDSCH transmission corresponds to only a single transport block.

[0039] In the second case, if the network does not configure the parameter PDSCH-CodeBlockGroupTransmission for a serving cell of the UE, i.e., does not turn on CBG-based HARQ transmission, Scheme 1: no harq-ACK-SpatialBundlingPUCCH or harq-ACK-Spatial BundlingPUSCH parameter is configured for the UE (i.e., spatial bundling for HARQ-ACK is not turned on, where spatial bundling may be understood as HARQ-ACK feedback compression aggregation between two codewords corresponding to the same PDSCH transmission, in which the harq-ACK-SpatialBundlingPUCCH parameter is used for HARQ-ACK transmission carried on the PUCCH, and the harq-ACK-SpatialBundlingPUSCH parameter is used for HARQ-ACK transmission carried on the PUSCH), and at least a portion of a downlink (DL) bandwidth of at least a serving cell of the UE is configured. If the maxNrofCodeWordsScheduledByDCI parameter for each PDSCH reception is configured to correspond to at most two transport blocks (Part, BWP), then a single DAI corresponds to two HARQ-ACK bits, of which the first bit indicates the HARQ-ACK of the first transport block and the second bit indicates the HARQ-ACK of the second transport block.

[0040] Method 2: If the harq-ACK-SpatialBundlingPUCCH or harq-ACK-SpatialBundlingPUSCH parameters have been configured for the UE, and the maxNrofCodeWordsScheduledByDCI parameter is configured for at least a DL BWP of at least a serving cell of the UE such that one PDSCH reception corresponds to at most two transport blocks, then a single DAI corresponds to a single HARQ-ACK bit, and the result is set to the logical AND of the HARQ-ACK of the first transport block and the HARQ-ACK of the second transport block.

[0041] Scheme 3: otherwise, a single DAI corresponds to a single HARQ-ACK bit, and the selected value is set to the HARQ-ACK of a unique transmission block. Wherein, "otherwise" refers to the remaining cases other than the cases listed in Scheme 1 and Scheme 2, that is, it indicates that it is not configured to correspond to at most two transmission blocks, and the Spatial Bundling related parameters are not configured. At this time, a single downlink DCI only schedules a single transmission block, so a single DAI corresponds to a single HARQ-ACK bit.

[0042] When the network side device configures the parameter PDSCH-Code BlockGroupTransmission for a serving cell or cells of the UE to turn on HARQ transmission based on CBG, the HARQ-ACK Codebook includes two HARQ-ACK sub-codebooks. Among them, the first sub-codebook includes all HARQ-ACK bits with TB granularity and is related to HARQ-ACK corresponding to SPS PDSCH release indication, SPS PDSCH reception, PDSCH transmission scheduled by DCI format 1_0 on serving cells where CBG-based HARQ transmission is turned on (these PDSCH transmissions only support HARQ-ACK feedback with TB granularity), and PDSCH transmission scheduled by DCI format 1_0 / 1_1 on serving cells where CBG-based HARQ transmission is not turned on (these PDSCH transmissions always support HARQ-ACK feedback with TB granularity), and the second sub-codebook includes all HARQ-ACK bits with CBG granularity and is related to HARQ-ACK corresponding to PDSCH transmission scheduled by DCI format 1_1 on serving cells where CBG-based HARQ transmission is turned on. The HARQ-ACK Codebook is sequentially cascaded by the first sub-codebook and the second sub-codebook.

[0043] The HARQ-ACK Codebook is generally transmitted on the PUCCH, and the time domain and frequency domain information of the PUCCH are indicated in the DCI (as an exception, the frequency domain information of the HARQ-ACK feedback PUCCH of the SPS PDSCH may be configured by a higher layer). When the PUCCH transmission overlaps with a certain PUSCH transmission in the time domain, some or all of the UCI carried on the PUCCH is multiplexed and transmitted on the PUSCH.

[0044] For the HARQ-ACK dynamic codebook, DCI check omission affects the construction of the HARQ-ACK Codebook (including the number of HARQ-ACK bits included in the Codebook), but the number of HARQ-ACK bits affects the time-frequency resources occupied when it is multiplexed and transmitted on the PUSCH, thereby affecting the time-frequency demapping and decoding of other data transmissions on the PUSCH (e.g., UL-SCH). In order to avoid the influence of the misunderstanding between the UE and the network side regarding the number of HARQ-ACK bits, the DAI corresponding to the HARQ-ACK Codebook to be multiplexed and transmitted may be indicated in the DCI format 0_1 ​​for scheduling the PUSCH, and may be called the UL DAI. The UL DAI is mainly used by the UE to determine the number of HARQ-ACK bits in the HARQ-ACK Codebook, and can be used to determine the DCI check omission status corresponding to the last HARQ-ACK bit of the HARQ-ACK Codebook. When the HARQ-ACK Codebook only relates to HARQ-ACK feedback with TB granularity (i.e., does not relate to two sub-codebooks), only a single UL DAI is indicated in DCI format 0_1 ​​(indicated by the DCI domain "1st downlink assignment index") and corresponds to a single HARQ-ACK Codebook. When the HARQ-ACK Codebook simultaneously relates to HARQ-ACK feedback with TB granularity and HARQ-ACK feedback with CBG granularity (i.e., is sequentially cascaded by two sub-codebooks), two UL DAIs are indicated simultaneously in DCI format 0_1, of which the first UL DAI (indicated by the DCI domain "1st downlink assignment index") is used for the first sub-codebook, and the second UL DAI (indicated by the DCI domain "2nd downlink assignment index") is used for the second sub-codebook.

[0045] Second, NR-U HARQ-ACK dynamic codebook extension.

[0046] The main points for the dynamic codebook implementation extension include the following:

[0047] The dynamically scheduled PDSCH is explicitly packetized, and the packets corresponding to the scheduled PDSCH are indicated in the scheduling DCI, and all HARQ-ACK feedbacks corresponding to the same PDSCH packet are carried on the same PUCCH.

[0048] C-DAI or T-DAI counting is performed within a single PDSCH packet.

[0049] Each PDSCH packet maintains a new feedback indicator (NFI), which indicates whether to transmit only new feedback or to resend the previous feedback according to the inversion method. If the NFI is inverted, the DCI with the inverted NFI indicates that all feedback for this PDSCH packet before is discarded, and only the DCI and the HARQ-ACK feedback of the PDSCH scheduled for this PDSCH packet are transmitted after the inversion of the NFI last time. If the NFI is not inverted, all HARQ-ACK feedback for this PDSCH packet after the inversion of the NFI last time must be transmitted, that is, all HARQ-ACK feedback with the same NFI value is valid. This may cause the number of HARQ-ACK bits that actually need to be transmitted for two feedback requests for the same PDSCH packet to change.

[0050] While a single DCI can request HARQ-ACK feedback for one to multiple PDSCH packets to be transmitted on the same PUCCH, typically a single downlink scheduling DCI will by default request HARQ-ACK feedback for PDSCH packets corresponding to the PDSCH scheduled by it, and this DCI can additionally trigger HARQ-ACK feedback for other PDSCH packets to be transmitted together on their indicated PUCCHs.

[0051] Currently the maximum number of PDSCH packets supported is two.

[0052] The UE may indicate, via the capability information, whether or not it supports an extended dynamic codebook.

[0053] When an extended dynamic codebook is configured for a UE, whether or not a UL DAI for an additional single PDSCH packet exists in an uplink non-fallback DCI, i.e., DCI format 0_1, can be configured by Radio Resource Control (RRC) signaling. However, when only a UL DAI for a single PDSCH packet exists in DCI format 0_1, there is currently no corresponding solution as to which PDSCH packet the UL DAI is used for.

[0054] The following describes a method for generating a HARQ-ACK codebook in an embodiment of the present application.

[0055] Please refer to Figure 2, which is a flowchart of a HARQ-ACK codebook generation method according to an embodiment of the present application. The HARQ-ACK codebook generation method of the embodiment of the present application may be used in a terminal.

[0056] As shown in FIG. 2, the HARQ-ACK codebook generation method may include the following steps:

[0057] Step 201: receiving first downlink control information DCI for scheduling a first physical uplink shared channel (PUSCH), where the first DCI includes a first DAI.

[0058] Step 202: determine a second DAI corresponding to each PDSCH group among the N PDSCH groups according to the first DAI, where N is a positive integer.

[0059] The second DAI corresponding to each PDSCH group is used to determine the HARQ-ACK bit sequence for this PDSCH group.

[0060] Step 203: generate a dynamic codebook to be transmitted on the first PUSCH according to the determined N second DAIs, where the dynamic codebook includes HARQ-ACK bit sequences of the N PDSCH groups.

[0061] When specifically implemented, the above-mentioned generating a dynamic codebook to be transmitted on the first PUSCH according to the determined N second DAIs is specifically determining a HARQ-ACK sequence for each PDSCH group among the N PDSCH groups based on the determined N second DAIs; and generating the dynamic codebook based on a HARQ-ACK sequence of each PDSCH group among the N PDSCH groups.

[0062] When specifically implemented, optionally, the HARQ-ACK sequence of each PDSCH group among the N PDSCH groups may be sequentially cascaded according to the size order of the group numbers of the N PDSCH groups to generate the dynamic codebook, but is not limited thereto.

[0063] In the HARQ-ACK codebook generation method of this embodiment, after receiving a first downlink control information DCI including a first DAI for scheduling a first physical uplink shared channel PUSCH, the terminal can determine a second DAI corresponding to each PDSCH group among N physical downlink shared channel PDSCH groups according to the first DAI, and further generate a dynamic codebook transmitted on the first PUSCH according to the determined N second DAIs, where the dynamic codebook includes HARQ-ACK bit sequences of the N PDSCH groups, where N is a positive integer. It can be seen that the embodiment of the present application provides a solution for generating a dynamic codebook including HARQ-ACK bit sequences of the N PDSCH groups according to the first DAI, and can further ensure the reliability of transmission of the dynamic codebook.

[0064] In this embodiment, selectively determining a second DAI corresponding to each PDSCH group among the N physical downlink shared channel PDSCH groups based on the first DAI as described above includes: determining a first relationship between the first DAI and N PDSCH groups; and determining a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the first relationship.

[0065] When specifically implemented, the determination of the first relationship between the first DAI and the N PDSCH groups may include the following two embodiments.

[0066] In a first embodiment, the first relationship satisfies that the first DAI corresponds to at least one PDSCH group among the N PDSCH groups.

[0067] That is, in the first embodiment, the first DAI necessarily has a corresponding relationship with at least one PDSCH group among the N PDSCH groups.

[0068] If N is equal to 1, ie, the N PDSCH groups include only one PDSCH group, the first DAI corresponds to this PDSCH group.

[0069] When N is greater than 1, optionally the first relationship is: The first DAI corresponds to the N PDSCH groups; the first DAI corresponds to a first PDSCH group among the N PDSCH groups.

[0070] The first PDSCH group is one of the N PDSCH groups.

[0071] When specifically implemented, the first PDSCH group may be any one of the N PDSCH groups. The first PDSCH group is a PDSCH group in which a PDSCH scheduled by a target DCI is located, and the target DCI is a DCI for scheduling a PDSCH in the N PDSCH groups that is last detected by the terminal; The first PDSCH group is determined by a protocol; the first PDSCH group is configured by a network side device.

[0072] For ease of understanding, each case will be explained separately below.

[0073] In case 1, the first PDSCH group is a PDSCH group in which a PDSCH scheduled by a target DCI is located, and the target DCI is a DCI for scheduling a PDSCH in the N PDSCH groups that is last detected by the terminal.

[0074] In case 1, the first PDSCH group is autonomously determined by the terminal according to the scheduling time of each PDSCH group.

[0075] Each PDSCH group includes at least one PDSCH, and each PDSCH corresponds to one DCI for scheduling its transmission, and the PDSCH scheduling time at which each DCI schedules the PDSCH may be different.

[0076] Exemplarily, if the N PDSCH groups include PDSCH group 1, PDSCH group 2, and PDSCH group 3, the terminal last detects that the DCI for scheduling the PDSCH in the N PDSCH groups is the DCI for scheduling the PDSCH in PDSCH group 3. Therefore, the terminal can determine the PDSCH group 3 as the first PDSCH group.

[0077] In case two, the first PDSCH group satisfies that the first PDSCH group is agreed upon by a protocol.

[0078] In case 2, the first PDSCH group is one PDSCH group among the N PDSCH groups agreed upon by a protocol.

[0079] For example, the first PDSCH group may be determined by the protocol to be the first or last PDSCH group among N PDSCH groups, or the PDSCH group with the smallest or largest group number, or the PDSCH group whose corresponding HARQ-ACK bit sequence is placed at the beginning or end of the bit sequence corresponding to the dynamic codebook when generating the dynamic codebook, or the PDSCH group whose group number is a specified value.

[0080] In case three, the first PDSCH group satisfies that the first PDSCH group is configured by a network side device.

[0081] In case 3, the first PDSCH group is one PDSCH group among the N PDSCH groups configured by a network side device.

[0082] For example, the first PDSCH group may be configured by the network side equipment so that it is the first or last PDSCH group among N PDSCH groups, or the PDSCH group with the smallest or largest group number, or the PDSCH group whose corresponding HARQ-ACK bit sequence is placed at the beginning or end of the bit sequence corresponding to the dynamic codebook when generating the dynamic codebook, or the PDSCH group whose group number is a specified value.

[0083] As can be seen, in cases 2 and 3, compared with case 1, the terminal does not need to autonomously determine the first PDSCH group, so that the burden on the terminal can be reduced. In cases 1 and 3, compared with case 2, the flexibility of determining the first PDSCH group is higher. In cases 1 and 2, compared with case 3, the terminal does not need to interact with a network side device to determine the first PDSCH group, so that the signaling overhead can be reduced.

[0084] In the second embodiment, the above-mentioned determining a first relationship between the first DAI and the N PDSCH groups includes: determining a first relationship between the first DAI and N PDSCH groups based on a preset rule; Among them, the preset rules are: determining a PDSCH group corresponding to the first DAI according to a PDSCH group located and scheduled by a target DCI, the target DCI being a DCI for scheduling a PDSCH in the N PDSCH groups last detected by the terminal; determining a PDSCH group corresponding to the first DAI based on a protocol agreement; determining a PDSCH group corresponding to the first DAI based on configuration information of network side devices.

[0085] Optionally, to the second embodiment, the first relationship is: The first DAI corresponds to a fifth PDSCH group among the N PDSCH groups, and the fifth PDSCH group is any one of the N PDSCH groups; The first DAI does not correspond to any of the N PDSCH groups.

[0086] It should be noted that the fifth PDSCH group is similar to the first PDSCH group, and for details, refer to the description of the first PDSCH group, and no further description will be given here.

[0087] As can be seen, in the second embodiment, when the first relationship between the first DAI and the N PDSCH groups is determined based on a preset rule, the first DAI does not need to correspond to any one of the N PDSCH groups, that is, the first DAI is not related to the N PDSCH groups. Therefore, in the second embodiment, the first DAI does not necessarily have a corresponding relationship with the N PDSCH groups.

[0088] As can be seen from the above, in this embodiment, the first relationship between the first DAI and the N PDSCH groups includes the following expression manner:

[0089] A first representation: the first DAI corresponds to a first PDSCH group among the N PDSCH groups, or the first DAI corresponds to a fifth PDSCH group among the N PDSCH groups.

[0090] In a second expression, the first DAI corresponds to the N PDSCH groups.

[0091] A third representation: the first DAI does not correspond to any PDSCH group among the N PDSCH groups.

[0092] In this embodiment, the specific embodiment of determining the second DAI corresponding to each PDSCH group among the N PDSCH groups based on the first relationship described above is related to a specific expression method of the first relationship between the first DAI and the N PDSCH groups. Therefore, the following describes the specific embodiment of determining the first relationship and the second DAI corresponding to each PDSCH group among the N PDSCH groups for the above three types of expression methods.

[0093] For the first expression method above Optionally, when the first DAI corresponds to the first PDSCH group, determining a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the first relationship as described above includes: determining the first DAI as a second DAI corresponding to the first PDSCH group; determining a third DAI as a second DAI corresponding to the second PDSCH group; Among them, the third DAI is a DAI in a DCI corresponding to a second PDSCH group last detected by the terminal, and the second PDSCH group is any one of the N PDSCH groups other than the first PDSCH group.

[0094] For ease of understanding, an example description is given below.

[0095] Suppose the N PDSCH groups include PDSCH group 0 and PDSCH group 1, PDSCH group 0 is the first PDSCH group, and PDSCH group 1 is the second PDSCH group.

[0096] For PDSCH group 0, the corresponding second DAI is the first DAI, and for PDSCH group 1, the corresponding second DAI is the DAI in the DCI corresponding to the PDSCH group last detected by the terminal, where the DCI corresponding to the PDSCH group means that the PDSCH scheduled by this DCI belongs to this PDSCH group.

[0097] When the first DAI corresponds to a fifth PDSCH group among the N PDSCH groups, optionally, determining a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the first relationship as described above, determining the first DAI as a second DAI corresponding to the fifth PDSCH group; determining an eighth DAI as a second DAI corresponding to the sixth PDSCH group; Among them, the eighth DAI is a DAI in a DCI corresponding to a sixth PDSCH group last detected by the terminal, and the sixth PDSCH group is any one of the N PDSCH groups other than the fifth PDSCH group.

[0098] In this case, the implementation principle of determining the second DAI corresponding to each PDSCH group among the N PDSCH groups based on the first relationship described above is the same as the implementation principle of determining the second DAI corresponding to each PDSCH group among the N PDSCH groups based on the first relationship described above when the first DAI corresponds to the first PDSCH group, and for details, please refer to the description above. No further description will be given here.

[0099] For the second expression method above Optionally, determining a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the first relationship as described above may include: Obtaining a fourth DAI in a second DCI corresponding to each PDSCH group among the N PDSCH groups, where the second DCI corresponding to each PDSCH group is the DCI corresponding to this PDSCH group that was last detected by the terminal; comparing a first value with the first DAI value to obtain a corresponding comparison result, wherein the first value is determined based on a sum of the obtained N fourth DAI values; and determining a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the comparison result.

[0100] When specifically implemented, in a first implementation manner, the first value may be a sum of the obtained N fourth DAIs.

[0101] In a second implementation, the first value may be a value obtained after performing a modulo operation on the sum of the obtained N fourth DAIs. If the fourth DAIs corresponding to the PDSCH packets in the N PDSCHs are DAI1, DAI2, ..., DAIN, respectively, the first value DAI_Sum may be calculated by the following formula:

[0102]

number

[0103] In a second representation, the first DAI corresponds to the N PDSCH groups, so that the first DAI corresponds to a sum of the obtained N fourth DAIs, and the terminal can compare the first DAI with the first value to obtain a comparison result, and then determine a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the comparison result.

[0104] The comparison result may be used to determine whether or not there is a DCI for scheduling PDSCHs of the N PDSCH groups in the terminal.

[0105] Specifically, if the comparison result is that the first value is equal to the first DAI, the terminal may determine that the terminal does not miss checking DCI for scheduling PDSCHs of the N PDSCH groups. If there is no missing checking, the terminal may determine a DAI in the last detected DCI corresponding to each PDSCH group among the N PDSCH groups as a second DAI corresponding to the PDSCH group.

[0106] If the comparison result is that the first value is not equal to the first DAI, the terminal may determine that the terminal has missed checking DCI for scheduling PDSCHs of the N PDSCH groups. If there is a missed check, the terminal may determine a second DAI corresponding to each PDSCH group among the N PDSCH groups in the following manner:

[0107] Optionally, the step of determining a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the comparison result as described above may further include: determining a fifth DAI, the fifth DAI being used to indicate a number of DCIs for scheduling PDSCHs of the N PDSCH groups that have not been checked; and determining a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the fifth DAI.

[0108] When specifically implemented, the fifth DAI may be determined based on the first value and a difference between the first DAI, where the first value is denoted as DAI_Sum, the difference between the first DAI is denoted as UL_DAI, and the fifth DAI is denoted as DAI_Diff, and optionally, DAI_Diff may be calculated according to the following formula:

[0109]

number

[0110] In this embodiment, the specific implementation manner of determining the second DAI corresponding to each PDSCH group among the N PDSCH groups according to the above-mentioned fifth DAI is related to whether the terminal turns on CBG-based HARQ transmission. In this embodiment, if a parameter PDSCH-CodeBlockGroupTransmission is configured in any serving cell of the terminal, it can be considered that the terminal turns on CBG-based HARQ transmission.

[0111] The following describes scene 1 in which the terminal does not turn on HARQ transmission based on CBG, and scene 2 in which the terminal turns on HARQ transmission based on CBG.

[0112] For a first scenario, optionally, determining a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the fifth DAI as described above; When the fifth DAI corresponds to a third PDSCH group among the N PDSCH groups, determining a second DAI corresponding to the third PDSCH group based on the fifth DAI and a sixth DAI, and determining a seventh DAI as the second DAI corresponding to a fourth PDSCH group; if the fifth DAI does not correspond to any of the N PDSCH groups, determining a DAI in the last detected DCI corresponding to each PDSCH group among the N PDSCH groups as a second DAI corresponding to the PDSCH group; Among them, the sixth DAI is a DAI in a DCI corresponding to the third PDSCH group last detected by the terminal, the seventh DAI is a DAI in a DCI corresponding to the fourth PDSCH group last detected by the terminal, the third PDSCH group is any one PDSCH group among the N PDSCH groups, and the fourth PDSCH group is any one PDSCH group other than the third PDSCH group among the N PDSCH groups.

[0113] It can be seen that in this embodiment, for scene 1, the terminal further needs to determine a second DAI corresponding to each PDSCH group among the N PDSCH groups based on a second relationship between the fifth DAI and the N PDSCH groups.

[0114] If the second relationship is that the fifth DAI corresponds to the third PDSCH group, the second DAI corresponding to the third PDSCH group is determined based on the fifth DAI and the sixth DCI. Specifically, the second DAI corresponding to the third PDSCH group may be obtained by adding the fifth DAI and the sixth DCI. Optionally, the added sum may be further moduloed to obtain the second DAI corresponding to the third PDSCH group. The second DAI corresponding to the fourth PDSCH group may be the DAI in the DCI corresponding to the fourth PDSCH group last detected by the terminal.

[0115] Furthermore, the HARQ-ACK bit sequence of the third PDSCH group includes a first bit sequence and a second bit sequence that are cascaded in sequence; Wherein, the first bit sequence is determined based on the sixth DAI, and the second bit sequence is determined based on the fifth DAI.

[0116] When specifically implemented, in the HARQ-ACK bit sequence of the third PDSCH group, the second bit sequence may be located after the first bit sequence.

[0117] It should be noted that in this embodiment, the method of determining the bit sequence based on the DAI is the same as the "method of determining the HARQ-ACK bit sequence corresponding to each DAI" in the above part, and specifically, refer to the above description. No further description will be given here. It should be noted that, since the dynamic codebook in this embodiment is transmitted on the PUSCH, it is necessary to replace the parameter harq-ACK-SpatialBundlingPUCCH with harq-ACK-SpatialBundlingPUSCH.

[0118] When there is a check omission in a terminal, the HARQ-ACK codebook for each PDSCH group is determined by the above method, so that the terminal and the network side equipment can understand the size of the dynamic codebook, and further, the network side equipment can successfully acquire the dynamic codebook, thereby improving the reliability of data transmission.

[0119] Optionally, the second bit sequence comprises: If a first condition is satisfied, the number of bits included in the second bit sequence is twice the value of the fifth DAI, and the bits of the second bit sequence are set in a negative acknowledgement NACK; If the first condition is not satisfied, the number of bits included in the second bit sequence is equal to the fifth DAI, and the bits of the second bit sequence are set to a NACK; Wherein, the first condition includes that the terminal turns on HARQ-ACK spatial bundling indication, and one PDSCH reception corresponds to at most two transport blocks.

[0120] In specific implementation, if the harq-ACK-SpatialBundlingPUSCH parameter is not configured in the terminal, it can be regarded that the terminal turns on the HARQ-ACK spatial bundling indication.

[0121] The maxNrofCodeWordsScheduledByDCI parameter can be configured such that one PDSCH reception corresponds to at most two transport blocks for at least one DL BWP of at least one serving cell of the terminal.

[0122] In this embodiment, if a bit is set to Negative Acknowledgement (NACK), the value of this bit can be set to "0".

[0123] When the second relationship is that the fifth DAI does not correspond to any of the N PDSCH groups, for each PDSCH group among the N PDSCH groups, the corresponding second DAI may be a DAI in a DCI corresponding to this PDSCH group that was last detected by the terminal.

[0124] For scene 2, optionally, determining a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the fifth DAI as described above, When the fifth DAI corresponds to a third PDSCH group among the N PDSCH groups, determining a second DAI corresponding to the third PDSCH group according to the first sub-DAI, the second sub-DAI, the third sub-DAI and the fourth sub-DAI, and determining a seventh DAI as the second DAI corresponding to the fourth PDSCH group; if the fifth DAI does not correspond to any of the N PDSCH groups, determining a DAI in the last detected DCI corresponding to each PDSCH group among the N PDSCH groups as a second DAI corresponding to the PDSCH group; Wherein, the fifth DAI includes the first sub-DAI corresponding to transmission block TB granularity and the second sub-DAI corresponding to CBG granularity, the third sub-DAI is a DAI in a first type DCI corresponding to the third PDSCH group last detected by the terminal, the fourth sub-DAI is a DAI in a second type DCI corresponding to the third PDSCH group last detected by the terminal, the seventh DAI is a DAI in a DCI corresponding to the fourth PDSCH group last detected by the terminal, a PDSCH scheduled by the first type DCI feeds back a HARQ-ACK based on TB granularity, a PDSCH scheduled by the second type DCI feeds back a HARQ-ACK based on CBG granularity, the third PDSCH group is any one PDSCH group among the N PDSCH groups, and the fourth PDSCH group is any one PDSCH group other than the third PDSCH group among the N PDSCH groups.

[0125] In scene 2, for a terminal to turn on HARQ transmission based on CBG, the DCI for scheduling PDSCHs of the N PDSCH groups may include a first type DCI and a second type DCI, where for a PDSCH scheduled by the first type DCI, it feeds back HARQ-ACK based on TB granularity, and for a PDSCH scheduled by the second type DCI, it feeds back HARQ-ACK based on TB granularity.

[0126] As can be seen from the above content, the fifth DAI is used to indicate the number of DCIs for scheduling the PDSCHs of the N PDSCH groups that have not been checked. Therefore, the fifth DAI includes a first sub-DAI corresponding to a transport block TB granularity and a second sub-DAI corresponding to a CBG granularity, in which the first sub-DAI may be used to indicate the number of first-type DCIs for scheduling the PDSCHs of the N PDSCH groups that have not been checked, and the second sub-DAI may be used to indicate the number of second-type DCIs for scheduling the PDSCHs of the N PDSCH groups that have not been checked.

[0127] For scene two, the terminal further needs to determine a second DAI corresponding to each PDSCH group among the N PDSCH groups based on a second relationship between the fifth DAI and the N PDSCH groups.

[0128] If the second relationship is that the fifth DAI corresponds to the third PDSCH group, the second DAI corresponding to the third PDSCH group is determined based on a first sub-DAI, a second sub-DAI, a third sub-DAI, and a fourth sub-DAI. Specifically, the second DAI corresponding to the third PDSCH group may be cascaded by the first sub-DAI, the second sub-DAI, the third sub-DAI, and a fourth sub-DAI. The second DAI corresponding to the fourth PDSCH group may be a DAI in a DCI corresponding to the fourth PDSCH group that is last detected by the terminal.

[0129] Furthermore, the HARQ-ACK bit sequence of the third PDSCH group includes a third bit sequence, a fourth bit sequence, a fifth bit sequence, and a sixth bit sequence, which are cascaded in sequence; Among them, the third bit sequence is determined based on the third sub-DAI, the fourth bit sequence is determined based on the first sub-DAI, the fifth bit sequence is determined based on the fourth sub-DAI, and the sixth bit sequence is determined based on the second sub-DAI.

[0130] When specifically implemented, in the HARQ-ACK bit sequence of the third PDSCH group, the third bit sequence and the fourth bit sequence may be consecutive, and the fourth bit sequence may be located after the third bit sequence, and the fifth bit sequence and the sixth bit sequence may be consecutive, and the sixth bit sequence may be located after the fifth bit sequence. Also, for the first combined bit sequence of the third bit sequence and the fourth bit sequence, and the second combined bit sequence of the fifth bit sequence and the sixth bit sequence, in the HARQ-ACK bit sequence of the third PDSCH group, the first combined bit sequence may be located after the second combined bit sequence, or may be located before the second combined bit sequence. Specifically, it may be set according to actual needs. The embodiment of the present application is not limited thereto.

[0131] When there is a check omission in a terminal, the HARQ-ACK codebook for each PDSCH group is determined by the above method, so that the terminal and the network side equipment can understand the size of the dynamic codebook, and further, the network side equipment can successfully acquire the dynamic codebook, thereby improving the reliability of data transmission.

[0132] Optionally, the fourth bit sequence comprises: If a first condition is satisfied, the number of bits included in the fourth bit sequence is twice the value of the first sub-DAI, and the bits of the fourth bit sequence are set in a negative acknowledgement NACK; If the first condition is not satisfied, the number of bits included in the fourth bit sequence is equal to the first sub-DAI value, and the bits of the fourth bit sequence are set to a NACK; Wherein, the first condition includes that the terminal turns on HARQ-ACK spatial bundling indication, and one PDSCH reception corresponds to at most two transport blocks.

[0133] Optionally, the sixth bit sequence comprises: The number of bits included in the sixth bit sequence is equal to the product of the second sub-DAI value and the fourth value, and the bits of the sixth bit sequence are set to NACK; Among them, the fourth value is determined based on the maximum number of transport blocks that can be scheduled by a single DCI and the maximum number of CBGs that can be divided by a single transport block.

[0134] When specifically implemented, the fourth value is: It could also be TIFF0007671934000017.tif6161. For the specific meaning of TIFF0007671934000018.tif6161, please refer to the above description, and no further explanation will be given here.

[0135] When the second relationship is that the fifth DAI does not correspond to any PDSCH group among the N PDSCH groups, for each PDSCH group among the N PDSCH groups, the corresponding second DAI may be a DAI in a DCI corresponding to this PDSCH group that was last detected by the terminal.

[0136] For the above-mentioned scene 1 and scene 2, when the fifth DAI does not correspond to any of the N PDSCH groups, selectively generating a dynamic codebook to be transmitted on the first PUSCH based on the above-mentioned determined N second DAIs; generating a dynamic codebook to be transmitted on the first PUSCH based on the fifth DAI and the determined N second DAIs.

[0137] Optionally, the step of generating a dynamic codebook to be transmitted on the first PUSCH based on the fifth DAI and the determined N second DAIs may include: generating a target bit sequence based on the fifth DAI.

[0138] When specifically implemented, the terminal may generate a target bit sequence according to the fifth DAI, and then add the target bit sequence to the dynamic codebook, that is, in this case, the dynamic codebook includes the HARQ-ACK bit sequences of the N PDSCH groups and the target bit sequence.

[0139] In this way, the terminal and the network side device can understand the size of the dynamic codebook, and the network side device can successfully acquire the dynamic codebook, thereby improving the reliability of data transmission.

[0140] When specifically implemented, optionally, the target bit sequence is: If the terminal does not turn on HARQ transmission based on CBG, the number of bits included in the target bit sequence is equal to the product of the fifth DAI and a second value, and the bits in the target bit sequence are set to NACK; When the terminal turns on HARQ transmission based on CBG, the fifth DAI may include a third sub-DAI corresponding to TB granularity and a fourth sub-DAI corresponding to CBG granularity, the number of bits included in the target bit sequence is equal to the sum of a first target value and a second target value, the first target value is equal to the product of a value of the third sub-DAI and a second value, the second target value is equal to the product of a value of the fourth sub-DAI and a third value, and a bit in the target bit sequence is set to NACK.

[0141] Furthermore, the second value is if the first condition is satisfied, the second value has a value of 2; if the first condition is not satisfied, the second value is 1; Wherein, the first condition includes that the terminal turns on HARQ-ACK spatial bundling indication, and one PDSCH reception corresponds to at most two transport blocks.

[0142] Furthermore, the third value is determined based on the maximum number of transport blocks that can be scheduled by a single DCI and the maximum number of CBGs that can be divided by a single transport block.

[0143] When concretely realized, the third value is: It could also be TIFF0007671934000019.tif6161. For the specific meaning of TIFF0007671934000020.tif6161, please refer to the above description, and no further explanation will be given here.

[0144] For the above scene 1 and scene 2, optionally, the third PDSCH group: The third PDSCH group is a PDSCH group in which a PDSCH scheduled by a target DCI is located, and the target DCI is a DCI for scheduling a PDSCH in the N PDSCH groups that is last detected by the terminal; the third PDSCH group is agreed upon by a protocol; the third PDSCH group is configured by a network side device.

[0145] For the third implementation method above Optionally, determining a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the first relationship as described above may include: determining a DAI in a last detected DCI corresponding to each PDSCH group among the N PDSCH groups as a second DAI corresponding to the PDSCH group.

[0146] In this embodiment, when the first value in the above first implementation method, third implementation method, and second implementation method is equal to the first DAI, the terminal determines the second DAI corresponding to each PDSCH group among the N physical downlink shared channel PDSCH groups, and then determines the HARQ-ACK sequence of each PDSCH group among the N PDSCH groups based on the determined N second DAIs. The method is the same as the "method of determining HARQ-ACK bit sequence corresponding to each DAI" in the above part, and specifically, refer to the above description. No further description will be given here. In addition, since the dynamic codebook of this embodiment is transmitted on PUSCH, it is necessary to replace the parameter harq-ACK-Spatial Bundling PUCCH with harq-ACK-Spatial Bundling PUSCH.

[0147] In addition, in this embodiment, when the terminal configures only a single serving cell, the DAI in the DCI corresponding to a certain PDSCH group last detected by the terminal is C-DAI, and when the terminal configures two or more serving cells, the DAI in the DCI corresponding to a certain PDSCH group last detected by the terminal is T-DAI.

[0148] Please refer to Figure 3, which is a flow chart of a method for generating a HARQ-ACK codebook according to an embodiment of the present application. The information transmission method of the embodiment of the present application is used in a network side device.

[0149] As shown in FIG. 3, the information transmission method may include the following steps.

[0150] Step 301: sending first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI including a first DAI, the first DAI being used to generate a dynamic codebook transmitted on the first PUSCH, in which the dynamic codebook includes HARQ-ACK bit sequences of the N physical downlink shared channel (PDSCH) groups, where N is a positive integer.

[0151] Optionally, the first DAI corresponds to at least one PDSCH group among N PDSCH groups.

[0152] Alternatively, if N is greater than 1, the first DAI corresponds to the N PDSCH groups, or the first DAI corresponds to a first PDSCH group among the N PDSCH groups.

[0153] Optionally, if the first DAI corresponds to the N PDSCH groups, the first DAI is determined based on a sum of N ninth DAIs; Among them, each PDSCH group among the N PDSCH groups corresponds to one of the ninth DAI, and each of the ninth DAIs is attached to a third DCI corresponding to the corresponding PDSCH group, and the third DCI corresponding to each PDSCH group is the DCI corresponding to this PDSCH group that was last transmitted by the network side device.

[0154] When specifically implemented, in one implementation, the first DAI value may be a sum of N ninth DAI values, while in another implementation, the first DAI value is obtained by performing a modulo operation on the sum of N ninth DAI values.

[0155] Optionally, the first DAI does not correspond to any PDSCH group among the N PDSCH groups.

[0156] In this case, the first DAI may be set to any value or may be set to a default value, for example 4.

[0157] In the information transmission method of this embodiment, a network side device transmits a first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI includes a first DAI, and the first DAI is used to generate a dynamic codebook transmitted on the first PUSCH, where the dynamic codebook includes HARQ-ACK bit sequences of the N physical downlink shared channel (PDSCH) groups, where N is a positive integer. In this way, after receiving the first DAI, the terminal can generate a dynamic codebook according to the first DAI, thereby improving the reliability of dynamic codebook transmission.

[0158] It should be noted that this embodiment is an embodiment of a network side device corresponding to the above method embodiment, so that the relevant description in the above method embodiment can be referred to, and the same beneficial effects can be achieved. In order to avoid repetition, no further description will be given here.

[0159] In addition, the multiple optional embodiments introduced in the examples of the present application may be realized in combination with each other or alone, and the examples of the present application are not limited thereto.

[0160] For ease of understanding, an example description is given below.

[0161] In the embodiment of the present application, when a downlink extended dynamic codebook is configured for a UE, and only a single or single group of UL DAI exists in uplink DCI format 0_1, the meaning and application of the UL DAI may adopt one of the following approaches:

[0162] Solution 1: Determine the meaning of the UL DAI value in DCI format 0_1 ​​(i.e., the value in the "1st downlink assignment index" domain and / or the "2nd downlink assignment index" domain in DCI format 0_1) based on the number of trigger PDSCH packets corresponding to the extended dynamic codebook that need to be overlapped in the time domain with and loaded on the PUSCH scheduled by DCI format 0_1. The following operations may be adopted:

[0163] When the extended dynamic codebook only corresponds to a single triggering PDSCH packet, the UL DAI value corresponds to this triggered single PDSCH packet, and the determination of the corresponding HARQ-ACK bit may adopt operation 2, see the following description.

[0164] If the extended dynamic codebook supports more than one trigger PDSCH packet, one of the following methods is adopted.

[0165] The UL DAI value corresponds to the sum of the DAIs of all triggered PDSCH packets (and takes modulo arithmetic into account) or the dynamically scheduled PDSCH reception / SPS PDSCH release indication number (and takes modulo arithmetic into account) corresponding to the extended dynamic codebook carried on the PUSCH.

[0166] Wherein, the DAI value or the corresponding HARQ-ACK bit applied to each PDSCH packet may be determined by using operation 1.

[0167] The UL DAI value corresponds to the most recently scheduled PDSCH packet before the extended dynamic codebook is transmitted, and the determination of the corresponding HARQ-ACK bit may adopt operation 2, see the following description.

[0168] The UL DAI value corresponds to a certain PDSCH packet, for example the first set or the second set, that is defined by the protocol or configured by the higher layer parameters, and the determination of the corresponding HARQ-ACK bit may adopt operation 2.

[0169] Method 2: The UL DAI in DCI format 0_1 ​​is fixedly used for a single PDSCH packet, and regardless of whether the number of PDSCH packets carried on the scheduled PUSCH is greater than 1, one of the following methods may be adopted.

[0170] The UL DAI value corresponds to a certain PDSCH packet, for example the first set or the second set, that is defined by the protocol or configured by the higher layer parameters, and the determination of the corresponding HARQ-ACK bit may adopt operation 2.

[0171] The UL DAI value corresponds to the most recently scheduled PDSCH packet before the extended dynamic codebook is transmitted, and the determination of the corresponding HARQ-ACK bit may adopt operation 2.

[0172] The above methods 1 and 2 may be completely consistent in actual operations in some cases, and only differ in the assumptions. One method distinguishes the number of PDSCH packets corresponding to the extended dynamic codebook and processes them separately, and the other method does not distinguish the number of PDSCH packets.

[0173] The above operations 1 and 2 will be explained below.

[0174] Operation 1: When the UL DAI in DCI format 0_1 ​​indicates the sum of the DAIs of more than one trigger PDSCH packet, or indicates the number of dynamically scheduled PDSCH reception / SPS PDSCH release indications corresponding to the extended dynamic codebook, the following scheme may be adopted to determine the DAI value or corresponding HARQ-ACK bit applied to each PDSCH packet.

[0175] First step: If the most recent downlink scheduling DCI of each trigger PDSCH packet is DCI format 1_0, then C-DAI in this DCI format 1_0. If the most recent downlink scheduling DCI is DCI format 1_1, then T-DAI in this DCI format 1_1, and calculate the relationship between the sum of C-DAI / T-DAI (and considering modulo operation) of each PDSCH packet and UL DAI. If they are equal, it is considered that there is no DCI check failure, and then execute the second step; otherwise, it is considered that there is DCI check failure in a certain PDSCH packet, and then execute the third step. If the extended dynamic codebook corresponds to N PDSCH packets, then the DAI of each PDSCH packet is DAI1, DAI2, ... DAIN, respectively, the above-mentioned calculation of the sum of C-DAI / T-DAI (and considering modulo operation) DAI_Sum of each PDSCH packet is as follows:

number

[0176] Step 2: Determine the number of HARQ-ACK bit sequences and the corresponding value for each trigger PDSCH packet based on the C-DAI / T-DAI in the most recent downlink scheduling DCI format 1_0 / 1_1 of this PDSCH packet. The operation flow for configuring the HARQ-ACK Codebook when it is loaded onto the PUCCH (regardless of the use of UL DAI) can be used as is, but the parameter harq-ACK-SpatialBundlingPUCCH is replaced by harq-ACK-SpatialBundlingPUSCH.

[0177] Step 3: Calculate the DAI difference, where the sum of C-DAI / T-DAI of each PDSCH packet (and considering modulo operation) is DAI_Sum, and the UL DAI value in DCI format 0_1 ​​is UL_DAI, then the DAI difference DAI_Diff=(UL_DAI-DAI_Sum-1) mod Round_Size+1. DAI_Diff may be understood as the number of DCIs that have not been checked, and according to different targets applied thereto, one of the following methods may be adopted:

[0178] Scheme 1: DAI_Diff is used for certain PDSCH packets, eg, first set or second set, as defined by the protocol or configured by higher layer parameters.

[0179] Scheme 2: DAI_Diff is used for PDSCH packets whose HARQ-ACK bit sequence is placed at the very end of the extended dynamic codebook, and in this way, at least other HARQ-ACK bits than the last ones of PDSCH packets whose HARQ-ACK bit sequence is placed at the very beginning of the extended dynamic codebook are not affected by DCI check omissions.

[0180] Scheme 3: DAI_Diff is used for the most recently scheduled PDSCH packet before the extended dynamic codebook is transmitted.

[0181] Method 4: DAI_Diff is not used for any PDSCH packet, but is only used to align the size of HARQ-ACK Codebook on both sides of UE and eNB, to avoid affecting RE demapping and decoding of UL-SCH.

[0182] For the above-mentioned methods 1, 2 and 3, after determining the PDSCH packet to be applied to DAI_Diff, the HARQ-ACK bit sequence of this PDSCH packet is determined based on the NR Rel-15 flow (at this time, each PDSCH packet only uses the DAI value indicated in the DCI when determining the HARQ-ACK bit sequence, but does not use the UL DAI value), and then applies DAI_Diff to the end of the determined HARQ-ACK bit sequence, and the following operations may be adopted when applying DAI_Diff.

[0183] If the harq-ACK-SpatialBundlingPUSCH parameter is not configured for the UE, and one PDSCH reception is configured to correspond to at most two transmission blocks for at least one DL BWP of at least one serving cell of the UE according to the maxNrofCodeWordsScheduledByCI parameter, each lost DAI corresponds to two HARQ-ACK bits, and in this case, DAI_Diff×2 bits with a value of "0" are added to the end of the determined HARQ-ACK bit sequence, corresponding to DAI_Diff×2 NACKs.

[0184] Otherwise, each lost DAI corresponds to a single HARQ-ACK bit, and in this case, DAI_Diff bits with a value of "0" are added to the end of the determined HARQ-ACK bit sequence, corresponding to DAI_Diff NACKs.

[0185] The above DAI_Diff application operation is applied when none of the serving cells of the UE has CBG-based HARQ transmission turned on.

[0186] When a parameter PDSCH-CodeBlockGroupTransmission is configured in a serving cell of a UE, that is, when HARQ transmission based on CBG is turned on, the HARQ-ACK Codebook of a single PDSCH packet is cascaded with two HARQ-ACK sub-codebooks, in which the first sub-codebook performs HARQ-ACK feedback to TB, and the second sub-codebook performs HARQ-ACK feedback to CBG. At this time, the above operation is applied to the sub-codebook at TB level, and the following operation may be adopted when applying DAI_Diff to the sub-codebook at CBG level.

[0187] At the end of the HARQ-ACK bit sequence determined above

number

number

[0188] In the above method 4, firstly, determine the HARQ-ACK bit sequence of each trigger PDSCH packet (at this time, each PDSCH packet only uses the DAI value indicated by the DCI when determining the HARQ-ACK bit sequence, but does not use the UL DAI value), then determine a complete HARQ-ACK Codebook according to the HARQ-ACK bit sequence of each trigger PDSCH packet (for example, cascade the HARQ-ACK bit sequences of each trigger PDSCH packet in ascending order of group number to obtain a complete HARQ-ACK Codebook), and finally adopt one of the following operations to add aligned bits to the end of the HARQ-ACK Codebook:

[0189] If a single trigger PDSCH packet is only related to TB level feedback (i.e., none of the serving cells of the UE have the parameter PDSCH-CodeBlockGroupTransmission configured to turn on CBG-based HARQ transmission), then DAI_DiffTB × Bit_Num_Per_DAITB bits with a value of "0" are added to the end of the HARQ-ACK Codebook, each bit corresponding to a single NACK, where DAI_DiffTB is the DAI_Diff calculated based on the UL DAI in DCI format 0_1, and Bit_Num_Per_DAITB is the number of HARQ-ACK bits corresponding to each DAI, where Bit_Num_Per_DAITB is the TB granularity.

[0190] If the single trigger PDSCH packet is related to CBG-level feedback (i.e., at least one serving cell of the UE is configured with the parameter PDSCH-CodeBlockGroupTransmission to turn on CBG-based HARQ transmission), first, add DAI_DiffTB×Bit_Num_Per_DAITB bits with a value of 0 to the end of the HARQ-ACK Codebook, each bit corresponding to a single NACK, where DAI_DiffTB is the DAI_Diff calculated based on the first UL DAI in DCI format 0_1 ​​(indicated by the “1st downlink assignment index” domain), and Bit_Num_Per_DAITB is the number of HARQ-ACK bits corresponding to each DAI, which is the TB granularity; then, add DAI_DiffCBG×Bit_Num_Per_DAICBG bits with a value of 0 to the end of the HARQ-ACK Codebook, each bit corresponding to a single NACK, where DAI_DiffCBG is the DAI_Diff calculated based on the first UL DAI in DCI format 0_1 ​​(indicated by the “1st downlink assignment index” domain). 0_1, and Bit_Num_Per_DAICBG is the number of HARQ-ACK bits corresponding to each DAI, which is the CBG granularity.

[0191] The Bit_Num_Per_DAITB may be determined based on the following method.

[0192] If the harq-ACK-SpatialBundlingPUSCH parameter is not configured for the UE and the max Nr of Code Words Scheduled ByDCI parameter is configured for at least one DL BWP of at least one serving cell of the UE such that one PDSCH reception corresponds to at most two transport blocks, then the Bit_Num_Per_DAITB value shall be 2; otherwise, the Bit_Num_Per_DAITB value shall be 1.

[0193] The Bit_Num_Per_DAICBG may be determined based on the following method.

[0194] Bit_Num_Per_DAICBG takes the following values: TIFF0007671934000031.tif6161, For the meaning of TIFF0007671934000032.tif6161, please refer to the description above.

[0195] Operation 2: If the UL DAI value corresponds to a single PDSCH packet, the operation flow for configuring the HARQ-ACK Codebook when it is carried on the PUCCH can be used directly to determine the HARQ-ACK bit sequence corresponding to this PDSCH packet.

[0196] If the codebook of each trigger PDSCH packet corresponds to two sub-codebooks, DCI format 0_1 ​​according to NR Rel-15 includes two UL DAI values, which correspond to the first sub-codebook and the second sub-codebook, respectively. The above scheme and related methods can be applied to each sub-codebook respectively.

[0197] As shown in Figure 4, the N PDSCH groups include PDSCH group 0 and PDSCH group 1. PDSCH group 0 includes two PDSCHs, D1 and D2, respectively, and the UE detects only D1 but does not detect D2. PDSCH group 1 includes four PDSCHs, D3, D4, D5, and D6, respectively, and the UE detects only D3, D4, and D5, but does not detect D6.

[0198] In Figure 4, UCI1 transmission fails. The PUCCH carrying UCI2 overlaps with the PUSCH in the time domain, and UCI2 is multiplexed on the PUSCH for transmission. The DCI located after D6 is used to schedule the PUSCH, and this DCI can indicate the UL DAI.

[0199] In an embodiment of the present application, the terminal can determine a second DAI corresponding to D1, D2, D3, D4, D5 and D6 respectively based on the UL DAI, further determine HARQ-ACK sequences for D1, D2, D3, D4, D5 and D6 based on the second DAI, further generate a dynamic codebook, and transmit the dynamic codebook on a PUSCH.

[0200] In the embodiment of the present application, a downlink extended dynamic codebook is configured for the UE, and when there is only a single or single group of UL DAI in the uplink DCI format 0_1, a corresponding solution is proposed for the application of the UL DAI, which ensures reliable transmission of the HARQ-ACK Codebook and does not affect other data transmission carried on the PUSCH.

[0201] Please refer to FIG. 5, which is a structural diagram of a terminal according to an embodiment of the present application. As shown in FIG. 5, the terminal 500 includes: A receiving module 501 for receiving first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI including a first DAI; A determining module 502 for determining a second DAI corresponding to each PDSCH group among the N physical downlink shared channel (PDSCH) groups according to the first DAI; and a generating module 503 for generating a dynamic codebook to be transmitted on the first PUSCH based on the determined N second DAIs; Wherein, the dynamic codebook includes HARQ-ACK bit sequences of the N PDSCH groups, where N is a positive integer.

[0202] Optionally, the decision module further comprises: a first determination sub-module for determining a first relationship between the first DAI and N PDSCH groups; and a second determining sub-module for determining a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the first relationship.

[0203] Optionally, the first relationship satisfies that the first DAI corresponds to at least one PDSCH group among the N PDSCH groups.

[0204] Optionally, when N is greater than 1, the first relationship is: The first DAI corresponds to the N PDSCH groups; the first DAI corresponds to a first PDSCH group among the N PDSCH groups; The first PDSCH group The first PDSCH group is a PDSCH group in which a PDSCH scheduled by a target DCI is located, and the target DCI is a DCI for scheduling a PDSCH in the N PDSCH groups that is last detected by the terminal; The first PDSCH group is determined by a protocol; the first PDSCH group is configured by a network side device.

[0205] Optionally, when the first DAI corresponds to the first PDSCH group, the second determining submodule specifically: determining the first DAI as a second DAI corresponding to the first PDSCH group; Used to determine a third DAI as a second DAI corresponding to a second PDSCH group; Among them, the third DAI is a DAI in a DCI corresponding to a second PDSCH group last detected by the terminal, and the second PDSCH group is any one of the N PDSCH groups other than the first PDSCH group.

[0206] Optionally, when the first DAI corresponds to the N PDSCH groups, the second determining sub-module is specifically used as follows:

[0207] The acquisition subunit is used to acquire a fourth DAI in a second DCI corresponding to each PDSCH group among the N PDSCH groups, and the second DCI corresponding to each PDSCH group is the DCI corresponding to this PDSCH group that was last detected by the terminal.

[0208] The comparison unit is used to compare a first value with the first DAI value to obtain a corresponding comparison result, and the first value is determined based on the sum of the obtained N fourth DAI values.

[0209] A determining unit is used for determining a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the comparison result.

[0210] Optionally, the determination unit is a first determination subunit for determining a fifth DAI if the first value is not equal to the first DAI, the fifth DAI being used to indicate a number of DCIs for scheduling PDSCHs of the N PDSCH groups that have not been checked; and a second determining subunit for determining, based on the fifth DAI, a second DAI corresponding to each PDSCH group among the N PDSCH groups.

[0211] Optionally, if the terminal does not turn on HARQ transmission based on code block group CBG, the second determining subunit specifically: When the fifth DAI corresponds to a third PDSCH group among the N PDSCH groups, determining a second DAI corresponding to the third PDSCH group based on the fifth DAI and a sixth DAI, and determining a seventh DAI as the second DAI corresponding to a fourth PDSCH group; if the fifth DAI does not correspond to any of the N PDSCH groups, determining a DAI in the last detected DCI corresponding to each PDSCH group among the N PDSCH groups as a second DAI corresponding to the PDSCH group; Among them, the sixth DAI is a DAI in a DCI corresponding to the third PDSCH group last detected by the terminal, the seventh DAI is a DAI in a DCI corresponding to the fourth PDSCH group last detected by the terminal, the third PDSCH group is any one PDSCH group among the N PDSCH groups, and the fourth PDSCH group is any one PDSCH group other than the third PDSCH group among the N PDSCH groups.

[0212] Optionally, the HARQ-ACK bit sequence of the third PDSCH group includes a first bit sequence and a second bit sequence that are cascaded in sequence; Wherein, the first bit sequence is determined based on the sixth DAI, and the second bit sequence is determined based on the fifth DAI.

[0213] Optionally, the second bit sequence comprises: If a first condition is satisfied, the number of bits included in the second bit sequence is twice the value of the fifth DAI, and the bits of the second bit sequence are set in a negative acknowledgement NACK; If the first condition is not satisfied, the number of bits included in the second bit sequence is equal to the fifth DAI, and the bits of the second bit sequence are set to a NACK; Wherein, the first condition includes that the terminal turns on HARQ-ACK spatial bundling indication, and one PDSCH reception corresponds to at most two transport blocks.

[0214] Optionally, when the terminal turns on HARQ transmission based on code block group CBG, the second determining subunit specifically: When the fifth DAI corresponds to a third PDSCH group among the N PDSCH groups, determining a second DAI corresponding to the third PDSCH group according to the first sub-DAI, the second sub-DAI, the third sub-DAI and the fourth sub-DAI, and determining a seventh DAI as the second DAI corresponding to the fourth PDSCH group; if the fifth DAI does not correspond to any of the N PDSCH groups, determining a DAI in the last detected DCI corresponding to each PDSCH group among the N PDSCH groups as a second DAI corresponding to the PDSCH group; Wherein, the fifth DAI includes the first sub-DAI corresponding to transmission block TB granularity and the second sub-DAI corresponding to CBG granularity, the third sub-DAI is a DAI in a first type DCI corresponding to the third PDSCH group last detected by the terminal, the fourth sub-DAI is a DAI in a second type DCI corresponding to the third PDSCH group last detected by the terminal, the seventh DAI is a DAI in a DCI corresponding to the fourth PDSCH group last detected by the terminal, a PDSCH scheduled by the first type DCI feeds back a HARQ-ACK based on TB granularity, a PDSCH scheduled by the second type DCI feeds back a HARQ-ACK based on CBG granularity, the third PDSCH group is any one PDSCH group among the N PDSCH groups, and the fourth PDSCH group is any one PDSCH group other than the third PDSCH group among the N PDSCH groups.

[0215] Optionally, the HARQ-ACK bit sequence of the third PDSCH group includes a third bit sequence, a fourth bit sequence, a fifth bit sequence, and a sixth bit sequence, which are cascaded in sequence; Among them, the third bit sequence is determined based on the third sub-DAI, the fourth bit sequence is determined based on the first sub-DAI, the fifth bit sequence is determined based on the fourth sub-DAI, and the sixth bit sequence is determined based on the second sub-DAI.

[0216] Optionally, the fourth bit sequence comprises: If a first condition is satisfied, the number of bits included in the fourth bit sequence is twice the value of the first sub-DAI, and the bits of the fourth bit sequence are set in a negative acknowledgement NACK; If the first condition is not satisfied, the number of bits included in the fourth bit sequence is equal to the first sub-DAI value, and the bits of the fourth bit sequence are set to a NACK; Wherein, the first condition includes that the terminal turns on HARQ-ACK spatial bundling indication, and one PDSCH reception corresponds to at most two transport blocks.

[0217] Optionally, the sixth bit sequence comprises: The number of bits included in the sixth bit sequence is equal to the product of the second sub-DAI value and the fourth value, and the bits of the sixth bit sequence are set to NACK; Among them, the fourth value is determined based on the maximum number of transport blocks that can be scheduled by a single DCI and the maximum number of CBGs that can be divided by a single transport block.

[0218] Optionally, the third PDSCH group comprises: The third PDSCH group is a PDSCH group in which a PDSCH scheduled by a target DCI is located, and the target DCI is a DCI for scheduling a PDSCH in the N PDSCH groups that is last detected by the terminal; the third PDSCH group is agreed upon by a protocol; the third PDSCH group is configured by a network side device.

[0219] Optionally, if the fifth DAI does not correspond to any of the N PDSCH groups, the generating module specifically: The fifth DAI is used to generate a dynamic codebook to be transmitted on the first PUSCH based on the fifth DAI and the determined N second DAIs.

[0220] Optionally, the generating module specifically: used to generate a target bit sequence based on the fifth DAI; Wherein, the target bit sequence is: If the terminal does not turn on HARQ transmission based on CBG, the number of bits included in the target bit sequence is equal to the product of the fifth DAI and a second value, and the bits in the target bit sequence are set to NACK; When the terminal turns on HARQ transmission based on CBG, the fifth DAI includes a third sub-DAI corresponding to TB granularity and a fourth sub-DAI corresponding to CBG granularity, the number of bits included in the target bit sequence is equal to the sum of a first target value and a second target value, the first target value is equal to the product of a value of the third sub-DAI and a second value, the second target value is equal to the product of a value of the fourth sub-DAI and a third value, and a bit in the target bit sequence is set to NACK.

[0221] Optionally, the second value is if the first condition is satisfied, the second value has a value of 2; if the first condition is not satisfied, the second value is 1; Wherein, the first condition includes that the terminal turns on HARQ-ACK spatial bundling indication, and one PDSCH reception corresponds to at most two transport blocks.

[0222] Optionally, the third value is determined based on the maximum number of transport blocks that can be scheduled by a single DCI and the maximum number of CBGs that can be divided by a single transport block.

[0223] Optionally, the step of determining a first relationship between the first DAI and the N PDSCH groups includes: determining a first relationship between the first DAI and N PDSCH groups based on a preset rule; Among them, the preset rules are: determining a PDSCH group corresponding to the first DAI according to a PDSCH group located and scheduled by a target DCI, the target DCI being a DCI for scheduling a PDSCH in the N PDSCH groups last detected by the terminal; determining a PDSCH group corresponding to the first DAI based on a protocol agreement; determining a PDSCH group corresponding to the first DAI based on configuration information of network side equipment.

[0224] Optionally, the first relationship is: The first DAI corresponds to a fifth PDSCH group among the N PDSCH groups, and the fifth PDSCH group is any one of the N PDSCH groups; The first DAI does not correspond to any of the N PDSCH groups.

[0225] Optionally, when the first DAI corresponds to a fifth PDSCH group among the N PDSCH groups, the second determining submodule specifically: determining the first DAI as a second DAI corresponding to the fifth PDSCH group; Used to determine an eighth DAI as a second DAI corresponding to a sixth PDSCH group; Among them, the eighth DAI is a DAI in a DCI corresponding to a sixth PDSCH group last detected by the terminal, and the sixth PDSCH group is any one of the N PDSCH groups other than the fifth PDSCH group.

[0226] The terminal 500 can implement each process that can be implemented by a terminal in the embodiment of the method of the present application and achieve the same beneficial effects. In order to avoid repetition of the description, it will not be described further here.

[0227] Referring to FIG. 6, FIG. 6 is a structural diagram of a network side device according to an embodiment of the present application. As shown in FIG. 6, the network side device 300 includes: The method includes: a transmitting module 601 for transmitting first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI including a first DAI, the first DAI being used to generate a dynamic codebook transmitted on the first PUSCH; Wherein, the dynamic codebook includes HARQ-ACK bit sequences of N PDSCH groups, where N is a positive integer.

[0228] Optionally, the first DAI corresponds to at least one PDSCH group among the N PDSCH groups.

[0229] Alternatively, if N is greater than 1, the first DAI corresponds to the N PDSCH groups, or the first DAI corresponds to a first PDSCH group among the N PDSCH groups.

[0230] Optionally, if the first DAI corresponds to the N PDSCH groups, the first DAI is determined based on a sum of N ninth DAIs; Among them, each PDSCH group among the N PDSCH groups corresponds to one of the ninth DAI, and each of the ninth DAIs is attached to a third DCI corresponding to the corresponding PDSCH group, and the third DCI corresponding to each PDSCH group is the DCI corresponding to this PDSCH group that was last transmitted by the network side device.

[0231] Optionally, the first DAI does not correspond to any PDSCH group among the N PDSCH groups.

[0232] The network side device 600 can realize each process that can be realized by the network side device in the embodiment of the method of the present application, and can achieve the same beneficial effects. In order to avoid repetition of the description, it will not be described further here.

[0233] Referring to FIG. 7, FIG. 7 is a second structural diagram of a terminal according to an embodiment of the present application. This terminal may be a hardware structural schematic diagram of a terminal implementing each embodiment of the present application. As shown in FIG. 7, the terminal 700 includes components such as, but not limited to, a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709, a processor 710, and a power supply 711. As can be understood by those skilled in the art, the terminal structure shown in FIG. 7 does not constitute a limitation on the terminal, and the terminal may include more or less components than the number of components shown, or any combination of components, or a different arrangement of components. In the embodiment of the present application, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a car-mounted terminal, a wearable device, and a pedometer.

[0234] Wherein, the radio frequency unit 701 is used for receiving first downlink control information DCI for scheduling a first physical uplink shared channel PUSCH, where the first DCI includes a first DAI.

[0235] The processor 710 is determining a second DAI corresponding to each PDSCH group among the N physical downlink shared channel (PDSCH) groups based on the first DAI; generating a dynamic codebook to be transmitted on the first PUSCH based on the determined N second DAIs; Wherein, the dynamic codebook includes HARQ-ACK bit sequences of the N PDSCH groups, where N is a positive integer.

[0236] Optionally, the processor 710 further comprises: determining a first relationship between the first DAI and N PDSCH groups; A second DAI corresponding to each PDSCH group among the N PDSCH groups is determined based on the first relationship.

[0237] Optionally, the first relationship satisfies that the first DAI corresponds to at least one PDSCH group among the N PDSCH groups.

[0238] Optionally, when N is greater than 1, the first relationship is: The first DAI corresponds to the N PDSCH groups; the first DAI corresponds to a first PDSCH group among the N PDSCH groups; The first PDSCH group The first PDSCH group is a PDSCH group in which a PDSCH scheduled by a target DCI is located, and the target DCI is a DCI for scheduling a PDSCH in the N PDSCH groups that is last detected by the terminal; The first PDSCH group is determined by a protocol; the first PDSCH group is configured by a network side device.

[0239] Optionally, if the first DAI corresponds to the first PDSCH group, the processor 710 further comprises: determining the first DAI as a second DAI corresponding to the first PDSCH group; Used to determine a third DAI as a second DAI corresponding to a second PDSCH group; Among them, the third DAI is a DAI in a DCI corresponding to a second PDSCH group last detected by the terminal, and the second PDSCH group is any one of the N PDSCH groups other than the first PDSCH group.

[0240] Optionally, if the first DAI corresponds to the N PDSCH groups, the processor 710 further comprises: Obtaining a fourth DAI in a second DCI corresponding to each PDSCH group among the N PDSCH groups, the second DCI corresponding to each PDSCH group being a DCI corresponding to the PDSCH group last detected by the terminal; comparing a first value with the first DAI value to obtain a corresponding comparison result, wherein the first value is determined based on a sum of the obtained N fourth DAI values; A second DAI corresponding to each PDSCH group among the N PDSCH groups is determined based on the comparison result.

[0241] Optionally, the processor 710 further comprises: determining a fifth DAI if the first value is not equal to the first DAI, the fifth DAI being used to indicate a number of DCIs for scheduling PDSCHs of the N PDSCH groups that have not been checked; A second DAI corresponding to each PDSCH group among the N PDSCH groups is determined based on the fifth DAI.

[0242] Optionally, if the terminal does not turn on HARQ transmission based on code block group CBG, the processor 710 further When the fifth DAI corresponds to a third PDSCH group among the N PDSCH groups, determining a second DAI corresponding to the third PDSCH group based on the fifth DAI and a sixth DAI, and determining a seventh DAI as the second DAI corresponding to a fourth PDSCH group; if the fifth DAI does not correspond to any of the N PDSCH groups, determining a DAI in the last detected DCI corresponding to each PDSCH group among the N PDSCH groups as a second DAI corresponding to the PDSCH group; Among them, the sixth DAI is a DAI in a DCI corresponding to the third PDSCH group last detected by the terminal, the seventh DAI is a DAI in a DCI corresponding to the fourth PDSCH group last detected by the terminal, the third PDSCH group is any one PDSCH group among the N PDSCH groups, and the fourth PDSCH group is any one PDSCH group other than the third PDSCH group among the N PDSCH groups.

[0243] Optionally, the HARQ-ACK bit sequence of the third PDSCH group includes a first bit sequence and a second bit sequence that are cascaded in sequence; Wherein, the first bit sequence is determined based on the sixth DAI, and the second bit sequence is determined based on the fifth DAI.

[0244] Optionally, the second bit sequence comprises: If a first condition is satisfied, the number of bits included in the second bit sequence is twice the value of the fifth DAI, and the bits of the second bit sequence are set in a negative acknowledgement NACK; If the first condition is not satisfied, the number of bits included in the second bit sequence is equal to the fifth DAI, and the bits of the second bit sequence are set to a NACK; Wherein, the first condition includes that the terminal turns on HARQ-ACK spatial bundling indication, and one PDSCH reception corresponds to at most two transport blocks.

[0245] Optionally, if the terminal turns on HARQ transmission based on code block group CBG, the processor 710 further comprises: When the fifth DAI corresponds to a third PDSCH group among the N PDSCH groups, determining a second DAI corresponding to the third PDSCH group according to the first sub-DAI, the second sub-DAI, the third sub-DAI and the fourth sub-DAI, and determining a seventh DAI as the second DAI corresponding to the fourth PDSCH group; if the fifth DAI does not correspond to any of the N PDSCH groups, determining a DAI in the last detected DCI corresponding to each PDSCH group among the N PDSCH groups as a second DAI corresponding to the PDSCH group; Wherein, the fifth DAI includes the first sub-DAI corresponding to transmission block TB granularity and the second sub-DAI corresponding to CBG granularity, the third sub-DAI is a DAI in a first type DCI corresponding to the third PDSCH group last detected by the terminal, the fourth sub-DAI is a DAI in a second type DCI corresponding to the third PDSCH group last detected by the terminal, the seventh DAI is a DAI in a DCI corresponding to the fourth PDSCH group last detected by the terminal, a PDSCH scheduled by the first type DCI feeds back a HARQ-ACK based on TB granularity, a PDSCH scheduled by the second type DCI feeds back a HARQ-ACK based on CBG granularity, the third PDSCH group is any one PDSCH group among the N PDSCH groups, and the fourth PDSCH group is any one PDSCH group other than the third PDSCH group among the N PDSCH groups.

[0246] Optionally, the HARQ-ACK bit sequence of the third PDSCH group includes a third bit sequence, a fourth bit sequence, a fifth bit sequence, and a sixth bit sequence, which are cascaded in sequence; Among them, the third bit sequence is determined based on the third sub-DAI, the fourth bit sequence is determined based on the first sub-DAI, the fifth bit sequence is determined based on the fourth sub-DAI, and the sixth bit sequence is determined based on the second sub-DAI.

[0247] Optionally, the fourth bit sequence comprises: If a first condition is satisfied, the number of bits included in the fourth bit sequence is twice the value of the first sub-DAI, and the bits of the fourth bit sequence are set in a negative acknowledgement NACK; If the first condition is not satisfied, the number of bits included in the fourth bit sequence is equal to the first sub-DAI value, and the bits of the fourth bit sequence are set to a NACK; Wherein, the first condition includes that the terminal turns on HARQ-ACK spatial bundling indication, and one PDSCH reception corresponds to at most two transport blocks.

[0248] Optionally, the sixth bit sequence comprises: The number of bits included in the sixth bit sequence is equal to the product of the second sub-DAI value and the fourth value, and the bits of the sixth bit sequence are set to NACK; Among them, the fourth value is determined based on the maximum number of transport blocks that can be scheduled by a single DCI and the maximum number of CBGs that can be divided by a single transport block.

[0249] Optionally, the third PDSCH group comprises: The third PDSCH group is a PDSCH group in which a PDSCH scheduled by a target DCI is located, and the target DCI is a DCI for scheduling a PDSCH in the N PDSCH groups that is last detected by the terminal; the third PDSCH group is agreed upon by a protocol; The third PDSCH group is configured by a network side device; Optionally, if the fifth DAI does not correspond to any PDSCH group among the N PDSCH groups, processor 710 further comprises: The fifth DAI is used to generate a dynamic codebook to be transmitted on the first PUSCH based on the fifth DAI and the determined N second DAIs.

[0250] Optionally, the processor 710 further comprises: used to generate a target bit sequence based on the fifth DAI; Wherein, the target bit sequence is: If the terminal does not turn on HARQ transmission based on CBG, the number of bits included in the target bit sequence is equal to the product of the fifth DAI and a second value, and the bits in the target bit sequence are set to NACK; When the terminal turns on HARQ transmission based on CBG, the fifth DAI includes a third sub-DAI corresponding to TB granularity and a fourth sub-DAI corresponding to CBG granularity, the number of bits included in the target bit sequence is equal to the sum of a first target value and a second target value, the first target value is equal to the product of a value of the third sub-DAI and a second value, the second target value is equal to the product of a value of the fourth sub-DAI and a third value, and a bit in the target bit sequence is set to NACK.

[0251] Optionally, the second value is if the first condition is satisfied, the second value has a value of 2; if the first condition is not satisfied, the second value is 1; Wherein, the first condition includes that the terminal turns on HARQ-ACK spatial bundling indication, and one PDSCH reception corresponds to at most two transport blocks.

[0252] Optionally, the third value is determined based on the maximum number of transport blocks that can be scheduled by a single DCI and the maximum number of CBGs that can be divided by a single transport block.

[0253] Optionally, the processor 710 further comprises: used to determine a first relationship between the first DAI and the N PDSCH groups based on a predetermined rule; Among them, the preset rules are: determining a PDSCH group corresponding to the first DAI according to a PDSCH group located and scheduled by a target DCI, the target DCI being a DCI for scheduling a PDSCH in the N PDSCH groups last detected by the terminal; determining a PDSCH group corresponding to the first DAI based on a protocol agreement; determining a PDSCH group corresponding to the first DAI based on configuration information of network side equipment.

[0254] Optionally, the first relationship is: The first DAI corresponds to a fifth PDSCH group among the N PDSCH groups, and the fifth PDSCH group is any one of the N PDSCH groups; The first DAI does not correspond to any of the N PDSCH groups.

[0255] Optionally, when the first DAI corresponds to a fifth PDSCH group among the N PDSCH groups, determining a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the first relationship as described above may include: determining the first DAI as a second DAI corresponding to the fifth PDSCH group; determining an eighth DAI as a second DAI corresponding to the sixth PDSCH group; Among them, the eighth DAI is a DAI in a DCI corresponding to a sixth PDSCH group last detected by the terminal, and the sixth PDSCH group is any one of the N PDSCH groups other than the fifth PDSCH group.

[0256] It should be noted that the above-mentioned terminal 700 in this embodiment can realize each process in the method embodiment in the embodiment of the present application, and achieve the same beneficial effects. In order to avoid repetition, no further description will be given here.

[0257] It should be understood that in the embodiment of the present application, the radio frequency unit 701 may be used for transmitting and receiving information or transmitting and receiving signals in a call. Specifically, the radio frequency unit 701 receives downlink data from a base station, and then processes the data in the processor 710, and transmits uplink data to the base station. In general, the radio frequency unit 701 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc. In addition, the radio frequency unit 701 may communicate with other devices through a wireless communication system or a network.

[0258] The terminal provides wireless broadband Internet access to the user through a network module 702, helping the user, for example, to send and receive e-mail, browse web pages and access streaming media.

[0259] The audio output unit 703 can convert audio data received by the radio frequency unit 701 or the network module 702 or stored in the memory 709 into an audio signal and output it as a voice. And the audio output unit 703 can further provide audio output related to a specific function performed by the terminal 700 (e.g., a call signal tone, a message tone, etc.). The audio output unit 703 includes a speaker, a buzzer, a handset, etc.

[0260] The input unit 704 is used to receive audio or video signals. The input unit 704 may include a graphics processor (Graphics Processing Unit, GPU) 7041 and a microphone 7042, where the graphics processor 7041 processes image data of still or video images captured by an image capture device (e.g., a camera) in a video capture mode or an image capture mode. The processed image frames may be displayed on the display unit 706. The image frames processed by the graphics processor 7041 may be stored in the memory 709 (or other storage medium) or transmitted by the radio frequency unit 701 or the network module 702. The microphone 7042 may receive voice and process such voice as audio data. The processed audio data may be converted into a format that can be transmitted to a mobile communication base station via the radio frequency unit 701 in a telephone call mode and output.

[0261] The terminal 700 further includes at least one sensor 705, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor, among which the ambient light sensor can adjust the brightness of the display panel 7061 according to the brightness of the ambient light, and the proximity sensor can turn off the display panel 7061 and / or the backlight when the terminal 700 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes) and can detect the magnitude and direction of gravity when stationary, and may be used to identify the terminal attitude (e.g., portrait / landscape screen switching, related games, magnetometer attitude calibration), vibration identification related functions (e.g., pedometer, tap), etc. The sensor 705 may further include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyro, a barometer, a hygrometer, a thermometer, an infrared sensor, etc. No further description is given here.

[0262] The display unit 706 is used to display information input by a user or information provided to a user. The display unit 706 may include a display panel 7061, and the display panel 7061 may be arranged in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), etc.

[0263] The user input unit 707 may be used for receiving input numeric or character information and generating key signal inputs related to the user's setting and function control of the terminal. Specifically, the user input unit 707 includes a touch panel 7071 and other input devices 7072. The touch panel 7071 is also called a touch screen, and can collect touch operations by a user on or near the touch panel 7071 (e.g., an operation performed on or near the touch panel 7071 by a user using any suitable object or accessory such as a finger, a touch pen, etc.). The touch panel 7071 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch direction by the user, detects a signal due to the touch operation, and transmits the signal to the touch controller, and the touch controller receives the touch information from the touch detection device, converts it into touch point coordinates, and then transmits them to the processor 710, and receives and executes commands transmitted from the processor 710. In addition, the touch panel 7071 may be realized by adopting various types such as a resistive type, a capacitive type, an infrared type, and a surface acoustic wave type. In addition to the touch panel 7071, the user input unit 707 may further include other input devices 7072. Specifically, the other input devices 7072 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 operating lever. No further description will be given here.

[0264] Further, the touch panel 7071 may be covered on the display panel 7061. When the touch panel 7071 detects a user's touch operation on or near it, the touch panel 7071 transmits the detected touch event to the processor 710 to identify the type of the touch event, and the processor 710 then provides a corresponding visual output on the display panel 7061 according to the type of the touch event. In FIG. 7, the touch panel 7071 and the display panel 7061 are two independent components to realize the input and output functions of the terminal, but in some embodiments, the touch panel 7071 and the display panel 7061 may be integrated to realize the input and output functions of the terminal. Specific examples are not limited herein.

[0265] The interface unit 708 is an interface for connecting an external device to the terminal 700. For example, the external device may include a wired or wireless headphone port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting to a device having an identification module, an audio input / output (I / O) port, a video I / O port, an earphone port, etc. The interface unit 708 may be used to receive inputs (e.g., data information, power, etc.) from the external device and transmit the received inputs to one or more elements in the terminal 700, or may be used to transmit data between the terminal 700 and the external device.

[0266] The memory 709 may be used to store software programs and various data. The memory 709 may mainly include a program storage area and a data storage area. The program storage area may store an operating system, an application program required for at least one function (e.g., a voice playback function, an image playback function, etc.), and the data storage area may store data generated by the use of the mobile phone (e.g., audio data, a phone book, etc.). The memory 709 may include a high-speed random access memory, and may further include a non-volatile memory, such as at least one magnetic disk memory device, a flash memory device, or other non-volatile solid-state memory device.

[0267] The processor 710 is the control center of the terminal, and is connected to each part of the entire terminal through various interfaces and lines, and monitors the entire terminal by running or executing software programs and / or modules stored in the memory 709, and by accessing data stored in the memory 709, performing various functions of the terminal, and processing data. The processor 710 may include one or more processing units. Alternatively, the processor 710 may integrate an application processor and a modem processor, where the application processor is mainly for processing the operating system, user interface, and application programs, and the modem processor is mainly for processing wireless communication. As can be understood, the modem processor may not be integrated into the processor 710.

[0268] The terminal 700 may further include a power source 711 (e.g., a battery) for supplying power to each component, and optionally, the power source 711 may be logically connected to the processor 710 by a power management system, thereby enabling the power management system to realize functions such as charge / discharge management and power consumption management.

[0269] The terminal 700 also includes some non-illustrated functional modules, which will not be further described here.

[0270] Optionally, the embodiment of the present application further provides a terminal, which includes a processor 710, a memory 709, and a computer program stored in the memory 709 and capable of running on the processor 710, and when the computer program is executed by the processor 710, it can realize each process of the embodiment of the above HARQ-ACK codebook generation method and achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0271] Referring to Figure 8, Figure 8 is a second structural diagram of a network side device according to an embodiment of the present application. As shown in Figure 8, the network side device 800 includes a processor 801, a memory 802, a user interface 803, a transceiver 804, and a bus interface.

[0272] In the embodiment of the present application, the network side device 800 further includes a computer program stored in the memory 802 and capable of running on the processor 801, and when the computer program is executed by the processor 801, it realizes the following steps:

[0273] Transmitting first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI including a first DAI, the first DAI being used to generate a dynamic codebook transmitted on the first PUSCH; Wherein, the dynamic codebook includes HARQ-ACK bit sequences of N PDSCH groups, where N is a positive integer.

[0274] Optionally, the first DAI corresponds to at least one PDSCH group among the N PDSCH groups.

[0275] Alternatively, the first DAI corresponds to the N PDSCH groups, or the first DAI corresponds to a first PDSCH group of the N PDSCH groups.

[0276] Optionally, if the first DAI corresponds to the N PDSCH groups, the first DAI is determined based on a sum of N ninth DAIs; Wherein, each PDSCH group among the N PDSCH groups corresponds to one of the ninth DAI, each of the ninth DAIs is associated with a third DCI corresponding to the corresponding PDSCH group, and the third DCI corresponding to each PDSCH group is the DCI corresponding to the PDSCH group that was last transmitted by the network side device. Optionally, the first DAI does not correspond to any of the N PDSCH groups.

[0277] In FIG. 8, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits, such as one or more processors represented by processor 801 and memory represented by memory 802. The bus architecture may link various other circuits, such as peripherals, voltage regulators and power management circuits, etc. These are all well known in the art and will not be described further herein. The bus interface provides an interface. The transceiver 804 may be multiple elements, i.e., includes a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium. For different user equipment, the user interface 803 may be an interface that can be externalized or internalized to the required equipment. The connected equipment includes, but is not limited to, a keypad, a display, a speaker, a microphone, a joystick, etc.

[0278] The processor 801 is responsible for managing the bus architecture and general processing, and the memory 802 may store data used by the processor 2601 in performing its operations.

[0279] Optionally, when the computer program is executed by the processor 801, the following steps can be realized.

[0280] The network side device 800 can implement each process implemented by the network side device in the above method embodiments, and will not be further described here to avoid repetition.

[0281] The embodiment of the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, which, when executed by a processor, can realize each process of the embodiment of the HARQ-ACK codebook generation method or the embodiment of the information transmission method, and achieve the same technical effect. In order to avoid repetition, no further description will be given here. Wherein, the computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0282] It is to be noted that, as used herein, the terms "comprises," "including," or any other variation thereof, are intended to cover a non-exclusive "inclusion," whereby a process, method, article, or apparatus that includes a set of elements not only includes those elements, but also includes other elements not expressly listed or that are inherent to such process, method, article, or apparatus. In the absence of further limitations, an element limited by the phrase "comprising a," does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0283] From the above description of the embodiments, it is clear to those skilled in the art that the methods of the above embodiments may be realized in the form of software and a necessary general-purpose hardware platform. Of course, they may also be realized in hardware, but in many cases the former is a preferred embodiment. Based on this understanding, the technical solution of the present application may be substantially or in part contributed to the prior art in the form of a software product. The computer software product 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 the embodiments of the present application.

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

Claims

1. A method for generating a Hybrid Automatic Repeat Request Response (HARQ-ACK) codebook for use in a terminal, comprising: receiving first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI including a first DAI; determining a correspondence relationship between the first DAI and N Physical Downlink Shared Channel (PDSCH) groups; determining a second DAI corresponding to each PDSCH group among the N physical downlink shared channel (PDSCH) groups based on the correspondence relationship; generating a dynamic codebook to be transmitted on the first PUSCH based on the determined N second DAIs; Wherein, the dynamic codebook includes HARQ-ACK bit sequences for the N PDSCH groups, where N is a positive integer; The first DAI corresponds to at least one PDSCH group among the N PDSCH groups; When N is equal to 1, the correspondence relationship satisfies that the value of the first DAI corresponds to a single PDSCH group that is triggered; The step of determining a second DAI corresponding to each PDSCH group among the N physical downlink shared channel (PDSCH) groups based on the correspondence relationship includes: determining the first DAI as the second DAI corresponding to a first PDSCH group.

2. When N is greater than 1, the correspondence relationship satisfies that the first DAI corresponds to a first PDSCH group among the N PDSCH groups, and the first PDSCH group is agreed upon by a protocol; The step of determining a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the correspondence relationship includes: determining the first DAI as the second DAI corresponding to the first PDSCH group; determining a third DAI corresponding to each second PDSCH group as the second DAI corresponding to each of the second PDSCH groups; 2. The method according to claim 1 , wherein the third DAI is a DAI in a DCI corresponding to the second PDSCH group last detected by the terminal, and the second PDSCH group is a PDSCH group other than the first PDSCH group among the N PDSCH groups.

3. When N is greater than 1, the correspondence relationship satisfies that the first DAI corresponds to the N PDSCH groups; The step of determining a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the correspondence relationship includes: acquiring a fourth DAI in a second DCI corresponding to each PDSCH group among the N PDSCH groups, the second DCI corresponding to each PDSCH group being a DCI corresponding to this PDSCH group that was last detected by the terminal; comparing a first value with the first DAI to obtain a corresponding comparison result, the first value being determined based on a sum of the obtained N fourth DAIs; and determining the second DAI corresponding to each PDSCH group among the N PDSCH groups based on the comparison result.

4. The step of determining the second DAI corresponding to each PDSCH group among the N PDSCH groups based on the comparison result includes: determining a fifth DAI if the first value is not equal to the first DAI, the fifth DAI being used to indicate a number of DCIs for scheduling PDSCHs of the N PDSCH groups that were missed; and determining the second DAI corresponding to each PDSCH group of the N PDSCH groups based on the fifth DAI.

5. When the terminal does not turn on Code Block Group (CBG)-based HARQ transmission, the step of determining the second DAI corresponding to each PDSCH group among the N PDSCH groups based on the fifth DAI includes: determining a second DAI corresponding to the third PDSCH group based on the fifth DAI and a sixth DAI when the fifth DAI corresponds to a third PDSCH group among the N PDSCH groups, and determining a seventh DAI corresponding to each fourth PDSCH group as the second DAI corresponding to each fourth PDSCH group; if the fifth DAI does not correspond to any of the N PDSCH groups, determining a DAI in a last detected DCI corresponding to each PDSCH group among the N PDSCH groups as the second DAI corresponding to that PDSCH group; 5. The method according to claim 4, wherein the sixth DAI is a DAI in a DCI corresponding to the third PDSCH group last detected by the terminal, the seventh DAI is a DAI in a DCI corresponding to the fourth PDSCH group last detected by the terminal, the third PDSCH group is any one PDSCH group among the N PDSCH groups, and the fourth PDSCH group is a PDSCH group other than the third PDSCH group among the N PDSCH groups.

6. An information transmission method used in a network side device, comprising: transmitting, to a terminal, first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI including a first DAI, the first DAI being used to generate a dynamic codebook transmitted on the first PUSCH; Wherein, the dynamic codebook includes HARQ-ACK bit sequences for N Physical Downlink Shared Channel (PDSCH) groups, where N is a positive integer; The first DAI corresponds to at least one PDSCH group among the N PDSCH groups; The first DCI is used to cause the terminal to determine a correspondence relationship between the first DAI and the N PDSCH groups, and to determine a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the correspondence relationship, thereby generating the dynamic codebook; 5. The method of claim 4, wherein when N is equal to 1, the first DAI value corresponds to a single PDSCH group being triggered.

7. 7. The method of claim 6, wherein, when N is greater than 1, the first DAI corresponds to the N PDSCH groups, or the first DAI corresponds to a first PDSCH group among the N PDSCH groups, and the first PDSCH group is any one PDSCH group among the N PDSCH groups.

8. If the first DAI corresponds to the N PDSCH groups, the first DAI is determined based on a sum of N ninth DAIs; 8. The method according to claim 7, wherein each PDSCH group among the N PDSCH groups corresponds to one of the ninth DAIs, each of the ninth DAIs is attached to a third DCI corresponding to the corresponding PDSCH group, and the third DCI corresponding to each PDSCH group is the DCI corresponding to this PDSCH group that was last transmitted by the network side device.

9. A terminal, A receiving module for receiving first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI including a first DAI; a determination module for determining a correspondence relationship between the first DAI and N physical downlink shared channel (PDSCH) groups, and determining a second DAI corresponding to each PDSCH group among the N physical downlink shared channel (PDSCH) groups based on the correspondence relationship; and a generating module for generating a dynamic codebook to be transmitted on the first PUSCH based on the determined N second DAIs; Wherein, the dynamic codebook includes HARQ-ACK bit sequences for the N PDSCH groups, where N is a positive integer; The first DAI corresponds to at least one PDSCH group among the N PDSCH groups; When N is equal to 1, the correspondence relationship satisfies that the value of the first DAI corresponds to a single PDSCH group that is triggered; The decision module: A terminal, characterized in that the first DAI is used to determine the second DAI corresponding to a first PDSCH group.

10. When N is greater than 1, the correspondence relationship satisfies that the first DAI corresponds to a first PDSCH group among the N PDSCH groups, and the first PDSCH group is agreed upon by a protocol; The decision module: determining the first DAI as the second DAI corresponding to the first PDSCH group; determining a third DAI corresponding to each second PDSCH group as the second DAI corresponding to each second PDSCH group; The terminal according to claim 9, characterized in that the third DAI is a DAI in a DCI corresponding to a second PDSCH group last detected by the terminal, and the second PDSCH group is a PDSCH group other than the first PDSCH group among the N PDSCH groups.

11. When N is greater than 1, the correspondence relationship satisfies that the first DAI corresponds to the N PDSCH groups; The decision module: Obtaining a fourth DAI in a second DCI corresponding to each PDSCH group among the N PDSCH groups, and determining that the second DCI corresponding to each PDSCH group is the DCI corresponding to this PDSCH group that was last detected by the terminal; comparing a first value with the first DAI iteration to obtain a corresponding comparison result, the first value being determined based on a sum of the obtained N fourth DAI iterations; and determining the second DAI corresponding to each PDSCH group among the N PDSCH groups based on the comparison result.

12. A network side device, The method includes: transmitting, to a terminal, first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI including a first DAI, the first DAI being used to generate a dynamic codebook transmitted on the first PUSCH; Wherein, the dynamic codebook includes HARQ-ACK bit sequences for N Physical Downlink Shared Channel (PDSCH) groups, where N is a positive integer; The first DAI corresponds to at least one PDSCH group among the N PDSCH groups; The first DCI is used to cause the terminal to determine a correspondence relationship between the first DAI and the N PDSCH groups, and to determine a second DAI corresponding to each PDSCH group among the N PDSCH groups based on the correspondence relationship, thereby generating the dynamic codebook; When N is equal to 1, the value of the first DAI corresponds to a single PDSCH group that is triggered.

Images