Methods for constructing HARQ-ACK intrusion code, methods for transmitting information, and the machine.

Abstract

The present application provides an HARQ-ACK codebook generation method, an information transmission method, a terminal, and a network-side device. The HARQ-ACK codebook generation method comprises: receiving first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI comprising a first DAI; determining, according to the first DAI, second DAIs respectively corresponding to N physical downlink shared channel (PDSCH) groups; and generating, according to the determined N second DAIs, a dynamic codebook transmitted on the first PUSCH, wherein the dynamic codebook includes HARQ-ACK bit sequences of the N PDSCH groups, and N is a positive integer.

Description

HARQ-ACK codebook generation method, information transmission method and equipment Technical Field This application relates 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 When a UE organization needs to report a HARQ-ACK bit sequence at a certain feedback time, the UE determines the correspondence between each PDSCH transmission and certain bits / bits in the organization's HARQ-ACK bit sequence based on predefined rules and the scheduling of PDSCH transmissions on the single / multiple carriers that need to report HARQ-ACK at this feedback time. This operation is called constructing the HARQ-ACK codebook. The HARQ-ACK codebook includes: a semi-static codebook and a dynamic codebook. HARQ-ACK Codebooks are typically transmitted on PUCCHs. However, when a PUCCH transmission overlaps with a PUSCH transmission in the time domain, some or all of the UCIs carried on the PUCCH will be multiplexed onto the PUSCH for transmission. The DAI corresponding to the multiplexed HARQ-ACK Codebook can be indicated in the DCI format 0_1 ​​of the PUSCH scheduling; this can be referred to as the UL DAI. Currently, the terminal can be configured to perform HARQ-ACK feedback for up to two PDSCH groups through a dynamic codebook. However, when there is only a single UL DAI or a single group in the uplink DCI format 0_1, there is no corresponding solution for how this UL DAI is used to generate the dynamic codebook. Summary of the Invention This application provides 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 based on UL DAI for HARQ-ACK feedback of up to two PDSCH groups. In a first aspect, embodiments of this application provide a HARQ-ACK codebook generation method, the method comprising: Receive first downlink control information (DCI) for scheduling the first physical uplink shared channel (PUSCH), wherein the first DCI includes a first DAI; Based on the first DAI, determine the second DAI corresponding to each PDSCH group in the N physical downlink shared channel PDSCH groups; Based on the determined N second DAIs, a dynamic codebook is generated for transmission on the first PUSCH; The dynamic codebook contains HARQ-ACK bit sequences of the N PDSCH groups, where N is a positive integer. Secondly, embodiments of this application provide an information sending method, the method comprising: Send a first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI including a first DAI for generating a dynamic codebook transmitted on the first PUSCH; The dynamic codebook contains HARQ-ACK bit sequences of N Physical Downlink Shared Channel (PDSCH) groups, where N is a positive integer. Thirdly, embodiments of this application also provide a terminal, the terminal comprising: The receiving module is configured to receive first downlink control information (DCI) for scheduling the first physical uplink shared channel (PUSCH), wherein the first DCI includes a first DAI. The determining module is used to determine the second DAI corresponding to each PDSCH group in the N physical downlink shared channel PDSCH groups based on the first DAI; The generation module is used to generate a dynamic codebook to be transmitted on the first PUSCH based on the determined N second DAIs. The dynamic codebook contains HARQ-ACK bit sequences of the N PDSCH groups, where N is a positive integer. Fourthly, embodiments of this application also provide a network-side device, the network-side device comprising: The transmitting module is used to transmit first downlink control information (DCI) for scheduling the first physical uplink shared channel (PUSCH), the first DCI including a first DAI, the first DAI being used for generating a dynamic codebook transmitted on the first PUSCH. The dynamic codebook contains HARQ-ACK bit sequences of N Physical Downlink Shared Channel (PDSCH) groups, where N is a positive integer. Fifthly, embodiments of this application also provide a terminal, which includes a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the steps of the HARQ-ACK codebook generation method as described above. In a sixth aspect, embodiments of this application also provide a network-side device, which includes a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the steps of the information transmission method described above. In a seventh aspect, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the HARQ-ACK codebook generation method applied to a terminal as described above, or the steps of the information transmission method applied to a network-side device. In this embodiment, after receiving first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), where the first DCI includes a first DAI, the terminal can determine a second DAI corresponding to each of the N PDSCH groups based on the first DAI. Then, based on the determined N second DAIs, a dynamic codebook for transmission on the first PUSCH is generated. The dynamic codebook contains HARQ-ACK bit sequences from the N PDSCH groups, where N is a positive integer. Therefore, this embodiment provides a solution for generating a dynamic codebook containing HARQ-ACK bit sequences from the N PDSCH groups based on the first DAI, thereby ensuring the reliability of the dynamic codebook transmission and avoiding or mitigating the impact on decoding other information multiplexed on the PUSCH. Attached Figure Description To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Figure 1 is a structural diagram of a network system applicable to an embodiment of this application; Figure 2 is a flowchart of the HARQ-ACK codebook generation method provided in the embodiments of this application; Figure 3 is a flowchart of the information sending method provided in an embodiment of this application; Figure 4 is a schematic diagram of the transmission of the dynamic codebook provided in an embodiment of this application; Figure 5 is one of the structural diagrams of the terminal provided in the embodiments of this application; Figure 6 is one of the structural diagrams of the network-side device provided in the embodiments of this application; Figure 7 is a second structural diagram of the terminal provided in an embodiment of this application; Figure 8 is a second structural diagram of the network-side device provided in the embodiments of this application. Detailed Implementation The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. The terms "first," "second," etc., used in this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes, methods, products, or apparatuses. Additionally, the use of "and / or" in this application indicates at least one of the connected objects, such as A and / or B and / or C, representing seven possibilities: including A alone, B alone, C alone, and the presence of both A and B, both B and C, both A and C, and the presence of A, B, and C. Please refer to Figure 1. Figure 1 is a structural diagram of a network system applicable to an embodiment of this application. As shown in Figure 1, it includes a terminal 11 and a network-side device 12, wherein the terminal 11 and the network-side device 12 can communicate with each other. In this embodiment, terminal 11 can also be referred to as user equipment (UE). In practical applications, terminal 11 can be a mobile phone, tablet personal computer, laptop computer, personal digital assistant (PDA), mobile internet device (MID), wearable device, or vehicle-mounted device, etc. Network-side equipment 12 can be a base station, relay, or access point, etc. Further, the base station can be a 5G base station (gNB), or a base station in other communication systems (such as an evolved Node B (eNB)). For ease of understanding, the following describes some aspects of the embodiments of this application: I. Dynamic codebook for Hybrid Automatic Repeat reQuest Acknowledgement (HARQ-ACK) in New Radio (NR). When a UE organization needs to report a HARQ-ACK bit sequence at a certain feedback moment, the UE determines the correspondence between each PDSCH transmission and certain bits in the organization's HARQ-ACK bit sequence based on predefined rules and the scheduling of PDSCH transmissions on the single / multiple carriers that need to report HARQ-ACK at this feedback moment. This operation is called constructing the HARQ-ACK codebook. When the semi-persistent scheduling (SPS) PDSCH is released via downlink control information (DCI), the UE also needs to use the HARQ-ACK bit to acknowledge receipt, so as to ensure that both sides have a consistent understanding of whether the SPS PDSCH is active. 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, mainly to ensure transmission reliability, but the feedback overhead is relatively large. The latter only provides feedback for actual DCI indications and PDSCH transmissions, with less feedback overhead, but transmission reliability may be affected to some extent when DCI missed detections are common. The dynamic codebook reserves HARQ-ACK feedback bits for each actually used DAI value by counting the downlink assignment index (DAI) of the actual scheduled PDSCH transmissions or SPS PDSCH release indications. If the UE infers from other detected DAIs that some DAIs have not received their corresponding PDSCH allocation indications or SPS PDSCH release indications, 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. DAI uses a limited number of bits (a single DAI typically occupies 2 bits) for indication. To extend its indication range, a modulo operation is introduced, which involves counting sequentially starting from 1 and then taking the modulo to obtain the DAI value corresponding to a given count. The processing of DAI in downlink scheduling can be referred to in the table below. The value of counter DAI in DCI format 1_0, and the value of counter DAI or total count DAI in DCI format 1_1. In the table above, the most significant bit (MSB), the least significant bit (LSB), the counter DAI (C-DAI), and the total DAI (T-DAI) are listed. Y represents the number of {serving cell, PDCCH monitoring occasion} pairs in which PDSCH transmission(s) associated with PDCCH or PDCCH indicating SPS PDSCH release is present, denoted as Y), where Y ≥ 1. When the UE is configured with only a single serving cell, the aforementioned DAI only applies to a single carrier and counts them one by one in the order indicated by the DCI, which can be called C-DAI. When a UE is configured with multiple serving cells, a new T-DAI is introduced to further increase reliability. This T-DAI indicates the number of all DCI indications received up to the current time-domain detection location, including all DCI indications received at the current time-domain detection location on each serving cell. Therefore, the value of T-DAI is only updated when the time-domain detection location changes. The combined use of T-DAI and C-DAI can effectively avoid the situation where the UE and gNB have inconsistent understanding of the transmission of DCI indications when DCI indications are lost on one or more serving cells at a certain time-domain detection location (as long as DCI indications are not lost on all serving cells). In the embodiments of this application, the method for determining the HARQ-ACK bit sequence corresponding to each DAI is described below: The first scenario is when the network-side device configures the parameter PDSCH-Code BlockGroupTransmission for a serving cell of the UE to enable HARQ transmission based on code block groups (CBG): Method 1: PDSCH transmission scheduled by DCI format 1_1 supports CBG-based HARQ transmission, with a single DAI corresponding to... One HARQ-ACK feedback bit. in, In response to A serving cell configured with the parameter PDSCH-CodeBlockGroupTransmission The maximum value; The value of the parameter maxNrofCodeWordsScheduledByDCI for serving cell c indicates the maximum number of transport blocks that a single DCI can schedule simultaneously. The value of the parameter maxCodeBlockGroupsPerTransportBlock for serving cell c indicates the maximum number of CBGs that a single transport block can be divided into. If we are targeting a specific serving cell c, Then UE will The last bit Each bit is set to NACK. forward Each bit is set based on the decoding status of each CBG corresponding to the actual received transport block. Method 2: PDSCH transmissions scheduled by DCI format 1_0 only support HARQ transmissions based on transport blocks (TBs). Similar to SPS PDSCH release indication and SPS PDSCH reception, only a single HARQ-ACK bit is fed back for each transport block. These cases all belong to the situation where a single DCI indication or PDSCH transmission corresponds to only a single transport block. The second scenario is when the network has not configured the parameter PDSCH-CodeBlockGroupTransmission for a certain serving cell of the UE, that is, when CBG-based HARQ transmission is not enabled: Method 1: If the harq-ACK-SpatialBundlingPUCCH or harq-ACK-Spatial BundlingPUSCH parameters are not configured for the UE (i.e., Spatial Bundling for HARQ-ACK is not enabled; Spatial Bundling can be understood as HARQ-ACK feedback compression and merging between two codewords corresponding to the same PDSCH transmission; the harq-ACK-SpatialBundlingPUCCH parameter is applied to HARQ-ACK transmissions carried on the PUCCH, and the harq-ACK-SpatialBundlingPUSCH parameter is applied to HARQ-ACK transmissions carried on the PUSCH), and it represents at least one downlink (DL) bandwidth portion of at least one serving cell of the UE, then... The Part (BWP) is configured with the maxNrofCodeWordsScheduledByDCI parameter to correspond to a maximum of two transport blocks in a single PDSCH reception. In this case, a single DAI corresponds to two HARQ-ACK bits, where 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. Method 2: If the harq-ACK-SpatialBundlingPUCCH or harq-ACK-SpatialBundlingPUSCH parameters have been configured for the UE, and the maxNrofCodeWordsScheduledByDCI parameter has been configured for at least one DL BWP of at least one serving cell of the UE to correspond to a maximum of two transport blocks for a single PDSCH reception, then a single DAI corresponds to a single HARQ-ACK bit, and its value is set as the logical AND of the HARQ-ACK of the first transport block and the HARQ-ACK of the second transport block. Method 3: Otherwise, a single DAI corresponds to a single HARQ-ACK bit, with the value set to the HARQ-ACK of a single transport block. "Otherwise" indicates any remaining cases other than those listed in Methods 1 and 2, where neither a maximum of two transport blocks is configured, nor are Spatial Bundling parameters configured. In this case, a single downlink DCI will only schedule a single transport block, therefore a single DAI corresponds to a single HARQ-ACK bit. When the network-side device configures the parameter PDSCH-Code BlockGroupTransmission for one or more serving cells of the UE to enable CBG-based HARQ transmission, the HARQ-ACK Codebook contains two HARQ-ACK sub-codebooks. The first sub-codebook contains HARQ-ACK bits at all TB granularities, involving SPS PDSCH release indication, SPS PDSCH reception, PDSCH transmissions scheduled by DCI format 1_0 on serving cells with CBG-based HARQ transmission enabled (these PDSCH transmissions only support TB-granular HARQ-ACK feedback), and HARQ-ACK corresponding to PDSCH transmissions scheduled by DCI format 1_0 / 1_1 on serving cells without CBG-based HARQ transmission enabled (these PDSCH transmissions necessarily only support TB-granular HARQ-ACK feedback). The second sub-codebook contains HARQ-ACK bits at all CBG granularities, involving HARQ-ACK corresponding to PDSCH transmissions scheduled by DCI format 1_1 on serving cells with CBG-based HARQ transmission enabled. The HARQ-ACK Codebook is formed by sequentially concatenating the first and second sub-codebooks. HARQ-ACK Codebooks are typically transmitted on the PUCCH, with the time and frequency domain information of the PUCCH indicated in the DCI (with one exception: the frequency domain information of the PUCCH for HARQ-ACK feedback of the SPS PDSCH can be configured by higher layers). When a PUCCH transmission overlaps with a PUSCH transmission in the time domain, some or all of the UCI carried on the PUCCH will be multiplexed onto the PUSCH for transmission. For HARQ-ACK dynamic codebooks, DCI misses affect the construction of the HARQ-ACK Codebook (including the number of HARQ-ACK bits contained in the Codebook). The number of HARQ-ACK bits affects the time-frequency resources occupied during multiplexing transmission on the PUSCH, thus impacting the time-frequency demapping and decoding of other data transmissions on the PUSCH (e.g., UL-SCH). To avoid the impact of inconsistencies in the UE's and network's understanding of the HARQ-ACK bit count, the DAI corresponding to the multiplexed HARQ-ACK Codebook can be indicated in the DCI format 0_1 ​​of the PUSCH scheduling; this can 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 also be used to determine the DCI miss status corresponding to the HARQ-ACK bits at the end of the HARQ-ACK Codebook. When the HARQ-ACK Codebook only involves TB-level HARQ-ACK feedback (i.e., not involving two sub-codebooks), DCI format 0_1 ​​indicates only a single UL DAI (indicated by the DCI field "1st downlink assignment index"), corresponding to a single HARQ-ACK Codebook. When the HARQ-ACK Codebook involves both TB-level and CBG-level HARQ-ACK feedback (i.e., formed by two sub-codebooks cascaded sequentially), DCI format 0_1 ​​indicates two UL DAIs simultaneously. The first UL DAI (indicated by the DCI field "1st downlink assignment index") is applied to the first sub-codebook, and the second UL DAI (indicated by the DCI field "2nd downlink assignment index") is applied to the second sub-codebook. II. Enhancement of HARQ-ACK dynamic codebook for NR-U. The enhancements introduced for dynamic codebooks mainly include the following: Explicitly group dynamically scheduled PDSCHs and indicate the corresponding groups in the scheduling DCI; HARQ-ACK feedback for the same PDSCH group is carried on the same PUCCH. Perform C-DAI or T-DAI counting within a single PDSCH group; Each PDSCH packet maintains a New Feedback Indicator (NFI), which indicates whether only new feedback needs to be transmitted or previous feedback also needs to be retransmitted by flipping the NFI. If the NFI flips, all feedback for this PDSCH packet before the DCI that indicated the NFI flip will be discarded, and only the HARQ-ACK feedback for this DCI and subsequent PDSCHs scheduled for this PDSCH packet will be transmitted. If the NFI does not flip, all HARQ-ACK feedback for this PDSCH packet since the last NFI flip needs to be transmitted, that is, HARQ-ACK feedback with the same NFI value is valid. Therefore, the actual number of HARQ-ACK bits that need to be transmitted for two feedback requests for the same PDSCH packet may change. A single DCI can request HARQ-ACK feedback for one or more PDSCH packets to be transmitted on the same PUCCH. Typically, a single downlink scheduling DCI requests HARQ-ACK feedback for the PDSCH packets corresponding to the PDSCH it schedules by default. This DCI can also additionally trigger HARQ-ACK feedback for other PDSCH packets to be transmitted together on the PUCCH it indicates. The maximum number of PDSCH packets currently supported is 2; The UE can indicate whether it supports enhanced dynamic codebook through capability information. When an enhanced dynamic codebook is configured for the UE, the presence of a UL DAI for an additional single PDSCH packet in the uplink non-fallback DCI, i.e., DCI format 0_1, can be configured by Radio Resource Control (RRC) signaling. However, when only a single PDSCH packet's UL DAI exists in DCI format 0_1, there is currently no solution regarding which PDSCH packet this UL DAI applies to. The following describes the HARQ-ACK codebook generation method according to the embodiments of this application. Referring to Figure 2, which is a flowchart of the HARQ-ACK codebook generation method provided in this application embodiment, the HARQ-ACK codebook generation method of this application embodiment can be applied to a terminal. As shown in Figure 2, the HARQ-ACK codebook generation method may include the following steps: Step 201: Receive first downlink control information (DCI) for scheduling the first physical uplink shared channel (PUSCH), wherein the first DCI includes a first DAI. Step 202: Based on the first DAI, determine the second DAI corresponding to each PDSCH group in the N Physical Downlink Shared Channel (PDSCH) groups, where N is a positive integer. The second DAI corresponding to each PDSCH group is used to determine the HARQ-ACK bit sequence of that PDSCH group. Step 203: Generate a dynamic codebook to be transmitted on the first PUSCH based on the determined N second DAIs; wherein the dynamic codebook contains the HARQ-ACK bit sequence of the N PDSCH groups. In a specific implementation, generating a dynamic codebook for transmission on the first PUSCH based on the determined N second DAIs may specifically include: Based on the determined N second DAIs, determine the HARQ-ACK sequence for each of the N PDSCH groups; The dynamic codebook is generated based on the HARQ-ACK sequence of each of the N PDSCH groups. In a specific implementation, optionally, the dynamic codebook can be generated by sequentially concatenating the HARQ-ACK sequences of each of the N PDSCH groups according to the group number order of the N PDSCH groups, but it is not limited to this. In this embodiment of the HARQ-ACK codebook generation method, after receiving first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), which includes a first DAI, the terminal can determine a second DAI corresponding to each of the N physical downlink shared channel (PDSCH) groups based on the first DAI. Then, based on the determined N second DAIs, a dynamic codebook for transmission on the first PUSCH is generated. The dynamic codebook contains HARQ-ACK bit sequences from the N PDSCH groups, where N is a positive integer. Therefore, this embodiment provides a solution for generating a dynamic codebook containing HARQ-ACK bit sequences from the N PDSCH groups based on the first DAI, thereby ensuring the reliability of the dynamic codebook transmission. In this embodiment, optionally, determining the second DAI corresponding to each PDSCH group in the N Physical Downlink Shared Channel (PDSCH) groups based on the first DAI includes: Determine the first relationship between the first DAI and the N PDSCH groups; Based on the first relationship, determine the second DAI corresponding to each of the N PDSCH groups. In specific implementation, the determination of the first relationship between the first DAI and the N PDSCH groups can include the following two implementation methods. Implementation Method 1: The first relationship satisfies the following: the first DAI corresponds to at least one of the N PDSCH groups. In other words, in Implementation Method 1, the first DAI must correspond to at least one of the N PDSCH groups. When N equals 1, that is, when the N PDSCH groups include only one PDSCH group, the first DAI corresponds to that PDSCH group. When N is greater than 1, the first relation may optionally satisfy any one of the following: The first DAI corresponds to the N PDSCH groups; The first DAI corresponds to the first PDSCH group among the N PDSCH groups. It should be noted that the first PDSCH group is one of the N PDSCH groups. In specific implementation, the first PDSCH group can be any one of the N PDSCH groups. Further, the first PDSCH group can satisfy any one of the following: The first PDSCH group is the PDSCH group where the target DCI schedules the PDSCH. The target DCI is the last DCI detected by the terminal used to schedule the PDSCH in the N PDSCH groups. The first PDSCH group is defined by the protocol; The first PDSCH group is configured by the network-side device. For ease of understanding, the following explanations will cover each situation separately: Case 1: The first PDSCH group satisfies the following: the first PDSCH group is the PDSCH group where the target DCI schedules the PDSCH, and the target DCI is the DCI last detected by the terminal for scheduling the PDSCH in the N PDSCH groups. In scenario one, the first PDSCH group is determined autonomously by the terminal based on the scheduling time of each PDSCH group. Details are as follows. Each PDSCH group includes at least one PDSCH, and each PDSCH corresponds to a DCI for scheduling its transmission. The PDSCH scheduling time for each DCI may be different. For example, assuming the N PDSCH groups include PDSCH group 1, PDSCH group 2, and PDSCH group 3, the terminal finally detects that the DCI used to schedule PDSCH in the N PDSCH groups is the DCI used to schedule PDSCH in PDSCH group 3. Therefore, PDSCH group 3 can be identified as the first PDSCH group. Scenario 2: The first PDSCH group satisfies the conditions stipulated in the protocol for the first PDSCH group. In scenario two, the first PDSCH group is one of the N PDSCH groups agreed upon in the protocol. For example, the protocol can specify that the first PDSCH group 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 at the beginning or end of the bit sequence corresponding to the dynamic codebook when the HARQ-ACK bit sequence is generated, or the PDSCH group with a specified group number. Scenario 3: The first PDSCH group satisfies the condition that the first PDSCH group is configured by the network-side device. In scenario three, the first PDSCH group is one of the N PDSCH groups configured by the network-side device. For example, the network-side device can configure the first PDSCH group as the first or last PDSCH group among N PDSCH groups, or as the PDSCH group with the smallest or largest group number, or as the PDSCH group at the beginning or end of the bit sequence corresponding to the dynamic codebook when the HARQ-ACK bit sequence is generated, or as the PDSCH group with a specified group number. As can be seen, compared to scenario one, in scenarios two and three, the terminal does not need to independently determine the first PDSCH group, thus reducing the terminal's burden. Compared to scenario two, in scenarios one and three, the determination of the first PDSCH group offers greater flexibility. Compared to scenario three, in scenarios one and two, the terminal does not need to interact with network-side equipment to determine the first PDSCH group, thus reducing signaling overhead. Implementation Method 2: Determining the first relationship between the first DAI and the N PDSCH groups includes: According to preset rules, the first relationship between the first DAI and the N PDSCH groups is determined; The preset rules include at least one of the following: The PDSCH group corresponding to the first DAI is determined based on the PDSCH group where the target DCI is scheduled. The target DCI is the last DCI detected by the terminal used to schedule PDSCH in the N PDSCH groups. The PDSCH group corresponding to the first DAI is determined according to the agreement. The PDSCH group corresponding to the first DAI is determined based on the configuration information of the network-side device. For implementation method two, optionally, the first relationship satisfies any one of the following: The first DAI corresponds to the 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. It should be noted that the fifth PDSCH group is similar to the first PDSCH group mentioned above. For details, please refer to the description of the first PDSCH group mentioned above. It will not be repeated here. Therefore, in Implementation Method 2, when the first relationship between the first DAI and the N PDSCH groups is determined based on a preset rule, the first DAI may not correspond to any of the N PDSCH groups; that is, the first DAI is unrelated to the N PDSCH groups. Thus, in Implementation Method 2, the first DAI does not necessarily have a corresponding relationship with the N PDSCH groups. As can be seen from the foregoing, in this embodiment, the first relationship between the first DAI and the N PDSCH groups includes the following representation. In the first representation mode, the first DAI corresponds to the first PDSCH group among the N PDSCH groups; or, the first DAI corresponds to the fifth PDSCH group among the N PDSCH groups. The second representation method is that the first DAI corresponds to the N PDSCH groups. The third representation is that the first DAI does not correspond to any of the N PDSCH groups. In this embodiment, the specific implementation of determining the second DAI corresponding to each PDSCH group in the N PDSCH groups based on the first relationship is related to the specific representation of the first relationship between the first DAI and the N PDSCH groups. Therefore, the following describes the specific implementation of determining the second DAI corresponding to each PDSCH group in the N PDSCH groups based on the first relationship, according to the above three representation methods. Regarding the aforementioned first mode of expression Optionally, when the first DAI corresponds to the first PDSCH group, the step of determining the second DAI corresponding to each of the N PDSCH groups based on the first relationship includes: The first DAI is determined to be the second DAI corresponding to the first PDSCH group; The third DAI is identified as the second DAI corresponding to the second PDSCH group; Wherein, the third DAI is the DAI in the DCI that the terminal last detected corresponding to the second PDSCH group; the second PDSCH group is any PDSCH group other than the first PDSCH group among the N PDSCH groups. For ease of understanding, the following example is provided: Assume that the N PDSCH groups include PDSCH group 0 and PDSCH group 1, where PDSCH group 0 is the first PDSCH group and PDSCH group 1 is the second PDSCH group. For PDSCH group 0, its corresponding second DAI is the same as the first DAI; for PDSCH group 1, its corresponding second DAI is the DAI in the DCI corresponding to the PDSCH group that the terminal last detected. Here, the DCI corresponding to the PDSCH group refers to the PDSCH scheduled by this DCI belonging to this PDSCH group. In the case where the first DAI corresponds to the fifth PDSCH group among the N PDSCH groups, optionally, determining the second DAI corresponding to each PDSCH group among the N PDSCH groups based on the first relationship includes: The first DAI is determined to be the second DAI corresponding to the fifth PDSCH group; The eighth DAI is identified as the second DAI corresponding to the sixth PDSCH group; Wherein, the eighth DAI is the DAI in the DCI that the terminal last detected corresponding to the sixth PDSCH group; the sixth PDSCH group is any PDSCH group other than the fifth PDSCH group among the N PDSCH groups. In this case, the implementation principle of determining the second DAI corresponding to each PDSCH group in the N PDSCH groups based on the first relationship is the same as the implementation principle of determining the second DAI corresponding to each PDSCH group in the N PDSCH groups based on the first relationship in the case where the first DAI corresponds to the first PDSCH group. For details, please refer to the foregoing description, which will not be repeated here. Regarding the second mode of expression mentioned above Optionally, determining the second DAI corresponding to each of the N PDSCH groups based on the first relationship includes: Obtain the fourth DAI in the second DCI corresponding to each of the N PDSCH groups, where the second DCI corresponding to each PDSCH group is the last DCI detected by the terminal that corresponds to that PDSCH group. The first value is compared with the value of the first DAI to obtain the corresponding comparison result; wherein, the first value is determined based on the sum of the N values ​​of the fourth DAI obtained; Based on the comparison results, the second DAI corresponding to each of the N PDSCH groups is determined. In a specific implementation, in the first implementation method, the first value can be the sum of the N values ​​of the fourth DAI obtained. In the second implementation, the first value can be obtained by performing a modulo operation on the sum of the N obtained fourth DAI values. Assuming that the fourth DAI corresponding to each PDSCH group in the N PDSCHs are DAI1, DAI2, ..., DAIN, then the first value DAI_Sum can be calculated using the following formula: Where Round_Size is the modulus of the modulo operation, which is related to the number of bits L occupied by a single DAI. Optionally, Round_Size = 2L. For example, when DAI uses 2 bits for indication, Round_Size = 4. In the second representation, the first DAI corresponds to the N PDSCH groups. Therefore, the first DAI corresponds to the sum of the values ​​of the N fourth DAIs. The terminal can compare the first DAI with the first value to obtain a comparison result. Then, based on the comparison result, the second DAI corresponding to each PDSCH group in the N PDSCH groups is determined. The comparison results can be used to determine whether the terminal has missed a DCI for scheduling the PDSCHs of the N PDSCH groups. Specifically, if the comparison result shows that the first value is equal to the value of the first DAI, the terminal can determine that there is no missed detection of DCI for scheduling the N PDSCH groups. In the case where there is no missed detection, the terminal can determine the DAI in the last detected DCI for each of the N PDSCH groups as the second DAI corresponding to that PDSCH group. If the comparison result shows that the first value and the first DAI are not equal, the terminal can determine that there is a missed detection of the DCI used to schedule the N PDSCH groups. In the case of a missed detection, the terminal can determine the second DAI corresponding to each of the N PDSCH groups using the following method. Optionally, determining the second DAI corresponding to each of the N PDSCH groups based on the comparison results includes: Determine the fifth DAI, which indicates the number of missed DCIs for scheduling the N PDSCH groups; Based on the fifth DAI, determine the second DAI corresponding to each of the N PDSCH groups. In specific implementation, the fifth DAI can be determined based on the first value and the value of the first DAI. Let the first value be DAI_Sum, the value of the first DAI be UL_DAI, and the fifth DAI be DAI_Diff. Optionally, DAI_Diff can be calculated using the following formula: DAI_Diff=(UL_DAI–DAI_Sum-1)mod Round_Size+1 Where X mod Y represents taking the modulus of X with respect to Y, and Round_Size is the modulus of the modulo operation, which is related to the number of bits L occupied by a single DAI. Optionally, Round_Size = 2L. For example, when DAI uses 2 bits for indication, Round_Size = 4. For instance, when UL_DAI = 3 and DAI_Sum = 4, DAI_Diff = (3 – 4 – 1) mod 4 + 1 = 3. In this embodiment, the specific implementation of determining the second DAI corresponding to each of the N PDSCH groups based on the fifth DAI is related to whether the terminal has enabled CBG-based HARQ transmission. In this embodiment, if some serving cells of the terminal are configured with the parameter PDSCH-CodeBlockGroupTransmission, it can be considered that the terminal has enabled CBG-based HARQ transmission. The following descriptions address scenario one, where the terminal has not enabled HARQ transmission based on CBG, and scenario two, where the terminal has enabled HARQ transmission based on CBG. For scenario one, optionally, determining the second DAI corresponding to each of the N PDSCH groups based on the fifth DAI includes any one of the following: When the fifth DAI corresponds to the third PDSCH group in the N PDSCH groups, the second DAI corresponding to the third PDSCH group is determined according to the fifth DAI and the sixth DAI, and the seventh DAI is determined as the second DAI corresponding to the fourth PDSCH group. If the fifth DAI does not correspond to any of the N PDSCH groups, the DAI in the last detected DCI corresponding to each of the N PDSCH groups is determined as the second DAI corresponding to that PDSCH group. Wherein, the sixth DAI is the DAI in the DCI corresponding to the third PDSCH group that was last detected by the terminal, and the seventh DAI is the DAI in the DCI corresponding to the fourth PDSCH group that was last detected by the terminal; the third PDSCH group is any one of the N PDSCH groups, and the fourth PDSCH group is any one of the N PDSCH groups other than the third PDSCH group. As can be seen, in this embodiment, for scenario one, the terminal also needs to further determine the second DAI corresponding to each PDSCH group in the N PDSCH groups based on the second relationship between the fifth DAI and the N PDSCH groups. When the second relationship is such 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 can be obtained by adding the fifth DAI and the sixth DCI. Optionally, the second DAI corresponding to the third PDSCH group can be obtained by taking the modulo of the sum. The second DAI corresponding to the fourth PDSCH group can be the DAI in the DCI last detected by the terminal that corresponds to the fourth PDSCH group. Furthermore, the HARQ-ACK bit sequence of the third PDSCH group includes a first bit sequence and a second bit sequence concatenated in sequence; The first bit sequence is determined based on the sixth DAI, and the second bit sequence is determined based on the fifth DAI. In a specific implementation, in the HARQ-ACK bit sequence of the third PDSCH group, the second bit sequence may be located after the first bit sequence. It should be noted that in this embodiment, the method for determining the bit sequence based on DAI is the same as the method for determining the HARQ-ACK bit sequence corresponding to each DAI in the aforementioned section, which can be found in the previous description and will not be repeated here. It should also be noted that since the dynamic codebook in this embodiment is transmitted on the PUSCH, the parameter harq-ACK-SpatialBundlingPUCCH needs to be replaced with harq-ACK-SpatialBundlingPUSCH. In the event of a missed detection at the terminal, determining the HARQ-ACK codebook for each PDSCH group using the above method allows the terminal and network-side devices to understand the size of the dynamic codebook, thereby enabling the network-side devices to successfully acquire the dynamic codebook and improving the reliability of data transmission. Optionally, the second bit sequence satisfies any one of the following: If the first condition is met, the number of bits in the second bit sequence is twice the value of the fifth DAI, and the bits in the second bit sequence are set to negative acknowledgment (NACK). If the first condition is not met, the number of bits in the second bit sequence is equal to the value of the fifth DAI, and the bits of the second bit sequence are set to NACK. The first condition includes: the terminal enables HARQ-ACK spatial binding indication, and a single PDSCH reception corresponds to a maximum of two transport blocks. In specific implementation, if the terminal is not configured with the harq-ACK-SpatialBundlingPUSCH parameter, then the HARQ-ACK spatial bundling instruction can be enabled on the terminal. The maxNrofCodeWordsScheduledByDCI parameter can be used to configure at least one DL BWP of at least one serving cell of the terminal to receive a maximum of two transport blocks per PDSCH. In this embodiment, when a certain bit is set to Negative Acknowledgement (NACK), the value of that bit can be set to '0'. When the second relationship is that the fifth DAI does not correspond to any of the N PDSCH groups, the second DAI corresponding to each of the N PDSCH groups can be the DAI in the DCI corresponding to the last PDSCH group detected by the terminal. For scenario two, optionally, determining the second DAI corresponding to each PDSCH group among the N PDSCH groups based on the fifth DAI includes any one of the following: When the fifth DAI corresponds to the third PDSCH group among the N PDSCH groups, the second DAI corresponding to the third PDSCH group is determined according to the first sub-DAI, the second sub-DAI, the third sub-DAI, and the fourth sub-DAI, and the seventh DAI is determined as the second DAI corresponding to the fourth PDSCH group. If the fifth DAI does not correspond to any of the N PDSCH groups, the DAI in the last detected DCI corresponding to each of the N PDSCH groups is determined as the second DAI corresponding to that PDSCH group. The fifth DAI includes the first sub-DAI corresponding to the transport block (TB) granularity and the second sub-DAI corresponding to the CBG granularity; the third sub-DAI is the DAI in the first type DCI last detected by the terminal corresponding to the third PDSCH group; the fourth sub-DAI is the DAI in the second type DCI last detected by the terminal corresponding to the third PDSCH group; and the seventh DAI is the DAI in the DCI last detected by the terminal corresponding to the fourth PDSCH group. The PDSCH scheduled by the first type DCI is based on TB granularity feedback HARQ-ACK, and the PDSCH scheduled by the second type DCI is based on CBG granularity feedback HARQ-ACK. The third PDSCH group is any one of the N PDSCH groups, and the fourth PDSCH group is any PDSCH group other than the third PDSCH group among the N PDSCH groups. In scenario two, the terminal initiates CBG-based HARQ transmission. Therefore, the DCI used to schedule the PDSCHs of the N PDSCH groups can include a first type of DCI and a second type of DCI. Specifically, for PDSCHs scheduled by the first type of DCI, it is based on TB-granular feedback HARQ-ACK; for PDSCHs scheduled by the second type of DCI, it is based on TB-granular feedback HARQ-ACK. As described above, the fifth DAI is used to indicate the number of missed DCIs for scheduling the N PDSCH groups. Therefore, the fifth DAI includes a first sub-DAI corresponding to the transport block (TB) granularity and a second sub-DAI corresponding to the CBG granularity. The first sub-DAI can be used to indicate the number of missed first-type DCIs for scheduling the N PDSCH groups; the second sub-DAI can be used to indicate the number of missed second-type DCIs for scheduling the N PDSCH groups. For scenario two, the terminal also needs to further determine the second DAI corresponding to each PDSCH group in the N PDSCH groups based on the second relationship between the fifth DAI and the N PDSCH groups. When the second relationship is such that the fifth DAI corresponds to the third PDSCH group, the second DAI corresponding to the third PDSCH group is determined based on the first sub-DAI, the second sub-DAI, the third sub-DAI, and the fourth sub-DAI. Specifically, the second DAI corresponding to the third PDSCH group can be formed by cascading the first sub-DAI, the second sub-DAI, the third sub-DAI, and the fourth sub-DAI. The second DAI corresponding to the fourth PDSCH group can be the DAI in the DCI last detected by the terminal that corresponds to the fourth PDSCH group. 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 concatenated in sequence; 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. In specific implementation, in the HARQ-ACK bit sequence of the third PDSCH group, the third bit sequence and the fourth bit sequence are consecutive, and the fourth bit sequence may be located after the third bit sequence; the fifth bit sequence and the sixth bit sequence are consecutive, and the sixth bit sequence may be located after the fifth bit sequence. Furthermore, for the first combined bit sequence of the third and fourth bit sequences, and the second combined bit sequence of the fifth and sixth bit sequences, in the HARQ-ACK bit sequence of the third PDSCH group, the first combined bit sequence may be located after or before the second combined bit sequence, depending on actual needs; this application embodiment does not limit this. In the event of a missed detection at the terminal, determining the HARQ-ACK codebook for each PDSCH group using the above method allows the terminal and network-side devices to understand the size of the dynamic codebook, thereby enabling the network-side devices to successfully acquire the dynamic codebook and improving the reliability of data transmission. Optionally, the fourth bit sequence satisfies any one of the following: If the first condition is met, the number of bits in the fourth bit sequence is twice the value of the first sub-DAI, and the bits in the fourth bit sequence are set to negative acknowledgment (NACK). If the first condition is not met, the number of bits in the fourth bit sequence is equal to the value of the first sub-DAI, and the bits of the fourth bit sequence are set to NACK. The first condition includes: the terminal enables HARQ-ACK spatial binding indication, and a single PDSCH reception corresponds to a maximum of two transport blocks. Optionally, the sixth bit sequence satisfies: The number of bits in the sixth bit sequence is equal to the product of the value of the second sub-DAI and the fourth value, and the bits in the sixth bit sequence are set to NACK; The fourth value is determined based on the maximum number of transport blocks that a single DCI can schedule and the maximum number of CBGs that a single transport block can be split into. In specific implementation, the fourth value can be: For the specific meaning of , please refer to the above description, which will not be repeated here. When the second relationship is that the fifth DAI does not correspond to any of the N PDSCH groups, the second DAI corresponding to each of the N PDSCH groups can be the DAI in the DCI corresponding to the last PDSCH group detected by the terminal. For scenarios one and two above, if the fifth DAI does not correspond to any of the N PDSCH groups, optionally, generating the dynamic codebook transmitted on the first PUSCH based on the determined N second DAIs includes: Based on the fifth DAI and the determined N second DAIs, a dynamic codebook is generated for transmission on the first PUSCH. Optionally, generating the dynamic codebook transmitted on the first PUSCH based on the fifth DAI and the determined N second DAIs includes: Based on the fifth DAI, the target bit sequence is generated. In specific implementation, after generating the target bit sequence based on the fifth DAI, the terminal can 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, as well as the target bit sequence. This allows the terminal and network-side devices to understand the size of the dynamic codebook, thereby enabling the network-side devices to successfully obtain the dynamic codebook and improving the reliability of data transmission. In a specific implementation, the target bit sequence may optionally satisfy any one of the following: When the terminal does not enable CBG-based HARQ transmission, the number of bits in the target bit sequence is equal to the product of the value of the fifth DAI and the second value, and the bits in the target bit sequence are set to NACK. When the terminal enables CBG-based HARQ transmission, 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 in the target bit sequence is equal to the sum of the first target value and the second target value, the first target value is equal to the product of the value of the third sub-DAI and the second value, the second target value is equal to the product of the value of the fourth sub-DAI and the third value, and the bits in the target bit sequence are set to NACK. Furthermore, the second value satisfies any one of the following: If the first condition is met, the second value is 2; If the first condition is not met, the second value is 1; The first condition includes: the terminal enables HARQ-ACK spatial binding indication, and a single PDSCH reception corresponds to a maximum of two transport blocks. Furthermore, the third value is determined based on the maximum number of transport blocks that a single DCI can schedule and the maximum number of CBGs that a single transport block can be split into. In practice, the third value can be... For the specific meaning of , please refer to the above description, which will not be repeated here. For scenarios one and two above, optionally, the third PDSCH group satisfies any one of the following: The third PDSCH group is the PDSCH group where the target DCI schedules the PDSCH. The target DCI is the last DCI detected by the terminal used to schedule the PDSCH in the N PDSCH groups. The third PDSCH group is defined by the protocol; The third PDSCH group is configured by the network-side equipment. Regarding the third implementation method mentioned above Optionally, determining the second DAI corresponding to each of the N PDSCH groups based on the first relationship includes: The DAI in the last detected DCI of each of the N PDSCH groups is determined as the second DAI corresponding to that PDSCH group. It should be noted that in this embodiment, for the cases where the first value and the first DAI are equal in the first, third, and second implementations described above, after determining the second DAI corresponding to each PDSCH group in the N physical downlink shared channel (PDSCH) groups, the terminal determines the HARQ-ACK sequence of each PDSCH group in the N PDSCH groups based on the determined N second DAIs in the same way as the "method of determining the HARQ-ACK bit sequence corresponding to each DAI" in the foregoing section. For details, please refer to the foregoing description, which will not be repeated here. It should also be noted that since the dynamic codebook in this embodiment is transmitted on the PUSCH, the parameter harq-ACK-Spatial Bundling PUCCH needs to be replaced with harq-ACK-Spatial Bundling PUSCH. In addition, in this embodiment, when the terminal is configured with only a single serving cell, the DAI in the DCI corresponding to a certain PDSCH group that the terminal last detected is C-DAI; when the terminal is configured with two or more serving cells, the DAI in the DCI corresponding to a certain PDSCH group that the terminal last detected is T-DAI. Referring to Figure 3, which is a flowchart of the HARQ-ACK codebook generation method provided in this application embodiment, the information transmission method of this application embodiment is applied to a network-side device. As shown in Figure 3, the information sending method may include the following steps: Step 301: Send a first downlink control information (DCI) for scheduling the first physical uplink shared channel (PUSCH). The first DCI includes a first DAI, which is used to generate a dynamic codebook transmitted on the first PUSCH. The dynamic codebook contains HARQ-ACK bit sequences of the N physical downlink shared channel (PDSCH) groups, where N is a positive integer. Optionally, the first DAI corresponds to at least one of the N PDSCH groups. Optionally, when N is greater than 1, the first DAI corresponds to the N PDSCH groups; or, the first DAI corresponds to the first PDSCH group among the N PDSCH groups. Optionally, when the first DAI corresponds to the N PDSCH groups, the first DAI is determined based on the sum of the values ​​of the N ninth DAIs; In this context, each of the N PDSCH groups corresponds to a ninth DAI, and each ninth DAI is carried in the third DCI corresponding to its corresponding PDSCH group. The third DCI corresponding to each PDSCH group is the last DCI sent by the network-side device that corresponds to that PDSCH group. In a specific implementation, in one approach, the value of the first DAI can be the sum of the values ​​of N ninth DAIs; in another approach, the value of the first DAI can be obtained by performing a modulo operation on the sum of the N ninth DAIs. Optionally, the first DAI does not correspond to any of the N PDSCH groups. In this case, the first DAI can be set to any value, or to the default value, such as 4. In this embodiment, the information transmission method involves a network-side device sending first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH). The first DCI includes a first dynamic codebook (DAI) used for generating a dynamic codebook transmitted on the first PUSCH. The dynamic codebook contains HARQ-ACK bit sequences from the N physical downlink shared channel (PDSCH) groups, where N is a positive integer. This allows the terminal to generate a dynamic codebook based on the first DAI after receiving it, thereby improving the reliability of the dynamic codebook transmission. It should be noted that this embodiment is an implementation of a network-side device corresponding to the above method embodiments. Therefore, the relevant descriptions in the above method embodiments can be referred to, and the same beneficial effects can be achieved. To avoid repetition, further details will not be provided here. Furthermore, the various optional implementation methods described in the embodiments of this application can be combined with each other or implemented individually, and the embodiments of this application do not limit this. For ease of understanding, the following example is provided: In this embodiment of the application, when a downlink enhanced dynamic codebook is configured for the UE, and only a single UL DAI or a single group exists in the uplink DCI format 0_1, the meaning and application of the UL DAI can adopt one of the following schemes: Option 1: Based on the number of triggering PDSCH packets corresponding to the enhanced dynamic codebooks carried on the PUSCH scheduled by DCI format 0_1 ​​that overlap with the PUSCH in the time domain, the meaning of the UL DAI value in this DCI format 0_1 ​​(i.e., the value of the "1st downlink assignment index" field and / or "2nd downlink assignment index" field in DCI format 0_1) can be determined as follows: When the enhanced dynamic codebook corresponds to only a single triggered PDSCH packet, the UL DAI value corresponds to this single triggered PDSCH packet, and the corresponding HARQ-ACK bit can be determined using operation 2, as described below. When the enhanced dynamic codebook corresponds to more than one triggering PDSCH packet, one of the following methods is adopted: The UL DAI value corresponds to the sum of the DAI of all triggered PDSCH packets (with modulo operation taken into account), or the number of dynamically scheduled PDSCH receive / SPS PDSCH release indications corresponding to the enhanced dynamic codebook carried on the PUSCH (with modulo operation taken into account). The determination of the DAI value or the corresponding HARQ-ACK bit for each PDSCH group can be achieved using operation 1. The UL DAI value corresponds to the most recently scheduled PDSCH packet before the enhanced dynamic codebook transmission. The corresponding HARQ-ACK bit can be determined using operation 2, as described below. The UL DAI value corresponds to a PDSCH packet specified by the protocol or configured by higher-layer parameters, such as the first or second group. The determination of the corresponding HARQ-ACK bit can be done using operation 2. Option 2: In DCI format 0_1, UL DAI is always applied to a single PDSCH packet, regardless of whether the number of PDSCH packets carried on its scheduled PUSCH is greater than 1. This can be achieved using one of the following methods: The UL DAI value corresponds to a PDSCH packet specified by the protocol or configured by higher-layer parameters, such as the first or second group. The determination of the corresponding HARQ-ACK bit can be done using operation 2. The UL DAI value corresponds to the most recently scheduled PDSCH packet before the enhanced dynamic codebook transmission, and the corresponding HARQ-ACK bit can be determined using operation 2. The actual operation of Scheme 1 and Scheme 2 is completely consistent in some cases, with the only difference being the premise assumptions. One distinguishes the number of PDSCH blocks corresponding to the enhanced dynamic codebook and processes them separately, while the other does not distinguish the number of PDSCH blocks. The following explains operations 1 and 2 above. Operation 1: When the UL DAI indicator in DCI format 0_1 ​​is greater than the sum of the DAIs of a single triggering PDSCH packet, or indicates the number of dynamically scheduled PDSCH receive / SPS PDSCH release indicators corresponding to the enhanced dynamic codebook, the DAI value or corresponding HARQ-ACK bit applied to each PDSCH packet can be determined as follows: Step 1: Take the nearest downlink schedule I of each triggering PDSCH packet as DCI format 1_0, then it is C-DAI in this DCI format 1_0; if the nearest downlink schedule DCI is DCI format 1_1, then it is T-DAI in this DCI format 1_1. Calculate the relationship between the sum of C-DAI / T-DAI of each PDSCH packet (considering modulo operation) and UL DAI. If they are equal, it is considered that there is no DCI missed detection, and Step 2 is executed; otherwise, it is considered that a certain PDSCH packet has a DCI missed detection, and Step 3 is executed. When the enhanced dynamic codebook corresponds to N PDSCH packets, assuming that the DAI of each PDSCH packet is DAI1, DAI2, ... DAIN, then the above calculation of the sum of C-DAI / T-DAI of each PDSCH packet (considering modulo operation) DAI_Sum can be expressed as: Here, Round_Size is the modulus of the modulo operation. When DAI uses a 2-bit indicator, Round_Size = 4. Step 2: Based on the C-DAI / T-DAI in the most recent downlink scheduling DCI format 1_0 / 1_1 for each triggering PDSCH packet, determine the number and value of the HARQ-ACK bit sequence corresponding to this PDSCH packet. The operation process of constructing the HARQ-ACK Codebook when carrying on PUCCH can be followed (without involving the use of UL DAI), but the parameter harq-ACK-SpatialBundlingPUCCH is replaced by harq-ACK-SpatialBundlingPUSCH. Step 3: Calculate the DAI difference. Assuming the sum of C-DAI / T-DAI for each PDSCH group (and considering modulo operations) 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 can be understood as the number of missed DCIs, and depending on the application objective, it can be implemented in one of the following ways: Method 1: DAI_Diff is applied to a specific PDSCH packet as specified in the protocol or configured by higher-layer parameters, such as the first or second group. Method 2: DAI_Diff is applied to the PDSCH packet at the very end of the enhanced dynamic codebook where the HARQ-ACK bit sequence is placed. This ensures that at least the other HARQ-ACK bits in the PDSCH packet at the very beginning of the enhanced dynamic codebook, excluding the tail, will not be affected by DCI missed detection. Method 3: DAI_Diff is applied to the most recently scheduled PDSCH packets before the enhanced dynamic codebook transmission. Method 4: DAI_Diff should not be applied to any PDSCH packets, but only to align the size of the HARQ-ACK Codebook on both sides of the UE and eNB, so as to avoid affecting the RE demapping and decoding of UL-SCH. For methods 1, 2, and 3 above, after determining the PDSCH packet to which DAI_Diff is applied, and after determining the HARQ-ACK bit sequence of this PDSCH packet based on the NR Rel-15 procedure (at this time, when determining the HARQ-ACK bit sequence for each PDSCH packet, only the DAI value indicated in the DCI is used, not the UL DAI value), DAI_Diff is then applied to the end of the determined HARQ-ACK bit sequence. The following operations can be used when applying DAI_Diff: If the harq-ACK-SpatialBundlingPUSCH parameter is not configured for the UE, and the maxNrofCodeWordsScheduledByCI parameter is configured for at least one DL BWP of at least one serving cell of the UE to correspond to a maximum of two transport blocks for a single PDSCH reception, then each missing DAI corresponds to 2 HARQ-ACK bits. 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 NACK bits. Otherwise, each missing DAI corresponds to a single HARQ-ACK bit. 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 NACK bits. The above DAI_Diff application operation applies when none of the UE's serving cells have enabled CBG-based HARQ transmission. When certain serving cells of a UE are configured with the parameter PDSCH-CodeBlockGroupTransmission, i.e., CBG-based HARQ transmission is enabled, the HARQ-ACK Codebook of a single PDSCH packet is composed of two concatenated HARQ-ACK sub-codebooks. The first sub-codebook provides HARQ-ACK feedback for the TB (Block Group), and the second sub-codebook provides HARQ-ACK feedback for the CBG. In this case, for TB-level sub-codebooks, DAI_Diff is applied as described above. For CBG-level sub-codebooks, the following operations can be used when applying DAI_Diff: Add to the end of the HARQ-ACK bit sequence determined above. Each bit has a value of '0', corresponding to There are NACKs, of which In response to A serving cell configured with the parameter PDSCH-CodeBlockGroupTransmission The maximum value, The value of the parameter maxNrofCodeWordsScheduledByDCI for serving cell c indicates the maximum number of transport blocks that a single DCI can schedule simultaneously. The value of the parameter maxCodeBlockGroupsPerTransportBlock for serving cell c indicates the maximum number of CBGs that a single transport block can be divided into. For method 4 above, first determine the HARQ-ACK bit sequence of each triggering PDSCH packet (at this time, when determining the HARQ-ACK bit sequence of each PDSCH packet, only the DAI value indicated in the DCI is used, not the UL DAI value), then determine the complete HARQ-ACK Codebook based on the HARQ-ACK bit sequence of each triggering PDSCH packet (for example, concatenate the HARQ-ACK bit sequences of each triggering PDSCH packet in ascending order of group number to obtain the complete HARQ-ACK Codebook), and finally, add alignment bits to the end of the HARQ-ACK Codebook using one of the following operations: When a single triggered PDSCH packet only involves TB-level feedback (i.e., none of the UE's serving cells have configured the parameter PDSCH-CodeBlockGroupTransmission to enable CBG-based HARQ transmission), DAI_DiffTB×Bit_Num_Per_DAITB bits with a value of '0' are added to the end of the HARQ-ACK Codebook. Each bit corresponds to a single NACK, where DAI_DiffTB is 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. In this case, Bit_Num_Per_DAITB is at the TB granularity. When a single triggered PDSCH packet involves CBG-level feedback (i.e., at least one serving cell of the UE is configured with the parameter PDSCH-CodeBlockGroupTransmission to enable CBG-based HARQ transmission), firstly, 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. Here, 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" field), and Bit_Num_Per_DAITB is the number of HARQ-ACK bits corresponding to each DAI, at the TB granularity. Secondly, DAI_DiffCBG × Bit_Num_Per_DAICBG bits with a value of '0' are further added to the end of the HARQ-ACK Codebook, each bit corresponding to a single NACK. Here, DAI_DiffCBG is the DAI_Diff calculated based on the second UL DAI in DCI format 0_1 ​​(indicated by the "2nd downlink assignment" field). The index field indicates that the calculated DAI_Diff is the number of HARQ-ACK bits corresponding to each DAI, and Bit_Num_Per_DAICBG is the CBG granularity. The Bit_Num_Per_DAITB mentioned above can be determined in the following way: If the harq-ACK-SpatialBundlingPUSCH parameter is not configured for the UE, and at least one DL BWP of at least one serving cell of the UE is configured with a maximum of two transport blocks corresponding to a single PDSCH reception through the max Nr of Code Words Scheduled ByDCI parameter, then Bit_Num_Per_DAITB is 2; otherwise, Bit_Num_Per_DAITB is 1. The Bit_Num_Per_DAICBG mentioned above can be determined in the following way: Bit_Num_Per_DAICBG takes the value of The meaning of is explained in the preceding description. Operation 2: When the UL DAI value corresponds to a single PDSCH packet, the operation process of constructing the HARQ-ACK Codebook when carrying it on PUCCH can be followed to determine the HARQ-ACK bit sequence corresponding to this PDSCH packet. When each codebook that triggers a PDSCH packet corresponds to two sub-codebooks, two UL DAI values ​​are included in DCI format 0_1 ​​based on NR Rel-15, corresponding to the first and second sub-codebooks respectively. The above scheme and related methods can be applied to each sub-codebook separately. As shown in Figure 4, there are N PDSCH groups, including PDSCH group 0 and PDSCH group 1. PDSCH group 0 includes two PDSCHs, D1 and D2, and the UE only detects D1 and not D2. PDSCH group 1 includes four PDSCHs, D3, D4, D5 and D6, and the UE only detects D3, D4 and D5 and not D6. In Figure 4, UCI1 transmission fails; the PUCCH and PUSCH for transmitting UCI2 overlap in the time domain, and UCI2 is multiplexed onto the PUSCH for transmission. The DCI located after D6 is used to schedule the PUSCH, and this DCI can indicate UL DAI. In this embodiment of the application, the terminal can use UL DAI to determine the second DAI corresponding to D1, D2, D3, D4, D5 and D6 respectively, and then determine the HARQ-ACK sequence of D1, D2, D3, D4, D5 and D6 according to the second DAI, thereby generating a dynamic codebook and transmitting the dynamic codebook on the PUSCH. In this application embodiment, when a downlink enhanced dynamic codebook is configured for the UE, and only a single UL DAI or a single group exists in the uplink DCI format 0_1, a corresponding solution is proposed for the application of UL DAI to ensure reliable transmission of the HARQ-ACK Codebook and to avoid affecting other data transmissions carried on the PUSCH. Referring to Figure 5, which is one of the structural diagrams of a terminal provided in an embodiment of this application, the terminal 500 includes: The receiving module 501 is configured to receive first downlink control information (DCI) for scheduling the first physical uplink shared channel (PUSCH), wherein the first DCI includes a first DAI. The determining module 502 is used to determine the second DAI corresponding to each PDSCH group in the N physical downlink shared channel PDSCH groups based on the first DAI; The generation module 503 is used to generate a dynamic codebook to be transmitted on the first PUSCH based on the determined N second DAIs. The dynamic codebook contains HARQ-ACK bit sequences of the N PDSCH groups, where N is a positive integer. Optionally, the determining module includes: The first determining submodule is used to determine the first relationship between the first DAI and the N PDSCH groups; The second determining submodule is used to determine the second DAI corresponding to each of the N PDSCH groups based on the first relationship. Optionally, the first relationship satisfies that the first DAI corresponds to at least one of the N PDSCH groups. Optionally, when N is greater than 1, the first relation satisfies any one of the following: The first DAI corresponds to the N PDSCH groups; The first DAI corresponds to the first PDSCH group among the N PDSCH groups, and the first PDSCH group satisfies any one of the following: The first PDSCH group is the PDSCH group where the target DCI schedules the PDSCH. The target DCI is the last DCI detected by the terminal used to schedule the PDSCH in the N PDSCH groups. The first PDSCH group is defined by the protocol; The first PDSCH group is configured by the network-side device. Optionally, when the first DAI corresponds to the first PDSCH group, the second determining submodule is specifically used for: The first DAI is determined to be the second DAI corresponding to the first PDSCH group; The third DAI is identified as the second DAI corresponding to the second PDSCH group; Wherein, the third DAI is the DAI in the DCI that the terminal last detected corresponding to the second PDSCH group; the second PDSCH group is any PDSCH group other than the first PDSCH group among the N PDSCH groups. Optionally, when the first DAI corresponds to the N PDSCH groups, the second determining submodule is specifically used for: The acquisition subunit is used to acquire the fourth DAI in the second DCI corresponding to each of the N PDSCH groups, where the second DCI corresponding to each PDSCH group is the last DCI detected by the terminal that corresponds to that PDSCH group. The comparison unit is used to compare the first value with the value of the first DAI to obtain the corresponding comparison result; wherein, the first value is determined based on the sum of the N values ​​of the fourth DAI obtained; The determining unit is configured to determine the second DAI corresponding to each of the N PDSCH groups based on the comparison results. Optionally, the determining unit includes: The first determining subunit is used to determine the fifth DAI when the first value is not equal to the value of the first DAI. The fifth DAI is used to indicate the number of missed DCIs for scheduling the N PDSCH groups. The second determining subunit is used to determine the second DAI corresponding to each PDSCH group among the N PDSCH groups based on the fifth DAI. Optionally, if the terminal has not enabled HARQ transmission based on code block group (CBG), the second determining subunit is specifically used for any of the following: When the fifth DAI corresponds to the third PDSCH group among the N PDSCH groups, the second DAI corresponding to the third PDSCH group is determined based on the fifth DAI and the sixth DAI, and the seventh DAI is determined as the second DAI corresponding to the fourth PDSCH group. If the fifth DAI does not correspond to any of the N PDSCH groups, the DAI in the last detected DCI corresponding to each of the N PDSCH groups is determined as the second DAI corresponding to that PDSCH group. Wherein, the sixth DAI is the DAI in the DCI corresponding to the third PDSCH group that was last detected by the terminal, and the seventh DAI is the DAI in the DCI corresponding to the fourth PDSCH group that was last detected by the terminal; the third PDSCH group is any one of the N PDSCH groups, and the fourth PDSCH group is any one of the N PDSCH groups other than the third PDSCH group. Optionally, the HARQ-ACK bit sequence of the third PDSCH group includes a first bit sequence and a second bit sequence concatenated in sequence; The first bit sequence is determined based on the sixth DAI, and the second bit sequence is determined based on the fifth DAI. Optionally, the second bit sequence satisfies any one of the following: If the first condition is met, the number of bits in the second bit sequence is twice the value of the fifth DAI, and the bits in the second bit sequence are set to negative acknowledgment (NACK). If the first condition is not met, the number of bits in the second bit sequence is equal to the value of the fifth DAI, and the bits of the second bit sequence are set to NACK. The first condition includes: the terminal enables HARQ-ACK spatial binding indication, and a single PDSCH reception corresponds to a maximum of two transport blocks. Optionally, when the terminal enables HARQ transmission based on code block group (CBG); the second determining subunit is specifically used for any one of the following: When the fifth DAI corresponds to the third PDSCH group among the N PDSCH groups, the second DAI corresponding to the third PDSCH group is determined according to the first sub-DAI, the second sub-DAI, the third sub-DAI and the fourth sub-DAI, and the seventh DAI is determined as the second DAI corresponding to the fourth PDSCH group. If the fifth DAI does not correspond to any of the N PDSCH groups, the DAI in the last detected DCI corresponding to each of the N PDSCH groups is determined as the second DAI corresponding to that PDSCH group. The fifth DAI includes the first sub-DAI corresponding to the transport block (TB) granularity and the second sub-DAI corresponding to the CBG granularity; the third sub-DAI is the DAI in the first type DCI last detected by the terminal corresponding to the third PDSCH group; the fourth sub-DAI is the DAI in the second type DCI last detected by the terminal corresponding to the third PDSCH group; and the seventh DAI is the DAI in the DCI last detected by the terminal corresponding to the fourth PDSCH group. The PDSCH scheduled by the first type DCI is based on TB granularity feedback HARQ-ACK, and the PDSCH scheduled by the second type DCI is based on CBG granularity feedback HARQ-ACK. The third PDSCH group is any one of the N PDSCH groups, and the fourth PDSCH group is any PDSCH group other than the third PDSCH group among the N PDSCH groups. 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 concatenated in sequence; 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. Optionally, the fourth bit sequence satisfies any one of the following: If the first condition is met, the number of bits in the fourth bit sequence is twice the value of the first sub-DAI, and the bits in the fourth bit sequence are set to negative acknowledgment (NACK). If the first condition is not met, the number of bits in the fourth bit sequence is equal to the value of the first sub-DAI, and the bits of the fourth bit sequence are set to NACK. The first condition includes: the terminal enables HARQ-ACK spatial binding indication, and a single PDSCH reception corresponds to a maximum of two transport blocks. Optionally, the sixth bit sequence satisfies: The number of bits in the sixth bit sequence is equal to the product of the value of the second sub-DAI and the fourth value, and the bits in the sixth bit sequence are set to NACK; The fourth value is determined based on the maximum number of transport blocks that a single DCI can schedule and the maximum number of CBGs that a single transport block can be split into. Optionally, the third PDSCH group satisfies any one of the following: The third PDSCH group is the PDSCH group where the target DCI schedules the PDSCH. The target DCI is the last DCI detected by the terminal used to schedule the PDSCH in the N PDSCH groups. The third PDSCH group is defined by the protocol; The third PDSCH group is configured by the network-side equipment. Optionally, if the fifth DAI does not correspond to any of the N PDSCH groups, the generation module is specifically used for: Based on the fifth DAI and the determined N second DAIs, a dynamic codebook is generated for transmission on the first PUSCH. Optionally, the generation module is specifically used for: Generate the target bit sequence based on the fifth DAI; Wherein, the target bit sequence satisfies any one of the following: When the terminal does not enable CBG-based HARQ transmission, the number of bits in the target bit sequence is equal to the product of the value of the fifth DAI and the second value, and the bits in the target bit sequence are set to NACK. When the terminal enables CBG-based HARQ transmission, 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 in the target bit sequence is equal to the sum of the first target value and the second target value, the first target value is equal to the product of the value of the third sub-DAI and the second value, the second target value is equal to the product of the value of the fourth sub-DAI and the third value, and the bits in the target bit sequence are set to NACK. Optionally, the second value satisfies any one of the following: If the first condition is met, the second value is 2; If the first condition is not met, the second value is 1; The first condition includes: the terminal enables HARQ-ACK spatial binding indication, and a single PDSCH reception corresponds to a maximum of two transport blocks. Optionally, the third value is determined based on the maximum number of transport blocks that a single DCI can schedule and the maximum number of CBGs that a single transport block can be split into. Optionally, determining the first relationship between the first DAI and the N PDSCH groups includes: According to preset rules, the first relationship between the first DAI and the N PDSCH groups is determined; The preset rules include at least one of the following: The PDSCH group corresponding to the first DAI is determined based on the PDSCH group where the target DCI is scheduled. The target DCI is the last DCI detected by the terminal used to schedule PDSCH in the N PDSCH groups. The PDSCH group corresponding to the first DAI is determined according to the agreement. The PDSCH group corresponding to the first DAI is determined based on the configuration information of the network-side device. Optionally, the first relationship satisfies any one of the following: The first DAI corresponds to the 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. Optionally, when the first DAI corresponds to the fifth PDSCH group among the N PDSCH groups, the second determining submodule is specifically used for: The first DAI is determined to be the second DAI corresponding to the fifth PDSCH group; The eighth DAI is identified as the second DAI corresponding to the sixth PDSCH group; Wherein, the eighth DAI is the DAI in the DCI that the terminal last detected corresponding to the sixth PDSCH group; the sixth PDSCH group is any PDSCH group other than the fifth PDSCH group among the N PDSCH groups. Terminal 500 can implement all the processes that the terminal can implement in the method embodiments of this application, and achieve the same beneficial effects. To avoid repetition, it will not be described again here. Referring to Figure 6, which is one of the structural diagrams of a network-side device provided in an embodiment of this application, the network-side device 300 includes: The transmitting module 601 is used to transmit first downlink control information (DCI) for scheduling the first physical uplink shared channel (PUSCH), the first DCI including a first DAI, the first DAI being used for generating a dynamic codebook transmitted on the first PUSCH. The dynamic codebook contains HARQ-ACK bit sequences of N Physical Downlink Shared Channel (PDSCH) groups, where N is a positive integer. Optionally, the first DAI corresponds to at least one of the N PDSCH groups. Optionally, when N is greater than 1, the first DAI corresponds to the N PDSCH groups; or, the first DAI corresponds to the first PDSCH group among the N PDSCH groups. Optionally, when the first DAI corresponds to the N PDSCH groups, the first DAI is determined based on the sum of the values ​​of the N ninth DAIs; In this context, each of the N PDSCH groups corresponds to a ninth DAI, and each ninth DAI is carried in the third DCI corresponding to its corresponding PDSCH group. The third DCI corresponding to each PDSCH group is the last DCI sent by the network-side device that corresponds to that PDSCH group. Optionally, the first DAI does not correspond to any of the N PDSCH groups. The network-side device 600 can implement all the processes that the network-side device in the method embodiments of this application can implement, and achieve the same beneficial effects. To avoid repetition, it will not be described again here. Please refer to Figure 7, which is a second structural diagram of a terminal provided in an embodiment of this application. This terminal can be a hardware structure diagram of a terminal implementing various embodiments of this application. As shown in Figure 7, the terminal 700 includes, but is not limited to, components such as: 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. Those skilled in the art will understand that the terminal structure shown in Figure 7 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements. In the embodiments of this application, the terminal includes, but is not limited to, mobile phones, tablet computers, laptop computers, PDAs, vehicle terminals, wearable devices, and pedometers. The radio frequency unit 701 is configured to: receive first downlink control information (DCI) for scheduling the first physical uplink shared channel (PUSCH), wherein the first DCI includes a first DAI; Processor 710, used for: Based on the first DAI, determine the second DAI corresponding to each PDSCH group in the N physical downlink shared channel PDSCH groups; Based on the determined N second DAIs, a dynamic codebook is generated for transmission on the first PUSCH; The dynamic codebook contains HARQ-ACK bit sequences of the N PDSCH groups, where N is a positive integer. Optionally, the processor 710 is also used for: Determine the first relationship between the first DAI and the N PDSCH groups; Based on the first relationship, determine the second DAI corresponding to each of the N PDSCH groups. Optionally, the first relationship satisfies that the first DAI corresponds to at least one of the N PDSCH groups. Optionally, when N is greater than 1, the first relation satisfies any one of the following: The first DAI corresponds to the N PDSCH groups; The first DAI corresponds to the first PDSCH group among the N PDSCH groups, and the first PDSCH group satisfies any one of the following: The first PDSCH group is the PDSCH group where the target DCI schedules the PDSCH. The target DCI is the last DCI detected by the terminal used to schedule the PDSCH in the N PDSCH groups. The first PDSCH group is defined by the protocol; The first PDSCH group is configured by the network-side device. Optionally, when the first DAI corresponds to the first PDSCH group, the processor 710 is further configured to: The first DAI is determined to be the second DAI corresponding to the first PDSCH group; The third DAI is identified as the second DAI corresponding to the second PDSCH group; Wherein, the third DAI is the DAI in the DCI that the terminal last detected corresponding to the second PDSCH group; the second PDSCH group is any PDSCH group other than the first PDSCH group among the N PDSCH groups. Optionally, when the first DAI corresponds to the N PDSCH groups, the processor 710 is further configured to: Obtain the fourth DAI in the second DCI corresponding to each of the N PDSCH groups, where the second DCI corresponding to each PDSCH group is the last DCI detected by the terminal that corresponds to that PDSCH group. The first value is compared with the value of the first DAI to obtain the corresponding comparison result; wherein, the first value is determined based on the sum of the N values ​​of the fourth DAI obtained; Based on the comparison results, the second DAI corresponding to each of the N PDSCH groups is determined. Optionally, the processor 710 is also used for: If the first value is not equal to the first DAI, a fifth DAI is determined, which is used to indicate the number of missed DCIs for scheduling the N PDSCH groups. Based on the fifth DAI, determine the second DAI corresponding to each of the N PDSCH groups. Optionally, if the terminal does not enable HARQ transmission based on code block group (CBG), the processor 710 is further configured to: [list of options]. When the fifth DAI corresponds to the third PDSCH group among the N PDSCH groups, the second DAI corresponding to the third PDSCH group is determined based on the fifth DAI and the sixth DAI, and the seventh DAI is determined as the second DAI corresponding to the fourth PDSCH group. If the fifth DAI does not correspond to any of the N PDSCH groups, the DAI in the last detected DCI corresponding to each of the N PDSCH groups is determined as the second DAI corresponding to that PDSCH group. Wherein, the sixth DAI is the DAI in the DCI corresponding to the third PDSCH group that was last detected by the terminal, and the seventh DAI is the DAI in the DCI corresponding to the fourth PDSCH group that was last detected by the terminal; the third PDSCH group is any one of the N PDSCH groups, and the fourth PDSCH group is any one of the N PDSCH groups other than the third PDSCH group. Optionally, the HARQ-ACK bit sequence of the third PDSCH group includes a first bit sequence and a second bit sequence concatenated in sequence; The first bit sequence is determined based on the sixth DAI, and the second bit sequence is determined based on the fifth DAI. Optionally, the second bit sequence satisfies any one of the following: If the first condition is met, the number of bits in the second bit sequence is twice the value of the fifth DAI, and the bits in the second bit sequence are set to negative acknowledgment (NACK). If the first condition is not met, the number of bits in the second bit sequence is equal to the value of the fifth DAI, and the bits of the second bit sequence are set to NACK. The first condition includes: the terminal enables HARQ-ACK spatial binding indication, and a single PDSCH reception corresponds to a maximum of two transport blocks. Optionally, when the terminal enables HARQ transmission based on code block group (CBG), the processor 710 is further configured to: [list of configurations]. When the fifth DAI corresponds to the third PDSCH group among the N PDSCH groups, the second DAI corresponding to the third PDSCH group is determined according to the first sub-DAI, the second sub-DAI, the third sub-DAI and the fourth sub-DAI, and the seventh DAI is determined as the second DAI corresponding to the fourth PDSCH group. If the fifth DAI does not correspond to any of the N PDSCH groups, the DAI in the last detected DCI corresponding to each of the N PDSCH groups is determined as the second DAI corresponding to that PDSCH group. The fifth DAI includes the first sub-DAI corresponding to the transport block (TB) granularity and the second sub-DAI corresponding to the CBG granularity; the third sub-DAI is the DAI in the first type DCI last detected by the terminal corresponding to the third PDSCH group; the fourth sub-DAI is the DAI in the second type DCI last detected by the terminal corresponding to the third PDSCH group; and the seventh DAI is the DAI in the DCI last detected by the terminal corresponding to the fourth PDSCH group. The PDSCH scheduled by the first type DCI is based on TB granularity feedback HARQ-ACK, and the PDSCH scheduled by the second type DCI is based on CBG granularity feedback HARQ-ACK. The third PDSCH group is any one of the N PDSCH groups, and the fourth PDSCH group is any PDSCH group other than the third PDSCH group among the N PDSCH groups. 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 concatenated in sequence; 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. Optionally, the fourth bit sequence satisfies any one of the following: If the first condition is met, the number of bits in the fourth bit sequence is twice the value of the first sub-DAI, and the bits in the fourth bit sequence are set to negative acknowledgment (NACK). If the first condition is not met, the number of bits in the fourth bit sequence is equal to the value of the first sub-DAI, and the bits of the fourth bit sequence are set to NACK. The first condition includes: the terminal enables HARQ-ACK spatial binding indication, and a single PDSCH reception corresponds to a maximum of two transport blocks. Optionally, the sixth bit sequence satisfies: The number of bits in the sixth bit sequence is equal to the product of the value of the second sub-DAI and the fourth value, and the bits in the sixth bit sequence are set to NACK; The fourth value is determined based on the maximum number of transport blocks that a single DCI can schedule and the maximum number of CBGs that a single transport block can be split into. Optionally, the third PDSCH group satisfies any one of the following: The third PDSCH group is the PDSCH group where the target DCI schedules the PDSCH. The target DCI is the last DCI detected by the terminal used to schedule the PDSCH in the N PDSCH groups. The third PDSCH group is defined by the protocol; The third PDSCH group is configured by the network-side equipment. Optionally, if the fifth DAI does not correspond to any of the N PDSCH groups, the processor 710 is further configured to: Based on the fifth DAI and the determined N second DAIs, a dynamic codebook is generated for transmission on the first PUSCH. Optionally, the processor 710 is also used for: Generate the target bit sequence based on the fifth DAI; Wherein, the target bit sequence satisfies any one of the following: When the terminal does not enable CBG-based HARQ transmission, the number of bits in the target bit sequence is equal to the product of the value of the fifth DAI and the second value, and the bits in the target bit sequence are set to NACK. When the terminal enables CBG-based HARQ transmission, 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 in the target bit sequence is equal to the sum of the first target value and the second target value, the first target value is equal to the product of the value of the third sub-DAI and the second value, the second target value is equal to the product of the value of the fourth sub-DAI and the third value, and the bits in the target bit sequence are set to NACK. Optionally, the second value satisfies any one of the following: If the first condition is met, the second value is 2; If the first condition is not met, the second value is 1; The first condition includes: the terminal enables HARQ-ACK spatial binding indication, and a single PDSCH reception corresponds to a maximum of two transport blocks. Optionally, the third value is determined based on the maximum number of transport blocks that a single DCI can schedule and the maximum number of CBGs that a single transport block can be split into. Optionally, the processor 710 is also used for: According to preset rules, the first relationship between the first DAI and the N PDSCH groups is determined; The preset rules include at least one of the following: The PDSCH group corresponding to the first DAI is determined based on the PDSCH group where the target DCI is scheduled. The target DCI is the last DCI detected by the terminal used to schedule PDSCH in the N PDSCH groups. The PDSCH group corresponding to the first DAI is determined according to the agreement. The PDSCH group corresponding to the first DAI is determined based on the configuration information of the network-side device. Optionally, the first relationship satisfies any one of the following: The first DAI corresponds to the 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. Optionally, when the first DAI corresponds to the fifth PDSCH group among the N PDSCH groups, determining the second DAI corresponding to each PDSCH group among the N PDSCH groups according to the first relationship includes: The first DAI is determined to be the second DAI corresponding to the fifth PDSCH group; The eighth DAI is identified as the second DAI corresponding to the sixth PDSCH group; Wherein, the eighth DAI is the DAI in the DCI that the terminal last detected corresponding to the sixth PDSCH group; the sixth PDSCH group is any PDSCH group other than the fifth PDSCH group among the N PDSCH groups. It should be noted that the terminal 700 described above in this embodiment can implement the various processes in the method embodiments of this application and achieve the same beneficial effects. To avoid repetition, it will not be described again here. It should be understood that, in this embodiment, the radio frequency unit 701 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink data from the base station and processes it with the processor 710; additionally, it transmits uplink data to the base station. Typically, 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. Furthermore, the radio frequency unit 701 can also communicate with networks and other devices through a wireless communication system. The terminal provides users with wireless broadband internet access through the network module 702, such as helping users send and receive emails, browse web pages, and access streaming media. 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 audio signals and output them as sound. Furthermore, the audio output unit 703 can also provide audio output related to specific functions performed by the terminal 700 (e.g., call signal reception sound, message reception sound, etc.). The audio output unit 703 includes a speaker, a buzzer, and a receiver, etc. Input unit 704 is used to receive audio or video signals. Input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042. The GPU 7041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on display unit 706. The image frames processed by GPU 7041 can be stored in memory 709 (or other storage medium) or transmitted via radio frequency unit 701 or network module 702. Microphone 7042 can receive sound and process such sound into audio data. The processed audio data can be converted into a format that can be transmitted to a mobile communication base station via radio frequency unit 701 in telephone call mode. The terminal 700 also 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. The ambient light sensor can adjust the brightness of the display panel 7061 according to the ambient light level, and the proximity sensor can turn off the display panel 7061 and / or 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 various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity and can be used to identify the terminal's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. The sensor 705 may also include a fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared sensor, etc., which will not be described in detail here. The display unit 706 is used to display information input by the user or information provided to the user. The display unit 706 may include a display panel 7061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like. User input unit 707 can be used to receive input numerical or character information, and generate key signal inputs related to user settings and function control of the terminal. Specifically, user input unit 707 includes a touch panel 7071 and other input devices 7072. Touch panel 7071, also known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 7071). Touch panel 7071 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to the processor 710, which receives and executes commands from the processor 710. In addition, touch panel 7071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. Besides touch panel 7071, user input unit 707 may also include other input devices 7072. Specifically, other input devices 7072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, joysticks, etc., which will not be described in detail here. Furthermore, the touch panel 7071 can cover the display panel 7061. When the touch panel 7071 detects a touch operation on or near it, it transmits the information to the processor 710 to determine the type of touch event. Subsequently, the processor 710 provides corresponding visual output on the display panel 7061 according to the type of touch event. Although in Figure 7, the touch panel 7071 and the display panel 7061 are shown as two separate components to implement the input and output functions of the terminal, in some embodiments, the touch panel 7071 and the display panel 7061 can be integrated to implement the input and output functions of the terminal. Specific details are not limited here. Interface unit 708 serves as an interface for connecting external devices to terminal 700. For example, external devices may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, and so on. Interface unit 708 can be used to receive input from external devices (e.g., data, power, etc.) and transmit the received input to one or more elements within terminal 700, or it can be used to transmit data between terminal 700 and external devices. The memory 709 can be used to store software programs and various data. The memory 709 may primarily include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). Furthermore, the memory 709 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. The processor 710 is the control center of the terminal, connecting various parts of the terminal through various interfaces and lines. It performs various functions and processes data by running or executing software programs and / or modules stored in the memory 709, and by calling data stored in the memory 709, thereby providing overall monitoring of the terminal. The processor 710 may include one or more processing units; optionally, the processor 710 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the aforementioned modem processor may also not be integrated into the processor 710. The terminal 700 may also include a power supply 711 (such as a battery) that supplies power to various components. Optionally, the power supply 711 may be logically connected to the processor 710 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. In addition, terminal 700 includes some functional modules not shown, which will not be described in detail here. Optionally, this application embodiment also provides a terminal, including a processor 710, a memory 709, and a computer program stored in the memory 709 and executable on the processor 710. When the computer program is executed by the processor 710, it implements the various processes of the above-described HARQ-ACK codebook generation method embodiment and achieves the same technical effect. To avoid repetition, it will not be described again here. Referring to Figure 8, which is a second structural diagram of the network-side device provided in the embodiments of this application, the network-side device 800 includes: a processor 801, a memory 802, a user interface 803, a transceiver 804, and a bus interface. In this embodiment, the network-side device 800 further includes a computer program stored in a memory 802 and executable on a processor 801. When executed by the processor 801, the computer program performs the following steps: Send a first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH), the first DCI including a first DAI for generating a dynamic codebook transmitted on the first PUSCH; The dynamic codebook contains HARQ-ACK bit sequences of N Physical Downlink Shared Channel (PDSCH) groups, where N is a positive integer. Optionally, the first DAI corresponds to at least one of the N PDSCH groups. Optionally, the first DAI corresponds to the N PDSCH groups; or, the first DAI corresponds to the first PDSCH group among the N PDSCH groups. Optionally, when the first DAI corresponds to the N PDSCH groups, the first DAI is determined based on the sum of the values ​​of the N ninth DAIs; In this configuration, each of the N PDSCH groups corresponds to a ninth DAI, and each ninth DAI is carried in the third DCI corresponding to its corresponding PDSCH group. The third DCI corresponding to each PDSCH group is the last DCI sent by the network-side device corresponding to that PDSCH group. Optionally, the first DAI does not correspond to any of the N PDSCH groups. In Figure 8, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 801 and memory represented by memory 802. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. Transceiver 804 may be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium. For different user equipment, user interface 803 may also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc. The processor 801 is responsible for managing the bus architecture and general processing, while the memory 802 can store the data used by the processor 2601 when performing operations. Optionally, when the computer program is executed by the processor 801, it may also perform the following steps: The network-side device 800 can implement the various processes implemented by the network-side device in the above method embodiments, and will not be described again here to avoid repetition. This application also provides a computer-readable storage medium storing a computer program. When executed by a processor, this computer program implements the various processes of the above-described HARQ-ACK codebook generation method embodiments or information transmission method embodiments, and achieves the same technical effect. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc. It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application. The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

