Patent Description:
An example telecommunication standard is <NUM> New Radio (NR), which is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT)), and other requirements.

In some wireless communications systems, multiple services may be supported that require different reliability and latency qualities. For example, eMBB services may support a first set of reliability and latency standards, while URLLC services may support a second set of standards with higher reliability and lower latency than the eMBB services. In order to more efficiently utilize a spectrum of time-frequency resources, UEs configured with different services may be dynamically multiplexed on the same time-frequency resources. As such, interference or conflicts may occur between the transmission on the same resources. Efficient techniques are desired for accommodating transmissions on the same resources to ensure both are transmitted and received successfully.

Document <CIT> relates to apparatuses, methods, and systems for transmission power control. One method includes receiving a first configuration indicating a plurality of bandwidth parts on a first serving cell and configuration information corresponding to the plurality of bandwidth parts. The configuration information comprises an open-loop power control configuration, a closed loop power control configuration, or a combination thereof corresponding to each bandwidth part of the plurality of bandwidth parts. The method comprises receiving scheduling information for a first uplink transmission on a first bandwidth part of the plurality of bandwidth parts. The method comprises determining a first transmission power for the first uplink transmission based on the configuration information and the scheduling information. The method comprises performing the first uplink transmission with the first transmission power. Document <CIT> relates to providing methods, apparatuses and computer program for power control. According to one or more embodiments, a method implemented in a terminal device comprises: performing power control for at least a first type of traffic based on a first parameter configuration of a first power control loop; and performing power control for at least a second type of traffic based on a second parameter configuration of a second control loop, wherein the first parameter configuration of the first power control loop includes at least one parameter different from the second parameter configuration of the second power control loop. Document <CIT> relates to systems, apparatuses, and methods for wireless communications. A base station may send, to a wireless device, one or more radio resource control messages comprising power control parameters and/or other wireless resources. The base station may send, to the wireless device, activation or deactivation of channel state information reporting. The wireless device may adjust, based on one or more of the activation or deactivation, at least one value associated with a transmission power of an uplink channel transmission.

The claimed invention is defined by the independent claims. Further embodiments of the claimed invention are described in the dependent claims. The systems, methods and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

The subject matter described in this disclosure is implemented as a method of wireless communication. The method is performed by a wireless communication device, and includes transmitting, to a first wireless device, scheduling information indicating first, second, and third open-loop power levels associated with uplink transmissions on a first wireless channel; selecting one of the first, second, or third open-loop power levels to be used for a first uplink transmission by the first wireless device based at least in part on a type of service associated with the first uplink transmission; transmitting, to the first wireless device, open-loop power control information indicating the selected open-loop power level; and receiving the first uplink transmission on the first wireless channel based on the selected open-loop power level. The selected open-loop power level represents a power of the first uplink transmission to be received by the wireless communication device. In some implementations, the first wireless channel is a physical uplink shared channel (PUSCH).

In some implementations, the type of service is an enhanced mobile broadband (eMBB) service type or an ultra-reliable low-latency communication (URLLC) service type. In some implementations, the first open-loop power level is associated with the eMBB service type, the second open-loop power level is a base open-loop power level associated with the URLLC service type, and the third open-loop power level is a boosted open-loop power level associated with the URLLC service type. In some implementations, the second open-loop power level is higher than the first open-loop power level, and the third open-loop power level is higher than the second open-loop power level.

In some implementations, the selecting of one of the first, second, or third open-loop power levels includes determining that the first uplink transmission is associated with the URLLC service type; determining whether the first uplink transmission is scheduled to overlap with uplink transmissions from other wireless devices on the first wireless channel; and selecting the second open-loop power level or the third open-loop power level based on whether the first uplink transmission is scheduled to overlap with uplink transmissions from other wireless devices. In some aspects, the second open-loop power level is selected responsive to determining that no uplink transmissions by other wireless devices are scheduled to overlap with the first uplink transmission. In some other aspects, the third open-loop power level is selected responsive to determining that a second uplink transmission by a second wireless device is scheduled to overlap with the first uplink transmission. In some implementations, the second uplink transmission is associated with the eMBB service type.

The scheduling information is transmitted in a radio resource control (RRC) message carrying a po-AlphaSets parameter and a Po-PUSCH-Set parameter. The first open-loop power level is indicated by a value of the po-AlphaSets parameter, the second open-loop power level is indicated by a first value of the Po-PUSCH-Set parameter, and the third open-loop power level is indicated by a second value of the Po-PUSCH-Set parameter.

The open loop power control information is transmitted in a downlink control information (DCI) message including at least an open loop power control field. The open loop power control information is indicated by a combination of bits in the open loop power control field.

The subject matter described in this disclosure is implemented in a wireless communication device. The wireless communication device includes one or more processors and a memory coupled to the one or more processors and including instructions that, when executed by the one or more processors, cause the wireless communication device to transmit, to a first wireless device, scheduling information indicating first, second, and third open-loop power levels associated with uplink transmissions on a first wireless channel; select one of the first, second, or third open-loop power levels to be used for a first uplink transmission by the first wireless device based at least in part on a type of service associated with the first uplink transmission; transmit, to the first wireless device, open-loop power control information indicating the selected open-loop power level; and receive the first uplink transmission on the first wireless channel based on the selected open-loop power level.

The subject matter described in this disclosure is implemented as a method of wireless communication. The method is performed by a wireless communication device, and includes receiving scheduling information indicating first, second, and third open-loop power levels associated with uplink transmissions on a first wireless channel; receiving open loop power control information indicating one of the first, second, or third open-loop power levels; determining a transmit power for a first uplink transmission based at least in part on the indicated open-loop power level; and performing the first uplink transmission, on the first wireless channel, at the determined transmit power. In some implementations, the first wireless channel is a PUSCH.

