SRS triggering and power control indication using dedicated signaling

Abstract

Various embodiments disclosed herein provide for methods and apparatuses to enable jointly trigger uplink Reference Signal transmission and dynamically indicating Transmit Power Control commands for closed-loop power control. There is disclosed a method performed by a wireless device for adapting a transmission power of an uplink Reference Signal transmission targeting a network node, the method comprising receiving a network configuration of at least one uplink reference signal closed-loop power control state, receiving a message triggering the uplink reference signal transmission, wherein the message comprises a transmission power control command for one of the at least one uplink reference signal closed-loop power control state, and adapting the transmission power of the uplink reference signal transmission based on the transmission power control command.

Description

SRS TRIGGERING AND POWER CONTROL INDICATION USING DEDICATED SIGNALING TECHNICAL FIELD

[0001] The present disclosure provides a method for Sounding Reference Signal (SRS) triggering and power control indication using dedicated signaling in a wireless communication system. BACKGROUND NR

[0002] Data scheduling in New Radio (NR) is typically in a slot basis, an example is shown in Figure 1 with a 14-symbol slot, where the first two symbols contain physical downlink control channel (PDCCH) and the rest contains physical shared data channel, either PDSCH (physical downlink shared channel) or PUSCH (physical uplink shared channel)

[0003] Downlink transmissions can be dynamically scheduled in a slot-by-slot basis. The scheduling information such as resource allocation and modulation order is contained in downlink control information (DCI) carried by PDCCH. Downlink (DL) user data is carried in PDSCH.

[0004] Uplink (UL) data transmission can also be dynamically scheduled using DCI carried in PDCCH. A User Equipment (UE) first decodes uplink grants in DCI and then transmits data in PUSCH based the scheduling information in the uplink grant.

[0005] In addition to dynamic scheduling of PUSCH, semi-persistent transmission of periodic PUSCH using configured grants (CG) is also supported in NR. In CG type 1, the periodicity as well as a slot offset are configured by Radio Resource Control (RRC). In CG type 2, the PUSCH transmission can be activated or deactivated dynamically by DCI.

[0006] For channel estimation purpose, channel state information reference signals, Channel State Information Reference Signal (CSI-RS), in the DL and sounding reference signals (SRS) in the UL are also supported.

[0007] Synchronization signals (SS), including primary SS (PSS) and secondary SS (SSS), are used in NR to allow a UE to acquire DL synchronization to a cell and the physical cell ID (PCI) associated to a cell. PSS and SSS are transmitted together with Physical broadcast channel (PBCH), referred to a SS / PBCH block or SSB in short. PBCH is used to transmit some critical information (i.e., master information block, MIB) in a cell for a UE to acquire system information from other system information blocks (SIBs)SRS

[0008] In NR, SRS is used for providing CSI to the gNB in the UL. The usage of SRS includes, e.g., deriving the appropriate transmission / reception beams and / or to perform link adaptation (i.e., setting the transmission rank and the Modulation and Coding Scheme (MCS)), and for selecting DL (e.g., for PDSCH transmissions) and UL (e.g., for PUSCH transmissions) MIMO precoding.

[0009] In Long Term Evolution (LTE) and NR, the SRS is configured via RRC, where parts of the configuration can be updated (for reduced latency) through Medium Access Control Control Element (MAC-CE) signaling. The configuration includes, for example, the SRS resource allocation (the physical mapping and the sequence to use) as well as the time-domain behavior (aperiodic, semi-persistent, or periodic). For aperiodic SRS transmission, the RRC configuration does not activate an SRS transmission from the UE but instead a dynamic activation trigger is transmitted from the gNB in the DL, via the DCI in the PDCCH which instructs the UE to transmit the SRS once, at a predetermined time.

[0010] When configuring SRS transmissions, the gNB configures, through the SRS-Config IE, a set of SRS resources and a set of SRS resource sets, where each SRS resource set contains one or more SRS resources. Uplink Power Control in NR

[0011] The gNB may consist of a single transmission and reception point (TRP) or multiple TRPs (mTRP). In case of multiple TRPs, a UE can be scheduled with downlink transmissions from one or more of the TRPs and uplink data transmission to one or more of the TRPs, either one TRP at a time or simultaneously.

[0012] Uplink power control in NR consists of two parts, i.e., open-loop power control and closed-loop power control. Open-loop power control is used to set the uplink transmit power based on a few factors such as pathloss estimation between the UE and a TRP in a serving cell, the target receive power, channel / signal bandwidth, modulation and coding scheme (MCS), fractional power control factor, etc.

[0013] Closed-loop power control is based on power adjustments signaled in power control commands received from the gNB. The power control commands are typically determined based on the difference between the actual received power and a desired received power at the gNB. Up to two closed power control loops can be configured in NR for each UL channel or signal. Either cumulative or non-cumulative closed-loop power adjustments are supported in NR. A closed loop adjustment at a given time is also referred to as a power control adjustment state.

[0014] A DL reference signal (RS) is transmitted from each TRP, which can be used by a UE to estimate the pathloss between the UE and the TRP. Each DL RS has an associated index for identifying it. For UL transmission, power control can be performed separately for each TRP.

[0015] For a UL channel or signal (e.g., PUSCH, Physical Uplink Control Channel (PUCCH), or SRS) to be transmitted in UL associated with a pathloss RS with index ^^^^, its transmit power in a transmission occasion i within a slot in a bandwidth part (BWP) of a carrierfrequency of a serving cell and a closed-loop index ^^^^ (^^^^ = 0,1) can be expressed as:^^^^ (^^^^) ^^^^(^^^^,^^^^, ^^^^) = ^^^^^^^^^^^^� ^^^^^^^^^^^^^^^^,^^^^,^^^^^^^^^^^^^^^^^^^^^^^^−^^^^^^^^^^^^^^^^(^^^^, ^^^^) + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^−^^^^^^^^^^^^^^^^(^^^^, ^^^^)where ^^^^^^^^^^^^^^^^^^^^,^^^^,^^^^(^^^^) is a UE’s maximum output power for the carrier frequency, f, of the serving cell, c, in transmission occasion ^^^^ for the UL channel or signal.is the openloop transmit power and ^^^^^^^^^^^^^^^^^^^^^^^^^^^^−^^^^^^^^^^^^^^^^(^^^^, ^^^^) is the closed loop power adjustment.

[0016] ^^^^^^^^^^^^^^^^^^^^−^^^^^^^^^^^^^^^^(^^^^, ^^^^) is given by:where ^^^^^^^^is the nominal target receive power for the UL channel or signal and comprises a cell specific part ^^^^^^^^,^^^^^^^^^^^^^^^^and a UE specific part ^^^^^^^^,^^^^^^^^, ^^^^^^^^^^^^(^^^^) is a power adjustment related to the bandwidth or number of RBs occupied by the channel or signal at transmission occasion ^^^^, ^^^^^^^^(^^^^) is a pathloss (PL) estimation based on a downlink reference signal (RS) with index k,^^^^ (0 < ^^^^ ≤ 1) is a fractional pathloss compensation factor, and ∆(^^^^) is a power offsetdetermined by modulation and code rate of the UL channel or signal.

[0017] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^−^^^^^^^^^^^^^^^^(^^^^, ^^^^) is given by:cumulation is enabled^^^^(^^^^, ^^^^); if cumulation is disabled (i. e. , absolute is enable)where ^^^^(^^^^, ^^^^) is a power adjustment value indicated in a transmit power control (TPC) commandin a DCI associated with the UL channel or signal at transmission occasion ^^^^ and configured withclosed-loop index ^^^^;^^^^(^^^^, ^^^^) is a sum of power adjustment values indicated incommands that the UE received for the channel or signal since the TPC command fortransmission occasion ^^^^ − ^^^^0.

[0018] Note that power control parameters ^^^^^^^^, ^^^^^^^^^^^^(^^^^), ^^^^, ^^^^^^^^, ∆(^^^^), ^^^^(^^^^, ^^^^) are generallyconfigured separately for each UL channel or signal (e.g., PUSCH, PUCCH, and SRS) and may be different for different UL channels or signals.Closed-Loop Power Control State in NR

[0019] In NR, two Closed-Loop power control adjustment states are supported for PUCCH, both are independent from the Closed-Loops of PUSCH and SRS. The TPC commands are indicated in the DCI format scheduling a PDSCH transmission (i.e., DCI format 1_0 / 1_1 / 1_2).

[0020] For PUSCH, two Closed-Loop power control states are supported (independent of PUCCH) and controlled by the DCI format scheduling a PUSCH transmission (i.e., DCI format 0_0 / 0_1 / 0_2).

[0021] Besides the DL / UL scheduling DCIs which are UE dedicated, DCI format 2_2 can be used for transmission of group common TPC commands for PUCCH and PUSCH, if the RRC parameters two PUCCH-PC-AdjustmentStates (see PUSCH-PowerControl IE) or twoPUSCH- PC-AdjustmentStates (see PUSCH-PowerControl IE) is configured.

[0022] Each SRS resource set can be configured to either follow one of the two Closed- Loop power control states for PUSCH, or a separate Closed-Loop power control state for only SRS.

