Multicast service feedback method and communication device

Abstract

A multicast service feedback method and a communication device are provided. The method includes: when a terminal device receives first configuration information from a network device and determines that a resource set overlaps with a unicast uplink resource, the terminal device transmits HARQ-ACK information for the multicast service to the network device in a first reporting mode. The HARQ-ACK information includes an ACK value or a NACK value. The first reporting mode indicates feeding back HARQ-ACK information based on ACK / NACK. The first configuration information indicates a second reporting mode, and the second reporting mode indicates feeding back HARQ-ACK information based on NACK-only. The resource set includes a plurality of multicast PUCCH resources. According to the method provided in this application, when there are a plurality of multicast PUCCH resources that can be used by the terminal device to transmit HARQ-ACK information for the multicast service, before obtaining a decoding result of the multicast PDSCH TB, the terminal device can determine whether a PUCCH resource used to feed back HARQ-ACK information overlaps with a unicast uplink resource to determine whether the second reporting mode should be switched to the first reporting mode.

Description

[Technical Field]

[0001] This application claims priority to Chinese Patent Application No. 202210432263.4, entitled "Multicast Service Feedback Method and Communication Apparatus," filed with the State Intellectual Property Administration of China on April 22, 2022, which is incorporated herein by reference in its entirety.

[0002] This application relates to the field of multicast service transmission technology, and in particular to a multicast service feedback method and communication device. [Background technology]

[0003] In the new radio (NR) technology, hybrid automatic repeat request (HARQ) for multicast services is supported to ensure the reliability of multicast services as much as possible. HARQ feedback for multicast services has a HARQ-ACK information reporting mode based on acknowledgment (ACK) / negative acknowledgment (NACK) and a HARQ-ACK information reporting mode based on NACK only. When there are multiple resources used to feed back HARQ-ACK information, how a terminal device feeds back HARQ-ACK information is a problem to be solved. Summary of the Invention

[0004] This application provides a multicast service feedback method and a communication device, which provides a solution for a terminal device to feedback HARQ-ACK information when there are multiple resources used to feedback HARQ-ACK information.

[0005] According to a first aspect, an embodiment of the present application provides a multicast service feedback method. The method can be performed by a first communication device. The first communication device may be a communication device or a communication apparatus capable of supporting functions required by the communication device to perform the method, such as a chip system. Hereinafter, an example in which the communication device is a terminal device is used for explanation. For example, the first communication device may be a terminal device, a chip disposed in the terminal device, or another component configured to implement functions of the terminal device. The method includes, when the terminal device receives first configuration information from a network device and determines that a resource set overlaps with unicast uplink resources, transmitting HARQ-ACK information for the multicast service to the network device in a first reporting mode. The first reporting mode indicates feedback of HARQ-ACK information based on ACK / NACK. The first configuration information indicates a second reporting mode, which indicates feedback of HARQ-ACK information based on NACK-only. The unicast uplink resources include PUCCH resources and / or unicast physical uplink shared channel (PUSCH) resources. The resource set includes multiple multicast PUCCH resources. The HARQ-ACK information includes an ACK value or a NACK value, and the HARQ-ACK information corresponding to the first reporting mode may include an ACK value or a NACK value. The HARQ-ACK information corresponding to the second reporting mode may include a NACK value but not an ACK value.

[0006] In this embodiment of the application, when a network device configures a second reporting mode for a terminal device, and there are multiple multicast PUCCH resources that can be used by the terminal device to transmit HARQ-ACK information for a multicast service, the terminal device can determine whether the multiple multicast PUCCH resources overlap with unicast uplink resources, and switch the second reporting mode to the first reporting mode when it determines that the multiple multicast PUCCH resources overlap with unicast uplink resources. According to the solution provided in this embodiment of the application, when it determines that the multiple PUCCH resources used to feed back HARQ-ACK information overlap with unicast uplink resources, the HARQ-ACK information is fed back in the first reporting mode.

[0007] In one possible implementation, the resource set and the unicast PUCCH resource belong to the same PUCCH resource set. Specifically, in this embodiment of the application, the PUCCH resource configured by the network device for the unicast service can be reused as the resource used to feed back HARQ-ACK information for the multicast service. For example, when the network device does not separately configure the PUCCH resource for the multicast service, the terminal device can reuse the PUCCH resource configured by the network device for the unicast service to transmit the HARQ-ACK information for the multicast service.

[0008] In one possible implementation, the method further includes the terminal device receiving second configuration information sent by the network device, the second configuration information indicating a multicast PUCCH resource set, and the resource set belonging to the multicast PUCCH resource set. Specifically, in this embodiment of the present application, the resource used to feed back HARQ-ACK information for the multicast service can be from the PUCCH resource specially configured by the network device for the multicast service. Therefore, the multicast PUCCH resource set can be flexibly obtained.

[0009] In one possible implementation, the resource set is m - 1 PUCCH resource, where m is the number of TBs used by the terminal device to feed back HARQ-ACK information, and m is an integer greater than or equal to 2.

[0010] In one possible implementation, the overlap of a resource set with unicast uplink resources includes the overlap of a resource set with unicast uplink resources having the same priority as the priority of the resource set. The same priority here means that the priority of the resource set is the same as the priority of the unicast uplink resources. In other words, "the resource set overlaps with unicast uplink resources having the same priority as the priority of the resource set" means "the resource set overlaps with unicast uplink resources having the same priority as the resource set."

[0011] In one possible implementation, the terminal device determining that a resource set overlaps with a unicast uplink resource includes the terminal device determining a candidate multicast PUCCH resource from the resource set, and determining that the resource set overlaps with the unicast uplink resource when the candidate multicast PUCCH resource satisfies a first condition. The first condition includes that the time domain resource corresponding to the candidate multicast PUCCH resource includes a set of time domain symbols respectively occupied by resources in the resource set. Specifically, the set of time domain symbols respectively occupied by resources in the resource set is explicitly specified as the candidate multicast PUCCH resource used for feeding back HARQ-ACK information for the multicast service.

[0012] In one possible implementation, the time domain resource corresponding to the candidate multicast PUCCH resource includes a set of time domain symbols each occupied by a resource in a resource set, including multiple implementations, for example the first, second, third, or fourth implementation below.

[0013] In a first implementation, the time domain resources corresponding to the candidate multicast PUCCH resources are sets of time domain symbols respectively occupied by resources in a resource set.

[0014] In a second implementation, the time domain resources corresponding to the candidate multicast PUCCH resources are a set of a first start symbol and a first end symbol occupied by the resource set, and symbols between the first start symbol and the first end symbol occupied by the resource set, where the first start symbol is the symbol with the earliest start time among the time domain symbols occupied by the resources in the resource set, and the first end symbol is the symbol with the latest end time among the time domain symbols occupied by the resources in the resource set.

[0015] In a third implementation, the time domain resource corresponding to a candidate multicast PUCCH resource is the set of all symbols contained in the slot in which the resource set lies.

[0016] In a fourth implementation, the time domain resource corresponding to the candidate multicast PUCCH resource is a set of a first symbol, a second symbol, and a symbol between the first symbol and the second symbol. The first symbol is the start symbol of the resource set, and the second symbol is the end symbol of the resource set. Furthermore, the start symbol of all PUCCH resources in the resource set is the same, and the end symbol of all PUCCH resources in the resource set is the same.

[0017] The symbols included in the time domain resource corresponding to the candidate multicast PUCCH resource are specified in the above four solutions. Therefore, before obtaining the decoding result of the multicast PUSCH TB, the terminal device may determine whether to switch the second reporting mode to the first reporting mode based on whether the candidate multicast PUCCH resource overlaps with the unicast uplink resource.

[0018] In one possible implementation, the method further includes the terminal device receiving indication information from the network device, where the indication information indicates how the terminal device determines that the resource set overlaps with the unicast uplink resources. In this solution, the network device can instruct the terminal device to determine how the resource set overlaps with the unicast uplink resources, and can, for example, indicate one of four implementation forms of the time domain resources corresponding to the candidate multicast PUCCH resources. This is more flexible.

[0019] According to a second aspect, an embodiment of the present application provides a multicast service feedback method. The method can be performed by a second communication device. The second communication device may be a communication device or a communication apparatus capable of supporting functions required by the communication device to perform the method, such as a chip system. Hereinafter, an example in which the communication device is a network device is used for explanation. For example, the second communication device may be a network device, a chip disposed in the network device, or another component configured to implement the functions of the network device. The method includes the network device transmitting first configuration information to a terminal device and, when determining that a resource set overlaps with unicast uplink resources, receiving HARQ-ACK information transmitted by the terminal device for the multicast service in a first reporting mode. The first reporting mode indicates feedback of HARQ-ACK information based on ACK / NACK. The first configuration information indicates a second reporting mode, which indicates feedback of HARQ-ACK information based on NACK-only. The unicast uplink resources include unicast PUCCH resources and / or unicast PUSCH resources. The resource set includes multiple multicast PUCCH resources. The HARQ-ACK information includes an ACK value or a NACK value, and the HARQ-ACK information corresponding to the first reporting mode may include an ACK value or a NACK value. The HARQ-ACK information corresponding to the second reporting mode may include a NACK value or no ACK value.

[0020] In one possible implementation, the resource set is m - 1 PUCCH resource, where m is the number of TBs used by the terminal device to feed back HARQ-ACK information, and m is an integer greater than or equal to 2.

[0021] In one possible implementation, the network device determining that the resource set overlaps with the unicast uplink resources includes the network device determining candidate multicast PUCCH resources from the resource set, and the network device determining that the resource set overlaps with the unicast uplink resources when the candidate multicast PUCCH resources satisfy a first condition, wherein the first condition includes that the time domain resources corresponding to the candidate multicast PUCCH resources include a set of time domain symbols respectively occupied by resources in the resource set.

[0022] In one possible implementation, the time domain resource corresponding to the candidate multicast PUCCH resource includes a set of time domain symbols each occupied by a resource in the resource set, including the first, second, third, or fourth case.

[0023] In the first case, the time domain resources corresponding to the candidate multicast PUCCH resources are sets of time domain symbols respectively occupied by resources in a resource set.

[0024] In the second case, the time domain resource corresponding to the candidate multicast PUCCH resource is a set of a first starting symbol occupied by the resource set, a first ending symbol occupied by the resource set, and symbols between the first starting symbol and the first ending symbol.

[0025] In the third case, the time domain resource corresponding to the candidate multicast PUCCH resource is the set of all symbols contained in the slot in which the resource set lies.

[0026] In a fourth case, the time domain resource corresponding to the candidate multicast PUCCH resource is a set of a first symbol, a second symbol, and a symbol between the first symbol and the second symbol. The first symbol is a start symbol of the resource set, and the second symbol is an end symbol of the resource set. The network device configures or indicates that the start symbol of all PUCCH resources in the resource set is the same, and the network device configures or indicates that the end symbol of all PUCCH resources in the resource set is the same.

[0027] In one possible implementation, the first starting symbol is the symbol with the earliest starting time among the time domain symbols occupied by the resources in the resource set, and the first ending symbol is the symbol with the latest ending time among the time domain symbols occupied by the resources in the resource set.

[0028] In one possible implementation, the resource set overlapping with the unicast uplink resources includes the resource set overlapping with the unicast uplink resources having the same priority as the priority of the resource set.

[0029] In one possible implementation, the method further includes the terminal device receiving indication information from the network device, the indication information indicating how the terminal device determines that the resource set overlaps with the unicast uplink resource.

[0030] In one possible implementation, the method further includes the terminal device receiving second configuration information from the network device, the second configuration information indicating a multicast PUCCH resource set, and the resource set belonging to the multicast PUCCH resource set.

[0031] In one possible implementation, the resource set and the unicast PUCCH resource belong to the same PUCCH resource set.

[0032] For the technical effects provided by the second aspect and possible implementations of the second aspect, please refer to the description of the technical effects of the first aspect and possible implementations of the first aspect.

[0033] According to a third aspect, an embodiment of this application provides a communication device, which has a function of performing the behaviors in the method embodiment of the first aspect. For beneficial effects, please refer to the description of the first aspect. Details will not be described again here. The communication device can be a terminal device in the first aspect, or the communication device can be a device, such as a chip or a chip system, capable of performing the method provided in the first aspect.

[0034] In one possible design, the communication device has corresponding means or modules configured to perform the method of the first aspect. For example, the communication device includes a processing unit (also referred to as a processing module or a processor) and / or a transceiver unit (also referred to as a transceiver module or a transceiver). Such units (modules) may perform corresponding functions of the example method of the first aspect.

[0035] For example, the transceiver module may be configured to receive first configuration information from a network device, the first configuration information indicating a second reporting mode, the second reporting mode indicating feeding back HARQ-ACK information based on NACK-only. When the processing module determines that the resource set overlaps with unicast uplink resources, the transceiver module may be further configured to transmit HARQ-ACK information for the multicast service to the network device in the first reporting mode. The first reporting mode indicates feeding back multicast HARQ-ACK information based on ACK / NACK. The second reporting mode indicates feeding back HARQ-ACK information based on NACK-only. The HARQ-ACK information may include an ACK value or a NACK value, and the HARQ-ACK information corresponding to the first reporting mode may include an ACK value or a NACK value. The HARQ-ACK information corresponding to the second reporting mode may include a NACK value but not an ACK value. The resource set includes a plurality of multicast PUCCH resources. The unicast uplink resources include unicast PUCCH resources and / or unicast PUSCH resources. For details, please refer to the detailed description in the method example, and the details will not be described again here.

