Altitude dependent uplink power control

Abstract

In SIB2 there is an entry containing information on PUSCH power control parameters. The current signaling entity is extended with entries that are dependent on UE operational altitude. For example, an altitude-dependent factor for the alpha parameter, or one parameter range for zero (ground level, default as per of today), one parameter range for intermediate altitude operation, and one entry for high-altitude operations, so that an airborne UE can select its appropriate power control parameters.

Claims

1. A method performed by a base station, BS, the method comprising: determining a UE's altitude; obtaining a power control parameter based on the determined altitude of the UE, the power control parameter being an alpha parameter and obtaining the alpha parameter comprising selecting an altitude based on the determined UE's altitude and identifying an alpha parameter that is associated with the selected altitude; and transmitting to the UE a message comprising the obtained power control parameter so that the UE can use the obtained power control parameter to calculate a power control value and then use the power control value to control an UL transmit power.

2. The method of claim 1, wherein the power control parameter is the alpha parameter; and obtaining the alpha parameter comprises calculating: (D×altFactor)+α.sub.def, where D is a difference between the UE's altitude and reference altitude (altRef) and α.sub.def is a default alpha parameter.

3. The method of claim 1, wherein selecting the altitude comprises selecting a relative altitude.

4. A base station, BS, the BS being configured to: determine a UE's altitude; obtain a power control parameter based on the determined altitude of the UE, the power control parameter being an alpha parameter and obtaining the alpha parameter comprising selecting an altitude based on the determined UE's altitude and identifying an alpha parameter that is associated with the selected altitude; and transmit to the UE a message comprising the obtained power control parameter so that the UE can use the obtained power control parameter to calculate a power control value and then use the power control value to control an UL transmit power.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) The accompanying drawings, which are incorporated herein and form part of the specification, illustrate various embodiments.

(2) FIG. 1 illustrates a radio network according to some embodiments.

(3) FIG. 2A is a flow chart illustrating a process according to one embodiment.

(4) FIG. 2B is a flow chart illustrating a process according to one embodiment.

(5) FIG. 3 is a flow chart illustrating a process according to one embodiment.

(6) FIG. 4 is a flow chart illustrating a process according to one embodiment.

(7) FIG. 5 is a flow chart illustrating a process according to one embodiment.

(8) FIG. 6 is a block diagram of a UE according to one embodiment.

(9) FIG. 7 is a diagram showing functional units of a UE according to one embodiment.

(10) FIG. 8 is a block diagram of a BS according to one embodiment.

(11) FIG. 9A is a diagram showing functional units of a BS according to one embodiment.

(12) FIG. 9B is a diagram showing functional units of a BS according to one embodiment.

DETAILED DESCRIPTION

(13) FIG. 1 illustrates a network 100 according to an exemplary embodiment. Network 100 includes the following network nodes: a UE 101, a first BS 105, which may be connected to (or located inside of) an unmanned aerial vehicle (UAV) 121, a second BS 107, which may be connected to (or located inside of) UAV 122, a first ground-based BS 108, and a second ground-based BS 110. As shown in FIG. 1, UE 101, BS 105 and BS 107 can each move in all three dimensions; thus, each of these nodes may have a time-varying altitude.

(14) FIG. 2A is a flow chart illustrating a process 200, according to some embodiments, that is performed by a base station, for example, BS 105. Process 200 may begin with step s202, in which BS 105 generates a message comprising a System Information Block (SIB) (e.g., SIB-2), wherein the SIB comprises information enabling a UE receiving the SIB to compute a power control function (e.g., P_PUSCH, which is also denoted P.sub.PUSCH) that takes into account the UE's altitude.

(15) For example, in a continuous alpha-compensation embodiment, the SIB comprises an altitude-dependent factor (altFactor) for use in modifying the alpha parameter, which may also be included in the SIB. In such an embodiment, the SIB may also comprise an altitude reference parameter (altRef). Also, in this embodiment the SIB may include an alpha compensation parameter (POalphaComp).

