Methods and nodes for indicating pathloss offset compensation for UL transmissions

Abstract

There is provided a method performed by a wireless device. The method comprises: receiving a first message comprising a configuration related to a first pathloss offset; receiving a second message comprising an indication to enable / disable application of the first pathloss offset in a transmit power calculation; and determining a transmit power based on the configuration and the indication. A wireless device implementing this method is also provided.

Description

Methods and nodes for indicating pathloss offset compensation for UL transmissions RELATED APPLICATIONS

[0001] This application claims the benefits of priority of US 63 / 558,695, entitled “indication of pathloss offset compensation for UL transmission” and filed at the USPTO on February 28, 2024, which is hereby incorporated by reference in its entirety. TECHNICAL FIELD

[0002] This application relates to communication networks and more particularly to methods and apparatuses / nodes for reporting coherent joint transmission (CJT) Channel State information (CSI) with time and frequency pre-compensation. BACKGROUND

[0003] Uplink (UL) power control in New Radio (NR)

[0004] A base station / gNB may consist of a single transmission and reception point (TRP) or multiple TRPs. In case of multiple TRPs, a User Equipment (UE) can be scheduled with Downlink (DL) transmissions from one or more of the TRPs and UL data transmission to one or more of the TRPs, either one TRP at a time or simultaneously.

[0005] 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 UL 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.

[0006] 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.

[0007] 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.

