US20180103433A1

Method and apparatus for deriving transmit power of ul (uplink) rs (reference signal) in a wireless communication system

Claim Score by NHIP

Abstract

A method and apparatus are disclosed, from the perspective of a UE, for transmitting UL RS. In one embodiment, the method includes deriving a first transmit power of a first UL RS based on a first power control mechanism, wherein derivation of the first transmit power based on the first power control mechanism is associated with an uplink data channel. In addition, the method includes deriving a second transmit power of a second UL RS based on a second power control mechanism, wherein derivation of the second transmit power based on the second power control mechanism is not associated with the uplink data channel. Furthermore, the method includes transmitting the first UL RS with the first transmit power. The method also includes transmitting the second UL RS with the second transmit power.

US20180103433A1, drawing sheet 1 — Sheet 1 of 40

Term

11 yearsto projected expiry

Projected expiry 28 September 2037, counted from filing; an application has no term until it is granted.

20 claims: 3 independent, 17 dependent

1
A method of a UE (User Equipment) for transmitting UL (Uplink) RS (Reference Signal), comprising:deriving a first transmit power of a first UL RS based on a first power control mechanism, wherein derivation of the first transmit power based on the first power control mechanism is associated with an uplink data channel;deriving a second transmit power of a second UL RS based on a second power control mechanism, wherein derivation of the second transmit power based on the second power control mechanism is not associated with the uplink data channel;transmitting the first UL RS with the first transmit power;andtransmitting the second UL RS with the second transmit power.
6
Broadest claimClaim Score 72, broad(NHIP)A method of a UE (User Equipment) for transmitting UL (Uplink) RS (Reference Signal), comprising:deriving a transmit power of a UL RS based on a specific power value;transmitting the UL RS on a first UE beam of multiple UE beams with the transmit power;andtransmitting the UL RS on a second UE beam of the multiple UE beams with the transmit power.
14
A User Equipment (UE), comprising:a control circuit;a processor installed in the control circuit;anda memory installed in the control circuit and operatively coupled to the processor;wherein the processor is configured to execute a program code stored in the memory to: derive a transmit power of a UL (Uplink) RS (Reference Signal) based on a specific power value;transmit the UL RS on a first UE beam of multiple UE beams with the transmit power;andtransmit the UL RS on a second UE beam of the multiple UE beams with the transmit power.

Independent claims3

258 paragraphs in 11 sections, as filed

The present Application claims the benefit of U.S. Provisional Patent Application Ser. Nos. 62/405,533 and 62/405,564 filed on Oct. 7, 2016, the entire disclosure of which are incorporated herein in its entirety by reference.

FIELD

This disclosure generally relates to wireless communication networks, and more particularly, to a method and apparatus for deriving transmit power of UL RS in a wireless communication system.

BACKGROUND

With the rapid rise in demand for communication of large amounts of data to and from mobile communication devices, traditional mobile voice communication networks are evolving into networks that communicate with Internet Protocol (IP) data packets. Such IP data packet communication can provide users of mobile communication devices with voice over IP, multimedia, multicast and on-demand communication services.

An exemplary network structure is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide high data throughput in order to realize the above-noted voice over IP and multimedia services. A new radio technology for the next generation (e.g., 5G) is currently being discussed by the 3GPP standards organization. Accordingly, changes to the current body of 3GPP standard are currently being submitted and considered to evolve and finalize the 3GPP standard.

SUMMARY

A method and apparatus are disclosed, from the perspective of a UE (User Equipment), for transmitting UL RS. In one embodiment, the method includes deriving a first transmit power of a first UL RS based on a first power control mechanism, wherein derivation of the first transmit power based on the first power control mechanism is associated with an uplink data channel. In addition, the method includes deriving a second transmit power of a second UL RS based on a second power control mechanism, wherein derivation of the second transmit power based on the second power control mechanism is not associated with the uplink data channel. Furthermore, the method includes transmitting the first UL RS with the first transmit power. The method also includes transmitting the second UL RS with the second transmit power.

BRIEF DESCRIPTION OF THE DRAWINGS

<figref idref="DRAWINGS">FIG. 1</figref> shows a diagram of a wireless communication system according to one exemplary embodiment.

<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram of a transmitter system (also known as access network) and a receiver system (also known as user equipment or UE) according to one exemplary embodiment.

<figref idref="DRAWINGS">FIG. 3</figref> is a functional block diagram of a communication system according to one exemplary embodiment.

<figref idref="DRAWINGS">FIG. 4</figref> is a functional block diagram of the program code of <figref idref="DRAWINGS">FIG. 3</figref> according to one exemplary embodiment.

<figref idref="DRAWINGS">FIG. 5</figref> is a diagram illustrating three types of beamforming according to one exemplary embodiment.

<figref idref="DRAWINGS">FIG. 6</figref> is a reproduction of Table 5.1.1.1-1 of 3GPP TS 36.213 v13.2.0.

<figref idref="DRAWINGS">FIG. 7A</figref> is a reproduction of Table 5.1.1.1-2 of 3GPP TS 36.213 v13.2.0.

<figref idref="DRAWINGS">FIG. 7B</figref> is reproduction of Table 5.1.1.1-3 of 3GPP TS 36.213 v13.2.0.

<figref idref="DRAWINGS">FIG. 8</figref> is a reproduction of Table 5.1.2.1-1 of 3GPP TS 36.213 v13.2.0.

<figref idref="DRAWINGS">FIG. 9</figref> is a reproduction of Table 5.1.2.1-2 of 3GPP TS 36.213 v13.2.0.

<figref idref="DRAWINGS">FIG. 10</figref> is a reproduction of Table 7.2.3-0 of 3GPP TS 36.213 v13.2.0.

<figref idref="DRAWINGS">FIG. 11</figref> is a reproduction of Table 7.2.3-1 of 3GPP TS 36.213 v13.2.0.

<figref idref="DRAWINGS">FIG. 12</figref> is a reproduction of Table 7.2.3-2 of 3GPP TS 36.213 v13.2.0.

<figref idref="DRAWINGS">FIG. 13</figref> is a reproduction of Table 7.2.3-3 of 3GPP TS 36.213 v13.2.0.

<figref idref="DRAWINGS">FIG. 14</figref> is a flow chart according to one exemplary embodiment from the perspective of a UE.

<figref idref="DRAWINGS">FIG. 15</figref> is a flow chart according to one exemplary embodiment from the perspective of a UE.

<figref idref="DRAWINGS">FIG. 16</figref> is a diagram according to one exemplary embodiment.

<figref idref="DRAWINGS">FIG. 17</figref> is a diagram according to one exemplary embodiment.

<figref idref="DRAWINGS">FIG. 18</figref> is a flow chart according to one exemplary embodiment from the perspective of a UE.

<figref idref="DRAWINGS">FIG. 19</figref> is a flow chart according to one exemplary embodiment from the perspective of a UE.

<figref idref="DRAWINGS">FIG. 20</figref> is a flow chart according to one exemplary embodiment from the perspective of a UE.

DETAILED DESCRIPTION

The exemplary wireless communication systems and devices described below employ a wireless communication system, supporting a broadcast service. Wireless communication systems are widely deployed to provide various types of communication such as voice, data, and so on. These systems may be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP LTE (Long Term Evolution) wireless access, 3GPP LTE-A or LTE-Advanced (Long Term Evolution Advanced), 3GPP2 UMB (Ultra Mobile Broadband), WiMax, or some other modulation techniques.

In particular, the exemplary wireless communication systems devices described below may be designed to support one or more standards such as the standard offered by a consortium named “3rd Generation Partnership Project” referred to herein as 3GPP, including: R2-162366, “Beam Forming Impacts”, Nokia and Alcatel-Lucent; R2-163716, “Discussion on terminology of beamforming based high frequency NR”, Samsung; R2-162709, “Beam support in NR”, Intel; R2-162762, “Active Mode Mobility in NR: SINR drops in higher frequencies”, Ericsson; RP-150465, “New SI proposal: Study on Latency reduction techniques for LTE”, Ericsson and Huawei; and TS 36.213 v13.2.0, “E-UTRA; Physical layer procedures (Release 13).” The standards and documents listed above are hereby expressly incorporated by reference in their entirety.

<figref idref="DRAWINGS">FIG. 1</figref> shows a multiple access wireless communication system according to one embodiment of the invention. An access network 100 (AN) includes multiple antenna groups, one including 104 and 106, another including 108 and 110, and an additional including 112 and 114. In <figref idref="DRAWINGS">FIG. 1</figref>, only two antennas are shown for each antenna group, however, more or fewer antennas may be utilized for each antenna group. Access terminal 116 (AT) is in communication with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 over forward link 120 and receive information from access terminal 116 over reverse link 118. Access terminal (AT) 122 is in communication with antennas 106 and 108, where antennas 106 and 108 transmit information to access terminal (AT) 122 over forward link 126 and receive information from access terminal (AT) 122 over reverse link 124. In a FDD system, communication links 118, 120, 124 and 126 may use different frequency for communication. For example, forward link 120 may use a different frequency then that used by reverse link 118.

Each group of antennas and/or the area in which they are designed to communicate is often referred to as a sector of the access network. In the embodiment, antenna groups each are designed to communicate to access terminals in a sector of the areas covered by access network 100.

In communication over forward links 120 and 126, the transmitting antennas of access network 100 may utilize beamforming in order to improve the signal-to-noise ratio of forward links for the different access terminals 116 and 122. Also, an access network using beamforming to transmit to access terminals scattered randomly through its coverage causes less interference to access terminals in neighboring cells than an access network transmitting through a single antenna to all its access terminals.

An access network (AN) may be a fixed station or base station used for communicating with the terminals and may also be referred to as an access point, a Node B, a base station, an enhanced base station, an evolved Node B (eNB), or some other terminology. An access terminal (AT) may also be called user equipment (UE), a wireless communication device, terminal, access terminal or some other terminology.

<figref idref="DRAWINGS">FIG. 2</figref> is a simplified block diagram of an embodiment of a transmitter system 210 (also known as the access network) and a receiver system 250 (also known as access terminal (AT) or user equipment (UE)) in a MIMO system 200. At the transmitter system 210, traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.

In one embodiment, each data stream is transmitted over a respective transmit antenna. TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream is then modulated (i.e., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for that data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions performed by processor 230.

The modulation symbols for all data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). TX MIMO processor 220 then provides NT modulation symbol streams to NT transmitters (TMTR) 222a through 222t. In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. NT modulated signals from transmitters 222a through 222t are then transmitted from NT antennas 224a through 224t, respectively.

At receiver system 250, the transmitted modulated signals are received by NR antennas 252a through 252r and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding “received” symbol stream.

An RX data processor 260 then receives and processes the NR received symbol streams from NR receivers 254 based on a particular receiver processing technique to provide NT “detected” symbol streams. The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by RX data processor 260 is complementary to that performed by TX MIMO processor 220 and TX data processor 214 at transmitter system 210.

A processor 270 periodically determines which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

The reverse link message may comprise various types of information regarding the communication link and/or the received data stream. The reverse link message is then processed by a TX data processor 238, which also receives traffic data for a number of data streams from a data source 236, modulated by a modulator 280, conditioned by transmitters 254a through 254r, and transmitted back to transmitter system 210.

At transmitter system 210, the modulated signals from receiver system 250 are received by antennas 224, conditioned by receivers 222, demodulated by a demodulator 240, and processed by a RX data processor 242 to extract the reserve link message transmitted by the receiver system 250. Processor 230 then determines which pre-coding matrix to use for determining the beamforming weights then processes the extracted message.

Turning to <figref idref="DRAWINGS">FIG. 3</figref>, this figure shows an alternative simplified functional block diagram of a communication device according to one embodiment of the invention. As shown in <figref idref="DRAWINGS">FIG. 3</figref>, the communication device 300 in a wireless communication system can be utilized for realizing the UEs (or ATs) 116 and 122 in <figref idref="DRAWINGS">FIG. 1</figref> or the base station (or AN) 100 in <figref idref="DRAWINGS">FIG. 1</figref>, and the wireless communications system is preferably the LTE system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, a program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308, thereby controlling an operation of the communications device 300. The communications device 300 can receive signals input by a user through the input device 302, such as a keyboard or keypad, and can output images and sounds through the output device 304, such as a monitor or speakers. The transceiver 314 is used to receive and transmit wireless signals, delivering received signals to the control circuit 306, and outputting signals generated by the control circuit 306 wirelessly. The communication device 300 in a wireless communication system can also be utilized for realizing the AN 100 in <figref idref="DRAWINGS">FIG. 1</figref>.

<figref idref="DRAWINGS">FIG. 4</figref> is a simplified block diagram of the program code 312 shown in <figref idref="DRAWINGS">FIG. 3</figref> in accordance with one embodiment of the invention. In this embodiment, the program code 312 includes an application layer 400, a Layer 3 portion 402, and a Layer 2 portion 404, and is coupled to a Layer 1 portion 406. The Layer 3 portion 402 generally performs radio resource control. The Layer 2 portion 404 generally performs link control. The Layer 1 portion 406 generally performs physical connections.

As described in 3GPP R2-162366, in lower frequency bands (e.g., current LTE bands <6 GHz), the required cell coverage may be provided by forming a wide sector beam for transmitting downlink common channels. However, in utilizing wide sector beam on higher frequencies (>>6 GHz), the cell coverage is reduced with same antenna gain. Thus, in order to provide required cell coverage on higher frequency bands, higher antenna gain is needed to compensate the increased path loss. To increase the antenna gain over a wide sector beam, larger antenna arrays (number of antenna elements ranging from tens to hundreds) are used to form high gain beams.

Because the high gain beams are narrow compared to a wide sector beam, multiple beams for transmitting downlink common channels are needed to cover the required cell area. The number of concurrent high gain beams that an access point is able to form may be limited by the cost and complexity of the utilized transceiver architecture. In practice, on higher frequencies, the number of concurrent high gain beams is much less than the total number of beams required to cover the cell area. In other words, the access point is able to cover only part of the cell area by using a subset of beams at any given time.

As described in 3GPP R2-163716, beamforming is generally a signal processing technique used in antenna arrays for directional signal transmission/reception. With beamforming, a beam can be formed by combining elements in a phased array of antennas in such a way that signals at particular angles experience constructive interference while others experience destructive interference. Different beams can be utilized simultaneously using multiple arrays of antennas.

Beamforming can be generally categorized into three types of implementation: digital beamforming, hybrid beamforming, and analog beamforming. For digital beamforming, the beam is generated on the digital domain, i.e., the weighting of each antenna element can be controlled by baseband (e.g., connected to a TXRU (Transceiver Unit)). Therefore it is very easy to tune the beam direction of each subband differently across the system bandwidth. Also, to change beam direction from time to time does not require any switching time between OFDM (Orthogonal Frequency Division Multiplexing) symbols. All beams whose directions cover the whole coverage can be generated simultaneously. However, this structure requires (almost) one-to-one mapping between TXRU (transceiver/RF chain) and antenna element and is quite complicated as the number of antenna element increases and system bandwidth increases (also heat problem exists).

For analog beamforming, the beam is generated on the analog domain, i.e., the weighting of each antenna element can be controlled by an amplitude/phase shifter in the RF (Radio Frequency) circuit. Since the weighing is purely controlled by the circuit, the same beam direction would apply on the whole system bandwidth. Also, if beam direction is to be changed, switching time is required. The number of beam generated simultaneous by an analog beamforming depends on the number of TXRU. Note that for a given size of array, the increase of TXRU may decrease the antenna element of each beam, such that wider beam would be generated. In short, analog beamforming could avoid the complexity and heat problem of digital beamforming, while is more restricted in operation. Hybrid beamforming can be considered as a compromise between analog and digital beamforming, where the beam can come from both analog and digital domain. The three types of beamforming is shown in <figref idref="DRAWINGS">FIG. 5</figref>.

As discussed in 3GPP R2-162709, an eNB (evolved Node B) may have multiple TRPs (either centralized or distributed). Each TRP (Transmission/Reception Point) can form multiple beams. The number of beams and the number of simultaneous beams in the time/frequency domain depend on the number of antenna array elements and the RF at the TRP.

Potential mobility type for NR (New Radio) can be listed as follows: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0052">Intra-TRP mobility</li><li id="ul0002-0002" num="0053">Inter-TRP mobility</li><li id="ul0002-0003" num="0054">Inter-NR eNB mobility</li></ul></li></ul>

As discussed in 3GPP R2-162762, reliability of a system purely relying on beamforming and operating in higher frequencies might be challenging, since the coverage might be more sensitive to both time and space variations. As a consequence of that the SINR (Signal-to-Interference-and-Noise Ratio) of that narrow link can drop much quicker than in the case of LTE.

Using antenna arrays at access nodes with hundreds of elements, fairly regular grid-of-beams coverage patterns with tens or hundreds of candidate beams per node may be created. The coverage area of an individual beam from such array may be small, down to the order of some tens of meters in width. As a consequence, channel quality degradation outside the current serving beam area is quicker than in the case of wide area coverage, as provided by LTE.

In 3GPP RAN1 #85 meeting, some agreements about beamforming are as follows:

Agreements:

<ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0058">Following three implementations of beamforming are to be studied in NR <ul id="ul0005" list-style="none"><li id="ul0005-0001" num="0059">Analog beamforming</li><li id="ul0005-0002" num="0060">Digital beamforming</li><li id="ul0005-0003" num="0061">Hybrid beamforming</li><li id="ul0005-0004" num="0062">Note: The physical layer procedure design for NR can be agnostic to UE/TRP with respect to the beamforming implementations employed at TRP/UE, but it may pursue beamforming implementation specific optimization not to lose efficiency</li></ul></li><li id="ul0004-0002" num="0063">RAN1 studies both multi-beam based approaches and single-beam based approaches for these channels/signals/measurement/feedback <ul id="ul0006" list-style="none"><li id="ul0006-0001" num="0064">Initial-access signals (synchronization signals and random access channels)</li><li id="ul0006-0002" num="0065">System-information delivery</li><li id="ul0006-0003" num="0066">RRM measurement/feedback</li><li id="ul0006-0004" num="0067">L1 control channel</li><li id="ul0006-0005" num="0068">Others are FFS</li><li id="ul0006-0006" num="0069">Note: The physical layer procedure design for NR can be unified as much as possible whether multi-beam or single-beam based approaches are employed at TRP at least for synchronization signal detection in stand-alone initial access procedure</li><li id="ul0006-0007" num="0070">Note: single beam approach can be a special case of multi beam approach</li><li id="ul0006-0008" num="0071">Note: Individual optimization of single beam approach and multiple beam approach is possible</li></ul></li><li id="ul0004-0003" num="0072">Multi-beam based approaches <ul id="ul0007" list-style="none"><li id="ul0007-0001" num="0073">In Multi-beam based approaches, multiple beams are used for covering a DL coverage area and/or UL coverage distance of a TRP/a UE</li><li id="ul0007-0002" num="0074">One example of multi-beam based approaches is beam sweeping: <ul id="ul0008" list-style="none"><li id="ul0008-0001" num="0075">When beam sweeping is applied for a signal (or a channel), the signal (the channel) is transmitted/received on multiple beams, which are on multiple time instances in finite time duration <ul id="ul0009" list-style="none"><li id="ul0009-0001" num="0076">Single/multiple beam can be transmitted/received in a single time instance</li></ul></li></ul></li><li id="ul0007-0003" num="0077">Others are FFS</li></ul></li><li id="ul0004-0004" num="0078">Single-beam based approaches <ul id="ul0010" list-style="none"><li id="ul0010-0001" num="0079">In single-beam based approaches, the single beam can be used for covering a DL coverage area and/or UL coverage distance of a TRP/a UE, similarly as for LTE cell-specific channels/RS</li></ul></li><li id="ul0004-0005" num="0080">For both single-beam and multi-beam based approaches, RAN1 can consider followings in addition <ul id="ul0011" list-style="none"><li id="ul0011-0001" num="0081">Power boosting</li><li id="ul0011-0002" num="0082">SFN</li><li id="ul0011-0003" num="0083">Repetition</li><li id="ul0011-0004" num="0084">Beam diversity (only for multi-beam approach)</li><li id="ul0011-0005" num="0085">Antenna diversity</li><li id="ul0011-0006" num="0086">Other approaches are not precluded</li></ul></li><li id="ul0004-0006" num="0087">Combinations of single-beam based and multi-beam based approaches are not precluded</li></ul></li></ul>

Agreements:

<ul id="ul0012" list-style="none"><li id="ul0012-0001" num="0000"><ul id="ul0013" list-style="none"><li id="ul0013-0001" num="0088">RAN1 to study the beamforming procedures and their system impacts at least for multi beam based approach <ul id="ul0014" list-style="none"><li id="ul0014-0001" num="0089">Physical layer procedures for beamforming optimizing different metrics such as overheads and latencies in multi beam and single beam based approaches</li><li id="ul0014-0002" num="0090">Physical layer procedures in multi beam based approach that require beam training, i.e. steering of transmitter and/or receiver beams <ul id="ul0015" list-style="none"><li id="ul0015-0001" num="0091">E.g. Periodic/Aperiodic downlink/uplink TX/RX beam sweeping signals, where periodic signals may be semi-statically or dynamically configured (FFS)</li><li id="ul0015-0002" num="0092">E.g. UL sounding signals</li><li id="ul0015-0003" num="0093">Other example is not precluded</li></ul></li></ul></li></ul></li></ul>