(16) In another embodiment, as an alternative to continuous alpha-compensation, the SIB includes a set of two or more alpha values, wherein each alpha value in the set is associated with a different altitude (e.g., a different relative altitude or “altitude region”). In such an embodiment, the SIB may also include a set of alpha compensation parameters, wherein each alpha compensation parameters included in the set is associated with a different altitude (e.g., low altitude, medium altitude, and high altitude). For example, the SIB may include the following information, as illustrated in table 2:

(17) TABLE-US-00005 TABLE 2 Alpha Compensation Altitude Alpha (α) Param (POalphaComp) Low 0.7 P1 Medium 0.6 P2 High 0.5 P3

(18) As the above illustrates, the SIB includes a set of three alpha values, wherein each one of the alpha values is associated with a different relative altitude. Likewise, the SIB includes a set of three alpha compensation parameters, wherein each one of the parameters is associated with one of the different altitudes. The SIB may also include information (e.g., a vector) that defines the different relative altitudes. For instance, the SIB may include i) information defining the “low” altitude as any altitude below X meters, ii) information defining the “medium” altitude as any altitude above or equal to X meters, but less than Y meters, and ii) information defining the “high” altitude as any altitude above Y meters. These altitude region settings can, for example, be cell specific and be selected based on building heights and ground level topology in the specific cell.

(19) In step s204, BS 105 transmits (e.g., broadcasts) the message.

(20) FIG. 2B is a flow chart illustrating a process 200, according to some embodiments, that is performed by a base station, for example, BS 105. Process 200 may begin with step s252, in which BS 105 determines UE 101's altitude. The altitude of UE 101 can be determined in several different ways. For example, the altitude of UE 101 can be determined by the BS from direction of arrival angle and timing advance. As another example, the BS can determine UE 101's altitude from an altitude report transmitted to the BS by, for example, UE 101, which can determine its own altitude using, for example, a barometric sensor, UAV flight equipment/recorder, or any other altitude measuring unit. For instance, the UE or other device may periodically (or via a trigger) send an altitude report to the BS indicating UE 101's altitude.

