Capacity Management

Admission Control & Congestion Control

 Capacity
management
Capacity >> LIMITED RESOURSES
• There is one code tree for each cell and each
DL Ch Codes carrier

UL & DL HW • Depends on installed capacity (UL CEs depend on

(Channel Elements) RAX boards and DL CEs depend on TX boards)

DL Transmitted Carrier
• Depends on the PA
Power

UL
• Radio conditions and traffic load
RTWP

UL & DL • Also limited by the code tree and settable by

Spreading Factor (SF) parameters

UL & DL
• Load measured in Air Speech Equivalents
ASE
Capacity >> LIMITED RESOURSES
• Depends on the license level and it is adjustable through
# HSDPA users parameters

• Depends on the license level and it is adjustable through

# EUL & 2ms EUL parameters

# EUL • Depends on the license level and it is adjustable through

non-serving) parameters

Transmission Bandwidth • Depends on installed capacity

EUL • Average rate of unhappy non-guaranteed users configured on

Scheduled rate EUL in one cell

# RLs in Compressed • The number of Radio Links in Compressed Mode

Mode

RRC Reject • Monitoring is done during a fix time interval. At the end of every time interval
the RRC Rejection Ratio is calculated from the number of admission requests
Ratio and the number of admission confirm messages sent.
Capacity Management

Admission Control

• accept/refuse new calls

Congestion Control

• detect and resolve overload situations

Dedicated Monitored
Resource Handling
• monitoring resources utilization
ADMISSION
CONTROL
ADMISSION Control POLICIES

BLOCKED

CONDITIONALLY BLOCKED

ADMITTED

Between the admission

If the resource is: and maximum level, (guaranteed, non-handover) or (non-
guaranteed, non-handover/handover)BLOCKED
requests are not admitted unless RN Soft Congestion
• Up till
actions canthe
findadmission
the required level, thetorequest
resources release. is admitted.
 Admission Request Attributes

• indicating whether the request for resources concerns a

Request Type handover of a connection or not (used in the
evaluation of admission policies).

• indicating whether the request for resources concerns

a request for guaranteed rate connection parts or
Request Class non-guaranteed connection parts (used in the
evaluation of admission policies).

Preemption • indicating whether this request can preempt a lower

priority (part of a) radio connection in case of resource
Capacity shortage.

Priority of the • (1..15)

request

Indication of additional resources required, including additional UL/DL

channelization codes, UL/DL ASE, and so on
 RAB ASSIGNMENT REQUEST message
RAB Parameters
RAB Assignment Request message IEs IE/Group Name
Information Elements RAB parameters
IE/Group Name Presence Range IE type and Semantics Criticality>Traffic Class
Assigned
reference description Criticality
Message Type M 9.2.1.1 YES >RAB Asymmetry Indicator
reject
RABs To Be Setup Or O YES ignore
Modified List
>RABs To Be Setup 1 to >Maximum Bit Rate
Or Modified Item IEs <maxnoofRABs>
>>First Setup Or M Grouping EACH >Guaranteed
reject Bit Rate
Modify Item reason:
same
>Delivery Order
criticality >Maximum SDU Size
>>>RAB ID M 9.2.1.2 The same -
RAB ID must >SDU parameters
only be
present in >Transfer Delay
one group.
>>>NAS O 9.2.3.18 - >Traffic Handling Priority
Synchronisation
Indicator
>>>RAB O 9.2.1.3 Includes all -
Parameters necessary
parameters >Allocation/Retention priority
for RABs
(both for
>Source Statistics Descriptor
3GPP
MSC and
SGSN)
including
QoS.
>Relocation Requirement

25.413 RANAP >Signalling Indication

>Extended Maximum Bit Rate

SOFT CONGESTION

• Increase accessibility in case of

What? resource shortage

• By admitting users in a cell in

How? case of resource shortage, if a
low priority user can lower its
rate or be preempted
SOFT CONGESTION ALGORITHM
Non-guaranteed requests can reduce the rate of
other lower priority, non-guaranteed connection parts
in steps. Example: from interactive PS 384/64 to
interactive PS 128/64, down to their lowest retainable
rate

Guaranteed requests can reduce the rate of

any priority, non-guaranteed connection parts in
steps down to their lowest retainable rate

If that is not sufficient, RN Soft Congestion can preempt

existing guaranteed RABs of lower priority, or non-
guaranteed RABs at the lowest retainable rate if request is
preemption capable and connection part targeted is
preemption vulnerable

RN Soft Congestion will not target users that have already ongoing HO
attempts, or that have been triggered (but not finished) to do soft congestion
actions by earlier admission requests.
SOFT CONGESTION ilustration

New User requesting New

PS RAB
64/HS

UL CE Admision
Limit Exceeded
128/HS 64/HS

Downgrade
 DOWnlink
channelization
Codes
 Downlink Channelization codes
SF 1

SF 2

SF 4
SF 8
SF 16
SF 32
SF 64
SF 128
SF 256

Channels Spread Factor Channels Spread Factor Channels Spread Factor