[0036] According to a fourth aspect, an embodiment of this application provides a communication device, which has a function of performing the behaviors in the method embodiments of the second aspect. For beneficial effects, please refer to the description of the second aspect. Details will not be described again here. The communication device can be a network device in the second aspect, or the communication device can be a device, such as a chip or a chip system, capable of performing the method provided in the second aspect.

[0037] In one possible design, the communication device has corresponding means or modules configured to perform the method of the second aspect. For example, the communication device includes a processing unit (also referred to as a processing module or a processor) and / or a transceiver unit (also referred to as a transceiver module or a transceiver). Such units (modules) may perform corresponding functions of the example methods of the second aspect.

[0038] For example, the transceiver module may be configured to transmit first configuration information to the terminal device, the first configuration information indicating a second reporting mode, the second reporting mode indicating feeding back HARQ-ACK information based on NACK-only. When the processing module determines that the resource set overlaps with unicast uplink resources, the transceiver module may be further configured to receive HARQ-ACK information transmitted by the terminal device for the multicast service in the first reporting mode. The first reporting mode indicates feeding back HARQ-ACK information based on ACK / NACK. The second reporting mode indicates feeding back HARQ-ACK information based on NACK-only. The HARQ-ACK information may include an ACK value or a NACK value, and the HARQ-ACK information corresponding to the first reporting mode may include either an ACK value or a NACK value. The HARQ-ACK information corresponding to the second reporting mode may include a NACK value but not an ACK value. The resource set includes a plurality of multicast PUCCH resources. The unicast uplink resource includes a unicast PUCCH resource and / or a unicast PUSCH resource. For details, please refer to the detailed description in the method example. The details will not be described again here.

[0039] According to a fifth aspect, an embodiment of the present application provides a communication device. The communication device may be the communication device according to either the third or fourth aspect of the above-mentioned embodiments, or a chip or chip system arranged in the communication device according to either the third or fourth aspect. The communication device includes a communication interface and a processor, and optionally further includes a memory. The memory is configured to store a computer program. The processor is coupled to the memory and the communication interface. When the processor loads the computer program or instructions, the communication device is enabled to perform the method performed by the terminal device or network device in the above-mentioned method embodiments.

[0040] The communication interface of the communication device in the fifth aspect may be, for example, a transceiver of the communication device implemented by using an antenna, a feeder, a codec, etc. of the communication device. Alternatively, if the communication device is a chip disposed within the communication device, the communication interface may be an input / output interface of the chip, for example, an input / output pin.

[0041] According to a sixth aspect, an embodiment of the present application provides a communications device, the communications device comprising an input / output interface and a logic circuit, the input / output interface configured to input and / or output information, and the logic circuit configured to perform a method according to either the first or second aspect.

[0042] According to a seventh aspect, an embodiment of the present application provides a chip system. The chip system includes a processor, and may further include a memory and / or a communication interface, and is configured to perform a method according to either the first or second aspect. In one possible implementation, the chip system further includes a memory configured to store a computer program. The chip system may include a chip, or may include a chip and another discrete component.

[0043] According to an eighth aspect, an embodiment of the present application provides a communication system. The communication system includes a terminal device and a network device. The terminal device is configured to perform the method performed by the terminal device in the first aspect, and the network device is configured to perform the method performed by the network device in the second aspect. Alternatively, the communication system may further include more terminal devices and / or more network devices.

[0044] According to a ninth aspect, the present application provides a computer-readable storage medium, the computer-readable storage medium storing a computer program, which, when executed, performs the method of the first or second aspect.

[0045] According to a tenth aspect, there is provided a computer program product, the computer program product comprising computer program code which, when executed, performs the method of the first or second aspect.

[0046] For the beneficial effects of the third to tenth aspects and their implementations, please refer to the description of the method according to the first or second aspect and the beneficial effects of their implementations. [Brief explanation of the drawings]

[0047] [Figure 1] 1 is a diagram of the architecture of a communication system to which an embodiment of this application is applicable; [Figure 2] FIG. 1 is a diagram of feeding back HARQ-ACK information for multicast services according to one embodiment of the present application. [Figure 3] FIG. 1 is a diagram of feeding back HARQ-ACK information (with two TBs) for multicast services according to one embodiment of the present application. [Figure 4]1 is a schematic flowchart of a multicast service feedback method according to an embodiment of the present application; [Figure 5] 2 is a first diagram of candidate multicast PUCCH resources according to an embodiment of the present application; [Figure 6] FIG. 10 is a second diagram of candidate multicast PUCCH resources according to an embodiment of the present application. [Figure 7] FIG. 10 is a third diagram of candidate multicast PUCCH resources according to an embodiment of the present application; [Figure 8] FIG. 4 is a fourth diagram of candidate multicast PUCCH resources according to an embodiment of the present application. [Figure 9] FIG. 5 is a fifth diagram of candidate multicast PUCCH resources according to an embodiment of the present application. [Figure 10] FIG. 6 is a sixth diagram of candidate multicast PUCCH resources according to an embodiment of the present application. [Figure 11] FIG. 7 is a seventh diagram of candidate multicast PUCCH resources according to an embodiment of the present application. [Figure 12] 1 is a diagram of a configuration of a communication device according to one embodiment of the present application; [Figure 13] FIG. 2 is a diagram of another configuration of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0048] The technical solutions provided in the embodiments of this application may be applied to a fifth-generation (5G) mobile communication system, such as an NR system, a long-term evolution (LTE) system, a next-generation mobile communication system, or other similar communication systems. The technical solutions provided in the embodiments of this application may also be applied to a wireless fidelity (Wi-Fi)-based IoT or wearable Wi-Fi network, such as an Internet of Things (IoT) system or a narrowband Internet of Things (NB-IoT) system. A wearable Wi-Fi network may be a Wi-Fi network formed by using a terminal device (e.g., a mobile phone) as a virtual access point and an associated wearable device. Internet of Things devices and wearable Wi-Fi network devices are powered by small-capacity batteries and require ultra-low power consumption and long battery life. Internet of Things devices include, for example, smart water meters, smart homes, and industrial sensors.

[0049] FIG. 1 is a diagram of an example architecture of a communication system to which embodiments of this application can be applied. The communication system may include a network device and six terminal devices. The six terminal devices may be cellular telephones, smartphones, portable computers, handheld communication devices, handheld computing devices, satellite radios, global positioning systems, personal digital assistants (PDAs), and / or any other suitable devices used for communication in a wireless communication system, and all may be connected to the network device. All six terminal devices may communicate with the network device. To be clear, the number of terminal devices in FIG. 1 is merely an example. There may be fewer or more terminal devices. The terminal devices in FIG. 1 are also an example. For example, the terminal devices may be Internet of Things devices such as smart water meters.

[0050] In the embodiments of this application, a terminal device is a device having a wireless transceiver function and capable of transmitting signals to and receiving signals from a network device. The terminal device may include user equipment (UE), and may also be referred to as a terminal, an access station, a UE station, a remote station, a wireless communication device, or a user equipment. The terminal device is configured to connect people, things, machines, etc., and can be widely used in various scenarios, including, but not limited to, terminal devices in the following scenarios: cellular communication, device to device (D2D), vehicle to everything (V2X), machine-to-machine / machine-type communications (M2M / MTC), IoT, virtual reality (VR), augmented reality (AR), industrial control, self driving, remote medical, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, unmanned aerial vehicles, and robots. For example, the terminal device may be a mobile phone, a tablet computer (Pad), a computer with a wireless transceiver function, a VR terminal, an AR terminal, a wireless terminal in industrial control, a wireless terminal in autonomous driving, a smart speaker in an IoT network, a wireless terminal device in telemedicine, a wireless terminal device in a smart grid, a wireless terminal device in traffic security, a wireless terminal device in a smart city, or a wireless terminal device in a smart home.

[0051] By way of example and not limitation, in embodiments of this application, the terminal device may instead be a wearable device. A wearable device, also referred to as a wearable intelligent device or an intelligent wearable device, is a general term for wearable devices, such as glasses, gloves, watches, clothes, and shoes, that are intelligently designed and developed for everyday wear by using wearable technology. When the various terminal devices described above are located in a vehicle (e.g., arranged or installed in a vehicle), all of these terminal devices may be considered as in-vehicle terminal devices. For example, an in-vehicle terminal device may also be referred to as an on-board unit (OBU). The terminal device in this application may instead be an in-vehicle module, automobile module, in-vehicle component, in-vehicle chip, or in-vehicle unit that is integrated into the vehicle as one or more components or units. The vehicle implements the method in this application using the in-vehicle module, automobile module, in-vehicle component, in-vehicle chip, or in-vehicle unit integrated into the vehicle.

[0052] In the embodiments of this application, a communication device configured to implement the functions of a terminal device may be a terminal device, or may be a device that can support a terminal device in implementing functions, such as a chip system. The device may be installed in a terminal device. In the technical solutions provided in the embodiments of this application, an example in which the device configured to implement the functions of a terminal device is a terminal device is used to describe the technical solutions provided in the embodiments of this application.

[0053] In the embodiments of this application, the network device may be an access device through which a terminal device wirelessly accesses a mobile communication system, and may include, for example, an access network (AN) device, such as a base station. Alternatively, the network device may be a device that communicates with a terminal device over an air interface. Alternatively, the network device may include an evolved NodeB (also referred to as eNB or e-NodeB for short) in an LTE system or a long-term evolution-advanced (LTE-A) system. Alternatively, the network device may include a next-generation NodeB (gNB) in a 5G NR system. Alternatively, the network device may include an access node or the like in a wireless fidelity (Wi-Fi) system. The network device may alternatively be a station, a relay station, an in-vehicle device, a future evolved Public Land Mobile Network (PLMN) device, a device in a D2D network, a device in an M2M network, a device in an Internet of Things (IoT) network, or a network device in a PLMN network, etc. The specific technology used by the network device and the specific device form are not limited to the embodiments of this application.

[0054] Furthermore, a base station in an embodiment of this application may include a central unit (CU) and distributed units (DUs), and multiple DUs may be centrally controlled by one CU. The CU and DU may be divided based on the protocol layer functions that each of the CU and DU has in a wireless network. For example, the packet data convergence protocol (PDCP) layer and protocol layer functions above the packet data convergence protocol layer are configured on the CU, and protocol layer functions below the PDCP layer, such as the radio link control (RLC) layer and the media access control (MAC) layer, are configured on the DU. Note that the division into protocol layers is merely an example, and other divisions of protocol layers are also possible. The radio frequency device may be deployed remotely rather than within the DU, may be integrated into the DU, or may be partially deployed remotely and partially integrated into the DU. This is not a limitation of the embodiment of this application. In some embodiments, the control plane (CP) and user plane (UP) of a CU may be separated into different entities for implementation, such as a control plane CU entity (CU-CP entity) and a user plane CU entity (CU-UP entity). In this network architecture, signaling generated by a CU can be sent to a terminal device via a DU, or signaling generated by a UE can be sent to a CU via a DU. The DU can transparently transmit signaling to a UE or CU by directly encapsulating the signaling at a protocol layer without analyzing the signaling. In this network architecture, the CU is classified as a network device on the radio access network (RAN) side.Alternatively, the CU may be classified as a network device on the core network (CN) side, although this is not a limitation in this application.

[0055] In the embodiments of this application, a communication device configured to implement the functions of a network device may be a network device, or may be a device that can support a network device in implementing functions, such as a chip system. The device may be installed in a network device. In the technical solutions provided in the embodiments of this application, an example in which the device configured to implement the functions of a network device is a network device is used to describe the technical solutions provided in the embodiments of this application.

[0056] The embodiments of this application mainly relate to HARQ feedback for multicast services. In order to better understand the solutions provided in the embodiments of this application, content related to multicast services and HARQ feedback for multicast services will be first described.

[0057] (1) A multicast service is a service targeted at multiple terminal devices, such as live streaming and scheduled program playback. In LTE, a multicast service is also called a multimedia broadcast multicast service (MBMS). In NR, a multicast service is also called a multicast broadcast service (MBS). In the embodiments of this application, a multicast service and a multimedia broadcast multicast service may be interchangeable, and a multicast service and a multicast / multicast broadcast service may be interchangeable.

[0058] Multicast services may be transmitted on a physical downlink shared channel (PDSCH). Unlike a PDSCH carrying unicast data, a PDSCH carrying multicast data is referred to as a multicast PDSCH. A network device (e.g., a base station) transmits downlink control information (DCI) carried on a physical downlink control channel (PDCCH) to a group of terminal devices in a cell, and the group of terminal devices receives the multicast PDSCH based on scheduling information included in the DCI.

