Patent Description:
<CIT> relates to Physical Uplink Control Channel (PUUCH) design for <NUM>th generation (<NUM>) new radio (NR).

<NPL>, relates to a summary of UL waveform design options for NR-U in sub-<NUM> band along with a performance evaluation.

<NPL>, relates to a number of observations and proposals for NR short PUCCH design.

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 uplink control channel transmission in high band operation, 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>, 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, memory <NUM> and/or memory <NUM> may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the base station <NUM> and/or the UE <NUM>, may cause the one or more processors, the UE <NUM>, and/or the base station <NUM> to perform or direct operations of, for example, process <NUM> of <FIG>, process <NUM> of <FIG>, and/or other processes as described herein. In some aspects, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

In some aspects, UE <NUM> may include means for determining an increased bandwidth configuration for an ePUCCH based at least in part on an ePUCCH format of the ePUCCH, wherein the increased bandwidth configuration uses a plurality of contiguous RBs for the ePUCCH, means for transmitting the ePUCCH using the increased bandwidth configuration, means for performing frequency-domain OCC operations for the plurality of contiguous RBs based at least in part on the increased bandwidth configuration, means for performing time-domain orthogonal cover coding (OCC) for the plurality of contiguous RBs based at least in part on the increased bandwidth configuration, and/or the like. In some aspects, such means may include one or more components of UE <NUM> described in connection with <FIG>, such as controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, and/or the like.

In some aspects, base station <NUM> may include means for determining an increased bandwidth configuration for an ePUCCH based at least in part on an ePUCCH format of the ePUCCH, wherein the increased bandwidth configuration uses a plurality of contiguous RBs for the ePUCCH, means for receiving the ePUCCH using the increased bandwidth configuration, and/or the like. In some aspects, such means may include one or more components of base station <NUM> described in connection with <FIG>, such as antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like.

A physical uplink control channel (PUCCH) is a physical channel used by a UE to convey control information. A PUCCH may be generated in accordance with a format. Different formats of PUCCH may be used to carry different types of information, may be used in different scenarios, and may be associated with different characteristics. A baseline NR deployment (e.g., enhanced mobile broadband (eMBB)) may be associated with five PUCCH formats (e.g., PUCCH Formats <NUM>, <NUM>, and <NUM> which may occupy one resource block (RB), and PUCCH Formats <NUM> and <NUM> which may occupy a configurable number of resource blocks).

In unlicensed Frequency Range <NUM> (FR1) bands, enhanced PUCCH (ePUCCH) formats may be used. The ePUCCH formats may include ePUCCH Formats <NUM>, <NUM>, <NUM>, and <NUM>, which are described below. A PUCCH that uses an ePUCCH format is referred to herein as an ePUCCH. In some aspects, an ePUCCH may use an interlace structure, meaning that RBs of the ePUCCH are interlaced across a set of resources. The usage of the interlace structure may increase the usable power (e.g., to a per UE maximum of <NUM> decibel-milliwatts (dBm)) while conforming with power spectral density (PSD) limits of <NUM> to <NUM> dBm per MHz. In some aspects, the interlace may spread out the RBs of the ePUCCH so that each RB can be transmitted at higher power while remaining under the PSD limits.

In some aspects, for ePUCCH Formats <NUM> and <NUM>, different RBs in the interlace may use different cyclic shifts, and a cyclic shift step size increase (e.g., to a step size of <NUM>) may be used for adjacent RBs in the interlace. In some aspects, for ePUCCH Format <NUM>, frequency-domain orthogonal cover coding (OCC) operations may be performed with OCC lengths of <NUM>, <NUM>, or <NUM> for user multiplexing. In some aspects, the OCC may be cycled across physical resource blocks (PRBs) of an interface to reduce peak-to-average power ratio (PAPR) and cubic metric (CM) values. In some aspects, for ePUCCH Format <NUM>, user multiplexing of control data associated with the ePUCCH may be based at least in part on pre-discrete Fourier transform (pre-DFT) OCC with block-wise repetition in the time domain, followed by mapping over the RBs across the interlace. User multiplexing for reference signals may be based at least in part on the use of different cyclic shifts of the same base sequence for all multiplexed users. An interlaced set of RBs may be referred to herein as a non-contiguous set of RBs.