[0008] For a UL channel or signal (e.g., Physical UL Shared Channel (PUSCH), Physical UL Control Channel (PUCCH), or Sounding reference Signal (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 as

[0009] where ^^^ெ^^,^,^^^^^ is a UE’s maximum output power for the carrier frequency, f, ofthe serving cell, c, in transmission occasion ^^ for the UL channel or signal. ^^^^^^ି^^^^^^^, ^^^ isthe open loop transmit power and ^^^^^^^ௗି^^^^^^^, ^^^ is the closed loop power adjustment.

[0010] ^^^^^^ି^^^^^^^, ^^^ is given by:

[0011] 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 Resource Blocks (RBs) occupied by the channel or signal at transmission occasion ^^, ^^^^^^^^ is a pathloss (PL) estimation based on a DL RS with index k,^^ ^0 ^ ^^ ^ 1^ is a fractional pathloss compensation factor, and ∆^^^^ is a power offset determinedby modulation and code rate of the UL channel or signal.

[0012] ^^^^^^^ௗି^^^^^^^, ^^^ is given by:if cumulation is enabled^^^^^, ^^^; if cumulation is disabled ^i. e. , absolute is enable^

[0013] 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 ^^ andconfigured with closed-loop index ^^;^^^^^, ^^^ is a sum of power adjustment values indicatedin TPC commands that the UE received for the channel or signal since the TPC command fortransmission occasion ^^ െ ^^^.

[0014] 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.

[0015] Sounding reference signal (SRS)

[0016] In NR, SRS is used for providing Channel State Information (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 MCS), and for selecting DL (e.g., for Physical DL Shared Channel (PDSCH) transmissions) and UL (e.g., for PUSCH transmissions) multiple input multiple output (MIMO) precoding.

[0017] In Long Term Evolution (LTE) and NR, the SRS is configured via Radio Resource Control (RRC), where parts of the configuration can be updated (for reduced latency) through Medium Access Control (MAC)-Control Element (CE) signaling. The configuration includes, forexample, 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 DL Control Information (DCI) in the Physical DL Control Channel (PDCCH) which instructs the UE to transmit the SRS once, at a predetermined time.

[0018] When configuring SRS transmissions, the gNB configures, through the SRS-Config information element (IE), a set of SRS resources and a set of SRS resource sets, where each SRS resource set contains one or more SRS resources.

[0019] Quasi co-located (QCL) and Transmission Configuration Indicator (TCI) states

[0020] In NR, several signals can be transmitted from different antenna ports of a same base station. These signals can have the same large-scale properties such as Doppler shift / spread, average delay spread, or average delay. These antenna ports are then said to be quasi co-located (QCL).

[0021] If the UE knows that two antenna ports are QCL with respect to a certain parameter (e.g. Doppler spread), the UE can estimate that parameter based on one of the antenna ports and apply that estimate for receiving signal on the other antenna port.

[0022] To introduce dynamics in beam and transmission point (TRP) selection, the UE can be configured through RRC signaling with up to 128 TCI states. The TCI state IE can be found in 3GPP TS 38.331 v The gNB can use DCI format 1_1 or 1_2 to indicate to the UE that it shall use one of the activated TCI states for the subsequent PDSCH reception. The field being used in the DCI is Transmission configuration indication, which is 3 bits if tci-PresentInDCI is “enabled”or tci-PresentForDCI-Format1-2-r16 is present respectively for DCI format 1_1 and DCI 1_2 by higher layer.

[0023] In third generation partnership project (3GPP) Rel-17, a new unified TCI state framework is specified, which aims to streamline the indication of transmit / receive spatial filter (and other QCL properties) to the UE by letting a single TCI state indicate QCL properties for multiple different DL and / or UL signals / channels.

[0024] The unified TCI state framework of Rel-17 can be RRC configured in one out of two modes of operation “Joint DL / UL TCI” or “Separate DL / UL TCI”. For “Joint DL / UL TCI” operation, one common Joint TCI state is used for both DL and UL signals / channels. For “Separate DL / UL TCI” operation, one common DL-only TCI state is used for DL channels / signals, and one common UL-only TCI state is used for UL signals / channels.

[0025] It is expected that “Joint DL / UL TCI” operation will be the most common use case (see an example in Fig.1), but “Separate DL / UL TCI” operation can be useful in specific scenarios where the optimal DL beam differs from optimal UL beam. For “Separate DL / UL TCI” operation, up to two TCI states can be activated per TCI codepoint, one for DL signals / channels (DL-only TCI state) and one for UL signals / channels (UL-only TCI state). One schematic example of how this may look is illustrated in Fig.2. In case the TCI codepoint is “0”, the UE should apply “DL- only TCI state 3” as common QCL source for DL signals / channels, and not update the QCL source for UL signals channel. In case the TCI codepoint is “7”, the UE should apply “UL-only TCI state 57” as QCL source for UL signals / channels, and not update the QCL source for DL signals / channel. In case the TCI codepoint is “2”, the UE should apply “DL-only TCI state 9” as QCL source for DL signals / channels and apply “UL-only TCI state 1” as QCL source for UL signals / channels.

[0026] The existing DCI formats 1_1 and 1_2 in NR are reused (as in Rel-15 / 16 beam management framework) for beam indication, both with and without DL assignment.

[0027] UL-only nodes

[0028] 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, vehicle to vehicle (V2V) communications, etc.

[0029] 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). Such a transmission node is be referred to 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 DL 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 the NR MIMO Rel- 19 WID RP-234007, New WID: NR MIMO Phase 5, Samsung, RAN#102, Edinburgh, Scotland, December 2023] where the power control for frequency range 1 (FR1) and FR2 will be enhanced to better support UL-only nodes. SUMMARY

[0030] There currently exist certain challenge(s). In existing NR multi-TRP operation, it is assumed that each node can be used for both DL transmission and UL reception. For NR Rel-19,the idea of deploying UL-only nodes in a cell has been proposed. UL-only nodes may be useful in following scenarios:

[0031] - UL-only nodes deployed at the cell edge to provide better UL coverage for cell edge UEs.

[0032] - UL-only node deployed in a Time Division Duplex (TDD) band where there is dominant UL allocation.

[0033] - UL-only node deployed in a band that can only be used for UL transmission due to regulatory issues.

[0034] - UL-only node deployed for network energy saving.

[0035] An UL-only node receives only and does not transmit any DL signals. For this reason, it can also be referred to as UL-only reception point (RP). However, one issue with enabling UL- only node is UL power control for UL transmissions to those nodes. In NR, UL power control is based on the DL pathloss computation at the UE (e.g., based on the pathloss computed from DL PL-RS). It has been disclosed how to derive pathloss between a UE and UL-only TRP based on measurements done by the network (NW). However, methods / solutions are needed to determine how the NW configures and indicates the pathloss offset. In particular, in FR2 (potentially also in FR1), if the UE uses a SRS resource as a QCL reference signal for UL TCI states both to the Anchor TRP and the UL-only TRP, and the UE is configured with DCI based updates of indicated TCI states (i.e. by setting the RRC parameter tci-PresentInDCI to enabled as specified in TS 38.331 version 17.2.0), then, depending on UE rotation / movements, the TCI state the UE should use for UL transmission to the Anchor node and / or to the UL-only node might be updated frequently using DCI. In this case, it might be too slow to use higher layer (RRC or MAC CE) messages to enable / disable pathloss offset compensation associated with an UL-TCI state (if the UL-TCI state is used for Anchor TRP, the pathloss offset should be disabled, and if the UL-TCI state is used for the UL-only node the pathloss offset should be enabled). As a note, an anchor node / TRP refers to a node that can perform both UL and DL transmissions.

[0036] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.

[0037] The disclosure describes exemplary methods to enable / disable dynamic indication of application of pathloss offset for an indicated TCI state, depending on if the TCI state is used by / for the Anchor node, or the UL-only node.

[0038] There is provided a method in a wireless device or UE for determining UL transmission power for a UL channel or signal. For example, the method comprises: receiving a first message comprising a configuration related to a first pathloss offset; receiving a secondmessage comprising an indication to enable / disable application of the first pathloss offset in a transmit power calculation; and determining a transmit power based on the configuration and the indication. There is also provided a method in a network for receiving a UL transmission with a determined transmit power. For example, the method comprises: sending a first message to a wireless device, the first message comprising a configuration related to a first pathloss offset; sending a second message comprising an indication to enable / disable application of the first pathloss offset in a transmit power calculation; and receiving a transmission with a transmit power determined based on the configuration and the indication.

[0039] Corresponding UE / wireless device and network node are provided to perform these methods, respectively.

[0040] Certain embodiments may provide one or more of the following technical advantage(s).

[0041] The solutions enable a dynamic application of pathloss offset compensation for a UE to estimate pathloss of an UL-only node due to frequent changes of the TCI states e.g., in FR2. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Exemplary embodiments will be described in more detail with reference to the following figures, in which:

[0043] Fig. 1 illustrates an example of activated TCI states and their mapping to TCI field codepoints for “Joint DL / UL TCI”.

[0044] Fig. 2 illustrates an example of activated TCI states and their mapping to TCI field codepoints for “Separate DL / UL TCI”.

[0045] Fig.3 illustrates an example of a UE communicating with a serving cell with an anchor TRP0 and an UL-only TRP1 using two panels.

[0046] Fig.4 illustrates a method for computing a pathloss by a UE.

[0047] Fig.5 illustrates an example of TCI configurations and signaling for deployment with UL-only node at FR2, for example, according to an embodiment.

[0048] Fig.6 illustrates a schematic deployment related to the flowchart described in Fig.5.

[0049] Fig. 7 illustrates a flow chart of a method from the UE perspective, according to an embodiment.

[0050] Fig.8 illustrates an example of a MAC CE used to indicate a pathloss offset, according to an embodiment.

[0051] Fig. 9 illustrates an example of a flow chart of a method in a UE, according to an embodiment.

[0052] Fig.10 illustrates an example of a flow chart of a method in a network node, according to an embodiment.

[0053] Fig.11 illustrates an example of a proprietary solution where the two sets of UL TCIs are configured to the UE, according to an embodiment.

[0054] Fig.12 shows an example of a communication system, according to an embodiment.

[0055] Fig.13 shows a schematic diagram of a UE, according to an embodiment.

[0056] Fig.14 shows a schematic diagram of a network node, according to an embodiment.

[0057] Fig.15 illustrates a block diagram illustrating a virtualization environment. DETAILED DESCRIPTION

[0058] 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.

[0059] In this disclosure, the terms UL-only node, UL-only TRP, UL-only Receive Point (RP) are exchangeable.

[0060] A general diagram of a serving cell with an UL-only node is shown in Fig.3, where an anchor node (TRP0) 10 provides a full coverage of a serving cell with both DL and UL transmissions and an UL-only node (TRP1) 12 is deployed, e.g., at the cell edge to improve UL performance of cell edge UEs. TRP0 and TRP1 are connected to a gNB (not shown) via an ideal backhaul link, for example. A UE 14 in the cell may perform initial access and network connection via TRP0. After initial access and / or network connection, if the UE 14 is closer to TRP1 than to TRP0 or if the gNB decides to move the UE 14 to TRP1, e.g., to reduce the UL interference for TRP0 or to improve resource usage efficiency, the gNB may direct the UE 14 to transmit towards the TRP1. Alternatively, instead of performing initial access via TRP0, for UEs close to TRP1, all UL transmissions including the ones in initial access can be performed via TRP1. The presence of TRP1 may be transparent to UEs in the cell. Due to UE mobility and depending on the deployment, the distance between the UE and TRP0 could be considerably different from the distance between the UE and TRP1. It will be useful to configure UE with separate UL-RSs (e.g., SRS resource sets and / or SRS resources) targeting TRP0 and TRP1 (SRS0 vs SRS1 in Fig.3).

[0061] In the following, the first node refers to a node with UL-only capabilities (such as for example TRP1 of Fig.3). The second node, or sometimes referred to as Anchor node, refers to a node with both DL and UL capabilities (such as TRP0 of Fig.3).

[0062] A general description of how a UE estimates the pathloss between the UE and the UL- only node, and determines the transmit power for an UL channel / signal towards the UL-only node, includes the following steps and is illustrated in the signal diagram 20 of Fig.4:

[0063] Step 1: the NW (or gNB) configures the UL-only node and the default pathloss reference RS associated with the transmission to the UL-only node to derive the transmission power to the UL-only node. The configuration can be sent to the UE via RRC or via other signals or via other configuration mechanisms, as known in the art.

[0064] Step 2: the UE transmits UL signal(s) to both the first (e.g., UL-only node) and the second (e.g., the anchor node) in the same or different slots.

[0065] Step 3: the NW computes the pathloss offset, i.e., the pathloss difference related to the first and the second nodes, based on e.g., UL received power (UL Reference Signal Received Power (RSRP)) at each of the two nodes.

[0066] There are different ways that the NW can compute the pathloss offset. In one example, denote the first UL signal as UL RS0 that is targeting the anchor TRP, whilst the second UL signal (UL RS1) is targeting the UL-only TRP. The pathloss offset ^^^^௱between PL0 (between UE and the anchor TRP) and PL1 (between UE and the UL-only TRP) is given by ^^^^௱ ൌ ^^^^^^^^1^^ோௌ^ െ ^^^^^^^^0^^ோௌ^ െ ^^^^^^ோௌ ^^^^^^

[0067] where ^^^^^^ோௌ ൌ ^^^^ோௌ^ െ ^^^^ோௌ^ is the difference in the transmit power ^^^^ோௌ^and^^^^ோௌ^, respectively; ^^^^^^^^0^^ோௌ^and ^^^^^^^^1^^ோௌ^denote the received RSRP of UL-RS0 at TRP0 and RSRP of UL-RS1 at TRP1, respectively. In the simplest case, the pathloss offset can be derived as: ^^^^௱ ൌ ^^^^^^^^1^^ோௌ^ െ ^^^^^^^^0^^ோௌ^ ^^^^^^

[0068] assuming the same UL RS0 is received by both the anchor TRP and the UL-only TRP.

[0069] Step 4: the NW signals the pathloss offset to the UE.

[0070] Step 5: the UE computes a pathloss associated with the anchor node (referred to as a second pathloss) based on a DL-RS transmitted from the second node.

[0071] Step 6: the UE computes an updated pathloss associated with the UL-only node (referred to as an updated first pathloss) based on the second pathloss, and the latest pathloss offset signaled / received from the NW.

[0072] Step 7: the UE computes a transmit power for an UL channel / signal towards the UL- only node based on the computed updated pathloss in step 6.

[0073] Step 8: the UE transmits the UL channel / signal with the computed transmit power.

[0074] The present disclosure describes the update of the pathloss or pathloss offset of Step 6 to derive the pathloss between the UE and UL-only TRP.

[0075] Fig.5 depicts an example of TCI state configuration and signaling scenario 50 for a schematic simplified deployment as shown in Fig. 6, where the Anchor node TRP010 has two SSBs, and the UE 14 has four UE beams, each associated with an SRS resource of an SRS resourceset (SRS set1) with usage Beam Management (BM). The examples below are mainly based on “separate DL / UL TCI states”, but the subsequent embodiments are also applicable to the “joint TCI states”.

[0076] In Step 52, the UE is RRC configured with DL and UL TCI states, where one UL TCI state is configured per SRS resource of SRS resource set1, for example. Furthermore, each UL- TCI state is configured with a pathloss offset, which the UE should be using when communicating with the UL-only node.

[0077] In Step 54, the network trigger transmission of SRS set1 by the UE, to determine suitable UL beam pair link(s) between the UE and / or the Anchor / UL-only TRP.

[0078] In Step 56, the network has determined that UL TCI state1 gives good performance for UL-only node and indicates that TCI state to the UE for upcoming UL communications.

[0079] In some examples, depending on which codepoint of the TCI bitfield in the DCI that is used to indicate the UL TCI state, the UE knows if it should apply the pathloss offset associated with the UL TCI state or not. In one example, M codepoints of the TCI state field in the DCI are assumed, the first X of the codepoints of the TCI state bitfield in the DCI is associated with enabling the pathloss offset associated with that UL-TCI state for UL transmissions with that UL- TCI state, and the last M-X codepoints in the TCI state bitfield in the DCI is associated with not enabling the pathloss offset associated with that UL-TCI state for UL transmission with that UL- TCI state (or vice versa, i.e. first X of the codepoints of the TCI state bitfield in the DCI is associated with not enabling the pathloss offset associated with that UL-TCI state for UL transmission with that UL-TCI state, and the last M-X codepoints in the TCI state bitfield in the DCI is associated with enabling the pathloss offset associated with that UL-TCI state for UL transmission with that UL-TCI state).

[0080] In some examples, which codepoints that are associated with enabling or not enabling the pathloss offset can be RRC configured.

[0081] In Step 58, the NW triggers the UE with UL transmission. In one example, the DCI used to trigger the UL transmission contains a new bitfield used to indicate if the pathloss offset of the indicated UL-TCI state (or UL TCI state associated with the triggered UL transmission) should be applied by the UE or not.

[0082] In Step 60, the UE transmits the triggered UL transmission using the indicated UL TCI state, while applying the pathloss offset (i.e. the UE has been indicated in either Step 56 or Step 58 that it should use the pathloss offset).

[0083] In Step 62, the UE rotates.

[0084] In Step 64, the UE is triggered with a transmission of SRS set1. The NW now determines that the UE beam associated with UL TCI state1 is pointing towards Anchor TRP, and it is now the currently strongest beam pair link between the UE and the Anchor TRP / UL-only node TRP.

[0085] In Step 66, the UE is triggered with UL transmission. The trigger DCI indicates that the UE should not apply the pathloss offset for the triggered UL transmission.

[0086] In Step 68, the UE transmits the triggered UL transmission using the indicated UL TCI state, while disabling the associated pathloss offset.

[0087] Fig.7 illustrates a more detailed solution on the update of the pathloss offset which is indicated to the UE to estimate the pathloss between the UE and UL-only node. Fig.7 depicts a flowchart 100 of the proposed scheme from the UE perspective.

[0088] In step 110, the UE receives higher layer configurations regarding pathloss calculation, e.g., the pathloss reference signal (PL-RS), and pathloss offset, etc.

[0089] In some examples, the configuration of the pathloss offset is included in the configuration of the UL / joint TCI state, e.g., TCI-UL-state IE, or TCI-state IE. In some examples, if a “joint” or “separate” unified TCI states are used for an UL-only TRP, the DL TCI state may not need to be used.

[0090] In some examples, a flag can be configured optionally in an TCI-UL-state IE (or a TCI-state IE) as defined in 3GPP TS 38.331. If the flag is configured (e.g. set to be true), the UE should apply a pathloss offset associated with that UL TCI state. The default pathloss offset value when the flag is configured can be set to 0 or another fixed value, either pre-configured using RRC or pre-configured according to specification. In some examples, some TCI states belong to a neighbour cell and have an associated PCI of the neighbor cell.

[0091] In some examples, multiple pathloss offsets can be configured to a serving cell where a pathloss offset index / identifier is provided in the TCI-UL-State IE (or TCI-state IE), see an example below. TCI-UL-State The IE TCI-UL-State indicates the TCI state information for UL transmission. TCI-UL-State information element -- ASN1START -- TAG-TCI-UL-STATE-START TCI-UL-State-r17 ::= SEQUENCE { tci-UL-StateId-r17 TCI-UL-StateId-r17, servingCellId-r17 ServCellIndex OPTIONAL, -- Need R bwp-Id-r17 BWP-Id OPTIONAL, -- Cond CSI-RSorSRS-IndicatedreferenceSignal-r17 CHOICE { ssb-Index-r17 SSB-Index, csi-RS-Index-r17 NZP-CSI-RS-ResourceId, srs-r17 SRS-ResourceId }, additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL, -- Need R ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL, -- Need R pathlossReferenceRS-Id-r17 PathlossReferenceRS-Id-r17 OPTIONAL, -- Cond Mandatory pathlossOffset-Id-r19 PathlossOffset-Id-r19 OPTIONAL, -- Cond Mandatory ..., [[ tag-Id-ptr-r18 ENUMERATED {n0,n1} OPTIONAL -- Cond 2TA ]] } -- TAG-TCI-UL-STATE-STOP -- ASN1STOP

[0092] In another example, the flag parameter is included in the TCI-state IE, see an example of implementation below: TCI-State information element -- ASN1START -- TAG-TCI-STATE-START TCI-State ::= SEQUENCE { tci-StateId TCI-StateId, qcl-Type1 QCL-Info, qcl-Type2 QCL-Info OPTIONAL, -- Need R ..., [[ additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL, -- Need R pathlossReferenceRS-Id-r17 PathlossReferenceRS-Id-r17 OPTIONAL, -- Cond JointTCI1 ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL -- Cond JointTCI pathlossOffset-Id-r19 PathlossOffset-Id-r19 OPTIONAL, -- Cond Mandatory ]], [[ tag-Id-ptr-r18 ENUMERATED {n0,n1} OPTIONAL -- Cond 2TA ]] } QCL-Info ::= SEQUENCE { cell ServCellIndex OPTIONAL, -- Need R bwp-Id BWP-Id OPTIONAL, -- Cond CSI-RS-Indicated referenceSignal CHOICE { csi-rs NZP-CSI-RS-ResourceId, ssb SSB-Index }, qcl-Type ENUMERATED {typeA, typeB, typeC, typeD}, ... } -- TAG-TCI-STATE-STOP -- ASN1STOP

[0093] In some examples, the UL TCI state is configured with SRS (e.g., with usage = BM) as QCL reference signal. In some examples, two SRSs are configured in two SRS resources of respective SRS resource sets. There can be one or more SRS antenna ports in the SRS resource. The SRS resource or resource set is configured with a set of power control parameters including a pathloss reference signal index and pathloss offset related information. The pathloss RS is associated to and transmitted from the anchor TRP (i.e., TRP0).

[0094] In some examples, the SRS is transmitted from different UL panels and / or UE beams. 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 be transmitted from 2 different UL panels at the same time. The transmission power of both SRS transmissions is associated with the DL-RS from the anchor TRP.

[0095] In some examples, the pathloss offset will be applied to PUCCH or PUSCH transmission if applyIndicatedTCI-State-r18 of PUCCH-config IE or PUSCH-config IE indicates “first”. Alternatively, the pathloss offset will be applied to PUCCH or PUSCH transmission if applyIndicatedTCI-State-r18 of PUCCH-config IE or PUSCH-config IE indicates “Second”. This functionality is useful if multi-DCI is used to enable the mTRP operation.

[0096] In one example, the initial pathloss offset is RRC configured (e.g., defaultPathlossOffset) which can be a cell common pathloss offset or a TRP specific pathloss offset that the UE needs to apply for the initial UL transmission before getting updated pathlossOffset information per TCI state or SRS resource. defaultPathloss-offset-r19 pathloss-offset-Range-r19

[0097] In some examples, the RRC configured pathlossOffset contains both srs-ResourceId and pathloss-offset. pathlossOffset-r19 ::= SEQUENCE { srs-ResourceId-r16 SRS-ResourceId, pathloss-offset-r19 pathloss-offset-Range-r19 } TCI-UL-State information element -- ASN1START -- TAG-TCI-UL-STATE-START TCI-UL-State-r17 ::= SEQUENCE { tci-UL-StateId-r17 TCI-UL-StateId-r17, servingCellId-r17 ServCellIndex OPTIONAL, -- Need R bwp-Id-r17 BWP-Id OPTIONAL, -- Cond CSI-RSorSRS-Indicated referenceSignal-r17 CHOICE { ssb-Index-r17 SSB-Index, csi-RS-Index-r17 NZP-CSI-RS-ResourceId,srs-r17 SRS-ResourceId }, additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL, -- Need R ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL, -- Need 8 pathlossReferenceRS-Id-r17 PathlossReferenceRS-Id-r17 OPTIONAL, -- Cond Mandatory pathlossOffset-r19 PathlossOffset-r19 OPTIONAL, -- Cond Mandatory ..., [[ tag-Id-ptr-r18 ENUMERATED {n0,n1} OPTIONAL -- Cond 2TA ]] } -- TAG-TCI-UL-STATE-STOP -- ASN1STOP

[0098] In some examples, the RRC configured pathlossOffset contains an srs-ResourceId, and a configurable length of value range of pathloss offset. Below shows one example that the new RRC parameters Pathloss-offset-config is a pathloss offset list with configurable length for which the values are given by the total range (e.g., pathloss-offset-range-r19). For example, the parameter pathlossOffset could be specified in TS 38.133. Pathloss-offset-r19 ::= SEQUENCE { pathlossoffsetList-r17 SEQUENCE (SIZE (1..xx)) OF pathloss-offset- range-r19 OPTIONAL, -- Need M ... }

[0099] In some examples, the field length of the indicated pathloss offset in a dynamic indication (e.g., DCI and / or MAC CE) is determined by the length of RRC configured pathloss-offset-range, e.g., ⌈^^^^^^ଶ^^^^^^^^^^^ℎ ^^^^^^^ℎ^^^^^^^^ െ ^^^^^^^^^^^^ െ ^^^^^^^^^^^^⌉ .

[0100] A configurable field length of pathloss offset makes L1 signalling more efficient.

[0101] In some examples, the length of the configurable pathloss offset list is related to a combination of multiple power control parameters, e.g., ^^^, α, etc.

[0102] In some examples, the length of the pathloss offset list is related to a single power control parameters, e.g., α.

[0103] In some examples, the length of the configurable pathloss offset list is related to different types of UL signals / channels.

[0104] In some examples, the field length of the pathloss offset in the DCI or MAC CE is fixed, regardless of the RRC configured length of pathloss-offset-range.

[0105] In some examples, if the joint TCI framework is used, the PL RS of the UL TCI state will follow the DL TCI state, alternatively the PL RS of the UL TCI may not follow the DL TCI state, even though the UL TCI state is the same as DL TCI state (i.e., the same spatial filter).

[0106] In step 120, the UE receives information about the pathloss offset and the application of the pathloss offset.

[0107] In one example, in the connected mode, the pathloss RS offset can be updated using e.g., a MAC-CE. Fig.8 shows an example of the Pathloss Offset MAC CE 200 which can indicate the pathloss offset for one or more UL-TCIs. The MAC CE 200 can contain one or more of the following fields (please note that the size of the fields might differ compared to the example below, the order of the fields might differ and / or the R fields might be removed or used for other purposes):

[0108] - Serving cell ID 210;

[0109] - UL / DL BWP ID 220;

[0110] - The TCI-UL state ID / TCI-State ID 230;

[0111] - The corresponding pathloss offset 240;

[0112] - field ^^^250 indicates if octet(s) containing the PL offset and the TCI-UL state ID corresponding to the ith TCI state is present or not. For instance, if Xi=1, then the field pathloss offset and corresponding field for TCI-UL state ID is present in the MAC CE.

[0113] In some examples, the DL scheduling DCIs (e.g., 1_1 / 1_2), or UL scheduling DCIs (e.g., 0_1 / 0_2) can be used jointly to indicate the TCI state and application of the pathloss offset.

[0114] In some examples, if the flag parameter to apply PL offset is enabled by RRC configuration, when this UL TCI state is activated by the DCI, it automatically will apply the pathloss offset in the derivation of the pathloss.

[0115] In some examples, the pathloss offset is provided by a MAC CE message as shown in Fig.8.

[0116] In some examples, a new bitfield is introduced in the DCI to provide the pathloss offset, where the length of the bitfield is reconfigurable, or according to the specification.

[0117] In some examples, some existing bitfields can be reused to indicate an application of pathloss offset and / or the pathloss offset value.

[0118] In some examples, the pathloss offset indicated in the DCI can override the pathloss offset provided from a higher layer e.g., RRC, and / or MAC CE.

[0119] In some examples, based on the RRC configuration, when only a subset of TCI states is indicated by the DCI, it automatically implies the application of the pathloss offset, for example, the TCI states which have reference SRS configured with usage = BM.

[0120] In some examples, based on the RRC configuration, when a subset of TCI states is indicated by the DCI, it does not imply an application of the pathloss offset, for example the TCI states which have reference SRS configured with usage = AntennaSwitching.

[0121] In some examples, an UL scheduling DCI can be used to jointly indicate an UL TCI state and provide the pathloss offset. In some examples, 3 bits will be introduced to the UL scheduling DCI to indicate one of the maximum 8 TCI state codepoints activated in a MAC CE message. In addition, 1 bit may be introduced to the DCI to enable / disable the application of pathloss offset; and a bitfield may be further introduced to the DCI to provide the pathloss offset value.

[0122] In Step 130, the UE computes the pathloss of the UL-only node based on the pathloss of the Anchor node and the dynamically indicated pathloss offset.

[0123] In some examples, the received pathloss offset can be associated with specific UL signals / channels.

[0124] In Step 140, the UE determines the transmit power for the UL signal (e.g., PUCCH / PUSCH / SRS / PRACH) towards the UL-only node based on the computed pathloss from Step 130.

[0125] In some examples, the derived pathloss is used to set UL transmission power to transmit PUSCH / PUCCH / SRS / PRACH.

[0126] In other examples, the above method can be summarized in an exemplary method 300, illustrated in the flow chart of Fig.9. Method 300 can be performed by a wireless device, such as the UE 14 of Fig.4, UE 1212 of Fig.12 or UE 1300 of Fig.13. Method 300 comprises:

[0127] Step 310: receiving a first message comprising a configuration related to a first pathloss offset (e.g. the configuration can comprise a set of power control parameters, such as a PL-RS and a PL-RS index, configuration of the pathloss offset and an indication of enabling pathloss adjustment by a pathloss offset, etc.; also, the set of power control parameters can be associated with an TCI state);

[0128] Step 320: receiving a second message comprising an indication to enable / disable the application of the pathloss offset in a transmit power calculation; and

[0129] Step 330: determining a transmit power based on the configuration and the indication.

[0130] In some examples, the wireless device can transmit an UL transmission to a first node using the determined transmit power. In some examples, the wireless device can receive a pathloss Reference Signal (RS) from a second node. In some examples, the first node is a node that does not transmit DL signals. In some examples, the configuration comprises an indication of a pathloss reference signal and an indication of the first pathloss offset. In some examples, the wireless devicecomputes a first pathloss based on the pathloss reference signal and the first pathloss offset. In some examples, the first pathloss is a pathloss between the first node and the wireless device. In some examples, the first pathloss offset is a pathloss difference between the first node and the wireless device and the second node and wireless device. In some examples, the configuration in the first message is a higher layer configuration provided via RRC. In some examples, the configuration is included in one or more of the following RRC Information Elements (IEs): joint / UL-TCI State IE or TCI-state IE; an existing IE associated to SRS / PUCCH / PUSCH / PRACH configuration. In some examples, the configuration comprises one or more joint / UL TCI states. In some examples, the first pathloss offset is associated with one UL TCI state. In some examples, prior to receiving the second message, the wireless device receives a third message related to the first pathloss offset. In some examples, the third message is carried in a MAC CE. In some examples, the MAC CE indicates an update of the first pathloss offset. In some examples, the second message is carried in DCI. In some examples, a 1-bit is introduced in the DCI to enable the application of the first pathloss offset. In some examples, a bitfield is introduced in DCI which provides a second pathloss offset. In some examples, if the indication in the second message comprises enabling the application of the first pathloss offset in the transmit power calculation, the wireless device transmits the uplink transmission to an UL-only node. In some examples, if the indication in the second message comprises disabling the application of the first pathloss offset in the transmit power calculation, the wireless device transmits the uplink transmission to an anchor node. For example, in this case, the wireless device does not use the first pathloss offset to determine the transmit power for the UL transmissions. Some other examples of this method have been described above, with reference to Fig.7, as well.

[0131] Now, turning to Fig. 10, a flow chart of an exemplary method 400 for receiving UL signals / transmissions will be described. The method can be performed in a gNB, which comprises at least a first node (e.g. an anchor node for example). In one example, the gNB can also include a second node (e.g. an UL only node). The gNB can be the network node 1210 of Fig.12 or 1400 of Fig.14. Method 400 comprises:

[0132] Step 410: sending a first message to a wireless device, the first message comprising a configuration related to a first pathloss offset (e.g. the configuration can comprise a set of power control parameters (e.g. associated with an TCI state)). For example, the parameters may comprise a pathloss reference signal (PL-RS), configuration of the pathloss offset and an indication of enabling pathloss adjustment by a pathloss offset, etc.

[0133] Step 420: sending a second message comprising an indication to enable / disable application of the first pathloss offset in a transmit power calculation; and

[0134] Step 430: receiving a transmission with a transmit power determined based on the configuration and the indication.

[0135] In some examples the configuration comprises an indication of a pathloss reference signal and an indication of the first pathloss offset. In some examples, the transmit power determined based on the configuration and the indication is computed based on a first pathloss, which is determined based on the pathloss reference signal and the first pathloss offset. In some examples, the first pathloss is a pathloss between the first node and the wireless device. In some examples, the network node further comprises a second node, which is an Uplink-only node. In some examples, the first pathloss offset is a pathloss difference between the first node and the wireless device and the second node and the wireless device. In some examples, the configuration in the first message is a higher layer configuration provided via RRC. In some examples, the configuration is included in one or more of the following RRC Information Elements (IEs): joint / UL-TCI State IE or TCI-state IE; an existing IE associated to SRS / PUCCH / PUSCH / PRACH configuration. In some examples, the configuration comprises one or more joint / UL TCI states. In some examples, the first pathloss offset is associated with one UL TCI state. In some examples, prior to sending the second message, the network node sends a third message related to the first pathloss offset. In some examples, the third message is carried in a MAC CE. In some examples, the MAC CE indicates an update of the first pathloss offset. In some examples, the second message is carried in DCI. In some examples, a 1-bit is introduced in the DCI to enable the application of the first pathloss offset. In some examples, a bitfield is introduced in DCI which provides a second pathloss offset. In some examples, if the indication in the second message comprises enabling the application of the first pathloss offset in the transmit power calculation, the second node receives the uplink transmission. In some examples, if the indication in the second message comprises disabling the application of the first pathloss offset in the transmit power calculation, the first node receives the uplink transmission.

[0136] Proprietary method

[0137] In case dynamically indication of enabling / disabling pathloss offset for an indicated UL TCI state is not introduced in 3GPP specification, proprietary methods can be used instead. In one embodiment, the UE is configured with two sets of UL-TCI states, where the two sets of UL TCI states are identical, except that one set of the UL-TCI states are configured without a pathloss offset (or pathloss offset set to 0), and the second set of UL TCI states are configured with a pathloss offset. One example of how this can look is illustrated in Fig.12, for a UE with four UE beams, and one SRS resource associated with each UE beam. In this case, the network can activate all 8 UL TCI states, and depending on if the strongest received SRS resource is associated withAnchor TRP or UL-only node, the UE will select the corresponding UL TCI state / e.g., assuming that SRS resource 1 is the strongest received SRS resource, and that it is received by Anchor TRP, the network can indicate UL-TCI state 1 for coming UL transmission, while if SRS resource 1 is the strongest received SRS resource but it is received by the UL-only node, the network can indicate UL-TCI state 5 for coming UL transmission. Please note that this embodiment requires double the amount of RRC signalling compared to the embodiments that are standardization related, and described above. Hence, this method, will most lily only be used in case the standardization embodiments are not introduced in NR or 6G.

[0138] Fig.12 shows an example of a communication system 1200 in accordance with some embodiments.

[0139] In the example, the communication system 1200 includes a telecommunication network 1202 that includes an access network 1204, such as a radio access network (RAN), and a core network 1206, which includes one or more core network nodes 1208. The access network 1204 includes one or more access network nodes, such as network nodes 1210a and 1210b (one or more of which may be generally referred to as network nodes 1210), or any other similar 3GPP access nodes or non-3GPP access points. 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 1202 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 1202 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 1202, including one or more network nodes 1210 and / or core network nodes 1208.

[0140] 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 nodein a physical node. Furthermore, an ORAN network node may be implemented 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 1210 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1212a, 1212b, 1212c, and 1212d (one or more of which may be generally referred to as UEs 1212) to the core network 1206 over one or more wireless connections.

[0141] 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 1200 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 1200 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0142] The UEs 1212 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 1210 and other communication devices. Similarly, the network nodes 1210 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 1212 and / or with other network nodes or equipment in the telecommunication network 1202 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 1202.

