A method and apparatus for transmitting uplink control information

Abstract

The application provides a transmission method and device of uplink control information. In the method, a terminal device acquires first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and second PUCCH configuration information corresponding to unicast data. When first hybrid automatic repeat request-acknowledgement (HARQ-ACK) information corresponding to one or more pieces of received multicast data and second HARQ-ACK information corresponding to one or more pieces of received unicast data belong to the same priority and need to be fed back in the same time unit, the PUCCH resource can be determined according to the first PUCCH configuration information or the second PUCCH configuration information, and then uplink control information including the first HARQ-ACK information and the second HARQ-ACK information is sent on the PUCCH resource. The application can effectively realize the feedback of the HARQ-ACK information of the multicast data and the unicast data.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method and apparatus for transmitting uplink control information. Background Technology

[0002] For unicast services, when multiple hybrid automatic repeat request-acknowledge (HARQ-ACK) messages of the same priority exist within the same time unit, the terminal device can combine these multiple HARQ-ACK messages of the same priority into a single HARQ-ACK codebook and feed back this codebook using the physical uplink control channel (PUCCH) configuration information corresponding to that priority HARQ-ACK message. When HARQ-ACK messages of different priorities exist within the same time unit, the terminal device will combine these messages of different priorities into their respective HARQ-ACK codebooks and feed back the corresponding HARQ-ACK codebooks according to the PUCCH configuration information corresponding to each of the different priorities. In other words, the number of priorities among the HARQ-ACK messages is bound to the number of HARQ-ACK codebooks and the number of PUCCH configuration information entries.

[0003] In communication systems such as 5G, a HARQ-ACK feedback mechanism is introduced into multicast services to improve data transmission efficiency. This requires network devices to configure PUCCH configuration information for multicast and unicast services separately for terminal devices. However, within the same time unit, if the HARQ-ACK information for multicast and unicast services has the same priority, the priority of the HARQ-ACK information no longer has the aforementioned binding relationship with the number of PUCCH configuration information, thus preventing the terminal device from feeding back HARQ-ACK information for both multicast and unicast services. Summary of the Invention

[0004] This application provides a method and apparatus for transmitting uplink control information, which can transmit at least one of the HARQ-ACK information corresponding to multicast data and the ARQ-ACK information corresponding to unicast data.

[0005] In a first aspect, embodiments of this application provide a method for transmitting uplink control information. In this method, a terminal device acquires first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and second PUCCH configuration information corresponding to unicast data; receives multiple data from a network device, the multiple data including one or more multicast data and one or more unicast data; first hybrid automatic repeat request-acknowledge (HARQ-ACK) information corresponding to one or more multicast data and second HARQ-ACK information corresponding to one or more unicast data belong to the same priority and need to be fed back within the same time unit; then, based on the first PUCCH configuration information or the second PUCCH configuration information, determines PUCCH resources; and sends uplink control information to the network device on the PUCCH resources; the uplink control information includes first HARQ-ACK information and second HARQ-ACK information.

[0006] As can be seen, in this embodiment of the application, when the first HARQ-ACK information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data have the same priority and need to be fed back in the same time unit, the terminal device feeds back the first HARQ-ACK information and the second HARQ-ACK information according to the PUCCH resources determined by the first PUCCH configuration information or the second PUCCH configuration information. This can effectively realize the HARQ-ACK feedback of the one or more multicast data and one or more unicast data, and avoid the terminal device being unable to transmit feedback information.

[0007] In one optional implementation, the terminal device determines the PUCCH resource based on either the first PUCCH configuration information or the second PUCCH configuration information. This includes: the terminal device determining the PUCCH resource based on the Physical Uplink Control Channel Resource Indication (PRI) in the last downlink control information (DCI) corresponding to one or more multicast data sets and the first PUCCH configuration information, wherein the PUCCH resource belongs to the set of PUCCH resources configured in the first PUCCH configuration information; or, the terminal device determining the PUCCH resource based on the Physical Uplink Control Channel Resource Indication (PRI) in the last downlink control information (DCI) corresponding to one or more unicast data sets and the second PUCCH configuration information, wherein the PUCCH resource belongs to the set of PUCCH resources configured in the second PUCCH configuration information. In other words, the PUCCH configuration information used by the terminal device to determine the PUCCH resource is either the first PUCCH configuration information or the second PUCCH configuration information.

[0008] In another optional implementation, the terminal device determines the PUCCH resource based on the first PUCCH configuration information or the second PUCCH configuration information, including: the terminal device determines the PUCCH resource based on the Physical Uplink Control Channel Resource Indicator (PRI) of the last downlink control information (DCI) corresponding to multiple data, and the PUCCH configuration information corresponding to the last DCI; the PUCCH resource belongs to the set of PUCCH resources configured in the first PUCCH configuration information, or belongs to the set of PUCCH resources configured in the second PUCCH configuration information.

[0009] As can be seen, the terminal device can flexibly determine the PUCCH resource based on the PUCCH configuration information corresponding to the last DCI of multiple data.

[0010] In another optional implementation, the terminal device determines the PUCCH resource based on the first PUCCH configuration information or the second PUCCH configuration information, including: the terminal device receiving first indication information from the network device; the first indication information instructing the terminal device to determine the PUCCH resource based on the first PUCCH configuration information or the second PUCCH configuration information; then, when the first indication information instructs the terminal device to determine the PUCCH resource based on the first PUCCH configuration information, the terminal device determines the PUCCH resource based on the Physical Uplink Control Channel Resource Indication (PRI) in the last downlink control information (DCI) corresponding to one or more multicast data and the first PUCCH configuration information; the PUCCH resource belongs to the set of PUCCH resources configured in the first PUCCH configuration information; or when the first indication information instructs the terminal device to determine the PUCCH resource based on the second PUCCH configuration information, the terminal device determines the PUCCH resource based on the Physical Uplink Control Channel Resource Indication (PRI) in the last downlink control information (DCI) corresponding to one or more unicast data and the second PUCCH configuration information; the PUCCH resource belongs to the set of PUCCH resources configured in the second PUCCH configuration information.

[0011] It is evident that the terminal device can select the PUCCH configuration information used when determining PUCCH resources based on the first instruction information sent by the network device.

[0012] In one optional implementation, when there is only one first PUCCH configuration information, the priority corresponding to the first PUCCH configuration information is high priority. That is, when there is only one PUCCH configuration information corresponding to multicast data, its corresponding PUCCH configuration information has a high priority, instead of the default low priority when there is only one PUCCH configuration information corresponding to unicast data.

[0013] In one alternative implementation, the priority corresponding to the first PUCCH configuration information is configured in bits within the DCI corresponding to one or more multicast data, or configured via a Radio Network Temporary Identifier (RNTI) scrambled with the DCI, or configured in Radio Resource Control (RRC) signaling. Therefore, the priority corresponding to the first PUCCH configuration information can be flexibly configured at the physical layer of the communication system.

[0014] In one optional implementation, the terminal device obtains the first physical uplink control channel (PUCCH) configuration information corresponding to the multicast data and the second PUCCH configuration information corresponding to the unicast data, including: the terminal device receiving the first PUCCH configuration information and the second PUCCH configuration information from the network device.

[0015] Secondly, this application also provides a method for transmitting uplink control information. In this method, a terminal device acquires first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and second PUCCH configuration information corresponding to unicast data; then, it receives multiple data from a network device, including one or more multicast data and one or more unicast data; the first hybrid automatic repeat request-acknowledgement (HARQ-ACK) information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data have the same priority and must be fed back within the same time unit; then, a first PUCCH resource is determined based on the first PUCCH configuration information, and a second PUCCH resource is determined based on the second PUCCH configuration information; finally, based on the first PUCCH resource and the second PUCCH resource, at least one of first uplink control information and second uplink control information is sent to the network device; the first uplink control information includes first HARQ-ACK information; the second uplink control information includes second HARQ-ACK information.

[0016] As can be seen, in this embodiment of the application, when the first hybrid automatic repeat request-acknowledgment (HARQ-ACK) information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data belong to the same priority and need to be fed back in the same time unit, the terminal device can feed back at least one of the first HARQ-ACK information and the second HARQ-ACK information according to the first PUCCH resource determined by the first PUCCH configuration information and the second PUCCH resource determined by the second PUCCH configuration information, so as to avoid the terminal device being unable to transmit feedback information.

[0017] In one optional implementation, the terminal device sends at least one of a first uplink control information and a second uplink control information to the network device based on a first PUCCH resource and a second PUCCH resource, including: when the first PUCCH resource and the second PUCCH resource do not overlap in the time domain, the terminal device sends the first uplink control information to the network device on the first PUCCH resource and sends the second uplink control information to the network device on the second PUCCH resource.

[0018] As can be seen, when the first PUCCH resource and the second PUCCH resource do not overlap in the time domain, the terminal device feeds back the first HARQ-ACK information and the second HARQ-ACK information on the first PUCCH resource and the second PUCCH resource respectively, realizing the HARQ-ACK feedback of the above-mentioned one or more multicast data and one or more unicast data.

[0019] In another optional implementation, the terminal device sends at least one of a first uplink control information and a second uplink control information to the network device based on the first PUCCH resource and the second PUCCH resource, including: when the first PUCCH resource and the second PUCCH resource overlap in the time domain, the terminal device sends the first uplink control information to the network device on the first PUCCH resource; or, sends the second uplink control information to the network device on the second PUCCH resource.

[0020] As can be seen, when the first PUCCH resource and the second PUCCH resource overlap in the time domain, the terminal device only feeds back one of the first HARQ-ACK information and the second HARQ-ACK information to the network device to ensure that at least one HARQ-ACK information is correctly fed back. That is, this implementation realizes HARQ-ACK feedback for one or more multicast data, or HARQ-ACK feedback for one or more unicast data.

[0021] In another optional implementation, the terminal device sends a first uplink control message to the network device on a first PUCCH resource; or, sends a second uplink control message to the network device on a second PUCCH resource, including: when the number of bits in the first uplink control message is greater than the number of bits in the second uplink control message, the terminal device sends the first uplink control message on the first PUCCH resource; or, when the number of bits in the second uplink control message is greater than or equal to the number of bits in the first uplink control message, the terminal device sends the second uplink control message on the second PUCCH resource.

[0022] It is evident that when the first PUCCH resource and the second PUCCH resource overlap in the time domain, the terminal device only sends the uplink control information with the larger number of bits in the first uplink control information and the second uplink control information to the network device, so as to ensure that the HARQ-ACK information with the larger number of bits is fed back.

[0023] In another optional implementation, the terminal device sends a first uplink control message to the network device on a first PUCCH resource; or, sends a second uplink control message to the network device on a second PUCCH resource, including: when the number of bits in the first uplink control message is less than the number of bits in the second uplink control message, the terminal device sends the first uplink control message on the first PUCCH resource; or, when the number of bits in the second uplink control message is less than or equal to the number of bits in the first uplink control message, the terminal device sends the second uplink control message on the second PUCCH resource.

[0024] It is evident that when the first PUCCH resource and the second PUCCH resource overlap in the time domain, the terminal device only sends the uplink control information with the smaller number of bits in the first uplink control information and the second uplink control information to the network device. This ensures that the HARQ-ACK information with the smaller number of bits is fed back, while reducing the PUCCH overhead occupied by the HARQ-ACK information and reducing interference to other terminal devices.

[0025] In another optional implementation, the terminal device sends a first uplink control message to the network device on a first PUCCH resource; or, sends a second uplink control message to the network device on a second PUCCH resource, including: when the time domain position of the first PUCCH resource is before the time domain position of the second PUCCH resource, the terminal device sends the first uplink control message on the first PUCCH resource; or, when the time domain position of the second PUCCH resource is before the time domain position of the first PUCCH resource, the terminal device sends the second uplink control message on the second PUCCH resource.

[0026] It is evident that when the first PUCCH resource and the second PUCCH resource overlap in the time domain, the terminal device only sends back its corresponding HARQ-ACK information to the network device on the PUCCH resource that is earlier in the time domain.

[0027] In another optional implementation, the terminal device sends a first uplink control message to the network device on the first PUCCH resource; or, sends a second uplink control message to the network device on the second PUCCH resource, including: when the first PUCCH resource is configured for repeated transmission, the terminal device sends the second uplink control message on the second PUCCH resource; or, when the second PUCCH resource is configured for repeated transmission, the terminal device sends the first uplink control message on the first PUCCH resource.

[0028] It is evident that when the first PUCCH resource and the second PUCCH resource overlap in the time domain, the terminal device does not feed back HARQ-ACK information carried on the PUCCH resource configured for repeated transmission, but feeds back HARQ-ACK information carried on the PUCCH resource not configured for repeated transmission, in order to ensure that the HARQ-ACK information carried on the PUCCH resource not configured for repeated transmission is fed back.

[0029] In one optional implementation, when there is only one first PUCCH configuration information, the priority corresponding to the first PUCCH configuration information is high priority. That is, when there is only one PUCCH configuration information corresponding to multicast data, its corresponding priority is not the default low priority, but the high priority configured by the network device.

[0030] In one optional implementation, the priority corresponding to the first PUCCH configuration information is configured in bits within the DCI corresponding to one or more multicast data, or configured via a Radio Network Temporary Identifier (RNTI) scrambled with the DCI, or configured in Radio Resource Control (RRC) signaling. In other words, the priority corresponding to the first PUCCH configuration information is configured at the physical layer of the communication system.

[0031] In one optional implementation, the terminal device obtains the first physical uplink control channel (PUCCH) configuration information corresponding to the multicast data and the second PUCCH configuration information corresponding to the unicast data, including: the terminal device receiving the first PUCCH configuration information and the second PUCCH configuration information from the network device.

[0032] Thirdly, this application also provides a method for transmitting uplink control information. This method corresponds to the method described in the first aspect, and is explained from the perspective of the network device. In this method, the network device sends a first Physical Uplink Control Channel (PUCCH) configuration information corresponding to multicast data and a second PUCCH configuration information corresponding to unicast data to the terminal device; then, it sends multiple data items to the terminal device, including one or more multicast data items and one or more unicast data items; the first Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) information corresponding to one or more multicast data items and the second HARQ-ACK information corresponding to one or more unicast data items have the same priority and must be fed back within the same time unit; then, it determines the PUCCH resource; the PUCCH resource belongs to the PUCCH resource set configured in the first PUCCH configuration information, or belongs to the PUCCH resource set configured in the second PUCCH configuration information; finally, it receives uplink control information from the terminal device on the PUCCH resource; the uplink control information includes the first HARQ-ACK information and the second HARQ-ACK information.

[0033] As can be seen, in this embodiment of the application, when the first hybrid automatic repeat request-acknowledgment (HARQ-ACK) information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data belong to the same priority and need to be fed back within the same time unit, the network device can receive the first HARQ-ACK information and the second HARQ-ACK information fed back by the terminal device on the PUCCH resource set configured in the first PUCCH configuration information or the PUCCH resource set configured in the second PUCCH configuration information, thereby avoiding the network device being unable to receive the feedback information.

[0034] In one optional implementation, the network device may also send a Physical Uplink Control Channel Resource Indicator (PRI) in the DCI corresponding to the last multicast data. The PRI indicates a PUCCH resource, which is one of the PUCCH resource sets configured in the first PUCCH configuration information. Alternatively, the network device may send a Physical Uplink Control Channel Resource Indicator (PRI) in the DCI corresponding to the last unicast data. The PRI indicates a PUCCH resource, which is one of the PUCCH resource sets configured in the second PUCCH configuration information.

[0035] As can be seen, the network device can indicate to the terminal device through the PRI in the DCI corresponding to the last multicast data that the PUCCH resource is one of the PUCCH resource sets configured in the first PUCCH configuration information, or indicate to the terminal device through the PRI in the DCI corresponding to the last unicast data that the PUCCH resource is one of the PUCCH resource sets configured in the second PUCCH configuration information.

[0036] In another optional implementation, the network device may also send a Physical Uplink Control Channel Resource Indicator (PRI) in the last downlink control information (DCI) corresponding to multiple data. The PRI indicates a PUCCH resource that belongs to the PUCCH resource set configured in the second PUCCH configuration information, or the PUCCH resource belongs to the PUCCH resource set configured in the second PUCCH configuration information.

[0037] As can be seen, the network device can indicate to the terminal device through the PRI in the last DCI corresponding to multiple data that the above PUCCH resources belong to the set of PUCCH resources configured in the first PUCCH configuration information or the second PUCCH configuration information.

[0038] In another optional implementation, the network device may further send a first indication information to the terminal device; the first indication information is used to indicate that the PUCCH resource belongs to the PUCCH resource set configured by the first PUCCH configuration information or to indicate that the PUCCH resource belongs to the PUCCH resource set configured by the second PUCCH configuration information; when the first indication information indicates that the PUCCH resource belongs to the PUCCH resource set configured by the first PUCCH configuration information, the network device sends a Physical Uplink Control Channel Resource Indicator (PRI) in the last DCI corresponding to one or more multicast data, and the PRI indicates the PUCCH resource; when the first indication information indicates that the PUCCH resource belongs to the PUCCH resource set configured by the second PUCCH configuration information, the network device sends a Physical Uplink Control Channel Resource Indicator (PRI) in the last DCI corresponding to one or more unicast data, and the PRI indicates the PUCCH resource.

