Sie sind auf Seite 1von 33

1 NOKIA 1999 31/10/2002 RANPAR Version 1.

0
Course Content
Radio Resource Management Overview
Parameter Configuration
Common Channels & Power Control
Load Control
Admission Control
Packet Scheduling
Handover Control
Resource Manager
2 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
3 NOKIA 1999 31/10/2002 RANPAR Version 1.0
AC Functional Overview
UL admission control
Power allocation in UL
DL admission control
Power allocation in DL
Dynamic Link Optimisation (DyLo)
Admission Control
4 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Admission Control Functional Overview
Maximises capacity whilst maintaining stability
Decides if new RAB request is admitted into RAN
AC decision procedure set according to whether;
Request is for RRC connection and RT or NRT RAB Setup
RAB setup can be for call setup or handover
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 & E
b
/N
o
targets
initial SIR target (used in Outer Loop PC) & upper and lower limits for the uplink SIR target
LC LC LC
AC
Network based functions
PS PS PS
RM RM RM
RNC
5 NOKIA 1999 31/10/2002 RANPAR Version 1.0
RAB
Establishment
6
Admission Control Functional Overview
RAB attributes (HLR);
SDU error ratio
traffic class
max bit rate
Nokia
RNC
Core
Network
RAB ASSIGNMENT REQUEST
NRT PS
call
AC RAB
admitted
RAB
request
denied
Queue
RAB
Radio Access Bearer
Service Request
1
Quality Requirements
of Radio Bearer
2
RB attributes (RNC);
target BLER
target Eb/No
initial SIRtarget
Admission
Decision
4
RT CS call
Power Increase
Estimates
3
UL/DL Load Change
Report to LC
5
RRC Connection
Establishment
0
NRT Admission
Decision Process (PS)
6 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Radio Access Bearer Service Request
UE RNC MSC HLR
RAB Assignment Response
Setup
RAB Assignment Request
Call Proceeding
Alerting
Connect
Connect Acknowledge
RAB service attribute RAB service attribute value
Traffic Class Conversational
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
Delivery Order Yes
Maximum SDU size 244 / 204 / 159 / 148 / 134 / 118 / 103 /95 bits
Traffic Handling Priority Not applicable
Source statistics descriptor Speech
SDU Parameters RAB sub-flow 1
(Class A bits)
RAB sub-flow 2
(Class B bits)
RAB sub-flow 3
(Class C bits)
-
>
SDU error ratio 7 * 10
-3
- -
-
>
Residual bit error ratio 10
-6
7) 10
-3
5 * 10
-3
Delivery of erroneous SDUs yes - -
SDU format information 1-9
Sub flow SDU size 1-9
Sub flow SDU size parameters 10
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
7 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
EbNoSetIdentifier specifies
which Eb/No table is used
depending on the type of
antenna configuration used
RAB QoS
Attributes
RAB QoS
Attributes
BLER
Calculated
EbNo
Mapping
EbNo
Mapping
Initial SIR
Max SIR
Min SIR
Initial Pwr
Max Pwr
Min Pwr
Target Eb/Nos are used
in calculating SIR
targets, power/load
increase estimates, DL
power allocations
8 NOKIA 1999 31/10/2002 RANPAR Version 1.0
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:
Initial SIR target

DPCCH TFC
d
TFC
c
C
DCH DCH
C
DCH
RL DCH
DCH
DCH
DCH
b DPCCH UL
Init
SF
N RM
N RM
W
R
N
E
SIR
Max
Max
2
0
,
log 10

9 NOKIA 1999 31/10/2002 RANPAR Version 1.0