[0143] In the depicted example, the core network 1206 connects the network nodes 1210 to one or more hosts, such as host 1216. 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 1206 includes one more core network nodes (e.g., core network node 1208) 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 1208. 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).

[0144] The host 1216 may be under the ownership or control of a service provider other than an operator or provider of the access network 1204 and / or the telecommunication network 1202, and may be operated by the service provider or on behalf of the service provider. The host 1216 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.

[0145] As a whole, the communication system 1200 of Fig.12 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 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); LTE, and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 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.

[0146] In some examples, the telecommunication network 1202 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1202. For example, the telecommunications network 1202 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 IoT services to yet further UEs.

[0147] In some examples, the UEs 1212 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 1204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1204. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE mayoperate with any one or combination of Wi-Fi, NR and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) NR – Dual Connectivity (EN-DC).

[0148] In the example, the hub 1214 communicates with the access network 1204 to facilitate indirect communication between one or more UEs (e.g., UE 1212c and / or 1212d) and network nodes (e.g., network node 1210b). In some examples, the hub 1214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1214 may be a broadband router enabling access to the core network 1206 for the UEs. As another example, the hub 1214 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 1210, or by executable code, script, process, or other instructions in the hub 1214. As another example, the hub 1214 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 1214 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1214 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1214 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices.

