120 may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit. A UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and/or a satellite radio), a vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and/or any other suitable device that is configured to communicate via a wireless or wired medium.

Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. An MTC UE and/or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and/or a location tag, that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered a Customer Premises Equipment. A UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and/or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.

In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, an air interface, or the like. A frequency may be referred to as a carrier, a frequency channel, or the like. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using a network node 110 as an intermediary to communicate with one another). For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or a mesh network. In such examples, a UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the network node 110.

Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF band.

With the above examples in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and/or FR5) may be modified, and techniques described herein are applicable to those modified frequency ranges.

In some aspects, a UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may transmit, to a network node, a primary cell (PCell) uplink transmission, wherein the PCell uplink transmission is associated with a transmit power control (TPC) adjustment value; and transmit, to the network node, a secondary cell (SCell) sounding reference signal (SRS) transmission based at least in part on a carrier switching from a PCell to an SCell, wherein the TPC adjustment value associated with the PCell uplink transmission is applied to the SCell SRS transmission based at least in part on a condition being satisfied. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive, from a UE, a PCell uplink transmission, wherein the PCell uplink transmission is associated with a TPC adjustment value; and receive, from the UE, an SCell SRS transmission based at least in part on a carrier switching from a PCell to an SCell, wherein the TPC adjustment value associated with the PCell uplink transmission is applied to the SCell SRS transmission based at least in part on a condition being satisfied. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.

As indicated above, FIG. 1 is provided as an example. Other examples may differ from what is described with regard to FIG. 1.

FIG. 2 is a diagram illustrating an example 200 of a network node 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 254. In some examples, a network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs, or one or more DUs.

At the network node 110, a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120). The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MC S(s) selected for the UE 120 and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a through 232t. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232. Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas), shown as antennas 234a through 234t.

At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive the downlink signals from the network node 110 and/or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems), shown as modems 254a through 254r. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller/processor 280. The term “controller/processor” may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and/or a CQI parameter, among other examples. In some examples, one or more components of the UE 120 may be included in a housing 284.

The network controller 130 may include a communication unit 294, a controller/processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

One or more antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252r) may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and/or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of FIG. 2.

On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from the controller/processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modems 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and/or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller/processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to FIGS. 4-8).

At the network node 110, the uplink signals from UE 120 and/or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232), detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to the controller/processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of the antenna(s) 234, the modem(s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and/or the TX MIMO processor 230. The transceiver may be used by a processor (e.g., the controller/processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to FIGS. 4-8).

The controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other component(s) of FIG. 2 may perform one or more techniques associated with transmitting SCell transmissions using TPC adjustment values associated with a PCell, as described in more detail elsewhere herein. For example, the controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other component(s) of FIG. 2 may perform or direct operations of, for example, process 500 of FIG. 5, process 600 of FIG. 6, and/or other processes as described herein. The memory 242 and the memory 282 may store data and program codes for the network node 110 and the UE 120, respectively. In some examples, the memory 242 and/or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the network node 110 and/or the UE 120, may cause the one or more processors, the UE 120, and/or the network node 110 to perform or direct operations of, for example, process 500 of FIG. 5, process 600 of FIG. 6, and/or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

In some aspects, a UE (e.g., UE 120) includes means for transmitting, to a network node, a PCell uplink transmission, wherein the PCell uplink transmission is associated with a TPC adjustment value; and/or means for transmitting, to the network node, an SCell SRS transmission based at least in part on a carrier switching from a PCell to an SCell, wherein the TPC adjustment value associated with the PCell uplink transmission is applied to the SCell SRS transmission based at least in part on a condition being satisfied. In some aspects, the means for the apparatus to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.

In some aspects, a network node (e.g., network node 110) includes means for receiving, from a UE, a PCell uplink transmission, wherein the PCell uplink transmission is associated with a TPC adjustment value; and/or means for receiving, from the UE, an SCell SRS transmission based at least in part on a carrier switching from a PCell to an SCell, wherein the TPC adjustment value associated with the PCell uplink transmission is applied to the SCell SRS transmission based at least in part on a condition being satisfied. In some aspects, the means for the apparatus to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.

While blocks in FIG. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and/or the TX MIMO processor 266 may be performed by or under the control of the controller/processor 280.

As indicated above, FIG. 2 is provided as an example. Other examples may differ from what is described with regard to FIG. 2.

Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station, or a network equipment may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP, or a cell, among other examples), or one or more units (or one or more components) performing base station functionality, may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station. “Network entity” or “network node” may refer to a disaggregated base station, or to one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A disaggregated base station (e.g., a disaggregated network node) may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other network nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU also can be implemented as virtual units, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.

Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of communication systems by separating base station functionality into one or more units that can be individually deployed. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

