Patent Description:
The next generation mobile wireless communication system (Fifth Generation (<NUM>)), or New Radio (NR), will support a diverse set of use cases and a diverse set of deployment scenarios. The latter includes deployment at both low frequencies, i.e., <NUM> of Megahertz (MHz), similar to Long Term Evolution (LTE) today, and very high frequencies, i.e., millimeter (mm) waves in the tens of Gigahertz (GHz).

Multi-antenna techniques can significantly increase the data rates and reliability of a wireless communication system. The performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. Such systems and/or related techniques are commonly referred to as MIMO.

The NR standard is currently being specified. A core component in NR is the support of MIMO antenna deployments and MIMO related techniques. NR will support uplink MIMO with at least <NUM> layer spatial multiplexing using at least <NUM> antenna ports with channel dependent precoding. The spatial multiplexing mode is aimed for high data rates in favorable channel conditions. An illustration of the spatial multiplexing operation is provided in <FIG> for where Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) is used on the uplink (UL).

As seen, the information carrying symbol vector s is multiplied by an NT x r precoder matrix W, which serves to distribute the transmit energy in a subspace of the NT (corresponding to NT antenna ports) dimensional vector space. The precoder matrix is typically selected from a codebook of possible precoder matrices, and is typically indicated by means of a Transmit Precoder Matrix Indicator (TPMI), which specifies a unique precoder matrix in the codebook for a given number of symbol streams. The r symbols in s each correspond to a layer and r is referred to as the transmission rank. In this way, spatial multiplexing is achieved since multiple symbols can be transmitted simultaneously over the same Time/Frequency Resource Element (TFRE). The number of symbols r is typically adapted to suit the current channel properties.

The received NR x <NUM> vector yn for a certain TFRE on subcarrier n (or alternatively data TFRE number n) is thus modeled by <MAT> where en is a noise/interference vector obtained as realizations of a random process. The precoder W can be a wideband precoder, which is constant over frequency, or frequency selective.

The precoder matrix W is often chosen to match the characteristics of the NRxNT MIMO channel matrix Hn, resulting in so-called channel dependent precoding. This is also commonly referred to as closed-loop precoding and essentially strives for focusing the transmit energy into a subspace which is strong in the sense of conveying much of the transmitted energy to the User Equipment device (UE). In addition, the precoder matrix may also be selected to strive for orthogonalizing the channel, meaning that after proper linear equalization at the UE, the inter-layer interference is reduced.

One example method for a UE to select a precoder matrix W can be to select the Wk that maximizes the Frobenius norm of the hypothesized equivalent channel: <MAT> where.

In closed-loop precoding for the NR uplink, the Transmission Reception Point (TRP) transmits, based on channel measurements in the reverse link (UL), TPMI to the UE that the UE should use on its UL antennas. The NR base station (gNB) configures the UE to transmit Sounding Reference Signal (SRS) according to the number of UE antennas it would like the UE to use for UL transmission to enable the channel measurements. A single precoder that is supposed to cover a large bandwidth (wideband precoding) may be signaled.

Other information than TPMI is generally used to determine the UL MIMO transmission state, such as SRS Resource Indicators (SRIs) as well as Transmission Rank Indicators (TRIs). These parameters, as well as the Modulation and Coding State (MCS), and the UL resources where Physical Uplink Shared Channel (PUSCH) is to be transmitted, are also determined by channel measurements derived from SRS transmissions from the UE. The transmission rank, and thus the number of spatially multiplexed layers, is reflected in the number of columns of the precoder W. For efficient performance, it is important that a transmission rank that matches the channel properties is selected.

SRSs are used for a variety of purposes in LTE, and are expected to serve similar purposes in NR. One primary use for SRS is for UL channel state estimation, allowing channel quality estimation to enable UL link adaptation (including determination of which MCS state the UE should transmit with) and/or frequency-selective scheduling. In the context of UL MIMO, they can also be used to determine precoders and a number of layers that will provide good UL throughput and/or Signal to Interference plus Noise Ratio (SINR) when the UE uses them for transmission on its UL antenna array. Additional uses include power control and UL timing advance adjustment.

Unlike LTE Release <NUM>, at least some NR UEs may be capable of transmitting multiple SRS resources. This is similar conceptually to multiple Channel State Information Reference Signal (CSI-RS) resources on the downlink (DL): an SRS resource comprises one or more SRS ports, and the UE may apply a beamformer and/or a precoder to the SRS ports within the SRS resource such that they are transmitted with the same effective antenna pattern. A primary motivation for defining multiple SRS resources in the UE is to support analog beamforming in the UE where a UE can transmit with a variety of beam patterns, but only one at a time. Such analog beamforming may have relatively high directivity, especially at the higher frequencies that can be supported by NR. Earlier LTE uplink MIMO and transmit diversity designs did not focus on cases where high directivity beamforming could be used on different SRS ports, and so a single SRS resource was sufficient. When an NR UE transmits on different beams, the power received by the TRP can be substantially different. One approach could be to have a single SRS resource, but to indicate to the UE which of its beams to use for transmission. However, since UE antenna designs vary widely among UEs and UE antenna patterns can be highly irregular, it is infeasible to have a predetermined set of UE antenna patterns with which the TRP could control UE UL precoding or beamforming. Therefore, an NR UE may transmit on multiple SRS resources using a distinct effective antenna pattern on each SRS resource, allowing the TRP to determine the composite channel characteristics and quality for the different effective antenna patterns used by the UE. Given this association of each effective antenna pattern with a corresponding SRS resource, the TRP can then indicate to the UE which of one or more effective antenna patterns should be used for transmission on PUSCH (or other physical channels or signals) through one or more SRS resource indicators, or 'SRis'.