[0149] The hub 1214 may have a constant / persistent or intermittent connection to the network node 1210b. The hub 1214 may also allow for a different communication scheme and / or schedule between the hub 1214 and UEs (e.g., UE 1212c and / or 1212d), and between the hub 1214 and the core network 1206. In other examples, the hub 1214 is connected to the core network 1206 and / or one or more UEs via a wired connection. Moreover, the hub 1214 may be configured to connect to an M2M service provider over the access network 1204 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1210 while still connected via the hub 1214 via a wired or wireless connection. In some embodiments, the hub 1214 may be a dedicated hub – that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1210b. In other embodiments, the hub 1214 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 1210b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0150] Fig.13 shows a UE / wireless device 1300 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 IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, 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 narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0151] 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).

[0152] The UE 1300 includes processing circuitry 1302 that is operatively coupled via a bus 1304 to an input / output interface 1306, a power source 1308, a memory 1310, a communication interface 1312, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Fig. 13. 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.

[0153] The processing circuitry 1302 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 1310. The processing circuitry 1302 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), togetherwith appropriate software; or any combination of the above. For example, the processing circuitry 1302 may include multiple central processing units (CPUs). Further, the processing circuitry 1302 is configured to perform any steps of method 300 of Fig.9.

[0154] In the example, the input / output interface 1306 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 1300. 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.