[0039] In other words, the network device can also indicate the aforementioned PUCCH resources to the terminal device through the first indication information.

[0040] In one optional implementation, when there is only one first PUCCH configuration information, the priority corresponding to the first PUCCH configuration information is high priority. That is, when there is only one PUCCH configuration information corresponding to multicast data, its corresponding priority is not the default low priority, but the high priority configured by the network device.

[0041] In one optional implementation, the priority corresponding to the first PUCCH configuration information is configured in bits within the DCI corresponding to one or more multicast data, or configured via a Radio Network Temporary Identifier (RNTI) scrambled with the DCI, or configured in Radio Resource Control (RRC) signaling. In other words, the priority corresponding to the first PUCCH configuration information is configured at the physical layer of the communication system.

[0042] Fourthly, this application also provides a method for transmitting uplink control information, which corresponds to the method for transmitting uplink control information described in the second aspect, and is described from the perspective of the network device. In this method, the network device sends the first Physical Uplink Control Channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data to the terminal device. Then, it sends multiple data items to the terminal device, including one or more multicast data items and one or more unicast data items. The first Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) information corresponding to one or more multicast data items and the second HARQ-ACK information corresponding to one or more unicast data items have the same priority and must be fed back within the same time unit. Next, the first PUCCH resource and the second PUCCH resource are determined. The first PUCCH resource belongs to the PUCCH resource set configured by the first PUCCH configuration information; the second PUCCH resource belongs to the PUCCH resource set configured by the second PUCCH configuration information. Finally, based on the first PUCCH resource and the second PUCCH resource, at least one of the first uplink control information and the second uplink control information from the terminal device is received. The first uplink control information includes the first HARQ-ACK information; the second uplink control information includes the second HARQ-ACK information.

[0043] As can be seen, in this embodiment of the application, when the first HARQ-ACK information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data belong to the same priority and need to be fed back within the same time unit, the network device can receive at least one of the first HARQ-ACK information and the second HARQ-ACK information fed back by the terminal device based on the PUCCH resource set configured in the first PUCCH configuration information or the PUCCH resource set configured in the second PUCCH configuration information, thereby avoiding the network device being unable to receive the feedback information.

[0044] In one optional implementation, the network device receives at least one of a first uplink control information and a second uplink control information from the terminal device based on a first PUCCH resource and a second PUCCH resource, including: the first PUCCH resource and the second PUCCH resource do not overlap; the network device receives the first uplink control information from the terminal device on the first PUCCH resource and receives the second uplink control information from the terminal device on the second PUCCH resource.

[0045] It is evident that when the first PUCCH resource and the second PUCCH resource do not overlap, the network device receives the first uplink control information and the second uplink control information sent by the terminal device.

[0046] In another optional implementation, the network device receives at least one of a first uplink control information and a second uplink control information from the terminal device based on a first PUCCH resource and a second PUCCH resource, including: the first PUCCH resource and the second PUCCH resource overlap, and the network device receives the first uplink control information from the terminal device on the first PUCCH resource; or, the network device receives the second uplink control information from the terminal device on the second PUCCH resource.

[0047] It is evident that when the first PUCCH resource and the second PUCCH resource overlap, the network device receives either the first uplink control information or the second uplink control information sent by the terminal device.

[0048] In another optional implementation, the network device receives first uplink control information from the terminal device on a first PUCCH resource; or, receives second uplink control information from the terminal device on a second PUCCH resource, including: the network device receiving the first uplink control information from the terminal device on the first PUCCH resource, wherein the number of bits in the first uplink control information is greater than the number of bits in the second uplink control information; or, the network device receiving the second uplink control information from the terminal device on the second PUCCH resource, wherein the number of bits in the second uplink control information is greater than or equal to the number of bits in the first uplink control information.

[0049] It is evident that when the first PUCCH resource and the second PUCCH resource overlap, the network device receives the uplink control information with the larger number of bits from the first uplink control information and the second uplink control information sent by the terminal device.

[0050] In another optional implementation, the network device receives first uplink control information from the terminal device on a first PUCCH resource; or, receives second uplink control information from the terminal device on a second PUCCH resource, including: the network device receiving the first uplink control information from the terminal device on the first PUCCH resource, wherein the number of bits in the first uplink control information is less than the number of bits in the second uplink control information; or, the network device receiving the second uplink control information from the terminal device on the second PUCCH resource, wherein the number of bits in the second uplink control information is less than or equal to the number of bits in the first uplink control information.

[0051] It is evident that when the first PUCCH resource and the second PUCCH resource overlap, the network device receives the uplink control information with the smaller number of bits between the first uplink control information and the second uplink control information sent by the terminal device.

[0052] In another optional implementation, the network device receives first uplink control information from the terminal device on a first PUCCH resource; or, receives second uplink control information from the terminal device on a second PUCCH resource, including: the network device receiving the first uplink control information from the terminal device on the first PUCCH resource, wherein the time domain position of the first PUCCH resource is before the time domain position of the second PUCCH resource; or, the network device receiving the second uplink control information from the terminal device on the second PUCCH resource, wherein the time domain position of the second PUCCH resource is before the time domain position of the first PUCCH resource.

[0053] It is evident that when the first PUCCH resource and the second PUCCH resource overlap, the network device receives the HARQ-ACK information fed back by the terminal device, which is carried on the PUCCH resource that is earlier in the time domain.

[0054] In another optional implementation, the network device receives first uplink control information from the terminal device on a first PUCCH resource; or, receives second uplink control information from the terminal device on a second PUCCH resource, including: the network device receiving the second uplink control information from the terminal device on the second PUCCH resource, and the first PUCCH resource being configured for repeated transmission; or, the network device receiving the first uplink control information from the terminal device on the first PUCCH resource, and the second PUCCH resource being configured for repeated transmission.

[0055] It is evident that when the first PUCCH resource and the second PUCCH resource overlap, the network device receives the HARQ-ACK information fed back by the terminal device, which is carried on the PUCCH resource that is not configured to be repeatedly transmitted.

[0056] In one optional implementation, when there is only one first PUCCH configuration information, the priority corresponding to the first PUCCH configuration information is high priority. That is, when there is only one PUCCH configuration information corresponding to multicast data, its corresponding priority is not the default low priority, but the high priority configured by the network device.

[0057] In one optional implementation, the priority corresponding to the first PUCCH configuration information is configured in bits within the DCI corresponding to one or more multicast data, or configured via a Radio Network Temporary Identifier (RNTI) scrambled with the DCI, or configured in Radio Resource Control (RRC) signaling. In other words, the priority corresponding to the first PUCCH configuration information is configured at the physical layer of the communication system.

[0058] Fifthly, this application also provides a method for transmitting uplink control information, which is also described from the perspective of the network device. In this method, the network device determines the first Physical Uplink Control Channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data. The first Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) information corresponding to multicast data and the second HARQ-ACK information corresponding to unicast data have different priorities. Then, the network device sends the first PUCCH configuration information and the second PUCCH configuration information to the terminal device.

[0059] As can be seen, in this embodiment, when the network device configures the first PUCCH configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data for the terminal device, the first hybrid automatic repeat request-acknowledgement (HARQ-ACK) information corresponding to multicast data and the second HARQ-ACK information corresponding to unicast data have different priorities. That is, the priorities of the first and second PUCCH configuration information configured by the network device are different. This allows the terminal device to feed back the first HARQ-ACK information and the second HARQ-ACK information respectively on the PUCCH resources determined according to the first PUCCH configuration information and the PUCCH resources determined according to the second PUCCH configuration information, based on the principle of different priorities. This facilitates a consistent understanding of the HARQ-ACK feedback method between the network device and the terminal device, thereby improving the efficiency of HARQ-ACK feedback.

[0060] Correspondingly, the terminal device does not expect the PUCCH configuration information corresponding to multicast data and the PUCCH configuration information corresponding to unicast data to have the same priority. This allows the terminal device to send feedback information for both multicast and unicast data to the network device based on the current feedback method for unicast data. Specifically, it sends the corresponding feedback information based on the PUCCH resources determined by the PUCCH configuration information for each type of data. This implementation method helps reduce the complexity of both network and terminal devices.

[0061] Sixthly, this application also provides a communication device. This communication device has some or all of the functions of the terminal device described in the first aspect, or some or all of the functions of the terminal device described in the second aspect, or some or all of the functions of the network device described in the third aspect, or some or all of the functions of the network device described in the fourth aspect, or some or all of the functions of the network device described in the fifth aspect. For example, the communication device may possess the functions of some or all of the embodiments of the terminal device described in the first aspect of this application, or it may possess the functions of any one embodiment of this application implemented individually. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0062] In one possible design, the communication device may include a processing unit and a communication unit. The processing unit is configured to support the communication device in performing the corresponding functions described in the above method. The communication unit supports communication between the communication device and other communication devices. The communication device may also include a storage unit coupled to the processing unit and the transceiver unit, which stores necessary program instructions and data for the communication device.

[0063] In one embodiment, the communication device includes:

[0064] The processing unit is used to obtain the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data;

[0065] The communication unit is used to receive multiple data from the network device, including one or more multicast data and one or more unicast data; the first hybrid automatic repeat request-acknowledgment (HARQ-ACK) information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data have the same priority and need to be fed back in the same time unit.

[0066] The processing unit is also configured to determine the PUCCH resource based on the first PUCCH configuration information or the second PUCCH configuration information;

[0067] The communication unit is also used to send uplink control information to network devices on PUCCH resources; the uplink control information includes first HARQ-ACK information and second HARQ-ACK information.

[0068] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the first aspect above, and will not be described in detail here.

[0069] In another embodiment, the communication device includes:

[0070] The processing unit is used to obtain the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data;

[0071] The communication unit is also used to receive multiple data from the network device, including one or more multicast data and one or more unicast data; the first HARQ-ACK information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data belong to the same priority and need to be fed back in the same time unit;

[0072] The processing unit is further configured to determine the first PUCCH resource based on the first PUCCH configuration information, and to determine the second PUCCH resource based on the second PUCCH configuration information;

[0073] The communication unit is further configured to send at least one of a first uplink control information and a second uplink control information to the network device based on the first PUCCH resource and the second PUCCH resource, wherein the first uplink control information includes a first HARQ-ACK information and the second uplink control information includes a second HARQ-ACK information.

[0074] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the second aspect above, and will not be described in detail here.

[0075] In another embodiment, the communication device includes:

[0076] The communication unit is used to send the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data to the terminal device.

[0077] The communication unit is also used to send multiple data to the terminal device, including one or more multicast data and one or more unicast data; the first hybrid automatic repeat request-acknowledgment (HARQ-ACK) information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data belong to the same priority and need to be fed back in the same time unit;

[0078] The processing unit is used to determine the PUCCH resource; the PUCCH resource belongs to the set of PUCCH resources configured in the first PUCCH configuration information, or belongs to the set of PUCCH resources configured in the second PUCCH configuration information.

[0079] The communication unit is also used to receive uplink control information from the terminal device on the PUCCH resource; the uplink control information includes first HARQ-ACK information and second HARQ-ACK information.

[0080] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the third aspect above, and will not be described in detail here.

[0081] In another embodiment, the communication device includes:

[0082] The communication unit is used to send the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data to the terminal device.

[0083] The communication unit is also used to send multiple data to the terminal device, including one or more multicast data and one or more unicast data; the first hybrid automatic repeat request-acknowledgment (HARQ-ACK) information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data belong to the same priority and need to be fed back in the same time unit;

[0084] The processing unit is used to determine the first PUCCH resource and the second PUCCH resource; the first PUCCH resource belongs to the PUCCH resource set configured by the first PUCCH configuration information; the second PUCCH resource belongs to the PUCCH resource set configured by the second PUCCH configuration information.

[0085] The communication unit is further configured to receive at least one of a first uplink control information and a second uplink control information from a terminal device, based on a first PUCCH resource and a second PUCCH resource; the first uplink control information includes a first HARQ-ACK information; and the second uplink control information includes a second HARQ-ACK information.

[0086] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the fourth aspect above, and will not be described in detail here.

[0087] In another embodiment, the communication device includes:

[0088] The processing unit is used to determine the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data. The first hybrid automatic repeat request-acknowledgement (HARQ-ACK) information corresponding to multicast data and the second HARQ-ACK information corresponding to unicast data belong to different priorities.

[0089] The communication unit is used to send the first PUCCH configuration information and the second PUCCH configuration information to the terminal device.

[0090] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the fifth aspect above, and will not be described in detail here.

[0091] As an example, the transceiver unit can be a transceiver or a communication interface, the storage unit can be a memory, and the processing unit can be a processor.

[0092] In one embodiment, the communication device includes:

[0093] The processor is used to acquire the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data.

[0094] The communication interface is used to receive multiple data from network devices, including one or more multicast data and one or more unicast data; the first HARQ-ACK information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data have the same priority and need to be fed back in the same time unit.

[0095] The processor is also used to determine PUCCH resources based on the first PUCCH configuration information or the second PUCCH configuration information;

[0096] The communication interface is also used to send uplink control information to network devices on PUCCH resources; the uplink control information includes first HARQ-ACK information and second HARQ-ACK information.

[0097] In addition, other optional implementations of the uplink communication device in this regard can be found in the relevant content of the first aspect above, and will not be described in detail here.

[0098] In another embodiment, the communication device includes:

[0099] The processor is used to acquire the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data.

[0100] The communication interface is used to receive multiple data from network devices, including one or more multicast data and one or more unicast data; the first HARQ-ACK information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data have the same priority and need to be fed back in the same time unit;

[0101] The processor is also configured to determine a first PUCCH resource based on the first PUCCH configuration information, and to determine a second PUCCH resource based on the second PUCCH configuration information;

[0102] The communication interface is also used to send at least one of a first uplink control information and a second uplink control information to the network device according to the first PUCCH resource and the second PUCCH resource, wherein the first uplink control information includes a first HARQ-ACK information and the second uplink control information includes a second HARQ-ACK information.

[0103] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the second aspect above, and will not be described in detail here.

[0104] In another embodiment, the communication device includes:

[0105] The communication interface is used to send the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data to the terminal device.

[0106] The communication interface is also used to send multiple data to the terminal device, including one or more multicast data and one or more unicast data; the first HARQ-ACK information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data belong to the same priority and need to be fed back in the same time unit;

[0107] The processor is used to determine the PUCCH resources; the PUCCH resources belong to the set of PUCCH resources configured in the first PUCCH configuration information, or belong to the set of PUCCH resources configured in the second PUCCH configuration information.

[0108] The communication interface is also used to receive uplink control information from the terminal device on the PUCCH resource; the uplink control information includes first HARQ-ACK information and second HARQ-ACK information.

[0109] In addition, other optional implementations of the uplink communication device in this regard can be found in the relevant content of the third aspect above, and will not be described in detail here.

[0110] In another embodiment, the communication device includes:

[0111] The communication interface is used to send the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data to the terminal device.

[0112] The communication interface is also used to send multiple data to the terminal device, including one or more multicast data and one or more unicast data; the first HARQ-ACK information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data belong to the same priority and need to be fed back in the same time unit;

[0113] The processor is used to determine the first PUCCH resource and the second PUCCH resource; the first PUCCH resource belongs to the PUCCH resource set configured by the first PUCCH configuration information; the second PUCCH resource belongs to the PUCCH resource set configured by the second PUCCH configuration information.

[0114] The communication interface is also configured to receive at least one of a first uplink control information and a second uplink control information from a terminal device, based on a first PUCCH resource and a second PUCCH resource; the first uplink control information includes a first HARQ-ACK information; and the second uplink control information includes a second HARQ-ACK information.

[0115] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the fourth aspect above, and will not be described in detail here.

[0116] In another embodiment, the communication device includes:

[0117] The processor is used to determine the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data. The first hybrid automatic repeat request-acknowledgment (HARQ-ACK) information corresponding to multicast data and the second HARQ-ACK information corresponding to unicast data belong to different priorities.

[0118] The communication interface is used to send the first PUCCH configuration information and the second PUCCH configuration information to the terminal device.

[0119] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the fifth aspect above, and will not be described in detail here.

[0120] In another embodiment, the communication device is a chip or chip system. The processing unit may also be a processing circuit or logic circuit; the transceiver unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system.

[0121] In implementation, the processor can be used for, but is not limited to, baseband-related processing, and the transceiver can be used for, but is not limited to, radio frequency transceiver. These devices can be disposed on separate chips, or at least partially or entirely on the same chip. For example, the processor can be further divided into analog baseband processors and digital baseband processors. The analog baseband processor can be integrated with the transceiver on the same chip, while the digital baseband processor can be disposed on a separate chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, a digital baseband processor can be integrated with multiple application processors (e.g., but not limited to graphics processors, multimedia processors, etc.) on the same chip. Such a chip can be called a System on a Chip (SoC). Whether the devices are disposed independently on different chips or integrated on one or more chips often depends on the needs of the product design. This application does not limit the implementation form of the above devices.

