WO2025092008A1

WO2025092008A1 - Transmit power control for srs transmission

Info

Publication number: WO2025092008A1
Application number: PCT/CN2024/103867
Authority: WO
Inventors: Lingling Xiao; Bingchao LIU; Wei Ling; Chenxi Zhu
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2024-07-05
Filing date: 2024-07-05
Publication date: 2025-05-08
Anticipated expiration: 2027-01-05

Abstract

Various aspects of the present disclosure relate to a UE, a network entity, a processor for wireless communication, methods, and a computer readable medium for transmit power control (TPC) indication for sounding reference signal (SRS) transmission. The UE receives a configuration indicating two separate closed loop power control adjustment states for SRS transmission in a serving cell. The UE further receives a UE- specific downlink control information (DCI) format triggering at least one SRS resource set, wherein the UE-specific DCI format includes at least one SRS TPC command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states. The UE further performs SRS transmission based on the at least one triggered SRS resource set associated with at least one of the two separate closed loop power control adjustment state. In this way, TPC commands can be flexibly indicated for the triggered SRS resource sets.

Description

TRANSMIT POWER CONTROL FOR SRS TRANSMISSION

TECHNICAL FIELD

The present disclosure relates to wireless communications, and more specifically to a user equipment (UE) , a network entity, a processor for wireless communication, methods, and a computer readable medium for transmit power control (TPC) indication for sounding reference signal (SRS) transmission.

BACKGROUND

A wireless communication system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. Each network communication devices, such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) . Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .

Up to Release 18 (Rel-18) , the downlink control information (DCI) , for example, DCI format 2_3 is used to indicate TPC command for SRS. In Rel-19 asymmetric downlink (DL) sTRP (single transmit/receive point) /uplink (UL) mTRP (multiple transmit/receive point) scenarios, two separate power control (PC) closed loops are introduced for SRS transmission. Issues regarding this feature need to be further studied.

SUMMARY

Embodiments of the present disclosure are provided to support two separate power control closed loops for SRS transmission. The present disclosure relates to a UE, a network entity, a processor for wireless communication, methods, and a computer readable medium for TPC indication for SRS transmission when two separate power control closed loops are configured.

In a first aspect, there is provided a UE. The UE comprises a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive, from a network entity, a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in a serving cell; receive, from the network entity, a UE-specific downlink control information (DCI) format triggering at least one SRS resource set, wherein the UE-specific DCI format includes at least one SRS transmit power control (TPC) command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states; and perform SRS transmission based on the at least one triggered SRS resource set associated with at least one of the two separate closed loop power control adjustment states.

In a second aspect, there is provided a network entity, comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: transmit, to a user equipment (UE) , a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in a serving cell; and transmit, to the UE, a UE-specific downlink control information (DCI) format triggering at least one SRS resource set, wherein the UE-specific DCI includes at least one SRS transmit power control (TPC) command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states.

In a third aspect, there is provided a processor for wireless communication. The a processor comprise at least one memory; and a controller coupled with the at least one memory and configured to cause the controller to: receive, from a network entity, a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in a serving cell; receive, from the network entity, a UE-specific downlink control information (DCI) format triggering at least one SRS resource set, wherein the UE-specific DCI format includes at least one SRS transmit power control (TPC) command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states; and perform SRS transmission based on the at least one triggered SRS resource set associated with at least one of the two separate closed loop power control adjustment states.

In a fourth aspect, there is provided method performed by a user equipment (UE) , the method comprising: receiving, from a network entity, a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in a serving cell; receiving, from the network entity, a UE-specific downlink control information (DCI) format triggering at least one SRS resource set, wherein the UE-specific DCI format includes at least one SRS transmit power control (TPC) command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states; and performing SRS transmission based on the at least one triggered SRS resource set associated with at least one of the two separate closed loop power control adjustment states.

In a fifth aspect, there is provided method performed by a network entity, the method comprising: transmitting, to a user equipment (UE) a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in a serving cell; and transmitting, to the UE, a UE-specific downlink control information (DCI) format triggering at least one SRS resource set, wherein the UE-specific DCI includes at least one SRS transmit power control (TPC) command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states.

In a sixth aspect, there is provided a computer readable medium having instructions stored thereon, the instructions, when executed by a processor of an apparatus, causing the apparatus to perform the method according to the fourth or the fifth aspect of the disclosure.

In some implementations of the methods, the UE and the network entity, the UE-specific DCI format comprises two SRS TPC command fields corresponding to the two separate closed loop power control adjustment states, respectively.

In some implementations of the methods, the UE and the network entity, the at least one triggered SRS resource set comprises multiple SRS resource sets that are associated with different closed loop power control adjustment states, and UE may apply values of each of the two SRS TPC command fields to each of the two separate closed loop power control adjustment states, respectively.

In some implementations of the methods, the UE and the network entity, the network entity may set TPC command values of the two SRS TPC command fields, the TPC command values corresponding to different separate closed loop power control adjustment states, respectively.

In some implementations of the methods, the UE and the network entity, the at least one triggered SRS resource set comprises multiple SRS resource sets that are associated with different closed loop power control adjustment states, the processor is further configured to set TPC command values of the two SRS TPC command field.

In some implementations of the methods, the UE and the network entity, the at least one triggered SRS resource set is associated with a same closed loop power control adjustment state, the network entity may set TPC command value for the corresponding SRS TPC command field.

In some implementations of the methods, the UE and the network entity, the at least one triggered SRS resource set is associated with a same closed loop power control adjustment state, and the UE may apply, a value of a SRS TPC command field corresponding to the associated closed loop power control adjustment state; and ignore the other SRS TPC command field.

In some implementations of the methods, the UE and the network entity, the UE-specific DCI format comprises one SRS TPC command field, and the UE may apply a value of the SRS TPC command field to both of the two separate closed loop power control adjustment states.

In some implementations of the methods, the UE and the network entity, the UE-specific DCI format comprises one SRS TPC command field, and the at least one triggered SRS resource set is associated with a same closed loop power control adjustment state, and the UE may apply a value of the SRS TPC command field to the associated closed loop power control adjustment state.

In some implementations of the methods, the UE and the network entity, the UE-specific DCI format is a DCI format without data scheduling, and the UE may determine, based on a configured scheduling radio network temporary identifier (CS- RNTI) scrambled UE-specific DCI and a combination of values of a plurality of fields included in the UE-specific DCI, that the UE-specific DCI format is used to trigger the SRS transmission and indicate TPC command values.

