Patent Description:
Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for allocating physical uplink control channel (PUCCH) resources for ultra-reliable low latency communication (URLLC).

<NPL>" relates to open issues on PUCCH resource allocation. <NPL>" analyses potential gain for compact DCI. Panasonic: R1-<NUM> "Discussion on resource allocation for uplink control channel" discusses remaining details on resource allocation for uplink control channel in NR.

In accordance with the present invention, there is provided a method of wireless communication performed by a UE as set out in claim <NUM>, a method of wireless communication performed by a base station as set out in claim <NUM> and a UE for wireless communication as set out in claim <NUM>. Other aspects of the invention can be found in the dependent claims.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the accompanying drawings and specification.

Controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform one or more techniques associated with allocating physical uplink control channel (PUCCH) resources for ultra-reliable low latency communication (URLLC), as described in more detail elsewhere herein. For example, controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform or direct operations of, for example, process <NUM> of <FIG>, process <NUM> of <FIG>, process <NUM> of <FIG>, process <NUM> of <FIG>, and/or other processes as described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively.

In some aspects, UE <NUM> may include means for determining whether a PUCCH transmission is associated with a first type of service or a second type of service, wherein the second type of service is associated with a higher reliability or a lower latency than the first type of service; means for transmitting the PUCCH transmission using a first set of resources when the PUCCH transmission is associated with the first type of service or using a second set of resources when the PUCCH transmission is associated with the second type of service; and/or the like. Additionally, or alternatively, UE <NUM> may include means for receiving a PUCCH configuration comprising a first set of parameters for transmissions associated with a first service type and a second set of parameters for transmissions associated with a second service type; means for generating UCI; means for transmitting a message that includes the UCI according to the PUCCH configuration and a service type of the message; and/or the like. In some aspects, such means may include one or more components of UE <NUM> described in connection with <FIG>.

In some aspects, base station <NUM> may include means for determining a first configuration of PUCCH resources to be used for PUCCH transmissions associated with a first type of service; means for determining a second configuration of PUCCH resources to be used for PUCCH transmissions associated with a second type of service, wherein the second type of service is associated with a higher reliability or a lower latency than the first type of service; means for transmitting the first configuration and the second configuration to a UE; and/or the like. In some aspects, such means may include one or more components of base station <NUM> described in connection with <FIG>.

<FIG> shows an example frame structure <NUM> for FDD in a telecommunications system (e.g., NR). The transmission time line for each of the downlink and uplink may be partitioned into units of radio frames (sometimes referred to as frames). In some aspects, a scheduling unit for the FDD may frame-based, subframe-based, slot-based, symbol-based, and/or the like.

An interlace structure may be used for each of the downlink and uplink for FDD in certain telecommunications systems (e.g., NR). For example, Q interlaces with indices of <NUM> through Q - <NUM> may be defined, where Q may be equal to <NUM>, <NUM>, <NUM>, <NUM>, or some other value. Each interlace may include slots that are spaced apart by Q frames. In particular, interlace q may include slots q, q + Q, q + 2Q, etc., where q ∈ {<NUM>,. , Q-<NUM>}.

New Radio (NR) may refer to radios configured to operate according to a new air interface (e.g., other than Orthogonal Frequency Divisional Multiple Access (OFDMA)-based air interfaces) or fixed transport layer (e.g., other than Internet Protocol (IP)).

<FIG> is a diagram <NUM> showing an example of a DL-centric slot or wireless communication structure. The DL-centric slot may include a control portion <NUM>. The control portion <NUM> may exist in the initial or beginning portion of the DL-centric slot. The control portion <NUM> may include various scheduling information and/or control information corresponding to various portions of the DL-centric slot. In some aspects, the control portion <NUM> may include legacy PDCCH information, shortened PDCCH (sPDCCH) information), a control format indicator (CFI) value (e.g., carried on a physical control format indicator channel (PCFICH)), one or more grants (e.g., downlink grants, uplink grants, and/or the like), and/or the like.

The DL-centric slot may also include a DL data portion <NUM>. The DL data portion <NUM> may sometimes be referred to as the payload of the DL-centric slot.

The DL-centric slot may also include an UL short burst portion <NUM>. The UL short burst portion <NUM> may sometimes be referred to as an UL burst, an UL burst portion, a common UL burst, a short burst, an UL short burst, a common UL short burst, a common UL short burst portion, and/or various other suitable terms. In some aspects, the UL short burst portion <NUM> may include one or more reference signals. Additionally, or alternatively, the UL short burst portion <NUM> may include feedback information corresponding to various other portions of the DL-centric slot. For example, the UL short burst portion <NUM> may include feedback information corresponding to the control portion <NUM> and/or the data portion <NUM>. Non-limiting examples of information that may be included in the UL short burst portion <NUM> include an ACK signal (e.g., a PUCCH ACK, a PUSCH ACK, an immediate ACK), a NACK signal (e.g., a PUCCH NACK, a PUSCH NACK, an immediate NACK), a scheduling request (SR), a buffer status report (BSR), a HARQ indicator, a channel state indication (CSI), a channel quality indicator (CQI), a sounding reference signal (SRS), a demodulation reference signal (DMRS), PUSCH data, and/or various other suitable types of information. The UL short burst portion <NUM> may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests, and various other suitable types of information.