In some implementations, the first open-loop power level is associated with an eMBB service type, the second open-loop power level is a base open-loop power level associated with a URLLC service type, and the third open-loop power level is a boosted open-loop power level associated with the URLLC service type. In some implementations, the second open-loop power level is higher than the first open-loop power level, and the third open-loop power level is higher than the second open-loop power level.

The scheduling information is received in an RRC message carrying a po-AlphaSets parameter and a Po-PUSCH-Set parameter. The first open-loop power level is indicated by a value of the po-AlphaSets parameter, the second open-loop power level is indicated by a first value of the Po-PUSCH-Set parameter, and the third open-loop power level is indicated by a second value of the Po-PUSCH-Set parameter.

The open loop power control information is received in a DCI message including at least an open loop power control field. The open loop power control information is indicated by a combination of bits in the open loop power control field.

The subject matter described in this disclosure is implemented in a wireless communication device. The wireless communication device includes one or more processors and a memory coupled to the one or more processors and including instructions that, when executed by the one or more processors, cause the wireless communication device to receive scheduling information indicating first, second, and third open-loop power levels associated with uplink transmissions on a first wireless channel; receive open loop power control information indicating one of the first, second, or third open-loop power levels; determine a transmit power for a first uplink transmission based at least in part on the indicated open-loop power level; and perform the first uplink transmission, on the first wireless channel, at the determined transmit power.

The following description is directed to some particular implementations for the purposes of describing innovative aspects of this disclosure. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. The described implementations can be implemented in any device, system or network that is capable of transmitting and receiving radio frequency (RF) signals according to one or more of the Long Term Evolution (LTE), <NUM>, <NUM> or <NUM> (New Radio (NR)) standards promulgated by the 3rd Generation Partnership Project (3GPP), the Institute of Electrical and Electronics Engineers (IEEE) <NUM> standards, the IEEE <NUM> standards, or the Bluetooth® standards as defined by the Bluetooth Special Interest Group (SIG), among others. The described implementations can be implemented in any device, system or network that is capable of transmitting and receiving RF signals according to one or more of the following technologies or techniques: code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), single-user (SU) multiple-input multiple-output (MIMO) and multi-user (MU) MIMO. The described implementations also can be implemented using other wireless communication protocols or RF signals suitable for use in one or more of a wireless wide area network (WWAN), a wireless personal area network (WPAN), a wireless local area network (WLAN), or an internet of things (IOT) network.

In some wireless communications systems, multiple services may be supported that require different reliability and latency qualities. For example, enhanced mobile broadband (eMBB) services may support a first set of reliability and latency standards, while ultra-reliable low latency communications (URLLC) services may support a second set of standards with higher reliability and lower latency than the eMBB services. In order to more efficiently utilize a spectrum of time-frequency resources, UEs configured with different services may be dynamically multiplexed (overlap) on the same time-frequency resources. As such, interference or conflicts may occur between the transmission on the same resources.

Various implementations relate generally to transmit power control in wireless communications. Some implementations more specifically relate to using existing signaling techniques to indicate multiple power levels related to different services. In some implementations, an open loop power parameter may be indicated by a base station to a UE using radio resource control (RRC) signaling. In some aspects, an open-loop power level associated with eMBB services may be indicated in an existing RRC parameter (such as p0-AlphaSets, as defined by Rel-<NUM> of the 3GPP standards). In some other aspects, one or more open-loop power levels associated with URLLC services may be indicated in a new RRC parameter (such as PO-PUSCH-Set). In some other implementations, an open loop power parameter may be indicated by a base station to a UE using one or more downlink control information (DCI) messages. For example, the open loop power parameter in the DCI message may indicate a selection of one of the open-loop power levels indicated in the RRC message. In some aspects, each DCI message may include at least one of a priority field or an open-loop power control (OLPC) field. The open-loop power levels associated with eMBB or URLLC services may be indicated based on a combination of bits in the priority field or the OLPC field.

<FIG> shows a diagram of an example wireless communications system and an access network <NUM>.

The base stations <NUM> configured for <NUM> LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC <NUM> through backhaul links <NUM> (e.g., S1 interface). The base stations <NUM> configured for <NUM> NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network <NUM> through backhaul links <NUM>. The base stations <NUM> may communicate directly or indirectly (e.g., through the EPC <NUM> or core network <NUM>) with each other over backhaul links <NUM> (e.g., X2 interface).

Some UEs <NUM> may communicate with each other using device-to-device (D2D) communication link <NUM>.

Some base stations, such as gNB <NUM>, may operate in a traditional sub <NUM> spectrum, in millimeter wave (mmW) frequencies, and/or near mmW frequencies in communication with the UE <NUM>. When the gNB <NUM> operates in mmW or near mmW frequencies, the gNB <NUM> may be referred to as a millimeter wave or mmW base station.

Referring again to <FIG>, in some aspects, the base station <NUM>/<NUM> may indicate an open-loop power level to be used for UL transmissions by one or more UEs <NUM> via RRC signaling or DCI messages (<NUM>). In some implementations, an open-loop power level associated with eMBB services may be indicated in an existing RRC parameter (such as p0-AlphaSets, as defined by Rel-<NUM> of the 3GPP standards). In some other implementations, one or more open-loop power levels associated with URLLC services may be indicated in a new RRC parameter (such as PO-PUSCH-Set). Still further, in some implementations, a selection of one of the open-loop power levels associated with eMBB or URLLC services may be indicated based on a combination of bits in the priority field or the OLPC field of one or more DCI messages.