A PUCCH in an unlicensed band higher than FR1, such as FR2, may occupy a larger bandwidth than a PUCCH in FR1. In some aspects, with a <NUM> subcarrier spacing (SCS), a PUCCH's total occupied bandwidth (referring to eMBB PUCCHs) may be <NUM> for PUCCH Formats <NUM>, <NUM>, and <NUM>, and up to approximately <NUM> with PUCCH Formats <NUM> and <NUM>. As another example, with a <NUM> SCS, a PUCCH's total occupied bandwidth may be approximately <NUM> for PUCCH Formats <NUM>, <NUM>, and <NUM>, and up to approximately <NUM> for PUCCH Formats <NUM> and <NUM>. In higher bands, there may be a PSD limit of <NUM> dBm/MHz with up to <NUM> dBm Effective Isotropic Radiated Power (EIRP). In some aspects, while a mobile terminal (e.g., a UE) may operate at approximately <NUM> dBm, some other user terminals, such as CPEs, may operate at a higher EIRP, such as up to the <NUM> dBm EIRP limit. However, the wider bandwidth of the PUCCH in the higher bands may mean that interlacing, such as the interlacing prescribed by the ePUCCH formats of unlicensed FR1, causes suboptimal resource utilization.

Some techniques and apparatuses described herein provide ePUCCH formats using an increased bandwidth configuration for higher bands, such as FR2, that use a contiguous set of RBs (e.g., without interlacing). In some aspects, an ePUCCH in a higher band may use a sufficiently wide bandwidth that interlacing provides little benefit at the cost of increased channel utilization, and the maximum transmit power requirements of the higher band may be achievable without using interlacing. A configuration for an ePUCCH that uses a contiguous set of RBs may be referred to as an increased bandwidth configuration. Particular examples of increased bandwidth configurations for an unlicensed higher band are described in connection with <FIG>. Thus, resource utilization, efficiency of PUCCH transmissions, and PAPR in unlicensed higher bands, such as FR2, are improved.

<FIG> is a diagram illustrating an example <NUM> of transmitting an ePUCCH in a higher band using an increased bandwidth configuration, in accordance with the present disclosure. As shown, example <NUM> includes a UE <NUM> and a BS <NUM>. As shown by reference number <NUM>, the UE <NUM> may be associated with a higher band, such as FR2 or a band higher than FR2. For example, the UE <NUM> may be configured to communicate in the higher band. As another example, the UE <NUM> may be associated with a frequency higher than <NUM>. In some aspects, the UE <NUM> may be associated with an SCS of <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and/or the like. Furthermore, the higher band may be unlicensed, meaning that the UE <NUM> may use channel access mechanisms to access the higher band.

As shown by reference number <NUM>, the UE <NUM> may determine an increased bandwidth configuration for an ePUCCH based at least in part on an ePUCCH format. For example, the UE <NUM> may receive information (e.g., configuration information, system information, or the like) indicating the ePUCCH format. In some aspects, the information indicating the ePUCCH format may indicate a maximum transmission bandwidth N_RB (in terms of resource blocks) and the ePUCCH format. In some aspects, the UE <NUM> may use an ePUCCH format based at least in part on the higher band being unlicensed. For example, the UE <NUM> may determine that an operating band of the UE <NUM> is a higher band and is unlicensed and may therefore determine to use the ePUCCH format. As another example, the UE <NUM> may receive information indicating the ePUCCH format based at least in part on the higher band being unlicensed.

The increased bandwidth configuration may use a contiguous set of RBs for the ePUCCH. In some aspects, the increased bandwidth configuration may not use an interlaced waveform for the ePUCCH. As shown by reference number <NUM>, the UE <NUM> may transmit the ePUCCH in accordance with the ePUCCH format. In some aspects, the UE <NUM> may transmit the ePUCCH using the increased bandwidth configuration. In some aspects, the UE <NUM> may perform frequency-domain and/or time-domain OCC based at least in part on the ePUCCH format, as described in more detail in connection with <FIG>. Thus, the resource efficiency of the ePUCCH may be improved, while a maximum transmit power is achieved.

