Method and device for transmitting automatic repeat request acknowledgement feedback information supporting multicast service

Abstract

A method and apparatus for transmitting automatic repeat request acknowledgement feedback information supporting multicast service, the method comprising: receiving N pieces of first downlink control information (DCI) and M pieces of second DCI in at least one first time unit, the first DCI being DCI of a first type, the second DCI being DCI of a second type, each first DCI comprising a first downlink allocation index (DAI), each second DCI comprising a second downlink allocation index (DAI) of a second type, the first DAI comprises a first downlink allocation index counter (C-DAI), and the first C-DAI indicates the cumulative number of the DCI of the first type transmitted by scheduling a downlink data channel; each piece of second DCI comprises a second downlink allocation index (DAI), the second DAI comprises a second downlink allocation index counter (C-DAI), and the second C-DAI indicates the cumulative number of the DCI of the second type transmitted by scheduling a downlink data channel; and receiving N first downlink data channels and M second downlink data channels in at least one second time unit, generating a codebook of automatic repeat request acknowledgement (HARQ-ACK) feedback information, and sending the codebook in a third time unit.

Description

[0001] This application is a divisional application of Chinese patent application filed on May 7, 2020, with application number 202080099770.X and invention title "A method and apparatus for transmitting automatic retransmission request confirmation feedback information supporting multicast services". Technical Field

[0002] This invention relates to the field of communication technology, and in particular to a method and apparatus for transmitting automatic retransmission request acknowledgment feedback information that supports multicast services. Background Technology

[0003] The International Telecommunication Union (ITU) has defined three main 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), 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 haptic interaction applications such as remote repair and remote surgery, characterized by requirements for ultra-high reliability, low latency, relatively small data volumes, and bursty nature. Typical mMTC services include smart grid distribution automation and smart cities, characterized by a large number of connected devices, relatively small data volumes, and low sensitivity to transmission latency; these mMTC terminals need to meet the requirements of low cost and very long standby time.

[0004] Research on wireless broadcasting / multicast services has continued unabated in recent years. The proliferation of mobile data multimedia services and various high-bandwidth multimedia services (such as Interactive Network Television (IPT) and mobile television), along with the provision of robust and essential communication services (such as group communications in disaster situations and public safety networks), has placed higher demands on broadcasting / multicast services. These mobile data multimedia services require multiple users to simultaneously receive the same data, and compared to general data services, they are characterized by large data volumes, long durations, and latency sensitivity.

[0005] The 3rd Generation Partnership Project (3GPP) 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 that transmits data from one data source to multiple target mobile terminals, enabling resource sharing between the core network and access network and improving the utilization of network resources (especially air interface resources). The MBMS service defined by 3GPP can not only realize low-bitrate plain text message multicast and broadcast, but also high-speed multimedia service broadcast and multicast, providing a variety of rich video, audio, and multimedia services. The characteristics of broadcast services enable better efficiency in sending information of public interest, which undoubtedly conforms to the future trend of mobile data development and provides a better business prospect for the development of communication technology.

[0006] Existing 5G New Radio (NR) supports unicast service transmission with a hybrid automatic repeat request (HARQ) mechanism. During this 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). Upon receiving the PDSCH, the UE needs to send an HARQ-ACK feedback message to the gNB, informing the gNB of the UE's reception status of the PDSCH. The HARQ-ACK feedback message is carried on either the PUCCH or PUSCH. If the UE receives the PDSCH correctly, it sends an acknowledgment (ACK) to the gNB. Upon 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. Upon receiving the NACK, the gNB can schedule the retransmission of the PDSCH.

[0007] Taking sending HARQ-ACK feedback information on the PUCCH as an example, the UE needs to determine the PUCCH resources carrying the HARQ-ACK before sending the feedback information. The UE receives the PDSCH-to-HARQ_feedback timing indicator (K1), which can be carried in the downlink control information (DCI) or configured by higher-layer parameters. This indicator information is used to represent the time unit offset between the PDSCH and HARQ. This time unit can be, for example, a time slot. After determining the time unit carrying the HARQ transmission, the UE selects the PUCCH resource set according to the HARQ-ACK load size in that time unit. This load refers to the number of HARQ-ACK feedback messages that need to be sent in that time unit.

[0008] like Figure 1a As shown, a simple example is given below. The gNB schedules the transmission of PDSCH#1 in time slot #1 via DCI#1, and the HARQ feedback timing indicator K1_1 in DCI#1 indicates an offset of 4 slots for HARQ-ACK feedback. Similarly, the gNB schedules the transmission of PDSCH#2 in time slot #2 via DCI#2, and the HARQ feedback timing indicator K1_2 in DCI#2 indicates an offset of 3 slots for HARQ-ACK feedback. The gNB schedules the transmission of PDSCH#3 in time slot #3 via DCI#3, and the HARQ feedback timing indicator K1_3 in DCI#3 indicates an offset of 2 slots for HARQ-ACK feedback. Therefore, HARQ-ACK feedback information for PDSCH#1, PDSCH#2, and PDSCH#3 needs to be fed back in time slot #5. In other words, in slot #5, the UE needs to provide 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.

[0009] However, if the UE fails to successfully receive one of the three scheduled PDSCH DCIs, the corresponding PDSCH will also not be received. Since the UE only perceives two scheduled PDSCH transmissions, it will only send back a 2-bit HARQ-ACK feedback message. However, the gNB does not know which DCI the UE failed to receive, nor does it know which two PDSCHs the UE's 2-bit HARQ-ACK feedback message is for, ultimately leading to a HARQ feedback error. Existing 5G NR standards use a dynamic codebook mechanism to address this issue.

[0010] Under the dynamic codebook mechanism, the downlink scheduling information includes the downlink assignment index (DAI). The DAI field is divided into two parts: the counter-DAI (C-DAI) and the total-DAI (T-DAI). C-DAI represents the cumulative number of DCIs sent for scheduling PDSCH transmissions and indicating the release of semi-statically scheduled (SPS) PDSCHs up to the current serving cell and PDCCH detection time. The counting rule for C-DAI is first counted according to the serving cell dimension (e.g., ascending order of the serving cell index), and then according to the time dimension (e.g., ascending order of the PDCCH detection time). T-DAI represents the cumulative number of DCIs sent for scheduling PDSCH transmissions and indicating the release of semi-statically scheduled (SPS) PDSCHs up to the current PDCCH detection time. Therefore, the value of T-DAI is updated over time. Back-off DCI (e.g., DCI format 1_0) may contain only DAI count information, while non-back-off 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.

[0011] like Figure 1bAs shown, for example, starting from time slot 1, the gNB transmits DCI 1, DCI 2, and DCI 3 on serving cell 1, serving cell 2, and serving cell 3 respectively to schedule PDSCH 1-3 transmissions. It is assumed that serving cells 1 and 3 transmit non-backoff DCI 1 and DCI 3, while serving cell 2 transmits backoff DCI 2. Since the C-DAI counting rule is to count in ascending order by serving cell index, the C-DAI value of DCI 1 is 1, the C-DAI value of DCI 2 is 2, and the C-DAI value of DCI 3 is 3. In the current time slot 1, a total of 3 DCIs for scheduling PDSCH transmissions are transmitted, and the T-DAI values ​​of DCI 1 and DCI 3 are both 3. Since DCI 2 is a backoff DCI, it only contains the C-DAI field and not the T-DAI field. In time slot 2, the gNB transmits DCI 4, which schedules PDSCH 4 transmission, 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 time slot 3, the gNB transmits DCI 5, which schedules PDSCH 5 transmission, on serving cell 1, and transmits 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 prerequisite for the C-DAI and T-DAI in a DCI to be cumulatively counted with at least one previous DCI can be, for example, that the PDSCH scheduled by this DCI and the PDSCH scheduled by the previous at least one DCI need to have HARQ-ACK feedback in the same time slot.

[0012] The dynamic codebook includes HARQ-ACK information for X PDSCHs, where X is the maximum T-DAI value among multiple DCIs that schedule PDSCH transmissions and require HARQ-ACH feedback in the same time slot. The HARQ-ACK feedback information for a PDSCH scheduled by a certain DCI is arranged at the Y-th position in the dynamic codebook, where Y equals the C-DAI value of that DCI. After the UE arranges the HARQ-ACK information corresponding to all detected DCI scheduled data, it fills the remaining unfilled HARQ-ACK positions in the dynamic codebook with NACK. Upon receiving this, the gNB will know 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.

[0013] like Figure 1c As shown, for Figure 1b The PDSCH transmission will form as follows Figure 1cThe dynamic codebook is shown. Since there are 6 PDSCHs that need to provide HARQ-ACK feedback in the same time slot, and the maximum value of T-DAI is 6, the dynamic codebook consists of 6 bits. The HARQ-ACK feedback information for PDSCH1-6 corresponds to bits 1-6 of the dynamic codebook, respectively. Assuming that the DCI used to schedule the transmission of PDSCH 5 is not detected by the UE, the UE will provide NACK feedback on bit 5. Thus, the gNB will retransmit the PDSCH 5 information to the UE in subsequent transmissions.