<FIG> shows an example of a first slot <NUM> within a <NUM>/NR frame structure. <FIG> shows an example of DL channels <NUM> within a <NUM>/NR slot. <FIG> shows an example of a second slot <NUM> within a <NUM>/NR frame structure. <FIG> shows an example of UL channels <NUM> within a <NUM>/NR slot. The <NUM>/NR frame structure may be FDD in which, for a particular set of subcarriers (carrier system bandwidth), slots within the set of subcarriers are dedicated for either DL or UL In other cases, the <NUM>/NR frame structure may be TDD in which, for a particular set of subcarriers (carrier system bandwidth), slots within the set of subcarriers are dedicated for both DL and UL. In the examples shown in <FIG>, the <NUM>/NR frame structure is configured as TDD, with slot <NUM> being configured with slot format <NUM> (with mostly DL), where D indicates DL, U indicates UL, and X indicates that the slot is flexible for use between DL/UL, and slot <NUM> being configured with slot format <NUM> (with mostly UL). While slots <NUM> and <NUM> are shown with slot formats <NUM> and <NUM>, respectively, any particular slot may be configured with any of the various available slot formats <NUM>-<NUM>. Slot formats <NUM> and <NUM> are all DL and all UL, respectively. This format may also apply to a <NUM>/NR frame structure that is FDD.

Accordingly, for slot configuration <NUM> and numerology µ, there are <NUM> symbols/slot and 2µ slots/subframe. The subcarrier spacing may be equal to <NUM>^µ*<NUM> kKz, where µ is the numerology <NUM> to <NUM>. The subcarrier spacing is <NUM> and symbol duration is approximately <NUM>.

Each time slot includes a resource block (RB) (also referred to as a physical RB (PRB)) that extends across <NUM> consecutive subcarriers and across a number of symbols. The intersections of subcarriers and symbols of the RB define multiple resource elements (REs).

As illustrated in <FIG>, some of the REs carry a reference (pilot) signal (RS) for the UE. In some configurations, one or more REs may carry a demodulation RS (DM-RS) (indicated as Rx for one particular configuration, where 100x is the port number, but other DM-RS configurations are possible). In some configurations, one or more REs may carry a channel state information reference signal (CSI-RS) for channel measurement at the UE. The REs may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

The PSS is used by a UE <NUM> to determine subframe or symbol timing and a physical layer identity.

<FIG> shows a block diagram of an example base station <NUM> and UE <NUM> in an access network.

The OFDM stream is spatially pre-coded to produce multiple spatial streams.

Information to be wirelessly communicated (such as for LTE or NR based communications) is encoded and mapped, at the PHY layer, to one or more wireless channels for transmission.

In some wireless communications systems, multiple services may be supported that require different reliability and latency qualities. For example, eMBB services may support a first set of reliability and latency standards, while URLLC services may support a second set of standards with higher reliability and lower latency than the eMBB services. In order to more efficiently utilize a spectrum of time-frequency resources, UEs configured with different services may be dynamically multiplexed on the same time-frequency resources. For example, if urgent uplink URLLC traffic arrives, a base station may need to schedule the URLLC traffic on time-frequency resources partially allocated to one or more eMBB UEs to ensure the URLLC traffic is successfully transmitted by the URLLC UEs. In some aspects, the base station may boost the power of the URLLC traffic to ensure that it is transmitted and received on the overlapping time-frequency resources. For example, the base station may transmit a transmit power control (TPC) command to indicate a power adjustment for all transmissions of one or more UEs.

The TPC for indicating a power adjustment for transmissions by one or more UEs may be part of an enhanced power control (or power boosting) technique employed by the base station and the one or more UEs. For example, based on the enhanced power control, the one or more UEs may boost their respective transmit power for transmitting URLLC traffic to reduce the chances of interference from eMBB traffic, thus ensuring that the URLLC traffic is successfully transmitted to the base station. In some implementations, the enhanced power control may include the base station dynamically indicating an open loop power control parameter for adjusting the transmit power. In some aspects, the open loop power control parameter may indicate at least one of an open-loop power level (or base power level) associated with eMBB services ( <MAT>), a base open-loop power level associated with URLLC services ( <MAT>) or a boosted open-loop power level associated with URLLC services ( <MAT>).

Since URLLC traffic requires higher reliability than eMBB traffic, <MAT> may be higher than <MAT> to achieve the greater reliability. Further, <MAT> may be even higher than <MAT>. <MAT> may be used when the URLLC transmission is scheduled on a resource that overlaps or partially overlaps with another UE's eMBB transmission. In such instances, the URLLC UE may need to transmit at a higher power <MAT> in order to mitigate the interference caused by the concurrent eMBB transmission.

The total transmit power for an uplink message (transmitted on a PUSCH) may be determined according to Equation <NUM>. <MAT> where PC,max represents a maximum transmit power for a UE configured to transmit the uplink message. P<NUM>(j) and α(j) may represent open-loop power control parameters, where P<NUM>(j) = P<NUM>,UE (j) + P<NUM>, nominal (j) and indicates a desired (or required) receive power at the base station for the uplink message and α(j) ≤ <NUM> and indicates a fractional path-loss compensation factor. j may represent an open-loop power control index, where j = <NUM> for a msg3 transmission (as part of a four-step random access channel (RACH) procedure), j = <NUM> for configured grant transmissions, and j = <NUM>. (j - <NUM>) for dynamically scheduled PUSCH transmissions. In some instances, an SRS resource indicator (SRI) may be used to further select between j = <NUM>. (j - <NUM>). Additionally, P<NUM>,UE (j) and a may be dynamically changed. PL(q) may represent a path-loss measured by downlink reference signals, and q may represent a path-loss index. MRB may represent a number of RBs for the PUSCH transmission, and µ may represent a sub-carrier spacing (SCS) for the PUSCH transmission. ΔTF may represent a configured value from the base station for a maximum power reduction (MPR) for the PUSCH transmission. f(l) may represent a closed-loop power control parameter signaled by the base station.