[0023] As described in TS 38.213 if the RRC parameter srs- PowerControlAdjustmentStates (in SRS-Config information element) is not configured or indicates sameAsFci2, the SRS closed-loop power control state should follow either the first or the second closed-loop power control states of PUSCH, respectively. Otherwise, a separate SRS closed-loop power control state is configured when srs-PowerControlAdjustmentStates indicates separateClosedLoop. SRS-Config Information Element: usage ENUMERATED {beamManagement,codebook,nonCodebook, antennaSwitching}, alpha Alpha OPTIONAL, -- Need S p0 INTEGER (-202..24) OPTIONAL, -- Cond Setup pathlossReferenceRS PathlossReferenceRS-Config OPTIONAL, -- Need M srs-PowerControlAdjustmentStates ENUMERATED { sameAsFci2, separateClosedLoop} OPTIONAL, -- Need S ..., [[ pathlossReferenceRSList-r16 SetupRelease { PathlossReferenceRSList-r16} OPTIONAL -- Need M ]], [[ usagePDC-r17 ENUMERATED {true} OPTIONAL, -- Need R

[0024] The separate Closed-Loop control state is conveyed in DCI format 2_3.UL-only Nodes

[0025] It is expected that the demand on capacity and user throughput will increase in the future. It is also expected that UL will become a limiting factor, partly due to the natural imbalance of spectral efficiency between UL and DL (which comes from for instance different number antennas, different power levels etc.) but also partly due to an increase of UL heavy services like gaming, V2V communication etc.

[0026] A potential remedy to this is to densify the networks more in the UL than in the DL. This may be done by for instance providing radio nodes that only receive in the UL (they do hence not perform any DL transmissions). We will refer to such a transmission node as an “UL-only node / TRP” herein. By using such UL-only nodes one could consequently enhance the UL without enhancing the DL. While there is obviously no direct improvement in downlink performance, as compared to normal DL+UL nodes, benefits of UL-only nodes include lower complexity, lower weight, smaller volumes, ease of deployment and avoiding the need for permits to deploy radio transmitters. A first step to better support UL-only nodes has been included in RP-234007 New WID Rel-19 NR MIMO Phase 5, Samsung, RAN Meeting #102, December 2023, where the power control for FR1 and FR2 will be enhanced to better support UL-only nodes.

[0027] In RP-234007, the following objective is included:

[0028] “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 TCI framework and fully reusing the legacy QCL / UL spatial relation rules, targeting FR1 and FR2 a. Two closed-loop PC adjustment states for SRS, both separate from PUSCH; and pathloss offset configurations for pathloss calculation to UL TRP(s), when the pathloss RS is from DL sTRP.”

[0029] In existing New Radio (NR) multi-TRP operation, it is assumed that each TRP can be used for both DL transmission and UL reception. For NR Rel-19, the idea of deploying UL only TRPs in a cell has been proposed in RWS-230248, Views on Rel-19 MIMO / UL enhancements, NTT DOCOMO, INC, 3GPP TSG RAN Rel-19 workshop, Taipei, June 15th – 16th, 2023 and RWS-230290, Views on Rel-19 MIMO evolution, ZTE, Sanechips, 3GPP TSG RAN Rel-19 workshop, Taipei, June 15th – 16th, 2023.

[0030] UL only TRPs may be useful in the following scenarios. • UL-only TRPs deployed at the cell edge to provide better UL coverage for cell edge UEs;• UL-only TRP deployed in a Time Division Duplex (TDD) band where there is dominant UL allocation; or • UL-only TRP deployed in a band that can only be used for UL transmission due to regulatory issues. SUMMARY

[0031] There currently exist certain challenge(s). An UL-only TRP receives only and does not transmit any DL signals. However, one issue with enabling UL-only TRP is, Closed-Loop UL power control for UL transmissions to those TRPs. Currently, NR only supports a maximum of 3 Closed-Loop power control states for Physical Uplink Shared Channel (PUSCH) and SRS. In Rel-19 MIMO in order to enable high UL throughput in Heterogeneous networks in which UE can receive DL transmission from the Macro gNB (the anchor TRP / node) and transmit UL to either the Macro gNB or non-co-located Micro node (the UL-only TRP / node), two Closed-Loop power control adjustment states for UL RS (e.g., SRS), both separate from PUSCH, should be supported. In legacy NR, the triggering of SRS transmission and provision of separate SRS closed-loop power control state are conveyed using different downlink control information (DCI) formats which is not a signaling efficient approach. Secondly, the legacy TPC provision DCI format 2_3 for separate SRS closed-loop power control state is a UE common DCI and provides a maximum of Transmit Power Controls (TPCs) for multiple UEs. There is not currently a way to indicate the new second separate Closed-Loop power control state for UL RS targeting the UL-only node in an efficient way.

[0032] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The core essence of the solution described herein is to enable triggering SRS transmission and providing TPC for separate SRS closed-loop power control state simultaneously using the same UE dedicated DCI format. Separate SRS power control with dedicated DCI format, e.g. DCI 0_1 and DCI 1_1, that is useful for Asymmetric M-TRP and UL-only TRP to get accurate measurement before switching to the UL-only TRP or switching back to Anchor TRP, is not yet supported in NR.

[0033] One aspect of the invention provides a method performed by a wireless device for adapting a transmission power of an UL Reference Signal transmission targeting a network node. The method comprises receiving a network configuration of at least one UL RS closed-loop power control state. The method further comprises receiving a message triggering the UL RS transmission. The message comprises a transmission power control command for one of the at least one UL RS closed-loop power control state. The method further comprises adapting thetransmission power of the UL RS transmission based on the transmission power control command.

[0034] Another aspect of the invention provides a wireless device for adapting a transmission power of an UL Reference Signal transmission targeting a network node. The wireless device comprises a radio interface and processing circuitry configured to receive a network configuration of at least one UL RS closed-loop power control state and receive a message triggering the UL RS transmission. The message comprises a transmission power control command for one of the at least one UL RS closed-loop power control state. The radio interface and processing circuitry further configured to adapt the transmission power of the UL RS transmission based on the transmission power control command.

[0035] Still another aspect of the invention provides a method performed by a network node for adapting a transmission power of an UL Reference Signal transmission from a wireless device. The method comprising transmitting a network configuration of at least one UL RS closed-loop power control state and transmitting a message triggering the UL RS transmission. The message comprises a transmission power control command for one of the at least one UL RS closed-loop power control state for adapting the transmission power of the UL RS transmission.

[0036] Yet another aspect of the invention provides a network node for adapting a transmission power of an UL Reference Signal transmission from a wireless device. The network node comprising a radio interface and processing circuitry configured to transmit a network configuration of at least one UL RS closed-loop power control state and transmit a message triggering the UL RS transmission. The message comprises a transmission power control command for one of the at least one UL RS closed-loop power control state for adapting the transmission power of the UL RS transmission.

[0037] Certain embodiments may enable the indication of a second separate (not tied to PUSCH) Closed-Loop power control targeting an UL-only TRP / node.

[0038] Various embodiments disclosed herein provide for methods to enable jointly trigger Sounding Reference Signal (SRS) transmission and dynamically indicating Transmit Power Control (TPC) commands for closed-loop SRS power control targeting asymmetric downlink (DL) single Transmission Reception Point (sTRP) and uplink (UL) multi-TRP (mTRP), and UL- only nodes using dedicated downlink control information (DCI) formats, namely one or more of DCI 0_1 / 0_2 / 0_3 for uplink transmission and / or one or more of DCI 1_1 / 1_2 / 1_3 for downlink reception.BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0040] Figure 1 shows an example of New Radio (NR) time-domain structure in accordance with some embodiments of the present disclosure.

[0041] Figure 2 shows an example of a serving cell with Uplink (UL) and Downlink (DL) Transmission Reception Point (TRP) and an UL-only TRP in accordance with some embodiments of the present disclosure.

[0042] Figure 3 shows a message sequence chart of a method for determining an UL transmission power for an UL Reference Signal (RS) targeting a UL-only network node in accordance with some embodiments of the present disclosure.

[0043] Figure 4 shows an UL-only TRP in an asymmetric DL sTRP UL mTRP deployment.

[0044] Figure 5 shows an example of a procedure configuring a UE for UL-only TRP operation in FR1.

[0045] Figure 6 shows a synchronization scenario UL-only TRP ahead of Anchor TRP.

[0046] Figure 7 shows an example of a communication system in accordance with some embodiments of the present disclosure.

[0047] Figure 8 shows a User Equipment device (UE) in accordance with some embodiments of the present disclosure.

[0048] Figure 9 shows a network node in accordance with some embodiments of the present disclosure.

[0049] Figure 10 is a block diagram of a host, which may be an embodiment of the host of Figure 7, in accordance with various aspects of the present disclosure described herein.

[0050] Figure 11 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized. DETAILED DESCRIPTION

[0051] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0052] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0053] Various embodiments disclosed herein provide for methods to enable jointly trigger Sounding Reference Signal (SRS) transmission and dynamically indicating Transmit Power Control (TPC) commands for closed-loop SRS power control targeting asymmetric downlink (DL) single Transmission Reception Point (sTRP) and uplink (UL) multi-TRP (mTRP), and UL- only nodes using dedicated downlink control information (DCI) formats, namely one or more of DCI 0_1 / 0_2 / 0_3 for uplink transmission and / or one or more of DCI 1_1 / 1_2 / 1_3 for downlink reception

[0054] In this disclosure, the terms UL TRP, UL-only TRP, UL-only node and UL-only RP are interchangeable.