The method for generating HARQ-ACK code breaks, accepting hybrid automatic repetition requests, applied to the terminal, where the method incorporates: receiving downlink control information DCI I, which is used for scheduling the PUSCH channel sharing the first physical uplink, where DCI I incorporates DAI I; configuration, which is based on DAI I, DAI II corresponding to each N group of PDSCH physical downlink sharing channels; and creation, which is based on N of the configured DAI II, dynamic code breaks to be transmitted on PUSCH I, where the dynamic code break incorporates the HARQ-ACK bit sequence of the NPDSCH group, and N is a positive integer.

2. The method according to claim 1, where the configuration, which is based on DAI I, DAI II corresponding to each N group of PDSCH physical downlink sharing channels, incorporates: configuring the relationship I between DAI I and the NPDSCH group; and the configuration, which is based on the relationship I,The first DAI corresponds to each NPDSCH group.

3. Method according to claim 2, where the first relation is based on that the first DAI corresponds to at least one of the NPDSCH groups. Method according to claim 3, where in the case that N equals 1, the first relation is based on that the value of the first DAI corresponds to one activated PDSCH group.

5. Method according to claim 3, where in the case that N is greater than 1, the first relation is based on one of the following: the first DAI corresponds to an NPDSCH group; or the first DAI corresponds to the first PDSCH group of an NPDSCH group, where the first PDSCH group is based on one of the following: the first PDSCH group is the PDSCH group in which the PDSCH scheduled by the DCI target pattern is located; where the DCI target pattern is the last one detected by the terminal and used for PDSCH scheduling; in one of the NPDSCH groups; the first PDSCH group is determined by the protocol; or the first PDSCH group is structured by the network side machine. Method according to claim 5, where in the case that the first DAI corresponds to the first PDSCH group,The configuration, which is based on the first relation, the second DAI corresponds to each NPDSCH group comprised of: the configuration of the first DAI to the second DAI corresponds to the first PDSCH group; and the configuration of the third DAI to the second DAI corresponds to the second PDSCH group, where the third DAI is the DAI in the DCI which is finally detected by the terminal and which corresponds to the second PDSCH group, and the second PDSCH group is anything of the NPDSCH group other than the first PDSCH group. The method according to claim 5, where in the case that the first DAI corresponds to the NPDSCH group, the configuration, which is based on the first relation, the second DAI corresponds to each NPDSCH group comprised of: obtaining the fourth DAI in the second DCI which corresponds to each NPDSCH group, where the second DCI PDSCH8 corresponds to each PDSCH group as the DCI which is finally detected by the terminal and which corresponds to the PDSCH group; comparing the first value with the value of the first DAI to obtain the corresponding comparison result, where the first value is determined which is based on the sum of the values ​​of the four obtained NDAIs; and the configuration, which is based on the comparison result,The second DAI corresponds to each group N in the method according to claim 7, whereby the configuration, which is based on the comparison results, the second DAI corresponds to each group NPDSCH comprised: in the case that the first value is not equal to the value of the first DAI, the configuration of the fifth DAI, where the fifth DAI is used to indicate the number of DCI components that were missed in detection and which are used for scheduling PDSCH in the NPDSCH group; and the configuration, which is based on the fifth DAI, the second DAI corresponds to each group NPDSCH 9. The method according to claim 8, whereby In the event that the terminal does not enable HARQ signaling based on CBG code block groups, the configuration, which is based on the fifth DAI, the second DAI corresponding to each NPDSCH group comprises one of the following: in the event that the fifth DAI corresponds to the third PDSCH group of the NPDSCH group, the configuration, which is based on the fifth and sixth DAIs, the second DAI corresponds to the third PDSCH group, and the seventh DAI configuration is based on the second DAI corresponding to the fourth PDSCH group; or in the event that the fifth DAI does not correspond to any of the NPDSCH groups,The DAI in DCI that was last detected and which corresponds to each NPDSCH group is the second DAI corresponding to the PDSCH group, where the sixth DAI is the DAI in DCI that was last detected by the terminal and which corresponds to the third PDSCH group, the seventh DAI is the DAI in DCI that was last detected by the terminal and which corresponds to the fourth PDSCH group, the third PDSCH group is one of the NPDSCH groups, and the fourth PDSCH group is one of the NPDSCH groups other than the third PDSCH group.