In some implementations of the methods, the UE and the network entity, the plurality of fields comprises redundancy version (RV) ; modulation and coding scheme (MCS) ; new data indicator (NDI) ; and frequency domain resource allocation (FDRA) .

In some implementations of the methods, the UE and the network entity, the scrambled CRC is scrambled by a CS-RNTI, the RV is set to all ‘1’ s, the MCS is set to all ‘0’ s, the NDI is set to ‘0’ , and the FDRA is set to all ‘0’ s for FDRA Type 0 or dynamicSwitch and set to all ‘1’ s for FDRA Type 1.

In some implementations of the methods, the UE and the network entity, the scrambled CRC is scrambled by a CS-RNTI, the RV is set to all ‘0’ s, the MCS is set to all ‘0’ s, the NDI is set to ‘0’ , and the FDRA is set to all ‘0’ s for FDRA Type 0 or dynamicSwitch and set to all ‘1’ s for FDRA Type 1.

In some implementations of the methods, the UE and the network entity, the UE may reuse fields, other than the plurality of fields, included in the UE-specific DCI as SRS TPC command fields.

In some implementations of the methods, the UE and the network entity, the UE may reuse a TPC command for scheduled physical uplink control channel (PUCCH) field as an SRS TPC command field.

In some implementations of the methods, the UE and the network entity, the UE may reuse a second TPC command for scheduled PUCCH if present or a field included in the UE-specific DCI format, different from the TPC command for scheduled PUCCH field , as another SRS TPC command field.

In some implementations of the methods, the UE and the network entity, the UE may receive, from the network entity, a common DCI format triggering at least one SRS resource set in at least one serving cell.

In some implementations of the methods, the UE and the network entity, the UE is configured with an SRS TPC type parameter set to Type A, the at least one triggered SRS resource set comprises aperiodic SRS resource sets in one of the at least one serving cell.

In some implementations of the methods, the UE and the network entity, for a SRS TPC type parameter set to Type A, in a case that at least one aperiodic SRS resource set in the at least one serving cell is configured with a list of available slot offsets including multiple entries and a SRS request is present in a block corresponding the UE in the common DCI format, the block includes an SRS offset indicator field to indicate the slot offset for SRS transmission.

In some implementations of the methods, the UE and the network entity, for a SRS TPC type parameter set to Type B, in a case that at least one aperiodic SRS resource set configured in an UL carrier is configured with a list of available slot offsets including multiple entries and a SRS request is present in a block corresponding the UE in the common DCI format, the block includes an SRS offset indicator field to indicate the slot offset for SRS transmission.

In some implementations of the methods, the UE and the network entity, a bit width of the SRS offset indicator field is bits, where K is the maximum number of entries of the list of the available slot offsets configured for all aperiodic SRS resource sets in the at least one serving cell.

In some implementations of the methods, the UE and the network entity, a triggered aperiodic SRS resource set is configured with a list of available slot offsets including multiple entries, and a default entry of the multiple entries is used to determine the SRS transmission slot offset of the triggered SRS resource set with a list of available slot offsets including multiple entries.

In some implementations of the methods, the UE and the network entity, the UE may determine, based on TPC commands, an accumulation part of SRS transmit power per closed loop power control adjustment state, and the accumulation part is jointly coded with other TPC commands in a physical downlink control channel (PDCCH) with a common DCI format or in a dedicated DCI format that triggers the SRS transmission.

In some implementations of the methods, the UE and the network entity, the UE may reset, based on at least one of a P0 parameter and an alpha parameter of an SRS resource set being configured or reconfigured, the accumulation part of a closed loop power control adjustment state associated with a joint or UL transmission configuration indicator (TCI) state determined for the SRS resource set.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a wireless communications system in which some embodiments of the present disclosure can be implemented.

FIG. 2 illustrates an example of a process flow for transmit power control indication for SRS transmission using a UE-specific DCI format in accordance with some example embodiments of the present disclosure.

FIG. 3 illustrates an example of a process flow for transmit power control indication for SRS transmission using a group common DCI format in accordance with some example embodiments of the present disclosure.

FIG. 4 illustrates an example of a device that is suitable for implementing some embodiments of the present disclosure.

FIG. 5 illustrates an example of a processor that is suitable for implementing some embodiments of the present disclosure.

FIG. 6 illustrates a flowchart of a method performed by a user equipment in accordance with aspects of the present disclosure.

FIG. 7 illustrates a flowchart of a method performed by a network entity in accordance with aspects of the present disclosure.

FIG. 8 illustrates a flowchart of a further method performed by a user equipment in accordance with aspects of the present disclosure.

FIG. 9 illustrates a flowchart of a further method performed by a network entity in accordance with aspects of the present disclosure.

Throughout the drawings, the same or similar reference numerals represent the same or similar elements.

DETAILED DESCRIPTION

Principles of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below. In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

References in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It shall be understood that although the terms “first” and “second” or the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms. In some examples, values, procedures, or apparatuses are referred to as “best, ” “lowest, ” “highest, ” “minimum, ” “maximum, ” or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of embodiments. As used herein, the singular forms “a, ” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises, ” “comprising, ” “has, ” “having, ” “includes” and/or “including, ” when used herein, specify the presence of stated features, elements, components and/or the like, but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof. For example, the term “includes” and its variants are to be read as open terms that mean “includes, but is not limited to. ” The term “based on” is to be read as “based at least in part on. ” The term “one embodiment” and “an embodiment” are to be read as “at least one embodiment. ” The term “another embodiment” is to be read as “at least one other embodiment. ” The use of an expression such as “A and/or B” can mean either “only A” or “only B” or “both A and B. ” Other definitions, explicit and implicit, may be included below.

The present disclosure targets issues on DCI indicating TPC command for SRS configured with two separate closed loops in asymmetric DL sTRP/UL mTRP deployment scenarios.

In Rel-19, it was agreed to specify enhancement for asymmetric DL sTRP/UL mTRP deployment scenarios, assuming intra-band intra-DU non-co-located mTRP scenarios, without changing existing cell definition or defining a new cell (e.g. UL-only cell) , assuming the Rel-17/18 unified transmission configuration indicator (TCI) framework and fully reusing the legacy QCL (quasi-colocation) /UL spatial relation rules, targeting FR1 and FR2. It was also agreed to support two closed-loop power control (CLPC) adjustment states for SRS in one component carrier (CC) , both separate from PUSCH.