[0155] In some embodiments, the power source 1308 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 1308 may further include power circuitry for delivering power from the power source 1308 itself, and / or an external power source, to the various parts of the UE 1300 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1308. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1308 to make the power suitable for the respective components of the UE 1300 to which power is supplied.

[0156] The memory 1310 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1310 includes one or more application programs 1314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1316. The memory 1310 may store, for use by the UE 1300, any of a variety of various operating systems or combinations of operating systems.

[0157] The memory 1310 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 random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or 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 ‘SIM card.’ The memory 1310 may allow the UE 1300 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 1310, which may be or comprise a device-readable storage medium.

[0158] The processing circuitry 1302 may be configured to communicate with an access network or other network using the communication interface 1312. The communication interface 1312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1322. The communication interface 1312 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 1318 and / or a receiver 1320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1318 and receiver 1320 may be coupled to one or more antennas (e.g., antenna 1322) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0159] In the illustrated embodiment, communication functions of the communication interface 1312 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, 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 in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, transmission control protocol / internetprotocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0160] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1312, 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).

[0161] 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.

[0162] 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 TV, 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 Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-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 1300 shown in Fig.13.

[0163] 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 casebe 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 and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0164] 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.

[0165] Fig.14 shows a network node 1400 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, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs (NBs), evolved NBs (eNBs) and NR NBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0166] 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 / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units 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).

