Patent Description:
The present disclosure relates generally to wireless communication systems, and more particularly, to uplink power control procedures.

Examples of such multiple-access technologies include Long Term Evolution (LTE) systems, LTE Advanced (LTE-A) systems, code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

In some examples, a wireless multiple-access communication system may include a number of base stations, each simultaneously supporting communication for multiple communication devices, otherwise known as user equipment (UEs). In LTE or LTE-A network, a set of one or more base stations may define an evolved Node B (eNB). In other examples (e.g., in a next generation or <NUM> network), a wireless multiple access communication system may include a number of distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmission reception points (TRPs), etc.) in communication with a number of central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), where a set of one or more distributed units, in communication with a central unit, may define an access node (e.g., a new radio base station (NR BS), a new radio BS (NR NB), a network node, <NUM> NB, eNB, a Next Generation NB (gNB), etc.). A BS or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a BS or to a UE) and uplink channels (e.g., for transmissions from a UE to a BS or DU).

3GPP Draft R1-<NUM> describes aspects of power control for NR. 3GPP draft R1-<NUM> describes a proposal for uplink power control.

Certain aspects provide a method for wireless communication by a user equipment (UE). The method generally includes obtaining at least first and second parameters for determining transmit power for a physical uplink shared channel (PUSCH) transmission, obtaining at least a third parameter, based on a relationship between the third parameter and the at least two parameters, and transmitting the PUSCH, with a transmit power calculated based on the first, second, and third parameters.

NR may support various wireless communication services, such as Enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g. <NUM> beyond), millimeter wave (mmW) targeting high carrier frequency (e.g. <NUM>), massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low latency communications (URLLC).

Aspects provide techniques and apparatus for to resource element group (REG) bundle interleaver design for mapping of REGs to control channel elements (CCEs) to support control resource set (CORESET) overlapping in communication systems operating according to NR technologies. Aspects provide a two-step interleaver design for efficient overlapping coreset. The first step includes permuting REG bundles in a segment of REG bundles to produced interleaved blocks (e.g., groups) of REG bundles, such that REG bundles from a same CCE are in different interleaved blocks. Thus, in the second step of the interleaving, the interleaved blocks are interleaved across the entire coreset and the REG bundles of the same CCE in the different blocks can end up far apart, thereby improving frequency diversity.

<FIG> illustrates an example wireless network <NUM>, such as a new radio (NR) or <NUM> network, in which aspects of the present disclosure may be performed. For example, UEs <NUM> shown in <FIG> may be configured to perform transmit power control in accordance with operations <NUM> described below.

As illustrated in <FIG>, the wireless network <NUM> may include a number of base stations (BSs) <NUM> and other network entities. A BS may be a station that communicates with UEs. Each BS <NUM> may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to a coverage area of a Node B and/or a NB subsystem serving this coverage area, depending on the context in which the term is used. In NR systems, the term "cell" and evolved NB (eNB), NB, <NUM> NB, Next Generation NB (gNB), access point (AP), BS, NR BS, <NUM> BS, or transmission reception point (TRP) may be interchangeable. In some examples, the BSs may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in the wireless network <NUM> through various types of backhaul interfaces such as a direct physical connection, a virtual network, or the like using any suitable transport network.

A network controller <NUM> may be coupled to a set of BSs and provide coordination and control for these BSs. The BSs <NUM> may also communicate with one another, e.g., directly or indirectly via wireless or wireline backhaul.

A UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a Customer Premises Equipment (CPE), a cellular phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or medical equipment, a biometric sensor/device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet, etc.), an entertainment device (e.g., a music device, a video device, a satellite radio, etc.), a vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium. Some UEs may be considered evolved or machine-type communication (MTC) devices or evolved MTC (eMTC) devices. Some UEs may be considered Internet-of Things (IoT) or narrowband IoT (NB-IoT) devices.

OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, subbands, etc. Each subcarrier may be modulated with data. For example, the spacing of the subcarriers may be <NUM> and the minimum resource allocation (called a resource block (RB)) may be <NUM> subcarriers (or <NUM>). Consequently, the nominal FFT size may be equal to <NUM>, <NUM>, <NUM>, <NUM> or <NUM> for system bandwidth of <NUM>, <NUM>, <NUM>, <NUM> or <NUM> megahertz (MHz), respectively. For example, a subband may cover <NUM> (i.e., <NUM> RBs), and there may be <NUM>, <NUM>, <NUM>, <NUM> or <NUM> subbands for system bandwidth of <NUM>, <NUM>, <NUM>, <NUM> or <NUM>, respectively.