NR also supports non-codebook based transmission/precoding for PUSCH in addition to codebook based precoding. For this scheme a set of SRS resources are transmitted where each SRS resource corresponds to one SRS port precoded by some precoder selected by the UE. The gNB can then measure the transmitted SRS resources and feedback to the UE one or multiple SRIs to instruct the UE to perform PUSCH transmission using the precoders corresponding to the referred SRS resources. The rank in this case will be determined from the number of SRIs fed back to the UE.

By configuring the UE with the higher layer parameter SRS-AssocCSIRS and with the higher layer parameter ulTxConfig set to 'NonCodebook', the UE may be configured with a Non-Zero Power (NZP) CSI-RS to utilize reciprocity to create the precoders used for SRS and PUSCH transmission. Hence by measuring on the specified CSI-RS the UE will be able to perform gNB transparent precoding based on reciprocity.

Another mode of operation is to instead let the UE choose the precoders such that each SRS resource corresponds to one UE antenna. Hence, in this case the SRS resource would be transmitted from one UE antenna at the time and the SRIs would hence correspond to different antennas. Thus, by choosing the UE precoders like this the gNB will be able to perform antenna selection at the UE by referring to the different SRIs which in turn will correspond to different antennas.

As indicated above, non-codebook based precoding includes both antenna selection and gNB transparent reciprocity based precoding.

Depending on UE implementation, it may be possible to maintain the relative phase of the transmit chains. In this case, the UE can form an adaptive array by selecting a beam on each transmit chain, and by transmitting the same modulation symbol on the selected beams of both transmit chains using a different gain and/or phase between the transmit chains. This transmission of a common modulation symbol or signal on multiple antenna elements with controlled phase can be labeled 'coherent' transmission'. The support for coherent uplink MIMO transmission in LTE Release <NUM> is indicated via a feature group indication for relative transmit phase continuity for UL spatial multiplexing, wherein a UE indicates if it can adequately maintain the relative phase of transmit chains over time in order to support coherent transmission.

In other UE implementations, the relative phase of the transmit chains may not be well controlled, and coherent transmission may not be used. In such implementations, it may still be possible to transmit on one of the transmit chains at a time, or to transmit different modulation symbols on the transmit chains. In the latter case, the modulation symbols on each transmit chain may form a spatially multiplexed, or 'MIMO', layer. This class of transmission may be referred to as 'non-coherent' transmission. Such non-coherent transmission schemes may be used by LTE Release <NUM> UEs with multiple transmit chains, but that do not support relative transmit phase continuity.

In still other UE implementations, the relative phase of a subset of the transmit chains is well controlled, but not over all transmit chains. One possible such example would be multi-panel operation, where phase is well controlled among transmit chains within a panel, but phase between panels is not well controlled. This class of transmission may be referred to as 'partially-coherent'.