The maximum and minimum limits for SIR target are calculated from this initial value;
Initial SIR target
( ) ( )
DPCCH UL
Init
DCH
N
E
DCH
N
E DPCCH UL
SIR SIR
b b
,
min
,
min
0 0
+ =
( ) ( )
DPCCH UL
Init
DCH
N
E
DCH
N
E DPCCH UL
SIR SIR
b b
,
max
,
max
0 0
+ =
10 NOKIA 1999 31/10/2002 RANPAR Version 1.0
AC produces the TrCH parameters:
Transport Formats (TF)
Transport Format Combination (TFC)
TFC identifiers
TrCH Parameters
Supported
Bitrates
0
TFCS (SL & RT RB)
TrCh 1
TFI0
TFI1
64
128
384
0
TFI2
384
128
Peak Bitrate
In Bearer
Parameters
Sheduled
Bitrate
TFS for RT RB
intermediate
Bitrates
64
128
0
TFS subset
For TFCS
construction
64
0
TrCh 2
TFI0
TFI1
0
64
0
TFI1
TFI0 TFI0
11 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.
NRT traffic RT traffic
Conversational Conversational Streaming Streaming Interactive Interactive Background Background
AM
RLC
AM
RLC
AM
RLC
AM
RLC
TM
RLC
TM
RLC
DCH
DCH
UM
RLC
UM
RLC
DCH
DCH
TM
RLC
TM
RLC
DCH
DCH
UM
RLC
UM
RLC
DCH
DCH
AM
RLC
AM
RLC
DCH
DCH
RACH/FACH
RACH/FACH
DCH/DCH
DCH/DCH
DCH/HS-DSCH
DCH/HS-DSCH
PS domain CS domain
12 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
100%
_ _ _ _ _ _ _
_ _ _ _ _ _
_

=
signatures preamble Allowed frame RACH per Slots Access Available
frame RACH per preambles RACH Number Avg
load RACH
13 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
14 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
15 NOKIA 1999 31/10/2002 RANPAR Version 1.0
RACH load for NRT RABs admission
RachNormalLoadBS
RachLoadIndicationPeriod
RachOverloadBS
RACH load
WinRachOverloadBS
No NRT RAB admission
WinRachNormalLoadBS
NRT RAB
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)
Example values
WinRACHOverloadBS = 3
WinRACHNormalLoadBS = 3
1 x RACH load ind. period
16 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
17 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
18 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Mesurement Averaging Window for AC

BTS Measurements
RRI Period
WinACRABsetupDL/UL