NR may utilize OFDM with a CP on the uplink and downlink and include support for half-duplex operation using time division duplex (TDD). A single component carrier bandwidth of <NUM> may be supported. NR resource blocks may span <NUM> sub-carriers with a sub-carrier bandwidth of <NUM> over a <NUM> duration. Each radio frame may consist of <NUM> subframes with a length of <NUM>. Consequently, each subframe may have a length of <NUM>. Each subframe may indicate a link direction (i.e., DL or UL) for data transmission and the link direction for each subframe may be dynamically switched. Each subframe may include DL/UL data as well as DL/UL control data. UL and DL subframes for NR may be as described in more detail below with respect to <FIG>. Alternatively, NR may support a different air interface, other than an OFDM-based. NR networks may include entities such CUs and/or DUs.

In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a BS) allocates resources for communication among some or all devices and equipment within its service area or cell. BSs are not the only entities that may function as a scheduling entity.

The ANC <NUM> may be a central unit (CU) of the distributed RAN <NUM>. The backhaul interface to the next generation core network (NG-CN) <NUM> may terminate at the ANC <NUM>. The backhaul interface to neighboring next generation access nodes (NG-ANs) <NUM> may terminate at the ANC <NUM>. The ANC <NUM> may include one or more TRPs <NUM>. As described above, a TRP may be used interchangeably with "cell".

A TRP <NUM> may include one or more antenna ports.

The logical architecture may support fronthauling solutions across different deployment types. The logical architecture may share features and/or components with LTE. The NG-AN <NUM> may support dual connectivity with NR. The NG-AN <NUM> may share a common fronthaul for LTE and NR. The logical architecture may enable cooperation between and among TRPs <NUM>. An inter-TRP interface may not be present.

The logical architecture may have a dynamic configuration of split logical functions. A BS may include a central unit (CU) (e.g., ANC <NUM>) and/or one or more distributed units (e.g., one or more TRPs <NUM>).

The C-CU <NUM> may be centrally deployed. The C-RU <NUM> may host core network functions locally. A DU <NUM> may host one or more TRPs. The DU <NUM> may be located at edges of the network with radio frequency (RF) functionality.

<FIG> illustrates example components of the BS <NUM> and UE <NUM> illustrated in <FIG>, which may be used to implement aspects of the present disclosure. As described above, the BS may include a TRP. One or more components of the BS <NUM> and UE <NUM> may be used to practice aspects of the present disclosure. For example, antennas <NUM>, Tx/Rx <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the UE <NUM> and/or antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the BS <NUM> may be used to perform the operations described herein.

For a restricted association scenario, the BS <NUM> may be the macro BS 110c in <FIG>, and the UE <NUM> may be the UE 120y. The BS <NUM> may also be a BS of some other type. The BS <NUM> may be equipped with antennas 434a through 434t, and the UE <NUM> may be equipped with antennas 452a through 452r.

The control information may be for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), etc. The data may be for the Physical Downlink Shared Channel (PDSCH), etc. The processor <NUM> may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The processor <NUM> may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signal A transmit (TX) multiple-input multiple-output (MIMO) processor <NUM> may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 432a through 432t. For example, the TX MIMO processor <NUM> may perform certain aspects described herein for RS multiplexing.

For example, MIMO detector <NUM> may provide detected RS transmitted using techniques described herein.

The symbols from the transmit processor <NUM> may be precoded by a TX MIMO processor <NUM> if applicable, further processed by the demodulators 454a through 454r (e.g., for SC-FDM, etc.), and transmitted to the BS <NUM>.

The processor <NUM> and/or other processors and modules at the base station <NUM> may perform or direct, e.g., the execution of the techniques described herein. The processor <NUM> and/or other processors and modules at the UE <NUM> may also perform or direct processes for the techniques described herein. The memories <NUM> and <NUM> may store data and program codes for the BS <NUM> and the UE <NUM>, respectively.

<FIG> is a diagram showing an example of a DL-centric subframe <NUM> (e.g., also referred to as a slot). The DL-centric subframe <NUM> may include a control portion <NUM>. The control portion <NUM> may include various scheduling information and/or control information corresponding to various portions of the DL-centric subframe <NUM>. The DL-centric subframe <NUM> may also include a DL data portion <NUM>. The DL data portion <NUM> may be referred to as the payload of the DL-centric subframe <NUM>.