<FIG> is a diagram <NUM> showing an example of an UL-centric slot or wireless communication structure. The UL-centric slot may include a control portion <NUM>. The control portion <NUM> may exist in the initial or beginning portion of the UL-centric slot. The control portion <NUM> in <FIG> may be similar to the control portion <NUM> described above with reference to <FIG>. The UL-centric slot may also include an UL long burst portion <NUM>. The UL long burst portion <NUM> may sometimes be referred to as the payload of the UL-centric slot. The UL portion may refer to the communication resources utilized to communicate UL data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or BS). In some configurations, the control portion <NUM> may be a physical DL control channel (PDCCH).

The UL-centric slot may also include an UL short burst portion <NUM>. The UL short burst portion <NUM> in <FIG> may be similar to the UL short burst portion <NUM> described above with reference to <FIG>, and may include any of the information described above in connection with <FIG>. The foregoing is merely one example of an UL-centric wireless communication structure, and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.

In some aspects, the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum).

In one example, a wireless communication structure, such as a frame, may include both UL-centric slots and DL-centric slots. In this example, the ratio of UL-centric slots to DL-centric slots in a frame may be dynamically adjusted based at least in part on the amount of UL data and the amount of DL data that are transmitted. For example, if there is more UL data, then the ratio of UL-centric slots to DL-centric slots may be increased. Conversely, if there is more DL data, then the ratio of UL-centric slots to DL-centric slots may be decreased.

In some instances, a BS and UE may communicate with one another via multiple types of services. For example, a first communication between the BS and the UE may use an enhanced mobile broadband (eMBB) service and a second communication between the BS and the UE may use an ultra-reliable low latency communication (URLLC) service. In such cases, the different types of services may have different characteristics and/or requirements, such as different latency and/or reliability requirements (e.g., a URLLC service has a higher reliability and lower latency requirement than eMBB). However, in some cases, the same sets of PUCCH resources may be allocated for communications between the BS and the UE regardless of the type of service (e.g., eMBB or URLLC) that is being used for the communication. Accordingly, a long PUCCH resource (e.g., <NUM> symbols) may not be useful for URLLC due to the rather large latency associated with the long PUCCH resource. On the other hand, URLLC PUCCH resources may need to be configured more frequently (e.g., every two symbols) to meet the low latency requirement, which is not necessary for eMBB services.

Furthermore, in some instances, downlink control information (DCI) may be different depending on the type of service being used. For example, the DCI may include different signaling methods for PUCCH resource allocation for eMBB than the signaling methods included in the DCI for URLLC. As such, when PUCCH resources are allocated regardless of the type of service that is to be used for a PUCCH transmission, the UE may improperly interpret which of the resources are to be used for a particular PUCCH transmission.

Furthermore, in some instances, when two PUCCH channels (e.g. one for eMBB and one for URLLC) are overlapping in time, the UE may need to multiplex uplink control information (UCI) bits for both channels (e.g., for both eMBB and URLLC) and transmit the UCI in a single channel. However, this can have a negative effect on reliability, because the multiplexed UCI does not indicate whether URLLC packets or eMBB packets have been properly received. The multiplexed UCI simply indicates a total number of packets received, regardless of the type of service that is associated with the packets. Furthermore, in some instances, the UE may use different timing for different types of services. For example, there may be a different response timing for eMBB acknowledgement or negative acknowledgement (ACK/NACK) than response timing for URLLC ACK/NACK. In some cases, ACK/NACK may be referred to as hybrid automatic repeat request acknowledgement (HARQ-ACK). Similarly, ACK/NACK feedback may be referred to as HARQ-ACK feedback, ACK/NACK information may be referred to as HARQ-ACK information, and/or the like.

Some aspects described herein provide resource allocation for PUCCH resources in connection with the type of service that is to be used for a PUCCH transmission. For example, the UE may send a PUCCH transmission using first sets of resources when the PUCCH transmission is associated with a first type of service (e.g., eMBB) and second sets of resources when the PUCCH transmission is associated with the second type of service (e.g., URLLC). Furthermore, some aspects described herein may identify a resource for a PUCCH transmission from signaling in the DCI based at least in part on the type of service that is associated with the PUCCH transmission to ensure that the proper resource is monitored and/or used. Some aspects described herein may use separate PUCCH resources to transmit a PUCCH transmission with UCI based at least in part on the type of service that is associated with the PUCCH transmission. For example, a downlink assignment index (DAI) operation performed for a PUCCH transmission associated with an eMBB service may be different than a DAI operation performed for a PUCCH transmission associated with a URLLC service.

Accordingly, some examples provided herein may allow for different PUCCH resources to be dynamically allocated or used for PUCCH transmission based at least in part on the type of service. For example, depending on the requirements of the service associated with the PUCCH transmission, the PUCCH transmission may achieve a higher reliability and/or lower latency for one type of service over another by using relatively fewer sets of PUCCH resources and/or relatively fewer resources in each set of resources for the PUCCH transmission. Additionally, or alternatively, another type of service, that may not require such high reliability or low latency, can conserve signaling bandwidth and be configured using a larger number of sets of PUCCH resources and/or a greater number or resources within the sets of resources. Accordingly, some examples herein may conserve network resources while increasing reliability and/or decreasing latency as needed depending on a service associated with a PUCCH transmission.