[0059] Logical channels used for multicast service transmission include a multicast control channel (MCCH), a multicast traffic channel (MTCH), and a dedicated traffic channel (DTCH). The MTCH is a point-to-point downlink channel and can be used by a network device to transmit MBS data of a multicast session or a broadcast session to a terminal device. The MCCH is also a point-to-point downlink channel and can be used by a network device to transmit multicast control information related to one or more MTCHs to a terminal device. The DTCH can be used by a network device to transmit MBS data of a multicast session to a terminal device. Both the MCCH and the MTCH can be mapped to a downlink shared channel (DL-SCH). The control information transmitted on the MCCH includes service identifiers and configuration information of the MTCH, such as a temporary mobile group identity (TMGI), a session ID, a group radio network temporary identifier (G-RNTI) used to scramble downlink control information (DCI), and time domain discontinuous reception (DRX) configuration information. One G-RNTI can be associated with one multicast service.It may be understood that when a network device schedules the PDSCH in a semi-persistent scheduling (SPS) manner, the radio network temporary identifier used to scramble the DCI is a group-configured scheduling-RNTI (G-CS-RNTI). One G-CS-RNTI may be associated with one multicast service.

[0060] A network device may transmit DCI carried on a physical downlink control channel (PDCCH) to a group of terminal devices in a cell. The DCI is scrambled with a G-RNTI or G-CS-RNTI associated with a multicast service and is used to schedule a multicast PDSCH carrying the multicast service. The terminal devices obtain the physical downlink channel PDSCH scheduled with the DCI by detecting the DCI scrambled with the G-RNTI, and further obtain the service data carried on the PDSCH.

[0061] (2) A HARQ-ACK information report for a multicast service may be referred to as a multicast HARQ-ACK information report (or feedback), or simply as a HARQ-ACK information report (or feedback). In the embodiments of this application, the multicast HARQ-ACK information report (or feedback) and the HARQ-ACK information report (or feedback) may be interchangeable.

[0062] The multicast HARQ-ACK information reporting includes two reporting modes, which are an ACK / NACK-based HARQ-ACK information reporting mode and a NACK-only-based HARQ-ACK information reporting mode, respectively. For ease of description, this specification refers to the ACK / NACK-based HARQ-ACK information reporting mode as the first reporting mode, and correspondingly, the NACK-only-based HARQ-ACK information reporting mode as the second reporting mode. The first reporting mode means that a terminal device feeds back an ACK or NACK on a multicast PUCCH based on a decoding result of a PDSCH carrying multicast service data. It can be understood that when the decoding result is correct, the terminal device feeds back an ACK, and when the decoding result is incorrect, the terminal device feeds back a NACK. For example, when the terminal device correctly decodes a transport block or detects a DCI format indicating a semi-persistent scheduling PDSCH release, the terminal device generates HARQ-ACK information with an ACK value; otherwise, the terminal device generates HARQ-ACK information with a NACK value.

[0063] Correspondingly, the second reporting mode means that the terminal device only feeds back a NACK on the multicast PUCCH when the multicast PDSCH is incorrectly decoded. The terminal device does not feed back an ACK when the multicast PDSCH is correctly decoded. This can also be understood as the terminal device not transmitting a PUCCH including only HARQ-ACK information with an ACK value. Note that the NACK-only based HARQ-ACK information reporting mode is not applicable in the following cases: the number of information bits of the HARQ-ACK information exceeds 4, the first SPS PDSCH reception after activation of SPS PDSCH reception for an SPS configuration, or a DCI format with associated HARQ-ACK information without scheduling PDSCH reception.

[0064] One or more cells may be configured for one terminal device, one or more G-RNTIs may be configured for one cell, and one or more G-CS-RNTIs may be configured for one cell. For the G-RNTI or G-CS-RNTI, the network device may configure a first reporting mode or a second reporting mode. This may also be understood as the following, that is, for a multicast service, the network device may configure the first reporting mode or the second reporting mode. For the G-RNTI or G-CS-RNTI, the network device may further configure to enable or disable HARQ-ACK information feedback. Alternatively, the network device may indicate whether to feedback HARQ-ACK information by using DCI. When the network device configures to indicate whether to feedback HARQ-ACK information using DCI, a field of the DCI may enable or disable HARQ-ACK information feedback for a scheduled multicast PDSCH.

[0065] (3) Resource configuration used to feed back HARQ-ACK information for multicast services: In the embodiments of this application, unless otherwise specified, the resources used to feed back HARQ-ACK information for multicast services and the resources used to feed back HARQ-ACK information (or PUCCH resources used to feed back HARQ-ACK information) may be replaced with each other. Alternatively, the resources used to feed back HARQ-ACK information for multicast services and the multicast PUCCH resources used to feed back HARQ-ACK information may be replaced with each other.

[0066] The network device may configure, for the terminal device, a PUCCH resource used to feed back HARQ-ACK information for a multicast service. The terminal device may transmit HARQ-ACK information for the multicast service to the network device based on the configuration of the network device. Figure 2 is a diagram of feeding back HARQ-ACK information for a multicast service. It can be seen from Figure 2 that the terminal device receives a multicast PDSCH in slot n and transmits HARQ-ACK information for the multicast PDSCH in slot n+k. If the first reporting mode is configured for the multicast service, the terminal device determines that the decoding result of the multicast PDSCH is incorrect and reports HARQ information including a NACK value on the multicast PUCCH; otherwise, the terminal device determines that the decoding result of the multicast PDSCH is correct and reports HARQ information including an ACK value on the multicast PUCCH. If the second reporting mode is configured for a multicast service, the terminal device determines that the decoding result of the multicast PDSCH is incorrect and reports HARQ information including a NACK value on the multicast PUCCH; otherwise, the terminal device determines that the decoding result of the multicast PDSCH is correct and does not report HARQ information including an ACK value.

[0067] In the first reporting mode, the network device may configure a PUCCH configuration (PUCCH-Config) for the terminal device, and the PUCCH-Config may indicate candidate PUCCH resources used by the terminal device to report HARQ information. Alternatively, the network device may configure multiple PUCCH configurations for the terminal device, which may be considered as the network device configuring a PUCCH configuration list (PUCCHConfigurationList). The PUCCHConfigurationList includes up to two PUCCH configurations. Similarly, in the second reporting mode, the network device may also configure an independent PUCCH-Config or PUCCHConfigurationList for the terminal device. Note that in the second reporting mode, the PUCCH resource format configured by the network device includes Format 0 or Format 1. In the first reporting mode, the PUCCH resource format configured by the network device includes Format 0, Format 1, Format 2, Format 3, or Format 4. In the second reporting mode, one PUCCH-Config includes one PUCCH resource set, and the resource set includes 32 or fewer PUCCH resources. In the first reporting mode, one PUCCH-Config may include up to four PUCCH resource sets. It may be understood that a network device configures a PUCCH configuration for a unicast service and also configures a PUCCH configuration for a multicast service. If the network device does not separately configure an independent PUCCH-Config or PUCCHConfigurationList for a multicast service, the unicast PUCCH-Config or PUCCHConfigurationList is reused.

[0068] The priorities of different multicast services may be different, which can be understood as the priorities of PDSCHs (referred to as multicast PDSCHs for short in this specification) carrying different multicast services may be different. The priority of a multicast PDSCH may be indicated in a DCI for scheduling the multicast PDSCH. If a field indicating the priority is not present in the DCI, the priority of the scheduled multicast PDSCH is a default low priority. For an SPS multicast PDSCH, the priority of the multicast PDSCH is configured in the multicast SPS-Config. Correspondingly, the multicast PUCCH resource used to feed back HARQ-ACK information also has a priority. In other words, different multicast PUCCH resources may have different priorities. Note that if the priority of the multicast PDSCH configured by the network device is a high priority and the network device enables HARQ-ACK information feedback, the terminal device feeds back the HARQ-ACK information by using the high-priority multicast PUCCH. When the priority of the multicast PDSCH configured by the network device is low priority and the network device enables HARQ-ACK information feedback, the terminal device feedbacks the HARQ-ACK information by using a low-priority multicast PUCCH. Specifically, two PUCCH-Configurations are configured in a PUCCH Configuration List, and the priority of the PUCCH resource configured in the first PUCCH-Configuration of the two PUCCH-Configurations is lower than the priority of the PUCCH resource configured in the second PUCCH-Config of the two PUCCH-Configs. It can be understood that the first PUCCH-Configuration and the second PUCCH-Config are distinguished based on the order of the PUCCH-Configurations in the PUCCH Configuration List.It should be noted that if a network device does not configure a PUCCHConfigurationList, there are no high-priority PUCCH resources by default, in other words, there are only low-priority PUCCH resources, and the PUCCH resources are configured in the PUCCH-Config.

[0069] Embodiments of this application relate to normal uplink (NUL) carriers and supplementary uplink (SUL) carriers. One or more uplink carriers associated with a cell's downlink carrier may include at least one NUL carrier and may further include one SUL carrier.

[0070] The terms "system" and "network" may be used interchangeably in the embodiments of this application. In the embodiments of this application, "multiple" may also be understood as "at least two." "At least one" may be understood as one or more, for example, one, two, or more. For example, "including at least one" means "including one, two, or more," without any limitation on which are included. For example, "including at least one of A, B, and C" may mean "including A, B, or C," "including A and B, A and C, or B and C," or "including A, B, and C." The term "and / or" describes an association relationship for describing related objects and indicates that three relationships may exist. For example, A and / or B may represent the following three cases: only A exists, both A and B exist, and only B exists. Furthermore, unless otherwise specified, the character " / " generally indicates an "or" relationship between related objects.

[0071] Unless otherwise specified, ordinal numbers such as "first" and "second" in the embodiments of this application are used to distinguish between multiple objects and are not intended to limit the order, chronology, priority, or importance of the multiple objects. For example, a first reporting mode and a second reporting mode are intended to distinguish between different reporting modes and are not intended to limit the function, priority, importance, etc. of the two reporting modes. In the embodiments of this application, unless otherwise specified, "when" and "if" can be interchanged.

[0072] Some terms in the embodiments of this application have been explained above, and some contents related to the embodiments of this application will be explained below.

[0073] In a terminal device configured with the second reporting mode, if the number of transport blocks (TBs) for feeding back HARQ-ACK information on the same multicast PUCCH is greater than four, the second reporting mode is switched to the first reporting mode. In other words, even if the network device configures the second reporting mode, if the number of TBs for feeding back HARQ-ACK information on the same multicast PUCCH is greater than four, the terminal device can feed back HARQ-ACK information in the first reporting mode. If the number of TBs for feeding back HARQ-ACK information on the same multicast PUCCH does not exceed four, the terminal device may select two TBs based on the decoding results of the TBs corresponding to each multicast PDSCH. TBの数 - Determine one PUCCH resource from one orthogonal multicast PUCCH resource to feed back HARQ-ACK information. If the number of TBs used by the terminal device to feed back HARQ-ACK information is m, then 2 mOne PUCCH resource is determined from one PUCCH resource to feed back HARQ-ACK information. However, if any one of the following cases occurs, the terminal device may switch from the second reporting mode to the first reporting mode:

[0074] Case 1: If a multicast PUCCH resource used to feed back HARQ-ACK information overlaps with a unicast PUCCH (or PUSCH) resource whose priority is the same as that of the multicast PUCCH resource, the second reporting mode is switched to the first reporting mode, and the unicast PUCCH resource or the unicast PUSCH resource is reused to feed back HARQ-ACK information. In other words, if a multicast PUCCH resource used to feed back HARQ-ACK information overlaps with a unicast PUCCH (or PUSCH) resource whose priority is the same as that of the multicast PUCCH resource, even if the network device configures the second reporting mode, the terminal device still feeds back HARQ-ACK information in the first reporting mode. In addition, the terminal device reuses the unicast PUCCH resource or the unicast PUSCH resource to feed back HARQ-ACK information.

[0075] Case 2: If the time domain resource of a multicast PUCCH resource based on the second reporting mode and the time domain resource of a multicast PUCCH resource based on the first reporting mode and having the same priority as the multicast PUCCH resource are in the same slot, the second reporting mode is switched to the first reporting mode.

[0076] It can be understood that when a terminal device uses one TB to feed back HARQ-ACK information and there is only one PUCCH resource used to feed back the HARQ-ACK information, if the PUCCH resource and a unicast PUCCH resource or PUSCH resource having the same priority as the PUCCH resource are in the same slot, even if the network device configures the second reporting mode, the terminal device still feeds back the HARQ-ACK information in the first reporting mode. In addition, the terminal device reuses the unicast PUCCH resource or the unicast PUSCH resource to feed back the HARQ-ACK information. Note that even if the terminal device determines that the TB decoding result for the HARQ-ACK information is correct, the terminal device reuses the unicast PUCCH resource or the unicast PUSCH resource to feed back the HARQ-ACK information.

