A method and device for transmitting automatic retransmission request confirmation feedback information supporting multicast services

Abstract

A method and apparatus for transmitting automatic repeat request confirmation feedback information supporting multicast services, the method comprising: receiving N first downlink control information (DCI) and M second DCI within at least one first time unit, wherein the first DCI is a first type of DCI and the second DCI is a second type of DCI, each of the first DCIs includes a first downlink allocation index (DAI), the first DAI includes a first downlink allocation index counter (C-DAI), and the first C-DAI indicates the cumulative number of the first type of DCIs scheduled for transmission on a downlink data channel; each of the second DCIs includes a second downlink allocation index (DAI), the second DAI includes a second downlink allocation index counter (C-DAI), and the second C-DAI indicates the cumulative number of the second type of DCIs scheduled for transmission on a downlink data channel; receiving N first downlink data channels and M second downlink data channels within at least one second time unit, generating a codebook for automatic repeat request confirmation (HARQ-ACK) feedback information, and sending the codebook within a third time unit.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a method and device for transmitting automatic repeat request confirmation feedback information supporting multicast services. Background Art

[0002] The International Telecommunication Union (ITU) has defined three major application scenarios for 5G and future mobile communication systems: enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and massive machine-type communications (mMTC). Typical eMBB services include ultra-high-definition video, augmented reality (AR), and virtual reality (VR). These services are characterized by large data volumes and high transmission rates. Typical URLLC services include wireless control in industrial manufacturing or production processes, motion control for autonomous vehicles and drones, and tactile interaction applications such as remote repair and remote surgery. These services require ultra-high reliability, low latency, low data volumes, and bursty transmission. Typical mMTC services include smart grid distribution automation and smart cities. They feature a large number of connected devices, low data volumes, and data insensitivity to transmission latency. These mMTC terminals must meet low costs and very long standby times.

[0003] Research on wireless broadcast / multicast services has continued unabated in recent years. The large number of mobile data multimedia services, various high-bandwidth multimedia services (such as interactive Internet Protocol Television (IPT) and mobile TV), and the provision of highly robust and critical communication services (such as group communications in disaster situations and public safety networks) have placed higher demands on broadcast / multicast services. These mobile data multimedia services require multiple users to receive the same data simultaneously. Compared to general data services, these services are characterized by large data volumes, long durations, and latency sensitivity.

[0004] The 3rd Generation Partnership Project (3GPP) has proposed the requirement for Multimedia Broadcast Multicast Service (MBMS). This service supports the provision of multicast / broadcast services in cellular systems. Multicast / broadcast is a technology for transmitting data from one data source to multiple target mobile terminals, which enables resource sharing between the core network and the access network and improves the utilization of network resources (especially air interface resources). The MBMS service defined by 3GPP can not only realize the multicast and broadcast of low-rate messages of plain text, but also realize the broadcast and multicast of high-speed multimedia services, providing a variety of rich video, audio and multimedia services. The characteristics of the broadcast service enable better efficiency in sending information of public interest, which undoubtedly conforms to the future trend of mobile data development and provides better business prospects for the development of communication technology.

[0005] The existing 5G New Radio (NR) supports unicast service transmission with a hybrid automatic repeat request (HARQ) mechanism. During HARQ-enabled unicast service transmission, the network device (gNB) sends a physical downlink control channel (PDCCH) to the user equipment (UE) to schedule the transmission of the physical downlink shared channel (PDSCH). After receiving the PDSCH, the UE sends an automatic repeat request acknowledgment (HARQ-ACK) feedback message to the gNB, informing the gNB of the UE's reception of the PDSCH. The HARQ-ACK feedback message is carried on the PUCCH or PUSCH. If the UE receives the PDSCH correctly, it sends an acknowledgment (ACK) to the gNB. After receiving the ACK, the gNB can schedule new data transmission. If the UE fails to receive the PDSCH correctly, it sends a negative acknowledgment (NACK) to the gNB. After receiving the NACK, the gNB can schedule retransmission of the PDSCH.

[0006] Taking the sending of HARQ-ACK feedback information on PUCCH as an example, the UE also needs to determine the PUCCH resources carrying HARQ-ACK before sending the HARQ-ACK feedback information. The UE receives the PDSCH to HARQ feedback timing indicator (PDSCH-to-HARQ_feedback timing indicator, K1), which can be carried in the downlink control information DCI or configured by high-level parameters. The indication information is used to indicate the time unit offset between PDSCH and HARQ. The time unit can be, for example, a time slot. After the UE determines the time unit carrying the HARQ transmission, it selects a PUCCH resource set based on the load size of the HARQ-ACK in the time unit. The load refers to the amount of HARQ-ACK feedback information required in the time unit.

[0007] like Figure 1a As shown below, a simple example is used to illustrate this. The gNB schedules the transmission of PDSCH#1 in slot #1 via DCI#1. The HARQ feedback timing indicator K1_1 in DCI#1 indicates a 4-slot offset for HARQ-ACK feedback. Similarly, the gNB schedules the transmission of PDSCH#2 in slot #2 via DCI#2. The HARQ feedback timing indicator K1_2 in DCI#2 indicates a 3-slot offset for HARQ-ACK feedback. The gNB schedules the transmission of PDSCH#3 in slot #3 via DCI#3. The HARQ feedback timing indicator K1_3 in DCI#3 indicates a 2-slot offset for HARQ-ACK feedback. Therefore, HARQ-ACK feedback information for PDSCH#1, PDSCH#2, and PDSCH#3 needs to be fed back in slot #5. That is, in time slot #5, the UE needs to feed back 1 bit of HARQ-ACK feedback information for each of PDSCH #1, PDSCH #2 and PDSCH #3, that is, a total of 3 bits of HARQ-ACK feedback information.

[0008] However, if one of the three DCIs scheduling a PDSCH is not successfully received by the UE, the corresponding PDSCH will not be received. Since the UE only perceives two scheduled PDSCH transmissions, it will only provide two bits of HARQ-ACK feedback. However, the gNB does not know which DCI was not successfully received by the UE, nor does it know which two PDSCHs the UE's two-bit HARQ-ACK feedback information refers to, ultimately resulting in HARQ feedback errors. The existing 5G NR standard uses a dynamic codebook mechanism to address this issue.

[0009] Under the dynamic codebook mechanism, the downlink scheduling information contains the downlink assignment index DAI (Downlink assignment index). The DAI field is divided into two parts, the DAI counter (counter-DAI) C-DAI and the total DAI (total-DAI) T-DAI. C-DAI indicates the cumulative number of DCIs sent for scheduling PDSCH transmission and DCIs used to indicate semi-static scheduling SPS PDSCH release until the current serving cell and PDCCH detection timing. The counting rule of C-DAI is to first count according to the serving cell dimension (for example, in ascending order of serving cell index), and then count according to the time dimension (for example, in ascending order of PDCCH detection timing). T-DAI indicates the cumulative number of DCIs sent for scheduling PDSCH transmission and DCIs used to indicate semi-static scheduling SPS PDSCH release until the current PDCCH detection timing. Therefore, the value of T-DAI is updated over time. Fallback DCI (e.g., DCI format 1_0) may contain only DAI count information, while non-fallback DCI (e.g., DCI formats 1_1 and 1_2) may contain both DAI count and total DAI, or only DAI count information. The UE generates a dynamic codebook for HARQ-ACK feedback information based on the C-DAI and T-DAI in the DCI.

[0010] like Figure 1bAs shown in the figure, for example, starting from slot 1, the gNB sends DCI 1, DCI 2, and DCI 3 in slot 1, respectively, to schedule the transmission of PDSCHs 1-3 in serving cells 1, 2, and 3. Assume that serving cells 1 and 3 send non-fallback DCI 1 and DCI 3, while serving cell 2 sends fallback DCI 2. Since the C-DAI counting rule is to count in ascending order by serving cell index, DCI 1 has a C-DAI value of 1, DCI 2 has a C-DAI value of 2, and DCI 3 has a C-DAI value of 3. In the current slot 1, a total of three DCIs are sent to schedule PDSCH transmissions, and the T-DAI value of both DCI 1 and DCI 3 is 3. Since DCI 2 is fallback DCI, it only contains the C-DAI field and does not contain the T-DAI field. In timeslot 2, the gNB sends DCI 4, which schedules the transmission of PDSCH 4, on serving cell 1 only. According to the above rules, the C-DAI value of DCI 4 is 4, and the T-DAI value is 4. In timeslot 3, the gNB sends DCI 5, which schedules the transmission of PDSCH 5, on serving cell 1, and DCI 6, which schedules PDSCH 6, on serving cell 3. According to the above rules, the C-DAI value of DCI 5 is 5, the C-DAI value of DCI 6 is 6, and the T-DAI value is 6. It should be noted that the C-DAI and T-DAI in a DCI can be cumulatively counted with at least one previous DCI, for example, if the PDSCH scheduled by the DCI and the PDSCH scheduled by the at least one previous DCI need to perform HARQ-ACK feedback in the same timeslot.

[0011] The dynamic codebook contains HARQ-ACK information for X PDSCHs, where X is the maximum T-DAI value in the DCI that schedules multiple PDSCH transmissions and requires HARQ-ACH feedback in the same timeslot. The HARQ-ACK feedback information for a PDSCH scheduled by a particular DCI is arranged at position Y in the dynamic codebook, where Y is equal to the C-DAI value in the DCI. The UE arranges the HARQ-ACK information corresponding to all detected DCI-scheduled data and then fills the remaining unfilled HARQ-ACK information positions in the dynamic codebook with NACKs. Upon receiving this information, the gNB determines that PDSCH 5 was not successfully received by the UE, or that the DCI scheduling PDSCH 5 transmission was not successfully received by the UE.

[0012] like Figure 1c As shown, for Figure 1b The PDSCH transmission will form the following Figure 1cThe dynamic codebook is shown. Since there are six PDSCHs that require HARQ-ACK feedback in the same timeslot, and the maximum T-DAI value is 6, the dynamic codebook consists of 6 bits. The HARQ-ACK feedback information for PDSCHs 1-6 is located in bits 1-6 of the dynamic codebook, respectively. Assuming the DCI scheduling PDSCH 5 transmission is not detected by the UE, the UE will return a NACK on bit 5. In this case, the gNB will retransmit the PDSCH 5 information to the UE in the next transmission.

[0013] However, there is currently no similar HARQ-ACK feedback mechanism for multicast transmission. Assume that the dynamic codebook mechanism under unicast transmission is applied to the multicast transmission scenario, such as Figure 1d As shown in the figure, to implement multicast services, the gNB needs to send multicast DCI (g-DCI) to multiple UEs (e.g., UE1 to UE3) in the same time slot to schedule PDSCH transmission. However, because each UE previously received a different unicast PDSCH, the bits of the multicast PDSCH in the dynamic codebook differ for each UE. As a result, the DAI value in the g-DCI is different for each UE, and the gNB cannot effectively set the DAI value, thus failing to ensure the reliability of the HARQ-ACK feedback information corresponding to the multicast PDSCH. Summary of the Invention

[0014] The embodiment of the present invention provides a method and device for transmitting automatic repeat request confirmation feedback information supporting multicast services.

[0015] A first aspect of an embodiment of the present invention provides a method for transmitting automatic repeat request confirmation feedback information supporting a multicast service, including:

[0016] Receiving N first downlink control information DCIs and M second DCIs within at least one first time unit, where the first DCIs are DCIs of the first type, and the second DCIs are DCIs of the second type, each of the first DCIs includes a first downlink allocation index DAI, the first DAI includes a first downlink allocation index counter C-DAI, and the first C-DAI indicates the cumulative number of DCIs of the first type scheduled for transmission on a downlink data channel; each of the second DCIs includes a second downlink allocation index DAI, the second DAI includes a second downlink allocation index counter C-DAI, and the second C-DAI indicates the cumulative number of DCIs of the second type scheduled for transmission on a downlink data channel;