The open-loop power level P<NUM>(j) may be indicated by the base station via one or more signaling techniques. For a dynamic PUSCH, the base station may dynamically signal the open-loop power level P<NUM>(j) via SRI. For a configured grant PUSCH, the base station may signal the open-loop power level P<NUM>(j) via RRC signaling. As described above, the open-loop power level P<NUM>(j) may be one of three possible values <MAT>, or <MAT>. Thus, there is a need to use existing signaling techniques (such as RRC and DCI) to indicate the three open-loop power levels, including which of the three open-loop power levels is to be implemented by a particular UE for a given transmission.

Various implementations relate generally to transmit power control in wireless communications. Some implementations more specifically relate to using existing signaling techniques to indicate multiple power levels related to different services. In some implementations, an open loop power parameter may be indicated by a base station to a UE using RRC signaling. In some aspects, an open-loop power level associated with eMBB services may be indicated in an existing RRC parameter (such as p0-AlphaSets, as defined by Rel-<NUM> of the 3GPP standards). In some other aspects, one or more open-loop power levels associated with URLLC services may be indicated in a new RRC parameter (such as PO-PUSCH-Set). For example, the base open-loop power level associated with URLLC services ( <MAT>) may be indicated by a first value of the PO-PUSCH-Set parameter and the boosted open-loop power level associated with URLLC services ( <MAT>) may be indicated by a second value of the P0-PUSCH-Set parameter.

In some other implementations, an open loop power parameter may be indicated by a base station to a UE using one or more DCI messages. For example, the open loop power parameter in the DCI message may indicate a selection of one of the open-loop power levels indicated in the RRC message. In some aspects, each DCI message may include at least one of a priority field or an open-loop power control (OLPC) field. The open-loop power levels associated with eMBB or URLLC services may be indicated based on a combination of bits in the priority field or the OLPC field. For example, a first bit pattern may represent the open-loop power level associated with eMBB services ( <MAT>), a second bit pattern may represent the base open-loop power level associated with URLLC services ( <MAT>), and a third bit pattern may represent the boosted open-loop power level associated with URLLC services ( <MAT>).

<FIG> shows a sequence diagram illustrating an example message exchange <NUM> between a base station <NUM> and a UE <NUM> according to some implementations. In some implementations, the base station <NUM> may be one example of the base station <NUM> of <FIG>, the UE <NUM> may be one example of the UE <NUM> of <FIG>, and the access network may be a <NUM> NR access network. The base station <NUM> may be any suitable base station or node including, for example, a gNB or an eNB. Although not shown, for simplicity, the base station <NUM> may include a multitude of antennas that can be configured to wirelessly transmit or receive information on a plurality of different beams, for example, to facilitate MIMO communications and beamforming.

The base station <NUM> determines an open loop power configuration for the UE <NUM>. In some implementations, the open loop power configuration may include at least an open-loop power level (or base power level) associated with eMBB services ( <MAT>) a base open-loop power level associated with URLLC services ( <MAT>), and a boosted open-loop power level associated with URLLC services ( <MAT>). In some aspects, the base station <NUM> may determine the open loop power configuration for the UE <NUM> based at least in part on one or more services (such as eMBB or URLLC) supported by the UE <NUM>. In some other aspects, the base station <NUM> may determine the open loop power configuration for the UE <NUM> based at least in part on one or more services associated with other UEs in communication with the base station <NUM>.

In some implementations, the base station <NUM> may signal the open loop power configuration to the UE <NUM> via an RRC configuration message. In some aspects, the open-loop power level associated with eMBB services <MAT> may be configured in an existing RRC parameter (such as p0-AlphaSets, as defined by Rel-<NUM> of the 3GPP standards). In some other aspects, the open-loop power levels associated with URLLC <MAT> and <MAT> may be configured in a new RRC parameter (such as PO-PUSCH-Set). For example, the base open-loop power level associated with URLLC services ( <MAT>) may be indicated by a first value of the PO-PUSCH-Set parameter and the boosted open-loop power level associated with URLLC services ( <MAT>) may be indicated by a second value of the PO-PUSCH-Set parameter.

In some aspects, the base station <NUM> may also transmit one or more Downlink Control Information (DCI) messages to the UE <NUM>. The DCI messages may contain a number of parameters, configurations, schedules, and/or characteristics of one or more DL/UL channels or beams upon which the base station <NUM> can transmit DL/UL data and control information to the UE <NUM>. The DCI messages may also activate and release one or more SPS configurations and/or one or more CG configurations.

The UE <NUM> may receive the RRC and DCI messages from the base station <NUM> and determine a power level for UL transmissions based, at least in part, on the open-loop power configuration provided in the RRC message. For example, the UE <NUM> may analyze the p0-AlphaSets or PO-PUSCH-Set parameters to determine the open-loop power level associated with eMBB services <MAT>, the base open-loop base power level associated with URLLC services <MAT>, and the boosted open-loop boosted power level associated with URLLC services <MAT>. The UE <NUM> may calculate the total transmit power for uplink transmissions (PPUSCH) by applying one of the open-loop power levels to Equation <NUM>. The UE <NUM> may then initiate UL transmissions to the base station <NUM> (via a PUSCH) using the calculated transmit power.

The base station <NUM> determines an open loop power configuration for the UE <NUM>. In some implementations, the open loop power configuration may indicate a selection of an open-loop power level (or base power level) associated with eMBB services ( <MAT>), a base open-loop power level associated with URLLC services ( <MAT>), or a boosted open-loop power level associated with URLLC services ( <MAT>). In some aspects, the base station <NUM> may determine the open loop power configuration for the UE <NUM> based at least in part on a service (such as eMBB or URLLC) associated with UL transmissions by the UE <NUM> on a set of time-frequency resources (such as a PUSCH). In some other aspects, the base station <NUM> may determine the open loop power configuration for the UE <NUM> based at least in part on whether other UEs are configured to share the set of time-frequency resources with the UE <NUM>.