[0077] However, when two or more TBs are used to feed back HARQ-ACK information on the same multicast PUCCH, i.e., when m is greater than or equal to 2, there are multiple multicast PUCCH resources used to feed back HARQ-ACK information. For example, if the number of TBs used by the terminal device to feed back HARQ-ACK information is 4, then the number of TBs used to feed back HARQ-ACK information is 2. 4There are -1=15 multicast PUCCH resources. Considering that the starting symbols occupied by different multicast PUCCH resources may be different for these multiple multicast PUCCH resources, the number of symbols occupied by different multicast PUCCH resources may also be different. Correspondingly, the cases in which different multicast PUCCH resources overlap with unicast PUCCH (or PUSCH) resources having the same priority as the priority of the multicast PUCCH resource also differ. For example, among multiple multicast PUCCH resources, some of the multicast PUCCH resources overlap with unicast PUCCH resources having the same priority as the priority of the multicast PUCCH resource, and some of the multicast PUCCH resources do not overlap with unicast PUCCH resources having the same priority as the priority of the multicast PUCCH resource.

[0078] The terminal device determines a multicast PUCCH resource to be used for feeding back HARQ-ACK information from multiple multicast PUCCH resources based on the decoding result of the multicast PDSCH TB. In order to reduce the processing latency of the terminal device and reduce the requirement for the network device to perform blind detection multiple times, the terminal device may determine whether the multicast PUCCH resource used for feeding back HARQ-ACK information overlaps with a unicast PUCCH resource having the same priority as the priority of the multicast PUCCH resource, without relying on the decoding result of the multicast PDSCH TB. However, before obtaining the decoding result of the multicast PDSCH TB, the terminal device cannot determine which one or more PUCCH resources will be used for feeding back HARQ-ACK information based on the decoding result of the multicast PDSCH TB, and therefore cannot determine whether the PUCCH resource used for feeding back HARQ-ACK information overlaps with a unicast PUCCH resource or a unicast PUSCH resource having the same priority as the priority of the PUCCH resource. Therefore, when a PUCCH resource used to feed back HARQ-ACK information overlaps with a unicast PUCCH resource or a unicast PUSCH resource having the same priority as the priority of the PUCCH resource, the terminal device may not be able to switch from the second reporting mode to the first reporting mode even if the second reporting mode is configured for the terminal device.

[0079] For ease of understanding, Figure 3 is a diagram of feeding back two multicast PDSCH TBs by a terminal device. Figure 3 uses an example in which the two TBs are TB 0 and TB 1. It can be understood that Figure 3 shows three multicast PUCCH resources, namely PUCCH resource 0, PUCCH resource 1, and PUCCH resource 2. The terminal device may feed back HARQ-ACK information on these three multicast PUCCH resources. The symbols occupied by PUCCH resource 0 are symbols 0 to 4, the symbols occupied by PUCCH resource 1 are symbols 7 and 8, and the symbols occupied by PUCCH resource 2 are symbols 0 and 1. Assume that the symbols occupied by unicast PUCCH resources are symbols 4 to 6. When the PUCCH resource used to feed back HARQ-ACK information is PUCCH resource 0, the PUCCH resource used to feed back HARQ-ACK information overlaps with a unicast PUCCH (or PUSCH) resource having the same priority as the priority of the PUCCH resource. When the PUCCH resource used to feed back HARQ-ACK information is PUCCH resource 1, the PUCCH resource used to feed back HARQ-ACK information does not overlap with a unicast PUCCH (or PUSCH) resource having the same priority as the priority of the PUCCH resource. Therefore, when there are multiple multicast PUCCH resources, before obtaining the decoding result of the multicast PDSCH TB, the terminal device cannot determine which one or more multicast PUCCH resources overlap with a unicast PUCCH resource or a unicast PUSCH resource having the same priority as the priority of the one or more multicast PUCCH resources. Thus, when the second reporting mode is configured for the terminal device, the second reporting mode is not switched to the first reporting mode when it needs to be switched to the first reporting mode.

[0080] In view of this, a solution is provided in an embodiment of this application. The embodiment of this application provides a method for determining whether a multicast PUCCH resource overlaps with a unicast PUCCH resource or a unicast PUSCH resource having the same priority as the priority of the multicast PUCCH resource in the time domain. Even if a terminal device does not obtain a decoding result of a multicast PDSCH TB, it can still determine whether a multicast PUCCH resource overlaps with a unicast PUCCH resource or a unicast PUSCH resource having the same priority as the priority of the multicast PUCCH resource in the time domain, and can determine whether the second reporting mode should be switched to the first reporting mode.

[0081] The following describes in detail the solution provided in the embodiments of this application with reference to the accompanying drawings. Figure 4 is a schematic flowchart of a multicast service feedback method according to an embodiment of this application. The following description uses an example in which the method is applicable to the communication system shown in Figure 1. The following unicast uplink resources include unicast PUCCH resources and / or unicast PUSCH resources. Whether a multicast PUCCH resource overlaps with a unicast PUCCH resource or a unicast PUSCH resource having the same priority as that of the multicast PUCCH resource in the time domain can be understood as follows: when the priority of the multicast PUCCH resource is the same as that of the unicast PUCCH resource or the unicast PUSCH resource, it is determined whether the multicast PUCCH resource overlaps with the unicast PUCCH resource or the unicast PUSCH resource in the time domain. It can be understood that the priority of multiple multicast PUCCH resources is the same. In other words, the priority of a resource set described below is the priority of any multicast PUCCH resource included in the resource set.

[0082] 4 is a schematic flowchart of a multicast service feedback method according to an embodiment of this application. The method procedure includes the following steps:

[0083] S401: A network device transmits first configuration information to a terminal device, and correspondingly, the terminal device receives the first configuration information transmitted by the network device.

[0084] The first configuration information may be used to configure a mode in which a terminal device feeds back HARQ-ACK information for a multicast service. For example, the first configuration information may instruct the terminal device to feed back HARQ-ACK information based on NACK-only. In other words, the first configuration information indicates a second reporting mode. For an explanation of the second reporting mode, please refer to the relevant content of the above technical terms. Details will not be described again here. The first configuration information may be carried in one or more of radio resource control (RRC) signaling, DCI, or MAC control element (CE).

[0085] S402: The network device sends second configuration information to the terminal device, and correspondingly, the terminal device receives the second configuration information sent by the network device.

[0086] The second configuration information may be used to configure, for the terminal device, a PUCCH resource used to feed back HARQ-ACK information. For example, the second configuration information may indicate a multicast PUCCH resource set, a PUCCH-Config, or a PUCCHConfigurationList. Specifically, the network device may configure one PUCCH resource or multiple PUCCH resources by using the second configuration information. It may be understood that the network device may also configure, for the terminal, a PUCCH resource used for a unicast service. If the network device configures a unicast PUCCH resource for the terminal device but does not configure a multicast PUCCH resource for the terminal device, the terminal device may reuse the unicast PUCCH resource to feed back HARQ-ACK information for the multicast service to the network device. Therefore, S402 is not a required step but is an optional step, and is indicated by a dashed line in FIG. 4.

[0087] S403: When determining that the resource set overlaps with the unicast uplink resource, the terminal device sends HARQ-ACK information for the multicast service to the network device in a first reporting mode.

[0088] The resource set may include multiple multicast PUCCH resources. If the network device configures a multicast PUCCH resource set for the terminal device, the resource set belongs to the multicast PUCCH resource set configured by the network device. In other words, the resource set belongs to the multicast PUCCH resource set indicated by the second configuration information. In particular, if the network device does not configure a multicast PUCCH resource for the terminal device, the resource set and the unicast PUCCH resource belong to the same PUCCH resource set. In this case, the terminal device reuses the unicast PUCCH resource as the multicast PUCCH resource.

[0089] When the number of TBs used by the terminal device to feed back HARQ-ACK information is m, the resource set is 2 m The resource set may include one PUCCH resource. When m is an integer greater than or equal to 1, the resource set includes multiple multicast PUCCH resources. The case where different multicast PUCCH resources overlap with unicast uplink resources is different, and some of the multicast PUCCH resources do not overlap with unicast uplink resources. Before obtaining the decoding result of the multicast PDSCH TB, the terminal device cannot determine which one or more multicast PUCCH resources are used to feed back HARQ-ACK information, and therefore cannot determine whether one or more multicast PUCCH resources used to feed back HARQ-ACK information overlap with unicast uplink resources.

[0090] Therefore, in this embodiment of this application, it is clearly defined that whether the multicast PUCCH resource used to feed back HARQ-ACK information overlaps with the unicast uplink resource is determined based on whether the resource set overlaps with the unicast uplink resource. m- Use one PUCCH resource as a whole to determine whether the PUCCH resource overlaps with a unicast uplink resource. Note that a resource set overlapping with a unicast uplink resource may include a resource set overlapping with a unicast uplink resource having the same priority as the priority of the resource set. In other words, the terminal device determines whether a resource set overlaps with a unicast uplink resource having the same priority as the priority of the resource set. Also, in this embodiment of this application, resource overlap means that resources overlap in the time domain, and the resource overlap may be partial or complete overlap.

[0091] It may be understood that the terminal device may transmit HARQ-ACK information by using some or all of the multiple multicast PUCCH resources. For ease of description, in this embodiment of the application, some or all of the multiple multicast PUCCH resources are referred to as candidate multicast PUCCH resources. It should be understood that the candidate multicast PUCCH resources belong to a resource set, and the terminal device may feed back HARQ-ACK information on some or all of the candidate multicast PUCCH resources. The terminal device may determine the candidate multicast PUCCH resources from the resource set. If the candidate multicast PUCCH resources overlap with the unicast uplink resources, the terminal device switches the second reporting mode to the first reporting mode even if the second reporting mode is configured for the terminal device.

[0092] In one possible implementation, when a candidate multicast PUCCH resource satisfies a first condition, the terminal device determines that the resource set overlaps with the unicast uplink resource. The first condition includes that the time domain resource corresponding to the candidate multicast PUCCH resource includes a set of time domain symbols each occupied by a resource in the resource set. This can also be understood as the terminal device using the set of time domain symbols each occupied by a resource in the resource set as the time domain resource used to feed back HARQ-ACK information. Note that the resource set can be determined based on the number m of TBs for feeding back HARQ by the terminal device. For example, if the network device configures 15 PUCCH resource sets but the number of TBs for feeding back HARQ by the terminal device is 2, the resource set is three PUCCH resource sets out of the 15 PUCCH resource sets.

[0093] The set of time domain symbols respectively occupied by the resources in the resource set may have multiple implementations, one or more of which may be predefined or preconfigured. In the following, multiple implementations are described separately. In the following description, it is assumed that m is 2 or more and the resource set is 2. m Use an example that includes one PUCCH resource.

[0094] Implementation 1: The time domain resource corresponding to the candidate multicast PUCCH resource is m - the set of symbols occupied by one PUCCH resource. m The union of the symbols each occupied by one PUCCH resource is used as the time domain resource corresponding to the candidate multicast PUCCH resource.

[0095] Implementation 2: The time domain resources corresponding to the candidate multicast PUCCH resources are the first start symbol, the first end symbol, and the second end symbol. m The symbols between the first start symbol and the first end symbol occupied by one PUCCH resource. The first start symbol is m The symbol with the earliest start time within the time domain symbols occupied by one PUCCH resource, the first ending symbol being the symbol with the earliest start time within the time domain symbols occupied by one PUCCH resource, m The symbol with the latest end time among the time domain symbols occupied by one PUCCH resource.

[0096] Implementation 3: The symbols occupied by the candidate multicast PUCCH resources in the time domain are m All symbols in a slot with one PUCCH resource.

[0097] Implementation 4: The time domain resource corresponding to the candidate multicast PUCCH resource is a set of a first symbol, a second symbol, and a symbol between the first symbol and the second symbol. m - the first symbol of one PUCCH resource, and the second symbol is m - the end symbol of one PUCCH resource. Note that the premise of implementation form 4 is that the network device m - The start symbol of one PUCCH resource is the same, and m - Configuring or indicating that the end symbols of one PUCCH resource are the same.

[0098] When the terminal device determines that the candidate multicast PUCCH resource implemented in any one of implementation forms 1 to 4 overlaps with the unicast uplink resource, the terminal device switches the second reporting mode to the first reporting mode. In other words, the terminal device transmits HARQ-ACK information on the candidate multicast PUCCH resource in the first reporting mode. Note that implementation forms 1 to 4 in this embodiment of this application are merely examples. In one possible implementation, the candidate multicast PUCCH resource may further include other implementation forms. For example, the candidate multicast PUCCH resource may be a unicast uplink resource. m - It may include symbols each occupied by one PUCCH resource and other symbols determined according to a preset rule.

[0099] In particular, in implementation form 4, the network device m - The start symbol of one PUCCH resource is the same, and m It can be understood that the terminal device configures or indicates that the end symbols of two PUCCH resources are the same. m -When a network device configures or indicates that the start symbols of two PUCCH resources are different, without expecting m - It is not expected that the network device configures or indicates that the end symbols of two PUCCH resources are different. m If the terminal device configures or indicates that the starting symbols of one PUCCH resource are different, the terminal device may consider that an incorrect configuration or indication has been received, and the terminal device may ignore the configuration or indication. Alternatively, the terminal device may m - Determine that the starting symbol of one PUCCH resource is different, and the terminal device does not feed back HARQ-ACK information. mIf the terminal device configures or indicates that the end symbols of one PUCCH resource are different, the terminal device may consider that an incorrect configuration or indication has been received, and the terminal device may ignore the configuration or indication. Alternatively, the terminal device may m - It is determined that the end symbol of one PUCCH resource is configured or indicated to be different, and the terminal device does not feed back HARQ-ACK information.

