Transmit Delay-Sensitive Uplink Control on a Secondary Carrier

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may select at least one of a primary carrier associated with a physical uplink control channel group or a secondary carrier associated with the physical uplink control channel group to transmit a physical uplink control channel message to a base station. The UE may transmit the physical uplink control channel message using at least one of the primary carrier or the secondary carrier based on the selection of at least one of the primary carrier or the secondary carrier.

Description

[0001] Cross - Reference to Related Applications

[0002] This patent application claims the benefit of priority of U.S. patent application Ser. No. 17 / 372,109, filed Jul. 9, 2021, entitled "TRANSMIT DELAY SENSITIVE UPLINK CONTROL ON SECONDARY CARRIER" by HUANG et al.; and U.S. Provisional Patent Application No. 63 / 052,925, filed Jul. 16, 2020, entitled "TRANSMIT DELAY SENSITIVE UPLINK CONTROL ON SECONDARY CARRIER" by HUANG et al.; both of the above - mentioned U.S. applications are assigned to the assignee of the present application and are hereby incorporated by reference in their entirety. Technical Field

[0003] The following relates to wireless communication, including transmitting delay - sensitive uplink control on a secondary carrier. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcasting, etc. These systems are capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multi - access systems include fourth - generation (4G) systems (e.g., Long - Term Evolution (LTE) systems, LTE - Advanced (LTE - A) systems, or LTE - A Pro systems) and fifth - generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT - S - OFDM). A wireless multi - access communication system may include one or more base stations or one or more network access nodes, each of which simultaneously supports communication for multiple communication devices (which may otherwise be referred to as user equipment (UE)). Summary of the Invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting the transmission of latency-sensitive uplink control on a secondary carrier. Generally speaking, the described techniques enable a user equipment (UE) to transmit control channel information, such as Physical Uplink Control Channel (PUCCH) information, on a secondary carrier of a PUCCH group. For example, a UE may be configured to perform multi-carrier communication using one or more cells associated with at least a primary carrier (e.g., a Primary Component Carrier (PCC)) and one or more secondary carriers (e.g., Secondary Component Carriers (SCCs)). The UE may receive downlink transmissions on one or more of the primary or secondary carriers of the PUCCH group, e.g., from one or more cells in the PUCCH group. The UE may identify or otherwise determine acknowledgment information associated with the downlink transmission (e.g., Acknowledgment / Negative Acknowledgment (ACK / NACK) information, a channel measurement report associated with the downlink transmission, etc.). The UE may then select one or more of the primary or secondary carriers to send feedback to the base station for indicating the acknowledgment information. For example, the UE may receive a signal configuring the time slot pattern of the primary carrier or the secondary carrier or both, where different time slot patterns may be selected for different carriers such that instances of uplink time slots are staggered to allow for better ability to transmit information. Accordingly, the UE may select one or more of the primary or secondary carriers to send a feedback message indicating the acknowledgment information.

[0006] A method of wireless communication at a UE is described. The method may include: receiving a downlink transmission from a base station on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group; determining acknowledgment information associated with the UE decoding the downlink transmission; selecting at least one of the primary carrier or the secondary carrier to send feedback to the base station based on determining the acknowledgment information; and transmitting a feedback message indicating the acknowledgment information using at least one of the primary carrier or the secondary carrier based on selecting at least one of the primary carrier or the secondary carrier.

[0007] Describes an apparatus for wireless communication at a UE. The apparatus may include: a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: receive a downlink transmission from a base station on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group; determine acknowledgment information associated with the UE decoding the downlink transmission; select at least one of the primary carrier or the secondary carrier to send feedback to the base station based on determining the acknowledgment information; and, based on selecting at least one of the primary carrier or the secondary carrier, use at least one of the primary carrier or the secondary carrier to send a feedback message indicating the acknowledgment information.

[0008] Describes another apparatus for wireless communication at a UE. The apparatus may include units for performing the following operations: receive a downlink transmission from a base station on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group; determine acknowledgment information associated with the UE decoding the downlink transmission; select at least one of the primary carrier or the secondary carrier to send feedback to the base station based on determining the acknowledgment information; and, based on selecting at least one of the primary carrier or the secondary carrier, use at least one of the primary carrier or the secondary carrier to send a feedback message indicating the acknowledgment information.

[0009] Describes a non-transitory computer-readable medium storing code for wireless communication at a UE. The code may include instructions executable by a processor to perform the following operations: receive a downlink transmission from a base station on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group; determine acknowledgment information associated with the UE decoding the downlink transmission; select at least one of the primary carrier or the secondary carrier to send feedback to the base station based on determining the acknowledgment information; and, based on selecting at least one of the primary carrier or the secondary carrier, use at least one of the primary carrier or the secondary carrier to send a feedback message indicating the acknowledgment information.

[0010] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for performing the following operations: receive a signal configuring a first time slot format pattern for the primary carrier and a second time slot format pattern for the secondary carrier, wherein the selection may be based on the first time slot format pattern, the second time slot format pattern, or a combination thereof.

[0011] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first time slot format pattern and the second time slot format pattern together include: interleaved instances of uplink time slots available for transmitting the feedback message in the time domain.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: determining an authorization for scheduling the downlink transmission that can be received within a first threshold duration before transmitting the feedback message; and determining that the downlink transmission can be received within a second threshold duration before transmitting the feedback message, wherein transmitting the feedback message may be based on the first threshold duration and the second threshold duration.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: transmitting a message indicating UE capabilities for using at least one of the primary subcarrier or the secondary subcarrier to transmit the feedback message, wherein receiving the downlink transmission on at least one of the primary carrier or the secondary carrier may be based on the UE capabilities.

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: receiving a signal that configures a first resource set for transmitting the feedback message on the primary carrier and a second resource set for transmitting the feedback message on the secondary carrier, wherein the selection may be based on the first resource set and the second resource set.

[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: determining resource usage for transmitting the feedback message; and determining available resources in the first resource set and available resources in the second resource set, wherein the selection may be based on the available resources meeting the resource usage for transmitting the feedback message.

[0016] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: determining a priority rule associated with transmitting the feedback message on the primary carrier and the secondary carrier, wherein the selection may be based on the priority rule and the available resources configured for transmitting the feedback message meeting the resource usage for transmitting the feedback message.

[0017] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the priority rules include a first priority associated with the primary carrier and a second priority associated with the secondary carrier, and the first priority is a higher priority than the second priority.

[0018] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the priority rules include a second priority associated with the secondary carrier and a third priority associated with an additional secondary carrier, and the second priority is a higher priority than the third priority.

[0019] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for performing the following: receiving an authorization that schedules the downlink transmission and indicates the primary carrier or the secondary carrier for sending the feedback message; and selecting at least one of the primary carrier or the secondary carrier based on the authorization to send the feedback message.

[0020] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for performing the following: receiving an activation of a semi-persistent resource for the downlink transmission and an authorization that indicates the primary carrier or the secondary carrier for sending the feedback message; and selecting at least one of the primary carrier or the secondary carrier based on the authorization to send the feedback message.

[0021] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for performing the following: receiving a configuration signal that indicates a semi-persistent resource for the downlink transmission and indicates the primary carrier or the secondary carrier for sending the feedback message; and selecting at least one of the primary carrier or the secondary carrier based on the configuration signal to send the feedback message.

[0022] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, selecting at least one of the primary carrier or the secondary carrier to send the feedback message may include operations, features, units, or instructions for performing the following: selecting the primary carrier and the secondary carrier to send the feedback message.

[0023] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the feedback message may include operations, features, units, or instructions for: sending a first feedback message on the primary carrier using a first codebook generated based on one or more downlink transmissions received on the primary carrier; and sending a second feedback message on the secondary carrier using a second codebook generated based on one or more downlink transmissions received on the secondary carrier.

[0024] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the feedback message may include operations, features, units, or instructions for: sending the feedback message on the primary carrier and the secondary carrier using a combined codebook generated based on one or more downlink transmissions received on the primary carrier and the secondary carrier.

[0025] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: determining that an uplink transmission can be scheduled to be sent to the base station; determining that a service type associated with the uplink transmission can be a service type supported by the UE for transmissions on the secondary carrier; and selecting the secondary carrier for transmission of the uplink transmission based on the service type.

[0026] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: determining that a second uplink transmission can be scheduled to be sent to the base station; determining that a second service type associated with the second uplink transmission can be a second service type supported by the UE for transmissions on the primary carrier; and selecting the primary carrier for transmission of the second uplink transmission based on the second service type.

[0027] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the service type associated with the uplink transmission includes an ultra-reliable / low-latency communication (URLLC) service type, and wherein the second service type associated with the second uplink transmission includes an enhanced mobile broadband (eMBB) service type.

[0028] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the acknowledgement information includes at least one of an acknowledgement or a negative acknowledgement.

[0029] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the feedback message includes: a Hybrid Automatic Repeat reQuest (HARQ) acknowledgement message, a reference signal measurement report transmission, or both.

[0030] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, each of the primary carrier, the secondary carrier, or a combination thereof includes a Time Division Duplex (TDD) carrier, a Frequency Division Duplex (FDD) carrier, or both.

[0031] A method of wireless communication at a base station is described. The method may include: transmitting a downlink transmission to a UE on at least one of a primary carrier associated with a Physical Uplink Control Channel (PUCCH) group or a secondary carrier associated with the PUCCH group; and receiving, based on a selection of at least one of the primary carrier or the secondary carrier, a feedback message indicating acknowledgement information using at least one of the primary carrier or the secondary carrier.

[0032] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: transmit a downlink transmission to a UE on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group; and receive, based on a selection of at least one of the primary carrier or the secondary carrier, a feedback message indicating acknowledgement information using at least one of the primary carrier or the secondary carrier.

[0033] Another apparatus for wireless communication at a base station is described. The apparatus may include units for: transmitting a downlink transmission to a UE on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group; and receiving, based on a selection of at least one of the primary carrier or the secondary carrier, a feedback message indicating acknowledgement information using at least one of the primary carrier or the secondary carrier.

[0034] A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code may include instructions executable by a processor to: transmit a downlink transmission to a UE on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group; and receive, based on a selection of at least one of the primary carrier or the secondary carrier, a feedback message indicating acknowledgement information using at least one of the primary carrier or the secondary carrier.

[0035] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: sending a signal configuring a first time slot format pattern for the primary carrier and a second time slot format pattern for the secondary carrier, wherein receiving the feedback message from the UE may be based on the first time slot format pattern, the second time slot format pattern, or a combination thereof.

[0036] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first time slot format pattern and the second time slot format pattern together include interleaved instances of uplink time slots available for sending the feedback message in the time domain.

[0037] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: sending authorization for scheduling a downlink transmission for a first threshold duration before the UE sends the feedback message; and sending the downlink transmission for a second threshold duration before the UE sends the feedback message, wherein receiving the feedback message may be based on the first threshold duration and the second threshold duration.

[0038] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: sending a signal configuring a first resource set for sending the feedback message on the primary carrier and a second resource set for sending the feedback message on the secondary carrier, wherein the UE's selection of the primary carrier or the secondary carrier may be based on the first resource set and the second resource set.

[0039] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: receiving a message indicating UE capabilities for using at least one of the primary subcarrier or the secondary subcarrier to send the feedback message, wherein sending the downlink transmission on at least one of the primary carrier and the secondary carrier may be based on the UE capabilities.

[0040] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: determining a priority rule associated with receiving the feedback message on the primary carrier and the secondary carrier, wherein the UE's selection of the primary carrier or the secondary carrier may be based on the priority rule and the available resources configured for sending the feedback message meet the resource usage for sending the feedback message.

[0041] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the priority rules include a first priority associated with the primary carrier and a second priority associated with the secondary carrier, and the first priority is a higher priority than the second priority.

[0042] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the priority rules include a second priority associated with the secondary carrier and a third priority associated with an additional secondary carrier, and the second priority is a higher priority than the third priority.

[0043] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for performing the following: sending an authorization for scheduling the downlink transmission and indicating the primary carrier or the secondary carrier for sending the feedback message, wherein the authorization indicating the primary carrier or the secondary carrier overrides the priority rules for selecting the primary carrier or the secondary carrier for sending the feedback message.

[0044] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for performing the following: sending an activation of a semi-persistent resource for the downlink transmission and indicating the primary carrier or the secondary carrier for sending the feedback message, wherein the authorization indicating the primary carrier or the secondary carrier overrides the priority rules for selecting the primary carrier or the secondary carrier for sending the feedback message.

[0045] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for performing the following: sending a configuration signal indicating a semi-persistent resource for the downlink transmission and indicating the primary carrier or the secondary carrier for sending the feedback message, wherein the configuration signal indicating the primary carrier or the secondary carrier overrides the priority rules for selecting the primary carrier or the secondary carrier for sending the feedback message.

[0046] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the feedback message may include operations, features, units, or instructions for performing the following: receiving the feedback message on the primary carrier and the secondary carrier.

[0047] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the feedback message may include operations, features, units, or instructions for performing the following: receiving a first feedback message on the primary carrier using a first codebook generated based on one or more downlink transmissions sent on the primary carrier; and receiving a second feedback message on the secondary carrier using a second codebook generated based on one or more downlink transmissions sent on the secondary carrier.

[0048] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the feedback message may include operations, features, units, or instructions for performing the following: receiving the feedback message on the primary carrier and the secondary carrier using a combined codebook generated based on one or more downlink transmissions sent on the primary carrier and the secondary carrier.

[0049] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for performing the following: determining that an uplink transmission can be scheduled to be sent from the UE; determining that a service type associated with the uplink transmission can be a service type supported by the UE for transmissions on the secondary carrier; and receiving the uplink transmission on the secondary carrier based on the service type.

[0050] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for performing the following: determining that a second uplink transmission can be scheduled to be sent to the base station; determining that a second service type associated with the second uplink transmission can be a second service type supported by the UE for transmissions on the primary carrier; and receiving the second uplink transmission on the primary carrier based on the second service type.

[0051] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the service type associated with the uplink transmission includes a URLLC service type, and wherein the service type associated with the uplink transmission includes an eMBB service type.

[0052] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the acknowledgement information includes at least one of an acknowledgement or a negative acknowledgement.

[0053] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the feedback message includes a hybrid automatic repeat / request acknowledgement message, a reference signal measurement report transmission, or a combination thereof.

[0054] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the primary carrier, the secondary carrier, or a combination thereof includes a time division duplex carrier, a frequency division duplex carrier, or both.

[0055] A method for wireless communication at a UE is described. The method may include: selecting at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group to transmit a PUCCH message to a base station; and, based on selecting at least one of the primary carrier or the secondary carrier, transmitting the PUCCH message to the base station using at least one of the primary carrier or the secondary carrier.

[0056] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: selecting at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group to transmit a PUCCH message to a base station; and, based on selecting at least one of the primary carrier or the secondary carrier, transmitting the PUCCH message to the base station using at least one of the primary carrier or the secondary carrier.

[0057] Another apparatus for wireless communication at a UE is described. The apparatus may include units for performing the following operations: selecting at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group to transmit a PUCCH message to a base station; and, based on selecting at least one of the primary carrier or the secondary carrier, transmitting the PUCCH message to the base station using at least one of the primary carrier or the secondary carrier.

[0058] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to perform the following operations: selecting at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group to transmit a PUCCH message to a base station; and, based on selecting at least one of the primary carrier or the secondary carrier, transmitting the PUCCH message to the base station using at least one of the primary carrier or the secondary carrier.

[0059] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: receiving a downlink transmission from a base station on at least one of the primary carrier or the secondary carrier; and determining acknowledgement information associated with the UE decoding the downlink transmission, wherein the selection may be based on the acknowledgement information.

[0060] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: receiving an authorization that schedules the downlink transmission and indicates the primary carrier or the secondary carrier for transmitting the PUCCH message, wherein the selection may be based on the authorization.

[0061] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: receiving a signal that configures a first time slot format pattern for the primary carrier and a second time slot format pattern for the secondary carrier, wherein the selection may be based on the first time slot format pattern, the second time slot format pattern, or a combination thereof.

[0062] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first time slot format pattern and the second time slot format pattern together include interleaved instances of uplink time slots available for transmitting the PUCCH message in the time domain.

[0063] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the interleaved instances include uplink time slots available on the primary carrier, the secondary carrier, or both during each time slot.

[0064] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: transmitting a message indicating UE capabilities for using at least one of the primary carrier or the secondary carrier to transmit the PUCCH message, wherein the selection of the at least one of the primary carrier or the secondary carrier may be based on the UE capabilities.

[0065] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: receiving a signal that configures a first resource set for transmitting the PUCCH message on the primary carrier and a second resource set for transmitting the PUCCH message on the secondary carrier, wherein the selection may be based on the first resource set and the second resource set.

[0066] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: determining resource usage for transmitting the PUCCH message, and determining available resources in the first resource set and available resources in the second resource set, wherein the selection may be based on the available resources satisfying the resource usage for transmitting the PUCCH message.

[0067] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: determining a priority rule associated with transmitting the PUCCH message on the primary carrier and the secondary carrier, wherein the selection may be based on the priority rule and the available resources configured for transmitting the PUCCH message satisfying the resource usage for transmitting the PUCCH message.

[0068] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the priority rule includes a first priority associated with the primary carrier and a second priority associated with the secondary carrier, and the first priority is a higher priority than the second priority.

[0069] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the priority rule includes a second priority associated with the secondary carrier and a third priority associated with an additional secondary carrier, and the second priority is a higher priority than the third priority.

[0070] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: receiving activation of semi-persistent resources for downlink transmission and an authorization indicating the primary carrier or the secondary carrier for transmitting the PUCCH message, and selecting at least one of the primary carrier or the secondary carrier based on the authorization to transmit the PUCCH message.

[0071] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: receiving a configuration signal indicating semi-persistent resources for downlink transmission and indicating the primary carrier or the secondary carrier for transmitting the PUCCH message, and selecting at least one of the primary carrier or the secondary carrier based on the configuration signal to transmit the PUCCH message.

[0072] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, selecting at least one of the primary carrier or the secondary carrier to transmit the PUCCH message may include operations, features, units, or instructions for performing the following: selecting the primary carrier and the secondary carrier to transmit the PUCCH message.

[0073] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting the PUCCH message may include operations, features, units, or instructions for performing the following: transmitting a first PUCCH message on the primary carrier using a first codebook generated based on one or more downlink transmissions received on the primary carrier; and transmitting a second PUCCH message on the secondary carrier using a second codebook generated based on one or more downlink transmissions received on the secondary carrier.

[0074] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting the PUCCH message may include operations, features, units, or instructions for performing the following: transmitting the PUCCH message on the primary carrier and the secondary carrier using a combined codebook generated based on one or more downlink transmissions received on the primary carrier and the secondary carrier.

[0075] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for performing the following: determining that an uplink transmission can be scheduled to be transmitted to the base station; determining that a service type associated with the uplink transmission can be a service type supported by the UE for transmissions on the secondary carrier; and selecting the secondary carrier for transmission of the uplink transmission based on the service type.

[0076] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for performing the following: determining that a second uplink transmission can be scheduled to be transmitted to the base station; determining that a second service type associated with the second uplink transmission can be a second service type supported by the UE for transmissions on the primary carrier; and selecting the primary carrier for transmission of the second uplink transmission based on the second service type.

[0077] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the service type associated with the uplink transmission includes a URLLC service type, and the second service type associated with the second uplink transmission includes an eMBB service type.

[0078] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the PUCCH message includes a first HARQ message associated with a dynamically scheduled downlink transmission, a second HARQ message associated with a semi-persistently activated downlink transmission, a first reference signal measurement report transmission associated with a periodic channel state information reference signal (CSI-RS), a second reference signal measurement report associated with an aperiodic channel state information (CSI)-RS, a third reference signal measurement report associated with a semi-persistent CSI-RS, a scheduling request, or a combination thereof.

[0079] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the primary carrier, the secondary carrier, or a combination thereof each includes a time division duplex carrier, a frequency division duplex carrier, or both.

[0080] A method for wireless communication at a base station is described. The method may include: receiving, from a UE, a PUCCH message using at least one of the primary carrier or the secondary carrier associated with the PUCCH group based on a selection of at least one of the primary carrier associated with the PUCCH group or the secondary carrier associated with the PUCCH group.

[0081] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: receiving, from a UE, a PUCCH message using at least one of the primary carrier or the secondary carrier associated with the PUCCH group based on a selection of at least one of the primary carrier associated with the PUCCH group or the secondary carrier associated with the PUCCH group.

[0082] Another apparatus for wireless communication at a base station is described. The apparatus may include units for performing the following operations: receiving, from a UE, a PUCCH message using at least one of the primary carrier or the secondary carrier associated with the PUCCH group based on a selection of at least one of the primary carrier associated with the PUCCH group or the secondary carrier associated with the PUCCH group.

[0083] A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code may include instructions executable by a processor to perform the following operations: receiving, from a UE, a PUCCH message using at least one of the primary carrier or the secondary carrier associated with the PUCCH group based on a selection of at least one of the primary carrier associated with the PUCCH group or the secondary carrier associated with the PUCCH group.

[0084] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: transmitting a downlink transmission to the UE on at least one of the primary carrier or the secondary carrier, where the PUCCH message includes a feedback message indicating acknowledgment information associated with the UE decoding the downlink transmission.

[0085] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: transmitting an authorization that schedules the downlink transmission and indicates the primary carrier or the secondary carrier for transmitting the feedback message.

[0086] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: transmitting a signal configuring a first time slot format pattern for the primary carrier and a second time slot format pattern for the secondary carrier, where receiving the PUCCH message from the UE may be based on the first time slot format pattern, the second time slot format pattern, or a combination thereof.

[0087] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first time slot format pattern and the second time slot format pattern together include interleaved instances of uplink time slots available for transmitting the feedback message in the time domain.

[0088] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the interleaved instances include uplink time slots available on the primary carrier, the secondary carrier, or both during each time slot. BRIEF DESCRIPTION OF THE DRAWINGS

[0089] Figure 1 Shows an example of a system for wireless communication that supports transmitting delay-sensitive uplink control on a secondary carrier in accordance with aspects of the present disclosure.

[0090] Figure 2 Shows an example of a wireless communication system that supports transmitting delay-sensitive uplink control on a secondary carrier in accordance with aspects of the present disclosure.

[0091] Figure 3 Shows an example of a carrier configuration that supports transmitting delay-sensitive uplink control on a secondary carrier in accordance with aspects of the present disclosure.

[0092] Figure 4 Shows an example of a carrier configuration that supports transmitting delay-sensitive uplink control on a secondary carrier in accordance with aspects of the present disclosure.

[0093] Figure 5 Illustrates an example of a carrier configuration that supports transmitting latency-sensitive uplink control on a secondary carrier, in accordance with aspects of the present disclosure.

[0094] Figure 6 Illustrates an example of a process that supports transmitting latency-sensitive uplink control on a secondary carrier, in accordance with aspects of the present disclosure.

[0095] Figure 7 and Figure 8 Illustrates a block diagram of a device that supports transmitting latency-sensitive uplink control on a secondary carrier, in accordance with aspects of the present disclosure.

[0096] Figure 9 Illustrates a block diagram of a communication manager that supports transmitting latency-sensitive uplink control on a secondary carrier, in accordance with aspects of the present disclosure.

[0097] Figure 10 Illustrates a diagram of a system that includes a device that supports transmitting latency-sensitive uplink control on a secondary carrier, in accordance with aspects of the present disclosure.

[0098] Figure 11 and Figure 12 Illustrates a block diagram of a device that supports transmitting latency-sensitive uplink control on a secondary carrier, in accordance with aspects of the present disclosure.

[0099] Figure 13 Illustrates a block diagram of a communication manager that supports transmitting latency-sensitive uplink control on a secondary carrier, in accordance with aspects of the present disclosure.

[0100] Figure 14 Illustrates a diagram of a system that includes a device that supports transmitting latency-sensitive uplink control on a secondary carrier, in accordance with aspects of the present disclosure.

[0101] Figures 15 to 19 Illustrates a flowchart of a method that depicts supporting transmitting latency-sensitive uplink control on a secondary carrier, in accordance with aspects of the present disclosure. Detailed Description

[0102] A user equipment (UE) may be configured to perform multi-carrier communication using one or more cells associated with one or more primary carriers (e.g., primary component carriers (PCCs)) and one or more secondary carriers (e.g., secondary component carriers (SCCs)). In some examples, a cell may include a physical uplink control channel (PUCCH) group associated with the UE for multi-carrier communication. One cell may be designated as a primary cell (PCell), and one or more other cells may be designated as secondary cells. The PCell may be associated with a PCC (e.g., a primary carrier), and each secondary cell may be associated with one or more SCCs (e.g., secondary carriers).

[0103] In addition, some carriers may be configured for a time-division duplex (TDD) protocol, where each time slot (e.g., each transmission opportunity, mini-slot, time slot, etc.) is designated as a downlink time slot, an uplink time slot, or a flexible time slot (e.g., can be used for uplink or downlink communication, may include a switching gap for the UE to retune from a downlink transmission to an uplink transmission (and vice versa), etc.). Some carriers may be configured for a frequency-division duplex (FDD) protocol, where any time slot can be used for uplink or downlink communication. In some wireless communication systems, the UE may be limited to sending control information, such as PUCCH information (which may also be referred to herein as PUCCH), on a primary carrier. However, when the primary carrier is a TDD carrier (and other scenarios), this may result in a large delay in PUCCH transmission due to the uplink / downlink / flexible time slot configuration or pattern (e.g., uplink transmission is not allowed in a downlink time slot). Accordingly, aspects of the described techniques provide a mechanism in which the UE is able to send uplink control information, such as PUCCH information, on a secondary carrier or on both the primary carrier and the secondary carrier.

[0104] Aspects of the present disclosure are first described in the context of a wireless communication system. Generally speaking, the described techniques provide for a UE to transmit PUCCH information on a secondary carrier of a PUCCH group. The UE may receive downlink transmissions from cells of the PUCCH group on a primary carrier or one or more of the secondary carriers. The UE may identify or otherwise determine acknowledgment information for the downlink transmission (e.g., acknowledgment / negative acknowledgment (ACK / NACK) information, channel measurement reports associated with the downlink transmission, etc.). The UE may then select one or more of the primary carrier or secondary carriers to send feedback indicating the acknowledgment information to the base station. For example, the UE may receive a signal configuring a time slot pattern for the primary carrier or one or more of the secondary carriers, where the time slot patterns for different carriers may be selected such that instances of uplink time slots are more frequently interleaved. Thus, the UE may select one or more of the primary carrier or secondary carriers to send a feedback message (e.g., a PUCCH transmission) indicating the acknowledgment information to the base station (e.g., a cell), rather than sending the feedback message only on the primary carrier.

[0105] Aspects of the present disclosure are further illustrated by and described with reference to diagrams, system diagrams, and flowcharts of apparatus for transmitting delay-sensitive uplink control on a secondary carrier.

[0106] Figure 1 An example of a wireless communication system 100 supporting transmission of delay-sensitive uplink control on a secondary carrier in accordance with aspects of the present disclosure is shown. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, communication with low-cost and low-complexity devices, or any combination thereof.

[0107] The base stations 105 may be spread throughout a geographic area to form the wireless communication system 100 and may be devices of different forms or having different capabilities. The base stations 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110, and the UEs 115 and the base stations 105 may establish one or more communication links 125 over the coverage area 110. The coverage area 110 may be an example of a geographic area over which the base stations 105 and the UEs 115 may support transmission of signals according to one or more radio access technologies.

[0108] UE 115 can be spread throughout the coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary, or mobile, or both at different times. The UE 115 can be devices of different forms or with different capabilities. In Figure 1 Some example UEs 115 are shown. The UE 115 described herein can be capable of communicating with various types of devices, such as other UEs 115, base stations 105, or network devices (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network devices), as Figure 1 shown.

[0109] The base station 105 can communicate with the core network 130, or communicate with each other, or perform both of the above operations. For example, the base station 105 can interface with the core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). The base station 105 can communicate with each other directly (e.g., directly between base stations 105), or indirectly (e.g., via the core network 130), or both on the backhaul link 120 (e.g., via X2, Xn or other interfaces). In some examples, the backhaul link 120 can be or include one or more wireless links.