In some implementations, the base station <NUM> may signal the open loop power configuration to the UE <NUM> via one or more DCI messages. In some aspects, the DCI format (such as DCI 0_1 or DCI 0_2) may include at least a priority field or an open-loop power control (OLPC) field. The open loop power configuration may be signaled by a combination of bits in the priority field or the OLPC field. For example, the priority field may be a <NUM>-bit field indicating whether the PUSCH transmission scheduled by the DCI message is associated with low priority or high priority. In some implementations, a low-priority indication in the priority field may be associated with eMBB open-loop power levels <MAT> and a high-priority indication in the priority field may be associated with URLLC open-loop power levels <MAT> and <MAT>. The OLPC field may be a <NUM>-bit field that can be used to further distinguish between the base open-loop power level <MAT> and the boosted open-loop power level <MAT> associated with URLLC services. However, the open-loop power level (or base power level) associated with eMBB services may be signaled by a low-priority indication in the priority field regardless of the OLPC field. Example bit combinations associated with the various open loop power levels is summarized in Table <NUM>.

The base station <NUM> may also transmit an RRC configuration message to the UE <NUM>. The RRC configuration message may facilitate connection establishment and release functions, broadcast of system information, radio bearer establishment, reconfiguration and release operations, RRC connection mobility procedures, paging notification, and power control. The RRC may also configure user and control planes, define multiple downlink semi-persistent scheduling (SPS) configurations, define multiple uplink configured grant (CG) configurations, and control various other functions of the access network.

The UE <NUM> may receive the RRC and DCI messages from the base station <NUM> and determine a power level for UL transmissions based, at least in part, on the open loop power level indication provided in the RRC configuration. For example, the UE <NUM> may analyze the combination of bits in the priority or OLPC fields of the received DCI message to determine whether to use the open-loop power level associated with eMBB services , the base open-loop power level associated with URLLC services <MAT>, or the boosted open-loop power level associated with URLLC services <MAT>. The UE <NUM> may calculate the total transmit power for uplink transmissions (PPUSCH) by applying the determined open-loop power level to Equation <NUM>. The UE <NUM> may then initiate UL transmissions to the base station <NUM> on the scheduled time-frequency resources (or PUSCH) using the calculated transmit power.

In some implementations, where the priority field is not configured in the DCI message, the UE <NUM> may determine the priority of PUSCH transmission scheduled by the DCI message based on the priority of the DCI format. For example, RRC signaling may indicate that the DCI format 0_1 is associated with a low priority whereas the DCI format 0_2 is associated with a high priority. In some instances, where both DCI format 0_1 and DCI format 0_2 are configured to the UE <NUM>, (UE <NUM> is configured to monitor both DCI format 0_1 and DCI format 0_2), the OLPC field may only be configured in DCI format 0_2 (and not DCI format 0_1), since DCI format 0_1 is associated with a low priority channel. Accordingly, the UE may determine the open loop power control parameter based on the priority of the DCI format (in lieu of the priority of the PUSCH) and the bit value of the OLPC field (such as described with respect to Table <NUM>). In some other implementations, where the OLPC field is not configured in the DCI, the UE may simply use the open loop power level associated with eMBB services <MAT> as its open-loop power level.

The base station <NUM> determines a number of open-loop power levels to be used for uplink transmissions on a particular wireless channel (such as a PUSCH). In some implementations, the open-loop power levels may include at least an open-loop power level (or base power level) associated with eMBB services ( <MAT>), a base open-loop power level associated with URLLC services ( <MAT>), and a boosted open-loop power level associated with URLLC services ( <MAT>). In some aspects, the base station <NUM> may determine the open-loop power levels based at least in part on one or more services (such as eMBB or URLLC) supported by the UE <NUM>. In some other aspects, the base station <NUM> may determine the open-loop power levels based at least in part on one or more services associated with other UEs in communication with the base station <NUM>.

In some implementations, the base station <NUM> may indicate the open-loop power levels to the UE <NUM> by transmitting an RRC configuration message including a p0-AlphaSets parameter and a PO-PUSCH-Set parameter. For example, the open-loop power level associated with eMBB services <MAT> may be indicated by a value of the p0-AlphaSets, the base open-loop power level associated with URLLC services ( <MAT>) may be indicated by a first value of the PO-PUSCH-Set parameter, and the boosted open-loop power level associated with URLLC services ( <MAT>) may be indicated by a second value of the PO-PUSCH-Set parameter.

The base station <NUM> may further select one of the open-loop power levels <MAT>, or <MAT> to be used for an uplink transmission (UL TX) by the UE <NUM> on the associated wireless channel. In some implementations, the base station <NUM> may select the open-loop power level based on the service associated with the UL transmission. For example, the base station <NUM> may select the open-loop power level associated with eMBB services if the UL TX is associated with the eMBB service. On the other hand, the base station <NUM> may select one of the open-loop power levels associated with URLLC services if the UL TX is associated with the URLLC service.

In some other implementations, the base station <NUM> may select the open-loop power level based on whether uplink transmissions by other UEs are scheduled to be multiplexed (or transmitted concurrently) with the UL TX by the UE <NUM> on the same wireless channel. For example, the base station <NUM> may select the base open-loop power level associated with URLLC services if no other uplink transmissions are scheduled to be multiplexed with the UL TX. On the other hand, the base station <NUM> may select the boosted open-loop power level associated with URLLC services if an uplink transmission (associated with eMBB services) from at least one other UE is scheduled to be multiplexed with the UL TX.