FIG. 3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units (such as a Near-RT RIC 325 via an E2 link, or a Non-RT RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both). A CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as through F1 interfaces. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be simultaneously served by multiple RUs 340.

Each of the units, including the CUs 310, the DUs 330, the RUs 340, as well as the Near-RT RICs 325, the Non-RT RICs 315, and the SMO Framework 305, may include one or more interfaces or be coupled with one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to one or multiple communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of the units can include a wired interface, configured to receive or transmit signals over a wired transmission medium to one or more of the other units, and a wireless interface, which may include a receiver, a transmitter or transceiver (such as an RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (for example, Central Unit-User Plane (CU-UP) functionality), control plane functionality (for example, Central Unit-Control Plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit can communicate bidirectionally with a CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 310 can be implemented to communicate with a DU 330, as necessary, for network control and signaling.

Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples. In some aspects, the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT), an inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which also may be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.

Each RU 340 may implement lower-layer functionality. In some deployments, an RU 340, controlled by a DU 330, may correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing an FFT, performing an iFFT, digital beamforming, or PRACH extraction and filtering, among other examples, based on a functional split (for example, a functional split defined by the 3GPP), such as a lower layer functional split. In such an architecture, each RU 340 can be operated to handle over the air (OTA) communication with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

The SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO Framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, non-RT RICs 315, and Near-RT RICs 325. In some implementations, the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an O1 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective O1 interface. The SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.

The Non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence/Machine Learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 325. The Non-RT RIC 315 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 325. The Near-RT RIC 325 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.

In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 325, the Non-RT RIC 315 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 325 and may be received at the SMO Framework 305 or the Non-RT RIC 315 from non-network data sources or from network functions. In some examples, the Non-RT RIC 315 or the Near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 305 (such as reconfiguration via an O1 interface) or via creation of RAN management policies (such as A1 interface policies).

As indicated above, FIG. 3 is provided as an example. Other examples may differ from what is described with regard to FIG. 3.

For an SRS, a UE may split a linear value {circumflex over (P)}_SRS,b,f,c(i, q_s, l) of a transmit power P_SRS,b,f,c(i, q_s, l) on an active uplink bandwidth part (BWP) b of a carrier f of a serving cell c equally across configured antenna ports for the SRS. When the UE transmits the SRS based at least in part on a configuration by an SRS resource set (SRS-ResourceSet) on the active uplink BWP b of the carrier f of the serving cell c using an SRS power control adjustment state with index l, the UE may determine an SRS transmission power P_SRS,b,f,c(i, q_s, l) in an SRS transmission occasion i as

$P_{SRS, b, f, c} (i, q_{s}, l) = \min {\begin{matrix} P_{CMAX, f, c} (i), \\ P_{O_SRS, b, f, c} (q_{s}) + 10 \log_{10} (2^{μ} \cdot M_{SRS, b, f, c} (i)) + \\ α_{SRS, b, f, c} (q_{s}) \cdot {PL}_{b, f, c} (q_{d}) + h_{b, f, c} (i, l) \end{matrix}}$

(in dBm), where P_CMAX,f,c(i) is a UE configured maximum output power for the carrier f of the serving cell c in the SRS transmission occasion i, P_{O_SRS,b,f,c}(q_s) is provided by p0 for the active uplink BWP b of the carrier f of the serving cell c and SRS resource set q_sis provided by an SRS resource set (SRS-ResourceSet) and an SRS resource set identifier (SRS-ResourceSetId), M_SRS,b,f,c(i) is an SRS bandwidth expressed in number of resource blocks for the SRS transmission occasion i on the active UL BWP b of the carrier f of the serving cell c and μ is a subcarrier spacing (SCS) configuration, and α_SRS,b,f,c(q_s) is provided by an alpha (alpha) parameter for the active uplink BWP b of the carrier f of the serving cell c and the SRS resource set q_s, PL_b,f,c(q_d) is a downlink pathloss estimate (in dB) calculated by the UE using a reference signal (RS) resource index q_dfor an active downlink BWP of the serving cell c and the SRS resource set q_s. Further, h_b,f,c(i, l)=f_b,f,c(i, l), where f_b,f,c(i, l) is a current physical uplink shared channel (PUSCH) power control adjustment state, if an SRS power control adjustment states (srs-PowerControlAdjustmentStates) parameter indicates a same power control adjustment state for SRS transmissions and PUSCH transmissions. Here, h_b,f,c(i, l) is an SRS power control adjustment state or a transmit power control (TPC) adjustment. When a configuration for a P_{O_SRS,b,f,c}(q_s) value or for a α_SRS,b,f,c(q_s) value for a corresponding SRS power control adjustment state with l for the active uplink BWP b of the carrier f of the serving cell c is provided by higher layers, h_b,f,c(k)=0, k=0, 1, . . . , i. In other words, h_b,f,c(k)=0 based at least in part on a change in serving cell or BWP.

When a UE transmits an SRS on a secondary cell (SCell) using a secondary component carrier (SCC) for an SRS carrier switching (SRS-CS) (e.g., when the UE switches from a primary cell (PCell) to the SCell), a TPC adjustment value may be reset (e.g., h_b,f,c(k)=0, k=0, 1, . . . , i) after an SCell activation. As a result, the UE may transmit the SRS on the SCell at a relatively high transmit power as compared to when transmitting the SRS on the PCell. The relatively high transmit power of the SRS transmission on the SCell may unnecessarily consume additional resources at the UE. For example, the UE may transmit with the relatively high transmit power on the SCell, which may not be required, thereby wasting resources at the UE. The relatively high power of the SRS transmission on the SCell may waste battery power at the UE. Further, the relatively high transmit power may cause interference between the UE and other UEs.

For example, a transmit power associated with a PCell SRS transmission with a TPC adjustment of −13 dBm may be approximately −25 dBm, whereas a transmit power associated with an SCell SRS transmission with a TPC adjustment of 0 dBm (e.g., h_b,f,c(k)=0) may be approximately −8 dBm. Due to the SRS-CS, the UE may reset the TPC adjustment from −13 dBm to 0 dBm. The transmit power of approximately −8 dBm for the SCell SRS transmission may be significantly more than the transmit power of approximately −25 dBm for the PCell SRS transmission, which may be based at least in part on resetting the TPC adjustment to 0 dBm after switching from the PCell to the SCell. Further, power control values other than the TPC adjustment may not change due to the SRS-CS. For example, both the PCell and the SCell may be associated with the same SRS bandwidth (e.g., M_SRS,b,f,c(i)), the same pathloss (e.g., PL_b,f,c(q_d)), etc., such that the relatively high power of the SRS transmission on the SCell may be largely attributed to the TPC reset to 0 dBm, which may occur after the SCell activation/addition. The relatively high power of the SRS transmission on the SCell may be based at least in part on the TPC adjustment for the PCell SRS transmission being a negative value (e.g., −13 dBm).

In various aspects of techniques and apparatuses described herein, a UE may transmit, to a network node, a PCell uplink transmission. The PCell uplink transmission may be a PCell SRS transmission or a PCell PUSCH transmission. The PCell uplink transmission may be associated with a TPC adjustment value. The UE may transmit, to the network node, an SCell SRS transmission based at least in part on a carrier switching (e.g., an SRS carrier switching). The UE may apply the TPC adjustment value associated with the PCell uplink transmission to the SCell SRS transmission based at least in part on a condition being satisfied. In some aspects, by applying the TPC adjustment value associated with the PCell uplink transmission to the SCell SRS transmission instead of resetting the TPC adjustment value prior to the SCell SRS transmission (e.g., setting the TPC adjustment value to zero), the UE may be able to perform the SCell SRS transmission with a lower transmit power, which may save battery power at the UE and avoid interference experienced by other UEs due to a higher transmit power associated with the UE. Further, by applying the TPC adjustment value associated with the PCell uplink transmission to the SCell SRS transmission, the UE may not transmit the SCell SRS transmission at a higher transmit power than needed, thereby saving resources at the UE.

FIG. 4 is a diagram illustrating an example 400 associated with transmitting SCell transmissions using TPC adjustment values associated with a PCell, in accordance with the present disclosure. As shown in FIG. 4, example 400 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network, such as wireless network 100.

As shown by reference number 402, the UE may transmit, to the network node, a PCell uplink transmission. The PCell uplink transmission may be a PCell SRS transmission or a PCell PUSCH transmission. The PCell uplink transmission may be associated with a TPC adjustment value. In other words, the UE may apply the TPC adjustment value to the PCell uplink transmission. The TPC adjustment value may be a TPC command factor.

In some aspects, the UE may perform a carrier switching from a PCell to an SCell. The PCell may be associated with a primary component carrier, whereas the SCell may be associated with a secondary component carrier. The carrier switching from the PCell to the SCell may involve an SCell activation/addition. In some cases, the carrier switching may be an SRS carrier switching.

As shown by reference number 404, the UE may transmit, to the network node, an SCell SRS transmission based at least in part on the carrier switching from the PCell to the SCell. The UE may apply the TPC adjustment value associated with the PCell uplink transmission to the SCell SRS transmission. In other words, the UE may apply the same TPC adjustment value that was applied to the PCell uplink transmission to the SCell SRS transmission. The UE may apply the same TPC adjustment value, as opposed to resetting the TPC adjustment value to zero for the SCell SRS transmission. In other words, the UE may apply the same TPC adjustment value that was applied to the PCell uplink transmission to the SCell SRS transmission instead of applying a TPC adjustment value of zero to the SCell SRS transmission.

In some aspects, the UE may apply the TPC adjustment value to the SCell SRS transmission based at least in part on a condition being satisfied. The condition may be satisfied based at least in part on a first value (A) being less than a second value (B), and based at least in part on a difference between the first value and the second value satisfying a threshold (X). The first value may correspond to an uplink transmit power (in dBm) of the PCell uplink transmission after incorporating the TPC adjustment value. The second value may correspond to an uplink transmit power of the SCell SRS transmission after incorporating a TPC adjustment value of zero. In other words, when A is less than B and an absolute value of A minus B is greater than X, the TPS adjustment value (e.g., h_b,f,c) of the PCell may be applied to the SCell SRS transmission instead of a TPS adjustment value of zero. Otherwise, the TPS adjustment value of zero (e.g., h_b,f,c=0) may be applied to the SCell SRS transmission. In other words, when A is not less than B and/or an absolute value of A minus B is not greater than X, the TPS adjustment value of zero may be applied to the SCell SRS transmission.

In some aspects, the condition may be satisfied based at least in part on the network node not configuring a downlink control information (DCI) format 2_3 in an RRC reconfiguration message. In some aspects, the condition may be satisfied based at least in part on the UE indicating in a UE capability indication that the UE does not support the DCI format 2_3. The UE may apply the TPC adjustment value to the SCell SRS transmission when the network does not configure the DCI format 2_3 or when the UE is not capable of supporting the DCI format 2_3 because the DCI format 2_3 may otherwise indicate a TPC adjustment value to be applied for the SCell.

As shown by reference number 406, the UE may receive, from the network node, an indication of a TPC adjustment value for the SCell. The UE may start to use the TPC adjustment value for the SCell, and the UE may no longer use the TPC adjustment value associated with the PCell uplink transmission. In other words, the TPC adjustment value associated with the PCell uplink transmission may no longer be applied to the SCell based at least in part on the indication of the TPC adjustment value for the SCell being received from the network node. The UE may receive the indication of the TPC adjustment value for the SCell via a DCI format 2_3 or via a message 2 TPC associated with a random access channel (RACH) procedure. The UE may receive the indication of the TPC adjustment value for the SCell via the DCI format 2_3 based at least in part on the network node configuring the DCI format 2_3 and the UE being able to support the DCI format 2_3. In some cases, the UE may receive the indication of the TPC adjustment value for the SCell via another DCI format (e.g., a DCI format other than DCI format 2_3).

In some aspects, the UE may apply the same TPC adjustment value applied to the PCell to the SCell for the SCell SRS transmission when the condition is satisfied. The UE may apply the same TPC adjustment value (e.g., the TPC adjustment value associated with the PCell) until the UE receives an indication of a TPC adjustment value to be applied to the SCell. In other words, the UE may apply the same TPC adjustment value until the UE receives the indication of the TPC adjustment value specifically for the SCell. The UE may receive the indication from the network node via the DCI format 2_3 or the message 2 TPC associated with the RACH procedure.

As indicated above, FIG. 4 is provided as an example. Other examples may differ from what is described with regard to FIG. 4.

FIG. 5 is a diagram illustrating an example process 500 performed, for example, by a UE, in accordance with the present disclosure. Example process 500 is an example where the UE (e.g., UE 120) performs operations associated with transmitting SCell transmissions using TPC adjustment values associated with a PCell.

As shown in FIG. 5, in some aspects, process 500 may include transmitting, to a network node, a PCell uplink transmission, wherein the PCell uplink transmission is associated with a TPC adjustment value (block 510). For example, the UE (e.g., using transmission component 704, depicted in FIG. 7) may transmit, to a network node, a PCell uplink transmission, wherein the PCell uplink transmission is associated with a TPC adjustment value, as described in connection with FIG. 4.

As further shown in FIG. 5, in some aspects, process 500 may include transmitting, to the network node, an SCell SRS transmission based at least in part on a carrier switching from a PCell to an SCell, wherein the TPC adjustment value associated with the PCell uplink transmission is applied to the SCell SRS transmission based at least in part on a condition being satisfied (block 520). For example, the UE (e.g., using transmission component 704, depicted in FIG. 7) may transmit, to the network node, an SCell SRS transmission based at least in part on a carrier switching from a PCell to an SCell, wherein the TPC adjustment value associated with the PCell uplink transmission is applied to the SCell SRS transmission based at least in part on a condition being satisfied, as described in connection with FIG. 4.

Process 500 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, the condition is satisfied based at least in part on: a first value being less than a second value; and a difference between the first value and the second value satisfying a threshold, wherein the first value corresponds to an uplink transmit power of the PCell uplink transmission after incorporating the TPC adjustment value, and the second value corresponds to an uplink transmit power of the SCell SRS transmission after incorporating a TPC adjustment value of zero.

In a second aspect, alone or in combination with the first aspect, the TPC adjustment value associated with the PCell uplink transmission and applied to the SCell SRS transmission is a non-zero value.

In a third aspect, alone or in combination with one or more of the first and second aspects, the PCell uplink transmission is a PCell SRS transmission.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the PCell uplink transmission is a PCell PUSCH transmission.

As shown in FIG. 5, in a fifth aspect, alone or in combination with one or more of the first through fourth aspects, process 500 includes receiving, from the network node, an indication of a TPC adjustment value for the SCell, wherein the TPC adjustment value associated with the PCell uplink transmission is no longer applied to the SCell based at least in part on the indication of the TPC adjustment value for the SCell being received from the network node (block 530).

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the indication of the TPC adjustment value for the SCell is received via a DCI format 2_3.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the indication of the TPC adjustment value for the SCell is received via a message 2 TPC associated with a RACH procedure.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the condition is satisfied based at least in part on the network node not configuring a DCI format 2_3 in an RRC reconfiguration message.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the condition is satisfied based at least in part on the UE indicating in a UE capability indication that the UE does not support a DCI format 2_3.

Although FIG. 5 shows example blocks of process 500, in some aspects, process 500 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 5. Additionally, or alternatively, two or more of the blocks of process 500 may be performed in parallel.

FIG. 6 is a diagram illustrating an example process 600 performed, for example, by a network node, in accordance with the present disclosure. Example process 600 is an example where the network node (e.g., network node 110) performs operations associated with transmitting SCell transmissions using TPC adjustment values associated with a PCell.

As shown in FIG. 6, in some aspects, process 600 may include receiving, from a UE, a PCell uplink transmission, wherein the PCell uplink transmission is associated with a TPC adjustment value (block 610). For example, the network node (e.g., using reception component 802, depicted in FIG. 8) may receive, from a UE, a PCell uplink transmission, wherein the PCell uplink transmission is associated with a TPC adjustment value, as described in connection with FIG. 4.

As further shown in FIG. 6, in some aspects, process 600 may include receiving, from the UE, an SCell SRS transmission based at least in part on a carrier switching from a PCell to an SCell, wherein the TPC adjustment value associated with the PCell uplink transmission is applied to the SCell SRS transmission based at least in part on a condition being satisfied (block 620). For example, the network node (e.g., using reception component 802, depicted in FIG. 8) may receive, from the UE, an SCell SRS transmission based at least in part on a carrier switching from a PCell to an SCell, wherein the TPC adjustment value associated with the PCell uplink transmission is applied to the SCell SRS transmission based at least in part on a condition being satisfied, as described in connection with FIG. 4.

Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a third aspect, alone or in combination with one or more of the first and second aspects, the PCell uplink transmission is a PCell SRS transmission.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the PCell uplink transmission is a PCell PUSCH transmission.

As further shown in FIG. 6, in a fifth aspect, alone or in combination with one or more of the first through fifth aspects, process 600 includes transmitting, to the UE, an indication of a TPC adjustment value for the SCell, wherein the TPC adjustment value associated with the PCell uplink transmission is no longer applied to the SCell based at least in part on the indication of the TPC adjustment value for the SCell being received from the network node (block 630).

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the indication of the TPC adjustment value for the SCell is received via a DCI format 2_3.

Although FIG. 6 shows example blocks of process 600, in some aspects, process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 6. Additionally, or alternatively, two or more of the blocks of process 600 may be performed in parallel.

FIG. 7 is a diagram of an example apparatus 700 for wireless communication, in accordance with the present disclosure. The apparatus 700 may be a UE, or a UE may include the apparatus 700. In some aspects, the apparatus 700 includes a reception component 702 and a transmission component 704, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus 700 may communicate with another apparatus 706 (such as a UE, a base station, or another wireless communication device) using the reception component 702 and the transmission component 704.

In some aspects, the apparatus 700 may be configured to perform one or more operations described herein in connection with FIG. 4. Additionally, or alternatively, the apparatus 700 may be configured to perform one or more processes described herein, such as process 500 of FIG. 5. In some aspects, the apparatus 700 and/or one or more components shown in FIG. 7 may include one or more components of the UE described in connection with FIG. 2. Additionally, or alternatively, one or more components shown in FIG. 7 may be implemented within one or more components described in connection with FIG. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

The reception component 702 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 706. The reception component 702 may provide received communications to one or more other components of the apparatus 700. In some aspects, the reception component 702 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 700. In some aspects, the reception component 702 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with FIG. 2.

The transmission component 704 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 706. In some aspects, one or more other components of the apparatus 700 may generate communications and may provide the generated communications to the transmission component 704 for transmission to the apparatus 706. In some aspects, the transmission component 704 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 706. In some aspects, the transmission component 704 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with FIG. 2. In some aspects, the transmission component 704 may be co-located with the reception component 702 in a transceiver.

The transmission component 704 may transmit, to a network node, a PCell uplink transmission, wherein the PCell uplink transmission is associated with a TPC adjustment value. The transmission component 704 may transmit, to the network node, an SCell SRS transmission based at least in part on a carrier switching from a PCell to an SCell, wherein the TPC adjustment value associated with the PCell uplink transmission is applied to the SCell SRS transmission based at least in part on a condition being satisfied. The reception component 702 may receive, from the network node, an indication of a TPC adjustment value for the SCell, wherein the TPC adjustment value associated with the PCell uplink transmission is no longer applied to the SCell based at least in part on the indication of the TPC adjustment value for the SCell being received from the network node.

The number and arrangement of components shown in FIG. 7 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in FIG. 7. Furthermore, two or more components shown in FIG. 7 may be implemented within a single component, or a single component shown in FIG. 7 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in FIG. 7 may perform one or more functions described as being performed by another set of components shown in FIG. 7.

FIG. 8 is a diagram of an example apparatus 800 for wireless communication, in accordance with the present disclosure. The apparatus 800 may be a network node, or a network node may include the apparatus 800. In some aspects, the apparatus 800 includes a reception component 802 and a transmission component 804, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus 800 may communicate with another apparatus 806 (such as a UE, a base station, or another wireless communication device) using the reception component 802 and the transmission component 804.

In some aspects, the apparatus 800 may be configured to perform one or more operations described herein in connection with FIG. 4. Additionally, or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as process 600 of FIG. 6. In some aspects, the apparatus 800 and/or one or more components shown in FIG. 8 may include one or more components of the network node described in connection with FIG. 2. Additionally, or alternatively, one or more components shown in FIG. 8 may be implemented within one or more components described in connection with FIG. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

The reception component 802 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 806. The reception component 802 may provide received communications to one or more other components of the apparatus 800. In some aspects, the reception component 802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 800. In some aspects, the reception component 802 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the network node described in connection with FIG. 2.

The transmission component 804 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 806. In some aspects, one or more other components of the apparatus 800 may generate communications and may provide the generated communications to the transmission component 804 for transmission to the apparatus 806. In some aspects, the transmission component 804 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 806. In some aspects, the transmission component 804 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the network node described in connection with FIG. 2. In some aspects, the transmission component 804 may be co-located with the reception component 802 in a transceiver.

The reception component 802 may receive, from a UE, a PCell uplink transmission, wherein the PCell uplink transmission is associated with a TPC adjustment value. The reception component 802 may receive, from the UE, an SCell SRS transmission based at least in part on a carrier switching from a PCell to an SCell, wherein the TPC adjustment value associated with the PCell uplink transmission is applied to the SCell SRS transmission based at least in part on a condition being satisfied. The transmission component 804 may transmit, to the UE, an indication of a TPC adjustment value for the SCell, wherein the TPC adjustment value associated with the PCell uplink transmission is no longer applied to the SCell based at least in part on the indication of the TPC adjustment value for the SCell being received from the network node.

The number and arrangement of components shown in FIG. 8 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in FIG. 8. Furthermore, two or more components shown in FIG. 8 may be implemented within a single component, or a single component shown in FIG. 8 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in FIG. 8 may perform one or more functions described as being performed by another set of components shown in FIG. 8.

The following provides an overview of some Aspects of the present disclosure:

- Aspect 1: A method of wireless communication performed by an apparatus of a user equipment (UE), comprising: transmitting, to a network node, a primary cell (PCell) uplink transmission, wherein the PCell uplink transmission is associated with a transmit power control (TPC) adjustment value; and transmitting, to the network node, a secondary cell (SCell) sounding reference signal (SRS) transmission based at least in part on a carrier switching from a PCell to an SCell, wherein the TPC adjustment value associated with the PCell uplink transmission is applied to the SCell SRS transmission based at least in part on a condition being satisfied.
- Aspect 2: The method of Aspect 1, wherein the condition is satisfied based at least in part on: a first value being less than a second value; and a difference between the first value and the second value satisfying a threshold, wherein the first value corresponds to an uplink transmit power of the PCell uplink transmission after incorporating the TPC adjustment value, and the second value corresponds to an uplink transmit power of the SCell SRS transmission after incorporating a TPC adjustment value of zero.