=
+
=
m
j
j n
total rx Total x
m
P
1
_ _ Pr
1
19 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
20 NOKIA 1999 31/10/2002 RANPAR Version 1.0
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
AC RAB Queuing Time
21 NOKIA 1999 31/10/2002 RANPAR Version 1.0
AC Functional Overview
UL admission control
Power allocation in UL
DL admission control
Power allocation in DL
Dynamic Link Optimisation (DyLo)
Admission Control
22 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
Average total DL transmit power
Non-controllable UL power Prx_NC = - Prx_NRT
Non-controllable DL power Ptx_NC = - 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
total rx P _
total tx P _
total rx P _
total tx P _
23 NOKIA 1999 31/10/2002 RANPAR Version 1.0
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;
UL Cell Load Admission Decision Process
rx_target rx_nc rx_nc P P P +
BS et t rx
total rx P P
_ arg _
_
or
power
load
max planned load
max planned power
?
24 NOKIA 1999 31/10/2002 RANPAR Version 1.0
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
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;
nrt rx nc rx total rx
P P P
_ _ _
+ =
Calculation of UL Prx_nc
nrt rx total rx nc rx
P P P
_ _ _
=
determined by PS
and delivered to AC
through LC Measured by Node B
and sent to RNC
25 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Estimation of UL Prx_nc
AC estimates the increase in the total non-
controllable UL power of a cell using a
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
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
Non-Controllable power is calculated by AC
using integral method and using the Load vs.
P
rx_nc
curves maintained by AC for every cell
L
L
Prx_nc
Prx_nc
Load factor
rx_target rx_nc rx_nc P P P +
BS et t rx
total rx P P
_ arg _
_
or
Current load L and
current received Non-
Controllable power
P
rx_nc
are measured
26 NOKIA 1999 31/10/2002 RANPAR Version 1.0
The estimated non-controllable UL interference power and the average measured
total UL interference are compared against their thresholds ->
If either or both are satisfied then the RAB can not be admitted
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
UL Cell Load Admission Criteria Thresholds
total rx P _
rx_target rx_nc rx_nc P P P +
BS et t rx
total rx P P
_ arg _
_
or
Prx_target_BS =
PrxNoise + PrxTarget + PrxOffset
Prx_target =
PrxNoise + PrxTarget
27 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Impact of Inaccurate Parameter Setting
AC likely to admit more capacity requests than it should
(higher actual interference floor increase than calculated)
PrxNoise set too high
NR = PrxNoise / Prxtotal
(Interference floor increase)
used in AC
Actual
Noise Floor
Uplink Load
Calc.
Interf.
floor
increase
PrxTotal
PrxNoise
Actual
interf.floor
increase
PrxNoise set
too high
PrxTarget
28 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Load < PrxTarget
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
Impact of Inaccurate Parameter Setting
RAB for new
user admitted
29 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Impact of Inaccurate Parameter Setting
AC likely to deny more capacity requests than it should
(lower actual interference floor increase than calculated)
PrxNoise set too low
NR = PrxNoise / Prxtotal
(Interference floor increase)
used in AC
Actual
Noise Floor
Uplink Load
PrxTotal
PrxNoise
Calc.
Interf.
floor
increase
Actual
interf.floor
increase
PrxNoise set
too low
30 NOKIA 1999 31/10/2002 RANPAR Version 1.0
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
Impact of Inaccurate Parameter Setting
Load >= PrxTarget
RAB for new
user denided
31 NOKIA 1999 31/10/2002 RANPAR Version 1.0
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
possible for the AC/PS to admit
NRT services and (AC) and
schedule (allocate) bitrate for
NRT services
however bitrate (load) increase
for NRT is not possible
Prx_NC
[dBm]
PrxTotal
[dBm]
PrxNoise [dBm] + PrxTarget [dB]
PrxNoise [dBm] + PrxTarget [dB] + PrxOffset [dB]
Parameters
Note:
PrxTarget_BS is defined as PrxTarget + PrxOffset
PtxTarget_BS is defined as PtxTarget + Ptx Offset
32 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Prx_NC
PrxTotal
Prx_NC + Prx_NC Prx_Target
PrxTotal Prx_Target_BS
RT RAB admitted (as well as NRT)
Admission Decisions
Prx_NC
Prx_Target_BS
Prx_Target
Case I Case II
Prx_NC
PrxTotal
Prx_NC
Prx_NC + Prx_NC Prx_Target
Prx_Target PrxTotal Prx_Target_BS
RT RAB admitted
33 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Prx_NC
PrxTotal
RT RAB denied (as well as NRT)
Admission Decisions
Prx_NC
Prx_Target_BS
Prx_Target
Case III Case IV
Prx_NC
PrxTotal
Prx_NC
RT RAB denied (NRT RAB permitted)
Prx_NC + Prx_NC Prx_Target
PrxTotal Prx_Target_BS
Prx_NC + Prx_NC Prx_Target
Prx_target PrxTotal Prx_Target_BS
34 NOKIA 1999 31/10/2002 RANPAR Version 1.0
UL Admission Procedure Summary
BTS sends periodically the received UL power to the RNC
Fractional load
[0..1]
OVER
LOAD
AREA
MARGINAL
LOAD
AREA
FEASIBLE
LOAD
AREA
0
Load curve in UL
PrxTotal
[dBm]
PrxNoise [dBm]
PrxTarget [dB]
PrxTarget [dB]+
PrxOffset [dB]
1
Noise Rise
NR [dB]
XX [dB]
RNC compares the measured received power levels against the set
thresholds
If measured UL (PrxTotal) load exceeds target thresholds (PrxTarget) AC
can admit NRT RABs to the cell. The NRT RAB bitrate can not be
increased and remains at the same level as after previous scheduling
period
If measured UL (PrxTotal) load exceeds overload thresholds
(PrxTarget+PrxOffset) no RABs can be admitted and NRT bitrates are
reduced until PrxTotal reaches again PrxTarget
Over
Load
Marginal
Load
Feasible
Load
In feasible load area the admission decision is based on the power rise
estimate of the new RT bearer
If the resulting power is still below PrxTraget the RAB is admitted
rx_target rx_nc rx_nc P P P +
In case the RAB can not be admitted it is put
into the queue
35 NOKIA 1999 31/10/2002 RANPAR Version 1.0
AC Functional Overview
UL admission control
Power allocation in UL
DL admission control
Power allocation in DL
Dynamic Link Optimisation (DyLo)
Admission Control
36 NOKIA 1999 31/10/2002 RANPAR Version 1.0
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
DPCCH Initial Power
37 NOKIA 1999 31/10/2002 RANPAR Version 1.0
The value of the DPCCH_Power_offset is determined by the equation
) log( 10
DPCCH DPCCH RSSI CPICH
SF SIR Rx Tx + + = DPCCH_POWER_OFFSET
Where:
Tx
CPICH
is the transmission power of Primary CPICH given by the RNP parameter PtxPrimaryCPICH
Rx
RSSI
is the received wide band interference power measured by BTS and offered by LC
SIR
DPCCH
is the required received SIR for DPCCH; it equals to the initial DPCCH SIR target
SF
DPCCH
is the spreading factor of the UL DPCCH
DPCCH Power Offset
38 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
39 NOKIA 1999 31/10/2002 RANPAR Version 1.0
AC Functional Overview
UL admission control
Power allocation in UL
DL admission control
Power allocation in DL
Dynamic Link Optimisation (DyLo)
Admission Control
40 NOKIA 1999 31/10/2002 RANPAR Version 1.0
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 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
nrt tx nc tx total tx
P P P
_ _ _
+ =
Estimation of DL Ptx_nc
41 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 E
b
/N
o
targets of the reference RAB and requesting RAB.
The default reference RAB/service is voice AMR 12.2 kbps which is specified using;
DLreferenceBitRate (Ri
ref
) = 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 E
b
/N
o
target of the reference
RAB (
ref
)
CPICHtoRefRABoffset
42 NOKIA 1999 31/10/2002 RANPAR Version 1.0
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)
The current transmission power of an active-set base
station, Ptx_total, is increased by the required maximum
power of the requesting user, Ptx, and by the required
total power of the inactive real-time users, Ptx_rt,inactive
(for which the RB is still in the establishment phase)
tx_target tx_nc tx_nc P P P +
BS et t tx
total tx P P
_ arg _
_
or
nrt tx total tx nc tx
P P P
_ _ _
=
inactive tx tx nc tx
P P P
, _
+ =
Estimation of DL Ptx_nc
43 NOKIA 1999 31/10/2002 RANPAR Version 1.0
The maximum DL transmission power per connection is determined by the parameter
CPICHToRefRABOffset and the 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)
CPICH coverage
=
Service Coverage
The maximum link power is defined so that the CPICH coverage and the
service coverage are ALWAYS the same
Estimation of DL Ptx_nc
P_CPICH-CPICHtorefRABoffset+scaling factor = =
max , tx tx
P P
44 NOKIA 1999 31/10/2002 RANPAR Version 1.0
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
P-CPICH Transmission Power Offset
45 NOKIA 1999 31/10/2002 RANPAR Version 1.0
DLreferenceBitRate ( )
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
ref
RI
DL Bit Rate of the Reference Service
46 NOKIA 1999 31/10/2002 RANPAR Version 1.0
The power needed by the inactive (still in
establishment phase) RT RBs Ptx_rt,inactive
can be calculated by summing all the RBs
together by using the same formula(s) as
before
tx_target tx_nc tx_nc P P P +
BS et t tx
total tx P P
_ arg _
_
or
nrt tx total tx nc tx
P P P
_ _ _
=
inactive tx tx nc tx
P P P
, _
+ =
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
Estimation of DL Ptx_nc
{ }