CPICH 256 PCH 256 HSDPA 16

BCH 256 PICH 256 PS 64/64 32
AICH 256 HS-SCCH 128 PS 64/128 16
FACH 64 Speech 128 PS 64/384 8
SF 1 SF 1

SF 2 SF 2

SF 4 SF 4
SF 8 SF 8
SF 16 SF 16
SF 32 SF 32
SF 64 10 HSDPA codes 1 user – R99 SF 64
FACH
SF 128 PS64/384 – SF 8
SF 64
SF 256 3 HS-SCCH 2 users – R99 08
Speech
26 Hs users PS64/128 – SF 16 users – CPICH

– A-DCH 4 users – R99 SF 128 BCH

PS64/64 – SF 32 AICH

PCH
PICH
 Downlink Channelization
› The admission request can be granted if the resource usage plus the
additional SF is below the admission level dlCodeAdm.

› Admission limit (dlCodeAdm) is set to 90% (reserving 10% of the code

tree for new handover legs).

PS R99, HS, Conditionally

Granted Blocked Blocked
Voice,VT - Setup Soft Congestion

Voice,VT - HO Granted Granted Blocked Downlink Code Usage %

+ Additional Request
0% dlCodeAdm 100%
90%
Downlink Channelization

BLOCKED

CONDITIONALLY
BLOCKED

ADMITTED
 DOWnlink
Transmitted
carrier power
DOWnlink Tx carrier power
100% (MaxTransmissionPower = MaxDlPowerCapability)

Congestion Control 99% (PowerOffset = 14)

Admission Control 85% (PowerAdm = 85)

User Traffic

20%

Common Channels
8 ~ 10%
CPICH
DOWnlink Tx carrier power
 DOWnlink Tx carrier power
› The admission request can be granted if the resource usage plus the
additional DL transmitted carrier power is below the admission level
pwrAdm.

› Admission limit (pwrAdm) is currently set to 85%.

› Monitored Dl Transmitted carrier power is considered for R99 traffic ( No
HSDPA Power)

PS R99, HS, Conditionally

Granted Blocked Blocked
Voice, VT- Setup Soft Congestion

Voice, VT- HO Granted Granted Blocked Downlink Pwr Usage %

+ Additional Request
0% PwrAdm
100%
85%
DOWnlink Tx carrier power

BLOCKED

CONDITIONALLY
BLOCKED

ADMITTED
 DL & UL
Spreading
FActors
 DL & UL Spreading FActors
› New Requests with SFXX, are denied if number of
connections exceed sfXXAdm
› UL SF Histogram Admission Policy
– sf4AdmUl, sf8AdmUl, sf16AdmUl, sf8gAdmUl
› DL SF Histogram Monitor Admission Policy
– sf8Adm, sf16Adm, sf32Adm, sf16gAdm
›
Actual configuration
Actual configuration
sf8Adm = 3
sf4AdmUl = 3
sf16Adm = 6
sf8AdmUl= 6
sf32Adm = 12
sf16AdmUl = 50
sf16gAdm = 6
sf8gAdmUl = 6
DL & UL Spreading FActors
Uplink Channel
Element Consumption Downlink Channel
Element Consumption
 UL & DL HW
(Channel Elements)
UL & DL HW
• CE is a measure of board capacity and radio bearer (RB)
Definition of CE capacity cost

• Downlink (DL): One AMR 12.2 kbps with SF=128

Normalization of 1 CE • Uplink (UL): One AMR 12.2 kbps with SF=64

• Different services have different HW consumption

Different Services (different Channel Elements consumption)

• Hardware consumption is related with the Symbol Rate >>

Hardware Consumption Inversely proportional to Spreading Factor (SF)

• due to different modulation scheme: QPSK (Downlink)

Spreading Factor is and BPSK (Uplink)
double in UL than in DL • BSPK (1bit per symbol). QPSK (2bits per symbol)
 UL & DL HW

› The admission request can be granted if the resource usage plus the
additional DL/UL Hardware is below the admission level dlHwAdm/
ulHwAdm.

› Admission limit dlHwAdm=100% (disabled) and ulHwAdm=90%.

PS R99, HS, Conditionally

Granted Blocked Blocked
Voice, VT- Setup Soft Congestion

Voice, VT- HO Granted Granted Blocked UL HW Usage% +

Additional Request
0% ulHwAdm
100%
90%
Other Admission
Policies
ASE Admision Policy
› Same behavior for Downlink and Uplink ASE
› ASE: Air Interface Speech Equivalents (ASE) in uplink and downlink
› This monitor accounts for the air interface resources usage in a cell.
› Currently DISABLED: ( No blocks due to UL/DL Ase)
– aseDlAdm=500 (MAX VALUE)
– aseUlAdm=500 (MAX VALUE)

PS R99, HS,
Granted
Voice, VT - Setup

Voice, VT - HO Granted
0% aseDlAdm=500
aseUlAdm=500
 Other Admission Policies

Compressed Mode Admission Policy