[0100] In order to understand Implementation Form 1 to Implementation Form 4, Implementation Form 1 to Implementation Form 4 will be described in detail below with reference to the accompanying drawings. It can be understood that one or more cells can be configured for one terminal device. One or more G-RNTIs can be configured for one cell, or one or more G-CS-RNTIs can be configured for one cell. When multiple cells are configured for a terminal device, the subcarrier spacings of the multiple cells may be the same or different. This is not limited in the embodiments of this application. Below, Implementation Form 1 to Implementation Form 4 will be described by using multiple different scenarios as examples.

[0101] Scenario 1: A cell is configured for a terminal device, and the carrier of the cell is a NUL carrier. In other words, the subcarrier spacings configured for the cells are the same.

[0102] For example, Figure 5 is a first diagram of candidate multicast PUCCH resources. In Figure 5, m=3 is used as an example. Specifically, there are three TBs for HARQ-ACK information, and there are seven corresponding multicast PUCCH resources. Specifically, the three TBs in Figure 5 are TB 0, TB 1, and TB 2. The seven multicast PUCCH resources are PUCCH resource 0 to PUCCH resource 6. The symbols occupied by PUCCH resource 0 are symbols 0 to 4, the symbols occupied by PUCCH resource 1 are symbols 7 and 8, the symbols occupied by PUCCH resource 2 are symbols 0 and 1, the symbols occupied by PUCCH resource 3 are symbols 7 to 11, the symbols occupied by PUCCH resource 4 are symbols 0 to 4, the symbols occupied by PUCCH resource 5 are symbols 10 and 11, and the symbols occupied by PUCCH resource 6 are symbols 3 and 4.

[0103] It can be seen from implementation 1 that the time domain resources corresponding to the candidate multicast PUCCH resources are symbol 0 to symbol 4 and symbol 7 to symbol 11. It can be seen from implementation 2 that the time domain resources corresponding to the candidate multicast PUCCH resources are symbol 0 to symbol 11. It can be seen from implementation 3 that the time domain resources corresponding to the candidate multicast PUCCH resources are symbol 0 to symbol 13. Assume that a network device configures or indicates that the starting symbol of PUCCH resource 0 to PUCCH resource 6 is the same and the ending symbol of PUCCH resource 0 to PUCCH resource 6 is the same. As shown in FIG. 5, if the starting symbol of PUCCH resource 0 to PUCCH resource 6 is symbol 0 and the ending symbol of PUCCH resource 0 to PUCCH resource 6 is symbol 4, it can be seen from implementation 4 that the time domain resources corresponding to the candidate multicast PUCCH resources are symbol 0 to symbol 4.

[0104] For example, the symbols occupied by unicast uplink resource 1 are symbol 5 and symbol 6. Based on Implementation 1, the terminal device may determine that the resource set does not overlap with unicast uplink resource 1, and therefore does not need to switch the second reporting mode to the first reporting mode. Based on Implementation 2, the terminal device may determine that the resource set overlaps with unicast uplink resource 1, i.e., overlap occurs on symbol 5 and symbol 6. In this case, the terminal device needs to switch the second reporting mode to the first reporting mode. Based on Implementation 3, the terminal device may determine that the resource set overlaps with unicast uplink resource 1, i.e., overlap occurs on symbol 5 and symbol 6. In this case, the terminal device needs to switch the second reporting mode to the first reporting mode. Based on Implementation 4, the terminal device may determine that the resource set does not overlap with unicast uplink resource 1. In this case, the terminal device does not need to switch the second reporting mode to the first reporting mode.

[0105] In another example, the symbols occupied by unicast uplink resource 2 are symbol 12 and symbol 13. The terminal device may determine, based on implementation 2, that the resource set does not overlap with unicast uplink resource 1, and therefore does not need to switch the second reporting mode to the first reporting mode. The terminal device may determine, based on implementation 2, that the resource set does not overlap with unicast uplink resource 2. In this case, the terminal device does not need to switch the second reporting mode to the first reporting mode. The terminal device may determine, based on implementation 3, that the resource set overlaps with unicast uplink resource 2, i.e., overlap occurs on symbol 12 and symbol 13. In this case, the terminal device needs to switch the second reporting mode to the first reporting mode. The terminal device may determine, based on implementation 4, that the resource set does not overlap with unicast uplink resource 2. In this case, the terminal device does not need to switch the second reporting mode to the first reporting mode.

[0106] Scenario 2: A plurality of cells can be configured for a terminal device, the carriers of the plurality of cells are all null carriers, and the subcarrier spacing of the plurality of cells is the same. A candidate multicast PUCCH resource is configured on the carrier of one of the plurality of cells.

[0107] For example, Figure 6 is a second diagram of candidate multicast PUCCH resources. Figure 6 uses an example in which two cells are configured for a terminal device, the carriers of the two cells are both null carriers, and the subcarrier spacing of the two cells is the same. The candidate multicast PUCCH resource is configured on the carrier of one of these cells, and the unicast uplink resource is configured on the carrier of the other cell. Figure 6 uses an example in which the terminal device transmits a multicast PUCCH in slot n1 and a PUSCH in slot n1. For the terminal device to determine whether the candidate multicast PUCCH resource overlaps with the unicast uplink resource in the scenario shown in Figure 6, please refer to the relevant content in Figure 5. Details will not be described again here.

[0108] Scenario 3: Multiple cells can be configured for a terminal device, and the carriers of the multiple cells can be different, and the subcarrier spacing of the multiple cells is the same. For example, the subcarrier spacing corresponding to two cells is 15 kHz. A candidate multicast PUCCH resource is configured on the carrier of one of the multiple cells.

[0109] For example, Figure 7 is a third diagram of candidate multicast PUCCH resources. Figure 7 uses an example in which two cells are configured for a terminal device, the carriers of the two cells include a NUL carrier and a SUL carrier, and the subcarrier spacing of the two cells is the same. The candidate multicast PUCCH resource is configured on the carrier of one of these cells, and the unicast uplink resource is configured on the carrier of the other cell. The difference between Figure 7 and Figure 6 is that the subcarriers of the two cells configured for the terminal device include a NUL carrier and a SUL carrier. For the terminal device to determine whether the candidate multicast PUCCH resource overlaps with the unicast uplink resource in the scenario shown in Figure 7, please refer to the relevant content in Figure 6. The details will not be described again here.

[0110] Scenario 4: Multiple cells can be configured for a terminal device, where the carriers of the multiple cells are the same and the subcarrier spacings of the multiple cells are different. For example, the subcarrier spacings corresponding to the multiple cells include 15 kHz and 30 kHz.

[0111] For example, Figure 8 is a third diagram of candidate multicast PUCCH resources. Figure 8 uses an example in which two cells are configured for a terminal device, the carriers of the two cells are null carriers, and the subcarrier spacing of one of the cells is 15 kHz and the subcarrier spacing of the other cell is 30 kHz. The subcarrier spacing corresponding to the multicast PUCCH resource is 30 kHz. The subcarrier spacing corresponding to the unicast uplink resource is 15 kHz. The terminal device transmits the multicast PUCCH in slot n1 and transmits the PUSCH in slot n2. Figure 8 uses m=4 as an example. Specifically, there are four TBs for HARQ-ACK information, and there are 15 multicast PUCCH resources. The four TBs in Figure 8 are TB 0, TB 1, TB 2, and TB 3. The 15 multicast PUCCH resources are PUCCH resource 0 to PUCCH resource 14. The symbols occupied by PUCCH resource 0 are symbol 3 and symbol 4, the symbols occupied by PUCCH resource 1 are symbol 8 and symbol 9, the symbols occupied by PUCCH resource 2 are symbol 3 and symbol 4, the symbols occupied by PUCCH resource 3 are symbol 8 and symbol 9, the symbols occupied by PUCCH resource 4 are symbol 3 and symbol 4, the symbols occupied by PUCCH resource 5 are symbol 8 and symbol 9, the symbols occupied by PUCCH resource 6 are symbol 3 and symbol 4, the symbols occupied by PUCCH resource 7 are symbol 8 and symbol 9, the symbols occupied by PUCCH resource 8 is symbol 4, the symbols occupied by PUCCH resource 9 is symbol 8, the symbols occupied by PUCCH resource 10 is symbol 3, the symbols occupied by PUCCH resource 11 is symbol 9, the symbols occupied by PUCCH resource 12 is symbol 4, the symbols occupied by PUCCH resource 13 is symbol 8, and the symbols occupied by PUCCH resource 14 is symbol 3.

[0112] It can be seen from implementation 1 that the time domain resources corresponding to the candidate multicast PUCCH resources are symbol 3, symbol 4, symbol 8, and symbol 9. It can be seen from implementation 2 that the time domain resources corresponding to the candidate multicast PUCCH resources are symbol 3 to symbol 9. It can be seen from implementation 3 that the time domain resources corresponding to the candidate multicast PUCCH resources are symbol 0 to symbol 13. Assume that the network device configures or indicates that the starting symbol of PUCCH resource 0 to PUCCH resource 14 is the same and the ending symbol of PUCCH resource 0 to PUCCH resource 14 is the same. As shown in Figure 8, if the starting symbol of PUCCH resource 0 to PUCCH resource 14 is symbol 0 and the ending symbol of PUCCH resource 0 to PUCCH resource 14 is symbol 4, it can be seen from implementation 4 that the time domain resources corresponding to the candidate multicast PUCCH resources are symbol 3 and symbol 4.

[0113] For example, the symbols occupied by unicast uplink resource 1 are symbol 0 to symbol 7. Based on Implementation 1, the terminal device may determine that the resource set does not overlap with unicast uplink resource 1, and therefore does not need to switch the second reporting mode to the first reporting mode. Based on Implementation 2, the terminal device may determine that the resource set does not overlap with unicast uplink resource 1, and therefore does not need to switch the second reporting mode to the first reporting mode. Based on Implementation 3, the terminal device may determine that the resource set overlaps with unicast uplink resource 1, i.e., overlap occurs on symbol 0 and symbol 1. In this case, the terminal device needs to switch the second reporting mode to the first reporting mode. Based on Implementation 4, the terminal device may determine that the resource set does not overlap with unicast uplink resource 1. In this case, the terminal device does not need to switch the second reporting mode to the first reporting mode.

[0114] In another example, the symbols occupied by unicast uplink resource 2 are symbol 0 to symbol 8. The terminal device may determine that the resource set overlaps with unicast uplink resource 2 based on Implementation 1, Implementation 2, Implementation 3, or Implementation 4. In other words, symbol 3 in the multicast PUCCH resource partially overlaps with symbol 8 in the unicast uplink resource. In this case, the second reporting mode needs to be switched to the first reporting mode.

[0115] In another example, the symbols occupied by unicast uplink resource 3 are symbol 12 and symbol 13. The terminal device can determine, based on Implementation 1, Implementation 2, or Implementation 4, that the resource set does not overlap with unicast uplink resource 3, and therefore does not need to switch the second reporting mode to the first reporting mode. The terminal device can determine, based on Implementation 3, that symbols 10 to 13 in the multicast PUCCH resource overlap with unicast uplink resource 3, and therefore needs to switch the second reporting mode to the first reporting mode.

[0116] In another example, symbols occupied by unicast uplink resource 4 are symbols 0 to 8 (resource 4-1) and symbols 12 and 13 (resource 4-2). Symbols 0 to 8 are used to transmit PUSCH 1, and symbols 12 and 13 are used to transmit PUSCH 2. The terminal device may determine, based on Implementation 1, Implementation 2, or Implementation 4, that the resource set does not overlap with resource 4-2 in the unicast uplink resources but overlaps with resource 4-1 in the unicast uplink resources 4, and thus needs to switch the second reporting mode to the first reporting mode. The terminal device may determine, based on Implementation 3, that the resource set overlaps with resource 4-1 in unicast uplink resources 4 and overlaps with resource 4-2 in the unicast uplink resources 4, and thus needs to switch the second reporting mode to the first reporting mode.

[0117] Scenario 5: A cell is configured for a terminal device, and the carriers configured for the cell include a NUL carrier and a SUL carrier, and the cell includes two different subcarrier spacings, for example, the subcarrier spacing corresponding to the SUL carrier is 15 kHz, and the subcarrier spacing corresponding to the NUL carrier is 30 kHz.

[0118] For example, Figure 9 is a fourth diagram of candidate multicast PUCCH resources. The difference between Figure 9 and Figure 8 is that in Figure 9, the carriers configured for a cell include a NUL carrier and an SUL carrier. For the terminal device to determine whether the candidate multicast PUCCH resources overlap with the unicast uplink resources in the scenario shown in Figure 9, please refer to the relevant content in Figure 8. The details will not be described again here.