Agreements:

<ul id="ul0016" list-style="none"><li id="ul0016-0001" num="0000"><ul id="ul0017" list-style="none"><li id="ul0017-0001" num="0094">Both intra-TRP and inter-TRP beamforming procedures are considered.</li><li id="ul0017-0002" num="0095">Beamforming procedures are considered with/without TRP beamforming/beam sweeping and with/without UE beamforming/beam sweeping, according to the following potential use cases: <ul id="ul0018" list-style="none"><li id="ul0018-0001" num="0096">UE movement, UE rotation, beam blocking: <ul id="ul0019" list-style="none"><li id="ul0019-0001" num="0097">Change of beam at TRP, same beam at UE</li><li id="ul0019-0002" num="0098">Same beam at TRP, change of beam at UE</li><li id="ul0019-0003" num="0099">Change of beam at TRP, change of beam at UE</li></ul></li><li id="ul0018-0002" num="0100">Other cases are not precluded</li></ul></li></ul></li></ul>

With the support of beam operation and TRP, a cell may have multiple choices to schedule a UE. For example, there may be multiple beams from a TRP transmitting the same data to the UE, which can provide more reliability for the transmission. Alternatively, multiple beams from multiple TRPs transmit the same data to the UE. To increase the throughput, it is also possible for a single TRP to transmit different data on different beams for the UE. Also, multiple TRPs can transmit different data on different beams to the UE.

In LTE system, the UL transmit power is determined by multiple factors wherein one of the factors is the DL pathloss. The pathloss is derived from CRS measurement. Besides, in legacy LTE or LTE-A, the transmit power of DM RS is tied to the corresponding UL transmission, for instance PUSCH (Physical Uplink Shared Channel) or PUCCH (Physical Uplink Control Channel). The transmit power for SRS (Sounding Reference Signal) is tied to the PUSCH for eNB to measure UL channel. More detail information can be found in Section 5 of 3GPP TS 36.213 as follows:

5 Power Control

Downlink power control determines the Energy Per Resource Element (EPRE). The term resource element energy denotes the energy prior to CP insertion. The term resource element energy also denotes the average energy taken over all constellation points for the modulation scheme applied. Uplink power control determines the average power over a SC-FDMA symbol in which the physical channel is transmitted.

5.1 Uplink Power Control

Uplink power control controls the transmit power of the different uplink physical channels. For PUSCH, the transmit power {circumflex over (P)}PUSCH,c(i) defined in subclause 5.1.1, is first scaled by the ratio of the number of antennas 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.

For PUCCH or SRS, the transmit power {circumflex over (P)}PUCCH(i), defined in subclause 5.1.1.1, or {circumflex over (P)}SRS,c(i) is split equally across the configured antenna ports for PUCCH or SRS. {circumflex over (P)}SRS,c(i) is the linear value of {circumflex over (P)}SRS,c(i) defined in subclause 5.1.3.

A cell wide overload indicator (OI) and a High Interference Indicator (HII) to control UL interference are defined in [9].

For a serving cell with frame structure type 1, a UE is not expected to be configured with UplinkPowerControlDedicated-v12x0.

5.1.1 Physical Uplink Shared Channel

If the UE is configured with a SCG, the UE shall apply the procedures described in this clause for both MCG and SCG <ul id="ul0020" list-style="none"><li id="ul0020-0001" num="0000"><ul id="ul0021" list-style="none"><li id="ul0021-0001" num="0109">When the procedures are applied for MCG, the terms ‘secondary cell’, ‘secondary cells’, ‘serving cell’, ‘serving cells’ in this clause refer to secondary cell, secondary cells, serving cell, serving cells belonging to the MCG respectively.</li><li id="ul0021-0002" num="0110">When the procedures are applied for SCG, the terms ‘secondary cell’, ‘secondary cells’, ‘serving cell’, ‘serving cells’ in this clause refer to secondary cell, secondary cells (not including PSCell), serving cell, serving cells belonging to the SCG respectively. The term ‘primary cell’ in this clause refers to the PSCell of the SCG.</li></ul></li></ul>

If the UE is configured with a PUCCH-SCell, the UE shall apply the procedures described in this clause for both primary PUCCH group and secondary PUCCH group <ul id="ul0022" list-style="none"><li id="ul0022-0001" num="0000"><ul id="ul0023" list-style="none"><li id="ul0023-0001" num="0112">When the procedures are applied for primary PUCCH group, the terms ‘secondary cell’, ‘secondary cells’, ‘serving cell’, ‘serving cells’ in this clause refer to secondary cell, secondary cells, serving cell, serving cells belonging to the primary PUCCH group respectively.</li><li id="ul0023-0002" num="0113">When the procedures are applied for secondary PUCCH group, the terms ‘secondary cell’, ‘secondary cells’, ‘serving cell’, ‘serving cells’ in this clause refer to secondary cell, secondary cells, serving cell, serving cells belonging to the secondary PUCCH group respectively.</li></ul></li></ul>

5.1.1.1 UE Behaviour

The setting of the UE Transmit power for a Physical Uplink Shared Channel (PUSCH) transmission is defined as follows.

If the UE transmits PUSCH without a simultaneous PUCCH for the serving cell c, then the UE transmit power PPUSCH,c(i) for PUSCH transmission in subframe i for the serving cell c is given by

<maths id="MATH-US-00001" num="00001"><math overflow="scroll"><mrow><mrow><msub><mi>P</mi><mrow><mi>PUSCH</mi><mo>,</mo><mi>c</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo>=</mo><mrow><mi>min</mi><mo></mo><mrow><mrow><mo>{</mo><mtable><mtr><mtd><mrow><mrow><msub><mi>P</mi><mrow><mi>CMAX</mi><mo>,</mo><mi>c</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo>,</mo></mrow></mtd></mtr><mtr><mtd><mtable><mtr><mtd><mrow><mrow><mn>10</mn><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><msub><mi>log</mi><mn>10</mn></msub><mo></mo><mrow><mo>(</mo><mrow><msub><mi>M</mi><mrow><mi>PUSCH</mi><mo>,</mo><mi>c</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo>)</mo></mrow></mrow></mrow><mo>+</mo><mrow><msub><mi>P</mi><mrow><mrow><mi>O</mi><mo></mo><mi>_</mi><mo></mo><mi>PUSCH</mi></mrow><mo>,</mo><mi>c</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mi>j</mi><mo>)</mo></mrow></mrow><mo>+</mo><mrow><mrow><msub><mi>α</mi><mi>c</mi></msub><mo></mo><mrow><mo>(</mo><mi>j</mi><mo>)</mo></mrow></mrow><mo>·</mo><msub><mi>PL</mi><mi>c</mi></msub></mrow><mo>+</mo></mrow></mtd></mtr><mtr><mtd><mrow><mrow><msub><mi>Δ</mi><mrow><mi>TF</mi><mo>,</mo><mi>c</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo>+</mo><mrow><msub><mi>f</mi><mi>c</mi></msub><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow></mrow></mtd></mtr></mtable></mtd></mtr></mtable><mo>}</mo></mrow><mo>[</mo><mstyle><mspace width="0.em" height="0.ex" /></mstyle><mo></mo><mi>dBm</mi><mo></mo><mstyle><mspace width="0.em" height="0.ex" /></mstyle><mo>]</mo></mrow></mrow></mrow></math></maths>

If the UE transmits PUSCH simultaneous with PUCCH for the serving cell c, then the UE transmit Power PPUSCH,c(i) for the PUSCH transmission in subframe i for the serving cell c is given by

<maths id="MATH-US-00002" num="00002"><math overflow="scroll"><mrow><mrow><msub><mi>P</mi><mrow><mi>PUSCH</mi><mo>,</mo><mi>c</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo>=</mo><mrow><mi>min</mi><mo></mo><mrow><mrow><mo>{</mo><mtable><mtr><mtd><mrow><mrow><mn>10</mn><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><msub><mi>log</mi><mn>10</mn></msub><mo></mo><mrow><mo>(</mo><mrow><mrow><msub><mover><mi>P</mi><mo>^</mo></mover><mrow><mi>CMAX</mi><mo>,</mo><mi>c</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo>-</mo><mrow><msub><mover><mi>P</mi><mo>^</mo></mover><mi>PUCCH</mi></msub><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow></mrow><mo>)</mo></mrow></mrow></mrow><mo>,</mo></mrow></mtd></mtr><mtr><mtd><mtable><mtr><mtd><mrow><mrow><mn>10</mn><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><msub><mi>log</mi><mn>10</mn></msub><mo></mo><mrow><mo>(</mo><mrow><msub><mi>M</mi><mrow><mi>PUSCH</mi><mo>,</mo><mi>c</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo>)</mo></mrow></mrow></mrow><mo>+</mo><mrow><msub><mi>P</mi><mrow><mrow><mi>O</mi><mo></mo><mi>_</mi><mo></mo><mi>PUSCH</mi></mrow><mo>,</mo><mi>c</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mi>j</mi><mo>)</mo></mrow></mrow><mo>+</mo><mrow><mrow><msub><mi>α</mi><mi>c</mi></msub><mo></mo><mrow><mo>(</mo><mi>j</mi><mo>)</mo></mrow></mrow><mo>·</mo><msub><mi>PL</mi><mi>c</mi></msub></mrow><mo>+</mo></mrow></mtd></mtr><mtr><mtd><mrow><mrow><msub><mi>Δ</mi><mrow><mi>TF</mi><mo>,</mo><mi>c</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo>+</mo><mrow><msub><mi>f</mi><mi>c</mi></msub><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow></mrow></mtd></mtr></mtable></mtd></mtr></mtable><mo>}</mo></mrow><mo></mo><mrow><mo>[</mo><mi>dBm</mi><mo>]</mo></mrow></mrow></mrow></mrow></math></maths>

If the UE is not transmitting PUSCH for the serving cell c, for the accumulation of TPC command received with DCI format 3/3A for PUSCH, the UE shall assume that the UE transmit power PPUSCH,c(i) for the PUSCH transmission in subframe i for the serving cell c is computed by

PPUSCH,c=min{PCMAX,c(i),PO_PUSCH,c(1)+αc(1)·PLc+fc(i)} [dBm]

where, <ul id="ul0024" list-style="none"><li id="ul0024-0001" num="0000"><ul id="ul0025" list-style="none"><li id="ul0025-0001" num="0118">{circumflex over (P)}CMAX,c(i) is the configured UE transmit power defined in [6] in subframe i for serving cell c and {circumflex over (P)}CMAX,c(i) is the linear value of PCMAX,c(i). If the UE transmits PUCCH without PUSCH in subframe i for the serving cell c, for the accumulation of TPC command received with DCI format 3/3A for PUSCH, the UE shall assume PCMAX,c(i) as given by subclause 5.1.2.1. If the UE does not transmit PUCCH and PUSCH in subframe i for the serving cell c, for the accumulation of TPC command received with DCI format 3/3A for PUSCH, the UE shall compute PCMAX,c(i) assuming MPR=0 dB, A-MPR=0 dB, P-MPR=0 dB and <img file="US2018103433A1_D0001.tif" />TC=0 dB, where MPR, A-MPR, P-MPR and <img file="US2018103433A1_D0002.tif" />TC are defined in [6].</li><li id="ul0025-0002" num="0119">{circumflex over (P)}PUCCH(i) is the linear value of PPUCCH(i) defined in subclause 5.1.2.1</li><li id="ul0025-0003" num="0120">MPUSCH,c(i) is the bandwidth of the PUSCH resource assignment expressed in number of resource blocks valid for subframe i and serving cell c.</li><li id="ul0025-0004" num="0121">If the UE is configured with higher layer parameter UplinkPowerControlDedicated-v12x0 for serving cell c and if subframe i belongs to uplink power control subframe set 2 as indicated by the higher layer parameter tpc-SubframeSet-r12, <ul id="ul0026" list-style="none"><li id="ul0026-0001" num="0122">when j=0, PO_PUSCH,c(0))=PO_UE_PUSCH,c,2(0))+PO_NOMLNAL_PUSCH,c,2(0), where j=0 is used for PUSCH (re)transmissions corresponding to a semi-persistent grant. PO_UE_PUSCH,c,2(0)) and PO_NOMINAL_PUSCH,c,2(0) are the parameters p0-UE-PUSCH-Persistent-SubframeSet2-r12 and p0-NominalPUSCH-Persistent-SubframeSet2-r12 respectively provided by higher layers, for each serving cell c.</li><li id="ul0026-0002" num="0123">when j=1, PO_PUSCH,c(1)=PO_UE_PUSCH,c,2(1)+PO_NOMINAL_PUSCH,c,2(1), where j=1 is used for PUSCH (re)transmissions corresponding to a dynamic scheduled grant. PO_UE_PUSCH,c,2(1) and PO_NOMINAL_PUSCH,c,2(1) are the parameters p0-UE-PUSCH-SubframeSet2-r12 and p0-NominalPUSCH-SubframeSet2-r12 respectively, provided by higher layers for serving cell c.</li><li id="ul0026-0003" num="0124">when j=2, PO_PUSCH,c(s)=PO_UE_PUSCH,c(2)+PO_NOMLNAL_PUSCH,c(2) where PO_UE_PUSCH,c(2)=0 and PO_NOMINAL_PUSCH,c(2)=PO_PRE+ΔPREAMBLE_Msg3, where the parameter preamblelnitialReceivedTargetPower [8] (PO_PRE) and ΔPREAMBLE_Msg3 are signalled from higher layers for serving cell c, where j=2 is used for PUSCH (re)transmissions corresponding to the random access response grant.</li></ul></li><li id="ul0025-0005" num="0125">Otherwise <ul id="ul0027" list-style="none"><li id="ul0027-0001" num="0126">PO_PUSCH,c(j) is a parameter composed of the sum of a component PO_NOMINAL_PUSCH,c(j) provided from higher layers for j=0 and 1 and a component PO_UE_PUSCH,c(j) provided by higher layers for j=0 and 1 for serving cell c. For PUSCH (re)transmissions corresponding to a semi-persistent grant then j=0, for PUSCH (re)transmissions corresponding to a dynamic scheduled grant then j=1 and for PUSCH (re)transmissions corresponding to the random access response grant then j=2. PO_UE_PUSCH,c (2)=0 and PO_NOMINAL_PUSCH,c(2)=PO-PRE+ΔPREAMBLE_Msg3, where the parameter preamblelnitialReceivedTargetPower [8] (PO_PRE) and ΔPREAMBLE_Msg3 are signalled from higher layers for serving cell c.</li></ul></li><li id="ul0025-0006" num="0127">If the UE is configured with higher layer parameter UplinkPowerControlDedicated-v12x0 for serving cell c and if subframe i belongs to uplink power control subframe set 2 as indicated by the higher layer parameter tpc-SubframeSet-r12, <ul id="ul0028" list-style="none"><li id="ul0028-0001" num="0128">For j=0 or 1, αc(j)=αc,2ϵ{0, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1}. αc,2 is the parameter alpha-SubframeSet2-r12 provided by higher layers for each serving cell c.</li><li id="ul0028-0002" num="0129">For j=2, αc(j)=1.</li></ul></li><li id="ul0025-0007" num="0130">Otherwise <ul id="ul0029" list-style="none"><li id="ul0029-0001" num="0131">For j=0 or 1, αcϵ{0, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1} is a 3-bit parameter provided by higher layers for serving cell c. For j=2, αc(j)=1.</li></ul></li><li id="ul0025-0008" num="0132">PLc is the downlink path loss estimate calculated in the UE for serving cell c in dB and PLc=referenceSignalPower higher layer filtered RSRP, where referenceSignalPower is provided by higher layers and RSRP is defined in [5] for the reference serving cell and the higher layer filter configuration is defined in [11] for the reference serving cell. <ul id="ul0030" list-style="none"><li id="ul0030-0001" num="0133">If serving cell c belongs to a TAG containing the primary cell then, for the uplink of the primary cell, the primary cell is used as the reference serving cell for determining referenceSignalPower and higher layer filtered RSRP. For the uplink of the secondary cell, the serving cell configured by the higher layer parameter pathlossReferenceLinking defined in [11] is used as the reference serving cell for determining referenceSignalPower and higher layer filtered RSRP.</li><li id="ul0030-0002" num="0134">If serving cell c belongs to a TAG containing the PSCell then, for the uplink of the PSCell, the PSCell is used as the reference serving cell for determining referenceSignalPower and higher layer filtered RSRP; for the uplink of the secondary cell other than PSCell, the serving cell configured by the higher layer parameter pathlossReferenceLinking defined in [11] is used as the reference serving cell for determining referenceSignalPower and higher layer filtered RSRP.</li><li id="ul0030-0003" num="0135">If serving cell c belongs to a TAG not containing the primary cell or PSCell then serving cell c is used as the reference serving cell for determining referenceSignalPower and higher layer filtered RSRP.</li></ul></li><li id="ul0025-0009" num="0136">ΔTF,c(i)=10 log10((2BPRE·K<sub2>s</sub2>−1)·βoffsetPUSCH) for KS=1.25 and 0 for KS=0 where KS is given by the parameter deltaMCS-Enabled provided by higher layers for each serving cell c. BPRE and βOffsetPUSCH for each serving cell c, are computed as below. KS=0 for transmission mode 2. <ul id="ul0031" list-style="none"><li id="ul0031-0001" num="0137">BPRE=OCQI/NRE for control data sent via PUSCH without UL-SCH data and</li></ul></li></ul></li></ul>