[0014] However, there is currently no similar HARQ-ACK feedback mechanism for multicast transmission. Suppose we apply the dynamic codebook mechanism from unicast transmission to a multicast transmission scenario, such as... Figure 1d As shown, to implement multicast services, the gNB needs to send multicast DCI (i.e., g-DCI) to multiple UEs (such as UE1 to UE3 in the figure) in the same time slot to schedule PDSCH transmission. However, since each UE has previously received different unicast PDSCH information, the bit positions of the multicast PDSCH in the dynamic codebook are also different for different UEs. Therefore, the DAI value in g-DCI is not the same 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

[0015] This invention provides a method and apparatus for transmitting automatic retransmission request acknowledgment feedback information that supports multicast services.

[0016] A first aspect of this invention provides a method for transmitting automatic retransmission request acknowledgment feedback information supporting multicast services, comprising:

[0017] Within at least one first time unit, N first downlink control information (DCI) and M second DCI are received. The first DCI is a first type of DCI, and the second DCI is a second type of DCI. Each first DCI includes a first downlink allocation index (DAI), and the first DAI includes a first downlink allocation index counter (C-DAI), which indicates the cumulative number of first type DCIs scheduled for downlink data channel transmission. Each second DCI includes a second downlink allocation index (DAI), and the second DAI includes a second downlink allocation index counter (C-DAI), which indicates the cumulative number of second type DCIs scheduled for downlink data channel transmission.

[0018] Within at least one second time unit, N first downlink data channels and M second downlink data channels are received, 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;

[0019] 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, a codebook for Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback information is generated. The codebook includes a first sub-codebook and a second sub-codebook. The first sub-codebook includes HARQ-ACK feedback information for the N first downlink data channels, and the second sub-codebook includes HARQ-ACK feedback information for the M second downlink data channels.

[0020] The codebook is sent within the third time unit.

[0021] A second aspect of this invention provides a method for transmitting automatic retransmission request acknowledgment feedback information supporting multicast services, comprising:

[0022] Within at least one first time unit, N first downlink control information (DCI) and M second DCI are transmitted. The first DCI is a first type of DCI, and the second DCI is a second type of DCI. Each first DCI includes a first downlink allocation index (DAI), and the first DAI includes a first downlink allocation index counter (C-DAI), which indicates the cumulative number of first type DCIs scheduled for downlink data channel transmission. Each second DCI includes a second downlink allocation index (DAI), and the second DAI includes a second downlink allocation index counter (C-DAI), which indicates the cumulative number of second type DCIs scheduled for downlink data channel transmission.

[0023] N first downlink data channels and M second downlink data channels are transmitted within at least one second time unit, 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;

[0024] The codebook for receiving HARQ-ACK feedback information for Automatic Repeat Requests within the third time unit includes a first sub-codebook and a second sub-codebook. The first sub-codebook includes HARQ-ACK feedback information for the N first downlink data channels, and the second sub-codebook includes HARQ-ACK feedback information for the M second downlink data channels.

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

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

[0027] 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, 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;

[0028] The processing module is configured to generate 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. The codebook includes a first sub-codebook and a second sub-codebook. The first sub-codebook includes HARQ-ACK feedback information for the N first downlink data channels, and the second sub-codebook includes HARQ-ACK feedback information for the M second downlink data channels.

[0029] The transceiver module is also used to send the codebook within the third time unit.

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

[0031] The transceiver module is configured to transmit N first downlink control information (DCI) and M second DCI within at least one first time unit. The first DCI is a first type of DCI, and the second DCI is a second type of DCI. Each first DCI includes a first downlink allocation index (DAI), and the first DAI includes a first downlink allocation index counter (C-DAI), which indicates the cumulative number of first type DCIs scheduled for downlink data channel transmission. Each second DCI includes a second downlink allocation index (DAI), and the second DAI includes a second downlink allocation index counter (C-DAI), which indicates the cumulative number of second type DCIs scheduled for downlink data channel transmission.

[0032] The transceiver module is also configured to transmit N first downlink data channels and M second downlink data channels within at least one second time unit, 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;

[0033] The transceiver module is also used to receive the codebook of HARQ-ACK feedback information within the third time unit;

[0034] The processing module is used 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 for the N first downlink data channels, and the second sub-codebook includes HARQ-ACK feedback information for the M second downlink data channels.

[0035] By employing the embodiments 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 set correctly and reasonably for unicast and multicast services respectively. 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, ensuring the reliability of the HARQ-ACK feedback information corresponding to the multicast downlink data channel. Attached Figure Description

[0036] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

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

[0038] Figure 1b This is a schematic diagram illustrating the HARQ-ACK feedback method using a dynamic codebook in traditional unicast services;

[0039] Figure 1c yes Figure 1b A schematic diagram of the dynamic codebook structure used in the document;

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

[0041] Figure 2 This is a schematic diagram of the architecture of a mobile communication system used in an embodiment of this application.

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

[0043] Figure 4 yes Figure 3 The diagram illustrates the DCI and downlink data channel configurations transmitted to terminal device 32.

[0044] Figure 5 yes Figure 4 A schematic diagram of DAI examples contained in the DCI.

[0045] Figure 6 Is Figure 4 and Figure 5 The diagram shows how the terminal device generates the corresponding codebook in the case of DCI transmission.

[0046] Figure 7 A schematic block diagram of a communication device 1100 provided in an embodiment of this application.

[0047] Figure 8 A schematic block diagram of a communication device 2100 provided in an embodiment of this application. Detailed Implementation

[0048] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0049] Figure 2 This is a schematic diagram of the architecture of a mobile communication system used in an embodiment of this application. Figure 2As shown, the mobile communication system includes core network equipment 210, radio access network equipment 220, and at least one terminal device (such as...). Figure 2 The terminal devices 230 and 240 are listed in the text. The terminal devices connect wirelessly to the wireless access network equipment, which in turn connects wirelessly or via a wired connection to the core network equipment. The core network equipment and the wireless access network equipment can be independent physical devices, or they can integrate the functions of the core network equipment and the logical functions of the wireless access network equipment onto the same physical device. Alternatively, a single physical device can integrate some of the functions of the core network equipment and some of the functions of the wireless access network equipment. The terminal devices can be fixed in location or mobile. Figure 2 This is just an illustration; the communication system may also include other network devices, such as wireless repeaters and wireless backhaul devices. Figure 2 Not shown in the diagram. The embodiments of this application do not limit the number of core network devices, radio access network devices, and terminal devices included in the mobile communication system.

[0050] The wireless access network device in this application embodiment is a device in a network system that wirelessly connects with terminal devices via an air interface, enabling the terminal devices to access the network through the air interface. Specifically, the wireless access network device may be a NodeB, an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc. This application embodiment does not limit the specific technology or device form used in the wireless access network device.

[0051] The terminal device in this application embodiment is an information processing device with wireless communication capabilities. 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, tablet computer, computer with wireless transceiver capabilities, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal device.

[0052] Wireless access network equipment and terminal equipment 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 the wireless access network equipment and terminal equipment.

[0053] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0054] The terms "first" and "second," etc., used in the specification and claims of this application are used to distinguish different objects, not to describe a specific order of objects. For example, "first target object" and "second target object," etc., are used to distinguish different target objects, not to describe a specific order of target objects.

[0055] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

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

[0057] Please refer to Figure 3 , Figure 3 This is a schematic flowchart illustrating a method for transmitting automatic retransmission request acknowledgment feedback information supporting multicast services, provided in an embodiment of this application. The method will now be described in detail with reference to the accompanying drawings.

[0058] 301: The access network device sends N first downlink control information (DCI) messages and M second DCI messages, and correspondingly, the terminal device receives N first downlink control information (DCI) messages and M second DCI messages.

[0059] 302: The access network device sends N first downlink data channels and M second downlink data channels, and correspondingly, the terminal device receives 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.

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

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

[0062] The type of DCI can be distinguished according to the identifier used for cyclic redundancy check (CRC) scrambling of the DCI. For example, the first type of DCI is a DCI whose CRC scrambling is done by the group radio network temporary identifier, and the second type of DCI is a DCI whose CRC scrambling is done by the cell radio network temporary identifier, the modulation and coding scheme-cell radio network temporary identifier, or the configured scheduling radio network temporary identifier CS-RNTI.

[0063] The type of DCI can be distinguished according to the type of service or scheduling method it schedules. For example, the first type of DCI is for scheduling multicast service transmission, and the second type of DCI is for scheduling unicast service transmission.

[0064] The type of DCI can be distinguished according to the location / area of ​​transmission or search. For example, the first type of DCI is transmitted in a first search space, and the second type of DCI is transmitted in a second search space different from the first search space. As another example, the first type of DCI is transmitted in a public search space, and the second type of DCI is transmitted in a UE-dedicated search space; the first type of DCI is transmitted in a first control channel resource set, and the second type of DCI is transmitted in a second control channel resource set.

[0065] It should be noted that the above-mentioned classification methods for DCI types can exist independently, or multiple classification methods can coexist and correspond or be related to 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. In this case, the first type of DCI has its cyclic redundancy check bit scrambled by the group radio network temporary identifier, and the second type of DCI has its cyclic redundancy check bit scrambled by the cell radio network temporary identifier, the modulation and coding scheme-cell radio network temporary identifier, or the configured scheduling radio network temporary identifier CS-RNTI. In this case, the first type of multicast service DCI can be arranged to be transmitted in the common search space, and the second type of unicast service DCI can be arranged to be transmitted in the UE-dedicated search space; or similarly, the first type of DCI can be transmitted in the first control channel resource set, and the second type of DCI can be transmitted in the second control channel resource set.