[0119] Scenario 6: Two cells are configured for a terminal device, and the carriers of the two cells are both null carriers, and the subcarrier spacing of the two cells is different. For example, the subcarrier spacing of one of the cells is 15 kHz, and the subcarrier spacing of the other cell is 30 kHz.

[0120] For example, Figure 10 is a fifth diagram of candidate multicast PUCCH resources. Figure 10 uses an example in which the subcarrier spacing of two cells is 15 kHz and 30 kHz, respectively. The subcarrier spacing corresponding to the multicast PUCCH resource is 15 kHz. The subcarrier spacing corresponding to the unicast uplink resource is 30 kHz. Figure 10 uses m=2 as an example. Specifically, there are two TBs for HARQ-ACK information, and there are three multicast PUCCH resources. The two TBs in Figure 10 are TB 0 and TB 1. The three multicast PUCCH resources are PUCCH resource 0 to PUCCH resource 2. A terminal device transmits a multicast PUCCH in slot n1, transmits PUSCH 1 in slot n2, and transmits a PUSCH in slot n2+1. The symbols occupied by PUCCH resource 0 are symbols 5 to 8, the symbol occupied by PUCCH resource 1 is symbol 13, and the symbol occupied by PUCCH resource 2 is symbol 6.

[0121] It can be seen from implementation 1 that the time domain resources corresponding to the candidate multicast PUCCH resources are symbol 5 to symbol 8 and symbol 13. It can be seen from implementation 2 that the time domain resources corresponding to the candidate multicast PUCCH resources are symbol 5 to symbol 13. It can be seen from implementation 3 that the time domain resources corresponding to the candidate multicast PUCCH resources are symbol 0 to symbol 13. Assume that a network device configures or indicates that the start symbol of PUCCH resource 0 to PUCCH resource 2 is the same and the end symbol of PUCCH resource 0 to PUCCH resource 2 is the same. As shown in Figure 10, if the start symbol of PUCCH resource 0 to PUCCH resource 2 is symbol 13 and the end symbol of PUCCH resource 0 to PUCCH resource 2 is symbol 13, it can be seen from implementation 4 that the time domain resource corresponding to the candidate multicast PUCCH resource is symbol 13.

[0122] For example, the symbols occupied by unicast uplink resource 1 are symbol 0 to symbol 9 in slot n2. Based on Implementation 1, Implementation 2, or Implementation 4, the terminal device can determine that the resource set does not overlap with unicast uplink resource 1, and therefore does not need to switch the second reporting mode to the first reporting mode. Based on Implementation 3, the terminal device can determine that the resource set overlaps with unicast uplink resource 1, i.e., overlap occurs on symbol 0 and symbol 1. In this case, the terminal device needs to switch the second reporting mode to the first reporting mode.

[0123] In another example, the symbols occupied by unicast uplink resource 2 are symbols 0 to 10 in slot n2. The terminal device can determine that the resource set overlaps with unicast uplink resource 2 based on Implementation 1, Implementation 2, and Implementation 3, and therefore needs to switch the second reporting mode to the first reporting mode. The terminal device can determine that the resource set does not overlap with unicast uplink resource 2 based on Implementation 4, and therefore does not need to switch the second reporting mode to the first reporting mode.

[0124] In another example, the symbols occupied by unicast uplink resource 3 are symbol 4 to symbol 11 in slot n2+1. Based on Implementation 1 or Implementation 4, the terminal device can determine that the resource set does not overlap with unicast uplink resource 3, and therefore does not need to switch the second reporting mode to the first reporting mode. Based on Implementation 2 or Implementation 3, the terminal device can determine that the multicast PUCCH resource overlaps with unicast uplink resource 3, and therefore needs to switch the second reporting mode to the first reporting mode.

[0125] In another example, symbols occupied by unicast uplink resource 4 are symbols 0 to 8 (resource 4-1) in slot n2 and symbols 12 and 13 (resource 4-2) in slot n2+1. Based on Implementation 1, the terminal device may determine that the resource set does not overlap with resource 4-2 in the unicast uplink resources but overlaps with resource 4-1 in the unicast uplink resources 4, and thus needs to switch the second reporting mode to the first reporting mode. Based on Implementation 2 or Implementation 3, the terminal device may determine that the resource set overlaps with both resource 4-1 and resource 4-2 in the unicast uplink resources 4, and thus needs to switch the second reporting mode to the first reporting mode. Based on Implementation 4, the terminal device may determine that the resource set does not overlap with unicast uplink resource 4, and thus needs to switch the second reporting mode to the first reporting mode.

[0126] Scenario 7: One cell is configured for a terminal device, and the carriers of the cell include a NUL carrier and a SUL carrier, and the subcarrier spacing of these two carriers is different: the subcarrier spacing corresponding to the SUL carrier is 15 kHz, and the subcarrier spacing corresponding to the NUL carrier is 30 kHz.

[0127] For example, Figure 11 is a seventh diagram of candidate multicast PUCCH resources. The difference between Figure 11 and Figure 10 is that in Figure 11, the carrier configured for the cell is a NUL carrier, and the carrier configured for other cells is an SUL carrier. For the terminal device to determine whether the candidate multicast PUCCH resources overlap with the unicast uplink resources in the scenario shown in Figure 11, please refer to the relevant content in Figure 10. The details will not be described again here.

[0128]

[0047] The above describes four implementation forms of candidate multicast PUCCH resources by using seven scenarios as examples. However, this embodiment of the application is not limited to these four implementation forms. For example, the candidate multicast PUCCH resources may include more symbols than those corresponding to Implementation Form 1. For example, as shown in Figure 5, the symbols corresponding to the candidate multicast PUCCH resources in the time domain may be symbol 0 to symbol 4, symbol 5, and symbol 7 to symbol 11, or the symbols corresponding to the candidate multicast PUCCH resources in the time domain may be symbol 0 to symbol 4, symbol 6, and symbol 7 to symbol 11.

[0129] S404: The network device sends indication information to the terminal device, and correspondingly, the terminal device receives the indication information sent by the network device.

[0130] The indication information may indicate how the terminal device determines that the resource set overlaps with the unicast uplink resources. It may be understood that the above four implementations may be pre-configured or pre-defined, and the network device may use the indication information to instruct the terminal device to determine whether the candidate multicast PUCCH resources overlap with the unicast uplink resources in one of the four implementations. The indication information may be carried in one or more of RRC signaling, MAC CE, or DCI.

[0131] Alternatively, in this embodiment of the present application, one of four implementations may be used to predefine whether a candidate multicast PUCCH resource overlaps with a unicast uplink resource. 404 is not a required step, but an optional step, and is indicated by a dashed line in Figure 4. If S404 is performed, S404 is performed before S403.

[0132] In an embodiment of this application, for a case where two or more TBs are used by a terminal device to feed back HARQ-ACK information, a method is provided for determining whether a multicast PUCCH resource overlaps with a unicast PUCCH resource or a unicast PUSCH resource having the same priority as that of the multicast PUCCH resource in the time domain. Even if the terminal device does not obtain the decoding result of the multicast PDSCH TB, it can still determine whether a multicast PUCCH resource overlaps with a unicast PUCCH resource or a unicast PUSCH resource having the same priority as that of the multicast PUCCH resource in the time domain, and can determine whether to switch the second reporting mode to the first reporting mode.

[0133] In the above-described embodiments provided in this application, the methods provided in the embodiments of this application are described separately from the perspective of interactions between terminal devices and network devices. To implement the functions in the methods provided in the above-described embodiments of this application, the terminal devices and network devices may include hardware configurations and / or software modules, and the above-described functions are implemented in the form of hardware configurations, software modules, or a combination of hardware configurations and software modules. Whether the functions in the above-described functions are performed using a hardware configuration, a software module, or a combination of a hardware configuration and a software module depends on the specific application and design constraints of the technical solution.

[0134] An embodiment of the present application further provides a communication device. Hereinafter, a communication device configured to implement the above-mentioned method in an embodiment of the present application will be described with reference to the accompanying drawings.

[0135] 12 is a block diagram of a communication device 1200 according to an embodiment of the present application. The communication device 1200 may include a processing module 1210 and a transceiver module 1220. Optionally, the communication device 1200 may further include a storage unit. The storage unit may be configured to store instructions (codes or programs) and / or data. The processing module 1210 and the transceiver module 1220 may be coupled to the storage unit. For example, the processing module 1210 may read the instructions (codes or programs) and / or data in the storage unit to perform a corresponding method. The above-mentioned modules may be independently located or may be partially or fully integrated.

[0136] In some possible implementations, the communication device 1200 can correspondingly implement the behavior and functions of the terminal device in the above-described method embodiments. The communication device 1200 may be a terminal device, a component (e.g., a chip or circuit) used in a terminal device, a chip or group of chips within a terminal device, or a part of a chip configured to perform related method functions. For example, the communication device 1200 may perform steps such as S401 to S403 in FIG. 4.

[0137] For example, the transceiver module 1220 is configured to receive first configuration information transmitted by a network device, the first configuration information indicating a second reporting mode, the second reporting mode indicating feedback of HARQ-ACK information based on NACK-only. The transceiver module is further configured to transmit HARQ-ACK information for a multicast service to the network device in the first reporting mode when the processing module 1210 determines that the resource set overlaps with unicast uplink resources. The first reporting mode indicates feedback of HARQ-ACK information based on ACK / NACK. The second reporting mode indicates feedback of HARQ-ACK information based on NACK-only. The resource set includes a plurality of multicast PUCCH resources, and the unicast uplink resources include unicast PUCCH resources and / or unicast PUSCH resources. The HARQ-ACK information includes an ACK value or a NACK value, and the HARQ-ACK information corresponding to the first reporting mode may include either an ACK value or a NACK value. The HARQ-ACK information corresponding to the second reporting mode includes a NACK value and does not include an ACK value.

[0138] In one optional implementation, the resource set is m - 1 PUCCH resource, where m is the number of transport blocks TB used by the communication device 1200 to feed back HARQ-ACK information, and m is an integer equal to or greater than 1.

[0139] In one optional implementation, the processing module 1210 is specifically configured to determine a candidate multicast PUCCH resource from the resource set, and determine that the resource set overlaps with the unicast uplink resource when the candidate multicast PUCCH resource satisfies a first condition, where the first condition includes that the time-domain resource corresponding to the candidate multicast PUCCH resource includes a set of time-domain symbols respectively occupied by resources in the resource set.

[0140] In one optional implementation, the time domain resources corresponding to the candidate multicast PUCCH resources including a set of time domain symbols each occupied by a resource in a resource set include one of the following, namely: the time domain resources corresponding to the candidate multicast PUCCH resources are a set of time domain symbols each occupied by a resource in a resource set; the time domain resources corresponding to the candidate multicast PUCCH resources are a set of a first starting symbol occupied by the resource set, a first ending symbol occupied by the resource set, and symbols between the first starting symbol and the first ending symbol; the time domain resources corresponding to the candidate multicast PUCCH resources are a set of all symbols included in a slot in which the resource set is located; and the time domain resources corresponding to the candidate multicast PUCCH resources are a set of a first symbol, a second symbol, and symbols between the first symbol and the second symbol, where the first symbol is the starting symbol of the resource set and the second symbol is the ending symbol of the resource set, and the starting symbol of all PUCCH resources in the resource set is the same, and the ending symbol of all PUCCH resources in the resource set is the same.

[0141] In one optional implementation, the first starting symbol is the symbol with the earliest starting time among the time domain symbols occupied by the resources in the resource set, and the first ending symbol is the symbol with the latest ending time among the time domain symbols occupied by the resources in the resource set.

[0142] In one optional implementation, the resource set overlapping with unicast uplink resources includes the resource set overlapping with unicast uplink resources that have the same priority as the resource set.

[0143] In one optional implementation, the transceiver module 1220 is further configured to receive indication information from the network device, the indication information indicating how the communications apparatus 1200 determines that the resource set overlaps with the unicast uplink resources.

[0144] In one optional implementation, the transceiver module 1220 is further configured to receive second configuration information from the network device, the second configuration information indicating a multicast PUCCH resource set, the resource set belonging to the multicast PUCCH resource set.

[0145] In one optional implementation, the resource set and the unicast PUCCH resource belong to the same PUCCH resource set.

[0146] For details, please refer to the relevant content in the above embodiment in Figure 4. The details will not be described again here.

[0147] In some other possible implementations, the communication device 1200 can correspondingly implement the behavior and functionality of the network device in the above-described method embodiments. The communication device 1200 may be a network device, a component (e.g., a chip or circuit) used in a network device, a chip or chipset within a network device, or a part of a chip configured to perform the related method functions. For example, the communication device 1200 may perform steps such as S401 to S404 of FIG. 4.

[0148] For example, the transceiver module 1220 is configured to transmit first configuration information to a terminal device, the first configuration information indicating a second reporting mode, the second reporting mode indicating feedback of HARQ-ACK information based on NACK-only. When the processing module 1210 determines that the resource set overlaps with unicast uplink resources, the transceiver module 1220 is further configured to receive HARQ-ACK information transmitted by the terminal device for the multicast service in the first reporting mode. The first reporting mode indicates feedback of HARQ-ACK information based on ACK / NACK. The second reporting mode indicates feedback of HARQ-ACK information based on NACK-only. The resource set includes a plurality of multicast PUCCH resources, and the unicast uplink resources include unicast PUCCH resources and / or unicast PUSCH resources. The HARQ-ACK information includes an ACK value or a NACK value, and the HARQ-ACK information corresponding to the first reporting mode may include either an ACK value or a NACK value. The HARQ-ACK information corresponding to the second reporting mode includes a NACK value and does not include an ACK value.