[0122] Seventhly, this application also provides a processor for executing the various methods described above. In executing these methods, the processes of sending and receiving the aforementioned information can be understood as the processor outputting the aforementioned information and the processor receiving the input information. When outputting the aforementioned information, the processor outputs the information to a transceiver for transmission. After being output by the processor, the information may require further processing before reaching the transceiver. Similarly, when the processor receives the input information, the transceiver receives the information and inputs it to the processor. Furthermore, after the transceiver receives the information, the information may require further processing before being input to the processor.

[0123] Based on the above principles, for example, the uplink control information mentioned in the aforementioned method can be understood as the uplink control information output by the processor.

[0124] Unless otherwise specified, or unless it contradicts its actual function or internal logic in the relevant description, the transmission, receiving, and receiving operations involved in the processor can be more generally understood as processor output and receiving, input, and other operations, rather than transmission, receiving, and receiving operations directly performed by radio frequency circuits and antennas.

[0125] In implementation, the processor can be a dedicated processor for executing these methods, or it can be a processor that executes computer instructions stored in memory to execute these methods, such as a general-purpose processor. The memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or disposed on different chips. This application does not limit the type of memory or the arrangement of the memory and the processor.

[0126] Eighthly, this application also provides a communication system comprising at least one terminal device and at least one network device as described above. In another possible design, the system may further include other devices that interact with the terminal device and network device as provided in this application.

[0127] Ninthly, this application provides a computer-readable storage medium for storing instructions that, when executed by a communication device, implement the method described in any one of the first to fifth aspects.

[0128] In a tenth aspect, this application also provides a computer program product including instructions that, when run on a communication device, cause the communication device to perform the method described in any one of the first to fifth aspects.

[0129] Eleventhly, this application provides a chip system including a processor and an interface. The interface is used to acquire programs or instructions. The processor is used to invoke the programs or instructions to implement or support a terminal device in implementing the functions involved in the first aspect, or to invoke the programs or instructions to implement or support a terminal device in implementing the functions involved in the second aspect, to invoke the programs or instructions to implement or support a network device in implementing the functions involved in the third aspect, to invoke the programs or instructions to implement or support a network device in implementing the functions involved in the fourth aspect, and to invoke the programs or instructions to implement or support a network device in implementing the functions involved in the fifth aspect. For example, determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing necessary program instructions and data for the terminal. The chip system may be composed of chips or may include chips and other discrete devices. Attached Figure Description

[0130] Figure 1 This is a schematic diagram of the structure of a communication system provided in an embodiment of this application;

[0131] Figure 2This is a schematic diagram of downlink scheduling provided in an embodiment of this application;

[0132] Figure 3 This is a schematic diagram illustrating the determination of a feedback time unit provided in an embodiment of this application;

[0133] Figure 4 This is a schematic diagram of another method for determining the feedback time unit provided in an embodiment of this application;

[0134] Figure 5 This is a schematic diagram of a PDSCH time-domain resource provided in an embodiment of this application;

[0135] Figure 6 This is a schematic diagram illustrating a network device scheduling multiple data streams according to an embodiment of this application;

[0136] Figure 7 This is a flowchart illustrating a method for transmitting uplink control information provided in an embodiment of this application;

[0137] Figure 8 This is a schematic diagram illustrating the determination of a PUCCH resource according to an embodiment of this application;

[0138] Figure 9 This is a schematic diagram illustrating another method for determining PUCCH resources provided in an embodiment of this application;

[0139] Figure 10 This is a flowchart illustrating another method for transmitting uplink control information provided in an embodiment of this application;

[0140] Figure 11a This is a schematic diagram of a first PUCCH resource and a second PUCCH resource provided in an embodiment of this application;

[0141] Figure 11b This is a schematic diagram of another first PUCCH resource and a second PUCCH resource provided in an embodiment of this application;

[0142] Figure 11c This is a schematic diagram of another first PUCCH resource and a second PUCCH resource provided in the embodiments of this application;

[0143] Figure 12 This is a flowchart illustrating another method for transmitting uplink control information provided in an embodiment of this application;

[0144] Figure 13 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0145] Figure 14 This is a schematic diagram of another communication device provided in an embodiment of this application;

[0146] Figure 15 This is a schematic diagram of the structure of a chip provided in an embodiment of this application. Detailed Implementation

[0147] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0148] First, in order to better understand the uplink control information transmission method disclosed in the embodiments of this application, the communication system applicable to the embodiments of this application will be described.

[0149] Please see Figure 1 , Figure 1 This is a schematic diagram of a communication system provided in an embodiment of this application. The communication system may include, but is not limited to, a network device and a terminal device. Figure 1 The number and form of devices shown are for illustrative purposes and do not constitute a limitation on the embodiments of this application. In actual applications, it may include two or more network devices and two or more terminal devices. Figure 1 The communication system illustrated uses a network device and a terminal device as an example, where the network device is capable of providing services to the terminal device. Figure 1 The network equipment in this application takes a base station as an example, and the terminal equipment takes a mobile phone as an example. The technical solutions of this application can be applied to various communication systems. For example, fourth-generation (4G) mobile communication systems, fifth-generation (5G) mobile communication systems, sixth-generation (6G) mobile communication systems, and with the continuous development of communication technology, the technical solutions of this application can also be used in subsequent evolved communication systems, such as seventh-generation (7G) mobile communication systems, etc.

[0150] In this embodiment of the application, a network device is an entity on the network side used to transmit or receive signals. The network device may be a device with wireless transceiver function or a chip that can be set in the device. This network equipment includes, but is not limited to: evolved node B (eNB), radio network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home network equipment (e.g., home evolved Node B, or home Node B, HNB), baseband unit (BBU), access point (AP), wireless relay node, wireless backhaul node, transmission and reception point (TRP or transmission point, TP) in wireless fidelity (WIFI) systems, and can also be equipment used in 4G, 5G, and even 6G systems, such as gNB in ​​NR systems, or transmission points (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of network equipment in 4G systems, or network nodes constituting gNB or transmission points, such as baseband unit (BBU), or distributed unit (DU), or central unit (CNU). Unit (CU), or Picocell, or Femtocell, or Roadside Unit (RSU) in intelligent driving scenarios.

[0151] In this application embodiment, the terminal device is an entity on the terminal side used to receive or transmit signals. The terminal device can be a device with wireless transceiver function or a chip that can be set in the device. The terminal device can also be called user equipment (UE), terminal, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, user agent, or user device, and can be applied to 4G, 5G, or even 6G systems. The terminal in the embodiments of this application can be a mobile phone, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal, augmented reality (AR) terminal, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, RSU of the aforementioned wireless terminal types, etc.

[0152] The embodiments of this application can be applied to communication scenarios where network devices schedule both multicast and unicast data to terminal devices, and the hybrid automatic repeat request (HARQ) ACK information corresponding to the scheduled multicast data and the HARQ-ACK information corresponding to the scheduled unicast data are fed back within the same time unit.

[0153] To facilitate understanding of the embodiments disclosed in this application, the following two points are explained.

[0154] (1) The scenarios in the embodiments disclosed in this application are illustrated using the scenario of an NR network in a wireless communication network. It should be noted that the solutions in the embodiments disclosed in this application can also be applied to other wireless communication networks, and the corresponding names can be replaced by the names of the corresponding functions in other wireless communication networks.

[0155] (2) The embodiments disclosed in this application will be presented in relation to systems including multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches may also be used.

[0156] Secondly, a brief introduction to the relevant concepts involved in the embodiments of this application will be given.

[0157] 1. Feedback information.

[0158] In this application, the feedback information is a Hybrid Automatic Repeat Request (HARQ-ACK) message. The HARQ-ACK message is designed for the rapid retransmission of lost or erroneous data. For example, after receiving a Physical Downlink Shared Channel (PDSCH) transmission, the terminal determines the HARQ-ACK information of that PDSCH transmission, such as by providing an ACK message or a NACK message, and sends this HARQ-ACK message to the network device so that the network device can determine whether the PDSCH needs to be retransmitted.

[0159] 2. Time unit.

[0160] A time unit can be one or more radio frames, one or more subframes, one or more time slots, one or more mini slots, one or more orthogonal frequency division multiplexing (OFDM) symbols, discrete fourier transform spread spectrum orthogonal frequency division multiplexing (DFT-S-OFDM) symbols, or a time window composed of multiple frames or subframes, such as a system information (SI) window. For example, the time domain resources occupied by one PDSCH transmission are one or more OFDM symbols, one or more DFT-S-OFDM symbols, or one or more mini slots. A mini slot can include multiple OFDM symbols or DFT-S-OFDM symbols. In the embodiments of this application, the time unit is configured by the network device for the terminal device, and can be 1 slot, 2 symbols, 7 symbols, etc.

[0161] 3. Unicast scheduling, multicast scheduling, unicast data, multicast data.

[0162] Unicast scheduling refers to a one-to-one scheduling method where network devices assign a cell radio network temporary identity (C-RNTI) to the UE. The UE then receives data based on downlink control information (DCI) scrambled with the C-RNTI.

[0163] Multicast scheduling refers to a one-to-many scheduling method where network devices schedule terminal devices in a multicast manner. When multiple UEs receive the same data service, the network device assigns the same group radio network temporary identity (G-RNTI) to these UEs, and different UEs receive the same data service based on the same G-RNTI-scrambled DCI.

[0164] Unicast data: refers to downlink data transmitted by network devices to the UE through unicast scheduling.

[0165] Multicast data: refers to downlink data transmitted to the UE by network devices through multicast scheduling.

[0166] When the number of UEs served by a network device is large, unicast scheduling consumes more downlink transmission resources compared to multicast scheduling. Therefore, using multicast scheduling can save downlink resources. Furthermore, for a single UE, the network device can assign either a C-RNTI to receive unicast data or a G-RNTI to receive multicast data.

[0167] For example, such as Figure 2 In the downlink scheduling diagram shown, PDSCH#1 on downlink time slot 0 is unicast scheduled to UE#1 by the network device, PDSCH#2 on downlink time slot 2 is multicast scheduled to both UE#1 and UE#2 by the network device, and PDSCH#3 on downlink time slot 4 is unicast scheduled to UE#2 by the network device.

[0168] 4. Feedback on HARQ-ACK information.

[0169] In new radio (NR) systems, the unicast scheduling described above employs the HARQ-ACK mechanism to ensure transmission reliability. Taking downlink transmission as an example, the UE receives the time-domain information of the scheduled PDSCH from the time-domain resource configuration bit field in the DCI scrambled by C-RNTI, including the start symbol of the time-domain resource and the time-domain length. The UE then receives the PDSCH based on this bit field. If the UE receives it correctly, it sends an ACK; if the UE receives it incorrectly, it sends a NACK. Specifically, the UE generates a HARQ-ACK codebook from the HARQ-ACK information corresponding to the PDSCH scheduled by the network device in a certain time unit and sends this HARQ-ACK codebook to the network device to achieve feedback of HARQ-ACK information. The following describes the UE's feedback process for HARQ-ACK information:

[0170] A) Determine the feedback time unit.

[0171] The UE determines the feedback time unit by defining the timing relationship n+k1 between receiving downlink data and sending HARQ-ACK information to the network device. Here, n represents the time unit for the terminal device to receive the PDSCH, and k1 represents the time difference between the time unit for receiving the PDSCH and the corresponding ACK / NACK feedback time unit. The value of k1 is indicated to the terminal device by the network device via DCI.

[0172] For example, such as Figure 3 As shown, the UE receives PDSCH in slot(n). If the network device indicates that k1 equals 4, the UE needs to send back HARQ-ACK information to the network device in slot(n+4).

[0173] B) Generate the HARQ-ACK codebook.

[0174] The UE uses a HARQ-ACK codebook to provide feedback on HARQ-ACK information. The network device configures two HARQ-ACK codebook modes for the UE: a semi-static codebook mode and a dynamic codebook mode. The UE can then generate the corresponding HARQ-ACK codebook based on the configured codebook mode, thereby enabling feedback on HARQ-ACK information.

[0175] The following example illustrates the generation process of semi-static and dynamic HARQ-ACK codebooks, assuming that the UE determines to send feedback information in slot(n+4), and slot(n+4) is slot(i).

[0176] a. The process of generating a semi-static HARQ-ACK codebook.

[0177] If the UE is configured in semi-static HARQ-ACK codebook mode, also known as Type 1 HARQ codebook, the UE generates a semi-static HARQ-ACK codebook for all required HARQ-ACK information. First, the UE determines a set of k1 values, which includes multiple k1 values ​​configured for the UE by the network device. Then, based on this set of k1 values, the UE works backward from slot(i) to determine the slot positions where HARQ-ACK feedback information is sent in slot(i). For example, as... Figure 4 As shown, the k1 set is {0,1,2,3,4}. Starting from slot(i), based on this k1 set, the UE can determine slot(i-4), slot(i-3), slot(i-2), slot(i-1), and all data in slot(i) will be fed back with HARQ-ACK information on slot(i).

[0178] In other words, if the UE receives a downlink DCI in each of slots (i-4), (i-3), (i-2), (i-1), and (i), and each DCI indicates k1 to slot (i), then all HARQ-ACK information in slots (i-4), (i-3), (i-2), (i-1), and (i) must be fed back in slot (i). Slots from slot (i-4) to slot (i) without scheduled PDSCH transmissions should feed back NACK in slot (i). Specifically, the UE determines the number of bits to feed back in each slot according to the following process:

[0179] First, the UE determines the PDSCH occasion in slots (i-4), (i-3), (i-2), (i-1), and (i). The PDSCH time-domain resource table configured for the UE by the network device contains a maximum of 16 rows. Each row indicates the start symbol S and the number of symbols L for a time-domain resource. S identifies the position of the data within a slot, and L represents the time-domain length starting from the start symbol S. The UE segments the valid (S, L) overlapping time-domain resources of the PDSCH to determine the number of bits for feedback in each slot. Specifically, the UE segments based on the earliest ending symbol of the time-domain resource. After segmentation, all valid (S, L) are associated with a PDSCH candidate occasion. Each PDSCH candidate occasion is associated with one or more overlapping (S, L) time-domain resources. These overlapping (S, L) time-domain resources are allowed to transmit at most one feedback message; therefore, each PDSCH candidate occasion corresponds to one ACK / NACK. Here, the valid (S,L) refers to the position of a PDSCH determined within a time unit.

[0180] For example, the PDSCH time domain resources configured in network devices, such as Figure 5 As shown, the PDSCH time-domain resource has 16 possible values, corresponding to time-domain resources #0 to #15. Assuming these time-domain resources are all valid (S,L), the UE effectively segments these 16 time-domain resources, with the segmentation positions as follows: Figure 5 The dashed lines indicate that after UE segmentation, four PDSCH candidate occasions are obtained, corresponding to the numbers in parentheses, containing time-domain resources {#0,#1,#2,#3,#4,#6,#12}, {#7,#9,#13}, {#5,#8,#10,#14}, and {#11,#15}, respectively. Each of these four groups of time-domain resources corresponds to one set of feedback information bits. Since PDSCH time-domain resources cannot overlap, only one time-domain resource in each group will have a PDSCH, and the feedback information corresponding to that time-domain resource is the feedback information corresponding to the time-domain resource group to which that time-domain resource belongs. Assuming that each PDSCH feeds back 1 bit of feedback information, the above four groups of time-domain resources will send 4 bits of feedback information, with each bit representing any one of the time-domain resources in that group. For example, the time-domain resource corresponding to the 1 bit of feedback from the first group is one of the time-domain resources {#0,#1,#2,#3,#4,#6,#12}.

[0181] After the UE determines the number of bits to be fed back, it concatenates the feedback information of multiple PDSCH candidate occasions associated with slot(i). Each PDSCH candidate occasion corresponds to its own ACK / NACK, and then forms the final HARQ-ACK codebook.

[0182] b. The process of generating a dynamic HARQ-ACK codebook.

[0183] If the UE is configured in dynamic HARQ-ACK codebook mode, also known as Type 2 HARQ codebook, then the UE generates a dynamic HARQ-ACK codebook.

[0184] If the physical uplink control channel (PDCCH) received by the UE indicates feedback in slot(i), then the HARQ-ACK codebook in slot(i) contains the feedback information of the PDSCH scheduled by the PDCCH. The UE arranges the HARQ-ACK information according to the PDCCH reception order to generate the HARQ-ACK codebook, that is, it generates feedback information with scheduling information.

[0185] If the PDSCH received by the UE does not contain scheduling information, i.e., the PDSCH is a semi-statically scheduled PDSCH, the UE adds M bits to the HARQ-ACK information containing scheduling information to provide feedback information corresponding to the PDSCH without scheduling information. Here, M is a positive integer greater than 1.

[0186] In other words, if the network device configures the UE to use a dynamic HARQ-ACK codebook, the UE generates the HARQ-ACK codebook based on the scheduled PDSCH, meaning it only feeds back the scheduled PDSCH.

[0187] 5. The relationship between the priority of physical uplink control channel (PUCCH) configuration information and HARQ-ACK information.

[0188] In unicast-scheduled services, the HARQ-ACK information of the scheduled PDSCH has two priorities: low priority and high priority. The priority of the HARQ-ACK information is configured by the network device for the UE. These two priorities correspond to enhanced mobile broadband (eMBB) data services and ultra-reliable low latency communication (URLLC) data services, respectively. Accordingly, the network device can configure one or two PUCCH configuration messages for the UE; this PUCCH configuration message refers to PUCCH-config. The UE can determine the resources for feeding back HARQ-ACK information based on this PUCCH configuration message.