Further, it was agreed to study whether and how to indicate TPC command for SRS CLPC adjustment states through UE-specific DCI format, such as DCI format 1_1 and/or 0_1, when the UE is configured two SRS CLPC adjustment states. It was proposed to add one 2-bit SRS TPC command field and one 1-bit closed-loop indicator field in DCI formats 1_1 and 0_1 with data scheduling data to indicate TPC commands. The intension of using such UE specific DCI format indicating TPC command for SRS is to avoid two-level DCI mechanism (i.e., one DCI is used to trigger SRS and another DCI is to indicate TPC command for the SRS transmission) . However, this method only indicates TPC command for SRS with one separate PC closed loop and another DCI is still needed to indicate TPC command for SRS with another separate PC closed loop.

In Rel-18, DCI format 2_3 is used to trigger SRS transmission and indicate TPC commands when SRS-CarrierSwitching is configured. The DCI format 2_3 may include a SRS request field (0 or 2 bits) which, if present, triggers SRS resource sets as defined by Table 7.3.1.1.2-24 in Technical Specification (TS) 38.212; and TPC commands, where each TPC command is applied to a respective UL carrier (i.e., a CC or a serving cell) provided by higher layer parameter cc-IndexInOneCC-Set. However, the SRS request in DCI format 2_3 can only trigger SRS resource set for ‘antennaswitching’ for SRS TPC type A (e.g., srs-TPC-PDCCH-Group=typeA) . In Rel-19 asymmetric DL sTRP/UL mTRP scenarios, two separate PC closed loops (i.e., two separate closed loop power control adjustment states) are introduced for SRS transmission, where the SRS transmission may be used for other usages such as beam management. Therefore, for SRS TPC type A, DCI format 2_3 needs to trigger SRS resource sets for other usage. Besides, in legacy, it is an error case if DCI format 2_3 is used to trigger SRS with more than one entry in availableSlotOffsetList which configures multiple candidate slot offset for SRS transmission. That means the SRS resource set triggered by DCI format 2_3 shall be configured with only one entry in availableSlotOffsetList. In legacy, the flexibility may not be a big issue since only SRS resource set for antenna switching is configured with one entry in availableSlotOffsetList. However, in Rel-19, since DCI format 2_3 is not only used for SRS for antenna switching, it will be too restrictive if all SRS resource sets are configured with only one entry in availableSlotOffsetList.

If P0 (which is the target receiving power at gNB) and/or alpha (which is the compensation factor for pathloss) of an SRS transmission is configured/re-configured by higher layers, the accumulation part in SRS transmit power calculation shall be reset. For asymmetric DL sTRP/UL mTRP scenarios, the resetting mechanism also needs to be further studied per closed loop.

In this disclosure, methods are provided to resolve those issues on DCI indicating TPC command for SRS configured with two separate PC closed loops in asymmetric DL sTRP/UL mTRP deployment scenarios.

Aspects of the present disclosure are described in the context of a wireless communications system. FIG. 1 illustrates an example of a wireless communications system 100 in which some embodiments of the present disclosure can be implemented. The wireless communications system 100 may include one or more network entities 102 (also referred to as network equipment (NE) ) , one or more UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.

The one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN) , a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. A network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface. In a 3GPP non-terrestrial network (NTN) , a network entity 102 in form of a satellite can directly communicate to UE 104 using NR/LTE Uu interface. The satellite may be a transparent satellite or a regenerative satellite. For NTN with a transparent satellite, a base station on earth may communicate with a UE via the satellite. For NTN with a regenerative satellite, the base station may be on board and directly communicate with the UE.

A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112. For example, a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies. In some implementations, a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In some other implementations, a UE 104 may be mobile in the wireless communications system 100. In some other implementations, a UE 104 may be a UAV UE and may communicate with one or more network entities 102 while flying.

The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1. A UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in FIG. 1. Additionally, or alternatively, a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.

A UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

A network entity 102 may support communications with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) . In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102) . In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) . In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) . An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .

In some implementations, a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) . For example, a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, or any combination thereof.

An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) . In some implementations, one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .

Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU. For example, a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.

Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or multiple different cells (e.g., via one or more RUs) . In some implementations, a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .

A CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u) , and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface) . In some implementations, a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.

The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.

The core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) . The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .

In the wireless communications system 100, the network entities 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) . In some implementations, the network entities 102 and the UEs 104 may support different resource structures. For example, the network entities 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) . The network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.

One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames) . Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) . In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) . In some implementations, the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) . In some implementations, FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) . For example, FR1 may be associated with a first numerology (e.g., μ=0) , which includes 15 kHz subcarrier spacing; a second numerology (e.g., μ=1) , which includes 30 kHz subcarrier spacing; and a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) . For example, FR2 may be associated with a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., μ=3) , which includes 120 kHz subcarrier spacing.

FIG. 2 illustrates an example of a process flow for transmit power control indication for SRS transmission using a UE-specific DCI format in accordance with some example embodiments of the present disclosure. The process flow 200 may involve a UE 201 and a network entity (e.g. a base station such as gNB) 202. The process flow 200 may be applied to the wireless communications system 100 with reference to FIG. 1, for example, the UE 201 may be any of UEs 104, and the network entity 202 may be any of the network entities 102. It would be appreciated that the process flow 200 may be applied to other communication scenarios.

At 210, the network entity 202 may transmit, to the UE 201, a configuration 215 indicating two separate closed loop power control adjustment states for SRS transmission in a serving cell. Accordingly, at 220, the UE 201 receives the configuration 215 from the network entity 202.

To facilitate the asymmetric DL sTRP/UL mTRP deployment scenarios, the UE 201 may be configured with two separate closed-loop power control (CLPC) adjustment states for SRS in one CC, both of which are separate from that of the PUSCH. For example, the parameter srs-PowerControlAdjustmentStates, which indicate which same closed loop or separate closed loop is used for an SRS resource set, may be set to “separateClosedLoop” to configure the UE 201 with two closed-loop PC adjustment states for SRS. For the UE 201 configured with two SRS CLPC adjustment states, the parameter closedLoopIndex-r17 for SRS in the associated joint/UL TCI state may indicates one of the SRS CLPC adjustment states.

At 230, the network entity 202 may transmit, to the UE 201, a UE-specific DCI format 235 triggering at least one SRS resource set and indicating TPC command for the triggered SRS resource set. In some embodiments, the SRS resource set may be aperiodic. In some embodiments, the SRS resource set may be aperiodic or semi-persistent. Accordingly, at 240, the UE 201 receives the UE-specific DCI format 235 from the network entity 202.