[0055] A general diagram of a serving cell with an UL-only TRP is shown in Figure 2, where an anchor TRP (TRP0) or DL / UL TRP 204 provides full coverage of a serving cell with both DL and UL transmissions and an UL-only TRP (TRP1) 206 is deployed at the cell edge to improve UL performance of cell edge UEs (e.g., UE 202). TRP 204 and TRP 206 (also referred to as “network nodes”) are connected to a gNB via an ideal backhaul link. A UE 202 in the cell may perform initial access and network connection via TRP 204. After initial access and / or network connection, if the UE 206 is closer to TRP 206 than to TRP 204, the gNB (e.g., network node 410 as shown in Figure 7) may direct the UE 202 to transmit towards the TRP 206. Alternatively, for UEs close to TRP 206, all UL transmissions including during initial access are via TRP 206. The presence of TRP 206 may be transparent to UEs in the cell. Due to UE mobility, the distance between UE and TRP 204 could be different from the distance between UE and TRP 206. It will be useful to configure UE with separate SRS resource sets and / or SRS resources targeting TRP 204 and TRP 206 respectively (SRS0 vs SRS1). To enable flexible power control for PUSCH and SRS transmissions, 4 separate Closed-Loop power control states can be associated to PUSCH0 / PUSCH1 / SRS0 / SRS1, respectively, with e.g., indices: • PUSCH0: Sri-PUSCH-ClosedLoopIndex = 0; • PUSCH1: Sri-PUSCH-ClosedLoopIndex = 1; • SRS0: SRSClosedLoopIdx = 0; or • SRS1: SRSClosedLoopIdx = 1.

[0056] Figure 3 shows a message sequence chart of a method for determining an UL transmission power for an UL Reference Signal (RS) targeting a UL-only network node in accordance with some embodiments of the present disclosure.

[0057] At step 302, the UE indicates during UE capability signaling support of UL-only node SRS power control loop(s). The UE capability signaling can for example contain one or more of the followings: • Indication of support of UL-only node; • Indication of Maximum number of Closed-Loop power control states for SRS which are separate from PUSCH the UE can be configured with; • Indication of support of triggering SRS and indication TPC in the same DCI format; • Indication of support of separateClosedLoop2 • Indication of using one or more of the dedicated DCI formats (DCI format 0_0 / 0_1 / 0_2 / 1_0 / 1_1 / 1_2) for TPC indication for SRS; o In one embodiment the UE capability signaling indicates support of TPC indication for SRS is using legacy DCI field in one or more of the DCI format 0_0 / 0_1 / 0_2 / 1_0 / 1_1 / 1_2; or o In one embodiment the UE capability signaling indicates support of one or more new fields are added to one or more of the DCI format 0_0 / 0_1 / 0_2 / 1_0 / 1_1 / 1_2, where the new field(s) are used for TPC indication for SRS.

[0058] In step 304, the network node 410 configures the UE a separate (not tied to PUSCH) UL RS Closed-Loop power control state(s) targeting UL-only TRP / node. This is referred to as the second separate UL RS Closed-loop power control state in response to a potential legacy separate UL RS Closed-loop power control state. The configuration for the second separate UL RS Closed-Loop power control state can for example comprise an initial / default transmit power associated to the UL-only and a list of relative power control adjustment values which can be indicated for example in DCI and used to adjust the transmit power. The configuration may further comprise UL signals / channels and / or UL / Joint TCI states that are associated with the second separate SRS Closed-Loop power control state.

[0059] In one embodiment the UL RS is an SRS. The SRS transmitted by the UE can be periodic, semi-persistent, or aperiodic. The SRS is configured in an SRS resource of an SRS resource set. There can be one or more SRS antenna ports in the SRS resource. The SRS resource or resource set can be configured with a set of power control parameters including at least a pathloss reference signal index and a closed-loop power control state index. The pathloss RS can be associated to and transmitted from the anchor TRP (i.e., TRP 204). In one alternative embodiment of step 302, the SRS is transmitted from different UL panels or SRS antenna ports. The different UL panels can be associated with different SRS resource sets. For a UE supporting only 1 UL transmission at a time, the SRS is transmitted from different panels on different symbols or slots. For a UE supporting 2 simultaneous UL transmissions, the SRS can betransmitted from 2 different UL panels at the same time. The transmission power of the both SRS transmission is associated with the DL-RS from the anchor TRP (i.e., TRP 204).

[0060] In one detailed embodiment, new higher layer (e.g., RRC) parameters are introduced in one or more of the following IEs as specified in 3GPP TS 38.331 (see bullet list below): • SRS resource set IE; • PUSCH config IE; • Physical Uplink Control Channel (PUCCH) resource Information Element (IE); or • Transmission Configuration Indicator (TCI)-UL-State IE.

[0061] where the new parameter indicates that the UE should apply a separate (not tied to PUSCH) Closed-Loop SRS power control state for a UL RS resource set or a UL TCI state (e.g. targeting an UL-only TRP / node).

[0062] In one embodiment, the UE is made aware by RRC configuration that the second separate closed-loop state for UL RS can be signaled in one of the UL scheduling DCI (e.g., DCI format 0_0 / 0_1 / 0_2) (either by re-purposing some of the legacy DCI fields, or by introducing one more new field(s)), see one example below where one or more of the parameters underlined are introduced in PUSCH Config IE: PUSCH-Config IE … betaOffsetsCrossPri1DCI-0-2-r17 SetupRelease { BetaOffsetsCrossPriSelDCI-0-2-r17 } OPTIONAL, -- Need M mappingPattern-r17 ENUMERATED {cyclicMapping, sequentialMapping} OPTIONAL, - - Cond SRSsets secondTPCFieldDCI-0-1-r17 ENUMERATED {enabled} OPTIONAL, -- Need R secondTPCFieldDCI-0-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R thirdTPCFieldDCI-0-1 ENUMERATED {enabled} OPTIONAL, -- Need R thirdTPCFieldDCI-0-2 ENUMERATED {enabled} OPTIONAL, -- Need R

[0063] In another embodiment, the UE is made aware by RRC configuration that the second separate closed-loop state for UL RS is signaled in one of the DL scheduling DCI (e.g., DCI format 1_0 / 1_1 / 1_2), (either by re-purposing some of the legacy DCI fields, or by introducing one more new field(s)), see one example below where one or more of the parameters underlined are introduced in PUCCH Config IE: PUCCH-Config IE … OPTIONAL, -- Need N secondTPCFieldDCI-1-1-r17 ENUMERATED {enabled} OPTIONAL, -- Need R secondTPCFieldDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R thirdTPCFieldDCI-1-1 ENUMERATED {enabled} OPTIONAL, -- Need RthirdTPCFieldDCI-1-2 ENUMERATED {enabled} OPTIONAL, -- Need R dl-DataToUL-ACK-r17 SetupRelease { DL-DataToUL-ACK-r17 } OPTIONAL, -- Need M dl-DataToUL-ACK-DCI-1-2-r17 SetupRelease { DL-DataToUL-ACK-DCI-1-2-r17} OPTIONAL, - - Need M …

[0064] Alternatively, in one embodiment there are still two legacy TPC fields in one or more of the DCI formats 1_1 / 1_2 / 0_1 / 0_2, and where one of the two legacy TPC fields are used to indicate the TPC command for a new second separated SRS close-loop power control state.

[0065] In one embodiment one or more new bitfield(s) is introduced in one or more of the DCI formats 1_1 / 1_2 / 0_1 / 0_2, where the one or more new bitfield(s) are used to indicate to the UE if one or more of the legacy TPC fields should be used to adapt the TPC for one or more of the SRS port control states (e.g. the new second separated SRS close-loop power control state)

[0066] In one detailed related embodiment, the usage of the secondTPCfield is dynamically indicated in the same DCI by a new single-bit bitfield, e.g., where the value “0” means legacy usage of the secondTPCField, while the value “1” means the secondTPCField is used to indicate TPC for the second separated SRS closed-loop power control state.

[0067] In a further detailed embodiment, the RRC can introduce a new state separateClosedLoop2 in srs-PowerControlAdjustmentStates in SRS-Config IE (alternatively, the separateClosedLoop2 can be configured in a new introduced RRC parameter in SRS config information element)

[0068] In some embodiment, the RRC configures the TPC fields in DCI 1_1 / 1_2 / 0_1 / 0_2 in SRS-Config IE by introducing a new flag for corresponding format, e.g. srs-TPCFieldDCI-1-1 for DCI 1-1. The new portions of the IE shown below or underlined: SRS-Config information element … usage ENUMERATED {beamManagement, codebook, nonCodebook, antennaSwitching}, alpha Alpha OPTIONAL, -- Need S p0 INTEGER (-202..24) OPTIONAL, -- Cond Setup pathlossReferenceRS PathlossReferenceRS-Config OPTIONAL, -- Need M srs-PowerControlAdjustmentStates ENUMERATED { sameAsFci2, separateClosedLoop, separateClosedLoop2} OPTIONAL, -- Need S srs-TPCFieldDCI-0-1 ENUMERATED {enabled} OPTIONAL, -- Need R srs-TPCFieldDCI-1-1 ENUMERATED {enabled} OPTIONAL, -- Need R ...,

[0069] Prior to step 306, the UE may transmit an UL signal / channel using either the initial / default transmit power of the corresponding UL-only node power control loop, if it is the first UL transmission associated with the UL-only node power control loop and / or no relative or absolute output power indication associated with the UL-only node Control-Loop power control has been received by the UE, or a transmit power calculated based on the initial / default transmit power and one or more relative or absolute transmit power indications in case one or more relative or absolute power indications associated with that UL-only node power control loop has been received by the UE.

[0070] In step 306, the network determines and indicates to the UE the change / adjustment of the transmit power for the UL RS to the UL-only node. The transmit power command can be conveyed in a Medium Access Control Control Element (MAC CE) or DCI.