[0017] receiving, within at least one second time unit, N first downlink data channels and M second downlink data channels, where the N first downlink data channels are scheduled by the N first downlink control information, and the M second downlink data channels are scheduled by the M second downlink control information;

[0018] Generate a codebook for automatic repeat request acknowledgment HARQ-ACK feedback information according to the first DAIs in the N first DCIs, the second DAIs in the M second DCIs, the N first downlink data channels, and the M second downlink data channels, the codebook including a first sub-codebook and a second sub-codebook, the first sub-codebook including ARQ-ACK feedback information of the N first downlink data channels, and the second sub-codebook including HARQ-ACK feedback information of the M second downlink data channels; and

[0019] The codebook is sent within a third time unit.

[0020] A second aspect of an embodiment of the present invention provides a method for transmitting automatic repeat request confirmation feedback information supporting a multicast service, including:

[0021] Sending N first downlink control information DCIs and M second DCIs within at least one first time unit, where the first DCIs are DCIs of the first type, and the second DCIs are DCIs of the second type, each of the first DCIs includes a first downlink allocation index DAI, the first DAI includes a first downlink allocation index counter C-DAI, and the first C-DAI indicates the cumulative number of DCIs of the first type scheduled for transmission through a downlink data channel; each of the second DCIs includes a second downlink allocation index DAI, the second DAI includes a second downlink allocation index counter C-DAI, and the second C-DAI indicates the cumulative number of DCIs of the second type scheduled for transmission through a downlink data channel;

[0022] Sending N first downlink data channels and M second downlink data channels within at least one second time unit, where the N first downlink data channels are scheduled by the N first downlink control information, and the M second downlink data channels are scheduled by the M second downlink control information;

[0023] A codebook for automatic repeat request confirmation HARQ-ACK feedback information is received within a third time unit, where the codebook includes a first sub-codebook and a second sub-codebook, the first sub-codebook including HARQ-ACK feedback information of the N first downlink data channels, and the second sub-codebook including HARQ-ACK feedback information of the M second downlink data channels.

[0024] A third aspect of an embodiment of the present invention provides a communication device, including a transceiver module and a processing module, wherein:

[0025] The transceiver module is configured to receive N first downlink control information DCIs and M second DCIs within at least one first time unit, where the first DCIs are DCIs of the first type, and the second DCIs are DCIs of the second type. Each of the first DCIs includes a first downlink allocation index DAI, the first DAI includes a first downlink allocation index counter C-DAI, and the first C-DAI indicates a cumulative number of DCIs of the first type scheduled for transmission through a downlink data channel; each of the second DCIs includes a second downlink allocation index DAI, the second DAI includes a second downlink allocation index counter C-DAI, and the second C-DAI indicates a cumulative number of DCIs of the second type scheduled for transmission through a downlink data channel;

[0026] The transceiver module is further configured to receive N first downlink data channels and M second downlink data channels within at least one second time unit, where the N first downlink data channels are scheduled by the N first downlink control information, and the M second downlink data channels are scheduled by the M second downlink control information;

[0027] The processing module is configured to generate a codebook for automatic repeat request acknowledgment HARQ-ACK feedback information according to the first DAI in the N first DCIs, the second DAI in the M second DCIs, the N first downlink data channels, and the M second downlink data channels, the codebook including a first sub-codebook and a second sub-codebook, the first sub-codebook including ARQ-ACK feedback information of the N first downlink data channels, and the second sub-codebook including HARQ-ACK feedback information of the M second downlink data channels; and

[0028] The transceiver module is further configured to send the codebook within a third time unit.

[0029] A fourth aspect of an embodiment of the present invention provides a communication device, including a processing module and a transceiver module, wherein:

[0030] The transceiver module is configured to send N first downlink control information DCIs and M second DCIs within at least one first time unit, where the first DCIs are DCIs of the first type, and the second DCIs are DCIs of the second type. Each of the first DCIs includes a first downlink allocation index DAI, the first DAI includes a first downlink allocation index counter C-DAI, and the first C-DAI indicates a cumulative number of DCIs of the first type scheduled for transmission through a downlink data channel; each of the second DCIs includes a second downlink allocation index DAI, the second DAI includes a second downlink allocation index counter C-DAI, and the second C-DAI indicates a cumulative number of DCIs of the second type scheduled for transmission through a downlink data channel;

[0031] The transceiver module is further configured to send N first downlink data channels and M second downlink data channels within at least one second time unit, where the N first downlink data channels are scheduled by the N first downlink control information, and the M second downlink data channels are scheduled by the M second downlink control information;

[0032] The transceiver module is further configured to receive a codebook of automatic repeat request confirmation HARQ-ACK feedback information within a third time unit;

[0033] The processing module is configured to determine HARQ-ACK feedback information from the codebook, wherein the codebook includes a first sub-codebook and a second sub-codebook, the first sub-codebook includes HARQ-ACK feedback information of the N first downlink data channels, and the second sub-codebook includes HARQ-ACK feedback information of the M second downlink data channels.

[0034] By adopting the embodiment of the present invention, the first C-DAI and the second C-DAI are accumulated and counted respectively, so that the C-DAI values ​​can be correctly and reasonably set for unicast and multicast services respectively, and at the same time, the data receiving end can generate HARQ-ACK feedback information for unicast and multicast services based on the first C-DAI and the second C-DAI, thereby ensuring the reliability of the HARQ-ACK feedback information corresponding to the multicast downlink data channel. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0036] Figure 1a This is a schematic diagram of the HARQ-ACK feedback method under traditional unicast services;

[0037] Figure 1b This is a schematic diagram of a HARQ-ACK feedback method using a dynamic codebook in a traditional unicast service;

[0038] Figure 1c yes Figure 1b Schematic diagram of the dynamic codebook structure used in;

[0039] Figure 1d This is a schematic diagram assuming that a dynamic codebook is used for HARQ-ACK feedback in a multicast service.

[0040] Figure 2 It is a schematic diagram of the architecture of the mobile communication system used in the embodiments of the present application.

[0041] Figure 3 It is a schematic diagram of a method for transmitting automatic repeat request confirmation feedback information supporting multicast services according to an embodiment of the present invention.

[0042] Figure 4 yes Figure 3 A schematic diagram illustrating the DCI and downlink data channel sent to the terminal device 32.

[0043] Figure 5 yes Figure 4 Schematic diagram of an example of DAI contained in DCI.

[0044] Figure 6 is Figure 4 and Figure 5 FIG. 1 is a schematic diagram showing a terminal device generating a corresponding codebook when DCI is sent. FIG.

[0045] Figure 7 A schematic block diagram of a communication device 1100 provided in an embodiment of the present application.

[0046] Figure 8 A schematic block diagram of a communication device 2100 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0047] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0048] Figure 2 Schematic diagram of the architecture of the mobile communication system used in the embodiment of the present application. Figure 2As shown, the mobile communication system includes a core network device 210, a wireless access network device 220 and at least one terminal device (such as Figure 2 Terminal devices 230 and 240 are shown in FIG. The terminal devices are wirelessly connected to the radio access network equipment, which is then wirelessly or wiredly connected to the core network equipment. The core network equipment and the radio access network equipment can be independent, distinct physical devices, or the core network equipment and the radio access network equipment's logical functions can be integrated into the same physical device. Alternatively, a single physical device can integrate some of the core network equipment's functions and some of the radio access network equipment's functions. Terminal devices can be fixed or mobile. Figure 2 This is just a schematic diagram. The communication system may also include other network devices, such as wireless relay devices and wireless backhaul devices. Figure 2 The embodiments of the present application do not limit the number of core network devices, wireless access network devices, and terminal devices included in the mobile communication system.

[0049] The wireless access network device in the embodiment of the present application is a device that is wirelessly connected to a terminal device through an air interface in a network system, enabling the terminal device to access the network through the air interface. The wireless access network device can specifically be a base station NodeB, an evolved base station (eNB), a transmission reception point (TRP), a next generation base station (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. The embodiments of the present application do not limit the specific technology and specific device form adopted by the wireless access network device.

[0050] The terminal device in the embodiment of the present application is an information processing device with wireless communication function. The terminal device can also be called a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device can be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The embodiment of the present application does not limit the specific technology and specific device form adopted by the terminal device.

[0051] Wireless access network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on aircraft, drones, balloons, and satellites. The embodiments of this application do not limit the application scenarios of wireless access network equipment and terminal devices.

[0052] The term "and / or" in this article is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0053] In the description and claims of the embodiments of this application, the terms "first" and "second" are used to distinguish different objects, rather than to describe a specific order of objects. For example, the terms "first target object" and "second target object" are used to distinguish different objects, rather than to describe a specific order of objects.

[0054] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0055] In the description of the embodiments of this application, unless otherwise specified, "multiple" means two or more. For example, "multiple processing units" means two or more processing units; "multiple systems" means two or more systems.

[0056] Please refer to Figure 3 , Figure 3 This is a flow chart of a method for transmitting automatic repeat request confirmation feedback information supporting multicast services provided by an embodiment of the present application.

[0057] 301: The access network device sends N first downlink control information DCIs and M second DCIs. Correspondingly, the terminal device receives N first downlink control information DCIs and M second DCIs.

[0058] 302: The access network device sends N first downlink data channels and M second downlink data channels. Correspondingly, the terminal device receives N first downlink data channels and M second downlink data channels, wherein the N first downlink data channels are scheduled by the N first downlink control information, and the M second downlink data channels are scheduled by the M second downlink control information.

[0059] Regarding the types of the first DCI and the second DCI

[0060] The first DCI is a first type of DCI, and the second DCI is a second type of DCI.

[0061] The type of the DCI may be distinguished according to the identifier used to scramble the cyclic redundancy check bit CRC of the DCI. For example, the first type of DCI is DCI whose cyclic redundancy check bit is scrambled by the group radio network temporary identifier, and the second type of DCI is DCI whose cyclic redundancy check bit is scrambled by the cell radio network temporary identifier, the modulation and coding mode-cell radio network temporary identifier, or the configured scheduling radio network temporary identifier CS-RNTI.

[0062] The type of DCI may be differentiated according to the service type or scheduling mode scheduled by the DCI. For example, the first type of DCI is DCI for scheduling multicast service transmission, and the second type of DCI is DCI for scheduling unicast service transmission.

[0063] The type of DCI may be differentiated according to the location / area where it is sent or searched. For example, the first type of DCI is sent within a first search space, and the second type of DCI is sent within a second search space different from the first search space. For another example, the first type of DCI is sent within a common search space, and the second type of DCI is sent within a UE-specific search space; the first type of DCI is sent within a first control channel resource set, and the second type of DCI is sent within a second control channel resource set.

[0064] It should be noted that the classification method of the above-mentioned DCI types may exist alone, or multiple classification methods may coexist and correspond to or be associated with each other. For example, the first type of DCI is the DCI for scheduling multicast service transmission, and the second type of DCI is the DCI for scheduling unicast service transmission. At this time, the first type of DCI cyclic redundancy check bits are DCI scrambled by the group radio network temporary identifier, and the second type of DCI is DCI scrambled by the cell radio network temporary identifier, the modulation and coding mode-cell radio network temporary identifier, or the configured scheduling radio network temporary identifier CS-RNTI. In this case, the DCI for the first type of multicast service can be arranged to be sent in the public search space, and the DCI for the second type of unicast service can be arranged to be sent in the UE-specific search space; or similarly, the first type of DCI is sent in the first control channel resource set, and the second type of DCI is sent in the second control channel resource set.

[0065] Temporal relationship

[0066] There is no strict order between steps 301 and 302, that is, step 302 is not limited to being executed after step 301 is fully executed. The timing relationship between steps 301 and 302 can be parallel, partially parallel, or interleaved.