<FIG> is a diagram illustrating an example <NUM> of allocating physical uplink control channel (PUCCH) resources for ultra-reliable low latency communication (URLLC), in accordance with various aspects of the present disclosure. In example <NUM>, BS <NUM> and UE <NUM> exchange a plurality of transmissions (or communications) with one another. In some instances, the transmissions may be associated with a first type of service and in some instances the transmissions may be associated with a second type of service. As described in the following examples, the first type of service may be an eMBB service and the second type of service may be a URLLC service, although the first and second types of services may be different services. For example, the second type of service may have a lower latency requirement than the first type of service, may have a higher reliability requirement than the first type of service, may be associated with a higher priority than the first type of service, may be associated with a faster processing time (e.g., a shorter processing timeline) than the first type of service, and/or the like.

In example <NUM>, because certain transmissions may be associated with different types of services, that operate according to different parameters (e.g., URLLC provides a higher reliability and/or lower latency than eMBB), BS <NUM> and UE <NUM> may configure and/or use PUCCH resources based at least in part on the type of service that is associated with the transmissions.

As shown in <FIG>, and by reference number <NUM>, BS <NUM> determines resource configurations for PUCCH transmissions based at least in part on types of services that may be used for PUCCH transmissions with UE <NUM>. For example, BS <NUM> may determine a first configuration of PUCCH resources to be used for PUCCH transmissions when the PUCCH transmissions are associated with eMBB and a second configuration of PUCCH resources to be used for the PUCCH transmission when the PUCCH transmission is associated with URLLC.

The configurations of PUCCH resources may identify a number of sets of PUCCH resources (e.g., resource blocks) that are to be used for the PUCCH transmissions, a number of resources that are to be included in the sets of resources, and/or the like. A PUCCH resource may include a set of resource blocks. In some cases, each set of PUCCH resources is associated with an uplink control information (UCI) payload range. For example, a first set of PUCCH resources may be configured to transmit UCI with a size of <NUM> bit or <NUM> bits, a second set of PUCCH resources may be configured to transmit UCI with a size of <NUM> bits to X<NUM> bits, a third set of PUCCH resources may be configured to transmit UCI with a size of (X<NUM> + <NUM>) bits to X<NUM> bits, and so on. For URLLC, a payload size of UCI is typically small to assist with achieving high reliability. Thus, fewer sets of PUCCH resources (e.g., one or two sets) may be needed for URLLC as compared to eMBB (e.g., which may use four sets). Accordingly, a first configuration for a PUCCH transmission using an eMBB service may include more sets of resources than a second configuration for PUCCH transmissions using a URLLC service.

In some cases, a URLLC PUCCH resource may be configured with a finer granularity than an eMBB PUCCH resource. For example, the eMBB PUCCH resource configuration may configure PUCCH resources with a length of a slot (e.g., <NUM> symbols), whereas the URLLC PUCCH resource configuration may configure PUCCH resources with a length of a sub-slot (or mini-slot) (e.g., less than <NUM> symbols). As a result, the eMBB PUCCH resource configuration may need to configure both short (e.g., <NUM> or <NUM> symbols) and long (e.g., <NUM> to <NUM> symbols) PUCCH resources, whereas the URLLC PUCCH resource configuration may only need to configured PUCCH resources smaller than the sub-slot (or mini-slot) length. Thus, fewer resources are needed in each PUCCH resource set for URLLC as compared to eMBB. Accordingly, for PUCCH transmissions associated with a URLLC service, each set of resources may include fewer resources than a PUCCH transmission that is associated with an eMBB service. In this case, while eMBB services may utilize a relatively long PUCCH (<NUM> symbols), this may cause too high of a latency for URLLC service, which is to be configured more frequently (e.g., every <NUM> symbols) to achieve the low latency. For an eMBB service, it may not be necessary to configure so frequently, and doing so may be a waste of signaling bandwidth and/or network resources. Therefore, eMBB services may use sets and sizes of resources for PUCCH transmission configured for eMBB and URLLC services may use sets or sizes of resources for PUCCH transmissions that are configured for URLLC.

In some cases, a PUCCH resource may be used to transmit HARQ-ACK feedback associated with a downlink semi-persistent scheduling (SPS) transmission. A PUCCH resource for transmitting HARQ-ACK feedback for downlink SPS may be configured in a radio resource control (RRC) message as part of the downlink SPS configuration. For example, a periodic PUCCH resource may be configured in the RRC message, and that PUCCH resource may be used to periodically transmit PUCCH for downlink SPS transmissions. The PUCCH resource configuration for downlink SPS may indicate a PUCCH identifier (PUCCH ID) that identifies the PUCCH resource to be used for the HARQ-ACK feedback. However, when downlink SPS is separately configured for eMBB and URLLC, the base station <NUM> may need to indicate not only a PUCCH ID, but also whether the PUCCH resource is associated with a URLLC transmission (or an eMBB transmission or other service type). In this case, the UE <NUM> may select a PUCCH resource from the set of PUCCH resources configured for URLLC transmissions. Accordingly, BS <NUM> may determine separate configurations for the PUCCH resources associated with downlink SPS transmission based at least in part on the types of services (e.g., eMBB or URLLC) used in communications between BS <NUM> and UE <NUM>. For example, for PUCCH resources associated with downlink SPS, BS <NUM> may determine a first configuration of PUCCH resources to be used for PUCCH transmissions when the PUCCH and the downlink SPS transmissions are associated with eMBB, and a second configuration of PUCCH resources to be used for the PUCCH transmissions when the PUCCH and the downlink SPS transmissions are associated with URLLC.