=
inactive rt RB
inactive tx
P
_ ,
,
(P_CPICH-CPICHtorefRABoffset+scaling factor)
47 NOKIA 1999 31/10/2002 RANPAR Version 1.0
For the RB to be established the increase of the non-controllable load Ptx_nc is
estimated on the basis of the measured
Then the estimated non-controllable DL power and the average measured total DL
transmission power are compared against their thresholds
If either or both of them are exceeded then the RAB can not be admitted
total tx P _
total tx P _
tx_target tx_nc tx_nc P P P +
BS et t tx
total tx P P
_ arg _
_
or
= + P
tx,inactive
P
tx_nc
= P
tx_total
P
tx_nrt
tx P tx_nc P
DL Cell Load Admission Criteria Thresholds
48 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Ptx_NC
PtxTotal
Ptx_NC + Ptx_NC Ptx_Target
PtxTotal Ptx_Target_BS
RT RAB admitted (as well as NRT)
DL Admission Decision
Ptx_NC
Ptx_Target_BS
Ptx_Target
Case I Case II
Ptx_NC
PtxTotal
Ptx_NC
Ptx_NC + Ptx_NC Ptx_Target
Ptx_Target PtxTotal Ptx_Target_BS
RT RAB admitted
49 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Ptx_NC
PtxTotal
RT RAB denied (as well as NRT)
DL Admission Decision
Ptx_NC
Ptx_Target_BS
Ptx_Target
Case III Case IV
Ptx_NC
PtxTotal
Ptx_NC
RT RAB denied (NRT RAB permitted)
Ptx_NC + Ptx_NC Ptx_Target
PtxTotal Ptx_Target_BS
Ptx_NC + Ptx_NC Ptx_Target
Prx_target PrxTotal Prx_Target_BS
50 NOKIA 1999 31/10/2002 RANPAR Version 1.0
BTS sends periodically the total transmitted DL power
to the RNC
RNC compares the measured transmitted power levels
against the thresholds
If measured DL (PtxTotal) transmitted power exceeds
target thresholds (PtxTarget) AC can admit NRT RABs
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
If measured DL (PTxTotal) transmitted power exceeds
overload thresholds (PtxTarget+PtxOffset) no RABs
can be admitted and NRT bitrates are reduced until
PtxTotal reaches again PtxTarget
Over
Load
Marginal
Load
Feasible
Load
In feasible load area the admission decision is based
on the power rise estimate of the new RT bearer
If the resulting power is still below PtxTraget the
RAB is admitted
In case the RAB can not be admitted it is put
into the queue
OVER
LOAD
AREA
MARGINAL
LOAD
AREA
FEASIBLE
LOAD
AREA
Load curve in DL
PtxTotal
[dBm]
PtxTarget [dBm]
PtxTarget [dBm]+
PtxOffset [dB]
Cell maximum [dBm]
Load
[0...1]
0
1
tx_target tx tx_total P P P +
DL Admission Procedure Summary
51 NOKIA 1999 31/10/2002 RANPAR Version 1.0
AC Functional Overview
UL admission control
Power allocation in UL
DL admission control
Power allocation in DL
Admission Control
52 NOKIA 1999 31/10/2002 RANPAR Version 1.0
The determination of the transmission power requires knowledge about several
parameter values:
required Eb/No of the connection ( )
signal-to-interference ratio per chip of the CPICH ( ) measured by the UE
Wis 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
0
N E
b
=
0
I E
c c
=
Initial DL Power Allocation

