Patent Description:
<CIT> discloses apparatuses, methods, and systems for uplink transmission power allocation. One method includes receiving a configuration of two uplink carriers. The method includes determining whether a configuration parameter corresponding to at least one of a first uplink carrier and a second uplink carrier for a serving cell is configured. The method includes determining whether a total user equipment transmit power for uplink transmissions in a transmission occasion exceeds a maximum user equipment output power, wherein the uplink transmissions comprise a first uplink transmission on the first uplink carrier and a second uplink transmission. The method includes, in response to determining that the total user equipment transmit power for uplink transmissions in the transmission occasion exceeds the maximum user equipment output power, determining a first priority level for the first uplink transmission and a second priority level for the second uplink transmission.

The 3GPP TSG-RAN WG2 Meeting #<NUM> electronic draft R2-<NUM>, 24th February - 6th March <NUM>, relates to design of MIMO DL MAC CE and recommends RAN2 to discuss and adopt the following proposals: Proposal <NUM>: One single new MAC CE should be introduced to support PUCCH spatial relation activation for PUCCH resource or PUCCH resource group. One indication bit is needed in the new MAC CE. Proposal <NUM>: The Rel-<NUM> SP SRS Activation/Deactivation MAC CE should be reused for Rel-<NUM> AP SRS activation/deactivation MAC CE. Proposal <NUM>: The Rel-<NUM> pathloss reference RS for PUSCH MAC CE should support multiple mappings between sri-PUSCH-PowerControlId and PUSCH-PathlossReferenceRS-Id. Proposal <NUM>: The Rel-<NUM> pathloss reference RS for SRS MAC CE should support multiple mappings between pathlossReferenceRS and an SRS resource set. Proposal <NUM>: The cell list indication field should be included in the simultaneous TCI states/spatial relation update for multiple CCs MAC CEs. Proposal <NUM>: Enhance the Rel-<NUM> TCI States Activation/Deactivation for UE-specific PDSCH MAC CE with reinterpretation of P field for Rel-<NUM> TCI States Activation/Deactivation for UE-specific PDSCH MAC CE for multi-PDCCH multi-TRP.

The 3GPP TSG-RAN WG4 RAN4#<NUM> draft R4-<NUM>, Reno, Nevada November 18th - 22nd, <NUM>, relates to applicable timing for pathloss RS activated/updated by MAC-CE.

The scope of protection of the present invention is defined by the independent claims.

Optional variants are defined by the dependent claims.

Without limiting the scope of this disclosure as expressed by the claims, which follow, some features will now be discussed briefly.

Certain aspects provide a method for wireless communication performed by a user equipment (UE), as defined by claim <NUM>.

Certain aspects provide a method for wireless communication performed by a network entity, as defined by claim <NUM>.

Aspects of the present disclosure provide means for, apparatus, processors, and computer programs for performing the methods described herein.

Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for determining an applicable time for a medium access control control element (MAC-CE) based path loss reference signal (PL RS). For example, a user equipment (UE) can be configured with multiple PL RS' by radio resource control (RRC) and one of the PL RS' can be activated or updated by the MAC-CE. For such MAC-CE based PL RS activation, application time (i.e., applicable time) may be determined for the newly activated PL RS power control, such as of one of sounding reference signals (SRS), physical uplink shared channel (PUSCH), or physical uplink control channel (PUCCH). The present disclosure provides methods for determining an applicable time for applying the PL RS update indicated by the MAC-CE based on one or more conditions (e.g., in different scenarios).

In addition, the scope of the disclosure is intended to cover such an apparatus or method, which is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein.