[0189] When a network device configures only one PUCCH configuration information for a UE, it indicates that the UE only receives eMBB data services, and the HARQ-ACK information corresponding to the eMBB data has a default low priority. This can also be understood as the HARQ-ACK information corresponding to the PUCCH configuration information having a low priority. If the network device configures two PUCCH configuration information for a UE, it indicates that the UE receives both eMBB and URLLC data services. The HARQ-ACK information corresponding to the PUCCH configuration information configured for eMBB data services has a low priority, while the HARQ-ACK information corresponding to the PUCCH configuration information configured for URLLC data services has a high priority.

[0190] Understandably, the low and high priorities of the HARQ-ACK information mentioned above refer to the data of different services, and are the absolute priorities corresponding to the data of different services. Moreover, the low priority of the HARQ-ACK information is the physical layer priority configured by the network device for the UE.

[0191] 6. PUCCH configuration information.

[0192] As described above, network devices can configure up to two PUCCH configuration information for a UE's unicast services. Furthermore, network devices can also configure PUCCH configuration information for a UE's multicast services; this configuration information is independent of the unicast service PUCCH configuration information.

[0193] Regardless of whether it is a unicast or multicast service, its PUCCH configuration information can include the following:

[0194] a) The k1 set. This k1 set is used to indicate to the UE in which time unit a certain PDSCH should provide HARQ-ACK feedback. It can also be understood that the UE determines the feedback time of HARQ-ACK information for a certain PDSCH by mapping the value of the k1 indication field "PDSCH-to-HARQ_feedback timing indicator" to the value in "dl-DataToUL-ACK".

[0195] Optionally, if the network device does not configure the k1 set in the PUCCH configuration information, the UE will use the default value to determine the feedback time unit of the HARQ-ACK information of a certain PDSCH.

[0196] b) PUCCH resource set. This PUCCH resource set is used by the UE to determine the PUCCH resource for feeding back HARQ-ACK information. The network device can configure up to 4 PUCCH resource sets for the UE, and each PUCCH resource set includes one or more PUCCH resources. The UE can determine one PUCCH resource set from the 4 PUCCH resource sets based on the size of the HARQ-ACK information or the size of the HARQ-ACK codebook.

[0197] Each PUCCH resource set also includes a resource list, which consists of one or more PUCCH resource identifiers. The UE can identify each PUCCH resource through each PUCCH resource identifier.

[0198] c) PUCCH Resources. The network device can allocate up to 32 PUCCH resources to the UE, and each PUCCH resource has its own PUCCH resource identity identifier. The UE can determine the PUCCH resource by mapping the value of the Physical Uplink Control Channel Resource Indicator (PRI) to a specific PUCCH resource identity identifier in the PUCCH resource set.

[0199] d) Format. There are five PUCCH formats in the PUCCH configuration information, designated as Format(0,1,2,3,4). Formats 0-1 include the initial cyclic shift, the time-domain symbol length of the PUCCH resource, and the time-domain start position. Formats 2-4 include the number of physical resource blocks (PRBs) occupied by the PUCCH resource, the time-domain symbol length of the PUCCH resource, and the time-domain start position.

[0200] 7. Last DCI, the last DCI corresponding to one or more multicast data, the last DCI corresponding to one or more unicast data, the last DCI corresponding to one or more multicast data and one or more unicast data, and the last DCI corresponding to multiple data.

[0201] The last DCI: In one implementation, it refers to the last DCI sent by the network device when scheduling multiple data to the UE, and correspondingly, it is also the last DCI received by the UE. In another implementation, the last DCI is the DCI used when scheduling the last data when scheduling multiple data. The results of the two implementations may be the same or different, and this application does not limit the specific implementation. It can be understood that the last DCI is the last of multiple DCIs whose corresponding feedback information is located in the same time unit. If there is only one DCI whose corresponding feedback information is located in the same time unit, then that DCI is also equivalent to the last DCI.

[0202] For example, network devices schedule multiple data requests to the UE, such as... Figure 6 As shown. From Figure 6It can be seen that the network device's scheduling of the UE includes scheduling of multicast data PDSCH#2 and PDSCH#5, and scheduling of unicast data PDSCH#1, PDSCH#3, and PDSCH#4. Specifically, DCI#1 schedules PDSCH#1, DCI#2 schedules PDSCH#2, DCI#3 schedules PDSCH#3, DCI#4 schedules PDSCH#4, and DCI#5 schedules PDSCH#5. Assuming the UE determines that PDSCH#1-PDSCH#5 are all fed back in time unit #3, then the last DCI for the determined feedback resource is within DCI#1-DCI#5. The UE attempts to receive DCIs in each serving cell during the blind detection period (MO), for example, receiving them in ascending order of serving cell index, and then repeating this process in the next MO. In other words, the UE receives DCIs in the order of frequency domain first, then time domain. Therefore, the UE receives... Figure 6 The order of DCI reception is as follows: first receive DCI#1, DCI#2, and DCI#3, then receive DCI#4, and then receive DCI#5, so the last DCI refers to DCI#5.

[0203] The last DCI corresponding to one or more multicast data: In one implementation, it refers to the last DCI sent by the network device when scheduling one or more multicast data, which is also the last DCI received by the UE. In another implementation, the last DCI corresponding to one or more multicast data is the DCI when the network device schedules the last multicast data when scheduling one or more multicast data. The results of the two implementations may be the same or different, and the embodiments of this application do not limit the specific implementation. For example, in the above... Figure 6 In the process of network equipment scheduling multicast data PDSCH#2 and PDSCH#5, the last DCI received by the UE is DCI#5. Therefore, the last DCI corresponding to one or more multicast data is DCI#5.

[0204] The last DCI corresponding to one or more unicast data: In one implementation, this refers to the last DCI sent by the network device when scheduling one or more unicast data, and correspondingly, it is also the last DCI received by the UE. For example, in the above... Figure 6 In the process of network equipment scheduling unicast data PDSCH#1, PDSCH#3, and PDSCH#4, the last DCI received by the UE is DCI#4. Therefore, the last DCI corresponding to one or more unicast data is DCI#4.

[0205] The last DCI corresponding to multiple data sets, or the last DCI corresponding to one or more multicast data sets and one or more unicast data sets: This refers to the last DCI sent by the network device when scheduling multiple data sets, or one or more multicast data sets and one or more unicast data sets, which is also the last DCI received by the UE. For example, ... Figure 6 As shown, the network device schedules multiple data, and the last DCI received by the UE is DCI#5. Therefore, the last DCI corresponding to the multiple data is DCI#5.

[0206] Currently, for unicast scheduling services, when multiple HARQ-ACK messages with the same priority exist within the same time unit, the terminal device combines these messages into a single HARQ-ACK codebook and feeds back the codebook using PUCCH resources determined by the PUCCH configuration information corresponding to these messages. When two HARQ-ACK messages with different priorities exist, the terminal device combines them into two separate codebooks with different priorities and feeds back two codebooks, or the codebook with the higher priority, based on the two PUCCH resources determined by the two different PUCCH configuration information corresponding to the two HARQ-ACK messages. In other words, the number of priorities for HARQ-ACK messages is bound to the number of HARQ-ACK codebooks and the number of PUCCH configuration information entries. That is, one PUCCH configuration information corresponds to the priority of one HARQ-ACK information, corresponds to one HARQ-ACK codebook, and corresponds to sending one PUCCH (also known as sending one uplink control information, the same below); two PUCCH configuration information correspond to the priorities of two HARQ-ACK information, correspond to two HARQ-ACK codebooks, and correspond to sending two PUCCH (when the two PUCCH resources do not overlap).

[0207] In communication systems such as 5G, a HARQ-ACK feedback mechanism is introduced into multicast services to improve data transmission efficiency. This requires network devices to configure PUCCH configuration information for multicast and unicast services separately for terminal devices. However, within the same time unit, if the HARQ-ACK information for multicast and unicast services has the same priority, the priority of the number of HARQ-ACK messages no longer has the aforementioned binding relationship with the number of PUCCH configuration messages. This causes the terminal device to send HARQ-ACK information for both multicast and unicast services, thus affecting the efficiency of HARQ-ACK feedback.

[0208] This application provides an uplink control information transmission method 100. In the uplink control information transmission method 100, a terminal device acquires first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and second PUCCH configuration information corresponding to unicast data; receives multiple data from a network device, including one or more multicast data and one or more unicast data; first hybrid automatic repeat request-acknowledgement (HARQ-ACK) information corresponding to one or more multicast data and second HARQ-ACK information corresponding to one or more unicast data have the same priority and need to be fed back within the same time unit; then, based on the first or second PUCCH configuration information, a PUCCH resource is determined; finally, uplink control information is sent to the network device on the PUCCH resource; the uplink control information includes first HARQ-ACK information and second HARQ-ACK information. It can be seen that the terminal device, based on the principle of equal priority for HARQ-ACK information, feeds back the first and second HARQ-ACK information on the PUCCH resource determined according to the first or second PUCCH configuration information.

[0209] This application embodiment also provides an uplink control information transmission method 200. Compared with the uplink control information transmission method 100, in the uplink control information transmission method 200, the terminal device sends at least one of a first uplink control information and a second uplink control information based on a first PUCCH resource determined according to a first PUCCH configuration information and a second PUCCH resource determined according to a second PUCCH configuration information. The first uplink control information includes first HARQ-ACK information, and the second uplink control information includes second HARQ-ACK information. It can be seen that, based on the principle that the first PUCCH configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data are different, the terminal device feeds back at least one of the first and second HARQ-ACK information on the first and second PUCCH resources.

[0210] This application also provides an uplink control information transmission method 300. Compared with uplink control information transmission methods 100 and 200, in uplink control information transmission method 300, when the terminal device configures the first PUCCH configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data, it does not expect the first HARQ-ACK information corresponding to multicast data and the second HARQ-ACK information corresponding to unicast data to have the same priority. Therefore, when the network device configures the first PUCCH configuration information and the second PUCCH configuration information for the terminal device, the first HARQ-ACK information and the second HARQ-ACK information have different priorities. This allows the terminal device to feed back the first HARQ-ACK information and the second HARQ-ACK information on the first PUCCH resource determined according to the first PUCCH configuration information and the second PUCCH resource determined according to the second PUCCH configuration information, respectively, based on the principle of different priorities. This facilitates a consistent understanding of the HARQ-ACK feedback method between the network device and the terminal device, thereby improving the efficiency of HARQ-ACK feedback.

[0211] The embodiments of this application and their related implementations are described below with reference to the accompanying drawings. It will be understood that in the following methods, the steps of the network device can be implemented by different functional entities that make up the network device; in other words, the functional entities performing the steps of the network device can be located in different physical entities. For example, the actions of transmitting or receiving by the network device can be located in the radio frequency (RF) unit, radio remote unit (RRU), or active antenna unit (AAU) of the network device. The actions of processing by the network device can be located in the central unit (CU) of the network device, etc. This application does not impose any limitations on these aspects.

[0212] Please see Figure 7 , Figure 7 This is a flowchart illustrating an uplink control information transmission method 100 provided in an embodiment of this application. The uplink control information transmission method 100 is described from the perspective of interaction between network devices and terminal devices. The uplink control information transmission method 100 includes, but is not limited to, the following steps:

[0213] S101. The network device sends the first physical uplink control channel (PUCCH) configuration information corresponding to the multicast data and the second PUCCH configuration information corresponding to the unicast data to the terminal device.

[0214] The contents of the first PUCCH configuration information and the second PUCCH configuration information are detailed in the description of the PUCCH configuration information above, and will not be repeated here.

[0215] S102. The terminal device obtains the first PUCCH configuration information and the second PUCCH configuration information;

[0216] In one implementation, the terminal device obtains the first PUCCH configuration information and the second PUCCH configuration information, including: the terminal device receiving the first PUCCH configuration information and the second PUCCH configuration information from the network device. That is, the first PUCCH configuration information and the second PUCCH configuration information are sent to the terminal device by the network device.

[0217] After the terminal device obtains the first PUCCH configuration information and the second PUCCH configuration information, it can perform HARQ-ACK feedback on both the received multicast data and the received unicast data.

[0218] S103. The network device determines the PUCCH resource; the PUCCH resource belongs to the set of PUCCH resources configured in the first PUCCH configuration information, or belongs to the set of PUCCH resources configured in the second PUCCH configuration information;

[0219] S104. The network device sends multiple data to the terminal device, including one or more multicast data and one or more unicast data; the first HARQ-ACK information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data have the same priority and need to be fed back in the same time unit;

[0220] The priority of the first HARQ-ACK message corresponding to one or more multicast data items is configured for the one or more multicast data items in the DCI of the network device when scheduling the one or more multicast data items. Therefore, the priority of the first HARQ-ACK message corresponding to one or more multicast data items is the priority of the one or more multicast data items. Similarly, the priority of the second HARQ-ACK message corresponding to one or more unicast data items is configured for the one or more unicast data items in the DCI of the network device when scheduling the one or more unicast data items. Therefore, the priority of the second HARQ-ACK message corresponding to one or more unicast data items is the priority of the one or more unicast data items.

[0221] Therefore, the first HARQ-ACK message has the same priority as the second HARQ-ACK message, which can be understood as the network device configuring the same priority for one or more multicast data as it configuring the same priority for one or more unicast data.

[0222] The feedback time of the first HARQ-ACK message is determined based on the k1 value mentioned above in the first PUCCH configuration information, and the feedback time of the second HARQ-ACK message is determined based on the k1 value mentioned above in the second PUCCH configuration information. Therefore, the requirement that the first HARQ-ACK message and the second HARQ-ACK message be fed back within the same time unit means that the feedback time of the first HARQ-ACK message determined by the terminal device based on the k1 value in the first PUCCH configuration information and the feedback time of the second HARQ-ACK message determined by the k1 value in the second PUCCH configuration information are within the same time unit.

[0223] S105. The terminal device receives multiple data from the network device;

[0224] S106. The terminal device determines the PUCCH resources based on the first PUCCH configuration information or the second PUCCH configuration information;

[0225] In one optional implementation, before determining the PUCCH resource based on the first PUCCH configuration information or the second PUCCH configuration information, the terminal device also generates a HARQ-ACK codebook from the first HARQ-ACK information and the second HARQ-ACK information to feed back the first HARQ-ACK information corresponding to the one or more multicast data and the second HARQ-ACK information corresponding to the one or more unicast data.

[0226] When the terminal device is configured as a semi-static HARQ-ACK codebook, it generates a semi-static HARQ-ACK codebook from the first and second HARQ-ACK information. When the terminal device is configured as a dynamic HARQ-ACK codebook, it generates a dynamic HARQ-ACK codebook from the first and second HARQ-ACK information. The implementation methods for generating the semi-static or dynamic HARQ-ACK codebook from the first and second HARQ-ACK information are described above and will not be repeated here.

[0227] In addition, the terminal device can generate a HARQ-ACK codebook from the first HARQ-ACK information and the second HARQ-ACK information in the following two optional implementation methods:

[0228] In one optional implementation, the terminal device generates a HARQ-ACK codebook #1 from the first HARQ-ACK information, generates a HARQ-ACK codebook #2 from the second HARQ-ACK information, and then obtains a HARQ-ACK codebook #3. The HARQ-ACK codebook #3 can be constructed by concatenating the HARQ-ACK codebook #1 and the HARQ-ACK codebook #2. Therefore, the HARQ-ACK codebook #3 is the HARQ-ACK codebook that the terminal device needs to feed back to the network device. This implementation allows the network device to obtain the HARQ-ACK information corresponding to both multicast and unicast data when it receives the HARQ-ACK codebook #3.

[0229] In another optional implementation, the terminal device arranges the HARQ-ACK information corresponding to one or more unicast data and one or more multicast data according to their temporal positions to generate a HARQ-ACK codebook #3. In this implementation, the terminal device combines multiple HARQ-ACK information into a HARQ-ACK codebook #3 based on the temporal position of the PDSCH, which helps to reduce the complexity of the terminal device.

[0230] The following describes various optional implementation methods for the terminal device to determine PUCCH resources based on the first PUCCH configuration information or the second PUCCH configuration information:

[0231] In one optional implementation, the terminal device determines the PUCCH resource based on the first PUCCH configuration information or the second PUCCH configuration information, including: the terminal device determines the PUCCH resource based on the Physical Uplink Control Channel Resource Indicator (PRI) in the last downlink control information (DCI) corresponding to one or more multicast data and the first PUCCH configuration information, wherein the PUCCH resource belongs to the set of PUCCH resources configured in the first PUCCH configuration information.

[0232] Understandably, in this implementation, the terminal device determines a PUCCH resource set from multiple PUCCH resource sets in the first PUCCH configuration information based on the size of the generated HARQ-ACK codebook #3, and then determines the PUCCH resource from the determined PUCCH resource set based on the resource indicated by the PRI in the last DCI corresponding to one or more multicast data.

[0233] In other words, the terminal device uses the first PUCCH configuration information corresponding to the multicast data and the PRI in the last DCI corresponding to one or more multicast data to determine the PUCCH resource, so that the PUCCH resource belongs to the set of PUCCH resources configured in the first PUCCH configuration information.