In some implementations, the base station <NUM> may indicate the selected open-loop power level to the UE <NUM> by transmitting a DCI message including at least a priority field or an OLPC field. More specifically, the selected open-loop power level may be indicated by a combination of bits (such as at least <NUM> bits) in the priority field or the OLPC field of the DCI message. For example, a first bit pattern may represent the open-loop power level associated with eMBB services ( <MAT>), a second bit pattern may represent the base open-loop power level associated with URLLC services ( <MAT>) and a third bit pattern may represent the boosted open-loop power level associated with URLLC services ( <MAT>).

The UE <NUM> may receive the RRC and DCI messages from the base station <NUM> and determine a power level for the UL TX based on the information in the received RRC and DCI messages. For example, the UE <NUM> may determine the selected open-loop power level (such as <MAT>, or <MAT>) based on the information carried in the priority field or the OLPC field of the received DCI message. The UE <NUM> may further determine the value of the selected open-loop power level <MAT>, or <MAT> based on a value of the p0-AlphaSets or the P0-PUSCH-Set parameter in the received RRC message. The UE <NUM> may calculate the total transmit power for the UL TX (PPUSCH) by applying the value of the selected open-loop power level to Equation <NUM>. The UE <NUM> may then perform the UL TX, on the wireless channel (or PUSCH), using the calculated transmit power.

<FIG> shows a sequence diagram illustrating an example message exchange <NUM> between a base station <NUM> and multiple UEs <NUM> and <NUM> according to some implementations. In some implementations, the base station <NUM> may be one example of the base station <NUM> of <FIG>, the UEs <NUM> and <NUM> may be examples of the UE <NUM> of <FIG>, and the access network may be a <NUM> NR access network. The base station <NUM> may be any suitable base station or node including, for example, a gNB or an eNB. Although not shown, for simplicity, the base station <NUM> may include a multitude of antennas that can be configured to wirelessly transmit or receive information on a plurality of different beams, for example, to facilitate MIMO communications and beamforming.

The base station <NUM> determines a number of open-loop power levels to be used for uplink transmissions on a particular wireless channel (such as a PUSCH). In some implementations, the open-loop power levels may include at least an open-loop power level (or base power level) associated with eMBB services ( <MAT>), a base open-loop power level associated with URLLC services ( <MAT>), and a boosted open-loop power level associated with URLLC services ( <MAT>). In some aspects, the base station <NUM> may determine the open-loop power levels based at least in part on one or more services (such as eMBB or URLLC) supported by the first UE <NUM> or the second UE <NUM>.

In some implementations, the base station <NUM> may indicate the open-loop power levels to the first UE <NUM> by transmitting an RRC configuration message including a p0-AlphaSets parameter and a P0-PUSCH-Set parameter. For example, the open-loop power level associated with eMBB services <MAT> may be indicated by a value of the p0-AlphaSets, the base open-loop power level associated with URLLC services ( <MAT>) may be indicated by a first value of the P0-PUSCH-Set parameter, and the boosted open-loop power level associated with URLLC services ( <MAT>) may be indicated by a second value of the P0-PUSCH-Set parameter.

The base station <NUM> may further select one of the open-loop power levels <MAT>, or <MAT> to be used for an uplink transmission (UL TX1) by the first UE <NUM> on the associated wireless channel. In some implementations, the base station <NUM> may select the open-loop power level based on the service associated with UL TX1. In some other implementations, the base station <NUM> may select the open-loop power level based on whether an uplink transmission (UL TX2) by the second UE <NUM> is scheduled to be multiplexed (or transmitted concurrently) with UL TX1 on the same wireless channel.

In the example of <FIG>, UL TX1 is associated with a URLLC service and UL TX2 is associated with an eMBB service. In some implementations, UL TX1 and UL TX2 may be scheduled to be transmitted at different times or on different wireless channels. In such implementations, the base station <NUM> may select the base open-loop power level associated with URLLC services ( <MAT>) for the first UE <NUM>. In some other implementations, UL TX1 and UL TX2 may be scheduled to be transmitted concurrently on the same (or overlapping) wireless channel. In such implementations, the base station may select the boosted open-loop power level associated with URLLC services ( <MAT>) for the first UE <NUM>.

In some implementations, the base station <NUM> may indicate the selected open-loop power level to the UE <NUM> by transmitting a DCI message including at least a priority field or an OLPC field. The selected open-loop power level may be indicated by a combination of bits in the priority field or the OLPC field of the DCI message. For example, the DCI message may include a first bit pattern representing the base open-loop power level associated with URLLC services or a second bit pattern representing the boosted open-loop power level associated with URLLC services based on whether UL TX1 and UL TX2 are multiplexed on the same wireless channel.

The first UE <NUM> may receive the RRC and DCI messages from the base station <NUM> and determine a power level for UL TX1 based on the information in the received RRC and DCI messages. For example, the first UE <NUM> may determine the selected open-loop power level (such as <MAT> or <MAT>) based on the information carried in the priority field or the OLPC field of the received DCI message. The first UE <NUM> may further determine the value of the selected open-loop power level <MAT> or <MAT> based on a value of the PO-PUSCH-Set parameter in the received RRC message. The first UE <NUM> may calculate the total transmit power for UL TX1 (PPUSCH) by applying the value of the selected open-loop power level to Equation <NUM>. The first UE <NUM> may then perform UL TX1, on the associated wireless channel (or PUSCH), using the calculated transmit power.

