You are on page 1of 65

Course Content

Radio Resource Management Overview


Parameter Configuration
Common Channels & Power Control
Load Control
Admission Control
Packet Scheduling
Handover Control
Resource Manager

1 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Course Objectives
At the end of the course you will be able to:
Describe the admission criteria for uplink and downlink
Describe the decision procedure of the admission control for RT and NRT RABs
Describe the role of the packet scheduler in the admission control
Name the main parameters admission control derives from the RAB parameter
set
Name and describe the main parameters admission control delivers to other
RRM entities

2 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Admission Control
AC Functional Overview
UL admission control
Power allocation in UL
DL admission control
Power allocation in DL
Dynamic Link Optimisation (DyLo)

3 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Admission Control Functional Overview
RNC
Maximises capacity whilst maintaining stability
LC
Decides if new RAB request is admitted into RAN PS
RM
AC decision procedure set according to whether; AC
Request is for RRC connection and RT or NRT RAB Setup
RAB setup can be for call setup or handover Network based functions
Admission control for RAB setup is different for RT and NRT
For RT RAB admission requests AC;
estimates the non-controllable power (load) increase that would result from admitting the new RAB
checks if the new non-controllable load is below a certain threshold

Bearer is not admitted if the predicted load exceeds defined thresholds in UL or DL


AC is also responsible for determining quality requirements of the RB including;
setting RLC and TrCH parameters
BLER & Eb/No targets
initial SIR target (used in Outer Loop PC) & upper and lower limits for the uplink SIR target

4 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Admission Control Functional Overview
RRC Connection
Establishment
0

NRT Admission
Decision Process (PS)
6 RAB
Establishment
Core
UL/DL Load Change Nokia RAB ASSIGNMENT REQUEST
Report to LC NRT PS RNC Network
5 call
RAB AC
admitted
RT CS call Radio Access Bearer
Admission Service Request
Decision 1
4 Quality Requirements
Power Increase of Radio Bearer
Estimates 2 RAB attributes (HLR);
RAB
request 3 SDU error ratio
denied traffic class
RB attributes (RNC); max bit rate
target BLER
target Eb/No
initial SIRtarget
Queue
RAB

5 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Radio Access Bearer Service Request
RAB service attribute RAB service attribute value
Traffic Class Conversational UE RNC MSC HLR
Maximum bit rate 12.2 / 10.2 / 7.95 / 7.4 / 6.7 / 5.9 / 5.15 / 4.75 kbit/s
Guaranteed bit rate 12.2 / 10.2 / 7.95 / 7.4 / 6.7 / 5.9 / 5.15 / 4.75 kbit/s
Setup
Delivery Order Yes Call Proceeding
Maximum SDU size 244 / 204 / 159 / 148 / 134 / 118 / 103 /95 bits
RAB Assignment Request
Traffic Handling Priority Not applicable
Source statistics descriptor Speech
SDU Parameters RAB sub-flow 1 RAB sub-flow 2 RAB sub-flow 3 RAB Assignment Response
(Class A bits) (Class B bits) (Class C bits)
- SDU error ratio 7 * 10-3 - -
>- Residual bit error ratio 10-6 7) 10-3 5 * 10-3 Alerting
> Delivery of erroneous SDUs yes - -
SDU format information 1-9 Connect
Sub flow SDU size 1-9
Sub flow SDU size parameters 10
Connect Acknowledge
Sub flow SDU size 10 0 0 0

AC maps RAB parameters into RB parameters using UE capability parameters and outputs:
BLER & Eb/No targets
Initial SIR target (with max/min values)
RLC , TrCH parameters
PDCP and physical channel parameters

6 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Mapping Residual BLER : Target BLER : Eb/Nos
AC uses calculated Residual BLER to obtain the target BLERs via look-up tables
Eb/Nos are obtained from another look-up table using target BLER values
Target BLER and Eb/Nos are obtained for UL and DL separately.
Both dedicated and signalling channels have there own targets
EbNo
EbNo Target Eb/Nos are used
Mapping
Mapping in calculating SIR
targets, power/load
increase estimates, DL
power allocations
RAB BLER
RABQoSQoS Calculated
Attributes
Attributes

Initial Pwr Initial SIR


Max Pwr Max SIR
Min Pwr Min SIR

EbNoSetIdentifier specifies
which Eb/No table is used
depending on the type of
antenna configuration used
7 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Initial SIR target
BTS measures the SIR from the pilot bits of the DPCCH. So radio link specific initial SIR
target depends on following elements:
DCH specific planned Eb/No.
DCH coding rate after the error correction coding and the static rate matching.
In UL there is one encoded bit in symbol.
The relative power difference between DPCCH and DPDCH.

The initial UL SIR target of the DPDCH is achieved from the equation:

E
RM DCH N DCH
RDCH DCH RL
C
TFC Max

2

UL , DPCCH
SIR Init = b + 10 log c
SFDPCCH

C TFC Max
N 0 DCH W RM DCH N DCH d

8 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Initial SIR target
The maximum and minimum limits for SIR target are calculated from this initial value;