[0066] Temporal Relationship

[0067] Steps 301 and 302 do not have a strict order; that is, it is not required that step 302 be executed only after step 301 has been fully executed. The timing relationship between steps 301 and 302 can be parallel, partially parallel, or interleaved.

[0068] Specifically, N first downlink control information (DCI) messages and M second DCI messages 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. The at least one first time unit and the at least one second time unit may not overlap completely, may partially overlap, or may be completely identical (i.e., completely overlap). In various embodiments of this application, the time unit may be a slot, a mini-slot, or other time lengths composed of multiple time-domain symbols.

[0069] For example, such as Figure 3As shown, within time slot 1, on the first serving cell, access network device 31 sends a second DCI to terminal device 32. Since the second DCI is used to schedule unicast service transmission, user equipment 33a-33n will not receive it. Subsequently, terminal device 32 receives the second downlink data channel scheduled by the second DCI. It should be understood that the above explanation uses only one serving cell as an example. When there are multiple serving cells between access network device 31 and terminal device 32, such as three serving cells, the aforementioned DCI transmission and data channel transmission can be performed simultaneously on each of the three serving cells.

[0070] Within time slot 2, for example in the second and third serving cells, access network device 31 sends a first DCI to terminal device 32 and multiple other terminal devices 33a-33n. Since this first DCI is used to schedule multicast service transmission, it is sent to multiple terminal devices 32, 33a-33n. This first DCI schedules the transmission of a first downlink data channel within time slot 2. This first downlink data channel carries multicast services, and multiple terminal devices 32, 33a-33n receive this first downlink data channel in both the second and third serving cells. Within time slot 2, for example in the first serving cell, access network device 31 can also send a second DCI to terminal device 32 to schedule unicast service transmission, a process similar to that described in time slot 1, and will not be repeated here.

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

[0072] Further integration Figure 4 , Figure 4 yes Figure 3 The diagram illustrates the DCI and downlink data channel configurations transmitted to terminal device 32. This example uses three serving cells between access network device 31 and terminal device 32. It should be understood that the presence of any one or two serving cells, or even more, is feasible. In the diagram, uDCI represents the second DCI used for scheduling unicast services, and uPDSCH represents the second downlink data channel. gDCI represents the first DCI used for scheduling multicast services, and gPDSCH represents the first downlink data channel. The DCI can be transmitted via the Physical Downlink Control Channel (PDCCH).

[0073] Within time slot 1, access network device 31 can schedule the transmission of uPDSCH1-3 by sending uDCI1-3 through serving cells 1-3 respectively. Within time slot 2, access network device 31 can schedule the transmission of gPDSCH1-2 using gDCI1-2 through serving cells 2-3 respectively, and schedule the transmission of uPDSCH4 using uDCI4 through serving cell 1. Similarly, within time slot 3, access network device 31 can schedule the transmission of uPDSCH5-6 using uDCI5-6 through serving cells 1 and 3 respectively, and schedule the transmission of gPDSCH3 using gDCI3 through serving cell 2.

[0074] DCI format and information

[0075] 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), the first C-DAI indicating the cumulative number of the first type of DCIs used to schedule downlink data channel transmissions; each of the second DCIs includes a second downlink allocation index (DAI), the second DAI including a second downlink allocation index counter (C-DAI), the second C-DAI indicating the cumulative number of the second type of DCIs used to schedule downlink data channel transmissions. That is, for C-DAI, in this embodiment of the application, the first DCIs used for scheduling multicast services and the second DCIs used for scheduling unicast services are counted separately. Specifically, the first C-DAI is the accumulation of the first DCIs used for scheduling multicast services, and the second C-DAI is the accumulation of the second DCIs used for scheduling unicast services.

[0076] Specifically, for example, considering scenarios where there can be more than one serving cell between the access network device and the terminal device, the first C-DAI can indicate the cumulative number of DCIs sent for scheduling the Physical Downlink Shared Channel (PDSCH) transmission and / or for indicating the release of the semi-static scheduling SPSPDSCH up to the detection time of the current serving cell and the Physical Downlink Control Channel (PDCCH). And / or, the second C-DAI can indicate the cumulative number of DCIs sent for scheduling the Physical Downlink Shared Channel (PDSCH) transmission and / or for indicating the release of the semi-static scheduling SPS PDSCH up to the detection time of the current serving cell and the Physical Downlink Control Channel (PDCCH).

[0077] The counting rule for the first C-DAI could 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 for the second C-DAI could 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.

[0078] The first DAI may further include a first total downlink allocation index T-DAI, which indicates the cumulative number of DCIs transmitted for scheduling physical downlink shared channel (PDSCH) transmission and for indicating the release of semi-statically scheduled (SPS) PDSCH up to the current physical downlink control channel (PDCCH) detection time. Similarly, the second DAI also includes a second total downlink allocation index T-DAI, which indicates the cumulative number of DCIs transmitted for scheduling physical downlink shared channel (PDSCH) transmission and for indicating the release of semi-statically scheduled (SPS) PDSCH up to the current physical downlink control channel (PDCCH) detection time.

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

[0080] Furthermore, it should be noted that, considering the capacity limitations of DCI, in order to save the bit overhead of DCI, the aforementioned C-DAI and T-DAI can be represented using a 2-bit loopback. That is, assuming that the actual value of C-DAI or T-DAI in decimal representation is set to X, then the C-DAI or T-DAI contained in DCI is Xmod4, where Xmod4 represents the remainder obtained by dividing X by 4.

[0081] The timing of PDCCH detection includes available time units for sending PDCCH or DCI to the terminal device, or time units when the terminal device needs to detect PDCCH or DCI. In various embodiments of this application, the time unit can be a slot, a mini-slot, or other time lengths composed of multiple time-domain symbols.

[0082] Refer to together Figure 5 , Figure 5 yes Figure 4 A schematic diagram of DAI examples contained in the DCI. Figure 4 The DAI contained in each CDI is represented in the format (C, T), where C represents the value of C-DAI and T represents the value of T-DAI. Here, it is assumed for example that time slots 1-3 are all PDCCH detection times, and uDCI2 and uDCI5 are fallback DCIs, not containing T-DAI. The other DCIs are non-fallback DCIs, containing T-DAI. If the T position has no value, it means that the DCI does not contain T-DAI.

[0083] Because the C-DAI counting rule is frequency domain first, then time domain, that is, first counting in ascending order according to the serving cell index, and then counting in ascending order according to the PDCCH detection timing, since... Figure 4 uDCI1 is located in serving cell 1 and time slot 1, therefore its second C-DAI value is 1. Correspondingly, uDCI2 and iDCI3, also located in time slot 1, are in serving cells 2 and 3 respectively. Following the frequency domain priority principle, their second C-DAI values ​​are 2 and 3. Since the cumulative number of second DCIs transmitted during the current PDCCH detection time (time slot 1) is 3, the second T-DAI value for both non-backoff uDCI1 and non-backoff uDCI2 is 3. Backoff uDCI2 does not include a second T-DAI.

[0084] In time slot 2, since uDCI4 is still the second DCI, the values ​​of the second C-DAI and second T-DAI contained in uDCI4 are the cumulative number of the second DCIs (i.e., uDCI1-3) in time slot 1. However, gDCI1 transmitted through serving cell 2 and gDCI2 transmitted through serving cell 3 are both first DCIs, and their first C-DAI needs to be accumulated separately. Therefore, for gDCI1, since one first DCI has been transmitted cumulatively up to the current serving cell (i.e., serving cell 2) and the current PDCCH detection time (time slot 2), the first C-DAI value of gDCI1 is 1. For gDCI2, since two first DCIs have been transmitted cumulatively up to the current serving cell (i.e., serving cell 3) and the current PDCCH detection time (time slot 2), the first C-DAI value of gDCI1 is 2. Since the cumulative number of first DCIs transmitted up to the current PDCCH detection time (i.e., time slot 2) is 2, the first C-DAI values ​​in both gDCI1 and gDCI2 are 2.

[0085] Similarly, in time slot 3, the backoff uDCI5 is the 5th second DCI cumulatively transmitted up to time slot 3 and serving cell 1, therefore the second C-DAI value in uDCI5 is 5, and it does not include T-DAI. The non-backoff uDCI6 is the 6th second DCI cumulatively transmitted up to time slot 3 and serving cell 3, therefore the second C-DAI value in uDCI6 is 6, and the second T-DAI value is 6. gDCI3 is the 3rd first DCI cumulatively transmitted up to time slot 3 and serving cell 2, therefore the first C-DAI value in gDCI3 is 3. Up to time slot 3, the cumulative number of first T-DAIs transmitted is 3, therefore the first T-DAI value in gDCI3 is 3.

[0086] It should be understood that in this embodiment, the HARQ-ACK feedback information transmission 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 transmission timing is the same time unit, which is referred to as the third time unit in this embodiment.

[0087] In one specific implementation, the access network device can send a PDSCH-to-HARQ feedback timing indicator (K1) to the terminal device. This indicator can be carried in the downlink control information (DCI), for example, in the first or second DCI, or configured by higher-layer parameters. This indicator information is used to indicate the time unit offset between the PDSCH and HARQ. Accordingly, the terminal device can receive the PDSCH-to-HARQ feedback timing indicator K1 to determine the timing of the HARQ feedback information corresponding to the PDSCH.