The policy aims to control the number of RLs allowed in compressed mode on cell level, in
order to limit the amount of DL power peaks caused by SF/2 compressed mode operation.

Serving HS-DSCH Admission Policy

By means of this policy it is possible to limit the number of simultaneous DL scheduled users
in a cell, preventing that many users have to share the available resources and get too low
throughput. hsdpaUsersAdm, maxNumHsdpaUser.

HS Setup Granted Blocked Blocked

HS HO Granted Granted Blocked Number of HS

Users
0 Users hsdpaUsersAdm=52 maxNumHsdpaUsers=64
 Other Admission Policies

Serving and Non-serving EUL Admission Policy

RN Admission Control must reject an EUL user, requesting the cell as serving cell if the total
number of serving cell EUL users including the requested is above eulServingCellUsersAdm
parameter.
EUL users can be in soft/softer handover. It is also possible to be able to limit the EUL users
having the cell as non-serving cell. This is to be able to limit the amount of UL hardware
reserved for the non-serving connections.
•eulServingCellUsersAdm, eulNonServingCellUsersAdm.
Congestion
Control
Congestion Control

› Detects and Resolves the following types of overload

UL RTWP

DL Cell Congestion

DL HSDPA Pwr
overload
Congestion
Detection
 UL RTWP CELL CONGESTION
Actually disabled
iFCong = 621= -49.9 dBm
iFHyst = 6000 = 60000ms

=6s

= 621

Congestion
No congestion Congestion
solved
UL RSSI EXAMPLE IN HIGH TRAFFIC CELL
DL Cell Congestion
Actual configuration
pwrAdm = 85%
pwrOffset = 14%

Congestion Congestion
No congestion
solved
DL CELL CONGESTION EXAMPLE
 DL HSDPA Congestion Detection

Congestion
No congestion Congestion
solved

Actual configuration
maxPowerOverloadHystTime = 10 s
Congestion
Resolve
HAndling
UL RTWP CELL Congestion
Resolve Handling

UL RTWP • Blocking all non handover

CELL requests until UL
CONGESTION congestion is resolved.
DL Cell and DL HSDPA Congestion
Resolve Handling

• Blocking all non handover requests

DL Cell & until UL congestion is resolved
DL HSDPA • RN Congestion Control starts
congestion resolve actions in the
Congestion cell.
Congestion Control Resolve Actions

• The interval between periodic congestion

resolve actions. The congestion resolve
Pace actions are periodic from the start of DL
congestion until the DL cell congestion
situation is resolved.

• The amount of ASE in DL to be released

Strength each congestion resolve action
CONGESTION CONTROL RESOLVE
=3s

= 3 ASE = 1 ASE

= 0.8 s =2s

Non-guaranteed RABs on dedicated, non-shared radio

channels are reduced to their lowest retainable rate in the
current radio configuration

Guaranteed RABs and non-guaranteed RABs

(remaining after step 1 and not on 0 kbps or on
common radio channels) on dedicated, non-shared
radio channels are released
Practical
examples
Spotting blocking in SMART
How to check • Check your RNCs RAB and RRC blocking counters
• The set of counters available in SMART is not
is there is comprehensive, but it is useful to spot some types of
blocking such as: DL Ch Codes blocking, DL Tx Power
blocking? Blocking, UL & DL HS (CEs)

How to solve • Analyze each case and check if there is room for
parameter optimization or coverage reduction
this cases?

I it solved • After applying the changes it is necessary to go back

now? to SMART and check if the statistics have improved
DF0586 RAB Blocking EXAMPLE
due to DL CH Codes & DL Tx Pwr
CR to clear W implementation of HSDPA+
rollback to default parameters
blocking

New CR to reduce blocking

IF you have a CSSR degradation

CSSR • If the CSSR is degraded and after

discarding alarms/unavailability of the site or
degradation surrounding sites
WHAT to look for?

RRC • In SMART you can easily isolate DL Ch Code and DL

Tx Pwr blocking
Blocking
RAB • In SMART you can easily isolate DL Ch Code, DL Tx
Pwr blocking, UL and DL HW, TN (transport network),
Blocking NB Speech, NB HS, UL and DL ASE, UL and DL SF

• In SMART you can check if there is time spent in

Congestion congestion state
RRC Blocking
RAB Blocking
Congestion
How to solve it with parametrization?
examples for some common issues

• Check is the sector does not have exceeded coverage

DL Ch Codes • Check the threshold dlCodeAdm (you can raise it by
steps upto 95%)
Blocking • Change the parameter numHsPdschCodes from the
default 5 to 3 or even 1

• Check is the sector does not have exceeded coverage

• Check the parameters pwrAdm and pwrOffset, increase
DL TX Pwr pwrAdm as much as possible taking into account that
pwrAdm + pwrOffset < 99%
• Check if it is possible to decrease primaryCpichPower

• Check is the sector does not have exceeded coverage

UL HW • Check if the site has maximum RAX board cofiguration
Additional
documents
Additional INFORMATION
› Presentation from previous workshops

› Ericsson document