SIR UL , DPCCH
min = ( )
Eb min
N 0 DCH ( )
Eb
N 0 DCH + SIR UL , DPCCH
Init

SIR UL , DPCCH
max = ( )
Eb max
N 0 DCH ( )
Eb
N 0 DCH + SIR UL , DPCCH
Init

9 NOKIA 1999 31/10/2002 RANPAR Version 1.0


TrCH Parameters
AC produces the TrCH parameters:
Transport Formats (TF)
Transport Format Combination (TFC)
TFC identifiers

384 384 TrCh 1 TrCh 2


128 TFI2
128 128
64 TFI1 64 TFI1
64
0 TFI0 0 TFI0 64 TFI1
0
TFI0 0 TFI0
00

Supported Peak Bitrate Sheduled TFS for RT RB TFS subset TFCS (SL & RT RB)
Bitrates In Bearer Bitrate intermediate For TFCS
Parameters Bitrates construction

10 NOKIA 1999 31/10/2002 RANPAR Version 1.0


RLC Transfer Mode
AC determines the UL & DL RLC transfer mode for RNC & UE
RLC transfer mode indicates, whether the RLC entity of a RB shall use an Acknowledged
(AM), an Unacknowledged (UM) or a Transparent (Tr) Mode data transfer.
Equal transfer mode is used in UL and DL for a RB.
The transfer mode is determined from the RAB parameters and CN domain information.

CS domain PS domain

Conversational Streaming Interactive Background

TM
TM UM
UM TM
TM UM
UM AM
AM AM
AM AM
AM
RLC
RLC RLC
RLC RLC
RLC RLC
RLC RLC
RLC RLC
RLC RLC
RLC

DCH
DCH DCH
DCH DCH DCH DCH
DCH DCH DCH RACH/FACH DCH/HS-
DCH/HS--DSCH
RACH/FACH DCH/HS
DCH/HS- DSCH DCH/DCH
DCH/DCH
RT traffic NRT traffic

11 NOKIA 1999 31/10/2002 RANPAR Version 1.0


AC for NRT RAB
For a NRT RAB admission request, AC will first check that the maximum bit rates
requested in the RAB Assignment Request message are lower or equal than
operator configurable limits for the specific target cell
If there is too much RACH signalling then there will be significant transmission
delays and collision probability resulting in lower throughputs in the RACH.
Furthermore, the uplink interference caused by the RACH transmissions can
become very significant.
Since after a NRT admission request is granted by AC, PS can decide to setup the
NRT RAB on common channels, if the RACH load is deemed excessive the AC
will block any NRT request before it reaches PS.
The instantaneous RACH load (%) in the associated Physical RACH is defined as

Avg _ Number _ RACH _ preambles _ per _ RACH _ frame


RACH _ load = 100%
Available _ Access _ Slots _ per _ RACH _ frame Allowed _ preamble _ signatures

12 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Admission decision for NRT RABs
NRT RABs do not cause an increase of the non-controllable load: their bit rate can be
reduced up to 0 if necessary
However, when capacity requests are transmitted, common channel signalling is
required, and RACH overload could occur
RACH load is taken into account in NRT RAB admission decision
RACH load is reported by the BTS in Radio Resource Indication messages in average
number of RACH received per radio frame
This number of received RACH messages is normalised to the product :
Number of access slots x Number of preamble signature allowed on
PRACH
AC produces the TFS for NRT RBs based on RAB requirements

MaxBitRateDLPSNRT and MaxBitRateULPSNRT define the maximum allowed bit


rates in a cell
range: [8, 16, 32, 64, 128, 256, 320, 384] kbps,
default: 384 kbps

13 NOKIA 1999 31/10/2002 RANPAR Version 1.0


RACH load for NRT RABs admission
If all RACH load measurement results received during the period WinRachOverloadBS exceed
RachOverloadBS, the cell is considered in RACH overload and no NRT RAB is admitted.
If all RACH load measurement results received during the period WinRachNormalLoadBS are
below RachNormalLoadBS, the cell is considered in normal RACH load and all NRT RABs are
admitted again.
RachOverloadBS: Threshold for RACH overload
range: [0...100]%; step: 1%;
default 100%
RachNormalLoadBS: Threshold for RACH normal load
range: [0...100]%; step: 1%;
default 100%
WinRachOverloadBS: Window for comparison of measurements and threshold in RACH overload
range: [0100] RACH load indication periods; step: 1;
default 1
WinRachNormalLoadBS: Window for comparison of measurements and threshold in RACH
normal load
range: [0100] RACH load indication periods; step: 1;
default 5
14 NOKIA 1999 31/10/2002 RANPAR Version 1.0
RACH load for NRT RABs admission
RACHLoadIndicationPeriod: defines the reporting period of the PRACHs in a BTS. The BTS may
report load figures to the RNC in every Nth (N=1-20) NBAP Radio Resource Indication
message.
range: [020] RRI periods; step: 1; default: 1 (reporting every RRI period)

RACH load WinRachOverloadBS

No NRT RAB admission


RachOverloadBS

RachNormalLoadBS