(21) In step s254, the BS obtains a power control parameter (e.g., the alpha parameter) based on the determined altitude of the UE. For example, the BS may obtain the alpha parameter by selecting an altitude (e.g., selecting a relative altitude) based on the UE's altitude determined in step s252 and then identifying the alpha parameter that is associated with the selected altitude. As another example, the BS may obtain the alpha parameter (α) by calculating: (D×altFactor)+α.sub.def, where D is a difference between the UE's altitude (e.g., a filtered version of the UE's altitude) and reference altitude (altRef) and α.sub.def is a default alpha parameter.

(22) In step s256, the BS transmits to UE 101 a message (e.g., an RRC message) containing the obtained power control parameter so that UE 101 can use the obtained power control parameter to calculate a power control value and then use the power control value to control an UL transmit power.

(23) FIG. 3 is a flow chart illustrating a power control process 300, according to a generic embodiment, that is performed by UE 101. Process 300 may begin with step s302, in which UE 101 determines its current altitude (e.g., 50 meters). In step s304, UE 101 calculates a power control value (e.g., P_PUSCH) using the determined altitude. For example, in step s304, UE 101 may determine UEalt, which is a filtered version of the altitude determined in step s302, and then use UEalt to calculate the power control value. For example, in step s304, UE 101 may calculate a value equal to (altRef−UEalt) and then use the calculated value to calculate the power control value. As another example, UE 101 may use UEalt to select an alpha value from a set of alpha values and then use the selected alpha value to calculate the power control value. In step s306, UE 101 controls a transmit power based on the calculated power control value.

(24) FIG. 4 is a flow chart illustrating a power control process 400, according to some embodiments, that is performed by UE 101. Process 400 may begin with step s402, in which UE 101 receives a SIB (e.g., SIB-2) transmitted by a BS (e.g., BS 105). In this embodiment, the SIB includes the altitude-dependent factor (altFactor) and the altitude reference parameter (altRef).

(25) In step s404, UE 101 determines whether it can obtain altitude information indicating its altitude (e.g., a value identifying UE 101's height above sea level or ground level). If it can obtain the altitude information, UE 101 obtains the information and determines a filtered altitude value (UEalt) based on the altitude information (step s406). If it cannot obtain the altitude information, the process proceeds to step s410.

(26) In step s408, UE 101 calculates a power control value (e.g., P_PUSCH) using UEalt, altRef, and altFactor. For example, in step s408 UE 101 calculates:
P.sub.PUSCH(i)=Min{P.sub.CMAX,(10 log.sub.10(M.sub.PUSCH(i))+P.sub.O_PUSCH(j)+α.sub.adj(j)×PL+Δ.sub.TF(I)+f(i))},
where
α.sub.adj(j)=α(j)+altFactor×D.sub.alt, where
D.sub.alt is a difference between altRef and UEalt (e.g., D.sub.alt=(altRef−UEalt), or D.sub.alt=(UEalt−altRef)).

(27) In step s410, UE 101 obtains default power control parameters from the SIB and then in step s412 calculates the power control value using the default values.

(28) In some embodiments, the P.sub.O_PUSCH setting should furthermore be adjusted according to alpha change as described in reference [2], as:
P.sub.O_PUSCH=α.Math.(SINR.sub.0+IN)+(1−α).Math.(P.sub.max−10 log M.sub.0)  (2)
where SINR0 is the SINR achieved when P=Pmax for M=M0.
P.sub.O_PUSCH=α.Math.(SINR.sub.0+IN)+(1−α).Math.(P.sub.max−10 log M.sub.0)  (3)
SIB2 configuration parameter for PO adjustment can be reduced as:
P.sub.O_PUSCH_ADJ=α.Math.(SINR.sub.0+IN−P.sub.max+10 log M.sub.0)+P.sub.max−10 log M.sub.0=α.Math.POalphaComp+P.sub.O_PUSCH   (4)

(29) And SIB2 parameter POalphaComp can be configured accordingly and the UE adjusts P.sub.O_PUSCH based on altitude adjusted alpha according to (4).

(30) A complete altitude compensating UE PUSCH power control can be specified as:
P.sub.PUSCH(i)=min{P.sub.CMAX,10 log.sub.10(M.sub.PUSCH(i))+P.sub.O_PUSCH_ADJ(j)+α.sub.adj(j)×PL+Δ.sub.TF(I)+f(i))},
where
P.sub.O_PUSCH_ADJ(j)=α.Math.POalphaComp+P.sub.O_PUSCH

(31) The total alpha factor can be limited to the range 0.5 to 1 ranging from free-space optimal value to UE at low altitude isolated from neighbor cells not causing any significant interference. The corresponding max and min values can also be SIB2 parameters.

(32) FIG. 5 is a flow chart illustrating a power control process 500, according to some embodiments, that is performed by UE 101. Process 500 may begin with step s502, in which UE 101 receives a SIB (e.g., SIB-2) transmitted by a BS (e.g., BS 105).

(33) In step s504, UE 101 determines whether it can obtain altitude information indicating its altitude (e.g., a value identifying UE 101's height above sea level or ground level). If it can obtain the altitude information, UE 101 obtains the information and determines a filtered altitude value (UEalt) based on the altitude information (step s506). If it cannot obtain the altitude information, the process proceeds to step s507.

(34) In step s507, UE 101 selects default power control parameter values. For example, if UE 101 is in, on or part of a UAV, but the UE 101 cannot obtain its altitude information, then UE 101 may be configured to select a conservative setting (e.g., the parameters associated with the “high” altitude). As another example, a non-UAV UE 101 (i.e., a that generally stays on the ground) may be configured to select a less conservative setting (e.g., the parameters associated with the “low” altitude).

(35) In step s508, which follows step s506, UE 101 selects an altitude (e.g., a relative altitude such as Low, Medium or High) based on UEalt. For example, in step s508, UE 101 uses UEalt and altitude information to select an altitude corresponding to UEalt. This altitude information may be included in the SIB. For example, the altitude information may be a vector of N altitude values, wherein each altitude value defines an altitude region boundary. Here is an example of such a vector: {25 m, 250 m}. This vector defines three relative altitudes, which may be labeled as “low”, “medium,” and “high.” Specifically, the vector specifies that: 1) any altitude less than 25 m is a “low” altitude; 2) any altitude greater than or equal to 25 but less than 250 is a “medium” altitude, and 3) any altitude greater than or equal to 250 is a “high” altitude.