[0234] For example, such as Figure 8 As shown, the network device schedules multiple multicast data and multiple unicast data for the UE in time units #1 and #2, and the UE determines that the first HARQ-ACK information corresponding to the multiple multicast data and the second HARQ-ACK information corresponding to the multiple unicast data must be fed back in time unit #N. The terminal device generates a HARQ-ACK codebook #3 based on the time domain positions of the unicast and multicast data, using the first and second HARQ-ACK information. Then, based on the size of the HARQ-ACK codebook #3, it determines the PUCCH resource set used for feeding back HARQ-ACK information as PUCCH resource set #2 from the multiple PUCCH resource sets in the first PUCCH configuration information. Then, based on the PRI in DCI #2, it determines a PUCCH resource in PUCCH resource set #2 to send the PUCCH. Therefore, the PUCCH resource determined by the terminal device belongs to the PUCCH resource set configured in the first PUCCH configuration information.

[0235] In another optional implementation, the terminal device determines the PUCCH resource based on the first PUCCH configuration information or the second PUCCH configuration information, including: the terminal device determines the PUCCH resource based on the Physical Uplink Control Channel Resource Indicator (PRI) in the last downlink control information (DCI) corresponding to one or more unicast data and the second PUCCH configuration information, wherein the PUCCH resource belongs to the set of PUCCH resources configured in the second PUCCH configuration information.

[0236] Understandably, in this implementation, the terminal device determines a PUCCH resource set from the multiple PUCCH resource sets in the second PUCCH configuration information based on the size of the generated HARQ-ACK codebook #3, and then determines the PUCCH resource from the determined PUCCH resource set based on the resource indicated by the PRI in the last DCI corresponding to one or more unicast data.

[0237] In other words, when determining PUCCH resources, the terminal device uses the second PUCCH configuration information corresponding to the unicast data and the PRI in the last DCI corresponding to one or more unicast data to determine the PUCCH resources, so that the determined PUCCH resources belong to the set of PUCCH resources configured in the second PUCCH configuration information.

[0238] For example, such as Figure 9As shown, the network device schedules multiple multicast data and multiple unicast data for the UE in time units #1 and #2, and the UE determines that the first HARQ-ACK information corresponding to the multiple multicast data and the second HARQ-ACK information corresponding to the multiple unicast data must be fed back in time unit #N. The terminal device generates a HARQ-ACK codebook #3 based on the time domain positions of the unicast and multicast data, using the first and second HARQ-ACK information. Then, based on the size of the HARQ-ACK codebook #3, it determines the PUCCH resource set used for feeding back HARQ-ACK information from the multiple PUCCH resource sets in the second PUCCH configuration information as PUCCH resource set #3. Then, based on the PRI in DCI #1, it determines the PUCCH resource in PUCCH resource set #3 to send the PUCCH. Therefore, the PUCCH resource determined by the terminal device belongs to the PUCCH resource set configured in the second PUCCH configuration information.

[0239] In another optional implementation, the terminal device determines the PUCCH resource based on the first PUCCH configuration information or the second PUCCH configuration information, including: the terminal device determines the PUCCH resource based on the Physical Uplink Control Channel Resource Indicator (PRI) of the last downlink control information (DCI) corresponding to multiple data, and the PUCCH configuration information corresponding to the last DCI; the PUCCH resource belongs to the set of PUCCH resources configured in the first PUCCH configuration information, or belongs to the set of PUCCH resources configured in the second PUCCH configuration information.

[0240] Understandably, in this embodiment, the terminal device determines a PUCCH resource set from the multiple PUCCH resource sets in the PUCCH configuration information corresponding to the last DCI of multiple data based on the size of the generated HARQ-ACK codebook #3, and then determines the PUCCH resource from the determined PUCCH resource set based on the resource indicated by PRI in the last DCI.

[0241] The PUCCH configuration information corresponding to the last DCI mentioned above refers to the PUCCH configuration information corresponding to the data scheduled by the last DCI. When the last DCI schedules multicast data, its corresponding PUCCH configuration information is the first PUCCH configuration information, and the determined PUCCH resource belongs to the PUCCH resource set configured in the first PUCCH configuration information; when the last DCI schedules unicast data, its corresponding PUCCH configuration information is the second PUCCH configuration information, and the determined PUCCH resource belongs to the PUCCH resource set configured in the second PUCCH configuration information.

[0242] For example, as mentioned above Figure 6 The last DCI#5 scheduled in the middle is PDSCH#5, which is multicast data. Therefore, the PUCCH configuration information corresponding to this DCI#5 is the first PUCCH configuration information, and the determined PUCCH resource belongs to the set of PUCCH resources configured in the first PUCCH configuration information.

[0243] In other words, when determining PUCCH resources, the terminal device uses the PUCCH configuration information corresponding to the last DCI of multiple data correspondences and the PRI in that DCI to determine it. Thus, the terminal device can flexibly determine the PUCCH resources that feed back HARQ-ACK information based on the DCI corresponding to the last scheduled data.

[0244] For example, as mentioned above Figure 8 As shown, multiple data points correspond to the last DCI, which is DCI#2, and the PDSCH scheduled by DCI#2 is a multicast PDSCH. Therefore, the terminal device determines the PUCCH resource set #2 in the first PUCCH configuration information based on the size of the HARQ-ACK codebook #3, and then determines the PUCCH resource as PUCCH in the determined PUCCH resource set #2 based on the PRI in DCI#2.

[0245] In another optional implementation, the terminal device determines the PUCCH resource based on the first PUCCH configuration information or the second PUCCH configuration information, including: the terminal device receiving first indication information from the network device; the first indication information instructing the terminal device to determine the PUCCH resource based on the first PUCCH configuration information or the second PUCCH configuration information; when the first indication information instructs the terminal device to determine the PUCCH resource based on the first PUCCH configuration information, the terminal device determines the PUCCH resource based on the Physical Uplink Control Channel Resource Indication (PRI) in the last downlink control information (DCI) corresponding to one or more multicast data and the first PUCCH configuration information; the PUCCH resource belongs to the set of PUCCH resources configured in the first PUCCH configuration information; when the first indication information instructs the terminal device to determine the PUCCH resource based on the second PUCCH configuration information, the terminal device determines the PUCCH resource based on the Physical Uplink Control Channel Resource Indication (PRI) in the last downlink control information (DCI) corresponding to one or more unicast data and the second PUCCH configuration information; the PUCCH resource belongs to the set of PUCCH resources configured in the second PUCCH configuration information.

[0246] The first indication information can be carried in the radio resource control (RRC) signaling. That is, the terminal device determines, through the received RRC signaling, whether the PUCCH configuration information used by the terminal device when determining PUCCH resources is the first PUCCH configuration information or the second PUCCH configuration information.

[0247] For example, if the terminal device determines the first indication information through RRC signaling, instructing the terminal device to determine the PUCCH resource according to the second PUCCH configuration information, then the terminal device determines a PUCCH resource set based on the size of the HARQ-ACK codebook #3 mentioned above, and then determines the PUCCH resource in the determined PUCCH resource set according to the PRI in the last DCI corresponding to one or more unicast data.

[0248] S107. The terminal device sends uplink control information to the network device on the PUCCH resource; the uplink control information includes first HARQ-ACK information and second HARQ-ACK information;

[0249] Specifically, when a terminal device sends uplink control information to a network device on a PUCCH resource, it means that the terminal device sends a PUCCH to the network device on a determined PUCCH resource. This PUCCH carries the first HARQ-ACK information and the second HARQ-ACK information. It can also be understood that this PUCCH carries the HARQ-ACK codebook #1 and HARQ-ACK codebook #2 generated based on the first HARQ-ACK information and the second HARQ-ACK information, respectively. That is, this PUCCH carries the HARQ-ACK codebook #3.

[0250] When a terminal device sends uplink control information to a network device on PUCCH resources, it can also be understood that the terminal device encodes HARQ-ACK codebook #3, that is, it jointly encodes HARQ-ACK codebook #1 and HARQ-ACK codebook #2, and then sends the HARQ-ACK codebook #3 on PUCCH resources.

[0251] In other words, by sending uplink control information, the terminal device sends back the first HARQ-ACK information for one or more multicast data and the second HARQ-ACK information for one or more unicast data to the network device, thereby improving the transmission efficiency of the one or more multicast data and one or more unicast data.

[0252] S108. The network device receives uplink control information from the terminal device on the PUCCH resource.

[0253] As can be seen, in this embodiment of the application, when the network device configures the terminal device with the first PUCCH configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data, and the first HARQ-ACK information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data received by the terminal device have the same priority and need to be fed back in the same time unit, the terminal device can feed back the first HARQ-ACK information and the second HARQ-ACK information to the network device on the PUCCH resources determined according to the first PUCCH configuration information or the second PUCCH configuration information, based on the principle that the first HARQ-ACK information and the second HARQ-ACK information have the same priority, thereby realizing the feedback of one or more multicast data and one or more unicast data, which is conducive to improving the data transmission efficiency.

[0254] In addition, in this embodiment, the network device may also send a PRI to the terminal device to indicate the PUCCH resource determined by the network device. The following describes several optional implementations of the network device indicating PUCCH resources to the terminal device via PRI:

[0255] In one optional implementation, the network device sends a Physical Uplink Control Channel Resource Indicator (PRI) in the DCI corresponding to the last multicast data. The PRI indicates a PUCCH resource, which is one of the PUCCH resource sets configured in the first PUCCH configuration information.

[0256] In other words, the network device informs the terminal device through the DCI corresponding to the last multicast data in one or more multicast data that the PUCCH resource is one of the PUCCH resource sets configured in the first PUCCH configuration information. Thus, when the terminal device determines the PUCCH resource based on the PRI, the determined PUCCH resource is one of the PUCCH resource sets configured in the first PUCCH configuration information.

[0257] In another optional implementation, the network device sends a Physical Uplink Control Channel Resource Indicator (PRI) in the DCI corresponding to the last unicast data. The PRI indicates a PUCCH resource, which is one of the PUCCH resource sets configured in the second PUCCH configuration information.

[0258] In other words, the network device informs the terminal device through the DCI corresponding to the last unicast data in one or more unicast data that the PUCCH resource is one of the PUCCH resource sets configured in the second PUCCH configuration information. Thus, when the terminal device determines the PUCCH resource based on the PRI, the determined PUCCH resource is one of the PUCCH resource sets configured in the second PUCCH configuration information.

[0259] In another optional implementation, the network device sends a Physical Uplink Control Channel Resource Indicator (PRI) in the last downlink control information (DCI) corresponding to multiple data. The PRI indicates a PUCCH resource that belongs to the PUCCH resource set configured in the first PUCCH configuration information, or the PUCCH resource belongs to the PUCCH resource set configured in the second PUCCH configuration information.

[0260] In other words, the network device informs the terminal device, through the last DCI corresponding to multiple data points, that the PUCCH resource belongs to the PUCCH resource set configured in the first PUCCH configuration information or the second PUCCH configuration information. When the last DCI corresponding to multiple data points schedules multicast data, the network device informs the terminal device that the PUCCH resource belongs to the PUCCH resource set configured in the first PUCCH configuration information; when the last DCI corresponding to multiple data points schedules unicast data, the network device informs the terminal device that the PUCCH resource belongs to the PUCCH resource set configured in the second PUCCH configuration information. Therefore, the terminal device can determine the PUCCH resource from the multiple PUCCH resource sets in the first or second PUCCH configuration information based on the PUCCH resource indicated by the PRI.

[0261] In another optional implementation, the network device sends a first indication information to the terminal device; the first indication information is used to indicate that the PUCCH resource belongs to the PUCCH resource set configured by the first PUCCH configuration information or to indicate that the PUCCH resource belongs to the PUCCH resource set configured by the second PUCCH configuration information; when the first indication information indicates that the PUCCH resource belongs to the PUCCH resource set configured by the first PUCCH configuration information, the network device sends a Physical Uplink Control Channel Resource Indicator (PRI) in the last DCI corresponding to one or more multicast data, the PRI indicating the PUCCH resource; when the first indication information indicates that the PUCCH resource belongs to the PUCCH resource set configured by the second PUCCH configuration information, the network device sends a Physical Uplink Control Channel Resource Indicator (PRI) in the last DCI corresponding to one or more unicast data, the PRI indicating the PUCCH resource.

[0262] In other words, the network device sends a first indication message to the terminal device regarding PUCCH resources. Then, when the first indication message indicates that the PUCCH resource belongs to the PUCCH resource set configured by the first PUCCH configuration information, the network device informs the terminal device of the PUCCH resource through the last DCI corresponding to one or more multicast data; when the first indication message indicates that the PUCCH resource belongs to the PUCCH resource set configured by the first PUCCH configuration information, the network device informs the terminal device of the PUCCH resource through the last DCI corresponding to one or more unicast data, so that the terminal device can determine the PUCCH resource based on the corresponding PUCCH configuration information and PRI.

[0263] It can be understood that the numbering of steps S101 to S103 above does not limit the execution order of these steps, and any logically consistent step is within the scope of protection of this application. For example, step S103 can precede step S102, or even S101.

[0264] This application also proposes an uplink control information transmission method 200. Figure 10 A flowchart illustrating the uplink control information transmission method 200.

[0265] S201. The network device sends the first physical uplink control channel (PUCCH) configuration information corresponding to the multicast data and the second PUCCH configuration information corresponding to the unicast data to the terminal device.

[0266] S202. The terminal device obtains the first PUCCH configuration information and the second PUCCH configuration information;

[0267] S203. The network device determines the first PUCCH resource and the second PUCCH resource; the first PUCCH resource belongs to the set of PUCCH resources configured by the first PUCCH configuration information; the second PUCCH resource belongs to the set of PUCCH resources configured by the second PUCCH configuration information.

[0268] S204. The network device sends multiple data to the terminal device, including one or more multicast data and one or more unicast data; the first HARQ-ACK information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data have the same priority and need to be fed back in the same time unit;

[0269] S205. The terminal device receives multiple data from the network device;

[0270] The implementation methods of S201-S205 are the same as those of S101-S105 described above, and will not be repeated here.

[0271] S206. The terminal device determines the first PUCCH resource based on the first PUCCH configuration information, and determines the second PUCCH resource based on the second PUCCH configuration information;

[0272] In one optional implementation, before the terminal device determines the first PUCCH resource based on the first PUCCH configuration information and the second PUCCH resource based on the second PUCCH configuration information, the terminal device generates a HARQ-ACK codebook #1 from the first HARQ-ACK information corresponding to one or more multicast data, and / or generates a HARQ-ACK codebook #2 from the second HARQ-ACK information corresponding to one or more unicast data. This allows the terminal device to respond to one or more multicast data by feeding back the HARQ-ACK codebook #1, and to respond to one or more unicast data by feeding back the HARQ-ACK codebook #2.

[0273] Therefore, the terminal device determining the first PUCCH resource based on the first PUCCH configuration information means that the terminal device determines a PUCCH resource set from the multiple PUCCH resource sets configured in the first PUCCH configuration information based on the size of the HARQ-ACK codebook #1. Alternatively, the terminal device can determine a PUCCH resource set configured in the first configuration information based on the size of the first HARQ-ACK information. Then, the terminal device determines the first PUCCH resource from the determined PUCCH resource set based on the PRI in the last DCI corresponding to one or more multicast data. It is evident that the first PUCCH resource determined by the terminal device belongs to the PUCCH resource set in the first PUCCH configuration information.

[0274] Similarly, when the terminal device determines the second PUCCH resource based on the second PUCCH configuration information, it means that the terminal device determines a PUCCH resource set from the multiple PUCCH resource sets configured in the second PUCCH configuration information based on the size of the HARQ-ACK codebook #2. In other words, the terminal device can determine a PUCCH resource set configured in the second configuration information based on the size of the second HARQ-ACK information. Then, the terminal device determines the second PUCCH resource from the determined PUCCH resource set based on the PRI in the last DCI corresponding to one or more unicast data. Therefore, the second PUCCH resource determined by the terminal device belongs to the PUCCH resource set in the second PUCCH configuration information.

[0275] For example, the terminal device can generate HARQ-ACK codebook #1 and HARQ-ACK codebook #2 from the first HARQ-ACK information and the second HARQ-ACK information, respectively. Then, based on the size of HARQ-ACK codebook #1, it determines the PUCCH resource set as PUCCH resource set #1 from the multiple PUCCH resource sets configured in the first PUCCH configuration information. Similarly, based on the size of HARQ-ACK codebook #2, it determines the PUCCH resource set as PUCCH resource set #3 from the multiple PUCCH resource sets configured in the second PUCCH configuration information. Finally, based on the PRI corresponding to one or more multicast data, it determines the first PUCCH resource from PUCCH resource set #1. Figure 11a The PUCCH#1 shown, and the second PUCCH resource determined in PUCCH resource set #3 based on the PRI corresponding to one or more unicast data, are... Figure 11a PUCCH#2 is shown.

[0276] S207. The terminal device sends at least one of a first uplink control information and a second uplink control information to the network device based on the first PUCCH resource and the second PUCCH resource; the first uplink control information includes a first HARQ-ACK information; the second uplink control information includes a second HARQ-ACK information;