<FIG> is a diagram illustrating an example <NUM> of an increased bandwidth configuration for an ePUCCH Format <NUM> or Format <NUM>, in accordance with the present disclosure. The increased bandwidth configuration for the ePUCCH Format <NUM> or <NUM> may use a contiguous set of RBs. In some aspects, each RB may span more than <NUM>, so an interlaced waveform may not be needed to achieve acceptable transmit power. Furthermore, aggregating the contiguous set of RBs may achieve lower PAPR than an interlaced waveform. Still further, the usage of contiguous RBs may enable frequency hopping.

In some aspects, the increased bandwidth configuration for the ePUCCH Format <NUM> or <NUM> may use an increased sequence length (that is, an extended sequence) relative to an existing PUCCH format defined in NR or to an ePUCCH Format that does not use an increased bandwidth configuration. For example, a longer sequence with M RBs may be used for ePUCCH Format <NUM> or <NUM>, where M is the number of RBs included in a PUCCH resource. Thus, the sequence may have a length equal to a total number of mapped REs of the PUCCH resource. In some aspects, the increased sequence length for the enhanced PUCCH format <NUM> or <NUM> may allow for the increased cyclic shift separation and the increased cyclic shift separation may enable better user multiplexing with PUCCH Format <NUM> or <NUM>. In some aspects, different cyclic shifts may be used to indicate an acknowledgment (ACK), a negative ACK (NACK), a scheduling request (SR), and so on. This may be particularly beneficial in bands higher than FR1 or FR2, since the channel's coherent bandwidth can be larger than in FR1 or FR2. Additionally, or alternatively, the increased bandwidth configuration for the ePUCCH Format <NUM> or <NUM> may use a different cyclic shift on each RB spanned by the increased bandwidth and the cyclic shift on each adjacent RB may be increased by a step size with the starting cyclic shift configured or signaled for the first RB for the ePUCCH format <NUM> or <NUM> of a default cyclic shift step size.