[0088] 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. The codebook includes a first sub-codebook and a second sub-codebook. The first sub-codebook includes the HARQ-ACK feedback information of the N first downlink data channels, and the second sub-codebook includes the HARQ-ACK feedback information of the M second downlink data channels.

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

[0090] The first sub-codebook consists of consecutive bits, and the second sub-codebook consists of consecutive bits. The codebook can be composed of consecutive bits, meaning the bits in the first sub-codebook and the bits in the second sub-codebook are consecutive or concatenated, with the first sub-codebook preceding or following the second sub-codebook. The codebook can also consist of non-consecutive bits, but the first sub-codebook and the second sub-codebook still consist of consecutive bits. In other words, the first and second sub-codebooks can be independent and non-consecutive; the codebook is simply a logical set that includes both the first and second sub-codebooks.

[0091] In one specific implementation, the total number of bits in the first sub-codebook (i.e., the payload size of the first sub-codebook) is equal to the maximum C-DAI value among the N received first DCIs, or the total number of bits in the first sub-codebook is the maximum T-DAI value among the N received first DCIs. Furthermore, the i-th bit in this first sub-codebook is used to feed back 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. Here, 1 ≤ i ≤ N, and i is a positive integer. If the terminal device does not receive the i-th first DCI, then the i-th bit is set to NACK or 0.

[0092] Similarly, the total number of bits in the second sub-codebook (i.e., the payload size of the second sub-codebook) is equal to the maximum value of C-DAI among the M received second DCIs, or the total number of bits in the second sub-codebook is the maximum value of T-DAI among the M received second DCIs. Furthermore, the j-th bit in this second sub-codebook is used to feed back 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 containing a C-DAI value of j. Here, 1 ≤ j ≤ M, and j is a positive integer. If the terminal device does not receive the j-th second DCI, then the j-th bit is set to NACK or 0.

[0093] Please refer to Figure 6 , Figure 6 Is Figure 4 and Figure 5 The diagram shows how the terminal device generates the corresponding codebook in the case of DCI transmission. Figure 6 In the codebook shown, bits 1 to 6 form the second sub-codebook, and bits 7 to 9 form the first sub-codebook. Figure 6 Although the first and second subcodebooks are shown in an exemplary manner in a concatenated manner, the first and second subcodebooks can also be independent.

[0094] Since the terminal device receives a total of 6 second DCIs, namely uDCI1-6, where the second DCI with the largest C-DAI is uDCI6 and the maximum value of C-DAI is 6, and the second DCI with the largest T-DAI is also uDCI6 and the maximum value of T-DAI is 6, the terminal device can generate a 6-bit second sub-codebook. Bits 1 to 6 correspond to the HARQ-ADK feedback information of uPDSCH1 to uPDSCH6 scheduled by uDCI1 to uDCI6, respectively. Assuming the terminal device did not successfully receive uDCI5, it also did not receive uPDSCH5. Since the terminal device did not receive a second DCI containing a C-DAI value of 5 (i.e., did not receive the 5th second DCI), it sets bit 5 in the second sub-codebook to NACK or 0. Depending on whether uPDSCH1-4 and uPDSCH5 were successfully received, the terminal device sets bits 1-4 and bit 6 to ACK or NACK. For example, ACK has a value of 1, and NACK has a value of 0.

[0095] Similarly, since the terminal device receives a total of three first DCIs, namely gDCI1-3, where the largest first DCI for C-DAI is gDCI3 and the maximum value of C-DAI is 3, and the largest first DCI for T-DAI is also gDCI3, the maximum value of T-DAI is 3, the terminal device can generate a 3-bit second subcodebook, i.e. Figure 6 Bits 7 through 9 of the codebook shown are also bits 1 through 3 of the second sub-codebook. Bits 1 through 3 of the second sub-codebook (i.e....) Figure 6 Bits 7 through 9 of the codebook shown correspond to the HARQ-ADK feedback information of gPDSCH1 through gPDSCH3 scheduled by gDCI1 through gDCI3. The terminal device sets bits 1 through 3 of the second sub-codebook to either ACK or NACK depending on whether gPDSCH1-3 was successfully received. For example, ACK is set to 1, and NACK is set to 0.

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

[0097] Within this third time unit, the terminal device can send the codebook in a concatenated manner with the first and second sub-codebooks, or it can send the first and second sub-codebooks separately to achieve the transmission of the entire codebook. The method for selecting the resources required for sending the codebook can utilize existing resource selection methods for sending dynamic codebooks, or it can use resource selection methods different from existing technologies. This embodiment provides several exemplary methods for implementing codebook transmission.

[0098] Method 1

[0099] In Method 1, step 304 can be implemented in the following way.

[0100] 701: The terminal device determines a first PUCCH resource set from multiple physical uplink control channel (PUCCH) resource sets based on the load size of the codebook, wherein each PUCCH resource set includes at least one PUCCH resource.

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

[0102] Different PUCCH resource sets can have different identifiers. PUCCH resources belonging to different PUCCH resource sets can have different sizes. Larger PUCCH resources can carry more bits of HARQ-ACK feedback information, while smaller PUCCH resources can carry fewer bits. For example, four PUCCH resource sets may have PUCCH Resource Set IDs 1-4. The PUCCH resource set with the smaller ID number contains fewer bits of HARQ-ACK feedback information carried by its PUCCH resources than the PUCCH resource set with the larger ID number.

[0103] The payload size of the codebook can be the number of bits in the codebook or other variables corresponding to the number of bits in the codebook. The terminal device can determine the payload size based on the total number of bits in the codebook. UCI The first PUCCH set is selected from the multiple PUCCH resource sets. For example, assuming there are four PUCCH resource sets (i.e., pucch-ResourceSetId = 0, 1, 2, 3), if O UCI If the value is ≤2, then the first PUCCH resource set (i.e., pucch-ResourceSetId = 0) is selected; if the value is 2... <O UCI If N2 is less than or equal to 1, the UE selects the second PUCCH resource set (i.e., pucch-ResourceSetId = 1), where N2 is configured by higher-layer parameters. If no higher-layer parameters are configured, the value of N2 is 1706; if N2 is less than or equal to 1706, the UE selects the second PUCCH resource set (i.e., pucch-ResourceSetId = 1). <OUCI If N3 is less than or equal to 2, the UE selects the third PUCCH resource set (pucch-ResourceSetId = 2), where N3 is configured by higher-layer parameters. If no higher-layer parameters are configured, the value of N3 is 1706; if N3 is less than or equal to 2, the UE selects the third PUCCH resource set (pucch-ResourceSetId = 2), where N3 is configured by higher-layer parameters. <O UCI If the value is ≤1706, the UE selects the fourth PUCCH resource set (pucch-ResourceSetId=3), where N3 is configured by higher-layer parameters. If no higher-layer parameters are 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.

[0104] 702: The terminal device determines the first PUCCH resource from the first PUCCH resource set based on the PUCCH resource indicator (PRI) contained in the m-th DCI.

[0105] In one implementation, the m-th DCI is the last received DCI among all HARQ-ACK information bits in the codebook. That is, the m-th DCI is the last received DCI among the N first DCIs and M second DCIs. Here, within the same time slot, the DCI with the largest serving cell index is considered the last received DCI. For example, in... Figure 4 and Figure 5 In the example shown, uDCI6 is the m-th DCI because it is the last one received out of all M+N DCIs.

[0106] In another implementation, the m-th DCI is the second DCI corresponding to the HARQ-ACK information bit of the last second downlink data channel in the codebook, or the m-th 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, within the same time slot, the DCI with the largest serving cell index is considered the last received DCI. And according to the counting rules of the second C-DAI, the second C-DAI value of the last received second DCI must be the largest.

[0107] In another implementation, the m-th DCI is either the first DCI corresponding to the HARQ-ACK information bit of the last first downlink data channel in the codebook, or the m-th 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, within the same time slot, the DCI with the largest serving cell index is considered the last received DCI. And according to the counting rules of the first C-DAI, the first C-DAI value of the last received first DCI must be the largest.

[0108] In addition, each DCI also contains 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 8 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.

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

[0110] 711: Determine the first PUCCH resource set from the 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 the payload of the codebook to be received;

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

[0112] 713: Generate the m-th DCI, which contains a PUCCH PRI, and the PRI is used to determine the first PUCCH resource.

[0113] It is understandable that although the access network device has not yet received the codebook during the process of determining the first PUCCH resource set, it is clear about the load size of the codebook to be received because it knows the cumulative number of DCI transmissions.

[0114] Steps 711-713 can be performed after the access network device sends the (m-1)th DCI and before sending the m-th DCI, or they can be performed before sending the (m-1)th DCI. Those skilled in the art will understand that this can be determined by the scheduling strategy inside the access network device, and there is no limitation here.

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

[0116] Method 2

[0117] In method two, step 304 can be implemented in the following way.

[0118] 801: The terminal device determines a first PUCCH resource set from multiple physical uplink control channel (PUCCH) resource sets based on the load size of the first subcodebook, wherein each PUCCH resource set includes multiple PUCCH resources; and determines a second PUCCH resource set from the multiple physical uplink control channel (PUCCH) resource sets based on the load size of the second subcodebook.