[0067] Specifically, N first downlink control information DCIs and M second DCIs are received within at least one first time unit, and N first downlink data channels and M second downlink data channels are received within at least one second time unit. At least one first time unit and at least one second time unit may not overlap at all, may partially overlap, or may be completely identical (i.e., completely overlap). The time unit in each embodiment of the present application may be a time slot, a mini-slot, or other time length consisting of multiple time domain symbols.

[0068] For example, Figure 3As shown, in time slot 1, on the first service cell, the access network device 31 sends a second DCI to the terminal device 32. Since the second DCI is used to schedule unicast service transmission, the user equipment 33a~33n will not receive the second DCI. Thereafter, the terminal device 32 receives the second downlink data channel scheduled for transmission by the second DCI. It should be understood that the above description is only based on one service cell as an example. When there are multiple service cells between the access network device 31 and the terminal device 32, for example, three service cells, the above-mentioned DCI transmission and data channel transmission can be performed simultaneously on the three service cells.

[0069] In time slot 2, for example, on the second and third service cells, the access network device 31 sends a first DCI to the terminal device 32 and multiple other terminal devices 33a~33n. Since the first DCI is used to schedule multicast service transmission, the first DCI is sent to multiple terminal devices 32, 33a~33n. The first DCI schedules the transmission of the first downlink data channel in time slot 2. The first downlink data channel carries multicast services, and multiple terminal devices 32, 33a~33n receive the first downlink data channel in the second and third service cells. In time slot 2, for example, on the first service cell, the access network device 31 can also send a second DCI to the terminal device 32 to schedule unicast service transmission. The process is similar to the description in time slot 1 and will not be repeated.

[0070] Similarly, in time slot 3, for example, on the second service cell, the access network device 31 can send a first DCI to the terminal device 32 and multiple other terminal devices 33a~33n to schedule multicast service transmission, and can also send a second DCI through the first and third service cells to schedule unicast service transmission.

[0071] Further integration Figure 4 , Figure 4 yes Figure 3 Schematic diagram of the DCI and downlink data channel sent to the terminal device 32. Here, the example of three service cells between the access network device 31 and the terminal device 32 is used for explanation. It should be known that it is feasible to have only one or two service cells in the figure, or to include more service cells. In the figure, uDCI represents the second DCI for scheduling unicast services, and uPDSCH represents the second downlink data channel. gDCI represents the first DCI for scheduling multicast services, and gPDSCH represents the first downlink data channel. DCI can be specifically sent through the physical downlink control channel PDCCH.

[0072] In time slot 1, the access network device 31 can send uDCI1-3 through serving cells 1-3, respectively, to schedule the transmission of uPDSCH1-3 in time slot 1. In time slot 2, the access network device 31 can use gDCI1-2 to schedule the transmission of gPDSCH1-2 through serving cells 2-3, and use uDCI4 to schedule the transmission of uPDSCH4 through serving cell 1. Similarly, in time slot 3, the access network device 31 can use uDCI5-6 to schedule the transmission of uPDSCH5-6 through serving cells 1 and 3, respectively, and use gDCI3 to schedule the transmission of gPDSCH3 through serving cell 2.

[0073] DCI format and information

[0074] Each of the first DCIs includes a first downlink allocation index DAI, the first DAI includes a first downlink allocation index counter C-DAI, and the first C-DAI indicates the cumulative number of the first type of DCIs for scheduling downlink data channel transmission; each of the second DCIs includes a second downlink allocation index DAI, the second DAI includes a second downlink allocation index counter C-DAI, and the second C-DAI indicates the cumulative number of the second type of DCIs for scheduling downlink data channel transmission. That is, for C-DAI, the embodiment of the present application counts the first DCI for scheduling multicast services and the second DCI for scheduling unicast services separately. That is, the first C-DAI is the accumulation of the first DCI for scheduling multicast services, and the second C-DAI is the accumulation of the second DCI for scheduling unicast services.

[0075] In particular, for example, considering the scenario that there can be more than one service cell between the access network device and the terminal device, the first C-DAI may indicate the cumulative number of DCIs for scheduling physical downlink shared channel PDSCH transmission and / or for indicating semi-static scheduling SPS PDSCH release sent until the current service cell and the physical downlink control channel PDCCH detection timing. And / or, the second C-DAI may indicate the cumulative number of DCIs for scheduling physical downlink shared channel PDSCH transmission and / or for indicating semi-static scheduling SPS PDSCH release sent until the current service cell and the physical downlink control channel PDCCH detection timing.

[0076] The counting rule of the first C-DAI may be to first count in ascending order according to the serving cell index, and then count in ascending order according to the PDCCH detection timing. Similarly, the counting rule of the second C-DAI may also be to first count in ascending order according to the serving cell index, and then count in ascending order according to the PDCCH detection timing.

[0077] The first DAI may also include a first total downlink allocation index T-DAI, wherein the first T-DAI indicates the cumulative number of DCIs for scheduling physical downlink shared channel PDSCH transmissions and first type DCIs for indicating semi-static scheduling SPS PDSCH releases sent until the current physical downlink control channel PDCCH detection timing. Similarly, the second DAI also includes a second total downlink allocation index T-DAI, wherein the second T-DAI indicates the cumulative number of DCIs for scheduling physical downlink shared channel PDSCH transmissions and second type DCIs for indicating semi-static scheduling SPS PDSCH releases sent until the current physical downlink control channel PDCCH detection timing.

[0078] Whether T-DAI is included in the first DAI and the second DAI may depend on the type of DCI. For example, fallback DCI (e.g., DCI format 1_0) only includes C-DAI, while non-fallback DCI (e.g., DCI format 1_1) may include only C-DAI or both C-DAI and T-DAI. This is just an example, and whether different DCI formats include T-DAI can be flexibly designed.

[0079] In addition, it should be noted that, due to the capacity limitation of DCI, in order to save the bit overhead of DCI, the above-mentioned C-DAI and T-DAI can be represented by 2-bit loopback, that is, assuming that the actual value of C-DAI or T-DAI represented in decimal is set to X, then the C-DAI or T-DAI contained in the DCI is Xmod4, and Xmod4 represents the remainder obtained by dividing X by 4.

[0080] The PDCCH detection opportunity includes the available time unit for sending PDCCH or DCI to the terminal device, or the time unit in which the terminal device needs to detect PDCCH or DCI. The time unit in each embodiment of the present application can be a time slot, a mini-time slot, or other time length consisting of multiple time domain symbols.

[0081] Refer to Figure 5 , Figure 5 yes Figure 4 Schematic diagram of an example of DAI contained in DCI. Figure 4 The DAI contained in each CDI is expressed in the format of (C, T), where C represents the value of C-DAI and T represents the value of T-DAI. Here, it is assumed that time slots 1-3 are all PDCCH detection opportunities, and uDCI2 and uDCI5 are assumed to be fallback DCIs and do not contain T-DAI. Other DCIs are non-fallback DCIs and contain T-DAI. If there is no value in the T position, it means that T-DAI is not contained in the DCI.

[0082] Since the counting rule of C-DAI is frequency domain first and time domain second, that is, first count in ascending order according to the serving cell index, and then count in ascending order according to the PDCCH detection opportunity, Figure 4 The uDCI1 in the PDCCH is located in serving cell 1 and in time slot 1, so the value of the second C-DAI is 1. Correspondingly, uDCI2 and iDCI3, which are also located in time slot 1, are located in serving cell 2 and serving cell 3. According to the principle of frequency domain priority, the second C-DAI values ​​in uDCI2 and iDCI3 are 2 and 3. Since the cumulative number of second DCIs sent at the current PDCCH detection opportunity (time slot 1) is 3, the second T-DAI value of non-fallback uDCI1 and non-fallback uDCI2 is 3, and fallback uDCI2 does not include the second T-DAI.

[0083] In timeslot 2, since uDCI4 is still the second DCI, the second C-DAI and second T-DAI values ​​contained in uDCI4 are the cumulative number of the second DCIs in timeslot 1 (i.e., uDCI1-3). However, gDCI1 sent through serving cell 2 and gDCI2 sent through serving cell 3 are both first DCIs, and the first C-DAIs contained in them need to be accumulated separately. Therefore, for gDCI1, the first DCI has been sent once cumulatively up to the current serving cell (i.e., serving cell 2) and the current PDCCH detection opportunity (timeslot 2), so the first C-DAI value of gDCI1 is 1. For gDCI2, the first DCI has been sent twice cumulatively up to the current serving cell (i.e., serving cell 3) and the current PDCCH detection opportunity (timeslot 2), so the first C-DAI value of gDCI1 is 2. Since the cumulative number of first DCIs sent up to the current PDCCH detection opportunity (i.e., time slot 2) is 2, the first C-DAI values ​​in gDCI1 and gDCI2 are both 2.

[0084] Similarly, in timeslot 3, fallback uDCI5 is the fifth cumulative second DCI sent on serving cell 1 up to timeslot 3, so the second C-DAI value in uDCI5 is 5 and does not include T-DAI. Non-fallback uDCI6 is the sixth cumulative second DCI sent on serving cell 3 up to timeslot 3, so the second C-DAI value in uDCI6 is 6 and the second T-DAI value is 6. gDCI3 is the third cumulative first DCI sent on serving cell 2 up to timeslot 3, so the first C-DAI value in gDCI3 is 3. The number of cumulative first T-DAIs sent up to timeslot 3 is 3, so the first T-DAI value in gDCI3 is 3.

[0085] It should be understood that in this embodiment, the HARQ-ACK feedback information sending timing corresponding to the N first downlink data channels and the M second downlink data channels is the third time unit (e.g., time slot), that is, the HARQ-ACK feedback information sending timing is the same time unit, which is referred to as the third time unit in this embodiment.

[0086] In a specific implementation, the access network device may send a PDSCH to HARQ feedback timing indication (PDSCH-to-HARQ_feedback timing indicator, K1) to the terminal device. The indication may be carried in the downlink control information DCI, for example, carried in the signed first DCI or the second DCI, or configured by a high-level parameter. The indication information is used to indicate the time unit offset between PDSCH and HARQ. Accordingly, the terminal device may receive the PDSCH to HARQ feedback timing indication K1 to determine the feedback timing of the HARQ feedback information corresponding to the PDSCH.

[0087] 303: The terminal device generates a codebook for automatic repeat request acknowledgment HARQ-ACK feedback information based on the first DAI in the N first DCIs, the second DAI in the M second DCIs, the N first downlink data channels, and the M second downlink data channels, where the codebook includes a first sub-codebook and a second sub-codebook, the first sub-codebook including ARQ-ACK feedback information of the N first downlink data channels, and the second sub-codebook including HARQ-ACK feedback information of the M second downlink data channels.

[0088] In a specific implementation, the terminal device generates a first subcodebook based on the first DAI in the N first DCIs and the N first downlink data channels, and generates a second subcodebook based on the second DAI in the M second DCIs and the M second downlink data channels. For example, the terminal device may determine the position of the HAQR-ACK feedback bits corresponding to the N first downlink data channels in the first subcodebook based on the first DAI in the N first DCIs, and determine the value of each bit in the first subcodebook based on the reception status of each first downlink data channel. Similarly, the terminal device may determine the position of the HAQR-ACK feedback bits corresponding to the M second downlink data channels in the second subcodebook based on the second DAI in the M second DCIs, and determine the value of each bit in the second subcodebook based on the reception status of each second downlink data channel.