In some aspects, BS <NUM> may determine a resource configuration that indicates that a same set of PUCCH resources may be accessible to UE <NUM> for PUCCH transmissions, but the resource configuration may assign a parameter to each of the PUCCH resources that allocates the PUCCH resources for use with a first type of service, a second type of service, or both types of service. For example, BS <NUM> may assign a parameter to each PUCCH resource, via the resource configuration for the PUCCH transmission, that indicates whether each PUCCH resource is to be used with eMBB, URLLC, or both eMBB and URLLC. As a result, as described herein, UE <NUM> may access a same set of PUCCH resources for both eMBB transmissions and URLLC transmissions, and select the appropriate resources for the PUCCH transmission according to the parameter and information received in the DCI (e.g., that identifies the PUCCH resources and/or a starting symbol of the PUCCH resources).

As further shown in <FIG>, and by reference number <NUM>, BS <NUM> transmits a PUCCH configuration with the resource configurations to UE <NUM>. In some aspects, the PUCCH configuration may include a first set of parameters for transmissions or communications associated with a first type of service (e.g., eMBB) and a second set of parameters for transmissions associated with a second type of service (e.g., URLLC). Additionally, or alternatively, BS <NUM> may send individual PUCCH configurations for the first type of service and the second type of service. For example, BS <NUM> may send a first PUCCH configuration for eMBB and a second PUCCH configuration for URLLC. In some aspects a maximum coding rate may be different for eMBB and URLLC. For example, the first set of parameters (and/or a first PUCCH configuration) may include a different maximum coding rate than a second set of parameters (and/or second PUCCH configuration).

As further shown in <FIG>, and by reference number <NUM>, BS <NUM> transmits a downlink communication with DCI. The downlink communication may include one or more packets associated with the type of service, which may indicate the type of service associated with the PUCCH transmission. For example, if the downlink communication is an eMBB communication, the PUCCH transmission may be associated with the eMBB services. Additionally, or alternatively, if the downlink communication is associated with a URLLC communication, the PUCCH transmission may be associated with the URLLC communication.

UE <NUM> may determine whether the DCI is associated with eMBB or URLLC. In some aspects, the DCI in the downlink communication may include an ACK/NACK resource indicator (ARI) field, referred to herein as a PUCCH resource indicator. In some aspects, UE <NUM> may determine a bitwidth (i.e., a number of bits) of the PUCCH resource indicator based at least in part on the type of service (e.g., eMBB or URLLC) to be used for the PUCCH transmission. For example, UE <NUM> may determine that the PUCCH resource indicator is <NUM> bits (e.g., indicating the number of resources of the sets of PUCCH resources is <NUM> or less), when the PUCCH transmission is associated with a URLLC transmission. As another example, UE <NUM> may determine that the PUCCH resource indicator is <NUM> bits (e.g., indicating the number of resources of the sets of PUCCH resources is <NUM> or less), when the PUCCH transmission is associated with an eMBB transmission.

As further shown in <FIG>, and by reference number <NUM>, UE <NUM> determines the type of service associated with the PUCCH transmission based at least in part on the downlink communication. In some aspects, UE <NUM> may determine the type of service based at least in part on the type of service used to receive and/or transmit a previous packet. For example, if the downlink communication is received via a first service, UE <NUM> may determine that the PUCCH transmission is to be transmitted using the first service and if the downlink communication is received via a second service, UE <NUM> may determine that the PUCCH transmission is to be transmitted using the second service.

As further shown in <FIG>, and by reference number <NUM>, UE <NUM> transmits the PUCCH transmission using the resources according to the resource configuration associated with the service type of the PUCCH transmission. Accordingly, using the DCI, UE <NUM> may determine which resource is to be used for the PUCCH transmission, and transmit the PUCCH transmission using that resource.

In some aspects, UE <NUM> may be configured with different PUCCH resource sets corresponding to the different services (e.g., eMBB and URLLC). UE <NUM> may determine which resources are to be used for the PUCCH transmission based at least in part on the configuration and the DCI within the received downlink communication that is related to the service type. For example, UE <NUM> may determine that the PUCCH transmission is associated with an eMBB service. In this case, UE <NUM> may select the PUCCH resource from the sets of resources configured for the eMBB service based at least in part on the configuration and the DCI within the received downlink communication. Additionally, or alternatively, UE <NUM> may determine that the PUCCH transmission is associated with a URLLC service. In this case, UE <NUM> may select the PUCCH resource from the sets of resources configured for the URLLC service based at least in part on the configuration and the DCI within the received downlink communication. The DCI may indicate a starting symbol, a number of OFDM symbols and resource blocks that are to be used, a PUCCH resource ID, and/or the like.

In some examples, when UE <NUM> uses a same PUCCH resource configuration for multiple types of services, UE <NUM> may refer to a table that indicates whether the PUCCH resources are to be used with URLLC or with eMBB (or with both). For example, UE <NUM> may refer to the following table identifying PUCCH resources for use with eMBB and URLLC:.