[0110] One or more of the base stations 105 described herein can include or can be referred to by those skilled in the art as base station transceivers, radio base stations, access points, radio transceivers, Node B, evolved Node B (eNB), next generation Node B or Gigabit Node B (any of which can be referred to as gNB), home Node B, home evolved Node B, or other suitable terms.

[0111] The UE 115 can include or can be referred to as a mobile device, wireless device, remote device, handheld device, or subscription device, or some other suitable term, where "device" can also be referred to as unit, station, terminal, or client, etc. The UE 115 can also include or can be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, the UE 115 can include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine type communication (MTC) device, etc., which can be implemented in various objects such as household appliances, or vehicles, meters, etc.

[0112] The UE 115 described herein is capable of communicating with various types of devices, such as other UEs 115 that can sometimes act as relays, as well as base stations 105 and network devices, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc., as Figure 1 shown.

[0113] The UE 115 and the base station 105 can wirelessly communicate with each other via one or more communication links 125 on one or more carriers. The term "carrier" may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating the operation of the carrier, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. According to the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used with both FDD component carriers and TDD component carriers.

[0114] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling for coordinating the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunications system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)) and may be placed according to a channel raster for discovery by the UE 115. A carrier may operate in independent mode, where the UE 115 may perform initial acquisition and connection via the carrier, or the carrier may operate in non-independent mode, where a different carrier (e.g., of the same or a different radio access technology) is used to anchor the connection.

[0115] The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105, or a downlink transmission from the base station 105 to the UE 115. A carrier may carry downlink or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0116] A carrier can be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth can be referred to as the "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth can be one of several defined bandwidths for a carrier of a specific radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communication system 100 (e.g., the base station 105, the UE 115, or both) can have a hardware configuration that supports communication on a specific carrier bandwidth or can be configurable to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 can include a base station 105 or a UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 can be configured to operate on a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0117] The signal waveform transmitted on a carrier can be composed of multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing an MCM technique, a resource element can include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and the subcarrier spacing are inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the more resource elements the UE 115 receives and the higher the order of the modulation scheme, the higher the data rate can be for the UE 115. Wireless communication resources can refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further increase the data rate or data integrity for communication with the UE 115.

[0118] One or more numerologies can be supported for a carrier, where a numerology can include a subcarrier spacing (Δf) and a cyclic prefix. A carrier can be divided into one or more BWPs having the same or different numerologies. In some examples, the UE 115 can be configured with multiple BWPs. In some examples, a single BWP for a carrier can be active at a given time, and communication for the UE 115 can be restricted to one or more active BWPs.

[0119] It can be in a basic time unit, which can for example refer to a sampling period of T s = 1 / (Δf max ·N f ) seconds, where Δf maxmay represent the maximum supported subcarrier spacing, and N f may represent a multiple of the maximum supported discrete Fourier transform (DFT) size) to represent a time interval for the base station 105 or the UE 115. The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0120] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a plurality of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a plurality of symbol periods (e.g., depending on the length of the cyclic prefix added in front of each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini-slots each containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f number of) sampling periods. The duration of the symbol period may depend on the subcarrier spacing or the operating frequency band.

[0121] A subframe, a time slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in the TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0122] Physical channels can be multiplexed on a carrier according to various techniques. For example, one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels on a downlink carrier. A control region for a physical control channel (e.g., a control resource set (CORESET)) can be defined by the number of symbol periods and can extend across the system bandwidth of the carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESETs) can be configured for a group of UEs 115. For example, one or more of the UEs 115 can monitor or search a control region for control information according to one or more search space sets, and each search space set can include one or more control channel candidates at one or more aggregation levels arranged in a cascaded manner. The aggregation level for a control channel candidate can refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with the coded information for a control information format having a given payload size. The search space sets can include a common search space set configured to send control information to multiple UEs 115 and a UE-specific search space set for sending control information to a specific UE 115.

[0123] Each base station 105 can provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" can refer to a logical communication entity for communicating (e.g., on a carrier) with the base station 105 and can be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or others) for distinguishing adjacent cells. In some examples, a cell can also refer to a geographic coverage area 110 or a portion of the geographic coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors (such as the capabilities of the base station 105), the scope of such a cell can range from a relatively small area (e.g., a structure, a subset of a structure) to a relatively large area. For example, a cell can be or include a building, a subset of a building, or an external space between or overlapping the geographic coverage areas 110, and so on.

[0124] Macro cells typically cover a relatively large geographical area (e.g., with a radius of several kilometers) and can allow unrestricted access by UEs 115 having a service subscription with the network provider that supports the macro cell. Compared to macro cells, small cells can be associated with lower-power base stations 105, and small cells can operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells can provide unrestricted access to UEs 115 having a service subscription with the network provider, or can provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a residence or office). Base station 105 can support one or more cells and can also support communication on one or more cells using one or more component carriers.

[0125] In some examples, a carrier can support multiple cells and can be configured with different cell configurations according to different protocol types that can provide access for different types of devices (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)).

[0126] In some examples, base station 105 can be movable and, thus, provide communication coverage for a mobile geographical coverage area 110. In some examples, different geographical coverage areas 110 associated with different technologies can overlap, but different geographical coverage areas 110 can be supported by the same base station 105. In other examples, overlapping geographical coverage areas 110 associated with different technologies can be supported by different base stations 105. The wireless communication system 100 can include, for example, a heterogeneous network in which different types of base stations 105 use the same or different radio access technologies to provide coverage for respective geographical coverage areas 110.

[0127] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, base stations 105 can have similar frame timings, and transmissions from different base stations 105 can be approximately aligned in time. For asynchronous operation, base stations 105 can have different frame timings, and in some examples, transmissions from different base stations 105 can not be aligned in time. The techniques described herein can be used for synchronous or asynchronous operation.

[0128] Some UEs 115 (e.g., MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with the base station 105 without human intervention. In some examples, M2M communication or MTC can include communication from devices integrated with sensors or meters to measure or capture information and relay such information to a central server or application, which utilizes the information or presents the information to a human interacting with the application. Some UEs 115 can be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, device monitoring, healthcare monitoring, wildlife monitoring, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business billing.

[0129] Some UEs 115 can be configured to operate in power-saving modes, e.g., half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception rather than simultaneous transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UEs 115 include entering a power-saving deep sleep mode when not participating in active communication, when operating over limited bandwidths (e.g., according to narrowband communication), or a combination of these techniques. For example, some UEs 115 can be configured for operation using a narrowband protocol type that is associated with a defined portion or range within a carrier, within a guard band of the carrier, or external to the carrier (e.g., a set of subcarriers or resource blocks (RBs)).

[0130] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. The UE115 can be designed to support ultra-reliable, low-latency, or critical functions (e.g., mission-critical functions). Ultra-reliable communication can include private communication or group communication and can be supported by one or more mission-critical services such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions can include prioritization of services, and mission-critical services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency can be used interchangeably herein.

[0131] In some examples, UE 115 is capable of communicating directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communication may be within the geographical coverage area 110 of base station 105. Other UEs 115 in such a group may be outside the geographical coverage area 110 of base station 105 or otherwise unable to receive transmissions from base station 105. In some examples, multiple groups of UEs 115 communicating via D2D communication may employ a one-to-many (1:M) system, where each UE 115 transmits to every other UE 115 in the group. In some examples, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving base station 105.

[0132] In some systems, D2D communication link 135 may be an example of a communication channel (e.g., a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination thereof. Vehicles may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information related to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (e.g., a roadside unit), or communicate with a network via one or more network nodes (e.g., base station 105) using vehicle-to-network (V2N) communication, or perform both operations.

[0133] The core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 can be an Evolved Packet Core (EPC) or a 5G Core (5GC), which can include at least one control plane entity that manages access and mobility (e.g., a Mobility Management Entity (MME), an Access and Mobility Management Function (AMF)) and at least one user plane entity that routes packets to or interconnects with an external network (e.g., a Serving Gateway (S-GW), a Packet Data Network (PDN) Gateway (P-GW), or a User Plane Function (UPF)). The control plane entity can manage Non-Access Stratum (NAS) functions such as mobility, authentication, and bearer management for a UE 115 served by a base station 105 associated with the core network 130. User IP packets can be transmitted through the user plane entity, which can provide IP address allocation and other functions. The user plane entity can be connected to a network operator IP service 150. The operator IP service 150 can include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or a packet-switched streaming service.

[0134] Some network devices in the wireless communication system 100 (e.g., the base station 105) can include subcomponents such as an access network entity 140, which can be an example of an Access Node Controller (ANC). Each access network entity 140 can communicate with a UE 115 through one or more other access network transmission entities 145 (which can be referred to as radio heads, intelligent radio heads, or Transmission / Reception Points (TRPs)). Each access network transmission entity 145 can include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 can be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., the base station 105).

[0135] The wireless communication system 100 can operate using one or more frequency bands (generally, in the range of 300 megahertz (MHz) to 300 gigahertz (GHz)). Generally, the region from 300 MHz to 3 GHz is known as the Ultra-High Frequency (UHF) region or the decimeter band because the wavelength range is approximately from one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, but the waves may be sufficient to penetrate structures to serve a UE 115 located indoors in a macro cell. Compared to transmissions using smaller frequencies and longer waves in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz, UHF wave transmissions can be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers).