[0167] 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 base station 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). The network node 1400 may comprise an anchor TRP and a UL-only TRP as described in this disclosure.

[0168] The network node 1400 includes a processing circuitry 1402, a memory 1404, a communication interface 1406, and a power source 1408. The network node 1400 may be composed of multiple physically separate components (e.g., a NB component and a 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 1400 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 1400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1404 for different RATs) and some components may be reused (e.g., a same antenna 1410 may be shared by different RATs). The network node 1400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1400, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, 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 network node 1400.

[0169] The processing circuitry 1402 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, 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 1400 components, such as the memory 1404, to provide network node 1400 functionality.

[0170] In some embodiments, the processing circuitry 1402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1402 includes one or more of radio frequency (RF) transceiver circuitry 1412 and baseband processing circuitry 1414. In some embodiments, the RF transceiver circuitry 1412 and the baseband processing circuitry 1414 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 RF transceiver circuitry 1412 and baseband processing circuitry 1414 may be on the same chip or set of chips, boards, or units. Further, the processing circuitry 1402 is configured to perform any steps of method 400 of Fig.10.

[0171] The memory 1404 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, random access memory (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 1402. The memory 1404 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 1402 and utilized by the network node 1400. The memory 1404 may be used to store any calculations made by the processing circuitry 1402 and / or any data received via the communication interface 1406. In some embodiments, the processing circuitry 1402 and memory 1404 is integrated.

[0172] The communication interface 1406 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 1406 comprises port(s) / terminal(s) 1416 to send and receive data, for example to and from a network over a wired connection. The communication interface 1406 also includes radio front-end circuitry 1418 that may be coupled to, or in certain embodiments a part of, the antenna 1410. Radio front-end circuitry 1418 comprises filters 1420 and amplifiers 1422. The radio front-end circuitry 1418 may be connected to an antenna 1410 and processing circuitry 1402. The radio front-end circuitry may be configured to condition signals communicated between antenna 1410 and processing circuitry 1402. The radio front-end circuitry 1418 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 1418 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1420 and / or amplifiers 1422. The radio signal may then be transmitted via the antenna 1410. Similarly, when receiving data, the antenna 1410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1418. The digital data may be passed to the processing circuitry 1402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0173] In certain alternative embodiments, the network node 1400 does not include separate radio front-end circuitry 1418, instead, the processing circuitry 1402 includes radio front-end circuitry and is connected to the antenna 1410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1412 is part of the communication interface 1406. In still otherembodiments, the communication interface 1406 includes one or more ports or terminals 1416, the radio front-end circuitry 1418, and the RF transceiver circuitry 1412, as part of a radio unit (not shown), and the communication interface 1406 communicates with the baseband processing circuitry 1414, which is part of a digital unit (not shown).

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

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

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