At 250, the UE 201 may perform SRS transmission 255 based on the at least one triggered SRS resource set associated with at least one of the two separate closed loop power control adjustment states. Accordingly, at 260, the network entity 202 receives the SRS from the UE 201.

The UE-specific DCI format 235 may include a SRS request field to trigger SRS resource set (s) , and at least one SRS TPC command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states. The UE specific DCI format 235 may include DL DCI format, e.g. DCI format 1_1/1_2 and UL DCI format, e.g., DCI format 0_1/0_2.

The UE specific DCI may only be used for triggering and indicating TPC command for SRS transmission or the UE specific DCI may also schedule a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) transmission in addition to indicating TPC command for SRS transmission. In the following, the two cases will be discussed separately.

In the first case, the UE specific DCI format can indicate TPC command for SRS and schedule data transmission (i.e., scheduling PDSCH or PUSCH transmission) simultaneously. In some embodiments, the UE-specific DCI format 235 may comprises two SRS TPC command fields corresponding to the two separate closed loop power control adjustment states, respectively. If a SRS request field is present in the UE-specific DCI format 235, and if two separate PC closed loops are configured for SRS in the serving cell, two SRS TPC command fields for indicating TPC command for SRS transmission may be added in the UE-specific DCI format 235, since the triggered different aperiodic SRS resource sets may correspond to different PC closed loops. Each SRS TPC command field may be used to indicate the TPC command for SRS transmission for each PC closed loop.

In particular, if the triggered SRS resource sets correspond to or are associated with different separate PC closed loops, the first SRS TPC command field is used to indicate the TPC command for the triggered SRS with separate PC closed loop 0 and the second SRS TPC command field is used to indicate the TPC command for the triggered SRS with separate PC closed loop 1. Accordingly, the UE 210 may apply the value of the first SRS TPC command field to the PC closed loop 0, and the value of the second SRS TPC command field to the PC closed loop 1.

If the triggered SRS resource sets correspond to or are associated with a same separate PC closed loop, the UE 201 may apply the value of the SRS TPC command field corresponding to that PC closed loop, and ignore the other SRS TPC command field. Specially, if the triggered SRS resource sets are corresponding to a same separate PC closed loop l = 0, the UE 201 applies the value of the first SRS TPC command field and ignore the value of the second SRS TPC command field; if the triggered SRS resource sets are corresponding to a same separate PC closed loop l = 1, the UE 201 applies the value of the second SRS TPC command field and ignore the value of the first SRS TPC command field. The benefit of including two SRS TPC commands in one DCI format is that it can flexibly indicate TPC command for the triggered SRS resource sets with only one bit increased.

An example of the configuration of aperiodic SRS resource sets in a CC is shown in Table 1. Suppose a DCI format 0_1 schedules a PUSCH transmission and SRS request is present in the DCI. Two SRS TPC command fields are also added in the DCI and the first SRS TPC command field is used to indicate TPC command for SRS with separate PC closed loop 0 and the second SRS TPC command field is used to indicate TPC command for SRS with separate PC closed loop 1. If the value of SRS request field is ‘01’ , aperiodic SRS resource set 0, 2, 3 and 5 will be triggered. Then, the first SRS TPC command field is used to indicate TPC command for SRS transmission based on SRS resource set 0 since the associated PC closed loop is separate 0 and the second SRS TPC command field is used to indicate TPC command for SRS transmission based on SRS resource set 2 and SRS resource set 3 since the associated PC closed loop is separate 1.

Table 1: Example of configuration of aperiodic SRS resource sets in a serving cell

In some embodiments, the UE-specific DCI format 235 may comprise one SRS TPC command field. To save DCI overhead, if the SRS request field is present in a UE specific DCI format, one SRS TPC command field for indicating TPC command for SRS transmission is added in the dedicated DCI format.

In one option, the one SRS TPC command may be applied to all of the triggered SRS resource sets regardless of whether they are associated with the same or different PC closed loops. The UE may apply the value of the one SRS TPC command field to any of the two separate closed loops associated with each trigger SRS resource set. In another option, since the only one SRS TPC command field can only indicate TPC command for SRS transmission for one separate PC closed loop, if two separate PC closed loops are configured for SRS in the serving cell, the UE is expected that the triggered SRS resource sets by the UE specific DCI format are associated with a same PC closed loop. That means different SRS resource sets configured with same trigger state or in same entry in aperiodicSRS-ResourceTriggerList are associated with a same closed loop index. In this event, the UE 201 applies the value of the one SRS TPC command field to the associated closed loop of all triggered SRS resource sets.

In addition, the UE 201 may be configured by an RRC parameter, e.g, twoTPCforSRS, to indicate whether one or two SRS TPC command field is present in UE specific DCI formats or indicate whether the second SRS TPC command field is present. The RRC configuration may be per DCI format.

In the second case, the UE specific DCI format can indicate the TPC command for SRS without data transmission. In legacy, DCI format 0_1/0_2 can trigger SRS only without data and without channel state information (CSI) request, and there is no issue when the DCI format 0_1/0_2 indicates the TPC command for SRS without data transmission. But for DL DCI, there is no such mechanism. Then the first issue is how to indicate a UE that a DL UE specific DCI is dedicated for indicating the TPC command for SRS.

In some embodiments, one bit may be added in the DL UE specific DCI format to indicate that the DCI is only for triggering aperiodic SRS transmission or for both SRS triggering and data scheduling. Alternatively, CS-RNTI is used to scramble the Cyclic Redundancy Check (CRC) for the DCI and some fields in the DCI may be used for this purpose. In some embodiments, the fields may include one or more of: redundancy version (RV) ; modulation and coding scheme (MCS) ; new data indicator (NDI) ; or frequency domain resource allocation (FDRA) .

The UE 201 may determine, based on CS-RNTI scrambled DCI and a combination of the values of the fields included in the UE-specific DCI, that the UE-specific DCI format is used to trigger the SRS transmission and/or indicate TPC command values. For example, if the CRC is scrambled by a configured scheduling radio network temporary identifier (CS-RNTI) , the RV is set to all ‘1’ s, the MCS is set to all ‘0’ s, the NDI is set to ‘0’ , and the FDRA is set to all ‘0’ s for FDRA Type 0 or dynamicSwitch and set to all ‘1’ s for FDRA Type 1, the UE 201 may determine that the DCI is used to trigger the SRS transmission and/or indicate TPC command values. As another example, if the CRC is scrambled by a CS-RNTI, the RV is set to all ‘0’ s, the MCS is set to all ‘0’ s, the NDI is set to ‘0’ , and the FDRA is set to all ‘0’ s for FDRA Type 0 or dynamicSwitch and set to all ‘1’ s for FDRA Type 1, the UE 201 may determine that the DCI is used to trigger the SRS transmission and/or indicate TPC command values.