Example values
WinRACHOverloadBS = 3 NRT RAB
WinRACHNormalLoadBS = 3
WinRachNormalLoadBS admission

1 x RACH load ind. period RachLoadIndicationPeriod


15 NOKIA 1999 31/10/2002 RANPAR Version 1.0
AMR RAB
The number of available AMR modes in each cell can be reduced to a
subset
AMRModeDL and AMRModeUL,

range: [4.75; 5.15; 5.9; 6.7; 7.4; 7.95; 10.2; 12.2] kbps;
default: 12.2 kbps (DL); 12.2 kbps (UL)
In RAN1.5 only 12.2 kbps is implemented
In RAN04 also other bitrates will be implemented

16 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Resources
If admission of an emergency call, RT call or pre-emption is unsuccessful due congested logical
(codes, transmission) or hardware (WTR) resources, several attempts are tried
RNCcongNumberofReAttempts defines the maximum number of re-attempts
range: [010]; step: 1; default 2

Meanwhile, WBTS is set in 'frozen' state.

BTSfrozenMaxTimer defines the maximum time the WBTS can remain frozen
range: [0 10]s; step: 0.1s; default 3s

If the RRC connection cannot be established, the UE is set a wait time before sending a new
RRC Connection Request

WaitTimeRRC defines this timer, and is set differently for each RRC connection setup cause
(conversational call, streaming call, interactive call, background call, emergency call, high
priority signalling, inter-RAT re-selection, registration, subscribed, unknown, other)
range: [0 15]s; step 1; default value for each type e.g.: WaitTimeRRCconversational = 3 s

17 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Mesurement Averaging Window for AC

BTS Measurements

RRI Period
WinACRABsetupDL/UL

1 m
Prx_total = Pr x _Totaln+ j
m j=1

18 NOKIA 1999 31/10/2002 RANPAR Version 1.0


DL/UL Mesurement Averaging Window for AC
WinACRABsetupDL/UL
This parameter determines the DL/UL load measurement averaging window size in
number of NBAP: Radio Resource Indication message periods. This window is used
in averaging the total transmission power measurement results of a cell that are
received from the BTS in the NBAP: Radio Resource Indication messages. Sliding
type of window is used: the oldest measurement result is removed when a new one
is received from BTS.

range: 1...20, step 1


default: 5

19 NOKIA 1999 31/10/2002 RANPAR Version 1.0


AC RAB Queuing Time
ACRABQueueTime

The parameter determines the period of time that a RAB establishment request can wait for
the admission decisionI

If the RAB has not been admitted during the allowed queuing time, the RAB establishment
request is rejected

Especially if the value of the parameter is less than the NBAP: RRIndPeriod , the request
has to be removed immediately from the queue provided that it cannot be admitted in the
first estimation

range: 0 ... 2000 ms, step 100 ms


default: 100ms

note that the default value is smaller than RRIndPeriod which means that the RAB must be removed before new
load information has been sent from the BTS to RNC -> basically no queuing -> parameter value should be
reconsidered when loading increases to reduce RAB setup failure rate

20 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Admission Control
AC Functional Overview
UL admission control
Power allocation in UL
DL admission control
Power allocation in DL
Dynamic Link Optimisation (DyLo)

21 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Load Based Admission Decision Process
To maintain stability, UL and DL loads at each cell must be maintained below defined
thresholds.
Admission decision takes into account 3 main issues;
The measured power quantities (current load status of the cell)
Average total wideband UL received power P rx _ total
Average total DL transmit powerP tx _ total
Non-controllable UL power Prx_NC = P rx _ total - Prx_NRT
Non-controllable DL power Ptx_NC = P tx _ total - Ptx_NRT

Where the Prx_NRT and Ptx_NRT are the sums of the initial powers allocated to NRT DCH users by
the PS and reported to LC every SchedulingPeriod

For RAN1.5 there is no guaranteed minimum bit rate for NRT DCHs (i.e. 0 kbps) thus all NRT DCH
power is classed as controllable power

Non-controllable power increase estimation associated with new admissions


Comparison against admission criteria thresholds

22 NOKIA 1999 31/10/2002 RANPAR Version 1.0


UL Cell Load Admission Decision Process
Admission decision is based on cell specific thresholds given by RNP
In UL the total received wideband interference power measured from the wideband
channel indicates the traffic load of the radio resources
Fundamental criterion;

power

Prx_nc + Prx_nc Prx_target max planned power

or
? max planned load

P rx _ total Prx _ t arget _ BS


load

23 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Calculation of UL Prx_nc
The total received wideband interference power can be expressed as the sum of:
the power caused by non-controllable traffic, Prx_nc,
the power caused by controllable traffic of non-real-time users, Prx_nrt

Prx _ total = Prx _ nc + Prx _ nrt


The non-controllable interference power, Prx_nc, consists of the powers of real-time
users, other-cell users, and noise
UL traffic load caused by the NRT RABs for which the Packet Scheduler (or Load
Control) can freely adjust the UL power (i.e., the UL transmission bit rate) according to
the current load, even drop it to zero when necessary (the best effort type of services)
Hence;

Prx _ nc = Prx _ total Prx _ nrt determined by PS