All three of these variants of relative phase control have been agreed for support in NR, and so UE capabilities have been defined for full coherence, partial coherence, and non-coherent transmission. Full coherence, partial coherence, and non-coherent UE capabilities are identified according to the terminology of Third Generation Partnership Project (3GPP) Technical Specification (TS) <NUM> Version <NUM>. <NUM> as `fullAndPartialAndNonCoherent', 'partialCoherent', and 'nonCoherent', respectively. This terminology is used because a UE supporting fully coherent transmission is also capable of supporting partial and non-coherent transmission and because a UE supporting partially coherent transmission is also capable of supporting and non-coherent transmission. A UE can then be configured to transmit using a subset of the UL MIMO codebook that can be supported with its coherence capability. In <NUM> section <NUM>. <NUM>, the UE can be configured with higher layer parameter ULCodebookSubset, which can have values 'fullAndPartialAndNonCoherent', 'partialAndNonCoherent', and 'nonCoherent', indicating that the UE uses subsets of a codebook that can be supported by UEs with fully coherent, partially coherent, and non-coherent transmit chains.

In TS <NUM> V15. <NUM> section <NUM>. <NUM>, the vector z corresponding to the antenna ports is specified for codebook based and non-codebook based precoding as follows:.

Setting output power levels of transmitters, base stations in DL, and mobile stations in UL in mobile systems is commonly referred to as Power Control (PC). Objectives of PC include improved capacity, coverage, improved system robustness, and reduced power consumption.

In LTE, PC mechanisms can be categorized into the groups (i) open-loop, (ii) closed-loop, and (iii) combined open- and closed loop. These differ in what input is used to determine the transmit power. In the open-loop case, the transmitter measures some signal sent from the receiver, and sets its output power based on this. In the closed-loop case, the receiver measures the signal from the transmitter, and based on this sends a Transmit Power Control (TPC) command to the transmitter, which then sets its transmit power accordingly. In a combined open- and closed-loop scheme, both inputs are used to set the transmit power.

In systems with multiple channels between the terminals and the base stations, e.g. traffic and control channels, different power control principles may be applied to the different channels. Using different principles yields more freedom in adapting the power control principle to the needs of individual channels. The drawback is increased complexity of maintaining several principles.

In TS <NUM> (V15. <NUM>), the UL power control for NR is specified in section <NUM> and it is specified how to derive PPUSCH,f,c(i,j,qd,l) which can be described as the "output" from the UL power control framework; this is the intended output power that should be used by the UE to conduct PUSCH transmission. When performing PUSCH transmission it is specified in TS <NUM> section <NUM> that:
"For PUSCH, a UE first scales a linear value P̂PUSCH,f,c(i,j,qd,l) of the transmit power PPUSCH,f. c(i,j,qd,l) on UL BWP b, as described in Subclause <NUM>, of carrier f of serving cell c, with parameters as defined in Subclause <NUM>. <NUM>, by the ratio of the number of antenna ports with a non-zero PUSCH transmission to the number of configured antenna ports for the transmission scheme. The resulting scaled power is then split equally across the antenna ports on which the non-zero PUSCH is transmitted.

<NPL>) describes a power control mechanism of scaling the transmit power by the ratio of the number of antennas ports with a non zero PUSCH transmission to the number of configured antenna ports.

As described herein, the inventors have found that the current UL power control scheme for PUSCH specified for NR has several problems. Solutions for addressing these problems are disclosed herein.

Systems and methods are disclosed herein for determining, or controlling, a power to be used for a set of antenna ports for a physical uplink shared channel transmission. In some embodiments, a User Equipment (UE) comprises processing circuitry configured to derive a power P to be used for uplink power control for a physical uplink shared channel transmission and determine a power to be used for a set of antenna ports based on the power P according to a rule that depends on whether the UE is utilizing codebook based transmission or non-codebook based transmission for the physical uplink shared channel transmission. The set of antenna ports is antenna ports on which the physical uplink shared channel transmission is transmitted with non-zero power. In some embodiments, the UE further comprises an interface, and the processing circuitry is further configured to transmit, via the interface, the physical uplink shared channel transmission using the set of antenna ports. A first aspect of the invention relates to a communications system defined by independent claim <NUM>. A second aspect of the invention relates to a method implemented in a communications system defined by independent claim <NUM>. Some embodiments relating to the first and second aspects are defined by dependent claims <NUM> to <NUM> and <NUM> to <NUM>.

The drawings illustrate selected embodiments of the disclosed subject matter. In the drawings, like reference labels denote like features.

Additional information may also be found in any document(s) provided in an Appendix hereto.

Other objectives, features, and advantages of the enclosed embodiments will be apparent from the description.

Certain concepts may be described herein with reference to particular technology fields or standards and/or using language applicable to those fields and/or standards. For instance, certain embodiments may be described with reference to cells, subframes/slots, channels, etc. as understood in the context of Long Term Evolution (LTE), or with reference to beams, slots/mini-slots, channels, etc. as understood in the context of Third Generation Partnership Project (3GPP) New Radio (NR). Nevertheless, unless otherwise indicated, the described concepts may be more generally applicable and are not to be limited according to any such field, standard, language, etc..

As discussed above, uplink (UL) power control in 3GPP NR is specified in Technical Specification (TS) <NUM> (V15. In TS <NUM> (V15. <NUM>), the UL power control for NR is specified in section <NUM>. Section <NUM> of TS <NUM> (V15. <NUM>) specifies how to derive PPUSCH,f,c(i,j,qd,l), which can be described as the "output" from the UL power control framework. This is the intended output power that should be used by the User Equipment (UE) to conduct Physical Uplink Shared Channel (PUSCH) transmission. When performing PUSCH transmission, TS <NUM> section <NUM> specifies that:
For PUSCH, a UE first scales a linear value PPUSCH,f,c(i,j,qd,l) of the transmit power PPUSCH,f,c(i,j,qd,l) on UL BWP b, as described in Subclause <NUM>, of carrier f of serving cell c, with parameters as defined in Subclause <NUM>. <NUM>, by the ratio of the number of antenna ports with a non-zero PUSCH transmission to the number of configured antenna ports for the transmission scheme. The resulting scaled power is then split equally across the antenna ports on which the non-zero PUSCH is transmitted.

UL power control for PUSCH as specified in TS <NUM>, Section <NUM> (V15. <NUM>) has several implications. The above power control supports the UE implementation #<NUM> shown in <FIG> for codebook based operation, where rank <NUM> transmission is shown. Each transmit chain only requires a Power Amplifier (PA) capable of one fourth of the total transmit power P̂PUSCH,f,c(i,j,qd,l) which is denoted herein as P. Note that each transmit chain in this example is presumed to carry a Sounding Reference Signal (SRS); that is, "non-precoded" SRS is used. Consequently, the NR base station (gNB) can estimate the total power received from all UE transmit chains as the sum of the power on the SRSs.

Three examples are illustrated below for implementation #<NUM> using codebook based precoding. Four antenna ports and rank <NUM> transmission are considered. Regarding these examples, it is noted that:.

From the above examples, it is noted that, for the case of antenna selection i.e. "CB, non-coherent", only P/<NUM> is transmitted. The reason for this is that the specification states that one should scale the power P "by the ratio of the number of antenna ports with a non-zero PUSCH transmission to the number of configured antenna ports for the transmission scheme". Thus, antenna ports transmitting no power will reduce the total power. Hence, the total power generated by using this precoder will be lower than if the codeword as given by Transmit Precoder Matrix Indicator (TPMI) = <NUM> were used. This property is desirable since it will allow the UE implementation as illustrated above.

Certain embodiments are presented herein in recognition of shortcomings associated with conventional techniques and technologies, such as the following. Current specifications for how to use PPUSCH,f,c(i,j,qd,l) when performing a transmission work well for a typical UE layout and codebook based transmission for a UE with full coherence capability. However, the design is not as efficient for non-codebook based transmission and for UEs with other capabilities.

A number of problems will now be described. A first problem (Problem <NUM>) relates to non-codebook based transmission. Consider the two implementations illustrated in <FIG> (Implementation #<NUM>) and <FIG> (Implementation #<NUM>) that illustrate non-codebook based transmission.

For implementation #<NUM>, corresponding to antenna selection, it is assumed that the first SRS resource is precoded with: <MAT>.

This implies that PUSCH will be transmitted as in the table below given that SRS Resource Indicator (SRI) = <NUM> is signaled from the gNB to the UE. Because the number of antenna ports with a Non-Zero Power (NZP) PUSCH transmission is <NUM> and since four antenna ports are configured for non-codebook based transmission, power control will set the total output power to P/<NUM>. This is not beneficial for implementation #<NUM> since it is desirable for UEs to transmit the required maximum power on each transmit chain.

Implementation #<NUM> corresponds to gNB transparent reciprocity based precoding, and so the UE, rather than the gNB, determines the precoder. Therefore, the precoding weights are denoted as vi instead of as wi used in implementation #<NUM>. Because each vi can attain any suitable value that the UE selects, possible values of wi are a subset of those of vi. One possibility is that the first SRS resource is precoded with <MAT>.

This implies that PUSCH will be transmitted as below given that SRI = <NUM> is signaled from the gNB to the UE. While the number of antennas transmitting is four, the number of antenna ports with a non-zero PUSCH transmission is still <NUM> as in the above example. Further, since four antenna ports are configured for non-codebook based transmission, power control will set the output power in the single transmitting antenna port to P/<NUM>, which the means the total output power is again P/<NUM>. Hence, although all antennas are used for transmission, the UE will do a power backoff since not all antenna ports are used. This is an undesired behavior since it will decrease the performance of non-cookbook precoding.

A second problem (Problem <NUM>) relates to UEs with non-coherent and partial coherence capabilities. If a UE with full coherence capabilities is considered, this UE may transmit as below for codebook based transmission given the current specification:.

Here, it is noted that, when the UE goes up in rank, the power per layer goes down. This is an intended behavior since it enables the UE to choose a lower rank to increase Signal to Noise Ratio (SNR) or alternatively increase rank when the SNR is high.

For a UE with non-coherent capability, the UE may instead transmit as follows:.

Hence, the behavior is the opposite of the desired behavior; the power per layer is constant and lowering rank will hence not increase the SNR. This makes it less appealing for the UE to use a lower rank. Furthermore, although the UE is allowed to transmit with a total power of P, as defined by the UL power control framework, the UE will only do so when using full rank. This is a severe limitation since it implies that when P reaches its maximal possible value P_cmax, the UE will transmit with P_cmax/<NUM>. A UE reaching P_cmax is typically a UE corresponding to low SNR and, for such a UE, a low rank transmission with as high power as possible is typically a suitable strategy.

Embodiments are described herein that address the aforementioned problems. In certain embodiments of the disclosed subject matter, new approaches are provided for controlling power (P) for PUSCH transmission. Certain embodiments involve defining a ratio of P that should be transmitted based on, e.g., (i) information about non-codebook based or codebook based transmission, (ii) information about UE capability for coherent transmission, and/or (iii) relying on a number of antenna ports used for PUSCH transmission instead of the number of configured antenna ports.

Certain embodiments of the disclosed subject matter may provide potential benefits compared to conventional techniques and technologies, such as the following examples. Certain embodiments provide efficient transmission for both codebook based precoding as well as non-codebook based precoding. Some such embodiments enable (a) UEs transmitting with non-codebook based reciprocity to utilize full power for rank <NUM>, or (b) UEs with non-coherent and partial coherent capabilities to transmit with full power for rank <NUM> and also enable the UEs to increase rank at the cost of lower power per layer.

The following description presents several embodiments on PUSCH transmission. The behavior of certain different embodiments in terms of total power is illustrated in Table <NUM>.

In one embodiment, the ratio of the power that should be used is specified in terms of number of ports {p<NUM>,. ,pρ-<NUM>} in PUSCH (i.e., the number of antenna ports used for the PUSCH transmission) instead of the number of configured ports. In terms of specification text this may be written as below, based on version <NUM>. <NUM> of 3GPP TS <NUM> section <NUM>:
For PUSCH, a UE first scales a linear value P̂PUSCH,f,c(i,j,qd,l) of the transmit power PPUSCH,f,c(i,j,qd,l) on UL BWP b, as described in Subclause <NUM>, of carrier f of serving cell c, with parameters as defined in Subclause <NUM>. <NUM>, by the ratio of the number of antenna ports with a non-zero PUSCH transmission to ρ, where ρ is the number of antenna ports {p<NUM>,. ,ρρ-<NUM>} according to <NUM><NUM>. The resulting scaled power is then split equally across the antenna ports on which the non-zero PUSCH is transmitted.

In some embodiments, when a codebook based mode of operation is used, ρ corresponds to a number of antenna ports over which a precoder in a codebook can apply for PUSCH transmission; while when a non-codebook based mode of operation is used, ρ corresponds to a number of antenna ports and spatial layers on which a PUSCH is transmitted. Hence, for non-codebook transmission, a ratio of <NUM> that should be divided on the different antenna ports in case of rank <NUM> transmission is obtained (instead as ¼ as in the current text of 3GPP TS <NUM> V15.

In some embodiments, it may be desirable to support UE implementations with N transmit chains having PAs with maximum power PIN (such as implementations #<NUM> and #<NUM>). In one such embodiment, P is determined as follows:.

This will hence address the problem for the case "NCB, reciprocity based". Potential benefits of this embodiment may include that the total transmitted power for non-codebook based operation with coherent operation increases as compared to the current specification, such that the total power for non-codebook based operation is the same as for codebook based operation for a given number of transmit chains and maximum transmit power per transmit chain in coherent operation.

In one embodiment, ρ is defined as the number of antenna ports {p<NUM>,. , pρ-<NUM>} according to TS <NUM><NUM>. Furthermore, let ρ<NUM> be the number of non-zero antenna ports in{p<NUM>,. , pρ-<NUM>}. K is defined such that.

From this, a ratio <MAT> is defined and a scaling factor (β) is derived as β = min{<NUM>, α}. The PUSCH power control is defined as described below in terms of a change to the current language of TS <NUM> V15. <NUM> section <NUM>:
For PUSCH, a UE first scales a linear value P̂PUSCH,f,c(i,j,qd,l) of the transmit power PPUSCH,f,c(i,j,qd,l) on UL BWP b, as described in Subclause <NUM>, of carrier f of serving cell c, with parameters as defined in Subclause <NUM>. <NUM>, by β and the resulting scaled power is then split equally across the antenna ports on which the non-zero PUSCH is transmitted.

Some examples of β assuming <NUM> and <NUM> configured ports are illustrated below.

In some embodiments, K = <NUM> when the UE is configured to transmit PUSCH on a single antenna port, and in other embodiments β = <NUM> when the UE is configured to transmit PUSCH on a single antenna port.

In some embodiments, UEs are configured to use subsets of an UL Multiple-Input-Multiple-Output (MIMO) codebook that are supported by its coherence capability. In such embodiments, the UE can be configured with higher layer parameter ULCodebookSubset, which can have values 'fullAndPartialAndNon Coherent', `partialAndNonCoherent', and 'noncoherent', indicating that the UE uses subsets of a codebook that can be supported by UEs with fully coherent, partially coherent, and non-coherent transmit chains. In such embodiments, the use of the codebook subset parameter allows the UE to adjust its power control to match its coherence capability. This behavior may be described as follows:
For PUSCH, a UE first scales a linear value P̂PUSCH,f,c(i,j,qd,l) of the transmit power PPUSCH,f,c(i,j,qd,l) on UL BWP b, as described in Subclause <NUM>, of carrier f of serving cell c, with parameters as defined in Subclause <NUM>. <NUM>, by β and the resulting scaled power is then split equally across the antenna ports on which the non-zero PUSCH is transmitted, where β = <NUM> for single antenna port transmission, and for multi-antenna port transmission:.