[0119] The explanation and implementation of the load and PUCCH resource set can be found in Method 1; repeated parts will not be repeated here. It should be noted that there is no restriction on the execution order of the operations of determining the first PUCCH resource set and determining the second PUCCH resource set, and the first PUCCH resource set and the second PUCCH resource set can be the same or different.

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

[0121] In one implementation, the m1-th DCI is the first DCI corresponding to the HARQ-ACK information bit of the last first downlink data channel in the codebook, or the m-th DCI is the last received first DCI, or the m-th DCI is the first DCI with the largest cumulative number of DCIs indicating the first type among the received first C-DAIs. The m2-th DCI is the second DCI corresponding to the HARQ-ACK information bit of the last second downlink data channel in the codebook, or the m-th DCI is the last received second DCI, or the m-th DCI is the second DCI with the largest cumulative number of DCIs indicating the second type among the received second C-DAIs.

[0122] Corresponding to the terminal device, before sending the m1th first DCI, the access network device further includes:

[0123] 811: Determine a first PUCCH resource set from multiple physical uplink control channel (PUCCH) resource sets, each of the multiple PUCCH resource sets including multiple PUCCH resources, and the first PUCCH resource set corresponds to the payload of the first subcodebook to be received;

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

[0125] 813: Generate the m1th DCI, which contains the first PUCCH resource indication information PRI, and the PRI is used to determine the first PUCCH resource.

[0126] Before sending the m2th second DCI, the access network device further includes:

[0127] 814: Determine a second PUCCH resource set from the plurality of physical uplink control channel (PUCCH) resource sets, the second PUCCH resource set corresponding to the payload of the second subcodebook to be received;

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

[0129] 816: Generate the m2th DCI, which contains the second PUCCH resource indication information PRI, and the PRI is used to determine the second PUCCH resource.

[0130] It can be understood that although the access network device has not yet received the codebook during 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, it must be clear about the payload size of the first sub-codebook and the payload size of the second sub-codebook to be received.

[0131] Steps 811-813 can be executed after the access network device sends the (m1-1)th first DCI and before sending the (m1-1)th first DCI, or they can be executed before sending the (m1-1)th first DCI. Steps 814-816 can be executed after the access network device sends the (m2-1)th second DCI and before sending the (m2-1)th second DCI, or they can be executed before sending the (m2-1)th second DCI. Those skilled in the art will understand that this can be determined by the scheduling strategy within the access network device, and is not limited here. Furthermore, there is no restriction on the order of steps 811-813 and 814-816; the order can be determined by the order of the (m1)th first DCI and the (m2)th second DCI, or by the scheduling strategy within the access network device.

[0132] 803: Within the third time unit, the terminal device transmits the first sub-codebook using the determined first PUCCH resource and transmits the second sub-codebook using the determined second PUCCH resource. Correspondingly, within the third time unit, the access network device receives the first sub-codebook on the first PUCCH resource and receives the second sub-codebook on the second PUCCH resource.

[0133] In Method 2 above, a multicast DCI is sent to a group of UEs, and the group of UEs will determine the PUCCH resource using the same PUCCH PRI. If the PUCCH resource is determined according to the PRI in the last multicast DCI, multiple UEs will simultaneously send PUCCHs carrying HARQ, leading to excessive system load. However, the PRI in the unicast DCI received by different UEs may be different. Therefore, the PUCCH resource determined according to the PRI in the unicast DCI can be staggered in the time domain, reducing system load to some extent.

[0134] In one implementation, the terminal device implementing 803 may specifically include:

[0135] When the first PUCCH resource and the second PUCCH resource do not overlap in the time domain, within the third time unit, the first sub-codebook is sent using the determined first PUCCH resource, and the second sub-codebook is sent using the determined second PUCCH resource.

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

[0137] The third PUCCH resource set is determined from the plurality of physical uplink control channel (PUCCH) resource sets based on the load size of the codebook;

[0138] Based on the PUCCH resource indication information PRI contained in the m-th DCI, determine the third PUCCH resource from the third PUCCH resource set;

[0139] Within the third time unit, the codebook is transmitted using the determined third PUCCH resource.

[0140] The explanation and implementation of the m-th DCI and PRI are the same as in 702, and will not be repeated here.

[0141] Accordingly, when implementing 803, access network devices may specifically include:

[0142] When the first PUCCH resource and the second PUCCH resource do not overlap in the time domain, the first sub-codebook is received on the first PUCCH resource and the second sub-codebook is received on the second PUCCH resource within the third time unit.

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

[0144] The third PUCCH resource set is determined from the plurality of physical uplink control channel (PUCCH) resource sets based on the payload size of the codebook to be received;

[0145] Based on the PUCCH resource indication information PRI contained in the m-th DCI, determine the third PUCCH resource from the third PUCCH resource set;

[0146] Within the third time unit, the codebook is received on the determined third PUCCH resource.

[0147] The aforementioned third PUCCH resource set can be exactly the same as the first PUCCH resource set or the second PUCCH resource set, or it can be a different PUCCH resource set from the first PUCCH resource set or the second PUCCH resource set.

[0148] Method 3

[0149] In method three, step 304 can be implemented in the following way.

[0150] The plurality of 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 a plurality of PUCCH resources.

[0151] 901: The terminal device determines a first PUCCH resource set from the first PUCCH resource set group based on the load size of the first subcodebook; and determines a second PUCCH resource set from the second PUCCH resource set group based on the load size of the second subcodebook.

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

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

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

[0155] In another implementation, different from the above, the time-domain end symbol of each PUCCH resource in the first PUCCH resource set group is located before the time-domain end symbol of each PUCCH resource in the second PUCCH resource set group.

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

[0157] In another implementation different from the above, the time-domain end symbol of each PUCCH resource in the first PUCCH resource set group is placed before the first symbol, and the time-domain end symbol of each PUCCH resource in the second PUCCH resource set group is placed after the first symbol.

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

[0159] Corresponding to the terminal device, before sending the m1th first DCI, the access network device further includes:

[0160] A first PUCCH resource set is determined from the first PUCCH resource set group, and the first PUCCH resource set corresponds to the payload size of the first subcodebook to be received;

[0161] The first PUCCH resource is determined from the first PUCCH resource set;

[0162] Generate the m1th DCI, which contains the first PUCCH resource indication information PRI, and the PRI is used to determine the first PUCCH resource.

[0163] Before sending the m2th second DCI, the access network device further includes:

[0164] A second PUCCH resource set is determined from the second PUCCH resource set group, and the second PUCCH resource set corresponds to the payload size of the second subcodebook to be received;

[0165] Determine the second PUCCH resource from the second PUCCH resource set;

[0166] Generate the m2th DCI, which contains the second PUCCH resource indication information PRI, and the PRI is used to determine the second PUCCH resource.

[0167] 903: Within the third time unit, the terminal device transmits the first sub-codebook using the determined first PUCCH resource and transmits the second sub-codebook using the determined second PUCCH resource. Correspondingly, within the third time unit, the access network device receives the first sub-codebook on the first PUCCH resource and receives the second sub-codebook on the second PUCCH resource.

[0168] In the above-described 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, with different time-domain positions of the PUCCH resources in the first and second PUCCH resource set groups. This design allows the HARQ-ACK feedback latency to better meet the requirements of unicast or multicast services. For example, unicast services, especially those in Ultra-Reliable and Low-Latency Communications (URLLC) scenarios, have high latency requirements. Multicast services, such as those in Enhanced Mobile Broadband (eMBB) scenarios, have relatively lower latency requirements. Therefore, when, for example, the start symbol in the time domain of each PUCCH resource in the first PUCCH resource set group is located before the first symbol, and the start symbol in the time domain of each PUCCH resource in the second PUCCH resource set group is located after the first symbol, it is beneficial for unicast services with high latency requirements to have their HARQ-ACK feedback information sent more promptly.

[0169] In one implementation, the terminal device, when implementing 903, may specifically include:

[0170] When the first PUCCH resource and the second PUCCH resource do not overlap in the time domain, within the third time unit, the first sub-codebook is sent using the determined first PUCCH resource, and the second sub-codebook is sent using the determined second PUCCH resource.

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

[0172] The third PUCCH resource set is determined from the 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 based on the load size of the codebook.

[0173] Based on the PUCCH resource indication information PRI contained in the m-th DCI, determine the third PUCCH resource from the third PUCCH resource set;

[0174] Within the third time unit, the codebook is transmitted using the determined third PUCCH resource.

[0175] In one implementation, the access network device implementing 903 may specifically include:

[0176] When the first PUCCH resource and the second PUCCH resource do not overlap in the time domain, the first sub-codebook is received on the first PUCCH resource and the second sub-codebook is received on the second PUCCH resource within the third time unit.

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

[0178] The third PUCCH resource set is determined based on the payload size of the codebook to be received, 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.

[0179] Based on the PUCCH resource indication information PRI contained in the m-th DCI, determine the third PUCCH resource from the third PUCCH resource set;

[0180] Within the third time unit, the codebook is received on the determined third PUCCH resource.

[0181] The third PUCCH resource set can be exactly the same as the first PUCCH resource set or the second PUCCH resource set, or it can be a different PUCCH resource set from the first PUCCH resource set or the second PUCCH resource set.

[0182] The explanation and implementation of the m-th DCI and PRI are the same as in 702, and will not be repeated here.

[0183] The explanation and implementation of the first DCI received for the m1th time and the second DCI received for the m2th time are the same as in Method 2, and will not be repeated here.