The DL-centric subframe <NUM> may also include a common UL portion <NUM>. The common UL portion <NUM> may sometimes be referred to as an UL burst, a common UL burst, and/or various other suitable terms. The common UL portion <NUM> may include feedback information corresponding to various other portions of the DL-centric subframe <NUM>. For example, the common UL portion <NUM> may include feedback information corresponding to the control portion <NUM>. Non-limiting examples of feedback information may include an ACK signal, a NACK signal, a HARQ indicator, and/or various other suitable types of information. The common UL portion <NUM> may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests (SRs), and various other suitable types of information. As illustrated in <FIG>, the end of the DL data portion <NUM> may be separated in time from the beginning of the common UL portion <NUM>. This time separation may be referred to as a gap, a guard period, a guard interval, and/or various other suitable terms. One of ordinary skill in the art will understand that the foregoing is merely one example of a DL-centric subframe and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.

<FIG> is a diagram showing an example of an UL-centric subframe <NUM>. The UL-centric subframe <NUM> may include a control portion <NUM>. The control portion <NUM> may exist in the initial or beginning portion of the UL-centric subframe <NUM>. The control portion <NUM> in <FIG> may be similar to the control portion <NUM> described above with reference to <FIG>. The UL-centric subframe <NUM> may also include an UL data portion <NUM>. The UL data portion <NUM> may be referred to as the payload of the UL-centric subframe. 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 PDCCH.

As illustrated in <FIG>, the end of the control portion <NUM> may be separated in time from the beginning of the UL data portion <NUM>. This time separation may be referred to as a gap, guard period, guard interval, and/or various other suitable terms. The UL-centric subframe <NUM> may also include a common UL portion <NUM>. The common UL portion <NUM> in <FIG> may be similar to the common UL portion <NUM> described above with reference to <FIG>. The common UL portion <NUM> may additional or alternative include information pertaining to channel quality indicator (CQI), sounding reference signals (SRSs), and various other suitable types of information. One of ordinary skill in the art will understand that the foregoing is merely one example of an UL-centric subframe and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.

Certain wireless communication system deployments utilize multiple downlink (DL) component carriers (CCs) as part of a carrier aggregation (CA) scheme. For example, in addition to a primary DL CC, one or more supplemental DL (SDL) CCs may be used to enhance date throughput and/or reliability.

As illustrated in <FIG>, for NR, Supplemental UL (SUL) may also be utilized. Supplemental UL may generally refer to an UL CC without a corresponding DL CC in the cell. In other words, SUL may generally refer to the case when there is only UL resource for a carrier from the perspective of an NR device. Aspects of the present disclosure provide techniques that may help support and enable RACH procedures in systems that allow a RACH transmission on either a (primary) UL CC or an SUL CC.

When sending uplink transmissions, such as physical uplink shared channel (PUSCH) transmissions, a UE may need to determine a value of transmit power to apply. The value is typically chosen to be just high enough that a base station can successfully decode the transmission, while mitigating interference to (uplink and/or downlink transmissions of) other UEs.

In some cases, a UE may be configured with a power control configuration involving various parameters to use in an equation the UE uses to determine transmit power for PUSCH, PUCCH, SRS, and PRACH transmissions from the UE. For example, the UE may determine PUSCH transmit power control, according to the following equation: <MAT> involving the following parameters:.