∘ ρ is the number of antenna ports {p<NUM>,. ,pρ-<NUM>} according to TS <NUM><NUM>. <NUM>
∘ ρ<NUM> be the number of non-zero antenna ports in {p<NUM>,. ,pρ-<NUM>} according to TS <NUM><NUM>. ∘ For non-codebook based transmission K=<NUM>. For codebook based transmission K is given from the table below, where ULCodebookSubset is a higher layer parameter.

Note: the number of configured ports can correspond to the maximum number of spatial layers the UE is capable of transmitting. For codebook based precoding, this can refer to the number of SRS ports in an SRS resource, while for non-codebook based precoding, this can refer to the total number of SRS ports configured to the UE for non-codebook based operation, or it can refer to the total number of SRS ports in an SRS resource set intended for use with codebook based operation.

CB and NCB refer to codebook based and non-codebook based UE capabilities, respectively. Full, partial, and non-coherent UE capabilities may be identified according to the terminology of 3GPP TS <NUM> V15. <NUM> as 'fullAndPartialAndNonCoherent', 'partialCoherent', and 'nonCoherent', respectively.

By using β as the ratio of P that should be transmitted on PUSCH, it is noted that for most cases in the table full power will be transmitted. The only cases corresponding to using a lower power corresponds to the cases in codebook based transmission where a gNB has chosen a codeword which structure corresponds to a "lower capability" than the UE's capability; the UE has in this sense an opportunity to turn off some of its branches and thereby reduce power consumption.