= tx_total CPICH tx,


1
P P
W
R
P
c
tx

53 NOKIA 1999 31/10/2002 RANPAR Version 1.0


64 kbit/s service with required DL Eb/No: 4.5dB = 2.82
PtxCPICH: 30dBm = 1 W
= 0.5, P
tx_total
= 37dBm (5.011)
measured Ec/Io (by the UE) -10dB = 0.1
Therefore:
P
tx_init
= 2.82*64/3840*(1/0.1*1-0.5*5.011) = 352.24mW (25.47dBm)
Initial DL Power Allocation
Example
54 NOKIA 1999 31/10/2002 RANPAR Version 1.0
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
Downlink power allocation of a radio link
55 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Downlink power allocation of a radio link
PTxTotalMax (Max total power of NodeB)
CPICHtoRefRABOffset (def 2 dB)
SF_adjustment
+PTxDPCHmin (default -28 dB)
+PTxDPCHMax (default -3 dB)
P_CPICH (Absolute CPICH power of cell)
PCrangeDL (default 15 dB)
The maximum DL power is the
lowest of these three values for
NRT and Multirab
The minimumDL power is the
maximumof these value
PCrangeDL
In most cases we are operating in this
range for voice. For PS data the
PTxDLabsMax can be lower than the
upper limit dictated by this
PtxDLabsMax
(Maximum planned DL
power of a radio link) This
parameter sets the
maximum power for any
radio link, only NRT and
Multirab..
PCrangeDL
56 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)
ref ref
eff
RI
RI
RI