[0071] In some embodiment, the TPC command of the one or more of the separate SRS Closed-loop states (legacy or new second separate closed loop power control state) can be signaled in one or more of the following dedicated DCI formats: • One of the UL scheduling DCI (e.g., DCI format 0_0 / 0_1 / 0_2); or • One of the DL scheduling DCI (e.g., DCI format 1_0 / 1_1 / 1_2).

[0072] In some embodiment, the dedicated DCI format can be used to indicate TPC for separate SRS closed-loop power control state in one or more of the following cases • Simultaneously providing TPCs for two separate SRS control states; • One separate SRS control state at a time; • Only the separate SRS control state #0; or • Only the separate STS control state #1.

[0073] In one embodiment, the DCI provision of closed-loop power control command to SRS targeting the UL-only TRP / node comprises one or more of • SRS request; • TPC commands; • Closed-Loop state Index / ID; • Path loss offset (e.g. a path loss offset introduced in Rel-19 for UL only node power control); o In one related embodiment, the DCI also indicates the UL-TCI state that the path loss offset is associated with.

[0074] In some embodiments, the TPC command for the second separate Close-Loop state can be signaled in the same DCI which provides UE the network received pathloss offset between the anchor TRP and the UL-only TRP.

[0075] In some embodiments, the legacy TPC fields for PUSCH or PUCCH transmission can be re-used to indicate TPCs for one or more separate SRS closed-loop power control states. In other words, if NW does not schedule PUSCH with DCI format 0_1 / 0_2 / 0_3, it can re-use some of the bits to indicate one or more of: • One or more separate closed-loop power control adjustment for SRS; • Open loop power control offset; o In a detailed embodiment, the associated UL TCI state is also indicated.

[0076] Similarly, if the NW does not schedule PDSCH for DCI format 1_1 / 1_2 / 1_3, it can re-use one or more fields / bits to indicate one or more of: • One or more separate closed-loop power control adjustment for SRS; • Open loop power control offset; o In a detailed embodiment, the associated UL TCI state is also indicated.

[0077] In some embodiments, aperiodic SRS is triggered with a DL DCI format, e.g., DCI 1_1, without PDSCH reception, • “SRS request” field is not set to “00”; and • indication of PDSCH not being scheduled, o the “Frequency domain resource assignment” (FDRA) field is set to all “0” s for FDRA type 0 or o the “Frequency domain resource assignment” (FDRA) field is set to all “0” s for FDRA type 1 or o the “Frequency domain resource assignment” (FDRA) field is set to all “0” s for FDRA type “dynamicSwitch” or o a new field in DCI indicating SRS only transmission.

[0078] In some embodiments UE ignores one or more of the fields used for indicating PDSCH reception, including one or more of the fields that has at least one bit in the DCI despite of RRC configuration: “Modulation and coding scheme”, “New data indicator”,” Redundancy version”, “HARQ process number”, “PUCCH resource indicator”, “TPC command for scheduled PUCCH”, “Antenna port(s)”, “DMRS sequence initialization”.

[0079] In some related embodiments some of these fields are re-used to indicate: • One or more separate closed-loop power control adjustment for SRS; • Open loop power control offset; o In a detailed embodiment, the associated UL TCI state is also indicated.

[0080] In some embodiments, the TPC field of PUCCH “TPC command for scheduled PUCCH” can also be used for providing TPC for separate SRS power control.

[0081] In some embodiment, aperiodic SRS is triggered with an UL DCI format, e.g. DCI 0_1, without PUSCH transmission i.e.: • “SRS request” field is not set to “00” and; • indication of PUSCH not being scheduled; o the “Frequency domain resource assignment" (FDRA) field is set to all “0”s for FDRA type 0 or; o the “Frequency domain resource assignment" (FDRA) field is set to all “0” s for FDRA type 1 or; o the “Frequency domain resource assignment" (FDRA) field is set to all “0” s for FDRA type “dynamicSwitch” or; o the “CSI request” field is set to all “0”s and “UL-SCH indicator” field is set to “0” when both fields are configured; or o a new field in DCI indicating SRS only transmission.

[0082] In some embodiments UE ignores the fields used for indicating PUSCH transmission, including one or more of fields that has at least one bit in the DCI despite of RRC configuration : “Modulation and coding scheme”, “New data indicator”,” Redundancy version”,” HARQ process number”,” 1st downlink assignment index”, “TPC command for scheduled PUSCH.

[0083] In some related embodiments some of these fields are re-used to indicate: • One or more separate closed-loop power control adjustment for SRS; • Open loop power control offset; o In a detailed embodiment, the associated UL TCI state is also indicated.

[0084] In some embodiments, the TPC field of PUSCH “TPC command for scheduled PUSCH” is re-used to provide TPC(s) for one or more of the separate SRS power control states.

[0085] In one embodiment, one or more of the ignored fields can be reused and be associated to SRS transmission, e.g., power updates.

[0086] In some embodiments, the SRS configuration usage is “beamManagement” or “antennaSwitching” when separate power control for SRS can be indicated in dedicated DCI.

[0087] In Step 308, the UE adapts the determined output power for UL RS targeting UL- only TRP.

[0088] In some embodiment the methods for separate SRS power control using dedicated DCI apply equally for UL-only TRP and anchor TRP.

[0089] Asymmetric DL sTRP UL mTRP has been endorsed as one of the features for NR MIMO Phase 5, with the following justification and objective:- Heterogeneous Network can be deployed to improve UL throughput. Since the macro gNB and micro nodes differ in power rating, a UE may receive DL transmission from the macro gNB, but transmit UL to either the macro gNB or non-co-located micro nodes in order to maximize UL throughput. As an option to further reduce energy consumption, the micro nodes can, for instance, reduce or even turn off DL transmissions. To support such deployment scenario, enhancements on UL power control (PC) would be useful. First, when pathloss RS is transmitted from the macro gNB and the UE transmits UL to the micro nodes, the pathloss measured from the pathloss RS from the macro gNB is not accurate. Therefore, it is necessary to configure the UE with pathloss offset to facilitate accurate calculation of the pathloss associated with the micro nodes. Second, an additional SRS closed-loop PC for DL CSI acquisition to the macro gNB (for DL transmission), separate from that for the SRS to the micro nodes (for UL mTRP reception) should be introduced. Therefore, there is a need for supporting two closed-loop PC adjustment states for SRS, both separate from PUSCH. - 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 TCI framework and fully reusing the legacy QCL / UL spatial relation rules, targeting FR1 and FR2. Two closed-loop PC adjustment states for SRS, both separate from PUSCH; and pathloss offset configurations for pathloss calculation to UL TRP(s), when the pathloss RS is from DL sTRP.

[0090] Figure 4 illustrates an asymmetric DL sTRP UL mTRP deployment. It consists of an Anchor TRP (providing both DL and UL service), and an UL-only TRP (only providing UL service), where the downlink reference signals and data transmissions for a UE are only provided from the Anchor TRP.

[0091] The main motivation for asymmetric DL sTRP UL mTRP deployment is to improve UL throughput at cell edge by UE transmitting UL date to the UL-only TRP. For example, the Anchor TRP in Figure 4 provides a full coverage of a serving cell with both DL and UL transmissions, and the UL-only TRP is deployed at the cell edge to improve UL performance of cell edge UEs. Other motivation is to reduce network energy consumption by avoid sending downlink data in the UL-only TRP. It is envisioned that a UE in the cell may perform initial access and network connection via the Anchor TRP. After initial access and when the UE is in the connected mode, if the UE is closer to the UL-only TRP than to the Anchor TRP (i.e. better UL link budget), or if the NW decides to move the UE to UL-only TRP, e.g., to reduce the UL interference for the Anchor TRP, or to improve resource usage efficiency, the NW may direct theUE to transmit towards the UL-only TRP. Enhancement on power control is useful to support the asymmetric deployment to fulfil these motivations.

[0092] In existing NR multi-TRP operation, it is assumed that each TRP can be used for both DL transmission and UL reception. Uplink power control can thus be based on the pathloss measurement of DL PL-RS from the same TRP which provides the DL service. Different pathloss for uplink and downlink arises when the power for uplink transmission toward UL-only TRP is based on pathloss measurement of DL PL-RS from the Anchor TRP. For supporting UL- only TRP in asymmetric multi-TRP deployment the following power control enhancement could be added: - Two closed-loop power control for SRS - Uplink power control with pathloss offset for path loss calculation.

[0093] Apart from the power control aspect, how to set the UL transmission timing towards the Anchor TRP and UL-only TRP, respectively, given the propagation delay difference between the Anchor TRP and the UL-only TRP is a secondary prominent that will impact the performance of the asymmetric TRP deployment. This propagation delay difference may exceed the range of one CP, if that happens, the Rel-18 two-TA scheme can be applied with minor specification modification.

[0094] In addition, multiple UL-only TRPs might be deployed per Anchor TRP, and the specified enhancements related to UL-only TRPs should preferably be applicable for all the following cases: - UE performs UL transmission to only the UL-only TRP - UE performs UL transmission to two different UL-only TRPs - UE performs UL transmission to one UL-only TRP and to the Anchor TRP