(36) In step s510, UE 101 selects power control parameter values (e.g., an alpha value and an alpha compensation parameter) based on the altitude selected in step s508. For instance, using table 2 (above) as an example, if the selected altitude is the “medium” altitude, then, in step s510, UE 101 selects an alpha value of 0.6 and the P2 alpha compensation parameter.

(37) In step s512, UE 101 uses the power control parameters selected in either step s507 or step s510 to calculate a power control value (e.g., P.sub.PUSCH). For instance, using the example above where step S510 is performed and the selected altitude is the “medium” altitude, UE 101 may calculate:
P.sub.PUSCH(i)=min{P.sub.CMAX,10 log.sub.10(M.sub.PUSCH(i))+P.sub.O_PUSCH_ADJ(j)+α.sub.adj(j)×PL+Δ.sub.TF(I)+f(i))}, where
α.sub.adj(j)=0.6, and
P.sub.O_PUSCH_ADJ(j)==α.Math.P2+P.sub.O_PUSCH.

(38) While the above examples have illustrated three relative altitudes (or altitude regions), N number of relative altitudes may be defined, N>3. If N relative altitudes are defined, then the SIB may contain N alpha value and N alpha compensation parameters, one for each of the N relative altitudes.

(39) In some embodiments, the flight altitude regions and correspondingly associated values of alpha could be shared with neighboring eNBs, potentially over the X2 interface.

(40) Also, in some embodiments, the altitude and flight altitude selection could furthermore be filtered with respect to UAV's current vehicle speed over ground and rate of climb/decent (i.e. vertical velocity component), and vehicle's current flight altitude.

(41) In some embodiments, the altitude of UE 101 can be estimated by a BS (e.g., the BS serving UE 101) from direction of arrival angle and timing advance. The altitude can be signaled to the UE or a UE specific alpha setting according the altitude can be configured by RRC-signaling.

(42) FIG. 6 is a block diagram of UE 101 according to some embodiments. As shown in FIG. 6, UE may comprise: processing circuitry (PC) 602, which may include one or more processors (P) 655 (e.g., a general purpose microprocessor and/or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like); circuitry 603 (e.g., radio transceiver circuitry comprising an Rx 605 and a Tx 606) coupled to an antenna system 604 for wireless communication with other UEs and/or base stations, such as 3GPP base stations or other base stations); and local storage unit (a.k.a., “data storage system”) 608, which may include one or more non-volatile storage devices and/or one or more volatile storage devices (e.g., random access memory (RAM)). In embodiments where DPA 602 includes a programmable processor, a computer program product (CPP) 641 may be provided. CPP 641 includes a computer readable medium (CRM) 642 storing a computer program (CP) 643 comprising computer readable instructions (CRI) 644. CRM 642 may be a non-transitory computer readable medium, such as, but not limited, to magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory, flash memory), and the like. In some embodiments, the CRI 644 of computer program 643 is configured such that when executed by data processing apparatus 602, the CRI causes UE to perform steps described herein (e.g., steps described herein with reference to the flow charts and/or message flow diagrams). In other embodiments, UE may be configured to perform steps described herein without the need for code. That is, for example, DPA 602 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and/or software.

(43) FIG. 7 is a diagram showing functional units of UE 101 according to some embodiments. As shown in FIG. 7, the UE 101 may include: a determining unit 702 configured to determine its altitude and a calculating unit 704 configured to calculate a power control value (e.g., P.sub.PUSCH) using the determined altitude.