[0149] In one optional implementation, the resource set is m - 1 PUCCH resource, where m is the number of transport blocks TB used by the communication device 1200 to feed back HARQ-ACK information, and m is an integer equal to or greater than 1.

[0150] In one optional implementation, the processing module 1210 is specifically configured to determine a candidate multicast PUCCH resource from the resource set, and determine that the resource set overlaps with the unicast uplink resource when the candidate multicast PUCCH resource satisfies a first condition, where the first condition includes that the time-domain resource corresponding to the candidate multicast PUCCH resource includes a set of time-domain symbols respectively occupied by resources in the resource set.

[0151] In one optional implementation, the time domain resources corresponding to the candidate multicast PUCCH resources including a set of time domain symbols each occupied by a resource in a resource set include one of the following, namely: the time domain resources corresponding to the candidate multicast PUCCH resources are a set of time domain symbols each occupied by a resource in a resource set; the time domain resources corresponding to the candidate multicast PUCCH resources are a set of a first starting symbol occupied by the resource set, a first ending symbol occupied by the resource set, and symbols between the first starting symbol and the first ending symbol; the time domain resources corresponding to the candidate multicast PUCCH resources are a set of all symbols included in a slot in which the resource set is located; and the time domain resources corresponding to the candidate multicast PUCCH resources are a set of a first symbol, a second symbol, and symbols between the first symbol and the second symbol, where the first symbol is the starting symbol of the resource set and the second symbol is the ending symbol of the resource set, and the starting symbol of all PUCCH resources in the resource set is the same, and the ending symbol of all PUCCH resources in the resource set is the same.

[0152] In one optional implementation, the first starting symbol is the symbol with the earliest starting time among the time domain symbols occupied by the resources in the resource set, and the first ending symbol is the symbol with the latest ending time among the time domain symbols occupied by the resources in the resource set.

[0153] In one optional implementation, the resource set overlapping with unicast uplink resources includes the resource set overlapping with unicast uplink resources that have the same priority as the resource set.

[0154] In one optional implementation, the transceiver module 1220 is further configured to transmit indication information to the terminal device, the indication information indicating how the terminal device determines that the resource set overlaps with the unicast uplink resources.

[0155] In one optional implementation, the transceiver module 1220 is further configured to send second configuration information to the terminal device, where the second configuration information indicates a multicast PUCCH resource set, and the resource set belongs to the multicast PUCCH resource set.

[0156] In one optional implementation, the resource set and the unicast PUCCH resource belong to the same PUCCH resource set.

[0157] For details, please refer to the relevant content in the above embodiment in Figure 4. The details will not be described again here.

[0158] It should be understood that the processing module 1210 in this embodiment of the application can be implemented by a processor or processor-related circuit components, and the transceiver module 1220 can be implemented by a transceiver, transceiver-related circuit components, or a communication interface.

[0159] FIG. 13 is a block diagram of a communication device 1300 according to an embodiment of this application. The communication device 1300 may be a terminal device and may implement the functions of the terminal device in the methods provided in the embodiments of this application. Alternatively, the communication device 1300 may be a device capable of supporting the terminal device in performing corresponding functions in the methods provided in the embodiments of this application. The communication device 1300 may be a chip system. In this embodiment of this application, the chip system may include a chip, or may include a chip and other discrete components. For specific functions, please refer to the description of the method embodiments above. Alternatively, the communication device 1300 may be a network device and may implement the functions of the network device in the methods provided in the embodiments of this application. Alternatively, the communication device 1300 may be a device capable of supporting the network device in performing corresponding functions in the methods provided in the embodiments of this application. The communication device 1300 may be a chip system. In this embodiment of this application, the chip system may include a chip, or may include a chip and other discrete components. For specific functions, please refer to the description of the method embodiments above.

[0160] The communication device 1300 includes one or more processors 1301 that may be configured to implement or support the communication device 1300 in performing the functions of a terminal device in the methods provided in the embodiments of this application. For details, please refer to the detailed description in the method examples. The details will not be described again here. The one or more processors 1301 may instead be configured to implement or support the communication device 1300 in performing the functions of a network device in the methods provided in the embodiments of this application. For details, please refer to the detailed description in the method examples. The details will not be described again here. The processor 1301 may also be referred to as a processing unit or a processing module and may implement specific control functions. The processor 1301 may be a general-purpose processor or a special-purpose processor, etc. For example, the processor may include a central processing unit, an application processor, a modem processor, a graphics processing unit, an image signal processor, a digital signal processor, a video codec processor, a controller, a memory, and / or a neural network processor. The central processing unit may be configured to control the communication device 1300, execute software programs, and / or process data. The different processors may be separate devices or may be integrated into one or more processors, for example integrated into one or more application specific integrated circuits.

[0161] Optionally, the communication device 1300 includes one or more memories 1302 configured to store instructions 1304. The instructions, when executed on the processor 1301, may enable the communication device 1300 to perform the methods described in the above-described method embodiments. The memory 1302 and the processor 1301 may be located separately or integrated together, and the memory 1302 may be considered to be coupled to the processor 1301. The coupling in this embodiment of the present application may be an indirect coupling or communication connection between devices, units, or modules in an electrical, mechanical, or other form, used for information exchange between the devices, units, or modules. The processor 1301 may cooperate with the memory 1302. At least one of the at least one memory may be included in the processor. Note that the memory 1302 is not required and is therefore depicted using dashed lines in FIG. 13 .

[0162] Optionally, the memory 1302 may further store data. The processor and the memory may be located separately or integrated together. In this embodiment of the application, the memory 1302 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid state drive (SSD), or a volatile memory, such as a random access memory (RAM). The memory is, but is not limited to, any other medium capable of carrying or storing expected program code in the form of instructions or data structures and capable of being accessed by a computer. The memory in the embodiment of the application may instead be a circuit or any other device capable of implementing a storage function and configured to store program instructions and / or data.

[0163] Optionally, the communication device 1300 may include instructions 1303 (which may also be referred to as code or program). The instructions 1303, when executed on the processor, may enable the communication device 1300 to perform the methods described in the above embodiments. The processor 1301 may also store data.

[0164] Optionally, the communications device 1300 may further include a transceiver 1305 and an antenna 1306. The transceiver 1305, which may also be referred to as a transceiver unit, transceiver module, transceiver machine, transceiver circuit, transceiver, or input / output interface, is configured to implement transceiver functionality of the communications device 1300 via the antenna 1306.

[0165] The processor 1301 and transceiver 1305 described in this application may be implemented on an integrated circuit (IC), an analog IC, a radio frequency identification (RFID) integrated circuit, a mixed signal IC, an ASIC, a printed circuit board (PCB), or an electronic device, etc. The communication apparatus described in this specification may be implemented by an independent device (e.g., an independent integrated circuit or a mobile phone) or may be part of a larger device (e.g., a module that can be embedded in another device). For details, please refer to the above description of the terminal device and the network device. The details will not be described again here.

[0166] In one possible implementation, the communication device 1300 can correspondingly implement the behavior and functions of the terminal device in the above-described method embodiments. The communication device 1300 may be a terminal device, a component (e.g., a chip or circuit) used in a terminal device, a chip or group of chips within a terminal device, or a part of a chip configured to perform the related method functions. For example, the communication device 1300 may perform the steps of FIG. 4.

[0167] For example, the transceiver 1305 is configured to transmit first configuration information to the terminal device, the first configuration information indicating a second reporting mode, where the second reporting mode indicates feeding back HARQ-ACK information based on NACK-only. When the processor 1301 determines that the resource set overlaps with unicast uplink resources, the transceiver 1305 is further configured to receive HARQ-ACK information transmitted by the terminal device for the multicast service in the first reporting mode. The first reporting mode indicates feeding back multicast HARQ-ACK information based on ACK / NACK. The resource set includes a plurality of multicast PUCCH resources, and the unicast uplink resources include unicast PUCCH resources and / or unicast PUSCH resources. The HARQ-ACK information includes an ACK value or a NACK value, and the HARQ-ACK information corresponding to the first reporting mode may include either an ACK value or a NACK value. The HARQ-ACK information corresponding to the second reporting mode includes a NACK value but does not include an ACK value.

[0168] In one optional implementation, the transceiver 1305 is further configured to receive indication information transmitted by the network device, the indication information indicating how the communications apparatus 1300 determines that the resource set overlaps with the unicast uplink resources.

[0169] In one optional implementation, the transceiver 1305 is further configured to receive second configuration information transmitted by the network device, the second configuration information indicating a multicast PUCCH resource set, and the resource set belonging to the multicast PUCCH resource set.

[0170] For details, please refer to the relevant content in the above embodiment in Figure 4. The details will not be described again here.

[0171] In some other possible implementations, the communication device 1300 can correspondingly implement the behavior and functionality of the network device in the above-described method embodiments. The communication device 1300 may be a network device, a component (e.g., a chip or circuit) used in a network device, a chip or chipset within a network device, or part of a chip configured to perform the associated method functions. For example, the communication device 1300 may perform the steps of FIG. 4.

[0172] For example, the transceiver 1305 is configured to transmit first configuration information to the terminal device, the first configuration information indicating a second reporting mode, where the second reporting mode indicates feeding back HARQ-ACK information based on NACK-only. When the processor 1301 determines that the resource set overlaps with unicast uplink resources, the transceiver 1305 is further configured to receive HARQ-ACK information transmitted by the terminal device for the multicast service in the first reporting mode. The first reporting mode indicates feeding back multicast HARQ-ACK information based on ACK / NACK. The resource set includes a plurality of multicast PUCCH resources, and the unicast uplink resources include unicast PUCCH resources and / or unicast PUSCH resources. The HARQ-ACK information includes an ACK value or a NACK value, and the HARQ-ACK information corresponding to the first reporting mode may include either an ACK value or a NACK value. The HARQ-ACK information corresponding to the second reporting mode includes a NACK value but does not include an ACK value.

[0173] In one optional implementation, the transceiver 1305 is further configured to transmit indication information to the terminal device, the indication information indicating how the terminal device determines that the resource set overlaps with the unicast uplink resources.

[0174] In one optional implementation, the transceiver 1305 is further configured to send second configuration information to the terminal device, where the second configuration information indicates a multicast PUCCH resource set, and the resource set belongs to the multicast PUCCH resource set.

[0175] For details, please refer to the relevant content in the above embodiment in Figure 4. The details will not be described again here.

[0176] Optionally, communication device 1300 may further include one or more of the following components: a wireless communication module, an audio module, an external memory interface, an internal memory, a universal serial bus (USB) interface, a power management module, an antenna, a speaker, a microphone, an input / output module, a sensor module, a motor, a camera, or a display. It may be understood that in some embodiments, communication device 1300 may include more or fewer components, some components may be integrated, or some components may be separated. These components may be implemented by hardware, software, or a combination of software and hardware.

[0177] It should be noted that the communication device in the above-described embodiments may be a terminal device (or a network device), a circuit, a chip used in a terminal device (or a network device), or any other combined device or component having the functionality of a terminal (or a network device). When the communication device is a terminal device (or a network device), the transceiver module may be a transceiver and may include an antenna and a radio frequency circuit, and the processing module may be a processor such as a central processing unit (CPU). When the communication device is a component having the functionality of a terminal device (or a network device), the transceiver module may be a radio frequency unit, and the processing module may be a processor. When the communication device is a chip system, the communication device may be a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system on chip (SoC), a CPU, a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chip. The processing module may be the processor of the chip system. The transceiver module or communication interface may be an input / output interface or interface circuit of the chip system. For example, the interface circuit may be a code / data read / write interface circuit. The interface circuit may be configured to receive code instructions (which may be stored in a memory and read directly from the memory or read from the memory via another device) and transmit the code instructions to a processor.The processor may be configured to execute the code instructions to perform the method in the above-mentioned method embodiments. In another example, the interface circuit may instead be a signal transmission interface circuit between the communication processor and the transceiver machine.

[0178] When the communication device is a chip-type device or circuit, the device may include a transceiver unit and a processing unit. The transceiver unit may be an input / output circuit and / or a communication interface. The processing unit may be an integrated processor, a microprocessor, or an integrated circuit.

[0179] An embodiment of this application further provides a communication system. Specifically, the communication system includes at least one terminal device and at least one network device. For example, the communication system includes a terminal device and a network device configured to implement the relevant functions in FIG. 4. For details, please refer to the relevant descriptions in the above method embodiments. The details will not be described again here.

[0180] An embodiment of the present application further provides a computer-readable storage medium containing instructions that, when executed on a computer, enable the computer to perform the method performed by the terminal device in Figure 4. Alternatively, when executed on a computer, the instructions enable the computer to perform the method performed by the network device in Figure 4.