[0184] By employing the embodiments 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 set correctly and reasonably for unicast and multicast services respectively. 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, ensuring the reliability of the HARQ-ACK feedback information corresponding to the multicast downlink data channel.

[0185] Figure 7 This is a schematic block diagram of a communication device 1100 provided in an embodiment of this application. Exemplarily, the communication device 1100 can be a terminal device, or a chip or other combination device or component having the aforementioned terminal device functions applied in the terminal device. The descriptions of the terminal device side in the foregoing embodiments are applicable to the communication device 1100 and will not be repeated hereafter. 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 can be a transceiver, which may include an antenna and radio frequency circuits, etc., and the processing module 1110 can 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 aforementioned terminal device functions, the transceiver module 1120 can be a radio frequency unit, and the processing module 1110 can be a processor, such as a baseband processor. When the communication device 1100 is a chip system, the transceiver module 1120 can be the input / output interface of a chip (e.g., a baseband chip), and the processing module 1110 can be the 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 this application can be implemented by a processor or processor-related circuit components, and the transceiver module 1120 can be implemented by a transceiver or transceiver-related circuit components.

[0186] For example, processing module 1110 can be used to execute Figure 3In the illustrated embodiment, the device performs all operations other than the transmit / receive operation, such as steps 303, 701, 702, 801, 802, 901, 902, and / or other processes supporting the technology described herein. The transceiver module 1120 can be used to perform... Figure 3 The embodiments shown include all transmit / receive operations performed by the terminal device, such as steps 301, 302, 304, 703, 803, 903 and / or other processes used to support the technology described herein.

[0187] Additionally, the transceiver module 1120 can be a functional module capable of performing both sending and receiving operations. For example, the transceiver module 1120 can be used to perform... Figure 3 In the illustrated embodiment, all sending and receiving operations are performed by the terminal device. For example, when performing a sending operation, the transceiver module 1120 can be considered as the sending module, and when performing a receiving operation, it can be considered as the receiving module. Alternatively, the transceiver module 1120 can also be two functional modules, which can be considered as a collective term for these two functional modules: the sending module and the receiving module. 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 receiving module performs all the sending operations by the first terminal device, and the receiving module is used to perform the receiving operations. For example, the receiving module can be used to perform... Figure 3 The illustrated embodiment represents all the receiving operations performed by the terminal device.

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

[0189] The transceiver module 1120 is configured to: receive N first downlink control information (DCI) and M second DCI; receive 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.

[0190] The processing module 1110 is configured to: generate 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. The codebook includes a first sub-codebook and a second sub-codebook. The first sub-codebook includes the HARQ-ACK feedback information of the N first downlink data channels, and the second sub-codebook includes the HARQ-ACK feedback information of the M second downlink data channels.

[0191] The transceiver module 1120 is also used to: send the codebook within a third time unit.

[0192] In one implementation,

[0193] The processing module 1110 is further configured to: determine a first PUCCH resource set from multiple physical uplink control channel (PUCCH) resource sets according to the load size of the codebook, wherein each PUCCH resource set in the multiple PUCCH resource sets includes at least one PUCCH resource; and determine the first PUCCH resource from the first PUCCH resource set according to the PUCCH resource indication information contained in the m-th DCI.

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

[0195] In another implementation,

[0196] The processing module 1110 is further configured to: determine a first PUCCH resource set from multiple physical uplink control channel (PUCCH) resource sets based on the load size of the first subcodebook, wherein each PUCCH resource set includes multiple PUCCH resources; determine a second PUCCH resource set from the multiple physical uplink control channel (PUCCH) resource sets based on the load size of the second subcodebook; determine a first PUCCH resource from the first PUCCH resource set based on the PUCCH PRI contained in the m1th received first DCI; and determine a second PUCCH resource from the second PUCCH resource set based on the PUCCH PRI contained in the m2th received second DCI.

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

[0198] Optionally, in this implementation,

[0199] The transceiver module 1120 is used to transmit the first sub-codebook using the determined first PUCCH resource and the second sub-codebook using the determined second PUCCH resource within the third time unit when the first PUCCH resource and the second PUCCH resource do not overlap in the time domain.

[0200] 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 plurality of 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 the PUCCH resource indication information PRI contained in the m-th DCI.

[0201] The transceiver module 1120 is also used to send the codebook using the determined third PUCCH resource within the third time unit.

[0202] In yet another implementation...

[0203] The processing module 1110 is further configured to: determine a first PUCCH resource set from the first PUCCH resource set group based on the load size of the first subcodebook; determine a second PUCCH resource set from the second PUCCH resource set group based on the load size of the second subcodebook; determine a first PUCCH resource from the first PUCCH resource set based on the PUCCH PRI contained in the m1th received first DCI; and determine a second PUCCH resource from the second PUCCH resource set based on the PUCCH PRI contained in the m2th received second DCI.

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

[0205] Optionally, in this implementation,

[0206] 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 sub-codebook using the determined first PUCCH resource and send the second sub-codebook using the determined second PUCCH resource within the third time unit;

[0207] 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 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 the load size of the codebook; and determine a third PUCCH resource from the third PUCCH resource set according to the PUCCH resource indication information PRI contained in the m-th DCI.

[0208] The transceiver module 1120 is also used to send the codebook using the determined third PUCCH resource within the third time unit.

[0209] Figure 8 This is a schematic block diagram of a communication device 2100 provided in an embodiment of this application. Exemplarily, the communication device 2100 may be the aforementioned access network device. The descriptions of the access network device side in the foregoing embodiments are 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 radio frequency circuits, etc. The processing module 2110 may be a processor, such as a baseband processor, which may include one or more central processing units (CPUs).

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

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

[0212] The transceiver module 2120 is also configured to transmit N first downlink data channels and M second downlink data channels within at least one second time unit, 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;

[0213] The transceiver module 2120 is also used to receive a codebook of HARQ-ACK feedback information within the third time unit;

[0214] The processing module 2110 is used 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 for the N first downlink data channels, and the second sub-codebook includes HARQ-ACK feedback information for the M second downlink data channels.

[0215] In one implementation,

[0216] The processing module 2110 is further configured to determine a first PUCCH resource set from multiple physical uplink control channel (PUCCH) resource sets, each of the multiple PUCCH resource sets including multiple PUCCH resources, the first PUCCH resource set corresponding to the payload of the codebook to be received; determine the first PUCCH resource from the first PUCCH resource set; generate the m-th DCI, the m-th DCI containing PUCCH resource indication information PRI, the PRI being used to determine the first PUCCH resource;

[0217] Specifically, the transceiver module 2120 is used to receive the codebook of HARQ-ACK feedback information on the first PUCCH resource within the third time unit.

[0218] In another implementation,

[0219] 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 PUCCH resource set including a plurality of PUCCH resources, the first PUCCH resource set corresponding to the payload of the first subcodebook to be received; determine the first PUCCH resource from the first PUCCH resource set; generate the m1th DCI, the m1th DCI containing 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 the payload of the second subcodebook to be received; determine the second PUCCH resource from the second PUCCH resource set; generate the m2th DCI, the m2th DCI containing second PUCCH resource indication information PRI, the PRI being used to determine the second PUCCH resource;

[0220] Specifically, the transceiver module 2120 is used to receive the first sub-codebook on the first PUCCH resource and the second sub-codebook on the second PUCCH resource within the third time unit.

[0221] In the above implementation method, optionally,

[0222] In the third time unit, the transceiver module 2120 receives the first sub-codebook on the first PUCCH resource and receives the second sub-codebook on the second PUCCH resource, specifically including:

[0223] The transceiver module 2120 is used to receive the first sub-codebook on the first PUCCH resource and the second sub-codebook 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.

[0224] 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 plurality of physical uplink control channel PUCCH resource sets according to the load size of the codebook to be received; and determine a third PUCCH resource from the third PUCCH resource set according to the PUCCH resource indication information PRI contained in the m-th DCI.

[0225] The transceiver module 2120 is also configured to receive the codebook within the determined third PUCCH resource during the third time unit.

[0226] In yet another implementation...

[0227] The plurality of 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 PUCCH resource set group includes a plurality of PUCCH resources;

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

[0229] The processing module 2110 is further configured to: determine a first PUCCH resource set from the first PUCCH resource set group, wherein the first PUCCH resource set corresponds to the payload size of the first subcodebook to be received; determine a first PUCCH resource from the first PUCCH resource set; generate the m1th DCI, wherein the m1th DCI contains first PUCCH resource indication information PRI, wherein the PRI is used to determine the first PUCCH resource; determine a second PUCCH resource set from the second PUCCH resource set group, wherein the second PUCCH resource set corresponds to the payload size of the second subcodebook to be received; and determine a second PUCCH resource from the second PUCCH resource set.

[0230] The processing module 2110 is further configured to generate the m2nd DCI, which contains the second PUCCH resource indication information PRI, and the PRI is used to determine the second PUCCH resource;

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

[0232] In one specific implementation, optionally,

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

[0234] The transceiver module 2120 is further configured to receive the first sub-codebook on the first PUCCH resource and the second sub-codebook 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.

[0235] 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 based on the load size of the codebook to be received, 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 a third PUCCH resource from the third PUCCH resource set based on the PUCCH resource indication information PRI contained in the m-th DCI.

[0236] The transceiver module 2120 is also configured to receive the codebook within the determined third PUCCH resource during the third time unit.