[0089] The first subcodebook is continuous bits, and the second subcodebook is continuous bits. The codebook can be continuous bits, that is, the first subcodebook bits and the second subcodebook bits are continuous or concatenated, the first subcodebook is before the second subcodebook, or the first subcodebook is after the second subcodebook. The codebook can be discontinuous bits, but the first subcodebook is still continuous bits, and the second subcodebook is still continuous bits. That is, the first subcodebook and the second subcodebook can be independent and discontinuous, and the codebook is just a set that logically includes the first subcodebook and the second subcodebook.

[0090] In a specific implementation, the total number of bits of the first subcodebook (i.e., the load size of the first subcodebook) is equal to the maximum value of the C-DAI in the N first DCIs received, or the total number of bits of the first subcodebook is the maximum value of the T-DAI in the N first DCIs received. In addition, the i-th bit in the first subcodebook is used to feedback the HARQ-ACK feedback information of the first downlink data channel scheduled by the i-th first DCI, where the i-th first DCI is the first DCI containing a C-DAI value of i. Wherein, 1≤i≤N, i is a positive integer. If the terminal device does not receive the i-th first DCI, the i-th bit is set to NACK or 0.

[0091] Similarly, the total number of bits of the second subcodebook (ie, the load size of the second subcodebook) is equal to the maximum value of C-DAI in the received M second DCIs, or the total number of bits of the second subcodebook is the maximum value of T-DAI in the received M second DCIs. In addition, the j-th bit in the second subcodebook is used to feedback the HARQ-ACK feedback information of the second downlink data channel scheduled by the j-th second DCI, where the j-th second DCI is the second DCI with a C-DAI value of j. Wherein, 1≤j≤M, j is a positive integer. If the terminal device does not receive the j-th second DCI, the j-th bit is set to NACK or 0.

[0092] Please refer to Figure 6 , Figure 6 is Figure 4 and Figure 5 FIG. 1 is a schematic diagram showing a terminal device generating a corresponding codebook when DCI is sent. FIG. Figure 6 In the codebook shown, bits 1 to 6 belong to the second subcodebook, and bits 7 to 9 belong to the first subcodebook. Figure 6 Although the first sub-codebook and the second sub-codebook are shown in an exemplary manner of cascading, the first sub-codebook and the second sub-codebook may also be independent.

[0093] Since the terminal device receives a total of 6 second DCIs, namely uDCI1-6, among which the second DCI with the largest C-DAI is uDCI6, and the maximum value of C-DAI is 6. The second DCI with the largest T-DAI is also uDCI6, and the maximum value of T-DAI is 6. Therefore, the terminal device can generate a 6-bit second sub-codebook, in which the first to sixth bits correspond to the HARQ-ADK feedback information of uPDSCH1 to uPDSCH6 scheduled by uDCI1 to uDCI6, respectively. Assume that the terminal device does not successfully receive uDCI5, and accordingly, the terminal device does not receive uPDSCH5. Since the terminal device does not receive the second DCI with a C-DAI value of 5 (that is, the fifth second DCI is not received), the terminal device sets the fifth bit in the second sub-codebook to NACK or 0. The terminal device sets the values ​​of bits 1-4 and 6 to ACK or NACK according to whether uPDSCH1-4 and uPDSCH5 are received successfully. For example, the value of ACK is 1, and the value of NACK is 0.

[0094] Similarly, since the terminal device receives a total of 3 first DCIs, namely gDCI1-3, among which the first DCI with the largest C-DAI is gDCI3, and the maximum value of C-DAI is 3. The first DCI with the largest T-DAI is also gDCI3, and the maximum value of T-DAI is 3. Therefore, the terminal device can generate a 3-bit second sub-codebook, namely Figure 6 The 7th to 9th bits in the codebook shown are also the 1st to 3rd bits in the second subcodebook. Figure 6 The 7th to 9th bits in the codebook shown correspond to the HARQ-ADK feedback information of gPDSCH1 to gPDSCH3 scheduled by gDCI1 to gDCI3, respectively. The terminal device sets the values ​​of bits 1 to 3 in the second sub-codebook to ACK or NACK based on whether gPDSCH1-3 is received successfully. For example, the value of ACK is 1 and the value of NACK is 0.

[0095] 304: The terminal device sends the codebook within the third time unit. Correspondingly, the access network device receives the codebook within the third time unit.

[0096] During the third time unit, the terminal device may send the codebook in a cascaded manner of the first sub-codebook and the second sub-codebook, or may send the first sub-codebook and the second sub-codebook separately to implement the transmission of the entire codebook. The method for selecting the resources required for sending the codebook may utilize the resource selection method for sending a dynamic codebook in the prior art, or may use a resource selection method different from the prior art. This embodiment exemplarily provides the following multiple methods for implementing codebook transmission.

[0097] Method 1

[0098] In the first approach, step 304 can be specifically implemented as follows.

[0099] 701: The terminal device determines a first PUCCH resource set from multiple physical uplink control channel PUCCH resource sets according to the load size of the codebook, each PUCCH resource set in the multiple PUCCH resource sets includes at least one PUCCH resource.

[0100] The terminal device is configured with multiple PUCCH resource sets, each of the multiple PUCCH resource sets including at least one PUCCH resource. For example, each of the multiple PUCCH resource sets includes multiple PUCCH resources. The multiple PUCCH resource sets may be pre-configured or fixedly configured in the terminal device according to a protocol, or may be configured to the terminal device by an access network device through signaling.

[0101] Different PUCCH resource sets may have different identifiers. The sizes of PUCCH resources belonging to different PUCCH resource sets may be different. Larger PUCCH resources can carry more bits of HARQ-ACK feedback information, and smaller PUCCH resources can carry fewer bits of HARQ-ACK feedback information. For example, the four PUCCH resource sets have PUCCH resource set identifiers (PUCCH Resource Set ID) 1-4 respectively. The number of bits of HARQ-ACK feedback information carried by the PUCCH resources contained in the PUCCH resource set with a smaller identification number is less than the number of bits of HARQ-ACK feedback information carried by the PUCCH resources contained in the PUCCH resource set with a larger identification number.

[0102] The load size of the codebook can be the number of bits of the codebook or other variables corresponding to the number of bits of the codebook. The terminal device can be configured based on the total number of bits of the codebook. UCI , select the first PUCCH set from the multiple PUCCH resource sets. For example, assuming there are the first to fourth PUCCH resource sets (ie, pucch-ResourceSetId = 0, 1, 2, 3), if O UCI ≤2, select the first PUCCH resource set (ie pucch-ResourceSetId = 0); if 2 <O UCI ≤N2, the UE selects the second PUCCH resource set (ie, pucch-ResourceSetId = 1), where N2 is configured by the high-level parameters. If the high-level parameters are not configured, the N2 value is 1706; if N2 <OUCI ≤N3, the UE selects the third PUCCH resource set (pucch-ResourceSetId=2), where N3 is configured by the high-level parameters. If the high-level parameters are not configured, the N3 value is 1706; if N3 <O UCI ≤1706, the UE selects the fourth PUCCH resource set (pucch-ResourceSetId=3), where N3 is configured by higher-layer parameters. If higher-layer parameters are not configured, the value of N3 is 1706. The above is only an example of a PUCCH resource set configuration method. Those skilled in the art can flexibly set the number of PUCCH resource sets and the codebook load range corresponding to each PUCCH resource set according to actual needs.

[0103] 702: The terminal device determines a first PUCCH resource from the first PUCCH resource set according to PUCCH resource indicator (PRI) included in the mth DCI.

[0104] In one implementation, the mth DCI is the last received DCI among all HARQ-ACK information bits in the codebook. That is, the mth DCI is the last received DCI among the N first DCIs and M second DCIs received. Here, in the same time slot, the DCI with the largest serving cell index is regarded as the last received DCI. For example, in Figure 4 and Figure 5 In the example shown, uDCI6 is the last one received among all M+N DCIs, so uDCI6 is the mth DCI.

[0105] In another implementation, the mth DCI is the second DCI corresponding to the HARQ-ACK information bit of the last second downlink data channel in the codebook, or the mth DCI is the second DCI with the largest received second C-DAI value. The second DCI corresponding to the HARQ-ACK information bit of the last second downlink data channel refers to: the last received DCI among the M received second DCIs. Similarly, in the same time slot, the DCI with the largest serving cell index is regarded as the last received DCI. According to the counting rule of the second C-DAI, the second C-DAI value in the last received second DCI must be the largest.

[0106] In yet another implementation, the mth DCI is the first DCI corresponding to the HARQ-ACK information bit of the last first downlink data channel in the codebook, or the mth DCI is the first DCI with the largest received first C-DAI value. The first DCI corresponding to the HARQ-ACK information bit of the last first downlink data channel refers to: the last received DCI among the N received first DCIs. Similarly, in the same time slot, the DCI with the largest serving cell index is regarded as the last received DCI. According to the counting rule of the first C-DAI, the first C-DAI value of the last received first DCI must be the largest.

[0107] In addition, each DCI also includes a PUCCH PRI. The PRI is used to determine the first PUCCH resource from the first PUCCH resource set. For example, the PRI can use a 3-bit index to represent eight PUCCH resources. The network device can pre-configure a PUCCH resource list resourceList, where each value / state in the PRI corresponds to a resource ID in the PUCCH resource list.

[0108] Corresponding to the terminal device, the access network device further includes, before sending the m-th DCI:

[0109] 711: Determine a first physical uplink control channel (PUCCH) resource set from the multiple PUCCH resource sets, each of the multiple PUCCH resource sets including multiple PUCCH resources, and the first PUCCH resource set corresponds to a load of the codebook to be received;

[0110] 712: Determine the first PUCCH resource from the first PUCCH resource set;

[0111] 713: Generate the mth DCI, where the mth DCI includes a PUCCH PRI, and the PRI is used to determine the first PUCCH resource.

[0112] It can be understood here that although the access network device has not received the codebook in the process of determining the first PUCCH resource set, since the access network device knows the accumulated number of DCI transmissions, the load size of the codebook to be received must be clear.

[0113] Steps 711-713 may be performed after the access network device sends the m-1th DCI and before sending the m-th DCI, or may be performed before sending the m-1th DCI. Those skilled in the art will appreciate that this may be determined by a scheduling policy within the access network device and is not limited here.

[0114] 703: The terminal device transmits the codebook using the determined first PUCCH resource within the third time unit. Correspondingly, the access network device receives the codebook on the first PUCCH resource.

[0115] Method 2

[0116] In the second method, step 304 can be implemented in the following manner.

[0117] 801: The terminal device determines a first PUCCH resource set from multiple physical uplink control channel (PUCCH) resource sets according to the payload size of the first subcodebook, where each PUCCH resource set in the multiple PUCCH resource sets includes multiple PUCCH resources; and determines a second PUCCH resource set from the multiple physical uplink control channel (PUCCH) resource sets according to the payload size of the second subcodebook.

[0118] For the explanation and implementation of the load and PUCCH resource set, refer to Method 1, and the repeated parts are not repeated here. It should be noted that there is no restriction on the order in which the operations of determining the first PUCCH resource set and determining the second PUCCH resource set are performed, and the first PUCCH resource set and the second PUCCH resource set can be the same or different.

[0119] 802: The terminal device determines a first PUCCH resource from the first PUCCH resource set based on the PUCCH PRI included in the m1th received first DCI; and determines a second PUCCH resource from the second PUCCH resource set based on the PUCCH PRI included in the m2th received second DCI.

[0120] In one implementation, the m1th DCI is the first DCI corresponding to the last HARQ-ACK information bit of the first downlink data channel in the codebook, or the mth DCI is the last received first DCI, or the mth DCI is the first DCI with the largest cumulative number of DCIs of the first type indicated in the received first C-DAI. The m2th DCI is the second DCI corresponding to the last HARQ-ACK information bit of the second downlink data channel in the codebook, or the mth DCI is the last received second DCI, or the mth DCI is the second DCI with the largest cumulative number of DCIs of the second type indicated in the received second C-DAI.