The following table illustrates characteristics of certain embodiments discussed above.

<FIG> illustrates a wireless network in accordance with some embodiments. Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in <FIG>. For simplicity, the wireless network of <FIG> only depicts network <NUM>, network nodes <NUM> and 560b, and Wireless Devices (WDs) <NUM>, 510b, and 510c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node <NUM> and WD <NUM> are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable Second, Third, Fourth, or Fifth Generation (<NUM>, <NUM>, <NUM>, or <NUM>) standards; Wireless Local Area Network (WLAN) standards, such as the IEEE <NUM> standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network <NUM> may comprise one or more backhaul networks, core networks, Internet Protocol (IP) networks, Public Switched Telephone Networks (PSTNs), packet data networks, optical networks, Wide Area Networks (WANs), Local Area Networks (LANs), WLANs, wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

As used herein, network node refers to equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless 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, evolved Node Bs (eNBs) and gNBs). A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a Distributed Antenna System (DAS). Yet further examples of network nodes include 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), core network nodes (e.g., MSCs, MMEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self Optimized Network (SON) nodes, positioning nodes (e.g., Evolved-Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).

It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions, and methods disclosed herein. Moreover, while the components of network node <NUM> are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium <NUM> may comprise multiple separate hard drives as well as multiple Random Access Memory (RAM) modules).