[0095] Uplink power control consists of two parts: open-loop power control and closed-loop power control. Open-loop power control is used to set the uplink transmit power based on a few factors such as pathloss estimation between the UE and a TRP in a serving cell, the target received UL power, channel / signal bandwidth, modulation and coding scheme (MCS), fractional power control factor, etc. The closed-loop power control is supposed to be work with power adjustments signalled in power control commands received from the gNB. The power control commands are typically determined based on the difference between the actual received power and a desired received power at the gNB. In legacy NR, a DL-RS is transmitted from each TRP, which is used by a UE to estimate the pathloss between the UE and the TRP. Each DL RS has an associated index for identifying it. For UL transmission based on the Rel-17 / 18 Unified TCI stateframework, power control can be performed separately per Joint / UL TCI state, i.e., independently for different TRPs. 1 For an UL channel or signal (e.g., PUSCH, PUCCH, or SRS) to be transmitted in UL associated with a pathloss RS with index ^^^^, its transmit power in a transmission occasion i within a slot in a bandwidth part (BWP) of a carrier frequency of a serving cell and a closed-loop index ^^^^ (^^^^ = 0,1) can be expressed aswhere ^^^^^^^^^^^^^^^^^^^^,^^^^,^^^^(^^^^) denotes a UE’s maximum output power for the carrier frequency, ^^^^, of the serving cell, ^^^^, in transmission occasion ^^^^ for the UL channel or signal, ^^^^^^^^^^^^^^^^^^^^−^^^^^^^^^^^^^^^^(^^^^,^^^^) is theopen-loop transmit power and ^^^^^^^^^^^^^^^^^^^^^^^^^^^^−^^^^^^^^^^^^^^^^(^^^^, ^^^^) is the closed-loop power adjustment.

[0096] As described above, the power control enhancement for UL-only TRP involves both open-loop power control and close-loop power control. 3 Considering first the open-loop power control, ^^^^^^^^^^^^^^^^^^^^−^^^^^^^^^^^^^^^^(^^^^,^^^^) in the transmission power equation in Section 2.1 is given by:5 where ^^^^^^^^is the nominal target receive power for the UL channel or signal and comprises a cell-specific part ^^^^^^^^,^^^^^^^^^^^^^^^^and a UE-specific part ^^^^^^^^,^^^^^^^^. Additionally, ^^^^^^^^^^^^(^^^^)is a power adjustment related to the bandwidth or number of RBs occupied by the channel or signal at transmission occasion ^^^^; and ^^^^^^^^(^^^^) is a pathloss (PL) estimation based on a DL-RS with index k; ^^^^ (0 < ^^^^ ≤ 1) is a fractional pathloss compensation factor; and ∆(^^^^) is a poweroffset determined by modulation and code rate of the UL channel or signal.

[0097] An UL-only TRP receives only and hence does not transmit any DL signals. Without a DL PL-RS transmission from an UL-only TRP, pathloss cannot be estimated in the existing NR framework to determine the UL power control for UL transmission towards UL-only TRP. It can be observed that it is possible for a UE to determine the pathloss for the UL-only TRP based on the pathloss of the Anchor TPR and a pathloss offset (^^^^^^^^∆[^^^^^^^^]) indicated by the NW:

[0098] As an illustrative example, the pathloss offset can be obtained by comparing the difference of UL RS RSRP received at the two TPRs, where the UL RS can be for example oneSRS resource transmitted from the UE. Denote the UL RS signal as UL-RS0, and the pathloss offset (^^^^^^^^∆[^^^^^^^^]) between PL0 (pathloss between UE and the Anchor TRP) and PL1 (pathloss between UE and the UL-only TRP) can be derived as ^^^^^^^^^^^^ = ^^^^^^^^^^^^^^^^1^^^^^^^^^^^^^^^^0 − ^^^^^^^^^^^^^^^^0^^^^^^^^^^^^^^^^0where ^^^^^^^^^^^^^^^^0^^^^^^^^^^^^^^^^0and ^^^^^^^^^^^^^^^^1^^^^^^^^^^^^^^^^0denote the received RSRP of UL-RS0 at the Anchor TRP (TRP0) and the UL-only TRP (TRP1), respectively. Generally speaking, the NW can also derive the pathloss offset based on multiple UL RS resources, or other UL signals / channels, such as PUCCH, or PUSCH. In our view how NW derives the pathloss offset should be based on network implementation and is transparent to UE.

[0099] According to RP-234007, the Rel-19 asymmetric DL sTRP and UL mTRP deployment assumes the Rel-17 / 18 unified TCI framework and fully re-use the legacy QCL / UL spatial relation rules, targeting FR1 and FR2.

[0100] The unified TCI state framework supports TCI configuration with one and only one of the two operation modes: “Joint DL / UL TCI” or “Separate DL / UL TCI”. For “Joint DL / UL TCI” one common Joint / DL TCI state (e.g., “DLorJoint-TCIState-r17”) is used for both DL and UL signals / channels, while for “Separate DL / UL TCI”, one common Joint / DL TCI is used for DL channels / signals and one common UL TCI state (e.g., UL-TCIState-r17) is used for UL signals / channels.

[0101] In the deployment of asymmetric DL sTRP UL mTRP, since the UL-only TRP does not transmit any DL signal / channel, it is natural to assume that UE can be configured with the “separate DL / UL TCI states”. For example in a (FR1) deployment as in Figure 4, UE can be configured with one DL TCI state towards the Anchor TRP, and two UL TCI states, towards the Anchor TRP and UL-only TRP, respectively.

[0102] In Rel-17, power control parameters (^^^^0,^^^^, closed-loop state index), and pathloss reference signal can be provided in the TCI state. This functionality is useful when the unified TCI framework is extended to mTRPs, since different TRPs would be associated with different TCI states, and it becomes trivial to associate different TRPs with different power control parameters. For instance, in the unified TCI state framework, a pathloss reference signal (PL-RS) is either included in or associated with a TCI state, which means the PL-RS is automatically updated when the TCI state is updated. This gives a good motivation to associate the new PL offset (^^^^^^^^∆) to an UL TCI state which is used for UL-only TRP.

[0103] Figure 5 illustrates an example of a procedure of how a UE can be configured to support UL-only TRP deployment. In this example it is assumed that the Anchor TRP willtransmit a single SSB (i.e. FR1), and that the UE has 2 TX chains and 2 RX chains with omni directional UE antennas: - After initial access, the UE receives RRC configurations for; - One SRS resource set with usage ‘codebook’ containing a single two-port SRS resource (SRS resource set 1) - The SRS resource set 1 is configured to follow the indicated / activated unified UL TCI state - Two TCI states associated with the Anchor TRP - One DL TCI and one UL TCI state associate using the SSB as QCL source RS (DL TCI state1 and UL TCI state1) - One UL TCI state associated with the UL-only TRP (UL TCI state 2) - UL TCI state 2 might be configured with the SRS resource from SRS resource set 1 as QCL RS - UL TCI state 2 might be configured / associated with a new introduced pathloss offset that can be used to facilitate UL power control for the UE towards the UL-only TRP - the UE is activated / indicated (using e.g. MAC-CE and / or DCI) with the TCI states associated with the Anchor TRP (i.e. DL TCI state 1 and UL TCI state 1), since the Anchor TRP still has not yet detected that the UE is within reach of the UL-only TRP. - the UE transmits the SRS resource set 1. The SRS resource set 1 is received at both the Anchor TRP and the UL-only TRP. The NW then detects that the SRS resource set 1 is received with stronger power at the UL-only TRP compared to the Anchor TRP, and therefore determines to establish UL transmission towards UL-only TRP instead of towards the Anchor TRP. - the NW indicates / activates UL TCI state targeting the UL-only TRP (i.e. UL TCI state 2) to the UE (using e.g. MAC-CE and / or DCI). As part of the previous step, the NW might indicate a pathloss offset associated with the UL TCI state 2, based on e.g., the difference in received power of SRS resource set 1 at the Anchor TRP and UL-only TRP. - the UE transmits SRS resource set 1 with an output power taking the pathloss offset into account (i.e. with a output power adapted towards the UL-only TRP). - the UE transmit PUSCH (associated with indicated / activated UL TCI state 2), using with an output power taking the pathloss offset into account (i.e. with a output power adapted towards the UL-only TRP).

[0104] It is noted that the pathloss reference signal for the Unified TCI state framework is semi-statically configured to an UL TCI state (using RRC signalling). When UE moves in the cell and the DL TCI state of the Anchor TRP changes, the statically configured pathloss referencesignal of the UL TCI state may not be the most suitable PL-RS and rapidly becomes outdated. In the worst case, UE might even not be able to receive the outdated PL-RS. In legacy, an update of the PL-RS associated with an UL TCI state requires an RRC reconfiguration which is a slow procedure. It is beneficial to support a dynamic update of the PL-RS associated to an UL TCI state, e.g., via a MAC CE message.

[0105] As described above, the NW could indicate the pathloss offset (^^^^^^^^∆) to UE for an estimation of the pathloss between UE and the UL-only TRP. The indicated pathloss offset should be common, and generally applicable to power control of all UL signals / channels, i.e., PUCCH / PUSCH / SRS / PRACH. Hence, a dynamic indication of PL offset via a MAC CE message seems to be logical. In addition, the UE should assume the initial value of the PL offset is 0 dB (until a MAC CE message indicates that a separate PL offset has been received).

[0106] As exemplified earlier, an UL RS (e.g., SRS) can be used by the NW to estimate the PL offset between the Anchor TRP and the UL-only TRP. It is therefore reasonable to determine the value range of PL offset based on the NR legacy value ranges of L1-RSRP measurement. Although the legacy L1-RSRP ranges (see e.g., RSRP-range and SRS-RSRP-range in TS 38.133 and TS 38.133) are specified for UE measurement and reporting, and a NW node is typically more capable than a UE. However, these legacy RSRP ranges should be still sufficient to specify the range for pathloss offset since for the purpose of UL power control the pathloss estimation is performed at the UE side.