[0181] An embodiment of the present application further provides a computer program product including instructions that, when executed on a computer, enable the computer to perform the method performed by the terminal device in Figure 4. Alternatively, the instructions, when executed on a computer, enable the computer to perform the method performed by the network device in Figure 4.

[0182] One embodiment of the present application provides a chip system, which includes a processor and may further include a memory, and is configured to implement the functions of the terminal device in the above-mentioned method, or the functions of the network device in the above-mentioned method, and may include a chip, or may include a chip and another discrete component.

[0183] It should be understood that the sequence numbers of the above processes do not imply the execution order in various embodiments of this application, and the execution order of the processes should be determined according to the functions and internal logic of the processes, and should not be construed as a limitation on the implementation process of the embodiments of this application.

[0184] Those skilled in the art can recognize that, in combination with the illustrative logical blocks described in the embodiments disclosed in this specification, steps can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether a function is performed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to go beyond the scope of this application.

[0185] It can be clearly understood by those skilled in the art that for the sake of convenience and conciseness, for the detailed operation processes of the above-mentioned systems, devices and units, please refer to the corresponding processes in the above-mentioned method embodiments, and the details will not be described again here.

[0186] In some embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the described device embodiments are merely examples. For example, the division into units is merely a logical division of function, and other divisions may be used in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented. Furthermore, the shown or described mutual couplings or direct couplings or communication connections may be implemented by using some interface. Indirect couplings or communication connections between devices or units may be implemented in electronic, mechanical, or other forms.

[0187] The units described as separate parts may or may not be physically separate, and the parts shown as units may or may not be physical units, and may be located in one location or distributed over multiple network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solution of the embodiment.

[0188] When functions are implemented in the form of a software functional unit and sold or used as an independent product, the functions may be stored in a computer-readable storage medium. Based on this understanding, a part that essentially contributes to the technical solution of this application or a part of the technical solution may be embodied in the form of a software product. A computer software product is stored in a storage medium and includes some instructions that enable a computer device (which may be a personal computer, a server, a network device, etc.) to execute all or some of the steps of the method in the embodiments of this application. The above-mentioned storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a RAM, a magnetic disk, or an optical disk.

[0189] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application, and this application intends to cover such modifications and variations to this application as long as they fall within the scope of protection defined by the following claims of this application and their equivalents.

Claims

1. A multicast service feedback method, comprising: receiving, by a terminal device, first configuration information from a network device, the first configuration information indicating a second reporting mode, the second reporting mode indicating feedback of Hybrid Automatic Repeat Request (HARQ-ACK) information based on negative acknowledgement only (NACK-only); When it is determined that a resource set overlaps with unicast uplink resources, transmitting HARQ-ACK information for the multicast service to the network device in a first reporting mode by the terminal device, the first reporting mode indicating feeding back HARQ-ACK information based on an acknowledgment (ACK) / negative acknowledgement (NACK), the resource set including a plurality of multicast Physical Uplink Control Channel (PUCCH) resources, and the unicast uplink resources including unicast PUCCH resources and / or unicast Physical Uplink Shared Channel (PUSCH) resources; and the HARQ-ACK information has an ACK value or a NACK value; determining, by the terminal device, that a resource set overlaps with unicast uplink resources, determining, by the terminal device, candidate multicast PUCCH resources from the resource set; determining, by the terminal device, that the resource set overlaps with the unicast uplink resource when the candidate multicast PUCCH resource satisfies a first condition, the first condition comprising: a time domain resource corresponding to the candidate multicast PUCCH resource including a set of time domain symbols respectively occupied by PUCCH resources in the resource set; the time domain resources corresponding to the candidate multicast PUCCH resources are a set of a start symbol of the resource set, an end symbol of the resource set, and symbols between the start symbol of the resource set and the end symbol of the resource set, where the start symbols of all PUCCH resources in the resource set are the same, and the end symbols of all PUCCH resources in the resource set are the same; method.

2. The resource set is 2 ｍ 2. The method of claim 1, wherein the PUCCH resource is -1, m is the number of transport blocks (TBs) used by the terminal device to feed back the HARQ-ACK information, and m is an integer greater than or equal to 2.

3. The method of claim 1 , wherein a resource set overlaps with unicast uplink resources comprising the resource set overlapping with the unicast uplink resources having the same priority as a priority of the resource set.

4. The method further comprises: receiving, by the terminal device, indication information from the network device, the indication information indicating how the terminal device determines that the resource set overlaps with the unicast uplink resources; 2. The method of claim 1, comprising:

5. The method further comprises: receiving, by the terminal device, second configuration information from the network device, the second configuration information indicating a multicast PUCCH resource set, the resource set belonging to the multicast PUCCH resource set; 2. The method of claim 1, comprising:

6. The method of claim 1 , wherein the resource set and the unicast PUCCH resource belong to the same PUCCH resource set.

7. A multicast service feedback method, comprising: sending, by a network device, first configuration information to a terminal device, the first configuration information indicating a second reporting mode, the second reporting mode indicating feedback of Hybrid Automatic Repeat Request (HARQ-ACK) information based on negative acknowledgement only (NACK-only); receiving, by the network device, HARQ-ACK information transmitted by the terminal device for a multicast service in a first reporting mode when it is determined that a resource set overlaps with unicast uplink resources, the first reporting mode indicating feeding back HARQ-ACK information based on an acknowledgment (ACK) / negative acknowledgement (NACK), the resource set including a plurality of multicast Physical Uplink Control Channel (PUCCH) resources, and the unicast uplink resources including unicast PUCCH resources and / or unicast Physical Uplink Shared Channel (PUSCH) resources; and the HARQ-ACK information has an ACK value or a NACK value; determining, by the network device, that a resource set overlaps with unicast uplink resources, determining, by the network device, candidate multicast PUCCH resources from the resource set; determining, by the network device, that the resource set overlaps with the unicast uplink resource when the candidate multicast PUCCH resource satisfies a first condition, the first condition comprising: a time domain resource corresponding to the candidate multicast PUCCH resource including a set of time domain symbols respectively occupied by PUCCH resources in the resource set; the time domain resources corresponding to the candidate multicast PUCCH resources are a set of a start symbol of the resource set, an end symbol of the resource set, and symbols between the start symbol of the resource set and the end symbol of the resource set, where the start symbols of all PUCCH resources in the resource set are the same, and the end symbols of all PUCCH resources in the resource set are the same; method.

8. The resource set is 2 ｍ 8. The method of claim 7, wherein the PUCCH resource is -1, m is the number of transport blocks (TBs) used by the terminal device to feed back the HARQ-ACK information, and m is an integer greater than or equal to 2.

9. The method of claim 7 , wherein a resource set overlaps with unicast uplink resources comprising the resource set overlapping with the unicast uplink resources having the same priority as a priority of the resource set.

10. The method further comprises: sending, by the network device, indication information to the terminal device, the indication information indicating how the terminal device should determine that the resource set overlaps with the unicast uplink resource; 8. The method of claim 7, comprising:

11. The method further comprises: sending, by the network device, second configuration information to the terminal device, the second configuration information indicating a multicast PUCCH resource set, the resource set belonging to the multicast PUCCH resource set; 8. The method of claim 7, comprising:

12. The method of claim 7 , wherein the resource set and the unicast PUCCH resource belong to the same PUCCH resource set.

13. 1. A communication device having a transceiver module and a processing module, the transceiver module is configured to receive first configuration information transmitted by a network device, the first configuration information indicating a second reporting mode, the second reporting mode indicating feedback of hybrid automatic repeat request (HARQ-ACK) information based on negative acknowledgement only (NACK-only); The transceiver module is further configured to, when the processing module determines that a resource set overlaps with unicast uplink resources, transmit HARQ-ACK information for the multicast service to the network device in a first reporting mode, the first reporting mode indicating feeding back HARQ-ACK information based on an acknowledgement (ACK) / negative acknowledgement (NACK), the resource set including a plurality of multicast Physical Uplink Control Channel (PUCCH) resources, and the unicast uplink resources including unicast PUCCH resources and / or unicast Physical Uplink Shared Channel (PUSCH) resources; the HARQ-ACK information has an ACK value or a NACK value; The processing module specifically includes: determining candidate multicast PUCCH resources from the resource set; determining that the resource set overlaps with the unicast uplink resources when the candidate multicast PUCCH resources satisfy a first condition, the first condition comprising: time domain resources corresponding to the candidate multicast PUCCH resources including a set of time domain symbols respectively occupied by PUCCH resources in the resource set; It is configured as follows: the time domain resources corresponding to the candidate multicast PUCCH resources are a set of a start symbol of the resource set, an end symbol of the resource set, and symbols between the start symbol of the resource set and the end symbol of the resource set, where the start symbols of all PUCCH resources in the resource set are the same, and the end symbols of all PUCCH resources in the resource set are the same; Communication equipment.

14. The resource set is 2 ｍ -1 PUCCH resource, m is the number of transport blocks (TBs) used by the communication device to feed back the HARQ-ACK information, and m is an integer greater than or equal to 2.

15. 14. The communications device of claim 13, wherein a resource set overlapping with unicast uplink resources comprises the resource set overlapping with the unicast uplink resources having the same priority as a priority of the resource set.

16. The transceiver module further comprises: receiving indication information from the network device, the indication information indicating a manner in which the processing module determines that the resource set overlaps with the unicast uplink resource; The communication device according to claim 13, configured to:

17. The transceiver module further comprises: receiving second configuration information from the network device, the second configuration information indicating a multicast PUCCH resource set, the resource set belonging to the multicast PUCCH resource set; The communication device according to claim 13, configured to:

18. The communications device of claim 13 , wherein the resource set and the unicast PUCCH resource belong to the same PUCCH resource set.

19. 1. A communication device having a transceiver module and a processing module, the transceiver module is configured to send first configuration information to a terminal device, the first configuration information indicating a second reporting mode, the second reporting mode indicating feedback of hybrid automatic repeat request (HARQ-ACK) information based on negative acknowledgement only (NACK-only); The transceiver module is further configured to receive HARQ-ACK information transmitted by the terminal device for a multicast service in a first reporting mode when the processing module determines that a resource set overlaps with unicast uplink resources, the first reporting mode indicating feeding back HARQ-ACK information based on an acknowledgement (ACK) / negative acknowledgement (NACK), the resource set including a plurality of multicast Physical Uplink Control Channel (PUCCH) resources, and the unicast uplink resources including unicast PUCCH resources and / or unicast Physical Uplink Shared Channel (PUSCH) resources; the HARQ-ACK information has an ACK value or a NACK value; The processing module further comprises: determining candidate multicast PUCCH resources from the resource set; determining that the resource set overlaps with the unicast uplink resources when the candidate multicast PUCCH resources satisfy a first condition, the first condition comprising: time domain resources corresponding to the candidate multicast PUCCH resources including a set of time domain symbols respectively occupied by PUCCH resources in the resource set; It is configured as follows: the time domain resources corresponding to the candidate multicast PUCCH resources are a set of a start symbol of the resource set, an end symbol of the resource set, and symbols between the start symbol of the resource set and the end symbol of the resource set, where the start symbols of all PUCCH resources in the resource set are the same, and the end symbols of all PUCCH resources in the resource set are the same; Communication equipment.

20. The resource set is 2 ｍ 20. The communication device of claim 19, wherein the communication device has -1 PUCCH resource, m is the number of transport blocks (TBs) used by the terminal device to feed back the HARQ-ACK information, and m is an integer greater than or equal to 2.

21. 20. The communications device of claim 19, wherein a resource set overlapping with unicast uplink resources comprises the resource set overlapping with the unicast uplink resources having the same priority as a priority of the resource set.

22. 20. The communications apparatus of claim 19, wherein the transceiver module is further configured to transmit indication information to the terminal device, the indication information indicating a manner in which the terminal device determines that the resource set overlaps with the unicast uplink resources.

23. The transceiver module further comprises: Send second configuration information to the terminal device, where the second configuration information indicates a multicast PUCCH resource set, and the resource set belongs to the multicast PUCCH resource set.

20. The communication device of claim 19, configured to:

24. The communications device of claim 19 , wherein the resource set and the unicast PUCCH resource belong to the same PUCCH resource set.

25. 10. A communications device having a processor and a communications interface, the communications interface configured to input and / or output information, and the processor configured to execute a computer program, such that the communications device performs a method according to any one of claims 1 to 6.

26. A communications device having a processor and a communications interface, wherein the communications interface is configured to input and / or output information, and the processor is configured to execute a computer program, such that the communications device performs a method according to any one of claims 7 to 12.

27. 10. A computer readable storage medium having stored thereon a computer program, which, when executed by a computer, enables the computer to carry out the method of any one of claims 1 to 6.

28. A computer-readable storage medium storing a computer program, which, when executed by a computer, enables the computer to perform a method according to any one of claims 7 to 12.

29. 7. A computer program product storing a computer program, which when executed by a computer enables the computer to carry out the method of any one of claims 1 to 6.

30. A computer program product storing a computer program, which, when executed by a computer, enables the computer to carry out a method according to any one of claims 7 to 12.

Images