10. The method according to claim 9, where the HARQ-ACK bit sequence of the third PDSCH group is incorporated with the first and second bit sequences that are respectively contaminated, where the first bit sequence is configured based on the sixth DAI, and the second bit sequence is configured based on the fifth DAI.

11. The method according to claim 10, where the second bit sequence satisfies one of the following: in the case that condition one is fulfilled, the number of bits incorporated into the second bit sequence is twice the value of the fifth DAI,And each bit of the second bit sequence is set to negative NACK acceptance: or in the case that the first condition is not performed, the number of bits incorporated into the second bit sequence is equal to the value of the fifth DAI. And each bit of the second bit sequence is set to NACK, in which the first condition is incorporated: spatial grouping is enabled and one PDSCH reception corresponds to a maximum of two transport blocks12. Method according to claim 8, in the case that the terminal is performing a HARO signal based on the CBG group code block, the configuration, which is based on the fifth DAI, the second DAI corresponds to each NPDSCH group composed of one of the following: in the case that the fifth DAI corresponds to the third PDSCH group of the NPDSCH group, the configuration, which is based on the first sub-DAI, the second sub-DAI, the third sub-DAI, and the fourth sub-DAI, the second DAI corresponds to the third PDSCH group, and the seventh DAI configuration is the second DAI corresponding to the fourth PDSCH group: or in the case that the fifth DAI does not correspond to any of the NPDSCH groups,The DAI configuration in DCI, which was last detected and corresponds to each NPDSCH group, is as follows: the second DAI corresponds to the PDSCH group; the fifth DAI comprises the first DAI-subcontractor corresponding to the TB granularity transport block and the second DAI-subcontractor corresponding to the CBG granularity block; the third DAI-subcontractor is the DAI in DCI type 1 that was last detected by the terminal and corresponds to the third PDSCH group; the fourth DAI-subcontractor is the DAI in DCI type 2 that was last detected by the terminal and corresponds to the third PDSCH group; and the seventh DAI is the DAI in DCI. I, which is finally detected by the terminal and which corresponds to the fourth PDSCH group, PDSCH scheduled by DCI type 1 HARQ-ACK feedback based on TB granularity, PDSCH scheduled by DCI type 2 HARQ-ACK feedback based on CBG granularity, the third PDSCH group is one of the NPDSCH groups, and the fourth PDSCH group is one of the NPDSCH groups other than the third PDSCH group.