[0107] Take an example of the SRS RSRP Range, the range is indicated as a list of integer IE values (0,…,98), where the mapping between SRS RSRP measurement and the integer IE values is specified in TS 38.133. The value range of the L1-RSRP measurement and reporting can be a natural start point to discuss the value range of the PL offset. However, it should be noted that, the L1-RSRP measurement is between -140dBm and -44dBm, i.e., all are negative values, whilst the PL offset is a difference between two SRS RSRPs which can be both positive and negative. Nevertheless, if the UE served by the UL-only TRP is always closer to the UL- only TRP than the Anchor TRP, the PL offset may always take positive values.

[0108] Compared to pathloss estimation based on a DL RS from the same TRP, there could be ambiguity issue with UE side pathloss estimation based on a DL RS from another TRP. In one example, if the NW does not have a qualified estimation of the PL offset, due to varies reasons, the UE may apply the latest indicated PL offset in UL power control.

[0109] Up to two closed power control loops can be configured in NR for each UL channel or signal. Either cumulative or non-cumulative closed-loop power adjustments are supported in NR. A closed loop adjustment at a given time is also referred as a power control adjustment state.6 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^−^^^^^^^^^^^^^^^^(^^^^, ^^^^) is given by:7 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^−^^^^^^^^^^^^^^^^(^^^^, ^^^^) =if cumulation is enabled^^^^(^^^^, ^^^^); if cumulation is disabled (i. e. , absolute is enable)8 where ^^^^(^^^^, ^^^^) is a power adjustment value indicated in a transmit power control (TPC)command in a DCI associated with the UL channel or signal at transmission occasion ^^^^ and configured with closed-loop index ^^^^;^^^^(^^^^, ^^^^) is a sum of power adjustmentindicated by the TPC commands.

[0110] In NR, SRS is used for providing Channel State Information (CSI) to the NW in the UL. The usage of SRS includes e.g., deriving the appropriated transmission / reception beams, performing link adaptation, and selecting DL and UL MIMO precoding. The transmit power of an SRS resource is described by9 The expression contains four terms: a constant term, a term that depends on the SRS bandwidth, a term that depends on the pathloss, and a term that depends on the closed-loop adjustment.

[0111] Each SRS resource set can be configured to either follow one of the two closed- loop power control states for PUSCH (sameAsFci1 and sameAsFci2, respectively), or follow a separate closed-loop power control state for only SRS transmission. In legacy, the separate closed-loop SRS power control state is indicated in the UE common DCI format 2_3 to providing the TPC commands. Following the legacy signaling framework, it is reasonable to introduce the second separate SRS closed-loop power control state to DCI format 2_3. Hence, the same DCI format can be used to indicate both separated (not tied to PDSCH closed-loop power control states) SRS closed-loop power control states, which is compatible to the legacy group common TPC provision for SRS power control.10 Using the UE common DCI format 2_3 for SRS power control is however cumbersome for UL-only TRP deployment because the SRS power control may be more flexible and dynamic to be used for establishing the uplink connection. Triggering of SRS transmission in DCI 1_1 / 0_1 and the provision of TPC for the separate SRS closed-loop power control state in DCI 2_3 is not an efficient signaling approach. Additionally, the UE common DCI format 2_3 used to provide the TPCs for multiple UE for SRS transmission has a limited number of TPC fields, that the size of DCI format 2_3 is limited by the size of DCI format 1_0. SRS triggering and SRS close-loop power control conveyed in a same UE dedicated DCI format 1_1 / 0_1 may be used. 11 For PUCCH, two Closed-Loop power control adjustment states are supported (both are independent from the Closed-Loops of PUSCH and SRS) and controlled by TPC commands indicated in same DCI format scheduling a PUCCH transmission (i.e., DCI format 1_0 / 1_1 / 1_2);for PUSCH, two Closed-Loop power control states are supported (independent of PUCCH) and TCP commands indicated in the same DCI format scheduling a PUSCH transmission (i.e., DCI format 0_0 / 0_1 / 0_2). Same functionality may be used also for SRS.

[0112] In NR, the UL signals / channel PUCCH / PUSCH / SRS transmission requires a proper timing advance (TA) control with respect to the DL reference timing. Multi-DCI based intra- cell multi-TRP operation introduced in Rel-16 and its extension inter-cell multi-TRP in Rel-17 both assume that the timing difference between signals received from the two TRPs is within a cyclic prefix (CP) length and that UE can transmit signals towards the two TRPs using the same timing advance (TA). To handle larger uplink timing differences (>CP) at a UE between two TRPs, the two-TA feature is introduced in Rel-18 for multi-DCI based multi-TRP, where separate timing advance control is supported and each can be applied to uplink transmission to a TRP. Difference between transmit timing to two TRP can be up to 34.5µs if UE supports the capability. According to the Rel-19 WID RP-234007, the asymmetric DL sTRP / UL mTRP deployment assumes intra-band intra-DU non-collocated mTRPs, hence the Rel-18 assumption on timing difference larger than CP is applied to the Rel-19 asymmetric mTRP scenario.

[0113] The Rel-18 two-TA feature is limited to mDCI based multi-TRP under Rel-18 unified TCI state framework. In addition, the Rel-18 two-TA feature relies on the legacy concept of a timing advance group (TAG), with enhancement that a UE can be configured with two TAGs in a serving cell. In more detailed description, each TAG is associated with UL transmission towards one of the two TRPs, where the mapping between UL channels / signals to a TAG is via the TCI state. Hence, a TA is applied to UL transmissions according to the TAGconfigured in the TCI state(s). The downlink timing refence signal of the TAG can be provided as a SSB signal configured in one of the TCI states associated to the TAG.

[0114] For UL-only TRP in Rel-19, the WID limits the scope to single-TRP operation in DL, and hence reusing the Rel-18 multi-DCI two-TA solution for UL-only TRP deployments seems to be an unnatural solution since multi-DCI multi-TRP operation is mainly motivated by DL multi-TRP operation with poor synchronization across DL TRPs. If we reuse the Rel-18 multi-DCI two-TA solution, a UE must support multi-DCI operation to support UL-only TRP operation, which is an unnecessary restriction.

[0115] Another option could be to adapt the Rel-18 multi-DCI based two-TA solutions to single-DCI operation. To do this, only minor changes for the Rel-18 two-TA solution may be needed, e.g. removing the association between a TAG and CORESETPooIndex, and using a single DL timing reference signal (from the Anchor TRP) for both TAs, instead of using two DL reference signals as in the Rel-18 multi-DCI two-TA solution.

[0116] A UE can be at different propagation delay w.r.t each TRP and after the initial transmit timing control (i.e., after performing PRACH), the UE can properly manage two separate TA loops to set UL timing towards the non-collocated TRPs, based on separate Timing Advance Commands, with respect to Anchor TRP DL timing reference. To enable two TAs with respect to two TRPs, UE may obtain DL reference timing and UL TA command towards UL-only TRP. In this section we further discuss the aspects of DL reference timing and UL TA towards the UL-only TRP. The two-TA feature in rel-18 assumes non-ideal synchronization (i.e., TRPs slot boundaries are not perfectly time aligned and there can be synchronization error of up to e.g., 3µs) between the TRPs. As per the WID, asymmetric and non-collocated deployment is supported for UL-only TRP. That means the synchronization assumptions in Rel-18 are applied for Rel-19 UL-only TRP also as operators may not deploy separate TRPs for using the UL-only TRP feature (e.g., operators may use same deployment for Rel-18 and 19).

[0117] As UL-only TRP do not transmit any SSB, UE may have to rely on Anchor TRP SSB to derive the DL reference timing. When slot boundaries of Anchor TRP and UL-only TRP are perfectly aligned in time (i.e., synchronization error is 0µs), UE may use the DL reference timing of Anchor TRP to perform random access procedure and obtain TA command to handle the asymmetric propagation delay difference between Anchor TRP to UE and UL-only TRP to UE.

[0118] However, in the practical deployments (such asymmetric deployments considered in this WI) it may not be always possible to maintain perfect synchronization between different TRP (even for intra-DU deployments as most of the NW deployments use something calledswitched fronthaul). Figure 6 illustrate synchronisation scenario where the timing of UL-only TRP is ahead of Anchor TRP. When UL-only TRP is ahead of Anchor TRP slot timing, when UE acquires DL timing from Anchor TRP and transmit PUSCH using the same DL reference timing, it may result in late arrival PUSCH at UL-only TRP.

[0119] Figure 7 shows an example of a communication system 400 in accordance with some embodiments.

[0120] In the example, the communication system 400 includes a telecommunication network 402 that includes an access network 404, such as a Radio Access Network (RAN), and a core network 406, which includes one or more core network nodes 408. The access network 404 includes one or more access network nodes, such as network nodes 410A and 410B (one or more of which may be generally referred to as network nodes 410), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs). In an embodiment, a network node 410, such as a base station can receive the UE capability information, and configure the UE as described in the message sequence chart in Figure 3. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 402 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 402 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 402, including one or more network nodes 410 and / or core network nodes 408.