[0177] Embodiments of the network node 1400 may include additional components beyond those shown in Fig.14 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 1400 may include user interface equipment to allow input of information into the network node 1400 and to allow output ofinformation from the network node 1400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1400.

[0178] Fig. 15 is a block diagram illustrating a virtualization environment 1500 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 1500 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 1500 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.

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

[0180] Hardware 1504 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 1506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1508a and 1508b (one or more of which may be generally referred to as VMs 1508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1506 may present a virtual operating platform that appears like networking hardware to the VMs 1508.

[0181] The VMs 1508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1506. Different embodiments of the instance of a virtual appliance 1502 may be implemented on one or more of VMs 1508, 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 beused 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.

[0182] In the context of NFV, a VM 1508 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 1508, and that part of hardware 1504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, 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 1508 on top of the hardware 1504 and corresponds to the application 1502.

[0183] Hardware 1504 may be implemented in a standalone network node with generic or specific components. Hardware 1504 may implement some functions via virtualization. Alternatively, hardware 1504 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 1510, which, among others, oversees lifecycle management of applications 1502. In some embodiments, hardware 1504 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 radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1512 which may alternatively be used for communication between hardware nodes and radio units.

[0184] 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 on the 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 multipledifferent 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.

[0185] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on 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 hard-wired 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.

[0186] The above-described embodiments are intended to be examples only. Alterations, modifications and variations may be effected to the particular embodiments by those of skill in the art without departing from the scope of the description.

Claims

CLAIMS 1. A method (300) performed by a wireless device (1212, 1300), the method comprising: - receiving (310) a first message comprising a configuration related to a first pathloss offset; - receiving (320) a second message comprising an indication to enable / disable application of the first pathloss offset in a transmit power calculation; and - determining (330) a transmit power based on the configuration and the indication.

2. The method of claim 1, further comprising transmitting an uplink transmission to a first node using the determined transmit power.

3. The method of claim 1 or 2, further comprising receiving a pathloss Reference Signal (RS) from a second node.

4. The method of claim 2 or 3, wherein the first node is a node that does not transmit downlink (DL) signals.

5. The method of any one of claims 1 to 4, wherein the configuration comprises an indication of a pathloss reference signal and an indication of the first pathloss offset.

6. The method of claim 5 further comprising computing a first pathloss based on the pathloss reference signal and the first pathloss offset.

7. The method of claim 6, wherein the first pathloss is a pathloss between the first node and the wireless device.

8. The method of any one of claims 3 to 7, wherein the first pathloss offset is a pathloss difference between the first node and the wireless device and the second node and wireless device.

9. The method of any one of claims 1 to 8, wherein the configuration in the first message is a higher layer configuration provided via Radio Resource Control (RRC).

10. The method of claim 9, wherein the configuration is included in one or more of the following RRC Information Elements (IEs): - joint / UL-TCI State IE or TCI-state IE; - an existing IE associated to SRS / PUCCH / PUSCH / PRACH configuration.

11. The method of any one of claims 1 to 10, wherein the configuration comprises one or more joint / UL TCI states.

12. The method of claim 11, wherein the first pathloss offset is associated with one UL TCI state 13. The method of any one of claims 1 to 12 further comprising, prior to receiving the second message, receiving a third message related to the first pathloss offset.

14. The method of claim 13, wherein the third message is carried in a Medium Access Control (MAC) Control Element (CE).

15. The method of claim 14, wherein the MAC CE indicates an update of the first pathloss offset.

16. The method of any one of claims 1 to 15, wherein the second message is carried in Downlink Control Information (DCI).

17. The method of claim 16, wherein a 1-bit is introduced in the DCI to enable the application of the first pathloss offset.

18. The method of any one of claims 1 to 17, wherein a bitfield is introduced in DCI which provides a second pathloss offset.

19. The method of any one of claims 1 to 18, wherein, if the indication in the second message comprises enabling the application of the first pathloss offset in the transmit power calculation, the wireless device transmits the uplink transmission to an UL-only node.

20. The method of any one of claims 1 to 18, wherein, if the indication in the second message comprises disabling the application of the first pathloss offset in the transmit power calculation, the wireless device transmits the uplink transmission to an anchor node.

21. A method (400) performed by a network node (1210, 1400), the network node comprising at least a first node, the method (400) comprising: - sending (410) a first message to a wireless device, the first message comprising a configuration related to a first pathloss offset; - sending (420) a second message comprising an indication to enable / disable application of the first pathloss offset in a transmit power calculation; and - receiving (430) a transmission with a transmit power determined based on the configuration and the indication.

22. The method of claim 21, wherein the first node is an anchor node.

23. The method of any one of claims 21 to 22, wherein the configuration comprises an indication of a pathloss reference signal and an indication of the first pathloss offset.

24. The method of claim 23, wherein the transmit power determined based on the configuration and the indication is computed based on a first pathloss, which is determined based on the pathloss reference signal and the first pathloss offset.

25. The method of claim 24, wherein the first pathloss is a pathloss between the first node and the wireless device.

26. The method of any one of claims 21 to 25, wherein the network node further comprises a second node, which is an Uplink-only node.

27. The method of claim 26, wherein the first pathloss offset is a pathloss difference between the first node and the wireless device and the second node and the wireless device.

28. The method of any one of claims 21 to 27, wherein the configuration in the first message is a higher layer configuration provided via Radio Resource Control (RRC).

29. The method of claim 28, wherein the configuration is included in one or more of the following RRC Information Elements (IEs): - joint / UL-TCI State IE or TCI-state IE; - an existing IE associated to SRS / PUCCH / PUSCH / PRACH configuration.

30. The method of any one of claims 21 to 29, wherein the configuration comprises one or more joint / UL TCI states.

31. The method of claim 30, wherein the first pathloss offset is associated with one UL TCI state.

32. The method of any one of claims 21 to 31, further comprising, prior to sending the second message, sending a third message related to the first pathloss offset.

33. The method of claim 32, wherein the third message is carried in a Medium Access Control (MAC) Control Element (CE).

34. The method of claim 33, wherein the MAC CE indicates an update of the first pathloss offset.

35. The method of any one of claims 21 to 34, wherein the second message is carried in Downlink Control Information (DCI).

36. The method of claim 35, wherein a 1-bit is introduced in the DCI to enable the application of the first pathloss offset.

37. The method of any one of claims 21 to 36, wherein a bitfield is introduced in DCI which provides a second pathloss offset.

38. The method of any one of claims 26 to 37, wherein, if the indication in the second message comprises enabling the application of the first pathloss offset in the transmit power calculation, the second node receives the uplink transmission.

39. The method of any one of claims 21 to 38, wherein, if the indication in the second message comprises disabling the application of the first pathloss offset in the transmit power calculation, the first node receives the uplink transmission.

40. A wireless device (1212, 1300) comprising a network interface (1312) and processing circuitry (1302) connected thereto, the processing circuitry configured to perform the method of any of the claims 1 to 20.

41. A network node (1210, 1400), having at least a first node, and comprising a network interface (1406) and processing circuitry connected (1402) thereto, the processing circuitry configured to perform the method of any of the claims 21 to 39.

42. The network node of claim 41, further comprising a second node, wherein the processing circuitry is configured to perform the method of claims 26 and 38.

43. A computer-readable medium comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the methods according to any one of claims 1 to 39.

Images