13. The method according to claim 12, where the HARQ-ACK bit sequence of the third PDSCH group is composed of the third bit sequence, the fourth bit sequence, the fifth bit sequence,And the sixth bit sequence is contaminated in sequence, where the third bit sequence is configured based on the third sub-DA1, the fourth bit sequence is configured based on the first sub-DA1, the fifth bit sequence is configured based on the fourth sub-DAI, and the sixth bit sequence is configured based on the second sub-DA1.

14. Method according to claim 13, where the fourth bit sequence satisfies one of the following: in the case that condition one is fulfilled, the number of bits incorporated into the fourth bit sequence is twice that of the first sub-DAI, and the bits of the fourth bit sequence are set to negative NACK acceptance; or in the case that condition one is not fulfilled, the number of bits incorporated into the fourth bit sequence is equal to that of the first sub-DA1, and the bits of the fourth bit sequence are set to NACK, in which condition one is incorporated: the terminal is used to use spatial HARQ-ACK bundle indication and one PDSCH receiver corresponds to a maximum of two transport blocks.

15. Method according to claim 13,Where the sixth bit sequence is as follows: the number of bits incorporated into the sixth bit sequence is equal to the product of the values ​​of the second sub-DA1 and the fourth value. And the bits of the sixth bit sequence are set to NACK, where the fourth value is assigned a value based on the largest number of transport blocks that can be scheduled by one piece of DCI and the largest number of CBGs into which one transport block can be separated.