<maths id="MATH-US-00003" num="00003"><math overflow="scroll"><mrow><munderover><mo>∑</mo><mrow><mi>r</mi><mo>=</mo><mn>0</mn></mrow><mrow><mi>C</mi><mo>-</mo><mn>1</mn></mrow></munderover><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><msub><mi>K</mi><mi>r</mi></msub><mo>/</mo><msub><mi>N</mi><mi>RE</mi></msub></mrow></mrow></math></maths><ul id="ul0032" list-style="none"><li id="ul0032-0001" num="0000"><ul id="ul0033" list-style="none"><li id="ul0033-0001" num="0000"><ul id="ul0034" list-style="none"><li id="ul0034-0001" num="0000"> for other cases. <ul id="ul0035" list-style="none"><li id="ul0035-0001" num="0138">where c is the number of code blocks, Kr is the size for code block r, OCQI is the number of CQI/PMI bits including CRC bits and NRE is the number of resource elements determined as NRE=MscPUSCH-initial·NsymbPUSCH-initial, where C, Kr, MscPUSCH-intitial and NsymbPUSCH-initial are defined in [4].</li></ul></li><li id="ul0034-0002" num="0139">βoffsetPUSCH=βoffsetCQI for control data sent via PUSCH without UL-SCH data and 1 for other cases.</li></ul></li><li id="ul0033-0002" num="0140">δPUSCH,c is a correction value, also referred to as a TPC command and is included in PDCCH/EPDCCH with DCI format 0/4 or in MPDCCH with DCI format 6-0A for serving cell c or jointly coded with other TPC commands in PDCCH/MPDCCH with DCI format 3/3A whose CRC parity bits are scrambled with TPC-PUSCH-RNTI. If the UE is configured with higher layer parameter UplinkPowerControlDedicated-v12x0 for serving cell c and if subframe i belongs to uplink power control subframe set 2 as indicated by the higher layer parameter tpc-SubframeSet-r12, the current PUSCH power control adjustment state for serving cell c is given by fc,2(i), and the UE shall use fc,2(i) instead of fc(i) to determine PPUSCH,c(i). Otherwise, the current PUSCH power control adjustment state for serving cell c is given by fc(i) fc,2(i) and fc(i) are defined by: <ul id="ul0036" list-style="none"><li id="ul0036-0001" num="0141">fc(i)=fc(i−1)+δPUSCH,c(i−KPUSCH) and fc,2(i)=fc,2(i−1)+δPUSCH,c(i−KPUSCH) if accumulation is enabled based on the parameter Accumulation-enabled provided by higher layers or if the TPC command δPUSCH,c is included in a PDCCH/EPDCCH with DCI format 0 or in a MPDCCH with DCI format 6-0A for serving cell c where the CRC is scrambled by the Temporary C-RNTI <ul id="ul0037" list-style="none"><li id="ul0037-0001" num="0142">where δPUSCH,c(i−KPUSCH) was signalled on PDCCH/EPDCCH with DCI format 0/4 or MPDCCH with DCI format 6-0A or PDCCH/MPDCCH with DCI format 3/3A on subframe i−KPUSCH, and where fc(0) is the first value after reset of accumulation. For a BL/CE UE configured with CEModeA, subframe i−KPUSCH is the last subframe in which the MPDCCH with DCI format 6-0A or MPDCCH with DCI format 3/3A is transmitted.</li><li id="ul0037-0002" num="0143">The value of KPUSCH is <ul id="ul0038" list-style="none"><li id="ul0038-0001" num="0144">For FDD or FDD-TDD and serving cell frame structure type 1, KPUSCH=4</li><li id="ul0038-0002" num="0145">For TDD, if the UE is configured with more than one serving cell and the TDD UL/DL configuration of at least two configured serving cells is not the same, or if the UE is configured with the parameter EIMTA-MainConfigServCell-r12 for at least one serving cell, or for FDD-TDD and serving cell frame structure type 2, the “TDD UL/DL configuration” refers to the UL-reference UL/DL configuration (defined in subclause 8.0) for serving cell c.</li><li id="ul0038-0003" num="0146">For TDD UL/DL configurations 1-6, KPUSCH is given in Table 5.1.1.1-1</li><li id="ul0038-0004" num="0147">For TDD UL/DL configuration 0</li><li id="ul0038-0005" num="0000"> If the PUSCH transmission in subframe 2 or 7 is scheduled with a PDCCH/EPDCCH of DCI format 0/4 or a MPDCCH of DCI format 6-0A in which the LSB of the UL index is set to 1, KPUSCH=7</li><li id="ul0038-0006" num="0000"> For all other PUSCH transmissions, KPUSCH is given in Table 5.1.1.1-1.</li></ul></li><li id="ul0037-0003" num="0148">For serving cell c and a non-BL/CE UE, the UE attempts to decode a PDCCH/EPDCCH of DCI format 0/4 with the UE's C-RNTI or DCI format 0 for SPS C-RNTI and a PDCCH of DCI format 3/3A with this UE's TPC-PUSCH-RNTI in every subframe except when in DRX or where serving cell c is deactivated.</li><li id="ul0037-0004" num="0149">For serving cell c and a BL/CE UE configured with CEModeA, the UE attempts to decode a MPDCCH of DCI format 6-0A with the UE's C-RNTI or SPS C-RNTI and a MPDCCH of DCI format 3/3A with this UE's TPC-PUSCH-RNTI in every BL/CE downlink subframe except when in DRX</li><li id="ul0037-0005" num="0150">For a non-BL/CE UE, if DCI format 0/4 for serving cell sand DCI format 3/3A are both detected in the same subframe, then the UE shall use the δPUSCH,c provided in DCI format 0/4.</li><li id="ul0037-0006" num="0151">For a BL/CE UE configured with CEModeA, if DCI format 6-0A for serving cell sand DCI format 3/3A are both detected in the same subframe, then the UE shall use the δPUSCH,c provided in DCI format 6-0A.</li><li id="ul0037-0007" num="0152">ΔPUSCH,c=0 dB for a subframe where no TPC command is decoded for serving cell c or where DRX occurs or i is not an uplink subframe in TDD or FDD-TDD and serving cell c frame structure type 2.</li><li id="ul0037-0008" num="0153">The δPUSCH,c dB accumulated values signalled on PDCCH/EPDCCH with DCI format 0/4 or MPDCCH with DCI format 6-0A are given in Table 5.1.1.1-2. If the PDCCH/EPDCCH with DCI format 0 or MPDCCH with DCI format 6-0A is validated as a SPS activation or release PDCCH/EPDCCH/MPDCCH, then δPUSCH, is 0 dB.</li><li id="ul0037-0009" num="0154">The δPUSCH dB accumulated values signalled on PDCCH/MPDCCH with DCI format 3/3A are one of SET1 given in Table 5.1.1.1-2 or SET2 given in Table 5.1.1.1-3 as determined by the parameter TPC-Index provided by higher layers.</li><li id="ul0037-0010" num="0155">If UE has reached PCMAX,c(i) for serving cell c, positive TPC commands for serving cell c shall not be accumulated</li><li id="ul0037-0011" num="0156">If UE has reached minimum power, negative TPC commands shall not be accumulated</li><li id="ul0037-0012" num="0157">If the UE is not configured with higher layer parameter UplinkPowerControlDedicated-v12x0 for serving cell c, the UE shall reset accumulation <ul id="ul0039" list-style="none"><li id="ul0039-0001" num="0158">For serving cell c, when PO_UE_PUSCH,c value is changed by higher layers</li><li id="ul0039-0002" num="0159">For serving cell c, when the UE receives random access response message for serving cell c</li></ul></li><li id="ul0037-0013" num="0160">If the UE is configured with higher layer parameter UplinkPowerControlDedicated-v12x0 for serving cell c, <ul id="ul0040" list-style="none"><li id="ul0040-0001" num="0161">the UE shall reset accumulation corresponding to fc(*) for serving cell c</li><li id="ul0040-0002" num="0000"> when PO_UE_PUSCH,c value is changed by higher layers</li><li id="ul0040-0003" num="0000"> when the UE receives random access response message for serving cell c</li><li id="ul0040-0004" num="0162">the UE shall reset accumulation corresponding to fc,2(*) for serving cell c</li><li id="ul0040-0005" num="0000"> when PO_UE_PUSCH,c,2 value is changed by higher layers</li></ul></li><li id="ul0037-0014" num="0163">If the UE is configured with higher layer parameter UplinkPowerControlDedicated-v12x0 for serving cell c and <ul id="ul0041" list-style="none"><li id="ul0041-0001" num="0164">if subframe i belongs to uplink power control subframe set 2 as indicated by the higher layer parameter tpc-SubframeSet-r12 fc(i)=fc(i−1)</li><li id="ul0041-0002" num="0165">if subframe i does not belong to uplink power control subframe set 2 as indicated by the higher layer parameter tpc-SubframeSet-r12 fc,2(i)=fc,2(i−1)</li></ul></li></ul></li><li id="ul0036-0002" num="0166">fc(i)=δPUSCH,c(i−KPUSCH) and fc,2=δPUSCH,c(i−KPUSCH) if accumulation is not enabled for serving cell c based on the parameter Accumulation-enabled provided by higher layers <ul id="ul0042" list-style="none"><li id="ul0042-0001" num="0167">where δPUSCH,c(i−KPUSCH) was signalled on PDCCH/EPDCCH with DCI format 0/4 or MPDCCH with DCI format 6-0A for serving cell c on subframe i−KPUSCH. For a BL/CE UE configured with CEModeA, subframe i−KPUSCH is the last subframe in which the MPDCCH with DCI format 6-0A or MPDCCH with DCI format 3/3A is transmitted.</li><li id="ul0042-0002" num="0168">The value of KPUSCH is <ul id="ul0043" list-style="none"><li id="ul0043-0001" num="0169">For FDD or FDD-TDD and serving cell frame structure type 1, KPUSCH=4</li><li id="ul0043-0002" num="0170">For TDD, if the UE is configured with more than one serving cell and the TDD UL/DL configuration of at least two configured serving cells is not the same, or if the UE is configured with the parameter EIMTA-MainConfigServCell-r12 for at least one serving cell, or FDD-TDD and serving cell frame structure type 2, the “TDD UL/DL configuration” refers to the UL-reference UL/DL configuration (defined in subclause 8.0) for serving cell c.</li><li id="ul0043-0003" num="0171">For TDD UL/DL configurations 1-6, KPUSCH is given in Table 5.1.1.1-1.</li><li id="ul0043-0004" num="0172">For TDD UL/DL configuration 0</li><li id="ul0043-0005" num="0000"> If the PUSCH transmission in subframe 2 or 7 is scheduled with a PDCCH/EPDCCH of DCI format 0/4 or a MPDCCH with DCI format 6-0A in which the LSB of the UL index is set to 1, KPUSCH=7</li><li id="ul0043-0006" num="0000"> For all other PUSCH transmissions, KPUSCH is given in Table 5.1.1.1-1.</li></ul></li><li id="ul0042-0003" num="0173">The δPUSCH,c dB absolute values signalled on PDCCH/EPDCCH with DCI format 0/4 or a MPDCCH with DCI format 6-0A are given in Table 5.1.1.1-2. If the PDCCH/EPDCCH with DCI format 0 or a MPDCCH with DCI format 6-0A is validated as a SPS activation or release PDCCH/EPDCCH/MPDCCH, then δPUSCH,c is 0 dB.</li><li id="ul0042-0004" num="0174">for a non-BL/CE UE, fc(i)=fc(i−1) and fc,2(i)=fc,2(i−1) for a subframe where no PDCCH/EPDCCH with DCI format 0/4 is decoded for serving cell c or where DRX occurs or i is not an uplink subframe in TDD or FDD-TDD and serving cell c frame structure type 2.</li><li id="ul0042-0005" num="0175">for a BL/CE UE configured with CEModeA, fc(i)=fc(i−1) and fc,2(i)=fc,2(i−1) for a subframe where no MPDCCH with DCI format 6-0A is decoded for serving cell c or where DRX occurs or i is not an uplink subframe in TDD.</li><li id="ul0042-0006" num="0176">If the UE is configured with higher layer parameter UplinkPowerControlDedicated-v12x0 for serving cell c and <ul id="ul0044" list-style="none"><li id="ul0044-0001" num="0177">if subframe i belongs to uplink power control subframe set 2 as indicated by the higher layer parameter tpc-SubframeSet-r12 fc(i)=fc(i−1)</li><li id="ul0044-0002" num="0178">if subframe i does not belong to uplink power control subframe set 2 as indicated by the higher layer parameter tpc-SubframeSet-r12 fc,2(i)=fc,2(i−1)</li></ul></li></ul></li><li id="ul0036-0003" num="0179">For both types of fc(*) (accumulation or current absolute) the first value is set as follows: <ul id="ul0045" list-style="none"><li id="ul0045-0001" num="0180">If PO_UE_PUSCH,c value is changed by higher layers and serving cell c is the primary cell or, if PO_UE_PUSCH,c value is received by higher layers and serving cell c is a Secondary cell <ul id="ul0046" list-style="none"><li id="ul0046-0001" num="0181">fc(0)=0</li></ul></li><li id="ul0045-0002" num="0182">Else <ul id="ul0047" list-style="none"><li id="ul0047-0001" num="0183">If the UE receives the random access response message for a serving cell c</li><li id="ul0047-0002" num="0000"> fc(o)ΔPrampup,c+δmsg2,c, where</li><li id="ul0047-0003" num="0000"> δmsg2,c is the TPC command indicated in the random access response corresponding to the random access preamble transmitted in the serving cell c, see subclause 6.2, and</li></ul></li></ul></li></ul></li></ul></li></ul>

<maths id="MATH-US-00004" num="00004"><math overflow="scroll"><mrow><mrow><mi>Δ</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><msub><mi>P</mi><mrow><mi>rampup</mi><mo>,</mo><mi>c</mi></mrow></msub></mrow><mo>=</mo><mrow><mi>min</mi><mo>[</mo><mrow><mrow><mo>{</mo><mrow><mi>max</mi><mo>(</mo><mrow><mn>0</mn><mo>,</mo><mrow><msub><mi>P</mi><mrow><mi>CMAX</mi><mo>,</mo><mi>c</mi></mrow></msub><mo>-</mo><mrow><mo>(</mo><mtable><mtr><mtd><mrow><mrow><mn>10</mn><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mrow><msub><mi>log</mi><mn>10</mn></msub><mo></mo><mrow><mo>(</mo><mrow><msub><mi>M</mi><mrow><mi>PUSCH</mi><mo>,</mo><mi>c</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mn>0</mn><mo>)</mo></mrow></mrow><mo>)</mo></mrow></mrow></mrow><mo>+</mo></mrow></mtd></mtr><mtr><mtd><mrow><mrow><msub><mi>P</mi><mrow><mrow><mi>O</mi><mo></mo><mi>_</mi><mo></mo><mi>PUSCH</mi></mrow><mo>,</mo><mi>c</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mn>2</mn><mo>)</mo></mrow></mrow><mo>+</mo><msub><mi>δ</mi><mrow><mi>msg</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mn>2</mn></mrow></msub><mo>+</mo></mrow></mtd></mtr><mtr><mtd><mrow><mrow><mrow><msub><mi>α</mi><mi>c</mi></msub><mo></mo><mrow><mo>(</mo><mn>2</mn><mo>)</mo></mrow></mrow><mo>·</mo><mi>PL</mi></mrow><mo>+</mo><mrow><msub><mi>Δ</mi><mrow><mi>TF</mi><mo>,</mo><mi>c</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mn>0</mn><mo>)</mo></mrow></mrow></mrow></mtd></mtr></mtable><mo>)</mo></mrow></mrow></mrow><mo>)</mo></mrow><mo>}</mo></mrow><mo>,</mo><msub><mi>P</mi><mrow><mi>rampuprequested</mi><mo>,</mo><mi>c</mi></mrow></msub></mrow><mo>]</mo></mrow></mrow></math></maths><ul id="ul0048" list-style="none"><li id="ul0048-0001" num="0000"><ul id="ul0049" list-style="none"><li id="ul0049-0001" num="0000"><ul id="ul0050" list-style="none"><li id="ul0050-0001" num="0000"><ul id="ul0051" list-style="none"><li id="ul0051-0001" num="0000"><ul id="ul0052" list-style="none"><li id="ul0052-0001" num="0184">and ΔPrampuprequested,c is provided by higher layers and corresponds to the total power ramp-up requested by higher layers from the first to the last preamble in the serving cell c, MPUSCH,c(0) is the bandwidth of the PUSCH resource assignment expressed in number of resource blocks valid for the subframe of first PUSCH transmission in the serving cell c, and ΔTF,c(0) is the power adjustment of first PUSCH transmission in the serving cell c.</li><li id="ul0052-0002" num="0185">If PO_UE_PUSCH,c,2 value is received by higher layers for a serving cell c.</li><li id="ul0052-0003" num="0000"> fc,2=0</li></ul></li></ul></li></ul></li></ul></li></ul>

Table 5.1.1.1-1 of 3GPP TS 36.213 v13.2.0, Entitled “K

PUSCH

for TDD Configuration 0-6”, is Reproduced as FIG.

Table 5.1.1.1-2 of 3GPP TS 36.213 v13.2.0, Entitled “Mapping of TPC Command Field in DCI Format 0/3/4 to Absolute and Accumulated δ

PUSCH,c

Values”, is Reproduced as FIG.

A

Table 5.1.1.1-3 of 3GPP TS 36.213 v13.2.0, Entitled “Mapping of TPC Command Field in DCI Format 3A to Accumulated δ

PUSCH,c

Values”, is Reproduced as FIG.

B

[ . . . ]

5.1.2 Physical Uplink Control Channel

If the UE is configured with a SCG, the UE shall apply the procedures described in this subclause for both MCG and SCG. <ul id="ul0053" list-style="none"><li id="ul0053-0001" num="0000"><ul id="ul0054" list-style="none"><li id="ul0054-0001" num="0188">When the procedures are applied for MCG, the term ‘serving cell’ in this subclause refers to serving cell belonging to the MCG.</li></ul></li></ul>

When the procedures are applied for SCG, the term ‘serving cell’ in this subclause refers to serving cell belonging to the SCG. The term ‘primary cell’ in this subclause refers to the PSCell of the SCG. If the UE is configured with a PUCCH-SCell, the UE shall apply the procedures described in this subclause for both primary PUCCH group and secondary PUCCH group. <ul id="ul0055" list-style="none"><li id="ul0055-0001" num="0000"><ul id="ul0056" list-style="none"><li id="ul0056-0001" num="0190">When the procedures are applied for the primary PUCCH group, the term ‘serving cell’ in this subclause refers to serving cell belonging to the primary PUCCH group.</li><li id="ul0056-0002" num="0191">When the procedures are applied for the secondary PUCCH group, the term ‘serving cell’ in this subclause refers to serving cell belonging to the secondary PUCCH group. The term ‘primary cell’ in this subclause refers to the PUCCH-SCell of the secondary PUCCH group.</li></ul></li></ul>

5.1.2.1 UE Behaviour

If serving cell c is the primary cell, for PUCCH format 1/1a/1b/2/2a/2b/3, the setting of the UE Transmit power PPUCCH for the physical uplink control channel (PUCCH) transmission in subframe i for serving cell c is defined by

<maths id="MATH-US-00005" num="00005"><math overflow="scroll"><mrow><mrow><msub><mi>P</mi><mi>PUCCH</mi></msub><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo>=</mo><mrow><mo> </mo><mrow><mi>min</mi><mo></mo><mrow><mrow><mo>{</mo><mtable><mtr><mtd><mrow><mrow><msub><mi>P</mi><mrow><mi>CMAX</mi><mo>,</mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>c</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo>,</mo></mrow></mtd></mtr><mtr><mtd><mrow><msub><mi>P</mi><mrow><mn>0</mn><mo></mo><mi>_PUCCH</mi></mrow></msub><mo>+</mo><msub><mi>PL</mi><mi>c</mi></msub><mo>+</mo><mrow><mi>h</mi><mo></mo><mrow><mo>(</mo><mrow><msub><mi>n</mi><mi>CQI</mi></msub><mo>,</mo><msub><mi>n</mi><mi>HARQ</mi></msub><mo>,</mo><msub><mi>n</mi><mi>SR</mi></msub></mrow><mo>)</mo></mrow></mrow><mo>+</mo><mrow><msub><mi>Δ</mi><mi>F_PUCCH</mi></msub><mo></mo><mrow><mo>(</mo><mi>F</mi><mo>)</mo></mrow></mrow><mo>+</mo><mrow><msub><mi>Δ</mi><mrow><mi>T</mi><mo>×</mo><mi>D</mi></mrow></msub><mo></mo><mrow><mo>(</mo><msup><mi>F</mi><mi>′</mi></msup><mo>)</mo></mrow></mrow><mo>+</mo><mrow><mi>g</mi><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow></mrow></mtd></mtr></mtable><mo>}</mo></mrow><mo></mo><mrow><mo>[</mo><mi>dBm</mi><mo>]</mo></mrow></mrow></mrow></mrow></mrow></math></maths>

If serving cell cis the primary cell, for PUCCH format 4/5, the setting of the UE Transmit power PPUCCH for the physical uplink control channel (PUCCH) transmission in subframe i for serving cell c is defined by

<maths id="MATH-US-00006" num="00006"><math overflow="scroll"><mrow><mrow><mrow><mrow><msub><mi>P</mi><mi>PUCCH</mi></msub><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo>=</mo></mrow><mo> </mo></mrow><mo></mo><mrow><mo> </mo><mrow><mi>min</mi><mo></mo><mrow><mo>{</mo><mtable><mtr><mtd><mrow><mrow><msub><mi>P</mi><mrow><mi>CMAX</mi><mo>,</mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>c</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo>,</mo></mrow></mtd></mtr><mtr><mtd><mrow><msub><mi>P</mi><mrow><mn>0</mn><mo></mo><mi>_PUCCH</mi></mrow></msub><mo>+</mo><msub><mi>PL</mi><mi>c</mi></msub><mo>+</mo><mrow><mn>10</mn><mo></mo><mrow><msub><mi>log</mi><mn>10</mn></msub><mo></mo><mrow><mo>(</mo><mrow><msub><mi>M</mi><mrow><mi>PUCCH</mi><mo>,</mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>c</mi></mrow></msub><mo>,</mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo>)</mo></mrow></mrow></mrow><mo>+</mo><mrow><msub><mi>Δ</mi><mrow><mi>TF</mi><mo>,</mo><mi>c</mi></mrow></msub><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo>+</mo><mrow><msub><mi>Δ</mi><mi>F_PUCCH</mi></msub><mo></mo><mrow><mo>(</mo><mi>F</mi><mo>)</mo></mrow></mrow><mo>+</mo><mrow><mi>g</mi><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow></mrow></mtd></mtr></mtable><mo>}</mo></mrow><mo></mo><mrow><mo> </mo><mstyle><mspace width="0.em" height="0.ex" /></mstyle><mo></mo><mrow><mo>[</mo><mi>dBm</mi><mo>]</mo></mrow></mrow></mrow></mrow></mrow></math></maths>

If the UE is not transmitting PUCCH for the primary cell, for the accumulation of TPC command for PUCCH, the UE shall assume that the UE transmit power PPUCCH for PUCCH in subframe i is computed by

PPUCCH(i)=min{PCMAX,c(i),P0_PUCCH+PLc+g(i)} [dBm]

where <ul id="ul0057" list-style="none"><li id="ul0057-0001" num="0000"><ul id="ul0058" list-style="none"><li id="ul0058-0001" num="0195">PCMAX,c(i) is the configured UE transmit power defined in [6] in subframe i for serving cell c. If the UE transmits PUSCH without PUCCH in subframe i for the serving cell c, for the accumulation of TPC command for PUCCH, the UE shall assume PCMAX,c(i) as given by subclause 5.1.1.1. If the UE does not transmit PUCCH and PUSCH in subframe i for the serving cell c, for the accumulation of TPC command for PUCCH, the UE shall compute PCMAX,c(i) assuming MPR=0 dB, A-MPR=0 dB, P-MPR=0 dB and <img file="US2018103433A1_D0003.tif" />TC=0 dB, where MPR, A-MPR, P-MPR and <img file="US2018103433A1_D0004.tif" />TC are defined in [6].</li><li id="ul0058-0002" num="0196">The parameter ΔF_PUCCH(F) is provided by higher layers. Each ΔF_PUCCH(F) value corresponds to a PUCCH format (F) relative to PUCCH format 1a, where each PUCCH format (F) is defined in Table 5.4-1 of [3].</li><li id="ul0058-0003" num="0197">If the UE is configured by higher layers to transmit PUCCH on two antenna ports, the value of ΔTxD(F′) is provided by higher layers where each PUCCH format F′ is defined in Table 5.4-1 of [3]; otherwise, ΔTxD(F′)=0.</li><li id="ul0058-0004" num="0198">h(nCQI,nHARQ,nSR) is a PUCCH format dependent value, where nCQI corresponds to the number of information bits for the channel quality information defined in subclause 5.2.3.3 in [4]. nSR=1 if subframe i is configured for SR for the UE not having any associated transport block for UL-SCH, otherwise nSR=0. If the UE is configured with more than one serving cell, or the UE is configured with one serving cell and transmitting using PUCCH format 3, the value of nHARQ is defined in subclause 10.1; otherwise, nHARQ is the number of HARQ-ACK bits sent in subframe i. <ul id="ul0059" list-style="none"><li id="ul0059-0001" num="0199">For PUCCH format 1,1a and 1b h(nCQI,nHARQ,nSR)=0</li><li id="ul0059-0002" num="0200">For PUCCH format 1b with channel selection, if the UE is configured with more than one serving cell,</li></ul></li></ul></li></ul>