and delivered to AC
Measured by Node B through LC
and sent to RNC

24 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Estimation of UL Prx_nc
P rx_nc + P rx_nc P rx_target Prx_nc

or
P rx _ total Prx _ t arg et _ BS

AC estimates the increase in the total non-


controllable UL power of a cell using a Prx_nc
proprietary estimation algorithm
Estimation of the load increase, L, for that
RAB is made based on bit rate, Eb/Nos etc.
L is mapped to an estimated value of L
Prx_nc using a load vs power curve.
Change in load factor L is calculated by AC
based on the new bearer Eb/No requirement.
The corresponding estimated new received L Load factor
Non-Controllable power is calculated by AC Current load L and
using integral method and using the Load vs. current received Non-
Prx_nc curves maintained by AC for every cell Controllable power
Prx_nc are measured
25 NOKIA 1999 31/10/2002 RANPAR Version 1.0
UL Cell Load Admission Criteria Thresholds
The estimated non-controllable UL interference power and the average measured
total UL interference P rx _ total are compared against their thresholds ->
If either or both are satisfied then the RAB can not be admitted

Prx_nc + Prx_nc Prx_target Prx_target =


PrxNoise + PrxTarget
or
P rx _ total Prx _ t arg et _ BS Prx_target_BS =
PrxNoise + PrxTarget + PrxOffset

If there is queuing time left for the RAB (parameter AcRabQueueTime) then the RAB
remains in the queue to wait for the next RADIO RESOURCE INDICATION message,
otherwise it is removed from the queue

26 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Impact of Inaccurate Parameter Setting
NR = PrxNoise / Prxtotal
(Interference floor increase) PrxNoise set
too high

PrxNoise set too high


Calc.
Interf.
floor Actual
PrxTarget increase interf.floor
increase
PrxTotal

PrxNoise

Actual
Noise Floor
Uplink Load
used in AC

AC likely to admit more capacity requests than it should


(higher actual interference floor increase than calculated)
27 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Impact of Inaccurate Parameter Setting
In case the PrxTarget value is set too high (higher than used in dimensioning) then:
the AC will admit new users beyond the planned UL load limit
cell breathing will cause coverage holes
RAB establishment will fail due to not enough power from UE

Load < PrxTarget


RAB for new
user admitted

28 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Impact of Inaccurate Parameter Setting
NR = PrxNoise / Prxtotal
(Interference floor increase) PrxNoise set
too low

PrxNoise set too low

Actual Calc.
interf.floor Interf.
increase floor
increase
PrxTotal
Actual
Noise Floor

PrxNoise
Uplink Load
used in AC
AC likely to deny more capacity requests than it should
(lower actual interference floor increase than calculated)
29 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Impact of Inaccurate Parameter Setting
In case the PrxTarget value is set too low:
UL load threshold exceeded too early.
Admission Control will reject RT RAB establishments even though there is enough
coverage in UL

Load >= PrxTarget

RAB for new


user denided

30 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Parameters
Prx_Target_BS is defined to allow instantaneously the target received power level to
be exceeded due to changes in interference and propagation conditions when UEs are
moving in the network
When the non-controllable part of the cell load exceeds the target limit, AC will
reject those RAB establishment requests that would mean immediate UL load
increase (i.e. RT services)

When the PrxTarget level has


been exceeded it is still
PrxNoise [dBm] + PrxTarget [dB] + PrxOffset [dB] possible for the AC/PS to admit
PrxTotal NRT services and (AC) and
[dBm] schedule (allocate) bitrate for
Prx_NC NRT services
[dBm]
PrxNoise [dBm] + PrxTarget [dB] however bitrate (load) increase
for NRT is not possible

Note:
PrxTarget_BS is defined as PrxTarget + PrxOffset
PtxTarget_BS is defined as PtxTarget + Ptx Offset
31 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Admission Decisions

Prx_Target_BS

Prx_Target

Prx_NC Prx_NC

PrxTotal PrxTotal
Prx_NC Prx_NC

Case I Case II
Prx_NC + Prx_NC Prx_Target Prx_NC + Prx_NC Prx_Target
PrxTotal Prx_Target_BS Prx_Target PrxTotal Prx_Target_BS

RT RAB admitted (as well as NRT) RT RAB admitted

32 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Admission Decisions
Prx_Target_BS

Prx_NC
Prx_Target

Prx_NC
PrxTotal
PrxTotal
Prx_NC
Prx_NC

Case III Case IV


Prx_NC + Prx_NC Prx_Target Prx_NC + Prx_NC Prx_Target
PrxTotal Prx_Target_BS
Prx_target PrxTotal Prx_Target_BS

RT RAB denied (as well as NRT) RT RAB denied (NRT RAB permitted)

33 NOKIA 1999 31/10/2002 RANPAR Version 1.0


UL Admission Procedure Summary
BTS sends periodically the received UL power to the RNC