16. Method according to claim 9 or 12, where the third PDSCH group is as follows: the third PDSCH group is the PDSCH group in which the PDSCH scheduled by the target DCI format is located, where the target DCI format is the last one detected by the terminal and used for PDSCH scheduling in one of the NPDSCH groups; the third PDSCH group is assigned by the protocol; or the third PDSCH group is structured by the network side machine.

17. Method according to claim 9 or 12, where in the case that the fifth DAI does not conform to one of the NPDSCH groups, the construct, which is based on N of the second DAIs assigned,The dynamic code break to be transmitted on PUSCH 1 consists of: a construct, which is based on DAI 5 and N of the second DAI 2 values, dynamic code break to be transmitted on PUSCH 11.

18. The method according to claim 17, in which the construct, which is based on DAI 5 and N of the second DAI 2 values, dynamic code break to be transmitted on PUSCH 1 consists of: a target bit sequence construct, which is based on DAI 5, in which the target bit sequence satisfies one of the following: in the case that the terminal cannot transmit a HARQ signal based on CBG, the number of bits incorporated into the target bit sequence is equal to the product of the value of DAI 5 and the second value, and the bits of the target bit sequence are set to NACK; or in the case that the terminal can transmit a HARQ signal based on CBG, DAI 5 consists of DA1-sub-third corresponding to the granularity TB and DA1-sub-four corresponding to the granularity CBG, the number of bits incorporated into the target bit sequence is equal to the sum of the target value 1 and the target value 2,The first target value is equal to the product of the values ​​of the third and second DAI sub-values; the second target value is equal to the product of the values ​​of the fourth and third DAI sub-values; and the bits of the target bit sequence are set to NACK19. Method according to claim 18, where the second value is 'according to one of the following:' in the case that condition one is met, the value of the second value is 2; or in the case that condition one is not met, the value of the second value is 1; where condition one is included: the terminal is using spatial HARQ-ACK bundle indication and one PDSCH receiver corresponds to a maximum of two transport blocks20. Method according to claim 18, where the third value is determined which is based on the maximum number of transport blocks that can be scheduled by one piece of DCI and the maximum number of CBGs into which one transport block can be separated21. Method according to claim 2, where the first relation between the first DAI and the NPDSCH group is included: the first relation between the first DAI and the NPDSCH group is determined according to a predefined rule;Where the predefined rule comprises at least one of the following: a configuration, which is based on the PDSCH group in which the PDSCH scheduled by the target DCI format is located, the PDSCH group corresponding to DAI I, in which the target DCI format is the last one detected by the terminal and used for PDSCH scheduling, is located in one of the NPDSCH groups; a configuration, which is based on the protocol, the PDSCH group corresponding to DAI I; or a configuration, which is based on the network-side machine's structuring information, the PDSCH group corresponding to DAI I.