[0121] Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O- CU-CP) or an O-CU User Plane (O-CU-UP), a RAN intelligent controller (near-real time or non- real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may beimplemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 410 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 412A, 412B, 412C, and 412D (one or more of which may be generally referred to as UEs 412) to the core network 406 over one or more wireless connections.

[0122] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 400 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 400 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0123] The UEs 412 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 410 and other communication devices. Similarly, the network nodes 410 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 412 and / or with other network nodes or equipment in the telecommunication network 402 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 402. In an embodiment, the UE 412 can be an example of the UE 202 as described in Figures 2 and 3.

[0124] In the depicted example, the core network 406 connects the network nodes 410 to one or more hosts, such as host 416. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 406 includes one more core network nodes (e.g., core network node 408) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 408. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF),Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0125] The host 416 may be under the ownership or control of a service provider other than an operator or provider of the access network 404 and / or the telecommunication network 402, and may be operated by the service provider or on behalf of the service provider. The host 416 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0126] As a whole, the communication system 400 of Figure 7 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 400 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.

[0127] In some examples, the telecommunication network 402 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 402. For example, the telecommunication network 402 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs, and / or massive Machine Type Communication (mMTC) / massive Internet of Things (IoT) services to yet further UEs.

[0128] In some examples, the UEs 412 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 404. Additionally, a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi-standard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).

[0129] In the example, a hub 414 communicates with the access network 404 to facilitate indirect communication between one or more UEs (e.g., UE 412C and / or 412D) and network nodes (e.g., network node 410B). In some examples, the hub 414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 414 may be a broadband router enabling access to the core network 406 for the UEs. As another example, the hub 414 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 410, or by executable code, script, process, or other instructions in the hub 414. As another example, the hub 414 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 414 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 414 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 414 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices.

[0130] The hub 414 may have a constant / persistent or intermittent connection to the network node 410B. The hub 414 may also allow for a different communication scheme and / or schedule between the hub 414 and UEs (e.g., UE 412C and / or 412D), and between the hub 414 and the core network 406. In other examples, the hub 414 is connected to the core network 406 and / or one or more UEs via a wired connection. Moreover, the hub 414 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 404 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 410 while still connected via the hub 414 via a wired or wireless connection. In some embodiments, the hub 414 may be a dedicated hub – that is, a hub whose primaryfunction is to route communications to / from the UEs from / to the network node 410B. In other embodiments, the hub 414 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and the network node 410B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0131] Figure 8 shows a UE 500 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged, and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0132] A UE may support Device-to-Device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle- to-Everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0133] The UE 500 includes processing circuitry 502 that is operatively coupled via a bus 504 to an input / output interface 506, a power source 508, memory 510, a communication interface 512, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 8. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0134] The processing circuitry 502 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 510. The processing circuitry 502 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 502 may include multiple Central Processing Units (CPUs).

[0135] In the example, the input / output interface 506 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 500. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0136] In some embodiments, the power source 508 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 508 may further include power circuitry for delivering power from the power source 508 itself, and / or an external power source, to the various parts of the UE 500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 508. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 508 to make the power suitable for the respective components of the UE 500 to which power is supplied.

[0137] The memory 510 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), ErasablePROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 510 includes one or more application programs 514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 516. The memory 510 may store, for use by the UE 500, any of a variety of various operating systems or combinations of operating systems.

[0138] The memory 510 may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High Density Digital Versatile Disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, Holographic Digital Data Storage (HDDS) optical disc drive, external mini Dual In-line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and / or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’ The memory 510 may allow the UE 500 to access instructions, application programs, and the like stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system, may be tangibly embodied as or in the memory 510, which may be or comprise a device-readable storage medium.

[0139] The processing circuitry 502 may be configured to communicate with an access network or other network using the communication interface 512. The communication interface 512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 522. The communication interface 512 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 518 and / or a receiver 520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 518 and receiver 520 may be coupled to one or more antennas (e.g., the antenna 522) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0140] In the illustrated embodiment, communication functions of the communication interface 512 may include cellular communication, WiFi communication, LPWANcommunication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, NFC, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.

[0141] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 512, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0142] As another example, a UE comprises an actuator, a motor, or a switch related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0143] A UE, when in the form of an IoT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application, and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- oritem-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and / or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 500 shown in Figure 8.

[0144] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0145] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator and handle communication of data for both the speed sensor and the actuators.

[0146] Figure 9 shows a network node 600 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged, and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment in a telecommunication network. Examples of network nodes include, but are not limited to, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O- CU).

[0147] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node), and / orRemote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a Distributed Antenna System (DAS).

[0148] Other examples of network nodes include multiple Transmission Point (multi-TRP) 5G access nodes, Multi-Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell / Multicast Coordination Entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0149] The network node 600 includes processing circuitry 602, memory 604, a communication interface 606, and a power source 608. The network node 600 may be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 600 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may in some instances be considered a single separate network node. In some embodiments, the network node 600 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 604 for different RATs) and some components may be reused (e.g., a same antenna 610 may be shared by different RATs). The network node 600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 600, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within the network node 600.

[0150] The processing circuitry 602 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic operable to provide, either alone or in conjunction with other network node 600 components, such as the memory 604, to provide network node 600 functionality.

[0151] In some embodiments, the processing circuitry 602 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 602 includes one or more of Radio Frequency (RF) transceiver circuitry 612 and baseband processing circuitry 614. In some embodiments, the RF transceiver circuitry 612 and the baseband processing circuitry 614 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the RF transceiver circuitry 612 and the baseband processing circuitry 614 may be on the same chip or set of chips, boards, or units.

[0152] The memory 604 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable, and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 602. The memory 604 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 602 and utilized by the network node 600. The memory 604 may be used to store any calculations made by the processing circuitry 602 and / or any data received via the communication interface 606. In some embodiments, the processing circuitry 602 and the memory 604 are integrated.

[0153] The communication interface 606 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 606 comprises port(s) / terminal(s) 616 to send and receive data, for example to and from a network over a wired connection. The communication interface 606 also includes radio front-end circuitry 618 that may be coupled to, or in certain embodiments a part of, the antenna 610. The radio front-end circuitry 618 comprises filters 620 and amplifiers 622. The radio front-end circuitry 618 may be connected to the antenna 610 and the processing circuitry 602. The radio front-end circuitry 618 may be configured to condition signals communicated between the antenna 610 and the processing circuitry 602. The radio front-end circuitry 618 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 618 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 620 and / or the amplifiers 622. The radio signal may then be transmitted via the antenna 610. Similarly, when receiving data, the antenna 610 may collect radio signals which are thenconverted into digital data by the radio front-end circuitry 618. The digital data may be passed to the processing circuitry 602. In other embodiments, the communication interface 606 may comprise different components and / or different combinations of components.

[0154] In certain alternative embodiments, the network node 600 does not include separate radio front-end circuitry 618; instead, the processing circuitry 602 includes radio front-end circuitry and is connected to the antenna 610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 612 is part of the communication interface 606. In still other embodiments, the communication interface 606 includes the one or more ports or terminals 616, the radio front-end circuitry 618, and the RF transceiver circuitry 612 as part of a radio unit (not shown), and the communication interface 606 communicates with the baseband processing circuitry 614, which is part of a digital unit (not shown).

[0155] The antenna 610 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 610 may be coupled to the radio front-end circuitry 618 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 610 is separate from the network node 600 and connectable to the network node 600 through an interface or port.

[0156] The antenna 610, the communication interface 606, and / or the processing circuitry 602 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node 600. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 610, the communication interface 606, and / or the processing circuitry 602 may be configured to perform any transmitting operations described herein as being performed by the network node 600. Any information, data, and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0157] The power source 608 provides power to the various components of the network node 600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 600 with power for performing the functionality described herein. For example, the network node 600 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 608. As a further example, the power source 608 may comprise a source of power in the form of a battery or battery pack which isconnected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0158] Embodiments of the network node 600 may include additional components beyond those shown in Figure 9 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 600 may include user interface equipment to allow input of information into the network node 600 and to allow output of information from the network node 600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 600.

[0159] Figure 10 is a block diagram of a host 700, which may be an embodiment of the host 416 of Figure 7, in accordance with various aspects described herein. As used herein, the host 700 may be or comprise various combinations of hardware and / or software including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 700 may provide one or more services to one or more UEs.

[0160] The host 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input / output interface 706, a network interface 708, a power source 710, and memory 712. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 5 and 6, such that the descriptions thereof are generally applicable to the corresponding components of the host 700.

[0161] The memory 712 may include one or more computer programs including one or more host application programs 714 and data 716, which may include user data, e.g. data generated by a UE for the host 700 or data generated by the host 700 for a UE. Embodiments of the host 700 may utilize only a subset or all of the components shown. The host application programs 714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, and heads-up display systems). The host application programs 714 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 700 may select and / or indicatea different host for Over-The-Top (OTT) services for a UE. The host application programs 714 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), etc.

[0162] Figure 11 is a block diagram illustrating a virtualization environment 800 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more Virtual Machines (VMs) implemented in one or more virtual environments 800 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 800 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0163] Applications 802 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 800 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0164] Hardware 804 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 806 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 808A and 808B (one or more of which may be generally referred to as VMs 808), and / or perform any of the functions, features, and / or benefits described in relation with some embodiments described herein. The virtualization layer 806 may present a virtual operating platform that appears like networking hardware to the VMs 808.

[0165] The VMs 808 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 806.Different embodiments of the instance of a virtual appliance 802 may be implemented on one or more of the VMs 808, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premise equipment.

[0166] In the context of NFV, a VM 808 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 808, and that part of the hardware 804 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs 808, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 808 on top of the hardware 804 and corresponds to the application 802.