[0136] The wireless communication system 100 may also operate in the super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also referred to as the centimeter band) or in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as the millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communication between the UE 115 and the base station 105, and compared to UHF antennas, the EHF antennas of the corresponding devices may be smaller and more closely spaced. In some examples, this may facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmissions, the propagation of EHF transmissions may suffer even greater atmospheric attenuation and shorter distances. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the designation of the frequency bands across these frequency regions may vary according to the country or regulatory body.

[0137] The wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ licensed-assisted access (LAA), LTE-unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed frequency band (such as the 5 GHz industrial, scientific, and medical (ISM) band). When operating in an unlicensed radio frequency spectrum band, devices (such as the base station 105 and the UE 115) may employ carrier sensing for collision detection and avoidance. In some examples, operation in the unlicensed frequency band may be based on a carrier aggregation configuration that combines component carriers operating in a licensed frequency band (e.g., LAA). Operations in the unlicensed spectrum may include downlink transmissions, uplink transmissions, peer-to-peer (P2P) transmissions, or device-to-device (D2D) transmissions, etc.

[0138] The base station 105 or the UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the base station 105 or the UE 115 may be located within one or more antenna arrays or antenna panels (which may support MIMO operation or transmit or receive beamforming). For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the base station 105 may be located at different geographical locations. The base station 105 may have an antenna array that has a number of rows and columns of antenna ports that the base station 105 may use to support beamforming for communication with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals transmitted via the antenna ports.

[0139] Base station 105 or UE 115 can use MIMO communication to take advantage of multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such a technique can be referred to as spatial multiplexing. For example, a transmitting device can transmit multiple signals via different antennas or different combinations of antennas. Similarly, a receiving device can receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) (where multiple spatial layers are transmitted to the same receiving device) and multi-user MIMO (MU-MIMO) (where multiple spatial layers are transmitted to multiple devices).

[0140] Beamforming (which can also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., base station 105, UE 115) to form or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals transmitted via the antenna elements of an antenna array such that some signals propagating in a particular orientation relative to the antenna array experience constructive interference while other signals experience destructive interference. The adjustment of the signals transmitted via the antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals carried via the antenna elements associated with the device. The adjustment associated with each antenna element can be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).

[0141] As part of the beamforming operation, base station 105 or UE 115 can use beam scanning techniques. For example, base station 105 can use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Base station 105 can transmit some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) multiple times in different directions. For example, base station 105 can transmit signals according to different sets of beamforming weights associated with different transmission directions. Transmissions in different beam directions can be used (e.g., by the transmitting device (such as base station 105) or by the receiving device (such as UE 115)) to identify the beam direction for subsequent transmissions or receptions by base station 105.

[0142] Base station 105 may transmit some signals (e.g., data signals associated with a particular receiving device (e.g., UE 115)) in a single beam direction (e.g., the direction associated with a particular receiving device). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on signals transmitted in one or more beam directions. For example, UE 115 may receive one or more of the signals transmitted by base station 105 in different directions, and may report to base station 105 an indication of the signal received by UE 115 that has the highest signal quality or otherwise acceptable signal quality.

[0143] In some examples, multiple beam directions may be used to perform transmissions by a device (e.g., by base station 105 or UE 115), and the device may use a combination of digital precoding or radio frequency beamforming to generate a combined beam for transmission (e.g., from base station 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across the system bandwidth or one or more subbands. Base station 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook). Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may employ similar techniques to transmit signals multiple times in different directions (e.g., for identifying beam directions for subsequent transmission or reception by UE 115) or to transmit signals in a single direction (e.g., for transmitting data to a receiving device).

[0144] When receiving various signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105, a receiving device (e.g., UE 115) may attempt multiple receive configurations (e.g., directional listening). For example, the receiving device may receive by receiving via different antenna sub-arrays, by processing received signals according to different antenna sub-arrays, by receiving according to different sets of receive beamforming weights (e.g., different sets of directional listening weights) applied to signals received at multiple antenna elements of the antenna array, or by processing received signals according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of the antenna array (any of the above operations may be referred to as "listening" according to different receive configurations or receive directions), thereby attempting multiple receive directions. In some examples, the receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving data signals). The single receive configuration may be aligned in a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, the highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

[0145] Wireless communication system 100 may be a packet-based network operating according to a hierarchical protocol stack. In the user plane, communication at the bearer or packet data convergence protocol (PDCP) layer may be IP-based. The radio link control (RLC) layer may perform packet segmentation and reassembly for transmission over logical channels. The medium access control (MAC) layer may perform priority handling and multiplexing of logical channels to transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer may provide the establishment, configuration, and maintenance of an RRC connection (which supports radio bearers for user plane data) between UE 115 and base station 105 or core network 130. At the physical layer, transport channels may be mapped to physical channels.

[0146] UE 115 and base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid Automatic Repeat reQuest (HARQ) feedback is a technique for increasing the likelihood that data is correctly received over communication link 125. HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat reQuest (ARQ)). HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions). In some examples, the device may support same-slot HARQ feedback, where the device may provide HARQ feedback for data received in previous symbols in a particular slot in that slot. In other cases, the device may provide HARQ feedback in a subsequent slot or according to some other time interval.

[0147] UE 115 may receive a downlink transmission from base station 105 on at least one of a primary carrier associated with a Physical Uplink Control Channel group or a secondary carrier associated with a Physical Uplink Control Channel group. UE 115 may determine acknowledgment information associated with UE 115 decoding the downlink transmission. UE 115 may select at least one of the primary carrier or the secondary carrier to send feedback to the base station at least in part based on determining the acknowledgment information. UE 115 may send a feedback message indicating the acknowledgment information using at least one of the primary carrier or the secondary carrier at least in part based on selecting at least one of the primary carrier or the secondary carrier.

[0148] Base station 105 may send a downlink transmission to UE 115 on at least one of a primary carrier associated with a Physical Uplink Control Channel group or a secondary carrier associated with a Physical Uplink Control Channel group. Base station 105 may receive a feedback message indicating the acknowledgment information using at least one of the primary carrier or the secondary carrier at least in part based on the selection of at least one of the primary carrier or the secondary carrier.

[0149] Figure 2 An example of a wireless communication system 200 supporting transmission of latency-sensitive uplink control on a secondary carrier in accordance with aspects of the present disclosure is shown. In some examples, wireless communication system 200 may implement aspects of wireless communication system 100. Wireless communication system 200 may include base station 205, base station 210, base station 215, and / or UE 220, which may be examples of the corresponding devices described herein. In some aspects, base station 205, base station 210, base station 215 may constitute or otherwise form a PUCCH group for UE 220 to support multi-carrier communication using at least a primary carrier and one or more secondary carriers.

[0150] As described above, the UE 220 may be configured to perform multi-carrier communication using one or more cells associated with at least a primary carrier (e.g., PCC) and secondary carriers (e.g., SCC). The cells may form a PUCCH group associated with the UE 220 for multi-carrier communication. In Figure 2 the example shown, the base stations 205, 210, and 215 may be considered cells within a PUCCH group for the UE 220 and thus form a PUCCH group for the UE 220. One cell (e.g., base station 205) may be designated as the PCell, and the other cells (e.g., base stations 210, 215) may be designated as secondary cells. The PCell may be associated with a PCC (e.g., primary carrier), and each secondary cell may be associated with one or more SCCs (e.g., secondary carriers). For example, base station 210 may be associated with a first secondary carrier (e.g., SCC1) and base station 215 may be associated with a second or additional secondary carrier (e.g., SCC2).

[0151] In addition, some carriers may be configured for the TDD protocol, where each time slot (e.g., each transmission opportunity, mini-slot, time slot, etc.) is designated as a downlink time slot, an uplink time slot, or a flexible time slot (e.g., can be used for uplink or downlink communication, may include a switching gap for the UE to re-tune from a downlink transmission to an uplink transmission (and vice versa), etc.). Some carriers may be configured for the FDD protocol, where any time slot can be used for uplink or downlink communication. In some wireless communication systems, the UE is only allowed to send PUCCH information on the primary carrier. However, when the primary carrier is a TDD carrier, this may result in a large delay in PUCCH transmission due to the uplink / downlink / flexible time slot configuration or pattern (e.g., uplink transmission is not allowed in a downlink time slot). Thus, aspects of the described techniques provide a mechanism in which the UE 220 is able to send PUCCH information on a secondary carrier (e.g., SCC1 and / or SCC2).

[0152] For example, the UE 220 may receive downlink transmissions (e.g., PDCCH and / or PDSCH) from cells of a PUCCH group on a primary carrier (e.g., on the PCC from the base station 205) and / or on secondary carriers (e.g., on SCC1 from the base station 210 and / or on SCC2 from the base station 215). The UE 220 may identify or otherwise determine acknowledgment information for the downlink transmission (e.g., based on whether the UE 220 can successfully decode the ACK / NACK information of the downlink transmission, a channel measurement report associated with the downlink transmission (e.g., CSI-RS measurement report), etc.). Then, the UE 220 may select a primary carrier (e.g., PCC) and / or secondary carriers (e.g., SCC1 and / or SCC2) to send feedback indicating the acknowledgment information to the base station (e.g., if the UE 220 selects the PCC, it is the base station 205; if the UE selects SCC1, it is the base station 210, etc.). The UE 220 may select a primary carrier and / or secondary carriers to send a feedback message indicating the acknowledgment information to the base station (e.g., PUCCH transmission) (depending on which carrier the UE 220 selects for PUCCH transmission).

[0153] In some aspects, this may include: when using the TDD protocol for uplink carrier aggregation (e.g., when all CCs in the PUCCH group are TDD carriers), the base station 205 (in this example, the PCell) may configure the TDD mode in a staggered / complementary manner (e.g., in the time domain) such that there is a maximum number of uplink time slots supporting uplink transmissions across all CCs. The base station 205 may send or otherwise convey a signal configuring the time slot format pattern, e.g., in RRC signaling, MAC CE, DCI, etc. In one non-limiting example, this may include: the base station 205 configures the time slot format pattern such that there is at least one carrier available for the UE 220 for uplink transmission in each time slot. For example, the UE 220 may receive a signal configuring the time slot format pattern for the primary carrier and / or secondary carriers, where the time slot patterns selected for different carriers are such that instances of uplink time slots are staggered to occur more frequently.

[0154] In Figure 2In the example shown, as an example, it should be understood that various carrier TDD / FDD configurations can be supported. That is, the PCC, SCC1, and / or SCC2 can be any combination of TDD carriers, FDD carriers, or TDD / FDD carriers. In one example, the PCC can be a TDD carrier, and SCC1 and / or SCC2 can be FDD carriers. In another example, the PCC can be an FDD carrier, and SCC1 and / or SCC2 can be TDD carriers. In another example, SCC1 can be a TDD carrier, and SCC2 can be an FDD carrier, and vice versa. Thus, aspects of the described techniques can be applied to any configuration of TDD / FDD carriers in a PUCCH group.

[0155] In some aspects, this can include: configuring PUCCH resources on each carrier in a PUCCH group to support PUCCH transmission on a secondary carrier. For example, the UE 220 can receive a signal from the base station 205 that configures a first resource set for sending a feedback message on a primary carrier (e.g., on the PCC), a second resource set for sending a feedback message on a secondary carrier (e.g., SCC1), a third resource set for sending a feedback message on an additional secondary carrier (e.g., SCC2), etc. The resources can include time resources, frequency resources, spatial resources, and / or code resources that are allocated for the transmission of PUCCH information on the corresponding carrier. In some aspects, the UE 220 can select a primary carrier (e.g., PCC) or a secondary carrier (e.g., SCC1 and / or SCC2) for sending a feedback message based on the configured resources and the resources required for sending the feedback message. For example, the UE 220 can determine the resource usage for sending a feedback message and select a primary carrier and / or a secondary carrier for sending the feedback information based on the available resources configured for the primary carrier and / or the secondary carrier.

[0156] In some aspects, the indication / determination of which carrier the UE 220 will use to send PUCCH information can be based on predefined priority rules, can be dynamically indicated (e.g., in DCI), can be semi-statically indicated (e.g., using RRC signaling), etc. Thus, the UE 220 can determine the priority rules associated with sending feedback messages on the primary carrier and the secondary carrier and select a carrier for sending the feedback message based on the priority rules.

[0157] Accordingly, the UE 220 can be configured (e.g., by the base station 205 (in this example, the PCell)) with default rules or priority rules, which can correspond to a first priority level associated with the PCC, a second priority level associated with the SCC1, a third priority level associated with the SCC 2, etc. without additional signaling. In some non-limiting examples, the first priority level can be a higher priority compared to the second priority level, the second priority level can be a higher priority compared to the third priority level, etc. In other non-limiting examples, the second priority level or the third priority level, etc. can be the highest priority level. That is, in the absence of additional signaling in the DCI, RRC, etc., if PUCCH transmission on a secondary carrier is enabled for the UE 220 (e.g., via RRC signaling), then in the time slot in which the UE 220 should feedback HARQ-ACK, the UE 220 can feedback HARQ-ACK on a carrier having sufficient uplink OFDM symbols to accommodate the PUCCH resources configured by the RRC, where the priority of the carrier starts from the PCC to the SCC1 to the SCC2, etc.

[0158] However, in some examples, when the UE 220 is to send PUCCH information, the base station 205 can use signaling to override the priority rules for carrier selection. As an example, for a dynamically scheduled PDSCH, in the DCI scheduling the PDSCH, the base station 205 can add a field to indicate the carrier index that the UE 220 will use to feedback HARQ-ACK. Accordingly, the UE 220 can receive an authorization (e.g., DCI from the base station 205) for scheduling a downlink transmission (e.g., PDSCH) and indicating the primary carrier (e.g., PCC) or secondary carriers (e.g., SCC1 and / or SCC2) for sending the feedback message. The UE 220 can select the primary carrier or a secondary carrier at least partially based on the authorization (e.g., DCI), e.g., can select the carrier corresponding to the carrier index indicated in the DCI.

[0159] In another example, for semi-persistent CSI and / or aperiodic CSI on the PUCCH (e.g., reference signal measurement reports such as CSI-RS reports), in the DCI that activates / schedules the semi-persistent CSI and / or periodic CSI, the base station 205 may add a field to indicate the carrier index that the UE 220 will use to transmit the CSI report on the PUCCH. For example, the UE 220 may receive authorization from the base station 205 that activates the semi-persistent resources for downlink transmission and indicates the primary carrier (e.g., PCC) or secondary carriers (e.g., SCC1 and / or SCC2) for sending the feedback message. In this example, the UE 220 may select the primary carrier and / or secondary carriers to send the feedback message based on the authorization rule. For example, it may select the carrier corresponding to the carrier index indicated in the DCI.

[0160] In another example, for periodic CSI on the PUCCH and / or ACK / NACK for the PDSCH based on semi-persistent scheduling (SPS), in the RRC that configures the PUCCH or SPS, the base station 205 may add a field to indicate the carrier index for transmitting the periodic CSI on the PUCCH. Thus, the UE 220 may receive a configuration signal from the base station 205 that indicates the semi-persistent resources for downlink transmission and indicates the primary carrier (e.g., PCC) or secondary carriers (e.g., SCC1 and / or SCC2) for sending the feedback message. In this example, the UE 220 may select the primary carrier and / or secondary carriers to send the feedback message based on the configuration signal. For example, it may select the carrier corresponding to the carrier index indicated in the DCI.

[0161] In another example, for a scheduling request (SR), the UE 220 may identify or otherwise determine that uplink information is available for transmission to the base station 205. Thus, in some examples, the feedback message may include an SR to the base station 205. In some examples, the SR may request resources (e.g., time resources, frequency resources, spatial resources, etc.) for transmitting the uplink information. In some examples, the UE 220 may select one or both of the primary carrier or secondary carriers based on the feedback message including the SR to send the feedback message to the base station 205 (e.g., SR via the PUCCH).

[0162] In some aspects, PUCCH transmissions on a secondary carrier can be UE-capability-based. For example, UE 220 can send or otherwise convey a message to base station 205 (e.g., the PCell in this example) that indicates the UE capabilities for sending feedback messages using the primary carrier and / or secondary carrier. Base station 205 can enable / disable, activate / deactivate, etc., PUCCH transmissions on the secondary carrier for UE 220 using, for example, RRC signaling, MAC CE, DCI, etc.

[0163] In some aspects, UE 220 can have uplink transmissions of different service types, and in some examples, these uplink transmissions can be sent on a secondary carrier. For example, UE 220 can have services such as URLLC, eMBB, etc., for uplink transmissions. In such cases, some examples can include allowing uplink transmissions (e.g., PUCCH and / or PUSCH) on a secondary carrier based on the service type (e.g., URLLC for latency reduction). In this example, UE 220 can send eMBB transmissions on the PCC. Thus, UE 220 can determine that an uplink transmission (e.g., URLLC) is scheduled to be sent to base station 205, and the uplink transmission has a corresponding service type supported for transmission on the secondary carrier. UE 220 can select a secondary carrier for the transmission of the uplink transmission (e.g., URLLC service) based on the service type. UE 220 can determine that a second uplink transmission (e.g., eMBB service) will be sent to base station 205, and the second uplink transmission has a corresponding second service type supported for transmission on the primary carrier. In this example, UE 220 can select the primary carrier for the transmission of the second uplink transmission according to its transmission type.

[0164] Figure 3 An example of a carrier configuration 300 that supports sending delay-sensitive uplink control on a secondary carrier in accordance with aspects of the present disclosure is shown. In some examples, carrier configuration 300 can be implemented by aspects of wireless communication system 100 and / or 200 or can implement aspects of wireless communication system 100 and / or 200. Aspects of carrier configuration 300 can be implemented by a base station and / or a UE (which can be examples of the corresponding devices described herein). For example, one or more base stations (e.g., cells) can constitute or otherwise form a PUCCH group for a UE that supports multi-carrier communication using at least a primary carrier and one or more secondary carriers.