[0277] In other words, the terminal device can send back first HARQ-ACK information and second HARQ-ACK information to the network device based on the first PUCCH resource and the second PUCCH resource, or send back one of the first HARQ-ACK information and the second HARQ-ACK information to the network device.

[0278] When the terminal device sends the first uplink control information to the network device on the first PUCCH resource, it means that the terminal device independently encodes the aforementioned HARQ-ACK codebook #1 and then sends the HARQ-ACK codebook #1 to the network device on the first PUCCH resource; when the network device sends the second uplink control information to the network device on the second PUCCH resource, it means that the terminal device independently encodes the aforementioned HARQ-ACK codebook #2 and then sends the HARQ-ACK codebook #2 to the network device on the second PUCCH resource.

[0279] The following details several optional implementations of a terminal device sending at least one of a first uplink control message and a second uplink control message to a network device based on a first PUCCH resource and a second PUCCH resource:

[0280] In one optional implementation, when the first PUCCH resource and the second PUCCH resource do not overlap in the time domain, the terminal device sends first uplink control information to the network device on the first PUCCH resource and sends second uplink control information to the network device on the second PUCCH resource. Here, the first PUCCH resource and the second PUCCH resource not overlapping in the time domain means that the first PUCCH resource and the second PUCCH resource occupy completely different symbols in the same time unit.

[0281] For example, the first PUCCH resource and the second PUCCH resource determined by the terminal device are as follows: Figure 11a As shown, the first PUCCH resource is PUCCH#1, and the second PUCCH resource is PUCCH#2. From Figure 11a It can be seen that PUCCH#1 and PUCCH#2 do not overlap in the time domain. Therefore, the terminal device sends the first uplink control information on PUCCH#1 to provide feedback on the first HARQ-ACK information, and sends the second uplink control information on PUCCH#2 to provide feedback on the second HARQ-ACK information.

[0282] As can be seen, in this embodiment, when the first PUCCH resource and the second PUCCH resource do not overlap in the time domain, the terminal device feeds back the first HARQ-ACK information and the second HARQ-ACK information on the first PUCCH resource and the second PUCCH resource, respectively.

[0283] In another optional implementation, when the first PUCCH resource and the second PUCCH resource overlap in the time domain, the terminal device sends first uplink control information to the network device on the first PUCCH resource; or, sends second uplink control information to the network device on the second PUCCH resource. Wherein, when the first PUCCH resource and the second PUCCH resource overlap in the time domain, it means that the first PUCCH resource and the second PUCCH resource have the same symbols in the same time slot. For example, if the first PUCCH resource occupies symbols 4-8 and the second PUCCH resource occupies symbols 6-10 in the same time slot, then both the first PUCCH resource and the second PUCCH resource occupy symbols 6, 7, and 8, meaning that the first PUCCH resource and the second PUCCH resource have the same symbols 6, 7, and 8.

[0284] In other words, when the first PUCCH resource and the second PUCCH resource overlap in the time domain, the terminal device feeds back one of the first HARQ-ACK information and the second HARQ-ACK information to the network device to ensure that one of the HARQ-ACK information is fed back correctly.

[0285] Furthermore, in one optional implementation, when the first PUCCH resource and the second PUCCH resource overlap in the time domain, if the number of bits of the first uplink control information is greater than the number of bits of the second uplink control information, the terminal device sends the first uplink control information on the first PUCCH resource; or, if the number of bits of the second uplink control information is greater than or equal to the number of bits of the first uplink control information, the terminal device sends the second uplink control information on the second PUCCH resource.

[0286] In other words, when the first PUCCH resource and the second PUCCH resource overlap in the time domain, the terminal device sends the uplink control information with the larger number of bits in the first uplink control information and the second uplink control information to the network device to ensure that the HARQ-ACK information with a larger amount of HARQ-ACK information is correctly fed back, thereby helping to improve the transmission efficiency of large amounts of data.

[0287] It is understandable that when the number of bits in the first uplink control information and the second uplink control information are the same, it can be agreed to send either the first uplink control information or the second uplink control information. This application does not impose any restrictions.

[0288] For example, such as Figure 11b As shown, the first PUCCH resource is PUCCH#1, and the second PUCCH resource is PUCCH#2. From Figure 11b It can be seen that PUCCH#1 and PUCCH#2 overlap in the time domain. If the number of bits of the first uplink control information is 16 bits and the number of bits of the second uplink control information is 7 bits, then the terminal device sends the first uplink control information on PUCCH#1 to feed back the first HARQ-ACK information.

[0289] In another optional implementation, when the first PUCCH resource and the second PUCCH resource overlap in the time domain, if the number of bits of the first uplink control information is less than the number of bits of the second uplink control information, the terminal device sends the first uplink control information on the first PUCCH resource; or, if the number of bits of the second uplink control information is less than or equal to the number of bits of the first uplink control information, the terminal device sends the second uplink control information on the second PUCCH resource.

[0290] In other words, when the first PUCCH resource and the second PUCCH resource overlap in the time domain, the terminal device sends the uplink control information with the smaller number of bits in the first uplink control information and the second uplink control information to the network device. This ensures that the HARQ-ACK information with a smaller number of bits is correctly fed back, which helps to improve the transmission efficiency of small data and at the same time reduces the PUCCH overhead occupied by the HARQ-ACK information and reduces interference to other terminal devices.

[0291] For example, the first PUCCH resource and the second PUCCH resource are as described above. Figure 11b As shown, if the first uplink control information has 9 bits and the second uplink control information has 6 bits, the terminal device sends the second uplink control information on PUCCH#2 to provide feedback on the second HARQ-ACK information.

[0292] In another optional implementation, when the first PUCCH resource and the second PUCCH resource overlap in the time domain, if the time domain position of the first PUCCH resource is earlier than the time domain position of the second PUCCH resource, the terminal device sends first uplink control information on the first PUCCH resource; or, if the time domain position of the second PUCCH resource is earlier than the time domain position of the first PUCCH resource, the terminal device sends second uplink control information on the second PUCCH resource. Here, "the time domain position of the first PUCCH resource is earlier than the time domain position of the second PUCCH resource" means that the time domain start position (or end position) of the first PUCCH resource is earlier than the time domain start position (or end position) of the second PUCCH resource. Similarly, "the time domain position of the second PUCCH resource is earlier than the time domain position of the first PUCCH resource" means that the time domain start position (or end position) of the second PUCCH resource is earlier than the time domain start position (or end position) of the first PUCCH resource.

[0293] In other words, when the first PUCCH resource and the second PUCCH resource overlap in the time domain, the terminal device feeds back the corresponding HARQ-ACK information on the PUCCH resource that is earlier in the time domain, so as to ensure that the HARQ-ACK information carried on the PUCCH resource that is earlier in the time domain is correctly fed back.

[0294] For example, the first PUCCH resource and the second PUCCH resource are as described above. Figure 11b As shown. From Figure 11b It can be seen that the time domain position of PUCCH#1 is before the time domain position of PUCCH#2. Therefore, the terminal device sends the first uplink control information to the network device on PUCCH#1 to feed back the first HARQ-ACK information.

[0295] In another optional implementation, when the first PUCCH resource and the second PUCCH resource overlap in the time domain, if the first PUCCH resource is configured to be repeatedly transmitted, the terminal device transmits the second uplink control information on the second PUCCH resource; or, if the second PUCCH resource is configured to be repeatedly transmitted, the terminal device transmits the first uplink control information on the first PUCCH resource.

[0296] Specifically, configuring the first PUCCH resource for repeated transmission means that the first PUCCH resource is not only configured to be transmitted in the time unit where the first PUCCH resource is located, but also configured to be transmitted at the same time domain position in other time units (i.e., occupying the same symbol position within the slot). Alternatively, configuring the first PUCCH resource for repeated transmission means that the first PUCCH resource is configured with "nrofSlots," indicating that within one or more slots represented by nrofSlots, a PUCCH carrying the first HARQ-ACK information is transmitted at the position of the first PUCCH resource; that is, the first uplink control information is transmitted at the position of the first PUCCH resource.

[0297] Similarly, configuring the second PUCCH resource for repeated transmission means that the second PUCCH resource is not only configured to be transmitted in the time unit where the second PUCCH resource is located, but also configured to be transmitted at the same time domain position in other time units. This can also be understood as the second PUCCH resource being configured for repeated transmission having "nrofSlots," indicating that within the slot represented by nrofSlots, a PUCCH carrying the second HARQ-ACK information is transmitted at the position of the second PUCCH resource; that is, the second uplink control information is transmitted at the position of the second PUCCH resource.

[0298] Since PUCCH resources configured for repeated transmission can also be transmitted at the same time domain location in other time units, the terminal device can discard a PUCCH resource if it is determined to be configured for repeated transmission. PUCCH resources not configured for repeated transmission, however, can only be transmitted within the time unit in which they are located. Therefore, the terminal device can send uplink control signals on PUCCH resources not configured for repeated transmission to ensure that the HARQ-ACK information carried on these resources is correctly fed back.

[0299] For example, such as Figure 11c As shown, the first PUCCH resource is PUCCH#1, and the second PUCCH resource is PUCCH#2. From Figure 11c It can be seen that, in addition to being configured to be transmitted in time unit #1, PUCCH#2 can also be transmitted in time units #2 and #3 at the same time domain position as in time unit #1. Therefore, to ensure that the HARQ-ACK information carried on PUCCH#1 is fed back, the terminal device sends the first uplink control information on PUCCH#1 at this time.

[0300] S208. The network device receives at least one of a first uplink control information and a second uplink control information from the terminal device based on the first PUCCH resource and the second PUCCH resource.

[0301] The implementation where the network device receives at least one of the first uplink control information and the second uplink control information from the terminal device based on the first PUCCH resource and the second PUCCH resource corresponds to the implementation in S206 above where the terminal device sends at least one of the first uplink control information and the second uplink control information to the network device based on the first PUCCH resource and the second PUCCH resource. The following describes several corresponding implementations of the network device receiving at least one of the first uplink control information and the second uplink control information from the terminal device based on the first PUCCH resource and the second PUCCH resource:

[0302] In one optional implementation, the network device receives at least one of a first uplink control information and a second uplink control information from a terminal device based on a first PUCCH resource and a second PUCCH resource. This includes: the first PUCCH resource and the second PUCCH resource do not overlap; the network device receives the first uplink control information from the terminal device on the first PUCCH resource and receives the second uplink control information from the terminal device on the second PUCCH resource. Therefore, when the first PUCCH resource and the second PUCCH resource do not overlap, the network device receives the first uplink control information and the second uplink control information sent by the terminal device.

[0303] In another optional implementation, the network device receives at least one of a first uplink control information and a second uplink control information from the terminal device based on a first PUCCH resource and a second PUCCH resource. This includes: the first PUCCH resource and the second PUCCH resource overlap, and the network device receives the first uplink control information from the terminal device on the first PUCCH resource; or, the network device receives the second uplink control information from the terminal device on the second PUCCH resource. Therefore, when the first PUCCH resource and the second PUCCH resource overlap, the network device receives either the first uplink control information or the second uplink control information sent by the terminal device.

[0304] In one optional implementation, the network device receives first uplink control information from the terminal device on a first PUCCH resource; or, receives second uplink control information from the terminal device on a second PUCCH resource, including: the network device receiving the first uplink control information from the terminal device on the first PUCCH resource, wherein the number of bits in the first uplink control information is greater than the number of bits in the second uplink control information; or, the network device receiving the second uplink control information from the terminal device on the second PUCCH resource, wherein the number of bits in the second uplink control information is greater than or equal to the number of bits in the first uplink control information.

[0305] It is evident that when the first PUCCH resource and the second PUCCH resource overlap, the network device receives the uplink control information with the larger number of bits from the first uplink control information and the second uplink control information sent by the terminal device.

[0306] In another optional implementation, the network device receives first uplink control information from the terminal device on a first PUCCH resource; or, receives second uplink control information from the terminal device on a second PUCCH resource, including: the network device receiving the first uplink control information from the terminal device on the first PUCCH resource, wherein the number of bits in the first uplink control information is less than the number of bits in the second uplink control information; or, the network device receiving the second uplink control information from the terminal device on the second PUCCH resource, wherein the number of bits in the second uplink control information is less than or equal to the number of bits in the first uplink control information.

[0307] It is evident that when the first PUCCH resource and the second PUCCH resource overlap, the network device receives the uplink control information with the smaller number of bits between the first uplink control information and the second uplink control information sent by the terminal device.

[0308] In another optional implementation, the network device receives first uplink control information from the terminal device on a first PUCCH resource; or, receives second uplink control information from the terminal device on a second PUCCH resource, including: the network device receiving the first uplink control information from the terminal device on the first PUCCH resource, wherein the time domain position of the first PUCCH resource is before the time domain position of the second PUCCH resource; or, the network device receiving the second uplink control information on the second PUCCH resource, wherein the time domain position of the second PUCCH resource is before the time domain position of the first PUCCH resource.

[0309] It is evident that when the first PUCCH resource and the second PUCCH resource overlap, the network device receives the HARQ-ACK information fed back by the terminal device, which is carried on the PUCCH resource that is earlier in the time domain.

[0310] In another optional implementation, the network device receives first uplink control information from the terminal device on a first PUCCH resource; or, receives second uplink control information from the terminal device on a second PUCCH resource, including: the network device receiving the second uplink control information from the terminal device on the second PUCCH resource, and the first PUCCH resource being configured for repeated transmission; or, the network device receiving the first uplink control information on the first PUCCH resource, and the second PUCCH resource being configured for repeated transmission.

[0311] It is evident that when the first PUCCH resource and the second PUCCH resource overlap, the network device receives the HARQ-ACK information fed back by the terminal device, which is carried on the PUCCH resource that is not configured to be repeatedly transmitted.

[0312] As can be seen, in this embodiment of the application, when the network device configures the terminal device with the first PUCCH configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data, and the first HARQ-ACK information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data received by the terminal device have the same priority and need to be fed back in the same time unit, the terminal device can send at least one of the first uplink control information and the second uplink control information to the network device according to the first PUCCH configuration information or the second PUCCH configuration information, so as to ensure that at least one of the first HARQ-ACK information and the second HARQ-ACK information is fed back, thereby improving the efficiency of data transmission.

[0313] It can be understood that the numbering of steps S201 to S203 above does not limit the execution order of these steps, and any logically consistent step is within the scope of protection of this application. For example, step S203 can precede step S202, or even S201.

[0314] In this embodiment, when the terminal device obtains the first PUCCH configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data, and the first HARQ-ACK information corresponding to one or more received multicast data and the second HARQ-ACK information corresponding to unicast data belong to the same priority and need to be fed back within the same time unit, whether to use the HARQ-ACK feedback method in the uplink control information transmission method 100 or the HARQ-ACK feedback method in the uplink control information transmission method 200 to feed back the first HARQ-ACK information and the second HARQ-ACK information is indicated by the network device to the terminal device. This ensures that the terminal device and the network device have a consistent understanding of the HARQ-ACK feedback method, thereby improving the transmission efficiency of HARQ-ACK information. Optionally, the network device can instruct the terminal device on the feedback method for HARQ-ACK information in this scenario through RRC signaling.

[0315] In other words, if the network device instructs the terminal device to generate a HARQ-ACK codebook from the first HARQ-ACK information and the second HARQ-ACK information, the terminal device will use the method in uplink control information transmission method 100 to feed back the first HARQ-ACK information and the second HARQ-ACK information on the PUCCH resources determined according to the first PUCCH configuration information or the second PUCCH configuration information; if the network device instructs the terminal device to generate corresponding HARQ-ACK codebooks from the first HARQ-ACK information and the second HARQ-ACK information respectively, the terminal device will use the method in uplink control information transmission method 200 to feed back at least one of the first HARQ-ACK information and the second HARQ-ACK information on the first PUCCH resources determined according to the first PUCCH configuration information and the second PUCCH resources determined according to the second PUCCH configuration information.

[0316] In one implementation, when a network device configures a second PUCCH configuration information corresponding to unicast data for a terminal device, but does not configure a first PUCCH configuration information corresponding to multicast data, and schedules one or more multicast data and one or more unicast data for the terminal device, and the first HARQ-ACK information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data have the same priority and need to be fed back within the same time unit, the terminal device combines the first HARQ-ACK information and the second HARQ-ACK information into a HARQ-ACK codebook #4. Then, based on the size of the HARQ-ACK codebook #4, it determines a PUCCH resource set from the multiple PUCCH resource sets in the second PUCCH configuration information. Then, based on the PRI indication in the last DCI corresponding to one or more multicast data and one or more unicast data, it determines a third PUCCH resource from the determined PUCCH resource set. Finally, it feeds back the HARQ-ACK codebook #4 to the network device on the third PUCCH resource to realize the feedback of the first HARQ-ACK information and the second HARQ-ACK information. Specifically, when the network device configures the terminal device with a semi-static codebook mode, the terminal device combines the first HARQ-ACK information and the second HARQ-ACK information into HARQ-ACK codebook #4 according to the semi-static codebook generation method described above. When the network device configures the terminal device with a dynamic codebook mode, the terminal device generates HARQ-ACK codebook #1 and HARQ-ACK codebook #2 respectively from the first HARQ-ACK information and the second HARQ-ACK information according to the dynamic codebook generation method described above, and then concatenates codebook #1 and codebook #2 to form codebook #4. It is understood that the PRI in the last DCI corresponding to one or more multicast data and one or more unicast data can be replaced with the PRI in the last unicast DCI, or it can be replaced with the PRI in other DCIs that schedule the unicast data, such as the PRI in the first DCI of one or more unicast data, or the PRI in the DCI of the first unicast data of one or more unicast data, or the PRI in the DCI of the last unicast data of one or more unicast data, or the PRI in other DCIs. Similarly, the last DCI corresponding to one or more multicast data and one or more unicast data can be replaced with the PRI in the multicast DCI, or it can be replaced with the PRI in other DCIs that schedule the multicast data, such as the PRI in the first DCI of one or more multicast data, or the PRI in the DCI of the first multicast data of one or more multicast data, or the PRI in the DCI of the last multicast data of one or more multicast data, or the PRI in other DCIs.It is understandable that PRI in DCI can also be replaced with other indicator fields to indicate PUCCH resources. This application does not limit this.