[0121] Corresponding to the terminal device, the access network device further includes, before sending the m1-th first DCI:

[0122] 811: Determine a first physical uplink control channel (PUCCH) resource set from multiple physical uplink control channel (PUCCH) resource sets, where each of the multiple PUCCH resource sets includes multiple PUCCH resources, and the first PUCCH resource set corresponds to a load of the first subcodebook to be received.

[0123] 812: Determine a first PUCCH resource from the first PUCCH resource set;

[0124] 813: Generate an m1th DCI, where the m1th DCI includes first PUCCH resource indication information PRI, and the PRI is used to determine the first PUCCH resource.

[0125] Before sending the m2-th second DCI, the access network device further includes:

[0126] 814: Determine a second physical uplink control channel (PUCCH) resource set from the multiple physical uplink control channel (PUCCH) resource sets, where the second PUCCH resource set corresponds to a load of the second subcodebook to be received.

[0127] 815: Determine a second PUCCH resource from the second PUCCH resource set;

[0128] 816: Generate an m2th DCI, where the m2th DCI includes second PUCCH resource indication information PRI, and the PRI is used to determine the second PUCCH resource.

[0129] It can be understood here that although the access network device has not received the codebook in the process of determining the first PUCCH resource set, since the access network device knows the cumulative number of first DCI transmissions and the cumulative number of second DCI transmissions, the load size of the first sub-codebook to be received and the load size of the second sub-codebook must be clear.

[0130] Steps 811-813 can be performed after the access network device sends the m1-1th first DCI and before sending the m1-1th first DCI, or before sending the m1-1th first DCI. Steps 814-816 can be performed after the access network device sends the m2-1th second DCI and before sending the m2-1th second DCI, or before sending the m2-1th second DCI. Those skilled in the art will understand that this can be determined by the scheduling policy within the access network device and is not limited here. In addition, there is no restriction on the order of steps 811-813 and steps 814-816. The order can be determined by the order of the m1th first DCI and the m2th second DCI, or by the scheduling policy within the access network device.

[0131] 803: The terminal device transmits the first subcodebook using the determined first PUCCH resource and transmits the second subcodebook using the determined second PUCCH resource within the third time unit. Accordingly, within the third time unit, the access network device receives the first subcodebook on the first PUCCH resource and receives the second subcodebook on the second PUCCH resource.

[0132] In the second approach described above, a multicast DCI is sent to a group of UEs. These UEs use the same PUCCH PRI to determine PUCCH resources. If the PUCCH resources were determined based on the PRI in the last multicast DCI, multiple UEs would simultaneously transmit HARQ PUCCHs, resulting in excessive system load. However, the PRIs in unicast DCI received by different UEs may differ. Therefore, the PUCCH resources determined based on the PRI in the unicast DCI can be staggered in time, reducing system load to a certain extent.

[0133] In one implementation, the terminal device may specifically include:

[0134] When the first PUCCH resource and the second PUCCH resource do not overlap in the time domain, within the third time unit, use the determined first PUCCH resource to send the first subcodebook, and use the determined second PUCCH resource to send the second subcodebook;

[0135] When the first PUCCH resource and the second PUCCH resource overlap in the time domain,

[0136] Determining a third PUCCH resource set from the multiple physical uplink control channel (PUCCH) resource sets according to a load size of the codebook;

[0137] Determine, according to the PUCCH resource indication information PRI included in the m-th DCI, a third PUCCH resource from the third PUCCH resource set;

[0138] The codebook is sent using the determined third PUCCH resource within the third time unit.

[0139] The explanation and implementation of the mth DCI and PRI are the same as those in 702 and will not be repeated here.

[0140] Accordingly, when implementing 803, the access network device may specifically include:

[0141] When the first PUCCH resource and the second PUCCH resource do not overlap in the time domain, receiving the first subcodebook on the first PUCCH resource and receiving the second subcodebook on the second PUCCH resource within a third time unit;

[0142] When the first PUCCH resource and the second PUCCH resource overlap in the time domain,

[0143] Determining a third PUCCH resource set from the multiple physical uplink control channel PUCCH resource sets according to a load size of the codebook to be received;

[0144] Determine, according to the PUCCH resource indication information PRI included in the m-th DCI, a third PUCCH resource from the third PUCCH resource set;

[0145] The codebook is received on the determined third PUCCH resource within the third time unit.

[0146] The third PUCCH resource set mentioned above may be completely identical to the first PUCCH resource set or the second PUCCH resource set, or may be a PUCCH resource set different from the first PUCCH resource set or the second PUCCH resource set.

[0147] Method 3

[0148] In the third method, step 304 can be implemented in the following manner.

[0149] The multiple physical uplink control channel PUCCH resource sets include a first PUCCH resource set group and a second PUCCH resource set group, and each PUCCH resource set in each of the PUCCH resource set groups includes multiple PUCCH resources.

[0150] 901: The terminal device determines a first PUCCH resource set from the first PUCCH resource set group according to the payload size of the first subcodebook; and determines a second PUCCH resource set from the second PUCCH resource set group according to the payload size of the second subcodebook.

[0151] Here, each of the first PUCCH resource set group and the second PUCCH resource set group includes multiple PUCCH resource sets, and each PUCCH resource set includes at least one PUCCH resource. The PUCCH resources included in the first PUCCH resource set group and the second PUCCH resource set group may be completely different.

[0152] In one implementation, the PUCCH resources within the first PUCCH resource set group are dedicated to feedback of HARQ-ACK feedback information corresponding to the first downlink data channel scheduled by the first type of DCI, and the PUCCH resources within the second PUCCH resource set group are dedicated to feedback of HARQ-ACK feedback information corresponding to the second downlink data channel scheduled by the second type of DCI.

[0153] In another implementation, a start symbol in the time domain of each PUCCH resource in the first PUCCH resource set group is located before a start symbol in the time domain of each PUCCH resource in the second PUCCH resource set group.

[0154] In another implementation manner different from the foregoing, the last symbol of each PUCCH resource in the first PUCCH resource set group in the time domain is located before the last symbol of each PUCCH resource in the second PUCCH resource set group in the time domain.

[0155] In another implementation different from the foregoing, a starting symbol in the time domain of each PUCCH resource in the first PUCCH resource set group is located before the first symbol, and a starting symbol in the time domain of each PUCCH resource in the second PUCCH resource set group is located after the first symbol; or

[0156] In another implementation different from the above, the last symbol of each PUCCH resource in the first PUCCH resource set group in the time domain is located before the first symbol, and the last symbol of each PUCCH resource in the second PUCCH resource set group in the time domain is located after the first symbol.

[0157] 902: The terminal device determines a first PUCCH resource from the first PUCCH resource set according to the PUCCH PRI included in the m1th received first DCI; and determines a second PUCCH resource from the second PUCCH resource set according to the PUCCH PRI included in the m2th received second DCI.

[0158] Corresponding to the terminal device, the access network device further includes, before sending the m1-th first DCI:

[0159] Determine a first PUCCH resource set from the first PUCCH resource set group, where the first PUCCH resource set corresponds to a payload size of the first subcodebook to be received;

[0160] Determine a first PUCCH resource from the first PUCCH resource set;

[0161] An m1th DCI is generated, where the m1th DCI includes first PUCCH resource indication information PRI, where the PRI is used to determine the first PUCCH resource.

[0162] Before sending the m2-th second DCI, the access network device further includes:

[0163] Determine a second PUCCH resource set from the second PUCCH resource set group, where the second PUCCH resource set corresponds to a payload size of the second subcodebook to be received;

[0164] Determine a second PUCCH resource from the second PUCCH resource set;

[0165] An m2th DCI is generated, where the m2th DCI includes second PUCCH resource indication information PRI, where the PRI is used to determine the second PUCCH resource.

[0166] 903: During the third time unit, the terminal device transmits the first subcodebook using the determined first PUCCH resource and transmits the second subcodebook using the determined second PUCCH resource. Correspondingly, during the third time unit, the access network device receives the first subcodebook on the first PUCCH resource and receives the second subcodebook on the second PUCCH resource.

[0167] In the above-mentioned method three, the multiple physical uplink control channel PUCCH resource sets include a first PUCCH resource set group and a second PUCCH resource set group, and the time domain positions of the PUCCH resources in the first PUCCH resource set group and the second PUCCH resource set group are different. Such a design can make the HARQ-ACK feedback delay more in line with the needs of unicast or multicast services. For example, if the unicast service is an ultra-reliable and low-latency communications (URLLC) service, it has a higher requirement for delay. If the multicast service is an enhanced mobile broadband (eMBB) service, it has a relatively low requirement for delay. Therefore, when, for example, the starting symbol of each PUCCH resource in the first PUCCH resource set group in the time domain is located before the first symbol, and the starting symbol of each PUCCH resource in the second PUCCH resource set group in the time domain is located after the first symbol, it is conducive to the HARQ-ACK feedback information of the unicast service with higher delay requirements being sent more timely.

[0168] In one implementation, the terminal device may specifically include:

[0169] When the first PUCCH resource and the second PUCCH resource do not overlap in the time domain, within the third time unit, use the determined first PUCCH resource to send the first subcodebook, and use the determined second PUCCH resource to send the second subcodebook;

[0170] When the first PUCCH resource and the second PUCCH resource overlap in the time domain,

[0171] Determine a third PUCCH resource set from the multiple physical uplink control channel PUCCH resource sets, the first PUCCH resource set group, the second PUCCH resource set group, or the third PUCCH resource set group according to the load size of the codebook;

[0172] Determine, according to the PUCCH resource indication information PRI included in the m-th DCI, a third PUCCH resource from the third PUCCH resource set;

[0173] The codebook is sent using the determined third PUCCH resource within the third time unit.

[0174] In one implementation, the access network device may specifically include:

[0175] When the first PUCCH resource and the second PUCCH resource do not overlap in the time domain, receiving the first subcodebook on the first PUCCH resource and receiving the second subcodebook on the second PUCCH resource within a third time unit;

[0176] When the first PUCCH resource and the second PUCCH resource overlap in the time domain,

[0177] Determine a third PUCCH resource set based on a plurality of physical uplink control channel PUCCH resource sets, the first PUCCH resource set group, the second PUCCH resource set group, or the third PUCCH resource set group according to a load size of the codebook to be received;

[0178] Determine, according to the PUCCH resource indication information PRI included in the m-th DCI, a third PUCCH resource from the third PUCCH resource set;

[0179] The codebook is received on the determined third PUCCH resource within the third time unit.

[0180] The third PUCCH resource set may be completely identical to the first PUCCH resource set or the second PUCCH resource set, or may be a PUCCH resource set different from the first PUCCH resource set or the second PUCCH resource set.

[0181] The explanation and implementation of the mth DCI and PRI are the same as those in 702 and will not be repeated here.

[0182] The explanation and implementation of the m1th received first DCI and the m2th received second DCI are the same as those in the second method and will not be repeated here.

[0183] By adopting the embodiment of the present invention, the first C-DAI and the second C-DAI are accumulated and counted respectively, so that the C-DAI values ​​can be correctly and reasonably set for unicast and multicast services respectively, and at the same time, the data receiving end can generate HARQ-ACK feedback information for unicast and multicast services based on the first C-DAI and the second C-DAI, thereby ensuring the reliability of the HARQ-ACK feedback information corresponding to the multicast downlink data channel.

