| Anchor | ||||
|---|---|---|---|---|
|
...
(Eq. 35)Mathinline body $G=\frac{{{P}_{active}}}{{{N}_{0}}+{{P}_{other}}+{{I}_{ext}}}$
with the following definitions:
...
The fractional power levels found in the link level data are defined for each user (channel) as:
...
(Eq. 36)Mathinline body $\frac{{{E}_{c}}}{{{I}_{or}}}=\frac{{{P}_{traff\_active}}/W}{{{P}_{total\_active}}/W}=\frac{{{P}_{traff\_active}}}{{{P}_{total\_active}}}$
with the following definitions:
...
If user has only 1 BS in the active set (simplex), the power received from the BS is:
...
...
Mathinline body Ptraff=Ptotal_active x
...
(Eq. 37)Ec/Ior
If user has 2 BS’s in the active set (2-way soft handover), power received from one of the BS’s is then:
...
Mathinline body Ptraff=(
...
Ptotal_active x
...
Ec/
...
Ior)/
...
(Eq. 38)2
Note that symmetry between the two soft handover legs (links with BS’s in the active set) is assumed. Therefore, when a user is connected to two BS’s, it receives equal power from each link. The determination of the traffic channel power levels for each user cannot be done in a single step. The inherent assumption in equations 37 and 38 is that Ptotal_active is known. However, Ptotal_active itself is the sum of the pilot, overhead and all traffic channel power levels received from the BS’s in the active set. Therefore, an iterative process is required to determine the individual traffic channel received power levels.
...
Once the initialization is complete, geometry and soft handover state for each user can be calculated based on the initial values of the BS broadcast levels. Then the Ec/Ior requirement for each active user can be obtained from the link level data using its mobile speed assignment, calculated geometry and soft handover state. Equations 37 and 38 can then be used to get the received traffic channel power levels for each user. Path loss information can then be used to determine the corresponding transmit channel power levels. However, the calculated transmit traffic channel power levels should be checked against the maximum allowable traffic channel power and transmit/receive levels should be adjusted if necessary. As a result of such an adjustment, a user may not meet its Ec/Ior requirement. Based on a “call drop threshold”, such a user may be removed from the system if it meets the following criterion:
...
Mathinline body Achieved Ec/Ior < Ec/Ior requirement – Call drop threshold (dB)
...
(Eq. 39)
The call drop threshold is set such that dropping a call is limited to extreme circumstances (thresholds less than 2dB are not recommended) and kept mostly as a safety measure to avoid a single user hogging the BS resources. In an actual system, calls are not dropped at the instant they fail to meet their link quality target. The system will tolerate quality degradation up to certain durations and at the same time avoid a single user to sacrifice the overall system performance by consuming all the BS resources (max. traff. chan. pow. setting). In fact, for systems that employ sufficient control of maximum traffic channel power, call drops may be avoided completely within the power control loop. Eventually, users not meeting their Ec/Ior target will be evaluated when the success rate of the system is calculated.
Once the transmit traffic channel levels are calculated, the broadcast power of each BS should accordingly be updated. If the total broadcast power of a BS turns out to be greater than its maximum allowable level, all traffic channels served by that BS should be scaled down so that the maximum BS power constraint is met. The scaling factor that should be applied to the traffic channel power levels can easily be calculated as:
| Mathinline | ||
|---|---|---|
|
where:
- Pmax is the maximum allowable BS power
- Pcalculated is the actual calculated BS broadcast power (including pilot and overhead).
...