[0317] In another implementation, when the network device terminal device is configured with first PUCCH configuration information corresponding to multicast data and second PUCCH configuration information corresponding to unicast data, and schedules one or more multicast data and one or more unicast data to the terminal device, and the first HARQ-ACK information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data belong to the same priority and need to be fed back in the same time unit, the terminal device feeds back the first HARQ-ACK information and the second HARQ-ACK information to the network device according to the implementation method of uplink control information transmission method 200, which will not be described in detail here.

[0318] In one optional implementation, when there is only one first PUCCH configuration information, the priority corresponding to the first PUCCH configuration information is high priority. The priority corresponding to the first PUCCH configuration information can be understood as the priority of the multicast data corresponding to the first PUCCH configuration information, or as the priority of the HARQ-ACK information corresponding to the first PUCCH configuration information. For example, when a network device schedules multicast data, if the priority of the multicast data is configured as high priority in the DCI for scheduling multicast data, then the priority corresponding to the first PUCCH configuration information is also high priority.

[0319] In other words, when a network device configures the first PUCCH for multicast data to be one, the network device configures the multicast data with a high priority, instead of the default low priority.

[0320] In another optional implementation, when there are two PUCCH configuration messages, one of the PUCCH configuration messages has a higher priority, and the other has a lower priority. In other words, when the network device configures two PUCCH configuration messages for the multicast data of the terminal device, the two PUCCH configuration messages have different priorities.

[0321] In one optional implementation, the priority corresponding to the first PUCCH configuration information is configured in bits within the DCI corresponding to one or more multicast data, or configured through the Radio Network Temporary Identifier (RNTI) scrambled with the DCI, or configured in the Radio Resource Control (RRC) signaling. That is, the priority corresponding to the first PUCCH configuration information is the physical layer priority configured by the network device for the terminal device, and is the priority at which the terminal device feeds back HARQ-ACK information from the PDSCH at the physical layer. Furthermore, the priority of the aforementioned HARQ-ACK information can also be understood as the priority of the PUCCH carrying the HARQ-ACK information.

[0322] In another optional implementation, when the priority of the first PUCCH configuration information is configured in the bits of the DCI corresponding to one or more multicast data, and the DCI format is 1_1 or 1_2, the priority indicator in the DCI indicates 0 or 1. When the priority indicator indicates '0', it means that the downlink data to be scheduled in the DCI has a low priority, that is, the priority corresponding to the first PUCCH configuration information is low priority; when the priority indicator indicates '1', it means that the downlink data to be scheduled in the DCI has a high priority, that is, the priority corresponding to the first PUCCH configuration information is high priority.

[0323] In another implementation, when the priority of the first PUCCH configuration information is configured in the bits of the DCI corresponding to one or more multicast data, and the DCI format is 1_0, there is no priority indicator field. In this case, the priority of the downlink data scheduled by the DCI can be assumed to be low priority, that is, the priority corresponding to the first PUCCH configuration information is low priority.

[0324] When a terminal device is scheduled with one or more multicast data and one or more unicast data, in order to ensure that the terminal device responds to the feedback information corresponding to the one or more multicast data and one or more unicast data in the same way as it currently responds to the feedback information corresponding to the unicast data, the terminal device does not expect to receive the first PUCCH configuration information corresponding to the multicast data and the second PUCCH configuration information corresponding to the unicast data with the same priority. Therefore, this application also provides an uplink control information transmission method 300. Figure 12 This is a flowchart illustrating the uplink control information transmission method 300. This uplink control information transmission method 300 is also described from the perspective of interaction between network devices and terminal devices. The uplink control information transmission method 300 includes, but is not limited to, the following steps:

[0325] S301. The network device determines the first physical uplink control channel (PUCCH) configuration information corresponding to the multicast data and the second PUCCH configuration information corresponding to the unicast data. The first hybrid automatic repeat request-acknowledgment (HARQ-ACK) information corresponding to the multicast data and the second HARQ-ACK information corresponding to the unicast data belong to different priorities.

[0326] The first HARQ-ACK message and the second HARQ-ACK message have different priorities, which can be understood as the first PUCCH configuration information having different priorities than the second PUCCH configuration information. This implementation allows the terminal device to provide feedback on the first HARQ-ACK message and the second HARQ-ACK message respectively, based on the principle that the HARQ-ACK messages have different priorities, when scheduled with one or more multicast data and one or more unicast data. For specific feedback methods, please refer to the above-described method for terminal devices to provide feedback on HARQ-ACK messages of different priorities, which will not be repeated here.

[0327] S302. The network device sends the first PUCCH configuration information and the second PUCCH configuration information to the terminal device;

[0328] S303. The terminal device receives the first PUCCH configuration information and the second PUCCH configuration information from the network device.

[0329] As can be seen, in this embodiment, when a terminal device is scheduled with one or more multicast data and one or more unicast data, the priorities of the first HARQ-ACK information corresponding to the received multicast data and the second HARQ-ACK information corresponding to the unicast data are different. Therefore, the terminal device can provide feedback on the first HARQ-ACK information and the second HARQ-ACK information respectively according to the principle of different priorities. This feedback method is consistent with the feedback method currently understood by network devices, thereby improving data transmission efficiency and reducing the processing complexity of network devices and terminal devices.

[0330] To achieve the functions of the methods provided in the embodiments of this application, the terminal device or network device may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0331] like Figure 13As shown, this application embodiment provides a communication device 1300. The communication device 1300 can be a component of a terminal device (e.g., an integrated circuit, a chip, etc.) or a component of a network device (e.g., an integrated circuit, a chip, etc.). The communication device 1300 can also be other communication units used to implement the methods in the method embodiments of this application. The communication device 1300 may include a communication unit 1301 and a processing unit 1302. Optionally, it may also include a processing unit 1302 and a storage unit 1303.

[0332] In one possible design, such as Figure 13 One or more units may be implemented by one or more processors, or by one or more processors and memory; or by one or more processors and transceivers; or by one or more processors, memory, and transceivers. This application does not limit the implementation in this way. The processors, memory, and transceivers can be configured individually or integrated.

[0333] The communication device 1300 has the functions of the terminal device described in the embodiments of this application. Optionally, the communication device 1300 also has the functions of the network device described in the embodiments of this application. For example, the communication device 1300 includes modules, units, or means corresponding to the steps involved in the terminal device described in the embodiments of this application. The functions, units, or means can be implemented by software, hardware, or hardware executing corresponding software, or a combination of software and hardware. Further details can be found in the corresponding descriptions in the foregoing method embodiments.

[0334] In one possible design, a communication device 1300 may include:

[0335] The processing unit 1302 is used to obtain the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data. It can be understood that the processing unit 1302 can obtain the first PUCCH configuration information and the second PUCCH configuration information from the network device through the communication unit 1301.

[0336] Communication unit 1301 is also used to receive multiple data from network devices, including one or more multicast data and one or more unicast data; the first hybrid automatic repeat request-acknowledgement (HARQ-ACK) information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data belong to the same priority and need to be fed back in the same time unit;

[0337] Processing unit 1302 is further configured to determine PUCCH resources based on the first PUCCH configuration information or the second PUCCH configuration information;

[0338] The communication unit 1301 is also used to send uplink control information to the network device on the PUCCH resource; the uplink control information includes first HARQ-ACK information and second HARQ-ACK information.

[0339] In one optional implementation, the processing unit 1302 determines PUCCH resources based on either the first PUCCH configuration information or the second PUCCH configuration information. Specifically, it is used to: determine PUCCH resources based on the Physical Uplink Control Channel Resource Indicator (PRI) in the last downlink control information (DCI) corresponding to one or more multicast data and the first PUCCH configuration information, wherein the PUCCH resources belong to the set of PUCCH resources configured in the first PUCCH configuration information; or, determine PUCCH resources based on the Physical Uplink Control Channel Resource Indicator (PRI) in the last downlink control information (DCI) corresponding to one or more unicast data and the second PUCCH configuration information, wherein the PUCCH resources belong to the set of PUCCH resources configured in the second PUCCH configuration information.

[0340] In another optional implementation, the processing unit 1302 determines the PUCCH resource based on the first PUCCH configuration information or the second PUCCH configuration information. Specifically, it is used to: determine the PUCCH resource based on the Physical Uplink Control Channel Resource Indicator (PRI) of the last downlink control information (DC) corresponding to multiple data and the PUCCH configuration information corresponding to the last DCI; the PUCCH resource belongs to the set of PUCCH resources configured in the first PUCCH configuration information or belongs to the set of PUCCH resources configured in the second PUCCH configuration information.

[0341] In another optional implementation, the processing unit 1302 determines the PUCCH resource based on the first PUCCH configuration information or the second PUCCH configuration information, specifically by: receiving first indication information from the network device; the first indication information instructing the terminal device to determine the PUCCH resource based on the first PUCCH configuration information or the second PUCCH configuration information; when the first indication information instructs the terminal device to determine the PUCCH resource based on the first PUCCH configuration information, determining the PUCCH resource based on the Physical Uplink Control Channel Resource Indication (PRI) in the last downlink control information (DCI) corresponding to one or more multicast data and the first PUCCH configuration information; the PUCCH resource belongs to the set of PUCCH resources configured in the first PUCCH configuration information; when the first indication information instructs the terminal device to determine the PUCCH resource based on the second PUCCH configuration information, determining the PUCCH resource based on the Physical Uplink Control Channel Resource Indication (PRI) in the last downlink control information (DCI) corresponding to one or more unicast data and the second PUCCH configuration information; the PUCCH resource belongs to the set of PUCCH resources configured in the second PUCCH configuration information.

[0342] In one optional implementation, when the number of first PUCCH configuration information is one, the priority of the first PUCCH configuration information is high priority.

[0343] In one alternative implementation, the priority corresponding to the first PUCCH configuration information is configured in bits of the DCI corresponding to one or more multicast data, or configured through the Radio Network Temporary Identifier (RNTI) scrambled with the DCI, or configured in the Radio Resource Control (RRC) signaling.

[0344] The embodiments of this application and the method embodiments of the above-described uplink control information transmission method 100 are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the above-described uplink control information transmission method 100 embodiments, which will not be repeated here.

[0345] In another possible design, a communication device 1300 may include:

[0346] The processing unit 1302 is used to obtain the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data. It can be understood that the processing unit 1302 can obtain the first PUCCH configuration information and the second PUCCH configuration information from the network device through the communication unit 1301.

[0347] The communication unit 1301 is also used to receive multiple data from the network device, including one or more multicast data and one or more unicast data; the first hybrid automatic repeat request-acknowledgement (HARQ-ACK) information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data belong to the same priority and need to be fed back in the same time unit;

[0348] The processing unit 1302 is further configured to determine the first PUCCH resource based on the first PUCCH configuration information, and to determine the second PUCCH resource based on the second PUCCH configuration information;

[0349] The communication unit 1301 is further configured to send at least one of a first uplink control information and a second uplink control information to the network device according to the first PUCCH resource and the second PUCCH resource, wherein the first uplink control information includes a first HARQ-ACK information and the second uplink control information includes a second HARQ-ACK information.

[0350] In one optional implementation, the communication unit 1301 sends at least one of a first uplink control information and a second uplink control information to the network device based on the first PUCCH resource and the second PUCCH resource. Specifically, when the first PUCCH resource and the second PUCCH resource do not overlap in the time domain, the first uplink control information is sent to the network device on the first PUCCH resource, and the second uplink control information is sent to the network device on the second PUCCH resource.

[0351] In another optional implementation, the communication unit 1301 sends at least one of a first uplink control information and a second uplink control information to the network device based on the first PUCCH resource and the second PUCCH resource. Specifically, it is used to: send the first uplink control information to the network device on the first PUCCH resource when the first PUCCH resource and the second PUCCH resource overlap in the time domain; or send the second uplink control information to the network device on the second PUCCH resource.

[0352] In another optional implementation, the communication unit 1301 sends first uplink control information to the network device on the first PUCCH resource; or, sends second uplink control information to the network device on the second PUCCH resource. Specifically, it is used to: send the first uplink control information on the first PUCCH resource when the number of bits of the first uplink control information is greater than the number of bits of the second uplink control information; or, send the second uplink control information on the second PUCCH resource when the number of bits of the second uplink control information is greater than or equal to the number of bits of the first uplink control information.

[0353] In another optional implementation, the communication unit 1301 sends a first uplink control message to the network device on the first PUCCH resource; or, sends a second uplink control message to the network device on the second PUCCH resource, for the following purposes: when the number of bits in the first uplink control message is less than the number of bits in the second uplink control message, the first uplink control message is sent on the first PUCCH resource; or, when the number of bits in the second uplink control message is less than or equal to the number of bits in the first uplink control message, the terminal device sends the second uplink control message on the second PUCCH resource.

[0354] In another optional implementation, the communication unit 1301 sends first uplink control information to the network device on the first PUCCH resource; or, sends second uplink control information to the network device on the second PUCCH resource. Specifically, it is used to: send the first uplink control information on the first PUCCH resource when the time domain position of the first PUCCH resource is before the time domain position of the second PUCCH resource; or, send the second uplink control information on the second PUCCH resource when the time domain position of the second PUCCH resource is before the time domain position of the first PUCCH resource.

[0355] In another optional implementation, the communication unit 1301 sends a first uplink control information to the network device on the first PUCCH resource; or, sends a second uplink control information to the network device on the second PUCCH resource. Specifically, it is used to: send the second uplink control information on the second PUCCH resource when the first PUCCH resource is configured to be repeatedly transmitted; or send the first uplink control information on the first PUCCH resource when the second PUCCH resource is configured to be repeatedly transmitted.

[0356] In one optional implementation, when the number of first PUCCH configuration information is one, the priority of the first PUCCH configuration information is high priority.

[0357] In one alternative implementation, the priority corresponding to the first PUCCH configuration information is configured in bits of the DCI corresponding to one or more multicast data, or configured through the Radio Network Temporary Identifier (RNTI) scrambled with the DCI, or configured in the Radio Resource Control (RRC) signaling.

[0358] The embodiments of this application and the method embodiments shown in the above-described uplink control information transmission method 200 are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the above-described uplink control information transmission method 200, which will not be repeated here.

[0359] In yet another possible design, a communication device 1300 may include:

[0360] Communication unit 1301 is used to send multiple data to terminal device, the multiple data including one or more multicast data and one or more unicast data; the first hybrid automatic repeat request-acknowledgement (HARQ-ACK) information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data belong to the same priority and need to be fed back in the same time unit;

[0361] Processing unit 1302 is used to determine PUCCH resources; the PUCCH resources belong to the set of PUCCH resources configured in the first PUCCH configuration information, or belong to the set of PUCCH resources configured in the second PUCCH configuration information.

[0362] The communication unit 1301 is also used to receive uplink control information from the terminal device on the PUCCH resource; the uplink control information includes first HARQ-ACK information and second HARQ-ACK information.

[0363] In one optional implementation, the communication unit 1301 is further configured to: send a Physical Uplink Control Channel Resource Indicator (PRI) in the DCI corresponding to the last multicast data, wherein the PRI indicates a PUCCH resource, and the PUCCH resource is one of the PUCCH resource sets configured in the first PUCCH configuration information; or, send a Physical Uplink Control Channel Resource Indicator (PRI) in the DCI corresponding to the last unicast data, wherein the PRI indicates a PUCCH resource, and the PUCCH resource is one of the PUCCH resource sets configured in the second PUCCH configuration information.

[0364] In another optional implementation, the communication unit 1301 is further configured to: send a Physical Uplink Control Channel Resource Indicator (PRI) in the last downlink control information (DCI) corresponding to multiple data, wherein the PRI indicates PUCCH resources, and the PUCCH resources belong to the PUCCH resource set configured in the first PUCCH configuration information, or the PUCCH resources belong to the PUCCH resource set configured in the second PUCCH configuration information.