[0184] Figure 7 A schematic block diagram of a communication device 1100 provided in an embodiment of the present application. Exemplarily, the communication device 1100 may be a terminal device, or may be a chip applied to a terminal device, or other combined devices, components, etc. having the functions of the above-mentioned terminal device. The description of the terminal device side in the foregoing embodiments is applicable to the communication device 1100 and will not be repeated later. The communication device 1100 includes a processing module 1110 and a transceiver module 1120. When the communication device 1100 is a terminal device, the transceiver module 1120 may be a transceiver, which may include an antenna and a radio frequency circuit, etc., and the processing module 1110 may be a processor, such as a baseband processor, which may include one or more central processing units (CPUs). When the communication device 1100 is a component having the functions of the above-mentioned terminal device, the transceiver module 1120 may be a radio frequency unit, and the processing module 1110 may be a processor, such as a baseband processor. When the communication device 1100 is a chip system, the transceiver module 1120 may be an input / output interface of the chip (e.g., a baseband chip), and the processing module 1110 may be a processor of the chip system, which may include one or more central processing units. It should be understood that the processing module 1110 in the embodiments of the present application may be implemented by a processor or processor-related circuit components, and the transceiver module 1120 may be implemented by a transceiver or transceiver-related circuit components.

[0185] For example, the processing module 1110 can be used to perform Figure 3In the embodiment shown, all operations performed by the device except for the receiving / transmitting operations, such as steps 303, 701, 702, 801, 802, 901, 902 and / or other processes used to support the technology described herein. The transceiver module 1120 can be used to perform Figure 3 All the receiving / transmitting operations performed by the terminal device in the illustrated embodiment, such as steps 301 , 302 , 304 , 703 , 803 , 903 and / or other processes for supporting the technology described herein.

[0186] In addition, the transceiver module 1120 may be a functional module that can perform both sending and receiving operations. For example, the transceiver module 1120 may be used to perform Figure 3 In the embodiment shown, all sending operations and receiving operations performed by the terminal device, for example, when performing a sending operation, the transceiver module 1120 can be considered as a sending module, and when performing a receiving operation, the transceiver module 1120 can be considered as a receiving module; or, the transceiver module 1120 can also be two functional modules, and the transceiver module 1120 can be regarded as a general term for the two functional modules, which are a sending module and a receiving module respectively. The sending module is used to complete the sending operation, for example, the sending module can be used to perform Figure 3 In any of the embodiments shown, the first terminal device performs all the sending operations, and the receiving module is used to complete the receiving operation. For example, the receiving module can be used to perform Figure 3 The embodiment shown shows all receiving operations performed by the terminal device.

[0187] Specifically, in one implementation of this embodiment,

[0188] The transceiver module 1120 is used to: receive N first downlink control information DCI and M second DCI; receive N first downlink data channels and M second downlink data channels, the N first downlink data channels are scheduled by the N first downlink control information, and the M second downlink data channels are scheduled by the M second downlink control information.

[0189] The processing module 1110 is configured to generate a codebook for automatic repeat request acknowledgment HARQ-ACK feedback information according to the first DAI in the N first DCIs, the second DAI in the M second DCIs, the N first downlink data channels, and the M second downlink data channels, wherein the codebook includes a first sub-codebook and a second sub-codebook, the first sub-codebook including ARQ-ACK feedback information of the N first downlink data channels, and the second sub-codebook including HARQ-ACK feedback information of the M second downlink data channels.

[0190] The transceiver module 1120 is further configured to send the codebook within a third time unit.

[0191] In one implementation,

[0192] The processing module 1110 is further configured to: determine a first PUCCH resource set from a plurality of physical uplink control channel (PUCCH) resource sets according to a load size of the codebook, each of the plurality of PUCCH resource sets including at least one PUCCH resource; and determine a first PUCCH resource from the first PUCCH resource set according to PUCCH resource indication information included in an mth DCI;

[0193] The transceiver module 1120 is configured to send the codebook using the determined first PUCCH resource within the third time unit.

[0194] In another implementation,

[0195] The processing module 1110 is further configured to: determine a first PUCCH resource set from a plurality of physical uplink control channel (PUCCH) resource sets according to a payload size of the first subcodebook, where each PUCCH resource set in the plurality of PUCCH resource sets includes a plurality of PUCCH resources; determine a second PUCCH resource set from the plurality of physical uplink control channel (PUCCH) resource sets according to a payload size of the second subcodebook; determine a first PUCCH resource from the first PUCCH resource set according to a PUCCH PRI included in an m1th received first DCI; and determine a second PUCCH resource from the second PUCCH resource set according to a PUCCH PRI included in an m2th received second DCI;

[0196] The transceiver module 1120 is configured to send the first subcodebook using the determined first PUCCH resource and send the second subcodebook using the determined second PUCCH resource within the third time unit.

[0197] Optionally, in this implementation,

[0198] The transceiver module 1120 is configured to, when the first PUCCH resource and the second PUCCH resource do not overlap in the time domain, send the first subcodebook using the determined first PUCCH resource and send the second subcodebook using the determined second PUCCH resource within the third time unit;

[0199] The processing module 1110 is further configured to: when the first PUCCH resource and the second PUCCH resource overlap in the time domain, determine a third PUCCH resource set from the multiple physical uplink control channel PUCCH resource sets according to the load size of the codebook; and determine a third PUCCH resource from the third PUCCH resource set according to PUCCH resource indication information PRI included in the mth DCI;

[0200] The transceiver module 1120 is further configured to send the codebook using the determined third PUCCH resource within the third time unit.

[0201] In yet another implementation,

[0202] The processing module 1110 is further configured to: determine a first PUCCH resource set from the first PUCCH resource set group according to the payload size of the first subcodebook; determine a second PUCCH resource set from the second PUCCH resource set group according to the payload size of the second subcodebook; determine a first PUCCH resource from the first PUCCH resource set according to the PUCCH PRI included in the m1th received first DCI; and determine a second PUCCH resource from the second PUCCH resource set according to the PUCCH PRI included in the m2th received second DCI;

[0203] The transceiver module 1120 is further configured to send the first subcodebook using the determined first PUCCH resource and send the second subcodebook using the determined second PUCCH resource within the third time unit.

[0204] Optionally, in this implementation,

[0205] The transceiver module 1120 is further configured to, when the first PUCCH resource and the second PUCCH resource do not overlap in the time domain, send the first subcodebook using the determined first PUCCH resource and send the second subcodebook using the determined second PUCCH resource within the third time unit;

[0206] The processing module 1110 is further configured to: when the first PUCCH resource and the second PUCCH resource overlap in the time domain, determine, according to the load size of the codebook, a third PUCCH resource set from the multiple physical uplink control channel PUCCH resource sets, the first PUCCH resource set group, the second PUCCH resource set group, or the third PUCCH resource set group; and determine, according to the PUCCH resource indication information PRI included in the mth DCI, a third PUCCH resource from the third PUCCH resource set;

[0207] The transceiver module 1120 is further configured to send the codebook using the determined third PUCCH resource within the third time unit.

[0208] Figure 8 The present invention provides a schematic block diagram of a communication device 2100 according to an embodiment of the present application. For example, the communication device 2100 may be the aforementioned access network device. The description of the access network device in the aforementioned embodiment is applicable to the communication device 2100 and will not be repeated hereafter. The communication device 2100 includes a processing module 2110 and a transceiver module 2120. The transceiver module 2120 may be a transceiver, which may include an antenna and a radio frequency circuit, etc. The processing module 2110 may be a processor, such as a baseband processor, which may include one or more central processing units (CPUs).

[0209] Specifically, in one implementation of this embodiment,

[0210] The transceiver module 2120 is configured to send N first downlink control information DCIs and M second DCIs within at least one first time unit, where the first DCI is a first type of DCI, and the second DCI is a second type of DCI. Each of the first DCIs includes a first downlink allocation index DAI, and the first DAI includes a first downlink allocation index counter C-DAI, where the first C-DAI indicates the cumulative number of DCIs of the first type scheduled for transmission through a downlink data channel; each of the second DCIs includes a second downlink allocation index DAI, and the second DAI includes a second downlink allocation index counter C-DAI, where the second C-DAI indicates the cumulative number of DCIs of the second type scheduled for transmission through a downlink data channel;

[0211] The transceiver module 2120 is further configured to send N first downlink data channels and M second downlink data channels within at least one second time unit, where the N first downlink data channels are scheduled by the N first downlink control information, and the M second downlink data channels are scheduled by the M second downlink control information;

[0212] The transceiver module 2120 is further configured to receive a codebook of automatic repeat request confirmation HARQ-ACK feedback information within a third time unit;

[0213] The processing module 2110 is configured to determine HARQ-ACK feedback information from the codebook, where the codebook includes a first sub-codebook and a second sub-codebook, the first sub-codebook includes HARQ-ACK feedback information of the N first downlink data channels, and the second sub-codebook includes HARQ-ACK feedback information of the M second downlink data channels.

[0214] In one implementation,

[0215] The processing module 2110 is further configured to determine a first PUCCH resource set from a plurality of physical uplink control channel (PUCCH) resource sets, each of the plurality of PUCCH resource sets including a plurality of PUCCH resources, the first PUCCH resource set corresponding to a load of the codebook to be received; determine a first PUCCH resource from the first PUCCH resource set; generate an mth DCI, the mth DCI including PUCCH resource indication information (PRI), the PRI being used to determine the first PUCCH resource;

[0216] The transceiver module 2120 is specifically configured to receive a codebook of automatic repeat request confirmation HARQ-ACK feedback information on the first PUCCH resource within a third time unit.

[0217] In another implementation,

[0218] The processing module 2110 is further configured to determine a first PUCCH resource set from a plurality of physical uplink control channel (PUCCH) resource sets, each of the plurality of PUCCH resource sets including a plurality of PUCCH resources, the first PUCCH resource set corresponding to a load of the first sub-codebook to be received; determine a first PUCCH resource from the first PUCCH resource set; generate an m1th DCI, the m1th DCI including first PUCCH resource indication information PRI, the PRI being used to determine the first PUCCH resource; determine a second PUCCH resource set from the plurality of physical uplink control channel (PUCCH) resource sets, the second PUCCH resource set corresponding to a load of the second sub-codebook to be received; determine a second PUCCH resource from the second PUCCH resource set; generate an m2th DCI, the m2th DCI including second PUCCH resource indication information PRI, the PRI being used to determine the second PUCCH resource;

[0219] The transceiver module 2120 is specifically configured to receive the first subcodebook on the first PUCCH resource and receive the second subcodebook on the second PUCCH resource within a third time unit.

[0220] In the above implementation, optionally,

[0221] The transceiver module 2120 receives the first subcodebook on the first PUCCH resource within the third time unit, and receives the second subcodebook on the second PUCCH resource specifically including:

[0222] The transceiver module 2120 is configured to receive the first subcodebook on the first PUCCH resource and receive the second subcodebook on the second PUCCH resource within a third time unit when the first PUCCH resource and the second PUCCH resource do not overlap in the time domain;

[0223] The processing module 2110 is further configured to, when the first PUCCH resource and the second PUCCH resource overlap in the time domain, determine a third PUCCH resource set from the multiple physical uplink control channel PUCCH resource sets according to a payload size of the codebook to be received; and determine a third PUCCH resource from the third PUCCH resource set according to PUCCH resource indication information PRI included in the mth DCI;

[0224] The transceiver module 2120 is further configured to receive the codebook on the determined third PUCCH resource within the third time unit.

[0225] In yet another implementation,

[0226] The multiple physical uplink control channel PUCCH resource sets include a first PUCCH resource set group and a second PUCCH resource set group, and each PUCCH resource set in each of the PUCCH resource set groups includes multiple PUCCH resources;

[0227] The codebook for receiving the HARQ-ACK feedback information by the transceiver module 2120 in the third time unit includes:

[0228] The processing module 2110 is further configured to determine a first PUCCH resource set from the first PUCCH resource set group, the first PUCCH resource set corresponding to a payload size of the first subcodebook to be received; determine a first PUCCH resource from the first PUCCH resource set; generate an m1th DCI, the m1th DCI including first PUCCH resource indication information PRI, the PRI being used to determine the first PUCCH resource; determine a second PUCCH resource set from the second PUCCH resource set group, the second PUCCH resource set corresponding to a payload size of the second subcodebook to be received; and determine a second PUCCH resource from the second PUCCH resource set;