<maths id="MATH-US-00007" num="00007"><math overflow="scroll"><mrow><mrow><mrow><mi>h</mi><mo></mo><mrow><mo>(</mo><mrow><msub><mi>n</mi><mi>CQI</mi></msub><mo>,</mo><msub><mi>n</mi><mi>HARQ</mi></msub><mo>,</mo><msub><mi>n</mi><mi>SR</mi></msub></mrow><mo>)</mo></mrow></mrow><mo>=</mo><mfrac><mrow><mo>(</mo><mrow><msub><mi>n</mi><mi>HARQ</mi></msub><mo>-</mo><mn>1</mn></mrow><mo>)</mo></mrow><mn>2</mn></mfrac></mrow><mo>,</mo></mrow></math></maths><ul id="ul0060" list-style="none"><li id="ul0060-0001" num="0000"><ul id="ul0061" list-style="none"><li id="ul0061-0001" num="0000"><ul id="ul0062" list-style="none"><li id="ul0062-0001" num="0000"> otherwise, h(nCQI,nHARQ,nSR)=0</li><li id="ul0062-0002" num="0201">For PUCCH format 2, 2a, 2b and normal cyclic prefix</li></ul></li></ul></li></ul>

<maths id="MATH-US-00008" num="00008"><math overflow="scroll"><mrow><mrow><mi>h</mi><mo></mo><mrow><mo>(</mo><mrow><msub><mi>n</mi><mi>CQI</mi></msub><mo>,</mo><msub><mi>n</mi><mi>HARQ</mi></msub><mo>,</mo><msub><mi>n</mi><mi>SR</mi></msub></mrow><mo>)</mo></mrow></mrow><mo>=</mo><mrow><mo>{</mo><mtable><mtr><mtd><mrow><mn>10</mn><mo></mo><mrow><msub><mi>log</mi><mn>10</mn></msub><mo></mo><mrow><mo>(</mo><mfrac><msub><mi>n</mi><mi>CQI</mi></msub><mn>4</mn></mfrac><mo>)</mo></mrow></mrow></mrow></mtd><mtd><mrow><mrow><mi>if</mi><mo></mo><mstyle><mspace width="0.8em" height="0.8ex" /></mstyle><mo></mo><msub><mi>n</mi><mi>CQI</mi></msub></mrow><mo>≥</mo><mn>4</mn></mrow></mtd></mtr><mtr><mtd><mn>0</mn></mtd><mtd><mi>otherwise</mi></mtd></mtr></mtable></mrow></mrow></math></maths><ul id="ul0063" list-style="none"><li id="ul0063-0001" num="0000"><ul id="ul0064" list-style="none"><li id="ul0064-0001" num="0000"><ul id="ul0065" list-style="none"><li id="ul0065-0001" num="0202">For PUCCH format 2 and extended cyclic prefix</li></ul></li></ul></li></ul>

<maths id="MATH-US-00009" num="00009"><math overflow="scroll"><mrow><mrow><mi>h</mi><mo></mo><mrow><mo>(</mo><mrow><msub><mi>n</mi><mi>CQI</mi></msub><mo>,</mo><msub><mi>n</mi><mi>HARQ</mi></msub><mo>,</mo><msub><mi>n</mi><mi>SR</mi></msub></mrow><mo>)</mo></mrow></mrow><mo>=</mo><mrow><mo>{</mo><mtable><mtr><mtd><mrow><mn>10</mn><mo></mo><mrow><msub><mi>log</mi><mn>10</mn></msub><mo></mo><mrow><mo>(</mo><mfrac><mrow><msub><mi>n</mi><mi>CQI</mi></msub><mo>+</mo><msub><mi>n</mi><mi>HARQ</mi></msub></mrow><mn>4</mn></mfrac><mo>)</mo></mrow></mrow></mrow></mtd><mtd><mrow><mrow><mrow><mi>if</mi><mo></mo><mstyle><mspace width="0.8em" height="0.8ex" /></mstyle><mo></mo><msub><mi>n</mi><mi>CQI</mi></msub></mrow><mo>+</mo><msub><mi>n</mi><mi>HARQ</mi></msub></mrow><mo>≥</mo><mn>4</mn></mrow></mtd></mtr><mtr><mtd><mn>0</mn></mtd><mtd><mi>otherwise</mi></mtd></mtr></mtable></mrow></mrow></math></maths><ul id="ul0066" list-style="none"><li id="ul0066-0001" num="0000"><ul id="ul0067" list-style="none"><li id="ul0067-0001" num="0000"><ul id="ul0068" list-style="none"><li id="ul0068-0001" num="0203">For PUCCH format 3 and when UE transmits HARQ-ACK/SR without periodic CSI, <ul id="ul0069" list-style="none"><li id="ul0069-0001" num="0204">If the UE is configured by higher layers to transmit PUCCH format 3 on two antenna ports, or if the UE transmits more than 11 bits of HARQ-ACK/SR</li></ul></li></ul></li></ul></li></ul>

<maths id="MATH-US-00010" num="00010"><math overflow="scroll"><mrow><mrow><mi>h</mi><mo></mo><mrow><mo>(</mo><mrow><msub><mi>n</mi><mi>CQI</mi></msub><mo>,</mo><msub><mi>n</mi><mi>HARQ</mi></msub><mo>,</mo><msub><mi>n</mi><mi>SR</mi></msub></mrow><mo>)</mo></mrow></mrow><mo>=</mo><mfrac><mrow><msub><mi>n</mi><mi>HARQ</mi></msub><mo>+</mo><msub><mi>n</mi><mi>SR</mi></msub><mo>-</mo><mn>1</mn></mrow><mn>3</mn></mfrac></mrow></math></maths><ul id="ul0070" list-style="none"><li id="ul0070-0001" num="0000"><ul id="ul0071" list-style="none"><li id="ul0071-0001" num="0000"><ul id="ul0072" list-style="none"><li id="ul0072-0001" num="0000"><ul id="ul0073" list-style="none"><li id="ul0073-0001" num="0205">Otherwise</li></ul></li></ul></li></ul></li></ul>

<maths id="MATH-US-00011" num="00011"><math overflow="scroll"><mrow><mrow><mi>h</mi><mo></mo><mrow><mo>(</mo><mrow><msub><mi>n</mi><mi>CQI</mi></msub><mo>,</mo><msub><mi>n</mi><mi>HARQ</mi></msub><mo>,</mo><msub><mi>n</mi><mi>SR</mi></msub></mrow><mo>)</mo></mrow></mrow><mo>=</mo><mfrac><mrow><msub><mi>n</mi><mi>HARQ</mi></msub><mo>+</mo><msub><mi>n</mi><mi>SR</mi></msub><mo>-</mo><mn>1</mn></mrow><mn>2</mn></mfrac></mrow></math></maths><ul id="ul0074" list-style="none"><li id="ul0074-0001" num="0000"><ul id="ul0075" list-style="none"><li id="ul0075-0001" num="0000"><ul id="ul0076" list-style="none"><li id="ul0076-0001" num="0206">For PUCCH format 3 and when UE transmits HARQ-ACK/SR and periodic CSI, <ul id="ul0077" list-style="none"><li id="ul0077-0001" num="0207">If the UE is configured by higher layers to transmit PUCCH format 3 on two antenna ports, or if the UE transmits more than 11 bits of HARQ-ACK/SR and CSI</li></ul></li></ul></li></ul></li></ul>

<maths id="MATH-US-00012" num="00012"><math overflow="scroll"><mrow><mrow><mi>h</mi><mo></mo><mrow><mo>(</mo><mrow><msub><mi>n</mi><mi>CQI</mi></msub><mo>,</mo><msub><mi>n</mi><mi>HARQ</mi></msub><mo>,</mo><msub><mi>n</mi><mi>SR</mi></msub></mrow><mo>)</mo></mrow></mrow><mo>=</mo><mfrac><mrow><msub><mi>n</mi><mi>HARQ</mi></msub><mo>+</mo><msub><mi>n</mi><mi>SR</mi></msub><mo>+</mo><msub><mi>n</mi><mi>CQI</mi></msub><mo>-</mo><mn>1</mn></mrow><mn>3</mn></mfrac></mrow></math></maths><ul id="ul0078" list-style="none"><li id="ul0078-0001" num="0000"><ul id="ul0079" list-style="none"><li id="ul0079-0001" num="0000"><ul id="ul0080" list-style="none"><li id="ul0080-0001" num="0000"><ul id="ul0081" list-style="none"><li id="ul0081-0001" num="0208">Otherwise</li></ul></li></ul></li></ul></li></ul>

<maths id="MATH-US-00013" num="00013"><math overflow="scroll"><mrow><mrow><mi>h</mi><mo></mo><mrow><mo>(</mo><mrow><msub><mi>n</mi><mi>CQI</mi></msub><mo>,</mo><msub><mi>n</mi><mi>HARQ</mi></msub><mo>,</mo><msub><mi>n</mi><mi>SR</mi></msub></mrow><mo>)</mo></mrow></mrow><mo>=</mo><mfrac><mrow><msub><mi>n</mi><mi>HARQ</mi></msub><mo>+</mo><msub><mi>n</mi><mi>SR</mi></msub><mo>+</mo><msub><mi>n</mi><mi>CQI</mi></msub><mo>-</mo><mn>1</mn></mrow><mn>2</mn></mfrac></mrow></math></maths><ul id="ul0082" list-style="none"><li id="ul0082-0001" num="0000"><ul id="ul0083" list-style="none"><li id="ul0083-0001" num="0000"><ul id="ul0084" list-style="none"><li id="ul0084-0001" num="0209">For PUCCH format 4, MPUCCH,c(i) is the bandwidth of the PUCCH format 4 expressed in number of resource blocks valid for subframe i and serving cell c. For PUCCH format 5, MPUCCH,c(i)=1.</li><li id="ul0084-0002" num="0210">ΔTF,c(i)=10 log10(21.25·BPRE(i)−1) where BPRE(i)=OUCI(i)/NRE(i), <ul id="ul0085" list-style="none"><li id="ul0085-0001" num="0211">OUCI(i) is the number of HARQ-ACK/SR/RI/CQI/PMI bits including CRC bits transmitted on PUCCH format 4/5 in subframe i;</li><li id="ul0085-0002" num="0212">NRE(i)=MPUCCH,c(i)·NscRB·NsymbPUCCH for PUCCH format 4 and NRE(i)=NscRB·NsymbPUCCH/2 for PUCCH format 5;</li><li id="ul0085-0003" num="0213">NsymbPUCCH=2·(NsymbUL−1)−1 if shortened PUCCH format 4 or shortened PUCCH format 5 is used in subframe i and nsymbPUCCH=2 (NsymbUL−1) otherwise.</li></ul></li></ul></li><li id="ul0083-0002" num="0214">PO_PUCCH is a parameter composed of the sum of a parameter PO_NOMINAL_PUCCH provided by higher layers and a parameter PO_UE_PUCCH provided by higher layers.</li><li id="ul0083-0003" num="0215">δPUCCH is a UE specific correction value, also referred to as a TPC command, included in a PDCCH with DCI format 1A/1B/1D/1/2A/2/2B/2C/2D for the primary cell, or included in a MPDCCH with DCI format 6-1A, or included in an EPDCCH with DCI format 1A/1B/1D/1/2A/2/2B/2C/2D for the primary cell, or sent jointly coded with other UE specific PUCCH correction values on a PDCCH/MPDCCH with DCI format 3/3A whose CRC parity bits are scrambled with TPC-PUCCH-RNTI. <ul id="ul0086" list-style="none"><li id="ul0086-0001" num="0216">For a non-BL/CE UE, if the UE is not configured for EPDCCH monitoring, the UE attempts to decode a PDCCH of DCI format 3/3A with the UE's TPC-PUCCH-RNTI and one or several PDCCHs of DCI format 1A/1B/1D/1/2A/2/2B/2C/2D with the UE's C-RNTI or SPS C-RNTI on every subframe except when in DRX.</li><li id="ul0086-0002" num="0217">If a UE is configured for EPDCCH monitoring, the UE attempts to decode <ul id="ul0087" list-style="none"><li id="ul0087-0001" num="0218">a PDCCH of DCI format 3/3A with the UE's TPC-PUCCH-RNTI and one or several PDCCHs of DCI format 1A/1B/1D/1/2A/2/2B/2C/2D with the UE's C-RNTI or SPS C-RNTI as described in subclause 9.1.1, and</li><li id="ul0087-0002" num="0219">one or several EPDCCHs of DCI format 1A/1B/1D/1/2A/2/2B/2C/2D with the UE's C-RNTI or SPS C-RNTI, as described in subclause 9.1.4.</li></ul></li><li id="ul0086-0003" num="0220">For a BL/CE UE configured with CEModeA, the UE attempts to decode a MPDCCH of DCI format 3/3A with the UE's TPC-PUCCH-RNTI and MPDCCH of DCI format 6-1A with the UE's C-RNTI or SPS C-RNTI on every BL/CE downlink subframe except when in DRX.</li><li id="ul0086-0004" num="0221">If the UE decodes <ul id="ul0088" list-style="none"><li id="ul0088-0001" num="0222">a PDCCH with DCI format 1A/1B/1D/1/2A/2/2B/2C/2D or</li><li id="ul0088-0002" num="0223">an EPDCCH with DCI format 1A/1B/1D/1/2A/2/2B/2C/2D or</li><li id="ul0088-0003" num="0224">an MPDCCH with DCI format 6-1A</li><li id="ul0088-0004" num="0225">for the primary cell and the corresponding detected RNTI equals the C-RNTI or SPS C-RNTI of the UE and the TPC field in the DCI format is not used to determine the PUCCH resource as in subclause 10.1, the UE shall use the δPUCCH provided in that PDCCH/EPDCCH/M PDCCH.</li></ul></li><li id="ul0086-0005" num="0226">Else <ul id="ul0089" list-style="none"><li id="ul0089-0001" num="0227">if the UE decodes a PDCCH/MPDCCH with DCI format 3/3A, the UE shall use the δPUCCH provided in that PDCCH/MPDCCH</li><li id="ul0089-0002" num="0228">else the UE shall set δPUCCH=0 dB.</li></ul></li></ul></li></ul></li></ul>

<maths id="MATH-US-00014" num="00014"><math overflow="scroll"><mrow><mrow><mi>g</mi><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo>=</mo><mrow><mrow><mi>g</mi><mo></mo><mrow><mo>(</mo><mrow><mi>i</mi><mo>-</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow><mo>+</mo><mrow><munderover><mo>∑</mo><mrow><mi>m</mi><mo>=</mo><mn>0</mn></mrow><mrow><mi>M</mi><mo>-</mo><mn>1</mn></mrow></munderover><mo></mo><mrow><msub><mi>δ</mi><mi>PUCCH</mi></msub><mo></mo><mrow><mo>(</mo><mrow><mi>i</mi><mo>-</mo><msub><mi>k</mi><mi>m</mi></msub></mrow><mo>)</mo></mrow></mrow></mrow></mrow></mrow></math></maths><ul id="ul0090" list-style="none"><li id="ul0090-0001" num="0000"><ul id="ul0091" list-style="none"><li id="ul0091-0001" num="0000"><ul id="ul0092" list-style="none"><li id="ul0092-0001" num="0000"> where g(i) is the current PUCCH power control adjustment state and where g(0) is the first value after reset. <ul id="ul0093" list-style="none"><li id="ul0093-0001" num="0229">For FDD or FDD-TDD and primary cell frame structure type 1, M=1 and k0=4.</li><li id="ul0093-0002" num="0230">For TDD, values of M and km are given in Table 10.1.3.1-1, where the “UL/DL configuration” in Table 10.1.3.1-1 corresponds to the eimta-HARQ-ReferenceConfig-r12 for the primary cell when the UE is configured with the parameter EIMTA-Main ConfigServCell-r12 for the primary cell.</li><li id="ul0093-0003" num="0231">The δPUCCH dB values signalled on PDCCH with DCI format 1A/1B/1D/1/2A/2/2B/2C/2D or EPDCCH with DCI format 1A/1B/1D/1/2A/2/2B/2C/2D or MPDCCH with DCI format 6-1A are given in Table 5.1.2.1-1. If the PDCCH with DCI format 1/1A/2/2A/2B/2C/2D or EPDCCH with DCI format 1/1A/2A/2/2B/2C/2D or MPDCCH with DCI format 6-1A is validated as an SPS activation PDCCH/EPDCCH/MPDCCH, or the PDCCH/EPDCCH with DCI format 1A or MPDCCH with DCI format 6-1A is validated as an SPS release PDCCH/EPDCCH/MPDCCH, then δPUCCH is 0 dB.</li><li id="ul0093-0004" num="0232">The δPUCCH dB values signalled on PDCCH/MPDCCH with DCI format 3/3A are given in Table 5.1.2.1-1 or in Table 5.1.2.1-2 as semi-statically configured by higher layers.</li><li id="ul0093-0005" num="0233">If PO_UE_PUCCH value is changed by higher layers, <ul id="ul0094" list-style="none"><li id="ul0094-0001" num="0234">g (0)=0</li></ul></li><li id="ul0093-0006" num="0235">Else <ul id="ul0095" list-style="none"><li id="ul0095-0001" num="0236">g (0)=ΔPrampup+δmsg2, where</li><li id="ul0095-0002" num="0000"> δmsg2 is the TPC command indicated in the random access response corresponding to the random access preamble transmitted in the primary cell, see subclause 6.2 and</li><li id="ul0095-0003" num="0000"> if UE is transmitting PUCCH in subframe</li></ul></li></ul></li></ul></li></ul></li></ul>

<maths id="MATH-US-00015" num="00015"><math overflow="scroll"><mrow><mrow><mi>Δ</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><msub><mi>P</mi><mi>rampup</mi></msub></mrow><mo>=</mo><mrow><mrow><mi>min</mi><mo></mo><mrow><mo>[</mo><mrow><mrow><mo>{</mo><mrow><mi>max</mi><mo></mo><mrow><mo>(</mo><mrow><mi>O</mi><mo>,</mo><mrow><msub><mi>P</mi><mrow><mi>CMAX</mi><mo>,</mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><mi>c</mi></mrow></msub><mo>-</mo><mrow><mo>(</mo><mtable><mtr><mtd><msub><mi>P</mi><mrow><mn>0</mn><mo>,</mo><mi>PUCCH</mi></mrow></msub></mtd></mtr><mtr><mtd><mrow><mrow><mo>+</mo><msub><mi>PL</mi><mi>c</mi></msub></mrow><mo>+</mo><mrow><mi>h</mi><mo>(</mo><mrow><msub><mi>n</mi><mi>CQI</mi></msub><mo>,</mo><msub><mi>n</mi><mi>HARQ</mi></msub><mo>,</mo><msub><mi>n</mi><mi>SR</mi></msub></mrow></mrow></mrow></mtd></mtr><mtr><mtd><mrow><mrow><mo>+</mo><mrow><msub><mi>Δ</mi><mi>F_PUCCH</mi></msub><mo></mo><mrow><mo>(</mo><mi>F</mi><mo>)</mo></mrow></mrow></mrow><mo>+</mo><mrow><msub><mi>Δ</mi><mrow><mi>T</mi><mo>×</mo><mi>D</mi></mrow></msub><mo></mo><mrow><mo>(</mo><msup><mi>F</mi><mi>′</mi></msup><mo>)</mo></mrow></mrow></mrow></mtd></mtr></mtable><mo>)</mo></mrow></mrow></mrow><mo>)</mo></mrow></mrow><mo>}</mo></mrow><mo>,</mo><mrow><mi>Δ</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><msub><mi>P</mi><mi>rampuprequested</mi></msub></mrow></mrow><mo>]</mo></mrow></mrow><mo>.</mo></mrow></mrow></math></maths><ul id="ul0096" list-style="none"><li id="ul0096-0001" num="0000"><ul id="ul0097" list-style="none"><li id="ul0097-0001" num="0000"><ul id="ul0098" list-style="none"><li id="ul0098-0001" num="0000"><ul id="ul0099" list-style="none"><li id="ul0099-0001" num="0000"><ul id="ul0100" list-style="none"><li id="ul0100-0001" num="0000"> Otherwise,</li><li id="ul0100-0002" num="0000"> ΔPrampup=min[{max(0,PCMAX,c−(P0_PUCCH+PLc))},ΔPrampuprequested] and</li><li id="ul0100-0003" num="0000"> ΔPrampuprequested is provided by higher layers and corresponds to the total power ramp-up requested by higher layers from the first to the last preamble in the primary cell.</li></ul></li><li id="ul0099-0002" num="0237">If UE has reached PCMAX,c(i) for the primary cell, positive TPC commands for the primary cell shall not be accumulated.</li><li id="ul0099-0003" num="0238">If UE has reached minimum power, negative TPC commands shall not be accumulated.</li><li id="ul0099-0004" num="0239">UE shall reset accumulation <ul id="ul0101" list-style="none"><li id="ul0101-0001" num="0240">when PO_UE_PUCCH value is changed by higher layers</li><li id="ul0101-0002" num="0241">when the UE receives a random access response message for the primary cell</li><li id="ul0101-0003" num="0242">g(i)=g(i−1) if i is not an uplink subframe in TDD or FDD-TDD and primary cell frame structure type 2.</li></ul></li></ul></li></ul></li></ul></li></ul>

For a BL/CE UE configured with CEModeA, if the PUCCH is transmitted in more than one subframe i0, i1, . . . , iN-1 where i0<i1< . . . <iN-1, the PUCCH transmit power in subframe ik, k=0, 1, . . . , N−1 is determined by

PPUCCH,c(ik)=PPUCCH,c(i0)

For a BL/CE UE configured with CEModeB, the PUCCH transmit power in subframe ik is determined by

PPUCCH,c(ik)=PCMAX,c(i0)

Table 5.1.2.1-1 of 3GPP TS 36.213 v13.2.0, Entitled “Mapping of TPC Command Field in DCI Format 1A/1B/1D/1/2A/2B/2C/2D/2/3 to δ

PUCCH

Values”, is Reproduced as FIG.

Table 5.1.2.1-2 of 3GPP TS 36.213 v13.2.0, Entitled “Mapping of TPC Command Field in DCI Format 3A to δ

PUCCH

Values”, is Reproduced as FIG.

5.1.3 Sounding Reference Symbol (SRS)

5.1.3.1 UE Behaviour

The setting of the UE Transmit power PSRS for the SRS transmitted on subframe i for serving cell c is defined by

PSRS,c(i)=min{PCMAX,c(i),PSRS_OFFSET,c(m)+10 log10(MSRS,c)+PO_PUSCH,c(j)+αc(j)·PLc+fc(i)} [dBm]

where <ul id="ul0102" list-style="none"><li id="ul0102-0001" num="0000"><ul id="ul0103" list-style="none"><li id="ul0103-0001" num="0246">PCMAX,c(i) is the configured UE transmit power defined in [6] in subframe i for serving cell c.</li><li id="ul0103-0002" num="0247">PSRS_OFFSET,c(m) is semi-statically configured by higher layers for m=0 and m=1 for serving cell c. For SRS transmission given trigger type 0 then m=0 and for SRS transmission given trigger type 1 then m=1.</li><li id="ul0103-0003" num="0248">MSRS,c is the bandwidth of the SRS transmission in subframe i for serving cell c expressed in number of resource blocks.</li><li id="ul0103-0004" num="0249">fc(i) is the current PUSCH power control adjustment state for serving cell c, see subclause 5.1.1.1.</li><li id="ul0103-0005" num="0250">PO_PUSCH,c(j) and αc(j) are parameters as defined in subclause 5.1.1.1 for subframe where j=1.</li></ul></li></ul>

If the UE is not configured with an SCG or a PUCCH-SCell, and if the total transmit power of the UE for the Sounding Reference Symbol in an SC-FDMA symbol would exceed {circumflex over (P)}CMAX(i), the UE scales {circumflex over (P)}SRS,c(i) for the serving cell c and the SC-FDMA symbol in subframe i such that the condition

is satisfied where {circumflex over (P)}SRS,c(i) is the linear value of PSRS,c, PCMAX(i) is the linear value of PCMAX defined in [6] in subframe i and w(i) is a scaling factor of {circumflex over (P)}SRS,c(i) for serving cell c where 0<w(i)≤1. Note that w(i) values are the same across serving cells.

If the UE is not configured with an SCG or a PUCCH-SCell, and if the UE is configured with multiple TAGs and the SRS transmission of the UE in an SC-FDMA symbol for a serving cell in subframe i in a TAG overlaps with the SRS transmission in another SC-FDMA symbol in subframe i for a serving cell in another TAG, and if the total transmit power of the UE for the Sounding Reference Symbol in the overlapped portion would exceed {circumflex over (P)}CMAX (i), the UE scales {circumflex over (P)}SRS,c for the serving cell c and each of the overlapped SRS SC-FDMA symbols in subframe i such that the condition

is satisfied where {circumflex over (P)}SRS,c(i) is the linear value of {circumflex over (P)}SRS,c (i), {circumflex over (P)}CMAX(i) is the linear value of PCMAX defined in [6] in subframe i and w(i) is a scaling factor of {circumflex over (P)}SRS,c(i) for serving cell c where 0<w(i)≤1. Note that w(i) values are the same across serving cells.

If the UE is configured with higher layer parameter UplinkPowerControlDedicated-v12x0 for serving cell c and if subframe i belongs to uplink power control subframe set 2 as indicated by the higher layer parameter tpc-SubframeSet-r12, the UE shall use fc,2(i) instead of fc(i) to determine PSRS,c(i) for subframe i and serving cell c, where fc,2(i) is defined in subclause 5.1.1.1.

Channel state information (CSI) may comprise channel quality indicator (CQI), PMI (precoding matrix indicator), RI (rank indicator). The CSI measurement is measured from CRS or CSI-RS. As can be seen from the below quotations, CQI is an indicator of affordable modulation and coding scheme under certain assumptions, e.g., error rate target, channel condition, which is a kind of implicit feedback for the channel, which can be determined by, e.g., signal to interference and noise ratio (SINR) of certain signal.

Alternatively, CQI can also be used to indicate real channel coefficient, with possible quantization. PMI is an indicator of preferred precoding matrix in the antenna domain, which can be used to enlarge the signal quality (beamforming gain), or reduce the interference between multiple streams (layers) from different antennas to a given UE. RI is an indicator of the preferred or affordable number of streams (layers) to the UE. More detail information can be found in Section 7.2 of 3GPP TS 36.213 as follows:

7.2 UE Procedure for Reporting Channel State Information (CSI)

If the UE is configured with a PUCCH-SCell, the UE shall apply the procedures described in this clause for both primary PUCCH group and secondary PUCCH group unless stated otherwise <ul id="ul0104" list-style="none"><li id="ul0104-0001" num="0000"><ul id="ul0105" list-style="none"><li id="ul0105-0001" num="0257">When the procedures are applied for the primary PUCCH group, the terms ‘secondary cell’, ‘secondary cells’, ‘serving cell’, and ‘serving cells’ in this clause refer to secondary cell, secondary cells, serving cell or serving cells belonging to the primary PUCCH group respectively unless stated otherwise.</li><li id="ul0105-0002" num="0258">When the procedures are applied for secondary PUCCH group, the terms ‘secondary cell’, ‘secondary cells’, ‘serving cell’ and ‘serving cells’ in this clause refer to secondary cell, secondary cells (not including the PUCCH-SCell), serving cell, serving cells belonging to the secondary PUCCH group respectively unless stated otherwise. The term ‘primary cell’ in this clause refers to the PUCCH-SCell of the secondary PUCCH group.</li></ul></li></ul>

The time and frequency resources that can be used by the UE to report CSI which consists of Channel Quality Indicator (CQI), precoding matrix indicator (PMI), precoding type indicator (PTI), CSI-RS resource indicator (CRI), and/or rank indication (RI) are controlled by the eNB. For spatial multiplexing, as given in [3], the UE shall determine a RI corresponding to the number of useful transmission layers. For transmit diversity as given in [3], RI is equal to one. A non-BL/CE UE in transmission mode 8 or 9 is configured with or without PMI/RI reporting by the higher layer parameter pmi-RI-Report.

A UE in transmission mode 10 can be configured with one or more CSI processes per serving cell by higher layers.

For a UE in transmission mode 10, <ul id="ul0106" list-style="none"><li id="ul0106-0001" num="0000"><ul id="ul0107" list-style="none"><li id="ul0107-0001" num="0262">If a UE is not configured with higher layer parameter eMIMO-Type, each CSI process is associated with a CSI-RS resource (defined in subclause 7.2.5) and a CSI-interference measurement (CSI-IM) resource (defined in subclause 7.2.6). A UE can be configured with up to two CSI-IM resources for a CSI process if the UE is configured with CSI subframe sets CCSI,0 and CCSI,1 by the higher layer parameter csi-SubFramePatternConfig-r12 for the CSI process.</li><li id="ul0107-0002" num="0263">If the UE is configured with higher layer parameter eMIMO-Type, and eMIMO-Type is set to ‘CLASS A’, each CSI process is associated with a CSI-RS resource (defined in subclause 7.2.5) and a CSI-interference measurement (CSI-IM) resource (defined in subclause 7.2.6). A UE can be configured with up to two CSI-IM resources for a CSI process if the UE is configured with CSI subframe sets CCSI,0 and CCSI,1 by the higher layer parameter csi-SubFramePatternConfig-r12 for the CSI process.</li><li id="ul0107-0003" num="0264">If the UE is configured with higher layer parameter eMIMO-Type, and eMIMO-Type is set to ‘CLASS B’, each CSI process is associated with one or more CSI-RS resource (defined in subclause 7.2.5) and one or more CSI-interference measurement (CSI-IM) resource (defined in subclause 7.2.6). Each CSI-RS resource is associated with a CSI-IM resource by higher layers. For a CSI process with one CSI-RS resource, a UE can be configured with CSI-IM resource for each CSI subframe sets if the UE is configured with CSI subframe sets CCSI,0 and CCSI,1 by the higher layer parameter csi-SubFramePatternConfig-r12 for the CSI process.</li></ul></li></ul>

For a UE in transmission mode 10, a CSI reported by the UE corresponds to a CSI process configured by higher layers. Each CSI process can be configured with or without PMI/RI reporting by higher layer signalling.

For UE in transmission mode 9 and the UE configured with higher layer parameter eMIMO-Type, the term ‘CSI process’ in this subclause refers to the CSI configured for the UE. For a UE in transmission mode 9, and if the UE is configured with higher layer parameter eMIMO-Type, and, <ul id="ul0108" list-style="none"><li id="ul0108-0001" num="0000"><ul id="ul0109" list-style="none"><li id="ul0109-0001" num="0267">eMIMO-Type is set to ‘CLASS A’, each CSI process is associated with a CSI-RS resource (defined in subclause 7.2.5).</li><li id="ul0109-0002" num="0268">eMIMO-Type is set to ‘CLASS B’, each CSI process is associated with one or more CSI-RS resource (defined in subclause 7.2.5).</li></ul></li></ul>

For a CSI process, and if a UE is configured in transmission mode 9 or 10, and UE is not configured with higher layer parameter pmi-RI-Report, and UE is configured with higher layer parameter eMIMO-Type, and eMIMO-Type is set to ‘CLASS B’, and the number of CSI-RS antenna ports in at least one of the one or more configured CSI-RS resource is more than one, the UE is considered to be configured without PMI reporting.

A UE is configured with resource-restricted CSI measurements if the subframe sets CCSI,0 and CCSI,1 are configured by higher layers.

For a serving cell with frame structure type 1, a UE is not expected to be configured with csi-SubframePatternConfig-r12.

CSI reporting is periodic or aperiodic.

A BL/CE UE configured with CEModeB is not expected to be configured with either aperiodic CSI or periodic CSI reporting.

If the UE is configured with more than one serving cell, it transmits CSI for activated serving cell(s) only.

If a UE is not configured for simultaneous PUSCH and PUCCH transmission, it shall transmit periodic CSI reporting on PUCCH as defined hereafter in subframes with no PUSCH allocation.

If a UE is not configured for simultaneous PUSCH and PUCCH transmission, it shall transmit periodic CSI reporting on PUSCH of the serving cell with smallest ServCellIndex as defined hereafter in subframes with a PUSCH allocation, where the UE shall use the same PUCCH-based periodic CSI reporting format on PUSCH.

A UE shall transmit aperiodic CSI reporting on PUSCH if the conditions specified hereafter are met. For aperiodic CQI/PMI reporting, RI reporting is transmitted only if the configured CSI feedback type supports RI reporting.

Table 7.2-1: Void

In case both periodic and aperiodic CSI reporting would occur in the same subframe, the UE shall only transmit the aperiodic CSI report in that subframe.

If the higher layer parameter altCQI-Table-r12 is configured and is set to allSubframes-r12, <ul id="ul0110" list-style="none"><li id="ul0110-0001" num="0000"><ul id="ul0111" list-style="none"><li id="ul0111-0001" num="0280">the UE shall report CQI according to Table 7.2.3-2.</li></ul></li></ul>

Else if the higher layer parameter altCQI-Table-r12 is configured and is set to csi-SubframeSet1-r12 or csi-SubframeSet2-r12, <ul id="ul0112" list-style="none"><li id="ul0112-0001" num="0000"><ul id="ul0113" list-style="none"><li id="ul0113-0001" num="0282">the UE shall report CQI according to Table 7.2.3-2 for the corresponding CSI subframe set configured by altCQI-Table-r12</li><li id="ul0113-0002" num="0283">the UE shall report CQI for the other CSI subframe set according to Table 7.2.3-1.</li></ul></li></ul>

Else <ul id="ul0114" list-style="none"><li id="ul0114-0001" num="0000"><ul id="ul0115" list-style="none"><li id="ul0115-0001" num="0285">the UE shall report CQI according to Table 7.2.3-1. [ . . . ] </li></ul></li></ul>

7.2.3 Channel Quality Indicator (CQI) Definition

The CQI indices and their interpretations are given in Table 7.2.3-1 for reporting CQI based on QPSK, 16QAM and 64QAM. The CQI indices and their interpretations are given in Table 7.2.3-2 for reporting CQI based on QPSK, 16QAM, 64QAM and 256QAM. The CQI indices and their interpretations are given in Table 7.2.3-3 for reporting CQI based on QPSK and 16QAM.

For a non-BL/CE UE, based on an unrestricted observation interval in time unless specified otherwise in this subclause, and an unrestricted observation interval in frequency, the UE shall derive for each CQI value reported in uplink subframe n the highest CQI index between 1 and 15 in Table 7.2.3-1 or Table 7.2.3-2 which satisfies the following condition, or CQI index 0 if CQI index 1 does not satisfy the condition: <ul id="ul0116" list-style="none"><li id="ul0116-0001" num="0000"><ul id="ul0117" list-style="none"><li id="ul0117-0001" num="0288">A single PDSCH transport block with a combination of modulation scheme and transport block size corresponding to the CQI index, and occupying a group of downlink physical resource blocks termed the CSI reference resource, could be received with a transport block error probability not exceeding 0.1.</li></ul></li></ul>

For a BL/CE UE, based on an unrestricted observation interval in time and frequency, the UE shall derive for each CQI value the highest CQI index between 1 and 10 in Table 7.2.3-3 which satisfies the following condition, or CQI index 0 if CQI index 1 does not satisfy the condition: <ul id="ul0118" list-style="none"><li id="ul0118-0001" num="0000"><ul id="ul0119" list-style="none"><li id="ul0119-0001" num="0290">A single PDSCH transport block with a combination of modulation scheme and transport block size corresponding to the CQI index, and occupying a group of downlink physical resource blocks termed the CSI reference resource, could be received with a transport block error probability not exceeding 0.1.</li></ul></li></ul>

If CSI subframe sets CCSI,0 and CCSI,1 are configured by higher layers, each CSI reference resource belongs to either CCSI,0 or CCSI,1 but not to both. When CSI subframe sets CCSI,0 and CCSI,1 are configured by higher layers a UE is not expected to receive a trigger for which the CSI reference resource is in subframe that does not belong to either subframe set. For a UE in transmission mode 10 and periodic CSI reporting, the CSI subframe set for the CSI reference resource is configured by higher layers for each CSI process.

For a UE in transmission mode 9 when parameter pmi-RI-Report is configured by higher layers and parameter eMIMO-Type is not configured by higher layers, the UE shall derive the channel measurements for computing the CQI value reported in uplink subframe n based on only the Channel-State Information (CSI) reference signals (CSI-RS) defined in [3] for which the UE is configured to assume non-zero power for the CSI-RS. For a non-BL/CE UE in transmission mode 9 when the parameter pmi-RI-Report is not configured by higher layers or in transmission modes 1-8 the UE shall derive the channel measurements for computing CQI based on CRS. For a BL/CE UE the UE shall derive the channel measurements for computing CQI based on CRS. For a UE in transmission mode 10, when parameter eMIMO-Type is not configured by higher layers, the UE shall derive the channel measurements for computing the CQI value reported in uplink subframe n and corresponding to a CSI process, based on only the non-zero power CSI-RS (defined in [3]) within a configured CSI-RS resource associated with the CSI process. For a UE in transmission mode 9 and the UE configured with parameter eMIMO-Type by higher layers, the term ‘CSI process’ in this clause refers to the CSI configured for the UE. For a UE in transmission mode 9 or 10 and for a CSI process, if the UE is configured with parameter eMIMO-Type by higher layers, and eMIMO-Type is set to ‘CLASS A’, and one CSI-RS resource configured, or the UE is configured with parameter eMIMO-Type by higher layers, and eMIMO-Type is set to ‘CLASS B’, and parameter channelMeasRestriction is not configured by higher layers, the UE shall derive the channel measurements for computing the CQI value reported in uplink subframe n and corresponding to the CSI process, based on only the non-zero power CSI-RS (defined in [3]) within a configured CSI-RS resource associated with the CSI process. If the UE is configured with parameter eMIMO-Type by higher layers, and eMIMO-Type is set to ‘CLASS B’ and the number of configured CSI-RS resources is K>1, and parameter channelMeasRestriction is not configured by higher layers, the UE shall derive the channel measurements for computing the CQI value using only the configured CSI-RS resource indicated by the CRI.

For a UE in transmission mode 9 or 10 and for a CSI process, if the UE is configured with parameter eMIMO-Type by higher layers, and eMIMO-Type is set to ‘CLASS B’, and parameter channelMeasRestriction is configured by higher layers, the UE shall derive the channel measurements for computing the CQI value reported in uplink subframe n and corresponding to the CSI process, based on only the most recent, no later than the CSI reference resource, non-zero power CSI-RS (defined in [3]) within a configured CSI-RS resource associated with the CSI process. If the UE is configured with parameter eMIMO-Type by higher layers, and eMIMO-Type is set to ‘CLASS B’ and the number of configured CSI-RS resources is K>1, and parameter channelMeasRestriction is configured by higher layers, the UE shall derive the channel measurements for computing the CQI value using only the most recent, no later than the CSI reference resource, non-zero power CSI-RS within the configured CSI-RS resource indicated by the CRI.

For a UE in transmission mode 10, when parameter eMIMO-Type is not configured by higher layers, the UE shall derive the interference measurements for computing the CQI value reported in uplink subframe n and corresponding to a CSI process, based on only the configured CSI-IM resource associated with the CSI process.

For a UE in transmission mode 10 and for a CSI process, when parameters eMIMO-Type and interferenceMeasRestriction is configured by higher layers, the UE shall derive the interference measurements for computing the CQI value reported in uplink subframe n and corresponding to the CSI process, based on only the most recent, no later than the CSI reference resource, configured CSI-IM resource associated with the CSI process. If the UE is configured with parameter eMIMO-Type by higher layers, and eMIMO-Type is set to ‘CLASS B’ and the number of configured CSI-RS resources is K>1, and interferenceMeasRestriction is configured, the UE shall derive interference measurement for computing the CQI value based on only the most recent, no later than the CSI reference resource, the configured CSI-IM resource associated with the CSI-RS resource indicated by the CRI. If interferenceMeasRestriction is not configured, the UE shall derive the interference measurement for computing the CQI value based on the CSI-IM associated with the CSI-RS resource indicated by the CRI.

If the UE in transmission mode 10 is configured by higher layers for CSI subframe sets CCSI,0 and CCSI,1 for the CSI process, the configured CSI-IM resource within the subframe subset belonging to the CSI reference resource is used to derive the interference measurement.

For a UE configured with the parameter EIMTA-MainConfigServCell-r12 for a serving cell, configured CSI-IM resource(s) within only downlink subframe(s) of a radio frame that are indicated by UL/DL configuration of the serving cell can be used to derive the interference measurement for the serving cell.

For a LAA Scell, <ul id="ul0120" list-style="none"><li id="ul0120-0001" num="0000"><ul id="ul0121" list-style="none"><li id="ul0121-0001" num="0299">for channel measurements, if the UE averages CRS/CSI-RS measurements from multiple subframes <ul id="ul0122" list-style="none"><li id="ul0122-0001" num="0300">the UE should not average CSI-RS measurement in subframe n1 with CSI-RS measurement in a later subframe n2, if any OFDM symbol of subframe n1 or any subframe from subframe n1+1 to subframe n2, is not occupied.</li><li id="ul0122-0002" num="0301">the UE should not average CRS measurement in subframe n1 with CRS measurement in a later subframe n2, if any OFDM symbol of the second slot of subframe n1 or any OFDM symbol of any subframe from subframe n1+1 to subframe n2-1, or any of the first 3 OFDM symbols in subframe n2, is not occupied.</li></ul></li><li id="ul0121-0002" num="0302">for interference measurements, the UE shall derive the interference measurements for computing the CQI value based on only measurements in subframes with occupied OFDM symbols.</li></ul></li></ul>

A combination of modulation scheme and transport block size corresponds to a CQI index if: <ul id="ul0123" list-style="none"><li id="ul0123-0001" num="0000"><ul id="ul0124" list-style="none"><li id="ul0124-0001" num="0304">the combination could be signalled for transmission on the PDSCH in the CSI reference resource according to the relevant Transport Block Size table, and</li><li id="ul0124-0002" num="0305">the modulation scheme is indicated by the CQI index, and</li><li id="ul0124-0003" num="0306">the combination of transport block size and modulation scheme when applied to the reference resource results in the effective channel code rate which is the closest possible to the code rate indicated by the CQI index. If more than one combination of transport block size and modulation scheme results in an effective channel code rate equally close to the code rate indicated by the CQI index, only the combination with the smallest of such transport block sizes is relevant.</li></ul></li></ul>

The CSI reference resource for a serving cell is defined as follows: <ul id="ul0125" list-style="none"><li id="ul0125-0001" num="0000"><ul id="ul0126" list-style="none"><li id="ul0126-0001" num="0308">For a non-BL/CE UE, in the frequency domain, the CSI reference resource is defined by the group of downlink physical resource blocks corresponding to the band to which the derived CQI value relates. For a BL/CE UE, in the frequency domain, the CSI reference resource includes all downlink physical resource blocks for any of the narrowband to which the derived CQI value relates.</li><li id="ul0126-0002" num="0309">In the time domain and for a non-BL/CE UE, <ul id="ul0127" list-style="none"><li id="ul0127-0001" num="0310">for a UE configured in transmission mode 1-9 or transmission mode 10 with a single configured CSI process for the serving cell, the CSI reference resource is defined by a single downlink or special subframe n-nCQI_ref. <ul id="ul0128" list-style="none"><li id="ul0128-0001" num="0311">where for periodic CSI reporting nCQI_ref is the smallest value greater than or equal to 4, such that it corresponds to a valid downlink or valid special subframe,</li><li id="ul0128-0002" num="0312">where for aperiodic CSI reporting, if the UE is not configured with the higher layer parameter csi-SubframePatternConfig-r12. <ul id="ul0129" list-style="none"><li id="ul0129-0001" num="0313">nCQI_ref is such that the reference resource is in the same valid downlink or valid special subframe as the corresponding CSI request in an uplink DCI format.</li><li id="ul0129-0002" num="0314">nCQI_ref is equal to 4 and subframe n-nCQI_ref corresponds to a valid downlink or valid special subframe, where subframe n-nCQI_ref is received after the subframe with the corresponding CSI request in a Random Access Response Grant.</li></ul></li><li id="ul0128-0003" num="0315">where for aperiodic CSI reporting, and the UE configured with the higher layer parameter csi-SubframePatternConfig-r12, <ul id="ul0130" list-style="none"><li id="ul0130-0001" num="0316">for the UE configured in transmission mode 1-9,</li><li id="ul0130-0002" num="0000"> nCQI_ref is the smallest value greater than or equal to 4 and subframe n-nCQI_ref corresponds to a valid downlink or valid special subframe, where subframe n-nCQI_ref is received on or after the subframe with the corresponding CSI request in an uplink DCI format;</li><li id="ul0130-0003" num="0000"> nCQI_ref is the smallest value greater than or equal to 4, and subframe n-nCQI_ref corresponds to a valid downlink or valid special subframe, where subframe n-nCQI_ref is received after the subframe with the corresponding CSI request in an Random Access Response Grant;</li><li id="ul0130-0004" num="0000"> if there is no valid value for nCQI_ref based on the above conditions, then nCQI_ref is the smallest value such that the reference resource is in a valid downlink or valid special subframe n-nCQI_ref prior to the subframe with the corresponding CSI request, where subframe n-nCQI_ref is the lowest indexed valid downlink or valid special subframe within a radio frame;</li><li id="ul0130-0005" num="0317">for the UE configured in transmission mode 10,</li><li id="ul0130-0006" num="0000"> nCQI_ref is the smallest value greater than or equal to 4, such that it corresponds to a valid downlink or valid special subframe, and the corresponding CSI request is in an uplink DCI format;</li><li id="ul0130-0007" num="0000"> nCQI_ref is the smallest value greater than or equal to 4, and subframe n-nCQI_ref corresponds to a valid downlink or valid special subframe, where subframe n-nCQI_ref is received after the subframe with the corresponding CSI request in a Random Access Response Grant;</li></ul></li></ul></li><li id="ul0127-0002" num="0318">for a UE configured in transmission mode 10 with multiple configured CSI processes for the serving cell, the CSI reference resource for a given CSI process is defined by a single downlink or special subframe n-nCQI_ref. <ul id="ul0131" list-style="none"><li id="ul0131-0001" num="0319">where for FDD serving cell and periodic or aperiodic CSI reporting nCQI_ref is the smallest value greater than or equal to 5, such that it corresponds to a valid downlink or valid special subframe, and for aperiodic CSI reporting the corresponding CSI request is in an uplink DCI format;</li><li id="ul0131-0002" num="0320">where for FDD serving cell and aperiodic CSI reporting nCQI_ref is equal to 5 and subframe n-nCQI_ref corresponds to a valid downlink or valid special subframe, where subframe n-nCQI_ref is received after the subframe with the corresponding CSI request in a Random Access Response Grant.</li><li id="ul0131-0003" num="0321">where for TDD serving cell, and 2 or 3 configured CSI processes, and periodic or aperiodic CSI reporting, nCQI_ref is the smallest value greater than or equal to 4, such that it corresponds to a valid downlink or valid special subframe, and for aperiodic CSI reporting the corresponding CSI request is in an uplink DCI format;</li><li id="ul0131-0004" num="0322">where for TDD serving cell, and 2 or 3 configured CSI processes, and aperiodic CSI reporting, nCQI_ref is equal to 4 and subframe n-nCQI_ref corresponds to a valid downlink or valid special subframe, where subframe n-nCQI_ref is received after the subframe with the corresponding CSI request in a Random Access Response Grant;</li><li id="ul0131-0005" num="0323">where for TDD serving cell, and 4 configured CSI processes, and periodic or aperiodic CSI reporting, nCQI_ref is the smallest value greater than or equal to 5, such that it corresponds to a valid downlink or valid special subframe, and for aperiodic CSI reporting the corresponding CSI request is in an uplink DCI format;</li><li id="ul0131-0006" num="0324">where for TDD serving cell, and 4 configured CSI processes, and aperiodic CSI reporting, nCQI_ref is equal to 5 and subframe n-nCQI_ref corresponds to a valid downlink or valid special subframe, where subframe n-nCQI_ref is received after the subframe with the corresponding CSI request in a Random Access Response Grant.</li></ul></li></ul></li><li id="ul0126-0003" num="0325">In the time domain and for a BL/CE UE, the CSI reference resource is defined by a set of BL/CE downlink or special subframes where the last subframe is subframe n-nCQI_ref, <ul id="ul0132" list-style="none"><li id="ul0132-0001" num="0326">where for periodic CSI reporting nCQI_ref is 4;</li><li id="ul0132-0002" num="0327">where for aperiodic CSI reporting nCQI_ref is 4;</li><li id="ul0132-0003" num="0328">where each subframe in the CSI reference resource is a valid downlink or valid special subframe;</li><li id="ul0132-0004" num="0329">where for wideband CSI reports: <ul id="ul0133" list-style="none"><li id="ul0133-0001" num="0330">The set of BL/CE downlink or special subframes is the set of the last ceil(RCSI/NNB,hopch,DL) subframes before n-nCQI_ref used for MPDCCH monitoring by the BL/CE UE in each of the narrowbands where the BL/CE UE monitors MPDCCH, where NNB,hopch,DL is the number of narrowbands where the BL/CE UE monitors MPDCCH.</li></ul></li><li id="ul0132-0005" num="0331">where for subband CSI reports: <ul id="ul0134" list-style="none"><li id="ul0134-0001" num="0332">The set of BL/CE downlink or special subframes is the set of the last RCSI subframes used for MPDCCH monitoring by the BL/CE UE in the corresponding narrowband before n-nCQI_ref;</li></ul></li><li id="ul0132-0006" num="0333">where RCSI is given by the higher layer parameter csi-NumRepetitionCE.</li></ul></li><li id="ul0126-0004" num="0334">A subframe in a serving cell shall be considered to be a valid downlink or a valid special subframe if: <ul id="ul0135" list-style="none"><li id="ul0135-0001" num="0335">it is configured as a downlink subframe or a special subframe for that UE, and</li><li id="ul0135-0002" num="0336">in case multiple cells with different uplink-downlink configurations are aggregated and the UE is not capable of simultaneous reception and transmission in the aggregated cells, the subframe in the primary cell is a downlink subframe or a special subframe with the length of DwPTS more than 7680·Ts, and</li><li id="ul0135-0003" num="0337">except for a non-BL/CE UE in transmission mode 9 or 10, it is not an MBSFN subframe, and</li><li id="ul0135-0004" num="0338">it does not contain a DwPTS field in case the length of DwPTS is 7680·Ts and less, and</li><li id="ul0135-0005" num="0339">it does not fall within a configured measurement gap for that UE, and</li><li id="ul0135-0006" num="0340">for periodic CSI reporting, it is an element of the CSI subframe set linked to the periodic CSI report when that UE is configured with CSI subframe sets, and</li><li id="ul0135-0007" num="0341">for a UE configured in transmission mode 10 with multiple configured CSI processes, and aperiodic CSI reporting for a CSI process, it is an element of the CSI subframe set linked to the downlink or special subframe with the corresponding CSI request in an uplink DCI format, when that UE is configured with CSI subframe sets for the CSI process and UE is not configured with the higher layer parameter csi-SubframePatternConfig-r12, and</li><li id="ul0135-0008" num="0342">for a UE configured in transmission mode 1-9, and aperiodic CSI reporting, it is an element of the CSI subframe set associated with the corresponding CSI request in an uplink DCI format, when that UE is configured with CSI subframe sets by the higher layer parameter csi-SubframePatternConfig-r12, and</li><li id="ul0135-0009" num="0343">for a UE configured in transmission mode 10, and aperiodic CSI reporting for a CSI process, it is an element of the CSI subframe set associated with the corresponding CSI request in an uplink DCI format, when that UE is configured with CSI subframe sets by the higher layer parameter csi-SubframePatternConfig-r12 for the CSI process.</li><li id="ul0135-0010" num="0344">except if the serving cell is a LAA Scell, and at least one OFDM symbol in the subframe is not occupied.</li><li id="ul0135-0011" num="0345">except if the serving cell is a LAA Scell, and n′s≠ns as described in sub clause 6.10.1.1 in [3].</li><li id="ul0135-0012" num="0346">except if the serving cell is a LAA Scell, and for a UE configured in transmission mode 9 or 10, the configured CSI-RS resource associated with the CSI process is not in the subframe.</li></ul></li><li id="ul0126-0005" num="0347">For a non-BL/CE UE, if there is no valid downlink or no valid special subframe for the CSI reference resource in a serving cell, CSI reporting is omitted for the serving cell in uplink subframe n.</li><li id="ul0126-0006" num="0348">In the layer domain, the CSI reference resource is defined by any RI and PMI on which the CQI is conditioned.</li></ul></li></ul>

In the CSI reference resource, the UE shall assume the following for the purpose of deriving the CQI index, and if also configured, PMI and RI: <ul id="ul0136" list-style="none"><li id="ul0136-0001" num="0000"><ul id="ul0137" list-style="none"><li id="ul0137-0001" num="0350">The first 3 OFDM symbols are occupied by control signalling</li><li id="ul0137-0002" num="0351">No resource elements used by primary or secondary synchronization signals or PBCH or EPDCCH</li><li id="ul0137-0003" num="0352">CP length of the non-MBSFN subframes</li><li id="ul0137-0004" num="0353">Redundancy Version 0</li><li id="ul0137-0005" num="0354">If CSI-RS is used for channel measurements, the ratio of PDSCH EPRE to CSI-RS EPRE is as given in subclause 7.2.5</li><li id="ul0137-0006" num="0355">For transmission mode 9 CSI reporting of a non-BL/CE UE: <ul id="ul0138" list-style="none"><li id="ul0138-0001" num="0356">CRS REs are as in non-MBSFN subframes;</li><li id="ul0138-0002" num="0357">If the UE is configured for PMI/RI reporting or without PMI reporting, the UE-specific reference signal overhead is consistent with the most recent reported rank if more than one CSI-RS port is configured, and is consistent with rank 1 transmission if only one CSI-RS port is configured; and PDSCH signals on antenna ports {7 . . . 6+υ} for υ layers would result in signals equivalent to corresponding symbols transmitted on antenna ports {15 . . . 14+P}, as given by</li></ul></li></ul></li></ul>

<maths id="MATH-US-00018" num="00018"><math overflow="scroll"><mrow><mrow><mrow><mo>[</mo><mtable><mtr><mtd><mrow><msup><mi>y</mi><mrow><mo>(</mo><mn>15</mn><mo>)</mo></mrow></msup><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow></mtd></mtr><mtr><mtd><mi>⋮</mi></mtd></mtr><mtr><mtd><mrow><msup><mi>y</mi><mrow><mo>(</mo><mrow><mn>14</mn><mo>+</mo><mi>P</mi></mrow><mo>)</mo></mrow></msup><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow></mtd></mtr></mtable><mo>]</mo></mrow><mo>=</mo><mrow><mrow><mi>W</mi><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo></mo><mrow><mo>[</mo><mtable><mtr><mtd><mrow><msup><mi>x</mi><mrow><mo>(</mo><mn>0</mn><mo>)</mo></mrow></msup><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow></mtd></mtr><mtr><mtd><mi>⋮</mi></mtd></mtr><mtr><mtd><mrow><msup><mi>y</mi><mrow><mo>(</mo><mrow><mi>v</mi><mo>-</mo><mn>1</mn></mrow><mo>)</mo></mrow></msup><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow></mtd></mtr></mtable><mo>]</mo></mrow></mrow></mrow><mo>,</mo></mrow></math></maths><ul id="ul0139" list-style="none"><li id="ul0139-0001" num="0000"><ul id="ul0140" list-style="none"><li id="ul0140-0001" num="0000"><ul id="ul0141" list-style="none"><li id="ul0141-0001" num="0000"> where x(i)=[x(0)(i) . . . x(υ−1)(i)]T is a vector of symbols from the layer mapping in subclause 6.3.3.2 of [3], PE {1,2,4,8,12,16} is the number of CSI-RS ports configured, and if only one CSI-RS port is configured, W(i) is 1, otherwise for UE configured for PMI/RI reporting W(i) is the precoding matrix corresponding to the reported PMI applicable to x(i) and for UE configured without PMI reporting W(i) is the selected precoding matrix corresponding to the reported CQI applicable to x(i). The corresponding PDSCH signals transmitted on antenna ports {15 . . . 14+P} would have a ratio of EPRE to CSI-RS EPRE equal to the ratio given in subclause 7.2.5.</li></ul></li><li id="ul0140-0002" num="0358">For transmission mode 10 CSI reporting, if a CSI process is configured without PMI/RI reporting: <ul id="ul0142" list-style="none"><li id="ul0142-0001" num="0359">If the number of antenna ports of the associated CSI-RS resource is one, a PDSCH transmission is on single-antenna port, port 7. The channel on antenna port {7} is inferred from the channel on antenna port {15} of the associated CSI-RS resource. <ul id="ul0143" list-style="none"><li id="ul0143-0001" num="0360">CRS REs are as in non-MBSFN subframes. The CRS overhead is assumed to be the same as the CRS overhead corresponding to the number of CRS antenna ports of the serving cell;</li><li id="ul0143-0002" num="0361">The UE-specific reference signal overhead is 12 REs per PRB pair.</li></ul></li><li id="ul0142-0002" num="0362">Otherwise, <ul id="ul0144" list-style="none"><li id="ul0144-0001" num="0363">If the number of antenna ports of the associated CSI-RS resource is 2, the PDSCH transmission scheme assumes the transmit diversity scheme defined in subclause 7.1.2 on antenna ports {0,1} except that the channels on antenna ports {0,1} are inferred from the channels on antenna port {15, 16} of the associated CSI resource respectively.</li><li id="ul0144-0002" num="0364">If the number of antenna ports of the associated CSI-RS resource is 4, the PDSCH transmission scheme assumes the transmit diversity scheme defined in subclause 7.1.2 on antenna ports {0,1,2,3} except that the channels on antenna ports {0,1,2,3} are inferred from the channels on antenna ports {15, 16, 17, 18} of the associated CSI-RS resource respectively.</li><li id="ul0144-0003" num="0365">The UE is not expected to be configured with more than 4 antenna ports for the CSI-RS resource associated with the CSI process configured without PMI/RI reporting.</li><li id="ul0144-0004" num="0366">The overhead of CRS REs is assuming the same number of antenna ports as that of the associated CSI-RS resource.</li><li id="ul0144-0005" num="0367">UE-specific reference signal overhead is zero.</li></ul></li></ul></li><li id="ul0140-0003" num="0368">For transmission mode 10 CSI reporting, if a CSI process is configured with PMI/RI reporting or without PMI reporting: <ul id="ul0145" list-style="none"><li id="ul0145-0001" num="0369">CRS REs are as in non-MBSFN subframes. The CRS overhead is assumed to be the same as the CRS overhead corresponding to the number of CRS antenna ports of the serving cell;</li><li id="ul0145-0002" num="0370">The UE-specific reference signal overhead is consistent with the most recent reported rank for the CSI process if more than one CSI-RS port is configured, and is consistent with rank 1 transmission if only one CSI-RS port is configured; and PDSCH signals on antenna ports {7 . . . 6+υ} for υ layers would result in signals equivalent to corresponding symbols transmitted on antenna ports {15 . . . 14+P}, as given by</li></ul></li></ul></li></ul>

<maths id="MATH-US-00019" num="00019"><math overflow="scroll"><mrow><mrow><mrow><mo>[</mo><mtable><mtr><mtd><mrow><msup><mi>y</mi><mrow><mo>(</mo><mn>15</mn><mo>)</mo></mrow></msup><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow></mtd></mtr><mtr><mtd><mi>⋮</mi></mtd></mtr><mtr><mtd><mrow><msup><mi>y</mi><mrow><mo>(</mo><mrow><mn>14</mn><mo>+</mo><mi>P</mi></mrow><mo>)</mo></mrow></msup><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow></mtd></mtr></mtable><mo>]</mo></mrow><mo>=</mo><mrow><mrow><mi>W</mi><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow><mo></mo><mrow><mo>[</mo><mtable><mtr><mtd><mrow><msup><mi>x</mi><mrow><mo>(</mo><mn>0</mn><mo>)</mo></mrow></msup><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow></mtd></mtr><mtr><mtd><mi>⋮</mi></mtd></mtr><mtr><mtd><mrow><msup><mi>y</mi><mrow><mo>(</mo><mrow><mi>v</mi><mo>-</mo><mn>1</mn></mrow><mo>)</mo></mrow></msup><mo></mo><mrow><mo>(</mo><mi>i</mi><mo>)</mo></mrow></mrow></mtd></mtr></mtable><mo>]</mo></mrow></mrow></mrow><mo>,</mo></mrow></math></maths><ul id="ul0146" list-style="none"><li id="ul0146-0001" num="0000"><ul id="ul0147" list-style="none"><li id="ul0147-0001" num="0000"><ul id="ul0148" list-style="none"><li id="ul0148-0001" num="0000"> where x(i)=[x(0)(i) . . . x(υ−1)(i)]T is a vector of symbols from the layer mapping in subclause 6.3.3.2 of [3], PE {1,2,4,8,12,16} is the number of antenna ports of the associated CSI-RS resource, and if P=1, W(i) is 1, otherwise for UE configured for PMI/RI reporting W(i) is the precoding matrix corresponding to the reported PMI applicable to x(i) and for UE configured without PMI reporting W(i) is the selected precoding matrix corresponding to the reported CQI applicable to x(i). The corresponding PDSCH signals transmitted on antenna ports {15 . . . 14+P} would have a ratio of EPRE to CSI-RS EPRE equal to the ratio given in subclause 7.2.5</li></ul></li><li id="ul0147-0002" num="0371">Assume no REs allocated for CSI-RS and zero-power CSI-RS</li><li id="ul0147-0003" num="0372">Assume no REs allocated for PRS <ul id="ul0149" list-style="none"><li id="ul0149-0001" num="0373">The PDSCH transmission scheme given by Table 7.2.3-0 depending on the transmission mode currently configured for the UE (which may be the default mode).</li><li id="ul0149-0002" num="0374">If CRS is used for channel measurements, the ratio of PDSCH EPRE to cell-specific RS EPRE is as given in subclause 5.2 with the exception of ρA which shall be assumed to be <ul id="ul0150" list-style="none"><li id="ul0150-0001" num="0375">ρA=PA+Δoffset+10 log10(2) [dB] for any modulation scheme, if the UE is configured with transmission mode 2 with 4 cell-specific antenna ports, or transmission mode 3 with 4 cell-specific antenna ports and the associated RI is equal to one;</li><li id="ul0150-0002" num="0376">ρA=PA+Δoffset [dB] for any modulation scheme and any number of layers, otherwise.</li></ul></li></ul></li><li id="ul0147-0004" num="0377">The shift Δoffset is given by the parameter nomPDSCH-RS-EPRE-Offset which is configured by higher-layer signalling.</li></ul></li></ul>

Table 7.2.3-0 of 3GPP TS 36.213 v13.2.0, Entitled “PDSCH Transmission Scheme Assumed for CSI Reference Resource”, is Reproduced as FIG.

Table 7.2.3-1 of 3GPP TS 36.213 v13.2.0, Entitled “4-Bit CQI Table”, is Reproduced as FIG.

Table 7.2.3-2 of 3GPP TS 36.213 v13.2.0, Entitled “4-Bit CQI Table 2”, is Reproduced as FIG.

Table 7.2.3-3 of 3GPP TS 36.213 v13.2.0, Entitled “4-Bit CQI Table 3”, is Reproduced as FIG.

In general, physical layer procedures for beamforming require multi-beam based approaches. The eNB performs beamforming to overcome the higher pathloss in higher frequency. At one time or one symbol time, the eNB generates part of eNB beams instead of all eNB beams due to the limitation of analog or hybrid beamforming. For transmission scheduling, the eNB requires the beam information of a UE, for instance which eNB beams are qualified for the UE. The eNB beam with qualified channel quality may mean the beam(s) with RSRP (Reference Signal Received Power) or SINR larger than some threshold or the beam(s) with pathloss (PL) smaller than some threshold. Alternatively, the eNB beam with qualified channel quality may mean the beam(s) with RSRP or SINR or PL (absolute) difference smaller than some threshold comparing to the eNB beam with the best channel quality.

The eNB may perform beam sweeping on SRS to get the qualified eNB beam information of a UE. Alternatively, a UE can perform eNB beam measurement, and then report the qualified eNB beam information to eNB. Similarly, the UE may possibly have the capability to perform beamforming, i.e., to form UE beam(s), to get more power gain.

Multi-beam based approaches require consideration on how to determine UL RS (Reference Signal) power. The UL RS may comprise UL RS for demodulation, UL RS for channel measurement, and UL RS for beam management. The UL RS for demodulation may be UL DMRS. The UL RS for channel measurement may be Sounding RS. The UL RS for beam management may be sounding RS or a new UL RS.

Considering different functional characteristics and requirements, different power control mechanisms may be applied.

Since UL RS for demodulation is for demodulation of uplink data and/or control channel, the transmit power of UL RS for demodulation shall be determined as transmit power of the associated uplink data and/or control channel.

As for UL RS for UL channel measurement, the motivation is to assist TRP or eNB in measuring UL channel. In LTE or LTE-A, SRS is utilized for UL channel measurement. And SRS power is associated with PUSCH, e.g., sharing some configured power parameters and sharing the close-loop power control adjustment state. For the multi-beam based approaches, one possible direction is to associate UL data channel for determining the transmit power of UL RS for channel measurement.

The UL RS for channel measurement may be sounding reference signal. The transmit power of UL RS for channel measurement on different UE beams may be different. Moreover, a TPC (Transmit Power Control) (command) can be applied for power control of UL RS for beam management, uplink data and/or control channel, and/or UL RS for UL channel measurement. The TPC (command) may be delivered via a DL (Downlink) control signaling. <ul id="ul0151" list-style="none"><li id="ul0151-0001" num="0000"><ul id="ul0152" list-style="none"><li id="ul0152-0001" num="0385">In case that the power control of uplink data channel is performed per UE beam, pathloss derivation and/or TPC command are applied per UE beam. The transmit power of UL RS for channel measurement of a UE beam can be associated with the uplink data channel of the same UE beam. More specifically, the transmit power of UL RS for channel measurement can be determined via sharing any of some configured power parameters, pathloss derivation or close-loop power control adjustment state of the uplink data channel on the same UE beam. Since the linked eNB beam(s) or TRP beam(s) and propagation path for each UE beam would be different, it would be more accurate and adaptive to perform per UE beam power control for UL RS for UL channel measurement.</li><li id="ul0152-0002" num="0386">In case that the power control of uplink data channel is not performed per UE beam, for instance, the power control of uplink data channel is performed per UE, and pathloss derivation and TPC command (enhanced) are applied to all beams. The UE can associate the transmit power of UL RS for channel measurement of a UE beam to the uplink data channel, irrespective of which UE beam is used for uplink data channel. More specifically, the transmit power of UL RS for channel measurement of a UE beam is associated with the transmit power of the latest uplink data channel transmission, irrespective of which UE beam is used for uplink data channel transmission. If there is an uplink data channel transmission in the same subframe, slot, or mini-slot with a UL RS transmission for channel measurement, the transmit power of the UL RS for channel measurement may be associated with the uplink data channel transmission. Alternatively, the UE can associate the transmit power of UL RS for channel measurement of a UE beam to the uplink data channel on the same UE beam. More specifically, the transmit power of UL RS for channel measurement of a UE beam is associated with the transmit power of the latest uplink data channel transmission on the same UE beam. If there is an uplink data channel transmission on the same UE beam in the same subframe, slot, or mini-slot with a UL RS transmission for channel measurement, the transmit power of the UL RS for channel measurement may be associated with the uplink data channel transmission. The association means that the transmit power determination of UL RS for channel measurement shares any of some configured power parameters, pathloss derivation, or the close-loop power control adjustment state of the associated uplink data channel.</li></ul></li></ul>

More specifically, the UL RS for channel measurement may be configured or transmitted on the UE beam(s) linked with qualified eNB beam(s) or TRP beam(s). It may be possible to skip UL RS transmission for channel measurement on a UE beam if there is no detected eNB beams or TRP beams, or if there is no linked qualified eNB beam(s) or TRP beam(s) on the UE beam. More specifically, no detected eNB beams or TRP beams or no linked qualified eNB beam(s) or TRP beam(s) may mean that the associated DL RS is not detected or that the channel quality of the associated DL RS is worse (for instance, RSRP is lower than a threshold). Alternatively, the UL RS for channel measurement is transmitted on a UE beam if there is no detected eNB beams or TRP beams or there is no linked qualified eNB beam(s) or TRP beam(s) on the UE beam.

As for UL RS for beam measurement, the motivation is to assist TRP or eNB in detecting and/or tracking qualified eNB beam(s) and/or qualified UE beam(s) for the UE. It may be assumed that all UE beams shares the same transmit power of UL RS for beam measurement. The power control of UL RS for beam management is performed separately from the power control of UL RS for UL channel measurement. More specifically, the power control of UL RS for beam management may not be associated with uplink data and/or control channel. Moreover, it is possible to design a TPC (command) specifically for power control of UL RS for beam management, instead of for uplink data and/or control channel and UL RS for UL channel measurement. The TPC (command) may be applied per UE beam. Moreover, the TPC (command) may be applied per UE beam group. The TPC (command) may be delivered via DL control signaling.

Furthermore, if there is no detected eNB beams or TRP beams, or if there is no linked qualified eNB beam(s) or TRP beam(s) on a UE beam, it is possible that the UE skips some or all transmit occasions of UL RS transmission for beam management on the UE beam. Alternatively, the UE may transmit (periodic) UL RS for beam management, except on the UE beam(s) with (periodic) UL RS for UL channel measurement. It may mean that if there is any detected eNB beams or TRP beams or if there is linked qualified eNB beam(s) or TRP beam(s) on a UE beam, the UE skips some or all transmit occasions of the (periodic) UL RS transmission for beam management on the UE beam. Since the (periodic) UL RS transmission for UL channel measurement can assist eNB or TRP in performing beam management. More specifically, no detected eNB beams or TRP beams or no linked qualified eNB beam(s) or TRP beam(s) may mean that the associated DL RS is not detected or that the channel quality of the associated DL RS is worse, for instance RSRP lower than a threshold. Alternatively, the UL RS for beam management is transmitted on a UE beam if there is no detected eNB beams or TRP beams or there is no linked qualified eNB beam(s) or TRP beam(s) on the UE beam.

<figref idref="DRAWINGS">FIG. 14</figref> is a flow chart 1400 according to one exemplary embodiment from the perspective of a UE. In step 1405, the UE derives a first transmit power of a first UL RS based on a first power control mechanism. In step 1410, the UE derives a second transmit power of a second UL RS based on a second power control mechanism. In step 1415, the UE transmits the first UL RS with the first transmit power. In step 1420, the UE transmits the second UL RS with the second transmit power.

<figref idref="DRAWINGS">FIG. 15</figref> is a flow chart 1500 according to one exemplary embodiment from the perspective of a UE. In step 1505, the UE derives a first transmit power of a first UL RS based on a first power control mechanism, wherein derivation of the first transmit power based on the first power control mechanism is associated with an uplink data channel. In step 1510, the UE derives a second transmit power of a second UL RS based on a second power control mechanism, wherein derivation of the second transmit power based on the second power control mechanism is not associated with the uplink data channel. In step 1515, the UE transmits the first UL RS with the first transmit power. In step 1520, the UE transmits the second UL RS with the second transmit power.

In one embodiment, as shown in step 1525, the UE receives a first TPC (command), wherein the first TPC (command) is applied to the first power control mechanism of the first UL RS and is applied to the uplink data channel. Furthermore, in step 1530, the UE receives a second TPC (command), wherein the second TPC (command) is applied to the second power control mechanism of the second UL RS and is neither applied to the uplink data channel nor the first power control mechanism of the first UL RS.

In one embodiment, the first UL RS and the second UL RS could be used for different functions with different characteristics. For example, the first UL RS could be used for channel measurement. For example, the second UL RS could be used for beam management. The first UL RS and the second UL RS could be different kinds or types of reference signaling. For example, the first UL RS could be a sounding reference signaling. For example, the second UL RS could be a sounding reference signal. The sounding reference signal of the second UL RS could be a different kind or type from the first UL RS. Alternatively, the second UL RS could be neither a DMRS (DeModulation Reference Signal) nor a sounding reference signal.

In one embodiment, for the first power control mechanism, the derivation of the first transmit power of the first UL RS could be associated with uplink data channel. For the first power control mechanism, the first transmit power derivation of the first UL RS could share any of some configured power parameters, pathloss derivation, or the close-loop power control adjustment state of the associated uplink data channel. Derivation of the first transmit power based on the first power control mechanism uses at least one of configured power parameters, pathloss derivation, and close-loop power control adjustment state of the associated uplink data channel.

For the first power control mechanism, if power control of the uplink data channel is performed per UE beam, the first transmit power of the first UL RS of a UE beam could be associated with the uplink data channel of the same UE beam. Alternatively, for the first power control mechanism, if power control of the uplink data channel is performed per UE, the first transmit power of the first UL RS of a UE beam could be associated with the uplink data channel regardless of which UE beam is used for the uplink data channel. Alternatively or additionally, the first transmit power of the first UL RS of a UE beam could be associated with the latest uplink data channel transmission regardless of which UE beam is used for the uplink data channel transmission.

In one embodiment, for the first power control mechanism, if there is an uplink data channel transmission in the same subframe, slot, or mini-slot with the first UL RS transmission, the first transmit power of the first UL RS could be associated with the uplink data channel transmission. For the first power control mechanism, if power control of the uplink data channel is performed per UE, the first transmit power of the first UL RS of a UE beam could be associated with the uplink data channel (or the latest of uplink data channel) on the same UE beam.

In one embodiment, for the first power control mechanism, if there is an uplink data channel transmission on the same UE beam in the same subframe, slot, or mini-slot with the first UL RS transmission, the first transmit power of the first UL RS could be associated with the uplink data channel transmission.

In one embodiment, the UE receives a first TPC (Transmit Power Control) (command). The first TPC (command) could be delivered via DL (Downlink) control signaling. The first TPC (command) could be applied to the first power control mechanism of the first UL RS. Alternatively or additionally, the first TPC (command) could be applied to the power control of the uplink data channel. Alternatively or additionally, the first TPC (command) could be applied to the uplink control channel.

In one embodiment, the UE could skip the first UL RS transmission on a UE beam if there is no detected eNB beams or TRP beams or there is no linked qualified eNB beam(s) or TRP beam(s) on the UE beam. For the first power control mechanism, the first transmit power of the first UL RS on different UE beams can be different.

In one embodiment, the derivation of the second transmit power of the second UL RS could be performed separately from the derivation of the first transmit power of the first UL RS. For the second power control mechanism, the derivation of the second transmit power of the second UL RS may not be associated with an uplink data and/or control channel. For the second power control mechanism, the second transmit power of the second UL RS on different UE beams could be the same.

In one embodiment, the UE receives a second TPC (command). The second TPC (command) could be delivered via DL control signaling. The second TPC (command) could be applied per UE beam or per UE beam group. Alternatively or additionally, the second TPC (command) could be applied (specifically) to the second power control mechanism of the second UL RS. However, the second TPC (command) may not be applied to an uplink data and/or control channel, and/or to the first power control mechanism of the first UL RS.

In one embodiment, if there is no detected eNB beam or TRP beam or there is no linked qualified eNB beam(s) or TRP beam(s) on a UE beam, the UE could skip some or all transmit occasions of the second UL RS on the UE beam. Alternatively, if there is any detected eNB beam or TRP beams or there is any linked qualified eNB beam(s) or TRP beam(s) on a UE beam, the UE could skip some or all transmit occasions of the second UL RS on the UE beam. No detected eNB beams or TRP beams on a UE beam could mean that the DL RS is not detected on the UE beam or that measured channel quality of the DL RS is worse. No linked qualified eNB beam(s) or TRP beam(s) on a UE beam could mean that an associated DL RS is not detected on the UE beam or measured channel quality of the DL RS is worse. Worse channel quality of the DL RS could mean that measured RSRP of the DL RS is lower than a threshold. The DL RS could be a beam reference signal.

An eNB beam or TRP beam with qualified channel quality could mean that the UE receives the eNB beam or TRP beam with RSRP or SINR larger than some threshold or with a pathloss smaller than some threshold.

In one embodiment, the UE could transmit the (periodic) second UL RS, except on UE beam(s) with the (periodic) first UL RS.

Referring back to <figref idref="DRAWINGS">FIGS. 3 and 4</figref>, in one exemplary embodiment of a UE illustrated in <figref idref="DRAWINGS">FIG. 14</figref> and discussed above, the device 300 includes a program code 312 stored in the memory 310. The CPU 308 could execute program code 312 to enable the UE (i) to derive a first transmit power of a first UL RS based on a first power control mechanism, (ii) to derive a second transmit power of a second UL RS based on a second power control mechanism, (iii) to transmit the first UL RS with the first transmit power, and (iv) to transmit the second UL RS with the second transmit power. Furthermore, the CPU 308 can execute the program code 312 to perform all of the above-described actions and steps or others described herein.

Referring back to <figref idref="DRAWINGS">FIGS. 3 and 4</figref>, in one exemplary embodiment of a UE illustrated in <figref idref="DRAWINGS">FIG. 15</figref> and discussed above, the device 300 includes a program code 312 stored in the memory 310. The CPU 308 could execute program code 312 to enable the UE (i) to derive a first transmit power of a first UL RS based on a first power control mechanism, wherein derivation of the first transmit power based on the first power control mechanism is associated with an uplink data channel, (ii) to derive a second transmit power of a second UL RS based on a second power control mechanism, wherein derivation of the second transmit power based on the second power control mechanism is not associated with the uplink data channel, (iii) to transmit the first UL RS with the first transmit power, and (iv) to transmit the second UL RS with the second transmit power.

In one embodiment, the CPU 308 could further execute program code 312 to enable the UE (i) to receive a first TPC (command), wherein the first TPC (command) is applied to the first power control mechanism of the first UL RS and is applied to the uplink data channel, and (ii) to receive a second TPC (command), wherein the second TPC (command) is applied to the second power control mechanism of the second UL RS and is neither applied to the uplink data channel nor the first power control mechanism of the first UL RS.

Furthermore, the CPU 308 can execute the program code 312 to perform all of the above-described actions and steps or others described herein.

During random access (for initial access), initial transmit power of some beam(s) used for random access may be decided. As shown in exemplary <figref idref="DRAWINGS">FIGS. 16 and 17</figref>, UE beam B2 with transmit power P1 is found during a RA (Random Access) procedure. It means that TRP can detect UL transmission on UE beam B2 with received power exceeding a reception threshold, PRX. Furthermore, for the same TRP, UE beam B3 is considered as candidate beam to be qualified UE beam, but UE beam B1 and B4. Then, not all candidate UE beams can be found with transmit power P1 since the received power at TRP is lower than the reception threshold, PRX.

Thus, to assist TRP in detecting all candidate UE beams, the following approach(es) could be considered and used:

First Approach

In general, the first approach is to use a specific power value for the transmit power of UL RS for beam management on each UE beam(s), e.g., UE beams B1˜B4 in the instance of <figref idref="DRAWINGS">FIG. 16</figref> and <figref idref="DRAWINGS">FIG. 17</figref>. The specific power value may be configured or specified. Moreover, pathloss may not be considered for the transmit power derivation. More specifically, the transmit power of UL RS for beam management is set as the specific power value. Alternatively, pathloss may be considered for the transmit power derivation, and the pathloss may be derived from DL RS measurement result of eNB beams or TRP beams. More specifically, the transmit power of UL RS for beam management is set as the specific power value+pathloss. The DL RS may be BRS (Beam Reference Signal).

Moreover, if there is no detected eNB beams or TRP beams or if there is no linked qualified eNB beam(s) or TRP beam(s) on a UE beam, it is possible that the UE skips some or all transmit occasions of UL RS for beam management on the UE beam.

Second Approach

In general, the second approach is that transmit power derivation of UL RS for beam management comprises required UL transmit power of UE beam(s) for eNB or TRP detection. The required UL transmit power of a UE beam for eNB or TRP detection means that the eNB or TRP can receive the UL RS with received power exceeding a reception threshold. Furthermore, the transmit power derivation of UL RS for beam management comprises an offset. More specifically, the offset is a qualified beam criterion. A eNB beam or a TRP beam with qualified channel quality means the eNB beam or the TRP beam with RSRP, SINR, or PL (absolute) difference smaller than the qualified beam criterion comparing to the eNB beam or the TRP beam with the best channel quality. For instance, UE beam B2 with transmit power P1 is derived during RA procedure. Then, the transmit power of UL RS for beam management on UE beam B2 is P1+offset. The transmit power of UL RS for beam management on UE beam B3, B1 and B4 are P1+offset as well. It means that the (initial) transmit power of the UL RS for beam management is derived at least from the offset and the required UL transmit power of a UE beam(s) derived from random access procedure.

The transmit power derivation of the UL RS for beam management may comprise the required UL transmit power of UE beam(s) for eNB or TRP detection with received power exceeding a reception threshold. Denoted P1, Px, Py, Pz are the required UL transmit power on UE beam B2, B1, B3, B4 for eNB or TRP detection with received power exceeding a reception threshold, PRX. With UE moving or rotation, the values of P1, Px, Py, Pz may change since propagation loss changes. Then, the transmit power derivation of UL RS for beam management may comprise min(P1, Px, Py, Pz). More specifically, the transmit power derivation of UL RS for beam management may be derived from min(P1, Px, Py, Pz)+offset. Alternatively, if the UE beam 2 is associated with the eNB beam or TRP beam with the best channel quality, the transmit power derivation of UL RS for beam management may comprise P1. More specifically, the transmit power derivation of UL RS for beam management may be derived from P1+offset.

More specifically, the required UL transmit power of a UE beam for eNB or TRP detection with received power exceeding a reception threshold may be derived from measuring DL RS of the eNB beam(s) or TRP beam(s). Thus, the P1, Px, Py, Pz may be derived from measuring DL RS of the eNB beam(s) or TRP beam(s). The DL RS may be BRS.

If there is no detected eNB beams or TRP beams or there is no linked qualified eNB beam(s) or TRP beam(s) on the UE Beam(s), it can be determined as Pcmax or no value. No value means that a value is not included in the transmit power determination of UL RS for beam management. For instance, the transmit power derivation of UL RS for beam management may comprise min(P1, Py) wherein the UE beam B2 and B3 are linked with qualified eNB beam(s) or TRP beam(s) and the UE beam B1 and B4 are not linked with any qualified eNB beam(s) or TRP beam(s).

Px and Pz are not included in the transmit power determination of UL RS for beam management, since there is no detected eNB beams or TRP beams or there is no linked qualified eNB beam(s) or TRP beam(s) on UE beam B1 and UE beam B4. More specifically, the transmit power derivation of UL RS for beam management may be derived from min(P1, Py)+offset. Alternatively, if Pcmax is determined for the UE beam(s) wherein there is no detected eNB beams or TRP beams, or if there is no linked qualified eNB beam(s) or TRP beam(s) on the UE Beam(s), the transmit power derivation of UL RS for beam management may comprise min(P1, Px, Py, Pz). More specifically, the transmit power derivation of UL RS for beam management may be derived from min(P1, Px, Py, Pz)+offset.

Furthermore, a specific value can be configured or specified as minimum required UE beam power for beam management. More specifically, the transmit power derivation of UL RS for beam management may be derived from Max(specific value, min(P1, Px, Py, Pz)+offset). If there is no detected eNB beams or TRP beams or if there is no linked qualified eNB beam(s) or TRP beam(s) on the UE beam B1 and UE beam B4, the transmit power derivation of UL RS for beam management may be derived from Max(specific power value, min(P1, Py)+offset) or Max(specific value, min(P1, Px, Py, Pz)+offset).

Third Approach

In general, the third approach is that the UE transmits (periodic) UL RS for beam management, except on the UE beam(s) with (periodic) UL RS for UL channel measurement. It may mean that if there is any detected eNB beams or TRP beams or there is linked qualified eNB beam(s) or TRP beam(s) on a UE beam, the UE skips some or all transmit occasions of the (periodic) UL RS transmission for beam management on the UE beam. Since the (periodic) UL RS transmission for UL channel measurement can assist eNB or TRP in performing beam management. Thus, in this approach, the transmit power of UL RS for beam management is determined or derived from a specific power value. The specific power value may be configured or specified. Moreover, pathloss may not be considered for the transmit power derivation. Alternatively, pathloss may be considered for the transmit power derivation and the pathloss may be derived from DL RS measurement result of eNB beams or TRP beams. The DL RS may be BRS.

More specifically, no detected eNB beams or TRP beams or no linked qualified eNB beam(s) or TRP beam(s) may mean that the associated DL RS is not be detected or the channel quality of the associated DL RS is worse, for instance RSRP lower than a threshold.

<figref idref="DRAWINGS">FIG. 18</figref> is a flow chart 1800 according to one exemplary embodiment from the perspective of a UE. In step 1805, the UE derives a transmit power of a UL RS based on a specific power value. In step 1810, the UE transmits the UL RS with the transmit power.

<figref idref="DRAWINGS">FIG. 19</figref> is a flow chart 1900 according to one exemplary embodiment from the perspective of a UE. In step 1905, the UE derives a transmit power of a UL RS wherein a derivation of the transmit power comprises a required UL transmit power of UE beam(s) for eNB or TRP detection. In step 1910, the UE transmits the UL RS with the transmit power.

<figref idref="DRAWINGS">FIG. 20</figref> is a flow chart 2000 according to one exemplary embodiment from the perspective of a UE. In step 2005, the UE derives a transmit power of a UL RS based on a specific power value. In step 2010, the UE transmits the UL RS on a first UE beam of multiple UE beams with the transmit power. In step 2015, the UE transmits the UL RS on a second UE beam of the multiple UE beams with the transmit power.

In one embodiment, the UL RS could be for beam management. The UL RS could be a sounding reference signaling. Alternative, the UL RS is neither a DMRS nor a sounding reference signal.

In one embodiment, the derivation of the transmit power of the UL RS may not be associated with an uplink data and/or control channel. The transmit power of the UL RS on different UE beams could be the same.

In one embodiment, a TPC (command) could be applied specifically for power control of the UL RS, instead of for an uplink data and/or control channel. The specific power value could be configured or specified. Alternatively, the specific power value could be a UL transmission power of a third UE beam derived from a random access procedure. The derivation of the transmit power of the UL RS could include a pathloss. The pathloss could be derived from DL RS measurement result of eNB beams or TRP beams. The DL RS could be a beam reference signal.

The transmit power may not be smaller than the specific power value. The transmit power (of the UL RS) could be set as the specific power value. Alternatively, the transmit power (of the UL RS) could be set as the specific power value+pathloss.

The derivation of the transmit power of the UL RS could comprise an offset. Alternatively or additionally, the derivation of the transmit power could be based on an offset. The offset could be a qualified beam criterion, wherein a eNB beam is considered with qualified channel quality if the eNB beam with RSRP, SINR, or PL (absolute) difference smaller than the qualified beam criterion comparing to a eNB beam or TRP beam with the best channel quality.

In one embodiment, the (initial) transmit power of the UL RS could be derived at least from an offset and the required UL transmit power of a UE beam(s) derived from a random access procedure. The required UL transmit power of a UE beam for eNB or TRP detection could mean that the eNB or TRP receives the UL RS with received power exceeding a reception threshold.

The derivation of the transmit power of the UL RS could comprise the required UL transmit power of a UE beam for eNB or TRP detection wherein the UE beam is associated with a eNB beam or TRP beam with the best channel quality. The transmit power of the UL RS could be derived at least from an offset and the required UL transmit power of a UE beam for eNB or TRP detection, wherein the UE beam is associated with a eNB beam or TRP beam with the best channel quality.

Alternatively or additionally, the derivation of the transmit power of the UL RS could comprise a minimum value among the required UL transmit power of each UE beam for eNB or TRP detection. The transmit power of the UL RS could be derived at least from an offset and a minimum value among the required UL transmit power of each UE beam for eNB or TRP detection. The required UL transmit power of a UE beam for eNB or TRP detection could be derived from measuring DL RS of eNB beam(s) or TRP beam(s) on the UE beam.

In one embodiment, if there is no detected eNB beam or TRP beam or if there is no linked qualified eNB beam or TRP beam on a UE beam, the UE could skip some or all transmit occasions of the UL RS on the UE beam.

In one embodiment, if there is no detected eNB beam or TRP beam or if there is no linked qualified eNB beam or TRP beam on a UE beam, the required UL transmit power of the UE beam could be determined as Pcmax.

In one embodiment, if there is no detected eNB beam or TRP beam or if there is no linked qualified eNB beam or TRP beam on a UE beam, the required UL transmit power of the UE beam may not be included in the derivation of the transmit power of the UL RS.

In one embodiment, a specific value could be configured or specified as minimum required transmit power for the transmit power of the UL RS.

In one embodiment, if there is any detected eNB beam or TRP beam or if there is linked qualified eNB beam(s) or TRP beam(s) on a UE beam, the UE could skip some or all transmit occasions of the (periodic) UL RS on the UE beam. The UE could transmit the (periodic) UL RS, except on UE beam(s) with a (periodic) UL RS transmission for UL channel measurement. No detected eNB beams or TRP beams on a UE beam could mean that DL RS is not be detected on the UE beam or that measured channel quality of the DL RS is worse. No linked qualified eNB beam(s) or TRP beam(s) on a UE beam could mean that an associated DL RS is not detected on the UE beam or that measured channel quality of the DL RS is worse. Worse measured channel quality of the DL RS means that RSRP of the DL RS is lower than a threshold.

In one embodiment, a eNB beam or TRP beam with qualified channel quality could mean that the UE receives the eNB beam or TRP beam with RSRP or SINR larger than some threshold or pathloss smaller than some threshold. The DL RS could be a beam reference signal.

Referring back to <figref idref="DRAWINGS">FIGS. 3 and 4</figref>, in one exemplary embodiment of a UE illustrated in <figref idref="DRAWINGS">FIG. 18</figref> and discussed above, the device 300 includes a program code 312 stored in the memory 310. The CPU 308 could execute program code 312 to enable the UE (i) to derive a transmit power of a UL RS based on a specific power value, and (ii) to transmit the UL RS with the transmit power. Furthermore, the CPU 308 can execute the program code 312 to perform all of the above-described actions and steps or others described herein.

Referring back to <figref idref="DRAWINGS">FIGS. 3 and 4</figref>, in one exemplary embodiment of a UE shown in <figref idref="DRAWINGS">FIG. 19</figref> and discussed above, the device 300 includes a program code 312 stored in the memory 310. The CPU 308 could execute program code 312 to enable the UE (i) to derive a transmit power of a UL RS wherein the derivation of the transmit power comprises a required UL transmit power of UE beam(s) for eNB or TRP detection, and (ii) to transmit the UL RS with the transmit power. Furthermore, the CPU 308 can execute the program code 312 to perform all of the above-described actions and steps or others described herein.

Referring back to <figref idref="DRAWINGS">FIGS. 3 and 4</figref>, in one exemplary embodiment of a UE illustrated in <figref idref="DRAWINGS">FIG. 20</figref> and discussed above, the device 300 includes a program code 312 stored in the memory 310. The CPU 308 could execute program code 312 to enable the UE (i) to derive a transmit power of a UL RS based on a specific power value, (ii) to transmit the UL RS on a first UE beam of multiple UE beams with the transmit power, and (iii) to transmit the UL RS on a second UE beam of the multiple UE beams with the transmit power. Furthermore, the CPU 308 can execute the program code 312 to perform all of the above-described actions and steps or others described herein.

In general, based on the invention, the UL RS transmit power can be determined based on the functional characteristic and requirement. The UL RS transmit power for beam management can be set to assist TRP or eNB in detecting and/or tracking qualified eNB beam(s) and/or qualified UE beam(s) for the UE.

Various aspects of the disclosure have been described above. It should be apparent that the teachings herein may be embodied in a wide variety of forms and that any specific structure, function, or both being disclosed herein is merely representative. Based on the teachings herein one skilled in the art should appreciate that an aspect disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, such an apparatus may be implemented or such a method may be practiced using other structure, functionality, or structure and functionality in addition to or other than one or more of the aspects set forth herein. As an example of some of the above concepts, in some aspects concurrent channels may be established based on pulse repetition frequencies. In some aspects concurrent channels may be established based on pulse position or offsets. In some aspects concurrent channels may be established based on time hopping sequences. In some aspects concurrent channels may be established based on pulse repetition frequencies, pulse positions or offsets, and time hopping sequences.

Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Those of skill would further appreciate that the various illustrative logical blocks, modules, processors, means, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two, which may be designed using source coding or some other technique), various forms of program or design code incorporating instructions (which may be referred to herein, for convenience, as “software” or a “software module”), or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

In addition, the various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or performed by an integrated circuit (“IC”), an access terminal, or an access point. The IC may comprise a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute codes or instructions that reside within the IC, outside of the IC, or both. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

It is understood that any specific order or hierarchy of steps in any disclosed process is an example of a sample approach. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The steps of a method or algorithm described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module (e.g., including executable instructions and related data) and other data may reside in a data memory such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. A sample storage medium may be coupled to a machine such as, for example, a computer/processor (which may be referred to herein, for convenience, as a “processor”) such the processor can read information (e.g., code) from and write information to the storage medium. A sample storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in user equipment. In the alternative, the processor and the storage medium may reside as discrete components in user equipment. Moreover, in some aspects any suitable computer-program product may comprise a computer-readable medium comprising codes relating to one or more of the aspects of the disclosure. In some aspects a computer program product may comprise packaging materials.

While the invention has been described in connection with various aspects, it will be understood that the invention is capable of further modifications. This application is intended to cover any variations, uses or adaptation of the invention following, in general, the principles of the invention, and including such departures from the present disclosure as come within the known and customary practice within the art to which the invention pertains.

Every citation, both ways

Citations
Document	Relation	Office	Category	Cited during	Relevant claims
US2018309487A1	Cited by	United States of America	–	Search report	–
CN113508621A	Cited by	China	–	Search report	–
WO2021228394A1	Cited by	World Intellectual Property Organization (WIPO)	–	International search	–
US2022200725A1	Cited by	United States of America	–	Search report	–
US10581504B2	Cited by	United States of America	–	Search report	–
US11601247B2	Cited by	United States of America	–	Applicant	–
US11558150B2	Cited by	United States of America	–	Search report	–
US10856234B2	Cited by	United States of America	–	Applicant	–
US2022322386A1	Cited by	United States of America	–	Pre-grant	–
US11496965B2	Cited by	United States of America	–	Applicant	–
US10763926B2	Cited by	United States of America	–	Search report	–
US11778607B2	Cited by	United States of America	–	Search report	–
CN111278120A	Cited by	China	–	Search report	–
US11770228B2	Cited by	United States of America	–	Applicant	–
US11742983B2	Cited by	United States of America	–	Search report	–
US2021058193A1	Cited by	United States of America	–	Search report	–
US2019261287A1	Cited by	United States of America	–	Search report	–
US11245552B2	Cited by	United States of America	–	Applicant	–
US11438121B2	Cited by	United States of America	–	Search report	–
US11570729B2	Cited by	United States of America	–	Search report	–
US10425901B2	Cited by	United States of America	–	Search report	–
US11528668B2	Cited by	United States of America	–	Applicant	–
US2019261347A1	Cited by	United States of America	–	Search report	–
US11395319B2	Cited by	United States of America	–	Applicant	–
US10476485B2	Cited by	United States of America	–	Search report	–
US2022030527A1	Cited by	United States of America	–	Search report	–
US10090986B2	Cites	United States of America	–	Search report	–
US10142949B2	Cites	United States of America	A	Search report	–
US10159052B2	Cites	United States of America	–	Search report	–
US10271287B2	Cites	United States of America	–	Search report	–
US10320475B2	Cites	United States of America	–	Search report	–
US10750453B2	Cites	United States of America	–	Search report	–
US10917854B2	Cites	United States of America	–	Search report	–
US11012948B2	Cites	United States of America	–	Search report	–
US11166242B2	Cites	United States of America	–	Search report	–
US2010103867A1	Cites	United States of America	–	Search report	–
US2010246561A1	Cites	United States of America	A	Search report	–
US2011098054A1	Cites	United States of America	A	Search report	–
US2011159914A1	Cites	United States of America	A	Search report	–
US2012113908A1	Cites	United States of America	A	Search report	–
US2013077571A1	Cites	United States of America	A	Search report	–
US2013121279A1	Cites	United States of America	A	Search report	–
US2013217404A1	Cites	United States of America	A	Search report	–
US2013250875A1	Cites	United States of America	–	Search report	–
US2014036809A1	Cites	United States of America	Y	Search report	1-5, 21-35
US2014071903A1	Cites	United States of America	–	Search report	–
US2014112260A1	Cites	United States of America	A	Search report	–
US2014169322A1	Cites	United States of America	–	Search report	–
US2014177531A1	Cites	United States of America	–	Search report	–
US2014185481A1	Cites	United States of America	A	Search report	–
US2014219232A1	Cites	United States of America	Y	Search report	1-5, 21-35
US2014376482A1	Cites	United States of America	A	Search report	–
US2015085787A1	Cites	United States of America	–	Search report	–
US2015092699A1	Cites	United States of America	–	Search report	–
US2016150490A1	Cites	United States of America	A	Search report	–
US2016165547A1	Cites	United States of America	A	Search report	–
US2016227485A1	Cites	United States of America	–	Search report	–
US2016337018A1	Cites	United States of America	–	Search report	–
US2017141894A1	Cites	United States of America	–	Search report	–
US2018014254A1	Cites	United States of America	Y	Search report	1-5, 21-35
US2018049137A1	Cites	United States of America	–	Search report	–
US2018352539A1	Cites	United States of America	–	Search report	–
US2018368075A1	Cites	United States of America	–	Search report	–
US2019097772A1	Cites	United States of America	–	Search report	–
US2019104549A1	Cites	United States of America	–	Search report	–
US2020106647A1	Cites	United States of America	–	Search report	–
US2020245253A1	Cites	United States of America	–	Search report	–
US9538410B2	Cites	United States of America	A	Search report	–
US9900849B2	Cites	United States of America	A	Search report	–

13 members in 7 offices

This recordMember, by publication datePriority claim

Priority claims10

Priority claims
Document	Office	Kind	Date
201662405533	United States of America	P	2016-10-07
201662405533	United States of America	P	2016-10-07
201662405564	United States of America	P	2016-10-07
201662405564	United States of America	P	2016-10-07
201715718335	United States of America	A	2017-09-28
62405533	–	–	–
62405564	–	–	–
US201662405533P	–	–	–
US201662405564P	–	–	–
US201715718335	–	–	–

Members13

Family members, oldest first
Document	Office	Kind
EP3306990A1	European Patent Office (EPO)	A1	2018-04-11
JP2018061246A	Japan	A	2018-04-12
US2018103433A1	United States of America	A1	2018-04-12
TW201815196A	Taiwan Province of China	A	2018-04-16
CN107920385A	China	A	2018-04-17
KR20180038992A	Republic of Korea	A	2018-04-17
TWI654893B	Taiwan Province of China	B	2019-03-21
JP6545232B2	Japan	B2	2019-07-17
CN107920385B	China	B	2020-03-03
EP3306990B1	European Patent Office (EPO)	B1	2020-03-11
KR102097854B1	Republic of Korea	B1	2020-04-06
ES2785474T3	Spain	T3	2020-10-07
US11737030B2	United States of America	B2	2023-08-22

30 transactions on the USPTO file

No rejections on record.

Non-final rejections: 0
Final rejections: 0
RCEs: 0
Appeals: 0

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event	Code
2018-07-19	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2018-07-19	Information Disclosure Statement (IDS) FiledM844	M844
2018-04-13	Email NotificationEML_NTR	EML_NTR
2018-04-12	PG-Pub Issue NotificationPG-ISSUE	PG-ISSUE
2018-03-22	Case Docketed to Examiner in GAUDOCK	DOCK
2018-01-15	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2018-01-15	Information Disclosure Statement (IDS) FiledM844	M844
2017-11-14	Case Docketed to Examiner in GAUDOCK	DOCK
2017-11-08	Application Dispatched from OIPEOIPE	OIPE
2017-10-18	Email NotificationEML_NTR	EML_NTR
2017-10-18	Application Is Now CompleteCOMP	COMP
2017-10-18	Filing Receipt - UpdatedFLRCPT.U	FLRCPT.U
2017-10-17	Sent to Classification ContractorPGPC	PGPC
2017-10-17	FITF set to YES - revise initial settingFTFS	FTFS
2017-10-13	Patent Term Adjustment - Ready for ExaminationPTA.RFE	PTA.RFE
2017-10-13	Additional Application Filing FeesADDFLFEE	ADDFLFEE
2017-10-13	Applicant has submitted new drawings to correct Corrected Papers problemsCORRDRW	CORRDRW
2017-10-13	Electronic ReviewELC_RVW	ELC_RVW
2017-10-13	Email NotificationEML_NTR	EML_NTR
2017-10-13	Email NotificationEML_NTF	EML_NTF
2017-10-13	Application ready for PDX access by participating foreign officesCCRDY	CCRDY
2017-10-13	Filing ReceiptFLRCPT.O	FLRCPT.O
2017-10-13	Corrected PaperCPAP	CPAP
2017-10-05	Cleared by OIPE CSRL194	L194
2017-09-28	PTO/SB/69-Authorize EPO Access to Search ResultsSREXR141	SREXR141
2017-09-28	Applicants have given acceptable permission for participating foreignAPPERMS	APPERMS
2017-09-28	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2017-09-28	IFW Scan & PACR Auto Security ReviewSCAN	SCAN
2017-09-28	Entity status set to undiscounted (initial default setting or status change)BIG.	BIG.
2017-09-28	Initial Exam Team nnIEXX	IEXX

26 legal events, as the office reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code
2023-08-02	Information on status: patent grantGrantedPATENTED CASESTCF	STCF
2023-06-26	Information on status: patent application and granting procedure in generalPUBLICATIONS -- ISSUE FEE PAYMENT VERIFIEDSTPP	STPP
2022-11-13	Information on status: patent application and granting procedure in generalRESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINERSTPP	STPP
2022-08-12	Information on status: patent application and granting procedure in generalNON FINAL ACTION MAILEDSTPP	STPP
2022-05-04	Information on status: application discontinuationFINAL REJECTION MAILEDSTCB	STCB
2022-05-04	Information on status: patent application and granting procedure in generalFINAL REJECTION MAILEDSTPP	STPP
2022-03-03	Information on status: patent application and granting procedure in generalRESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINERSTPP	STPP
2021-11-24	Information on status: patent application and granting procedure in generalNON FINAL ACTION MAILEDSTPP	STPP
2021-11-19	Information on status: patent application and granting procedure in generalRESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINERSTPP	STPP
2021-08-13	Information on status: application discontinuationFINAL REJECTION MAILEDSTCB	STCB
2021-08-13	Information on status: patent application and granting procedure in generalFINAL REJECTION MAILEDSTPP	STPP
2021-05-05	Information on status: patent application and granting procedure in generalNON FINAL ACTION MAILEDSTPP	STPP
2021-04-29	Information on status: patent application and granting procedure in generalDOCKETED NEW CASE - READY FOR EXAMINATIONSTPP	STPP
2021-01-25	Information on status: patent application and granting procedure in generalDOCKETED NEW CASE - READY FOR EXAMINATIONSTPP	STPP
2020-10-21	Information on status: application discontinuationFINAL REJECTION MAILEDSTCB	STCB
2020-10-21	Information on status: patent application and granting procedure in generalFINAL REJECTION MAILEDSTPP	STPP
2020-03-24	Information on status: patent application and granting procedure in generalDOCKETED NEW CASE - READY FOR EXAMINATIONSTPP	STPP
2019-12-18	Information on status: application discontinuationFINAL REJECTION MAILEDSTCB	STCB
2019-12-18	Information on status: patent application and granting procedure in generalFINAL REJECTION MAILEDSTPP	STPP
2019-10-09	Information on status: patent application and granting procedure in generalRESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINERSTPP	STPP
2019-07-08	Information on status: patent application and granting procedure in generalNON FINAL ACTION MAILEDSTPP	STPP
2019-06-13	Information on status: patent application and granting procedure in generalRESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINERSTPP	STPP
2019-04-30	Information on status: patent application and granting procedure in generalNON FINAL ACTION MAILEDSTPP	STPP
2017-11-14	Information on status: patent application and granting procedure in generalDOCKETED NEW CASE - READY FOR EXAMINATIONSTPP	STPP
2017-09-28	AssignmentAS	AS
2017-09-28	Fee payment procedureENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP

Method and apparatus for deriving transmit power of ul (uplink) rs (reference signal) in a wireless communication system

Claim Score by NHIP

Abstract

Term

FIELD

BACKGROUND

SUMMARY

BRIEF DESCRIPTION OF THE DRAWINGS

DETAILED DESCRIPTION

PUSCH

A

B

PUCCH

PUCCH

Priority claims10

Members13

Over time

Transactions

Over the term

Events

Numbers

Titles

Classification

Abstract

Term

CROSS-REFERENCE TO RELATED APPLICATIONS

FIELD

BACKGROUND

SUMMARY

BRIEF DESCRIPTION OF THE DRAWINGS

DETAILED DESCRIPTION

PUSCH

A

B

PUCCH

PUCCH

Priority claims10

Members13

Over time

Transactions

Over the term

Events

Numbers

Titles

Classification