[0165] For example, a UE may be configured to perform multi-carrier communication using one or more cells associated with at least a primary carrier (e.g., PCC) and a secondary carrier (e.g., SCC). The cells may form a PUCCH group associated with the UE for multi-carrier communication. One cell (e.g., one base station) may be designated as the PCell, and other cells (e.g., other base stations) may be designated as secondary cells. The PCell may be associated with a PCC (e.g., the primary carrier), and each secondary cell may be associated with one or more SCCs (e.g., secondary carriers).

[0166] In addition, some carriers may be configured for the TDD protocol, where each time slot 305 (e.g., each transmission opportunity, mini-slot, time slot, etc.) is designated as a downlink time slot 310, an uplink time slot 315, or a switching time slot 320 (e.g., can be used for uplink or downlink communication, may include a switching gap for the UE to retune from downlink transmission to uplink transmission (and vice versa), etc.). In some wireless communication systems, only the UE is allowed to send PUCCH information on the primary carrier. However, when the primary carrier is a TDD carrier, due to the uplink / downlink / flexible time slot configuration or mode (e.g., uplink transmission is not allowed in the downlink time slot), this may result in a large delay in PUCCH transmission. Therefore, aspects of the described techniques provide a mechanism in which the UE can send PUCCH information on a secondary carrier (e.g., SCC).

[0167] For example, the UE may receive a downlink transmission (e.g., PDCCH and / or PDSCH) from the cells of the PUCCH group on the primary carrier (e.g., on the PCC) and / or on a secondary carrier (e.g., on the SCC) during the downlink time slot 305. The UE may identify or otherwise determine the acknowledgment information for the downlink transmission (e.g., based on whether the UE can successfully decode the ACK / NACK information of the downlink transmission, the channel measurement report associated with the downlink transmission (such as the CSI-RS measurement report), etc.). Then, the UE may select the primary carrier (e.g., PCC) and / or a secondary carrier (e.g., SCC2) to send feedback indicating the acknowledgment information to the base station. Therefore, the UE may select the primary carrier and / or a secondary carrier to send a feedback message (e.g., PUCCH transmission) indicating the acknowledgment information to the base station (depending on which carrier the UE selects for PUCCH transmission).

[0168] In some aspects, this can include: when the TDD protocol is used for uplink carrier aggregation (e.g., when all CCs in a PUCCH group are TDD carriers), the base station (in this example, the PCell) can configure the TDD mode in a staggered / complementary manner (e.g., in the time domain) such that there is a maximum number of uplink time slots 315 that support uplink transmissions across all carriers. The base station can send or otherwise convey a signal configuring the slot format pattern, e.g., in RRC signaling, MAC CE, DCI, etc. In one non-limiting example, this can include: the base station configures the slot format pattern such that there is at least one carrier available for the UE for uplink transmission in each time slot 305. For example, the UE can receive a signal configuring the slot format pattern for the primary carrier and / or secondary carriers, where the slot patterns for different carriers are selected such that instances of uplink time slots 315 are staggered to occur more frequently.

[0169] Figure 3 The carrier configuration 300 shown in provides an example of a slot format pattern that can be signaled to a UE in accordance with aspects of the described techniques. The slot format pattern can include a first slot format pattern for the primary carrier and a second slot format pattern for the secondary carrier. For example, the first slot format pattern for the primary carrier (e.g., PCC) can include that the downlink time slot 310 is configured for a first subset of the initial symbols of time slots 305-a, 305-b, 305-c, the initial symbols of time slots 305-e, 305-f, and a first subset of the initial symbols of time slot 305-g. The second slot format pattern for the secondary carrier (e.g., SCC) can include that the downlink time slot 310 is configured for a first subset of the initial symbols of time slot 305-a, time slots 305-c, 305-d, a first subset of the initial symbols of time slot 305-e, time slots 305-g, and 305-h.

[0170] The first slot format pattern for the primary carrier (e.g., PCC) can include that the uplink time slot 315 is configured for a second subset of the last symbols of time slots 305-c, 305-d, a second subset of the last symbols of time slots 305-g, and time slot 305-h. The second slot format pattern for the secondary carrier (e.g., SCC) can include that the uplink time slot 315 is configured for a second subset of the last symbols of time slot 305-a, time slots 305-b, a second subset of the last symbols of time slot 305-e, and time slot 305-f.

[0171] The first time slot format pattern for a primary carrier (e.g., PCC) may include a switching period 320 configured during time slots 305-c and 305-g (e.g., during a third subset of the middle symbols of time slots 305-c and 305-g). The second time slot format pattern for a secondary carrier (e.g., SCC) may include a switching period 320 configured during time slots 305-a and 305-e (e.g., during a third subset of the middle symbols of time slots 305-a and 305-e).

[0172] Thus, the first time slot format pattern for the primary carrier and the second time slot format pattern for the secondary carrier together include interleaved instances of uplink time slot 315 for transmitting feedback messages in the time domain. In Figure 3 the non-limiting example shown, the first time slot format pattern and the second time slot format pattern provide instances of uplink time slot 315 for transmitting feedback messages that occur every other time slot 305 in the time domain.

[0173] Of course, it should be understood that when additional secondary carriers are provided or otherwise configured within a PUCCH group, additional time slot format patterns may be configured for the additional secondary carriers, which reduces the instances between uplink time slots 315 configured across carriers.

[0174] Figure 4 An example of a carrier configuration 400 that supports transmitting delay-sensitive uplink control on a secondary carrier in accordance with aspects of the present disclosure is shown. In some examples, carrier configuration 400 may be implemented by aspects of wireless communication system 100 and / or 200 and / or carrier configuration 300 or may implement aspects of wireless communication system 100 and / or 200 and / or carrier configuration 300. Aspects of carrier configuration 400 may be implemented by a base station and / or a UE, which may be examples of the corresponding devices described herein. For example, one or more base stations (e.g., cells) may constitute or otherwise form a PUCCH group of a UE that supports multi-carrier communication using at least a primary carrier and one or more secondary carriers.

[0175] For example, a UE may be configured to perform multi-carrier communication using one or more cells associated with at least a primary carrier (e.g., PCC) and a secondary carrier (e.g., SCC). The cells may constitute a PUCCH group associated with the UE for multi-carrier communication. One cell (e.g., one base station) may be designated as a PCell, and other cells (e.g., other base stations) may be designated as secondary cells. The PCell may be associated with a PCC (e.g., a primary carrier), and each secondary cell may be associated with one or more SCCs (e.g., secondary carriers).

[0176] In addition, some carriers may be configured for a TDD protocol, where each time slot (e.g., each transmission opportunity, mini-slot, time slot, etc.) is designated as a downlink time slot 415, an uplink time slot 420, or a switching period 425 (e.g., can be used for uplink or downlink communication, can include a switching gap for the UE to retune from downlink transmission to uplink transmission (and vice versa), etc.). In addition, some carriers in the PUCCH group may be configured with different sub-carrier spacing (SCS) configurations, which may result in time slots with different durations. In Figure 4 In the non-limiting example shown, the primary carrier (e.g., PCC) has an SCS that provides a duration of time slot 405 on the PCC that is twice the duration of time slot 410 on a secondary carrier with a different SCS. For example, time slot 410-a and time slot 410-b of the SCC may have a duration that spans the same duration as time slot 405-a of the PCC in the time domain, time slot 410-c and time slot 410-d of the SCC may have a duration that spans the same duration as time slot 405-b of the PCC in the time domain, time slot 410-e and time slot 410-f of the SCC may have a duration that spans the same duration as time slot 405-c of the PCC in the time domain, and time slot 410-g and time slot 410-h of the SCC may have a duration that spans the same duration as time slot 405-d of the PCC in the time domain.

[0177] In some wireless communication systems, only the UE is allowed to send PUCCH information on the primary carrier. However, when the primary carrier is a TDD carrier, this may result in a large delay in PUCCH transmission due to the uplink / downlink / flexible time slot configuration or mode (e.g., uplink transmission is not allowed in a downlink time slot). Therefore, aspects of the described techniques provide a mechanism where the UE is able to send PUCCH information on a secondary carrier (e.g., SCC).

[0178] For example, the UE may receive downlink transmissions (e.g., PDCCH 430 during time slot 405-a (which schedules PDSCH 435 during time slot 405-b), and acknowledgment information 440 during time slot 405-d on the PCC and / or PDCCH 450 during time slot 410-b (which schedules PDSCH 455 during time slot 410-e), and acknowledgment information 460 during time slot 410-h) from the cells of the PUCCH group during one or more downlink time slots 415 on the primary carrier (e.g., on the PCC) and / or on a secondary carrier (e.g., on the SCC).

[0179] The UE can identify or otherwise determine the acknowledgment information 440 / 460 for a corresponding downlink transmission (e.g., based on whether the UE can successfully decode the ACK / NACK information of the downlink transmission, the channel measurement report associated with the downlink transmission (such as the CSI-RS measurement report), etc.). Then, the UE can select a primary carrier (e.g., PCC) and / or a secondary carrier (e.g., SCC) to send feedback indicating the acknowledgment information 440 / 460 to the base station. Thus, the UE can select a primary carrier and / or a secondary carrier to send a feedback message (e.g., PUCCH transmission) indicating the acknowledgment information 440 / 460 to the base station (depending on which carrier the UE selects for PUCCH transmission).

[0180] In some aspects, this may result in overlapping uplink time slots 420 on the primary carrier and the secondary carrier. In this case, the UE can identify or otherwise select the primary carrier (e.g., PCC) and the secondary carrier (e.g., SCC) for sending the feedback message. The UE can send the feedback message on both the primary carrier and the secondary carrier. In some aspects, different options can be supported for the transmission of the feedback message on the primary carrier and the secondary carrier.

[0181] One option can include the UE transmitting HARQ-ACKs in parallel on the PCC / SCC respectively (e.g., without combining multiple HARQ-ACK codebooks into one HARQ-ACK codebook). For example, the UE can implement a separate codebook construction and downlink assignment indicator (DAI) mechanism on a per-carrier basis. This can include the UE receiving a downlink transmission on the PCC (e.g., PDCCH 430 scheduling PDSCH 435 and acknowledgement information 440), and determining the acknowledgement information 440 for the downlink transmission (e.g., based on whether the UE can successfully receive and decode PDCCH 430 and / or PDSCH 435). The UE can construct a first codebook for the downlink transmission on the PCC, and send an indication of the codebook in the acknowledgement information 440 provided in the feedback message transmitted during slot 405-d. For the SCC, this can include the UE receiving a downlink transmission on the SCC (e.g., PDCCH 450 scheduling PDSCH 455 and acknowledgement information 460), and determining the acknowledgement information 460 for the downlink transmission (e.g., based on whether the UE can successfully receive and decode PDCCH 450 and PDSCH 455). The UE can construct a second codebook for the downlink transmission on the SCC, and send an indication of the codebook in the acknowledgement information 460 provided in the feedback message transmitted during slot 410-h. Thus, the UE can send a first feedback message using a first codebook generated at least in part based on the downlink transmission received on the primary carrier. The UE can send a second feedback message using a second codebook generated at least in part based on the downlink transmission received on the secondary carrier.

[0182] Another option can include: When multiple DCIs / RRCs point to HARQ-ACK transmissions in overlapping uplink time slots 420 or handover periods 425, the UE can send a combined HARQ-ACK codebook in the HARQ-ACK resource after the most recently received DCI. For example, the UE can implement a single codebook construction / DAI mechanism for downlink transmissions received on the PCC and SCC. This can include the UE receiving downlink transmissions on the PCC (e.g., PDCCH 430 scheduling PDSCH 435 and acknowledgment information 440) and downlink transmissions on the SCC (e.g., PDSCH 450 scheduling PDSCH 455 and acknowledgment information 460). The UE can determine the acknowledgment information 440 / 460 for the downlink transmissions (e.g., based on whether the UE can successfully receive and decode PDCCH 430, PDSCH 435, PDCCH 450, and / or PDSCH 455). The UE can construct a combined codebook for the downlink transmissions on the PCC and SCC and send an indication of the combined codebook in the acknowledgment information 440 provided in the feedback message sent during time slot 405-d and in the acknowledgment information 460 provided in the feedback message sent during time slot 410-h. In this example, the acknowledgment information 440 is the same as the acknowledgment information 460 (e.g., the combined codebook). Thus, the UE can send feedback messages on the primary carrier and the secondary carrier using a combined codebook generated at least in part based on downlink transmissions received on the primary carrier and the secondary carrier.

[0183] Figure 5 FIG. shows an example of a carrier configuration 500 that supports transmitting delay-sensitive uplink control on a secondary carrier, in accordance with aspects of the present disclosure. In some examples, carrier configuration 500 may be implemented by aspects of wireless communication system 100 and / or 200 and / or carrier configuration 300 and / or 400 or may implement aspects of wireless communication system 100 and / or 200 and / or carrier configuration 300 and / or 400. Aspects of carrier configuration 500 may be implemented by a base station and / or a UE, which may be examples of the corresponding devices described herein. For example, one or more base stations (e.g., cells) may constitute or otherwise form a PUCCH group of a UE that supports multi-carrier communication using at least a primary carrier and one or more secondary carriers.

[0184] For example, a UE may be configured to perform multi-carrier communication using one or more cells associated with at least a primary carrier (e.g., PCC) and a secondary carrier (e.g., SCC). The cells may form a PUCCH group associated with the UE for multi-carrier communication. One cell (e.g., one base station) may be designated as the PCell, and other cells (e.g., other base stations) may be designated as secondary cells. The PCell may be associated with a PCC (e.g., a primary carrier), and each secondary cell may be associated with one or more SCCs (e.g., secondary carriers).

[0185] In addition, some carriers may be configured for the TDD protocol, where each time slot (e.g., each transmission opportunity, mini-slot, time slot, etc.) is designated as a downlink time slot 515, an uplink time slot 520, or a switching period 525 (e.g., can be used for uplink or downlink communication, may include a switching gap for the UE to retune from downlink transmission to uplink transmission (and vice versa), etc.). In addition, some carriers in the PUCCH group may be configured with different sub-carrier spacing (SCS) configurations, which may result in time slots with different durations. In Figure 5 the non-limiting example shown, the primary carrier (e.g., PCC) has an SCS that provides a duration of time slot 505 on the PCC that is twice the duration of time slot 510 on a secondary carrier with a different SCS. For example, time slot 510-a and time slot 510-b of the SCC may have a duration that spans the same duration as time slot 505-a of the PCC in the time domain, time slot 510-c and time slot 510-d of the SCC may have a duration that spans the same duration as time slot 505-b of the PCC in the time domain, time slot 510-e and time slot 510-f of the SCC may have a duration that spans the same duration as time slot 505-c of the PCC in the time domain, and time slot 510-g and time slot 510-h of the SCC may have a duration that spans the same duration as time slot 505-d of the PCC in the time domain.

[0186] In some wireless communication systems, only allowing the UE to send PUCCH information on the primary carrier. However, when the primary carrier is a TDD carrier, due to the uplink / downlink / flexible time slot configuration or mode (e.g., uplink transmission is not allowed in a downlink time slot), this may result in a large delay in PUCCH transmission. Therefore, aspects of the described techniques provide a mechanism where the UE can send PUCCH information on a secondary carrier (e.g., SCC).

[0187] For example, during one or more downlink time slots 515, a UE may receive downlink transmissions from cells of a PUCCH group on a primary carrier (e.g., on a PCC) and / or on a secondary carrier (e.g., on an SCC). For example, during time slot 505-a, a PDCCH 530 (which schedules a PDSCH 535 during time slot 505-b), and during time slot 505-d on the PCC, an acknowledgement message 540 and / or during time slot 510-e, a PDCCH 550 (which schedules a PDSCH 555 during time slot 510-f), and during time slot 510-h, an acknowledgement message 560.

[0188] The UE may identify or otherwise determine the acknowledgement message 540 / 560 for the corresponding downlink transmission (e.g., based on whether the UE can successfully decode the ACK / NACK information of the downlink transmission, a channel measurement report associated with the downlink transmission (such as a CSI-RS measurement report), etc.). Then, the UE may select a primary carrier (e.g., PCC) and / or a secondary carrier (e.g., SCC) to send feedback indicating the acknowledgement message 540 / 560 to the base station. Thus, the UE may select a primary carrier and / or a secondary carrier to send a feedback message (e.g., a PUCCH transmission) indicating the acknowledgement message 540 / 560 to the base station (depending on which carrier the UE selects for PUCCH transmission).

[0189] As described above, there may be overlapping uplink time slots 520 on the primary carrier and the secondary carrier. In this case, the UE may identify or otherwise select a primary carrier (e.g., PCC) and a secondary carrier (e.g., SCC) for sending the feedback message. The UE may send the feedback message on both the primary carrier and the secondary carrier. An option that may support this technique may include: when multiple DCIs / RRCs point to HARQ-ACK transmissions in overlapping uplink time slots 520 or handover periods 525, the UE may send a combined HARQ-ACK codebook in the HARQ-ACK resource after the most recently received DCI. For example, the UE may implement a single codebook construction / DAI mechanism for downlink transmissions received on the PCC and SCC. Thus, the UE may use a combined codebook generated at least partially based on downlink transmissions received on the primary carrier and the secondary carrier to send the feedback message on the primary carrier and the secondary carrier.

[0190] In some aspects, the construction of the combined codebook may require sufficient time for processing such that various time thresholds can be configured separately for the downlink transmissions and the corresponding acknowledgment information 540 and / or 560 on the PCC and SCC. This can allow the UE sufficient turnaround time to combine the HARQ-ACK codebooks for the downlink transmissions received on the PCC and SCC and switch to the carrier after the last received DCI. In this case, a first threshold (T_Threshold 1) can be defined relative to the last received DCI before the first OFDM symbol in the overlapping uplink time slot 520 (e.g., the ACK / NACK resource corresponding to the first OFDM symbol of time slot 505-d on the PCC). That is, the grant (e.g., the DCI transmitted in PDCCH 530 and / or PDCCH 550) scheduling the downlink transmission (e.g., PDSCH 535 and / or PDSCH 555) can be received for the first threshold duration before the feedback message is sent. In Figure 5 the example shown, the grant received on the PCC (e.g., PDCCH 530) does not meet the first threshold duration (e.g., T_Threshold 1) before the acknowledgment information 540 is sent, but the grant received on the SCC (e.g., PDCCH 550) meets the first threshold duration (e.g., T_Threshold 1) before the acknowledgment information 560 is sent.