The second issue is how to indicate the TPC command (s) for the SRS (s) triggered by the UE specific DCI format without data scheduling. In some embodiments, the methods described with reference to the DCI with data scheduling may be reused. Additionally or alternatively, fields other than the fields used to identify a UE specific DCI for indicating SRS triggering only, included in the DCI dedicated, may be reused as one or two SRS TPC command fields.

In some embodiments, the DCI may include one SRS TPC command field for SRS TPC command indication. For example, the UE 201 may reuse a TPC command for scheduled PUCCH field as an SRS TPC command field.

In some embodiments, the DCI may include two SRS TPC command field for SRS TPC command indication. If a second TPC command for a scheduled PUCCH is present, the TPC command for scheduled PUCCH field and the second TPC command for scheduled PUCCH field can be reused to indicate TPC command for SRS for each PC closed loop. If a second TPC command for scheduled PUCCH field is not present, the TPC command for scheduled PUCCH field and one other field with bitwidth no smaller than that of SRS TPC command field, e.g., FDRA, or TDRA, or HARQ process number, or PUCCH resource indicator, or PDSCH-to-HARQ_feedback timing indicator, or antenna port, can be reused to indicate the TPC command for SRS for each PC closed loop.

FIG. 3 illustrates an example of a process flow for transmit power control indication for SRS transmission using a group common DCI format which is used for indication for a plurality of UEs in accordance with some example embodiments of the present disclosure. The process flow 300 may involve a UE 201 and a network entity (e.g. a base station such as gNB) 202. The process flow 300 may be applied to the wireless communications system 100 with reference to FIG. 1, for example, the UE 201 may be any of UEs 104, and the network entity 202 may be any of the network entities 102. It would be appreciated that the process flow 300 may be applied to other communication scenarios. The steps of the process flow 300 may be performed separately from or in combination with the process flow 200 in FIG. 2.

At 310, the network entity 202 may transmit, to the UE 201, a configuration 315 indicating two separate closed loop power control adjustment states for SRS transmission in at least one serving cell. Accordingly, at 320, the UE 201 receives the configuration 315 from the network entity 202. The configuration 315 may be the same as the configuration 215 in FIG. 2.

At 330, the network entity 202 may transmit, to the UE 201, a common DCI format 335 triggering at least one SRS resource set. Accordingly, at 340, the UE 201 receives the common DCI format 335 from the network entity 202. The common DCI format 335 may be a group common DCI format such as DCI format 2_3.

At 350, the UE 201 may perform SRS transmission 355 based on the at least one triggered SRS resource set associated with at least one of the two separate closed loop power control adjustment states. Accordingly, at 360, the network entity 202 receives the SRS from the UE 201.

In Rel-19 asymmetric DL sTRP/UL mTRP scenarios, two separate PC closed loops (i.e., two closed-loop PC adjustment states for SRS, both separate from PUSCH) are introduced for SRS transmission. Different SRS resource sets may use different PC closed loops in a serving cell. The different SRS resource sets can be used for antenna switching, or for other purpose, for example, for beam management and others. In Rel-19 asymmetric DL sTRP/UL mTRP, the feature of two SRS CLPC adjustment states should not tie with SRS antenna switching. However, current DCI format 2_3 can only trigger SRS resource sets for the usage “antennaSwitching” for SRS TPC type A, enhancement is needed to also trigger SRS resource sets with other usage.

In some embodiments, if the UE 201 is configured with an SRS TPC type parameter set to Type A, the aperiodic SRS resource sets in one of the at least one serving cell are triggered by the DCI format 335, regardless of the configured usage. Therefore, following enhancement in Table 2 is provided. If a UE is configured with two separate closed loops for SRS transmission, Table 2 may be used for interpreting SRS request, instead of the current one in standards TS 38.212, Table 7.3.1.1.2-24. Note that restrictions on usage “antennaSwitching” are removed from current table.

Table 2: SRS request

Flexible SRS triggering was introduced in Rel-17 that availableSlotOffsetList is configured per SRS resource set and may contain up to four entries. Each entry indicates an available slot offset value for the aperiodic SRS transmission. An SRS offset indicator field of up to 2 bits in DCI other than DCI format 2_3 is used to indicate which entry is used. Since there is no SRS offset indicator field in DCI format 2_3, the SRS resource set triggered by DCI format 2_3 shall be configured with only one entry in availableSlotOffsetList. In legacy, since DCI format 2_3 can only trigger aperiodic SRS resource set (s) for antenna switching, the availableSlotOffsetList configured for these SRS resource sets shall contain one entry. The flexibility may not be a big issue. However, in Rel-19, since DCI format 2_3 does not tie to antenna switching, it will be too restrictive if all SRS resource sets are configured with only one entry in availableSlotOffsetList. Otherwise, a DCI other than DCI format 2_3 will be used to indicate slot offset for the trigger aperiodic SRS and a DCI format 2_3 is used to indicate TPC command for SRS transmission. This two-level DCI mechanism will increase UE’s decoding complexity. Following methods are provided to resolve this issue.

In some embodiments, an SRS offset indicator field may be introduced in DCI format 2_3. Depending on the SRS TPC type, the SRS offset indicator field may be added in DCI format 2_3 for the following cases. For Type A, if the SRS request is present and availableSlotOffsetList with multiple entries is configured in at least one SRS resource set in an UL carrier in cc-IndexInOneCC-Set, an SRS offset indicator field may be added in the block corresponding to the UE. The SRS offset indicator field is common for all SRS resource sets in the CC set (i.e., cc-IndexInOneCC-Set) , which means a same SRS offset indicator field is added to indicate the slot offset for the triggered SRS in different UL carrier in the CC set. For Type B (e.g., srs-TPC-PDCCH-Group=typeB) , if the SRS request is present and availableSlotOffsetList with multiple entries is configured in at least one SRS resource set for a UE in an UL carrier, an SRS offset indicator field is added in the block corresponding to the UE.

In some embodiments, the bit width of SRS offset indicator field is bits, where K is the maximum number of entries of availableSlotOffsetList configured for all aperiodic SRS resource set (s) in the at least one serving cell. Specifically, for SRS TPC type A, the at least one serving cell is an UL carrier in the CC set; for SRS TPC type B, the at least one serving cell is the UL carrier corresponding to the block of the UE.