In some cases, for each cell (BWP or bandwidth part), up to <NUM> values alpha and P<NUM> may be configured (e.g., for j=<NUM>, <NUM>,. For each cell/BWP, a number, M, downlink reference signals may be configured to transmit to a UE (e.g., qd = <NUM>, <NUM>,. For each SRS resource set, one DL reference signal is configured per resource (e.g., via RRC configuration).

Unfortunately, a UE may have difficulty obtaining all the necessary parameters to determine uplink transmission power based on the equation above, as there is currently no defined relationship (linkage) between j, qd, and l. As a result, sub-optimal values of parameters for transmit power control may be used. For example, before SRS configuration (such as Msg <NUM>), DL reference signals may be implicitly derived and j may be assumed fixed (e.g., at a value of <NUM>).

Aspects of the present disclosure, however, provide a mechanism that provides and takes advantage of such a linkage. As a result, the techniques presented herein may help achieve improved transmit power control by a UE, which may help improve system performance, mitigate interference to other UEs, and/or help conserve power by the UE.

<FIG> illustrates example of example operations <NUM> for transmit power control in accordance with aspects of the present disclosure. For example, operations <NUM> may be performed by a user equipment (UE) when transmitting PUSCH.

Operations <NUM> begin, at <NUM>, by obtaining at least first and second parameters for determining transmit power for a physical uplink shared channel (PUSCH) transmission. The first parameter may provide an indication of a downlink reference signal (e.g., parameter qd in the equation described above), while the second parameter may provide an indication of a power control process (e.g., parameter l).

At <NUM>, the UE obtain at least a third parameter, based on a relationship between the third parameter and the at least two parameters. The third parameter may be an open-loop power control index (e.g., parameter j) used to obtain a combination of parameter values used to calculate the transmit power.

At <NUM>, the UE transmits the PUSCH, with a transmit power calculated based on the first, second, and third parameters. For example, once obtained, parameter j may be used to find a value for PO_UE_PUSCH,b,f,c(j) in the equation above and used to calculate transmit power for PUSCH.

In some cases (e.g., for grant-based PUSCH), the parameter j in the PUSCH power control configuration may be determined based on the index qd which, in turn, may be derived from a corresponding SRS resource indicator (SRI) value. The SRI value may be indicated in an SRI field in a downlink control information (DCI) transmission. The SRI value may be used to indicate (by the BS) and select (by the UE) multiple SRS resources from configured SRS resource sets. The BS and UE may be configured with a table or mapping of the SRI field to which SRS resource from which SRS resource set is to be used for a multi-panel uplink transmission.

<FIG> illustrates an example mapping of parameters, in accordance with aspects of the present disclosure. As illustrated, there may be mapping from SRI values to values of DL reference signal index qd. As further illustrated, there may also be a mapping/linking of values of qd to values for the open loop power control index j. As illustrated, one or both of the mappings may include at least some one-to-many mapping. Using a mapping, such as that shown in <FIG>, a UE may determine the parameters (qd and j), based on an SRI value provided in a DCI, used to perform transmit power (e.g., for a PUSCH transmission scheduled by the DCI).

As noted above, at least for each SRS resource set for CSI acquisition, a DL reference signal may be configured per resource (e.g., via RRC configuration). This can be done either by explicitly providing the synchronization signal block (SSB) resource index or channel state information reference signal (CSI-RS) resource index or preferably an index for qd, in a PUSCH power control configuration, or both. If only via SSB/CSI-RS resource index, a UE may need to match the SSB index/CSI-RS index in the corresponding PUSCH PC configuration and find a value of qd accordingly. This may happen, for example, if the network configures the corresponding DL reference signal in PUSCH power control configuration after the SRS resource set configuration and before the corresponding PUSCH starts.

In some cases, for each of the up to M DL reference signals in the PUSCH power control configuration, an index j may be configured so as to link each DL reference signal with the corresponding open-loop PC parameter (alpha and P0). Whenever reference signal(s) in the PUSCH PC control configuration (through RRC) is (are) changed, j can be reconfigured (e.g., by providing a revised/updated mapping of values of j to qd and/or SRI values to qd).

For grant-based UL transmission, if multi-beam UL is not supported, a power control processes value (e.g., l=<NUM> or <NUM>) may be configured or fixed (e.g., in a standard specification). In some cases, if multi-beam UL transmission may be supported for grant-based UL transmission, l can be indicated via the following options:.

At least for grant-based PUSCH, a value of the reference signal index qd may be derived from the corresponding SRI value (if present). As noted above, this value of qd may then be linked to an open loop power control index j in the PUSCH power control configuration. As noted above, before SRS configuration, such as Msg3, DL reference signal(s) may be implicitly derived and the value of j may be fixed (e.g., fixed at <NUM>).

For example, various operations shown in <FIG> may be performed by various processors shown in <FIG>. More particularly, operations <NUM> of <FIG> may be performed by one or more of processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the UE <NUM>.

For example, means for transmitting and/or means for receiving may comprise one or more of a transmit processor <NUM>, a TX MIMO processor <NUM>, a receive processor <NUM>, or antenna(s) <NUM> of the base station <NUM> and/or the transmit processor <NUM>, a TX MIMO processor <NUM>, a receive processor <NUM>, or antenna(s) <NUM> of the user equipment <NUM>. Additionally, means for generating, means for multiplexing, and/or means for applying may comprise one or more processors, such as the controller/processor <NUM> of the base station <NUM> and/or the controller/processor <NUM> of the user equipment <NUM>.

Claim 1:
A method for wireless communications by a user equipment, UE, comprising:
obtaining (<NUM>) a first parameter, wherein the first parameter comprises a sounding reference signal (SRS) resource indicator (SRI) value;
obtaining a second parameter comprising an indication of a power control process and an indication of a downlink reference signal index value;
obtaining (<NUM>) a third parameter based at least in part on the first parameter,
wherein the third parameter comprises an open-loop power control index;
determining transmit power for a physical uplink shared channel (PUSCH) transmission based at least in part on the first, second, and third parameters; and
transmitting (<NUM>) the PUSCH, using the transmit power.