[0237] This application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a computer, the computer can implement the processes related to the terminal device in the embodiments provided above.

[0238] This application also provides a computer-readable storage medium for storing a computer program. When the computer program is executed by a computer, the computer can implement the processes related to the access network device in the embodiments provided above.

[0239] This application also provides a computer program product for storing a computer program. When the computer program is executed by a computer, the computer can implement the processes related to the terminal device in the embodiments provided in the above method embodiments.

[0240] This application also provides a computer program product for storing a computer program. When the computer program is executed by a computer, the computer can implement the processes related to the access network device in the embodiments provided above.

[0241] It should be understood that the processor mentioned in the embodiments of this application can be a CPU, or 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. A general-purpose processor can be a microprocessor or any conventional processor.

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

[0243] 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, or discrete hardware component, the memory (storage module) is integrated into the processor.

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

[0245] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply 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 this application.

[0246] Those skilled in the art will recognize that the units and algorithm steps of the various examples 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 implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art 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.

[0247] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0248] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0249] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0250] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0251] If the aforementioned functions are implemented as 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 this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned computer-readable storage medium can be any available medium that a computer can access. For example, but not limited to: 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, portable hard disk, or other optical disc storage, disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer.

[0252] The above description is merely a specific embodiment of this application, but the protection scope of the embodiments of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the embodiments of this application should be included within the protection scope of the embodiments of this application. Therefore, the protection scope of the embodiments of this application should be determined by the protection scope of the claims.

Claims

1. A method for transmitting automatic repeat request acknowledgement feedback information for multicast services, characterized in that, comprising: receiving N first downlink control information (DCI) and M second DCI, the first DCI being a first type of DCI, the second DCI being a second type of DCI, each of the first DCI comprising a first downlink assignment index (DAI), the first DAI comprising a first downlink assignment index counter (C-DAI), the first C-DAI indicating a cumulative number of the first type of DCI scheduling downlink data channel transmission; each of the second DCI comprising a second downlink assignment index (DAI), the second DAI comprising a second downlink assignment index counter (C-DAI), the second C-DAI indicating a cumulative number of the second type of DCI scheduling downlink data channel transmission; receiving N first downlink data channels and M second downlink data channels, the N first downlink data channels being scheduled by the N first downlink control information, the M second downlink data channels being scheduled by the M second downlink control information; generating a codebook of hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback information according to the first DAI in the N first DCI, the second DAI in the M second DCI, the N first downlink data channels and the M second downlink data channels, the codebook comprising a first sub-codebook and a second sub-codebook, the first sub-codebook comprising HARQ-ACK feedback information of the N first downlink data channels, the second sub-codebook comprising HARQ-ACK feedback information of the M second downlink data channels; and transmitting the codebook.

2. The method of claim 1, wherein: the first type of DCI is a DCI with cyclic redundancy check bits scrambled by a group radio network temporary identifier, and the second type of DCI is a DCI with cyclic redundancy check bits scrambled by a cell radio network temporary identifier, a modulation and coding scheme-cell radio network temporary identifier, or a configured scheduling radio network temporary identifier (CS-RNTI); or the first type of DCI is a DCI for multicast service, and the second type of DCI is a DCI for unicast service.

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

4. The method of any one of claims 1 to 3, wherein: the first C-DAI indicates a cumulative number of the first type of DCI scheduling physical downlink shared channel (PDSCH) transmission and / or indicating semi-persistent scheduling (SPS) PDSCH release until a current serving cell and physical downlink control channel (PDCCH) detection occasion; 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-persistent scheduling (SPS) PDSCH release until the current serving cell and physical downlink control channel (PDCCH) detection occasion.

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

6. The method of any one of claims 1 to 5, wherein, The first DAI further includes a first total downlink assignment index (T-DAI), which represents the cumulative number of DCIs for scheduling PDSCH transmission and the first type of DCIs for indicating SPS PDSCH release until the current PDCCH detection occasion; and / or The second DAI further includes a second total downlink assignment index (T-DAI), which represents the cumulative number of DCIs for scheduling PDSCH transmission and the second type of DCIs for indicating SPS PDSCH release until the current PDCCH detection occasion.

7. The method of any one of claims 1 to 6, wherein, The HARQ-ACK feedback information transmission occasion corresponding to the N first downlink data channels and the M second downlink data channels is the third time unit.

8. The method of any one of claims 1 to 7, wherein, The first sub-codebook is a continuous bit, and the second sub-codebook is a continuous bit.

9. The method of any one of claims 1 to 8, wherein, The codebook for generating automatic repeat request acknowledgement (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 includes: generating the first sub-codebook according to the reception of the N first downlink data channels and the first DAI in the N first DCIs; generating the second sub-codebook according to the reception of the M second downlink data channels and the second DAI in the M second DCIs.

10. The method of any one of claims 1 to 9, wherein, The first sub-codebook is concatenated with the second sub-codebook.

11. The method of claim 10, wherein, The first sub-codebook is before the second sub-codebook, or the first sub-codebook is after the second sub-codebook.

12. The method of claim 10 or 11, wherein, The sending of the codebook in the third time unit includes: determining a first PUCCH resource set from a plurality of PUCCH resource sets according to the 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) contained in the mth DCI; sending the codebook by using the determined first PUCCH resource in the third time unit.

13. A method of transmitting automatic repeat request acknowledgement feedback information for multicast services, the method comprising: including: transmitting N first downlink control information (DCI) and M second DCI, the first DCI being a first type of DCI, the second DCI being a second type of DCI, each of the first DCI comprising a first downlink assignment index (DAI), the first DAI comprising a first downlink assignment index counter (C-DAI), the first C-DAI indicating a cumulative number of the first type of DCI scheduling downlink data channel transmission; each of the second DCI comprising a second downlink assignment index (DAI), the second DAI comprising a second downlink assignment index counter (C-DAI), the second C-DAI indicating a cumulative number of the second type of DCI scheduling downlink data channel transmission; transmitting N first downlink data channels and M second downlink data channels, the N first downlink data channels being scheduled by the N first downlink control information, the M second downlink data channels being scheduled by the M second downlink control information; receiving a codebook of hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback information, the codebook comprising a first sub-codebook and a second sub-codebook, the first sub-codebook comprising HARQ-ACK feedback information of the N first downlink data channels, the second sub-codebook comprising HARQ-ACK feedback information of the M second downlink data channels.

14. The method of claim 13, wherein: the first type of DCI is DCI with cyclic redundancy check bits scrambled by a group radio network temporary identifier, and the second type of DCI is DCI with cyclic redundancy check bits scrambled by a cell radio network temporary identifier, a modulation and coding scheme-cell radio network temporary identifier, or a configured scheduling radio network temporary identifier (CS-RNTI); or the first type of DCI is DCI for multicast service, and the second type of DCI is DCI for unicast service.

15. The method of claim 13 or 14, wherein: the first type of DCI is transmitted in a first search space, and the second type of DCI is transmitted in a second search space different from the first search space; or the first type of DCI is transmitted in a common search space, and the second type of DCI is transmitted in a UE-specific search space; or the first type of DCI is transmitted in a first set of control channel resources, and the second type of DCI is transmitted in a second set of control channel resources.

16. The method of any one of claims 13 to 15, wherein: the first C-DAI indicates a cumulative number of the first type of DCI scheduling physical downlink shared channel (PDSCH) transmission and / or indicating semi-persistent scheduling (SPS) PDSCH release until a current serving cell and physical downlink control channel (PDCCH) detection occasion; 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-persistent scheduling (SPS) PDSCH release until the current serving cell and physical downlink control channel (PDCCH) detection occasion.

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

18. The method of any one of claims 13 to 17, wherein, The first DAI further includes a first total downlink assignment index (T-DAI), which represents the cumulative number of DCIs for scheduling physical downlink shared channel (PDSCH) transmission and the first type of DCIs for indicating semi-persistent scheduling (SPS) PDSCH release until the current physical downlink control channel (PDCCH) detection occasion; and / or The second DAI further includes a second total downlink assignment index (T-DAI), which represents the cumulative number of DCIs for scheduling physical downlink shared channel (PDSCH) transmission and the second type of DCIs for indicating semi-persistent scheduling (SPS) PDSCH release until the current physical downlink control channel (PDCCH) detection occasion.

19. The method of any one of claims 13 to 18, wherein, The HARQ-ACK feedback information transmission occasion corresponding to the N first downlink data channels and the M second downlink data channels is the third time unit.

20. The method of any one of claims 13 to 19, wherein, The first sub-codebook is a continuous bit, and the second sub-codebook is a continuous bit.

21. The method of any one of claims 13 to 20, wherein, The first sub-codebook is concatenated with the second sub-codebook.

22. The method of claim 21, wherein, The first sub-codebook is before the second sub-codebook, or the first sub-codebook is after the second sub-codebook.

23. The method of claim 21 or 22, wherein, Further comprising: determining a first physical uplink control channel (PUCCH) resource set from a plurality of PUCCH resource sets, each PUCCH resource set in the plurality of PUCCH resource sets including a plurality of PUCCH resources, the first PUCCH resource set corresponding to the load of the codebook to be received; determining a first PUCCH resource from the first PUCCH resource set; generating an mth DCI, the mth DCI including PUCCH resource indication information (PRI), the PRI being used to determine the first PUCCH resource; The codebook for receiving the automatic repeat request-acknowledgement (HARQ-ACK) feedback information in the third time unit includes: receiving the codebook for automatic repeat request-acknowledgement (HARQ-ACK) feedback information on the first PUCCH resource in the third time unit.