In some embodiments, a default entry may be used. If the SRS offset is not explicitly indicated in the DCI, a default entry may be used to indicate the slot offset for a triggered aperiodic SRS resource set configured with availableSlotOffsetList including multiple entries.

For both type A and type B, if availableSlotOffsetList with multiple entries is configured for at least one triggered aperiodic SRS resource set, a default entry, e.g., the value in the first entry may be used for the SRS transmission based on the SRS resource set configured with multiple entries in availableSlotOffsetList. This method does not change the DCI format 2_3 and increase the payload size of a block in DCI format 2_3 corresponding to the UE. The benefit is that SRS resource sets can be configured with one entry in availableSlotOffsetList or can be configured with multiple entries in availableSlotOffsetList in the serving cell and DCI format 2_3 can trigger and indicate TPC command for the different SRS resource set simultaneously.

An example of the configuration of aperiodic SRS resource sets in a CC set is shown in Table 3. Suppose SRS request is present in the block corresponding to the UE in DCI format 2_3 and srs-TPC-PDCCH-Group = typeA. If SRS request is ‘01’ , aperiodic SRS resource set 0, 1, 2 and 3 in CC 0 will be triggered. Based on current rule, it will be an error case, since SRS resource set 3 is configured with more than one entry in availableSlotOffsetList. If the default entry method is used, one DCI format 2_3 can trigger them together and for SRS resource set 3, the first entry in availableSlotOffsetList configured for SRS resource set 3 is used for determining the SRS transmission slot.

Table 3: Example of configuration of aperiodic SRS resource sets in a CC set

If two separate PC closed loops are configured for SRS transmission in a serving cell, the UE 201 may determine, based on TPC commands, an accumulation part of SRS transmit power per closed loop power control adjustment state. The accumulation part in calculation SRS transmit power will be where l is the PC closed loop index and δ_{SRS, b, f, c} (m, l) may be jointly coded with other TPC commands in a PDCCH with DCI format 2_3. If the UE specific DCI formats are also used for indicating TPC command for aperiodic SRS transmission, δ_{SRS, b, f, c} (m, l) can also be included in a UE specific DCI format that triggers the SRS transmission occasion i on active UL BWP b of carrier f of serving cell c in addition to jointly coded with other TPC commands in a PDCCH with DCI format 2_3.

If P0 and/or alpha of an SRS transmission or SRS resource set is configured or re-configured by higher layers, the accumulation part h_b, f, c (k, l) in calculation SRS transmit power may be reset per separate PC closed loop. That is, if 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 l for active UL BWP b of carrier f of serving cell c is provided by higher layers, the accumulation part may be reset, i.e., h_b, f, c (k, l) =0, k=0, 1, …, i, where l is the power control adjustment state associated with the joint/UL TCI state determined for the SRS resource set q_s.

FIG. 4 illustrates an example of a device that is suitable for implementing some embodiments of the present disclosure. The device 400 may be an example of a UE 104 or network entity 102 as described herein. The device 400 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 400 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 402, a memory 404, a transceiver 406, and, optionally, an I/O controller 408. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 402, the memory 404, the transceiver 406, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 402, the memory 404, the transceiver 406, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

In some implementations, the processor 402, the memory 404, the transceiver 406, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 402 and the memory 404 coupled with the processor 402 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 402, instructions stored in the memory 404) .

For example, the processor 402 may support wireless communication at the device 400 in accordance with examples as disclosed herein. The device 400 may be an example of a UE 104. In this case, the processor 402 may be configured to operable to support means for receiving, from a network entity, a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in a serving cell; means for receiving, from the network entity, a UE-specific downlink control information (DCI) format triggering at least one SRS resource set, wherein the UE-specific DCI format includes at least one SRS transmit power control (TPC) command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states; and means for performing SRS transmission based on the at least one triggered SRS resource set associated with at least one of the two separate closed loop power control adjustment states.

Additionally or alternatively, the processor 402 may be configured to operable to support means for receiving, from a network entity, a configuration indicating two separate closed loop power control adjustment states for SRS transmission in at least one serving cell; means for receiving, from the network entity, a common DCI format triggering at least one SRS resource set in the at least one serving cell; and means for performing SRS transmission based on the at least one triggered SRS resource set associated with at least one of the two separate closed loop power control adjustment states.

The device 400 may be an example of a network entity 102, e.g. a network entity. In this case, the processor 402 may be configured to operable to support means for transmitting, to a user equipment (UE) a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in a serving cell; and means for transmitting, to the UE, a UE-specific downlink control information (DCI) format triggering at least one SRS resource set, wherein the UE-specific DCI includes at least one SRS transmit power control (TPC) command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states.

Additionally or alternatively, the processor 402 may be configured to operable to support means for transmitting, to a UE, a configuration indicating two separate closed loop power control adjustment states for SRS transmission in at least one serving cell; and means for transmitting, to the UE, a common DCI format triggering at least one SRS resource set in the at least one serving cell.

The processor 402 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some implementations, the processor 402 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 402. The processor 402 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 404) to cause the device 400 to perform various functions of the present disclosure.

The memory 404 may include random access memory (RAM) and read-only memory (ROM) . The memory 404 may store computer-readable, computer-executable code including instructions that, when executed by the processor 402 cause the device 400 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 402 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 404 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The I/O controller 408 may manage input and output signals for the device 400. The I/O controller 408 may also manage peripherals not integrated into the device 400. In some implementations, the I/O controller 408 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 408 may utilize an operating system such as or another known operating system. In some implementations, the I/O controller 408 may be implemented as part of a processor, such as the processor 402. In some implementations, a user may interact with the device 400 via the I/O controller 408 or via hardware components controlled by the I/O controller 408.

In some implementations, the device 400 may include a single antenna 410. However, in some other implementations, the device 400 may have more than one antenna 410 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 406 may communicate bi-directionally, via the one or more antennas 410, wired, or wireless links as described herein. For example, the transceiver 406 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 406 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 410 for transmission, and to demodulate packets received from the one or more antennas 410. The transceiver 406 may include one or more transmit chains, one or more receive chains, or a combination thereof.

A transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) . The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmit chain may also include one or more antennas 410 for transmitting the amplified signal into the air or wireless medium.

A receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receive chain may include one or more antennas 410 for receive the signal over the air or wireless medium. The receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal. The receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