max
max,
57 NOKIA 1999 31/10/2002 RANPAR Version 1.0
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)
P
tx_DPCH_max
= PtxDPCHMax =3dB below the maximum power = 40dBm
Maximum DL Ptx of the Radio Link
Example
58 NOKIA 1999 31/10/2002 RANPAR Version 1.0
P
tx_max
= 2.63 W (34.20dBm)
P
tx,range
= PCrangeDL =15dB
P
tx_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
Minimum DL Ptx of the Radio Link
Example
59 NOKIA 1999 31/10/2002 RANPAR Version 1.0
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
DL Power Thresholds
60 NOKIA 1999 31/10/2002 RANPAR Version 1.0
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
DL Power Control Dynamic Range
61 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
62 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
63 NOKIA 1999 31/10/2002 RANPAR Version 1.0
Admission Control (AC) Summary
RB information
Resource
information
Active set
information
Load change
information
Target BLER,
B ER and SIR
Load
information
Admission Control
RAB admission decision
Load change estimation
Producing L2 parameters
Producing TFS
DL power allocation
Iu
Packet Scheduler
Radio resource
scheduling
Load Control
Producing of load
information
Power Control
UL Outer loop
power control
Handover Control
Active state mobility
control
Resource Manager
Radio resource information
Code allocation
Transport resource allocation
Resource
request
RAB setup/modify/release request
Load
information
64 NOKIA 1999 31/10/2002 RANPAR Version 1.0
RRC connection setup
RRC connection setup
RAB setup
RAB setup
Admitted if total load is below
overload threshold
If total load is above overload
threshold, RRC connection over NRT and
RT RAB pre-emption procedures can be
applied
Admitted if total load is below
overload threshold
If total load is above overload
threshold, RRC connection over NRT and
RT RAB pre-emption procedures can be
applied
Admitted if non-controllable load is
below target and total load is below
overload threshold
If total load is above overload
threshold, RRC connection over NRT
procedure can be applied
Admitted if non-controllable load is
below target and total load is below
overload threshold
If total load is above overload
threshold, RRC connection over NRT
procedure can be applied
Emergency
call
Emergency
call
RT
RT
NRT
NRT
Admitted if non-controllable load is
below target and total load is below
overload threshold
Admitted if non-controllable load is
below target and total load is below
overload threshold
Admitted if non-controllable load
added by estimated change is below
target and total load is below
overload threshold
If non-controllable load added by
estimated change is above target, RT
RAB pre-emption procedure can be
applied
If total load is above overload
threshold, RT over NRT procedure can be
applied
Admitted if non-controllable load
added by estimated change is below
target and total load is below
overload threshold
If non-controllable load added by
estimated change is above target, RT
RAB pre-emption procedure can be
applied
If total load is above overload
threshold, RT over NRT procedure can be
applied
Admitted if total load is below
overload threshold
Admitted if total load is below
overload threshold
Admission Control for RT and NRT (RAN1.5)
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
65 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?

Das könnte Ihnen auch gefallen