[0191] Additionally, a second threshold (e.g., T_Threshold 2) can be defined relative to the last received PDSCH and the first OFDM symbol in the overlapping uplink time slot 520. That is, the downlink transmission (e.g., PDSCH 535 and / or PDSCH 555) scheduled by the grant (e.g., PDCCH 530 and / or PDCCH 550) can be received for the second threshold duration before the feedback message (e.g., the acknowledgment information 560) is sent. In Figure 5 the example shown, the downlink transmission received on the PCC (e.g., PDSCH 535) does not meet the second threshold duration (e.g., T_Threshold 2) before the acknowledgment information 540 is sent, but the downlink transmission received on the SCC (e.g., PDSCH 555) meets the second threshold duration (e.g., T_Threshold 2) before the acknowledgment information 560 is sent.

[0192] Accordingly, aspects of the described techniques may support a PUCCH group being configured such that when a downlink transmission is scheduled for a UE on a PCC and / or SCC, a first threshold duration (e.g., T_Threshold 1) and a second threshold duration (e.g., T_Threshold 2) are considered.

[0193] Figure 6 An example of process 600 that supports transmitting latency-sensitive uplink control on a secondary carrier in accordance with aspects of the present disclosure is shown. In some examples, process 600 may be implemented by or may implement aspects of wireless communication system 100 and / or 200 and / or carrier configurations 300, 400, and / or 500. Aspects of process 600 may be implemented by base station 605 and / or UE 610, which may be examples of corresponding devices described herein. In some aspects, base station 605 may be part of a PUCCH group configured for UE 610, and UE 610 supports multi-carrier communication using at least a primary carrier and a secondary carrier. In a non-limiting example, base station 605 may be a PCell in the PUCCH group of UE 610.

[0194] At 615, base station 605 may transmit (and UE 610 may receive) a downlink transmission on a primary carrier and / or a secondary carrier associated with the PUCCH group. In some aspects, UE 610 may determine an authorization to receive a scheduled downlink transmission for a first threshold duration before transmitting a feedback message. In some aspects, UE 610 may determine to receive a downlink transmission for a second threshold duration before transmitting a feedback message. In some aspects, this may include UE 610 transmitting (and base station 605 receiving) a message indicating UE capabilities for transmitting a feedback message using the primary carrier and / or the secondary carrier.

[0195] At 620, UE 610 may determine acknowledgement information associated with the UE decoding the downlink transmission. In some aspects, this may include UE 610 determining whether it is able to successfully receive and decode the PDCCH and / or PDSCH of the downlink transmission. For example, the acknowledgement information may be positive acknowledgement information (e.g., ACK) or negative acknowledgement information (e.g., NACK).

[0196] At 625, the UE 610 may select a primary carrier and / or a secondary carrier to send feedback to the base station 605 based on the acknowledgment information. In some aspects, this may include the base station 605 sending (and the UE 610 receiving) a signal configuring a first time slot format pattern for the primary carrier and a second time slot format pattern for the secondary carrier. In some aspects, the UE 610 may select a primary carrier and / or a secondary carrier for sending a feedback message based on the first time slot format pattern and / or the second time slot format pattern. In some aspects, the first time slot format pattern and the second time slot format pattern may define interleaved instances of uplink time slots available for sending a feedback message in the time domain.

[0197] In some aspects, this may be based on the base station 605 sending (and the UE 610 receiving) a signal that configures a first resource set for sending a feedback message on the primary carrier and a second resource set for sending a feedback message on the secondary carrier. For example, the UE 610 may determine the resource usage for sending a feedback message and the available resources in the first resource set and / or the second resource set. The UE 610 may select a primary carrier and / or a secondary carrier based on the available resources satisfying the resource usage for sending a feedback message.

[0198] In some aspects, this may be based on priority rules. For example, the UE 610 may determine priority rules associated with sending a feedback message on the primary carrier and / or the secondary carrier. The UE 610 may select a primary carrier and / or a secondary carrier based on the priority rules and the available resources configured for sending a feedback message satisfying the resource usage for sending a feedback message. The priority rules may include a first priority associated with the primary carrier and a second priority associated with the secondary carrier, where the first priority is a higher priority compared to the second priority. Similarly, the priority rules may include a second priority associated with a secondary carrier (e.g., SCC1) and a third priority associated with an additional secondary carrier (e.g., SCC2), where the second priority is a higher priority compared to the third priority.

[0199] In some aspects, the priority rules can be overridden by various signaling. For example, the base station 605 can send (and the UE 610 can receive) an authorization for scheduling a downlink transmission and indicating a primary carrier and / or a secondary carrier for sending a feedback message. The UE 610 can select the primary carrier and / or the secondary carrier to send the feedback message, as indicated in the authorization for scheduling the downlink transmission, which overrides the priority rules. In another example, the base station 605 can send (and the UE 610 can receive) an activation of semi-persistent resources for downlink transmission and an authorization indicating a primary carrier and / or a secondary carrier for sending a feedback message. The UE 610 can select the primary carrier and / or the secondary carrier, as indicated in the authorization for the transmission of the feedback message, which can override the priority rules. In another example, the base station 605 can send (and the UE 610 can receive) a configuration signal indicating semi-persistent resources for downlink transmission and indicating a primary carrier and / or a secondary carrier for sending a feedback message. The UE 610 can select the primary carrier and / or the secondary carrier, as indicated in the configuration signal for sending the feedback message, which can override the priority rules.

[0200] At 630, the UE 610 can use the primary carrier and / or the secondary carrier to send (and the base station 605 can receive) a feedback message indicating acknowledgement information. In some aspects, sending the feedback message can be at least partially based on a first threshold duration and / or a second threshold duration.

[0201] In some aspects, this can include the UE 610 selecting both the primary carrier and the secondary carrier to send the feedback message. For example, the UE 610 can send a first feedback message on the primary carrier using a first codebook generated based on the downlink transmission received on the primary carrier. The UE 610 can send a second feedback message in the secondary carrier using a second codebook generated based on the downlink transmission received on the secondary carrier. In another example, the UE 610 can send the feedback message on both the primary carrier and the secondary carrier using a combined codebook generated based on the downlink transmissions received on the primary carrier and the secondary carrier.

[0202] In some aspects, this can include the UE 610 determining that an uplink transmission is scheduled to be sent to the base station 605. The UE 610 can determine that the traffic type associated with the uplink transmission is a traffic type supported by the UE for transmission on a secondary carrier (e.g., URLLC traffic type), and thus select a secondary carrier for the transmission of the uplink transmission. The UE 610 can determine that a second uplink transmission is scheduled to be sent to the base station 605. The UE 610 can determine that the second traffic type associated with the second uplink transmission is a second traffic type supported by the UE for transmission on a primary carrier (e.g., eMBB traffic type). The UE 610 can select a primary carrier for the transmission of the second uplink transmission based on the second traffic type.

[0203] Figure 7 FIG. 700 is a block diagram of a device 705 that supports transmitting latency-sensitive uplink control on a secondary carrier in accordance with aspects of the present disclosure. The device 705 can be an example of aspects of the UE 115 described herein. The device 705 can include a receiver 710, a communication manager 715, and a transmitter 720. The device 705 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0204] The receiver 710 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to transmitting latency-sensitive uplink control on a secondary carrier, etc.). The information can be passed to other components of the device 705. The receiver 710 can be an example of aspects of the transceiver 1020 described Figure 10 herein. The receiver 710 can employ a single antenna or a group of antennas.

[0205] The communication manager 715 can receive a downlink transmission from the base station on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group. The communication manager 715 can determine acknowledgment information associated with the UE decoding the downlink transmission. The communication manager 715 can select at least one of the primary carrier or the secondary carrier to send feedback to the base station based on determining the acknowledgment information. The communication manager 715 can send a feedback message indicating the acknowledgment information using at least one of the primary carrier or the secondary carrier based on selecting at least one of the primary carrier or the secondary carrier. The communication manager 715 can be an example of aspects of the communication manager 1010 described herein.

[0206] The communication manager 715 may select at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group to send a PUCCH message to a base station. The communication manager 715 may use at least one of the primary carrier or the secondary carrier to send the PUCCH message to the base station, at least in part based on the selection of at least one of the primary carrier or the secondary carrier.

[0207] The communication manager 715 or its subcomponents may be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 715 or its subcomponents may be performed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0208] The communication manager 715 or its subcomponents may be physically located at various positions, including being distributed such that portions of the functions are implemented by one or more physical components at different physical locations. In some examples, in accordance with various aspects of this disclosure, the communication manager 715 or its subcomponents may be separate and distinct components. In some examples, in accordance with various aspects of this disclosure, the communication manager 715 or its subcomponents may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or combinations thereof.

[0209] The transmitter 720 may send signals generated by other components of the device 705. In some examples, the transmitter 720 may be co-located with the receiver 710 in a transceiver module. For example, the transmitter 720 may be an example of aspects of the transceiver 1020 described with reference to Figure 10 The transmitter 720 may employ a single antenna or a group of antennas.

[0210] Figure 8 Block diagram 800 illustrates a device 805 in accordance with various aspects of this disclosure that supports sending latency-sensitive uplink control on a secondary carrier. The device 805 may be an example of aspects of the device 705 or UE 115 described herein. The device 805 may include a receiver 810, a communication manager 815, and a transmitter 840. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0211] The receiver 810 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to transmitting latency-sensitive uplink control on a secondary carrier, etc.). The information can be passed to other components of the device 805. The receiver 810 can be an example of aspects of the transceiver 1020 described with reference to Figure 10 The receiver 810 can utilize a single antenna or a set of antennas.

[0212] The communication manager 815 can be an example of aspects of the communication manager 715 described herein. The communication manager 815 can include a DL transmission manager 820, an acknowledgment information manager 825, a carrier selection manager 830, and a feedback message manager 835. The communication manager 815 can be an example of aspects of the communication manager 1010 described herein.

[0213] The DL transmission manager 820 can receive a downlink transmission from a base station on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group.

[0214] The acknowledgment information manager 825 can determine acknowledgment information associated with the UE decoding the downlink transmission.

[0215] The carrier selection manager 830 can select at least one of a primary carrier or a secondary carrier to send feedback to the base station based on determining the acknowledgment information. The carrier selection manager 830 can select at least one of a primary carrier associated with the PUCCH group or a secondary carrier associated with the PUCCH group to send a PUCCH message to the base station.

[0216] The feedback message manager 835 can use at least one of the primary carrier or the secondary carrier to send a feedback message indicating the acknowledgment information based on selecting at least one of the primary carrier or the secondary carrier. The feedback message manager 835 can use at least one of the primary carrier or the secondary carrier to send a PUCCH message to the base station at least in part based on selecting at least one of the primary carrier or the secondary carrier.

[0217] The transmitter 840 can send signals generated by other components of the device 805. In some examples, the transmitter 840 can be co-located with the receiver 810 in a transceiver module. For example, the transmitter 840 can be an example of aspects of the transceiver 1020 described with reference to Figure 10 The transmitter 840 can employ a single antenna or a set of antennas.

[0218] Figure 9Block diagram 900 shows a communication manager 905 that supports transmitting latency - sensitive uplink control on a secondary carrier, in accordance with aspects of the present disclosure. The communication manager 905 may be an example of aspects of the communication manager 715, communication manager 815, or communication manager 1010 described herein. The communication manager 1105 may include a DL transmission manager 910, an acknowledgement information manager 915, a carrier selection manager 920, a feedback message manager 925, a time slot format mode manager 930, a UE capability manager 935, a resource configuration manager 940, a priority rule manager 945, a multi - carrier transmission manager 950, and a multi - transmission manager 955. Each of these modules may communicate directly or indirectly with one another (e.g., via one or more buses).

[0219] The DL transmission manager 910 may receive a downlink transmission from a base station on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group.

[0220] The acknowledgement information manager 915 may determine acknowledgement information associated with the UE decoding the downlink transmission. In some cases, the acknowledgement information includes at least one of an acknowledgement or a negative acknowledgement.

[0221] The carrier selection manager 920 may select at least one of a primary carrier or a secondary carrier to send feedback to the base station based on determining the acknowledgement information. In some cases, the primary carrier, the secondary carrier, or a combination thereof includes a TDD carrier, an FDD carrier, or both. The carrier selection manager 920 may select at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group to send a PUCCH message to the base station.

[0222] The feedback message manager 925 may use at least one of the primary carrier or the secondary carrier to send a feedback message indicating the acknowledgement information based on selecting at least one of the primary carrier or the secondary carrier. In some cases, the feedback message includes a HARQ - ACK message, a reference signal measurement report transmission (e.g., a CSI - RS measurement report), an SR, or a combination thereof. The feedback message manager 925 may use at least one of the primary carrier or the secondary carrier to send a PUCCH message to the base station based at least in part on selecting at least one of the primary carrier or the secondary carrier.

[0223] The slot format pattern manager 930 may receive a signal configuring a first slot format pattern for a primary carrier and a second slot format pattern for a secondary carrier, where the selection is based on the first slot format pattern, the second slot format pattern, or a combination thereof. In some examples, the slot format pattern manager 930 may determine an authorization for scheduling a downlink transmission received for a first threshold duration prior to transmitting a feedback message. In some examples, the slot format pattern manager 930 may determine a downlink transmission received for a second threshold duration prior to transmitting a feedback message, where transmitting the feedback message is based on the first threshold duration and the second threshold duration.

[0224] In some cases, the first slot format pattern and the second slot format pattern together include interleaved instances of uplink slots available for transmitting a feedback message in the time domain. In some cases, the interleaved instances include uplink slots available on the primary carrier, the secondary carrier, or both during each slot.

[0225] The UE capability manager 935 may send a message indicating a UE capability for transmitting a feedback message using at least one of a primary carrier or a secondary carrier, where receiving a downlink transmission on at least one of the primary carrier or the secondary carrier is based on the UE capability. The UE capability manager 935 may send a message indicating a UE capability for transmitting a PUCCH message using at least one of a primary carrier or a secondary carrier, where selecting at least one of the primary carrier or the secondary carrier is at least partially based on the UE capability.

[0226] The resource configuration manager 940 may receive a signal that configures a first resource set for transmitting a feedback message on a primary carrier and a second resource set for transmitting a feedback message on a secondary carrier, where the selection is based on the first resource set and the second resource set. In some examples, the resource configuration manager 940 may receive a signal that configures a first resource set for transmitting a PUCCH message on a primary carrier and a second resource set for transmitting a PUCCH message on a secondary carrier, where the selection is based on the first resource set and the second resource set. In some examples, the resource configuration manager 940 may determine a resource usage for transmitting a feedback message. In some examples, the resource configuration manager 940 may determine available resources in the first resource set and available resources in the second resource set, where the selection is based on the available resources satisfying the resource usage for transmitting a feedback message. In some examples, the resource configuration manager 940 may determine a resource usage for transmitting a PUCCH message. In some examples, the resource configuration manager 940 may determine available resources in the first resource set and available resources in the second resource set, where the selection is based on the available resources satisfying the resource usage for transmitting a PUCCH message.

[0227] The priority rule manager 945 may determine priority rules associated with sending feedback messages on the primary carrier and the secondary carrier, wherein the selection is based on the priority rules and the available resources configured for sending feedback messages meet the resource usage for sending feedback messages. The priority rule manager 945 may determine priority rules associated with sending PUCCH messages on the primary carrier and the secondary carrier, wherein the selection is based on the priority rules and the available resources configured for sending feedback messages meet the resource usage for sending PUCCH messages. In some examples, the priority rule manager 945 may receive an authorization for scheduling a downlink transmission and indicating a primary carrier or a secondary carrier for sending feedback messages. In some examples, the priority rule manager 945 may receive an activation of semi-persistent resources for a downlink transmission and indicating a primary carrier or a secondary carrier for sending feedback messages.

[0228] In some examples, the priority rule manager 945 may receive a configuration signal indicating semi-persistent resources for a downlink transmission and indicating a primary carrier or a secondary carrier for sending feedback messages. In some examples, the priority rule manager 945 may receive a configuration signal indicating semi-persistent resources for a downlink transmission and indicating a primary carrier or a secondary carrier for sending PUCCH messages. In some cases, the priority rules include a first priority associated with the primary carrier and a second priority associated with the secondary carrier, and the first priority is a higher priority than the second priority. In some cases, the priority rules include a second priority associated with the secondary carrier and a third priority associated with an additional secondary carrier, and the second priority is a higher priority than the third priority. In some cases, selecting at least one of the primary carrier or the secondary carrier for sending feedback messages based on the authorization overrides the priority rules. In some cases, selecting at least one of the primary carrier or the secondary carrier for sending feedback messages based on the configuration signal overrides the priority rules.

[0229] The multi-carrier transmission manager 950 may select a primary carrier and a secondary carrier for sending feedback messages. In some examples, the multi-carrier transmission manager 950 may send a first feedback message on the primary carrier using a first codebook generated based on one or more downlink transmissions received on the primary carrier. In some examples, the multi-carrier transmission manager 950 may send a second feedback message on the secondary carrier using a second codebook generated based on one or more downlink transmissions received on the secondary carrier. In some examples, the multi-carrier transmission manager 950 may send feedback messages on the primary carrier and the secondary carrier using a combined codebook generated based on one or more downlink transmissions received on the primary carrier and the secondary carrier.

[0230] The multi-carrier transmission manager 950 may select a primary carrier and a secondary carrier for transmitting PUCCH messages. In some examples, the multi-carrier transmission manager 950 may use a first codebook generated based on one or more downlink transmissions received on the primary carrier to transmit a first PUCCH message on the primary carrier. In some examples, the multi-carrier transmission manager 950 may use a second codebook generated based on one or more downlink transmissions received on the secondary carrier to transmit a second PUCCH message on the secondary carrier. In some examples, the multi-carrier transmission manager 950 may use a combined codebook generated based on one or more downlink transmissions received on the primary carrier and the secondary carrier to transmit PUCCH messages on the primary carrier and the secondary carrier.