<FIG> illustrates an example wireless communication network <NUM> (e.g., an NR/<NUM> network), in which aspects of the present disclosure may be performed. For example, the wireless network <NUM> may include a UE <NUM> configured to perform operations <NUM> of <FIG> to process PR RS sent from a network entity (performing operations <NUM> of <FIG>).

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 user equipments (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 NodeB (NB) and/or a NodeB subsystem serving this coverage area, depending on the context in which the term is used. In NR systems, the term "cell" and next generation NodeB (gNB), new radio base station (NR BS), <NUM> NB, access point (AP), or transmission reception point (TRP) may be interchangeable. In some examples, the base stations may be interconnected to one another and/or to one or more other base stations or network nodes (not shown) in wireless communication network <NUM> through various types of backhaul interfaces, such as a direct physical connection, a wireless connection, a virtual network, or the like using any suitable transport network.

A RAT may also be referred to as a radio technology, an air interface, etc. A frequency may also be referred to as a carrier, a subcarrier, a frequency channel, a tone, a subband, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs.

In the example shown in <FIG>, a relay station 110r may communicate with the BS 110a and a UE 120r to facilitate communication between the BS 110a and the UE 120r.

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 computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, an appliance, 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, gaming device, reality augmentation device (augmented reality (AR), extended reality (XR), or virtual reality (VR)), or any other suitable device that is configured to communicate via a wireless or wired medium.

Consequently, the nominal Fast Fourier Transfer (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.

In some scenarios, air interface access may be scheduled. For example, a scheduling entity (e.g., a base station (BS), Node B, eNB, gNB, or the like) can allocate resources for communication among some or all devices and equipment within its service area or cell. That is, for scheduled communication, subordinate entities can utilize resources allocated by one or more scheduling entities.

Turning back to <FIG>, this figure illustrates a variety of potential deployments for various deployment scenarios. For example, in <FIG>, a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and/or uplink. Other lines show component to component (e.g., UE to UE) communication options.

For example, for RAN sharing, radio as a service (RaaS), and service specific ANC deployments, TRPs <NUM> may be connected to more than one ANC.

The logical architecture of distributed RAN <NUM> may support various backhauling and fronthauling solutions. This support may occur via and across different deployment types.

<FIG> illustrates example components of BS <NUM> and UE <NUM> (as depicted in <FIG>), which may be used to implement aspects of the present disclosure. For example, antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the UE <NUM> may be used to perform operations <NUM> of <FIG>, while antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of the BS <NUM> may be used to perform operations <NUM> of <FIG>.

The control information may be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid ARQ (automated repeat request, or HARQ) indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC 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.

At the UE <NUM>, antennas 452a through 452r may receive downlink signals from the base station <NUM> and may provide received signals to demodulators (DEMODs) in transceivers 454a through 454r, respectively. Each demodulator <NUM> may condition (e.g., filter, amplify, down convert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector <NUM> may obtain received symbols from all demodulators 454a through 454r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.

At the BS <NUM>, uplink signals from the UE <NUM> may be received by the antennas <NUM>, processed by the modulators <NUM>, detected by a MIMO detector <NUM> if applicable, and further processed by a receive processor <NUM> to obtain decoded data and control information sent by the UE <NUM>.

The controllers/processors <NUM> and <NUM> may direct operations at the base station <NUM> and the UE <NUM>, respectively. The processor <NUM> and/or other processors and modules at the BS <NUM> may perform or direct execution of processes for techniques described herein.

Embodiments discussed herein may include a variety of spacing and timing deployments. For example, in LTE, the basic transmission time interval (TTI) or packet duration is the <NUM> subframe. A subframe contains a variable number of slots (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, slots) depending on the subcarrier spacing.

A mini-slot is a subslot structure (e.g., <NUM>, <NUM>, or <NUM> symbols).

In NR, a synchronization signal (SS) block (SSB) is transmitted. The PSS may provide half-frame timing, and the SS may provide the CP length and frame timing. The PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frame, SS burst set periodicity, system frame number, etc..

As shown in <FIG>, the SS blocks may be organized into SS burst sets to support beam sweeping. As shown, each SSB within a burst set may be transmitted using a different beam, which may help a UE quickly acquire both transmit (Tx) and receive (Rx) beams (particular for mmW applications). A physical cell identity (PCI) may still decoded from the PSS and SSS of the SSB.

Certain deployment scenarios may include one or both NR deployment options. Some may be configured for non-standalone (NSA) and/or standalone (SA) option. A standalone cell may need to broadcast both SSB and remaining minimum system information (RMSI), for example, with SIB1 and SIB2. A non-standalone cell may only need to broadcast SSB, without broadcasting RMSI. In a single carrier in NR, multiple SSBs may be sent in different frequencies, and may include the different types of SSB.

A control resource set (CORESET) for an OFDMA system (e.g., a communications system transmitting PDCCH using OFDMA waveforms) may comprise one or more control resource (e.g., time and frequency resources) sets, configured for conveying PDCCH, within the system bandwidth. Within each CORESET, one or more search spaces (e.g., common search space (CSS), UE-specific search space (USS), etc.) may be defined for a given UE. Search spaces are generally areas or portions where a communication device (e.g., a UE) may look for control information.

According to aspects of the present disclosure, a CORESET is a set of time and frequency domain resources, defined in units of resource element groups (REGs). Each REG may comprise a fixed number (e.g., twelve) tones in one symbol period (e.g., a symbol period of a slot), where one tone in one symbol period is referred to as a resource element (RE). A fixed number of REGs may be included in a control channel element (CCE). Sets of CCEs may be used to transmit new radio PDCCHs (NR-PDCCHs), with different numbers of CCEs in the sets used to transmit NR-PDCCHs using differing aggregation levels. Multiple sets of CCEs may be defined as search spaces for UEs, and thus a NodeB or other base station may transmit an NR-PDCCH to a UE by transmitting the NR-PDCCH in a set of CCEs that is defined as a decoding candidate within a search space for the UE, and the UE may receive the NR-PDCCH by searching in search spaces for the UE and decoding the NR-PDCCH transmitted by the NodeB.

Operating characteristics of a NodeB or other base station in an NR communications system may be dependent on a frequency range (FR) in which the system operates. A frequency range may comprise one or more operating bands (e.g., "n1" band, "n2" band, "n7" band, and "n41" band), and a communications system (e.g., one or more NodeBs and UEs) may operate in one or more operating bands. Frequency ranges and operating bands are described in more detail in "Base Station (BS) radio transmission and reception" TS38. <NUM> (Release <NUM>), which is available from the 3GPP website.

As described above, a CORESET is a set of time and frequency domain resources. The CORESET can be configured for conveying PDCCH within system bandwidth. A UE may determine a CORESET and monitors the CORESET for control channels. During initial access, a UE may identify an initial CORESET (CORESET #<NUM>) configuration from a field (e.g., pdcchConfigSIB1) in a maser information block (MIB). This initial CORESET may then be used to configure the UE (e.g., with other CORESETs and/or bandwidth parts via dedicated (UE-specific) signaling. When the UE detects a control channel in the CORESET, the UE attempts to decode the control channel and communicates with the transmitting BS (e.g., the transmitting cell) according to the control data provided in the control channel (e.g., transmitted via the CORESET).

According to aspects of the present disclosure, when a UE is connected to a cell (or BS), the UE may receive a master information block (MIB). The MIB can be in a synchronization signal and physical broadcast channel (SS/PBCH) block (e.g., in the PBCH of the SS/PBCH block) on a synchronization raster (sync raster). In some scenarios, the sync raster may correspond to an SSB. From the frequency of the sync raster, the UE may determine an operating band of the cell. Based on a cell's operation band, the UE may determine a minimum channel bandwidth and a subcarrier spacing (SCS) of the channel. The UE may then determine an index from the MIB (e.g., four bits in the MIB, conveying an index in a range <NUM>-<NUM>).

Given this index, the UE may look up or locate a CORESET configuration (this initial CORESET configured via the MIB is generally referred to as CORESET #<NUM>). This may be accomplished from one or more tables of CORESET configurations. These configurations (including single table scenarios) may include various subsets of indices indicating valid CORESET configurations for various combinations of minimum channel bandwidth and SCS. In some arrangements, each combination of minimum channel bandwidth and SCS may be mapped to a subset of indices in the table.

Alternatively or additionally, the UE may select a search space CORESET configuration table from several tables of CORESET configurations. These configurations can be based on a minimum channel bandwidth and SCS. The UE may then look up a CORESET configuration (e.g., a Type0-PDCCH search space CORESET configuration) from the selected table, based on the index. After determining the CORESET configuration (e.g., from the single table or the selected table), the UE may then determine the CORESET to be monitored (as mentioned above) based on the location (in time and frequency) of the SS/PBCH block and the CORESET configuration.

<FIG> shows an exemplary transmission resource mapping <NUM>, according to aspects of the present disclosure. In the exemplary mapping, a BS (e.g., BS 110a, shown in <FIG>) transmits an SS/PBCH block <NUM>. The SS/PBCH block includes a MIB conveying an index to a table that relates the time and frequency resources of the CORESET <NUM> to the time and frequency resources of the SS/PBCH block.

The BS may also transmit control signaling. In some scenarios, the BS may also transmit a PDCCH to a UE (e.g., UE <NUM>, shown in <FIG>) in the (time/frequency resources of the) CORESET. The PDCCH may schedule a PDSCH <NUM>. The BS then transmits the PDSCH to the UE. The UE may receive the MIB in the SS/PBCH block, determine the index, look up a CORESET configuration based on the index, and determine the CORESET from the CORESET configuration and the SS/PBCH block. The UE may then monitor the CORESET, decode the PDCCH in the CORESET, and receive the PDSCH that was allocated by the PDCCH.

Different CORESET configurations may have different parameters that define a corresponding CORESET. For example, each configuration may indicate a number of resource blocks (e.g., <NUM>, <NUM>, or <NUM>), a number of symbols (e.g., <NUM>-<NUM>), as well as an offset (e.g., <NUM>-<NUM> RBs) that indicates a location in frequency.

In many cases, it is important for a UE to know which assumptions it can make on a channel corresponding to different transmissions. For example, the UE may need to know which reference signals it can use to estimate the channel in order to decode a transmitted signal (e.g., PDCCH or PDSCH). It may also be important for the UE to be able to report relevant channel state information (CSI) to the BS (gNB) for scheduling, link adaptation, and/or beam management purposes. In NR, the concept of quasi co-location (QCL) and transmission configuration indicator (TCI) states is used to convey information about these assumptions.

QCL assumptions are generally defined in terms of channel properties. Per 3GPP TS <NUM>, "two antenna ports are said to be quasi-co-located if properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed. " Different reference signals may be considered quasi co-located ("QCL'd") if a receiver (e.g., a UE) can apply channel properties determined by detecting a first reference signal to help detect a second reference signal. TCI states generally include configurations such as QCL-relationships, for example, between the DL RSs in one CSI-RS set and the PDSCH DMRS ports.

In some cases, a UE may be configured with up to M TCI-States. Configuration of the M TCI-States can come about via higher layer signalling, while a UE may be signalled to decode PDSCH according to a detected PDCCH with DCI indicating one of the TCI states. Each configured TCI state may include one RS set TCI-RS-SetConfig that indicates different QCL assumptions between certain source and target signals.

<FIG> illustrate examples of the association of DL reference signals with corresponding QCL types that may be indicated by a TCI-RS-SetConfig.

In the examples of <FIG>, a source reference signal (RS) is indicated in the top block and is associated with a target signal indicated in the bottom block. In this context, a target signal generally refers to a signal for which channel properties may be inferred by measuring those channel properties for an associated source signal. As noted above, a UE may use the source RS to determine various channel parameters, depending on the associated QCL type, and use those various channel properties (determined based on the source RS) to process the target signal. A target RS does not necessarily need to be PDSCH's DMRS, rather it can be any other RS: PUSCH DMRS, CSIRS, TRS, and SRS.

As illustrated, each TCI-RS-SetConfig contains parameters. These parameters can, for example, configure quasi co-location relationship(s) between reference signals in the RS set and the DM-RS port group of the PDSCH. The RS set contains a reference to either one or two DL RSs and an associated quasi co-location type (QCL-Type) for each one configured by the higher layer parameter QCL-Type.

As illustrated in <FIG>, for the case of two DL RSs, the QCL types can take on a variety of arrangements. For example, QCL types may not be the same, regardless of whether the references are to the same DL RS or different DL RSs. In the illustrated example, SSB is associated with Type C QCL for P-TRS, while CSI-RS for beam management (CSIRS-BM) is associated with Type D QCL.

QCL information and/or types may in some scenarios depend on or be a function of other information. For example, the quasi co-location (QCL) types indicated to the UE can be based on higher layer parameter QCL-Type and may take one or a combination of the following types:.

Spatial QCL assumptions (QCL-TypeD) may be used to help a UE to select an analog Rx beam (e.g., during beam management procedures). For example, an SSB resource indicator may indicate a same beam for a previous reference signal should be used for a subsequent transmission.

An initial CORESET (e.g., CORESET ID <NUM> or simply CORESET#<NUM>) in NR may be identified during initial access by a UE (e.g., via a field in the MIB). A ControlResourceSet information element (CORESET IE) sent via radio resource control (RRC) signaling may convey information regarding a CORESET configured for a UE. The CORESET IE generally includes a CORESET ID, an indication of frequency domain resources (e.g., number of RBs) assigned to the CORESET, contiguous time duration of the CORESET in a number of symbols, and Transmission Configuration Indicator (TCI) states.

As noted above, a subset of the TCI states provide quasi co-location (QCL) relationships between DL RS(s) in one RS set (e.g., TCI-Set) and PDCCH demodulation RS (DMRS) ports. A particular TCI state for a given UE (e.g., for unicast PDCCH) may be conveyed to the UE by the Medium Access Control (MAC) Control Element (MAC-CE). The particular TCI state is generally selected from the set of TCI states conveyed by the CORESET IE, with the initial CORESET (CORESET#<NUM>) generally configured via MIB.

Search space information may also be provided via RRC signaling. For example, the Search Space IE is another RRC IE that defines how and where to search for PDCCH candidates for a given CORESET. Each search space is associated with one CORESET. The Search Space IE identifies a search space configured for a CORESET by a search space ID. In an aspect, the search space ID associated with CORESET # <NUM> is Search Space ID #<NUM>. The search space is generally configured via PBCH (MIB).

A UE may receive a PL RS from a BS. The UE may measure the PL RS to determine downlink channel quality between the UE and the BS. For example, based on the measurement of the PL RS, the UE may estimate path loss (or path attenuation) between the UE and the BS on the downlink. In certain aspects, the estimated path loss on the downlink may also be applicable to estimated path loss on a corresponding uplink (e.g., when the downlink and uplink have similar channel conditions). For example, the UE also determines estimated path loss on an uplink based on the measured PL RS.

In certain aspects, the PL RS is associated with one or more types of uplink transmission. For example, the BS may transmit a plurality of different PL RS (or PL RS', interchangeable herein), where each PL RS is associated with a particular one or more types of uplink transmission such as one or more of a physical uplink shared channel (PUSCH), a sounding reference signal (SRS), an aperiodic SRS (AP-SRS), a semi-persistent SRS (SP-SRS), a periodic SRS (P-SRS), or a physical uplink control channel (PUCCH). In some cases, the BS may configure the UE with multiple PL RS by radio resource control (RRC) signaling and activate or update one of the multiple PL RS via medium access control control element (MAC-CE) for an SRS set.

In some examples, a second radio access network (RAN) may provide further signaling details. Higher layer filtered reference signal received power (RSRP) may be reused for path loss measurement and used to define an application time in some situations. In one specific example, the next slot after the Nth measurement sample, wherein the first measurement sample corresponds to the first instance, or three milliseconds after sending acknowledgement (ACK) for the MAC-CE, may be used as the application time. In this example, N may be an integer such as five.

Some conditions or assumptions may be apply for the determination of the application time. For example, the determination may assume the UE supports the number of RRC-configurable PL RS greater than a certain number, such as four, for the case that the activated PL RS by the MAC-CE is not tracked. In such cases, the UE may only be required to track the activated PL RS if the number of PL RS configured by RRC is greater than the number. The UE may determine whether to update the filtered RSRP value for the previous PL RS <NUM> after sending ACK for the MAC-CE. An LS may be sent to RAN4 to validate these conditions.

In certain aspects, based on measuring the PL RS and determining estimated path loss between the UE and the BS, the UE is configured to perform uplink power control. For example, in certain aspects the UE is configured to perform uplink power control to adjust a transmission power used by the UE to transmit an uplink transmission of a type associated with the PL RS.

In certain aspects, the PL RS may be associated with a particular beam. For example, the UE and/or the BS may utilize beamforming for transmitting and/or receiving signals. In particular, the UE and/or the BS may utilize receive-side beamforming to perform beamforming when receiving signals, such that signals are received with increased gain (e.g., amplified) in a particular direction and decreased gain (e.g., attenuated) in other directions. Further, the UE and/or the BS may utilize transmit-side beamforming to perform beamforming when transmitting signals, such that signals are transmitted with increased gain (e.g., amplified) in a particular direction and decreased gain (e.g., attenuated) in other directions. A pair of a transmit beam, used by a device to send signals, and a receive beam, used by another device to receive signals, may be referred to as a beam pair or beam pair link. Accordingly, in certain aspects, the estimated path loss by the UE may be for a particular beam pair, a particular transmit beam of the BS, and or a particular receive beam of the UE.

In certain aspects, the UE utilizes or applies the PL RS for taking one or more actions. For example, based on the estimated path loss from measuring the PL RS, the UE may one or more of perform uplink power control, perform a handover from one BS to another, declare a radio link failure (RLF), perform downlink and/or uplink beam management, etc. For example, if the PL RS indicates that path loss between the UE and a BS is high (e.g., above a threshold), the UE may perform uplink power control. In another example, if the PL RS indicates that path loss between the UE and a BS is high, the UE may perform handover from the BS to another BS. In another example, if the PL RS indicates that path loss between the UE and a BS is high for a particular beam pair, the UE and/or BS may perform beam management procedure (e.g., beam selection procedures) to select a new beam pair for communication. In another example, if the PL RS indicates that path loss between the UE and a BS is high, the UE may increase transmit power for transmitting on an uplink or perform other uplink power control.

In certain aspects, a BS is configured to activate a particular PL RS, such as of a plurality of PL RSs transmitted by the BS, for a UE. In particular, in certain such aspects, the UE is configured to track, monitor, and/or measure the particular PL RS when activated. The particular PL RS may be associated with one or more of a particular transmit beam of the BS, a particular receive beam of the UE, or a particular uplink channel/transmission by the UE to the BS. Accordingly, measurement of the particular PL RS when activated may be used to perform an action, as discussed, with respect to a particular transmit beam of the BS, a particular receive beam of the UE, or a particular uplink channel/transmission by the UE to the BS.

Activation of MAC-CE based path loss reference signal (PL RS) application time may be decided for newly activated PL RS for sounding reference signals (SRS) and physical uplink shared channel (PUSCH) power control. In some scenarios, the application time is unspecified for physical uplink control channel (PUCCH). The present disclosure provides methods (e.g., or techniques, also implementable as guidelines or rules) for determining the application time for PUCCH, SRS, or PUSCH to apply PL RS update based on one or more conditions.

Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for determining an applicable time for a MAC-CE based path loss reference signal (PL RS) for PUCCH and other uplink transmissions.

<FIG> illustrates example operations <NUM> for wireless communication by a UE, in accordance with certain aspects of the present disclosure. The operations <NUM> may be performed, for example, by a UE <NUM> of <FIG> and <FIG>.

Operations <NUM> begin, at <NUM>, by receiving a medium access control (MAC) control element (CE) indicating a path loss reference signal (PL RS) update. For example, the UE may receive a MAC-CE updating PUCCH spatial relation.

At <NUM>, the UE determines a time for applying the PL RS update based on one more conditions. For example, as described in different scenarios below, the applicable time for applying the PL RS update may be different for different cases (each correspond to one or more conditions).

<FIG> is a flow diagram illustrating example operations <NUM> for wireless communication by a network entity, and may be considered complementary to operations <NUM> of <FIG>. For example, operations <NUM> may be performed, for example, by a BS <NUM> (e.g., a gNB) of <FIG> and <FIG>, in conjunction with a UE <NUM> performing operations <NUM> of <FIG>.

Operations <NUM> begin, at <NUM>, by sending a UE a medium access control (MAC) control element (CE) indicating a path loss reference signal (PL RS) update.

At <NUM>, the network entity determining a time for the UE to apply the PL RS update based on one more conditions. For example, the time (or applicable time) determined by the network entity is for the UE to apply the PL RS update, when some of the one or more conditions are satisfied.

In certain aspects, the applicable time or application time for MAC-CE based PUCCH PL RS update may depend on the following cases and conditions.

In certain aspects, the one or more conditions relate to at least one of a total configured number of PL RS for the UE, whether a MAC-CE based PL RS activation feature is enabled, or whether a same PL RS is already measured or maintained for power control of one or more other uplink channels.

In certain aspects, the one or more conditions relate to at least one of: if the PL RS has a configured transmission configuration indicator (TCI) state and the TCI state is known by the UE, if the PL RS has no configured TCI state and the PL RS is of a certain type, or if the PL RS has no configured TCI state and the PL RS is known to the UE. For example, the certain type includes at least one of a synchronization signal block (SSB) or a channel state information reference signal (CSI-RS).

In certain aspects, the application time is determined to be a period after acknowledgement of the MAC-CE. For example, the PL RS applicable time may be three milliseconds after the end of an acknowledgment (ACK) by the UE for PDSCH carrying MAC-CE updating PUCCH spatial relation as well as corresponding PL RS, subject to one or more following conditions (as example applications of the one or more conditions mentioned above). <FIG> illustrates an example (Case <NUM>) of the application time being a certain time period after ACK. As shown, the application time between the ACK <NUM> and applying PL RS update at <NUM> equals to the certain timer period, such as <NUM>, after the ACK <NUM>. The certain time period may be defined as another value subject to the conditions below.

For example, one condition may be that the total configured PL RS number is no more than a limit (e.g., where the total configured PL RS limit is four, the total configured PL RS number may not be more than four). The total configured PL RS can be for PUSCH/PUCCH/SRS/physical random access channel (PRACH) power control (PC), or just for PUCCH PC. One condition may be that the MAC-CE based PL RS activation feature is disabled, (e.g., if a corresponding RRC flag enablePLRSupdateForPUSCHSRS is turned off). One condition may be that the same PL RS is already measured and/or maintained for PC of other UL channels, (e.g., PUSCH/SRS/PRACH). Satisfying one or more of these three conditions is sufficient for the applicable time to be three milliseconds after the end of ACK for PDSCH carrying MAC-CE updating PUCCH spatial relation and the corresponding PL RS.

In certain aspects, the application time corresponds to a certain measurement sample of a new PL RS a period after acknowledgement of the MAC-CE. For example, the PL RS applicable time may be after a fifth measurement sample of the new PL RS, where the first measurement sample is the one after three milliseconds from the end of ACK for PDSCH carrying MAC-CE updating PUCCH spatial relation as well as corresponding PL RS, subject to one or more following conditions (as example applications of the one or more conditions mentioned earlier). <FIG> illustrates an example (Case <NUM>) of the application time corresponding to a certain measurement sample of the new PL RS is shown in <FIG>. As shown, the application time between the end of ACK <NUM> and applying the PL RS update at <NUM> equals to the certain time period between the first new PL RS measurement sample and the end of ACK <NUM> and the duration corresponding to Nth PL RS measurement samples.

One condition may be that the total configured PL RS number is no more than a limit (e.g., where the total configured PL RS limit is four, the total configured PL RS number may not be more than four). The total configured PL RS can be for PUSCH/PUCCH/SRS/physical random access channel (PRACH) PC, or just for PUCCH PC (i.e., the PL RS is specified for PC of the PUCCH only). One condition may be that the MAC-CE based PL RS activation feature is enabled, (i.e., corresponding RRC flag enablePLRSupdateForPUSCHSRS is turned on. ) One condition may be that the same PL RS is not measured and/or maintained for PC of other UL channels, (e.g., PUSCH/SRS/PRACH).

One condition may be that the PL RS has a configured TCI state where the TCI state is "known" as described below. One condition may be that the PL RS has no configured TCI state, where such PL RS includes a standardized building block (SSB) and a periodic channel state information resource signal (CSI-RS). One condition may be that the PL RS has no configured TCI state and the PL RS is "known" as described below.

In certain aspects, the PL RS applicable time may be after a specific duration after a certain number of measurement sample (e.g., the fifth measurement sample) of the new PL RS, where a first measurement sample is the measurement after milliseconds from the end of ACK for PDSCH carrying MAC-CE updating PUCCH spatial relation as well as corresponding PL RS, subject to one or more conditions. <FIG> illustrates an example (Case <NUM>) for applying PL RS update is shown in <FIG>, between the end of the ACK <NUM> and applying the PL RS update at <NUM>. As shown, the application time is determined based on a certain time period (e.g., <NUM>) after the end of ACK <NUM>, a certain number (e.g., N = <NUM>) of measurement samples of the new PL RS, and a specific duration thereafter. The specific duration may be TL1-RSRP, as discussed below.

One condition may be that the total configured PL RS number is no more than a limit (e.g., where the total configured PL RS limit is four, the total configured PL RS number may not be more than four). The total configured PL RS can be for PUSCH/PUCCH/SRS/physical random access channel (PRACH) PC, or just for PUCCH PC. One condition may be that the MAC-CE based PL RS activation feature is enabled, (e.g., if a corresponding RRC flag enablePLRSupdateForPUSCHSRS is turned on). One condition may be that the same PL RS is not measured and/or maintained for PC of other UL channels, (e.g., PUSCH/SRS/PRACH. ) One condition may be that the PL RS has a configured TCI state and the TCI state is "unknown. " One condition may be that the PL RS has a configured TCI state where the TCI state is "known. " One condition may be that the PL RS has no configured TCI state and the PL RS is "unknown.

For example, the specific duration can be TL1-RSRP as defined in TS <NUM> section <NUM>. <NUM> for required time for L1-RSRP report. TL1-RSRP is the time for L1-RSRP measurement for Rx beam refinement defined as (<NUM>) TBM_Measurement_Period_SSB for SSB in FR2 as specified in clause <NUM>. <NUM>, with the assumption of M = <NUM>, or (<NUM>) TBM_Measurement_Period_CSI-RS for CSI-RS in FR2 as specified in clause <NUM>. <NUM>, with the assumption of M = <NUM> for periodic CSI-RS or for aperiodic CSI-RS if number of resources in resource set at least equal to MaxNumberRxBeam.

In certain aspects, the same rule of applicable time for MAC-CE based PUCCH PL RS update can also be applied to MAC-CE based PL RS update for other UL channels, including PUSCH/SRS/PRACH.

In certain aspects, the TCI state is considered "known" subject to one or more conditions (or when one or more of the following conditions are satisfied). One condition may be that during the period from the last transmission of the RS resource used for the L1-RSRP measurement reporting for the target TCI state to the completion of active TCI state switch, the RS resource for L1-RSRP measurement is the RS in target TCI state or QCLed to the target TCI state. One condition may be that the TCI state switch command is received within <NUM>,<NUM> milliseconds upon the last transmission of the RS resource for beam reporting or measurement. One condition may be that the UE has sent at least one L1-RSRP report for the target TCI state before the TCI state switch command. One condition may be that the TCI state remains detectable during the TCI state switching period. One condition may be that the SSB associated with the TCI state remain detectable during the TCI switching period (the SNR of the TCI state is greater than or equal to -<NUM> dB). Otherwise, the TCI state is unknown.

In certain aspects, a "known" PL RS can be determined subject to one or more conditions. One condition may be that the UE receives activation command for a PL RS within a previous number of seconds within the last transmission of this PL RS. One condition may be that the UE has sent at least one measurement report for this PL RS. One condition may be that the PL RS and/or its SSB QCL source remain detectable during the PL RS switching period (the SNR of the TCI state is greater than or equal to - <NUM> dB). Otherwise, the PL RS is unknown.

<FIG> illustrates a communications device <NUM> (e.g., a UE) that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations <NUM> illustrated in <FIG>. The communications device <NUM> includes a processing system <NUM> coupled to a transceiver <NUM> (e.g., a transmitter and/or a receiver).

The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium/memory <NUM> via a bus <NUM>. In certain aspects, the computer-readable medium/memory <NUM> is configured to store instructions (e.g., computer-executable code) that when executed by the processor <NUM>, cause the processor <NUM> to perform the operations <NUM> illustrated in <FIG>, or other operations for performing the various techniques discussed herein. In certain aspects, computer-readable medium/memory <NUM> stores code <NUM> for receiving a medium access control (MAC) control element (CE) indicating a path loss reference signal (PL RS) update, and code <NUM> for determining a time for applying the PL RS update based on one more conditions. In certain aspects, the processor <NUM> has circuitry configured to implement the code stored in the computer-readable medium/memory <NUM>. The processor <NUM> includes circuitry <NUM> for receiving a medium access control (MAC) control element (CE) indicating a path loss reference signal (PL RS) update, and circuitry <NUM> for determining a time for applying the PL RS update based on one more conditions.

The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium/memory <NUM> via a bus <NUM>. In certain aspects, the computer-readable medium/memory <NUM> is configured to store instructions (e.g., computer-executable code) that when executed by the processor <NUM>, cause the processor <NUM> to perform the operations <NUM> illustrated in <FIG>, or other operations for performing the various techniques discussed herein. In certain aspects, computer-readable medium/memory <NUM> stores code <NUM> for sending a UE a medium access control (MAC) control element (CE) indicating a path loss reference signal (PL RS) update, and code <NUM> for determining a time for the UE to apply the PL RS update based on one more conditions. In certain aspects, the processor <NUM> has circuitry configured to implement the code stored in the computer-readable medium/memory <NUM>. The processor <NUM> includes circuitry <NUM> for sending a UE a medium access control (MAC) control element (CE) indicating a path loss reference signal (PL RS) update, and circuitry <NUM> for determining a time for the UE to apply the PL RS update based on one more conditions.

Aspect wherein the application time determined for the UE to apply the PL RS update is based on a certain time period after an end of acknowledgement (ACK) for physical downlink shared channel (PDSCH) carrying MAC-CE updating physical uplink control channel (PUCCH) spatial relation and a corresponding PL RS.

Aspect wherein the application time determined for the UE to apply the PL RS update is based on a certain number of measurement samples of a new PL RS, counted from a first measurement sample corresponding to a certain time period after the end of ACK for PDSCH carrying MAC-CE updating PUCCH spatial relation and the corresponding PL RS.

Claim 1:
A method for wireless communication by a user equipment (<NUM>), UE, the method comprising:
receiving (<NUM>), from a network entity (<NUM>), a medium access control control element, MAC-CE, indicating a path loss reference signal, PL RS, update for an uplink channel;
determining whether one or more conditions are satisfied, the one or more conditions include whether a same PL RS is already measured or maintained for power control of one or more other uplink channels; and
determining (<NUM>) an application time for applying the PL RS update based on whether the one more conditions are satisfied.