where the URLLC/eMBB flag identifies whether the PUCCH resource is to be used with URLLC PUCCH transmissions, eMBB PUCCH transmissions, or both URLLC and eMBB PUCCH transmissions. In some aspects, each PUCCH resource may have two separate identifiers (e.g., virtual IDs that are implicitly determined at the UE based at least in part on the URLLC/eMBB flag), one for URLLC and one for eMBB. As an example, for a PUCCH transmission associated with URLLC, UE <NUM> may receive PUCCH resource indicator = <NUM> (indicating a URLLC ID of <NUM>) in the DCI. Accordingly, UE <NUM>, using the PUCCH resource indicator = <NUM> and starting from resource #<NUM>, identifies resource #<NUM> as the PUCCH resource for the PUCCH transmission, where resource #<NUM> has a URLLC ID of <NUM>, resource #<NUM> has a URLLC ID of <NUM>, resource #<NUM> has a URLLC ID of <NUM>, and resource #<NUM> has a URLLC ID of <NUM>. Accordingly, each resource #<NUM>-<NUM> may have additional identifiers that are based at least in part on the type of service (e.g., eMBB or URLLC) that is associated with the PUCCH transmission.

In some aspects, UE <NUM> may use a starting symbol parameter to determine which PUCCH resource is to be used for the PUCCH transmission. The example starting symbol parameter, which may be included in the DCI, may be different for URLLC and eMBB. For example, for eMBB, the starting symbol parameter may refer to a relative index within a slot. Additionally, or alternatively, for URLLC, the starting symbol parameter may indicate a timing relative to a signaling (e.g., a K1 signaling in the DCI, which identifies when an ACK/NACK is to be transmitted).

In some aspects, to achieve transmit diversity (e.g., for a URLLC service PUCCH transmission), the PUCCH transmission may be transmitted over two or more resources of the sets of resources identified in the corresponding resource configuration. For example, for a PUCCH transmission associated with a URLLC service, the PUCCH transmission may be transmitted via at least two transmit antennas on two resources of the sets of resources allocated for the URLLC service to obtain transmit diversity gain. This can improve reliability of PUCCH transmissions within URLLC. In such cases, multiple PUCCH resources may be configured with a same identifier. Accordingly, if the DCI indicates that the PUCCH transmission is to be sent via a PUCCH resource with that identifier, the PUCCH transmission can be sent via multiple resources. In some cases, the DCI may indicate an index k and UE <NUM> may use PUCCH resources based at least in part on the index and a radio resource control (RRC) configuration M (e.g., which may be received via an RRC communication prior to receiving the DCI), which indicates the number of PUCCH resources that is allocated to the UE to transmit PUCCH. Accordingly, the k may be received dynamically and the M may be received semi-statically. UE <NUM> may use k and M to identify the PUCCH resources of the corresponding sets of resources that are to be used. For example, UE <NUM> may identify PUCCH resources with identifiers equal to M(k-<NUM>), M(k-<NUM>) +<NUM>,. , Mk-<NUM>. Additionally, or alternatively, the UE <NUM> may identify PUCCH resources with identifiers equal to k, k+<NUM>,. , k+M-<NUM>. In some aspects, different or additional PUCCH formats can be used to achieve transmit diversity. For example, certain PUCCH formats may be configured for URLLC but not for eMBB. In some aspects, the schemes discussed above in connection with transmit diversity may be applied for URLLC PUCCH transmissions but not applied for eMBB PUCCH transmissions.

A downlink assignment index (DAI) may be used to indicate the number of physical downlink shared channel (PDSCH) communications that the UE <NUM> has received up to the current DCI. For example, the UE <NUM> may receive an indication of a counter DAI and/or a total DAI. The value of the counter DAI may denote the accumulative number of serving cell PDCCH monitoring occasions in which PDSCH reception or SPS PDSCH release is present, up to the current serving cell and current PDCCH monitoring occasion. The value of total DAI, when present, may denote the total number of serving cell PDCCH monitoring occasion pair in which PDSCH reception and SPS PDSCH release is present, up to the current PDCCH monitoring occasion. In some aspects, the UE <NUM> may track and/or store different sets of DAIs for URLLC and eMBB, and may perform separate DAI counting and/or DAI accumulation for URLLC and eMBB. For example, the UE <NUM> may keep track of and/or store two sets of DAIs, where the first set of {counter DAI, total DAI} applies to URLLC transmissions only and the second set of {counter DAI, total DAI} applies to eMBB transmissions only. In this case, the URLLC DAI does not count toward the eMBB DAI, and vice versa. In some aspects, UE <NUM>, based at least in part on the PUCCH resource configurations, may be configured to perform separate DAI operations for different types of services. For example, uplink control information (UCI) in the PUCCH transmission may be determined according to a first downlink assignment index (DAI) operation when the PUCCH transmission is associated with eMBB, and the UCI in the PUCCH transmission may be determined according to a second DAI operation when the PUCCH transmission is associated with URLLC.

UE <NUM> may determine whether the DCI is associated with eMBB or URLLC. In some aspects, the DCI in the downlink communication may include a DAI field. In some aspects, UE <NUM> may determine a bitwidth (i.e., a number of bits) of the DAI based at least in part on the type of service (e.g., eMBB or URLLC) to be used for the PUCCH transmission. For example, UE <NUM> may determine that the DAI is <NUM> bit, when the PUCCH transmission is associated with a URLLC transmission. As another example, UE <NUM> may determine that the DAI is <NUM> bits, when the PUCCH transmission is associated with an eMBB transmission.