[0231] The multi-transmission manager 955 may determine that an uplink transmission is scheduled to be sent to the base station. In some examples, the multi-transmission manager 955 may determine that the traffic type associated with the uplink transmission is a traffic type supported by the UE for transmissions on the secondary carrier. In some examples, the multi-transmission manager 955 may select a secondary carrier for the transmission of the uplink transmission based on the traffic type. In some examples, the multi-transmission manager 955 may determine that a second uplink transmission is scheduled to be sent to the base station. In some examples, the multi-transmission manager 955 may determine that a second traffic type associated with the second uplink transmission is a second traffic type supported by the UE for transmissions on the primary carrier. In some examples, the multi-transmission manager 955 may select a primary carrier for the transmission of the second uplink transmission based on the second traffic type. In some cases, the traffic type associated with the uplink transmission includes a URLLC traffic type, and wherein the second traffic type associated with the second uplink transmission includes an eMBB traffic type. In some cases, the PUCCH message includes a first HARQ message associated with a dynamically scheduled downlink transmission, a second HARQ message associated with a semi-persistently activated downlink transmission, a first reference signal measurement report transmission associated with a periodic CSI-RS, a second reference signal measurement report associated with an aperiodic CSI-RS, a third reference signal measurement report associated with a semi-persistent CSI-RS, an SR, or a combination thereof.

[0232] Figure 10FIG. shows a system 1000 including a device 1005 that supports transmission of latency-sensitive uplink control on a secondary carrier, in accordance with aspects of the present disclosure. Device 1005 may be an example of device 705, device 805, or UE 115 as described herein, or may include components of device 705, device 805, or UE 115. Device 1005 may include components for two-way voice and data communication, including components for transmitting and receiving communication, including communication manager 1010, I / O controller 1015, transceiver 1020, antenna 1025, memory 1030, and processor 1040. These components may communicate electronically via one or more buses (e.g., bus 1045).

[0233] Communication manager 1010 may receive a downlink transmission from a base station on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with a PUCCH group. Communication manager 1010 may determine acknowledgement information associated with the UE decoding the downlink transmission. Communication manager 1010 may select at least one of a primary carrier or a secondary carrier to send feedback to the base station based on determining the acknowledgement information. Communication manager 1010 may send a feedback message indicating the acknowledgement information using at least one of the primary carrier or the secondary carrier based on selecting at least one of the primary carrier or the secondary carrier. Communication manager 1010 may select at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with a PUCCH group to send a PUCCH message to the base station. Communication manager 1010 may send a PUCCH message to the base station using at least one of the primary carrier or the secondary carrier based at least in part on selecting at least one of the primary carrier or the secondary carrier. I / O controller 1015 may manage input and output signals for device 1005. I / O controller 1015 may also manage peripheral devices not integrated into device 1005. In some cases, I / O controller 1015 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1015 may utilize an operating system such as or another known operating system. In other cases, I / O controller 1015 may represent a modem, keyboard, mouse, touch screen, or similar device or interact with the aforementioned devices. In some cases, I / O controller 1015 may be implemented as part of a processor. In some cases, a user may interact with device 1005 via I / O controller 1015 or via hardware components controlled by I / O controller 1015.

[0234] The transceiver 1020 can communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, the transceiver 1020 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1020 can also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and for demodulating packets received from the antenna.

[0235] In some cases, the wireless device can include a single antenna 1025. However, in some cases, the device can have more than one antenna 1025 that can simultaneously send or receive multiple wireless transmissions.

[0236] The memory 1030 can include random access memory (RAM) and read-only memory (ROM). The memory 1030 can store computer-readable, computer-executable code 1035 that includes instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, in addition, the memory 1030 can also contain a basic input / output system (BIOS) that can control basic hardware or software operations, such as interactions with peripheral components or devices.

[0237] The processor 1040 can include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1040 can be configured to operate a memory array using a memory controller. In other cases, the memory controller can be integrated into the processor 1040. The processor 1040 can be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) to cause the device 1005 to perform various functions (e.g., functions or tasks supporting the transmission of latency-sensitive uplink control on a secondary carrier).

[0238] The code 1035 can include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communication. The code 1035 can be stored on a non-transitory computer-readable medium (e.g., system memory or other types of memory). In some cases, the code 1035 may not be directly executable by the processor 1040, but can cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0239] Figure 11Block diagram 1100 shows device 1105 that supports transmitting latency-sensitive uplink control on a secondary carrier, in accordance with aspects of the present disclosure. Device 1105 may be an example of aspects of base station 105 as described herein. Device 1105 may include receiver 1110, communication manager 1115, and transmitter 1120. Device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0240] Receiver 1110 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to transmitting latency-sensitive uplink control on a secondary carrier, etc.). The information may be passed to other components of device 1105. Receiver 1110 may be an example of aspects of transceiver 1420 described with reference to Figure 14 Receiver 1110 may employ a single antenna or a set of antennas.

[0241] Communication manager 1115 may send a downlink transmission to a UE on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with a PUCCH group. Communication manager 1115 may receive a feedback message indicating acknowledgment information using at least one of the primary carrier or the secondary carrier based on a selection of at least one of the primary carrier or the secondary carrier. Communication manager 1115 may receive a PUCCH message from a UE using at least one of the primary carrier or the secondary carrier based at least in part on a selection of at least one of the primary carrier associated with a PUCCH group or the secondary carrier associated with a PUCCH group. Communication manager 1115 may be an example of aspects of communication manager 1410 described herein.

[0242] Communication manager 1115 or its subcomponents may be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of communication manager 1115 or its subcomponents may be executed by a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

[0243] The communication manager 1115 or its sub-components may be physically located at various locations, including being distributed such that some of the functions are implemented by one or more physical components at different physical locations. In some examples, in accordance with various aspects of the present disclosure, the communication manager 1115 or its sub-components may be separate and distinct components. In some examples, in accordance with various aspects of the present disclosure, the communication manager 1115 or its sub-components may be combined with one or more other hardware components, including but not limited to I / O components, transceivers, network servers, another computing device, one or more other components described in the present disclosure, or combinations thereof.

[0244] The transmitter 1120 may send signals generated by other components of the device 1105. In some examples, the transmitter 1120 may be co-located with the receiver 1110 in a transceiver module. For example, the transmitter 1120 may be an example of aspects of the transceiver 1420 described with reference to Figure 14 The transmitter 1120 may employ a single antenna or a set of antennas.

[0245] Figure 12 FIG. 1200 is a block diagram of a device 1205 supporting transmission of latency-sensitive uplink control on a secondary carrier in accordance with aspects of the present disclosure. The device 1205 may be an example of aspects of the device 1205 or the base station 105 described herein. The device 1205 may include a receiver 1210, a communication manager 1215, and a transmitter 1230. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0246] The receiver 1210 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to transmission of latency-sensitive uplink control on a secondary carrier, etc.). The information may be passed to other components of the device 1205. The receiver 1210 may be an example of aspects of the transceiver 1420 described with reference to Figure 14 The receiver 1210 may employ a single antenna or a set of antennas.

[0247] The communication manager 1215 may be an example of aspects of the communication manager 1115 described herein. The communication manager 1215 may include a DL transmission manager 1220 and a feedback message manager 1225. The communication manager 1215 may be an example of aspects of the communication manager 1410 described herein.

[0248] The DL transmission manager 1220 may send a downlink transmission to the UE on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group.

[0249] The feedback message manager 1225 may receive a feedback message indicating acknowledgment information using at least one of a primary carrier or a secondary carrier based on a selection of at least one of the primary carrier or the secondary carrier. The feedback message manager 1225 may receive a PUCCH message from a UE using at least one of a primary carrier or a secondary carrier based at least in part on a selection of at least one of the primary carrier associated with a PUCCH group or the secondary carrier associated with the PUCCH group.

[0250] The transmitter 1230 may transmit signals generated by other components of the device 1205. In some examples, the transmitter 1230 may be co-located with the receiver 1210 in a transceiver module. For example, the transmitter 1230 may be an example of aspects of the transceiver 1420 described with reference to Figure 14 aspects of the transceiver 1420 described. The transmitter 1230 may employ a single antenna or a group of antennas.

[0251] Figure 13 FIG. 1300 is a block diagram of a communication manager 1305 that supports transmitting delay-sensitive uplink control on a secondary carrier in accordance with aspects of the present disclosure. The communication manager 1305 may be an example of aspects of the communication manager 1115, the communication manager 1215, or the communication manager 1410 described herein. The communication manager 1305 may include a DL transmission manager 1310, a feedback message manager 1315, a time slot format mode manager 1320, a resource configuration manager 1325, a UE capability manager 1330, a priority rule manager 1335, a multi-carrier transmission manager 1340, and a multi-transmission manager 1345. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0252] The DL transmission manager 1310 may transmit a downlink transmission to a UE on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group. In some cases, the primary carrier, the secondary carrier, or a combination thereof includes a time division duplex carrier, a frequency division duplex carrier, or both.

[0253] The feedback message manager 1315 may receive a feedback message indicating acknowledgment information using at least one of a primary carrier or a secondary carrier based on a selection of at least one of the primary carrier or the secondary carrier. In some cases, the acknowledgment information includes at least one of an acknowledgment or a negative acknowledgment. The feedback message manager 1315 may receive a PUCCH message from a UE using at least one of a primary carrier or a secondary carrier based at least in part on a selection of at least one of the primary carrier associated with a PUCCH group or the secondary carrier associated with the PUCCH group. In some cases, the feedback message includes a HARQ acknowledgment message, a reference signal measurement report transmission, an SR, or a combination thereof.

[0254] The slot format pattern manager 1320 may send a signal configuring a first slot format pattern for a primary carrier and a second slot format pattern for a secondary carrier, wherein receiving a feedback message from the UE is based on the first slot format pattern, the second slot format pattern, or a combination thereof. In some examples, the slot format pattern manager 1320 may send an authorization for scheduling a downlink transmission for a first threshold duration before the UE sends a feedback message. In some examples, the slot format pattern manager 1320 may send a downlink transmission for a second threshold duration before the UE sends a feedback message, wherein receiving the feedback message is based on the first threshold duration and the second threshold duration. In some cases, the first slot format pattern and the second slot format pattern together include interleaved instances of uplink slots available for sending feedback messages in the time domain.

[0255] The slot format pattern manager 1320 may send a signal configuring a first slot format pattern for a primary carrier and a second slot format pattern for a secondary carrier, wherein receiving a PUCCH message from the UE is at least partially based on the first slot format pattern, the second slot format pattern, or a combination thereof. In some cases, the first slot format pattern and the second slot format pattern together include interleaved instances of uplink slots available for sending feedback messages in the time domain. In some cases, the interleaved instances include uplink slots available on the primary carrier, the secondary carrier, or both during each slot.

[0256] The resource configuration manager 1325 may send a signal that configures a first resource set for sending a feedback message on a primary carrier and a second resource set for sending a feedback message on a secondary carrier, wherein the UE selects the primary carrier or the secondary carrier based on the first resource set and the second resource set.

[0257] The UE capability manager 1330 may receive a message indicating the UE capability for using at least one of the primary carrier or the secondary carrier to send a feedback message, wherein sending a downlink transmission on at least one of the primary carrier and the secondary carrier may be based on the UE capability.

[0258] The priority rule manager 1335 may determine a priority rule associated with receiving feedback messages on the primary carrier and the secondary carrier, wherein the UE selects the primary carrier or the secondary carrier based on the priority rule and the available resources configured for sending the feedback message meet the resource usage for sending the feedback message. In some examples, the priority rule manager 1335 may send an authorization for scheduling a downlink transmission and indicating the primary carrier or the secondary carrier for sending the feedback message, wherein the authorization indicating the primary carrier or the secondary carrier overrides the priority rule for selecting the primary carrier or the secondary carrier to send the feedback message.

[0259] In some examples, the priority rule manager 1335 may send activation of semi-persistent resources for downlink transmission and indicate authorization for a primary carrier or a secondary carrier for sending a feedback message, where the indication of authorization for the primary carrier or the secondary carrier overrides the priority rule for selecting the primary carrier or the secondary carrier for sending the feedback message. In some examples, the priority rule manager 1335 may send an indication of semi-persistent resources for downlink transmission and indicate a configuration signal for a primary carrier or a secondary carrier for sending a feedback message, where the indication of the configuration signal for the primary carrier or the secondary carrier overrides the priority rule for selecting the primary carrier or the secondary carrier for sending the feedback message. In some cases, the priority rule includes a first priority associated with the primary carrier and a second priority associated with the secondary carrier, and the first priority is a higher priority than the second priority. In some cases, the priority rule includes a second priority associated with the secondary carrier and a third priority associated with an additional secondary carrier, and the second priority is a higher priority than the third priority.

[0260] The multi-carrier transmission manager 1340 may receive feedback messages on the primary carrier and the secondary carrier. In some examples, the multi-carrier transmission manager 1340 may receive a first feedback message on the primary carrier using a first codebook generated based on one or more downlink transmissions sent on the primary carrier. In some examples, the multi-carrier transmission manager 1340 may receive a second feedback message on the secondary carrier using a second codebook generated based on one or more downlink transmissions sent on the secondary carrier. In some examples, the multi-carrier transmission manager 1340 may receive feedback messages on the primary carrier and the secondary carrier using a combined codebook generated based on one or more downlink transmissions sent on the primary carrier and the secondary carrier.

[0261] The multi-transmission manager 1345 may determine that an uplink transmission is scheduled to be sent from the UE. In some examples, the multi-transmission manager 1345 may determine that the traffic type associated with the uplink transmission is a traffic type supported by the UE for transmission on the secondary carrier. In some examples, the multi-transmission manager 1345 may receive the uplink transmission on the secondary carrier based on the traffic type. In some examples, the multi-transmission manager 1345 may determine that a second uplink transmission is scheduled to be sent to the base station. In some examples, the multi-transmission manager 1345 may determine that the second traffic type associated with the second uplink transmission is a second traffic type supported by the UE for transmission on the primary carrier. In some examples, the multi-transmission manager 1345 may receive the second uplink transmission on the primary carrier based on the second traffic type. In some cases, the traffic type associated with the uplink transmission includes the URLLC traffic type, and where the traffic type associated with the uplink transmission includes the eMBB traffic type.

[0262] Figure 14 FIG. 1400 shows a system 1400 including a device 1405 that supports transmission of latency-sensitive uplink control on a secondary carrier, in accordance with aspects of the present disclosure. Device 1405 may be an example of device 1105, device 1205, or base station 105 as described herein, or may include components of device 1105, device 1205, or base station 105. Device 1405 may include components for two-way voice and data communication, including components for transmitting and receiving communication, including communication manager 1410, network communication manager 1415, transceiver 1420, antenna 1425, memory 1430, processor 1440, and inter-station communication manager 1445. These components may communicate electronically via one or more buses (e.g., bus 1450).

[0263] Communication manager 1410 may send a downlink transmission to a UE on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with a PUCCH group. Communication manager 1410 may receive a feedback message indicating acknowledgment information using at least one of the primary carrier or the secondary carrier based on a selection of at least one of the primary carrier or the secondary carrier. Communication manager 1410 may receive a PUCCH message from a UE using at least one of the primary carrier or the secondary carrier based at least in part on a selection of at least one of the primary carrier associated with a PUCCH group or the secondary carrier associated with a PUCCH group.

[0264] Network communication manager 1415 may manage communication with a core network (e.g., via one or more wired backhaul links). For example, network communication manager 1415 may manage the transmission of data communication for client devices (e.g., one or more UEs 115).

[0265] Transceiver 1420 may communicate bi-directionally via one or more antennas, wired or wireless links as described above. For example, transceiver 1420 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. Transceiver 1420 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and for demodulating packets received from the antenna.

[0266] In some cases, a wireless device may include a single antenna 1425. However, in some cases, the device may have more than one antenna 1425 that are capable of simultaneously transmitting or receiving multiple wireless transmissions.

[0267] Memory 1430 may include RAM, ROM, or a combination thereof. Memory 1430 may store computer-readable code 1435 that includes instructions that, when executed by a processor (e.g., processor 1440), cause the device to perform the various functions described herein. In some cases, in addition, memory 1430 may also contain a BIOS, etc., which may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0268] Processor 1440 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1440 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into processor 1440. Processor 1440 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1430) to cause device 1405 to perform various functions (e.g., functions or tasks that support transmitting latency-sensitive uplink control on a secondary carrier).

[0269] The inter-station communication manager 1445 may manage communication with other base stations 105 and may include a controller or scheduler for collaboratively controlling communication with UE 115 with other base stations 105. For example, the inter-station communication manager 1445 may coordinate the scheduling of transmissions to UE 115 to implement various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-station communication manager 1445 may provide an X2 interface within the LTE / LTE-A wireless communication network technology to provide communication between base stations 105.

[0270] Code 1435 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communication. Code 1435 may be stored in a non-transitory computer-readable medium (e.g., system memory or other types of memory). In some cases, code 1435 may not be directly executable by processor 1440, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0271] Figure 15 A flowchart depicting a method 1500 for supporting transmitting latency-sensitive uplink control on a secondary carrier in accordance with aspects of the present disclosure is shown. Operations of method 1500 may be implemented by UE 115 or its components as described herein. For example, the operations of method 1500 may be performed by, as referred to in Figures 7 to 10Performed by the described communication manager. In some examples, the UE may execute an instruction set to control the functional units of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0272] At 1505, the UE may optionally receive a downlink transmission from the base station on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group. The operation of 1505 may be performed according to the methods described herein. In some examples, aspects of the operation of 1505 may be performed by a DL transmission manager as described with reference to Figures 7 to 10 The described DL transmission manager.

[0273] At 1510, the UE may optionally determine acknowledgment information associated with the UE decoding the downlink transmission. The operation of 1510 may be performed according to the methods described herein. In some examples, aspects of the operation of 1510 may be performed by an acknowledgment information manager as described with reference to Figures 7 to 10 The described acknowledgment information manager.

[0274] At 1515, the UE may select at least one of a primary carrier or a secondary carrier to send feedback to the base station based on the determined acknowledgment information. The operation of 1515 may be performed according to the methods described herein. In some examples, aspects of the operation of 1515 may be performed by a carrier selection manager as described with reference to Figures 7 to 10 The described carrier selection manager.

[0275] At 1520, the UE may use at least one of the primary carrier or the secondary carrier to send a feedback message (e.g., a PUCCH message) indicating the acknowledgment information based on the selection of at least one of the primary carrier or the secondary carrier. The operation of 1520 may be performed according to the methods described herein. In some examples, aspects of the operation of 1520 may be performed by a feedback message manager as described with reference to Figures 7 to 10 The described feedback message manager.