(44) FIG. 8 is a block diagram of base station (BS) 105 according to some embodiments. As shown in FIG. 8, BS may comprise: processing circuitry (PC) 802, which may include one or more processors (P) 855 (e.g., a general purpose microprocessor and/or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like); a network interface 848 comprising a transmitter (Tx) 845 and a receiver (Rx) 847 for enabling the BS to transmit data to and receive data from other nodes connected to a network 110 (e.g., an Internet Protocol (IP) network) to which network interface 848 is connected; circuitry 803 (e.g., radio transceiver circuitry comprising an Rx 805 and a Tx 806) coupled to an antenna system 804 for wireless communication with BSs); and local storage unit (a.k.a., “data storage system”) 808, which may include one or more non-volatile storage devices and/or one or more volatile storage devices (e.g., random access memory (RAM)). In embodiments where DPA 802 includes a programmable processor, a computer program product (CPP) 841 may be provided. CPP 841 includes a computer readable medium (CRM) 842 storing a computer program (CP) 843 comprising computer readable instructions (CRI) 844. CRM 842 may be a non-transitory computer readable medium, such as, but not limited, to magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory, flash memory), and the like. In some embodiments, the CRI 844 of computer program 843 is configured such that when executed by data processing apparatus 802, the CRI causes BS to perform steps described herein (e.g., steps described herein with reference to the flow charts and/or message flow diagrams). In other embodiments, BS may be configured to perform steps described herein without the need for code. That is, for example, DPA 802 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and/or software.

(45) FIG. 9A is a diagram showing functional units of BS 105 according to some embodiments. As shown in FIG. 9A, the BS 105 includes a generating unit 902 for generating a message comprising a SIB, wherein the SIB may include a set of alpha values where each one of the alpha values is associated with a different altitude or the SIB may include an altitude factor and an altitude reference. BS 105 also includes a transmitting unit 904 for employing a transmitter (e.g., transmitter 806) to transmit the generated message.

(46) FIG. 9B is a diagram showing functional units of BS 105 according to some embodiments. As shown in FIG. 9B, the BS 105 includes: an altitude determining unit 952 for determining UE 101's altitude; a power control parameter obtaining unit 954 for obtaining a power control parameter based on the determined altitude of UE 101; and a transmitting unit 956 for employing a transmitter (e.g., transmitter 806) to transmit to UE 101 a message (e.g., an RRC message) comprising the obtained power control parameter so that the UE 101 can use the obtained power control parameter to calculate a power control value and then use the power control value to control an UL transmit power.

(47) While various embodiments of the present disclosure are described herein, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the disclosure unless otherwise indicated herein or otherwise clearly contradicted by context.

(48) Additionally, while the processes described above and illustrated in the drawings are shown as a sequence of steps, this was done solely for the sake of illustration. Accordingly, it is contemplated that some steps may be added, some steps may be omitted, the order of the steps may be re-arranged, and some steps may be performed in parallel.

REFERENCES

(49) [1] Uplink Power Control in LTE—Overview and Performance Principles and Benefits of Utilizing rather than Compensating for SINR Variations, A. Simonsson et al., conference paper [2] Ericsson 3GPP TSG-RAN WG1 #51 R1-074850, “Uplink Power Control for E-UTRA-Range and Representation of P0”, located at www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_51/Docs/R1-074850.zip

ABBREVIATIONS

(50) 3GPP 3rd Generation Partnership Project'

(51) ANR Automatic Neighbor Relation

(52) eNB Evolved Node B

(53) HO Handover

(54) LoS Line of Sight

(55) LTE Long Term Evolution

(56) NRT Neighbor Relation Table

(57) PL Path Loss

(58) PUSCH Physical Uplink Shared Channel

(59) RRC Radio Resource Control

(60) RRM Radio Resource Management

(61) SIB System Information Block

(62) TS Technical Specification

(63) UAV Unmanned Aerial Vehicle

(64) UE User Equipment

(65) X2 eNB-eNB interface for LTE