The example PUCCH transmission may be an ACK/NACK. The ACK/NACK may be sent dynamically (e.g., in response to receiving the downlink communication), and/or according to semi-persistent scheduling (SPS). In some aspects, different DAI operations may be performed with respect to ACK/NACK bundling for URLLC as compared to eMBB. More specifically, UE <NUM> may not multiplex between URLLC and eMBB when sending PUCCH transmissions. Accordingly, the ACK/NACK for receipt of URLLC packets may be sent in a separate PUCCH transmission from an ACK/NACK for receipt of eMBB packets. In some aspects, when ACK/NACKs for both URLLC and eMBB overlap in time, the eMBB ACK/NACK may be dropped (e.g., to meet the low latency and high reliability requirement of URLLC). However, if the transmissions are to occur in the same slot, but are not overlapping, then the eMBB ACK/NACK may not be dropped. For example, if a first PUCCH transmission is scheduled on symbols <NUM>-<NUM> and a second PUCCH transmission is scheduled on symbols <NUM>-<NUM>, then neither the first PUCCH transmission nor the second PUCCH transmission is dropped. Additionally, or alternatively, when two transmissions are configured to partially overlap, the overlapping portion of the eMBB PUCCH transmission may be dropped. For example, if an eMBB PUCCH transmission is on symbols <NUM>-<NUM> and an URLLC PUCCH transmission is to be on symbols <NUM>-<NUM>, then data in symbols <NUM>-<NUM> for the eMBB PUCCH transmission may be dropped.

In some aspects, the PUCCH transmission may include a service request (SR) (e.g., to request uplink resources) and/or a channel state information (CSI) report (e.g., to indicate a status of the channel used to receive the downlink communication).

<FIG> is a diagram illustrating examples <NUM> and <NUM> of allocating PUCCH resources for URLLC. In <FIG>, diagrams of resources that may be allocated according to a type of service (e.g., eMBB or URLLC) are shown. As shown by example <NUM>, eMBB PUCCH resource sets may be different from PUCCH resource sets allocated for URLLC. For example, eMBB PUCCH resources may include sets A, B, C, D and URLLC PUCCH resource sets may include sets X, Y, Z. Furthermore, as shown by example <NUM>, different amounts of resource sets may be allocated based at least in part on the type of service. For example, four PUCCH resource sets A, B, C, D are allocated for eMBB, while three resource sets X, Y, Z are allocated for URLLC.

As shown by example <NUM>, in some aspects, a same set of PUCCH resources may be shared for multiple types of services and some resource sets may be used for particular types of resource sets. For example, both eMBB and URLLC may use sets ABC, but only eMBB may use set <NUM> and only URLLC may use set <NUM>. Accordingly, PUCCH resource sets can be allocated for PUCCH transmissions based at least in part on the type of PUCCH transmission.

<FIG> is a diagram illustrating an example <NUM> of allocating PUCCH resources for URLLC. As shown by example <NUM>, to achieve transmit diversity, multiple resources within a set of resources may be assigned a same resource ID. In <FIG>, two resources have ID=<NUM> and four resources have ID=<NUM>. Accordingly, when UE <NUM> determines that a PUCCH transmission is to be transmitted via a PUCCH resource with ID=<NUM>, UE <NUM> may transmit the PUCCH transmission via two resources. Similarly, when UE <NUM> determines that a PUCCH transmission is to be transmitted via a PUCCH resource with ID=<NUM>, UE <NUM> may transmit the PUCCH transmission via four resources. In some aspects, the two PUCCH resources or the four PUCCH resources may be associated with the same time-domain resources (e.g., may be configured on the same OFDM symbols), in which case the UE <NUM> transmits PUCCHs on these indicated PUCCH resources simultaneously from different transmit antennas to achieve spatial diversity.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where a UE (e.g., UE <NUM> and/or the like) performs operations associated with identifying PUCCH resources and sending a PUCCH transmission using PUCCH resources allocated in accordance with some examples described herein.