Similarly, network node <NUM> may be composed of multiple physically separate components (e.g., a Node B component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. For example, a single RNC may control multiple Node Bs. In such a scenario, each unique Node B and RNC pair may in some instances be considered a single separate network node. In some embodiments, network node <NUM> may be configured to support multiple Radio Access Technologies (RATs). Network node <NUM> may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node <NUM>, such as, for example, GSM, Wideband Code Division Multiple Access (WCDMA), LTE, NR, WiFi, or Bluetooth wireless technologies.

Processing circuitry <NUM> may comprise a combination of one or more of a microprocessor, controller, microcontroller, Central Processing Unit (CPU), Digital Signal Processor (DSP), Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other network node <NUM> components, such as device readable medium <NUM>, network node <NUM> functionality. In some embodiments, processing circuitry <NUM> may include a System on a Chip (SOC).

In some embodiments, processing circuitry <NUM> may include one or more of Radio Frequency (RF) transceiver circuitry <NUM> and baseband processing circuitry <NUM>. In some embodiments, RF transceiver circuitry <NUM> and baseband processing circuitry <NUM> may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by processing circuitry <NUM> executing instructions stored on device readable medium <NUM> or memory within processing circuitry <NUM>.

Device readable medium <NUM> may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, RAM, Read Only Memory (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 processing circuitry <NUM>.

Interface <NUM> is used in the wired or wireless communication of signaling and/or data between network node <NUM>, network <NUM>, and/or WDs <NUM>.

In some embodiments, antenna <NUM> may comprise one or more omni-directional, sector, or panel antennas operable to transmit/receive radio signals between, for example, <NUM> gigahertz (GHz) and <NUM>.

Any information, data, and/or signals may be received from a wireless device, another network node, and/or any other network equipment. Any information, data, and/or signals may be transmitted to a wireless device, another network node, and/or any other network equipment.

As used herein, WD refers to a device capable, configured, arranged, and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with UE. Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a Voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a Personal Digital Assistant (PDA), a wireless camera, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a Laptop Embedded Equipment (LEE), a Laptop-Mounted Equipment (LME), a smart device, a wireless Customer Premise Equipment (CPE), a vehicle-mounted wireless terminal device, etc.. A WD may support Device-to-Device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I), Vehicle-to-Everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD 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 WD and/or a network node. The WD may in this case be a Machine-to-Machine (M2M) device, which may in a 3GPP context be referred to as a Machine Type Communication (MTC) device. As one particular example, the WD may be a UE implementing the 3GPP Narrowband IoT (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device <NUM> includes antenna <NUM>, interface <NUM>, processing circuitry <NUM>, device readable medium <NUM>, user interface equipment <NUM>, auxiliary equipment <NUM>, power source <NUM>, and power circuitry <NUM>.

Any information, data, and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry, and/or antenna <NUM> may be considered an interface.

Radio front end circuitry <NUM> comprises one or more filters <NUM> and amplifiers <NUM>.

Processing circuitry <NUM> may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD <NUM> components, such as device readable medium <NUM>, WD <NUM> functionality.

Device readable medium <NUM> may include computer memory (e.g., RAM or ROM), mass storage media (e.g., a hard disk), removable storage media (e.g., a CD or a 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 processing circuitry <NUM>.

User interface equipment <NUM> may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a Universal Serial Bus (USB) port, or other input circuitry.

UE <NUM> may be any UE identified by the 3GPP, including a NB-IoT UE, a MTC UE, and/or an enhanced MTC (eMTC) UE. UE <NUM>, as illustrated in <FIG>, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3GPP, such as 3GPP's GSM, UMTS, LTE, and/or <NUM> standards. As mentioned previously, the term WD and UE may be used interchangeably.

In <FIG>, UE <NUM> includes processing circuitry <NUM> that is operatively coupled to input/output interface <NUM>, RF interface <NUM>, network connection interface <NUM>, memory <NUM> including RAM <NUM>, ROM <NUM>, and storage medium <NUM> or the like, communication subsystem <NUM>, power source <NUM>, and/or any other component, or any combination thereof.

Processing circuitry <NUM> may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or DSP, together with appropriate software; or any combination of the above. For example, the processing circuitry <NUM> may include two CPUs.

Network connection interface <NUM> may be configured to provide a communication interface to network 643a. Network 643a may encompass wired and/or wireless networks such as a LAN, a WAN, a computer network, a wireless network, a telecommunications network, another like network, or any combination thereof. For example, network 643a may comprise a WiFi network. Network connection interface <NUM> may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, Transmission Control Protocol (TCP) /IP, Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), or the like. The transmitter and receiver functions may share circuit components, software, or firmware, or alternatively may be implemented separately.

Storage medium <NUM> may be configured to include memory such as RAM, ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.

Storage medium <NUM> may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High-Density Digital Versatile Disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, Holographic Digital Data Storage (HDDS) optical disc drive, external mini-Dual In-Line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a Subscriber Identity Module (SIM) or a Removable User Identity (RUIM) module, other memory, or any combination thereof.

In <FIG>, processing circuitry <NUM> may be configured to communicate with network 643b using communication subsystem <NUM>. Network 643a and network 643b may be the same network or networks or different network or networks. Communication subsystem <NUM> may be configured to include one or more transceivers used to communicate with network 643b. For example, communication subsystem <NUM> may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE <NUM>, Code Division Multiple Access (CDMA), WCDMA, GSM, LTE, Universal Terrestrial RAN (UTRAN), WiMax, or the like. Further, transmitter <NUM> and receiver <NUM> of each transceiver may share circuit components, software, or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem <NUM> may include 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. For example, communication subsystem <NUM> may include cellular communication, WiFi communication, Bluetooth communication, and GPS communication. Network 643b may encompass wired and/or wireless networks such as a LAN, a WAN, a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 643b may be a cellular network, a WiFi network, and/or a near-field network. Power source <NUM> may be configured to provide Alternating Current (AC) or Direct Current (DC) power to components of UE <NUM>.

The features, benefits, and/or functions described herein may be implemented in one of the components of UE <NUM> or partitioned across multiple components of UE <NUM>. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software, or firmware.

Virtualization environment <NUM>, comprises general-purpose or special-purpose network hardware devices <NUM> comprising a set of one or more processors or processing circuitry <NUM>, which may be Commercial off-the-Shelf (COTS) processors, dedicated ASICs, or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise one or more Network Interface Controllers (NICs) <NUM>, also known as network interface cards, which include physical network interface <NUM>. Software <NUM> may include any type of software including software for instantiating one or more virtualization layers <NUM> (also referred to as hypervisors), software to execute virtual machines <NUM> as well as software allowing it to execute functions, features, and/or benefits described in relation with some embodiments described herein.

During operation, processing circuitry <NUM> executes software <NUM> to instantiate the hypervisor or virtualization layer <NUM>, which may sometimes be referred to as a Virtual Machine Monitor (VMM).

Alternatively, hardware <NUM> 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 (MANO) <NUM>, which, among others, oversees lifecycle management of applications <NUM>.

Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and CPE.

Each of virtual machines <NUM>, and that part of hardware <NUM> that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines <NUM>, forms a separate Virtual Network Element (VNE).

<FIG> illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.

Referring to <FIG>, in accordance with an embodiment, a communication system includes a telecommunication network <NUM>, such as a 3GPP-type cellular network, which comprises access network <NUM>, such as a radio access network, and core network <NUM>. Access network <NUM> comprises a plurality of base stations 812a, 812b, 812c, such as Node Bs, eNBs, gNBs, or other types of wireless access points, each defining a corresponding coverage area 813a, 813b, 813c. Each base station 812a, 812b, 812c is connectable to core network <NUM> over a wired or wireless connection <NUM>. A first UE <NUM> located in coverage area 813c is configured to wirelessly connect to, or be paged by, the corresponding base station 812c. A second UE <NUM> in coverage area 813a is wirelessly connectable to the corresponding base station 812a.

Telecommunication network <NUM> is itself connected to host computer <NUM>, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. Intermediate network <NUM> may be one of, or a combination of more than one of, a public, private, or hosted network; intermediate network <NUM>, if any, may be a backbone network or the Internet; in particular, intermediate network <NUM> may comprise two or more sub-networks (not shown).

Similarly, base station <NUM> need not be aware of the future routing of an outgoing UL communication originating from the UE <NUM> towards the host computer <NUM>.

<FIG> illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.

In particular, processing circuitry <NUM> may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions.

In the embodiment shown, hardware <NUM> of base station <NUM> further includes processing circuitry <NUM>, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions.

Hardware <NUM> of UE <NUM> further includes processing circuitry <NUM>, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions.

It is noted that host computer <NUM>, base station <NUM> and UE <NUM> illustrated in <FIG> may be similar or identical to host computer <NUM>, one of base stations 812a, 812b, 812c and one of UEs <NUM>, <NUM> of <FIG>, respectively.

Wireless connection <NUM> between UE <NUM> and base station <NUM> is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE <NUM> using OTT connection <NUM>, in which wireless connection <NUM> forms the last segment. For instance, certain embodiments may provide efficient transmission for both codebook based precoding as well as non-codebook based precoding. Some such embodiments enable (a) UEs transmitting with non-codebook based reciprocity to utilize full power for rank <NUM>, or (b) UEs with non-coherent and partial coherent capabilities to transmit with full power for rank <NUM> and also enable the UEs to increase rank at the cost of lower power per layer. Such improvements may provide benefits such as increasing the quality or responsiveness of an OTT service.

In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer <NUM>'s measurements of throughput, propagation times, latency, and the like. The measurements may be implemented in that software <NUM> and <NUM> causes messages to be transmitted, in particular empty or 'dummy' messages, using OTT connection <NUM> while it monitors propagation times, errors, etc..

For the sake of brevity, only drawing references to <FIG> will be included in this section.

<FIG> illustrates a schematic block diagram of an apparatus <NUM> in a wireless network (for example, the wireless network shown in <FIG>). The apparatus may be implemented in a wireless device or network node (e.g., wireless device <NUM> or network node <NUM> shown in <FIG>). Apparatus <NUM> is operable to carry out the example method described with reference to <FIG> and possibly any other processes or methods disclosed herein. It is also to be understood that the method of <FIG> is not necessarily carried out solely by apparatus <NUM>. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus <NUM> may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include DSPs, special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as ROM, RAM, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause the units in apparatus <NUM> to perform corresponding functions according one or more embodiments of the present disclosure.

As illustrated in <FIG>, apparatus <NUM> comprises receiving unit <NUM>, determining unit <NUM>, adjusting unit <NUM>, and transmitting unit <NUM>. These units are configured to perform corresponding operations performed by the method of <FIG>.

The term "unit" may have conventional meaning in the field of electronics, electrical devices, and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

<FIG> illustrates a method according to some embodiments.

Referring to <FIG>, the method may comprise receiving signaling identifying a multi-antenna transmission configuration (S1505), determining a power scaling ratio R, the ratio R being a first number antenna ports divided by a second number of antenna ports (S1510), wherein the first number of antenna ports is a number of antenna ports with NZP, and the second number of antenna ports being determined according to the multi-antenna transmission configuration as one of (a) a third number of ports used in a precoder indicated by a gNB, and (b) a fourth number of spatial layers indicated by the gNB, adjusting an initial power value P0 by at least the ratio R to determine P (S1515), and transmitting the physical channel using the power P (S1520).

Alternatively, the method may comprise receiving signaling identifying a first number of antenna ports on which the physical channel is to be transmitted and a multi-antenna transmission configuration, the multi-antenna configuration identifying if codebook based or non-codebook based transmission scheme is to be used (S1505), determining a power scaling ratio R according to the number of antenna ports, a second number of antenna ports, and at least one of the multi-antenna configuration and a UE coherence capability, where the second number of antenna ports is a number of antenna ports with NZP (S1510), adjusting an initial power value P0 by at least the ratio R to determine P (S1515), and transmitting the physical channel using the power P (S1520).

<FIG> is a flow chart that illustrates the operation of a UE in accordance with some embodiments of the present disclosure. As illustrated, the UE derives a power P to be used for UL power control (step <NUM>). As described herein, the UL power control is for a PUSCH transmission. The UE decides (or determines) a second power P' to be used for a set of antenna ports according to some rule (step <NUM>). This rule may be any of the rules described herein (e.g., any of the rules described above with respect to Embodiments <NUM> to <NUM>). As described herein, in some embodiments, the rule is a rule that depends on whether the UE is utilizing codebook based transmission or non-codebook based transmission for the PUSCH transmission, where the set of antenna ports is antenna ports on which the PUSCH transmission is transmitted with NZP. As also described herein, in some embodiments, the rule is a rule that depends on a capability of the UE in terms of full coherence, partial coherence, or non-coherence transmission, where the set of antenna ports is antenna ports on which the PUSCH transmission is transmitted with NZP. Further details regarding these and additional embodiments are described above and therefore not repeated here.

Embodiment <NUM>: A method (<NUM>) in a UE for determining a transmission power P for a physical channel configured for multi-antenna transmission, comprising: receiving signaling identifying a multi-antenna transmission configuration (S1505); determining a power scaling ratio R, the ratio R being a first number antenna ports divided by a second number of antenna ports (S1510), wherein the first number of antenna ports is a number of antenna ports with non-zero power, and the second number of antenna ports being determined according to the multi-antenna transmission configuration as one of (a) a third number of ports used in a precoder indicated by a gNB, and (b) a fourth number of spatial layers indicated by the gNB; adjusting an initial power value P0 by at least the ratio R to determine P (S1515); and transmitting the physical channel using the power P (S1520).

Claim 1:
A telecommunications system comprising:
a New Radio base station, gNB, adapted to provide radio access for a plurality of User Equipment, UEs; and
a User Equipment, UE, (<NUM>) having a plurality of transmit chains that do not support relative transmit phase continuity, the UE comprising:
processing circuitry (<NUM>) configured to:
derive a power P to be used for uplink power control for a physical uplink shared channel transmission to the gNB; and
determine a power to be used for a set of antenna ports based on the power P according to a rule that depends on whether the UE (<NUM>) is utilizing codebook based transmission or non-codebook based transmission for the physical uplink shared channel transmission, the set of antenna ports being antenna ports on which the physical uplink shared channel transmission is transmitted with non-zero power,
wherein the rule is such that, for a case of codebook based transmission, in order to determine the power to be used for the set of antenna ports based on the power P according to the rule, the processing circuitry (<NUM>) is further configured to:
derive a second power P' by scaling the power P with a ratio, R, wherein the ratio R is a first number antenna ports divided by a second number of antenna ports, wherein the first number of antenna ports is a number of antenna ports on which the physical uplink shared channel transmission is transmitted with non-zero power, and the second number of antenna ports is determined according to a multi-antenna transmission configuration as a third number of spatial layers indicated by the gNB; and
equally divide the second power P' across the set of antenna ports on which the physical uplink shared channel transmission is transmitted with non-zero power.