22. The method according to claim 21, where the first relationship is based on one of the following: DAI I corresponds to the fifth PDSCH group of the NPDSCH group, in which the fifth PDSCH group is one of the NPDSCH groups; or DAI I does not correspond to one of the NPDSCH groups.

23. The method according to claim 22, where in the case that DAI I corresponds to the fifth PDSCH group of the NPDSCH group, the configuration, which is based on the first relationship,The second DAI corresponds to each NPDSCH group: the configuration of the first DAI as the second DAI corresponds to the fifth PDSCH group; and the configuration of the eighth DAI as the second DAI corresponds to the sixth PDSCH group, where the eighth DAI is the DAI in the DCI that is finally detected by the terminal and which corresponds to the sixth PDSCH group, and the sixth PDSCH group is something of the NPDSCH group other than the fifth PDSCH group information transmission method, which is applied to the network side machine, where the method is assembled: DCI downlink control information transmission. One method is used for scheduling the PUSCH channel that shares the first physical uplink, where the first DCI is incorporated with the first DAI, and the first DAI is used for constructing a dynamic code break to be transmitted on the first PUSCH, where the dynamic code break is incorporated with the HARQ-ACK bit sequence of N groups of the PDSCH channel that shares the first physical downlink, and N is a positive integer 25. Method according to claim 24, where the first DAI corresponds to at least one of the NPDSCH26 groups. Method according to claim 25, where in the case that N is greater than 1,The value of the first DAI corresponds to one PDSCH group that stimulates it.