[0229] The processing module 2110 is further configured to generate an m2-th DCI, where the m2-th DCI includes second PUCCH resource indication information PRI, where the PRI is used to determine the second PUCCH resource;

[0230] The transceiver module 2120 is further configured to receive the first subcodebook on a first PUCCH resource and receive the second subcodebook on a second PUCCH resource within the third time unit.

[0231] In a specific implementation, optionally,

[0232] The transceiver module 2120 is further configured to receive, within the third time unit, the first subcodebook on the first PUCCH resource and the second subcodebook on the second PUCCH resource, including:

[0233] The transceiver module 2120 is further configured to, when the first PUCCH resource and the second PUCCH resource do not overlap in the time domain, receive the first subcodebook on the first PUCCH resource and receive the second subcodebook on the second PUCCH resource within a third time unit;

[0234] The processing module 2110 is further configured to, when the first PUCCH resource and the second PUCCH resource overlap in the time domain, determine a third PUCCH resource set from a plurality of physical uplink control channel PUCCH resource sets, the first PUCCH resource set group, the second PUCCH resource set group, or a third PUCCH resource set group according to a payload size of the codebook to be received; and determine a third PUCCH resource from the third PUCCH resource set according to PUCCH resource indication information PRI included in the mth DCI;

[0235] The transceiver module 2120 is further configured to receive the codebook on the determined third PUCCH resource within the third time unit.

[0236] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program. When the computer program is executed by a computer, the computer can implement the process related to the terminal device in the embodiment provided in the above method embodiment.

[0237] An embodiment of the present application further provides a computer-readable storage medium, which is used to store a computer program. When the computer program is executed by a computer, the computer can implement the process related to the access network device in the embodiment provided in the above method embodiment.

[0238] An embodiment of the present application further provides a computer program product, which is used to store a computer program. When the computer program is executed by a computer, the computer can implement the process related to the terminal device in the embodiment provided in the above method embodiment.

[0239] An embodiment of the present application further provides a computer program product, which is used to store a computer program. When the computer program is executed by a computer, the computer can implement the process related to the access network device in the embodiment provided in the above method embodiment.

[0240] It should be understood that the processor mentioned in the embodiments of the present application may be a CPU, or may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0241] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0242] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) is integrated into the processor.

[0243] It should be noted that the memory described herein is intended to include, but not be limited to, these and any other suitable types of memory.

[0244] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0245] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0246] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0247] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0248] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0249] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0250] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned computer-readable storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), universal serial bus flash disk, mobile hard disk, or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0251] The above description is merely a specific embodiment of the present application, but the scope of protection of the embodiments of the present application is not limited thereto. Any person skilled in the art can easily conceive of changes or substitutions within the technical scope disclosed in the embodiments of the present application, and such changes or substitutions should be included in the scope of protection of the embodiments of the present application. Therefore, the scope of protection of the embodiments of the present application should be based on the scope of protection of the claims.

Claims

1. A method for transmitting automatic repeat request confirmation feedback information supporting multicast services, characterized in that: include: Receiving N first downlink control information DCIs and M second DCIs within at least one first time unit, where the first DCIs are DCIs of a first type, the first type of DCIs are DCIs for a multicast service, the second DCIs are DCIs of a second type, and the second type of DCIs are DCIs for a unicast service, each of the first DCIs includes a first downlink allocation index DAI, the first DAI includes a first downlink allocation index counter C-DAI, and the first C-DAI indicates a cumulative number of DCIs of the first type scheduled for transmission through a downlink data channel; each of the second DCIs includes a second downlink allocation index DAI, the second DAI includes a second downlink allocation index counter C-DAI, and the second C-DAI indicates a cumulative number of DCIs of the second type scheduled for transmission through a downlink data channel; receiving, within at least one second time unit, N first downlink data channels and M second downlink data channels, where the N first downlink data channels are scheduled by the N first downlink control information, and the M second downlink data channels are scheduled by the M second DCIs; Generate, according to the first DAIs in the N first DCIs, the second DAIs in the M second DCIs, the N first downlink data channels, and the M second downlink data channels, a codebook for automatic repeat request acknowledgment HARQ-ACK feedback information, the codebook including a first sub-codebook and a second sub-codebook, the first sub-codebook including ARQ-ACK feedback information of the N first downlink data channels, and the second sub-codebook including HARQ-ACK feedback information of the M second downlink data channels; Determining a first PUCCH resource set from a plurality of physical uplink control channel (PUCCH) resource sets according to a load size of the codebook, each PUCCH resource set in the plurality of PUCCH resource sets including at least one PUCCH resource; Determining a first PUCCH resource from the first PUCCH resource set according to PUCCH resource indication information PRI included in an m-th DCI, wherein the m-th DCI is a second DCI corresponding to the last HARQ-ACK information bit of the second downlink data channel in the codebook; In a third time unit, the codebook is sent using the first PUCCH resource.

2. The method according to claim 1, wherein The first type of DCI cyclic redundancy check bit is a DCI scrambled by a group radio network temporary identifier, and the second type of DCI is a DCI scrambled by a cell radio network temporary identifier, a modulation and coding mode-cell radio network temporary identifier, or a configured scheduling radio network temporary identifier CS-RNTI.

3. The method according to claim 1 or 2, wherein: The first type of DCI is sent in a first search space, and the second type of DCI is sent in a second search space different from the first search space; or The first type of DCI is sent in a common search space, and the second type of DCI is sent in a UE-specific search space; or The first type of DCI is sent within a first control channel resource set, and the second type of DCI is sent within a second control channel resource set.

4. The method according to claim 1 or 2, wherein: The first C-DAI indicates the number of DCIs of the first type sent cumulatively for scheduling physical downlink shared channel PDSCH transmission and / or for indicating semi-persistent scheduling SPS PDSCH release until the current serving cell and physical downlink control channel PDCCH detection timing; and / or, The second C-DAI indicates the cumulative number of DCIs for scheduling physical downlink shared channel PDSCH transmission and / or the second type of DCIs for indicating semi-static scheduling SPSPDSCH release sent until the current serving cell and physical downlink control channel PDCCH detection timing.

5. The method according to claim 4, wherein The counting rule of the first C-DAI is to first count in ascending order according to the serving cell index, and then count in ascending order according to the PDCCH detection timing; and / or, the counting rule of the second C-DAI is to first count in ascending order according to the serving cell index, and then count in ascending order according to the PDCCH detection timing.

6. The method according to claim 1 or 2, wherein: The first DAI further includes a first total downlink allocation index T-DAI, where the first T-DAI indicates a cumulative number of DCIs for scheduling physical downlink shared channel (PDSCH) transmission and first type DCIs for indicating semi-persistent scheduling (SPS) PDSCH release sent until a current physical downlink control channel (PDCCH) detection opportunity; and / or The second DAI also includes a second total downlink allocation index T-DAI, which represents the cumulative number of second-type DCIs sent for scheduling physical downlink shared channel PDSCH transmission and for indicating semi-static scheduling SPS PDSCH release until the current physical downlink control channel PDCCH detection timing.

7. The method according to claim 1 or 2, wherein: A timing for sending HARQ-ACK feedback information corresponding to the N first downlink data channels and the M second downlink data channels is the third time unit.

8. The method according to claim 1 or 2, wherein: The first sub-codebook is continuous bits, and the second sub-codebook is continuous bits.

9. The method according to claim 1 or 2, wherein: The generating, according to the first DAI in the N first DCIs, the second DAI in the M second DCIs, the N first downlink data channels, and the M second downlink data channels, a codebook for automatic repeat request acknowledgment HARQ-ACK feedback information includes: Generate the first subcodebook according to reception status of the N first downlink data channels and the first DAI in the N first DCIs; Generate the second subcodebook according to the reception status of the M second downlink data channels and the second DAI in the M second DCIs.

10. The method according to claim 1 or 2, wherein: The first sub-codebook and the second sub-codebook are cascaded.

11. The method according to claim 10, wherein The first subcodebook is before the second subcodebook, or the first subcodebook is after the second subcodebook.

12. A method for transmitting automatic repeat request confirmation feedback information supporting multicast services, characterized in that: include: Sending N first downlink control information DCIs and M second DCIs within at least one first time unit, where the first DCIs are DCIs of the first type, which are DCIs for multicast services, the second DCIs are DCIs of the second type, and the second type of DCIs are DCIs for unicast services, each of the first DCIs includes a first downlink allocation index DAI, the first DAI includes a first downlink allocation index counter C-DAI, and the first C-DAI indicates the cumulative number of DCIs of the first type scheduled for transmission through a downlink data channel; each of the second DCIs includes a second downlink allocation index DAI, the second DAI includes a second downlink allocation index counter C-DAI, and the second C-DAI indicates the cumulative number of DCIs of the second type scheduled for transmission through a downlink data channel; Sending N first downlink data channels and M second downlink data channels within at least one second time unit, where the N first downlink data channels are scheduled by the N first downlink control information, and the M second downlink data channels are scheduled by the M second DCIs; receiving, within a third time unit, a codebook for automatic repeat request acknowledgment HARQ-ACK feedback information, the codebook including a first sub-codebook and a second sub-codebook, the first sub-codebook including HARQ-ACK feedback information of the N first downlink data channels, and the second sub-codebook including HARQ-ACK feedback information of the M second downlink data channels; Determining a first physical uplink control channel (PUCCH) resource set from a plurality of PUCCH resource sets, each of the plurality of PUCCH resource sets including a plurality of PUCCH resources, the first PUCCH resource set corresponding to a load of the codebook to be received; Determine a first PUCCH resource from the first PUCCH resource set; Generate an m-th DCI, where the m-th DCI includes PUCCH resource indication information PRI, where the PRI is used to determine the first PUCCH resource; The mth DCI is the second DCI corresponding to the last HARQ-ACK information bit of the second downlink data channel in the codebook; The codebook for receiving automatic repeat request acknowledgment HARQ-ACK feedback information within the third time unit includes: In a third time unit, a codebook of automatic repeat request acknowledgement HARQ-ACK feedback information is received on the first PUCCH resource.

13. The method according to claim 12, wherein: The first type of DCI cyclic redundancy check bit is a DCI scrambled by a group radio network temporary identifier, and the second type of DCI is a DCI scrambled by a cell radio network temporary identifier, a modulation and coding mode-cell radio network temporary identifier, or a configured scheduling radio network temporary identifier CS-RNTI.

14. The method according to claim 12 or 13, wherein: The first type of DCI is sent in a first search space, and the second type of DCI is sent in a second search space different from the first search space; or The first type of DCI is sent in a common search space, and the second type of DCI is sent in a UE-specific search space; or The first type of DCI is sent within a first control channel resource set, and the second type of DCI is sent within a second control channel resource set.

15. The method according to claim 12 or 13, wherein: The first C-DAI indicates the number of DCIs of the first type sent cumulatively for scheduling physical downlink shared channel PDSCH transmission and / or for indicating semi-persistent scheduling SPS PDSCH release until the current serving cell and physical downlink control channel PDCCH detection timing; and / or, The second C-DAI indicates the cumulative number of DCIs for scheduling physical downlink shared channel PDSCH transmission and / or the second type of DCIs for indicating semi-static scheduling SPSPDSCH release sent until the current serving cell and physical downlink control channel PDCCH detection timing.

16. The method according to claim 15, wherein The counting rule of the first C-DAI is to first count in ascending order according to the serving cell index, and then count in ascending order according to the PDCCH detection timing and / or the counting rule of the second C-DAI is to first count in ascending order according to the serving cell index, and then count in ascending order according to the PDCCH detection timing.