RNC compares the measured received power levels against the set PrxTotal
[dBm]
thresholds
Noise Rise OVER
NR [dB] LOAD PrxTarget [dB]+
AREA PrxOffset [dB]
If measured UL (PrxTotal) load exceeds overload thresholds
(PrxTarget+PrxOffset) no RABs can be admitted and NRT bitrates are MARGINAL
Over LOAD
Load reduced until PrxTotal reaches again PrxTarget AREA PrxTarget [dB]
FEASIBLE
LOAD XX [dB]
AREA
If measured UL (PrxTotal) load exceeds target thresholds (PrxTarget) AC
can admit NRT RABs to the cell. The NRT RAB bitrate can not be Load curve in UL
PrxNoise [dBm]
Marginal increased and remains at the same level as after previous scheduling
Load period 0 Fractional load 1
[0..1]

In feasible load area the admission decision is based on the power rise
Feasible estimate of the new RT bearer
Load
P rx_nc + P rx_nc P rx_target
In case the RAB can not be admitted it is put
If the resulting power is still below PrxTraget the RAB is admitted into the queue

34 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Admission Control
AC Functional Overview
UL admission control
Power allocation in UL
DL admission control
Power allocation in DL
Dynamic Link Optimisation (DyLo)

35 NOKIA 1999 31/10/2002 RANPAR Version 1.0


DPCCH Initial Power
After PRACH procedure the initial UL DPCCH transmit power is set by RRC
When one or more radio links already exist then the current UL transmission power
is used as initial transmission power for new radio link to be established
When establishing the first DPCCH the UE starts the UL inner loop power control at
a power level according to:

DPCCH_Initial_power = DPCCH_Power_offset CPICH_RSCP

The value for the CPICH_RSCP, is measured by the UE


DPCCH_Power_offset is determined by AC/PS of RNC and its value is signaled to
the UE in the UL DPCH power control info IE included in the RRC CONNECTION
SETUP message

36 NOKIA 1999 31/10/2002 RANPAR Version 1.0


DPCCH Power Offset
The value of the DPCCH_Power_offset is determined by the equation

DPCCH_POWER_OFFSET = Tx CPICH + Rx RSSI + SIR DPCCH 10 log( SFDPCCH )

Where:
TxCPICH is the transmission power of Primary CPICH given by the RNP parameter PtxPrimaryCPICH
RxRSSI is the received wide band interference power measured by BTS and offered by LC
SIRDPCCH is the required received SIR for DPCCH; it equals to the initial DPCCH SIR target
SFDPCCH is the spreading factor of the UL DPCCH

37 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Max UE Transmission Power
UEtxPowerMaxDPCH
This parameter defines the maximum transmission power level a UE can use on
DPCH. It is signaled to UE in the Maximum allowed UL TX power IE of a proper
RRC message, when a radio link is set up.
range: -50 ... 33 dBm, step 1 dB
default: 24dBm
UEtxPowerMaxRACH
This parameter defines the maximum transmission power level a UE can use on
PRACH. The value of the parameter also effects the cell selection and
reselection procedures. The value of the parameter is sent to UE in the Cell
selection and re-selection of System Information Blocks 3 and 4 of the serving
cell.
range: -50 ... 33 dBm, step 1 dB
default: 21dBm

38 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Admission Control
AC Functional Overview
UL admission control
Power allocation in UL
DL admission control
Power allocation in DL
Dynamic Link Optimisation (DyLo)

39 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Estimation of DL Ptx_nc
Admission decision based on cell specific thresholds given by RNP (same as UL)
Each BTS measures the total transmitted DL power (PtxTotal) of each cell, and reports the
results to the RNC by using RADIO RESOURCE INDICATION message
BTS applies same process as UL for calculating averaged Ptx_Total values ( filter)
RNC applies sliding window averaging using WinAcRabSetupDl to obtain av Ptx_Total
Ptx_total can be expressed as the sum of the power caused by the non-controllable
traffic, Ptx_nc, and the power caused by the controllable traffic of non-real-time users,
Ptx_nrt:

Ptx _ total = Ptx _ nc + Ptx _ nrt

Ptx_Total can be calculated in the same way as Prx_Total


For each RAB request the admission control has to estimate the increase in the total non-
controllable transmission power (caused by the new RAB), Ptx_NC