[0365] In another optional implementation, the communication unit 1301 is further configured to: send first indication information to the terminal device; the first indication information is used to indicate that the PUCCH resource belongs to the PUCCH resource set configured by the first PUCCH configuration information or to indicate that the PUCCH resource belongs to the PUCCH resource set configured by the second PUCCH configuration information; when the first indication information indicates that the PUCCH resource belongs to the PUCCH resource set configured by the first PUCCH configuration information, the network device sends a Physical Uplink Control Channel Resource Indicator (PRI) in the last DCI corresponding to one or more multicast data, and the PRI indicates the PUCCH resource;

[0366] When the first indication information indicates that the PUCCH resource belongs to the PUCCH resource set configured by the second PUCCH configuration information, the network device sends a Physical Uplink Control Channel Resource Indicator (PRI) in the last DCI corresponding to one or more unicast data, and the PRI indicates the PUCCH resource.

[0367] In one optional implementation, when the number of first PUCCH configuration information is one, the priority of the first PUCCH configuration information is high priority.

[0368] In one alternative implementation, the priority corresponding to the first PUCCH configuration information is configured in bits of the DCI corresponding to one or more multicast data, or configured through the Radio Network Temporary Identifier (RNTI) scrambled with the DCI, or configured in the Radio Resource Control (RRC) signaling.

[0369] The embodiments of this application and the method embodiments of the above-described uplink control information transmission method 100 are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the above-described uplink control information transmission method 100 embodiments, which will not be repeated here.

[0370] In yet another possible design, a communication device 1300 may include:

[0371] Communication unit 1301 is used to send the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data to the terminal device.

[0372] The communication unit 1301 is also used to send multiple data to the terminal device, the multiple data including one or more multicast data and one or more unicast data; the first hybrid automatic repeat request-acknowledgement (HARQ-ACK) information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data belong to the same priority and need to be fed back in the same time unit;

[0373] Processing unit 1302 is used to determine a first PUCCH resource and a second PUCCH resource; the first PUCCH resource belongs to the PUCCH resource set configured by the first PUCCH configuration information; the second PUCCH resource belongs to the PUCCH resource set configured by the second PUCCH configuration information.

[0374] The communication unit 1301 is further configured to receive at least one of a first uplink control information and a second uplink control information from the terminal device according to the first PUCCH resource and the second PUCCH resource; the first uplink control information includes a first HARQ-ACK information; and the second uplink control information includes a second HARQ-ACK information.

[0375] In one optional implementation, the communication unit 1301 receives at least one of a first uplink control information and a second uplink control information from the terminal device based on the first PUCCH resource and the second PUCCH resource. Specifically, the first PUCCH resource and the second PUCCH resource do not overlap; the first uplink control information from the terminal device is received on the first PUCCH resource; and the second uplink control information from the terminal device is received on the second PUCCH resource.

[0376] In another optional implementation, the communication unit 1301 receives at least one of a first uplink control information and a second uplink control information from the terminal device based on the first PUCCH resource and the second PUCCH resource. Specifically, it is used for: the first PUCCH resource and the second PUCCH resource overlap, receiving the first uplink control information from the terminal device on the first PUCCH resource; or, receiving the second uplink control information from the terminal device on the second PUCCH resource.

[0377] In one optional implementation, the communication unit 1301 receives first uplink control information from the terminal device on a first PUCCH resource; or, receives second uplink control information from the terminal device on a second PUCCH resource. Specifically, it is used to: receive the first uplink control information on the first PUCCH resource, wherein the number of bits in the first uplink control information is greater than the number of bits in the second uplink control information; or, receive the second uplink control information on the second PUCCH resource, wherein the number of bits in the second uplink control information is greater than or equal to the number of bits in the first uplink control information.

[0378] In another optional implementation, the communication unit 1301 receives first uplink control information from the terminal device on the first PUCCH resource; or, receives second uplink control information from the terminal device on the second PUCCH resource, specifically configured to: receive the first uplink control information on the first PUCCH resource, wherein the number of bits of the first uplink control information is less than the number of bits of the second uplink control information; or, the network device receives the second uplink control information on the second PUCCH resource, wherein the number of bits of the second uplink control information is less than or equal to the number of bits of the first uplink control information.

[0379] In another optional implementation, the communication unit 1301 receives first uplink control information from the terminal device on the first PUCCH resource; or, receives second uplink control information from the terminal device on the second PUCCH resource, specifically for: receiving the first uplink control information on the first PUCCH resource, wherein the time domain position of the first PUCCH resource is before the time domain position of the second PUCCH resource; or, receiving the second uplink control information on the second PUCCH resource, wherein the time domain position of the second PUCCH resource is before the time domain position of the first PUCCH resource.

[0380] In another optional implementation, the communication unit 1301 receives first uplink control information from the terminal device on the first PUCCH resource; or, receives second uplink control information from the terminal device on the second PUCCH resource, specifically used for: receiving the second uplink control information on the second PUCCH resource, wherein the first PUCCH resource is configured to be repeatedly transmitted; or, receiving the first uplink control information on the first PUCCH resource, wherein the second PUCCH resource is configured to be repeatedly transmitted.

[0381] In one optional implementation, when the number of first PUCCH configuration information is one, the priority of the first PUCCH configuration information is high priority.

[0382] In one alternative implementation, the priority corresponding to the first PUCCH configuration information is configured in bits of the DCI corresponding to one or more multicast data, or configured through the Radio Network Temporary Identifier (RNTI) scrambled with the DCI, or configured in the Radio Resource Control (RRC) signaling.

[0383] The embodiments of this application and the method embodiments shown in the above-described uplink control information transmission method 200 are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the above-described uplink control information transmission method 200 embodiments, which will not be repeated here.

[0384] In yet another possible design, a communication device 1300 may include:

[0385] Processing unit 1302 is used to determine the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data, wherein the first hybrid automatic repeat request-acknowledgement (HARQ-ACK) information corresponding to multicast data and the second HARQ-ACK information corresponding to unicast data belong to different priorities.

[0386] The communication unit 1301 is used to send the first PUCCH configuration information and the second PUCCH configuration information to the terminal device.

[0387] The embodiments of this application and the method embodiments shown in the above-described uplink control information transmission method 300 are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the above-described uplink control information transmission method 300 embodiments, which will not be repeated here.

[0388] This application also provides a communication device 1400. Figure 14 This is a schematic diagram of the communication device 1400. The communication device 1400 can be a terminal device or a network device, or it can be a chip, chip system, or processor that supports the implementation of the above methods in a terminal device, or it can be a chip, chip system, or processor that supports the implementation of the above methods in a network device. This device can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0389] The communication device 1400 may include one or more processors 1401. The processor 1401 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal, terminal chip, DU or CU, etc.), execute software programs, and process data from the software programs.

[0390] Optionally, the communication device 1400 may include one or more memories 1402, which may store instructions 1404 that can be executed on the processor 1401, causing the communication device 1400 to perform the methods described in the above method embodiments. Optionally, the memory 1402 may also store data. The processor 1401 and the memory 1402 may be provided separately or integrated together.

[0391] Optionally, the communication device 1400 may further include a transceiver 1405 and an antenna 1406. The transceiver 1405 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 1405 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0392] The communication device 1400 is a terminal device: the transceiver 1405 is used to execute S102, S105, and S107 in the uplink control information transmission method 100, and S202, S205, and S207 in the uplink control information transmission method 200; the processor 1401 is used to execute S106 in the uplink control information transmission method 100, S206 in the uplink control information transmission method 200, and S303 in the uplink control information transmission method 300.

[0393] The communication device 1400 is a network device: transceiver 1405 is used to execute S101, S104, and S108 in the uplink control information transmission method 100, and S201, S204, and S208 in the uplink control information transmission method 200, and S302 in the uplink control information transmission method 300; processor 1401 is used to execute S103 in the uplink control information transmission method 100, S203 in the uplink control information transmission method 200, and S301 in the uplink control information transmission method 300.

[0394] In another possible design, the processor 1401 may include a transceiver for implementing receive and transmit functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or for transmitting or relaying signals.

[0395] In another possible design, the processor 1401 may optionally store instructions 1403, which, when executed on the processor 1401, cause the communication device 1400 to perform the methods described in the above method embodiments. Instructions 1403 may be embedded in the processor 1401; in this case, the processor 1401 may be implemented in hardware.

[0396] In another possible design, the communication device 1400 may include circuitry that can perform the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this application embodiment can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive channel metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0397] The communication device described in the above embodiments may be a first device, but the scope of the communication device described in the embodiments of this application is not limited thereto, and the structure of the communication device may be unrestricted. Figure 14 The communication device may be a standalone device or part of a larger device. For example, the communication device may be:

[0398] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0399] (2) A collection of one or more ICs, optionally including a storage component for storing data and instructions;

[0400] (3) ASIC, such as modem (MSM);

[0401] (4) Modules that can be embedded in other devices;

[0402] (5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.

[0403] (6) Others, etc.

[0404] For cases where the communication device can be a chip or a chip system, please refer to [link / reference]. Figure 15 The diagram shows the structure of the chip. Figure 15 The chip 1500 shown includes a processor 1501 and an interface 1502. The number of processors 1501 can be one or more, and the number of interfaces 1502 can be multiple. The chip 1500 may also include a memory 1503.

[0405] In one design, the chip is used to implement the functions of the terminal device in the embodiments of this application:

[0406] The processor 1501 is used to acquire the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data.

[0407] The interface 1502 is used to receive multiple data from the network device, including one or more multicast data and one or more unicast data; the first HARQ-ACK information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data have the same priority and need to be fed back in the same time unit.

[0408] The processor 1501 is further configured to determine PUCCH resources based on the first PUCCH configuration information or the second PUCCH configuration information;

[0409] The interface 1502 is also used to send uplink control information to the network device on the PUCCH resource; the uplink control information includes first HARQ-ACK information and second HARQ-ACK information.

[0410] In another design, regarding the case where the chip is used to implement the functions of the terminal device in the embodiments of this application:

[0411] The processor 1501 is used to acquire the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data.

[0412] The interface 1502 is used to receive multiple data from the network device, including one or more multicast data and one or more unicast data; the first HARQ-ACK information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data have the same priority and need to be fed back in the same time unit.

[0413] The processor 1501 is further configured to determine a first PUCCH resource based on the first PUCCH configuration information, and to determine a second PUCCH resource based on the second PUCCH configuration information;

[0414] The interface 1502 is further configured to send at least one of a first uplink control information and a second uplink control information to the network device based on the first PUCCH resource and the second PUCCH resource, wherein the first uplink control information includes a first HARQ-ACK information and the second uplink control information includes a second HARQ-ACK information.

[0415] In another design, regarding the use of the chip to implement the functions of the network device in the embodiments of this application:

[0416] The interface 1502 is used to send the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data to the terminal device.

[0417] The interface 1502 is also used to send multiple data to the terminal device, including one or more multicast data and one or more unicast data; the first hybrid automatic repeat request-acknowledgement (HARQ-ACK) information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data belong to the same priority and need to be fed back in the same time unit;

[0418] The processor 1501 is used to determine PUCCH resources; the PUCCH resources belong to the set of PUCCH resources configured in the first PUCCH configuration information, or belong to the set of PUCCH resources configured in the second PUCCH configuration information.

[0419] The interface 1502 is also used to receive uplink control information from the terminal device on the PUCCH resource; the uplink control information includes first HARQ-ACK information and second HARQ-ACK information.

[0420] In another design, regarding the use of the chip to implement the functions of the network device in the embodiments of this application:

[0421] The interface 1502 is used to send the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data to the terminal device.

[0422] The interface 1502 is also used to send multiple data to the terminal device, including one or more multicast data and one or more unicast data; the first hybrid automatic repeat request-acknowledgement (HARQ-ACK) information corresponding to one or more multicast data and the second HARQ-ACK information corresponding to one or more unicast data belong to the same priority and need to be fed back in the same time unit;

[0423] The processor 1501 is used to determine a first PUCCH resource and a second PUCCH resource; the first PUCCH resource belongs to the PUCCH resource set configured by the first PUCCH configuration information; the second PUCCH resource belongs to the PUCCH resource set configured by the second PUCCH configuration information.

[0424] The interface 1502 is further configured to receive at least one of a first uplink control information and a second uplink control information from the terminal device, based on the first PUCCH resource and the second PUCCH resource; the first uplink control information includes a first HARQ-ACK information; and the second uplink control information includes a second HARQ-ACK information.

[0425] In another design, regarding the use of the chip to implement the functions of the network device in the embodiments of this application:

[0426] The processor 1501 is used to determine the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data, wherein the first hybrid automatic repeat request-acknowledgment (HARQ-ACK) information corresponding to multicast data and the second HARQ-ACK information corresponding to unicast data belong to different priorities.

[0427] The interface 1502 is used to send first PUCCH configuration information and second PUCCH configuration information to the terminal device.

[0428] In this application embodiment, the communication device 1400 and chip 1500 can also execute the implementation method described in the communication device 1300 above. Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented through hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can use various methods to implement the described functionality for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this application.

[0429] The embodiments of this application and the method embodiments shown in the above-described uplink control information transmission methods 100, 200 and 300 are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the above-described uplink control information transmission methods 100, 200 and 300, which will not be repeated here.

[0430] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented through hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this application.

[0431] This application also provides a computer-readable storage medium for storing computer software instructions that, when executed by a communication device, implement the functions of any of the above method embodiments.

[0432] This application also provides a computer program product for storing computer software instructions, which, when executed by a communication device, implement the functions of any of the above method embodiments.

[0433] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

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

Claims

1. A method for transmitting uplink control information, characterized in that, The method is applied to a terminal device or a chip of the terminal device, and the method includes: Obtain the configuration information of the first physical uplink control channel (PUCCH) corresponding to multicast data and the configuration information of the second physical uplink control channel (PUCCH) corresponding to unicast data; Receive multiple data from network devices, the multiple data including one or more multicast data and one or more unicast data; the first hybrid automatic repeat request-acknowledgment (HARQ-ACK) information corresponding to the one or more multicast data and the second HARQ-ACK information corresponding to the one or more unicast data have the same priority and need to be fed back in the same time unit; Receive first indication information from the network device; the first indication information is used to instruct the determination of PUCCH resources based on the second PUCCH configuration information. The PUCCH resource is determined based on the Physical Uplink Control Channel Resource Indication (PRI) in the last downlink control information (DCI) corresponding to the one or more unicast data and the second PUCCH configuration information; the PUCCH resource belongs to the set of PUCCH resources configured in the second PUCCH configuration information. Uplink control information is sent to the network device on the PUCCH resource, the uplink control information including the first HARQ-ACK information and the second HARQ-ACK information; The priority corresponding to the first PUCCH configuration information is configured in bits in the DCI corresponding to the one or more multicast data, or configured through the Radio Network Temporary Identifier (RNTI) scrambled with the DCI, or configured in the Radio Resource Control (RRC) signaling.

2. The method according to claim 1, characterized in that, The first indication information is specifically used to indicate that the PUCCH resource belongs to the PUCCH resource set configured by the second PUCCH configuration information.

3. The method according to claim 1 or 2, characterized in that, When there is only one first PUCCH configuration information, the priority of the first PUCCH configuration information is high priority.

4. A method for transmitting uplink control information, characterized in that, The method is applied to a network device or a chip of the network device, and the method includes: Send the first physical uplink control channel (PUCCH) configuration information corresponding to multicast data and the second PUCCH configuration information corresponding to unicast data to the terminal device; Multiple data are sent to the terminal device, including one or more multicast data and one or more unicast data; the first hybrid automatic repeat request-acknowledgment (HARQ-ACK) information corresponding to the one or more multicast data and the second HARQ-ACK information corresponding to the one or more unicast data have the same priority and need to be fed back in the same time unit. Send a first indication message to the terminal device; the first indication message is used to indicate that PUCCH resources are determined according to the second PUCCH configuration information; In the last DCI corresponding to the one or more unicast data, a Physical Uplink Control Channel Resource Indicator (PRI) is sent, the PRI indicating the PUCCH resource; Identify the PUCCH resource; the PUCCH resource belongs to the set of PUCCH resources configured in the second PUCCH configuration information; The uplink control information received from the terminal device on the PUCCH resource includes the first HARQ-ACK information and the second HARQ-ACK information. The priority corresponding to the first PUCCH configuration information is configured in bits in the DCI corresponding to the one or more multicast data, or configured through the Radio Network Temporary Identifier (RNTI) scrambled with the DCI, or configured in the Radio Resource Control (RRC) signaling.

5. The method according to claim 4, characterized in that, The method further includes: The first indication information is specifically used to indicate that the PUCCH resource belongs to the PUCCH resource set configured by the second PUCCH configuration information.

6. The method according to claim 4 or 5, characterized in that, When there is only one first PUCCH configuration information, the priority of the first PUCCH configuration information is high priority.

7. A communication device, characterized in that, The device includes a processor and a communication interface for communicating with other communication devices; the processor is configured to run a program that causes the communication device to implement the method of any one of claims 1 to 3, or to cause the communication device to implement the method of any one of claims 4 to 6.

8. A communication device, characterized in that, include: Processor and interface; The interface is used to receive code instructions and transmit them to the processor; The processor is configured to execute the code instructions to perform the method as described in any one of claims 1 to 3, or to execute the code instructions to perform the method as described in any one of claims 4 to 6.

9. A computer-readable storage medium for storing instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 3; or cause the computer to perform the method of any one of claims 4 to 6.

Images