[0276] Figure 16 A flowchart of a method 1600 depicting support for sending latency-sensitive uplink control on a secondary carrier in accordance with aspects of the present disclosure is shown. The operations of method 1600 may be implemented by a UE 115 or its components as described herein. For example, the operations of method 1600 may be performed by a communication manager as described with reference to Figures 7 to 10 The described communication manager. In some examples, the UE may execute an instruction set to control the functional units of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0277] At 1605, the UE may optionally receive a downlink transmission from the base station on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group. The operation of 1605 may be performed according to the methods described herein. In some examples, aspects of the operation of 1605 may be performed by a DL transmission manager as described with reference to Figures 7 to 10 The description of the DL transmission manager.

[0278] At 1610, the UE may optionally determine acknowledgement information associated with the UE decoding the downlink transmission. The operation of 1610 may be performed according to the methods described herein. In some examples, aspects of the operation of 1610 may be performed by an acknowledgement information manager as described with reference to Figures 7 to 10 The description of the acknowledgement information manager.

[0279] At 1615, the UE may select at least one of a primary carrier or a secondary carrier to send feedback to the base station based on the determined acknowledgement information. The operation of 1615 may be performed according to the methods described herein. In some examples, aspects of the operation of 1615 may be performed by a carrier selection manager as described with reference to Figures 7 to 10 The description of the carrier selection manager.

[0280] At 1620, the UE may receive a signal configuring a first time slot format pattern for a primary carrier and a second time slot format pattern for a secondary carrier, wherein the selection is based on the first time slot format pattern, the second time slot format pattern, or a combination thereof. The operation of 1620 may be performed according to the methods described herein. In some examples, aspects of the operation of 1620 may be performed by a time slot format pattern manager as described with reference to Figures 7 to 10 The description of the time slot format pattern manager.

[0281] At 1625, the UE may, based on selecting at least one of a primary carrier or a secondary carrier, use at least one of the primary carrier or the secondary carrier to send a feedback message (e.g., a PUCCH message) indicating the acknowledgement information. The operation of 1625 may be performed according to the methods described herein. In some examples, aspects of the operation of 1625 may be performed by a feedback message manager as described with reference to Figures 7 to 10 The description of the feedback message manager.

[0282] Figure 17 A flowchart illustrating a method 1700 for supporting delayed-sensitive uplink control transmission on a secondary carrier, in accordance with aspects of the present disclosure. The operations of method 1700 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of method 1700 may be performed by a component as described with reference to Figures 7 to 10The described communication manager performs it. In some examples, the UE may execute an instruction set to control the functional units of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0283] At 1705, the UE may send a message indicating the UE's capabilities for using at least one of the primary carrier or the secondary carrier to send a feedback message, where receiving a downlink transmission on at least one of the primary carrier or the secondary carrier is based on the UE's capabilities. The operation of 1705 may be performed according to the methods described herein. In some examples, aspects of the operation of 1705 may be performed by a UE capabilities manager as described with reference to Figures 7 to 10 the description.

[0284] At 1710, the UE may optionally receive a downlink transmission from the base station on at least one of the primary carrier associated with the PUCCH group or the secondary carrier associated with the PUCCH group. The operation of 1710 may be performed according to the methods described herein. In some examples, aspects of the operation of 1710 may be performed by a DL transmission manager as described with reference to Figures 7 to 10 the description.

[0285] At 1715, the UE may determine the acknowledgement information associated with the UE's decoding of the downlink transmission. The operation of 1715 may be performed according to the methods described herein. In some examples, aspects of the operation of 1715 may be performed by an acknowledgement information manager as described with reference to Figures 7 to 10 the description.

[0286] At 1720, the UE may select at least one of the primary carrier or the secondary carrier to send feedback to the base station based on the determined acknowledgement information. The operation of 1720 may be performed according to the methods described herein. In some examples, aspects of the operation of 1720 may be performed by a carrier selection manager as described with reference to Figures 7 to 10 the description.

[0287] At 1725, the UE may use at least one of the primary carrier or the secondary carrier to send a feedback message (e.g., a PUCCH message) indicating the acknowledgement information based on the selection of at least one of the primary carrier or the secondary carrier. The operation of 1725 may be performed according to the methods described herein. In some examples, aspects of the operation of 1725 may be performed by a feedback message manager as described with reference to Figures 7 to 10 the description.

[0288] Figure 18FIG. 1800 is a flow chart illustrating a method for supporting transmission of latency-sensitive uplink control on a secondary carrier in accordance with aspects of the present disclosure. Operations of method 1800 may be implemented by a base station 105 or components thereof as described herein. For example, operations of method 1800 may be performed by a communication manager as described with reference to Figures 11 to 14 In some examples, the base station may execute an instruction set to control functional units of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.

[0289] At 1805, the base station may optionally transmit a downlink transmission to the UE on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group. The operation of 1805 may be performed according to the methods described herein. In some examples, aspects of the operation of 1805 may be performed by a DCI transmission manager as described with reference to Figures 11 to 14 described.

[0290] At 1810, the base station may receive a feedback message (e.g., a PUCCH message) indicating acknowledgment information using at least one of a primary carrier or a secondary carrier based on a selection of at least one of the primary carrier or the secondary carrier. The operation of 1810 may be performed according to the methods described herein. In some examples, aspects of the operation of 1810 may be performed by a feedback message manager as described with reference to Figures 11 to 14 described.

[0291] Figure 19 FIG. 1900 is a flow chart illustrating a method for supporting transmission of latency-sensitive uplink control on a secondary carrier in accordance with aspects of the present disclosure. Operations of method 1900 may be implemented by a base station 105 or components thereof as described herein. For example, operations of method 1900 may be performed by a communication manager as described with reference to Figures 11 to 14 In some examples, the base station may execute an instruction set to control functional units of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.

[0292] At 1905, the base station may optionally transmit a downlink transmission to the UE on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group. The operation of 1905 may be performed according to the methods described herein. In some examples, aspects of the operation of 1905 may be performed by a DCI transmission manager as described with reference to Figures 11 to 14 described.

[0293] At 1910, the base station may receive a feedback message (e.g., a PUCCH message) indicating acknowledgment information using at least one of a primary carrier or a secondary carrier based on a selection of at least one of the primary carrier or the secondary carrier. The operations at 1910 may be performed according to the methods described herein. In some examples, aspects of the operations at 1910 may be performed by a feedback message manager as described with reference to Figures 11 to 14 the described feedback message manager.

[0294] At 1915, the base station may determine priority rules associated with receiving feedback messages on a primary carrier and a secondary carrier, wherein the UE selects the primary carrier or the secondary carrier based on the priority rules and the available resources configured for transmitting the feedback message satisfy the resource usage for transmitting the feedback message. The operations at 1915 may be performed according to the methods described herein. In some examples, aspects of the operations at 1915 may be performed by a priority rule manager as described with reference to Figures 11 to 14 the described priority rule manager.

[0295] The following provides an overview of aspects of the present disclosure:

[0296] Aspect 1: A method for wireless communication at a UE, comprising: selecting at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group to send a PUCCH message to a base station; and sending the PUCCH message to the base station using at least one of the primary carrier or the secondary carrier based at least in part on the selection of at least one of the primary carrier or the secondary carrier.

[0297] Aspect 2: The method according to aspect 1, further comprising: receiving a downlink transmission from the base station on at least one of the primary carrier or the secondary carrier; and determining acknowledgment information associated with decoding the downlink transmission by the UE, wherein the selection is at least in part based on the acknowledgment information.

[0298] Aspect 3: The method according to aspect 2, further comprising: receiving an authorization that schedules the downlink transmission and indicates the primary carrier or the secondary carrier for sending the PUCCH message, wherein the selection is at least in part based on the authorization.

[0299] Aspect 4: The method according to any one of aspects 1 to 3, further comprising: receiving a signal configuring a first time slot format pattern for the primary carrier and a second time slot format pattern for the secondary carrier, wherein the selection is at least in part based on the first format pattern, the second time slot format pattern, or a combination thereof.

[0300] Aspect 5: The method according to aspect 4, wherein the first time slot format pattern and the second time slot format pattern together include interleaved instances of uplink time slots available for transmitting the PUCCH message in the time domain.

[0301] Aspect 6: The method according to aspect 5, wherein the interleaved instances include uplink time slots available on the primary carrier, the secondary carrier, or both during each time slot.

[0302] Aspect 7: The method according to any one of aspects 1 to 6, further comprising: transmitting a message indicating UE capabilities for using at least one of the primary carrier or the secondary carrier to transmit the PUCCH message, wherein the selection of at least one of the primary carrier or the secondary carrier is at least partially based on the UE capabilities.

[0303] Aspect 8: The method according to any one of aspects 1 to 7, further comprising: receiving a signal that configures a first resource set for transmitting the PUCCH message on the primary carrier and a second resource set for transmitting the PUCCH message on the secondary carrier, wherein the selection is at least partially based on the first resource set and the second resource set.

[0304] Aspect 9: The method according to aspect 8, further comprising: determining a resource usage for transmitting the PUCCH message; and determining available resources in the first resource set and available resources in the second resource set, wherein the selection is at least partially based on the available resources satisfying the resource usage for transmitting the PUCCH message.

[0305] Aspect 10: The method according to any one of aspects 1 to 9, further comprising: determining a priority rule associated with transmitting the PUCCH message on the primary carrier and the secondary carrier, wherein the selection is at least partially based on the priority rule and the available resources configured for transmitting the PUCCH message satisfying the resource usage for transmitting the PUCCH message.

[0306] Aspect 11: The method according to aspect 10, wherein the priority rule includes a first priority associated with the primary carrier and a second priority associated with the secondary carrier, and the first priority is a higher priority than the second priority.

[0307] Aspect 12: The method according to any one of aspects 10 to 11, wherein the priority rule includes a second priority associated with the secondary carrier and a third priority associated with an additional secondary carrier, and the second priority is a higher priority than the third priority.

[0308] Aspect 13: The method according to any one of aspects 10 to 12 further includes: receiving an activation of semi-persistent resources for downlink transmission and an authorization indicating the primary carrier or the secondary carrier for transmitting the PUCCH message, and selecting at least one of the primary carrier or the secondary carrier to transmit the PUCCH message at least partially based on the authorization.

[0309] Aspect 14: The method according to any one of aspects 10 to 13 further includes: receiving a configuration signal indicating semi-persistent resources for downlink transmission and indicating the primary carrier or the secondary carrier for transmitting the PUCCH message, and selecting at least one of the primary carrier or the secondary carrier to transmit the PUCCH message at least partially based on the configuration signal.

[0310] Aspect 15: The method according to any one of aspects 1 to 14, wherein selecting at least one of the primary carrier or the secondary carrier to transmit the PUCCH message includes: selecting both the primary carrier and the secondary carrier to transmit the PUCCH message.

[0311] Aspect 16: The method according to aspect 15, wherein transmitting the PUCCH message includes: transmitting a first PUCCH message on the primary carrier using a first codebook generated at least partially based on one or more downlink transmissions received on the primary carrier; and transmitting a second PUCCH message on the secondary carrier using a second codebook generated at least partially based on one or more downlink transmissions received on the secondary carrier.

[0312] Aspect 17: The method according to any one of aspects 15 to 16, wherein transmitting the PUCCH message includes: transmitting the PUCCH message on the primary carrier and the secondary carrier using a combined codebook generated at least partially based on one or more downlink transmissions received on the primary carrier and the secondary carrier.

[0313] Aspect 18: The method according to any one of aspects 1 to 17 further includes: determining that an uplink transmission is scheduled to be sent to the base station; determining that the service type associated with the uplink transmission is a service type supported by the UE for transmission on the secondary carrier; and selecting the secondary carrier for transmission of the uplink transmission at least partially based on the service type.

[0314] Aspect 19: The method according to aspect 18 further includes: determining that a second uplink transmission is scheduled to be sent to the base station; determining that a second service type associated with the second uplink transmission is the second service type supported by the UE for transmissions on the primary carrier; and selecting, at least in part based on the second service type, the primary carrier for transmission of the second uplink transmission.

[0315] Aspect 20: The method according to aspect 19, wherein the service type associated with the uplink transmission includes a URLLC service type, and the second service type associated with the second uplink transmission includes an eMBB service type.

[0316] Aspect 21: The method according to any one of aspects 1 to 20, wherein the PUCCH message includes a first Hybrid Automatic Repeat reQuest (HARQ) acknowledgment message associated with a dynamically scheduled downlink transmission, a second HARQ message associated with a semi-persistently activated downlink transmission, a first reference signal measurement report transmission associated with a periodic CSI-RS, a second reference signal measurement report associated with an aperiodic CSI-RS, a third reference signal measurement report associated with a semi-persistent CSI-RS, a Scheduling Request (SR), or a combination thereof.

[0317] Aspect 22: The method according to any one of aspects 1 to 21, wherein the primary carrier, the secondary carrier, or a combination thereof includes a Time Division Duplex (TDD) carrier, a Frequency Division Duplex (FDD) carrier, or both.

[0318] Aspect 23: A method for wireless communication at a base station, including: receiving, using at least one of the primary carrier or the secondary carrier associated with a PUCCH group, a PUCCH message from a UE, at least in part based on a selection of at least one of the primary carrier associated with the PUCCH group or the secondary carrier associated with the PUCCH group.

[0319] Aspect 24: The method according to aspect 23 further includes: sending a downlink transmission to the UE on at least one of the primary carrier or the secondary carrier, wherein the PUCCH message includes a feedback message indicating acknowledgment information associated with the UE's decoding of the downlink transmission.

[0320] Aspect 25: The method according to aspect 24 further includes: sending an authorization that schedules the downlink transmission and indicates the primary carrier or the secondary carrier for sending the feedback message.

[0321] Aspect 26: The method according to any one of aspects 23 to 25 further includes: sending a signal configuring a first time slot format pattern for the primary carrier and a second time slot format pattern for the secondary carrier, wherein receiving the PUCCH message from the UE is at least partially based on the first time slot format pattern, the second time slot format pattern, or a combination thereof.

[0322] Aspect 27: The method according to aspect 26, wherein the first time slot format pattern and the second time slot format pattern together include interleaved instances of uplink time slots available for transmitting the feedback message in the time domain.

[0323] Aspect 28: The method according to aspect 27, wherein the interleaved instances include uplink time slots available on the primary carrier, the secondary carrier, or both during each time slot.

[0324] Aspect 29: A method for wireless communication at a UE includes: receiving a downlink transmission from a base station on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group; determining acknowledgment information associated with the UE decoding the downlink transmission; selecting at least one of the primary carrier or the secondary carrier to send feedback to the base station at least partially based on determining the acknowledgment information; and sending a feedback message indicating the acknowledgment information using at least one of the primary carrier or the secondary carrier at least partially based on selecting at least one of the primary carrier or the secondary carrier.

[0325] Aspect 30: The method according to aspect 29 further includes: receiving a signal configuring a first time slot format pattern for the primary carrier and a second time slot format pattern for the secondary carrier, wherein the selection is at least partially based on the first time slot format pattern, the second time slot format pattern, or a combination thereof.

[0326] Aspect 31: The method according to aspect 30, wherein the first time slot format pattern and the second time slot format pattern together include interleaved instances of uplink time slots available for transmitting the feedback message in the time domain.

[0327] Aspect 32: The method according to any one of aspects 30 to 31 further includes: determining an authorization for scheduling the downlink transmission received for a first threshold duration before sending the feedback message; and determining that the downlink transmission is received for a second threshold duration before sending the feedback message, wherein sending the feedback message is at least partially based on the first threshold duration and the second threshold duration.

[0328] Aspect 33: The method according to any one of aspects 29 to 32 further includes: sending a message indicating UE capabilities for using at least one of the primary carrier or the secondary carrier to send the feedback message, wherein receiving the downlink transmission on at least one of the primary carrier or the secondary carrier is at least partially based on the UE capabilities.

[0329] Aspect 34: The method according to any one of aspects 29 to 33 further includes: receiving a signal that configures a first resource set for sending the feedback message on the primary carrier and a second resource set for sending the feedback message on the secondary carrier, wherein the selection is at least partially based on the first resource set and the second resource set.

[0330] Aspect 35: The method according to aspect 34 further includes: determining a resource usage for sending the feedback message; and determining available resources in the first resource set and available resources in the second resource set, wherein the selection is at least partially based on the available resources meeting the resource usage for sending the feedback message.

[0331] Aspect 36: The method according to any one of aspects 29 to 35 further includes: determining a priority rule associated with sending the feedback message on the primary carrier and the secondary carrier, wherein the selection is at least partially based on the priority rule and the available resources configured for sending the feedback message meeting the resource usage for sending the feedback message.

[0332] Aspect 37: The method according to aspect 36, wherein the priority rule includes a first priority associated with the primary carrier and a second priority associated with the secondary carrier, and the first priority is a higher priority than the second priority.

[0333] Aspect 38: The method according to any one of aspects 36 to 37, wherein the priority rule includes a second priority associated with the secondary carrier and a third priority associated with an additional secondary carrier, and the second priority is a higher priority than the third priority.

[0334] Aspect 39: The method according to any one of aspects 36 to 38 further includes: receiving an authorization that schedules the downlink transmission and indicates the primary carrier or the secondary carrier for sending the feedback message; and selecting at least one of the primary carrier or the secondary carrier to send the feedback message at least partially based on the authorization.

[0335] Aspect 40: The method according to any one of Aspects 36 to 39 further includes: receiving authorization to activate semi-persistent resources for the downlink transmission and indicating the primary carrier or the secondary carrier for transmitting the feedback message; and selecting at least one of the primary carrier or the secondary carrier to transmit the feedback message at least partially based on the authorization.

[0336] Aspect 41: The method according to any one of Aspects 36 to 40 further includes: receiving a configuration signal indicating semi-persistent resources for the downlink transmission and indicating the primary carrier or the secondary carrier for transmitting the feedback message; and selecting at least one of the primary carrier or the secondary carrier to transmit the feedback message at least partially based on the configuration signal.

[0337] Aspect 42: The method according to any one of Aspects 29 to 41, wherein selecting at least one of the primary carrier or the secondary carrier to transmit the feedback message includes: selecting the primary carrier and the secondary carrier to transmit the feedback message.

[0338] Aspect 43: The method according to Aspect 42, wherein transmitting the feedback message includes: transmitting a first feedback message on the primary carrier using a first codebook generated at least partially based on one or more downlink transmissions received on the primary carrier; and transmitting a second feedback message on the secondary carrier using a second codebook generated at least partially based on one or more downlink transmissions received on the secondary carrier.

[0339] Aspect 44: The method according to any one of Aspects 42 to 43, wherein transmitting the feedback message includes: transmitting the feedback message on the primary carrier and the secondary carrier using a combined codebook generated at least partially based on one or more downlink transmissions received on the primary carrier and the secondary carrier.