FIG. 5 illustrates an example of a processor 500 is suitable for implementing some embodiments of the present disclosure. The processor 500 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 500 may include a controller 502 configured to perform various operations in accordance with examples as described herein. The processor 500 may optionally include at least one memory 504. Additionally, or alternatively, the processor 500 may optionally include one or more arithmetic-logic units (ALUs) 506. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 500 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 500) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .

The controller 502 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 500 to cause the processor 500 to support various operations in accordance with examples as described herein. For example, the controller 502 may operate as a control unit of the processor 500, generating control signals that manage the operation of various components of the processor 500. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

The controller 502 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 404 and determine subsequent instruction (s) to be executed to cause the processor 500 to support various operations in accordance with examples as described herein. The controller 502 may be configured to track memory address of instructions associated with the memory 504. The controller 502 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 502 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 500 to cause the processor 500 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 502 may be configured to manage flow of data within the processor 500. The controller 502 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 500.

The memory 504 may include one or more caches (e.g., memory local to or included in the processor 500 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 504 may reside within or on a processor chipset (e.g., local to the processor 500) . In some other implementations, the memory 504 may reside external to the processor chipset (e.g., remote to the processor 500) .

The memory 504 may store computer-readable, computer-executable code including instructions that, when executed by the processor 500, cause the processor 500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 502 and/or the processor 500 may be configured to execute computer-readable instructions stored in the memory 404 to cause the processor 500 to perform various functions. For example, the processor 500 and/or the controller 502 may be coupled with or to the memory 404, the processor 500, the controller 502, and the memory 404 may be configured to perform various functions described herein. In some examples, the processor 500 may include multiple processors and the memory 504 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

The one or more ALUs 506 may be configured to support various operations in accordance with examples as described herein. In some implementation, the one or more ALUs 506 may reside within or on a processor chipset (e.g., the processor 500) . In some other implementations, the one or more ALUs 506 may reside external to the processor chipset (e.g., the processor 500) . One or more ALUs 506 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 506 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 506 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 506 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 506 to handle conditional operations, comparisons, and bitwise operations.

The processor 500 may support wireless communication in accordance with examples as disclosed herein. The processor 500 may implemented at a UE 104. In this case, the processor 500 may be configured to operable to support means for receiving, from a network entity, a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in a serving cell; means for receiving, from the network entity, a UE-specific downlink control information (DCI) format triggering at least one SRS resource set, wherein the UE-specific DCI format includes at least one SRS transmit power control (TPC) command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states; and means for performing SRS transmission based on the at least one triggered SRS resource set associated with at least one of the two separate closed loop power control adjustment states.

Additionally or alternatively, the processor 500 may be configured to operable to support means for receiving, from a network entity, a configuration indicating two separate closed loop power control adjustment states for SRS transmission in at least one serving cell; means for receiving, from the network entity, a common DCI format triggering at least one SRS resource set in the at least one serving cell; and means for performing SRS transmission based on the at least one triggered SRS resource set associated with at least one of the two separate closed loop power control adjustment states.

The processor 500 may be implemented at a network entity 102, e.g. a base station. In this case, the processor 500 may be configured to operable to support means for transmitting, to a user equipment (UE) a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in a serving cell; and means for transmitting, to the UE, a UE-specific downlink control information (DCI) format triggering at least one SRS resource set, wherein the UE-specific DCI includes at least one SRS transmit power control (TPC) command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states.

Additionally or alternatively, the processor 500 may be configured to operable to support means for transmitting, to a UE, a configuration indicating two separate closed loop power control adjustment states for SRS transmission in at least one serving cell; and means for transmitting, to the UE, a common DCI format triggering at least one SRS resource set in the at least one serving cell.

FIG. 6 illustrates a flowchart of a method 600 performed by a UE in accordance with aspects of the present disclosure. The operations of the method 600 may be implemented by a device or its components as described herein. For example, the operations of the method 600 may be performed by a UE 104 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 610, the method may include receiving, from a network entity, a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in a serving cell. The operations of 610 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 610 may be performed by a UE 104 as described with reference to FIG. 1.

At 620, the method may include receiving, from the network entity, a UE-specific downlink control information (DCI) format triggering at least one SRS resource set, wherein the UE-specific DCI format includes at least one SRS transmit power control (TPC) command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states. The operations of 620 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 620 may be performed by a UE 104 as described with reference to FIG. 1.

At 630, the method may include performing SRS transmission based on the at least one triggered SRS resource set associated with at least one of the two separate closed loop power control adjustment states. The operations of 630 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 620 may be performed by a UE 104 as described with reference to FIG. 1.

FIG. 7 illustrates a flowchart of a method 700 performed by a network entity in accordance with aspects of the present disclosure. The operations of the method 700 may be implemented by a device or its components as described herein. For example, the operations of the method 700 may be performed by a network entity 102 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 710, the method may include transmitting, to a user equipment (UE) a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in a serving cell. The operations of 710 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 710 may be performed by a network entity 102 as described with reference to FIG. 1.

At 720, the method may include transmitting, to the UE, a UE-specific downlink control information (DCI) format triggering at least one SRS resource set, wherein the UE-specific DCI includes at least one SRS transmit power control (TPC) command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states. The operations of 720 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 720 may be performed by a network entity 102 as described with reference to FIG. 1.

FIG. 8 illustrates a flowchart of a method 800 performed by a UE in accordance with aspects of the present disclosure. The operations of the method 800 may be implemented by a device or its components as described herein. For example, the operations of the method 800 may be performed by a UE 104 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 810, the method may include receiving, from a network entity, a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in at least one serving cell. The operations of 810 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 810 may be performed by a UE 104 as described with reference to FIG. 1.

At 820, the method may include receiving, from the network entity, a common downlink control information (DCI) format triggering at least one SRS resource set in the at least one serving cell. The operations of 820 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 820 may be performed by a UE 104 as described with reference to FIG. 1.

At 830, the method may include performing SRS transmission based on the at least one triggered SRS resource set associated with at least one of the two separate closed loop power control adjustment states. The operations of 830 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 830 may be performed by a UE 104 as described with reference to FIG. 1.

FIG. 9 illustrates a flowchart of a method 900 performed by a network entity in accordance with aspects of the present disclosure. The operations of the method 900 may be implemented by a device or its components as described herein. For example, the operations of the method 900 may be performed by a network entity 102 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 910, the method may include transmitting, to a user equipment (UE) a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in at least one serving cell. The operations of 910 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 910 may be performed by a network entity 102 as described with reference to FIG. 1.

At 920, the method may include transmitting, to the UE, a common DCI format triggering at least one SRS resource set in the at least one serving cell. The operations of 920 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 920 may be performed by a network entity 102 as described with reference to FIG. 1.

It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

As used herein, including in the claims, an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

A user equipment (UE) comprising:

a processor; and

a transceiver coupled to the processor,

wherein the processor is configured to:

receive, from a network entity, a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in a serving cell;

receive, from the network entity, a UE-specific downlink control information (DCI) format triggering at least one SRS resource set, wherein the UE-specific DCI format includes at least one SRS transmit power control (TPC) command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states; and

perform SRS transmission based on the at least one triggered SRS resource set associated with at least one of the two separate closed loop power control adjustment states.
The UE of claim 1, wherein the UE-specific DCI format comprises two SRS TPC command fields corresponding to the two separate closed loop power control adjustment states, respectively.
The UE of claim 2, wherein the at least one triggered SRS resource set is associated with a same closed loop power control adjustment state, and the processor is further configured to:

apply, a value of a SRS TPC command field corresponding to the associated closed loop power control adjustment state; and

ignore the other SRS TPC command field.
The UE of claim 1, wherein the UE-specific DCI format comprises one SRS TPC command field, and the processor is further configured to:

apply a value of the SRS TPC command field to both of the two separate closed loop power control adjustment states.
The UE of claim 1, wherein the UE-specific DCI format comprises one SRS TPC command field, and the at least one triggered SRS resource set is associated with a same closed loop power control adjustment state, and wherein the processor is further configured to:

apply a value of the SRS TPC command field to the associated closed loop power control adjustment state.
The UE of claim 1, wherein the UE-specific DCI format is a DCI format without data scheduling, wherein the processor is further configured to:

determine, based on a combination of values of a plurality of fields included in the UE-specific DCI scrambled with CS-RNTI, that the UE-specific DCI format is used to trigger the SRS transmission and indicate TPC command values.
The UE of claim 6, wherein the plurality of fields comprises:

redundancy version (RV) ;

modulation and coding scheme (MCS) ;

new data indicator (NDI) ; and

frequency domain resource allocation (FDRA) .
The UE of claim 7, wherein the scrambled CRC is scrambled by a configured scheduling radio network temporary identifier (CS-RNTI) , the RV is set to all ‘1’s, the MCS is set to all ‘0’s, the NDI is set to ‘0’ , and the FDRA is set to all ‘0’s for FDRA Type 0 or dynamicSwitch and set to all ‘1’s for FDRA Type 1.
The UE of claim 7, wherein the scrambled CRC is scrambled by a CS-RNTI, the RV is set to all ‘0’s, the MCS is set to all ‘0’s, the NDI is set to ‘0’ , and the FDRA is set to all ‘0’s for FDRA Type 0 or dynamicSwitch and set to all ‘1’s for FDRA Type 1.
The UE of claim 6, wherein the processor is further configured to:

reuse fields, other than the plurality of fields, included in the UE-specific DCI as SRS TPC command fields.
The UE of claim 1, wherein the processor is further configured to:

receive, from the network entity, a common DCI format triggering at least one SRS resource set in at least one serving cell.
The UE of claim 11, wherein the UE is configured with an SRS TPC type parameter set to Type A, the at least one triggered SRS resource set comprises aperiodic SRS resource sets in one of the at least one serving cell.
The UE of claim 11, wherein

for a SRS TPC type parameter set to Type A,

in a case that at least one aperiodic SRS resource set in the at least one serving cell is configured with a list of available slot offsets including multiple entries and a SRS request is present in a block corresponding the UE in the common DCI format, the block includes an SRS offset indicator field to indicate the slot offset for SRS transmission; and

wherein for a SRS TPC type parameter set to Type B,

in a case that at least one aperiodic SRS resource set configured in an UL carrier is configured with a list of available slot offsets including multiple entries and a SRS request is present in a block corresponding the UE in the common DCI format, the block includes an SRS offset indicator field to indicate the slot offset for SRS transmission.
The UE of claim 13, wherein a bit width of the SRS offset indicator field isbits, where K is the maximum number of entries of the list of the available slot offsets configured for all aperiodic SRS resource sets in the at least one serving cell.
The UE of claim 11, wherein a triggered aperiodic SRS resource set is configured with a list of available slot offsets including multiple entries, and a default entry of the multiple entries is used to determine the SRS transmission slot offset of the triggered SRS resource set with a list of available slot offsets including multiple entries.
The UE of claim 1, wherein the processor is further configured to:

determine, based on TPC commands, an accumulation part of SRS transmit power per closed loop power control adjustment state,

wherein the accumulation part is jointly coded with other TPC commands in a physical downlink control channel (PDCCH) with a common DCI format or in a dedicated DCI format that triggers the SRS transmission.
The UE of claim 1, wherein the processor is further configured to:

reset, based on at least one of a P0 parameter and an alpha parameter of an SRS resource set being configured or reconfigured, the accumulation part of a closed loop power control adjustment state associated with a joint or UL transmission configuration indicator (TCI) state determined for the SRS resource set.
A network entity comprising:

a processor; and

a transceiver coupled to the processor,

wherein the processor is configured to:

transmit, to a user equipment (UE) , a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in a serving cell; and

transmit, to the UE, a UE-specific downlink control information (DCI) format triggering at least one SRS resource set, wherein the UE-specific DCI includes at least one SRS transmit power control (TPC) command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states.
A processor for wireless communication, comprising:

at least one memory; and

a controller coupled with the at least one memory and configured to cause the controller to:

receive, from a network entity, a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in a serving cell;

receive, from the network entity, a UE-specific downlink control information (DCI) format triggering at least one SRS resource set, wherein the UE-specific DCI format includes at least one SRS transmit power control (TPC) command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states; and

perform SRS transmission based on the at least one triggered SRS resource set associated with at least one of the two separate closed loop power control adjustment states.
A method performed by a user equipment (UE) , the method comprising:

receiving, from a network entity, a configuration indicating two separate closed loop power control adjustment states for sounding reference signal (SRS) transmission in a serving cell;

receiving, from the network entity, a UE-specific downlink control information (DCI) format triggering at least one SRS resource set, wherein the UE-specific DCI format includes at least one SRS transmit power control (TPC) command field used for indicating TPC command values for both of the two separate closed loop power control adjustment states; and

performing SRS transmission based on the at least one triggered SRS resource set associated with at least one of the two separate closed loop power control adjustment states.