In some implementations, the base station <NUM> also may transmit an RRC message indicating the open-loop power levels <MAT>, and <MAT> to the second UE <NUM>. The base station <NUM> may further transmit a DCI message indicating a selection of the open-loop power level associated with eMBB services ( <MAT>). The second UE <NUM> may receive the RRC and DCI messages from the base station <NUM> and determine a power level for UL TX2 based on the information in the received RRC and DCI messages. For example, the second UE <NUM> may determine the selected open-loop power level <MAT> based on the information carried in the priority field or the OLPC field of the received DCI message. The second UE <NUM> may further determine the value of the selected open-loop power level <MAT> based on a value of the p0-AlphaSets parameter in the received RRC message. The second UE <NUM> may calculate the total transmit power for UL TX2 (in accordance with Equation <NUM>) and perform UL TX2, on the associated wireless channel (or PUSCH), using the calculated transmit power.

<FIG> shows a flowchart illustrating an example process <NUM> for wireless communication that supports power control indication for multiple services according to some implementations. In some implementations, the process <NUM> may be performed by a wireless communication device operating as or within a network node, such as one of the base stations <NUM> or <NUM> described above with reference to <FIG> and <FIG>, respectively.

In some implementations, the process <NUM> begins in block <NUM> with transmitting, to a first wireless device, scheduling information indicating first, second, and third open-loop power levels associated with uplink transmissions on a first wireless channel. In some implementations, the scheduling information is transmitted in an RRC message carrying a p0-AlphaSets parameter and a PO-PUSCH-Set parameter. In some implementations, the first open-loop power level is indicated by a value of the p0-AlphaSets parameter, the second open-loop power level is indicated by a first value of the PO-PUSCH-Set parameter, and the third open-loop power level is indicated by a second value of the PO-PUSCH-Set parameter.

In block <NUM>, the process <NUM> proceeds with selecting one of the first, second, or third open-loop power levels to be used for a first uplink transmission by the first wireless device based at least in part on a type of service associated with the first uplink transmission. For example, the selected open-loop power level may represent a power of the first uplink transmission received by the wireless communication device. In some implementations, the type of service may include an eMBB service type or a URLLC service type. In some implementations, the first open-loop power level may be associated with the eMBB service type, the second open-loop power level may be a base open-loop power level associated with the URLLC service type, and the third open-loop power level may be a boosted open-loop power level associated with the URLLC service type. In some implementations, the second open-loop power level may be higher than the first open-loop power level, and the third open-loop power level may be higher than the second open-loop power level.

In block <NUM>, the process <NUM> proceeds with transmitting, to the first wireless device, open-loop power control information indicating the selected open-loop power level. In some implementations, the open loop power control information may be transmitted in a DCI message including at least one of a priority field or an open loop power control field. In some implementations, the open loop power control information may be indicated by a combination of bits in the priority field or the open loop power control field. In block <NUM>, the process <NUM> proceeds with receiving the first uplink transmission on the first wireless channel based on the selected open-loop power level.

With reference for example to <FIG>, the process <NUM> may be a more detailed implementation of the open-loop power level selection operation described in block <NUM> of the process <NUM>. For example, the process <NUM> may begin, in block <NUM>, after the transmission of the scheduling information to the first wireless device in block <NUM>, and before the transmission of the open loop power control information to the first wireless device in block <NUM>.

In block <NUM>, the process <NUM> proceeds with determining that the first uplink transmission is associated with the URLLC service type. In block <NUM>, the process <NUM> proceeds with determining whether the first uplink transmission is scheduled to overlap with uplink transmissions from other wireless devices on the first wireless channel. In block <NUM>, the process <NUM> proceeds with selecting the second open-loop power level or the third open-loop power level based on whether the first uplink transmission is scheduled to overlap with uplink transmissions from other wireless devices.

In some aspects, the second open-loop power level may be selected responsive to determining that no uplink transmissions by other wireless devices are scheduled to overlap with the first uplink transmission. In some other aspects, the third open-loop power level may be selected responsive to determining that a second uplink transmission by a second wireless device is scheduled to overlap with the first uplink transmission. In some implementations, the second uplink transmission may be associated with the eMBB service type.

In some implementations, the process <NUM> begins in block <NUM> with receiving scheduling information indicating first, second, and third open-loop power levels associated with uplink transmissions on a first wireless channel. In some implementations, the scheduling information is received in an RRC message carrying a p0-AlphaSets parameter and a PO-PUSCH-Set parameter. In some implementations, the first open-loop power level is indicated by a value of the p0-AlphaSets parameter, the second open-loop power level is indicated by a first value of the PO-PUSCH-Set parameter, and the third open-loop power level is indicated by a second value of the P0-PUSCH-Set parameter.

In block <NUM>, the process <NUM> proceeds with receiving open loop power control information indicating one of the first, second, or third open-loop power levels. In some implementations, the open loop power control information may be received in a DCI message including at least one of a priority field or an open loop power control field. In some implementations, the open loop power control information may be indicated by a combination of bits in the priority field or the open loop power control field.

In block <NUM>, the process <NUM> proceeds with determining a transmit power for a first uplink transmission based at least in part on the indicated open-loop power level. In block <NUM>, the process <NUM> proceeds with performing the first uplink transmission, on the first wireless channel, at the determined transmit power. In some implementations, the first open-loop power level may be associated with an eMBB service type, the second open-loop power level may be a base open-loop power level associated with a URLLC service type, and the third open-loop power level is a boosted open-loop power level associated with the URLLC service type. In some implementations, the second open-loop power level may be higher than the first open-loop power level, and the third open-loop power level may be higher than the second open-loop power level.