40 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Estimation of DL Ptx_NC
No load curve is used to estimate the power increase associated with a new RAB
The increase in non-controllable power due to a new RT RAB, Ptx_nc, is calculated using;
Estimation for Tx power increase due to admission of a reference RAB
Estimations due to the increase from other RAB are calculated by multiplying the
power of the reference RAB by an appropriate normalising factor based on the ratio
between the bit rates and Eb/No targets of the reference RAB and requesting RAB.
The default reference RAB/service is voice AMR 12.2 kbps which is specified using;
DLreferenceBitRate (Riref) = Bit rate of reference RAB/service (12.2 kpbs)
DLreferenceTargetBLER = value for target BLER for reference service (value is 10log
BLER)(note: DLreferenceTargetBLER is used to obtain the Eb/No target of the reference
RAB (ref)
CPICHtoRefRABoffset

41 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Estimation of DL Ptx_nc
Ptx_nc + Ptx_nc Ptx_target The current transmission power of an active-set base
or station, Ptx_total, is increased by the required maximum
P tx _ total Ptx _ t arg et _ BS power of the requesting user, Ptx, and by the required
total power of the inactive real-time users, Ptx_rt,inactive
Ptx _ nc = Ptx _ total Ptx _ nrt (for which the RB is still in the establishment phase)

Ptx _ nc = Ptx + Ptx ,inactive

Together with the DL admission decision equation the maximum allowed DL


transmission power per connection limits the coverage (and capacity) of
certain user (using certain service)

42 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Estimation of DL Ptx_nc
The maximum DL transmission power per connection is determined by the parameter
CPICHToRefRABOffset and the scaling factor

Ptx = Ptx , max = P_CPICH-CPICHtorefRABoffset+scaling factor


scaling factor is the mapping of the max power to the actual bearer based on the
wanted service bitrate and downlink Eb/No compared to the reference service
bitrate and Eb/No (12.2 kbps AMR)
The maximum link power is defined so that the CPICH coverage and the
service coverage are ALWAYS the same

CPICH coverage
=
Service Coverage

43 NOKIA 1999 31/10/2002 RANPAR Version 1.0


P-CPICH Transmission Power Offset
CPICHtoRefRABoffset

The parameter defines the offset of the primary CPICH transmission power, and the
maximum DL transmission power of the reference service channel in DL power allocation

The maximum transmission power of the reference service is calculated (in dBm) by
subtracting the value of the parameter from the transmission power of the primary CPICH

range : -10 ... 17 dB, step 0.5 dB


default : 2dB

Note that the default value is obtained for AMR 12.2 kbit/s due to that the AMR speech is
probably the most used service

44 NOKIA 1999 31/10/2002 RANPAR Version 1.0


DL Bit Rate of the Reference Service

DLreferenceBitRate (RI ref )

The parameter defines the downlink bit rate of the reference service. Reference service is
used in the determination of the maximum downlink code channel transmission power

The service is considered to be AMR speech, if the bit rate is one of the followings: 12.2,
10.2, 7.95, 7.4, 6.7, 5.9, 5.15, 4.75 (kbit/s). Otherwise the service is data service

range : 0.01 ... 16000 kbit/s , step 0.01 kbit/s


default : 12.2 kbit/s

Note that the default value is obtained for AMR 12.2 kbit/s speech service

45 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Estimation of DL Ptx_nc
P tx_nc + P tx_nc P tx_target
or Ptx _ nc = Ptx _ total Ptx _ nrt The power needed by the inactive (still in
P tx _ total Ptx _ t arg et _ BS establishment phase) RT RBs Ptx_rt,inactive
Ptx _ nc = Ptx + Ptx ,inactive can be calculated by summing all the RBs
together by using the same formula(s) as
before

Ptx ,inactive = (P_CPICH-CPICHtorefRABoffset+


{RB , rt _ inactive
}
scaling factor)

Each time data transfer begins in the DCH the corresponding portion of the inactive RT
RB is removed from the equation above at the time next RRI report (or perhaps after
several periods depending on the RAB queuing parameters) is received from the BTS
Therefore MAC has to inform AC,LC and PS when the data transfer is activated in DCH
at RL setup

46 NOKIA 1999 31/10/2002 RANPAR Version 1.0


DL Cell Load Admission Criteria Thresholds

For the RB to be established the increase of the non-controllable load Ptx_nc is


estimated on the basis of the measured P tx _ total
Then the estimated non-controllable DL power and the average measured total DL
transmission power P tx _ total are compared against their thresholds
If either or both of them are exceeded then the RAB can not be admitted

Ptx_nc+ Ptx_nc Ptx_target


Ptx_nc = Ptx_total Ptx_nrt or Ptx_nc = Ptx + Ptx,inactive
Ptx _ total Ptx _ t arget _ BS

47 NOKIA 1999 31/10/2002 RANPAR Version 1.0


DL Admission Decision

Ptx_Target_BS

Ptx_Target

Ptx_NC Ptx_NC

PtxTotal PtxTotal
Ptx_NC Ptx_NC

Case I Case II
Ptx_NC + Ptx_NC Ptx_Target Ptx_NC + Ptx_NC Ptx_Target
PtxTotal Ptx_Target_BS Ptx_Target PtxTotal Ptx_Target_BS

RT RAB admitted (as well as NRT) RT RAB admitted

48 NOKIA 1999 31/10/2002 RANPAR Version 1.0


DL Admission Decision

Ptx_Target_BS

Ptx_NC
Ptx_Target

Ptx_NC
PtxTotal
PtxTotal
Ptx_NC
Ptx_NC

Case III Case IV


Ptx_NC + Ptx_NC Ptx_Target Ptx_NC + Ptx_NC Ptx_Target
PtxTotal Ptx_Target_BS
Prx_target PrxTotal Prx_Target_BS

RT RAB denied (as well as NRT) RT RAB denied (NRT RAB permitted)

49 NOKIA 1999 31/10/2002 RANPAR Version 1.0


DL Admission Procedure Summary
BTS sends periodically the total transmitted DL power
PtxTotal
to the RNC [dBm]

Cell maximum [dBm]


RNC compares the measured transmitted power levels
against the thresholds PtxTarget [dBm]+ OVER
LOAD
PtxOffset [dB] AREA
If measured DL (PTxTotal) transmitted power exceeds MARGINAL
Over overload thresholds (PtxTarget+PtxOffset) no RABs LOAD
AREA
Load can be admitted and NRT bitrates are reduced until PtxTarget [dBm]
PtxTotal reaches again PtxTarget FEASIBLE
LOAD
If measured DL (PtxTotal) transmitted power exceeds AREA

Marginal target thresholds (PtxTarget) AC can admit NRT RABs Load curve in DL
Load to the cell (no RT RABs can be admitted). The NRT
RAB bitrates can not be increased and they remain at
the same level as after previous scheduling period 0 1 Load
In feasible load area the admission decision is based [0...1]
Feasible on the power rise estimate of the new RT bearer
Load
P tx_total + P tx P tx_target
In case the RAB can not be admitted it is put
If the resulting power is still below PtxTraget the
into the queue
RAB is admitted

50 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Admission Control
AC Functional Overview
UL admission control
Power allocation in UL
DL admission control
Power allocation in DL

51 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Initial DL Power Allocation
The determination of the transmission power requires knowledge about several
parameter values:
required Eb/No of the connection ( = Eb N 0 )
signal-to-interference ratio per chip of the CPICH ( c = Ec I 0) measured by the UE
W is the chip rate, R is bit rate, Ptx_total is measured by the base station (and
reported back to the RNC in Radio Resource Indication)
Ptx_CPICH is the CPICH power (determined by PtxPrimaryCPICH)
is the orthogonality factor

R 1
Ptx = Ptx, CPICH Ptx_total
W c

52 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Initial DL Power Allocation
Example

64 kbit/s service with required DL Eb/No: 4.5dB = 2.82


PtxCPICH: 30dBm = 1 W
= 0.5, Ptx_total= 37dBm (5.011)
measured Ec/Io (by the UE) -10dB = 0.1
Therefore:
Ptx_init = 2.82*64/3840*(1/0.1*1-0.5*5.011) = 352.24mW (25.47dBm)

53 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Downlink power allocation of a radio link
When radio link is established or modified both maximum DL transmission power and
minimum DL transmission power has to be determined for it
The average power of transmitted DPDCH symbols over one timeslot must not exceed
maximum DL transmission power, or it can not be below minimum DL transmission
power
The power control dynamic range of BTS is the difference between the maximum and
the minimum transmit output power of a code channel

54 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Downlink power allocation of a radio link
The maximum DL power is the
lowest of these three values for
NRT and Multirab
PTxTotalMax (Max total power of NodeB)
PtxDLabsMax
(Maximum planned DL
power of a radio link) This
parameter sets the +PTxDPCHMax (default -3 dB)
maximum power for any
radio link, only NRT and P_CPICH (Absolute CPICH power of cell)
Multirab.. CPICHtoRefRABOffset (def 2 dB)
SF_adjustment
PCrangeDL

PCrangeDL (default 15 dB)


PCrangeDL

+PTxDPCHmin (default -28 dB)

In most cases we are operating in this The minimum DL power is the


range for voice. For PS data the maximum of these value
PTxDLabsMax can be lower than the
upper limit dictated by this
55 NOKIA 1999 31/10/2002 RANPAR Version 1.0
How it is actually done
Define maximum radio link power:
RT: Ptx_max_rl=min{P_CPICH-CPICHtorefRABoffset+SF_adjustment, Ptxtotalmax-
PTxDPCHmax}
NRT & Multirab: Ptx_max_rl=min{P_CPICH-CPICHtorefRABoffset+SF_adjustment,
Ptxtotalmax-PTxDPCHmax, PTxDLabsMax}
Define minimum radio link power:
Ptx_min_rl=max{Ptx_max_rl-PCrangeDL, Ptxmax-PTxDPCHmin}
SF_adjustment is the mapping of the max power to the actual bearer
based on spreading factor and downlink Eb/No compared to the
reference service (12.2 kbps AMR)

RI max
RI max,eff =
ref RI ref

56 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Maximum DL Ptx of the Radio Link
Example

64 kbit/s service with required DL Eb/No: 4.5dB =2.82


Reference service: speech 12.2kbit/s Eb/No 5.5dB = 3.548
CPICHtoRefRabOffset = 2dB (for speech)
PtxCPICH: 30dBm = 1W
SF_Adjustment= 2.82*64/(3.548*12.2) = 4.17
PtxCPICH - CPICHtoRefRabOffset = 30 dBm-2 dB=28 dBm= 0.630 W
Ptx_max_rl=min(4.17*0.630, 10W) = 2.63 W (34.20dBm)
Ptx_DPCH_max = PtxDPCHMax =3dB below the maximum power = 40dBm

57 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Minimum DL Ptx of the Radio Link
Example

Ptx_max = 2.63 W (34.20dBm)


Ptx,range = PCrangeDL =15dB
Ptx_DPCH_min = PtxDPCHMin = 28dB below the maximum power = 15dBm
Ptx_min_rl=max(34.20dBm - 15dB, 15 dBm) = max(19.20dBm, 15dBm)
=> Ptx_min_rl = 19.20dBm

58 NOKIA 1999 31/10/2002 RANPAR Version 1.0


DL Power Thresholds
PtxDPCHMax
Parameter defines the maximum code channel output power for the power control
dynamic range of BTS. The maximum transmission power is calculated by adding the
value of the parameter to the BTS maximum output power (Pmax in dBm).
range: -3 ... 0dB , step 0.1dB
default: -3 dB

PtxDPCHMin
Parameter defines the minimum code channel output power for the power control
dynamic range of BTS. Minimum transmission power is calculated by adding the value
of the parameter to the BTS maximum output power (Pmax in dBm).
range: -60 ... 28dB , step 1dB
default: -28 dB

59 NOKIA 1999 31/10/2002 RANPAR Version 1.0


DL Power Control Dynamic Range
PCrangeDL

The parameter defines the downlink power control range in relation to the maximum
allocated transmission power of the radio link

The minimum transmission power is achieved by subtracting the value of the parameter
from the maximum transmission power of the radio link

However, the minimum BTS output power of the code channel defines the absolute lower
limit for the minimum transmission power

range: 0 ... 25 dB, step 1 dB


default: 15dB

60 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Planned Maximum DL Ptx of the Radio Link
PtxDLabsMax
The planned maximum downlink transmission power of radio link. This parameter is
used in the downlink power allocation when CCTrCH includes one or more DCH's of
interactive or background traffic class RAB's. The allocated power of a radio link
cannot exceed the value of this parameter. The parameter is set separately for each
cell. This parameter is the planned maximum, not the physical limit.

range: -10 ... 50 dBm, step 0.1 dBm


default: 50 dBm

61 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Admission Control in case of Congestion
If there are no Iub resources available the admission request will be denied.
The purpose of the pre-emption procedures is to immediately offer a
service of a guaranteed level to the subscribers in a temporary resource
congestion situation. RT RAB pre-emption is possible.
In case of congestion RT RAB pre-emption procedure is possible for RT or
emergency call, when RT RABs which has RAB based indication "vulnerable
to pre-emption" are released.
RT over NRT procedure can also be applied
NRT RAB bitrate can go to 0 kbits/s in case of congestion

62 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Admission Control (AC) Summary
Iu

RAB setup/modify/release request


Handover Control
Active state mobility RB information
Admission Control Packet Scheduler
control
RAB admission decision Load Radio resource
Active set
Load change estimation information scheduling
information
Producing L2 parameters
Producing TFS Target BLER, Power Control
Resource DL power allocation B ER and SIR
information UL Outer loop
power control
Resource
request Load change
Load
information
Resource Manager information
Radio resource information Load Control
Code allocation
Transport resource allocation Producing of load
information

63 NOKIA 1999 31/10/2002 RANPAR Version 1.0


Admission Control for RT and NRT (RAN1.5)
RRC
RRC connection
connection setup
setup RAB
RAB setup
setup
Admitted
Admitted if
if total
total load
load is
is below
below Admitted
Admitted if
if non-controllable
non-controllable load
load
overload
overload threshold
threshold added
added by
by estimated
estimated change
change is
is below
below
target
target and
and total
total load
load is
is below
below
Emergency
Emergency If
If total
total load
load is
is above
above overload
overload overload threshold
overload threshold
call
call threshold,
threshold, RRC connection over
RRC connection over NRT
NRT and
and
RT
RT RAB
RAB pre-emption
pre-emption procedures
procedures can
can be
be If
If non-controllable
non-controllable load
load added
added by
by
applied
applied estimated
estimated change
change isis above
above target,
target, RT
RT
RAB
RAB pre-emption
pre-emption procedure
procedure can
can be
be
Admitted
Admitted if
if non-controllable
non-controllable load
load is
is applied
applied
below target and total load is below
below target and total load is below
overload
overload threshold
threshold If
If total
total load
load is
is above
above overload
overload
RT
RT threshold,
threshold, RTRT over
over NRT
NRT procedure
procedure can
can be
be
If
If total
total load
load is
is above
above overload
overload applied
applied
threshold,
threshold, RRC
RRC connection
connection over
over NRT
NRT
procedure can be applied
procedure can be applied

Admitted
Admitted if
if non-controllable
non-controllable load
load is
is Admitted
Admitted if
if total
total load
load is
is below
below
NRT below
below target
target and
and total
total load
load is
is below
below overload
overload threshold
threshold
NRT overload threshold
overload threshold

During SHO branch addition is possible in the case when total DL load is less than
the overload threshold, valid both for RT and NRT traffic
64 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Chapter 4
-Admission Control-

1. What is the admission control needed for?

2. What triggers execution of the admission control?

3. Name main issues taken into account by AC.

4. What condition prevents the RT RAB to be admitted in the UL?

5. What condition prevents the RT RAB to be admitted in the DL?

6. What effect will cause too high/ too low PrxNoise?

65 NOKIA 1999 31/10/2002 RANPAR Version 1.0

You might also like