17. The method according to claim 12 or 13, wherein: The first DAI also includes a first total downlink allocation index T-DAI, where the first T-DAI represents the cumulative number of DCIs for scheduling physical downlink shared channel PDSCH transmission and first type of DCIs for indicating semi-persistent scheduling SPS PDSCH release sent until the current physical downlink control channel PDCCH detection timing; and / or The second DAI also includes a second total downlink allocation index T-DAI, which represents the cumulative number of second-type DCIs sent for scheduling physical downlink shared channel PDSCH transmission and for indicating semi-static scheduling SPS PDSCH release until the current physical downlink control channel PDCCH detection timing.

18. The method according to claim 12 or 13, wherein: A timing for sending HARQ-ACK feedback information corresponding to the N first downlink data channels and the M second downlink data channels is the third time unit.

19. The method according to claim 12 or 13, wherein: The first sub-codebook is continuous bits, and the second sub-codebook is continuous bits.

20. The method according to claim 12 or 13, wherein: The first sub-codebook and the second sub-codebook are cascaded.

21. The method according to claim 20, wherein The first subcodebook is before the second subcodebook, or the first subcodebook is after the second subcodebook.

22. A communication device, characterized in that: It includes a transceiver module and a processing module, wherein: The transceiver module is configured to receive N first downlink control information DCIs and M second DCIs within at least one first time unit, where the first DCI is a first type of DCI, the first type of DCI is a DCI for a multicast service, the second DCI is a second type of DCI, and the second type of DCI is a DCI for a unicast service, each of the first DCIs includes a first downlink allocation index DAI, the first DAI includes a first downlink allocation index counter C-DAI, and the first C-DAI indicates the cumulative number of the first type of DCIs scheduled for transmission on a downlink data channel; each of the second DCIs includes a second downlink allocation index DAI, the second DAI includes a second downlink allocation index counter C-DAI, and the second C-DAI indicates the cumulative number of the second type of DCIs scheduled for transmission on a downlink data channel; The transceiver module is further configured to receive, within at least one second time unit, N first downlink data channels and M second downlink data channels, wherein the N first downlink data channels are scheduled by the N first downlink control information, and the M second downlink data channels are scheduled by the M second DCIs; The processing module is configured to generate a codebook for automatic repeat request acknowledgment HARQ-ACK feedback information according to the first DAI in the N first DCIs, the second DAI in the M second DCIs, the N first downlink data channels, and the M second downlink data channels, the codebook including a first sub-codebook and a second sub-codebook, the first sub-codebook including ARQ-ACK feedback information of the N first downlink data channels, and the second sub-codebook including HARQ-ACK feedback information of the M second downlink data channels; and The processing module is further configured to determine a first PUCCH resource set from a plurality of physical uplink control channel (PUCCH) resource sets according to a load size of the codebook, each PUCCH resource set in the plurality of PUCCH resource sets including at least one PUCCH resource; The processing module is further configured to determine a first PUCCH resource from the first PUCCH resource set according to PUCCH resource indication information PRI included in the mth DCI; the mth DCI being the second DCI corresponding to the last HARQ-ACK information bit of the second downlink data channel in the codebook; The transceiver module is further configured to send the codebook using the first PUCCH resource within a third time unit.

23. The communication device according to claim 22, wherein: The first type of DCI cyclic redundancy check bit is a DCI scrambled by a group radio network temporary identifier, and the second type of DCI is a DCI scrambled by a cell radio network temporary identifier, a modulation and coding mode-cell radio network temporary identifier, or a configured scheduling radio network temporary identifier CS-RNTI.

24. The communication device according to claim 22 or 23, wherein: The first type of DCI is sent in a first search space, and the second type of DCI is sent in a second search space different from the first search space; or The first type of DCI is sent in a common search space, and the second type of DCI is sent in a UE-specific search space; or The first type of DCI is sent within a first control channel resource set, and the second type of DCI is sent within a second control channel resource set.

25. The communication device according to claim 22 or 23, wherein: The first C-DAI indicates the number of DCIs of the first type sent cumulatively for scheduling physical downlink shared channel PDSCH transmission and / or for indicating semi-persistent scheduling SPS PDSCH release until the current serving cell and physical downlink control channel PDCCH detection timing; and / or, The second C-DAI indicates the cumulative number of DCIs for scheduling physical downlink shared channel PDSCH transmission and / or the second type of DCIs for indicating semi-static scheduling SPSPDSCH release sent until the current serving cell and physical downlink control channel PDCCH detection timing.

26. The communication device according to claim 25, wherein The counting rule of the first C-DAI is to first count in ascending order according to the serving cell index, and then count in ascending order according to the PDCCH detection timing; and / or, the counting rule of the second C-DAI is to first count in ascending order according to the serving cell index, and then count in ascending order according to the PDCCH detection timing.

27. The communication device according to claim 22 or 23, wherein: The first DAI also includes a first total downlink allocation index T-DAI, where the first T-DAI represents the cumulative number of DCIs for scheduling physical downlink shared channel PDSCH transmission and first type of DCIs for indicating semi-persistent scheduling SPS PDSCH release sent until the current physical downlink control channel PDCCH detection timing; and / or The second DAI also includes a second total downlink allocation index T-DAI, which represents the cumulative number of second-type DCIs sent for scheduling physical downlink shared channel PDSCH transmission and for indicating semi-static scheduling SPS PDSCH release until the current physical downlink control channel PDCCH detection timing.

28. The communication device according to claim 22 or 23, wherein: A timing for sending HARQ-ACK feedback information corresponding to the N first downlink data channels and the M second downlink data channels is the third time unit.

29. The communication device according to claim 22 or 23, wherein: The first sub-codebook is continuous bits, and the second sub-codebook is continuous bits.

30. The communication device according to claim 22 or 23, wherein: The generating, according to the first DAI in the N first DCIs, the second DAI in the M second DCIs, the N first downlink data channels, and the M second downlink data channels, a codebook for automatic repeat request acknowledgment HARQ-ACK feedback information includes: Generate the first subcodebook according to reception status of the N first downlink data channels and the first DAI in the N first DCIs; Generate the second subcodebook according to the reception status of the M second downlink data channels and the second DAI in the M second DCIs.

31. The communication device according to claim 22 or 23, wherein: The first sub-codebook and the second sub-codebook are cascaded.

32. The communication device according to claim 31, wherein The first subcodebook is before the second subcodebook, or the first subcodebook is after the second subcodebook.

33. A communication device, characterized in that: It includes a processing module and a transceiver module, wherein: The transceiver module is used to send N first downlink control information DCI and M second DCI within at least one first time unit, where the first DCI is a first type of DCI, the first type of DCI is a DCI for a multicast service, the second DCI is a second type of DCI, and the second type of DCI is a DCI for a unicast service, each of the first DCIs includes a first downlink allocation index DAI, the first DAI includes a first downlink allocation index counter C-DAI, and the first C-DAI indicates the cumulative number of the first type of DCIs scheduled for transmission on a downlink data channel; each of the second DCIs includes a second downlink allocation index DAI, the second DAI includes a second downlink allocation index counter C-DAI, and the second C-DAI indicates the cumulative number of the second type of DCIs scheduled for transmission on a downlink data channel; The transceiver module is further configured to send N first downlink data channels and M second downlink data channels within at least one second time unit, where the N first downlink data channels are scheduled by the N first downlink control information, and the M second downlink data channels are scheduled by the M second DCIs; The transceiver module is further configured to receive a codebook of automatic repeat request confirmation HARQ-ACK feedback information within a third time unit; The processing module is configured to determine HARQ-ACK feedback information from the codebook, wherein the codebook includes a first sub-codebook and a second sub-codebook, the first sub-codebook includes HARQ-ACK feedback information of the N first downlink data channels, and the second sub-codebook includes HARQ-ACK feedback information of the M second downlink data channels; The processing module is further configured to determine a first PUCCH resource set from a plurality of physical uplink control channel (PUCCH) resource sets, each of the plurality of PUCCH resource sets including a plurality of PUCCH resources, the first PUCCH resource set corresponding to a load of the codebook to be received; The processing module is further configured to determine a first PUCCH resource from the first PUCCH resource set; The processing module is further configured to generate an mth DCI, where the mth DCI includes PUCCH resource indication information PRI, where the PRI is used to determine the first PUCCH resource; the mth DCI is a second DCI corresponding to the last HARQ-ACK information bit of the second downlink data channel in the codebook; The codebook for the transceiver module to receive automatic repeat request confirmation HARQ-ACK feedback information within the third time unit includes: The transceiver module is configured to receive a codebook of automatic repeat request confirmation HARQ-ACK feedback information on the first PUCCH resource within a third time unit.

34. The communication device according to claim 33, wherein: The first type of DCI cyclic redundancy check bit is a DCI scrambled by a group radio network temporary identifier, and the second type of DCI is a DCI scrambled by a cell radio network temporary identifier, a modulation and coding mode-cell radio network temporary identifier, or a configured scheduling radio network temporary identifier CS-RNTI.

35. The communication device according to claim 33 or 34, characterized in that The first type of DCI is sent in a first search space, and the second type of DCI is sent in a second search space different from the first search space; or The first type of DCI is sent in a common search space, and the second type of DCI is sent in a UE-specific search space; or The first type of DCI is sent within a first control channel resource set, and the second type of DCI is sent within a second control channel resource set.

36. The communication device according to claim 33 or 34, characterized in that The first C-DAI indicates the number of DCIs of the first type sent cumulatively for scheduling physical downlink shared channel PDSCH transmission and / or for indicating semi-persistent scheduling SPS PDSCH release until the current serving cell and physical downlink control channel PDCCH detection timing; and / or, The second C-DAI indicates the cumulative number of DCIs for scheduling physical downlink shared channel PDSCH transmission and / or the second type of DCIs for indicating semi-static scheduling SPSPDSCH release sent until the current serving cell and physical downlink control channel PDCCH detection timing.

37. The communication device according to claim 36, wherein: The counting rule of the first C-DAI is to first count in ascending order according to the serving cell index, and then count in ascending order according to the PDCCH detection timing; and / or, the counting rule of the second C-DAI is to first count in ascending order according to the serving cell index, and then count in ascending order according to the PDCCH detection timing.

38. The communication device according to claim 33 or 34, wherein: The first DAI also includes a first total downlink allocation index T-DAI, where the first T-DAI represents the cumulative number of DCIs for scheduling physical downlink shared channel PDSCH transmission and first type of DCIs for indicating semi-persistent scheduling SPS PDSCH release sent until the current physical downlink control channel PDCCH detection timing; and / or The second DAI also includes a second total downlink allocation index T-DAI, which represents the cumulative number of second-type DCIs sent for scheduling physical downlink shared channel PDSCH transmission and for indicating semi-static scheduling SPS PDSCH release until the current physical downlink control channel PDCCH detection timing.

39. The communication device according to claim 33 or 34, wherein: A timing for sending HARQ-ACK feedback information corresponding to the N first downlink data channels and the M second downlink data channels is the third time unit.

40. The communication device according to claim 33 or 34, wherein: The first sub-codebook is continuous bits, and the second sub-codebook is continuous bits.

41. The communication device according to claim 33 or 34, wherein: The first sub-codebook and the second sub-codebook are cascaded.

42. The communication device according to claim 41, wherein The first subcodebook is before the second subcodebook, or the first subcodebook is after the second subcodebook.

43. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which, when executed on a computer, enables the computer to execute the method according to any one of claims 1 to 11, or enables the computer to execute the method according to any one of claims 12 to 21.

44. A computer program product, characterized in that The computer program product is used to store a computer program, and when the computer program is executed by a computer, the computer is caused to implement the method according to any one of claims 1 to 11, or the computer is caused to implement the method according to any one of claims 12 to 21.

Images