<FIG> shows a block diagram of an example wireless communication device <NUM> according to some implementations. In some implementations, the wireless communication device <NUM> is configured to perform any of the processes <NUM> or <NUM> described above with reference to <FIG> and <FIG>, respectively. The wireless communication device <NUM> can be an example implementation of any of the base stations <NUM> or <NUM> described above with reference to <FIG> and <FIG>, respectively. For example, the wireless communication device <NUM> can be a chip, SoC, chipset, package or device that includes at least one processor and at least one modem (for example, a Wi-Fi (IEEE <NUM>) modem or a cellular modem).

The wireless communication device <NUM> includes a reception component <NUM>, a communication manager <NUM>, and a transmission component <NUM>. The communication manager <NUM> further includes an open-loop (OL) power level configuration component <NUM> and an OL power level selection component <NUM>. Portions of one or more of the components <NUM> and <NUM> may be implemented at least in part in hardware or firmware. In some implementations, at least some of the components <NUM> or <NUM> are implemented at least in part as software stored in a memory (such as the memory <NUM>). For example, portions of one or more of the components <NUM> and <NUM> can be implemented as non-transitory instructions (or "code") executable by a processor (such as the controller/processor <NUM>) to perform the functions or operations of the respective component.

The reception component <NUM> is configured to receive RX signals representing UL transmissions from other wireless devices. The transmission component <NUM> is configured to transmit TX signals representing DL transmissions to other wireless devices. In some implementations, the TX signals may carry scheduling information indicating first, second, and third open-loop power levels associated with uplink transmissions on a first wireless channel. The communication manager <NUM> is configured to manage communications between the wireless communication device <NUM> and one or more other wireless devices. In some implementations, the OL power level configuration component <NUM> may determine the first, second, and third open-loop power levels; and the OL power level selection component <NUM> may select one of the first, second, or third open-loop power levels to be used for a first uplink transmission by a first wireless device based at least in part on a type of service associated with the first uplink transmission. In some implementations, the selected open-loop power level may be indicated in TX signals transmitted to the first wireless device.

<FIG> shows a block diagram of an example wireless communication device <NUM> according to some implementations. In some implementations, the wireless communication device <NUM> is configured to perform the processes <NUM> described above with reference to <FIG>. The wireless communication device <NUM> can be an example implementation of any of the UEs <NUM> or <NUM> described above with reference to <FIG> and <FIG>, respectively. For example, the wireless communication device <NUM> can be a chip, SoC, chipset, package or device that includes at least one processor and at least one modem (for example, a Wi-Fi (IEEE <NUM>) modem or a cellular modem).

The wireless communication device <NUM> includes a reception component <NUM>, a communication manager <NUM>, and a transmission component <NUM>. The communication manager <NUM> further includes an open-loop (OL) power level determination component <NUM> and an uplink (UL) transmit (TX) power determination component <NUM>. Portions of one or more of the components <NUM> and <NUM> may be implemented at least in part in hardware or firmware. In some implementations, at least some of the components <NUM> or <NUM> are implemented at least in part as software stored in a memory (such as the memory <NUM>). For example, portions of one or more of the components <NUM> and <NUM> can be implemented as non-transitory instructions (or "code") executable by a processor (such as the controller/processor <NUM>) to perform the functions or operations of the respective component.

The reception component <NUM> is configured to receive RX signals representing DL transmissions from a base station. In some implementations, the RX signals may carry scheduling information indicating first, second, and third open-loop power levels associated with uplink transmissions on a first wireless channel. In some other implementations, the RX signals may carry open loop power control information indicating one of the first, second, or third open-loop power levels. The transmission component <NUM> is configured to transmit TX signals representing UL transmissions to the base station. The communication manager <NUM> is configured to manage communications between the wireless communication device <NUM> and the base station. In some implementations, the OL power level determination component <NUM> may determine an open-loop power level associated with a first uplink transmission based on the scheduling information and the open loop power control information in the received RRC and DCI messages, respectively; and the UL TX power determination component <NUM> may determine a transmit power for the first uplink transmission based at least in part on the determined open-loop power level. In some implementations, the TX signals, including the first uplink transmission, may be transmitted at the determined transmit power.

As used herein, a phrase referring to "at least one of" or "one or more of" a list of items refers to any combination of those items, including single members. For example, "at least one of: a, b, or c" is intended to cover the possibilities of: a only, b only, c only, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a and b and c.

Various modifications to the implementations described in this disclosure may be readily apparent to persons having ordinary skill in the art, and the generic principles defined herein may be applied to other implementations without departing from the scope of this disclosure. Thus, the claims are not intended to be limited to the implementations shown herein, but are to be accorded the widest scope consistent with this disclosure, the principles and the novel features disclosed herein.

Additionally, various features that are described in this specification in the context of separate implementations also can be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation also can be implemented in multiple implementations separately or in any suitable subcombination. As such, although features may be described above as acting in particular combinations, and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Claim 1:
A method of wireless communication performed by a base station, comprising:
transmitting (<NUM>), to a first user equipment, UE, scheduling information indicating first, second, and third open-loop power levels associated with uplink transmissions on a first wireless channel, wherein the scheduling information is transmitted in a radio resource control, RRC, message carrying a po-AlphaSets parameter and a Po-PUSCH-Set parameter,
wherein the first open-loop power level is indicated by a value of the po-AlphaSets parameter, the second open-loop power level is indicated by a first value of the Po-PUSCH-Set parameter, and the third open-loop power level is indicated by a second value of the Po-PUSCH-Set parameter;
selecting (<NUM>) one of the first, second, or third open-loop power levels to be used for a first uplink transmission by the first UE;
transmitting (<NUM>), to the first UE, open-loop power control information indicating the selected open-loop power level, wherein the open loop power control information is transmitted in a downlink control information, DCI, message including at least an open loop power control field, wherein the open loop power control information is indicated by a combination of bits in the open loop power control field; and
receiving (<NUM>) the first uplink transmission on the first wireless channel based on the selected open-loop power level.