[0167] The hardware 804 may be implemented in a standalone network node with generic or specific components. The hardware 804 may implement some functions via virtualization. Alternatively, the hardware 804 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 810, which, among others, oversees lifecycle management of the applications 802. In some embodiments, the hardware 804 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a RAN or a base station. In some embodiments, some signaling can be provided with the use of a control system 812 which may alternatively be used for communication between hardware nodes and radio units.

[0168] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based onthe obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box or nested within multiple boxes, in practice computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0169] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole and / or by end users and a wireless network generally.

[0170] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein. NUMBERED EMBODIMENTS 1. A method performed by a user equipment, UE, (202) for determining an uplink, UL, transmission power for an UL Reference Signal, RS, targeting a network node (206) that does not transmit a downlink, DL, signal or transmits a limited DL signal, the method comprising: receiving (304) a network configuration of a set of power control parameters associated with one or more closed-loop states; receiving (306) a message triggering a Sounding Reference Signal, SRS, transmission, wherein the message comprises a transmit power control command associated with the powercontrol parameters associated with the one or more closed-loop states; and determining (308) a transmit power for the SRS transmission based on the transmit power control command. 2. The method of embodiment 1, wherein the network configuration is received via Radio Resource Control, RRC, signaling. 3. The method of any of embodiments 1 to 2, wherein the power control parameters are per UL RS resource set. 4. The method of any of embodiments 1 to 3, wherein the power control parameters comprise one or more of: • an associated closed-loop state index; • a nominal or initial transmit power; or • a value range of the transmit power. 5. The method of any of embodiments 1 to 4, wherein the one or more closed-loop states are separate from closed-loop states of other UL channels. 6. The method of any of embodiments 1 to 5, wherein the power control parameters are introduced in one or more of the following information elements, IEs: • SRS Resource Set IE; • Physical Uplink Shared Channel configuration IE; • Physical Uplink Control Channel resource IE; or • Transmission Configuration Indicator UL State IE. 7. The method of embodiment 4, wherein the value range of the transmit power can be the same as a legacy transmit power control command, or different than the legacy transmit power control command. 8. The method of any of embodiments 1 to 7, wherein the message comprises one or more of a: • an SRS request; • a transmit power control command; or• a closed-loop state identifier. 9. The method of any of embodiments 1 to 8, wherein the message is received via downlink control information, DCI. 10. The method of embodiment 9, wherein the DCI can be one or more of UL scheduling DCI, or DL scheduling DCI. 11. The method of embodiment 10, wherein a transmit power control command of a separate SRS power control state is indicated in a new field or re-used in an existing field of the UL scheduling DCI or DL scheduling DCI. 12. The method of any of embodiments 1 to 11, wherein a location of a transmit power control command of a separate SRS power control state is shared with a transmit power control command of another UL signal or channel. 13. The method of embodiment 12, wherein an association of the transmit power control command to an UL signal or channel is provided by one or more of: • a higher layer configuration; • a flag in a same DCI format; • according to a specification; or • according to predefined rules. 14. The method of any of embodiments 1 to 13, wherein the transmit power control command is jointly indicated with an UL Reference Signal Received Power, RSRP, difference between multiple transmission reception points, TRPs. 15. The method of any of embodiments 1 to 14, wherein the transmit power control command indicates either an absolute power adjustment or a relative power adjustment. 16. The method of any of embodiments 1 to 15, further comprising: providing (302), to another network node (204), UE capability information. 17. A user equipment, UE, (202) for determining an uplink, UL, transmission power for anUL Reference Signal, RS, targeting a network node (206) that does not transmit a downlink, DL, signal or transmits a limited DL signal, the UE (202) comprising a radio interface and processing circuitry configured to: receive (304) a network configuration of a set of power control parameters associated with one or more closed-loop states; receive (306) a message triggering a Sounding Reference Signal, SRS, transmission, wherein the message comprises a transmit power control command associated with the power control parameters associated with the one or more closed-loop states; and determine (308) a transmit power for the SRS transmission based on the transmit power control command 18. The UE (202) of embodiment 17, wherein the processing circuitry is configured to perform any of the methods of embodiments 2 to 16.CLAIMS 1. A method performed by a wireless device (202, 412, 500) for adapting a transmission power of an uplink, UL, Reference Signal, RS, transmission targeting a network node (204, 206, 410, 600), the method comprising: receiving (304) a network configuration of at least one UL RS closed-loop power control state; receiving (306) a message triggering the UL RS transmission, wherein the message comprises a transmission power control command for one of the at least one UL RS closed-loop power control state; and adapting (308) the transmission power of the UL RS transmission based on the transmission power control command. 2. The method of claim 1, wherein the message is a dedicated wireless device message scheduling an UL or downlink, DL, shared channel. 3. The method of any of claims 1-2, wherein the message further comprises a transmission power control command associated with an UL channel closed-loop power control state. 4. The method of any of claims 1-3, wherein the at least one closed-loop power control state is separate from closed-loop power control states of other UL channels and / or signals. 5. The method of claim 4, wherein the at least one closed-loop power control state is separate from closed-loop power control states of a physical uplink shared channel, PUSCH, and a physical uplink control channel, PUCCH. 6. The method of any of claims 1-5, wherein the at least one UL RS closed-loop power control state comprises two or more UL RS closed-loop power control states, and wherein the message further comprises a closed-loop state identifier, identifying the UL RS closed-loop power control state that the transmission power control command applies to. 7. The method of any of claims 1-6, further comprising: providing (302), to a network node, wireless device capability information indicating support of a separate closed-loop power control state for the UL RS and / or support for using one

Claims

or more dedicated wireless device message for a separate transmission power control command for the UL RS.

8. The method of any of claims 1-7, wherein the message is received via downlink control information, DCI.

9. The method of claim 8, wherein the DCI is a DCI format 1_1.

10. The method of any of claim 1-9, wherein the UL RS is a sounding reference signal, SRS.

11. The method of any of claims 1-10, wherein the transmission power control command indicates an absolute power adjustment or a relative power adjustment.

12. The method of any of claims 1-11, wherein the network configuration is received via Radio Resource Control, RRC, signaling.

13. The method of any of claims 1-12, wherein the network node is an UL / DL anchor TRP (204, 410, 600) or an UL-only TRP (206).

14. A wireless device (202, 412, 500) for adapting a transmission power of an uplink, UL, Reference Signal, RS, transmission targeting a network node (204, 206, 410, 600), the wireless device (202, 412, 500) comprising a communication interface (512) and processing circuitry (502) configured to: receive a network configuration of at least one UL RS closed-loop power control state; receive a message triggering the UL RS transmission, wherein the message comprises a transmission power control command for one of the at least one UL RS closed-loop power control state; and adapt the transmission power of the UL RS transmission based on the transmission power control command.

15. The wireless device (202, 412, 500) of claim 14, wherein the communication interface (512) and processing circuitry (502) is further configured to perform the method of any one of claim 2 to 12.

16. A method performed by a network node (204, 410, 600) for adapting a transmission power of an uplink, UL, Reference Signal, RS, transmission from a wireless device (202, 412, 500), the method comprising: transmitting (304) a network configuration of at least one UL RS closed-loop power control state; and transmitting (306) a message triggering the UL RS transmission, wherein the message comprises a transmission power control command for one of the at least one UL RS closed-loop power control state for adapting the transmission power of the UL RS transmission.

17. The method of claim 16, wherein the message is a dedicated wireless device message scheduling an UL or downlink, DL, shared channel.

18. The method of any of claims 16-17, wherein the message further comprises a transmission power control command associated with an UL channel closed-loop power control state.

19. The method of any of claims 16-18, wherein the at least one closed-loop power control state is separate from closed-loop power control states of other UL channels and / or signals.

20. The method of claim 19, wherein the at least one closed-loop power control state is separate from closed-loop power control states of a physical uplink shared channel, PUSCH, and a physical uplink control channel, PUCCH.

21. The method of any of claims 16-20, wherein the at least one UL RS closed-loop power control state comprises two or more UL RS closed-loop power control states, and wherein the message further comprises a closed-loop state identifier, identifying the UL RS closed-loop power control state that the transmission power control command applies to.

22. The method of any of claims 16-21, further comprising: receiving (302), from the wireless device (202, 412, 500), wireless device capability information indicating support of a separate closed-loop power control state for the UL RS and / or support for using one or more dedicated wireless device message for a separate transmission power control command for the UL RS.

23. The method of any of claims 16-22, wherein the message is transmitted via downlink control information, DCI.

24. The method of claim 23, wherein the DCI is a DCI format 1_1.

25. The method of any of claim 16-24, wherein the UL RS is a sounding reference signal, SRS.

26. The method of any of claims 16-25, wherein the transmission power control command indicates an absolute power adjustment or a relative power adjustment.

27. The method of any of claims 16-26, wherein the network configuration is transmitted via Radio Resource Control, RRC, signaling.

28. A network node (204, 410, 600) for adapting a transmission power of an uplink, UL, Reference Signal, RS, transmission from a wireless device (202, 412, 500), the network node (204, 410, 600) comprising a communication interface (606) and processing circuitry (602) configured to: transmit a network configuration of at least one UL RS closed-loop power control state; and transmit a message triggering the UL RS transmission, wherein the message comprises a transmission power control command for one of the at least one UL RS closed-loop power control state for adapting the transmission power of the UL RS transmission.

29. The network node (204, 410, 600) of claim 28, wherein the communication interface (606) and processing circuitry (602) is further configured to perform the method of any one of claim 17 to 27.

Images