[0340] Aspect 45: The method according to any one of Aspects 29 to 44 further includes: determining that an uplink transmission is scheduled to be sent to the base station; determining that the traffic type associated with the uplink transmission is a traffic type supported by the UE for transmissions on the secondary carrier; and selecting the secondary carrier for transmission of the uplink transmission at least partially based on the traffic type.

[0341] Aspect 46: The method according to aspect 45 further includes: determining that a second uplink transmission is scheduled to be sent to the base station; determining that a second service type associated with the second uplink transmission is a second service type supported by the UE for transmissions on the primary carrier; and selecting the primary carrier for transmission of the second uplink transmission at least in part based on the second service type.

[0342] Aspect 47: The method according to aspect 46, wherein the service type associated with the uplink transmission includes a URLLC service type, and the second service type associated with the second uplink transmission includes an eMBB service type.

[0343] Aspect 48: The method according to any one of aspects 29 to 47, wherein the acknowledgement information includes at least one of an acknowledgement or a negative acknowledgement.

[0344] Aspect 49: The method according to any one of aspects 29 to 48, wherein the feedback message includes a HARQ acknowledgement message, a reference signal measurement report transmission, or both.

[0345] Aspect 50: The method according to any one of aspects 29 to 49, wherein the primary carrier, the secondary carrier, or a combination thereof each includes a time division duplex carrier, a frequency division duplex carrier, or both.

[0346] Aspect 51: A method for wireless communication at a base station, including: sending a downlink transmission to a UE on at least one of a primary carrier associated with a PUCCH group or a secondary carrier associated with the PUCCH group; and receiving a feedback message indicating acknowledgement information using at least one of the primary carrier or the secondary carrier at least in part based on a selection of at least one of the primary carrier or the secondary carrier.

[0347] Aspect 52: The method according to aspect 51 further includes: sending a signal configuring a first time slot format pattern for the primary carrier and a second time slot format pattern for the secondary carrier, wherein receiving the feedback message from the UE is at least in part based on the first time slot format pattern, the second time slot format pattern, or a combination thereof.

[0348] Aspect 53: The method according to aspect 52, wherein the first time slot format pattern and the second time slot format pattern together include interleaved instances of uplink time slots available for sending the feedback message in the time domain.

[0349] Aspect 54: The method according to any one of Aspects 52 to 53 further includes: sending an authorization for scheduling the downlink transmission for a first threshold duration before the UE sends the feedback message; and sending the downlink transmission for a second threshold duration before the UE sends the feedback message, wherein receiving the feedback message is at least partially based on the first threshold duration and the second threshold duration.

[0350] Aspect 55: The method according to any one of Aspects 51 to 54 further includes: sending a signal that configures a first resource set for sending the feedback message on the primary carrier and a second resource set for sending the feedback message on the secondary carrier, wherein the UE selects the primary carrier or the secondary carrier at least partially based on the first resource set and the second resource set.

[0351] Aspect 56: The method according to any one of Aspects 51 to 55 further includes: receiving a message indicating the UE capability for using at least one of the primary carrier or the secondary carrier to send the feedback message, wherein sending the downlink transmission on at least one of the primary carrier and the secondary carrier is at least partially based on the UE capability.

[0352] Aspect 57: The method according to any one of Aspects 51 to 56 further includes: determining a priority rule associated with receiving the feedback message on the primary carrier and the secondary carrier, wherein the UE selects the primary carrier or the secondary carrier at least partially based on the priority rule and the available resources configured for sending the feedback message meet the resource usage for sending the feedback message.

[0353] Aspect 58: The method according to Aspect 57, wherein the priority rule includes a first priority associated with the primary carrier and a second priority associated with the secondary carrier, and the first priority is a higher priority than the second priority.

[0354] Aspect 59: The method according to any one of Aspects 57 to 58, wherein the priority rule includes a second priority associated with the secondary carrier and a third priority associated with an additional secondary carrier, and the second priority is a higher priority than the third priority.

[0355] Aspect 60: The method according to any one of Aspects 57 to 59 further includes: sending an authorization for scheduling the downlink transmission and indicating the primary carrier or the secondary carrier for sending the feedback message, wherein the authorization indicating the primary carrier or the secondary carrier covers the priority rule for selecting the primary carrier or the secondary carrier to send the feedback message.

[0356] Aspect 61: The method according to any one of Aspects 57 to 60 further includes: sending an activation of semi-persistent resources for the downlink transmission and indicating an authorization for the primary carrier or the secondary carrier for sending the feedback message, wherein the indication of the authorization for the primary carrier or the secondary carrier covers the priority rule for selecting the primary carrier or the secondary carrier for sending the feedback message.

[0357] Aspect 62: The method according to any one of Aspects 57 to 61 further includes: sending a configuration signal indicating semi-persistent resources for the downlink transmission and indicating the primary carrier or the secondary carrier for sending the feedback message, wherein the indication of the configuration signal for the primary carrier or the secondary carrier covers the priority rule for selecting the primary carrier or the secondary carrier for sending the feedback message.

[0358] Aspect 63: The method according to any one of Aspects 51 to 62, wherein receiving the feedback message includes: receiving the feedback message on the primary carrier and the secondary carrier.

[0359] Aspect 64: The method according to Aspect 63, wherein receiving the feedback message includes: receiving a first feedback message on the primary carrier using a first codebook generated at least partially based on one or more downlink transmissions sent on the primary carrier; and receiving a second feedback message on the secondary carrier using a second codebook generated at least partially based on one or more downlink transmissions sent on the secondary carrier.

[0360] Aspect 65: The method according to any one of Aspects 63 to 64, wherein receiving the feedback message includes: receiving the feedback message on the primary carrier and the secondary carrier using a combined codebook generated at least partially based on one or more downlink transmissions sent on the primary carrier and the secondary carrier.

[0361] Aspect 66: The method according to any one of Aspects 51 to 65 further includes: determining that an uplink transmission is scheduled to be sent from the UE; determining that the service type associated with the uplink transmission is a service type supported by the UE for transmission on the secondary carrier; and receiving the uplink transmission on the secondary carrier at least partially based on the service type.

[0362] Aspect 67: The method according to aspect 66 further includes: determining that a second uplink transmission is scheduled to be sent to the base station; determining that a second service type associated with the second uplink transmission is a second service type supported by the UE for transmissions on the primary carrier; and receiving the second uplink transmission on the primary carrier at least partially based on the second service type.

[0363] Aspect 68: The method according to aspect 67, wherein the service type associated with the uplink transmission includes a URLLC service type and the service type associated with the uplink transmission includes an eMBB service type.

[0364] Aspect 69: The method according to any one of aspects 51 to 68, wherein the acknowledgment information includes at least one of an acknowledgment or a negative acknowledgment.

[0365] Aspect 70: The method according to any one of aspects 51 to 69, wherein the feedback message includes a HARQ acknowledgment message, a reference signal measurement report transmission, or a combination thereof.

[0366] Aspect 71: The method according to any one of aspects 51 to 70, wherein the primary carrier, the secondary carrier, or a combination thereof each includes a time division duplex carrier, a frequency division duplex carrier, or both.

[0367] Aspect 72: An apparatus for wireless communication at a UE, including: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of aspects 1 to 22.

[0368] Aspect 73: An apparatus for wireless communication at a UE, including at least one unit for performing the method according to any one of aspects 1 to 22.

[0369] Aspect 74: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by a processor to perform the method according to any one of aspects 1 to 22.

[0370] Aspect 75: An apparatus for wireless communication at a base station, including: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of aspects 23 to 28.

[0371] Aspect 76: An apparatus for wireless communication at a base station, including at least one unit for performing the method according to any one of aspects 23 to 28.

[0372] Aspect 77: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code including instructions executable by a processor to perform the method according to any one of Aspects 23 to 28.

[0373] Aspect 78: An apparatus for wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of Aspects 29 to 50.

[0374] Aspect 79: An apparatus for wireless communication at a UE, comprising at least one unit for performing the method according to any one of Aspects 29 to 50.

[0375] Aspect 80: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by a processor to perform the method according to any one of Aspects 29 to 50.

[0376] Aspect 81: An apparatus for wireless communication at a base station, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of Aspects 51 to 71.

[0377] Aspect 82: An apparatus for wireless communication at a base station, comprising at least one unit for performing the method according to any one of Aspects 51 to 71.

[0378] Aspect 83: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code including instructions executable by a processor to perform the method according to any one of Aspects 51 to 71.

[0379] It should be noted that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible. In addition, aspects from two or more methods may be combined.

[0380] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for purposes of example, and the LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond the scope of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to a variety of other wireless communication systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0381] The information and signals described herein can be represented using any of a variety of different technologies and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0382] Various illustrative blocks and components described in connection with the disclosure herein can be implemented or performed using a general purpose processor, DSP, ASIC, CPU, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0383] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these items. The features implementing the functions can also be physically located at various positions, including being distributed such that portions of the functions are implemented at different physical locations.

[0384] A computer-readable medium includes both a non-transitory computer storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another. The non-transitory storage medium can be any available medium that can be accessed by a general-purpose or a special-purpose computer. By way of example and not limitation, the non-transitory computer-readable medium can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store the desired program code units in the form of instructions or data structures and that can be accessed by a general-purpose or a special-purpose computer, or a general-purpose or a special-purpose processor. Additionally, any connection is properly termed a computer-readable medium. For example, if software is transmitted using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable medium.

[0385] As used herein (including in the claims), the "or" as used in a list of items (e.g., a list of items that ends with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that a list of, for example, at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Additionally, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0386] In the figures, similar components or features may have the same reference numeral. Additionally, various components of the same type can be distinguished by following the reference numeral with a dash and a second numeral, which is used to distinguish among similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, regardless of the second reference numeral or any other subsequent reference numerals.

[0387] This description of example configurations has been presented in conjunction with the accompanying drawings, and does not represent all examples that can be implemented or are within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration", rather than "preferred" or "advantageous over other examples". For the purpose of providing an understanding of the described technology, the detailed description includes specific details. However, the technology may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0388] This description is provided to enable a person skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but is accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: selecting at least one of a primary carrier associated with a physical uplink control channel set or a secondary carrier associated with the physical uplink control channel set for transmitting a physical uplink control channel message; receiving a signal configuring a first time slot format pattern for the primary carrier and a second time slot format pattern for the secondary carrier, wherein the first time slot format pattern and the second time slot format pattern together include interleaved instances of uplink time slots available for transmitting the physical uplink control channel message in the time domain, wherein the interleaved instances include uplink time slots available on the primary carrier, the secondary carrier, or both during each time slot; and transmitting the physical uplink control channel message to a base station using at least one of the primary carrier or the secondary carrier, at least partially based on selecting at least one of the primary carrier or the secondary carrier.

2. The method according to claim 1, further comprising: receiving a downlink transmission from the base station on at least one of the primary carrier or the secondary carrier; and determining acknowledgement information associated with the UE decoding the downlink transmission, wherein the selection is at least partially based on the acknowledgement information.

3. The method according to claim 2, further comprising: receiving an authorization scheduling the downlink transmission and indicating the primary carrier or the secondary carrier for transmitting the physical uplink control channel message, wherein the selection is at least partially based on the authorization.

4. The method according to claim 1, wherein, The selection is at least partially based on the first time slot format pattern, the second time slot format pattern, or a combination thereof.

5. The method according to claim 1, further comprising: receiving signaling from the base station, the signaling being at least partially based on the UE having the capability to enable transmission of the physical uplink control channel message on the secondary carrier.

6. The method according to claim 1, further comprising: receiving a signal configuring a first resource set for transmitting the physical uplink control channel message on the primary carrier and a second resource set for transmitting the physical uplink control channel message on the secondary carrier, wherein the selection is at least partially based on the first resource set and the second resource set.

7. The method according to claim 6, further comprising: determining resource usage for transmitting the physical uplink control channel message; and determining available resources in the first resource set and available resources in the second resource set, wherein the selection is at least partially based on the available resources satisfying the resource usage for transmitting the physical uplink control channel message.

8. The method according to claim 1, further comprising: Determine a priority rule associated with transmitting the physical uplink control channel message on the primary carrier and the secondary carrier, wherein the selection is at least partially based on the priority rule and the available resources configured for transmitting the physical uplink control channel message meet the resource usage for transmitting the physical uplink control channel message.

9. The method according to claim 8, wherein The priority rule includes a first priority associated with the primary carrier and a second priority associated with the secondary carrier, and the first priority is a higher priority than the second priority.

10. The method according to claim 8, wherein The priority rule includes a second priority associated with the secondary carrier and a third priority associated with an additional secondary carrier, and the second priority is a higher priority than the third priority.

11. The method according to claim 8, further comprising: Receiving activation of semi-persistent resources for downlink transmission and authorization indicating the primary carrier or the secondary carrier for transmitting the physical uplink control channel message, and selecting at least one of the primary carrier or the secondary carrier to transmit the physical uplink control channel message at least partially based on the authorization.

12. The method according to claim 8, further comprising: Receiving a configuration signal indicating semi-persistent resources for downlink transmission and indicating the primary carrier or the secondary carrier for transmitting the physical uplink control channel message; Selecting at least one of the primary carrier or the secondary carrier to transmit the physical uplink control channel message at least partially based on the configuration signal.

13. The method according to claim 1, wherein Selecting at least one of the primary carrier or the secondary carrier to transmit the physical uplink control channel message includes: Selecting the primary carrier and the secondary carrier to transmit the physical uplink control channel message.

14. The method according to claim 13, wherein, Transmitting the physical uplink control channel message includes: Transmitting a first physical uplink control channel message on the primary carrier using a first codebook generated at least partially based on one or more downlink transmissions received on the primary carrier; and Transmitting a second physical uplink control channel message on the secondary carrier using a second codebook generated at least partially based on one or more downlink transmissions received on the secondary carrier.

15. The method according to claim 13, wherein, Transmitting the physical uplink control channel message includes: Transmitting the physical uplink control channel message on the primary carrier and the secondary carrier using a combined codebook generated at least partially based on one or more downlink transmissions received on the primary carrier and the secondary carrier.

16. The method according to claim 1, further comprising: Determining that an uplink transmission is scheduled to be sent to the base station; Determining that the service type associated with the uplink transmission is a service type supported by the UE for transmission on the secondary carrier; And Selecting the secondary carrier for transmission of the uplink transmission at least partially based on the service type.

17. The method according to claim 16, further comprising: Determining that a second uplink transmission is scheduled to be sent to the base station; Determine that the second service type associated with the second uplink transmission is the second service type supported by the UE for transmissions on the primary carrier; and Select the primary carrier for transmission of the second uplink transmission, at least in part based on the second service type.

18. The method according to claim 17, wherein The service type associated with the uplink transmission includes: a ultra-reliable / low-latency communication (URLLC) service type, and wherein, the second service type associated with the second uplink transmission includes: an enhanced mobile broadband (eMBB) service type.

19. The method according to claim 1, wherein The physical uplink control channel message includes: a first hybrid automatic repeat / request acknowledgment (HARQ) message associated with a dynamically scheduled downlink transmission, a second HARQ message associated with a semi-persistently activated downlink transmission, a first reference signal measurement report transmission associated with a periodic channel state information reference signal (CSI-RS), a second reference signal measurement report associated with an aperiodic CSI-RS, a third reference signal measurement report associated with a semi-persistent CSI-RS, a scheduling request, or a combination thereof.

20. The method according to claim 1, wherein, The primary carrier, the secondary carrier, or a combination thereof each includes a time division duplex carrier, a frequency division duplex carrier, or both.

21. A method for wireless communication at a base station, comprising: Transmit a signal configuring a first time slot format pattern for a primary carrier and a second time slot format pattern for a secondary carrier, wherein, the first time slot format pattern and the second time slot format pattern together include interleaved instances of uplink time slots available for a user equipment (UE) to transmit physical uplink control channel messages in the time domain, wherein, the interleaved instances include uplink time slots available on the primary carrier, the secondary carrier, or both during each time slot; Receive the physical uplink control channel message from the UE using at least one of the primary carrier or the secondary carrier, at least in part based on the UE's selection of at least one of the primary carrier associated with a physical uplink control channel set or the secondary carrier associated with the physical uplink control channel set.

22. The method according to claim 21, further comprising: Transmit a downlink transmission to the UE on at least one of the primary carrier or the secondary carrier, wherein, the physical uplink control channel message includes a feedback message indicating acknowledgment information associated with the UE's decoding of the downlink transmission.

23. The method according to claim 22, further comprising: Transmit an authorization scheduling the downlink transmission and indicating the primary carrier or the secondary carrier for transmitting the feedback message.

24. The method according to claim 21, wherein, Receiving the physical uplink control channel message from the UE is at least in part based on the first time slot format pattern, the second time slot format pattern, or a combination thereof.

25. An apparatus for wireless communication at a user equipment (UE), comprising: A processor; A memory coupled to the processor; And Instructions that are stored in the memory and executable by the processor to cause the device to perform the following operations: Select at least one of a primary carrier associated with a physical uplink control channel group or a secondary carrier associated with the physical uplink control channel group for transmitting a physical uplink control channel message; Receive a signal configuring a first time slot format pattern for the primary carrier and a second time slot format pattern for the secondary carrier, wherein the first time slot format pattern and the second time slot format pattern together include interleaved instances of uplink time slots available for transmitting the physical uplink control channel message in the time domain, wherein the interleaved instances include uplink time slots available on the primary carrier, the secondary carrier, or both during each time slot; and Transmit the physical uplink control channel message to a base station using at least one of the primary carrier or the secondary carrier, at least in part based on selecting at least one of the primary carrier or the secondary carrier.

26. A device for wireless communication at a base station, comprising: A processor; A memory coupled to the processor; And Instructions that are stored in the memory and executable by the processor to cause the device to perform the following operations: Transmit a signal configuring a first time slot format pattern for a primary carrier and a second time slot format pattern for a secondary carrier, wherein the first time slot format pattern and the second time slot format pattern together include interleaved instances of uplink time slots available for a user equipment (UE) to transmit a physical uplink control channel message in the time domain, wherein the interleaved instances include uplink time slots available on the primary carrier, the secondary carrier, or both during each time slot; Receive the physical uplink control channel message from the UE using at least one of the primary carrier or the secondary carrier, at least in part based on the UE's selection of at least one of the primary carrier associated with a physical uplink control channel group or the secondary carrier associated with the physical uplink control channel group.

Images