As shown in <FIG>, in some aspects, process <NUM> may include determining whether a PUCCH transmission is associated with a first type of service or a second type of service, wherein the second type of service is associated with a higher reliability or a lower latency than the first type of service (block <NUM>). For example, the UE (e.g., using receive processor <NUM>, transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may determine whether a PUCCH transmission is associated with a first type of service or a second type of service, as described above. In some aspects, the second type of service is associated with a higher reliability or a lower latency than the first type of service.

As further shown in <FIG>, in some aspects, process <NUM> may include transmitting the PUCCH transmission using a first set of resources when the PUCCH transmission is associated with the first type of service or using a second set of resources when the PUCCH transmission is associated with the second type of service (block <NUM>). For example, the UE (e.g., using receive processor <NUM>, transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may transmit the PUCCH transmission using a first set of resources when the PUCCH transmission is associated with the first type of service or using a second set of resources when the PUCCH transmission is associated with the second type of service, as described above.

In a first aspect, the first type of service comprises an enhanced mobile broadband (eMBB) service and the second type of service comprises an ultra-reliable, low-latency communication (URLLC) service.

In a second aspect, alone or in combination with the first aspect, the first set of resources includes multiple resource sets configured for the first type of service.

In a third aspect, alone or in combination with one or more of the first and second aspects, the second set of resources includes multiple resource sets configured for the second type of service.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the PUCCH transmission comprises at least one of: an acknowledgement and/or negative acknowledgement (ACK/NACK), a service request (SR), or a channel state information (CSI) report.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the ACK/NACK is associated with dynamic scheduling or semi-persistent scheduling (SPS).

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the first set of resources includes four resource sets, and the second set of resources includes fewer than four resource sets.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the first set of resources is different than the second set of resources.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, a number of resource sets in the second set of resources is less than a number of resource sets in the first set of resources.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, at least one resource set of the first set of resources is a same resource set as a resource set included in the second set of resources.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, a number of resources within each set of the second set of resources is less than a number of resources within each set of the first set of resources.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the UE is configured to determine a number of resources within each set of the first set of resources or the second set of resources based at least in part on a bitwidth of a PUCCH resource indicator field in downlink control information (DCI) received from a base station in association with the PUCCH transmission.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the PUCCH transmission is transmitted over two or more resources of the second set of resources based at least in part on a determination that the PUCCH transmission is associated with the second type of service.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the PUCCH transmission is transmitted via at least two transmit antennas on two resources of the second set of resources based at least in part on a determination that the PUCCH transmission is associated with the second type of service.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, at least two resources of one set of the second set of resources share a same identifier and the PUCCH transmission is transmitted using the at least two resources when the identifier is received in association with the PUCCH transmission.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the PUCCH transmission is transmitted using one or more resources of the second set of resources based at least in part on receiving, from a base station, an index and a semi-statically received configuration in association with the PUCCH transmission.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, resources of the second set of resources are identified for use in connection with the PUCCH transmission differently than resources of the first set of resources.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the resources of the second set of resources are identified for use in connection with the PUCCH transmission differently than the resources of the first set of resources in connection with using a different PUCCH format.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, a resource of the first set of resources is identified for use in association with the first type of service based at least in part on a first value of a parameter associated with the resource of the first set of resources, or a resource of the second set of resources is identified for use in association with the second type of service based at least in part on a second value of the parameter associated with the resource of the second set of resources.

In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, for a resource of the PUCCH transmission, a parameter indicates whether the resource is associated with the first type of service, the second type of service, or both the first type of service and the second type of service based at least in part on a value of the parameter.

In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the parameter is included within a configuration of the resource for the PUCCH transmission.

In a twenty-first aspect, alone or in combination with one or more of the first through twentieth aspects, the value of the parameter indicates that a same resource of the first set of resources and the second set of resources is associated with the first type of service and the second type of service.

In a twenty-second aspect, alone or in combination with one or more of the first through twenty-first aspects, the first set of resources is a same set of resources as the second set of resources. In some aspects, each resource of the same set of resources is associated with a first identifier for the PUCCH transmission when the PUCCH transmission is associated with the first type of service and a second identifier for the PUCCH transmission when the PUCCH transmission is associated with the second type of service.

In a twenty-third aspect, alone or in combination with one or more of the first through twenty-second aspects, the PUCCH transmission is transmitted using one of the same set of resources based at least in part on receiving downlink control information that indicates an index associated with the first type of service or the second type of service.

In a twenty-fourth aspect, alone or in combination with one or more of the first through twenty-third aspects, a starting symbol parameter identifies a different starting symbol when the PUCCH transmission is associated with the first type of service than when the PUCCH transmission is associated with the second type of service.

In a twenty-fifth aspect, alone or in combination with one or more of the first through twenty-fourth aspects, the starting symbol parameter when the PUCCH transmission is associated with the first type of service identifies a relative index with a slot for the PUCCH transmission.

In a twenty-sixth aspect, alone or in combination with one or more of the first through twenty-fifth aspects, the starting symbol parameter when the PUCCH transmission is associated with the second type of service identifies a timing associated with signaling in downlink control information (DCI).

In a twenty-seventh aspect, alone or in combination with one or more of the first through twenty-sixth aspects, uplink control information (UCI) in the PUCCH transmission is determined according to a first downlink assignment index (DAI) operation when the PUCCH transmission is associated with the first type of service and the UCI in the PUCCH transmission is determined according to a second DAI operation when the PUCCH transmission is associated with the second type of service.

In a twenty-eighth aspect, alone or in combination with one or more of the first through twenty-seventh aspects, when the PUCCH transmission is a first PUCCH transmission associated with the first type of service, and a second PUCCH transmission associated with the second type of service is to be transmitted on using symbols that overlap with the symbols of the first PUCCH transmission, the symbols that overlap are dropped from the first PUCCH transmission.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a base station, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where a base station (e.g., base station <NUM> and/or the like) performs operations associated with allocation of PUCCH resources in connection with a type of service associated with a PUCCH transmission.

As shown in <FIG>, in some aspects, process <NUM> may include determining a first configuration of PUCCH resources to be used for PUCCH transmissions associated with a first type of service (block <NUM>). For example, the base station (e.g., using controller/processor <NUM>, memory <NUM>, and/or the like) may determine a first configuration of PUCCH resources to be used for PUCCH transmissions associated with a first type of service, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include determining a second configuration of PUCCH resources to be used for PUCCH transmissions associated with a second type of service, wherein the second type of service is associated with a higher reliability or a lower latency than the first type of service (block <NUM>). For example, the base station (e.g., using controller/processor <NUM>, memory <NUM>, and/or the like) may determine a second configuration of PUCCH resources to be used for PUCCH transmissions associated with a second type of service, as described above. In some aspects, the second type of service is associated with a higher reliability or a lower latency than the first type of service.

As further shown in <FIG>, in some aspects, process <NUM> may include transmitting the first configuration and the second configuration to a user equipment (UE) (block <NUM>). For example, the base station (e.g., using transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may transmit the first configuration and the second configuration to a UE, as described above.

In a second aspect, alone or in combination with the first aspect, the first configuration is different from the second configuration.

In a third aspect, alone or in combination with one or more of the first and second aspects, sets of PUCCH resources included in the first configuration are different than sets of PUCCH resources included in the second configuration.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the second configuration includes fewer sets of PUCCH resources than the first configuration.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, a number of PUCCH resources in each set of PUCCH resources included in the second configuration is less than a number of PUCCH resources in each set of PUCCH resources included in the first configuration.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, a bitwidth of a PUCCH resource indicator in downlink control information (DCI) corresponds to the second type of service according to a number of PUCCH resources in each set of PUCCH resources included in the second configuration.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, for each PUCCH resource of the first configuration and the second configuration, a parameter indicates whether the PUCCH resource is associated with the first type of service, the second type of service, or both the first type of service and the second type of service.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, a first set of resources of the first configuration is a same set of resources as a second set of resources of the second configuration, and each resource of the same set of resources is associated with a first identifier for a PUCCH transmission when the PUCCH transmission is associated with the first type of service and a second identifier for the PUCCH transmission when the PUCCH transmission is associated with the second type of service.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the first configuration is one of a first plurality of configurations of PUCCH resources to be used for PUCCH transmissions associated with the first type.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, a maximum coding rate of the first configuration is different than a maximum coding rate of the second configuration.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where a UE (e.g., UE <NUM> and/or the like) performs operations associated with using a PUCCH configuration, configured according to a type of service, to transmit a message associated with that type of service.

As shown in <FIG>, in some aspects, process <NUM> may include receiving a PUCCH configuration comprising a first set of parameters for transmissions associated with a first service type and a second set of parameters for transmissions associated with a second service type (block <NUM>). For example, the UE (e.g., using receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may receive a PUCCH configuration comprising a first set of parameters for transmissions associated with a first service type and a second set of parameters for transmissions associated with a second service type, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include generating uplink control information (UCI) (block <NUM>). For example, the UE (e.g., using transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may generate UCI, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include transmitting a message that includes the UCI according to the PUCCH configuration and a service type of the message (block <NUM>). For example, the UE (e.g., using transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may transmit a message that includes the UCI according to the PUCCH configuration and a service type of the message, as described above.

In a first aspect, the service type of the message is determined based at least in part on downlink control information (DCI) received from a base station.

In a second aspect, alone or in combination with the first aspect, a maximum coding rate indicated by the first set of parameters is different than a maximum coding rate indicated by the second set of parameters.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a base station, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where a BS (e.g., BS <NUM> and/or the like) performs PUCCH configuration for a plurality of types of services (e.g., eMBB and URLLC).

As shown in <FIG>, in some aspects, process <NUM> may include determining a first configuration of a PUCCH to be used for PUCCH transmissions associated with a first type of service (block <NUM>). For example, BS <NUM> (e.g., using transmit processor <NUM>, TX MIMO processor <NUM>, controller/processor <NUM>, and/or the like) may determine a first configuration of a PUCCH to be used for PUCCH transmissions associated with a first type of service, as described above. In some aspects, BS <NUM> may determine the first configuration in connection with receiving an indication that UE <NUM> is capable of communicating via the first type of service.

As shown in <FIG>, in some aspects, process <NUM> may include determining a second configuration of the PUCCH to be used for PUCCH transmissions associated with a second type of service, wherein the second type of service is associated with a higher reliability or a lower latency than the first type of service (block <NUM>). For example, BS <NUM> (e.g., using transmit processor <NUM>, TX MIMO processor <NUM>, controller/processor <NUM>, and/or the like) may determine a second configuration of the PUCCH to be used for PUCCH transmissions associated with a second type of service, as described above. In some aspects, the second type of service is associated with a higher reliability or a lower latency than the first type of service. In some aspects, BS <NUM> may determine the second configuration in connection with receiving an indication that UE <NUM> is capable of communicating via the second type of service.

As shown in <FIG>, in some aspects, process <NUM> may include transmitting the first configuration and the second configuration to a user equipment (UE) (block <NUM>). For example, BS <NUM> (e.g., using transmit processor <NUM>, TX MIMO processor <NUM>, modulator <NUM>, antenna <NUM>, controller/processor <NUM>, and/or the like) may transmit the first configuration and the second configuration to UE <NUM>, as described above. In some aspects, BS <NUM> may transmit the first configuration and the second configuration in connection with determining the first configuration and the second configuration.

In a second aspect, alone or in combination with the first aspect, a maximum coding rate of the first configuration of the PUCCH is different than a maximum coding rate of the second PUCCH configuration.

Claim 1:
A method of wireless communication performed by a user equipment, UE, comprising:
receiving downlink control information, DCI, from a base station, BS;
determining (<NUM>) whether a physical uplink control channel, PUCCH, transmission is associated with a first type of service or a second type of service, wherein the second type of service is associated with a higher reliability or a lower latency than the first type of service; and
transmitting (<NUM>) the PUCCH transmission based at least in part on a first set of resources when the PUCCH transmission is associated with the first type of service or based at least in part on a second set of resources when the PUCCH transmission is associated with the second type of service;
wherein the PUCCH transmission is determined based on a downlink assignment index, DAI, field included in the DCI; and
wherein a first bitwidth of the DAI field for the first type of service is different to a second bitwidth of the DAI field for the second type of service.