27. According to claim 25, where N is greater than 1, the first DAI corresponds to an NPDSCH group, or the first DAI corresponds to the first PDSCH group of an NPDSCH group, and the first PDSCH group is one of the NPDSCH groups.

28. According to claim 27, where N is greater than 1, the first DAI is assigned a value based on the sum of the values ​​of the nine NDAIs, where each NPDSCH group corresponds to one ninth DAI, and each ninth .... The third DCI corresponds to the PDSCH group, which corresponds to the ninth DAI, and the third DCI corresponding to each PDSCH group is the DCI that receives the final signal by the network side machine and which corresponds to the PDSCH29 group. According to claim 24, the first DAI does not correspond to anything of the NPDSCH30 group. The terminal, which comprises: a receiving module, which is structured to receive the first DCI downlink control information used for scheduling the PUSCH channel that shares the first physical uplink;Where the first CI comprises the first DAI: the configuration module, which is structured to configure, based on the first DAI, the second DAI corresponds to each of the N groups of PDSCH physical downlink shared channels; and the creation module, which is structured to create, based on the N of the second DAIs configured, dynamic code breaks to be transmitted on PUSCH one, where the dynamic code break comprises the HARQ-ACK bit sequence of the NPDSCH groups, and N is a positive integer 31. The network side machine, where the network side machine comprises: the signaling module, which is structured to transmit downlink control information DCI one used for scheduling the PUSCH channels that share the first physical uplink, where DCI one comprises the first DAI, and the first DAI is used for creating any dynamic code breaks to be transmitted on PUSCH one, where the dynamic code break comprises the HARQ-ACK bit sequence of the N groups of PDSCH physical downlink shared channels, and N is a positive integer 32. The terminal machine, which comprises the processor,Memory and computer programs stored in memory and executable by a processor, where, when the computer program is executed by the processor, the procedure for constructing a HARQ-ACK code book according to one of the claims 1 through 23 is realized.

33. Networked machine, which includes a processor, memory, and computer programs stored in memory and executable by a processor, where, when the computer program is executed by the processor, the procedure for transmitting information according to one of the claims 24 through 29 is realized.

34. Computer-readable storage media, where computer-readable storage media stores computer programs, and when the computer program is executed by the processor, the procedure for constructing a HARQ-ACK code book according to one of the claims 1 through 23 or the procedure for transmitting information according to one of the claims 24 through 29 is realized;

Images