In some aspects, the ePUCCH may be split into a plurality of RB groups, such as K RB groups. This is shown by reference number <NUM>. An RB group may include one or more RBs. In this case, and as shown, each RB group may use a cyclic shift value in accordance with a cyclic shift step size. For example, cyclic shifts may be cycled across RBs in accordance with the cyclic shift step size. In some aspects, a first set of RB groups (e.g., <NUM> RB groups, or a different number depending on the cyclic shift and the number of RBs) may use a first root, and a second set of RB groups may use a second root. In some aspects, the cyclic shift step size may indicate a positive or negative SR. In some aspects, the UE <NUM> may select a different cyclic shift step size based at least in part on a positive or negative SR. In some aspects, as shown, the ePUCCH may use repetition in the frequency domain. As further shown, the ePUCCH may use a sequence of length N for each RB group of the PUCCH resource. In some aspects, N may be equal to the number of mapped REs per RB of the PUCCH resource. In some aspects, the sequence may be repeated in each RB group (such as with a different cyclic shift X<NUM>.

Reference number <NUM> shows an example of an ePUCCH that uses a longer sequence than the example shown by reference number <NUM>. In some aspects, the ePUCCH shown by reference number <NUM> may use a sequence that spans a plurality of RBs. For example, the sequence may span the ePUCCH (e.g., may have a length equal to the total number of mapped REs of a PUCCH resource of the ePUCCH). In this case, the ePUCCH may use a first root, and a next ePUCCH may use a second root.

<FIG> is a diagram illustrating an example <NUM> of an increased bandwidth configuration for an ePUCCH Format <NUM>, in accordance with the present disclosure. In example <NUM>, <NUM> RBs (each with <NUM> resource elements (REs)) are code-division multiplexed (CDM). In some aspects, the increased bandwidth configuration for the ePUCCH Format <NUM> may use frequency-domain OCC for a plurality of contiguous RBs. In some aspects, the frequency-domain OCC may have a length greater than <NUM>, such as <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or the like. Here, the frequency-domain OCC has a length of <NUM>. Thus, multiple contiguous RBs may be multiplexed with frequency domain OCC spanning multiple contiguous RBs. This may be particularly useful for a <NUM> SCS, since the channel may be relatively flat in such an SCS, leading to improved PAPR relative to other SCSs. It should be noted that any number of contiguous RBs can be multiplexed in this fashion.

<FIG> is a diagram illustrating an example <NUM> of an increased bandwidth configuration such as for an ePUCCH Format <NUM>, in accordance with the present disclosure. The increased bandwidth configuration may use block-wise pre-DFT time-domain OCC operations for M contiguous RBs, where M can include all allocated RBs. In some aspects, the OCC length may be extended beyond <NUM> (e.g., to <NUM>, <NUM>, <NUM>, or another number), which may be particularly beneficial for the <NUM> SCS. In example <NUM>, as shown, block-wise pre-DFT time-domain OCC operations are performed for <NUM> modulation signals [b<NUM>. b<NUM>-<NUM>] to be transmitted by a UE0 (e.g., UE <NUM>) and a UE1 (e.g., UE <NUM>). As further shown, block-wise pre-DFT time-domain OCC operations and DFT spreading leads to the UE0 and the UE1 using alternating tones, thus reducing interference between the UE0 and the UE1. For example, the UE0 uses a first tone, a third tone, and so on, as indicated by shading of the tones shown by reference number <NUM> in the UE0's diagram. Furthermore, the UE1 uses a second tone, a fourth tone, and so on, as indicated by shading of the tones shown by reference number <NUM> in the UE1's diagram. In some aspects, example <NUM> may be applicable for an ePUCCH Format <NUM> or an ePUCCH Format <NUM>.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a UE, in accordance with the present disclosure. Example process <NUM> is an example where the UE (e.g., UE <NUM> and/or the like) performs operations associated with uplink control channel transmission in high band operation.

As shown in <FIG>, in some aspects, process <NUM> may include receiving configuration information indicating an enhanced physical uplink control channel (ePUCCH) format for an ePUCCH, wherein the ePUCCH is associated with an increased bandwidth configuration based at least in part on the ePUCCH format of the ePUCCH, wherein the increased bandwidth configuration uses a plurality of contiguous RBs for the ePUCCH (block <NUM>). In some aspects, the UE (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may receive configuration information, such as via radio resource control (RRC) signaling, medium access control (MAC) signaling, downlink control information (DCI), or a combination thereof. The configuration information may indicate an ePUCCH format for an ePUCCH. The ePUCCH format may be associated with an increased bandwidth configuration, as described above. In some aspects, the increased bandwidth configuration uses a plurality of contiguous RBs for the ePUCCH.

As further shown in <FIG>, in some aspects, process <NUM> may include transmitting the ePUCCH using the increased bandwidth configuration (block <NUM>). In some aspects, the UE (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may transmit the ePUCCH using the increased bandwidth configuration, as described above.

In a first aspect, based at least in part on the increased bandwidth configuration, the plurality of contiguous RBs are encoded using an extended sequence relative to a sequence specified by the ePUCCH format for the ePUCCH.

In a second aspect, alone or in combination with the first aspect, based at least in part on the increased bandwidth configuration, the plurality of contiguous RBs are encoded using respective cyclic shifts relative to a cyclic shift specified by the ePUCCH format for the ePUCCH.

In a third aspect, alone or in combination with the first aspect and/or the second aspect, the respective cyclic shifts are different for each RB of the plurality of contiguous RBs, and wherein the respective cyclic shifts are derived based at least in part on a cyclic shift step size relative to the cyclic shift specified by the ePUCCH format for the ePUCCH.

In a fourth aspect, alone or in combination with one or more of the first and third aspects, based at least in part on the increased bandwidth configuration, the plurality of contiguous RBs are grouped into a plurality of groups of contiguous RBs.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the plurality of groups of contiguous RBs are associated with a same root and respective cyclic shift values based at least in part on a cyclic shift step size.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the plurality of groups of contiguous RBs are associated with different roots.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, a cyclic shift step size of the ePUCCH is selected based at least in part on whether the ePUCCH is multiplexed with a scheduling request.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the ePUCCH format is an ePUCCH Format <NUM> or an ePUCCH Format <NUM>.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, process <NUM> includes performing frequency-domain OCC operations for the plurality of contiguous RBs based at least in part on the increased bandwidth configuration.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, each of the frequency-domain OCC operations spans one or more contiguous RBs.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the frequency-domain OCC operations are performed using a length greater than <NUM>.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the ePUCCH format is an ePUCCH Format <NUM>.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, process <NUM> includes performing time-domain OCC for the plurality of contiguous RBs based at least in part on the increased bandwidth configuration.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the time-domain OCC operations comprise block-wise time-domain OCC operations performed before DFT precoding.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the time-domain OCC operations are performed across all RBs of the plurality of contiguous RBs.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the time-domain OCC operations are performed using a length greater than <NUM>.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the ePUCCH format is an ePUCCH Format <NUM>.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, receiving configuration information indicating an ePUCCH format for an ePUCCH associated with an increased bandwidth configuration is based at least in part on the UE being associated with a frequency range above <NUM>.

<FIG> is a diagram illustrating an example process <NUM> performed, in some aspects, by a base station, in accordance with the present disclosure. Example process <NUM> is an example where the base station (e.g., BS <NUM> and/or the like) performs operations associated with uplink control channel transmission in high band operation.

As shown in <FIG>, in some aspects, process <NUM> may include transmitting configuration information indicating an ePUCCH format for an ePUCCH, wherein the ePUCCH is associated with an increased bandwidth configuration based at least in part on the ePUCCH format of the ePUCCH, wherein the increased bandwidth configuration uses a plurality of contiguous RBs for the ePUCCH (block <NUM>). In some aspects, the base station (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may transmit configuration information (such as via RRC signaling, MAC signaling, DCI, or a combination thereof). The configuration information may indicate an ePUCCH format for an ePUCCH. The ePUCCH may be associated with an increased bandwidth configuration based at least in part on the ePUCCH format of the ePUCCH, as described above. In some aspects, the increased bandwidth configuration uses a plurality of contiguous RBs for the ePUCCH.

As further shown in <FIG>, in some aspects, process <NUM> may include receiving the ePUCCH using the increased bandwidth configuration (block <NUM>). In some aspects, the base station (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may receive the ePUCCH using the increased bandwidth configuration, as described above.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the ePUCCH uses frequency-domain OCC operations for the plurality of contiguous RBs based at least in part on the increased bandwidth configuration.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the ePUCCH uses time-domain orthogonal cover coding (OCC) operations for the plurality of contiguous RBs based at least in part on the increased bandwidth configuration.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the time-domain OCC operations are performed using a length greater than <NUM>.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the ePUCCH format is an ePUCCH Format <NUM>.

Claim 1:
A user equipment (<NUM>), UE, for wireless communication, the UE (<NUM>) comprising:
a memory; and
one or more processors, coupled to the memory, configured to:
receive configuration information indicating an enhanced physical uplink control channel, ePUCCH, format for an ePUCCH, wherein the ePUCCH is associated with an increased bandwidth configuration based at least in part on the ePUCCH format of the ePUCCH, wherein the increased bandwidth configuration uses a plurality of contiguous resource blocks, RBs, for the ePUCCH; and
transmit the ePUCCH using the increased bandwidth configuration, wherein, based at least in part on the increased bandwidth configuration, the plurality of contiguous RBs are encoded using an extended sequence relative to a sequence specified by the ePUCCH format for the ePUCCH, and
wherein the ePUCCH format is an ePUCCH Format <NUM> or an ePUCCH Format <NUM>.