24. A communications device, characterized by comprising a transceiver module and a processing module, wherein The transceiver module is configured to receive N first downlink control information (DCI) and M second DCI, the first DCI is a first type of DCI, the second DCI is a second type of DCI, each of the first DCI includes a first downlink assignment index (DAI), the first DAI includes a first downlink assignment index counter (C-DAI), the first C-DAI indicates a cumulative number of the first type of DCI scheduling downlink data channel transmission; each of the second DCI includes a second downlink assignment index (DAI), the second DAI includes a second downlink assignment index counter (C-DAI), the second C-DAI indicates a cumulative number of the second type of DCI scheduling downlink data channel transmission; The transceiver module is further configured to 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, the M second downlink data channels are scheduled by the M second downlink control information; The processing module is configured to generate a codebook of hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback information according to the first DAI in the N first DCI, the second DAI in the M second DCI, the N first downlink data channels and the M second downlink data channels, 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, the second sub-codebook includes HARQ-ACK feedback information of the M second downlink data channels; and The transceiver module is further configured to send the codebook.

25. The communication apparatus of claim 24, wherein, the first type of DCI is DCI with cyclic redundancy check bits scrambled by a group radio network temporary identifier, and the second type of DCI is DCI with cyclic redundancy check bits scrambled by a cell radio network temporary identifier, a modulation and coding scheme-cell radio network temporary identifier, or a configured scheduling radio network temporary identifier (CS-RNTI); or the first type of DCI is DCI for multicast service, and the second type of DCI is DCI for unicast service.

26. The communication apparatus of claim 24 or 25, 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 in a first set of control channel resources, and the second type of DCI is sent in a second set of control channel resources.

27. The communication apparatus of any of claims 24 to 26, wherein, ​ the first C-DAI indicates a cumulative number of DCIs for scheduling physical downlink shared channel (PDSCH) transmission and / or a first type of DCI for indicating semi-persistent scheduling (SPS) PDSCH release until a current serving cell and physical downlink control channel (PDCCH) detection occasion; and / or the second C-DAI indicates a cumulative number of DCIs for scheduling PDSCH transmission and / or a second type of DCI for indicating SPS PDSCH release until the current serving cell and PDCCH detection occasion.

28. The communications apparatus of claim 27, wherein a counting rule of the first C-DAI is to count first in ascending order of serving cell index and then in ascending order of PDCCH detection occasion; and / or a counting rule of the second C-DAI is to count first in ascending order of serving cell index and then in ascending order of PDCCH detection occasion.

29. The communication apparatus of any of claims 24 to 28, wherein, the first DAI further comprises a first total downlink assignment index (T-DAI) indicating a cumulative number of DCIs for scheduling PDSCH transmission and the first type of DCI until a current PDCCH detection occasion; and / or the second DAI further comprises a second T-DAI indicating a cumulative number of DCIs for scheduling PDSCH transmission and the second type of DCI until the current PDCCH detection occasion.

30. The communication apparatus of any of claims 24 to 29, wherein, the HARQ-ACK feedback information transmission occasion corresponding to the N first downlink data channels and the M second downlink data channels is the third time unit.

31. The communication apparatus of any of claims 24 to 30, wherein, the first sub-codebook is continuous bits and the second sub-codebook is continuous bits.

32. The communication apparatus of any of claims 24 to 31, wherein, generating the codebook of automatic repeat request acknowledgement (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 comprises: generating the first sub-codebook according to a reception condition of the N first downlink data channels and the first DAI in the N first DCIs; and generating the second sub-codebook according to a reception condition of the M second downlink data channels and the second DAI in the M second DCIs.

33. The communication apparatus of any of claims 24 to 32, wherein, the first sub-codebook is concatenated with the second sub-codebook.

34. The communications apparatus of claim 33, wherein the first sub-codebook is before the second sub-codebook, or the first sub-codebook is after the second sub-codebook.

35. The communication apparatus of claim 33 or 34, wherein The processing module is further configured to determine a first PUCCH resource set from a plurality of PUCCH resource sets according to a load size of the codebook, each PUCCH resource set in the plurality of PUCCH resource sets comprising at least one PUCCH resource; and determine a first PUCCH resource from the first PUCCH resource set according to PUCCH resource indication information (PRI) contained in the mth DCI. The transceiver is configured to transmit the codebook in the third time unit. The transceiver is configured to transmit the codebook in the third time unit using the determined first PUCCH resource.

36. A communications device, characterized by The communication device comprises a processing module and a transceiver, wherein The transceiver is configured to transmit N first DCIs and M second DCIs, the first DCIs being DCIs of a first type, and the second DCIs being DCIs of a second type, each first DCI comprising a first downlink assignment index (DAI), the first DAI comprising a first downlink assignment index counter (C-DAI) indicating a cumulative number of the DCIs of the first type scheduling downlink data channel transmissions; and each second DCI comprising a second downlink assignment index (DAI), the second DAI comprising a second downlink assignment index counter (C-DAI) indicating a cumulative number of the DCIs of the second type scheduling downlink data channel transmissions. The transceiver is further configured to transmit N first downlink data channels and M second downlink data channels, the N first downlink data channels being scheduled by the N first DCIs, and the M second downlink data channels being scheduled by the M second DCIs. The transceiver is further configured to receive a codebook of HARQ-ACK feedback information. The processing module is configured to determine the HARQ-ACK feedback information from the codebook, wherein the codebook comprises a first sub-codebook and a second sub-codebook, the first sub-codebook comprising HARQ-ACK feedback information of the N first downlink data channels, and the second sub-codebook comprising HARQ-ACK feedback information of the M second downlink data channels.

37. The communication device of claim 36, wherein the DCIs of the first type are DCIs with cyclic redundancy check bits scrambled by a group radio network temporary identifier, and the DCIs of the second type are DCIs with cyclic redundancy check bits scrambled by a cell radio network temporary identifier, a modulation and coding scheme-cell radio network temporary identifier, or a configured scheduling radio network temporary identifier (CS-RNTI); or the DCIs of the first type are DCIs for multicast services, and the DCIs of the second type are DCIs for unicast services.

38. The communication device of claim 36 or 37, wherein the DCIs of the first type are transmitted in a first search space, and the DCIs of the second type are transmitted in a second search space different from the first search space; or ​ the first type of DCI is transmitted in a common search space and the second type of DCI is transmitted in a UE-specific search space; or the first type of DCI is transmitted in a first set of control channel resources and the second type of DCI is transmitted in a second set of control channel resources.

39. The communication apparatus of any of claims 36 to 38, wherein the first C-DAI indicates a cumulative number of DCIs for scheduling physical downlink shared channel (PDSCH) transmissions and / or a first type of DCIs for indicating semi-persistent scheduling (SPS) PDSCH release until a current serving cell and physical downlink control channel (PDCCH) detection occasion; and / or the second C-DAI indicates a cumulative number of DCIs for scheduling PDSCH transmissions and / or a second type of DCIs for indicating SPS PDSCH release until the current serving cell and PDCCH detection occasion.

40. The communications apparatus of claim 39, wherein a counting rule of the first C-DAI is to count first in ascending order of serving cell index and then in ascending order of PDCCH detection occasion; and / or a counting rule of the second C-DAI is to count first in ascending order of serving cell index and then in ascending order of PDCCH detection occasion.

41. The communication apparatus of any of claims 36 to 40, wherein, the first DAI further comprises a first total downlink assignment index (T-DAI) indicating a cumulative number of DCIs for scheduling PDSCH transmissions and the first type of DCIs for indicating SPS PDSCH release until a current PDCCH detection occasion; and / or the second DAI further comprises a second T-DAI indicating a cumulative number of DCIs for scheduling PDSCH transmissions and the second type of DCIs for indicating SPS PDSCH release until the current PDCCH detection occasion.

42. The communication apparatus of any of claims 36-41, wherein, the HARQ-ACK feedback information transmission occasion corresponding to the N first downlink data channels and the M second downlink data channels is the third time unit.

43. The communication apparatus of any of claims 36-42, wherein, the first sub-codebook is continuous bits and the second sub-codebook is continuous bits.

44. The communication apparatus of any of claims 36 to 43, wherein, the first sub-codebook is concatenated with the second sub-codebook.

45. The communications apparatus of claim 44, wherein the first sub-codebook is before the second sub-codebook or the first sub-codebook is after the second sub-codebook.

46. The communication apparatus of claims 44 or 45, wherein, wherein the processing module is further configured to determine a first set of PUCCH resources from a plurality of sets of PUCCH resources, each set of PUCCH resources in the plurality of sets of PUCCH resources comprising a plurality of PUCCH resources, the first set of PUCCH resources corresponding to a load of the codebook to be received; and determine a first PUCCH resource from the first set of PUCCH resources. Generate the m-th DCI, which contains PUCCH resource indication information PRI, and the PRI is used to determine the first PUCCH resource; The transceiver module's codebook for receiving HARQ-ACK feedback information within the third time unit includes: The transceiver module is used to receive a codebook of HARQ-ACK feedback information on the first PUCCH resource within the third time unit.

Images